Changes between Version 39 and Version 40 of Processing/Lidarqcprocedure


Ignore:
Timestamp:
Dec 22, 2009 3:58:22 PM (9 years ago)
Author:
knpa
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Processing/Lidarqcprocedure

    v39 v40  
    3434=== Check overlap of neighbouring lines ===
    3535
     36==== Horizontal ====
    3637The 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").
    3738Check 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.
    3839
     40==== Vertical ====
    3941The elevation between neighbouring flight lines must be checked too.  This can be done in various ways:
    4042 * examining profiles over the overlapping regions: allows measurements of the height difference to be made (in Terrascan/Microstation)
     
    4345  '''Make a note of the average elevation offsets between flight lines for use in the delivery read me file.'''
    4446
    45 If 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 (although you may have already corrected for roll to the best extent possible). 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).
     47If 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 (although you may have already corrected for roll previously). 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).
    4648
    4749