CEH2007/06 (GB2007/12), flight day 192c/2007, Didcott

[mggr]

Data location: ~arsf/arsf_data/in_progress/2007/flight_data/uk/CEH2007_06-2007_192c_Didcott

Data arrived from ARSF via second SATA disk transfer at the start of Sept.

Scientific details:

• ~/arsf_data/in_progress/2007/ARSF_Applications-GB_2007/GB07-12_Application_and_science_case.pdf

Only a single line of data.

[mggr]

Fixed summary line..

[mggr]

PI, Andrew Wilson, only wants raw data & processed applanix.

[anee]

Combined operation unacceptably high – need to sort

[anee]

location of base station (oxfr)
51 49 26.23733
-1 17 18.74360

location of 1st site
50 50 5.97049
-1 29 48.95154

location of 2nd site
50 45 30.30952
-2 26 47.89430

[mggr]

Seems that the problem here was due to there being 3 sites visited on the one flight:

• 192a (first site, Dorchester, LIDAR only)
• 192b (second site, New Forest, LIDAR only)
• 192c (third site, Didcott)

However, Didcott is actually only a single line of data so it doesn't look like another site - it's actually the straight part past the wiggle around 13:45 (time). The base station OXFR is the correct base station for this site. If you restrict the processing time range to just the part over Didcott (~13:35 - 13:55), it processes fine :)

[anee]

Finished applanix processing using tips given above and a few small tweaks. Everything looks to be fine.

[mggr]

Synced back into main repository.

[mggr]

Sent on disk 3 to Andrew.

[mggr]

Updating code per Gary's instructions:

GB07/12 was an ambiguous code that referred to eight different jobs, many of which were commissioned by CEH. To reduce confusion these were modified (in consultation with Andrew) to a CEH07 code. I know the log sheets still holds the code GB07/12 but I suggest that for the purposes of reporting these can be entered as 'CEH07/01 (GB07/12)'  for Buckingham (240), 'CEH07/06 (GB07/12)'  for Didcot (192b).  

[mggr]

Archived at NEODC.

[dac]

Hyperspectral

Processed data for this flight has been requested. Config file had already been generated.

Eagle header was named *_orig.hdr so renamed to match raw data.

[dac]

Hyperspectral

Existing SCT values in config file were correct so processed using these. Level 3 data have some gaps in them - not sure why. Tried processing with different DEM and also get gaps. Created delivery but need to explain holes before delivery check.

[dac]

Hyperspectral

Holes in mapped data are regions masked out due to incorrect smear correction. Have added to readme. Ready for delivery check.

[asm]

Hyperspectral Delivery Check
Started

[asm]

Hyperspectral Delivery Check

-> Project tidy is complaining about all names but everything seems fine.
-> Pixels masked due to smear correction catches the eye, note on readme makes sense and it is clear.
-> Everything else looks OK.

Zipping files and should be ready to send.

[asm]

Hyperspectral Delivery Check

Mapped files have been zipped. Project ready to be delivered.

[dac]

Hyperspectral files uploaded to FTP server (arsf7) on 2016-11-09.