Changes between Version 1 and Version 2 of Ticket #166


Ignore:
Timestamp:
Jun 13, 2008, 11:07:43 AM (16 years ago)
Author:
benj
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #166 – Description

    v1 v2  
    33We believe these are caused by the lidar being aimed down a steep slope flying one way and up it flying the other coupled to a slight boresight offset, causing a difference in exactly where it hits the slope in each case being calculated as the same location (hence why it only happens on steep slopes, and only on slopes that are either roughly parallel to or perpendicular to the plane, depending on which boresight angle is off).
    44
    5 Suggested solution is to average the lines using r.mapcalc in Grass prior to interpolation of null areas. If the slope is of a fairly constant gradient and the problem is caused by the above, this should hopefully produce reasonable results. Also asked Gabriel Amable at ULM for any suggestions. Given example data in ~arsf/support/20080813-JohnStevenson
     5Suggested solution is to average the lines using r.mapcalc in Grass prior to interpolation of null areas. If the slope is of a fairly constant gradient and the problem is caused by the above, this should hopefully produce reasonable results. Also asked Gabriel Amable at ULM for any suggestions. Given example data in ~arsf/support/20080813-!JohnStevenson
    66
    77Original email as below: