New Features in GeoCue 2011.1 Products (R6)...

New Features in GeoCue 2011.1 Products (R6)

September 15, 2011

Important Note: This guide provides information only about changes from GeoCue 7.0 to 2011.1. Please see the appropriate user guide for full information regarding the use of GeoCue products.

GeoCue Corporation 9668 Madison Blvd. Suite 202 Madison, AL 35758 1-256-461-8289 www.geocue.com

NOTICES The material in GeoCue documents is protected by United States Copyright laws.

You may make as many copies of this document for use internal to your company as you desire. Please do not distribute this document outside of your company without first discussing with us.

Trademarks, Service Marks

MapObjects and ESRI are trademarks of Environmental Systems Research Institute

Windows and .NET are trademarks of Microsoft Corporation MicroStation is a trademark of Bentley Systems Incorporated TerraScan is a trademark of Terrasolid Oy ImageStation, OrthoPro and DMC are trademarks of Intergraph

Corporation, a Hexagon company GeoCue®, NIIRS10®, CuePac® are registered trademarks of GeoCue

Corporation SOCET SET is a trademark of BAE Systems GPro/XPro are service marks of Hexagon Geospatial Solutions LYNX™ is a Trademark of Optech

Best Practices – Throughout this document you will see this symbol. This flags a tip or a best practice for improving your GeoCue experience.

Getting Help

This guide contains information about using features new to Version 2011.1 of the GeoCue product family. We are sure that you will experience different problems with GeoCue that range from installation issues to defects that made it through our testing undetected. We hope that you will immediately contact us with any problems or questions and have the patience to work with us through a successful GeoCue deployment.

Please contact us via email for assistance with or comments about GeoCue products. email:

[email protected]

GeoCue New Features User’s Guide

New Features in GeoCue 2011.1 Products i 15 September 2011 Copyright 2011 GeoCue Corporation

Contents 1 An Overview of GeoCue 2011.1 ............................................................................ 1-1

1.1 GeoCue Server/Client:................................................................................... 1-1 1.2 Environment Builder (included with GeoCue Server)..................................... 1-2 1.3 LIDAR 1 CuePac ............................................................................................. 1-3 1.4 Raster Tools CuePac ...................................................................................... 1-3 1.5 DEM CuePac ................................................................................................. 1-3 1.6 DMC PPS CuePac (available from Intergraph) ................................................ 1-3 1.7 OrthoPro CuePac .......................................................................................... 1-3 1.8 DSS (Rapid Ortho CuePac) ............................................................................. 1-3 1.9 Railway Feature Extraction CuePac (RFX CuePac) .......................................... 1-4 1.10 GeoCue Federator (includes Project Dashboard) ........................................... 1-4

2 GeoCue Server and GeoCue Client ........................................................................ 2-5 2.1 GeoCue Options ............................................................................................ 2-5

2.1.1 Drawing................................................................................................... 2-6 2.1.2 Performance Settings .............................................................................. 2-6

2.2 Disabling ‘Dangerous’ Commands ................................................................. 2-7 2.3 Tracking View................................................................................................ 2-9 2.4 Table of Contents (TOC) .............................................................................. 2-11

2.4.1 TOC Symbology ..................................................................................... 2-11 2.4.2 Visibility ................................................................................................ 2-14 2.4.3 Folders .................................................................................................. 2-15 2.4.4 Hiding Layers and Folders ...................................................................... 2-15 2.4.5 Table of Contents - Layouts .................................................................. 2-17 2.4.6 User Settings ......................................................................................... 2-20 2.4.7 Layer Manager ...................................................................................... 2-21

2.5 Warning Symbology .................................................................................... 2-22 2.6 Checklist Legend ......................................................................................... 2-23 2.7 Support for Web Mapping Services (WMS) ................................................. 2-25

2.7.1 Setting up the WMS Catalog .................................................................. 2-26 2.7.2 Adding a WMS Layer to a Project .......................................................... 2-29

2.8 Coordinate Reference Systems ................................................................... 2-31 2.8.1 CRS Transformations in GeoCue ............................................................ 2-31 2.8.2 Datum Tags ........................................................................................... 2-32 2.8.3 Required and Optional Transformation Definitions in GeoCue .............. 2-32 2.8.4 Table of Contents CRS icons .................................................................. 2-33 2.8.5 The Project Coordinate Reference System............................................. 2-34 2.8.6 Setting a Coordinate Reference System (CRS)........................................ 2-36 2.8.7 Creating a Ground System ..................................................................... 2-37 2.8.8 Creating a Custom CRS via a Datum Qualifier ........................................ 2-39 2.8.9 Approving a Default Transformation ..................................................... 2-41


New Features in GeoCue 2011.1 Products ii 15 September 2011 Copyright 2011 GeoCue Corporation

2.8.10 Defining a Transformation Chain ........................................................... 2-44 2.8.11 Creating a New Transform Path ............................................................. 2-47

2.9 Layer Opacity .............................................................................................. 2-56 2.10 Disable Image Enhancements ..................................................................... 2-57 2.11 On-The-Fly Display Chain Image Reprojection ............................................. 2-57 2.12 GeoCue Easter Eggs .................................................................................... 2-57

3 Command Dispatch System (D) ............................................................................. 3-1 3.1 Improved Cloud Configuration ...................................................................... 3-1 3.2 Dynamic Cloud Reconfiguration at the Subtask Level .................................... 3-3 3.3 Dynamic All Machines Cloud ......................................................................... 3-4 3.4 Automatic Cloud Selection and Processing .................................................... 3-4

3.4.1 Dispatching to a default Cloud ................................................................ 3-4 3.4.2 Assigning Default Clouds ......................................................................... 3-5 3.4.3 Cloud Precedence ................................................................................... 3-8

3.5 Auto Run Next Step Supports Default Cloud Dispatch ................................... 3-9 3.6 Inter-Checklist Step Linking Supports Auto Run ........................................... 3-11

4 Environment Builder ............................................................................................. 4-1 4.1 Modifying a System Defined Checklist ........................................................... 4-1 4.2 Checklist Fields.............................................................................................. 4-3

5 LIDAR 1 CuePac ..................................................................................................... 5-1 5.1 Support for Standard GPS Time ..................................................................... 5-1 5.2 Macro Catalog............................................................................................... 5-2

5.2.1 Assignment from Master List ................................................................... 5-3 5.2.2 Modifying Project-level Macros ............................................................... 5-4

5.3 Auto Run Macros .......................................................................................... 5-4


New Features in GeoCue 2011.1 Products 1-1 15 September 2011 Copyright 2011 GeoCue Corporation

1 An Overview of GeoCue 2011.1 GeoCue 2011.1 is the major GeoCue feature upgrade release for 2011. GeoCue has now been in heavy day-to-day production (in commercial release) for about 7 years. Many of the new features that have appeared in GeoCue are a direct result of the feedback that we received from our user base of GeoCue customers. GeoCue Version 2011.1 and the associated CuePacs contain a number of new features. The highlights of these new features are described in the following sections with details provided in the subsequent chapters.

Note: GeoCue Server is available in three versions. Sections that apply only to a specific version will be denoted as follows:

GeoCue Workstation (W) GeoCue Professional (P) GeoCue Departmental (formerly Enterprise) (D)

1.1 GeoCue Server/Client:

GeoCue Client has been rewritten from the ground up on a new core platform technology. The dependence on ESRI Map Objects has been removed from all GeoCue products. This change was necessitated by ESRI’s decision to discontinue support for the Map Objects development platform. GeoCue no longer has any dependencies on third party commercial products.

True 64 bit support. GeoCue will now install as a 64 bit application on 64 bit operating systems (Windows 71, Windows XP, Windows Server) and a 32 bit application on 32 bit versions of these operating systems. GeoCue interoperates seamlessly between 64 and 32 bit client/server configurations. We do recommend a 64 bit Operating System (OS) for both GeoCue Server and GeoCue Client

Improved entity caching to reduce in-memory footprint of GeoCue Server Default command and project Cloud definition for distributed/dispatched processing Ability to cascade all ‘external’ and select ‘internal’ batch commands for

dispatched/distributed processing Automatic dispatch to default cloud Intra-checklist linking (ICL) system Various improvements in Dispatch Manager for configuring Clouds Ability to establish checklist prerequisites based on ICLs Ability to Auto Run a checklist step (of any batch type) via an ICL

1 Note that GeoCue has not been thoroughly tested on Windows Vista. We recommend against using Vista for production environments.



Significantly enhanced horizontal and vertical datum support including intrinsic support for epoch observation dates and Horizontal Time Dependent Positioning (HTDP) and Ground-Grid anchored systems

Support for National Geodetic Survey Earth Gravitational Model 2008 (EGM2008) Ability to disable certain commands based on user/group credentials (e.g. Delete Layer,

Delete Entity) New Table of Contents (TOC) with user defined hierarchical folders (replaces the

Legend) Named TOC “Layouts” with event driven updates to all layout users Ability to “publish” TOC layouts as read or modify New icon controls for TOC functions Ability to hide layers/folders in the TOC On-the-fly raster reprojection for map display Variable entity opacity (on a per layer basis) Navigable Map Overview window (“Tracking” view) Addition of Warning level display to the Map View symbology settings Processing step status pane (Checklist Legend) Support for Web Mapping Service (WMS) layers directly in the TOC GoTo Queue Item button on the Queue Toolbars – allows navigating to a queue item by

Index or the Selected Entity Import Wizard for creating entities from CAD/GIS files Improved user interface for the Gridding tool Ability to create grids over multiple polygons with one operation (allows disjoint aligned

grids) Layer Manager for managing the TOC in a tabular view (synchronizes with Entity

Manager) Ability to override GeoCue generated start/end dates in Project Dashboard Ability to override GeoCue aggregated Budgeted Effort in Project Dashboard Custom company logo support in Project Dashboard Ability to reset Actual Hours on GeoCue entities Time Keeper function to allow for pausing the automatic accumulation of Actual Time

on an interactive checklist step including automatic invocation when the workstation goes into a locked state

1.2 Environment Builder (included with GeoCue Server)

Save/Restore Environment definitions Filter Environments in Environment Builder to reduce clutter



Environment Builder support for Inter-Checklist Linking (ICL) functions Ability to set default Clouds on a per-command basis

1.3 LIDAR 1 CuePac

Support for absolute GPS time projects Ability to generate dZ images on a per scanner basis for Mobile Mapping System (MMS)

workflows Significantly improved workflow for managing and applying TerraScan LIDAR processing

macros Ability to “cascade” operations allowing for fewer “button presses” (for example, have

LIDAR macros automatically dispatched to the default cloud immediately after assignment). This is a side benefit of the Inter-Checklist Linking (ICL) Auto Run capability

Ability to cascade certain setup-run commands such as automatically dispatching a LIDAR processing macro when it is applied (as opposed to requiring a separate step)

1.4 Raster Tools CuePac

Ability to reproject rasters when using “cookie cutter tools 1.5 DEM CuePac

