Opened 13 years ago

Closed 12 years ago

Last modified 7 years ago

#391 closed flight processing (fixed)

EUFAR11/03, flight day 095/2011, HYMEDECOS (erosion)

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

Description (last modified by knpa)

Data location: ~arsf/arsf_data/2011/flight_data/spain_portugal/EUFAR11_03-2011_095_HYMEDECOS_Erosion/

Data arrived from ARSF via network transfer on 19/04/11.

Scientific objective:
(1) to derive spatial information on vegetation, soil and terrain for hydrological model input by combined hyperspectral and
LiDAR data
(2) to conduct a spectral fingerprinting approach allowing to trace back sources and pathways of sediments. Airborne data
acquisition will be accompanied by an extensive field campaign

Priority: a4h

PI: H. Kaufmann

Sensors:

  • Leica LIDAR Replacement (27/06/2011)

Change History (14)

comment:1 Changed 13 years ago by knpa

  • Description modified (diff)

comment:2 Changed 13 years ago by emca

  • Owner set to emca
  • Status changed from new to accepted

Prcoessed the IPAS data - have created a folder on the workspace to put the data until the new directory structure has been finalised.

Going to start the LiDAR processing

comment:3 Changed 13 years ago by emca

LiDAR processing complete - ready for delivery check at
~arsf/arsf_data/2011/flight_data/spain_portugal/EUFAR11_03-2011_095_HYMEDECOS_erosion/processing/delivery/EUFAR11_03-095-lidar-20110616

comment:4 Changed 13 years ago by iopa

LiDAR delivery check ;

  • this is a mountainous region and lidar-aster discontinuity reaches upto ~50m, is mostly within ~20m however, the peaks of this difference (at 50m) can show artifacts during the mapping stage with the provided mapper for hyperspectral data, resampling+interpolating the DEM to a resolution that reduces this sudden step between neighbour cells below 25m can improve/fix this
  • if .tex is available could change EUFAR11_03 to EUFAR11/03 in first page of readme
  • rename logsheet to have day in format 095
  • could re-generated the logsheet for using the new bold format which looks nicer, with this command "generateLogsheet.py --renewtemplate -m auto -o processing/", it would mean re-entering the manual data but it doesn't look that much anyway

The data looks very good, nice work classifying those power cables.

comment:5 Changed 13 years ago by emca

Updated readme & logsheet for above changes.
Mentioned DEM issue in readme, but perhaps the hyperspectral readme is a more appropriate place for this.

Data ready to deliver.

comment:6 Changed 13 years ago by emca

  • Component changed from Processing: general to Archiving
  • Description modified (diff)

LiDAR data sent to PI 27/06/2011

comment:7 Changed 13 years ago by knpa

  • Description modified (diff)

comment:8 Changed 13 years ago by knpa

Beginning archiving.

comment:9 Changed 13 years ago by knpa

Tarball created and made available to NEODC (22/12/11)

comment:10 Changed 13 years ago by knpa

Archived by NEODC, moved to archive disk.

comment:11 Changed 12 years ago by knpa

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

comment:12 Changed 12 years ago by knpa

  • Milestone set to 2011 data processing completion

comment:13 Changed 7 years ago by asm

Archiving

Only Lidar data and Lidar delivery, created JSON files and started uploading them to CEDA for the EUFAR flight finder tool (started on 15/01/2018).

comment:14 Changed 7 years ago by asm

Archiving

Upload finished, CEDA notified on 18/01/2017.

Note: See TracTickets for help on using tickets.