BAS13/01, flight day 069/2014, Tamar

[knpa]

Data location: /users/rsg/arsf/arsf_data/2014/flight_data/uk/BAS13_01-2014_069_Tamar/

Data arrived from ARSF via network transfer on 10/03/2014

BAS13/01 Scientific objective: unknown

BAS13/01 Priority: 8

PI: France Gerard

Sensors:

Camera (16/07/14)
LiDAR (Requested)

[knpa]

France would like the flightlines divided into manageable chunks, 3 per flightline was suggested.

[benj]

Gary has confirmed that the PI would like FW LiDAR data for this flight (if we have any).

[knpa]

Resuming RCD processing from emca

[knpa]

Removed the following images because of overexposure (clouds):
10115615100220G3.tif 10115615100221G3.tif 10115615100222G3.tif 10115615100225G3.tif 10115615100228G3.tif 10115615100308G3.tif 10115615100309G3.tif 10115615100311G3.tif 10115615100312G3.tif 10115615100312G3.tif 10115615100314G3.tif 10115615100385G3.tif 10115615100388G3.tif 10115615100389G3.tif 10115615100390G3.tif 10115615100391G3.tif 10115615100392G3.tif 10115615100393G3.tif 10115615100224G3.tif 10115615100310G3.tif

[knpa]

There were a few photos that were put in the outbounds dir, but I moved them back up because they look like they are just on the ends of the flightlines.

[knpa]

Finished RCD processing.

Delivery ready at:
/users/rsg/arsf/arsf_data/2014/flight_data/uk/BAS13_01-2014_069_Tamar/processing/delivery

[knpa]

Beginning LiDAR processing.

[tipo]

Image 001 is slightly overexposed. There are also several images that are mostly obscured by cloud that should be mentioned in the quality section of the readme.

[knpa]

Updated ReadMe. Ready to deliver.

[knpa]

Delivered RCD to France Gerard at CEH Wallingford on 16/07/14

[knpa]

Reprocessing LiDAR with the non-FLA torsion and PES version of the calibration as this has produced less pitch and roll errors for other flights.

[mark1]

Edited KML file in-place in RCD delivery to correct data paths for rcd thumbnails.

[dap]

Taken over LiDAR processing from knpa

[dap]

LiDAR Processing

Found roll error of -0.003864392 radians to be correct for lines 133512 and 134850. Now processing the other lines with this roll error.

[dap]

LiDAR Processing
After having tried several roll errors on other lines, found that there is no particular roll error applicable to all lines.

Have now produced LAS files with different roll errors using alsproc and investigating files produced.

[dap]

LiDAR Processing

Roll error values found so far:

Flightline	Roll error (radians)
133512	-0.003864392
134850	-0.003864392
140154	-0.003864392
141432	-0.003964392
142744	-0.003814392
144050	-0.004094392
145428	-0.003964392
150641	-0.003964392

[dap]

LiDAR Processing

Roll errors have now been found for all flight lines (using alsproc, files with corrected roll error values found in las/alsproc). Will now process using alspp and output to las/corrected_alspp/unsplit.

[dap]

LiDAR Processing

All flight lines have been processed using alspp using above roll errors.

Now splitting flight lines in to manageable segments, in to las/corrected_alspp/split.

[dap]

LiDAR Processing

Classifying LAS files in to las-classified using classify_las_files.sh, classification algorithm isolated 4 5.

[dap]

LiDAR Processing

Created delivery and tried to open las1.2/* for measuring elevation differences but found that the files did not open in lag. las files in processing directories do, however, open. Will reclassify files and copy files to delivery directory and see if problem persists.

[dap]

LiDAR Processing

Reclassified LAS files and copied to delivery directory. Files now open in lag so will proceed by sorting them by time.

[dap]

LiDAR Processing

Delivery and read me created, delivery at BAS13_01-069-lidar-20140926 now ready for quality check.

[tec]

Lidar Delivery Check
Issues I have found:

• DEM covers the whole of south west, should be smaller.
• LiDAR ASCII files do not have CRLF line terminators.
• Have reclassified the following lines, you'll need to recreate the corresponding ASCII files.
  • 2
  • 8
  • 22 (major cloud!)
  • 24
  • 27
• Don't like screenshot 27.
• DEM Screenshot will need redoing.

[dap]

LiDAR Processing

• Have generated a smaller DEM covering a smaller area.
• unix2dos'd the ascii LiDAR files after regenerating them with reclassified points
• Left screenshot 27 as is
• Regenerated DEM screenshot

LiDAR delivery at BAS13_01-069-lidar-20140926/ now ready for second quality check

[tec]

LiDAR DC
Looks fine

[dap]

Beginning archive for flight

[dap]

LiDAR data has been submitted to NEODC, 10/10/2014