GB09/07, flight day 132/2009, West coast

[mggr]

Data location: ~arsf/arsf_data/2009/flight_data/uk/GB09_07-2009_132_West_coast

Data arrived from ARSF via SATA disk on 19/May/2009.

Scientific details: plant distribution on dune fields.

Priority: α4L

PI: Andreas Baas

Sensors:

• Eagle (07/12/09)
• Hawk (07/12/09)
• Leica LIDAR (28/10/2009)
• Digital Photography (15/01/2010)

[mggr]

Logsheet missing, runscripts not generated. Requested vectors and logsheet from Gary.

[mggr]

Corrected grading following fixing trac's priority list..

[mggr]

Note hawk files may need renaming, not in SWIR* form.

[mggr]

Other points of note from the application:

• potentially interested in atmospheric correction / level 2 products (adding peland & sbg to cc)
• no nextmap access, no digimap (Gary will check?)

[mggr]

Logsheet received, but as a scan in a PDF file. Someone will have to create the run scripts manually.

[mggr]

Email from PI:

Thanks for the update on the data processing status. I would just like to confirm that we would certainly be interested in atmospheric correction / level 2 products. Also, I have given Gary the OS / Nextmap / Digimap (whatever it's called these days) subscription number of our university, so that should hopefully not be any issue anymore.

Will ask peland to follow up on the atmospheric/level 2 question.

[jatt]

Project directory copied to ~arsf/workspace.

Applanix has been processed and copied to this location.

All run scripts have been created.

More than one site - project will need to be split into separate project directories.

[knpa]

hawk raw files renamed as per SWIRsh convention

[knpa]

runscripts edited to SWIRsh convention

[knpa]

Directory structure divided into 7 trees according to logsheet groupings: 132a through 132g.

[knpa]

Incorrect GPS end time on H1 header file (given as 00:00:00). Corrected and updated header file.

[knpa]

No sync info for h6.

[knpa]

SCT offsets have been found for 45/52 flightlines. The remaining 7 do not have sufficient wobbles or overlapping fls with wobbles. Will need to wait for vectors (or lidar) before these can be corrected.

[mggr]

Contacted by PI requesting an update and an estimate of time to delivery. Explained the SCT offset issue and the overall LIDAR processing issues. Offered a potential predelivery of the 45 corrected lines with the proviso of no OS error estimate.

[knpa]

Have put the majority of the flightlines (excluding lines 5-8) (not yet verified by vectors) lev1 and 3 on pml ftp1 as well as data quality report, readme and screenshot of sites overview.

[benj]

Have agreed to process this as higher priority because funding for the PhD student intended to look at this (Lily Zhang) runs out soon(ish).

[emca]

Starting LIDAR processing

[mark1]

Vectors have arrived.

[emca]

LIDAR processing has been finished. Vector data has been received for two sites only (f & g). Emailed PI to offer delivery without checking against vectors.

Delivery directory has been created at
~airborne/workspace/GB09_07-2009_132_West_coast/delivery

Passing ticket to Mark1 for delivery checking.

[mark1]

Checked ascii files load ok in Grass and look good. Made a few minor edits to read_me. Ready to deliver.

[mark1]

LIDAR data delivered on 28th October 2009

[mark1]

Processed LIDAR data needs to be rsynced back to main arsf repository, probably best to split the project on the main arsf repository to match the processed project directory structure?

[mark1]

Have processed the raw RCD camera images and tagged the tiff files.

[knpa]

Delivery preparation complete, ready for checking

[benj]

Have delivery checked flight a. Issues so far:

• Replace data quality report with most up-to-date version
• Band 232 blank in all hawk files (need to look into this but can deliver this dataset anyway - suspect it's a bandset issue, but band 232 is poor quality anyway, plus should be very similar to band 231)
• Should mention band 232 issue and Hawk dropping frames (frame grabber card issue) under "Quality of data" in the readme.

[benj]

Also, level 1 files for delivery should include the flight letter (eg. e132a01.bil, not just e13201.bil)

[benj]

Actually, don't worry about that for this delivery. Generally it's true, but all the line numbers are different for the various bits of this project so there's not a lot of point in spending the time to do it.

[benj]

Checking the azgcorr command for flight g hawk line 22 gives the following error in azgcorr:

A UK National Grid projection has been chosen for data that is
 outside the coverage of that projection:  48 N to 62 N and 10 W to 4 E
 The approximate centre of this data set is:  1934672355233165591537245121105912802295402703577532870545838032454086581895847108349688088720759117458960729463204240031593719663501917896233906591097033570989736332795780424822577168766990391955691527327118824677766524783913284925690272373793852668180679655723892736.00 S  2090841113072791560219652599314024076327586797782366537025425377203007704621009079605789662969587471652344465029184481219704709311303332865575410371840520542199889353972652820448798628886650676506023337676581152228735021609379087974166344382137771452130393675695114079533135878132719919721720908435540672512.00 W

The location is, obviously, rubbish, so something somewhere's gone funny with the file. Running hawk line 23 is fine.

[benj]

Made a few minor readme changes, everything else looks fine. Once the comments above about flight a are fixed and hawk line 22 is investigated this can be rsynced back and delivered.

[knpa]

SCTs

	e	h
1	0.07	0.09
2	0.04	0.02
3	0.08	0.08
4	0.07	0.04

5	-0.02	0.04
6	-0.01	0.7
7	0.07	0.07
8	0.02	0.05

9	0.02	0.00
10	0.02	0.07
11	0.03	0.01
12	0.06	0.07
13	-0.01	0.07

14	-0.01	0.06
15	0.07	0.06

16	0.06	0.08
17	0.04	0.06
18	0.06	0.03

19	0.09	0.09
20	0.08	0.05
21	0.07	0.06

22	0.05	0.07
23	0.02	0.09
24	0.07	0.03
25	0.09	0.06
26	0.08	0.04

[knpa]

Hyperspectral delivered 7th December 09.

[mark1]

Photography has been split up into the 7 sites. Image event file has been edited for images which failed to record a time (using time differences from sensorstat log). Images affected are:
12200323100117G3.raw
12200323100153G3.raw
12200323100154G3.raw
12200323100155G3.raw
12200323100156G3.raw
12200323100157G3.raw
12200323100194G3.raw
12200323100195G3.raw
12200323100196G3.raw
12200323100197G3.raw
12200323100198G3.raw
12200323100239G3.raw

[mark1]

Digital Photography has been dispatched to PI on 15th January 2010

[knpa]

Everything delivered - Ready for archiving.

[knpa]

This project seems to be a bit messed up in the repository, taking archiving status off until this is sorted.

[knpa]

Project now sorted out in repository (matches the workspace lay-out of one dir for each site. Raw data is in in site A).
R-synced with workspace.
Ready to begin archiving.

[knpa]

Beginning Archiving.
Everything appears to be r-synced and delivered.

Need to include note when we send to NEODC that the layout of delivery folders varies according to how it was delivered. It seems HS and photography were delivered divided up into separate project folders for the 7 different sites (a-g) but lidar was delivered all in one folder.

[knpa]

Doesn't appear to be any webcam data for this project

[knpa]

Have finished preparing for archiving.
Have requested DTG archive the project (28/04/10).

[knpa]

28 extra raw image files (1-28) in site A.

[knpa]

*above is referring to RCD

[knpa]

can't find ipas processing information for this project, i.e. gps and extract folders are empty.

[knpa]

Have split lidar delivery into seven site structure of this project, this makes it easier to be ingested by NEODC but note lidar is no longer in the same state that it was delivered.

[knpa]

Made available in NEODC transfer area.

[knpa]

NEODC have confirmed that they have received, backed-up and checked this project.

[knpa]

Project has been moved to non-backed up space and workspace version deleted.
Closing ticket.

[lah]

Archiving

Tidied d, e and f, and ready for upload to NEODC.

[asm]

Archiving

Will start archiving of re-processed hyperspectral data.

[asm]

Archiving

Re-processed hyperspectral data has been archived and everythin is ready to be downloaded from CEDA. Will close this ticket.

[asm]

Archiving

Reprocessed hyperspectral has been archived and it is available from CEDA at ​http://browse.ceda.ac.uk/browse/neodc/arsf/2009/GB09_07/GB09_07-2009_132a_West_coast/hyperspectral-reprocessed

Plymouth 11th May 2017