Changes between Version 2 and Version 3 of Procedures/AlsprocProcessing


Ignore:
Timestamp:
Aug 13, 2013 4:59:04 PM (6 years ago)
Author:
besm
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/AlsprocProcessing

    v2 v3  
    3636* '''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
    38 * '''sol-file''' - change this to the location of the sol file created during navigation processing
     38* '''sol-file''' - change this to the location of the sol file created during navigation processing, it may already be filled in for you
    3939* '''sup-file''' - as with the sol file
    4040
    41 PROJECTIONS TABLE GOES HERE
     41|| '''Projection''' || '''Use-Case''' || '''proj.4 string''' ||
     42|| 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 ||
     43|| UTM || everywhere else || +proj=utm +zone='''<zone number>*''' +ellps=WGS84 +datum=WGS84 ||
     44
     45* UTM zones need to be selected appropriately, a map of UTM zones can be found here: [http://www.dmap.co.uk/utmworld.htm]
    4246
    4347You 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.
    4448{{{
    4549[110618_090736]
    46 output-file = %(output_dir)s/ldr110618_090736.las
     50output-file = %(output_dir)s/ldr110618_090736%(output-file-ext)s
    4751process_line = true
     52line_number = 1
    4853
    4954# GMT 09:07:52 to 09:08:39, 47.3 seconds
     
    6065Alsproc is fed its arguments with the wrapper script alsproc_batch.py, which also handles certain LiDAR preformatting if using las12_las.
    6166{{{
    62 alsproc_batch.py processing/als50/2013121.cfg
     67alsproc processing/als50/2013121.cfg
    6368}}}
    6469
     
    100105{{{
    101106output-projection = +init=epsg:27700 +nadgrids=/users/rsg/arsf/usr/share/proj/OSTN02_NTv2.gsb +geoidgrids=/users/rsg/arsf/usr/share/proj/osgm02_wgs.gtx
    102 sol-file = %(ipas_dir)s/20130524_103914.sol
    103 sup-file = %(ipas_dir)s/20130524_103914.sup
     107sol-file = %(project_dir)s/posatt/ipas_honeywell/proc/20130524_103914.sol
     108sup-file = %(project_dir)s/posatt/ipas_honeywell/proc/20130524_103914.sup
    104109}}}
    105110
     
    110115
    111116
    112 Then process the dataset.
     117Then 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.
    113118
    114119{{{
     
    117122
    118123
    119 <how to prh correct>
     124<TO BE CONTINUED>