GeoCue Support » Archives for GeoCue Support » Page 28
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…
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…
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…
The following is a brief explanation for how to set filters for classification flags in LP360. The Live View Filter allows the user to set flags for: single class, multiple classes, single flag, or multiple flag combination scenarios. For this example, we will review setting the Live View filter for displaying these flags. The same…
Canopy Height Model (CHM) is important for a variety of uses. The distinguishing factor of this model is that it is a height above ground model and does not represent absolute elevation. We can produce this model in LP360 with the following workflow that incorporates Point Cloud Tasks (PCTs) and the export function. Note: the…
GeoCue Client encounters the error message, “Unable to contact the specified repository server (Server name and IP address). A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond IP address.” The GeoCue server is not running. There are…
In Feature Analyst, the Flat Feature analysis function allows the user to test that the delta Z (MaxZ – MinZ) for all vertices of a feature is less than the specified Z tolerance range. By default the value is 0, but the user can specify the tolerance value when activating this function in the Feature…
On occasion, users may experience issues with GeoCue running properly or being unable to complete certain processes. The GeoCue Server has robust event logging to help troubleshoot these problems. The normal event log entries section demonstrates the expected messaging during the normal GeoCue Server startup sequence. Below that are listed common GeoCue Server Event Log…
Attempting to Create Trajectories in GeoCue results in the error message, “No matching Sensor Trajectory found”. The LIDAR_Source entity displays red and the “Create TerraScan Trajectory” checklist step icon displays red, showing that the last run of the step failed. The error message can be found in the Checklist Step Details on the History tab…
The user in unable to edit LAS points in LP360 or True View EVO and receives the following error message: “Filters require editable points. Open the LAS files for read/write and try again.” Note: Read/write functionality applies to all True View Evo users. Also, applicable to all Standard and above LP360 license level users. For…