Opened 8 years ago

Last modified 7 years ago

#417 assigned flight processing

EM10/06, flight day 260/2011, Italy

Reported by: knpa Owned by: knpa
Priority: alpha 4 medium Milestone: 2011 data processing completion
Component: Archiving Keywords:
Cc: Other processors:

Description (last modified by adbe)

Data location: /users/rsg/arsf/arsf_data/2011/flight_data/italy/EM10_06-2011_260_Italy

Data arrived from ARSF via network transfer on 28/09/2011

EM10/06 Scientific objective:
Earthquake study in Italy by examination of geology.

EM10/06 Priority: a4m

PI: Ken McCaffrey

Notes: This project was previously flown in Greece last year but the data was confiscated.

Sensors:

Camera (25/11/2011)
Eagle (25/11/2011)
Hawk (25/11/2011)
LiDAR (25/11/2011)

Change History (22)

comment:1 Changed 8 years ago by knpa

  • Description modified (diff)

comment:2 Changed 8 years ago by adbe

Started to process navigation

comment:3 Changed 8 years ago by adbe

Processed navigation: poor quality (best solution)

comment:4 Changed 8 years ago by adbe

Started camera processing

comment:5 Changed 8 years ago by emca

Blocking LiDAR processing:
Processing of day 265 shows very low intensity values and max AGC values. This is possibly due to the high altitude of flight during data collection. Querying with Ops.

comment:6 Changed 8 years ago by adbe

Camera ready for delivery check

comment:7 Changed 8 years ago by knpa

Checking camera.

comment:8 Changed 8 years ago by knpa

Camera delivery check completed.

No problems, ready to deliver.

comment:9 Changed 8 years ago by emca

Processing LiDAR data.

The data will need to be flagged as bad in the delivery due to the intensity issues mentioned above. We presently have no way to correct the intensity or to compensate for the incorrect elevation values.

comment:10 Changed 8 years ago by jaho

Started hyperspectral processing.

comment:11 Changed 8 years ago by jaho

Hyperspectral ready for delivery check.

comment:12 Changed 8 years ago by emca

Processing LiDAR data.

Classifying the points. Due to the large tree height a lot of ground points were misclassified as noise. Reclassified (using -isolated 12 1) to try to retain the ground hits as valid data and still identify the random high/low points as noise. Some mis-classified points may remain in the data but this seemed to be the best compromise.

comment:13 Changed 8 years ago by adbe

Hyperspectral Delivery Check:

  • Mention in ReadMe that eagle bands 0 and 254 are blank (first and last)

Otherwise, ready to deliver.

comment:14 Changed 8 years ago by jaho

ReadMe updated.

comment:15 Changed 8 years ago by emca

LiDAR data ready for delivery check.

Missing pdf readme but tex version should be available (left it running).

comment:16 Changed 8 years ago by adbe

LiDAR delivery check:

  • There is a file "u2dtmpH1a9EU" in the ascii directory
  • DEM is gridded at 5.0 metre pixels, usually 2.0

Otherwise, ready to deliver

comment:17 Changed 8 years ago by jaho

Removed u2dtmpH1a9EU.

comment:18 Changed 8 years ago by adbe

Camera, Hyperspectral and LiDAR delivered to Ken McCaffrey on 25/11/2011 on disk 102

comment:19 Changed 8 years ago by adbe

  • Description modified (diff)

comment:20 Changed 8 years ago by mark1

Hyperspectral XML files have been re-created and re-delivered to PI (via email). This corrects Eagle IFOV value in XML and extra comments included.

comment:21 Changed 8 years ago by adbe

Hyperspectral sct's

lineeaglehawk
1-0.15-0.05
2-0.06-0.06
3-0.040.00
4-0.13-0.10
5-0.080.01
6-0.030.02
7-0.05-0.03
8-0.08-0.03
90.050.01
10-0.10-0.07
11-0.020.04
12-0.08-0.14
13-0.020.05
14-0.11-0.10
150.030.05
16-0.06-0.13
17-0.05-0.05

comment:22 Changed 7 years ago by knpa

  • Component changed from Processing: general to Archiving
  • Owner changed from emca to knpa
  • Status changed from new to assigned

Beginning archiving.

Note: See TracTickets for help on using tickets.