Opened 11 years ago
Last modified 10 years ago
#512 new flight processing
BAS13/01, flight day 063/2014, Tamar
Reported by: | knpa | Owned by: | |
---|---|---|---|
Priority: | alpha 4 medium | Milestone: | |
Component: | Processing: general | Keywords: | |
Cc: | Other processors: |
Description (last modified by benj)
Data location: /users/rsg/arsf/arsf_data/2014/flight_data/uk/BAS13_01-2014_063_Tamar
Data arrived from ARSF via network transfer on 10/03/2014
BAS13/01 Scientific objective: unknown
BAS13/01 Priority: ?
PI: France Gerard
Sensors:
LiDAR (Requested)
FW LiDAR (Requested)
Change History (21)
comment:1 Changed 11 years ago by knpa
comment:2 Changed 11 years ago by emca
Processed the navigation data
PPP processing result for basestation APPL
Lat: 51 03 24.94187
Long: 04 11 58.74243
Elev: 68.773
comment:3 Changed 10 years ago by benj
- Description modified (diff)
Gary has confirmed that the PI would like FW LiDAR data for this flight
comment:4 Changed 10 years ago by stgo
Continuing from emca, roll error present in LiDAR.
comment:5 Changed 10 years ago by stgo
Pitch and roll values found for lines 2315 and 2329:
pitch | 0.00110716 |
roll | -0.004054414 |
Testing against other lines.
comment:6 Changed 10 years ago by stgo
Lines 010635 and 005208 are both affected by a fault in the scan mirror resulting in a FOV of 0.1. Because of this they are made up of a single line of points at the nadir of the flightline, the lines will not be included in the delivery and are not salvageable.
comment:7 Changed 10 years ago by stgo
Full wave form data present, processing lines split into 3 parts. Not including above lines.
comment:8 Changed 10 years ago by stgo
Processed waveform data, checking point classification and starting delivery creation.
comment:9 Changed 10 years ago by stgo
Closer inspection of some of the earlier las files shows the LiDAR scan mirror had issues throughout. This doesn't effect the majority of the lines though, data is definitely still usable.
comment:10 Changed 10 years ago by stgo
Classification complete, copying to waveform and creating delivery.
comment:11 Changed 10 years ago by stgo
I've found variable roll errors in a couple of lines, will correct.
comment:12 Changed 10 years ago by stgo
Roll for line 234316 is -0.003900413
comment:13 Changed 10 years ago by stgo
roll for other lines:
235709 | -0.004250413 |
001051 | -0.003700413 |
002522 | -0.004410413 |
003842 | -0.003450413 |
Will set about classifying points, wave form will take 4 hours per line, and each line has to be processed 3 times for splitting. (96 hours total, assuming nothing goes wrong)
comment:14 Changed 10 years ago by stgo
Line 0038 will not process the waveform data when attempting to split with min and max y values of 69170 and 83700. Otherwise all lines are ready for classification.
comment:15 Changed 10 years ago by stgo
Lidar data is ready for delivery check.
comment:16 Changed 10 years ago by dap
Beginning LiDAR delivery check.
comment:17 Changed 10 years ago by dap
LiDAR delivery check complete. The following issues were found and have been corrected:
- Typo in data quality remarks - "effected" should be "affected"
Please address the following problems before delivery:
- Typo in the logsheet ('mirror').
- RCD acquisition was made, but typed up logsheet does not reflect this
- Three broken links in the readme document:
- Japan's Data Ground System
- ASTER GDEM Validation Summary Report (pdf)
- https://lpdaac.usgs.gov/lpdaac/products/aster policies
- In the 'Per flight line statistics' section of the read me, each flight line has the same number - should these be named 56a, 56b, 56c etc.?
- Full waveform LAS files need to be named such that there is a '-' between the numbers at the end. (e.g. LDR-FW-BAS13_01-2014-063-21.LAS).
comment:18 Changed 10 years ago by stgo
Applied above Lidar corrections, ready for recheck.
comment:19 Changed 10 years ago by dap
LiDAR Delivery Recheck
Just a few issues:
- Two logsheets found in logsheet directory, one of which has the typo corrected - removed old one and renamed new one to follow the naming convention.
- Intensity tif screenshot left in screenshots directory - I've removed it.
- Data quality remarks typo "effected" has reappeared - fixed.
- Weird 'u' has appeared in the flight line overlap measurement table in the Read me - fixed.
- full-waveform.pdf in doc/ was incorrectly named - I've renamed it.
- Old delivery remains in processing/delivery directory - please remove this.
Delivery check complete, ready for delivery.
comment:20 Changed 10 years ago by dap
Beginning flight archive
comment:21 Changed 10 years ago by dap
Data has been submitted to NEODC, 25/09/2014
France would like the flightlines divided into manageable chunks, 3 per flightline was suggested.