GeoCue Support has written 723 articles

Error 401 during GeoCue Installation

GeoCue installation reports the error. “String variable is not large enough for string. Check the string declarations. Error 401.“ This is caused by path environment variable being too long (over 1024 characters). This can be resolved by changing/altering the path. The user can see/set it by typing path at the command prompt or it may…

Share

LP360 for ArcGIS not showing in ArcMap Extensions

The LP360 for ArcGIS extension is not showing in the ArcMap Extensions list (ArcMap -> Customize -> Extensions). Since ArcMap is only a 32-bit application, to install LP360 for ArcMap requires using a separate installer than LP360. Ensure that you have run the applicable “LP360 for ArcGIS Installer (Includes LP360 32-bit Arc Extension Only)”, named…

Share

Timeout attempting to WRITE LOCK the layout

GeoCue user receives the follow error message: “Timeout attempting to WRITE LOCK the layout. Layout is currently WRITE LOCKED by (machine name).” This is observed on multiple machines opening specific projects. Open the specific projects that are currently locked out on the machine listed in the error message. This will allow other users to write…

Share

Calculate Average Stockpile Height

LP360 has many tools for analyzing stockpiles and terrain. With these tools, it is possible to calculate average stockpile height and quantify this on a pile by pile basis in an automated fashion. The Volumetric Analysis point cloud task (PCT) has the ability to calculate a height dataset when the base and hull is known.…

Share

Missing Geoid File for Source Vertical Coordinate System

Executing the Reproject LAS Point Cloud Task encounters the error, “Error setting up the transformation: Missing geoid file for source vertical coordinate system.” The spatial reference system (SRS) must be properly set on the LAS Layer as that is where the Reproject PCT will be looking for the information. For example, if the original LAS…

Share

How to Thin the Dataset

A common issue that is encountered when trying to take a bare earth surface generated from LIDAR or photogrammetric point cloud datasets into other programs is that those other programs cannot handle the volume of data. LP360 currently provides four options that can be used to thin the bare earth dataset to allow you to…

Share

Trajectory File Time Range Warning

Starting the Create True View Trajectory process results in a Trajectory File Time Range Warning, “Warning: The Post Process Trajectory File start time was AFTER the start time of the first flight line. Geocoded LIDAR may not cover all of your flight lines. Continue and create all possible Trajectory Files?” This check was put in…

Share

POSITION_FILE_PARSE_FAILED

Attempting to run POSPacCloud to process the trajectory solution for a TrueView 3DIS results in an error message stating, “POSITION_FILE_PARSE_FAILED”. Verify the project path contains no special characters as the Applanix POSPacCloud utility cannot handle them. If you do have special characters, close TrueView EVO, take the special characters out of the path, then re-open…

Share

Advertised Application Error During Install

Attempting to run the LP360 installer through Microsoft Endpoint Configuration Manager, formerly System Center Configuration Manager and Systems Management Server (SCCM) results in an error, “This advertised application will not be installed because it might be unsafe. Contact your administrator to change the installation user interface option of the package to basic.” LP360 requires the…

Share

Using Classification Flags in LP360

The classification of a LIDAR data point consists of both a classification and a classification flag. The classification flag allows for a point to be simultaneously flagged for particular uses while maintaining the classification of the point. For example, a model key-point can be flagged as such while maintaining the ground classification. Classification flags are…

Share