GB09/05, flight day 278c, Leighton moss

[mark1]

Data location: ~arsf/arsf_data/2009/flight_data/uk/GB09_05-2009_278c_Leighton_moss

Data arrived from ARSF via SATA disk LETTER L on 7th October 2009.

Scientific objective: /users/rsg/arsf/arsf_data/2009/ARSF_Applications/GB09-05.pdf

Priority: alpha-4-low

PI: A. Blackburn

Sensors:

• Eagle (09/03/10)
• Hawk (09/03/10)
• Leica LIDAR (28/04/10) (see ticket #270)

[mark1]

This project has been split from GB09/05 278b (ticket #270) and contains duplicates of the applanix and rinex data but separate Eagle/Hawk and logsheets. The Leica Lidar data has remained in GB09/05 278b since its difficult to tell where it should be split or which project areas it relates to.

[mggr]

Re: #281 (Hawk frame rates are double what they should be), the following lines are affected and the .hdr file will need to be edited to halve the fps number:

uk/GB09_05-2009_278c_Leighton_moss/hawk/SWIR278c-09-1.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB09_05-2009_278c_Leighton_moss/hawk/SWIR278c-09-2.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB09_05-2009_278c_Leighton_moss/hawk/SWIR278c-09-3.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB09_05-2009_278c_Leighton_moss/hawk/SWIR278c-09-4.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB09_05-2009_278c_Leighton_moss/hawk/SWIR278c-09-5.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB09_05-2009_278c_Leighton_moss/hawk/SWIR278c-09-6.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB09_05-2009_278c_Leighton_moss/hawk/SWIR278c-09-7.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB09_05-2009_278c_Leighton_moss/hawk/SWIR278c-09-8.hdr: predicted length half recorded length, frame rate doubling problem?
uk/GB09_05-2009_278c_Leighton_moss/hawk/SWIR278c-09-9.hdr: predicted length half recorded length, frame rate doubling problem?

[chrfi]

awaiting vectors

[chrfi]

users dosen't want to wait for vectors.

sct offsets,

flightline	eagle	hawk
1	0.02	0.88
2	-0.07	0.60
3	0.00	0.60
4	0.00	0.15
5	0.00	0.52
6	0.06	0.55
7	0.00	0.47
8	0.04	0.52
9	-0.04	0.23

[mark1]

vectors arrived 02/03/2010

[mark1]

Delivery checked Hyperspectral delivery. Viewed all data and tested example commands, looks good. Few edits made to read_me file. Need to change flight line numbers - then ready to deliver.

[chrfi]

eagle and hawk data dispatched, email sent, hard drive table updated

[chrfi]

forgot to mention, dispatched 9th March

[mark1]

LIDAR delivery has been checked. Minor corrections made to read me and filenames. Needs comparison to vectors and probably best to split the DEM and screenshots into 2 separate ones rather than one big one.

[chrfi]

lidar roll offsets

154230	-0.403
154612	-0.0393
155020	-0.00390
155413	-0.00393
155802	-0.00373
160344	-0.00344
160717	-0.00333
161214	-0.00359
161543	-0.00354

[chrfi]

lidar dispatched 28/04/2010

[chrfi]

my mistake, still needs rsyncing and archiving.
waiting for space on bowhead

[knpa]

Begun archiving.

[knpa]

No webcam data for this project.

[knpa]

Hawk runscripts missing.

[knpa]

Raw hawk unusually has one nav file that covers all the lines.

[knpa]

Archived and backed up by NEODC.

Moved to archive disk.

[knpa]

Deleted workspace version.

Closing ticket.

[lah]

Tidying

There is no reprocessed hyperspectral delivery, but there are reprocessed files, so I've created a new delivery out of these and added a readme. This will need a delivery check before archiving. Oddly there are no fodis data. I have not deleted any of the hyperspectral processing files yet - will wait until after the delivery is checked.

[asm]

Archiving

Archived and it is available from CEDA. Re-processed hyperspectral data at ​​http://browse.ceda.ac.uk/browse/neodc/arsf/2009/GB09_05/GB09_05-2009_278c_Leighton_moss/hyperspectral-reprocessed

Plymouth 12th May 2017