This article provides a comparison of fixed wing “flying wings” versus gliders as mapping platflorms. Read more...

As we outlined in a previous “LP360 – Under the Hood”, we have added volumetric analysis to LP360. This feature was first released with 2013.2 at the end of last year with an enhanced version in our recent Experimental (EXP) release. An important element of the analysis associated with volumes is the generation of cross-sections. Read more...

This is the third installment in our series on the new Point Cloud Task (PCT) mechanisms introduced in LP360 version 2013.2 released in December of 2013. We have previously discussed the new Input/Output Manager (IOM) and the Conflate tool. We now will cover the Volumetric Analysis tools. Read more...

This article discusses LIDAR datasets that are freely available from multiple providers and using them as a source for working with LIDAR data in LP360. Read more...

This article was written by a recent student at Penn State who completed Penn State's online LIDAR training program using LP360. This paper takes a look at flooding in the Fox River Valley and its impact on housing using LIDAR and related technology. Read more...

In the last edition of LP360 News, we discussed the creation of 3D breaklines for enforcing situations where the elevation must be a constant along the breakline. In this final installment of the breakline series, we will consider the case of varying elevation along the breakline. Read more...

In the last edition of LP360 News, we discussed the creation of 3D breaklines. Recall that, for our purposes, a 3D breakline is a vector that has an elevation value (Z) associated with each vertex. In this edition, let’s look at a constant Z example such as a flat water body. Read more...

As we have discussed in the last two issues of LP360 News, breaklines are two- or three-dimensional graphic data (points, lines, polygons) that we introduce into an elevation model to alter the topology. Surveyed mass points, scanned contour lines, correlated stereo models, and myriad other sources produce irregular elevation data that can be modeled as a TIN, and tools (such as LP360) that can manipulate random points are generally adept at processing these various data sources. Read more...

One of the more powerful capabilities within LP360 is breakline capture and enforcement. Find out what breaklines are and how they should be used here. Read more...

In the previous issue of LP360 News, I introduced the use of Triangulated Irregular Networks (TIN) for modeling point derived elevation data as well as the basic concepts of “soft” breaklines. I realized when writing that first article that it is probably a useful exercise to review contours. Thus this part II article will be devoted to this subject and we will continue with breaklines in the third article of the series. Read more...

LIDAR data included as a standard layer in your ArcGIS® project (using LP360 for ArcGIS®, of course) can prove very useful, simply for dynamic visualization. Read more...

As with any data, breaklines should undergo a QA/QC process. For breaklines this should entail a check for potential topology errors as well as incorrect elevation values. Read more...

Learn how to use the GeoCue workflow management framework to manage LAS files in TerraScan. Read more...

Much LIDAR data has been delivered in text format (American Standard Code for Information Interchange, ASCII) rather than the rich binary LAS format. In this article we examine the value of ASCII LIDAR data. Read more...

This article will provide an overview of the LAS format, which is a public file format for the interchange of 3D point cloud data between data users. Read more...

This technical note provides recommended flight planning procedures and suggestions for contractual data deliverables for organizations that are subcontracting field data collection for a LIDAR project to a service provider. Read more...