GeoCue Group’s repository of articles for the GeoCue workflow management product, covering tools, tips, and workflows.
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…
When converting coordinate data between different datums, obtaining a specific accuracy may require time-dependent processing when converting. This is because one datum may be defined relative to another and in a way that includes coefficients that are a function of time. Even in the case of a single datum, a measured position may have different…
The GeoCue software suite uses client/server architecture. Production staff use a GeoCue Client installed on their local workstation to access projects resident on a GeoCue Server. The GeoCue Server is normally installed on the same local network as the workstations hosting the Clients, but hosted on a separate machine. Technically, any Client will be able…
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…
GeoCue Server runs on top of a SQL database. The database stores all the metadata about your projects as well as all internal links to your geospatial data stored in the GeoCue warehouses. The database may be a full SQL database installation or a limited edition of SQL such as Microsoft SQL Server Express (Express)…
GeoCue Server runs on top of a SQL database. The database stores all the metadata about projects as well as all internal links to the geospatial data stored in the GeoCue warehouses. The database may be a full SQL database installation or a limited edition of SQL such as Microsoft SQL Server Express (Express) or…
This technical note provides instructions for adding logical or ‘Yes/No’ steps to a GeoCue checklist. These types of steps can be useful for tracking work that is not linked to a particular production tool. A common example would be adding a “Ship Data to Client” step at the end of a workflow. They can be…
