Opened 6 years ago

Closed 4 years ago

#500 closed flight processing (fixed)

IG13/19, flight day 224b/2013, Virkisjokull

Reported by: knpa Owned by:
Priority: alpha 4 medium Milestone: 2013 data processing completion
Component: Processing: general Keywords:
Cc: Other processors:

Description (last modified by knpa)

Data location: /users/rsg/arsf/arsf_data/2013/flight_data/greenland_iceland/IG13_19-2013_224b_Virkisjokull

Data arrived from ARSF via network transfer on 23/08/2013

IG13/19 Scientific objective: unknown

IG13/19 Priority: 8

PI: Tom Bradwell

Notes: Low to zero returns on some lidar line due to surface water.

Sensors:

Camera
Eagle
Hawk
LiDAR

Change History (23)

comment:1 Changed 6 years ago by knpa

  • Description modified (diff)

comment:2 Changed 6 years ago by besm

Started navigation data processing without decent basestation files. This will need to be redone when the basestation data arrives.

comment:3 Changed 6 years ago by besm

Created rough navigation solution to correct SCTs with. Started hyperspectral processing.

comment:4 Changed 6 years ago by stgo

New ppp result:

Lat 66 24 02.38154
Long 38 12 50.55338
Height 421.299

comment:5 Changed 6 years ago by besm

Hyperspectral delivery created. This was delayed because of the lack of basestation data meaning no navigation solution was accurate enough to do some of the SCTs. Processing has now been completed with a low quality solution using the basestation data, but a better solution may soon become available for the LiDAR data.

Delivery checker should be aware that the navigation solution did not have a great quality, but should be ok. Watch out for inaccurate SCTs.

Last edited 6 years ago by besm (previous) (diff)

comment:6 Changed 6 years ago by stgo

Delivery checked, 2 things need to be mentioned in the readme:

  • large amount of underflow in hawk lines 2 4 5 and 8
  • the quality of the navigation data is bad, it will not improve beyond what we have.

Otherwise ready to deliver.

comment:7 Changed 6 years ago by besm

Made those changes to the hyperspectral readme. Ready to be checked.

comment:8 Changed 6 years ago by stgo

Hyperspectral delivery checked, included logsheet and ready to deliver.

Last edited 6 years ago by stgo (previous) (diff)

comment:9 Changed 6 years ago by stgo

Lidar has extremely low returns on all lines:
001 54.0%
002 53.6%
003 51.2%
004 37.2%
005 20.0%
006 3.0%
007 0%
047 26.5%

comment:10 Changed 6 years ago by stgo

Hyperspectral delivered 03/10/2013

comment:11 Changed 6 years ago by stgo

LiDAR ready for delivery check.

comment:12 Changed 6 years ago by stgo

RCD Image events file is full of non data (same gps second for all tiffs) this means all are recognised as outbounds. Will manually check each image then minimally tag for delivery.

comment:13 Changed 6 years ago by emca

Delivery checked LiDAR and RCD.

LiDAR - just need to change the name of the nav files to be consistent with naming structure (PROJCODE-YEAR_JULDAY), otherwise ready to deliver.

RCD - Remove the Image Collection "overview of your photographs" bit as there are no images displayed. Also add something to say that the KML file only contains the Eagle/Hawk and LiDAR but no camera data due the issues during data collection.

comment:14 Changed 6 years ago by stgo

Made corrections according to the above, RCD readme could do with my alterations being checked to make sure tey are suitable before being sent.

comment:15 Changed 6 years ago by emca

RCD readme is fine, ready to deliver.

comment:16 Changed 6 years ago by stgo

I will check the navigation with the new basestation data sent by PI before delivering LiDAR, if there is no improvement then we'll continue otherwise will reprocess LiDAR with new nav solution.

comment:17 Changed 6 years ago by stgo

PIs data has considerably improved the navigation data, it's still not great but much better than what was used with the LiDAR before. I will reprocess this data before sending the final delivery.

comment:18 Changed 6 years ago by stgo

Recreated LiDAR delivery with new nav, ready for delivery check.

comment:19 Changed 6 years ago by emca

Delivery checked LiDAR data.

The readme says the nav result was poor - not sure if this is from the old or new nav. If not relevant this can be removed. Also low returns are due to the surface (mainly water) - gaps in data are due to range gate problem. Otherwise no issues, ready to deliver.

comment:20 Changed 6 years ago by stgo

Made the alterations to the readme, creating dispatch.

comment:21 Changed 6 years ago by stgo

Camera and LiDAR dispatched 22/10/2013.

comment:22 Changed 4 years ago by tec

Archival
Starting

comment:23 Changed 4 years ago by dac

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

Archiving

Data now available from NEODC.

Note: See TracTickets for help on using tickets.