Opened 11 years ago

Last modified 8 years ago

#366 reopened flight processing

EU10/03, flight day 238a/2010, Lake Balaton East Area — at Version 18

Reported by: iopa Owned by:
Priority: alpha 5 Milestone:
Component: Processing: general Keywords:
Cc: Other processors:

Description (last modified by benj)

Data location: ~arsf/workspace/EU10_03-2010_238a_Lake_Balaton_East_Area

Data arrived from ARSF via SATA disk Q on 15/09/2010.

Scientific objective: Lake Balaton provides an ideal area for testing emerging algorithms on retrieval of in-water constituents and on mapping bloom-forming cyanobacteria using in-situ radiometric, airborne and satellite data.

Priority: a5

PI: Andrew Tyler

Note: Data is currently symlinked from ~arsf/arsf_data/2010/flight_data/archive_overflow and when this is resolved the symlinks will need to be re-directed.

Sensors:

  • Eagle (20/10/2010)
  • Hawk (Requested by PI)
  • Leica LiDAR (Requested but low priority)
  • Digital Photography (20/10/2010)

Change History (18)

comment:1 Changed 11 years ago by iopa

  • Description modified (diff)

comment:2 Changed 11 years ago by iopa

Please note that data files 10 for both eagle and hawk are not on the logsheet, the 12 logged flightlines required to be processed are data files 1-9 and 11-12 inclusive.

comment:3 Changed 11 years ago by iopa

  • Resolution set to invalid
  • Status changed from new to closed

comment:4 Changed 11 years ago by iopa

Project has been removed from the workspace and taken back to the unpacking stage since it is potentially missing applanix, rcd, tabi data and is actually missing IPAS and LiDAR. The data is being currently downloaded from thelma.

comment:5 Changed 11 years ago by iopa

  • Description modified (diff)

The IPAS and LiDAR data for this project have been downloaded from thelma, including WebCamImages and all the accompanying log files. This project has been re-fastcopied into the workspace and re-entered on the processing order page.

comment:6 Changed 11 years ago by iopa

  • Resolution invalid deleted
  • Status changed from closed to reopened

comment:7 Changed 11 years ago by iopa

  • Description modified (diff)

comment:8 Changed 11 years ago by anch

Applanix and Ipas processing for this project have been completed and copied to workspace.

I'll now begin the eagle processing.

comment:9 Changed 11 years ago by anch

HDR file for flight line 5 was incorrect.

It has 1837 lines , however after looking at the RAW file size, the number of lines turned out to be 7602.

This has been updated, and the flightline has now been successfully processed.

comment:10 Changed 11 years ago by emca

Delivery checked Camera
~airborne/workspace/EU10_03-2010_238a_Lake_Balaton_East_Area/delivery/20101013/EU10_03

The following need to be ammended in the Readme:
KML file needs to be added to delivery contents in the Readme.
Remove comma from flight numbers
Sample exiftool output - lines overrun page.. need to be split

In the KML file remove line 10 as this is not a genuine flightline

comment:11 Changed 11 years ago by emca

Delivery checked Eagle
~airborne/workspace/EU10_03-2010_238a_Lake_Balaton_East_Area/delivery/20101014/EU10_03

All processed files need to have flight letter added (238a - lev1 files & jpgs)
Add DEM to delivery
Change permissions of *.bil files so they are readable to all (as this will cause problems when copying to disk)
Misc directory is empty - add appropriate separation file here

Readme:
Add flight letter (238a) to each filename
Add DEM to delivery contents

comment:12 Changed 11 years ago by benj

Ioannis, on what date did you start the LiDAR processing?

comment:13 Changed 11 years ago by benj

Bah... sorry, ignore that, looking at the wrong column in the spreadsheet.

comment:14 Changed 11 years ago by emca

Eagle and Camera sent to A Tyler 20/10/2010

comment:15 Changed 11 years ago by anch

SCT Offsets for Eagle:

EAGLE
-1 : 0.03
-2 : 0.01
-3 : 0.02
-4 : 0.00
-5 : 0.00
-6 : 0.01
-7 : 0.02
-8 : 0.00
-9 : 0.00
-11 : 0.00
-12 : 0.02
-13 : 0.00

comment:16 Changed 11 years ago by knpa

Appears to be an issue with the bandset labels in the header files; they start at 900nm which is lower than it should be. Possibly incorrect bandset selected or none specified. Will leave this until end of the year and new Hawk calibration.

comment:17 Changed 11 years ago by emca

  • Description modified (diff)

comment:18 Changed 11 years ago by benj

  • Description modified (diff)
Note: See TracTickets for help on using tickets.