Opened 11 years ago
Last modified 9 years ago
#495 new flight processing
IG13/19, flight day 219/2013, Virkisjokull
Reported by: | knpa | Owned by: | |
---|---|---|---|
Priority: | alpha 4 medium | Milestone: | 2013 data processing completion |
Component: | Processing: general | Keywords: | |
Cc: | Other processors: |
Description (last modified by edfi)
Data location: /users/rsg/arsf/arsf_data/2013/flight_data/greenland_iceland/IG13_19-2013_219_Virkisjokull
Data arrived from ARSF via network transfer on 23/08/2013
IG13/19 Scientific objective: unknown
IG13/19 Priority: 8
PI: Tom Bradwell
Notes: Some lidar lines have no returns due to surface water.
Sensors:
Camera (dispatched 22/10/2013)
Eagle (dispatched 22/10/2013)
Hawk (dispatched 22/10/2013)
LiDAR (dispatched 22/10/2013)
Change History (21)
comment:1 Changed 11 years ago by tipo
comment:2 Changed 11 years ago by knpa
- Description modified (diff)
comment:3 Changed 11 years ago by edfi
Nav initially processed using PPP whilst waiting for good nav.
Hyperspectral started
RCD conversion to Tiff completed
comment:4 Changed 11 years ago by edfi
Navigation improved
Processing hyperspectral with SCTs
LiDAR started initial run.
PPP_base (KVSK)
63 58 56.07578
-16 25 57.81442
98.505
comment:5 Changed 11 years ago by edfi
Hyperspectral ready to D/C
comment:6 Changed 11 years ago by edfi
Adjusted the processed event file (new version: processed2) so that the Raw and Tif labels are correct, also removed the event information for all the images as the records had repeats which are wrong. These problem are likely to be due to instrument error.
comment:7 Changed 11 years ago by edfi
Realised LiDAR delivery is in UTM27 rather than UTM28. Will Remake delivery. Checked camera and hyperspectral both correct
comment:8 Changed 11 years ago by edfi
adjustments made to LiDAR now in correct projection
comment:9 Changed 11 years ago by stgo
Beginning hyperspectral D/C
comment:10 Changed 11 years ago by stgo
Check_apl fails due to incomplete level 1 eagle file on line 1, have checked the logfile and it seems the processing did not complete. Have run check_apl to completion and all other files are fine.
Additionally several hawk lines have a high level of underflow. 2, 4, 5, 7, 8 and 10
comment:11 Changed 11 years ago by stgo
Finished LiDAR D/C, some lines have a very high level of noise classification (especially 5, 6 and 7) is it worth applying a stricter isolated points routine?
Nav file needs to be named according to conventions and the same for vectors screenshot.
Otherwise ready to deliver.
comment:12 Changed 11 years ago by stgo
Finished RCD D/C, ready to deliver other than a few changes to readme:
- remove "The following is an overview of your photo collecion..." from image collection section, or the whole section if it make it flow better since there are no photos in the readme.
- make a note that the RCD images are not included in the KML file and that this only contains hyperspectral and LiDAR information.
comment:13 Changed 11 years ago by stgo
Rechecked LiDAR and rcd, both are ready for delivery.
comment:14 Changed 11 years ago by edfi
Hyperspectral adjustments
Reprocessed line 1, added underflow commented into read me and renamed DEM
comment:15 Changed 11 years ago by stgo
Hyperspectral D/Cd, ready for delivery. Zipping mapped files then will start dispatch.
comment:16 Changed 11 years ago by edfi
- Description modified (diff)
comment:17 Changed 11 years ago by edfi
RCD, LiDAR and Hyperspectral Deliveries dispatched
comment:18 Changed 11 years ago by tipo
Hawk 11's darkline transition isn't instant, it fades over the course of several lines. I've set the start of the darklines to a line after the transition, This leaves 2 or 3 lines of not-quite-light, not-quite-dark at the end of the processed image.
comment:19 Changed 9 years ago by dac
Archiving
Started archiving
comment:20 Changed 9 years ago by dac
Archiving
rsyncing data to NEODC
comment:21 Changed 9 years ago by dac
Archiving
Data uploaded to NEODC via rsync 25/06/2015
Started navigation processing.