GeoCue Group’s repository of articles for the GeoCue workflow management product, covering tools, tips, and workflows.
Due to the fact that TerraMatch Corrections cannot be applied via TerraSlave, it is important to make sure that the macro has been assigned correctly when running via dispatch within GeoCue. Here are the steps to take when setting up the macro within GeoCue. ***Note: Best practice is to save the tms file in the…
LAS v1.4 introduced the concept of the Overlap classification flag. Since this new flag did not previously exist in the classification code byte, the class offsets discussed here do not apply to the Overlap classification flag. A user would need to have both LP360 and TerraScan in order to properly identify and flag overlap points.…
If you are involved in airborne LIDAR workflows in North America, you will immediately understand the value of supporting LAS Version 1.4, Point Data Record Format 6 for your end-to-end workflow as this will be the required deliverable format for the USGS 3D Elevation Program. Of course, this will drive all standard airborne LIDAR deliverables…
Purpose: This technical note explains Grid-to-ground projections (AKA “ground coordinates”, “surface coordinates”, “localized coordinate networks”, etc.) within GeoCue. A ground coordinate system is a local coordinate system created by modifying the origin and scale of an existing projected coordinate system, such as a state plane or UTM grid system. The ground system is tied to…
Purpose: This technical note explains how to assign strip numbers to source (flight lines) prior to populating LAS working segments or generating TerraScan Trajectories. Most LIDAR system manufacturer software does not automatically assign file source ID to the strip based LAS files. Also, original strip numbers may not correspond with flight plan strip numbers. For…
Maintaining maintenance on your GeoCue Workflow Management software is more than just gaining access to all software releases during the maintenance period. In addition, it allows access to our wide range of support and training services: Customer Advisory Bulletins; An online searchable knowledge base, support.GeoCue.com, for finding solutions to frequently asked questions, technical insights, and general…
Attempting to process a project within GeoCue results in, “System.IO.IOException: Not enough server storage is available to process this command.” The error message indicates that the server has run out of memory for processing commands. Typically this error message is unrelated to the size of the project that is currently being processed within GeoCue.To help…
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…
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…
