GB12/05, flight day 152a/2014, Monks Wood

[knpa]

Data location: /users/rsg/arsf/arsf_data/2014/flight_data/uk/GB12_05-2014_152a_Monks_Wood

Data arrived from ARSF via network transfer on 02/06/2014

GB12/05 Scientific objective: unknown

GB12/05 Priority: 8

PI: Ross Hill

Sensors:

Fenix (Requested), delivered 25/09/2014
LiDAR (Requested), delivered 29/10/2014
FW LiDAR (Requested but lower priority)
RCD (Not requested?)

[knpa]

This flight can not be processed until we have calibration data (day 141 looks like it's not usable).

[mark1]

Basestation PPP result:

Latitude = 52 18 26.95697
Longitude = -0 37 28.68639
Ell Height = 97.448

[mark1]

Navigation processing completed.

[mark1]

LiDAR processing started.

[mark1]

Stopped processing as we don't have an up to date lidar calibration for this project yet.

[mark1]

Renamed fenix raw files to have 'a' sortie in filename, also renamed files 6 sets of files from 'FENIX152a-14-1-1' to 'FENIX152a-14-12', 'FENIX152a-14-1-2' to 'FENIX152a-14-13' etc to be consistent and allow scripts to pick up file names.

[mark1]

SCT correcting of 17 flightlines has taken ~3.5 hrs (excluding the processing time). Processing final files for further checks and delivery creation.

[knpa]

Created HS delivery.

[stgo]

HS delivery check complete:

• I've changed the aplcorr command to point to the view vector bil file as it was segfaulting, haven't recreated the readme yet though.

• Line 1 has a bad pixel from band 400 to band 621 in the form of a white line at sample 145 which needs mentioning in the readme. This doesn't effect other lines.

[knpa]

Fixed above issues. Delivering.

[knpa]

This area is still waiting for vectors.

Have emailed Ross Hill if he wants a pre-vector delivery.

Autoreply says he is away until 4th August.

[mark1]

Made some slight corrections to read me file

[mark1]

Fenix timing corrections:

file	sct
-1	0.94
-2	0.95
-3	0.95
-4	0.95
-5	0.97
-6	0.95
-7	0.93
-8	0.95
-9	0.94
-10	0.95
-11	0.96
-12	0.95
-13	0.98
-14	0.96
-15	0.96
-16	0.97
-17	0.97

[knpa]

The HS has been blocked waiting for vectors since 25/07/14.

We've sent an email asking if Dr Hill would like delivery but have not had a reply.

Suggest sending another one when the LiDAR is ready.

[lah]

Started lidar processing with variable roll and pitch offsets:

File	Roll	Pitch
-1	-0.006022596	-0.00095719
-2	-0.005822596	-0.00080719
-3	-0.005822596	-0.00080719
-4	-0.005922596	-0.00085719
-5	-0.005672596	-0.00083219
-6	-0.005972596	-0.00090719
-7	-0.005522596	-0.00080719
-8	-0.006022596	-0.00095719
-9	-0.005422596	-0.00075719
-10	-0.006072596	-0.00105719
-11	-0.005422596	-0.00065719
-12	-0.006122596	-0.00125719
-13	-0.005222596	-0.00055719
-14	-0.006222596	-0.00125719
-15	-0.005122596	-0.00055719
-16	-0.006222596	-0.00135719
-17	-0.005822596	-0.00055719

[lah]

Lidar ready for delivery check.

[dap]

Hyperspectral data delivered to Dr Ross Hill, 25/09/2014

[dap]

Beginning LiDAR delivery check

[dap]

LiDAR Delivery Check

Complete. Found the following problems with the delivery located at GB12_05-152a-lidar-20140917:

• las1.2 files were produced but directory structure and read me states las1.0 files were produced.
• Hyperspectral section (page 4) in logsheet is blank - not sure if there is point in keeping it.
• Screenshots incorrectly named - I've renamed these so that they follow the convention using rename.sh .txt.jpg .jpg
• Flightline no. 10 is oddly shaped at the end, looks like it could be a range gate issue. This should be commented on in the data quality remarks section of the read me.
• proj_tidy.sh is complaining about there being no vectors intensity screenshot but, as noted above, PI was sent the pre-vector delivery enquiry and we did not get a response. Will therefore ignore this problem.
• Navigation files were incorrectly named, I've renamed these from BG12_05-2014-152a.* to BG12_05-2014_152a.*

I'm unsure of how to use demcompare.py so am unsure as to whether the output was good. I'll speak to mark1 about this upon his return.

Please address the above issues and resubmit for delivery check when finished.

[lah]

• Renamed to las1.2 to in the directory structure and in read me.
• Removed the extra page in logsheet. Script really needs changing to avoid doing this every time.
• Made comment about line 10 in read me.
• Ran dem compare (demcompare.py -d ./dem/GB12_05-2014_152a-lidar_ASTER-bng.dem --lidar flightlines/discrete_laser/ascii/ -l UKBNG -n ./navigation/BG12_05-2014_152a.sol) with means of -1.67 and -0.22.

[dap]

LiDAR Delivery Check

Checked the delivery again and found some minor problems:

• Table in logsheet on page 3 goes off the page
• Link for LAS specification links to LAS 1.0 spec, link address should be changed to ​http://www.asprs.org/a/society/committees/standards/asprs_las_format_v12.pdf

Edit: demcompare results weren't actually a problem, human error on my behalf!

[dap]

LiDAR Delivery Check

Re-checked the results from demcompare against acceptable values according to the delivery checking procedure and noticed that there was no problem with the results. Previous ticket amended accordingly.

Once the issues with the readme and logsheet (noted in previous ticket) are fixed, the dataset can be delivered.

[lah]

Have changed the link in logsheet.
Every previous logsheet has this issue, so the script needs changing. Not going to do this now.
Still looking into dem issue.

[dap]

LiDAR data at GB12_05-152a-lidar-20140917/ now ready for delivery.

[dap]

LiDAR data delivered on 29 October 2014 to Dr Hill at Bournemouth University.