GeoCue Support has written 723 articles

LP360 Command Line Executables

LP360 has several command line executable style programs that assist with productivity for different tasks, particularly when working with large amounts of data or repeating processes. These executables may be run: Via an MS-DOS style batch scripts By configuring corresponding commands and checklist steps within the GeoCue workflow software to take advantage of the command…

Share

Could not probe surface

Problem: User encounters the message, “Could not probe surface. Verify coverage and that surface is not in use.” in the system messages column of the Checklist Step Details pane when attempting to run the Probe checklist step on a Photogrammetric_Point entity in GeoCue. Probable Resolution#1: Verify the layer being probed is not currently locked in…

Share

LP360 Startup Stuck on Processing Shell Command

Problem: When attempting to start LP360 it gets stuck on the splash screen and there is a small message at the bottom of the splash screen that says, “Processing shell command”. Probable Resolution: This is a known problem in Windows 10 that has since been fixed by Microsoft in an update to Windows 10. Please…

Share

LP360 2018.2 Feature Matrix

LP360 – This is the native 64 bit Windows version of LP360. It has no software prerequisites other than Windows.  It executes on Windows x64, Version 7 and later. LP360 for ArcGIS® – A fully qualified extension for ArcMap® desktop. LP360 for ArcGIS® requires the Basic level of ArcMap.  This remains a 32 bit product…

Share

Error 1001: LP360CustomActions.InstallState

Problem: User encounters error message, “Error 1001. Could not find file ‘C:\Program Files (x86)\Common Files\LP360\LP360CustomActions.InstallState.” or “Error 1001. Could not find file ‘C:\Program Files\Common Files\LP360\LP360CustomActions.InstallState.”, while attempting to install LP360 v2018.1 or later. Probable Resolution: Uninstall all instances of LP360 from the machine, then attempt to install the latest version of LP360.

Share

When would one use Out Areas in Breakline Enforcement?

Out areas are used to create void areas in the TIN, resulting in No Data values in the exported DEM raster. One may wish to do this for: Waterbodies Perhaps for sensitive areas To not generate contours in the interior of buildings If the project area is a corridor or oddly shaped, then one can…

Share

Breaklines in LP360- Part 5

In the last section, we discussed the creation of 3D breaklines for enforcing situations where the elevation must be a constant along the breakline. The most common example of this application is “water body flattening” such as lakes and ponds. In this final section we will consider the case of varying elevation along the breakline.…

Share

Breaklines in LP360- Part 4

This is the fourth edition of our series on breaklines in LP360. In this edition, we will have a look at how features are represented in LP360 as well as the tools available for collecting “flat” breaklines. Features: Features in LP360 are internally stored as files in Shape format. This is a binary standard developed…

Share

Slow Responsiveness of GeoCue Client

Problem: Slow responsiveness of the GeoCue Client is observed corresponding with high CPU usage by the RepHostGUI.exe on the GeoCue Server machine. Probable Resolution: RepHostGUI.exe is the primary GeoCue server process, which handles all interaction with all GeoCue clients and the database. Since this executable implements multithreaded processing and handles all the necessary locks it…

Share

Error 6: EPSG PCS/GCS code not found in EPSG Support Files

Symptom: While running the Point Cloud Statistics Extractor Point Cloud Task it returns “Error 6: EPSG PCS/GCS code 37518 not found in EPSG Support Files. Is this a valid EPSG coordinate system?“. The error message indicates that one or more input LAS files has been assigned an EPSG code that is not a valid code.…

Share