Opened 11 years ago
Last modified 8 years ago
#518 closed flight processing
GB12/05, flight day 075/2014, Monks Wood — at Version 25
Reported by: | knpa | Owned by: | |
---|---|---|---|
Priority: | alpha 4 medium | Milestone: | 2014 data processing completion |
Component: | Processing: general | Keywords: | |
Cc: | Other processors: |
Description (last modified by dap)
Data location: /users/rsg/arsf/arsf_data/2014/flight_data/uk/GB12_05-2014_075_Monks_Wood/
Data arrived from ARSF via network transfer on 17/03/2014
GB12/05 Scientific objective: unknown
GB12/05 Priority: 8
PI: Ross Hill
Sensors:
Camera (Requested)
LiDAR (Requested), delivered 25/09/2014
FW LiDAR (Requested but lower priority), delivered 25/09/2014
Fenix (Requested)
Change History (25)
comment:1 Changed 11 years ago by knpa
- Description modified (diff)
comment:2 Changed 11 years ago by knpa
comment:3 Changed 11 years ago by tipo
Started navigation processing.
comment:4 Changed 11 years ago by tipo
Finished navigation processing, started RCD processing.
comment:5 Changed 11 years ago by tipo
Started LiDAR processing.
comment:6 Changed 11 years ago by tipo
Created hyperspectral delivery.
comment:7 Changed 11 years ago by tipo
LiDAR has lines flown at different heights which need slightly different pitch and roll values.
High lines: p=0.00118716 r=-0.003968414
comment:8 Changed 10 years ago by stgo
RCD D/c in progress
comment:9 Changed 10 years ago by stgo
RCD d/c complete, no problems found. Will include in delivery this afternoon.
comment:10 Changed 10 years ago by stgo
RCD data dispatched on 04/06/2014
comment:11 Changed 10 years ago by tipo
LiDAR is taking a long time, as I'm having to find the roll error seperately for each line.
comment:12 Changed 10 years ago by tipo
Higher altitude lines:
line | pitch | roll |
150700 | 0.00113716 | -0.00426684 |
151651 | 0.00113716 | -0.00376841 |
152408 | 0.00113716 | -0.00416841 |
153326 | 0.00113716 | -0.00376841 |
153957 | 0.00108716 | -0.00399841 |
154845 | 0.00108716 | -0.00374841 |
155537 | 0.00108716 | -0.00428414 |
160352 | 0.00108716 | -0.00374841 |
161021 | 0.00118716 | -0.00404841 |
165550 | 0.00118716 | -0.00404841 |
164909 | 0.00118716 | -0.00404841 |
164120 | 0.00118716 | -0.00404841 |
0.00108716 | -0.003968414 |
comment:13 Changed 10 years ago by tipo
Lines 151651 and 154845 have areas where they narrow or taper off. The log shows that it was close to the maximum range gate, so its possible it moved slightly out of range, causing the gaps in the data.
comment:14 Changed 10 years ago by tec
Beginning hyperspectral processing
comment:15 Changed 10 years ago by tec
Hyperspectial processing has stoped due to lack of suitable darkframes. Speaking to ops to get data with an integration time of 20.000
Fenix data has integration times of
Int 1 | Int2 |
---|---|
20.0000 | 10.0000 |
29.3000 | 2.2000 |
25.0000 | 12.0000 |
30.0000 | 18.0000 |
comment:16 Changed 10 years ago by stgo
Low altitude full waveform created.
comment:17 Changed 10 years ago by stgo
High altitude waveform has been created. Lidar ready for delivery check.
comment:18 Changed 10 years ago by dap
Beginning LiDAR delivery check.
comment:19 Changed 10 years ago by dap
LiDAR Delivery Check
Complete. Issues found as follows:
- Contents page of readme does not have full waveform files listed.
- Link in "Data Details" section is a LAS 1.0 link, but LAS 1.2 data was processed.
- "Per flight line statistics" section is on next page from heading. I'd suggest you put the heading on the next page.
- HAWK data was collected, but typed up logsheet does not reflect this.
- Navigation directory is empty - should contain the .sol, .sup and .trj files.
- Flightline screenshots have ".txt.jpg" file extension - should be just .jpg.
- No vector screenshots - PI has not replied to knpa's email regarding this.
- Multiple LiDAR deliveries found in delivery directory - please delete one.
- Line 18 is oddly shaped - please comment on this in the data quality remarks.
- ASCII files should have had DOS line terminators - I've fixed this.
comment:20 Changed 10 years ago by stgo
I've recreated the readme for the lidar delivery following the comments above.
The logsheet is at fault here, we can't have collected hawk data as the hawk instrument has not been installed in the plane. I think Ops meant the SWIR part of Fenix.
comment:21 Changed 10 years ago by dap
LiDAR Delivery Check
Rechecking delivery.
comment:22 Changed 10 years ago by dap
LiDAR Delivery Check
Completed. Issues found were:
- Two LiDAR delivery directories - please remove irrelevant one
- .sup file is missing from navigation directory
- Screenshots named incorrectly - the LDR need not precede the project code in the file names.
- .sol file is named incorrectly - the Julian day should be preceded by a '_' character, not '-'.
comment:23 Changed 10 years ago by dap
LiDAR Delivery Check
Complete. proj_tidy complained at screenshot of each flightline - script should be updated to not do this.
LiDAR data ready for delivery.
comment:24 Changed 10 years ago by dap
LiDAR data delivered to Dr Ross Hill, 25/09/2014.
comment:25 Changed 10 years ago by dap
- Description modified (diff)
There is a problem with the Fenix data, the .nav and .f98 files are blank.
From Tom:
Okay there was a problem with the Fenix PPS cable (bad solder joint) hence the reason that the .f98 and .nav files are empty. You will have to talk to Gary as we have been informed that there are enough ground control points on the Monks Wood site for the data to be corrected. Also the navigation data was collected and is there for the Fenix, it just wasn't included in the sensor generated files.