Support for Absolute GPS Time projects (when importing LAS) Can now specify NO_DATA value when exporting GeoTIFF Supports Intergraph’s DTM format – including densification of breaklines when

converting to LAS

1.6 DMC PPS CuePac (available from Intergraph)

Support for all DMC versions including DMC-II

1.7 OrthoPro CuePac (D) Completely new CuePac for integration of Intergraph’s OrthoPro into GeoCue (available from Hexagon) 1.8 DSS (Rapid Ortho CuePac) (D) This is a new CuePac designed for Applanix (a Trimble company) Rapid Ortho workflows.



1.9 Railway Feature Extraction CuePac (RFX CuePac)

Support for Loading GeoCue images in LP36 0RFX Line drawn between actual and snapped location of RFX Features in LP360 RFX Auto-rotate of Profile view in LP360 to be either parallel or orthogonal with nearest

centerline. WMS support in LP360 RFX Synchronization of vector files between RFX and GeoCue

1.10 GeoCue Federator (includes Project Dashboard)

Significantly improved Template project creation scheme for Project Dashboard email events are now asynchronously triggered (e.g. sent when a trigger event occurs

without the need of a user login)



2 GeoCue Server and GeoCue Client This section contains the highlights of new features in the core GeoCue products; GeoCue Server and GeoCue Client. Note that changes to the Command Dispatch System (the GeoCue system for distributed and dispatched command processing) is in the next chapter, even though these are components of GeoCue Departmental Server. Most of the changes in GeoCue have occurred in the GeoCue Client and GeoCue Server. Prior versions of GeoCue Client relied on ESRI’s Map Objects software development kit for certain display functions in the GeoCue Client Map View as well as for the horizontal components of the coordinate transformation system. ESRI discontinued support for Map Objects, forcing us (and many other companies) to look around and see what was a viable path for replacement. We first examined ESRI’s product portfolio for software developers since our experience with ESRI technology has been quite good. Unfortunately, one of our main goals with moving off of Map Objects was full support for 64 bit Windows platforms. While ESRI is claiming that it will release on these platforms in the very near future, this technology was not available when we started our port to 64 bit (and indeed, is still not as of this writing). Thus we decided to go with an open source platform called “Dot Spatial” (dotspatial.codeplex.com), originally developed for a NOAA project (Hydro Desktop). Over the course of the past year, GeoCue Corporation has made numerous contributions to Dot Spatial and has incorporated this viewing platform into GeoCue Client. We are very pleased with the result and think that you will be, as well. As usual, most of your direct experience with GeoCue Server will be via the GeoCue Client interface. Thus, in the topics of the following sections, we will not try to make a big distinction between what services are provided on the Client-side versus what is supplied by the Server. Those interested in this level of detail are typically using GeoCue as a development platform and can make any necessary differentiation via the GeoCue Software Developer Kit (SDK) documentation. 2.1 GeoCue Options Several new option settings have been added to GeoCue 2011.1. The GeoCue Options dialog is accesses via the menu chain: Setup ► Options ► GeoCue …



2.1.1 Drawing Several aspects of Drawing can be configured via the Drawing tab (Figure 2-1). Dynamic Drawing allows you to configure the look of the dynamic rectangle that is drawn when you “drag” select items in the Map View. Note that this setting does not affect the select symbology (the select symbology is hard coded to white and cannot be configured). Tracking Symbology allows you to configure the look of the rectangle in the Tracking View that indicates the current location of the Map View.

Figure 2-1: GeoCue Drawing Options

2.1.2 Performance Settings Performance settings are available on the Admin tab of the Options dialog. Note that you must have GeoCue Administrator privilege for this tab to appear. GeoCue Server maintains an in-memory cache of entities. Any entity that is in memory will exhibit faster data access than an entity whose information must be retrieved from the GeoCue Server database. However, caching large numbers of entities requires large amounts of physical memory on the server that hosts GeoCue Server. The Maximum Loaded Entity Count allows you to configure the approximate maximum number of entities that GeoCue Server will cache. Note that this setting affects the GeoCue Server machine, not the GeoCue Client machine (unless the Server and Client are running on the same machine such as occurs in a GeoCue Workstation configuration).



GeoCue is being used more and more frequently as a Quality Check system for very large image (e.g. camera post-processing, Ortho QC, etc.) projects.

Figure 2-2: GeoCue Client performance settings

2.2 Disabling ‘Dangerous’ Commands You can now disable:

Entity Delete (on the Working Set Queue toolbar) Layer Delete (on the Table of Contents toolbar) Project Delete (on the Project Utilities menu)

These functions are disabled from User Manager. Open User Manager by navigating the GeoCue Setup menu: Setup ► Administration ► User Manager … This will display the web-based User Manager dialog (Figure 2-3).



Figure 2-3: User Manager

Double click the name of the person who’s delete privileges you wish to restrict (or select the row and press “Properties”). This will display the Properties dialog for that person (Figure 2-4). Now simply uncheck the permissions that you do not want this person to have. NOTE: A person who is a member of the Administrator’s Group will have full permission for all permission protected areas of GeoCue, regardless of individual settings!!



Figure 2-4: Disabling Delete Permission

2.3 Tracking View GeoCue now supports a “Tracking View.” This is a second project view that is used for navigating in the GeoCue Map View. The Tracking View can be quickly turned off and on via the Views toolbar in the main GeoCue toolbar section (Figure 2-5).

Figure 2-5: Turning on the Tracking View

Like all views in GeoCue Client, the Tracking View pane can be undocked and parked outside of the GeoCue Client “Frame” (yet another reason to convince your boss to let you have four monitors!). The Tracking View is depicted in Figure 2-6.



Figure 2-6: GeoCue Tracking View

The Tracking View has a permanent toolbar used for manipulating the view. The use of these tools is explained in

Table 2-1: Tracking View Tools Icon Tool Use

Track Mode Multi-purpose tool. A single click in the Tracking View will re-

center the GeoCue Map View at the clicked location. Dragging a rectangle by holding down the left mouse button while dragging will zoom the Map View to the defined rectangle.



Icon Tool Use

Zoom in, Zoom out

Single clicking this button will allow you to do a single zoom in/out centered on the point clicked in the Tracking View. Double clicking enters “sticky” mode, enabling you to perform multiple zoom in/out operations in the Tracking View.

Pan Allows you to pan the Tracking View. Double clicking enters

“sticky” mode.

Fit Fits the Tracking View to the Project extents. Note that Web

Mapping Service (WMS) layers are not included in determining the project extent.

Park a Tracking View on one of your monitors with the project fitted to the view. Use the Track Mode tool (which is the default enabled tool) to quickly navigate in the project by clicking where you would like to re-center the Map View or dragging a rectangle to change the Map View zoom level and location.

2.4 Table of Contents (TOC) In GeoCue 2011.1, we have completely redesigned the map legend (default location is the upper left GeoCue Client pane). To more accurately reflect the purpose of this pane, we have renamed it the “Table of Contents” (TOC). The redesigned TOC supports a number of new features, among which are:

Check boxes replaced by graphical icons Hierarchical folders for organizing layers The ability to save a specific TOC layout as a named Layout The ability to ‘publish’ layouts for use by other team members (as read only or

read/write) The ability to hide information fields in the TOC

2.4.1 TOC Symbology An example Table of Contents is depicted in Figure 2-7. Note that both TOC toolbars are ‘docked’ on the TOC border. If you do not see the toolbars, right click in the top area of the TOC and check the desired toolbar.



Figure 2-7: An example Table of Contents (TOC)

The toolbar on the right in Figure 2-7 is the Select Columns toolbar. It is used to add and remove symbology icons from the TOC entries. Clicking a tool button will show/hide the column tool in the TOC. The name and function of each is tabulated in Table 2-2.

Table 2-2: Table of Contents Symbology Tools Icon Tool Use

Coordinate Transform Status

This icon indicates the current status of the coordinate system transform that has been established between this layer and the Project Coordinate System. Note that this column cannot be turned off if a warning or error state exists.



Icon Tool Use

Processing Status

This column indicates the current processing status of entities associated with this layer that have not yet established a GeoCue geometry. For example, when importing LIDAR sources, the processing status is associated with the Layer since the flight lines do not exist in GeoCue until the import completes. Double click the layer in the TOC and select the Processing Tab to check the status.

Select When enabled, entities on this layer are selectable

Labels Toggles label display on and off for entities on the layer

Processing Status – fill

Works in conjunction with the Processing Status tool bar in GeoCue. When enabled, the processing status selected in the Processing Status tool bar will be displayed for this layer as the fill color (applies to polygonal entities). Mutually exclusive with the Outline status icon.

Processing Status – outline

Works in conjunction with the Processing Status tool bar in GeoCue. When enabled, the processing status selected in the Processing Status tool bar will be displayed for this layer as the entity outline (applies to all entity geometry types). Mutually exclusive with the Fill status icon.

Locks Enables the display of lock status for entities on the layer.

Works in conjunction with the lock status tools on the main Symbology toolbar.

Cache Enables the display of file cache status for entities on the

layer. Works in conjunction with the cache status tools on the main Symbology toolbar.

User Selection

Works in conjunction with the processing status tools on the Symbology toolbar.

Priority Load

When enabled, raises the priority of this layer with respect to loading information to the layer when the project is initially opened.

Raster Footprints

Turns on/off the display of footprints on a rater layer

Rasters Turns on/off the display of rasters on a raster layer.

Information columns

Shows/hides the information columns in the TOC. Turning this off gives a clean display of the TOC. We recommend keeping this off and reviewing detailed TOC layer status in the new Layer Manager tool. Note that, unlike the other tools in this toolbar, this tool applies to the entire TOC (you cannot turn information on/off on a per layer basis)



Information for a particular layer is toggled on/off by pressing the corresponding symbology icon on that layer in the TOC.

2.4.2 Visibility Visibility of entities in GeoCue is controlled at the row level in the GeoCue Table of Contents (TOC). Simply single left click the Folder (for folder rows) or layer icon to toggle visibility off and on. When visibility is off, the folder/layer icon becomes transparent (Figure 2-8).

Figure 2-8: Turning row visibility on and off

Note that if you turn the visibility of a row in the lower section of a nested hierarchy on, and somewhere above in the hierarchy the visibility of a folder is off, the row you just turned on will not display. To avoid annoyance, GeoCue will, in these cases, display the message of Figure 2-9. Simply select Yes to ensure that the row you are toggling to visible will actually show in the Map View.

Figure 2-9: Quick visibility enabling for nested rows

On

Off



2.4.3 Folders Folders allow you to establish a hierarchical ordering to the Table of Contents (TOC). Some general guidelines for folders are:

There is no limit to the nesting level of folders in GeoCue (that is, folders can contain folders)

You can drag and drop layers and folders in the TOC, at will Any given level of the folder hierarchy can be heterogeneous with respect to

folder/layer combinations Turning off a property at a layer level (e.g. visibility) turns off that property for all items

