Opened 6 months ago

Closed 6 weeks ago

#632 closed flight processing (fixed)

CEH18/16, flight day 177b/2018, Monks Wood

Reported by: dac Owned by:
Priority: whenever Milestone:
Component: Processing: general Keywords:
Cc: Other processors:

Description (last modified by dac)

Data location: ~arsf/arsf_data/2018/flight_data/uk/CEH18_16-2018_177b_Monks_Wood

Data arrived from NERC-ARF hard drive on 13/07/2018

Scientific objective: Flight over Monks Wood

Priority: Unknown

PI: France Gerard
BAS Project Code: C016

The following issues were identified during unpacking

  • Owl data missing GPS start time.

Sensors:

  • Fenix (flown, required)
  • OWL (not flown, required)
  • Phase One (flown, required)

Change History (26)

comment:1 Changed 6 months ago by wja

Navigation Processing

Navigation processing under way.

comment:2 Changed 6 months ago by wja

Navigation Processing

Basestation PPP:

Latitude52°11'07.33076"
Longitude-0°06'44.96865"
Ellipsoid Height120.209m

This is using the St. Neots OS basestation (SNEO), however these PPP results are considerably different (minutes) to the ones generated for flight 2018 129 (ticket #628) which also uses this basestation. Will look into why this is so different.

comment:3 Changed 6 months ago by wja

Navigation Processing

The above basestation PPPs are close to the basestation location recorded in the RINEX header. Will continue processing using these values.

comment:4 Changed 6 months ago by dac

Digital Camera Processing

Converted raw images to tiffs.

comment:5 Changed 6 months ago by dac

  • Description modified (diff)

comment:6 Changed 6 months ago by dac

Hyperspectral Processing

Starting hyperspectral processing using .sol file Mark generated.

comment:7 Changed 6 months ago by wja

Owl Processing

Starting owl processing.

First looks:

-20 flightlines.
-Darkframes are not recorded in the data. DARKREF.raw data exists for all flightlines apart from 3.
-T1 calibration data missing for flightlines 3, 8 and 9.
-T2 calibration data only present for flightlines 1, 2 and 4.
-No navigation synchronisation.
-The following flightlines each have 1 dropped frame recorded in their log files: 2, 4, 9, 10, 13, 14, 19.

comment:8 Changed 6 months ago by dac

Hyperspectral Processing

Using sol file created with basestation produced files with lots of geolocation problems (wobbly, wrong location, twisted in parts). After lots of work on trying to process with basestation used PPP processing for aircraft GPS. Fenix files processed well with this. Found SCT values:

Flightline FENIX
1 2
2 2
3 1
4 37.04
5 2
6 2

Mapping all bands.

Last edited 6 months ago by dac (previous) (diff)

comment:9 Changed 6 months ago by wja

Navigation Processing

Reprocessed using the Peterborough (PETE) OS basestation. Here are the PPP results.

Basestation PPP:
Latitude 52°35'01.53701"
Longitude -0°15'47.43300"
Ellipsoid Height 72.841m

*.sol file generated using this basestation and has been moved to /posatt/ipas20/basestation_PETE.
Analysis looks okay, only area of potential concern is Solution Analysis peaks exceed ±0.05 but do not go beyond ±0.1.

comment:10 Changed 6 months ago by dac

Hyperspectral Processing

Reprocessed using .sol file created using basestation. Geolocation looks good. Creating delivery.

comment:11 Changed 6 months ago by dac

Hyperspectral Processing

Generated delivery. Waiting for delivery check.

comment:12 Changed 6 months ago by dac

Hyperspectral Processing

Line 4 had a problem with time in navigation going backwards. Processed using use_nav = false and did manual SCT correction. Found value to be 37.04 (table above updated).

Moved files to existing delivery. Ready for checking.

comment:13 Changed 6 months ago by wja

Hyperspectral Delivery Check

Logsheet plot of flightlines is missing flightline 4. Otherwise all looks good.

comment:14 Changed 6 months ago by dac

Hyperspectral Delivery

Fixed logsheet. Started zipping mapped files.

comment:15 Changed 6 months ago by wja

Hyperspectral Delivery Sent
Delivery via FTP 4. Notification e-mail sent to PI.

comment:16 Changed 5 months ago by dac

Owl data

Owl lines were copy of data from 177a. Marking as blocked until data for this flight are received from ops.

comment:17 Changed 5 months ago by dac

Digital Camera

Offset between creation time and GPS of 7287 seconds found for 178 also works for this flight. Tagging photos using this.

comment:18 Changed 5 months ago by dac

Digital Camera

Generated delivery. Ready for checking.

comment:19 Changed 5 months ago by wja

Digital Camera Delivery Check
Read_Me correctly mentions that photographs 1-3 & 254 do not have GPS metadata tagged, although EXIFtool sample output is of photo 1. May need changing to include GPS related fields if deemed necessary.
Delivery otherwise looks ready to deliver.

comment:20 Changed 5 months ago by dac

Digital Camera

Removed photographs without GPS, renumbered and remade Readme.

comment:21 Changed 5 months ago by dac

Digital Camera

Data delivered to PI via FTP (slot 4).

comment:22 Changed 4 months ago by dac

  • Description modified (diff)

Owl

Owl failed during flight and no data were collected.

comment:23 Changed 2 months ago by wja

Archiving
Preparing archive for CEDA.

comment:24 Changed 2 months ago by wja

Archiving
Started rsync to CEDA.

comment:25 Changed 2 months ago by wja

Archiving
rsync to CEDA complete.

comment:26 Changed 6 weeks ago by wja

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

Archived
Received confirmation of upload to CEDA. archived_flight.txt has been updated. Closing ticket.

Note: See TracTickets for help on using tickets.