Opened 12 years ago

Last modified 10 years ago

#377 assigned flight processing

UR10/01 flight day 259b/2010, Iceland — at Version 16

Reported by: anch Owned by: knpa
Priority: alpha 5 Milestone: 2010 data processing completion
Component: Archiving Keywords:
Cc: Other processors:

Description (last modified by knpa)

Data location: /data/okhotsk1/scratch/arsf/archive-overflow/UR10_01-2010_259b_Iceland

Data arrived from ARSF via SATA disk DAPHNE 03 on 7/10/2010

Scientific objective: Not known

Priority: A5

PI: M. Kirkbride

Sensors:

  • Eagle
  • Hawk
  • Leica LIDAR (11/01/11)
  • Digital Photography (11/01/11)

Change History (16)

comment:1 Changed 12 years ago by anch

  • Description modified (diff)

comment:2 Changed 12 years ago by iopa

Applanix and IPAS done and are in 259a in the workspace.

comment:3 Changed 12 years ago by knpa

  • Owner set to knpa
  • Status changed from new to assigned

Starting eagle processing.

comment:4 Changed 12 years ago by knpa

Found eagle scts for most lines but a couple don't have sufficient wobbles.

Need LIDAR to correct.

comment:5 Changed 12 years ago by knpa

Taking LIDAR.

comment:6 Changed 12 years ago by knpa

Processed LIDAR has gaps in the data over the high areas, presumably volcano. Could be due to smoke or ice but looks to me like a range issue. Need to investigate further. The range settings in alspp look fine but Mark1 says there is a separate 'range gate' that is set manually. A record of this is kept in flightlinelog in leica/logs but this seems to be missing. Will request this file from ops and investigate further.

Note, this also occured in the other sortie of the day, 259a.

comment:7 Changed 12 years ago by anch

This has also occurred on flight day 258 (Am updating the other ticket now).

comment:8 Changed 12 years ago by knpa

Phone call from Phil:

This is indeed an issue with the range gate, the plane was flying lower than intended relative to the ground due to an out of date DTM (the volcano had caused the terrain to rise).

Can't do anything about these gaps, resuming processing.

comment:9 Changed 12 years ago by iopa

Camera delivery has been checked.

It might be worth adding a sentence in data quality remarks about images 622-625,629-631,
705-712 saying that the images are correct but the high brightness reflected from the snow has
caused the lens' shape to appear in the recorded image.

Otherwise all is good and ready for delivery.

comment:10 Changed 12 years ago by knpa

LIDAR QC:

Vertical and horizontally discrepancies OK. Doesn't appear to be any significant consistent roll.

Currently classifying. There is a LOT of noise on all flightlines (due to Ice I think, this would be consistent with previous projects).

comment:11 Changed 12 years ago by knpa

Finished LIDAR - awaiting delivery check.

comment:12 Changed 12 years ago by anch

Delivery checking LIDAR

comment:13 Changed 12 years ago by anch

LIDAR delivery checked - all looks good to go except the file

dem/README_DEM_MAY_NOT_BE_ACCURATE.txt

Which mentions SRTM when ASTER data has been used to generate the DEM.

comment:14 Changed 12 years ago by knpa

Have fixed above, preparing lidar for delivery.

comment:15 Changed 12 years ago by knpa

LIDAR and Photography data sent to M. Kirkbride at Dundee on 11/01/11

comment:16 Changed 12 years ago by knpa

  • Description modified (diff)
Note: See TracTickets for help on using tickets.