Changes between Version 1 and Version 2 of Procedures/AlsprocProcessing


Ignore:
Timestamp:
Aug 13, 2013 12:27:43 PM (6 years ago)
Author:
besm
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/AlsprocProcessing

    v1 v2  
    22The configuration file is made with the generate_alsproc_config.py program. It will examine your current working directory and derive a project directory, from which it will determine the best available calibration to base your configuration file on, and populate it with information derived from your flightlines. This can take a while, as it needs to perform a cursory check on all of the raw data.
    33{{{
    4 generate_alsproc_config.py
     4generate_alsproc_config
    55}}}
    66
    77Example:
    88{{{
    9 airborne@pmpc1322:/users/rsg/arsf/arsf_data/2013/flight_data/uk/RG12_09-2013_121_Wessex# ~besm/local/alsproc/scripts/generate_alsproc_config.py
     9airborne@pmpc1322:/users/rsg/arsf/arsf_data/2013/flight_data/uk/RG12_09-2013_121_Wessex# generate_alsproc_config
    1010Gathering details about project...
    1111Using calibration file (/users/rsg/arsf/calibration/lidar/20130219/als50.cfg)...
     
    3434Fields of particular interest to you as a data processor are:
    3535* output-format - can normally be left as the default
    36 * '''projection''' - will need to be set per-flight depending on where the flight is based (TODO: VERIFY)
     36* '''output-projection''' - will need to be set per-flight depending on where the flight is based, consult the projections table below
    3737* output_dir - default is probably fine, but it can be useful to change, especially when working on the pitch and roll values later
    3838* '''sol-file''' - change this to the location of the sol file created during navigation processing
    3939* '''sup-file''' - as with the sol file
     40
     41PROJECTIONS TABLE GOES HERE
    4042
    4143You will then see a section for each flightline. process_line should be set to true for each flightline unless there was some problem, in which case the maintainer for alsproc should be contacted.
     
    6466
    6567== Pitch and Roll Errors ==
     68First you will need to generate an initial dataset to base some observations off
     69
     70{{{
     71airborne@pmpc1322:/users/rsg/arsf/arsf_data/2013/flight_data/uk/GB13_05-2013_144_Glenmore/processing/als50# generate_alsproc_config
     72Gathering details about project...
     73Using calibration file (/users/rsg/arsf/calibration/lidar/20130219/als50.cfg)...
     74Collating details for .cfg file...
     75Writing .cfg file
     76Scanning flightline 130524_130407... ok
     77Scanning flightline 130524_130807... ok
     78Scanning flightline 130524_131239... ok
     79Scanning flightline 130524_131711... ok
     80Scanning flightline 130524_132140... ok
     81Scanning flightline 130524_132606... ok
     82Scanning flightline 130524_133035... ok
     83Scanning flightline 130524_133540... ok
     84Scanning flightline 130524_134001... ok
     85Scanning flightline 130524_134447... ok
     86Scanning flightline 130524_134927... ok
     87Scanning flightline 130524_135443... ok
     88Scanning flightline 130524_135900... ok
     89Scanning flightline 130524_140340... ok
     90Scanning flightline 130524_140918... ok
     91Scanning flightline 130524_141340... ok
     92Scanning flightline 130524_141645... ok
     93Scanning flightline 130524_142158... ok
     94Scanning flightline 130524_142738... ok
     95all done
     96}}}
     97
     98Then edit the resulting .cfg file and set the appropriate fields. Example:
     99
     100{{{
     101output-projection = +init=epsg:27700 +nadgrids=/users/rsg/arsf/usr/share/proj/OSTN02_NTv2.gsb +geoidgrids=/users/rsg/arsf/usr/share/proj/osgm02_wgs.gtx
     102sol-file = %(ipas_dir)s/20130524_103914.sol
     103sup-file = %(ipas_dir)s/20130524_103914.sup
     104}}}
     105
     106output-projection is set according to global position. This is a UK flight so I have selected the British National Grid.
     107
     108
     109sol-file and sup-file have been set according to what was created during the navigation processing.
     110
     111
     112Then process the dataset.
     113
     114{{{
     115alsproc 2013144.cfg
     116}}}
     117
     118
    66119<how to prh correct>