Opened 6 years ago

Last modified 8 days ago

#408 assigned flight processing

EU10/01, flight day 180/2011, Norrunda

Reported by: anch Owned by: knpa
Priority: immediate 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/sweden/EU10_01-2011_180_Norrunda

Data arrived from ARSF via network transfer on 13/07/2011

EU10/01 Scientific objective: 1. To provide better understanding of the key impact factors on CO2 and H2O fluxes of mixed forest stands 2. To reduce uncertainty in the upscaling of greenhouse gas fluxes to a regional or even global scale.

EU10/01 Priority: a5

PI: Natascha Klujn

Sensors:

Camera (26/08/2011)
Eagle (28/09/2011)
Hawk (28/09/2011)
LiDAR (28/09/2011)

Change History (29)

comment:1 Changed 6 years ago by anch

Starting navigation processing

comment:2 Changed 6 years ago by knpa

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

Created binary dem for HS use at ~/dems/sweden_norrunda

comment:3 Changed 6 years ago by knpa

Added VNIR and SWIR prefix.

Line 1 (SWIR180-11-1.raw) and associated files were incorrectly named as datacube.*

Have fixed. There doesn't appear to be any actual datacube file included.

comment:4 Changed 6 years ago by anch

Finished navigation processing.

Created SOL file, camera.sol file and sbet

comment:5 Changed 6 years ago by jaho

Removed camera images 1 to 16 (take before the flights) and 257-372 (taken after the flights).

comment:6 Changed 6 years ago by jaho

Lidar ready for delivery check.

comment:7 Changed 6 years ago by knpa

  • Owner changed from anch to jaho

Beginning LiDAR delivery check.

comment:8 Changed 6 years ago by knpa

Delivery check completed. Issues:

  1. Don't need "LiDAR data for Line " for each line name entry in ReadMe.
  2. Should use names in data quality elevation difference Readme section - e.g. Nor019 and Nor018.
  3. Classification needs improving. Many false classifications (trees) and some significant groups of missed points under ground. (Lines 08 & 03 checked)

Once these things are fixed then this should be ready to deliver (unless you regenerate the LiDAR lines entirely in which case they will need to be rechecked)

comment:9 Changed 6 years ago by jaho

Camera for 178 and 180 sent to Natascha Kljun on 26/07/2011 on disk 110.

comment:10 Changed 6 years ago by adbe

  • Removed "LiDAR data for Line " for each line name entry in ReadMe.
  • Added names in elevation difference
  • Re-classified lines

-Needs to be re-checked

comment:11 Changed 6 years ago by knpa

  • Owner changed from jaho to adbe

Classification looks better, ready to deliver.

comment:12 Changed 6 years ago by adbe

Created hyperspectral delivery

comment:13 Changed 6 years ago by knpa

Starting delivery check.

comment:14 Changed 6 years ago by knpa

Delivery check complete.

All looks good apart from:

  1. project_information/project_readme - what is that?
  2. Need to included a misc file for use with ASTER dem.
  3. Might need to unix2dos hawk bad pixel files
  4. First and last eagle bands are blank - need to mention in readme.
  5. First hawk band blank - ditto
  6. Get rid of tmp_check directory

comment:15 Changed 6 years ago by adbe

Delivered LiDAR and hyperspectral on disk 84 to Natascha Klujn.

comment:16 Changed 6 years ago by adbe

  • Description modified (diff)

comment:17 Changed 6 years ago by adbe

  • Component changed from Processing: general to Archiving

comment:18 Changed 5 years ago by mark1

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

comment:19 Changed 5 years ago by adbe

lineeaglehawk
1-0.02-0.04
2-0.02-0.04
3-0.03-0.11
40.000.03
5-0.04-0.11
6-0.01-0.01
7-0.07-0.11
8-0.02-0.02
9-0.02-0.04

comment:20 Changed 5 years ago by knpa

  • Owner changed from adbe to knpa

Beginning archiving.

comment:21 Changed 2 weeks ago by dac

PI requested full waveform data - is available so just needs to be processed.

Assigning asm to process.

comment:22 Changed 13 days ago by asm

Lidar Re-processing

Started. Found a corrupt file that was causing problems. Removed LDR110629_102146_0000000001.scn as it was 0 in size from the RawLaser.

comment:23 Changed 13 days ago by asm

Lidar Re-Processing

Found a small pitch offset. New values:

pitch -0.0028
roll 0.002173359

Will create the FW files

comment:24 Changed 12 days ago by asm

Lidar Re-Processing

Lidar discrete files have been re-classified. Running over FW.

comment:25 Changed 12 days ago by asm

Lidar Re-Processing

Creating new delivery and readme.

comment:26 Changed 11 days ago by asm

Lidar Re-Processing

Delivery created. Awaiting delivery check.

comment:27 Changed 9 days ago by lah

Lidar DC

Have done most checks and most things look ok. Full waveform are present in waveviewer some of the time, and laszip works fine. Just need to view the files in lag, but unfortunately it is only loading a single pixel of each file if anything, so will have to use another computer.

comment:28 Changed 9 days ago by lah

Lidar DC

Overlap and classification look good, so good to deliver (got LAG working on VM).

comment:29 Changed 8 days ago by asm

Lidar Delivery

Delivered to PI via FTP (using slot 20) on 21-March-2017. Notification mail has been sent.

Note: See TracTickets for help on using tickets.