GB08/12, flight day 152a/2009, Borth Bog

[jatt]

Data location: ~arsf/arsf_data/2009/flight_data/uk/GB08_12-2009_152a_Borth_Bog

Data arrived from ARSF via SATA disk M on 9th June 2009.

Scientific objective: see ~arsf/arsf_data/in_progress/2008/ARSF_Applications/GB_and_NL/GB08-12 Application Form and Science Case.pdf

Priority: α4H

PI: Angela Harris

Sensors:

• Eagle (20/11/10)
• Hawk (20/11/10)
• Leica LIDAR (29/01/10)
• RCD (29/01/10)

[jatt]

Both eagle and hawk raw files for flight line 2 are very small (eagle 51M and hawk 12M), suggesting little or no data for that flight line.

[jatt]

Requested vectors from Gary.

[knpa]

Timestamps do not match between LIDAR (and webcam) and Eagle/Hawk

[knpa]

According to Phil, timestamps for the folders (and therefore the lidar and jpgs filenames) are two hours FAST (i.e. a 9am flightline appears as 11am).
In addition, some of the jpegs have even further off timestamps (4 hrs in one case) but this has just been seen for test lines so far.

[knpa]

Some flightlines do not have sync info (Eagle lines 1-3 and hawk line 2 so far). Having to correct SCT by hand, will have to check against vectors when they arrive.

[knpa]

All eagle flightlines missing sync info (didn't realise they share a single .nav file).
Will adjust SCT to minimise wobbles and then correct to an acceptable accuracy with vectors on arrival.

[knpa]

A regular drop of scan lines on Hawk flightline #11 resulting in 4 across track black lines approx 7 pixels wide.

[knpa]

SCTs found for all flightlines (despite lack of sync info).
Awaiting arrival of vectors before can proceed to delivery checking.

[knpa]

Have contacted PI and they are happy to wait a couple of weeks for vectors.

[chrfi]

starting lidar processing

[mark1]

Vectors have arrived.

[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/GB08_12-2009_152a_Borth_Bog/hawk/Hawk152-09-2.hdr: predicted length half recorded length, frame rate doubling problem

[knpa]

halved fps in .hdr for H2 from 40 to 20

[benj]

Taking ticket for delivery checking

[benj]

Delivery check done, comments:

• Flightline numbers need to be corrected in the readme (currently all XXX) - should match output to input flightline
• Correct description of screenshots directory in the readme
• Readme typo - "A regular drop of scan lines on Hawk flightlines resulting in approx. 4 across track black (~7 pixels wide) per flightline." - should be "...black lines per flightline."
• DEM filename in azgcorr example command should be an exact filename, not a wildcard match (eg. borth_bog.dem)
• azgcorr example command shouldn't have a \ on the end of the last line
• Filenames for azgcorr example commands should match those delivered (ie no "b" on the end of the level 1 filename, 01 rather than 1)
• Pixel size description requires units (1m x 1m, not 1x1)
• Fax number for ARSF ops is 01452 713219 (I'll update the template)

Other issues:

• Eagle lines 1, 3, 10, 11, 12 - number of lines in the header file does not agree with the file size (off by 3-4 lines)
• Hawk lines 1-12 - number of lines in the header file does not agree with the file size (off by >40 lines). Also looks like it's included dark frames in the level 1. Band 232 is completely black in all images.

[benj]

Dark line issue in ticket #287

[knpa]

HYPERSPECTRAL DATA DELIVERED

[knpa]

Lidar data issue(s)

The two higher altitude flightlines' points are hundreds of meters in absolute value above the lower flightlines.
Tried offsetting height through ALSPP. Got one of the flightlines to the same level but higher flightline exhibits a 'banana' effect in which the centre is higher than the edges.
emca thinks problems could possibly be caused by a program version issue. There is a .sup file which is generated by newer versions of IPAS and is used by ALSPP - this is not present. Has suggested reprocessing navigation from start with new version of IPAS.

[knpa]

On investigation have discovered that the height error originates in the original .scn files i.e. the range value is wrong by around 1.5km (for the two high flightlines only). Have e-mailed Phil @ ops about the problem, awaiting reply.

[knpa]

Delivery prepared, awaiting delivery check.

[emca]

Delivery check for LIDAR data complete.
Removed the .svn directories from the bin folder. Renamed the ascii laser files (had incorrect project code & julian day). Loaded data into grass and looks good.
Ready for delivery.

[knpa]

rsynced back to repository

[knpa]

LIDAR and photography delivered today (29/01/10)

[knpa]

Ready for archiving

[knpa]

Found that LIDAR was originally processed with wrong calibration file.
Have reprocessed lines and sent out again on disk today.

[knpa]

*NOTE need to rsync this project again before archiving.

[knpa]

This project has been r-synced.

[knpa]

Started archiving.

Creating separate delivery directory for the reprocessed lidar that was sent out in June.

[knpa]

Archiving complete. Awaiting NEODC downloading.

[knpa]

Downloaded and backed-up by NEODC.

Moved to archive disk.

[knpa]

Deleted workspace copy.

Closing ticket.

[asm]

Archiving

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