Opened 11 years ago

Last modified 11 years ago

#505 new flight processing

THL13/01, flight day 267c/2013, Thales — at Version 8

Reported by: edfi Owned by: benj
Priority: immediate Milestone:
Component: Archiving Keywords:
Cc: Other processors:

Description (last modified by tipo)

Ticket content

Data location: /users/rsg/arsf/arsf_data/2013/flight_data/uk/THL13_01-2013_267c_Thales

Data arrived from ARSF via SATA disk LETTER OR network transfer on

THL13/01 Scientific objective: Commercial flight to test Thales instrument

THL13/01 Priority: priority_not_known

PI: ARSF Internal

Sensors:

Eagle (Dispatched 30/10/2013)
Hawk (Dispatched 30/10/2013)

Change History (8)

comment:1 Changed 11 years ago by edfi

This flight "C" is taken from splitting up the original Thales flight. The data was split up according the flight lines. So far this has been done to the hyperspectral files and the RCD. The RCD raw files were kept/deleted according to the frame number from the log sheets. Further more the event files were edited to reflect the images which were kept. Files which were not immediately obvious were to trim were kept in tact. Where files have been edited an original copy should be also located within the folder.

comment:2 Changed 11 years ago by tipo

All LiDAR lines have zero returns.

comment:3 Changed 11 years ago by tipo

Created hyperspectral delivery.

comment:4 Changed 11 years ago by stgo

Check_apl fails on nav files. Searching for e218071b_nav_post_processed.bil not e267c071b_nav_post_processed.bil - have fixed this.

Also there are whole bands that are blank in the eagle bil files, 221 through to 59.

comment:5 Changed 11 years ago by tipo

Added comment about blank bands to the readme.

comment:6 Changed 11 years ago by stgo

Rechecked hyperspectral, ready to deliver.

comment:7 Changed 11 years ago by tipo

Hyperspectral dispatched 30/10/2013

comment:8 Changed 11 years ago by tipo

  • Component changed from Processing: general to Archiving
  • Description modified (diff)
  • Owner set to benj
Note: See TracTickets for help on using tickets.