Transcript Introduction   ARSF processing  Objectives and what we deal with  Brief description of processing flow  Accuracy and error User processing  Prerequisites  Common problems  Sample run.

Introduction


ARSF processing

Objectives and what we deal with

Brief description of processing flow

Accuracy and error
User processing

Prerequisites

Common problems

Sample run
What we do


Objectives

Processing

User support and training

Improved communication (wiki, ticketing, etc)
What we deal with:


Specim (Eagle & Hawk), CASI, ATM
Use: LiDAR, NextMap, vectors
ATM
CASI
Eagle
Hawk
All sensors
Components of processing

(data acquisition)

Processing and integration of navigation

Correction of timing issues

Boresight calibration

Radiometric calibration

Processing to level 1 (handling any errors on the way)

Accuracy measurement / quality control

Documentation and delivery

User support
Level 1 data
Level 3 data
Accuracy

How we check (multiple vector measurements)

Expected accuracy


Boresight error <5m

Some scenes 25m

Error varies across scene
Typically correctable by manual adjustment
Sources of error

GPS (~5cm) and IMU error

DEM inaccuracies (?)


5m pixels for NextMap, ~1m pixels for ULM LiDAR
Instrument calibration

Internal (?)

Boresight (<5m)

Vector overlay errors (?)

Other: e.g. coordinate conversions
User processing

Why deliver level 1 data rather than level 3?

What the user needs to do:

Acquire DEM

Choose datum and projection, making appropriate
conversions

Level 1 operations (e.g. atmospheric correction)

Process to level 3 with azgcorr & azexhdf

Make georeferencing adjustments as necessary
Using azgcorr

Machine running Linux operating system

Understand concepts

Read the manual

“azgcorr -help” for exact usage

Sample commands supplied with data

Any problems or questions? Ask us!

[email protected]
Sample azgcorr command

./bin/azgcorr.484

Executable name

-v

Verbose mode (more output)

-1 ./lev1/a16601b.hdf

Name of level 1 data file

-3 ./lev3/a16603b.hdf

Name of level 3 output file

-bl 5 3 2 -1

Band listing (bands 5,3,2)

-p 1 1

Pixel size (1m x 1m)

-mUK99 misc/osgb02.cgrf

Projection (UK)

-eh ./dem/flatfile.dem

Name of DEM file
Common processing problems


Geocorrection: various distortions (roll, pitch,
yaw, height, time*)
DEM (lack of, and incomplete – interpolate)


Creation from LiDAR or NextMap
Pixel size / interpolation
No DEM
With DEM
DEM & no-DEM overlaid
Incomplete DEM coverage
Timing errors

Should be corrected in delivered data
Pixel size/interpolation
Geocorrection: pitch
Geocorrection: roll
Geocorrection: heading/yaw
Sample run and questions

Laptop(s) with azgcorr, tools and sample data

azgcorr simple run


With/without DEM

Pitch, roll, heading adjustments
Questions?

Complex ones to [email protected] !