at a lower level in the hierarchy Folder structure is maintained in the definition of a Layout (explained in a subsequent

section) Hiding a folder will hide all hierarchy at and below that folder level

Create folders using the Folder tool from the main TOC toolbar (Figure 2-10) or by selecting “Folder” from the TOC right click tools.

Figure 2-10: The Folder Tool

If you create a new Parent folder while multiple layers/folders are selected in the TOC, those selected folders/layers will be contained within your new folder. You can use Drag and Drop to move folders and layers about within the TOC. Thus you can drag folders into and out of hierarchies, layers into folders and so forth.

Once you have a folder layer that you wish to keep, save the Layout using the Layouts tool from the TOC Main toolbar (see Layout section).

2.4.4 Hiding Layers and Folders You can mark layers and/or folders as Hidden in the Table of Contents (TOC). Once marked as hidden, these layers and folders can be displayed or hidden by using the Hidden Rows tool in the TOC main toolbar (Figure 2-11).



Figure 2-11: The Hidden Rows Tool

To mark a row or rows in the TOC as hidden, first select the desired rows. Selecting in the TOC works the same as selecting in Windows Explorer (using Shift to select all rows between the initially selected location and the current location and Control to select/unselect individual rows). Once selected, press the drop-down arrow on the right of the Hidden Rows tool in the TOC main tool bar (Figure 2-11) or right-click (but be careful not to unselect your rows!). Select the command Mark Selected Rows as Hidden (see Figure 2-12).

Figure 2-12: Marking selected rows as Hidden

Now when you toggle the Hidden Rows tool in the main TOC toolbar, rows marked as hidden will show/hide. The state of hidden rows is saved in the current Layout.

Use the hidden rows function to simplify Layouts for particular users. For example, if you have a QC function for edited LIDAR tools in a complex LIDAR project, consider hiding all but the layer to be QCed. “Publish” this configuration as a “QC” for the QC staff.

NOTE: A hidden row will not display in the Map View, even if Visibility is toggled on for

that row.



2.4.5 Table of Contents - Layouts Configuring a Table of Contents (TOC), especially for a many layered project, can be quite time consuming. In addition, there are many circumstances under which you would like to pre-configure an arrangement of the TOC for a select class of users (for example, a simple layout for QC). GeoCue assists with this need by allowing you to save a particular arrangement of the TOC as a “Layout.” Layouts are Project constructs within GeoCue; that is, a layout is always associated with a particular project. This has to be the case since, in general, no two projects will have the exact same TOC. When working in GeoCue, you are always within the context of a Layout. This concept is so fundamental to GeoCue that the current Layout is listed in the Project title bar of the GeoCue client. Until you create a specific named layout for a project, you will be working within the context of your own, unique “default” layout (see Figure 2-13).

Figure 2-13: The current Layout

Your “default” layout is a private layout associated with your GeoCue login. It can never be shared (it can, however, be cloned to create a new layout that you can share). Every time you make a change of the following nature to the TOC, that change is saved in the current layout:

Order of rows Folders and folder contents Status of Hidden rows Opacity settings for layers Image enhancement settings for layers

You can save different configurations of the TOC by creating new Layouts. To create a layout, press the Layout tool in the main TOC toolbar (Figure 2-14).



Figure 2-14: The Layout Tool

This will invoke the dialog of Figure 2-15. Press the New Layout tool (highlighted in red in Figure 2-15) to create the new Layout.

Figure 2-15: The Layouts Dialog

This will invoke the New Layout dialog (Figure 2-16). Enter a Name for your new layout and (optionally) a description. You can use any text string for the name (it is not case sensitive) that is unique within Layout names for the current project. Remember that a layout is unique to a Project and thus “QC” in Project A is not the same as “QC” in Project B. The Lock Project Layer to Top option ensures that the Project Layer will always be the topmost layer in your TOC. It avoids the annoyance of having layers such as GeoAnalysis layers pop in above your project layer. The Permissions section of the dialog allows you to control how other users in the current project can interact with this TOC layout. Private means that no other users will see this layout when they bring up their Layouts dialog.



Figure 2-16: The New Layout dialog

Published means that this layout will be available to other users within this project. By default, all users with have Modify permission to the named layout. This means that they will be able to change layout-stored items such as folder contents. If you want to restrict other users, simply use the standard GeoCue permission system to do so. For example, if you want to create a layout for QC users that shows only LAS layers in your project and does not allow the QC group to change the layout, do the following:

1. Create a new layout named QC 2. Set the Layout to Published (the Published radio button option in Figure 2-16) 3. Set the QC group in the Read section of the permissions 4. Set yourself in the Modify section of the dialog (as with all permissions of this type in

GeoCue, setting at least one user changes the default behavior from all GeoCue users having the permission to only the named user having permission)

5. Arrange the TOC as you want it to appear to the QC group (for example, you might hide all layers except for the LAS layers that you need QCed)

In general, you should always use Groups for various permission function in GeoCue rather than individual names. This allows you to maintain logical groupings in one place (User Manager) when the group configuration changes.



NOTE – Users with Administrative privilege in GeoCue will always be able to access all layouts. NOTE: Users who do not have modify privilege to a layout will not be able to use the following TOC tools while in the layout:

Delete Layer Create Layer Mark Layer Hidden /Visible Hide/Unhide Layer

They also will not be able to move any layers in the TOC. Note that Layouts in GeoCue are dynamically updated in real time. This means, for example, if four users in Project Madison are sharing layout “Great Layout”, every time a user (with modify permission to Great Layout) changes an aspect of the TOC that is stored in a layout, everyone using Great Layout will see the change, as it happens. For example, if a user creates a new folder named Sources and moves SBET and LIDAR source layers into the new folder, all other users of same layout will see the changes as they occur. This dynamic, real time layout capability makes a very powerful tool for organizing projects for specific classes of users.

2.4.6 User Settings User Settings are generally settings that do not form part of a layout. These include:

Symbology columns being displayed in the Table of Contents (TOC) On/off visibility status of layers/folders Status of each individual symbology setting on a layer/folder

User setting are not shared with Layouts but are stored on a per-user basis. This makes logical sense. If Joe turns on selectability of a LAS layer in a project, Bob does not generally want his LAS layer in this project to suddenly become selectable, even if he is using the same Layout as Joe. User settings are saved when you either change to a different Layout or when you exit the project. The next time you open the project in the layout, you settings will be restored. Note that you can save multiple different setting configurations simply by setting up a number of different, private layouts.



2.4.7 Layer Manager Layer Manager is used to view and management the layers in a project. It is invoked from the main GeoCue toolbar (Figure 2-17).

Figure 2-17: Invoking Layer Manager

When invoked, the dialog of Figure 2-18 is displayed.

Figure 2-18: Layer Manager

Layer Manager is designed to work in a synchronized manner with the Table of Contents. When you select a row in one, the corresponding row in the other will also select. You can apply sorting and filters in Layer Manger. Actual operations such as toggling layers on/off are performed in the TOC itself. Thus the idea is to use Layer Manager as an index into the TOC but perform actual changes in the TOC itself. Note that Layer Manager is integral to Entity Manager. Thus by selecting rows in Layer Manger and then tabbing over to Entity Manager, you will have automatically selected entities on the selected TOC rows.

Keep a ‘clean’ TOC view by toggling off “information” ( ) and use Layer Manager to inspect details such as coordinate systems and entity counts.



2.5 Warning Symbology Warning symbology can be turned on with the Symbology toolbar “Warning” button (see Figure 2-19). A warning level is used in a number of GeoCue operations to indicate that something out of the ordinary has occurred but it is not an error. For example, when you Populate Working Segments in the LIDAR 1 CuePac flow, a warning will be set for working segments that did not intersect any underlying LIDAR sources and hence contain zero points.

Figure 2-19: Enabling Warning Symbology

To display entities in the Map View that are in a Warning state, set the symbology toggle on the associated layer(s) in the TOC and enable the Warning symbology via the Symbology toolbar, Warning tool (Figure 2-19). Figure 2-20 depicts the Map View showing Working Segments with Populate steps in the Warning state.

Figure 2-20: Working Segments in a Warning state



GeoCue does not automatically display symbology for entities that have entered a Warning state. Thus it is a good idea to toggle through warning state display after running a checklist step to ensure that none of the entities have transitioned to Warning. We always point out in CuePac workflows where and why Warning state is used.

2.6 Checklist Legend GeoCue 2011.1 includes a new Checklist Legend tool for viewing the production status of entities in GeoCue. The production status of the currently selected entity is shown in the checklist pane (assuming that production status for the associated layer is enabled in the TOC and in the Symbology toolbar) – see Figure 2-21. However, in prior versions of GeoCue it has not been possible to easily view the production status of entities on a single layer that have different checklists.

Figure 2-21: Associating fill symbology with Checklist State

This is actually the case in Figure 2-21 – the last three rows of LAS tiles have a different checklist than the top 6 rows. To further complicate matters, the checklists have been designed (rather poorly, we might confess but this is a contrived example for illustrating a feature!) such that Final QC complete has different colors in the two checklist!



Thus selecting one of the tiles on this layer of LAS tiles will give a misleading view of status if we simply examine the Checklist pane. The new Checklist Legend tool addresses this problem. The Checklist Legend tool is invoked from the View Panes toolbar in the Map View tool bar area (Figure 2-22).

Figure 2-22: Displaying the Checklist Legend view pane

This will enable the view pane shown in Figure 2-23.

Figure 2-23: The Checklist Legend View Pane

All checklists that have both visibility and Production Symbology (either fill or outline) turned on in the Table of Contents (TOC) will be listed in the left column of the Checklist Legend. In our example of Figure 2-23, we have visibility and fill symbology turned on for a layer of LAS working segments that contains entities some of which have the checklist “LAS Working Segments with LP360” assigned and others with the checklist “LAS Working Segment 5.0” assigned.



Selecting a checklist name in the left pane causes the Processing steps of the checklist to display in the right pane. Enabling the Auto-Synchronize Selected Entities button (left most button in the Checklist Legend toolbar section) will cause the entities with the checklist selected in the left pane of the Checklist Legend to Select in the Map View. This allows you to easily identify those entities with the currently selected checklist. This is depicted in Figure 2-24 where we have selected the checklist “LAS Working Segment with LP360” and the associated entities have selected in the Map View.

Figure 2-24: Synchronizing the selected checklist with associated entities

Note that if the entities are not set as Selectable in the TOC, they will not select in the Map View via Checklist synchronization unless you enable “Override TOC Selectable” (the arrow tool in the Checklist Legend toolbar). NOTE: The Checklist Legend can become confusing if you have too many overlapping layers in the Map View with Symbology enabled. This is particularly true when one layer completely obscures another layer. For example, you may have LIDAR Sources higher in the TOC than LAS Tiles that were extracted from those sources. If you turn on fill symbology for both of these layers, the LAS tiles will be completely obscured by the LIDAR sources. You can address this sort of issue by turning off the obscuring layer, setting opacity below 100% on the obscuring layer or setting the symbology display in the TOC to outline rather than fill on the upper layer. 2.7 Support for Web Mapping Services (WMS)



