Opened 15 years ago
Last modified 8 years ago
#329 closed flight processing
GB07/12, flight day 99/2010, Debden — at Version 17
Reported by: | benj | Owned by: | anch |
---|---|---|---|
Priority: | alpha 4 low | Milestone: | 2010 data processing completion |
Component: | Archiving | Keywords: | |
Cc: | Other processors: |
Description (last modified by anch)
Data location: ~arsf/arsf_data/2010/flight_data/uk/GB07_12-2010_099_Debden
Data arrived from ARSF via network transfer on 15th April 2010.
Scientific objective: Monitoring of peat fires and quantification of pyrogenic carbon conversion
Priority: a4l
PI: Martin Wooster
This is the post-burning flight relating to #323 and #324
Sensors:
- Eagle : Delivered 13/08/2010
- Hawk
- Leica LIDAR : Delivered 13/08/2010
Change History (17)
comment:1 Changed 15 years ago by benj
- Milestone set to 2010 data processing completion
comment:2 Changed 15 years ago by benj
comment:3 Changed 14 years ago by pmlvis10
IPAS navigation for this project has been processed.
comment:4 Changed 14 years ago by ella
Looks like the applanix navigation processing has been done. Saved in arsf Samba workspace.
comment:5 Changed 14 years ago by anch
- Owner set to anch
- Status changed from new to accepted
Hyperspectral processed
comment:6 Changed 14 years ago by knpa
Delivery checked.
All checks out apart from:
- 5 Readmes - delete all apart form pdf.
- Readme contents section - flightline named in right-hand side column should be name from logsheet e.g. '020'
- 'Quality issues...' Section - "Digital Elevation Modeland tested" - should be space between "Model" and "and"
- Formatting on azgcoor command incorrect, put on correct lines and make sure to escape newlines with '\'
- eagle lev1 images look strangely squashed...need to investigate this.
Have not checked hawk due to current bandsetting issue. Be sure to get this checked before delivering.
comment:7 Changed 14 years ago by benj
Timing offsets taken from config file
Line | Eagle SCT | Hawk SCT |
3 | 0.94 | 0.00 |
4 | 1.70 | 0.04 |
5 | 1.20 | 0.00 |
6 | 1.01 | 0.00 |
7 | 1.00 | 0.53 |
8 | 0.42 | |
9 | 0.01 | 1.09 |
10 | 0.01 | |
11 | 1.17 | |
12 | 0.04 |
comment:8 Changed 14 years ago by jb362
Beginning LiDAR processing
comment:9 Changed 14 years ago by jb362
Abandoned LiDAR processing!
comment:10 Changed 14 years ago by benj
Why abandoned?
comment:11 Changed 14 years ago by jb362
Abandoned because I am making the fixes on my delivery checked projects, then starting the hyperspectral processing in the unpacking folder so will leave this for the next person to do.
comment:12 Changed 14 years ago by anch
I have started the LIDAR processing for this project.
.LAS files have been created in ALSPP and I am now doing QC in lag
comment:13 Changed 14 years ago by anch
LIDAR processing of this project is complete and ready for checking.
I have added it to the delivery checking list.
comment:14 Changed 14 years ago by jb362
Starting LiDAR delivery check
comment:15 Changed 14 years ago by jb362
LiDAR delivery check looks fine.
comment:16 Changed 14 years ago by anch
Eagle hyperspectral and LiDAR data have been dispatched on disk.
The data was put on the same disk as project GB08/19, as they were both for the same PI.
Eagle and LiDAR have been rsynced.
comment:17 Changed 14 years ago by anch
- Description modified (diff)
Eagle has an extra blank line collected near Nottingham (they were going to do another collection and were put off by the weather). I have removed line 099-10-1.* from the Eagle directory (it's static, presumably running with the lens cap on because they weren't actually trying to collect data). I have also removed SWIR099-10-12.nav from the Hawk directory - it has no associated raw (or other) file.