Opened 14 years ago

Last modified 12 years ago

#344 assigned flight processing

GB08/19, 154b/2010, London night — at Version 10

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

Description (last modified by benj)

Data location: users/rsg/airborne/workspace/GB08_19-2010_154b_London_night

Data arrived from ARSF via network transfer on 08/06/2010.

Scientific objectives:
Classify urban landcover with ARSF remote senseing, remotely determine surface topography and surface temperature, which is then to be combined with meteorological data to model the urban energy balance (UEB).

Priority: a5

PI: M. J. Wooster

Sensors

LiDAR
Thermal

Change History (10)

comment:1 Changed 14 years ago by ella

Sensors
LiDAR
Eagle
Thermal

comment:2 Changed 14 years ago by benj

  • Description modified (diff)

comment:3 follow-up: Changed 14 years ago by ella

There is a gap in one of the flight lines.
Two basestations have been used and two sbets files generated (one for each basestation) because we could not minimise the combined seperation or get a green line for all flight lines.

comment:4 Changed 14 years ago by jb362

IPAS navigation processing complete.

comment:5 Changed 14 years ago by jb362

Applanix processing: 2 gaps in flight so we split it into 3 sections. The first 2 sections are fine but the last failed to produce an sbet file. Everything is in workspace though, including the semi-completed third section. Each section is in a seperate folder detailing the GPS start and end time for that section. Both IPAS and Applanix processing used network adjustment to obtain new basestation co-ordinates which helped minimise combined seperation error.

comment:6 in reply to: ↑ 3 ; follow-up: Changed 14 years ago by jb362

Replying to ella:

There is a gap in one of the flight lines.
Two basestations have been used and two sbets files generated (one for each basestation) because we could not minimise the combined seperation or get a green line for all flight lines.

This is for the Applanix processing. We have also since split the flight line into 3 sections each in their own folders which can be found alongside the two folders mentioned here, in the applanix directory. See comments below...

comment:7 in reply to: ↑ 6 Changed 14 years ago by jb362

Replying to jb362:

Replying to ella:

There is a gap in one of the flight lines.
Two basestations have been used and two sbets files generated (one for each basestation) because we could not minimise the combined seperation or get a green line for all flight lines.

This is for the Applanix processing. We have also since split the flight line into 3 sections each in their own folders which can be found alongside the two folders mentioned here, in the applanix directory. See comments above...

comment:8 Changed 14 years ago by jb362

At the time of unpacking there was no room in the arsf repository so this project has not yet been fast copied there.

comment:9 Changed 14 years ago by jb362

There was an eagle directory here but all files were for 154a London day and the directory has now been deleted. It looks as if there is only LiDAR data here.

comment:10 Changed 14 years ago by benj

  • Description modified (diff)

There is no Eagle or Hawk data recorded on the logsheet, the Eagle data was an unpacking error copying in some from 154a instead. This flight is LiDAR and TABI only.

Note: See TracTickets for help on using tickets.