GeoCue Support » Archives for GeoCue Support » Page 63
Symptom: While attempting to complete the authorization of LP360 licenses using the downloaded AUT, you receive a message stating, “Invalid Machine Code (24237): Authorization file was not created for this machine. Unable to register…” Probable Resolution #1: Are you attempting to activate the LP360 license from the machine on which the AUT file was registered?…
These instructions are specific only to customers who are using the GeoCue software to run TerraSlave via a Run Macro step. Using Microstation set-up TerraScan with all the projection systems, input and output formats, transformations and any other settings that might be needed for any given project. This information is saved in the Terra Applications…
Almost always, the selection of a NAD83 based layer in older versions of GeoCue (pre v2011.1) NAD83 was used to refer to the then current NAD83 datum, for instance NAD83(CORS96) for most early LIDAR collections, and subsequently NAD83(NSRS2007). The current realization of NAD83 is NAD83(2011). All of these realizations are available for selection in GeoCue…
The recent service pack release of LP360 for ArcGIS, version 2014.1.51.1, now gives a Windows user with even just basic permissions the ability to change the LP360 license level if all licenses at the currently desired license level in the LP360 License Administrator are unavailable. Users of LP360 for Windows are currently able to run…
GeoCue’s Distributed Project Management System (DPMS) for GeoCue Project Portal is being used for the Florida Department of Emergency Management Coast Mapping Project (FDEM). The Master Project for FDEM is being maintained by URS Corporation using GeoCue Enterprise Server and GeoCue Project Portal. Project Portal is an enhanced version of GeoCue Web Server. The coordination…
This technical note provides instructions for configuring a GeoCue project to participate in the Florida Department of Emergency Management Coast Mapping Project (FDEM). The Master Project for FDEM will be maintained by URS Corporation using GeoCue Enterprise Server and GeoCue Project Portal. Project Portal is an enhanced version of GeoCue Web Server. Project updating and…
We added support for v1.4 of the ASPRS LAS data format to GeoCue v2014. If you are involved in LIDAR workflows in North America, you will immediately understand the value of supporting LAS Version v1.4, Point Data Record Formats (PDRFs) 6 through 8. These are the required deliverable formats for the United States Geological Survey…
Datums identified only as NAD 83 or WGS 84 are not specific enough to clearly define the reference frame of geodetic data. Additional information is needed that defines the realization or version of a particular datum. In the case of NAD 83, a “datum tag” must be appended to the name, such as NAD 83…
The GeoCue software suite uses local data repositories or ‘warehouses’ to store all geospatial data for a project. A warehouse is essentially a shared network storage location accessible to all users. Warehouse locations are set-up and managed by the GeoCue Administrator using the ‘Database Manager’ tool. The GeoCue Server can reference multiple warehouses spread across…
Python scripts offer a convenient method for integrating custom scripts into a GeoCue workflow. To facilitate calling a Python script from a GeoCue checklist step there is a command in the GeoCue library called PythonSurrogate.exe. The PythonSurrogate executable is installed in the GeoCue Client install folder as part of the normal GeoCue installation routine, no…