226 articles LP360 Tools, Tips and Workflows

Information regarding the tools available in LP360.

Breaklines in LP360- Part 3

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…

Share

Modifying VERT_CS WKT for USGS

A recent USGS addendum to the LIDAR Base Specification has stated that “User-defined entities will not be allowed for capturing specific geoid information in the WKT”. LP360 (v2015.1.76.15 or later) In order to remove this information from the VERT_CS WKT being included in LP360 generated WKTs it is necessary to replace the following file(s): “C:\Program…

Share

Importing Control/Check Points into LP360

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…

Share

Breaklines in LP360- Part 2

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…

Share

LP360 Error: Getting x coordinate failed (16881)

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 […

Share

Breaklines in LP360 – Part I

Prolog: I am writing a new whitepaper on model constraints in LP360 (any reference to LP360 where I do not add the term “for ArcGIS,” I am talking about the standalone version. This document is extracted and heavily revised from a series of articles that I wrote for the GeoCue Group Newsletter in 2013. The…

Share

Reproject Raster in LP360

LP360 has a Point Cloud Task (PCT) that can reproject raster layers, create pyramids, and JPEG compress.  The PCT is named Reproject Raster.  When we reproject an existing orthophoto to a new coordinate system, or re-write to a different unit, the user can choose to output uncompressed, or JPEG compressed. If JPEG compression is selected, the user…

Share

Errors in Surface Generation

Problem: There are some situations that can cause there to be a mismatch between surface elevations between tiles.  This can become apparent in the vicinity of waterbody breaklines where a tile covers the water but only overlaps with a single shoreline. In this scenario, the surface generation process cannot consider the influence of breaklines on…

Share

Putting LIDAR data on a single layer

When data is originally added to LP360 the selected files will be grouped into layers, depending upon certain criteria so that only compatible LAS files will be on a single LAS layer. When adding new data to the layout, if all the data meets the compatible rules, then checking the option to “Append to Compatible Layers”…

Share

Unexpected error in ILPBrkLineEnforcer:GetLayerName(). (17486)

Problem: While attempting to execute a conflate point cloud task the user receives an “Executing task(s) failed. (8690) Unexpected error in ILPBrkLineEnforcer:GetLayerName(). (17486)” COM Exception. Probable Resolution: The root cause of this error tends to be that one of the layers listed in the breakline enforcement is not valid. Either the file no longer exists…

Share