Changes between Version 45 and Version 46 of Processing/Lidarqcprocedure


Ignore:
Timestamp:
May 20, 2010 12:38:59 PM (10 years ago)
Author:
knpa
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Processing/Lidarqcprocedure

    v45 v46  
    44
    55=== Check overlap of neighbouring lines ===
     6
     7==== Horizontal ====
     8The first thing to do here is to load up all lines into a viewer (or if runs out of memory load them up in pairs) and see how well they overlap in the horizontal plane. The Fugro viewer is probably best for this because it also allows Shapefiles to be read in (though you can also just use Terrascan with "Colour by intensity").
     9Check along features that cross between flight lines, for example, roads/field boundaries/hedgerows do they continue unbroken or are they offset between flight lines. Also, compare against the vectors (if available) for any gross offsets.
    610
    711==== Vertical ====
     
    1317
    1418If the elevations are offset consistently between flight lines then this probably means an error with the calibration values (boresight or range correction). This should be corrected using the settings in alspp. If the offsets are random per flight line then the average offset per flight line should be noted but not corrected for (unless ground control points are available).
    15 
    16 
    17 ==== Horizontal ====
    18 The first thing to do here is to load up all lines into a viewer (or if runs out of memory load them up in pairs) and see how well they overlap in the horizontal plane. The Fugro viewer is probably best for this because it also allows Shapefiles to be read in (though you can also just use Terrascan with "Colour by intensity").
    19 Check along features that cross between flight lines, for example, roads/field boundaries/hedgerows do they continue unbroken or are they offset between flight lines. Also, compare against the vectors (if available) for any gross offsets.
    2019
    2120