Troubleshooting Geocoding Issues

📌 Problem

After geocoding the point cloud, there were fewer points geocoded than expected. 

🔍 Root Cause

Possible causes for having significantly fewer points geocoded in LP360 then expected include:

• Unique Point Source IDs
• Clip Angle and Clip Range Settings
• True Track Disabled
• Noise Filter Settings
• RiUNITE Processing
• Display Filtering
• Sensor Trajectory
• Geocoding Errors

✅ Probable Resolutions

1. Check point source ID assignment for uniqueness.

   If unique point source IDs are not properly assigned for each flight line, it can cause issues with point identification and geocoding. Ensure each line has a unique starting ID, especially in multi-Cycle projects.

2. Review clip angle and range settings.

   Incorrect settings may exclude points from the geocoding process. Verify that these are set to include all relevant points.

3. Ensure True Track is enabled.

   If True Track is not enabled, the software may not compensate for aircraft roll, leading to misaligned or missing points.

4. Adjust noise filter settings as needed.

   For Riegl sensors, the noise filter is enabled by default. If set incorrectly, valid points may be filtered out, or too much noise may be included.

5. Use RiUNITE processing if applicable.

   For TrueView680 or TrueView720 Riegl laser scanner data, ensure the Riegl RiUNITE utility is used if required.

6. Check display settings to ensure no filters are applied.

   • Open the Live View dialog.
   • Review the display filter tabs; if a filter is active, the Filter on Indicator in the tab will display with a yellow filter icon .
   • Confirm that none of the display filter tabs show the yellow filter icon .
   • If filters are applied, turn off the Filter Selector on the Tabs.

7. Review the Sensor Trajectory Processing logs and reports.

   • In the Job Manager , select the applicable PPT job(s) and press View Log to review for any issues.
   • Review the applicable Sensor Trajectory Processing Report for your sensor model to ensure a valid and complete solution was obtained:
     • Trajectory Report Review for TrueView 3DIS (Applanix)
     • Trajectory Report Review for TrueView 3DIS (CHCNav)
     • Trajectory Plot Review for TrueView 3DIS (TruNav)
   • Incomplete or low quality sensor trajectory solutions can cause geocoding errors or omissions.

8. Review the Geocoding logs.

   1. Review the Sensor Processing (TVSP) or Sensor Processing Extension (SPX) job log, as applicable, for any warnings or errors by selecting the job in Job Manager , then press View Log.

   2. For TVSP jobs, also review the geocoding.log for any warnings or errors by selecting the job in Job Manager , then press File Explorer and navigating to the LAS folder.

      Troubleshooting: Geocoding Warning: “Could Not Be Matched” for One or More Flight Lines – LP360

   3. For SPX jobs, select the job in Job Manager , then press File Explorer to open the job folder and review the additional logs in the folder for any warnings or errors.

By systematically checking these areas and ensuring all users follow the same workflow, you can identify and resolve discrepancies in geocoded point counts.

📬 Need Help?

If you're still stuck, please Contact Support for assistance.