Opened 5 years ago

Last modified 3 years ago

#528 new flight processing

GB13/01, flight day 164/2014, Bury St Edmunds

Reported by: knpa Owned by:
Priority: alpha 4 high Milestone: 2014 data processing completion
Component: Processing: general Keywords:
Cc: Other processors:

Description (last modified by tec)

Data location: /users/rsg/arsf/arsf_data/2014/flight_data/uk/GB13_01-2014_164_Bury_St_Edmunds

Data arrived from ARSF via network transfer on 13/06/2014

GB13/01 Scientific objective: a combination of an ecological model with remotely sensed data can result in an accurate, high resolution map of vegetation communities. Such maps can form the basis to model the distribution of animal species or groups.

GB13/01 Priority: 9

PI: Tim Benton (different to logsheet - check)

Notes: Owl Present FW present LiDAR and OWL missing for 19:43 line. Deleted corrupted webcam images 091457 and 093128

Sensors:

Camera (Requested), Archvied 13/05/2015
Fenix (Requested), Archvied 13/05/2015
LiDAR (Requested), Archvied 13/05/2015
FW LiDAR (Not requested), Archvied 13/05/2015
OWL

Change History (30)

comment:1 Changed 5 years ago by tec

Started processing navigation data.

comment:2 Changed 5 years ago by tec

Basestation Data
Latitude52 16 00.50433
Longitude0 24 54.96244
El Height72.813m
Last edited 5 years ago by tec (previous) (diff)

comment:3 Changed 5 years ago by tec

The navigational data for the first and last flight lines might be less accurate as there is an ambiguity fix of 1.

comment:4 Changed 5 years ago by tec

Finished navigation processing.

comment:5 Changed 5 years ago by tec

Started processing the RCD and Fenix data.

comment:6 Changed 5 years ago by dap

Beginning LiDAR processing.

comment:7 Changed 5 years ago by tec

Fenix SCT Values:

FlightlineSCT
01 0.95
02 0.97
03 0.97
04 0.97
05 0.96
06 0.97
07 0.96
08 0.97
09 0.95
10 0.99
11 0.95
12 0.97
13 0.97
14 1.00
Last edited 5 years ago by tec (previous) (diff)

comment:8 Changed 5 years ago by dap

Poor return values from LiDAR data in ALSPP on line 093401, possibly due to change in altitude.

comment:9 Changed 5 years ago by dap

-0.005569263 used as roll error in LiDAR processing

Last edited 5 years ago by dap (previous) (diff)

comment:10 Changed 5 years ago by dap

Finished LiDAR processing. Awaiting delivery check.

comment:11 Changed 5 years ago by tec

Finished Fenix processing. Awaiting delivery check.

comment:12 Changed 5 years ago by benj

Delivery checking this but stuck checking APL commands - aplcorr is segfaulting on me:

airborne@pmpc1384:/users/rsg/arsf/arsf_data/2014/flight_data/uk/
GB13_01-2014_164_Bury_St_Edmunds/processing/delivery/
GB13_01-164-hyperspectral-20140722#
check_apl_cmd -c /users/rsg/arsf/arsf_data/2014/flight_data/uk/
GB13_01-2014_164_Bury_St_Edmunds/processing/hyp_genreadme-airborne.cfg

[snipped]

Will trim view vectors to fit the level 1 filename: 
flightlines/level1b/f164011b.bil
Creating view vector object.
/users/rsg/arsf/usr/bin/check_apl_cmd: line 289: 10900 Segmentation fault      
(core dumped) aplcorr -lev1file flightlines/level1b/f164011b.bil -igmfile 
../../tmp_cmd_check/f164013b.igm -vvfile /data/visuyan2/scratch/arsf/2014/
flight_data/uk/GB13_01-2014_164_Bury_St_Edmunds/processing/delivery/
GB13_01-164-hyperspectral-20140722/sensor_FOV_vectors -navfile flightlines/
navigation/f164011b_nav_post_processed.bil -dem dem/GB13_01-2014_164-ASTER.dem

