137 articles GeoCue Tools, Tips and Workflows

Can’t find ImageStation ziphoto.dll

User encounters an error message, “Unable to locate ziphoto.dll in folder”, when attempting to run the stereo edit step in GeoCue using ImageStation. This error message is caused by the install location of ImageStation products being in a different location than in previous versions. Specifically, the ziphoto.dll file. This is usually caused by updating the…

Share

Managing versioning in GeoCue

Summary: When processing in GeoCue, it is a good idea to setup automatic versioning and checkpoints. This allows the user to roll back to a previous state of processing if a mistake occurs or a change needs to be made. This document will review how to access and change settings related to this: Managing versioning…

Share

How to Enable/Disable Dispatch Logs

If asked by support, the following two code snippets when copied and pasted into a text document and saved as “EnableDispatchLogs.reg” and “DisableDispatchLogs.reg” respectively will enable/disable dispatch logs on the GeoCue Server machine when imported to the registry and the GeoCue Server service restarted. Import the EnableDispatchLogs.reg file using admin rights After importing, restart the…

Share

Attaching LAS Files to LAS Working Segments

If you already have LAS files and an index for those LAS files you can skip some of the processing steps typically performed when starting from LAS Source Strips. Start by creating your Working Segment entities using a pre-existing compatible shapefile or CAD file. Next, attach the LAS files to the Working Segment entities following…

Share

Error Starting GeoCue

While attempting to open the GeoCue Client you get an Error Starting Geocue dialog box that says “The GeoCue Server did not respond”. In the box is a list of four things to verify: Please verify the standard four issues as shown in the message. Can you ping the GeoCue Server by name (Server Name)…

Share

Error Generating TSTrajectory File with SOL

User encounters an “Error Generating TSTrajectory File with SOL” while trying to create TerraScan trajectories in GeoCue, “An attempt was made to move the file pointer before the beginning of the file.” The sensor trajectory file is over 2GB in size causing an indexing issue. Reduce the file size to below 2GB by clipping unnecessary…

Share

Insufficient Resources Available in Dispatch Manager

Distributed tasks don’t seem to take full advantage of the available Distributed Subtask Licenses (DSLs). When the task is running, the first pending subtask in Dispatch Manager under the “Pending Reason” column reads “Insufficient Resources Available”. Insufficient resources available means the available machine resources are less than the predicted usage of the command being run,…

Share

Where can I see my Licenses in GeoCue?

How can I check my licenses and license usage in Geocue? GeoCue License Monitor on the GeoCue Server Machine shows dynamic license usage. License monitor has a table for in-use percentage over a period of time (set in settings), and a drop down menu to choose which license you’d like to visualize. It can be…

Share

Adjusting Intensities in GeoCue

When creating a greyscale (or inverted greyscale) LIDAR Ortho Raster, you may want to adjust how your intensity values are displayed in the output image(s). Off: This does not apply any adjustment to the intensities. Automatic (per image): Each image is automatically adjusted based on a % clip algorithm. The algorithm works by setting a…

Share

Factors that control Command Dispatch Dispatched and Distributed Instances

To modify the number of subtasks that are launched when Dispatching/Distributing from GeoCue, consider customizing Machine Resources. (Note that these are advanced GeoCue settings and require GeoCue Administrator level privileges). The factors that need to be considered when fine-tuning your Command Dispatch System are: 1. Available Machine Resources Resources available per machine are controlled by:…

Share