LiDAR Calibration Notes - Known Software issues

Attune

  • AutoBoreSight.exe error -"Boresight programme could not be found"
    • Resolution: Check projection is correct (UTM or OSGB)
      • Note: sometimes this doesn't fully resolve the issue, in which case currently no (good) solution has been found.
        • One solution that has worked previously is to keep open the tie point editor and then (without closing attune) create a new project, repeat the process of loading in the lines and swapping them from the ground classified images then solve calibration parameters again.
  • Further details (Calibration 2013)
    • Autoboresight.exe is a program running within Attune. When autoboresight.exe crashes it doesn't necessarily crash Attune. In this case usually just autoboresight.exe crashed
      and therefore wasn't creating an output. On the one occasion that autoboresight.exe was consistently working and a reasonable number of tie points were collected Attune
      itself crashed. When the attune project was reloaded and autoboresight.exe was run again it would crash but attune would stay open.

If attune throws an error saying that AutoBoresight.exe couldn't be found/won't work try running attune from the program files folder rather than a shortcut (C:/Program Files/Leica Geosystems/Attune/Attune.exe)

Autoboresight begins to fail at reducing tie points sometimes, this appears to be at random. It's likely that attune will not be able to find any of the tie points you have made if this happens. The only fix seems to be to create a new project, add all your lines again (as the same line number/name!) then rename the old tie points file to the new project name convention and re-run. This does not work every time.

lasground / ground_classify_las_bin.sh

  • Failing on a section of line
    • Resolution: Use a different line or manually classify that line.

ALSPP

  • RangeCardCal Error
    • Resolution: RangeCardCal File missing from "Sent to" (C:\Documents and Settings\*user*\SendTo) folder, this file can be copied and pasted from another person's SendTo folder.
      • Alternatively use a different user's account that has already been set up.

  • Pulse Rate error when loading in raw LiDAR data - Doesn't appear to change the result, currently no solution
  • Compute Scanner Offsets
    • For some reason this appears not to work on the windows version of ALSPP however it does run through Wine

We are investigating the issues related to the software errors and have contacted the manufacturer

http://arsf-dan.nerc.ac.uk/trac/ticket/473 (Calibration Ticket)

http://arsf-dan.nerc.ac.uk/trac/ticket/474 (Leica e-mails)

Back to LiDAR Calibration Page here

Last modified 5 years ago Last modified on Sep 5, 2014 10:24:05 AM