Changes between Version 1 and Version 2 of Procedures/AlsprocProcessing

Timestamp:

Aug 13, 2013, 12:27:43 PM (11 years ago)

Author:

besm

Comment:

--

Procedures/AlsprocProcessing

@@ -2 +2 @@
 The 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.
 {{{
-generate_alsproc_config.py
+generate_alsproc_config
 }}}
 
 Example:
 {{{
-airborne@pmpc1322:/users/rsg/arsf/arsf_data/2013/flight_data/uk/RG12_09-2013_121_Wessex# ~besm/local/alsproc/scripts/generate_alsproc_config.py 
+airborne@pmpc1322:/users/rsg/arsf/arsf_data/2013/flight_data/uk/RG12_09-2013_121_Wessex# generate_alsproc_config
 Gathering details about project...
 Using calibration file (/users/rsg/arsf/calibration/lidar/20130219/als50.cfg)...
@@ -34 +34 @@
 Fields of particular interest to you as a data processor are:
 * output-format - can normally be left as the default
-* '''projection''' - will need to be set per-flight depending on where the flight is based (TODO: VERIFY)
+* '''output-projection''' - will need to be set per-flight depending on where the flight is based, consult the projections table below
 * output_dir - default is probably fine, but it can be useful to change, especially when working on the pitch and roll values later
 * '''sol-file''' - change this to the location of the sol file created during navigation processing
 * '''sup-file''' - as with the sol file
+
+PROJECTIONS TABLE GOES HERE
 
 You 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.
@@ -64 +66 @@
 
 == Pitch and Roll Errors ==
+First you will need to generate an initial dataset to base some observations off
+
+{{{
+airborne@pmpc1322:/users/rsg/arsf/arsf_data/2013/flight_data/uk/GB13_05-2013_144_Glenmore/processing/als50# generate_alsproc_config 
+Gathering details about project...
+Using calibration file (/users/rsg/arsf/calibration/lidar/20130219/als50.cfg)...
+Collating details for .cfg file...
+Writing .cfg file
+Scanning flightline 130524_130407... ok
+Scanning flightline 130524_130807... ok
+Scanning flightline 130524_131239... ok
+Scanning flightline 130524_131711... ok
+Scanning flightline 130524_132140... ok
+Scanning flightline 130524_132606... ok
+Scanning flightline 130524_133035... ok
+Scanning flightline 130524_133540... ok
+Scanning flightline 130524_134001... ok
+Scanning flightline 130524_134447... ok
+Scanning flightline 130524_134927... ok
+Scanning flightline 130524_135443... ok
+Scanning flightline 130524_135900... ok
+Scanning flightline 130524_140340... ok
+Scanning flightline 130524_140918... ok
+Scanning flightline 130524_141340... ok
+Scanning flightline 130524_141645... ok
+Scanning flightline 130524_142158... ok
+Scanning flightline 130524_142738... ok
+all done
+}}}
+
+Then edit the resulting .cfg file and set the appropriate fields. Example:
+
+{{{
+output-projection = +init=epsg:27700 +nadgrids=/users/rsg/arsf/usr/share/proj/OSTN02_NTv2.gsb +geoidgrids=/users/rsg/arsf/usr/share/proj/osgm02_wgs.gtx
+sol-file = %(ipas_dir)s/20130524_103914.sol
+sup-file = %(ipas_dir)s/20130524_103914.sup
+}}}
+
+output-projection is set according to global position. This is a UK flight so I have selected the British National Grid.
+
+
+sol-file and sup-file have been set according to what was created during the navigation processing.
+
+
+Then process the dataset.
+
+{{{
+alsproc 2013144.cfg
+}}}
+
+
 <how to prh correct>