You can add layers in the GeoCue Map View that are ‘mapping’ to a Web Mapping Service. For example, Figure 2-24 depicts a backdrop image being supplied by Open Street Map. It is often the case that you will continually reuse a small set of WMS layers within your GeoCue projects. To make this use case easy, we have implemented a WMS Catalog Service. Thus, prior to adding a WMS layer, you must first establish the catalog.

2.7.1 Setting up the WMS Catalog The WMS catalog is set up using the WMS Manager tool in GeoCue Client. This tool is accessed from the main GeoCue Map View toolbar (Figure 2-25).

Figure 2-25: Invoking the WMS Manager

The WMS Manager is depicted in Figure 2-26. The first step in adding to the WMS Catalog is to add a WMS Server or select from the GeoCue pre-defined servers (Open Street Map and Bing in GeoCue version 2011.1).



Figure 2-26: WMS Manager

To add your own WMS Server, press the Add button that is located directly below the Available Servers pane. This will invoke the dialog of Figure 2-27. Enter the name you would like associated with this server in the Server Name field. This is a simple text field that you will use as your ‘familiar’ name for the server. Enter the actual Universal Resource Locator (URL) string in the Server URL field.



Figure 2-27: Add WMS Server dialog

GeoCue will validate your server and display the hierarchy. Select the ‘branch that you wish to use as a layer in GeoCue (by expanding entries and selecting the appropriate terminal branch in the Servers pane) and then press the Add button below the Catalogs section of the dialog. Note – If you have not selected a valid catalog level in the Servers pane (a valid level, usually at the EPSG code entry, will appear in green), the message “No Valid Catalog Entry selected in Available Servers” will be displayed and the Add button will not enable. When you press the Add button under Catalog Entries, you will be presented the dialog of Figure 2-28.

Figure 2-28: Adding a WMS Catalog Entry

The Name is any familiar text string you would like to use. It must be unique across all of your WMS catalog entries. This is the name that will be displayed to users when they add a new WMS layer to a project so it should be chosen to make the layer content obvious.



The description can be any textual notation. It is not displayed during layer selection by users. The Style field allows you to choose the desired style being presented by the WMS Server entry. This field is populated by a Style request sent to your selected WMS Server. Pick the desired style from the dropdown list. Finally, Token is used by restricted or licensed WMS Servers (such as Google and Bing). You must obtain a token from your chosen WMS provider using whatever scheme that provider has instituted. Some providers allow temporary or experimental use without a registered token. You can attempt to use these experimental services by typing in a string such as “token” for this field. Note that Open Street Map does not require a token. Click OK on the Add Catalog (Figure 2-28) dialog and your new WMS entry will be ready for use!

2.7.2 Adding a WMS Layer to a Project A Web Mapping Service (WMS) layer is added to a project via the Add Layer tool in the Table of Contents (TOC). To add a WMS layer, select the layer just above where you would like the new WMS layer inserted in the TOC. Next either press the Create New Layer tool (on the TOC main toolbar - Figure 2-29) or right-click and select “Create New Layer” from the right click TOC menu.

Figure 2-29: Creating a New Layer



The Create New Layer command will display the dialog of Figure 2-30. Choose WMS from the layer type radio button section. This will enable a drop-down list of all of your WMS catalog entries. Provide a name for the layer and an (optional) description. Note that the coordinate system is displayed for informational purposes only; it cannot be changed (if your WMS Server provides different coordinate systems, make a separate entry for those you desire to use in the WMS Manager).

Figure 2-30: Create New Layer dialog

That’s all there is to adding the WMS layer! NOTE: A WMS layer in GeoCue is a fully qualified layer, You can add multiple WMS layers, sort the layers, set opacity, hide them and so forth. Since GeoCue Client supports “on-the-fly” coordinate reprojection, you can add WMS layers with mixed coordinate reference systems and have them simultaneously displayed. NOTE: Many WMS Servers provide data in less than optimal speed. GeoCue has implemented WMS drawing as an asynchronous activity. This means that you can continue working in a project while a WMS layer repaints in the background.



2.8 Coordinate Reference Systems GeoCue includes advanced coordinate reference system (CRS) support. Among the features added in 2011.1 are:

Support for multiple stage CRS transformations (effectively unlimited) Native support for National Geodetic Survey2 (NGS) Horizontal Time Dependent

Positioning (HTDP) Native support for construction style “Ground-Grid” local space rectangular anchored

systems (a single GeoCue project can support multiple stations) Ability to “publish” common transforms to a global GeoCue repository for reuse in

projects without the need to redefine Of course, GeoCue retains all of the features previously found in its robust CRS support system such as support for vertical CRS and reprojection of data during common project operations such as transferring LIDAR data from source swaths to processing tiles.

2.8.1 CRS Transformations in GeoCue Coordinate Reference Systems (CRS) are defined at the layer level in GeoCue. That is, all entities on a layer (within the Table of Contents) share the same CRS, as defined by that layer. Unlike a GIS, a layer in GeoCue generally has both a horizontal CRS (HCRS) and a vertical CRS (VCRS). Unless we need to specify a distinction, we will simply refer to these collectively as the CRS. A transformation from one CRS to another CRS will be simply projective if the two CRSs are based on the same Datum or a full datum transformation if the two CRSs are based on different datums. GeoCue segregates CRS transformations based on the underlying datum. If two CRSs are based on the same datum, GeoCue does not require an explicit CRS transformation. An example of this might be a layer defined as NAD 83 NSRS 2007 UTM Zone 17 N (meters) and a second layer defined as NAD 83 NSRS 2007 State Plane Ohio North (feet). Since these two layers are based on the same datum (NAD 83 NSRS 2007), no explicit transform will be required.

2 NGS is a branch of the United States National Oceanic and Atmospheric Administration (NOAA)



If, on the other hand, two layers are based on differing datums, an explicit transform must be defined in GeoCue. An example might be a layer with the CRS NAD 1983 State Plane Kentucky North (feet) and a second layer with CRS WGS 19843. Here one layer is based on the NAD 1983 datum whereas the other layer is based on the WGS 84 datum. Since the datums are different, an explicit datum transform will have to be defined in GeoCue if data are to be translated between these two layers. 2.8.2 Datum Tags It is a very unfortunate circumstance that a number of common datums have been redefined over the years without any explicit notation to guide the user as to which particular version of a datum is in use. As an example, the following version of North American Datum 1983 exist:

NAD 83 – 1986 (the original definition of NAD 83) NAD 83 HARN NAD83 CORS96 NAD83 NSRS 2007 (commonly called NAD 83 – 2007)

Each of these four versions of NAD 83 are a different realization of the datum. As such, a datum transformation is required to move between the realizations. The transform between NAD83-1986 and any of the other three is significant. The differences between the other three is small for project precisions above 6 cm or so. To enable you to define rigorous transformations between different realizations of a datum, GeoCue now supports user defined datum tags. A datum tag simply allows you to tag a CRS, allowing a unique datum transformation to be assigned. Datum tags are of particular importance when you use:

Horizontal Time Dependent Positioning (HTDP) Ground-Grid Systems (where the datum tag is used to define a station)

2.8.3 Required and Optional Transformation Definitions in GeoCue Transformations between Coordinate Reference Systems (CRS) can occur in several places in GeoCue:

Between a layer and the Project CRS Between a layer and the current Map View CRS

