RG12/10, flight day 206b/2012, Milton Keynes

[knpa]

Data location: /users/rsg/arsf/arsf_data/2012/flight_data/uk/RG12_10-2012_206b_Milton_Keynes

Data arrived from ARSF via SATA disk on 27/07/2012

RG12/10 Scientific objective:

RG12/10 Priority: 8 high

PI: Karen Anderson

Sensors:

Camera (11/09/2012)
Eagle (13/11/2012)
Hawk (13/11/2012)
LiDAR (13/11/2012)
LiDAR + FWF (Requested)

[knpa]

Changed Hawk raw file names from 1, 2, 1.1, 1.2 etc to match the Eagle.

[anhi]

Camera delivery created

[adbe]

Camera Delivery Check: No problems, ready to deliver

[adbe]

Hyperspectral delivery created

[knpa]

Beginning HS delivery check.

[knpa]

This is actually just an Eagle delivery as there was has been no boresight for the Hawk yet.

[knpa]

Finished Eagle delivery check.

All looks good apart from:
-Do we need to include a OSTN02_NTV2.gsb file? If so, put in ReadMe contents too.
-No screenshot with vectors - don't think we've gotten vectors. Need to ask PI if they don't mind us skipping this step.
-Need to remove Hawk examples from ReadMe delivery contents.

[adbe]

Removed OSTN02_NTV2.gsb file
Removed Hawk example from ReadMe contents
Renamed to eagle delivery

[adbe]

Delivered Camera to Karen Anderson on 11/09/2012 on disk 44

[anhi]

LiDAR delivery created, no full waveform or vectors.
Altitude 4980 feet
Pitch:-0.0027
Roll:+0.00002

[anhi]

milton_x line remade due to being flown at a different altitude to the other lines.
Altitude 5170 feet
Pitch:-0.00295
Roll:0.0002

[anhi]

LiDAR delivery created

[besm]

LiDAR delivery delivery-checked. I found the following issues:

• The reported minimum and maximum values of Y for each of the flightlines under "Per flight line statistics" in the readme appear to be wrong, they don't reflect the values of the LiDAR data, and seem unrealistic.
• proj_tidy.sh complains about the data quality report being missing, it's there but it's differently named. Either proj_tidy.sh or make_lidar_delivery.py probably needs to change. The exact filename of the data quality report probably isn't important.
• The proj_tidy.sh script kicks up about lidar_intensity_vectors_screenshot.jpg being missing, I don't think this is a problem, but best check.

[anhi]

• Read_Me remade with the minimum and maximum Y values corrected.
• LiDAR data quality report is named correctly, proj_tidy.sh probably should be updated.
• We do not have the vectors to create the LiDAR intensity vector screenshot.

[besm]

Looks okay now. proj_tidy.sh still complains about the logsheet being absent, but it's definitely there, so I'm marking this project as ready to deliver.

[anhi]

Hawk delivery created, eagle vectors still not arrived so will create Hyperspectral delivery

[anhi]

Hyperspectral delivery created

[anhi]

Hawk line 1 level 1 file remade. Believe the error had something to do with the header and the bil file being made on different days before/after the boresight.

[besm]

Appears to be ok. I found only one thing that didn't look right:

In FastQC, when opening the file h206b011b.bil, it warned that the file size of the bil in the header and the actual file size didn't match. The time of creation of the bil seemed completely wrong too. It's been re-made and there should be no problem now, BUT: We don't know what caused this.

Otherwise, all good.

[anhi]

Vector screenshots created and added to delivery, ready to make delivery of everything except LiDAR FWF.

[besm]

Redelivery checking, delivery has been remade with the vector overlays.

[besm]

Updated LiDAR data quality report in all known copies of delivery to November 09 2012 version.

Delivered everything, camera (again), hawk, eagle, LiDAR (no FWF) to Karen Anderson on 13/11/2012 on disk 132.