I am writing a new whitepaper on model constraints in LP360, which is our advanced LIDAR and point cloud processing software (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 big change is that, at that time, we only had enforcement in the standalone version of LP360. Even in LP360 for ArcGIS, one had to use a number of ArcGIS tools to fully edit a breakline model. Now, we are essentially feature-complete with new tools in standalone LP360. Not only are all of the breakline creation tools present, but we also have a very rich set of 3D feature edit tools. Finally, you can do very high-performance 3D breakline creation and editing in a standalone Windows 64-bit application.
For the next perhaps 5 issues of GeoCue Group News, I will present these new tools. While this series is aimed squarely at our product, LP360, the information on constraining point cloud models is general to any software implementation. Even if you are not a user of our LP360 software, you will still gain a pretty good understanding of how breaklines are used to modify three-dimensional (3D) model data.
One of the more powerful capabilities within LP360 is breakline capture and enforcement. In fact, many LIDAR production shops use LP360 as their tool of choice for supplementing point cloud data derived from LIDAR or correlated imagery (so-called Structure from Motion, SfM, Dense Image Matching, DIM, Semi-Global Matching, SGM and a few other monikers) with breaklines. But what are breaklines and how should they be used? In this paper, I will be providing some background information on elevation modeling and then delve in to how these advanced features are implemented in our LP360 (native 64-bit Windows version) tools.