Opened 21 months ago

Last modified 14 months ago

#601 new flight processing

RANNIS15/28, flight day 247b/2015, Hekla

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

Description (last modified by asm)

Data location: ~arsf/arsf_data/2015/flight_data/iceland/RANNIS15_28-2015_247b_Hekla

Data arrived from ARSF via SATA disk 8 on 28/09/2015.

Priority: Unknown

PI: Gro Pedersen

CAFAM code: R028

Sensors:

  • Fenix (requested but not flown due to failure)
  • Owl (requested - currently unfunded)
  • Leica LIDAR (requested)
  • RCD (requested)

Change History (28)

comment:1 Changed 21 months ago by dac

  • Description modified (diff)

comment:2 Changed 21 months ago by asm

General Processing

-No Fenix Data (No Returns)
-Only 3 flightlines on the logsheet, remaining coverage for Hekla.
-Notice that the logsheet is named as 248b but was recorded on 247b. Same for projects from 241 to 247. Fenix files has been renamed.
-It is recommended to process the data and afterwards generate the final Logsheet and remove from there the flightlines that have no usable data (Initially, 13 flightlines on overview).
-Flightlines 005 to HNI2_CROSS are from 247a and there are 5 flighylines on this area: 051a, 053a, 051b, 052, 053b. The last three are in accordance with the times recorded on the logsheet.

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

comment:3 Changed 21 months ago by asm

General Processing
Sent to PI ARSF data arrival notification for RANNIS15/28.

comment:4 Changed 19 months ago by asm

Navigation Processing

Started.

comment:5 Changed 19 months ago by asm

  • Description modified (diff)

Navigation Processing

Basestation verification has been done using data downloaded for REYK via Ipas TC. Navigation has been also done. Finished.

comment:6 Changed 19 months ago by asm

  • Description modified (diff)

comment:7 Changed 18 months ago by dac

PI prefers delivery by hard drive

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

comment:8 Changed 17 months ago by dac

Marking as blocked - still waiting on GPS data from IMO.

comment:9 Changed 17 months ago by asm

Navigation processing

Navigation reprocessed with GPS data provided by Icelandic Met-office .

Basestation verification for FEDG:
Latitude 64 01 30.92864
Lon -19 41 22.06204
Ell Height 503.927
Ant Height 1.00 m, to L1-PC (TRM411249.00, MeasDist 0.929)
Which corresponds on decimal degrees to the values sent by Met-office: -19.68946006 64.02525821 503.73149445

Basestation verification for HESA:
Latitude 64 02 48.62721
Lon -19 33 38.08804
Ell Height 529.118
Ant Height 1.090 m, to L1-PC (TRM411249.00, MeasDist 1.019)
Also match data received: -19.56057992 64.04684073 529.08620580 HESA deltaz=0.244

Basestation verification for MJSK:
Latitude 63 55 58.59991
Lon -19 40 20.53063
Ell Height 770.647
Ant Height 0.979 m, to L1-PC (Generic)
Also match data received:-19.6723625459 63.9329479506 770.861162678

Best solution found using FEDG. Basestation MJSK is shorter than IMU data and does not covers the entire flown data. Copying files and will rename old basestation and ipas_honeywell to old_nav_basestation (Please clean after processing, before archiving).

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

comment:10 Changed 16 months ago by lah

RCD processing

There are only 3 flight lines of data, though the logsheet overview indicates that there should be 13. It seems that the first 8 are 247a (though both logsheets state the julian day as 248) and 9 & 10 were aborted on logsheet b.

This may have caused an extra problem in creating the readme, as it looked for the lidar flightlines in the kml file and thought that line 4 name "ARSF post flight google earth file" was a lidar filename and subsequently crashed. Avoided by editing kml file while creating readme, so please check this works fine in DC.

There is a lot of cloud in the final 2 flightlines, which I've mentioned in the readme.

now ready for DC

Last edited 16 months ago by lah (previous) (diff)

comment:11 Changed 16 months ago by asm

RCD Delivery Check

There are still pictures covered by clouds with no usable data. Please check and remove:
->37-39
->59-62
->135 -143 (also I suggest to remove 144 and 145)

comment:12 Changed 16 months ago by lah

RCD

Removed the cloudiest images (and remade readme).

comment:13 Changed 16 months ago by lah

RCD

Removed removed images from kml file and eventfile.

comment:14 Changed 16 months ago by asm

RCD Delivery Check

Everything looks fine now. Ready to go.

comment:15 Changed 16 months ago by asm

Delivery

Camera data dispatched via hard drive on 03/03/2016.

comment:16 Changed 16 months ago by gej

Lidar processing

There are 5 lines in RAW laser files, but alspp says there are no return for one, and another only has 1% first returns and a size of 813kB, so have only processed the 3 lines which have a usable amount of data.

Pitch and roll found:

rollpitch
-0.00102-0.0022

Starting classification now.

comment:17 Changed 16 months ago by gej

Lidar Processing

Classification complete, creating delivery

comment:18 Changed 16 months ago by gej

Lidar Processing

Delivery and Readme created,

Ready for delivery check

comment:19 Changed 16 months ago by lah

started Lidar DC

  • Rather consistent pitch error of ~0.7m remains between 2nd & 3rd line. Was this found using the automated method or alsproc?

comment:20 Changed 15 months ago by gej

Lidar Processing

New pitch and roll of

rollpitch
-0.00102-0.002375

Classifying and remaking delivery now.

Last edited 15 months ago by gej (previous) (diff)

comment:21 Changed 15 months ago by gej

Lidar Processing

New delivery and readme created

Ready for DC

comment:22 Changed 15 months ago by lah

Lidar Processing

Creating a new delivery in the correct projection with:

line roll pitch
1 -0.001 -0.002375
2 -0.001 -0.0026
3 -0.001 -0.0026

Copied classification from old delivery and made some adjustments.

comment:23 Changed 15 months ago by lah

Lidar

New delivery and readme completed, ready for new delivery check.

comment:24 Changed 15 months ago by stgo

Lidar DC

Two issues:

  • logsheet James is called Jams
  • proj tidy complains about the naming of everything, this is to do with the RANNIS project name so I think we can overlook it. Files look correctly named.

comment:25 Changed 15 months ago by stgo

Lidar

Fixed logsheet, copying to hard drive.

comment:26 Changed 15 months ago by stgo

Delivery

Lidar data sent on USB harddrive 24/03/2016

comment:27 Changed 15 months ago by asm

Delivery

PI confirmed arrival of lidar data on 31/03/2016

comment:28 Changed 14 months ago by asm

RCD

PI requested pictures not included due to clouds (not usable data). Reprocessed and delivered again.

Delivered on 9/May/2016 using ftp 4

Note: See TracTickets for help on using tickets.