Opened 11 years ago
Last modified 10 years ago
#517 new flight processing
BAS13/01, flight day 070/2014, Tamar
Reported by: | knpa | Owned by: | |
---|---|---|---|
Priority: | alpha 4 medium | Milestone: | 2014 data processing completion |
Component: | Processing: general | Keywords: | |
Cc: | stgo | Other processors: |
Description
Data location: /users/rsg/arsf/arsf_data/2014/flight_data/uk/BAS13_01-2014_070_Tamar/
Data arrived from ARSF via network transfer on 11/03/2014
BAS13/01 Scientific objective: unknown
BAS13/01 Priority: a4m
PI: France Gerard
Sensors:
Camera (Requested)
LiDAR (Requested)
Change History (22)
comment:1 Changed 11 years ago by knpa
comment:2 Changed 11 years ago by benj
Gary has confirmed that the PI would like FW LiDAR data for this flight (if we have any).
comment:3 Changed 11 years ago by stgo
Tipo has completed nav processing already, have begun LiDAR processing.
comment:4 Changed 11 years ago by tipo
Created hyperspectral delivery.
comment:5 Changed 11 years ago by stgo
LiDAR pitch and roll values for lines 1221 and 1209:
pitch | 0.00110916 |
roll | -0.003909414 |
Testing against other lines.
comment:6 Changed 11 years ago by stgo
Beginning RCD D/C
comment:7 Changed 11 years ago by stgo
Strange mark to top right corner of all images, scratch on lens? Will investigate other days to check for presence.
comment:8 Changed 11 years ago by stgo
D/C complete:
- in data details, partialy needs to be spelled partially. Also need notes on how clouds effect data. (Effects on contrast etc)
- Strange white tint round edges (possibly cloud though) present from image 76 onwards
- some images, particularly 46 and 114 have high levels of cloud cover, is it worth delivering these?
- mention artefact in top right, have we got a better explanation about this?
comment:9 Changed 11 years ago by tipo
Corrected readme.
White tint is just due to the direction of the sun.
46, 114 etc do have a lot of cloud cover, but they also have quite a bit of the ground showing, so they may still be useful.
comment:10 Changed 11 years ago by stgo
RCD d/c in progress.
comment:11 Changed 11 years ago by stgo
Changes are fine, prepping for delivery.
comment:12 Changed 11 years ago by stgo
RCD data dispatched on 04/06/2014
comment:13 Changed 10 years ago by stgo
LiDAR roll values:
105232 | -0.003650414 |
110145 | -0.003450414 |
110457 | -0.004080414 |
111817 | -0.003850414 |
113038 | -0.003900414 |
114318 | -0.003709414 |
115604 | -0.004100414 |
120905 | -0.003909414 |
122134 | -0.003909414 |
124730 | -0.003650414 |
130040 | -0.003895214 |
131333 | -0.003909414 |
132746 | -0.004100414 |
134117 | -0.003690414 |
135412 | -0.004265414 |
comment:14 Changed 10 years ago by stgo
LiDAR delivery created. Awaiting D/C
comment:15 Changed 10 years ago by mark1
Delivery check comments:
- Lidar are las 1.2 but in directory named 1.0, and in readme contents it says they are 1.0 (and later in data details). Also need to update hyperlink in read me to 1.2 format descriptors.
- PI name spelt incorrectly on logsheet
- please don't split line 01 or 03, they are only small anyway
- recreate the DEM (and screenshots) without so much ASTER patching
- only checked one line (02_parta vs 04_partc) but looks like some roll/pitch residual errors > 50cm - these need fixing if possible
comment:16 Changed 10 years ago by stgo
Corrected values for line 2 (105232):
pitch: 0.00070916
roll: -0.003595214
Variable pitch was the cause of the error, will continue with lines 3 and 1.
comment:17 Changed 10 years ago by stgo
Line 3 corrected values:
Pitch:0.000909160
Roll:-0.003445214
comment:18 Changed 10 years ago by stgo
Fixed delivery according to above comments. Now reflects 1.2 status. 1 and 3 are no longer split.
comment:19 Changed 10 years ago by mark1
- Cc stgo added
delivery check (lidar):
- ascii filenames need renaming (remove *part_a* etc).
- projected dem needs renaming to include projection (-bng)
- do we need to send the sup file? Probably just confusing - I'd remove it from delivery.
- logsheet still has name spelt wrong
Other than the above the data looks fine - fix above and should be ready to deliver.
comment:20 Changed 10 years ago by stgo
Made changes requested. Setting to ready to deliver.
comment:21 Changed 10 years ago by stgo
Camera and lidar deliveries sent to NEODC for archiving 30/07/2014
comment:22 Changed 10 years ago by mark1
Edited KML file in-place in RCD delivery to correct data paths for rcd thumbnails.
France would like the flightlines divided into manageable chunks, 3 per flightline was suggested.