Opened 4 months ago

Last modified 7 weeks ago

#715 new flight processing

SwathS, flight day 177a/2023, Grosseto

Reported by: jann Owned by:
Priority: immediate Milestone:
Component: Processing: general Keywords:
Cc: Other processors:

Description

Data location: /users/rsg/airborne/2023_arsf_data/flight_data/italy/SwathS_23-2023_177a_Grosseto

Data arrived from NERC-ARF via hard drive September/October 2023

PI: Martin Wooster

Sensors:
Fenix1k (requested, flown)
IBIS ( main requested, flown)
OWL ( requested, flown)

Change History (14)

comment:1 Changed 4 months ago by jann

Final checks - warning about the real time navigation time stamps was flagged.

comment:2 Changed 3 months ago by wja

Navigation Processing

Basestation data converted to RINEX. All previous flights are also included in the basestation data, so just this flights data needed to be extracted (done with teqc).

GPS and GLONASS broadcast ephermides, along with precise ephemeris data accessed from CDDIS. PosPac could not access these itself.

Completed processing using the single base method.

comment:3 Changed 3 months ago by wja

Owl Processing

This is a priority flight.

comment:4 Changed 3 months ago by wja

Owl Processing

All calibration files present, no significant frames dropped (other than line 1, has 5 dorpped frames), headers look fine.

Processing to L1b on the grid.

comment:5 Changed 3 months ago by wja

Owl Processing

Line 10 failed, unsure why. Reprocessing locally.

comment:6 Changed 3 months ago by wja

Owl Processing

All lines processed to L1b. APL config produced (but needs updating). Data need mapping.

SRTM DEM produced.

comment:7 Changed 3 months ago by wja

Owl Processing

Note there are three boresights. APL config seems to handle this if there's an owl_boresight parameter in owl line section that isn't a nadir facing line.

Testing mapping with three lines.

Four lines failed to map: 1, 7, 13 and 17.

1 failed because "time goes backwards" in the navigation file. Will need to force this.

Other lines failed because they are out of the extent of the DEM. Will need to recreate.

Geoaccuracy of the rest of the lines look good.

comment:8 Changed 3 months ago by wja

Created new DEM to cover whole area. This should be good to use for any 2023 Italy flight.

comment:9 Changed 2 months ago by wja

Ready for checking

Delivery created.

Note it includes view angles in logssheet and the addition of geometry files.

comment:10 Changed 2 months ago by asm

Owl DC

Started

Last edited 2 months ago by asm (previous) (diff)

comment:11 Changed 2 months ago by asm

Owl DC

-The DEM was symlinked only to the processing dir and therefore the scripts failed to copy across in the delivery. Copied that manually.
-Navigation for line 01 is missing.
-Flightline 01 is not mapped correctly (very wobbly)
-The spectra for a lot of files is not correct. It looks like there was a lot of saturation and the software could not process the data properly. This affects a large number of flightlines in this project. I am having a closer look to this.

comment:12 Changed 2 months ago by asm

Owl DC

-The spectra of the mapped owl lines is correct. This was an artifact caused by Tuiview when visualising the files as it was relying on xml files that were likely created by another visualization tool. Once those files were deleted from the directory, the files showed good spectra.
-Flightline 01 is wobbly due to a fail with the navigation. I have therefore taking this out from the delivery and we are only delivering level1b for this flightline. I made a note on the quality issues in the readme for this.
-All other checks have been run and all passed. I am zipping the files and will mark this project as ready to be delivered as soon as those are zipped and checked.

comment:13 Changed 8 weeks ago by asm

Owl DC

Mapped files were zipped fine. Project is ready to be delivered.

comment:14 Changed 7 weeks ago by dac

Delivery
Copied to FTP server (arsf1)

Note: See TracTickets for help on using tickets.