Opened 11 months ago

Last modified 7 months ago

#711 new flight processing

SwathS, flight day 150/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_150_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 (19)

comment:1 Changed 11 months ago by jann

OWL: Some lines don't have nav data, these are data recorded in Siena.

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

comment:2 Changed 10 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 9 months ago by jann

Flightlines 1-29 only being processed, the remainder, lines 30-41 were recorded in Siena and have no nav data.

comment:4 Changed 9 months ago by jann

Radiometric calibration completed, waiting on boresight.

comment:5 Changed 8 months ago by wja

Last edited 8 months ago by wja (previous) (diff)

comment:6 Changed 8 months ago by wja

Fenix1k Processing

Line 7 was recorded when IMU was not facing nadir. Cannot map.

comment:7 Changed 8 months ago by wja

Fenix1k Processing

Geoaccuracy is not perfect but is not bad. Looks like a slight SCT and/or boresight error throughout.

Processing all bands

comment:8 Changed 8 months ago by wja

Line 4.0 failed. Reprocessing.

comment:9 Changed 8 months ago by asm

Owl Delivery

Jane created a delivery and I have added a readme and logsheet. This should be ready for DC now so will mark as such.

comment:10 Changed 8 months ago by wja

Delivery Check

Starting delivery check

comment:11 Changed 8 months ago by wja

Fenix1k Processing

Line 8 is when IMU is directed at an angle. Will not processing.

comment:12 Changed 8 months ago by wja

Owl Delivery

Delivery looks good.

Updated logsheet to include view angles.

Zipping mapped lines.

Marking ready to deliver.

comment:13 Changed 8 months ago by wja

Creating Fenix1k Delivery

comment:14 Changed 8 months ago by wja

Owl Delivery

Put on FTP slot 1. PI notified.

comment:15 Changed 7 months ago by wja

Fenix1k Delivery

Ready for checking

comment:16 Changed 7 months ago by dac

Fenix1k Delivery Check

  • Delivery had fodis folder, have removed
  • Spectra look good using Py6S checker script
  • check_apl_cmd ran through OK.
  • Geolocation in line 7 (both parts) is way off, looks too far south
  • For line 5 part 1 it looks like the timing is slightly off towards the north, part 0 looks good so it could just be due to the length of the line and not much we can do about it.
  • Other lines looks good and align well with Owl from the quick check I did.
  • No geometry files. Think they are only needed for Owl but might be worth mentioning when delivering

Once line 7 is fixed then is good to go.

comment:17 Changed 7 months ago by wja

Fenix1k Delivery Check

Line 7 was recorded when the IMU was directed at and angle. Will remove mapped and nav data and add a note in the Read Me.

Line 5 and Line 8 show flight timing errors. However, I think this is a FPS issue (or a combination of both) as both are worse at the end of the line compared to the start. Nevertheless, they match well with the owl data so will include with a note in the readme.

Will let PI know about absense of geometry files when delivering.

Zipping mapped data

comment:18 Changed 7 months ago by wja

Fenix1k Delivery

Marking ready to delivery (when zipping is complete)

comment:19 Changed 7 months ago by wja

Fenix1K Delivery

Added geometry files (aplcorr --atmosfile outputs) to the deliveries at PI's request.

Note: See TracTickets for help on using tickets.