GeoCue’s repository of articles covering tools, tips, and workflows for processing point clouds in LP360 Geospatial.
Problem: When attempting to start LP360 it gets stuck on the splash screen and there is a small message at the bottom of the splash screen that says, “Processing shell command”. Probable Resolution: This is a known problem in Windows 10 that has since been fixed by Microsoft in an update to Windows 10. Please…
In the last section, we discussed the creation of 3D breaklines for enforcing situations where the elevation must be a constant along the breakline. The most common example of this application is “water body flattening” such as lakes and ponds. In this final section we will consider the case of varying elevation along the breakline.…
This is the fourth edition of our series on breaklines in LP360. In this edition, we will have a look at how features are represented in LP360 as well as the tools available for collecting “flat” breaklines. Features: Features in LP360 are internally stored as files in Shape format. This is a binary standard developed…
Symptom: While running the Point Cloud Statistics Extractor Point Cloud Task it returns “Error 6: EPSG PCS/GCS code 37518 not found in EPSG Support Files. Is this a valid EPSG coordinate system?“. The error message indicates that one or more input LAS files has been assigned an EPSG code that is not a valid code.…
Problem: While trying to select a feature in LP360 using the Feature Edit tools a user receives an error message, “Error getting feature geometries (GetFeatureGeometries). Exception information: HRESULT: 0x80004005. Description: Unable to convert shape using ShapetoLPGeometry.” The message indicates that the type of feature being selected is not supported in that version of LP360. Probable…
Introduction to Part 3: In the last part of this series, we discussed in some detail how a Triangulated Irregular Network (TIN) can be constrained by features external to the point cloud model such as lines, points and polygons. In this month’s edition, we will look at contours and how LP360 can extract elevation information…
Platform: LP360 (Standalone) Minimum Licensing: Standard, sUAS Version: 2017.1 or higher Date: 15 September 2018 Introduction: This note describes importing control and/or check points in text format into LP360 for use in accuracy assessment. We distinguish these points as: Control Point – A point that was used in the modeling process. It generally should not…
This article is a continuation of the discussion of breaklines in LP360 (the standalone version). In last month’s installment, we discussed the overall concept of data modeling, especially the Triangulated Irregular Network (TIN). In this installment, I will discuss the general concept of adding constraints in the form of breaklines to these models. In future…
Problem: Getting the error, “Getting x coordinate failed. (16881)“, when attempting to open the control point table from the LP360 Control Points toolbar. [Window Title] LP360 Error [Main Instruction] Getting x coordinate failed. (16881) [Expanded Information] Exception Information: HRESULT: 0x80040202 Source: “esri.Point” Description: The operation was attempted on an empty geometry. [V] Expand this […
