Opened 15 months ago

Last modified 3 months ago

#705 new flight processing

SPLICE, flight day 200/2023, Alice Holts

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

Description (last modified by asm)

Data location: /users/rsg/arsf/arsf_data/2023/flight_data/uk/SPLICE-2023_200_Alice_Holts

Data arrived from NERC-ARF via hard driver on 19/07/2023
Evaluate the impact of 3D structure on calculations of photosynthesis

PI: Tristan Quaife

Sensors:
Fenix1k (requested, flown)
IBIS ( main requested, flown)
Camera ( requested, flown)
LiDAR ( requested, flown)

Change History (24)

comment:1 Changed 15 months ago by asm

  • Description modified (diff)

comment:2 Changed 15 months ago by asm

Data unpacked
There are 16 IBIS lines.
Fenix1k crashed collecting 1 line and did not collected the following one resulting on 14 usable lines. Moved 1 line to a "crashed dir".
Basestation collected by NERC-FSF has been also download and added to the project.
Ibis and Fenix1k files have been renamed. Project is ready for processing.

comment:3 Changed 15 months ago by asm

PI notified of data arrival on 4th August 2023

comment:4 Changed 12 months ago by wja

Navigation Processing

Processing navigation data.

FSF provided their basestation data. I also downloaded the following stations from OS:

  • AMER
  • ARDL
  • CHIO
  • HARD
  • HART
  • NEWR
  • PRIS
  • SANO
  • SHOE
  • SNEO
  • SOTN
  • STEE
  • STRA
  • TEDD
  • WEIW

These basestations should cover a conclusive area between Duxford and Alice Holts.

comment:5 Changed 12 months ago by wja

Navigation Processing

Completed processing in POSPac using the SmartBase (multi basestation) method.

Basestations used:

  • AMER
  • CHIO
  • HARD
  • NEWR
  • PRIS
  • SANO
  • SNEO
  • SOTN
  • STEE
  • STRA
  • TEDD

ARDL, SHOE and WEIW were not needed due to distance, HART had incomplete temporal coverage.

Lever arms were estimated as: 0.427 -0.497 -1.48

Have exported with angular offset of Z: 180 (IMU is backwards relative to Ibis and Fenix1k for this flight).

comment:6 Changed 12 months ago by wja

Hyperspectral & Ibis Processing

Processed Fenix1k data with three bands using boresight values from flight 2023 198 (ticket #704). Geoaccuracy looks good.

Need to calculate Ibis boresight. There is no data from flight 2023 190 (Alconbury) so will have to use 2023 143 (Siena).

comment:7 Changed 12 months ago by wja

Fenix1k Processing

Mapping all bands

comment:8 Changed 12 months ago by wja

Ibis Processing

Still doing boresight.

SCT errors on lines 11 & 14 (possible due to frames being dropped).

comment:9 Changed 12 months ago by wja

Ibis Processing

Calculated boresight from Siena (flight 2023 143, ticket #702) but the values are wrong for this flight. The sensor must have moved sometime between these flights.

Will do my best to estimate boresight from this flight's flightlines.

comment:10 Changed 11 months ago by wja

Felix Delivery

Ready for checking.

Note, this is just the standard delivery. Level 2 data has been requested but Ibis l1b will be prioritised first.

comment:11 Changed 11 months ago by wja

Ibis Processing

Have painstakingly found what I think is the best boresight we can do without the proper flightline configuration. Spatial offset is a few pixels (~3m) and does not seem consistant. Unfortunately I think this the best we can do without a proper boresight flight.

Processing all bands.

comment:12 Changed 10 months ago by wja

Ibis Delivery

Created. Ready for checking.

comment:13 Changed 10 months ago by wja

Fenix1k delivery check

Undertaken by anla.

  • check_apl_cmd didn't run properly
  • No project information XML
  • Line 11 too large for fastQC

Zipping mapped files.

comment:14 Changed 10 months ago by asm

Ibis Delivery Check

Started

comment:15 Changed 10 months ago by asm

Ibis Delivery Check

-Data looks good as far as I can tell. The oxygen absorption at 760 nm is clearly visible through all data.
-There is no underflows or overflows.
-There were two screenshots for each line. Deleted duplicates labelled as UTM.
-Check_apl_cmd needs updating. I will recheck after that.

comment:16 Changed 9 months ago by asm

Ibis Delivery Check

-Mark updated check_apl_cmd, all running good.
-There is quite a bit of cloud shadows in the data, it might be good to capture that in the data quality section of the readme but it is rather obvious in the data.
-Started zipping files and will mark as delivered once completed and checked as all other checks were done and the delivery passed all.

comment:17 Changed 9 months ago by asm

Ibis Delivery Check

-Mapped files have been zipped successfully. Marking this project then as ready to go.

comment:18 Changed 9 months ago by wja

Deliveries Sent

Fenix1K and Ibis deliveries placed on FTP slot 17. PI notified. Deliveries finalised.

comment:19 Changed 8 months ago by asm

Fenix1k atmospheric correction

Delivery created and ready to be checked.

comment:20 Changed 8 months ago by asm

Ibis Delivery

Just noting here that IBIS flightline 12 could not be processed and delivered because there were no dark frames collected for this flightline.

comment:21 Changed 8 months ago by asm

Fenix1k atmospheric correction

This delivery has been checked and it is ready to be delivered.

comment:22 Changed 3 months ago by wja

LiDAR Processing

Continuing development work on this dataset.

comment:23 Changed 3 months ago by wja

LiDAR Processing

Note there is no fullwaveform for this flight, there is a Digitizer directory within the raw directory but it is empty.

Note that the presence of this file might obligate the LMS software to "try" and process fullwaveform.

comment:24 Changed 3 months ago by wja

LiDAR Processing

The LMS standard discrete data processing steps have completed. Exporting to ASCCI and LAS1.2.

Note: See TracTickets for help on using tickets.