Things found so far:

  • Generated logsheet seems to have gone off the side of the first page
  • CSS and XSL files are in the doc, the project_information directory as well as the line_information directory - we should just deliver one copy (in project_information)?
  • No vector mosaic present - do we have vectors for this flight?
  • Mosaic screenshot breaks eog (somehow). Works with xvj and Gimp though. Don't know if we care.
  • Text files need converting to DOS format (unix2dos)
  • Readme description of the "flightlines" directory is "Directory containing the level1b datasets" - this isn't all that's in here. Probably the readme generator needs an update?
  • Readme comment on DEMs - "Also note that processing without a Digital Elevation Model (DEM) will result in substantial inaccuracies for any non-flat terrain." - Should say any terrain significantly above the vertical datum used. The terrain might be flat but if it's 100m above the ellipsoid there'll still be big errors. Pretty sure this is something else that will need changing in the readme generator.

comment:13 Changed 5 years ago by benj

Command checks taking forever. Have checked everything except full set of APL commands (results running into ~benj/scratch/delcheck), proj_tidy, correct L3 files and correct L3 projection.

comment:14 Changed 5 years ago by benj

Note screenshots all have "stretched" pixels along the edges. Need to check if this is present in the L3s or just an artifact of screenshot generation.

comment:15 Changed 5 years ago by benj

Fenix delivery check completed, fix issues above and then good to go.

comment:16 Changed 5 years ago by tec

PI wants it now, doesn't want to wait for vectors. Fixed logsheet. Fixed Readme. Fixed line endings. CSS files are OK according to mark1.

comment:17 Changed 5 years ago by stgo

Delivery checking camera.

comment:18 Changed 5 years ago by stgo

Camera delivery complete:

  • take out image 00001, it's overexposed.
  • weird tint on image 381, should be explained or removed

comment:19 Changed 5 years ago by dap

Points from RCD delivery check corrected. Ready for re-check.

comment:20 Changed 5 years ago by knpa

Beginning LiDAR delivery check.

comment:21 Changed 5 years ago by tec

Delivery checked camera. All seems fine. Ready for delivery.

comment:22 Changed 5 years ago by knpa

LiDAR delivery check complete. Following need addressing:

  • ReadMe was still in processing parent directory (dap has now moved)
  • Logsheet was not copied into logsheet/ dir - have done so
  • navigation directory is empty. Find out if we deliver navigation files with a non-FW delivery and if so, create them
  • There are 3 DEMs in the dem directory. Should only be two - one in latlong and one in local coordinate system (bng) in this case
  • ReadMe says LAS1.0 when I think we use 1.2 now. Check your alspp cfg file to see what was used (also ask update the ReadME generator, or ask someone else to do it)
  • It's strange that there is a little line all by itself in the SW. Might be worth checking with ops that this is actually part of this collection
  • ascii lidar data does not have CRLF terminators. Check with mark1 if they need to have them. If not, then please update wiki instructions with this exception
  • There's a tif in the screenshots. Should that be here? Please edit relevant script appropriately if not.

comment:23 Changed 5 years ago by dap

Addressed the points mentioned by knpa and solved an issue where not all underscore characters were escaped in the .tex file.

Ready for delivery.

comment:24 Changed 5 years ago by tec

Finished and sent Fenix, LiDAR and RCD on Wednesday 06 of August

Sent to:
Prof. Tim Benton at
University of Leeds,
School of Biology,
Miall Building,
Leeds LS2 9JT

comment:25 Changed 4 years ago by tec

Archiving
Starting archiving

comment:26 Changed 4 years ago by tec

  • Description modified (diff)

Archiving
Done confirmed as of 13/05/2015 12:10

comment:27 Changed 4 years ago by mark1

Fenix
Fenix data needs reprocessing due to fault with sensor. Incorrect SWIR times recorded in raw files. Have changed tint2 value in hdr files from 14.4 to 2.15 as recommended by Specim. Data are also binned spectrally.

comment:28 Changed 4 years ago by mark1

Fenix

Data have been reprocessed.

comment:29 Changed 4 years ago by dac

Fenix

Reprocessed data delivered to Tim Benton on USB harddrive 31/07/2015

comment:30 Changed 3 years ago by dac

Fenix Delivery

Hard drive received back

Note: See TracTickets for help on using tickets.