Opened 13 years ago
Last modified 13 years ago
#425 assigned flight processing
GB11/05, flight day 285/2011, London
Reported by: | knpa | Owned by: | knpa |
---|---|---|---|
Priority: | whenever | Milestone: | 2011 data processing completion |
Component: | Archiving | Keywords: | |
Cc: | Other processors: |
Description (last modified by adbe)
Data location:
/users/rsg/arsf/arsf_data/2011/flight_data/uk/GB11_05-2011_285_London
Data arrived from ARSF via network transfer on 18/11/2011
GB11/05 Scientific objective: Atmospheric study over London.
GB11/05 Priority: not_required
PI: Benjamin Barratt
Sensors:
Camera (23/02/2012)
Eagle (23/02/2012)
Hawk (23/02/2012)
LiDAR (23/02/2012)
Change History (16)
comment:1 Changed 13 years ago by adbe
- Description modified (diff)
comment:2 Changed 13 years ago by adbe
comment:3 Changed 13 years ago by adbe
Started processing LiDAR. 2 flight lines: 1 small, 1 very large
comment:4 Changed 13 years ago by adbe
Finished RCD processing ready for delivery check.
comment:5 Changed 13 years ago by adbe
LiDAR ready for delivery check
comment:6 Changed 13 years ago by adbe
Hyperspectral ready for delivery check
comment:7 Changed 13 years ago by emca
Delivery checked camera data.
KML file shows five eagle/hawk lines - is this correct? The images/line no's shown in the logsheet don't match with the KML file either, or the images numbers shown on the logsheet... it's all a bit confusing.
comment:8 Changed 13 years ago by adbe
Camera: There are 4 hawk lines, and 5 eagle line, this is made more clear in the hyperspectral ReadME. I have the camera images matching the correct lines. I have now changed the logsheet for the hyperspectral, so that it matched the data. The LiDAR logsheet matches the LiDAR data, there are 3 lines.
comment:9 Changed 13 years ago by adbe
Updated full waveform LiDAR files so that there is not a gap between them.
comment:10 Changed 13 years ago by emca
Checked all three deliveries.
Camera - No problems, ready to deliver
Hyperspectral - Should include the OS *.gsb file with the delivery as it is needed to process the data. Readme - pg 4 should be 'Hawk Line for Eagle line UL001'. Bottom right corner of DEM looks a bit strange, like there is an area of no data - check this is correct.
LiDAR - Same issue with DEM as above, otherwise ready to deliver
comment:11 Changed 13 years ago by adbe
Hyperspectral: Do no need to include .gsb file in delivery. Update ReadMe to say about Hawk line 1 missing. DEM does goes over the sea in the bottom right area, that has made it look strange.
LiDAR: DEM does goes over the sea in the bottom right area, that has made it look strange.
comment:12 Changed 13 years ago by adbe
Hyperspectral sct's
line | eagle | hawk |
1 | 0.00 | MISSING |
2 | -0.04 | -0.02 |
3 | 0.59 | 1.01 |
4 | 0.03 | -0.07 |
5 | -0.04 | -0.09 |
comment:13 Changed 13 years ago by adbe
- Description modified (diff)
Camera, Hyperspectral and LiDAR sent to Benjamin Barratt on disk 76 on 23/02/2012
comment:14 Changed 13 years ago by knpa
- Component changed from Processing: general to Archiving
- Milestone set to 2011 data processing completion
- Owner changed from mark1 to knpa
- Status changed from new to assigned
comment:15 Changed 13 years ago by knpa
Beginning archiving.
comment:16 Changed 13 years ago by knpa
no intensity vectors screenshot
Processed navigation