3 If no datum tags are present, we assume the original datum (e.g. NAD 1983 – 1986 realization and the original epoch of WGS 84



Between source and destination layers when a data CRS conversion is occurring (for example, when populating LIDAR working tiles from a source strip layer where the source and destination layers are based on different datums).

Some datum transformations are mandatory in GeoCue whereas others are optional. The various conditions are described in Table 2-3.

Table 2-3: Datum Transformations in GeoCue CRS 1 CRS 2 Mandatory? Notes TOC Layer

Project Yes GeoCue will not allow the completion of a layer to be finalized until the layer to Project transformation is defined

TOC Layer 1

TOC Layer 2

No (unless) Only required if a datum transformation operation is to occur between the two layers such as transforming LIDAR data from source files to LAS working tiles. GeoCue will direct the user to the datum transform definition dialog if the transform is needed but is not defined.

TOC Layer

Map View CRS

No (unless the Map View CRS is the same as the Project CRS)

The Map View can be set to display in any desired CRS. If a datum transform is needed between a particular GeoCue layer and this Map View CRS and the transform does not exist, the entities on that layer will not be displayed (the No Transform Defined icon will show for the offending layer(s))

2.8.4 Table of Contents CRS icons One of the most important considerations in a production project is assuring that all Coordinate Reference Systems and transformations between these systems are established and correct. The GeoCue Client provides feedback on transformations between layers and the Map View Coordinate Reference System (CRS) via the left-most icon for each layer in the Table of Contents (TOC). Note that the Map View CRS defaults to the Project CRS for a new project but it can be changed at any time via the Map Coordinate Systems tool found on the main TOC toolbar (see Figure 2-31).



Figure 2-31: The Map Coordinate Systems tool

These icons and their meanings are denoted in Table 2-4.

Table 2-4: Coordinate Reference System Transform icons in the TOC Icon Status Notes

No Transform needed

No transformation is required between this layer and the Map View Coordinate Reference System (CRS)

Unapproved Transform

A transform is required and has been established between this layer and the Map View CRS (most likely automatically by GeoCue) but it has not been explicitly approved by a user.

Approved Transform

A transform is required and has been established between this layer and the Map View CRS and it has been explicitly approved by a user.

No Transform Established

A transform is required between this layer and the Map View CRS. GeoCue is not able to generate a default transformation. The user must enter the Coordinate System Manager and explicitly define a transformation or data from this layer will not be displayed. Note that if the Map View CRS is currently identical to the Project CRS, this condition should not occur (since defining a transform between the Project CRS and each layer’s CRS is mandatory).

Always Approve CRS transforms for your projects. This means that you should have no warning ( ) icons in your TOC.

2.8.5 The Project Coordinate Reference System The Project Coordinate Reference System (CRS) is established when you first create a project and cannot, in general, be changed. There are no real restrictions on the CRS that you establish for a project. However, it is wise to consider the following when deciding upon the Project CRS:



A transformation to and from the Project CRS must be established for every layer that is subsequently created in your project (layers in the Table of Contents, TOC). It is not necessary, however, that a transformation exist between layers in the TOC that are not the Project layer. Thus it is a good idea to avoid using an obscure CRS or one for which limited transforms (e.g. NAD 27) exist as the Project CRS.

The Map View can be set to any desired CRS. However, a transform must exist between a layer in the TOC and this CRS if entities on the layer are to be displayed. Thus it is a good idea to define the Project CRS as the most used Map View CRS.

If your project is located in the United States of America and you intend to use the NGS Horizontal Time Dependent Positioning capabilities within GeoCue then we recommend that you use:

o NAD 83 NSRS 2007 (North American Datum 1983, National Spatial Reference System version 2007)

as the project CRS. In fact, NAD83, NSRS 2007 is a good choice for the project CRS, in general, for USA projects.

You should not use an anchored local space rectangular (a so-called “ground” system) for your project CRS. We give this advice because the horizontal range over which the LSR is valid is limited. Thus using an LSR as the project system would only make sense if all layers in the project will use a single station LSR.

All GeoAnalysis construction commands create layers in the Project CRS. Thus you may want to avoid using a geographic CRS for the Project layer (note – there is absolutely no issue with using a geographic CRS for the project layer – you just might not want to do GeoAnalysis constructions in geographic since you will note the usual skew between this system and projected systems)

GeoCue performs “on-the-fly” reprojections to the current Map CRS (which is not necessarily the Project CRS – you can change the Map CRS). Thus choosing a project CRS that is representative of the majority of layers in your project can improve performance.

The Project Coordinate Reference System (CRS) is established during the creation of a new project (Figure 2-32) via the Select Coordinate System button.



Figure 2-32: The New Project dialog

2.8.6 Setting a Coordinate Reference System (CRS) A coordinate reference system (CRS) is established for a project or a project layer from the common Select Coordinate System dialog (Figure 2-33). The upper section is used for creating a horizontal CRS, the center section is used for creating a modified Horizontal CRS based on the upper section of the dialog and finally, the lower section is used to define a Vertical CRS. A base horizontal CRS is defined by either browsing for the appropriate choice in the right side of the dialog or by importing a “PRJ” file. Note that many new systems have been added to GeoCue 2011.1 including NAD 83, NSRS 2007 (recommended for most USA projects). The Vertical system is set by browsing in the Vertical Datum section of the dialog. If you are creating a two dimensional CRS (for example, an image layer), you will not be able to set the Vertical system. Occasionally you may need to create a 3D layer with an undefined vertical system. This is accomplished by choosing “Unspecified” in the vertical section.



Figure 2-33: Select/Create Coordinate Reference System dialog

2.8.7 Creating a Ground System 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. These are commonly used when conventional ‘on-the-ground’ construction must occur (e.g. highway projects). The ground system is tied to the grid system at the specified origin (specified in grid system coordinates) and scale corrections are applied. Ground measurements will more closely match measurements in this local system than in the standard grid system on which it is based. However, scale distortions will increase as the distance from the local origin increase, and with changes in elevation.

2.8.7.1 Specifying the Ground System Check the Create Custom Coordinate System from Selection checkbox to open the Custom Coordinate System Settings portion of the Select/Create Coordinate Reference System dialog. Check the Create Ground Coordinate System checkbox item. The dialog



will expose fields to allow you to enter a name for the new ground system (for an existing GeoCue project, a default name based on the project name is provided, but you may enter an alternate).

Specify the location of the origin for the local system (using the original grid system coordinates) and the factor to use for scale correction. You may optionally enter additional False Easting and False Northing offset amounts (e.g. an additional 100,000 foot offset in each direction can aid in distinguishing ground coordinates from standard grid coordinates). A new coordinate system with the indicated name will be created and will appear in the User Defined folder, or a selected subfolder, of the Horizontal Coordinate Systems window.



2.8.8 Creating a Custom CRS via a Datum Qualifier GeoCue allows new coordinate systems to be created by appending a user-specified qualifier to the datum, geographic system name, and if applicable, the projected system name. This qualifier is useful for identifying a particular time that data was observed, as well as a particular location. This can be used to support Horizontal Time-Dependent Positioning (HTDP). For example, to indicate data was observed mid-year 2010 in Hardin County, Tennessee, qualifiers such as "2010.5” and “Hardin County" might be used to create the coordinate system: "NAD 1983 NSRS2007 StatePlane Tennessee{2010.5;Hardin County}". This information is necessary to create datum transformations that are time-dependent (such as between NAD83 and WGS84), or to adjust for crustal motion between two observation dates of the same datum. Note however, that use of qualifiers results in “custom” datums, and corresponding datums transform will have to be created.

2.8.8.1 Specifying Qualifiers Check the Create Custom Coordinate System from Selection checkbox to open the Custom Coordinate System Settings portion of the Select/Create Coordinate Reference System dialog. Check the Specify Qualifying Parameters checkbox to enable the controls to allow entry of qualifying parameters.



Select Qualifying Parameters

Select existing qualifiers, or enter new date and location qualifiers. The Description field allows for more detailed information about the qualifiers and is displayed in GeoCue wherever coordinate system details are shown, such as when viewing layer properties. The Description field will be read-only for Date/Location combinations that already exist. Use the default name and location for the new coordinate system, or check Override Default and use the Select button to specify your own custom name and/or location for the new coordinate system.



2.8.9 Approving a Default Transformation A Coordinate Reference System (CRS) transform is required when the CRS of a project layer is based on a datum that is different that the datum on which the Project CRS is based. GeoCue will always attempt to select a default transformation for these cases. When a

default transformation is established, GeoCue will display a warning triangle icon ( ) at the far left of the layer in the Table of Contents. It is very important that you approve the transformation that GeoCue has selected because it may not be correct or it may not be the optimal transform. To approve a datum transformation, select the layer on which the warning icon appears and press the Map Coordinate Systems tool on the main Table of Contents (TOC) toolbar (Figure 2-31). This will invoke the Map Coordinate Systems dialog (Figure 2-34). In the upper section of this dialog will be listed every CRS defined in this project.

Figure 2-34: The Map Coordinate Systems dialog

Referring to the upper section of Figure 2-34, the Project CRS is shown in blue and is the first listed CRS. The CRS checked as Active defines the current display CRS for the Map View. The CRS checked as default is the default CRS that will appear when you are creating new layers in GeoCue. Thus this option provides a short cut when several layers with the same CRS are to be created. The third column, filter, is for your used in



filtering the list down to a subset (checked items will show if you set the filter to True whereas unchecked items will show if you set the column filter to False). When you select a row in the Available Map Coordinate Reference Systems section of this dialog, the lower panes list the datum transformations that could potentially be required for this selection (Horizontal in the left pane and Vertical in the right pane). Transforms in this section can be in one of three states:

Undefined Defined but not approved Defined and approved

The idea of unapproved is to prompt you to review the transforms that GeoCue automatically selects to ensure they will perform as intended. To approve an unapproved transform, select the desired transform and press Define… (note that you can directly press Approve but this will be approving the transform without reviewing its implementation – a bad practice!). This will invoke the dialog of Figure 2-35.

Figure 2-35: Define Datum Transform dialog

The first section of this dialog lists all of the available paths for transforming from the “From” datum to the “To” datum. A path is a chain of transforms through a sequence of datums. The highlighted row represents the current path for the transform that you are



approving. Notice in our example of approving a transform from North_American_1983 to WGS_1984, GeoCue has selected a single stage transform. The second pane of the dialog lists each stage of the transform path selected in the top pane. In our example, a single entry appears since we are using a single stage transform. Finally, the bottom pane of the dialog lists all of the available transforms for the stage selected in the middle pane. The highlighted transform (it also will have Assigned checked) is the transform currently in use for the selected stage. View the details of this transform by pressing the Review… button in the lower right section of the dialog. This will display all of the parameters being used in the transform (see Figure 2-36). If you are satisfied with the transform, close the dialog and OK off the parent dialog. If you are clueless as to what these parameters mean, you should seek assistance from the person in your organization responsible for geodesy.

Figure 2-36: Review Datum Transform Stage dialog

This will return you to the Map Coordinate System dialog. Select the datum that you just reviewed and press Approve. This will mark this transform as approved. If you are not satisfied with the assigned datum transformation, then you will need to perform a modification. See the next section.



2.8.10 Defining a Transformation Chain If you are not satisfied with the transformation choice made by GeoCue or GeoCue cannot determine a transform, you will need to make the definition. The most common scenario for needing to define (versus approve) a datum transformation is in the case of creating a new layer with a CRS for which GeoCue cannot determine a transform to the Project CRS (recall that all layers in GeoCue must have a transform to the Project CRS defined). In the following example, we have a project whose project CRS is NAD83, State Plane, Kentucky North (feet). When we create a LAS layer in NAD83 HARN, GeoCue cannot determine a default transform and thus the dialog of Figure 2-37 appears when the OK button is pressed on the Coordinate system dialog.

Figure 2-37: Missing Datum Transformation dialog

Pressing the Define button on this dialog takes you directly to the Define Transform dialog with the needed To/From CRSs defined (Figure 2-37). The upper left section of this dialog gives you the option of setting an identity transform for the From To Datum transformation. This, of course, is going to cause serious errors unless the transform really is identity (or close enough to identity for the accuracy requirements of your project). There are, however, cases where this is true such as the transform from NAD83 (CORS96) to NAD83 (HARN). If the transform truly is identity, set this radio button and OK off the dialog – you are done!



Figure 2-38: Define Datum Transform dialog

In the case of the transform not being Identity (the more usual case), the first step is to select a Path. A path is a sequence of one or more transforms that lead from the From datum to the To datum (these are displayed at the top of the dialog). GeoCue looks up and lists in the first pane of the Define Datum Transform dialog all paths in the GeoCue Transformation database that connect From to To. You can limit the considered path length by setting the Maximum Stages number in the upper left of the dialog. For example, setting this to 2 will cause only the 1 and 2 stage paths to be considered. The general procedure for defining the transformation is to first select a path in the Available Paths section of the dialog. The Path Stages for the selected path will be displayed in the Path Stages central pane of the dialog. The number of rows will correspond, of course, to the path length of the path selected in the first section. Finally, the Stages section of the dialog (bottom pane) will show the available single stage transforms for the currently selected Path Stage. Thus select the path in the first pane, for each path stage in the middle pane, select the desired single stage transform in the lower pane. You can assign this stage by either double clicking the desired stage or setting the check box in the Assigned column. Finally, you can review the parameters of your selected stage by selecting the stage (again, in the Stages section of the dialog) and pressing the Review… button.



For our example (NAD 83 HARN to NAD 83), we will select a single stage path. This shows, of course, only one path in the Path Stages section of the dialog. Finally, the Stage Library lists a myriad of stages since this particular implementation uses a local lookup table. Since our project is in Kentucky, we selected the NAD_1983_To_ HARN_Kentucky transform in the Stage Library. This is illustrated in Figure 2-39.

Figure 2-39: Setting the NAD_83 to NAD_83 HARN transform

Note that if we picked the two stage path (a suboptimal transform for the case of NAD83 to NAD83 HARN), we would need to set a transform stage for each of the two Path Stages. Finally, press OK when you are satisfied with the overall path definition. This will take you bake to the Missing Datum Transform dialog with the transform now defined but not approved (Figure 2-40). Since we carefully set up our transform, we probably will exit the dialog by pressing Approve. However, if you are not sure that the transform is correct, you may want to leave the transform unapproved to allow an expert in your organization to perform a review. An unapproved transform will be fully functional in GeoCue but will carry the warning icon to remind you to validate correctness of the transform.



Figure 2-40: The Datum is now defined but not yet approved

2.8.11 Creating a New Transform Path There are often occasions when GeoCue cannot determine an initial list of paths for creating a transform chain (in fact, this will always be the case the first time you define a custom Coordinate Reference System by using a datum tag). In these cases, you will need to define the transform path. We will examine this process by adding a CRS to a project where GeoCue does not have an initial path. For our example, we will add a NAD83 (CORS96) layer to a project whose Project CRS is NAD83 State Plane Kentucky North (feet). GeoCue does not have a predefined transform path from NAD 83 (CORS96) to NAD 83 (in the absence of a tag on NAD 83, one should generally assume the original realization of 1986). We begin by creating a new layer in the project. Figure 2-41 depicts the selection of the CRS for this new layer.



Figure 2-41: Selecting the NAD83 (CORS96) CRS

When we press OK on the Create Layer dialog (Figure 2-42), GeoCue pops up the Missing Datum Transform dialog (Figure 2-43) because it cannot determine a default datum transform from NAD83 (1986) to NAD83 (CORS96). Pressing Define… on this dialog takes us to the Define Datum Transforms dialog (Figure 2-44) but this time with no paths recognized by GeoCue. Thus in this example, we will have to start from scratch with a path definition.



Figure 2-42: The Create Layer dialog just before 'OK'

Figure 2-43: The Missing Datum Transform dialog indicating the missing CORS96 to NAD83 (1986)

transform



Figure 2-44: Define Datum Transform with no recognized paths

We know (and this is outside the scope of GeoCue support – see your company’s geodesy expert!) that that:

1. NAD 83, CORS96 is, for all but sub-centimeter work, equivalent to NAD83 HARN 2. The best transform from NAD 83 HARN to NAD 83 (1986) is via a local state HARN

lookup table This tells us we need to define a two stage transform. We begin by pressing Create Path.. at the top of the Define Datum Transforms dialog. This invokes the Create Path dialog (Figure 2-45) with the full path From and To datums filled in at the upper right of the dialog.



Figure 2-45: The Create Path dialog

The stage 1 From datum is pre-populated (in our example with NAD_83_CORS96). We need to define our first stage as moving to NAD83 HARN. Thus we select this datum from the drop-down To Datum list (Figure 2-46).



Figure 2-46: Selecting an intermediate datum

Now press “Add Path Stage” to add this first stage of the path to the Path Stages section of the dialog. The second stage will be from HARN to NAD 83. Since this will be our final stage, we can simply press “Add Final Path Stage” to add this to the path section. The result is depicted in Figure 2-47. Note that the first stage (CORS96 to HARN) has located no transforms in the GeoCue transformation library. The second stage has located 46 possible transforms.



Figure 2-47: The completed path definition

Thus on the CORS96 to HARN stage, we will have to define a transform. The Define Transform dialog is invoked by pressing the Add button in the lower right section of the dialog. This brings up the Create Data Transform Stage dialog (Figure 2-48). Since we intend to use a unity transform, we accept the default Geocentric transform with zero translation. Press OK on the dialog.



Figure 2-48: The Create Datum Transform Stage dialog

We are now returned to the Create Path dialog with one Stage choice now defined for the CORS96 to HARN transform.

Figure 2-49: The result of defining the CORS96 to HARN transformation stage



Our final step is to select the transform definition for the second stage of our transform. Click the second stage in the upper pane of the dialog and note that the 46 possible stages found in the GeoCue transformation library are listed. For our example, this is a list of the state by state lookup tables. Select the lookup table for Kentucky by either double clicking the entry or checking the Assigned checkbox. This completes the path definition (Figure 2-50).

Figure 2-50: The completed transform path

Click OK to revert to the Define Datum Transform dialog. Notice that your newly defined path has been added to the list in the Available Paths section of the dialog. Additionally, any other paths that GeoCue can construct using any of your newly defined datum stage will be added. In our example, GeoCue was able to construct a three stage path using the newly defined CORS96 HARN transform. Select the 2 stage transform we just defined You can now OK out of the stacked dialogs.



2.9 Layer Opacity We have added the ability to set an opacity level on a layer basis. This feature applies to both vector and raster layers. Opacity is set on the Display tab of a layer’s properties. To access layer properties, select a layer or layers and press the Layer Properties tool on the main Table of Contents (TOC) toolbar (Figure 2-51).

Figure 2-51: Layer Properties tool

Select the Display tab and check the Opacity Enabled box (Figure 2-52). Each time you slide the slider control (or press the +/- buttons), and release the slider, the current opacity will be applied to the layer. Note in Figure 2-52 that we have set opacity to 26% on the LAS layer, resulting in a semi-transparent fill symbology for the layer.

Figure 2-52: Setting Opacity

If you subsequently disable the Opacity option for a layer, the current setting is remembered.



You can set the opacity for multiple layers simultaneously by selecting all desired layers prior to invoking Layer Properties. 2.10 Disable Image Enhancements It is often useful to be able to disable GeoCue’s image enhancement settings for all images on a layer (or layers) at once. This is typically used in workflows such as Ortho QC where the actual contrast and gamma of an image needs to be observed. This can be achieved from the Display tab of layer properties (see section 2.9). 2.11 On-The-Fly Display Chain Image Reprojection GeoCue support on-the-fly reprojection of images. This means that multiple layers of imagery, all on layers of differing Coordinate Reference Systems (CRS), can be simultaneously displayed in GeoCue. As with all GeoCue layers, the only requirement is that a CRS transformation be defined between the layer and the current Map View CRS. All transforms will exist if the Map View CRS is set to the Project CRS since GeoCue requires that a transform be defined between every layer and the Project CRS. NOTE: To ensure reasonable display performance when manipulating the Map View (zoom, pan, etc.), GeoCue uses an approximate transformation (an affine transform) between raster layers and the current Map View CRS. For this reason, you may observe misalignments between rasters and vectors or raster and rasters when zoomed out to extreme levels.

When digitizing or measuring on a raster layer, always set the Map View CRS the same as the raster CRS. This results in a unity (or no) transform between the raster layer and the Map View. Since vector layers are always rigorously transformed, this will ensure that you are digitizing and/or measuring at full accuracy.

2.12 GeoCue Easter Eggs GeoCue contains a number of “non-obvious” commands (usually keyboard activated) for recovery operations or command modification. These features are listed below:

1. Ctrl-Key down when dialog is opening resets default size/location



2. Ctrl-Key AND Shift-Key down when clicking any toolbar button command will reset command mode to “Select” (useful when XC crashes and leaves GeoCue Client locked waiting on XC to release)

3. While in Draw Ellipse command: a. Default is to draw fitted ellipse b. Shift-Key draws fitted circle c. Ctrl-Key draws fitted ellipse with ellipse center at first data point, d. Ctrl-Key AND Shift-Key draws fitted circle with center at first data point.

4. While in any drawing command, hold down the Alt key to snap to the nearest vertex of existing geometry

5. Pressing any letter after selecting a row in the legend will automatically find and select the next row beginning with that letter.

6. Ctrl-Key down when starting GeoCue will reset default size/location and NOT Auto-Open last project (if this option is selected in GeoCue options)

7. Ctrl-Key down when starting Layer Properties will allow changing Layer Coordinate System. (same as Repair Tools.

8. Ctrl-Key down when wheel zooming will do a fast zoom. 9. Double-clicking Layer in legend will display Layer Properties. 10. Double-clicking Raster Row in legend will display Raster Properties. 11. Double-clicking Folder Row in legend will expand/collapse folder. 12. Ctrl-Key down when selecting entities in map will append to select queue (or unselect

entities if previously selected) 13. Ctrl-Key down when “Flashing” the current queue entity will also “Navigate To” that

entity using the current navigation mode. 14. Ctrl-Key down when opening a project will load the TOC like it’s the first time in project.

Gives user opportunity to create a “New” Layout with default settings. 15. Ctrl-Key down in Queue Playback mode will disable image enhancements (boost

playback speed). 16. Multi-selecting rows in TOC/Entity Manager and clicking checkbox will toggle checkbox

for all selected rows. 17. Ctrl-Key down when starting User Manager from pull-down menu will run the old Non-

Web version of User Manager. 18. Ctrl-Key down when digitizing a shape is the same as a double-click data point. Allows

better precision. 19. Shift-Key in Map View enables LP360 Zoom and Pan Mode. Left mouse button zooms,

right mouse button pans. 20. Ctrl-A in many grids will select all rows in the grid. 21. Ctrl-Key down while closing a project will save the entire Active Layout from scratch to

match the existing state of the TOC.



3 Command Dispatch System (D) We have introduced a number of new features in the Command Dispatch System for GeoCue version 2011.1 In addition, we have simplified or removed features that were designed for specific purposes that are no longer needed.

3.1 Improved Cloud Configuration It is much easier to configure Clouds (local processing machine clusters) in GeoCue 2011.1. The Clouds tab of Dispatch Manager now has an Add (or Clone if you select an existing cloud) button that enables a machine selection dialog (Figure 3-1). Simply add and remove machines from the configuration using the Add/Remove tools.

Figure 3-1: Modifying a Processing Cloud

Note that all machines are added with 100% Processor resources assigned to the cloud. You can modify this assignment using the lower pane of the Clouds tab in Dispatch Manager.



Visualizing Machine – Cloud assignments is now made more visual via highlighting in Dispatch Manager (See Figure 3-2, Figure 3-3).

+

Figure 3-2: Machine to Cloud Mapping



Figure 3-3: Cloud to Machine Mapping

3.2 Dynamic Cloud Reconfiguration at the Subtask Level You can now dynamically reconfigure a Cloud, even when subtasks are queued against the cloud. For example assume you have configured a cloud called “LIDAR” with machines A, B and C. You now invoke a 2,000 tile TerraScan macro run. The CDS will queue up the 2,000 tiles and load them into machines A, B and C for processing (the number per machine depends on how you have configured each machine with respect to the CDS as well as the number of Distributed Subtask Licenses you have available. If we assume one macro per machine, you will see three simultaneous subtasks running (1 each on A, B and C). If you now add machine D to the “LIDAR” cloud, the CDS will perform a reconfiguration, on the fly, of the queued subtasks and you will see that there are now 4 simultaneous subtasks running for the Apply Macro step. This reconfiguration occurs under all circumstances of machines being added and removed from Clouds. Thus if you have set machine D to be “off-line” from 2 AM to 4 AM each day (perhaps for maintenance), machine D will be gracefully removed and added back to the Cloud.



3.3 Dynamic All Machines Cloud We have added a new system cloud called “All Machines.” This cloud automatically adds and removes all machines that are available in your GeoCue system. The advantage of this is if you add a new Client or remote node machine to your GeoCue Departmental Server, it will be automatically added to the “All Machines” Cloud.

3.4 Automatic Cloud Selection and Processing In the spirit of “Button Clicks cost money” in production scenarios, we have added automatic cloud selection and dispatch to this new release of GeoCue. A “Cloud” is a configuration of machines grouped together and provided a familiar name (e.g. “LIDAR Cluster”, “Ortho Cloud”). When dispatching in GeoCue, you can send the dispatched command to a set of user selected machines or to a cloud. With the new automatic mode, you can set projects such that dispatches are sent directly to a default cloud without the need to interact with the Dispatch dialog.

3.4.1 Dispatching to a default Cloud If, in any Dispatchable Command, the Dispatch Selection Icon shows a cloud,

then automatic cloud selection mode is enabled for this action. Pressing In-Progress from the Checklist Toolbar or “OK” from a dialog that supports dispatch will automatically invoke the command using the default cloud rather than displaying the intermediate machine/cloud selection dialog. Hovering the mouse pointer over the cloud icon will display the default cloud for the current command.



3.4.2 Assigning Default Clouds Default Clouds can be assigned at three levels in GeoCue; Checklist, Command and Project When processing to a default cloud, the Command Dispatch System first examines the Checklist Step for a default cloud. If one is not assigned at this level, it next checks the Command configuration (set in Environment Builder). Finally, it checks the Project for a default cloud assignment. A default processing cloud can be assigned at the checklist step level using the Checklist tab in Environment Builder (see Figure 3-4)

Figure 3-4: Assigning a default cloud at the Checklist Step level

A default processing cloud can be assigned on a per command basis using the Command tab of Environment Builder (New/Modify Command dialog). The default cloud is assigned in the Command Dispatch Settings section of the dialog (Figure 3-5).



Figure 3-5: Assigning a Default Cloud on a per command basis

A default cloud can also be assigned at the GeoCue Project level when a new project is created (Figure 3-6) or via the Project Properties dialog after project creation (Figure 3-7).



Figure 3-6: Assigning a default Cloud during project creation



Figure 3-7: Assigning or Modifying the default Cloud via Project Properties

If you do not want automatic cloud dispatching enabled, do not assign a cloud at either the Command or the Project levels. This will force the dispatch mode selector to the normal, interactive dispatch mode.

3.4.3 Cloud Precedence When a command (“Task”) is to be dispatched in GeoCue, the Checklist Step is first examined to see if a Cloud has been assigned (Checklist tab in Environment Builder). If a Cloud is assigned at this level, it becomes the dispatch target. If a Cloud has not been assigned at the Step level, the command properties are next examined (Figure 3-5). If a default Cloud has been assigned at this level, it will become the target for the automatic cloud dispatch mode, regardless of Project settings.



If a default cloud has not been assigned at the command level, then the default cloud setting for the Project is examined. If a value has been set for this parameter, then this cloud becomes the default cloud for the task that is being dispatched. If a default cloud has not been assigned at the command or the project level, automatic cloud selection is disabled and the user must interactively select machines or a cloud via the Dispatch Dialog. The overall selection process is depicted in Figure 3-8

Figure 3-8: Selecting the default processing Cloud

3.5 Auto Run Next Step Supports Default Cloud Dispatch All external commands and certain internal commands (e.g. Run Macro, Generate Image,…) can be the targets of “Auto Run Next Step” in a checklist (configured in Environment Builder). In the previous version of the Command Dispatch System, these commands always had to follow a “batch” command and always ran on the same machine or machine group as the driving command (the one with Auto Run Next Step set). Now these commands will run on the default cloud associated with the command/project.

Yes

Cloud Assigned At Cmd. Level?

Cloud Assigned At

Project Level?

Dispatch to Cmd Cloud

Select Machines/ Cloud via Dispatch Manager

No

No

Yes

Dispatch to Project Cloud

Yes

Cloud Assigned At Step. Level?

Dispatch to Step Cloud

No



Auto Run Next Step is configured in the checklist pane of Environment Builder, Modify Checklist. Note that the Auto Run Next Step attribute is set on the step that precedes (in state engine terms) the step you wish to automatically dispatch to the cloud. Note in Figure 3-9 that we are setting the Auto Run Next Step property on the “Assign Macro” step.

Figure 3-9: Setting Auto Run Next Step

The target of the Auto Run Next Step is determined by the “Select Step” setting on the checklist step for which Auto Run Next Step has been set. In our Assign Macro example, we have set the Assign Macro “Select Step” to “Run Macro” (see Figure 3-10). Note that the Select Target must be a member of the COMPLETE Targets list for Auto Run Next Step to function.

Figure 3-10: Target of Auto Run Next Step

In addition, GeoCue 7.0 did not support setting Auto Run Next Step on an interactive command (such as Set Image Parameters). This is now supported so long as the target command (or project) has been configured with a default cloud.



3.6 Inter-Checklist Step Linking Supports Auto Run GeoCue 2011.1 supports a new set of features generally entitled “Inter-Checklist Linking” or ICL. This is an advanced capability that will begin to be used within GeoCue workflows with release 2011.2. In the meantime, it is fully functional for users who create/modify their own checklists. The general use of ICLs will be documented in the Environment Builder Guide. Inter-Checklist Linking enables a step on one type of checklist to depend in various ways on a step on a different checklist. For example, you might have an Ortho entity with a checklist step called Rectify. You could use an ICL to link this step to the QC step on a separate DEM entity (or entities) that are to be used by the Rectify step. Using ICL, a dependency can be established such that the Rectify step on the Ortho entity cannot be executed until the QC step on the DEM entity has been successfully completed. In addition to simple inter-checklist step dependencies, ICL can also be used to Auto Run checklist steps. In the above scenario, you could set the Auto Run property on the Rectify step such that Rectify would automatically dispatch to its default cloud when the DEM QC step transitions to Complete. ICL relationships are set on the Checklist tab of Environment Builder, under Modify Checklist. An example is depicted in Figure 3-11. Here we have established a link from a LIDAR Ortho to a LAS tile (a LIDAR data processing tile). The LIDAR ortho is generated from LAS data in the LAS tile. Thus the Generate step cannot occur until the Populated step on the LAS tile is complete.

Figure 3-11: Setting Auto Run for an ICL-triggered Step

The ICL fields depicted in Figure 3-11 perform the functions listed in Table 3-1.

Note: If a default cloud is set at the project level (a GeoCue best practice), then this cloud becomes the default cloud for every command executed in the context of the project unless a default cloud has been specifically set at the command level.



Table 3-1: ICL Properties ICL Option Name Function Input ICL The link (see GeoCue linking in the Environment Builder

guide) that connects one entity to another Input ICL Logic A link can have a many to one relationship. AND means

all linked objects must be Compete before this step can proceed. OR means only one need be complete.

On Input ICL Reset The action to take if the linked entity’s checklist transitions from Complete back to some other state (e.g. Not Started, Exception, …). This is used for error back propagation.

Input ICL Auto Run If checked, this step (assuming its Intra-checklist prerequisites are met) will auto run with the ICL driving step completes. A default cloud must be defined for this action to occur.

Input ICL Warning Same as Complete

This is used in controlling error propagation. You may not want this checklist step to treat a Warning state from its driving checklist as an Error.

Output ICL This is the place where the link of the “transmitting” checklist step is placed (e.g. in our example of Figure 3-11, the Output ICL of the LAS Tile’s Populate step would be set to the link connecting the LIDAR Ortho Generate step. Chains are possible so that multiple entity, multiple step configurations can be created.



4 Environment Builder A number of changes have been made in Environment Builder for release 2011.1, primarily in support of managing the new checklist system. Checklists are collections of Checklist Steps that are associated with Entities. You can modify many aspects of a checklist, setting options and vectoring targets. You can also construct entirely new checklists and add those checklists into System supplied environments. Thus, for example, if you need three Process in TerraScan steps that you want to label “Classify Ground”, “Classify Vegetation” and “Set Model Keypoints” you can accomplish this by building a new checklist and associating that checklist with LAS Working Segments.

4.1 Modifying a System Defined Checklist First select the desired checklist in the top table (Checklists) on the Checklists tab of Environment Builder. This will display the associated checklist steps in the second table, Assigned Checklist Steps (Figure 4-1).



Figure 4-1: The Checklist tab of Environment Builder

You can modify most parameters of a system-defined checklist by pressing the Modify Group button to the right of the Checklists table: This will display the Modify Assigned Checklist Steps dialog (Figure 4-2).



Figure 4-2: Modify Assigned Checklist Steps

The Modify dialog allows you to “edit in place.” After performing modifications, press OK to apply.

If you are going to make major modifications to a checklist (adding steps, changing the vectoring behavior) it is a good idea to “clone” the system checklist into a new checklist. This will allow you to easily recover the delivered list.

4.2 Checklist Fields The fields displayed in the Modify Checklist function of Environment Builder are described in Table 4-1. The Modify Checklist table is a single, wide table with the Step name pinned at the left side as you scroll across columns. Groups of columns within the table are color coded to make navigation easier.

Table 4-1: Modifying Checklist Functions Column Function Notes Step - Color The step color that is

displayed by GeoCue Symbology

Read only – Set via the Color ID column

Step - Symbol “A” represents an Automatic (Batch) step whereas “I” is interactive (fired by the user).

Read Only. Toggled by the “Interactive” checkbox



Column Function Notes Step Number Sequential number of this

step. Read Only – note that this does not represent the order in which steps are executed – this is determined by the vector logic.

Name Step Name preceded by a: Square represents a Mandatory step, Round represents an Optional step.

You can rename the step by editing in the name field. This overrides the name specified in the Checklist Step area of Environment Builder. The Mandatory, Optional symbol is controlled by the “Optional” check box field.

Step Key Step Key This is the unique GeoCue key assigned when you create a step in the Checklist Step section of Environment Builder. This is where you actually select the step that will be executed. Thus this is the first field that must be edited when building a new checklist or adding a step. It is selected via a drop-down list. NOTE: A specific Checklist Step can appear only once in a Checklist.

Color ID Override the Checklist Step default color

Pick the desired color from the drop-down. The colors are selected from the Checklist Step master table (accessed from the Checklist Steps tab).

Allow Override Allow the user to enter this step, provided its Predecessor conditions are met, by using the Override Step Sequence button on the Checklist Toolbar

Generally used to do out-of-sequence processing when things go awry. An example might be the need to repopulate working segments in a LIDAR flow. The step will not enable if predecessor conditions are not set.



Column Function Notes Reset to Not Started on Override

You can specify one or more steps in the Checklist. These steps will be set back to their Not Started status if this step is executed via the Override Step Sequence button on the checklist toolbar.

This function allows you to ensure, in your state logic, that the user does not become confused when stepping back in a checklist. An example would be setting Populate to Not Started if Set Population Parameters is run via an override after Populate had already been successfully run.

Reentry Allowed This flag specifies (if checked) that this step can be executed again (if it is the target another step).

This function is used for “fire once” scenarios. For example, you might group three steps and allow the user to execute them in any order. You can use this function to prevent the user from running the same step twice, even if its predecessor condition is valid.

Predecessor Steps One or more steps that must be in the COMPLETE state before this step can be executed.

This is the most fundamental of the Checklist transition rules. It cannot be overridden by any checklist action.

COMPLETE Targets These are the steps that will potentially be enabled when this step transitions to Complete.

Steps will not enable if their predecessor condition is not met or they have already been transitioned to complete and their Allow Reentry flag is not set.

Select Step This is the step that will be selected (when the entity associated with this checklist instance is moved into the working set) from the list of COMPLETE Targets after the associated step completes.

If the Select Target cannot be executed (due to predecessor requirements or the Reentry flag), no step will be Selected. Note that the Select Step must be one of the COMPLETE Targets.

ERROR Targets These are the steps that will enable if the executable associated with this step crashes.

Note that like all steps, the ERROR target must have its predecessor targets complete.



Column Function Notes FAIL Targets These are the steps that

will enable if the user declares a Failure. This is usually initiated via the Fail option of the Checklist Step Completion dialog.

Note that like all steps, the FAIL target(s) must have its predecessor targets complete.

WARNING Targets These are the steps that will be enabled if the executable (or exist dialog) associated with this step declares a Warning.

Note that like all steps, the WARNING target(s) must have its predecessor targets complete.

Intentional Skip Required

This option forces the user to press the Intentional Skip button on the checklist processing toolbar if they want to move past this step without executing.

This effectively sets up an optional checklist step that records an audit trail even if someone does not run the step. It is useful when you need the user to deliberately think about not applying an operation (the fact that this step was intentionally skipped will be recorded in the Checklist history)

INTENTIONALLY SKIPPED Targets

These are the steps that will enable if the user sets the state of the current step to Intentionally Skipped.

Note that like all steps, the INTENTIONALLY SKIPPED target(s) must have its predecessor targets complete.

Interactive Checking this box allows the user to interactively execute this step

The step must be an interactive step as defined in the Step Library

Optional Checking this box causes the Step ion to display as round (optional) rather than square (required)

Note that this is for appearances only since the state logic determines the vectoring. HOWEVER, if you use the Reset function on the Checklist to revert to a linear checklist, this flag is used to set the linear transition logic.

Description Free form text that displays in the description field of the Checklist in GeoCue Client



Column Function Notes Users and Groups Allows you to set

permissions on a per step basis.

This overrides any permissions you may have set on the step in the Checklist Step section of Environment Builder.

Auto Run Next Step4 If this step successfully completes, the COMPLETE Target will automatically move to the In Progress state.

The associated executable of the target step must be an External command or an Auto Run internal command. All predecessor conditions must be met.

Same Machine Used in conjunction with Auto Run Next Step and the Command Dispatch System. If enabled, the auto run step will be queued to run on the same machine as this step.

This is used in application where (for performance reasons) step n writes data to a local resource. For maximum performance, step n+1 needs to run on the same machine.

Default Cloud Overrides cloud assignment at the Command and Project level.

If a cloud is assigned at this level, all other cloud assignments will be overridden and the command will execute on this cloud if dispatched in Automatic mode.

DPMS Import Enables Distributed Project Management System (DPMS) import for this step

Entities can be imported into a GeoCue project via the DPMS. If this check is enabled, a DPMS import of entities with the same Entity ID as the entity associated with this step will have their checklist step synchronized.

DPMS Name The name of this step when in the DPMS workflow

DPMS Key A unique key for matching steps between GeoCue systems.

This DPMS key must be the same on the other GeoCue systems participating in the DPMS network.

4 All “batch” external commands and select CuePac commands can be Auto Run.



Column Function Notes Set Complete on DPMS Import

If an entity is imported via DPMS and it meets key and step criteria, set this step complete.

Guide Links to a document that is used as a user guide for this step.

Guide documents must be stored in the GeoCue Common folder under the folder “Document Library” (subfolders can be created).

Effort Type Interactive or System. Determines which category GeoCue uses for Earned Value Management (EVM) time tracking

Read only – set in the Checklist Step editor via the Interactive checkbox.

Auto Budgeted Effort Enabled

Causes GeoCue to automatically compute Budgeted Effort for the entity associated with this checklist when the entity is created.

Auto Budgeted Effort Type

Absolute = the Auto Budgeted Effort (BE) Value is assigned to the step Computed = the Auto Budgeted Effort is computed based on the size of the associated entity

The actual values are computed and assigned when an entity with this checklist assigned is created.

Auto Budgeted Effort Value

Either an absolute value or a multiplier as determined by the Auto Budgeted Effort Type field

Multiplier set in Effort Type causes GeoCue to compute the BE based on the size of the entity times this value (entity area for polygon entities, entity length for polylines).

Auto Budgeted Effort Units

Specifies the units of the Auto Budgeted Effort Value when using Multiplier mode.

GeoCue automatically converts the Auto Budgeted Effort Value to the correct value based on the units specified in this field and the units of the Layer on which the associated entity is being created.



Column Function Notes Show Time Keeper Display the Time Keeper

when this step is in progress.

GeoCue includes a dialog that allows a user to stop/start the Actual Effort computations. This is useful for situations where the user does not wish to end the underlying application in order to pause time keeping.

On Complete, Display File Alias

Use the specified file alias for the GC Display Raster on Complete

If the associated processing step computes a new image and you wish to use this new image as the image displayed in GeoCue for the entity (applies to Raster entities only), set the new alias.

On Reset, Display File Alias

Use the specified file alias for the GC Display Raster on Reset

This is useful for Raster entities where resetting the step should invalidate the displayed raster (e.g. unwinding a Dodge step).

Input ICL Input Inter-Checklist Link (ICL)

If this checklist step depends on a step in a different checklist, the link/channel from the driving checklist is selected from this dropdown.

Input ICL Logic Set to AND/OR. If multiple entities are connect via this link/channel, AND means that all input links must be True before this condition is True whereas OR implies only one need be True.

On Input ICL Reset The action that should occur on this Checklist step if the linked ICL resets (transitions to Not Started)

Input ICL Auto Run If checked, this step will Auto Run when its ICL input transitions to True and all Prerequisites are met.

Input ICL Warning same as Complete

If set, treat a Warning from the linked step as equivalent to a Complete



Column Function Notes Output ICL Links this step to another

checklist step on a different checklist

Allows cascading of ICL linkages.

System Indicates a GeoCue supplied checklist step

Only limited fields of a System checklist can be modified by the user. Clone the list to obtain full modification ability.

When a checklist is being evaluated by the GeoCue State Engine, the order of priority is as follows:

1. Predecessor – If a step’s predecessor step(s) is not Complete, the step cannot be executed under any circumstances (i.e. it cannot be overridden)

2. If the Override Step Logic button is pressed on the checklist processing toolbar in GeoCue Client, the Predecessor step(s) is/are Complete and the Allow Override option has been checked in the Checklist configuration, the step will enable. Note that this will override the Allow Reentry flag

NOTE: If you add, remove or reorder steps in a checklist that is already assigned to GeoCue entities, you must reassign the checklist using the repair tool, “Checklist Changer” (accessed via the GeoCue Client, Administration menu).



5 LIDAR 1 CuePac New features in the LIDAR 1 CuePac are contained in this chapter. See the LIDAR 1 CuePac User Guide for a full description of all features. 5.1 Support for Standard GPS Time Traditionally, GPS time in LIDAR LAS files and supporting trajectories (such as Applanix’s Smoothed, Best Estimated Trajectory, SBET) have been recorded in GPS week format. Recently systems have introduced “standard” (translated absolute) GPS time. This is a much better format for time since it removes the ambiguity of GPS Week time. When you create a new project in one of the LIDAR environments, an options dialog will appear (Figure 5-1). Select the time format that will be used in the project from the drop-down selector.

Figure 5-1: LIDAR Time format option

If you have set the project as GPS Standard Time, you will need to select a GPS Week each time you import LAS data that is in GPS Week format. A calendar control is used for this selection (Figure 5-2). It is not necessary to know the exact day of the time stamp; any day in the correct week will suffice.



Figure 5-2: Setting GPS Week

5.2 Macro Catalog The TerraScan macro catalog facility has been rewritten in GeoCue 2011.1. Macros that existed in prior versions of GeoCue will be automatically added to the new catalog system. You can import other file-based TerraScan macros using the import facility. You can do this independently of a GeoCue project or when you assign macros in a LIDAR project.



You can access the Macro Catalog Manager independently of a GeoCue project from All Programs ► GeoCue ► LIDAR 1 CuePac ► Manage Macros. This will invoke the dialog of Figure 5-3. Import additional macros into the master list (top section of the dialog) via the Import… button.

Figure 5-3: Manage Macros dialog

Macros are assigned to LAS Working Segments from the Project Level Macro List section of dialog Figure 5-3 (you can directly assign a macro from the Master list which will, as a side effect, add the assigned macro to the Project list – see next section). The idea is to maintain a complete and detailed history of the macros that have been used in a project. The assigned macro is recorded by GeoCue Client in the processing step history. You can use this history and the macro catalog to diagnose problems or to fine tune macros.

5.2.1 Assignment from Master List The macros in the top section of the dialog serve as the template macros. The lower pane of the dialog represents macros that can or have been assigned to the current project. Note that you can immediately Assign macros to working segments by selecting the macro in the top pane and pressing Assign in the lower right of the dialog. This will immediately assign the selected Master catalog entry to the LAS tiles that are in the working set and add the macro to the Project list.



Note that you can modify Macros in the Master list by selecting the macro and pressing Modify (the modify button to the right of the Master list).

5.2.2 Modifying Project-level Macros A typical macro application will involved selecting a template macro from the master list, making some modification to that macro and then applying to the working segments that are currently in the working set. This workflow is accomplished by:

1. Adding a macro from the Master list to the Project list (select the macro in the master list and press Add).

2. Select the desired macro from the project list. a. If the selected macro has not yet been assigned to any working segments in the

project, the Modify button will be enabled and you can directly modify the macro. Otherwise…

b. Press Clone to create a new copy of the macro 3. Modify the desired parameters 4. Assign a new name (if you do not do this, GeoCue will automatically generate a new

name) 5. OK to close the dialog 6. Press Assign to assign the modified macro and exit the macro catalog

5.3 Auto Run Macros You can configure GeoCue to automatically dispatch a LAS working segment for macro processing. This will cause the assigned tile to be dispatched to the default processing cloud immediately upon existing the Assign Macro step. See the Command Dispatch System chapter of this document for instructions on configuring your checklist to enable this action.

Configure your LAS Working Segment checklist such that it automatically runs the “Run Macro” step. Add your most common macros to the Master List section of the Macro Catalog. With this configuration, you can select a macro in the Master list and press Assign. The Macro catalog dialog will dismiss with your macro assigned. The Command Dispatch System will immediately distribute the tiles involved in the assignment to the default processing cloud (see the Command Dispatch System chapter for details).

Date post:	20-Apr-2020
Category:	Documents
Upload:	others
View:	2 times
Download:	0 times

New Features in GeoCue 2011.1 Products (R6)...

Documents