Changes between Version 2 and Version 3 of Procedures/AlsprocProcessing

Timestamp:

Aug 13, 2013, 4:59:04 PM (11 years ago)

Author:

besm

Comment:

--

Procedures/AlsprocProcessing

@@ -36 +36 @@
 * '''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
+* '''sol-file''' - change this to the location of the sol file created during navigation processing, it may already be filled in for you
 * '''sup-file''' - as with the sol file
 
-PROJECTIONS TABLE GOES HERE
+|| '''Projection''' || '''Use-Case''' || '''proj.4 string''' ||
+|| British National Grid || all British flights || +init=epsg:27700 +nadgrids=/users/rsg/arsf/usr/share/proj/OSTN02_NTv2.gsb +geoidgrids=/users/rsg/arsf/usr/share/proj/osgm02_wgs.gtx ||
+|| UTM || everywhere else || +proj=utm +zone='''<zone number>*''' +ellps=WGS84 +datum=WGS84 ||
+
+* UTM zones need to be selected appropriately, a map of UTM zones can be found here: [http://www.dmap.co.uk/utmworld.htm]
 
 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.
 {{{
 [110618_090736]
-output-file = %(output_dir)s/ldr110618_090736.las
+output-file = %(output_dir)s/ldr110618_090736%(output-file-ext)s
 process_line = true
+line_number = 1
 
 # GMT 09:07:52 to 09:08:39, 47.3 seconds
@@ -60 +65 @@
 Alsproc is fed its arguments with the wrapper script alsproc_batch.py, which also handles certain LiDAR preformatting if using las12_las.
 {{{
-alsproc_batch.py processing/als50/2013121.cfg
+alsproc processing/als50/2013121.cfg
 }}}
 
@@ -100 +105 @@
 {{{
 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
+sol-file = %(project_dir)s/posatt/ipas_honeywell/proc/20130524_103914.sol
+sup-file = %(project_dir)s/posatt/ipas_honeywell/proc/20130524_103914.sup
 }}}
 
@@ -110 +115 @@
 
 
-Then process the dataset.
+Then process the dataset. This can take a while; 20 minutes to 20 hours depending on the size of the dataset and load on the network. On early iterations, you may identify just a few flightlines and focus your efforts on those, but you '''must''' check flightlines from across the entire dataset, as pitch and roll has been known to change over the course of a flight in the most unfortunate cases.
 
 {{{
@@ -117 +122 @@
 
 
-<how to prh correct>
+<TO BE CONTINUED>