WorkingwithGeoMedia PDF

Working with GeoMedia®
Working with GeoMedia

DJA0628D0
SJ**509 (6.1)
Warranties and Liabilities
All warranties given by Intergraph Corporation about software are set forth in the End User License
Agreement and Limited Product Warranty (“EULA”) provided with the software, and nothing stated in or
implied by this document or its contents shall be considered or deemed a modification or amendment of
such warranties.
The information and the software discussed in this document are subject to change without notice and
should not be considered commitments by Intergraph Corporation. Intergraph Corporation assumes no
responsibility for any error that may appear in this document.
No responsibility is assumed by Intergraph for the use or reliability of software on equipment that does not
meet the specified requirements as found in the product Readme.
Trademarks
Intergraph and GeoMedia are registered trademarks of Intergraph Corporation. Windows and Windows
Vista are registered trademarks of Microsoft Corporation. MapInfo is a registered trademark of MapInfo
Corporation. Dynamap/2000 is a registered trademark of Tele Atlas North America, Inc. FLEXlm is a
registered trademark of Macrovision Corporation. Oracle is a registered trademark of Oracle Corporation.
All other brands and product names are trademarks of their respective owners.
Copyright
© 1998-2008 Intergraph Corporation. All Rights Reserved.
Including software, file formats, and audiovisual displays; may be used pursuant to applicable software
license agreement. Contains confidential and proprietary information of Intergraph and/or third parties,
which is protected by copyright and trade secret law, and international treaty, and may not be provided or
otherwise made available to end users other than purchaser without proper authorization from Intergraph
Corporation.
The software discussed in this document is furnished under a license and may be used or copied only in
accordance with the terms of the accompanying license. Because these documentation files are delivered
as PDF files, an industry-standard format, most photocopy vendors can print them for you from the PDF
file. You have permission to make two hardcopies per license for your internal, non-commercial use.
Purchaser shall not have reproduced more than two hardcopies per license without prior written permission
from Intergraph Corporation.
Copyright for the Canadian National Transformation Version 2 Software: ©1995. Her Majesty the
Queen in Right of Canada, represented by the Minister of Natural Resources. Produced under licence from
Her Majesty the Queen in Right of Canada, represented by the Minister of Natural Resources. Software
based on the National Transformation Version 2 developed by Geodetic Survey Division, Geomatics
Canada.
Copyright for Dynamap/2000 ©2002-2005 Tele Atlas North America, Inc. This product contains
proprietary and confidential property of Tele Atlas North America, Inc. Unauthorized use, including
copying for other than testing and standard backup procedures, of this product is expressly prohibited.
U.S. Government Restricted Rights Legend
Software is subject to the U.S. Export Regulations. Any diversion of the software that is contrary to U.S.
law is prohibited.
Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian
agencies: This was developed at private expense and is “restricted computer software” submitted with
restricted rights in accordance with subparagraphs (a) through (d) of the Commercial Computer Software -
Restricted Rights clause at 52.227-19 of the Federal Acquisition Regulations (“FAR”) and its successors,
and is unpublished and all rights are reserved under the copyright laws of the United States. For units of
the Department of Defense (“DoD”): This is “commercial computer software” as defined at DFARS
252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3.
Unpublished – rights reserved under the copyright laws of the United States.
Terms of Use
Use of this software product is subject to the EULA delivered with this software product.
Intergraph Corporation
Huntsville, Alabama 35813-0001
What do you think about Working with GeoMedia?
DJA0628D0
We would like your opinion of this document. Please help us improve our documentation by completing this
questionnaire. Write your comments or circle your responses to the questions. Circle all responses that apply, and
include additional pages of comments if you wish. When you have completed the questionnaire, fold and mail it to
Intergraph. Postage is prepaid. Thank you for taking the time to let us know what you think.
1. How much of this document have you worked through? 1. 1 - 2 - 3 - 4 - 5

(1=entire document, 2=most of it, 3=about half, 4=about one-third, 5=one-fourth or less)
2. How easy was this document to read and understand? 2. 1 - 2 - 3 - 4 - 5

(1=difficult . . . 5=easy)
3. How easy was it to find specific information in this document? 3. 1 - 2 - 3 - 4 - 5

(1=difficult . . . 5=easy)
4. What was your primary intent in using this document? 4. 1 - 2 - 3 - 4 - 5

(1=orientation . . . 5=thorough understanding)
5. How well did this document satisfy this intent? 5. 1 - 2 - 3 - 4 - 5

(1=poorly . . . 5=very well)
6. Have you used Intergraph software before? (1=yes, 2=no) 6. 1 - 2
7. What percentage of your work time is spent using Intergraph software? 7. 1 - 2 - 3 - 4 - 5

(1=10% or less, 2=25%, 3=50%, 4=75%, 5=90% or more)
8. How would you rate your level of software use? 8. 1 - 2 - 3 - 4 - 5

(1=demanding . . . 5=casual)
9. Did this document help you learn to use the software in a satisfactory way? 9. 1 - 2
(1=yes, 2=no)
10. How would you rate this document overall? (1=poor . . . 5=excellent) 10. 1 - 2 - 3 - 4 - 5
11. Have you used Intergraph documentation before? (1=yes, 2=no) 11. 1 - 2
12. Please describe and note page numbers of any errors or inconsistencies in this document.
13. How would you improve this document?
Name Date
Organization Phone
Address
City State Zip Code
Thanks again for your time and effort.
--------------------------------------------------------------------------------------------------
BUSINESS REPLY MAIL

FIRST CLASS MAIL PERMIT NO. 9079 HUNTSVILLE, AL
POSTAGE WILL BE PAID BY ADDRESSEE
Security, Government & Infrastructure (SG&I) Division

Manager, Technical Documentation
Mail Stop IW17B1
P.O. Box 6695
Huntsville, AL 35813-0001
--------------------------------------------------------------------------------------------------
Table of Contents
Start Here .................................................................................................................................... 1-1
Looking at GeoMedia: An Overview.................................................................................... 1-1
What You Need to Know to Work......................................................................................... 1-2
Documents Provided .............................................................................................................. 1-2
Getting Started ....................................................................................................................... 1-6
Getting Around in the Software ............................................................................................. 1-6
Customizing the Menus and Toolbars.................................................................................... 1-7
The Product Workflow........................................................................................................... 1-9
What is a GIS? ....................................................................................................................... 1-9
Working with GeoWorkspaces................................................................................................. 2-1
Creating a GeoWorkspace...................................................................................................... 2-1
Opening a GeoWorkspace...................................................................................................... 2-2
Delaying Data Loading .......................................................................................................... 2-3
Automatically Backing Up GeoWorkspaces.......................................................................... 2-4
Saving, Closing, and Copying a GeoWorkspace ................................................................... 2-4
E-Mailing a GeoWorkspace................................................................................................... 2-5
Creating a GeoWorkspace Template...................................................................................... 2-6
Linking and Embedding a GeoWorkspace............................................................................. 2-7
Working with Coordinate Systems .......................................................................................... 3-1
Defining a Coordinate System for a GeoWorkspace ............................................................. 3-5
Defining a Coordinate System for a Feature Class ................................................................ 3-7
Matching GeoWorkspace and Default Warehouse Coordinate Systems ............................... 3-9
Getting Coordinate Readouts ............................................................................................... 3-11
Setting Units and Formats.................................................................................................... 3-12
Configuring for Datum Transformations ............................................................................. 3-14
Displaying Data That Has No Coordinate System Specified............................................... 3-15
Creating Coordinate-System Files from Design Files.......................................................... 3-19
Working with Warehouses........................................................................................................ 4-1
Creating a Read-Write Access Warehouse ............................................................................ 4-3
Defining a Coordinate System for a Warehouse.................................................................... 4-4
Preparing to Connect.............................................................................................................. 4-4
Working with Connections .................................................................................................. 4-14
Viewing Changes in a Multi-User Environment.................................................................. 4-18
Creating an Access Warehouse Template............................................................................ 4-19
Changing the Coordinate System of a New Access Warehouse Template .......................... 4-19
Configuring PickLists with Access Warehouses ................................................................. 4-20
i
Working with Images ................................................................................................................. 5-1

Inserting Images into Warehouses ......................................................................................... 5-1
Managing Warehouse Images ................................................................................................ 5-8
Changing the Raster Image Display..................................................................................... 5-12
Creating Image Footprints.................................................................................................... 5-15
Displaying Selected Images ................................................................................................. 5-17
Working with Map Windows ................................................................................................... 6-1
Controlling the Map Window ................................................................................................ 6-2
Working with Styles............................................................................................................. 6-12
Working with Legends......................................................................................................... 6-36
Creating Additional Map Windows ..................................................................................... 6-65
Displaying CAD Files .......................................................................................................... 6-76
Working with Data Windows ................................................................................................... 7-1
Opening a New Data Window ............................................................................................... 7-1
Controlling the Data Window ................................................................................................ 7-3
Editing Cells in the Data Window ......................................................................................... 7-6
Taking a Snapshot of the Data Window................................................................................. 7-8
Working with Features ............................................................................................................. 8-1
Understanding Geometry Types ............................................................................................ 8-1
Working with Feature Classes ............................................................................................... 8-2
Outputting Feature Data to Warehouses .............................................................................. 8-10
Selecting Features in the Map Window ............................................................................... 8-17
Inserting Features into a Feature Class ................................................................................ 8-23
Inserting Text Features into a Feature Class ........................................................................ 8-25
Editing Text.......................................................................................................................... 8-27
Selecting and Searching for Text ......................................................................................... 8-30
Adding Hypertext to a Feature Class ................................................................................... 8-31
Adding Geometry................................................................................................................. 8-34
Changing Attribute Values of Features................................................................................ 8-35
Changing and Deleting Features .......................................................................................... 8-38
Working with Categories ..................................................................................................... 8-41
Working with Catalogs ............................................................................................................. 9-1
Catalog Features..................................................................................................................... 9-2
What Is Geospatial Metadata? ............................................................................................... 9-3
Updating Metadata Databases for GeoMedia 6.0 or Higher .................................................. 9-7
Creating a New Catalog ......................................................................................................... 9-7
Creating a New Catalog Connection...................................................................................... 9-9
Managing Catalog Connections ........................................................................................... 9-10
Importing Catalog Records .................................................................................................. 9-13
Exporting Catalog Records .................................................................................................. 9-15
ii
Table of Contents
Associating Catalog Records ............................................................................................... 9-21

Exploring Catalogs............................................................................................................... 9-26
Sample Catalog Explorer Workflows .................................................................................. 9-37
Glossary of Catalog Terminology ........................................................................................ 9-38
Software Delivery ................................................................................................................ 9-39
Analyzing GeoMedia Data ...................................................................................................... 10-1
Working with Filter Queries ................................................................................................ 10-1
Working with Native Queries ............................................................................................ 10-18
Manipulating Queries......................................................................................................... 10-26
Working with Spatial Filters .............................................................................................. 10-30
Querying Graphics-Only Features in MGE and MGSM.................................................... 10-43
Working with Queued Edit ................................................................................................ 10-44
Working with Searches ...................................................................................................... 10-55
Working with Joins ............................................................................................................ 10-62
Analyzing Geometry .......................................................................................................... 10-65
Placing Buffer Zones Around Features.............................................................................. 10-70
Working with Functional Attributes .................................................................................. 10-72
Merging Feature Classes and Queries................................................................................ 10-83
Aggregating Data ............................................................................................................... 10-88
Generating Base Geometry ................................................................................................ 10-97
Selecting Attributes.......................................................................................................... 10-100
Combining Feature Classes and Queries.......................................................................... 10-103
Linear Referencing .................................................................................................................. 11-1
What is Linear Referencing?................................................................................................ 11-1
Linear Referencing and Geospatial Technology .................................................................. 11-2
LRS Linear Features and Event Data................................................................................... 11-4
Linear Referencing Commands............................................................................................ 11-6
Working with Labels ............................................................................................................... 12-1
Inserting Labels.................................................................................................................... 12-1
Inserting Leader Lines.......................................................................................................... 12-5
Resolving Text Conflicts...................................................................................................... 12-9
Geocoding ................................................................................................................................. 13-1
Geocoding and Finding Addresses....................................................................................... 13-1
Address Geocoding - User Concepts ................................................................................... 13-4
Finding an Address .............................................................................................................. 13-7
Geocoding Multiple Addresses .......................................................................................... 13-12
Defining Parsing Rules ...................................................................................................... 13-19
Geocoding Coordinates...................................................................................................... 13-23
iii
Working with Layout Windows .............................................................................................. 14-1

Layout Window Overview................................................................................................... 14-1
Starting the Layout Window ................................................................................................ 14-4
Inserting Layout Sheets........................................................................................................ 14-4
Importing Layout Sheets and Layout Templates ................................................................. 14-5
Exporting Layout Sheets and Templates.............................................................................. 14-9
Selecting and Manipulating Layout Sheets........................................................................ 14-12
Renaming Layout Sheets.................................................................................................... 14-12
Deleting Layout Sheets ...................................................................................................... 14-13
Viewing Background and Working Sheets ........................................................................ 14-13
Viewing Layout Window Properties.................................................................................. 14-14
Manipulating Layers .......................................................................................................... 14-15
Designing Map Layouts for Printing in the Layout Window .............................................. 15-1
Designing Map Layouts Overview ...................................................................................... 15-1
Map Window Considerations When Printing from the Layout Window............................. 15-1
Basic Map Layout Workflows ............................................................................................. 15-6
Components of the Map Layout........................................................................................... 15-8
Workflows for Placing Map Graphics Using Layout Frames............................................ 15-42
Workflows for Placing Map Graphics Without Using Layout Frames.............................. 15-48
Updating Map Graphics in Layout Sheets ......................................................................... 15-62
Modifying Map Graphics in Layout Sheets ....................................................................... 15-64
Inserting Cartographic Grids.............................................................................................. 15-78
Inserting Reference Grids and Indexes .............................................................................. 15-91
Inserting a Data Table ........................................................................................................ 15-97
Printing in GeoMedia .............................................................................................................. 16-1
Printing Overview ................................................................................................................ 16-1
Defining the Map Window Page Setup................................................................................ 16-1
Printing a Map Window ....................................................................................................... 16-3
Printing to a File................................................................................................................... 16-4
Defining the Data Window Page Setup................................................................................ 16-5
Printing a Data Window....................................................................................................... 16-7
Defining the Layout Window Page Setup............................................................................ 16-8
Printing Layout Sheets from the Layout Window ............................................................. 16-10
Plotting ............................................................................................................................... 16-15
Printing Transparent or Translucent Graphics ................................................................... 16-16
Outputting PDF from GeoMedia ....................................................................................... 16-17
Working with Libraries .......................................................................................................... 17-1
Creating a New Library........................................................................................................ 17-2
Creating a New Library Connection .................................................................................... 17-3
Managing Library Connections............................................................................................ 17-7
Organizing Libraries ............................................................................................................ 17-9
iv
Table of Contents
Exporting Data to Other Systems .......................................................................................... 18-1

Exporting to Shapefile.......................................................................................................... 18-1
Exporting to MapInfo Interchange Format .......................................................................... 18-5
Exporting to Design File ...................................................................................................... 18-8
Exporting to AutoCAD ...................................................................................................... 18-17
Exporting to GML.............................................................................................................. 18-21
How to Reach Intergraph ........................................................................................................ A-1
Electronic Self-Help Support ................................................................................................ A-1
Frequently Asked Questions (FAQs) .................................................................................... A-1
GeoMedia 6.1 Release Notes and Issues Resolved............................................................... A-1
Coordinate System Information...............................................................................................B-1
Projection Algorithms ............................................................................................................B-1
Datum Transformation Models ..............................................................................................B-1
Standard Geodetic Datums.....................................................................................................B-9
Named Geodetic Datums .....................................................................................................B-11
Vertical Datums ...................................................................................................................B-12
Ellipsoids..............................................................................................................................B-12
Units of Measure (UOM) .....................................................................................................B-14
State Plane Zone Codes—NAD27 and Old Island Datums .................................................B-16
State Plane Zone Codes—NAD83 Datum ...........................................................................B-17
UTM Zones ..........................................................................................................................B-20
GeoTIFF Capabilities...........................................................................................................B-21
Raster Information ................................................................................................................... C-1
Raster Formats Supported in GeoMedia ................................................................................C-1
Compression Techniques .......................................................................................................C-3
Tiling......................................................................................................................................C-4
Data Types .............................................................................................................................C-4
File Types and Categories Listed for Inserting a Georeferenced Image ................................C-5
Layout Window Graphics Commands ................................................................................... D-1
Conversion Tables .....................................................................................................................E-1

International System of Units to United States Customary System....................................... E-1
United States Customary System to International System of Units....................................... E-2
Catalogs: Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers ................. F-1
Creating a Catalog Using Oracle............................................................................................ F-1
Server Database Upgrades ..................................................................................................... F-5
Creating a Catalog Using MS-SQL Server ............................................................................ F-7
v
LRS Data Structures ................................................................................................................. G-1

Overview............................................................................................................................... G-1
Single-Level LRS Data Structures ........................................................................................ G-1
Event Data Structures.......................................................................................................... G-12
Supported SVG Element Types................................................................................................ H-1
Background ........................................................................................................................... H-1
Discussion ............................................................................................................................. H-1
Supported Types ................................................................................................................... H-2
Geometry Elements............................................................................................................... H-5
Common Attributes............................................................................................................. H-11
SVG Symbol Metadata XML Schema ................................................................................ H-15
Example .............................................................................................................................. H-20
Additional Geocoding Information ...........................................................................................I-1
Address Geocoding - Administrator Concepts and Workflows.............................................. I-1
Geocoding Models and Parsing Rules .................................................................................. I-15
Intersection Geocoding ......................................................................................................... I-24
Sound Like Algorithm........................................................................................................... I-26
File Types.................................................................................................................................... J-1
Index .......................................................................................................................................... IN-1
vi
Start Here
Welcome to GeoMedia®—the next generation in geographic-information systems (GIS).
Based on Jupiter technology from Intergraph Corporation, this product is an enterprise
GIS for the Windows® XP, Windows Vista®, or later operating systems.
As a viewing and analysis tool, this product allows you to combine geographic data from
different sources, in different formats, and with different map projections, all into a single
environment. Using this product, you can perform complex queries on spatial and
attribute data from various sources, and produce numerous views of highly sophisticated
maps in a single GeoWorkspace. Furthermore, this product gives you the capability of
printing those map views on a single sheet and adding borders, marginalia, and other
finishing touches.
++This product is also a software-development environment, and you can customize it
with standard Windows-development tools such as Microsoft® Visual Basic® and Visual
C®.
Looking at GeoMedia: An Overview

The first thing you do in this product is create a GeoWorkspace or open an existing one.
After you open a GeoWorkspace, you configure it to suit your needs. You can, for
example, change the coordinate-system properties or insert a map or raster image to use
as a backdrop for geographic data. Your configuration is saved when you save the
GeoWorkspace and restored when you reopen it.
The data you view is stored in warehouses, and you access data by creating connections
from the GeoWorkspace to one or more warehouses. The software presents a series of
dialog boxes necessary to create the connection. Because data are not stored in the
GeoWorkspace, all workflows require at least one warehouse connection.
A warehouse stores both geometric (graphic) and attribute (nongraphic) information. For
example, a parcel might be represented by an area geometry and defined by attribute
information such as the owner’s name and the date it was purchased.
Once you connect to at least one warehouse, you can display and analyze data from it.
The software allows you to view multiple data sets from different warehouses in various
formats in a single GeoWorkspace. This means you can perform spatial analyses on data
from different sources in different formats using buffer zones, spatial queries, and
thematic displays.
1-1
In this product, features are contained in feature classes, and the word feature refers to
each instance of a feature within a feature class. Feature classes, images, query results,
and thematic displays in the map window are collectively referred to as either features or
map objects.
Features are represented in the map window by geometry and in the data window by
attributes. You can display any number of map and data windows simultaneously or
separately. They are linked so that changes made in one window are automatically
reflected in the other.
You display features in a map window by adding entries to the legend. The legend is the
control center for the map window. Through the legend, you populate the contents of the
map window and control the display characteristics of the features, including their style
and display priority.
To perform certain tasks, such as inserting images or buffer zones, you must have a
read/write Access warehouse connection open. As with any other warehouse type, data
written to a read/write warehouse can be viewed along with other data sets in a single
GeoWorkspace.
Results of your analyses can be customized in the map window, printed, and saved for
future use, all without altering the original data.
What You Need to Know to Work

The documentation and learning tools assume that you have the following prerequisites:
• A basic understanding of your operating system.
• The ability to move around in the Windows environment.
• An understanding of the data that you want to use.
Documents Provided
The documents provided with GeoMedia are delivered into three groups: Developer
Documentation, User Documentation, and Utilities Documentation..
Developer Documentation
Developer Documentation is accessed online only.
Document Description
GeoMedia Information about using the Command Wizard to create Visual Basic
Command Wizard commands for the GeoMedia-based application and to edit or to delete
Help Visual Basic or Visual C++ command-set information. Access through
the Command Wizard.
1-2
Start Here
GeoMedia Object Programmer's guide to the objects, methods, and properties in the
Reference software’s automation layer. Access through Start > All Programs >
GeoMedia > Developer Documentation.
Building on the Information about customizing the software and building your own
GeoMedia Engine applications with the GeoMedia engine. Access through Start > All
Programs > GeoMedia > Developer Documentation.
User Documentation
User Documentation is accessed, depending on the component, both in hard copy and
online or online only.
GeoMedia Step-by-step instructions for all tasks and information about tools and
Help dialog boxes. Available in the software and from Start > All Programs >
GeoMedia > User Documentation.
Installing Instructions for installing the product. Available in pdf format through the
GeoMedia PDF Viewer from Start > All Programs > GeoMedia > User
Documentation.
Learning Hands-on tutorial that guides you through the software basics using an
GeoMedia example workflow and real data. Runs through a Web browser.
Available online from Start > All Programs > GeoMedia > User
Documentation.
Working with Overview of and workflows for performing most software tasks.
GeoMedia Available in .pdf format through the PDF Viewer from Start All >
Programs > GeoMedia > User Documentation, or from the C:\Program
Files\GeoMedia folder.
Utilities Documentation
Utilities Documentation consists of online-only documentation for the following delivered
utilities (Start > All Programs > GeoMedia > Utilities):
• Define CAD Server Schema File
• Define Coordinate System File
• Define Symbol File
• Define Text File Server Format File
• Define Warehouse Configuration File
• Licensing Utility
• Edit MGSM Parameter File
1-3
• Publish Address Geocoding Index

• Publish to GeoMedia SmartStore Warehouse
You can access this online documentation by:
• Selecting the utility document name in the GeoMedia Help menu.
• Pressing F1 while the utility is active.
• Selecting online Help from the utility Help menu in the Define CAD Server Schema
File, Define Text File Server Format File, and Publish to GeoMedia SmartStore
Warehouse utilities.
Typeface Conventions Used in the Documents

ALL Keyboard keys.
CAPS If keys are separated by a comma, press them in sequence. For example:
ALT, F5. If they are joined by a plus sign, press them at the same time.
For example: CTRL+z.
Bold An item in the graphical interface, such as the title of a dialog box or a
unserifed tool. Paths through menus use right angle brackets between items you
type select.
For example: Select File > Open to load a new file.
Courier Information you type.
type
For example: Type original.dat to load the ASCII file.
Italic type A document title, the first occurrence of a new or special term, folder
and filenames, or information about what the software is doing.
Interactive Documents
This product provides an interactive tutorial to help you learn how to perform the basic
tasks. If you are new to this product, you should work through Learning GeoMedia
Help is available online if you need step-by-step instructions, and other documents are
available for programmers who want to customize the software.
Learning GeoMedia
Learning GeoMedia steps you through an example workflow that uses real data and
covers the basic tasks. You start this tutorial by selecting Help > Learning GeoMedia
from the GeoMedia menu or by selecting Start > All Programs > GeoMedia > User
Documentation > Learning GeoMedia. This opens the tutorial in your default Web
browser. This tutorial works best with Internet Explorer 5.0, but it will run on another
browser.
1-4
Start Here
After you have worked through Learning GeoMedia, use Working with GeoMedia to gain
a broader understanding of what you can accomplish using this product.
Help Topics
You can find information for advanced topics and procedures from the online Help.
Included with the Help topics is a dictionary.
If Help was not installed on your hard drive during setup, you must have the GeoMedia
CD in your CD-ROM drive or be connected to the network node containing the Help
files.
To display Help when the software is active, select Help > GeoMedia Help from the
menu. To display Help when the software is not active, select Start > All Programs
> GeoMedia > User Documentation > GeoMedia Help.
Help is context sensitive, which means that you can press F1 to display Help for the
active window or dialog box. You can also click the Help button or press
SHIFT+F1. When the cursor changes to a question mark, select a menu item,
toolbar, or area of a window or dialog box.
Programming Guides
This product includes two online guides for developers who have experience with
programming languages that use automated objects and who want to customize or build
applications on this software.
• Building on the GeoMedia Engine is an interactive user’s guide developed in HTML.
• GeoMedia Object Reference covers the objects, methods, and properties available
through automation.
You can access the documents through Start > All Programs > GeoMedia Developer
Documentation.
What’s New in GeoMedia 6.1

To learn about changed and new features in GeoMedia 6.1, see the GeoMedia 6.1 Release
Notes.
1. To access this document, go to the “SG&I Support” page:
http://support.intergraph.com/.
2. Under Product Support, select GeoMedia from the Products drop-down list; then
click Go.
3. On the “GeoMedia Support” page, scroll down to the Product Versions table; then
click the Release Notes arrow for the latest 06.01 version information.
1-5
Getting Started
To start this product, select Start > All Programs > GeoMedia > GeoMedia. If it has
not been turned off, the introductory GeoMedia dialog box appears.
This dialog box lets you create a new GeoWorkspace using a blank GeoWorkspace or a
GeoWorkspace template or open an existing GeoWorkspace from a list of recently opened
GeoWorkspaces. You can select one from the list, and click OK, or if the existing
GeoWorkspace you want is not listed, you can select More Files, and click OK to find the
GeoWorkspace yourself. To not open this dialog box when you start the software, check
the Don’t show this dialog box again check box.
Note: To exit the software at any time, select File > Exit from the GeoMedia menu.
See the “Working with GeoWorkspaces” chapter for complete information on using
GeoWorkspaces.
Getting Around in the Software

Familiarity with Microsoft Windows conventions and Microsoft Office applications
should make it easy for you to get around in this product. As in Windows, for example,
you move a window by placing the cursor over the title bar and dragging the window to a
new location. Buttons and menu items are dimmed when the tools they invoke are not
available, and you can see what tool a button invokes by placing your cursor over the
button.
Common tools, such as File > Print, work essentially the same in this application as they
do in any Windows application.
Still, this product’s working environment does have some special characteristics:
1-6
Start Here
• Within the software, you work in three types of windows, map windows, data
windows, and the layout window. These windows are contained in a GeoWorkspace,
which is roughly analogous to a workbook in Microsoft Excel®. If you have a
Microsoft IntelliMouse™, you can use it to manipulate map, data, and layout
windows faster and more efficiently.
• The software offers several specialized toolbars that are available only under the
appropriate circumstances. The Data toolbar, for example, is available only when the
data window is active. Select View > Toolbars to specify which toolbars you want
to display.
• Some right mouse menus are available in this product. You display pop-up menus by
pressing the right mouse button. The tools on the menu vary with the location of
your cursor.
• The product’s toolbars can be moved from their default locations and docked at other
locations within the interface. Moving a toolbar over a map window converts the
toolbar to a dockable control, and some tools provide a control rather than a dialog
box interface. Further, clicking the right mouse button on the title bar of a control
displays a menu that allows you to restore, move, minimize, maximize, or hide the
control, while clicking the X icon dismisses the control. Clicking the right mouse
button on a toolbar (or on the icons in a control) displays a menu that allows you to
turn toolbars on and off, display the Status and Precision Coordinates toolbars, and
customize toolbars.
• All controls in the product that perform the display and entry of either graphic text or
attribute text, support multi-language text (Unicode).
See the “Working with Map Windows”, “Working with Data Windows”, and “Working
with Layout Windows” chapters for information on the three types of windows.
Customizing the Menus and Toolbars

You can customize the GeoMedia working environment to display the menu items and
buttons you want and to accept the keyboard shortcuts you specify. You can do this on a
particular installation of your software by using the Customize command. In addition,
you and/or your administrator can also use the Save Customized Settings and Load
Customized Settings commands to save customized menus and toolbars to an XML
document that can be placed and reused on other machines.
Using the Customize Command

The Customize command (Tools > Customize) lets you customize menus, keyboard
shortcuts, and toolbars to help you perform your tasks more efficiently, as follows:
Keyboard shortcuts—Assign shortcut keys to commands and remove them as well as
restore all shortcut key assignments to the original settings.
1-7
Menus—Add new menu items to and remove items from menus for quick access to the
commands you use most often, and reset menus to the original settings. You can also add,
rename, and delete menus.
Toolbars—Create new custom toolbars and add command buttons to delivered and custom
toolbars.
See the “Using the Customize Command” topic in the GeoMedia Help for complete
information on using this command.
Using the Save/Load Customized Settings Commands

Once you have customized the menus and toolbars for map windows and data windows
with the Customize command, the software provides an easy way to save (Save
Customized Settings) and to recall (Load Customized Settings) the customized
menu/toolbar configurations through a customized settings file (GeoMedia Customized
Settings, .xml), including commands from the core products and add-on products, as well
as custom commands. The layout window menus and toolbars, however, are not included
in these customized settings. You can thus create custom interfaces for specific purposes
or workflows as required. You may, for example, create a menu and toolbar configuration
for an edit-only workflow.
To save a customized configuration, you select Tools > Save Customized Settings to open
the Save As common dialog box. You then select the drive and folder for the new
customized settings file; the default folder is \GeoWorkspaces. Next, you type an
appropriate name for the customized settings file in the File name field, verify that the
Save as type drop-down list displays Customized Settings File (*.xml), and then click
OK.
To load a saved customized settings file, which removes all current menus and toolbars and
replaces them with the menus and toolbars defined in the XML document, the software
provides the following three options: Load Customized Settings command, command
line, and startup. The startup option is configured through the product’s automation layer.
The last two options let you load your customized settings at the end of GeoMedia
initialization. The schema for these documents is defined in GeoMedia
Professional\Schemas\gmcustom.xsd.
Note: A standard menus and toolbars customized settings file,

\ProgramFiles\GeoMediaProfessional\CustomizedSettings\StandardSettings.xml, is
delivered with the software. You can use this file to restore the delivered default menu and
toolbar settings.
To load a customized settings file with the Load Customized Settings command, you
select Tools > Load Customized Settings to open the Open common dialog box. You
then select the drive and folder containing the customized settings file you want to load.
1-8
Start Here
Next, you type the name of the customized settings file in the File name field or select it
from the list, and then click Open.
The command line option is /custom “<filename>”. During GeoMedia initialization, this
option is read, and the menus and toolbars are loaded, for example: GeoMedia.exe /custom
“D:\xmlfiles\MySettings.xml”.
The Product Workflow

This is a simplified example workflow for the most common tasks. Your workflow, of
course, will vary with the needs of your project.
1. Create a GeoWorkspace. See the “Working with GeoWorkspaces” chapter.
2. Define a coordinate system. See the “Working with Coordinate Systems” chapter.
3. Create warehouse connections. See the “Working with Warehouses” chapter.
4. Display data in your map window. See the “Working with Map Windows” chapter.
5. Change the appearance of the map-window contents. See the “Working with Map
Windows” chapter.
6. Display a data window. See the “Working with Data Windows” chapter.
7. Build and run a query. See the “Analyzing GeoMedia Data” chapter.
8. Create a thematic display. See the “Working with Map Windows” chapter.
9. Add labels to the map. See the “Analyzing GeoMedia Data” chapter.
10. Display a layout window. Display a layout window. See the “Working with Layout
Windows” chapter.
11. Prepare the map for printing. See the “Designing Map Layouts for Printing in the
Layout Window” chapter.
12. Print the map. See the “Printing in GeoMedia” chapter.
What is a GIS?
A GIS (geographic information system) is a computer system capable of assembling,
storing, manipulating, analyzing, and displaying geographically referenced information.
This system contains both data identified according to their locations as well as graphic
and nongraphic data.
What Can I Do with a GIS ?

A GIS allows you to perform the following functions:
• Locate information spatially – for example, find a site by latitude and longitude or by
proximity to other features.
1-9
• Visualize information more effectively and intuitively.

• Spatially analyze information from many integrated data sources.
• Graphically navigate through data sets, for example, drill downs.
• Answer questions more quickly and accurately.
• Plan work and activities more effectively.
• Save resources on construction, maintenance, management, surveying, and similar
activities.
Aspects of a GIS
The following are some important aspects of a GIS system:
• A GIS knows where things are, which is essential to rational decision making in many
cases.
• The a GIS is only as useful and accurate as the information you put into it.
• Proper implementation of the technology is critical to the system’s success
• A map itself is not a GIS; a map is a derived output product of a GIS.
• A map is to a GIS as a report is to a database.
Types of Information
A GIS may contain the following types of information:
Textual—Reports, tabular data, and data streams.
Image Files—Aerial photos, scanned images, and photographs.
CAD (Vector)—Drawings containing linework, such as floor plans, schematics, and
diagrams, which are sometimes drawn to scale and sometimes not.
GIS (Smart Vectors)—Maps, properly scaled and properly oriented, and support for
multiple projections. Map feature definitions also include nongraphic data (attributes).
Other Documents—Office automation: presentations, spreadsheets, web pages, and so
forth.
GIS Concepts & Terminology

The following are several important GIS concepts and terminology that are used when
describing GeoMedia. They are discussed at greater length in their respective parts of this
document.
1-10
Start Here
Warehouses—Collections of GIS data, for example Oracle, ArcInfo, and CAD databases.
GeoMedia establishes connections to warehouses to gain access to the GIS information.
Features—Features are digital representations for real-world entities.
• Features have attributes. A feature class definition defines all of the attributes and
associated data types. Specific instances of the feature class have unique values for the
attribute fields.
1-11
• Features can represent almost anything.
• Features can be represented in the GIS as points, lines, polylines, areas, arcs, text, and
images.
• Features can be organized into categories, themes, or layers.

Legends—Legends control what information appears in a map window, including
symbology, render order, and interactive characteristics.
Queries and Spatial Queries—Queries are questions, some complex, some simple, that
you can pose to the GIS. For example, a simple query might be to see all cities with more
than 100,000 people. Or, you may ask to see all states with a population over 100,000
1-12
Start Here
containing cities where the total crime rate is greater than 125. Spatial queries supplement
relational operators with spatial operators.
Coordinate Systems and Projections—Mathematical transformations must take place to

represent the Earth in two-dimensional space. It is the same source information in each
case, just represented differently. This is the primary cause for data from disparate sources
not to overlay properly.
Analytical Commands—Complex analyses and processing of the contents of the GIS.
GIS Applications
A GIS can be productively used in many endeavors, including the following:
• Agriculture
• Business
• Cartography
• Meteorology
• Geology
• Tourism
1-13
• Education
• Archeology
• Facilities Management
• Military installation management
• Asset Management
• Environmental Management
• Utilities Management (water and sewer, electric, communication systems, cable, cell
phone coverage areas, and so forth)
• Natural Resources and Resource Conservation
• Public Safety (emergency dispatch management)
• Disaster planning (hurricane evacuation, earthquake)
• Health Care Industry (disease outbreak studies, epidemics)
• Industrial (plants, pipelines, storage tanks, and so forth)
• Aeronautical (Airport GIS, airspace management)
• Marine Engineering (biology, soundings)
• State and local government – Land Information Systems (LIS): parcels, right-of-way,
and so forth.
• Transportation Industry (highways, railroads, planning and analysis)
Benefits of GIS
Some of the benefits of using a GIS are the following:
Reduces Operations and Maintenance Costs—As a productivity multiplier, a GIS
enables less-skilled personnel to complete sophisticated analyses, as well as expanding the
output of the technical staff.
Improves Mission Effectiveness—A GIS provides command and management personnel
with the opportunity to rapidly analyze multidisciplinary sets of data and to arrive at the
best solution with complete supporting documentation.
Provides Rapid Modeling Capabilities for Analyzing Alternative Strategies— A GIS
provides the capability for command personnel to make the best and most cost-effective
decisions in tight budget environments.
Greatly Improved Communication Aids—Effective communication is essential for
managing an infrastructure, whether it be a college campus, military installation, or a city.
GIS visualization tools are fast and easy to use.
Promotes Harmony—By providing a standard set of data and tools for modeling and
analysis, major alternatives for a project can be consistently produced and analyzed. This
1-14
Start Here
capability helps bring teams together with the increased job satisfaction associated with the
feeling of effective group participation.
Provides a Repository of Institutional Knowledge—By incorporating as much
knowledge as possible into standard GIS functions, the loss of key personnel knowledge
can be minimized.
1-15
1-16
Working with GeoWorkspaces
A GeoWorkspace is the container for all your work in this product. Within its confines are
the warehouse connections to your data, map windows, data windows, layout windows,
toolbars, coordinate-system information, and queries you have built. The first thing you do
is open an existing GeoWorkspace or create a new one.
Once you are in a GeoWorkspace, you can change its coordinate system, establish
warehouse connections, run queries, display data, and perform spatial analyses. The
settings and connections you define in a GeoWorkspace are saved in a .gws file, although
the actual data remains stored in warehouses. The software is delivered with an example
GeoWorkspace, USSampleData.gws.
Note: The U.S. Sample Data Set contains a shaded relief image of the United States,
complete with hypsometric tints. The data consist of a 1000-meter pixel resolution RGB
GeoTIFF file.
Every GeoWorkspace is built on a template, and you can create your own templates or use
an existing one. The software is delivered with a default GeoWorkspace template,
normal.gwt, which contains an empty map window, an empty legend, and a predefined
coordinate system. If you accidentally delete the normal.gwt file, you must reinstall the
software to restore the template; so it is a good idea to back up this file.
This is a representative workflow for creating and configuring a GeoWorkspace:
1. Select File > New GeoWorkspace.
2. Select a template.
3. If the coordinate system you want differs from the one in the template, define a
different coordinate system for the GeoWorkspace.
4. Make warehouse connections; configure map and data windows (topics covered in
other chapters).
5. Save the GeoWorkspace.
Creating a GeoWorkspace
You create a GeoWorkspace using normal.gwt or another template in the
\GeoMedia\Templates\GeoWorkspace folder. The available templates are displayed when
you select File > New GeoWorkspace from the GeoMedia menu or Create new
GeoWorkspace using from the introductory GeoMedia dialog box.
2-1
The software assigns a default title of GeoWorkspace1 to each new GeoWorkspace.

When you save a GeoWorkspace, you assign it a filename, and the software automatically
adds a .gws extension.
Opening a GeoWorkspace
You can have only one GeoWorkspace open at a time. When you open a second
GeoWorkspace in the same software session, the software closes the open GeoWorkspace.
If the GeoWorkspace you want to open is read-only, you are advised that it is read-only
and asked if you still want to open it. If you open it, the software makes a copy of the
read-only GeoWorkspace and opens it as read-only. If you then make changes to this
internally copied GeoWorkspace and try to save it, you are advised that you have made
changes and asked if you want to save the GeoWorkspace to a different file name because
the original GeoWorkspace is read-only. The changes you make to a read-only
GeoWorkspace are discarded when you close it unless you save it with a different file
name.
A list of the most recently used GeoWorkspaces appears at the bottom of the File menu.
You can open a GeoWorkspace from this list by clicking the filename.
Note: GeoWorkspace (*.gws) files created in GeoMedia and other GeoMedia applications
that are saved to disk with queries specific to those applications, such as geometry
validation queries, will not open in GeoMedia.
To open a GeoWorkspace:
1. Select File > Open GeoWorkspace.
2-2
2. Select the GeoWorkspace you want.

3. Click Open.
Note: If a connection fails while attempting to open a GeoWorkspace, an error dialog box
appears prompting you to verify that your warehouse connection parameters are correct.
Delaying Data Loading

Depending on your data, opening an existing GeoWorkspace may take a long time. The
amount of time varies with the number of feature classes being loaded into displays, the
amount of data per feature class, and the processing time of any queries. To improve
performance, you can delay the loading of data by selecting the Do not load data when
opening GeoWorkspace check box on the General tab of the Options dialog box (Tools
> Options). If this check box is not selected, which is the default, the software loads all
data when opening a GeoWorkspace.
Upon setting this option, the map windows and data windows are empty when you open a
GeoWorkspace. The legend entries in the map view are created but not in a loaded state;
the data view shows a title but displays no records. Any existing queries are not re-
executed. Also, any subsequent opening of an existing GeoWorkspace, in the same session
or future sessions, does not load the data.
After opening a GeoWorkspace, you can selectively load its data as follows:
Legend Entries
• Select View > Update All to update all legend entries in all map windows and all data
windows.
2-3
• Select one or more legend entries, display the right mouse menu (on the legend, not the
map window), and select Load Data. This is enabled only when one or more of the
selected legend entries is in an unloaded state.
Data Windows
• Select View > Update All to update all legend entries in all map windows and all data
windows.
• Display the right mouse menu, and select Load Data. This is enabled only when the
data window is in an unloaded state.
Automatically Backing Up GeoWorkspaces

To protect you against data loss due to GeoWorkspace corruption, the software contains an
automatic backup function. This automated backup is performed immediately after a
GeoWorkspace has been successfully read, at which point it is known that the
GeoWorkspace is not corrupted and a copy can be safely saved. This backup is performed
only if the GeoWorkspace itself is read-write, as there is no danger of a file corruption if it
is read-only. Furthermore, the GeoWorkspace may be read-only because it is in a read-
only folder or on a read-only medium (for example, a CD), which would prohibit creation
of the backup in any case.
The backup copy of the GeoWorkspace is made using a file copy, which ensures the
backup copy is identical to the original GeoWorkspace except for the filename. The
backup file has the same path and filename as the original GeoWorkspace except that the
extension is .bak. If a former backup file by the same name already exists, it will be
overwritten. The default is to automatically back up GeoWorkspaces, but you can turn this
feature off by unchecking the Create backup when opening GeoWorkspace check box
on the General tab of the Options dialog box (Tools > Options).
Saving, Closing, and Copying a GeoWorkspace

In addition to saving GeoWorkspaces automatically through the backup function, there are
several ways to save or to close one. When you save or copy a GeoWorkspace, you are
saving all its settings—the window configuration, the coordinate system, queries, legends,
thematic displays, and warehouse connections—even if you are connected to a read-only
warehouse.
The default location for GeoWorkspaces is specified during installation, usually the
\GeoWorkspaces folder of your root folder. You can change the default folder through the
File Locations tab of the Options dialog box. The default file extension for
GeoWorkspaces is .gws.
• To save changes to a GeoWorkspace any time during a session, select File > Save
GeoWorkspace. This saves but does not close the GeoWorkspace.
2-4
• To save a new GeoWorkspace, select File > Save GeoWorkspace As, and type a
name for the GeoWorkspace in the File name field.
Note: To make a GeoWorkspace read-only, you use standard Windows procedures for
changing file attributes.
• To copy the open GeoWorkspace to a new file, select File > Save GeoWorkspace As,
and give the GeoWorkspace a different name. This closes the open GeoWorkspace
without saving changes to it since the session was opened or since the last save. The
newly named GeoWorkspace becomes the open one.
• To close a GeoWorkspace without saving changes made since the last save or since the
current session was opened, select File > Close GeoWorkspace.
To change the location of your GeoWorkspace files:

The default storage location of your GeoWorkspace files is established when the software
is installed, but you can change it from the File Locations tab of the Options dialog box.
E-Mailing a GeoWorkspace
When you select File > Send from the GeoMedia menu, the electronic-mail application on
your system starts and attaches a copy of the open GeoWorkspace.
Because all warehouse connections are stored as folder paths, the person receiving the
GeoWorkspace will be able to open the GeoWorkspace, re-establish all original warehouse
connections, and view the data as it appeared when you e-mailed the GeoWorkspace.
2-5
1. Select File > Send.

2. Fill in the To and Subject fields as you would for any e-mail message.
3. Send the message.
Creating a GeoWorkspace Template

The default location for GeoWorkspace templates is \Program
Files\GeoMedia\Templates\GeoWorkspaces. You can specify a different folder through
Tools > Options > File Locations.
To create a GeoWorkspace template:

1. Select File > New GeoWorkspace.
2. On the GeoWorkspace Template dialog box, select the Template option.
3. Select the normal.gwt template, and click New.
4. Define the GeoWorkspace coordinate system (View > GeoWorkspace Coordinate
System).
5. Make the warehouse connections you want for this template (Warehouse > New
Connection).
6. Turn on and position—or turn off—the legend, north arrow, and scale bar (View
menu).
7. Adjust the size and locations of the map and data windows.
8. In the map window, display the features and background images you want.
9. Build the queries you want saved with the template.
10. Select File > Save GeoWorkspace As.
Note: If you have named an alternate file location for GeoWorkspace templates, that
location appears in the Save in field of the Save GeoWorkspace As dialog box. Then
if you want to store the new template in the main templates folder, click the drop-down
arrow and browse to the \Program Files \GeoMedia\Templates\GeoWorkspaces folder.
11. Verify that GeoWorkspace Template appears in the Save as type field.
12. Type a name for the template in the File name text box. The file extension must be
.gwt.
13. Click Save.
2-6
Linking and Embedding a GeoWorkspace

GeoMedia can act as an OLE server, which means you can insert a GeoWorkspace as an
object into a container application that supports OLE. All such applications have an Insert
Object command, or something equivalent, that lets you link or embed objects. You can
also embed a GeoWorkspace by dragging and dropping the .gws file name from Windows
Explorer into a container application.
Only one view in a link can be active, and the container application shows the active view
by default when you link a GeoWorkspace. However, in some container applications, you
can edit the link and change the item part of the link source to a named view, which is the
title on a map or data window (by default, MapWindow1 or DataWindow1, for example).
When you embed a GeoWorkspace, the entire GeoWorkspace is embedded, not just a
single map or data window, although you can see only the active view of the embedded
GeoWorkspace in the document of the container document. The embedded GeoWorkspace
can be edited in one of two ways. First, you can in-place activate GeoMedia within the
container application. When you do this, the container application displays its own File
and Windows menus, but all other menus and tools belong to GeoMedia. Clicking outside
the embedded GeoWorkspace takes you back to the container document. Second, you can
open the embedded document in a separate GeoMedia window. This allows access to the
other windows in the embedded GeoWorkspace.
2-7
2-8
Working with Coordinate Systems
This application displays all data—even data from different sources—using the coordinate
system defined for the GeoWorkspace. Each feature class stored in a warehouse can have
its own unique coordinate system and is transformed on the fly into the GeoWorkspace
coordinate system when you display them in the map window.
IMPORTANT: To accurately display raster images, FRAMME data, or data from many
non-Intergraph proprietary formats in a GeoWorkspace, the coordinate system of the
GeoWorkspace must either match that of the feature data in the warehouse or you must
define a coordinate system file for the feature data so that it can be correctly converted for
you. Assigning a coordinate system to your source data is the only way to ensure that
GeoMedia understands the source projection of your data. Data servers that use coordinate
system files typically specify the association of feature name to coordinate system file in
their ini file. In some cases these data servers allow the same coordinate system file to be
shared by all features in the warehouse. To create a coordinate system file (*.csf), you use
the Define Coordinate System File utility that is delivered with the software. A common
method to create the .ini file is the Define Warehouse Configuration File utility.
See "Displaying Data That Has No Coordinate System Specified" in this chapter. Also, see
the Define Coordinate System File utility’s online Help.
A coordinate system provides the mathematical basis for relating the features in your study
area to their real-world positions. The software supports the following types of coordinate
systems:
• A geographic coordinate system (the default) references a spheroid, expressing
coordinates as longitude, latitude, where longitude is the angular distance from a prime
meridian, and latitude is the angular distance from the equator.
• A projected coordinate system references a projection plane that has a well-know
relationship to a spheroid, expressing coordinates as X,Y, where X normally points
east on the plane of the map, and Y points north at the point chosen for the origin of
the map. The X coordinate is called easting, and the Y coordinate is called northing.
• A geocentric coordinate system references an earth-centered Cartesian system,
expressing coordinates as defining the position of a specific point with respect to the
center of the earth. These coordinates are Cartesian (X, Y, Z) where the X axis of the
geocentric system passes through the intersection of the prime meridian and the
equator, the Y axis passes through the intersection of the equator with 90 degrees East,
and the Z axis corresponds with the earth’s polar axis. The X and Y axes are positive
pointing outwards, while the Z axis is positive towards the North Pole.
3-1
Geographic and projected coordinate systems reference horizontal position using either
longitude, latitude, or X,Y. Such a position may be extended to reference a vertical
position in the form of a third coordinate that indicates elevation above a known reference.
All GeoMedia coordinate systems provide both horizontal and vertical reference
information.
Coordinates may be transformed between these the geographic, projected, and geocentric
reference spaces. A paper reference space, which is a scaled representation of the
projection plane, is also supported.
Because the shape of the earth's surface varies from one geographic area to another, the
software interprets horizontal coordinates with reference to a network of geodetic control
points called the geodetic datum. The horizontal geodetic datum in turn defines the
reference ellipsoid, which is the model used to represent the shape of the earth’s surface.
Vertical coordinates (elevations) are interpreted with reference to a network of vertical
control or other vertical reference frame called the vertical datum.
See the “Coordinate System Information” appendix for a list of supported horizontal
geodetic datums, vertical datums, and ellipsoids.
If you change the coordinate system after displaying data, the data are transformed to the
new coordinate system, and the display is updated. Changing the coordinate system in the
GeoWorkspace does not affect the data in the warehouse, only data in the map window.
When you add a feature class to a GeoWorkspace, the software checks the datums in the
warehouse and in the GeoWorkspace for compatibility. If the datums are different, the
software automatically builds the appropriate datum transformation for these datums.
Note: To customize the datum transformation, edit the datum-transformation-building

algorithm in the file …\cssruntm\cfg\autodt.ini
The default coordinate system in the software contains the following settings:
• Base storage type—Geographic
• Horizontal storage unit—1 degree
• Vertical storage unit—1 meter
• Projection algorithm—Cylindrical Equirectangular
• Projection parameters—Centered at the equator and the prime meridian
• Horizontal geodetic datum and ellipsoid—WGS84
• Vertical datum— Earth Gravitational Model (EGM96)
• Nominal map scale—1:50,000
3-2
Note: When the coordinate system type is geocentric, the projection algorithm is preset to
be Local Space Rectangular with latitude of origin at the North Pole. When the coordinate
system type is geographic, the projection algorithm is preset to Cylindrical Equirectangular
centered at the equator and prime meridian. For the geocentric and geographic coordinate
system types the projection algorithm is preset and cannot be changed.
You can change coordinate-system settings in an individual GeoWorkspace at any time.

Or you can create a new template with different settings so that all the GeoWorkspaces or
warehouses you create with the new template will have the different settings.
For projected coordinate systems, you can define a projection algorithm and its specific
projection parameters or accept the default of Cylindrical Equirectangular centered at the
equator and the prime meridian. For both projected and geographic coordinate systems,
you can define the horizontal and vertical storage units and storage-center parameters; or
you can accept the defaults. For geocentric coordinate systems, you can define the uniform
storage unit and storage center.
You can review but cannot change ellipsoid parameters unless you select user-defined
(non-standard) datum and ellipsoid types. Then you can type an equatorial radius value
and any other parameter and let the software calculate the remaining values.
In addition to using predefined horizontal geodetic datums, GeoMedia includes support for
custom named geodetic datums using the NamedHDatum.ini configuration file. For more
information see the …\cssruntm\cfg\NamedHDatum.ini file.
Finally, coordinate systems are heavily data dependant; therefore, you should not define
them arbitrarily. The projection you use in the definition should be the one that best suits
the data being displayed.
Storage Units
You can set the horizontal storage unit, vertical storage unit, geocentric storage unit, and
storage center parameters on the Storage Space tab of the Define Coordinate System File
dialog box, the GeoWorkspace Coordinate System dialog box, and the Coordinate
System Properties dialog box. The content of this tab varies depending on base storage
type. The following example is for the projection base storage type:
3-3
For the geographic base storage type, you also define the horizontal and vertical storage
units, but the storage center options are longitude, latitude, and height. For the geocentric
base storage type, you define the geocentric storage unit and the storage center options of
X, Y, and Z.
Horizontal storage unit—For the coordinate system of a data source, the horizontal
storage unit defines what the distance between sequential integer X or Y coordinate
values is when the base storage type is geographic or projection.
For example, if the resolution is 0.001 ft., and then the X coordinate of a point changes
from 1 to 2, the distance in the X direction of the change is 0.001 ft. This is very important
for data sources that store coordinates as integers (MGE, MGDM, MGSM, and CAD with
.dgn files) because for these data types, you cannot go between 1 and 2. Thus, the smallest
distance that will resolve two values as being separate is 0.001 ft., which leads to the term
resolution being applied to integer storage. In the context of IGDS/MGE, this concept was
presented with the term UOR (Unit of Resolution), whereas GeoMedia uses storage
coordinates. Thus, when MGE tells you that you have 1000 UORs per ft., it is telling you
exactly the same thing that GeoMedia is telling you when it says you have a horizontal
resolution of 0.001 ft. (1 ft./1000 UORs). GeoMedia is just looking at the distance
between two adjoining UORs, whereas MGE/MCSO presents the same concept as "how
many UORs fill a common distance (such as 1 ft.)". The GeoMedia way of presentation
mimics common language, such as, "My data are at cm. resolution" (meaning the distance
between UORs is 1 cm., whereas MGE would state this as "100 UORs per m." or "1 UOR
per cm.").
For CAD and MGE users, the horizontal resolution is expressing the very real limitations
of the data. For example, you cannot draw a line and measure between two UORs.
For other data sources that use floating point, these limitations do not exist (within reason).
Much ArcInfo and MapInfo data are defined with a horizontal storage unit of 1 meter (or
for geographic data, 1 degree). That just means that the data source chose to store the
coordinates in those units. It is not necessary for floating point data to be stored as
hundredths of a foot, for example, which would be wasted calculation; they just store it as
feet (or meters, or whatever—whole units, usually).
3-4
Likewise, data in GeoMedia's own geometry cache is kept as floating point. Thus, it is
normally not necessary to adjust the resolution definition for the GeoWorkspace coordinate
system. This is especially true due to the ability to match GeoWorkspace and default
warehouse coordinate systems through the General tab of the Options dialog box (Tools >
Options).
Note: If you are exporting data from an integer-based storage format to a floating-point
storage format, you should set the horizontal resolution for the coordinate system in the
target warehouse to 1. This ensures that the coordinates stored reflect the actual
coordinates of the data rather than the UOR values.
Vertical storage unit—For the coordinate system of a data source, the vertical storage unit
defines what the distance between sequential Z coordinate values is, when the base storage
type is geographic or projection.
Geocentric storage unit—For the coordinate system of a data source, the geocentric
storage unit defines what the distance between sequential X, Y, or Z coordinate values is,
when the base storage type is geocentric.
For a geocentric coordinate system, the geocentric storage unit takes the place of both
horizontal and vertical storage units because the geocentric storage space has uniform
scaling in all directions.
The description of how the horizontal storage unit relates to integer and floating point data
storage applies also to the vertical storage unit and the geocentric storage unit parameters.
Storage center—This is another legacy from integer storage. Integer storage mechanisms
such as MGE and CAD .dgn files can only store so many UORs. In some cases, users need
to offset the range of UORs that is used (some users wanted all coordinates to be positive,
for example). The MicroStation global origin offset would accomplish that. This appears
in GeoMedia as the storage center. A normal data set has a center of (0,0), which means
no shifting is defined.
Note: If you are exporting data from an-integer based storage format to a floating-point
storage format, you should set the storage center for the coordinate system in the target
warehouse to 0. This ensures that the coordinates stored reflect the actual coordinates of
the data rather than the shifted values.
Defining a Coordinate System for a GeoWorkspace

You can define the following coordinate-system properties in a GeoWorkspace:
• Coordinate system type (geographic, projection, or geocentric)
• Horizontal and vertical storage units or geocentric storage unit
3-5
• Storage center
• Projection algorithm and parameters
• Horizontal (geodetic) and vertical datums
• Reference ellipsoid and parameters
See the "Coordinate System Information" appendix for the settings available in the
software.
To define a GeoWorkspace coordinate system:

1. Select View > GeoWorkspace Coordinate System.
2. On the General tab of the GeoWorkspace Coordinate System dialog box, select the
Geographic, Projection, or Geocentric coordinate system type.
3. Optional: To change the storage units and storage center, select the Storage Space
tab.
Note: Changing the coordinate system type from Projection or Geocentric to

Geographic resets the horizontal storage unit to 1 degree and the vertical storage unit
to 1 meter. Changing the coordinate system type from Geographic or Geocentric to
Projection will reset the horizontal and vertical storage units to 1 meter. Changing the
coordinate system type from Projection or Geographic to Geocentric resets the
geocentric storage unit to 1 meter. Each of these changes resets the storage center to
(0,0,0).
4. For projected coordinate systems only: On the Projection Space tab, select a
projection algorithm from the Projection algorithm drop-down list.
To change parameters, click Projection Parameters. Depending on the projection
algorithm selected, some text boxes may be read-only.
3-6
5. Optional: On the Geographic Space tab, select the geodetic datum from the Geodetic
datum drop-down list.
6. Optional: If you select a user-defined (non-standard) geodetic datum, you can change
the ellipsoid on the Geographic Space tab; and if you select a user-defined (non-
standard) ellipsoid, you can change ellipsoid parameters as well.
7. Optional: On the Geographic Space tab, select the vertical datum from the Vertical
Note: Changing the coordinate system type from Projection or Geographic to

Geocentric resets the vertical datum to Ellipsoid (geometric).
8. On the GeoWorkspace Coordinate System dialog box, click OK.
Defining a Coordinate System for a Feature Class

For a new feature class being defined or an existing feature class being edited (other than
non-graphic, that is, tabular-only, non-spatial data) that has no data, you can define or
review the following coordinate-system properties of the default coordinate system:
• Base storage type (geographic, projection, or geocentric)
• Horizontal and vertical storage units or geocentric storage unit.
• Storage center
• Projection algorithm and parameters
• Horizontal (geodetic) and vertical datums
• Reference ellipsoid and parameters
For information about creating feature classes, see the “Working with Features” chapter.
Note: For a feature class being reviewed or a feature class being edited that has data, you
can only review the coordinate system properties. However, a warehouse coordinate
system may be marked as the default coordinate system for the warehouse while reviewing
or editing an existing feature class, or while creating a new feature class.
To define a coordinate system for a new feature class:

1. Create or connect to a read-write warehouse.
2. Select Warehouse > Feature Class Definition.
3. On the Feature Class Definition dialog box, click New; then define new feature class
name, optional description, and data type.
3-7
You may select a coordinate system by name from the Coordinate system drop-down
list. The properties of the selected coordinate system may be reviewed by clicking the
Properties button, which displays the Coordinate System Properties dialog box
(described below) in read-only mode. To create a new coordinate system for the
feature class, click New, which displays the Coordinate System Properties dialog
box in read-write mode:
4. On the General tab of the Coordinate System dialog box, select the Geographic,
Projection, or Geocentric coordinate system type.
tab.

Projection resets the horizontal and vertical storage units to 1 meter. Changing the
(0,0,0).
To change parameters, click Projection Parameters. Depending on the projection
algorithm selected, some text boxes may be read-only.
3-8

10. Optional: On the General tab, type values in the coordinate system Name and
Description fields.
Both will be stored in the warehouse and can make it easier to determine what
coordinate systems are assigned to specific feature classes. The Name entry will be
used in the Coordinate system drop-down list on the New <feature class name>
dialog box when you exit the Coordinate System Properties dialog box with OK.
11. Click OK on the Coordinate System Properties dialog box.
12. Optional: To create or change the default coordinate system for the warehouse, select
the appropriate coordinate system from the Coordinate system drop-down list; then
click the Set As Default button.
Note: You can assign only one default coordinate system per warehouse.
13. Click OK on the New <feature class name> dialog box..
Matching GeoWorkspace and Default Warehouse

Coordinate Systems
The General tab of the Options dialog box (Tools > Options) provides two options to
match the GeoWorkspace and default warehouse coordinate systems. These options
improve performance when loading and displaying data by not imposing unnecessary
coordinate-system transformations. Both options are selected by default.
3-9
The default warehouse coordinate system is assigned by clicking the Set As Default button
on the New / Edit / Review <feature class name> dialog box within the Warehouse >
Feature Class Definition command. If a default coordinate system has not been defined,
the software will look for the first coordinate system having the Description property
value Default. If no default is found that way, the first coordinate system found in the
metadata table GCoordSystem will be used.
The When making first connection option allows you to match the two coordinate
systems by copying the definition of the default coordinate-system of the first warehouse
connection made for the GeoWorkspace with the New Connection command to the current
GeoWorkspace coordinate system. If you do not select this option, New Connection has
no effect on the definition of the GeoWorkspace coordinate system. You can verify the
new coordinate-system definition through View > GeoWorkspace Coordinate System.
The When creating a new warehouse option allows you to match the two coordinate
systems by copying the coordinate-system definition of the current GeoWorkspace to the
default coordinate system of a new Access warehouse when it is created. If you do not
select this option, the active template defines the default coordinate system of the new
warehouse. This option does not affect Oracle or SQL Server connections.
The optimum workflow in many situations is to first use New Connection to connect to
your data, thus setting the GeoWorkspace coordinate system, and then to use New
Warehouse to create any appropriate new Access warehouse(s). This sequence ensures
that the new Access warehouse shares the same coordinate-system definition with the data
source and the GeoWorkspace.
Note: The When creating a new warehouse option does not apply to the Oracle Object
Model. When using the Oracle Object Model, you need to verify that the coordinate
system is set to what you want it to be; it is not automatically set by the software.
3-10
Related Effects
The software automatically updates the various aspects of the system that are affected by
copying the default coordinate-system definition of the first connection to the
GeoWorkspace coordinate system. Any transformation pathways to coordinate systems of
connections that were previously created and then deleted will be updated. Any spatial
filters that exist (either from the GeoWorkspace template or from running Spatial Filter
definition commands) will be transformed into the new GeoWorkspace coordinate system.
Coordinate-system information will be updated on all map views, resulting in recalculation
of the display scale. If the north arrow and scale bar are displayed, they will be refreshed
to account for the new coordinate system and display scale.
Copying the GeoWorkspace Coordinate-System Definition onto the Default
Coordinate System of a New (Access) Warehouse
If you select the matching options, the software copies the definition of the coordinate
system of the GeoWorkspace into the warehouse and marks it as the default coordinate
system for the warehouse. This definition is written into the GCoordSystem table of the
database. The software creates a new row if necessary.
You can actually use the New Warehouse command in two slightly different ways to
create 1) a new Access warehouse (.mdb – the default), or 2) a new Access warehouse
template (.mdt). Only when creating a new warehouse (.mdb) does the command establish
a connection to the new warehouse. Because an open connection is required to update or
to add a row to the GCoordSystem table of the warehouse, it is only when a new warehouse
(not warehouse template) is created (and the preference is set) that the New Warehouse
command copies the GeoWorkspace coordinate system to the warehouse and marks it as
the default coordinate system.
The impacts of copying the GeoWorkspace coordinate-system definition onto the
coordinate system of a new (Access) warehouse affect the optimum workflow. The
optimum workflow in many situations is to first use New Connection to connect to your
data source, thus setting the GeoWorkspace coordinate system, and then to use New
Warehouse to create any new warehouse(s). This ordering ensures that the new
warehouse shares the same coordinate-system definition with the data source and
GeoWorkspace.
Getting Coordinate Readouts

To see the coordinates of any location in the map window, turn on the Precision
Coordinates display (View > Precision Coordinates).
This control displays the precision coordinates for the current cursor position in the map
window. The current coordinate format drop-down list determines if the displayed
3-11
coordinates are geographic or projected. The coordinate display and entry field displays
the coordinate readout for the current cursor position. The units and precision of the
coordinate readout are defined using the Units and Formats tab of the GeoWorkspace
Coordinate System dialog box. You have the option to update coordinates with a mouse
move (the default) or with a click. The coordinate display and entry options drop-down
menu displays options that include the following:
• Update coordinates on mouse move
• Update coordinates on click
• Clear coordinates after enter (this option applies to precision keyins, not to precision
readouts)
See the Precision Coordinates Help topic in GeoMedia Help for complete information.
Setting Units and Formats

When setting a GeoWorkspace coordinate system, the Units and Formats tab of the
GeoWorkspace Coordinate System dialog box allows you to set default measurement
options for all commands that involve measuring, for example, Measure Distance and
Analyze Geometry. This tab also allows you to control the way coordinate readout
information appears on the Precision Coordinates dockable control.
When setting the coordinate system of a feature class, the Units and Formats tab allows
you to set the units and formats parameters on the tab; however, when the dialog box is
displayed from the Feature Class Definition command, these parameters only have an
effect on this dialog box or its sub-dialogs (for example, the Projection Parameters dialog
box). Specific units and formats are not stored for individual features, only the coordinate
system and the master unit are stored. This is also true for other commands (commands
other than the GeoWorkspace Coordinate System command) that use this dialog box.
These are the options you can set on the Units and Formats tab:
3-12
• Type specifies the type of unit for which to set the default unit and precision. Each
unit type used by the software is listed. When the software outputs values of the
specified unit type, those values by default are displayed using the units and precision
specified here. Some commands allow you to override these defaults.
• Unit sets the linear, areal, or angular unit of measure. The choices vary with the unit
type.
• Precision defines the number of decimal places of precision in the coordinate-readout
applicable commands. A separate precision may be specified for each unit type.
• Geographic coordinate format defines the ordering of longitude and latitude values
and the definition of the positive direction of the two axes (including the option for
using character designators) when geographic coordinates are formatted or parsed as
ASCII strings.
• Projection coordinate format defines the ordering of projection east/west and
north/south values and the definition of the positive direction of these two axes used in
projection coordinate strings that are formatted for output or parsed for input.
• Measurement interpretation specifies how Earth curvature and nominal map scale
are accounted for in measurements and coordinate calculations.
− True (spheroidal) specifies that distance/area/azimuth(bearing) measurements are
taken on the surface of the ellipsoid by taking the curvature of the Earth into
account. These measurements do not contain any projection distortions.
− Projected (planar) specifies that distance/area/azimuth(bearing) measurements are
taken on the projection plane without taking the curvature of the Earth into
account. These measurements do contain projection distortions. This is the default
setting.
− Paper (scaled) specifies that distance measurements are computed on the paper
plane that is scaled in relation to the projection plane at the current nominal map
scale.
Note: This option is available only when the Units and Formats dialog box is
displayed with the Tools > Measure Distance dockable control.
• Azimuth settings specify the direction and starting point when setting and displaying
azimuths. An azimuth is a way of specifying an angle by measuring either clockwise
or counterclockwise from 0 to 360 degrees. These options apply to the distance and
azimuth readouts and keyins, and to some coordinate system projection parameters.
See the “Conversion Tables” appendix for multiplication factors for converting from/to the
International System of Units (metric) to/from the United States Customary System.
Units and formats can be temporarily set when displaying the Units and Formats dialog
box from the Tools > Measure Distance and the Insert > Feature dockable controls.
3-13
The Paper (scaled) measurement interpretation is only available with the Tools >
Measure Distance dockable control.
See the "Measuring Distances" in the “Working with Map Windows” chapter.
Configuring for Datum Transformations

To convert data between two coordinate systems that are based on different horizontal or
vertical geodetic datums, you need one or more datum transformations. The software uses
the autodt.ini file to generate datum transformations during the building of coordinate-
system transformation paths, such as the path between the GeoWorkspace coordinate
system and a warehouse coordinate system. The autodt.ini file is in the …\cssruntm\cfg
folder.
When datum transformation is needed to go between a specific set of datums, the entries
from this file are used to create a network graph of the datum transformation possibilities
and the shortest path through the graph is used to choose the set of datum transformations
that you want. When building the graph, the software processes this file in order from top
to bottom. Where more than one file entry exists to transform between a given set of
datums, only the first entry will be used.
You can cause a different model or definition to be used by changing the order of the
entries in the autodt.ini file. You can also define new entries for many models, if you have
access to the parameters for these models that suit your needs. The Second Degree
Conformal Polynomial model may be used to achieve a Helmert transformation. All datum
transformation models can transform in both the forward and inverse directions.
For example, an entry that begins "csgdNAD27,
csvdNAVD88,csgdNAD83,csvdNAVD88, . . ." will match a search for a transformation to
go from NAD83 to NAD27 as well as a transformation from NAD27 to NAD83.
Details of the syntax for model-specific parameters are included as comments in the
autodt.ini file. The general syntax for all entries in this file is as follows:
ForwardInputHorizontalDatum,ForwardInputVerticalDatum,Forward
OutputHorizontalDatum,ForwardOutputVerticalDatum,DatumTransMo
delType[,model-specific-parameters...]
• Fields are separated by a comma (,).
• A semicolon (;) in the first column denotes a comment line.
• Horizontal datums are defined using the ASCII mnemonics from the
CSGeodeticDatumConstants enumeration and named horizontal datum names from the
NamedHDatum.ini configuration file.
• Vertical datums are defined using the ASCII mnemonics from the
CSVerticalDatumConstants enumeration.
3-14
• Datum-transformation-model types are defined using the ASCII mnemonics from the
CSDatumTransformationModelConstants enumeration.
• This file is never localized for different languages, rather, it is always interpreted in
English (it uses the comma for the field separator and the dot for the decimal
character). No thousands grouping character is used.
• Floating point values are never written in scientific notation.
When you make changes to the autodt.ini file, they do not affect any GeoMedia or
GeoMedia object-based process that is currently running. This is because the coordinate
transformation software only reads the file once at start-up time; so if the file is altered
afterwards, the process does not know about the alteration until the next time the process is
run.
In addition, when you make changes to the autodt.ini file, they do not affect
transformations that have already been persisted in a GeoMedia GeoWorkspace. This is
because the coordinate transformation software only uses the autodt.ini file to build new
datum transformations. If, for example, you make a connection and the software at that
time uses the autodt.ini file to include a datum transformation and you then save the
GeoWorkspace, any subsequent change you make to the autodt.ini file does not affect that
saved GeoWorkspace. This is because the datum transformation has already been created
and saved within the GeoWorkspace.
See the “Coordinate System Information” appendix for a list of datum-transformation
models the software supports.
Displaying Data That Has No Coordinate System

Specified
To be displayed accurately in a GeoWorkspace, all data must specify a coordinate system.
MGE, MGDM, and MGSM data already specify coordinate systems (type-56 element), but
all ARC/INFO, Arc/View, and MapInfo data and some FRAMME, CAD, and raster data
do not. To accommodate data with no specified coordinate system, you first define a
coordinate-system file (.csf) outside of the software.
To define a coordinate-system file:

1. From the Windows Start menu, select All Programs > GeoMedia > Utilities >
Define Coordinate System File.
2. On the General tab of the Define Coordinate System File dialog box, select the base
storage type—Geographic, Projection, or Geocentric—of the coordinate-system that
is to be saved to the file.
tab.
3-15

Projection resets the horizontal and vertical storage units to 1 meter. Changing the
(0,0,0).
5. Optional: To change parameters, click Projection Parameters. Depending on the
projection algorithm selected, some text boxes may be read-only.

9. Optional: On the General tab, type values in the coordinate system Name and
Description fields.
These will be saved in the .csf file. Many data servers that use .csf files will use these
values as the name and description exposed for a coordinate system, which may, for
example, be seen during Review of feature properties within the Feature Class
Definition command.
10. On the Define Coordinate System File dialog box, click Save As.
11. On the Save Coordinate System File As dialog box, select the drive and folder where
you want to save the coordinate-system file. If you do not select a path, the
coordinate-system file will be saved in the root folder of your active drive.
Select one of the following locations:
− The folder containing the specific warehouse for which the coordinate-system file
defines coordinate data. This is the preferred location.
3-16
− The folder where the warehouses are stored. The default is <drive:>\Warehouses.
It may be necessary to use this location, for example, when the actual warehouse
data are located on read-only media.
− For FRAMME data, you can specify the folder containing the gateway file fsa.gtw
or the folder named in the gralocs.txt file, which is located on the FRAMME
graphics server. The default is \win32app\ingr\frs\cfg.
12. In the File name text box, type the name that you want to give to the coordinate-
system file.
13. Verify that the Save as type is set to Coordinate System File (*.csf).
14. Click Save.
To display ARC/INFO data:
(.csf)You identify the coordinate-system file for the ARC/INFO data by creating a
<workspace>.ini file, where <workspace> is the name of the ARC/INFO GeoWorkspace
data folder. Within this file, you specify the coordinate-system file to be used. Place the
<workspace>.ini file in the ARC/INFO GeoWorkspace folder, or if that is not possible, in
the software’s \Warehouses folder specified during installation.
See the “Creating Data Server .INI Files” topic in GeoMedia Help.
To display ArcView data:

You identify the coordinate-system file for the ArcView data by creating a
<workspace>.ini file, where <workspace> is the name of the ArcView GeoWorkspace
data folder. Within this file, you specify the coordinate-system file (.csf) to be used. Place
the <workspace>.ini file in the ArcView GeoWorkspace folder, or if that is not possible, in
the software’s \Warehouses folder specified during installation ($/GeoMedia/bin is the one
specified for the .ini file).
To display CAD-server data:

For CAD-server data, perform the following:
• Specify the coordinate-system file(s) in the CAD schema definition (.csd) file.
• While creating the .csd file on the Files tab of the CAD Server Definition dialog box,
select all the coordinate-system files to be used, and specify the coordinate-system file
on the Coordinate Systems tab.
• For the IGDS Scanner, you can use either a .dgn file (with a type-56 element) or a .csf
file (created by Define Coordinate System File) to specify the coordinate-system
information.
• For the AutoCAD Scanner, you can use only a .csf file (created by Define Coordinate
System File) to specify the coordinate-system information.
3-17
To display FRAMME data:

For FRAMME data, there are two ways to get spatially accurate displays:
Method 1
Under the [CoordinateSystem] keyword of the FRAMME .ini file, specify a design
file (.dgn) that contains a type-56 element. The syntax is FILE=<filename>. For
example, FILE=myfile.dgn.
If the design file you specify does not contain a type-56 element, the working units and
global origin defined in the type-9 element will be used to create a coordinate system.
If you do not specify a design file, the wrk_seed.dgn file on the FRAMME server will be
used to create a coordinate system.
See MGE Basic Nucleus or MGE Projection Manager documentation for information
about type-56 elements.
Method 2
Define a coordinate-system file (.csf) that contains the coordinate-system parameters of the
FRAMME data. Then identify the coordinate-system file under the
[CoordinateSystem] keyword in the FRAMME .ini file as follows:
FILE=<filename>. For example, FILE=myfile.csf.
To display MapInfo data:

You identify the coordinate-system file for the MapInfo data by creating a
<workspace>.ini file, where <workspace> is the name of the MapInfo GeoWorkspace
folder. Within this file, you specify the coordinate-system file (.csf) to be used. Place the
<workspace>.ini file in the MapInfo GeoWorkspace folder, or if that is not possible, in the
software’s \Warehouses folder specified during installation.
If there is no .ini file, the data server will look for a .csf file in the MapInfo GeoWorkspace
folder that bears the same name as the MapInfo table and use that .csf file for the
corresponding GeoMedia feature class. This way, you need one .csf file for one feature
class in the GeoWorkspace folder. You cannot use a single .csf file for the whole folder
unless you specify it in the .ini file.
See the “Creating Data Server .INI Files” topic in GeoMedia Help..
To display raster images:

For Intergraph-format raster images that are inserted using the by-header placement mode
or other raster formats that have an associated ESRI word file, you define a coordinate-
system file and then insert the image into a read-write warehouse.
See the “Working with Images” chapter and the “Raster Information” appendix.
3-18
To edit a coordinate-system file:

To edit an existing .csf file, double click the file name. This opens the Define Coordinate
System File dialog box. Make changes to the file, and click OK.
Creating Coordinate-System Files from Design

Files
You can easily create a coordinate-system file (.csf) from an IGDS design file (.dgn) with
Define Coordinate System File. This utility can read a .dgn file if you:
1. Drag the .dgn file from Explorer onto the Define Coordinate System File icon.
OR
2. Rename the file from a .dgn extension to a .csf extension and then double click to open
the file in Define Coordinate System File.
OR
After invoking the Define Coordinate System File utility from the Start menu, select
the Load button. Then on the Load Coordinate System From File dialog box,
change the Files of type selection to Design Files (*.dgn).
Note that Define Coordinate System File can only read .dgn files, not write to them. The
only format this utility can write to is the .csf (OLE compound files structured-storage)
format. If you want to write coordinate-system information into a type-56 element of a
design file, you need to use MGE. Also, in this 6.0 version of the software, MicroStation
Version 8 .dgn files cannot be read.
Define Coordinate System File reads .dgn files with or without a type-56 element.
Without a type-56 element, it reads only the information on working units (storage units)
and global origin (storage center) from the type-9 element. It then sets the projection to
Rectangular Grid, which means no algorithm is defined to get from Projection to
Geographic coordinates. With a valid type-56 element, in addition to reading the type-9
element, this utility reads projection and datum information from the type-56 element.
A potential workflow to use this capability would be with CAD server when you have .dgn
data, and 1) the .dgn data does not contain a type-56 element with projection information,
and 2) the information of the .dgn about working units (storage units) and global origin
(storage center) is valid.
In this case, if you know the projection information, but for example were digitizing with
vanilla MicroStation, you may want to use Define Coordinate System File to read the
working units and global origin information of the .dgn. You would then use it to define
the projection and datum, and you would save the information out to a .csf file.
3-19
3-20
Working with Warehouses
You display feature geometries and attribute data in a GeoWorkspace through connections
to warehouses where the data are stored. Each warehouse connection uses a data server to
convert the data into a format that the software can display. Connections are links that
allow the transfer and translation of feature data from the various supported data
warehouse types.
You can output feature data in any GeoMedia-supported format to a warehouse with the
Output to Feature Classes command. You must have at least one read-write open
connection to use this command.
See the “Outputting Feature Data to Warehouses” section of the “Working with Features”
chapter
The New Connection command lets you to easily create warehouse connections. This
command guides you through the process of entering the information necessary to define
and to make the connection to your data. You specify the name and location of the
connection and all the necessary connection parameters. This command lets you specify a
warehouse configuration (.ini) file for many data connections. You can create the .ini files
using the Define Warehouse Configuration Utility before connecting to the data.
Note: Access-based warehouses, catalogs, and libraries all use *.mdb files. You should
maintain these in separate directories in order to make the individual database type more
easily found. In addition, the software has separate folder locations for the Access versions
of these files, and you should add the word catalog, library, or warehouse to filenames in
order to distinguish them from each other. Oracle and SQL Server can also contain
libraries and catalogs, and the associated schemas should be named to distinguish them
from standard spatial schemas.
4-1
See the “Creating Data Server .INI Files” and the “New Connection Dialog Box” topics
in GeoMedia Help and the Define Warehouse Configuration File utility’s online Help for
complete information.
This version of the software lets you connect to data created in the following formats:
• Access • MGE Data Manager
• ARC/INFO • MGE Segment Manager (MGSM)
• ArcView shapefile • ODBC Tabular
• CAD – AutoCAD and MicroStation®/IGDS • Oracle® Object Model
• FRAMME™ • SQL Server
• GeoGraphics • SmartStore Server
• GML • Text File Server
• I/CAD MAP • WFS
• MapInfo • WMS
• (MGDM)Modular GIS Environment (MGE)
See the “Working with Map Windows” and “Working with Data Windows” chapters for
more information.
All warehouse types are read-only, except for Access, Oracle, and SQL Server. This
protects the integrity of your source data. So, if you want only to display data in the
software from one or more warehouses, you simply create one or more warehouse
connections and then use map windows and data windows to display the data.
This is a representative workflow for accessing the warehouse data you want to display:
1. Open a new GeoWorkspace.
2. Connect to the warehouse containing the data for your area of interest.
3. Connect to other warehouse(s).
4. Display the feature data.
If you want write access to the data in the software—to add new features or change
attributes of existing ones, for example—you create a new Access warehouse and import
data into it. You may also import data into an Oracle Object Model or SQL Server
warehouse assuming you have a read-write connection.
Whether you are displaying data or writing it, your GeoWorkspace can contain data from
many different sources, even those whose native data types are incompatible.
This is a representative workflow for importing data into a read-write warehouse:
1. Follow the steps in the preceding workflow to identify the area for which data are to be
imported.
2. Optional: Define a coordinate system for the empty warehouse. (The GeoWorkspace
defaults to the coordinate system from the first feature added to the legend.)
3. Import feature classes from the connected warehouses into your read-write warehouse
(Access, Oracle Object Model, or SQL Server).
4-2
Creating a Read-Write Access Warehouse

A read-write Access warehouse can contain feature class definitions, features, raster
images, and a coordinate system.
Like a GeoWorkspace, a read-write Access warehouse is built on a template, and you can
create your own template(s) or use an existing one. The software is delivered with a
default Access warehouse template, normal.mdt.
See the “Working with Features” chapter.
If you accidentally delete the normal.mdt file, you may have to run repair to re-install the
normal.mdt template. If you have Microsoft Access, you can create a blank .mdb file to
use as your template. Be sure and follow the instructions for defining a warehouse
coordinate system, since this default database will not have one. Better still, make a
backup copy of the template.
Note: Warehouse, catalog, and library all use *.mdb files. Therefore, you should maintain
files for each of these three components in separate folders, or under separate users in SQL
Server and Oracle. In addition, the software has special and separate folder locations for
the Access versions of these files, and you should add catalog, library, or warehouse to
filenames (Access) or user names (SQL Server, Oracle) to help distinguish between files
for each use.
To create a read-write Access warehouse:

1. Select Warehouse > New Warehouse.
2. On the Warehouse Template dialog box, select a template. The default is
normal.mdt.
3. Verify that the Document option is selected.
4. Click New.
5. On the New Warehouse dialog box in the Save in field, select a storage location. The
default is <drive:>\Warehouses.
Note: The default storage location is established when the software is installed, but
you can change it in the product from the File Locations tab of the Options dialog box
(Tools > Options).
6. In the File name field, type a unique file name.

7. Leave Access as the file type.
8. Click Save.
4-3
Defining a Coordinate System for a Warehouse

Normally, you define a warehouse coordinate system only for an empty read-write Access
warehouse that you just created. You can view but cannot change the coordinate system in
a warehouse in which feature classes already exist, but you can accomplish a change to the
coordinate system with the following procedure:
1. Create a new read-write Access warehouse.
2. Change the coordinate system.
3. Import the data into the new warehouse.
4. Delete the old warehouse.
If you plan to use multiple coordinate systems in your Access warehouse, you need to
assign one coordinate system to use as the default. To do this, type Default in the
Description field when naming or assigning a coordinate system to a feature class.
When digitizing in GeoMedia, you must ensure that the GeoWorkspace coordinate system
matches the coordinate system of the feature class into which you are digitizing. Failure to
do so can result in data that contains incorrect coordinates. GeoMedia will compare the
GeoWorkspace coordinate system to the coordinate system of the feature you select for
editing and will warn you if there is a mismatch. It will be up to you to rectify the
mismatch.
See the “Working with Coordinate Systems” chapter.
Preparing to Connect
As the universal geographic client, the software lets you combine data from many sources
and in different formats into one spatially accurate environment. To ensure accuracy, you
must set up your data servers and provide the software with certain information about the
data you want to view. Each data type requires different information; the following
sections cover special procedures or information required for each.
Connecting to an Access Warehouse

To connect to an Access database, you must identify or select an Access GeoMedia
Database file (.mdb).
Connecting to an ARC/INFO Warehouse

To connect to an ARC/INFO warehouse you must identify or select an ARC/INFO
warehouse folder. Before trying to connect, check the following:
• ARC/INFO data must be in native format (not exported). Native format requires a
warehouse folder that contains subfolders corresponding to coverages and an \INFO
folder that contains an ARCDR9 or ARC.DIR file.
4-4
• A coordinate-system file (.csf) for the ARC/INFO data must be created with Define
Coordinate System File.
• The coordinate-system file for the ARC/INFO data must be identified in a
<Arc/Infoworkspace folder name>.ini file, which should be stored in the ARC/INFO
GeoWorkspace folder, or if that is not possible, in the software’s \Warehouses folder.
• For ease of maintenance, you should store the .csf and .ini files along with the data in
the ARC/INFO warehouse folder as the primary location. When this is not possible
(due to read-only media, for example), you should store these files in the default
warehouse location, and the software will find them there.
The software does not support the PC version of ARC/INFO.
See “Displaying Data That Has No Coordinate System Specified” in the “Working with
Coordinate Systems” chapter and the “Creating Data Server .INI Files” topic in
GeoMedia Help.
Connecting to an ArcView Warehouse

To connect to an ArcView warehouse, you must identify or select an ArcView Shape Files
folder. Before trying to connect, check the following:
• ArcView data must be in native format (not exported). Native format requires a
warehouse folder that contains themes with each theme having its individual .dbf, .shp,
and .shx files.
• A coordinate-system file (.csf) for the ArcView data must be created with Define
Coordinate System File.
• The coordinate-system file for the ArcView data should be identified in a <workspace
name>.ini file, which should be stored in the Arc View Shape Files folder, or if that is
not possible, in the \Warehouses folder of the software.
• For maintenance ease, you should store the .csf and .ini files along with the data in the
ArcView Shape Files folder as the primary location. When this is not possible (due to
read-only media, for example), you should store these files in the default warehouse
location, and the software will find them there.
• If an <ArcView Shape Files folder>.ini file is not found, the server looks for a <theme
name>.csf file in the \GeoWorkspaces folder.
GeoMedia Help.
Connecting to a CAD Warehouse

To connect to a CAD warehouse, you must identify or select a CAD Server Schema file.
Before trying to connect, check the following:
4-5
• For AutoCAD and MicroStation V8 data, a coordinate-system file (.csf) must have
been created with Define Coordinate System File
See “Displaying Data That Has No Coordinate System Specified” in the “Working
with Coordinate Systems” chapter.
• For IGDS and AutoCAD data, an ODBC data source must have been created if there
are database attribute linkages that have to be served.
• A CAD schema definition file (.csd) must have been defined with Define CAD Server
Schema File utility (Start > All Programs > Product_Name > Utilities > Define
CAD Server Schema File). The CAD data server allows you to use MicroStation V7
design files (with or without attribute linkages) or AutoCAD files (.dwg/.dxf with or
without database attribute linkages) or MicroStation V8 design files (without attribute
linkages) as a GeoMedia data source.
Note: In order to use the Define CAD Server Schema File utility, you must have clear
and complete understanding of your CAD data.
You can specify a .ini file in the .csd file that allows for persistent caching. Persistent
caching is done in CAD data server to improve server performance.
See the Define CAD Server Schema File utility’s online Help for complete information
about this utility.
Supported MicroStation Element Types

The following table lists the MicroStation element types supported by GeoMedia:
Type Name GDO Geometry Type
2 Cell (named) OrientedPointGeometry, TextPointGeometry, and
Collection Geometry. This is served based on the .ini
file variables.
2 Cell (orphaned) BoundaryPolygonGeometry
2 Cell (unnamed) BoundaryPolygonGeometry
3 Line PolylineGeometry and OrientedPointGeometry. In case
of degenerate lines, OrientedPointGeometry is served.
4 LineString PolylineGeometry
6 Shape PolygonGeometry
7 TextNode TextPointGeometry (collection)
11 Curve Stroked PolylineGeometry
12 Complex String CompositePolylineGeometry
14 Complex Shape CompositePolygonGeometry
15 Ellipse PolygonGeometry
16 Arc Stroked PolylineGeometry for elliptical arcs.
ArcGeometry for circular arcs.
4-6
17 Text TextPointGeometry
22 Point OrientedPointGeometry (collection)
35 Shared Cell OrientedPointGeometry, TextPointGeometry, and
CollectionGeometry. This is served based on the .ini file
variables.
Connecting to a FRAMME Warehouse

To connect to FRAMME data, the software needs a valid FRAMME gateway file (.gtw).
You specify the location of the FRAMME Gateway file and select the FRAMME segments
you want. Identifying a warehouse configuration (.ini) file is optional.
If necessary, use Define Coordinate System File to create a coordinate-system-file for
your FRAMME data. Also, certain data configurations may require a
<rulebase_name>.ini file for your FRAMME data server.
GeoMedia Help.
Connecting to a GeoGraphics Warehouse

To connect to a GeoGraphics warehouse, you must set up an ODBC data source name that
identifies the project database. Then, to connect to the warehouse, you need to identify a
GeoGraphics project folder. The GeoGraphics project folder should contain MicroStation
V8 design files. The data server ignores all the missing/invalid map files, including any
MicroStation V7 design files that may be present in the project folder. If the ODBC
connection requires a user name and a password, you are prompted to supply them each
time the warehouse connection is opened. If you would like to specify the ODBC
connection parameters only once, use the Advanced option on the Warehouse > New
Connection dialog box.
On the New Connection dialog box, you specify the following parameters:
• GeoGraphics project folder (full path to where the project is located)
• Warehouse configuration (.ini) file (optional)
• ODBC data source (DSN)
• Advanced Information (DSN, username, password, and additional ODBC parameters
about the schema)
See the “Creating Data Server .INI Files” topic in GeoMedia Professional Help
Connecting to a GML Warehouse

To connect to a GML (Geography Markup Language) Server warehouse, you must indicate
the following:
4-7
• GML file, the .gml / .xml filename with its full path or address. The file can be a file
on the disk or an URL of a .gml file on the Web.
• Advanced options:
o When the GeoReferenceService (GRS) fails to return the coordinate system (CS)
object for a given EPSG code and a matching coordinate system file is not found
for a feature class in the default \EPSG folder, the options are:
− Ignore the coordinate system, that is, serve the feature class data without the
coordinate system.
− Skip the feature class.
− Abort the connection and report an error about the missing coordinate system
file.
o When the GeoReferenceService (GRS) fails to return the coordinate system (CS)
for a feature instance in the default \EPSG folder, the options are:
− Serve with the coordinate system of the feature class, that is, serve the feature
instance data with the coordinate system of the feature class.
− Skip the feature instance.
− Serve only the attributes of feature instance data, that is, the geometry is made
NULL.
− Abort the query and report an error about the missing coordinate system file
for the feature instance.
o Swap the coordinate order for the following coordinate system types: Geographic
and Projected.
Connecting to an I/CAD MAP Warehouse

You can connect to an I/CAD MAP warehouse in two ways: through the GeoMedia
Warehouse > New Connection command or through GeoMedia automation objects.
Connecting through the New Connection Command

To connect to an I/CAD MAP warehouse, you specify the following parameters on the
New Connection dialog box:
• I/CAD MAP file, required
• Coordinate system file, recommended but not required
• An optional warehouse configuration file (.ini) to provide parameters like geometry
types for feature classes, linkage information for the feature classes, and the rich text
parameters required to serve text.
4-8
Connecting through GeoMedia Automation Objects

To connect to an I/CAD MAP warehouse using GeoMedia automation objects, you need to
specify the connection string in the format specified as follows:
DATA=<MAP file name with the complete path>[;CSF=<coordinate system file
name with the complete path>][;INI=<INI file name with the complete path>]
You must replace the parts enclosed by angle brackets (< >) with appropriate values. The
following example (VB code snippet) illustrates usage of GeoMedia’s Connection object to
connect to an I/CAD MAP warehouse:
Dim objConn As Object
Set objConn = CreateObject("GeoMedia.Connection")
With objConn
.Type = "ICADMAP.GDatabase"
.Name = "I/CAD MAP Connection 1"
.Location = "I/CAD MAP file location"
.Mode = gmcModeReadOnly
.ConnectInfo = “DATA=\\node1\ICADMAP\data\Florida\Florida.map;” & _
“CSF=\\node1\ICADMAP\data\Florida\Florida.csf;” & _
“INI=\\node1\ICADMAP\data\Florida\Florida.ini"
.Connect
End With
Connecting to a MapInfo Warehouse

To connect to a MapInfo warehouse, you must specify the folder location of the MapInfo
files, the MapInfo Tables folder with valid MapInfo tables (.tab or .txt files). The server
can then read the MapInfo tables in the folder and create the feature classes. Before trying
to connect, check the following:
• A coordinate-system file (.csf) for the MapInfo data must be created with Define
Coordinate System File and be referenced by the .ini file. There can be one .csf file
for the entire MapInfo dataset or one .csf file created for each MapInfo table.
• MapInfo data must be in native format (not exported). There should be a table file
(.tab), an index file (.id), a map file (.map), and/or an info file (.dat/.dbf or .xls). All
four files are needed for both geometry and attribution.
• The coordinate-system file(s) for the MapInfo data should be identified in a <MapInfo
Tables folder name>.ini file using the COORDINATE SYSTEM: .ini variable. If a
<MapInfo Tables folder name >.ini file is not found in the \Warehouses folder or the
MapInfo Tables folder, the server looks for a <MapInfo Tables folder name>.csf file
in the MapInfo Tables folder. If this is not found, the server looks for a <MapInfo
Tables folder name>.csf file in the MapInfo Tables folder.
• The software geometry type (point, linear, areal, graphicstext, or anyspatial) for each
MapInfo Table can also be defined in the <MapInfo Tables folder name>.ini file using
4-9
the GEOMETRY TYPE: variable. If there is no entry in the .ini file regarding
geometry type for a coverage, the data are served up as AnySpatial.
• If the coverage has text in addition to a point, linear, or areal geometry, use the
TEXT: variable in the <MapInfo Tables folder name>.ini file to enable the data
server to serve up Text. The server will not display the Text Geometry for a coverage
if this is not enabled in the <MapInfo Tables folder name>.ini file.
• The COORDINATE SYSTEM: section should be the first section in the <MapInfo
Tables folder name>.ini file. The other sections may or may not be present. If they
are present, they may be in any order.
GeoMedia Help.
Connecting to an MGE or MGDM Warehouse

Before you can connect to an MGE or MGDM warehouse, you must set up an ODBC data
source name that identifies the project database. The ODBC data source must have the
same name as the schema identified in the MGE or MGDM (.mge) project file. Verify that
the path variable in the .mge file matches the actual folder/location for the MGE project.
Then, to connect to the warehouse, you need to identify an MGE or MGDM (.mge) project
file. If the ODBC connection requires a user name and a password, you are prompted to
supply them each time the warehouse connection is opened. If you would like to specify
the ODBC connection parameters only once, use the Advanced option on the Warehouse
> New Connection dialog box. Identifying a warehouse configuration (.ini) file is
optional.
Connecting to an MGSM Warehouse

To connect to MGSM data, you will need to identify the following:
• MGE project file (.mge)
• Warehouse configuration file (.ini)
• Parameter file (.prm)
• Seed file (.dgn)
• Coordinate file (.crd)
• RIS schema password (if using RIS and the schema is passworded)
Use your ODBC Administrator to set up access to distributed attribute tables in warehouses
that you access through ODBC connections. To access an MGSM warehouse from ODBC
4-10
client, you need to have an ODBC driver installed on your machine corresponding to your
database. You also need to configure the ODBC driver to point to your database with a
DSN (Data Source Name). This DSN is the schema name in the .mge file.
Connecting to an ODBC Tabular Warehouse

Before you try to connect to an ODBC Tabular Model warehouse, you must set up an
ODBC connection through the ODBC Data source Administrator. You will need to choose
the correct ODBC driver for the database you want to connect and enter the appropriate
information.
To connect to ODBC Tabular Model data, you will need to identify the following:
• ODBC connection name.
• ODBC Data source (from the ODBC Administrator).
• User name (as required by data source).
• Password (as required by data source).
Using the ODBC Tabular read-only data server is an alternative to using the Attach table
command (Warehouse > Feature Class Definition). This data server uses Microsoft’s
ODBC and ADO technology to create a warehouse connection and to serve up any type of
data that can be used with the Settings > Control Panel, Data Sources (ODBC)
command. If you are connecting to text files, you place the files in a folder to themselves
and then use the Data Sources (ODBC) command to create a Data Source Name (DSN)
that points to the folder containing the data. The connection will read the Schema.ini file
found in the folder to determine the format of the text file(s). You can create the
Schema.ini file manually or use the Data Sources command to create the file.
See “Working with Feature Classes” in the “Working with Features” chapter for
information on the Feature Class Definition command.
You can also use ODBC Tabular to serve up tables from other formats and databases as
nongraphic (data) tables. Examples might include Dbase, Paradox, Excel, and so forth.
Note: It is strongly recommended that you use ODBC Tabular only for data types that do
not have a data server available in GeoMedia. For example, do not use the ODBC Tabular
data server to connect to Access; instead connect using the Access data server.
If you are using the ODBC Tabular data server to connect to Excel (.xls), you need to
define a named range in the Excel workbook to expose a table name. By default, the range
is usually already defined as all rows and the name is defined as the sheet name. You can
easily define a name in Excel by selecting the range of data for the table and then using the
Insert > Name > Define command.
4-11
You cannot use the ODBC Tabular data server to connect to Oracle Object Model
warehouses. You can, however, use it to connect to any Oracle schema containing
attribute data.
For more information on Excel, ODBC, and ADO technology see
http://www.microsoft.com.
Connecting to an Oracle Object Model Warehouse

Before you try to connect to an Oracle Object Model warehouse, you must have already set
up an Oracle database server with Oracle’s Spatial Cartridge and added a user account
containing object model data that you want to access.
At a minimum, the Oracle Client software must reside on the system running the software,
and you must create a database alias/service. Use the Oracle Net 8 configuration utility to
configure a database alias/service.
See the Oracle documentation for more information.
To connect to Oracle Object Model data, you will need to identify the following:
• Oracle connection name.
• Whether to use Windows to authenticate the network login ID or to use Oracle
database to authenticate the user ID and password.
• User name.
• Password.
• Host string. The host string is the Oracle database alias/service name that you create
with the Oracle network configuration utility.
Connecting to a SmartStore Server Warehouse

The GeoMedia SmartStore warehouse is a spatially indexed cache of 2-D geometry and
significant attributes used to facilitate the quick generation of maps without querying the
original warehouse database. It supports all of the GeoMedia GDO-based warehouse
types. The GeoMedia SmartStore data server supports read-only access to the SmartStore
warehouse.
See the Publish to GeoMedia SmartStore Warehouse utility’s online Help for complete
information on this server and its limitations.
Before you try to connect to a GeoMedia SmartStore warehouse, you must indicate the
following:
• A single GeoMedia SmartStore file (.ddc)
OR
4-12
• A GeoMedia SmartStore GeoWorkspace folder containing one or more GeoMedia

SmartStore files.
Note: The Select a folder containing GeoMedia SmartStore files option on the New
Connection dialog box assumes that the .ddc files you have published to this folder came
from a single source warehouse. If your folder contains .ddc files from multiple source
warehouses, you will encounter errors.
You have the option of using the coordinate system of the input warehouse, or of
specifying that SmartStore is to transform the data to a different coordinate system.
Connecting to an SQL Server Warehouse

Before you try to connect to an SQL Server warehouse, you must set up a SQL Server
database.
To connect to SQL Server data, you will need to indicate the following:
• SQL connection name.
• Server name.
• SQL Server database name.
• Whether to use Windows to authenticate the network login ID or to use SQL Server to
authenticate the user ID and password.
• Login.
• Password.
Connecting to a Text File Server Warehouse

To connect to Text File Server data, you will need to indicate the following:
• Input data text file, which can be any ASCII file.
• Text format definition file (.tfd)
• Coordinate system file (.csf) - optional
Connecting to the Text File Server is a two-step process. You must first define the format
of the input data file so that the server can understand it. The Define Text File Server
Format File utility lets you perform this definition. Then you perform the actual
connection with the New Connection command, using the format definition file as input,
in addition to the input data file, and an optional coordinate system file.
See the Define Text File Server Format File utility’s online Help for complete information.
Connecting to a WFS Server Warehouse

Before you try to connect to a WFS (Web Feature Server) warehouse, you must indicate
the following:
• WFS connection name and optional description
4-13
• WFS URL
o When a matching coordinate system file is not found for a feature class in the
default \EPSG folder, the options are:
– Ignore the coordinate system, that is, serve the feature class data without
coordinate system.
– Skip the feature class.
– Abort the connection and report an error about the missing coordinate system
file.
o Swap the coordinate order for the following coordinate system types: Geographic
and Projected.
Connecting to a WMS Warehouse

Before you try to connect to a WMS (WebMap Server) warehouse , you must indicate the
following:
• WMS connection name and optional description
• Web Map Server (WMS) URL
o When the GeoReferenceService (GRS) fails to return a coordinate system (CS)
for a feature class in the default \EPSG folder, the options are:
– Skip feature class.
– Abort the connection and report an error about the missing coordinate system
file.
Working with Connections

To make connecting to your data a simple matter, the software provides the New
Connection command. Before you start, you need to know what type of connection you
want to make, the name and location of certain files, and other server-specific information.
The connection types available to you depend on which data servers were installed during
setup. The complete list of available connection types appears in the New Connection
dialog box. If you want a connection type for a data server that the software provides but
that does not appear in the Connection type list, you can add it by reinstalling the
software. The connection type you choose determines what additional information you
need. You can also create a new connection by the same procedure through the New
button of the Connections command (Warehouse > Connections) described later in this
4-14
section. The Connections command also lets you open, close, reopen, and delete
connections as well as view and edit connection parameters.
Enabling AFM Proxy Servers for GeoMedia PublicWorks

Manager
One of the connection parameters lets you enable a data server to use an AFM (Advanced
Feature Model) proxy server to proxy the warehouse connection. An AFM proxy server is
one that is AFM aware or enabled so that it can process AFM metadata if it is present.
See the GeoMedia PublicWorks Manager documentation for more information on proxy
servers (Available with GeoMedia PublicWorks Manager).
You enable this capability by checking the Enable advanced feature model check box,
below the Connection type list, on the New Connection dialog box. You can later change
this setting through the Connections command on the Properties dialog box, displayed
when you click the Properties button. This check box is enabled if the following criteria
are met.
• The AFM proxy server is available.
• The data server is one of the following servers:
o Access read-only o Oracle Object LTT read-write
o Access read-write o Oracle Object Model read-only
o DB2 read-only o Oracle Object Model read-write
o DB2 read-write o SQL Server read-only
o Oracle Object LTT read-only o SQL Server read-write
For all other cases, the connection is not proxied.
While using the Connections command, verify if the connection type is AFM.GDatabase.
In such case, instead of displaying the data server type as AFM, the underlying data server
name is determined and populated.
Setting Connection Status

The Connections command lets you set the connection status by opening, closing, and
reopening connections. The dialog box of this command displays all the connections
present in the GeoWorkspace in a grid, sorted in alphabetical order by name. The read-
only columns display the name, connection type, and warehouse. The status of a
connection is indicated by an icon to the left of the connection name as follows:
Open Read-Write
Open Read-Only
Closed
Your choices of status are summarized in the following table:
4-15
Command Button Initial Final Connection Status

Connection
Status If the data server is If the data server is
read-only: read-write:
Open Connection Open read-write N/A No action – status
remains unchanged.
Open read-only No action – status No action – status
remains unchanged. remains unchanged.
Closed Open read-only Open read-write
Open Read-Only Open read-write N/A No action – status
remains unchanged.
Open read-only No action – status No action – status
Closed Open read-only Open read-only
Reopen Connection Open read-write N/A Open read-write
Open read-only Open read-only Open read-only

Closed N/A N/A
Close Connection Open read-write Closed Closed
Open read-only Closed Closed
Closed No action – status No action – status
If you choose an open status, the software creates a physical connection to the warehouse.
If you choose a closed status, you will not have immediate access to the data. Later you
can change the status simply by editing the warehouse connection status. Reopening
connection(s) closes and then automatically reopens the selected connection(s) as a
shortcut for refreshing their contents.
Note: The Library and Catalogs commands use a similar connection system and
interface.
Viewing and Editing Connection Properties

Properties lets you display the appropriate connection properties control for the data
server involved and also edit those properties. The Properties dialog box offers you
convenient and usable browsing of the connection parameters, unlike the Warehouse
column on the Connections dialog box, which presents the connection parameters for the
warehouse as a single text string. After reviewing the connection properties, you can then
edit them as necessary for your workflow.
4-16
To create a new warehouse connection:

1. Select Warehouse > New Connection.
2. Select the Connection type appropriate for your data.

3. Optional: Check the Enable advanced feature model check box if available.
4. Type a Connection name, or keep the default.
5. Optional: Type a Connection description.
6. Provide the remaining required information, which varies with each connection type;
then click OK.
IMPORTANT: Avoid opening more than one connection to a single warehouse.
To open, reopen, or close a warehouse connection:

1. Select Warehouse > Connections.
2. Select the row selector of the row(s) whose open/close status you want to change.
4-17
Note: Use Shift/Ctrl to select multiple rows; click the top left-corner grid button, to
the left of the Name row, in order to select all rows.
3. Click the appropriate open, reopen, or close button.

To create a new warehouse connection:
2. Click New to display the New Connections dialog box; then follow the previously
described procedure to create a new warehouse connection
To view or edit warehouse connection properties:

2. On the Connections dialog box, select the row of the connection whose properties you
want to view or edit; then click Properties.
Viewing Changes in a Multi-User Environment

You can use Warehouse > Refresh with Warehouse Changes to update the workspace
for any changes made to the schema outside your GeoMedia session. This is useful in
multi-user environments where other GeoMedia users may be making modifications to the
same schema you are using. Changes you make though non-GeoMedia software do not
appear unless you close and reopen the connection or you restart your session. The
exception is with the use of the Oracle Object Model data server. In an Oracle schema,
you can assign Modification Log triggers to the feature classes you wish to track. These
Modification Log Triggers are assigned to feature classes using Database Utilities, and
they log all insert, update, or delete events. Refresh with Warehouse Changes then picks
4-18
up external modifications on these feature classes even if the changes are made by non-
GeoMedia applications.
Creating an Access Warehouse Template

The default location for warehouse templates is <drive:>\Program
Files\GeoMedia\Templates\Warehouses. You can specify a different folder through Tools
> Options > File locations.
To create an Access warehouse template:

1. Select Warehouse > New Warehouse.
2. On the Warehouse Template dialog box, select the Template option.
3. Select the normal.mdt template, and click New.
4. On the New Warehouse dialog box, accept the default storage folder, or browse to
select a new one. If you have named an alternate file location for warehouse templates,
that location appears in the Save in field.
5. Verify that Access Template appears in the Save as type field.
6. Type a name for the template in the File name text box.
7. Click Save.
Changing the Coordinate System of a New Access

Warehouse Template
Because the New Warehouse command does not establish a connection when you use it to
create a new Access warehouse template (.mdt), you should use the following workflow to
change the coordinate system of such a new template.
To change the coordinate system of a new access warehouse template:

1. Using the procedure from the previous section, create and save a new Access
warehouse template, selecting normal.mdt as the template on the New dialog box.
Note: Because you are creating a template, no GeoWorkspace coordinate-system

matching occurs, regardless of the preference setting.
2. Select Warehouse > New Connection.

3. On the New Connection dialog box, select Access as the connection type.
4. Type a connection name, or keep the default.
4-19
5. Select your new template as the new GeoMedia database file. You must either type the
full path or change the file dialog filter to *.* if you browse for your new template.
6. Optional: Type a description of the connection.
7. Click OK.
8. Select View > GeoWorkspace Coordinate System, and proceed to change the
appropriate values.
9. Select Warehouse > Edit Connection to close and to delete the connection to the
template.
Note: After changing the coordinate system, the new Access warehouse template is ready
for you to use to create new warehouses. When you turn on the Match GeoWorkspace
and Warehouse coordinate systems options on the General tab of the Options dialog
box (Tools > Options), the coordinate system defined in the template by the previous
procedure will be the coordinate system of the newly created Access warehouses.
Configuring PickLists with Access Warehouses

GeoMedia includes support for the use of PickLists through the Properties dialog box
(Edit > Select Set Properties). PickLists allow for a predefined list of values to be used
when updating attribute fields.
GeoMedia determines if an attribute has a PickList by querying a preconfigured metadata
table. The name of the table that stores the PickList configuration must be defined in
GAliasTable with a TableType of INGRPickLists. You can use any name you want for the
PickList definition table as long as it is referenced in the GAliasTable.
Use Microsoft Access to make the necessary changes to the GAliasTable. For example, if
the PickList definition table were called GPickListTable, the following entries would need
to be added to GAliasTable:
GAliasTable
TABLETYPE TABLENAME
INGRPickLists GPickListTable
The table referred to by the GAliasTable entry for INGRPickLists must contain the
following fields: FeatureName, FieldName, PickListTableName, ValueFieldName,
DescriptionFieldName, and FilterClause. Use the New Table command in Access to
create the PickList metadata table using the following provided definitions (the table itself
can be called anything as long as it is referenced in the GAliasTable):
4-20
GPickListTable
Column Name Datatype
FeatureName Varchar(255)
FieldName Varchar(255)
PickListTableName Varchar(255)
ValueFieldName Varchar(255)
DescriptionFieldName Varchar(255)
FilterClause Varchar(255)
In the table definition:

• FeatureName and FieldName refer to the Feature Class and the specific Attribute
field for which the PickList is to be used.
• PickListTableName specifies a table in the schema containing the PickList values.
• ValueFieldName and DescriptionFieldName refer to the name of the fields in the
table containing the PickList values.
• The ValueFieldName specifies the field in the PickList table that contains values to be
stored in the database. The datatype of the field in the PickList table specified here
must match the datatype of the Attribute assigned in the FieldName.
• The DescriptionFieldName specifies the field that contains PickList descriptions to be
displayed in the pop-up menu on the Attribute tab of the Properties dialog box.
• The values stored in ValueFieldName and DescriptionFieldName could be the same
when the displayed values are the same as the stored values.
• The FilterClause is optional and may contain an SQL where clause that will be used
to filter the records in the PickList. The filter allows a single PickList table to be used
when creating multiple PickLists.
PickList tables can be any tables that contain the required information, including existing
feature classes. You can implement a PickList as a code list (using separate value and
description entries) or as a domain list (when value and description entries are the same).
Ranges are not supported.
4-21
The following is an example of tables, columns, and values that could be defined for
PickLists:
GAliasTable
TableType TableName
INGRPickLists GPickListTable
GPickListTable
FeatureName FieldName PickListTableName ValueField
Name
Buildings Name PL_Building CodeValue
Buildings State PL_State StateName
Buildings Type PL_Building CodeValue
DescriptionFieldName FliterClause
ValDescription Bld_Type =
'NAME'
Desc
ValDescription Bld_Type =
'TYPE'
PL_Building
CodeValue ValDescription Bld_Type
0 MOTEL TYPE
1 MARRIOT NAME
2 HOLIDAY INN NAME
3 BED AND BREAKFAST TYPE
PL_State
StateName Desc
Alabama ALABAMA
Arkansas ARKANSAS
Colorado COLORADO
Texas TEXAS
Florida FLORIDA
4-22
Working with Images
In GeoMedia, raster images, such as a scanned map sheet, an aerial photograph, or a
satellite image, reside in image feature classes. Image feature classes are distinguished
from one another based on the coordinate system of the feature class. You can only insert
images into an existing feature class when the coordinate systems of the image and the
feature class are in agreement. All the images in an image feature class can be represented
by a either a single legend entry or multiple legend entries. You can add images to existing
feature classes as needed, without the images being displayed, thereby managing system
resources more efficiently.
Inserting Images into Warehouses

You can insert a raster image into a read-write warehouse and use it as a logo or a
backdrop in your GeoWorkspace. The image file is not moved from its location on your
hard disk, but the paths to the image and the geometry of the image are saved in the
warehouse. To edit or to change the actual image content (image pixels), you must edit the
source file. Image linkage and geometries are stored in the database tables (warehouse
feature classes) and are managed like any other feature. While multiple images can be
represented by a single legend entry, they must be images from the same feature class.
Note: Avoid inserting multiple images with the same filename into a single warehouse,
even if the images are stored in different folders.
The file type, associated metadata, and ancillary information contained in the file
determine whether the file must be inserted by interactive placement or, optionally, by
georeferenced placement.
Before inserting the image(s), you should determine the appropriate warehouse, feature
class, and placement method. You should define the image feature class name for the
specified image(s). This feature class name is actually the table name in the warehouse in
which the specified image(s)’s information will be placed.
Note: A valid image feature class must have a primary key of type autonumber. The
Insert > Interactive Image and the Insert > Georeferenced Image commands
automatically insert this key into any new image feature classes they create. Image feature
classes created with other tools are not usable unless they also have a primary key of type
autonumber.
5-1
Interactive Image placement—Requires you to draw a dynamic rectangle by placing two

points in the map window to define the size and the location of the image. With
Interactive Image placement, the coordinate system of the inserted image is identical to
the GeoWorkspace coordinate system, as is the coordinate system of the target image
feature class. The aspect ratio (ratio of width to height) of this rectangle is determined by
the number of lines and pixels per line in the image (the image pixels are assumed to be
square). It is possible to insert images interactively into an image feature class without
displaying the image because the visibility of any feature class is dependent on the legend
status of the feature class.
Georeferenced Image placement—Inserts georegistered images directly into an image
feature class in a user-specified warehouse. All the selected images must share the same
coordinate system. When you select a new georeference mode, you must select the
coordinate system file if the mode requires an externally defined coordinate system. This
placement method lets you insert one image file or multiple image files into either an
existing image feature class or a new image feature class. The georeferencing mode is
determined by those available for the selected file(s) and the operator’s choice when
multiple modes are available. Some georeferencing modes require you to define the
correct coordinate system using external files – either a .dgn or a .csf file can be used.
Georeferenced placement uses the following georeference modes:
• Automatic (the default) lets the command choose the georeference mode based on the
images you select.
• GeoTIFF (the default mode) tags - if a well-defined set of GeoTIFF tags is available
in the header
• Intergraph GeoTie information
• Intergraph header matrix
• Other with internal coordinate system
• Other with external coordinate system
• USGS DOQ
• Associated world file
In all cases, when the raster image is displayed, the appropriate affine transformation is
applied to warp the image into the GeoWorkspace coordinate system. This is only an
approximation; rigorous re-projection through samplings of the raster image is not
available in GeoMedia.
If you use the Automatic georeference mode, all the files selected from the Available files
list must match in coordinate system and method of georeferencing. For instance, if the
first selected file is a GeoTIFF, all subsequent files must be GeoTIFFs that match the first
one in their coordinate system in order to be selected. If the first selected file has an
associated world file, all subsequent files must have associated world files in order to be
5-2
Working with Images
selected. This selection is handled automatically by the command during the error
checking for the > and >> file selection buttons.
Note: The following website contains the GeoTIFF specification, details about who is
supporting GeoTIFF, source code, and sample images:
http://www.remotesensing.org/geotiff/geotiff.html
GeoTie information consists of coordinates for the corners of the map image in a
geographic coordinate system based on the WGS84 datum. Only Intergraph raster-file
formats support the use of GeoTie information.
A Header matrix is a proprietary Intergraph data structure that uses design file UORs to
properly position the image geographically. This type of matrix is only found in
Intergraph raster format and TIFF format images.
A Native matrix with internal CS image is an image that contains a matrix and a coordinate
system definition within the image itself, but which does not fall into the other categories
with internal coordinate system information: GeoTIFF, Intergraph GeoTie, or USGS
DOQ.
A Native matrix with external CS image is an image that contains a matrix but which does
not contain any internal coordinate system information and which does not fall into the
world file or by-header category. The ECW raster format is an example of this.
A USGS DOQ image is an image with geodetic information in its header in a format
specific to USGS data. The software places USGS DOQ images using this information.
MrSid files, TIFF files, or JFIF (.jpg) files can have associated world files (*.sdw , *.tfw, or
*.jgw). These world files contain the six parameters necessary to define an affine matrix
that will transform the image to the desired geographic location in a specific coordinate
system. World files do not contain coordinate system information, so you must specify
this information in a coordinate system file or a MicroStation design file, which contains a
type 56 (coordinate system definition) element. The use of JFIF (*.jpg) files is
discouraged.
IMPORTANT: With the georeferenced placement mode using a world file, you must
supply a design file to which the image was originally registered or create a coordinate
system file for the image. The coordinate system you define in the coordinate system file
describes the native coordinate system of the image, not the coordinate system of the
GeoWorkspace. When you insert an image into your map window, you specify the design
file or coordinate system file to be used in the Coordinate system file field.
To insert an interactive image:

1. Select Insert > Interactive Image.
5-3
2. In the Image name field, type the name of the image you want to insert, or click
Browse to select the image from the standard Open dialog box.
3. From the Warehouse drop-down list, select the read-write warehouse where you want
to store the path to the image and other associated attributes.
4. From the Feature class drop-down list, select the feature class to add the image to, or
type a new feature class name. Remember, all images in a single feature class must
have a common coordinate system and projection. Only those image feature classes in
which the coordinate system matches that of the GeoWorkspace will appear in the
drop-down list.
5. Click OK to load the image into the specified warehouse and feature class.
The software prompts you to define a rectangle by two points in the active map window
for the location of the image.
6. Place the cursor over the location for one corner, press and hold the mouse button, and
then drag the cursor to the opposite corner.
The aspect ratio of the image is maintained.
7. Release the mouse button.
The image is inserted into the specified feature class, and the path to the image is
saved in the read-write warehouse.
If you specified a new feature class, a new image entry is added to the top of the
legend associated with the active map window, and the image is displayed. If you
specified an existing image feature class, the display of the newly inserted image is
dependent on the current display properties of the image feature class.
To insert georeferenced images:

1. Select Insert > Georeferenced Images.
5-4
Working with Images
2. From the Georeference mode drop-down list, select the appropriate mode (Automatic
is the default). If your Georeference mode is USGS DOQ, GeoTIFF, Other with
internal coordinate system, or GeoTie, no coordinate system file is required; go to Step
4.
3. In the Folder field, type the name of the folder that contains the appropriate image
files, or click Browse to select it from the standard Browse for Folder dialog box.
4. Optional: In the Extensions field, type a new extension to change the default *.*.
If you enter a new extension, the Images list is updated accordingly, and any selected
image files are unselected.
5. From the Available files list, select an image or images; then move the selected
image(s) to the Selected files list using the arrow buttons.
6. In the Coordinate system file field, type the name of the coordinate system for the
chosen georeference mode, or click Browse to select it from the standard Open dialog
box.
7. From the Warehouse drop-down list, select the read-write warehouse where you want
to store the path to the image.
8. From the Image feature classes with matching coordinate systems drop-down list,
select the image feature class to add the image to, or type a new image feature class
name. Only those existing image feature classes that have coordinate systems
matching those of the selected images are available for selection.
5-5
9. Optional: For a new feature class only, select the Image display method by checking
the Add new legend entry for feature class check box, or by leaving it unchecked
(the default) to not add a new legend entry.
Note: When inserting large numbers of images, it may be to your advantage to not add
the entire feature class to the legend. This allows the use of a spatial filter to restrict
image display as desired.
10. Click OK or Apply.

The images are inserted into the specified feature class.
If a new feature class name was provided, a new image feature class is created in the
specified warehouse. If the Add new legend entry for feature class check box was
selected, the feature class name appears on the legend, and the images are displayed.
If this check box was not selected, the new feature class is created, but no entry for it is
placed on the legend, and the images do not display.
If an existing feature class was selected, the images are inserted into that feature class.
Display of the newly inserted images depends on whether the feature class appears on
the legend, and on the current display settings for that legend entry.
See the “Raster Information” appendix.
See “Adding Entries to the Legend” in the “Working with Map Windows” chapter.
Images and Coordinate Systems

In GeoMedia, each data source has its own coordinate system. This coordinate system is
defined in a variety of ways. In the case of GeoMedia feature data in Access, SQL Server,
or Oracle databases, the feature class coordinate system is defined when the feature class is
created. Data in non-GeoMedia based warehouses, such as ArcView, ARC/INFO,
MapInfo, FRAMME, and MGE data, can be imported to GeoMedia feature classes or
served directly from the warehouse. These data sources may or may not have their
coordinate system explicitly defined. If GeoMedia is unable to determine the coordinate
system of a dataset, you must provide this information by associating a coordinate system
definition file with the data source. This is the case when serving CAD data that specify an
XY coordinate for a feature but do not provide coordinate system, projection, unit, and
datum.
When importing vector features to a GeoMedia read-write warehouse, the coordinate
system file is used for the one-time transformation of the data to the coordinate system of
the new feature class. Leaving the vector data in the native warehouse means that
GeoMedia refers to the coordinate system definition file whenever the data are served from
that warehouse.
Image data are treated a little differently. There is no non-GeoMedia based image
warehouse from which images can be served. Records for all images will reside in
GeoMedia image feature classes that are stored in a read-write warehouse. Also,
5-6
Working with Images
GeoMedia image records are always stored in their native coordinate system – there is no
warping or transformation of the image geometry prior to its insertion into an image feature
class.
The suitability of any image feature class for storage of a new image record is determined
by how similar the two coordinate systems (that of the feature class and that of the image)
are to one another. If the match is not sufficiently close, a new feature class needs to be
created to store the new image record. When an image is inserted into an image feature
class, the path to the image file and the geometry of the image are recorded. Relocation of
the image file causes errors when displaying the image. Modification of any file-based
georeferencing information stored in or with the image file (GeoTIFF tags, world file
information, and so forth) is ignored by GeoMedia, once the images are inserted into an
image feature class.
The coordinate system of a given image (and of the image feature class it can be inserted
into) can be specified in a number of ways. With some georeferencing modes (GeoTIFF,
GeoTie, and DOQ) the image files contain their own coordinate system definitions. For
these data, the image feature class coordinate system is taken from the image file header.
Other modes of georeferencing images (an image with a WorldFile or an Intergraph raster
format with header matrix) require the use of an associated coordinate system definition
file to provide the necessary context. This file can be either a MicroStation design file that
contains a coordinate system element (.dgn) or a GeoMedia Coordinate System File (.csf).
MicroStation Design Files

For MicroStation design (.dgn) files, a coordinate system element is written into the file by
Intergraph’s MGE Coordinate System Operations (MCSO) software, which is bundled
with various Intergraph software packages such as MGE, and by ZI Imaging’s ZI
Coordinate System Operations (ZICSO) software, which is bundled with various ZI
Imaging software packages such as I/RAS C.
Define Coordinate System File

The second method of specifying a coordinate system is through the Define Coordinate
System File utility provided with GeoMedia applications. This utility creates a Coordinate
System File (.csf) containing the coordinate system information. The .csf file or a .dgn file
can be associated with a particular data source (warehouse) using an entry in an .INI file.
See the “Creating Data Server .INI Files” topic in GeoMedia Help for data on .INI
naming conventions, folder paths, and coordinate system entries for the data source types.
Linking Geometry Data to Coordinate Systems

The geometry field for raster images contains only the footprint of the raster. An affine
transformation is performed on the footprint when the coordinate system of the image is
displayed in a GeoWorkspace with a different coordinate system. The actual image is
retrieved from the hard disk containing the raster file and placed on the footprint. Since the
5-7
raster image must be retrieved from a hard disk, it is often advisable to use a UNC path
when inserting images residing on other computers.
Managing Warehouse Images

You can manage the image records that exist in an image feature class of a selected
warehouse connection with the Images command. These image records are shown on the
dialog box as either a filename or an XML (Extensible Markup Language) moniker. You
can display, update, delete, and validate image records with a filename in a read-write
connection; in a read-only connection, you can only display and validate the records. For
those image records with an XML moniker, you can only display or delete the records in a
read-write connection and only display those in a read-only connection.
Each image record listed for a connection has a corresponding icon to denote whether
GeoMedia can link an image record to a file or to an XML string, as follows:
The specified file or XML moniker is valid.
Note: An XML moniker is always considered valid, so the associated icon is always the
valid icon.
The specified file is invalid.
The specified file has an unknown state.

This command displays selected images from an image feature class in an open warehouse
connection in the active map window. You can choose one or more valid image entries
(which can be filenames, XML monikers, or both) and display these images using a single
legend entry or separate legend entries for each selected image. Alternatively, you can
create a query from selected images, to be added to the legend at a later time. The selected
images are stored in a query based on the values of their primary key field(s). This query
contains a fixed and permanent list of images, referenced by keys. This list is not editable.
However, you can use the Queries command to edit the query, but only to edit the query
name and description. The image files of the selected filename entries are automatically
validated and their associated icons are updated after the display operation.
See “Adding Entries to the Legend” in the “Working with Map Windows” chapter.
Note: If you want to add all the images in a feature class to the display, under a single
legend entry, consider using the Legend > Add Feature Class command.
The Images command also lets you review the image entries and update the paths to any
filename image entries, single or multiple, not pointing to valid raster image files. You
5-8
Working with Images
cannot, however, update multiple images entries that contain both filenames and XML
monikers, nor single or multiple XML monikers, which are always valid. GeoMedia does
not store the image in the warehouse; rather the path to the image is stored in the image
feature class. If the location of the image file is changed, you can update the path stored in
the geometry column with this command. The image files of the selected filename entries
are automatically validated and their associated icons are updated after the update
operation.
If an image will no longer be used, you can delete its record from its image feature class
with the Images command. Alternatively, select the image in the map window and use the
Delete Feature command, or you can delete the feature class entirely with the Feature
Class Definition command.
Additionally, this command lets you validate the files associated with the selected entries.
The icons of the entries are then updated after the operation. As previously stated, you
cannot validate entries with XML monikers because they are always valid.
To display selected warehouse images in a map window (as a single legend

entry, or multiple legend entries), or to group images as a query that can be
added to the legend at any time:
1. Select Warehouse > Images.
2. Select the appropriate image record from the Feature class drop-down list, which only
displays image feature classes.
All image records of the selected image feature class are displayed in the Images list.
3. To display selected images, select the valid image record(s) from the Images list; then
click Display.
5-9
4. Select the Display in a single legend entry (the default) option to display the selected
images in a single legend entry; then click OK.
OR
Select the Display in separate legend entries option to display the selected images
with one legend entry per image; then click OK.
OR
Select the Create query without legend entry option to create a query containing the
selected images that can be added to the legend at a later time through the Analysis >
Queries command; then click OK.
The image files of the selected entries are automatically validated, the icons of the
entries are updated after the operation, and the images are displayed in the active map
window or the query is created.
To update image records:

2. Select the appropriate image feature class from the Feature class drop-down list.
3. To update a single image record with the invalid filename icon, select the appropriate
record from the Images list; then click Update to open the standard Open file dialog
box, from which you choose a valid path and filename.
4. To update a single valid or unknown-state image record or multiple image records
(regardless of the icon) from the Images list, select the entry or entries; then click
Update to open the standard Browse for Folder dialog box, from which you choose a
valid folder.
Once the update is finished and the dialog dismissed, the image entries are updated
with the new folder and the warehouse is updated. The Images list is then refreshed so
that the appropriate icons are displayed for any updated entries.
5-10
Working with Images
5. Click Close.
To delete image records:

3. Select the image record(s) that you want to delete from the Images list.
4. Click Delete.
Note: You can also delete an image as any other legend entry by selecting the image name
on the legend using the Select by Legend Entry and Delete commands on the Edit menu.
To delete an image feature class with Warehouse > Feature Class Definition:
2. Select the image feature class to delete from the Feature Classes drop-down list.
3. Click Delete.
4. Click Yes to confirm the deletion of the image feature class.
The image feature class is deleted from the warehouse, and any images in that feature
class that were displayed are removed from the map window. Notice that the name of
the image feature class may still be on the legend
5. Click Close.
6. Delete the old image feature class entry from the legend.
To validate image records:

3. Select the image record filename(s) you want to validate from the Images list.
4. Click Validate.
All files of the selected entries are validated and their associated icons are updated
accordingly.
Removing Images from a View and Redisplaying Them

Deleting an image feature class or query from the legend removes its images from the
view but does not alter the contents of the image feature class in the warehouse. If you
5-11
remove an image feature class from the legend, the Legend > Add Legend Entries
command lets you redisplay the entire contents of the image feature class.
Note: When inserting large numbers of images, it may be to your advantage to not add the
entire feature class to the legend. This allows the use of a spatial filter to restrict image
display as appropriate. If you want to display only selected images from the image feature
class, use the Warehouse > Images command as previously described.
To remove an image feature class or query from a view and redisplay it:
1. Select the image feature class or query name on the legend.
2. Press DELETE on the keyboard; then confirm the deletion from the legend and map
window by clicking Yes.
3. Select Legend > Add Legend Entries.
4. Select the appropriate categories, queries, reference features, or connections node
from the Features treeview to display all feature classes within that group.
5. Select the appropriate image feature class check box from the treeview; then click OK
to redisplay the image.
Changing the Raster Image Display

An image style is of the image style class. As such, it provides display capability for
imagery. Raster image data is now supported through the same mechanisms as vector data,
for consistency and simplicity. You can change the image display through the image
Legend Entry Properties dialog box and the Style Properties dialog box. As with all
other style types, you must dismiss the dialog box before you can see the style definition
changes in the map window.
See “Working with Styles” in the “Working with Map Windows” chapter for more
information on styles.
You define the following style properties on the Image Style tab of the Style Properties
dialog box:
5-12
Working with Images
Translucency percentage—The degree to which the image is to be translucent or see-

through, with 0% indicating totally opaque and 100% indicating totally transparent. It is
applicable to all image types.
Contrast—The contrast of the image display on a scale of –100 to 100, applicable to all
image types, including 8-bit color index imagery, however, not binary.
Brightness—The brightness of the image display on a scale of –100 to 100, applicable to
all image types, including 8-bit color index imagery, however, not binary.
Invert Image—Indicates whether the image display should be inverted (creates the effect
of a negative) , applicable to all image types, including 8-bit color index imagery, however,
not binary.
Transparent color—A color within the image that is to be treated as transparent (not
drawn). This is an actual color value (R,G,B), not a color index or pixel value. It is
applicable to all image types except binary.
Transparent pixel values—A set of pixel values within the image that are to be treated as
transparent (not drawn), applicable only to color index and grayscale images. These are
color index or pixel values, not an actual color value (R,G,B). The pixel values are
presented as comma (,) and a hyphen (-), separated values from 0-255.
Binary foreground color—The color with which the foreground pixels of a binary image
are to be displayed, applicable only to binary images.
Binary background color—The color, if any, with which the background pixels of a
binary image are to be displayed, applicable only to binary images. The background may
be made transparent by not specifying a background color.
Note: When using images as a backdrop, it is often useful to use the legend to turn off the
locate property for the image feature class so that the image canvas is not selected when
working with features.
5-13
You can also use the Advanced tab to change attribute-based symbology. This tab
redisplays some of the information from the Image Style tab in a grid format with the
Default Value column containing the values from the Image Style tab. The Attribute
Based column lets you drive the value of a given property from a field value or from an
expression.
To change the raster image display:

1. On the legend, double click the style key of the image feature class you want to change
to display the Legend Entry Properties dialog box.
2. Make the appropriate change; then click Apply.

The changes are saved and reflected in the display of the image(s) in the associated
map window.
5-14
Working with Images
OR
Click Properties to display the Style Properties dialog box.
Note: The first image type associated with the raster legend entry determines which
tab is available.
3. On the Image Style tab, change the characteristics of the selected image(s).
4. Optional: On the Advanced tab, change the attribute-based symbology.
5. Click OK to dismiss the dialog box and display the changes.
The changes are saved and reflected in the display of the image(s) in the associated
map window.
Creating Image Footprints

The Image Footprints command lets you create image footprint polygons of an image
feature class, query, category, or reference feature. An image footprint is an area geometry
that represents the outline of the image. Using image footprints when possible, rather than
the raster images themselves, greatly speeds display processing (panning, zooming, and so
forth). The separate Display Selected Images command loads the images from selected
footprints. You must have an active map window to use this command.
You can add the footprints query to a map and/or data window, and you can also edit these
queries using the standard edit query procedure. The Image Footprints command also
creates a legend entry of labels based on the image filenames. These labels are centered
within the footprint polygons. The default title of the legend entry for the labels is “GGG
of QQQ” where GGG is the name of the text geometry field, and QQQ is the query name.
5-15
The default name for the text geometry field is ImageLabelGeometry. This default field
name cannot be changed through the command dialog box. An example legend entry title
is ImageLabelGeometry of Image footprints of LincolnCoTopos.
See “Displaying Selected Images” in the next section in this chapter.
To create image footprints:

1. Select Analysis > Image Footprints.
2. Select an image feature class, query, category, or reference feature from the Create
image footprints for drop-down list.
Note: Only image feature classes and reference features are listed. If a query or
categorized item is chosen, it is verified to have an image geometry.
3. Optional: Change the output Query name and/or optional Description.

4. Optional: Check the Display footprints in map window check box; then optionally
change the name in the Map window name field.
5. Optional: Click Style, and change the default style on the Select Style dialog box.
6. Optional: Check the Display labels in map window check box; then optionally
change the name in the Map window name field.
8. Optional: Check the Display results in data window check box; then optionally
change the name in the Data window name field.
9. Click OK.
The dialog is dismissed and the query is added to the queries folder. The appropriate
legend entries are created in the map window based on the settings of the check boxes.
A data window is created if the check box is checked.
5-16
Working with Images
Displaying Selected Images

The Display Selected Images command displays images from those features in a select set
that have coverage geometries. Objects in the select set that do not have a coverage
geometry are skipped. This command is designed to be used in conjunction with the
Image Footprints command, which creates image footprint polygons of an image feature
class or query, although it can also be used in other contexts. The Display Selected
Images command loads only those images that have been placed in the select set, whether
they have been placed by selection of their footprints in a map window, their rows in a data
window, or some other technique. To use this command, which has no graphical interface,
you must have a select set, and an active map window.
In a typical workflow, you would use Image Footprints to generate footprints (image
shapes) for an image feature class. A subset of these footprints is placed into a select set,
and the images are then displayed through Display Selected Images. Alternatively,
footprints may have been created through the Functional Attributes command, through
custom software, provided directly through a data server, and so forth. In another
workflow, Display Selected Images may operate without footprints, for example, through
image features selected in a data window. This command has no graphical interface.
See the previous “Creating Image Footprints” section in this chapter.
See “Working with Functional Attributes” in the “Analyzing GeoMedia Data” chapter
Once all the image geometries in the select set are found, a legend entry is created. If
coverage geometries from multiple feature classes are found in the select set, multiple
legend entries are created. The title of each legend entry will be Selected images of <X>
where X is the feature class or query from the select set that contains the image geometry.
Legend entries for a given feature are reused if they exist. That is, for the existing legend
entry, the previous selected images are unloaded and the newly selected images are
displayed. If no newly selected images match an existing legend entry, the legend entry
5-17
remains in the legend but has zero records; thus, any displayed images for that legend entry
are unloaded. This reuse allows legend entry settings, such as transparency, to be
maintained across multiple invocations of the Display Selected Images command. If no
matching legend entry can be found, a new legend entry will be created with the extended
property set to the appropriate value. Objects in the select set that do not have an image
geometry are skipped.
Queries are not created as output. To make a reusable named query in the GeoWorkspace,
you must use the Select Set to Query command.
See“Defining Queries from Select Sets” in the “Working with Features” chapter.
To display selected images:

1. Generate a select set of objects that have image geometries.
2. Make a map window active.
3. Select View > Display Selected Images.
5-18
Working with Map Windows
The GeoMedia GeoWorkspace can contain one or more windows—map windows, data
windows, and a layout window. These windows provide you with different ways of
visualizing your data. The map window shows a graphic display of the geographic data
(features, images, and so forth). The data window shows the same features in tabular form,
displaying the attributes associated with the geographic data. Thus, if a feature is
displayed in multiple map and data windows, it highlights in all windows when selected.
The layout window allows you to design and to plot a map layout. Map graphics in the
layout window are linked their originating map window to reflect any changes made to the
data, or they can optionally be placed as a static snapshot reflecting the characteristics of
the map window at the time of placement.
Each map window contains the following marginalia items: a legend, a north arrow, and a
scale bar. You can select or deselect each of them on the View menu to turn them on or
off. Whatever the active parameters are for these marginalia items in the map window, the
same parameters are used to render these items in the layout window.
For the most part you define the content and design of each map window through its
legend. While a traditional legend simply reflects what is displayed on a map, you use the
GeoMedia legend to control what is displayed in the map window and how it looks.
The following is a representative workflow for displaying geographic data and map objects
in a map window:
1. In an open GeoWorkspace, connect to the warehouse(s) containing the data you want
to display.
2. Display the legend in the active map window.
3. Add entries to the legend.
4. Customize the look of your map by using the legend to change the display
characteristics of the geographic data.
5. Turn on the north arrow and change its appearance.
6. Turn on the scale bar and change its appearance.
7. Customize the appearance of the legend.
8. Add new map and/or data windows to the GeoWorkspace to show different views of
your map and/or data.
See the “Working with Data Windows” and the “Working with Layout Windows” chapters
for information on data windows and layout windows.
6-1
Controlling the Map Window

To the left of a map-window title or in the upper-left corner of a maximized map window
is the map-window icon. Clicking this icon displays a menu that allows you to control the
map window.
Depending on the current state of the map window, this menu lets you do the following:
• Restore a minimized window.
• Move, restore, minimize, or maximize the window.
• Close the map window.
• Activate the next map or data window in the stack.
The GeoMedia Window menu contains tools for cascading or tiling windows and for
activating a different window. The bottom of this menu lists all the open windows in the
GeoWorkspace. A checkmark appears next to the title of the active window. You set the
title and behavior of a map window by setting its properties. To adjust the display in a map
window, you use the mouse and the map viewing tools. The north arrow and scale bar,
which you can turn on and off from the View menu, dynamically update to reflect changes
to the map window. The status bar dynamically updates to reflect the current display scale
or view extents.
On the Map Display tab of the Options dialog box, you can specify with the When
resizing map windows options that the contents of a map window be fit automatically
when the window is resized, or that the map scale be preserved.
Changing Map Window Properties

When you set map window properties, you specify the title that appears in the map window
as well as the way the map window displays features you select in another window.
Because the windows in a GeoWorkspace are linked, features you select in one map or data
window always highlight in the other map or data windows. Moreover, you can set certain
properties in a map window to have its view change when you select a feature in another
window.
For example, suppose you set the properties in Map Window A to fit and zoom out at
200%. When you select a feature in a data window or in another map window, the view in
Map Window A changes to fit the selected feature and zooms out at double the view scale.
In another example, you can use these properties as a simple queuing mechanism.
The following properties determine the display in the map view when a feature is selected
in another window:
6-2
• View at current scale (the default—Features in the select set are highlighted, but the
map window does not shift or change scale.)
• Center at current scale—Features in the select set are highlighted and centered in the
map view, but the map window does not change scale.
• Fit and zoom out—Features in the select set are fit to the map view, and the view
zooms out according to the percentage you specify. The default setting is 105%.
If you set the properties in Window 1, for example, to Center at current scale or Fit and
zoom out, selecting features in any window changes the zoom scale or window location.
You probably do not want this to happen when selecting features in Window 1 itself, only
when selecting in other windows. To override this behavior in Window 1, you select the
View at current scale option.
The following diagram shows a feature selected in the left map window. The same feature
is centered, fit, and zoomed out in the right map window:
The following diagram shows a the same feature selected in a data window and centered,
fit, and zoomed out in the map window:
6-3
To change the properties of a map window:

1. Select Window > Map Window Properties.
2. Type a new title in the Map window name field if appropriate.

3. Select the appropriate For items in the select set option.
4. If you selected Center at current scale or Fit and zoom out, select or accept the
setting for selecting in the current window.
5. Click OK.
Defining Map Window Display Properties

View > Display Properties helps you visualize what your map data in the map window
will look like when viewed or plotted at a given map scale.
This command lets you define the following properties that affect the way the map
graphics are displayed:
Display scale—Typically associated with screen displays, display scale is the scale factor
with which to view the map data in a map window. This factor is flexible, changing every
time you zoom in or out. The current display scale is shown in the GeoWorkspace in the
lower-right corner of the Status bar.
Nominal map scale—Typically associated with style scaling, the nominal map scale is the
scale factor that serves as the base or reference scale. It is referenced when legend entries
have their style scaling set to Paper. When defining the style of a feature (for example,
6-4
line thickness, symbol size, or text size), you define the size of the style in paper units.
With Paper style scaling, the styles are rendered at the nominal map scale and increase or
decrease in size as you zoom in or zoom out away from the nominal map scale. When you
display the Display Properties dialog box, this field contains the current nominal map
scale.
You can choose from two different ways of displaying data in a map window: View (size
is true at any display scale) and Paper (size is true at nominal map scale). Both options
are global, affecting the style scaling for all legend entries. When View (size is true at
any display scale) is turned on, the appearance of the style of a feature will not change as
you zoom in and out in the map window. In other words, the size of the symbols and the
text features, and the thickness of the lines, will not increase or decrease as the display
scale changes.
When Paper (size is true at nominal map scale) is turned on, the nominal map scale
becomes important in controlling the display in the map window because it serves as the
base scale for the definition of the style. The appearance of the style will increase or
decrease in size as the display scale changes. For example, if your nominal map scale is
set to 1:10,000, and you symbolize your text feature to be 12 point size, they will only
appear this size on the screen when the display scale is set to 1:10,000. If you zoom out to
1:20,000, the text will then appear to be 6 point in size. For this reason, you may notice
that certain features sometimes are too small to be seen, even though you set the style to be
20 points. This is because your nominal map scale is large, for example, 1:5,000, and you
are zoomed out so the display scale is much smaller, for example, 1:100,000. The text is
thus being displayed at 1/20th of its point size. You can fix this by changing the nominal
map scale, close to something you want to plot at. Or you can set style scaling for all
legend entries to View, so it always displays at 20 points, regardless of how far in or out
you are zoomed (display scale).
Rotation angle—Rotation angle of the map view. When the units are degrees (deg), the
values in the drop-down list are: -90, -75, -60, -45, -30, -15, 0, 15, 30, 45, 60, 75, and 90.
When the units are not degrees, the values are the preceding degree values converted to the
current angular units.
Units—Angular units. Changing the units converts the rotation value to the new units.
Set style scaling for all legend entries to—Legend entry display in the map window.
• View (size is true at any display scale)—The styles on all legend entries are display-
scale independent, overwriting the setting of the legend right mouse menu Style
Scaling > View command.
• Paper (size is true at nominal map scale)—The styles on all legend entries are
display-scale dependent, overwriting the legend right mouse menu Style Scaling >
Paper command.
To achieve a WYSIWYG (What You See Is What You Get) display in the map view, you
set the Display scale and Nominal map scale to the intended plot scale, set the Set style
scaling for all legend entries to setting to Paper (size is true at nominal map scale), and
6-5
apply any rotation angle. The display of the features on the screen is how they will look
when plotted. If line weights, text sizes, and symbol sizes appear too small or too large,
you should make the necessary adjustments in the style definition for those features. In
general, the nominal map scale should be the same as the plot scale. However, it is not
necessary that they be the same, and having them differ does offer additional design
flexibility. After you have set these properties, you can use the View > Pan command to
view different areas of the intended plot area.
See “Defining Map Objects Display Properties” in this chapter and “Defining Map
Specifications in the Map Window” and “Previewing the Map in the Map Window” in the
“Designing Map Layouts for Printing in the Layout Window” chapter.
When you first open a dataset, such as the USSampleData.gws, various feature classes may
appear not to load properly to the legend, for example, Labels of Major Cities, Major
Cities, Interstates, and Highway Interchange. These feature classes have a not loaded
legend key. The actual legend key does not load to the legend view initially because these
feature classes are all set to view by scale and are thus not visible. The software does not
load data for a legend entry until/unless that legend entry is within its display scale range.
This behavior thus allows large data sets to be loaded quickly. When you zoom in so that
these features become visible, the actual legend keys display in the legend, as in the
following:
Using the Mouse in a Map Window
Note: If your mouse has been reconfigured so that the button functions are reversed, you
must reverse left and right mouse-button instructions in all the product’s documents.
In a map window, you use the left mouse button to do the following:
• Activate the window.
• Create a select set.
• Place or edit a map object.
6-6
• Zoom and pan when the appropriate viewing tool is selected.

• Invoke a hypertext link.
You use the right mouse button to click in an empty space in the map window and invoke
the map-window pop-up menu. This menu contains tools most commonly used in the map
window.
Using an IntelliMouse
If you have a Microsoft IntelliMouse, you can use it to manipulate the display in your map
windows faster and more efficiently. Rolling the IntelliMouse wheel forward causes the
view to zoom in at the current cursor location, and rolling the IntelliMouse wheel
backward causes the view to zoom out at the current cursor location.
Using Map Viewing Tools

The following viewing tools are available only when a map window is active. You exit
persistent viewing tools by pressing ESC, by selecting another viewing command, or by
selecting the Select Tool.
Zoom In Zoom in on a point you identify with a single mouse click
or on an area you define by pressing and holding the left
mouse button on one corner of the area, dragging the fence
to the diagonally opposite corner, and then releasing the
mouse button. A right mouse click exits this command.
Zoom Out Zoom out on a point you identify with a single mouse click
or on an area you define with a dynamic two-point line. A
right mouse click exits this command.
Zoom Return a map window to its previous zoom scale and view
Previous extents.
Zoom to Zoom the display scale of the map window to the current
Nominal nominal map scale as specified on the Display Properties
Map Scale dialog box.
Fit All Fit all displayable objects to the active window.
Fit Select Fit the contents of a select set to the active window.
Set
Note: This command generates expected results only when the selected features are
within the defined display scale range of the legend entry.
Update Load unloaded legend entries and refresh the display in all
All map windows.
6-7
Note: This command redraws the graphics in all map windows in which the loading
of data in the legend was terminated by the ESC key, beginning at the point in the
legend where the interruption occurred. This command does NOT refresh the map
window if the legend content has not changed. It does not repaint the window after
any view process has been interrupted; this applies only to the interrupting of the
loading of legend entry data.
Pan Drag the display in the direction of the cursor. A right
mouse click exits this command.
Pan has two modes, dynamic and fast, which are set through the When panning map
windows options on the Map Display tab of the Options dialog box (Tools > Options).
While the Pan command is active, you can switch between dynamic and fast panning by
changing the selected option.
The Use dynamic pan option means that all the graphics in the map window move
continuously in unison with the mouse cursor when panning is performed as you press and
hold the left mouse button.
The Fast pan option means that the graphics in the map window remain fixed while
panning is performed, thus limiting the number of map window redraw operations. This
mode is useful if the map window contains a large number of graphic objects, images in
particular, which results in dynamic panning not being smooth and efficient because it
takes too long to continuously redraw the window due to the large number of graphic
objects.
In performing fast panning, the graphics do not move until the left mouse button is
released. Placing the cursor in the map view and pressing and holding the left mouse
button defines the pan starting point. As you move the cursor, the graphics remain fixed,
and a dynamic dashed line appears. One end of this line remains fixed at the pan starting
point; the other end moves dynamically with the cursor, thus giving you a visual indication
of the distance and direction of the pan that will occur when the left mouse button is
released. Releasing the mouse button defines the pan ending point and ends the current
pan action, and the dashed line disappears. The map window is redrawn with the pan
starting point moved to the pan ending point.
On the General tab of the Options dialog box, which you access from the Tools menu,
you can specify whether to display in the status bar the view extents or the display scale. If
you have the status bar turned on, the view extents or current display scale appears in the
rightmost panel at the bottom of the GeoWorkspace window. To see the display scale
change, select it on the Options dialog box, and zoom in or out in the map window.
Changing Display Characteristics of Map Objects

You change the display characteristics of a map object by changing the properties of its
legend entry. Map windows are independent of each other, and each has its own legend.
This means, for example, that you can display highways as blue dashed lines in one map
window and as red solid lines in another map window within the same GeoWorkspace.
6-8
The look and function of a map is determined by certain display characteristics of each
map object:
• Display priority. Which map objects are displayed on top of other map objects?
• Style. What does each map object look like?
• Scale range. At what scale range can map objects be displayed?
• Locatability. Can the map object be selected or highlighted in the map window?
Changing the Display Priority of Map Objects

The order in which map objects are displayed determines which object can be seen when
more than one object has the same spatial location. Depending on their relative size, type,
and display setting, the object on top is likely to be the only one you can see.
Moving entries within the legend affects the display priority of associated map objects in
map windows. The closer an entry is to the top of the legend, the higher the display
priority of its map objects. For example, if you have a legend entry for a light-duty road
and it is at the top of the legend, its map objects will appear on top of any other map
objects in the map window.
You can change the display priority of a map object to optimize display by changing its
order on the legend. The map object associated with the bottom legend entry is drawn
first, the object associated with the next-to-last entry is drawn on top of it, and so forth.
The map object associated with the first legend entry has highest priority and is drawn last.
You can change the display priority on the legend by simply selecting an entry and
dragging it up or down the list of legend entries. You cannot, however, move legend
entries between legends.
When you are using drag-and-drop, you can perform the following:
• Copy with CTRL key pressed.
• Cut/Copy selected multiple legend entries; all are inserted consecutively at the drop
point.
• Cut/Copy a group legend entry to automatically move/copy its entire subordinate
hierarchy.
• Cut/Copy nested legend entries of a thematic group legend entry within the group.
This also changes the order of display of the nested legend entries.
See the “Working with Legends” section later in this chapter for information.
Defining Map Objects Display Properties

The legend right mouse menu Style Scaling > Paper/View commands let you define the
display behavior of the style of a feature. The Paper setting is the same as the Paper (size
is true at nominal map scale) option on the View > Display Properties dialog box, and
6-9
the View setting is the same as the View (size is true at any display scale) option. To
maximize you workflow, you can select multiple legend entries at a time and change this
setting. For global changes (all legend items), you can still use the Display Properties
dialog box.
The styles of legend entries that are defined as View maintain their size definition when
you change the display scale in the map window. Line weight, text size, and symbol size
definitions are always rendered at the current display scale. When you zoom in on a linear
feature that has its legend entry defined as View, the line remains the same width in the
display.
The following diagram shows the affect of having the View setting defined for text features
at three different display scales. The text remains the same size in all of the displays.
The styles of legend entries that are defined as Paper are display scale dependent, meaning
that its display is associated with a particular scale. Line weight, text size, and symbol size
are rendered at the nominal map scale defined on the Display Properties dialog box. The
display appears larger as you zoom in and smaller as you zoom out.
The following diagram shows the affect of having the Paper setting defined for text
features at three different display scales. The size of the text varies as the window is
zoomed out but remains proportionate to the map.
The active Style Scaling setting for any given legend entry appears with a check mark
when viewed in the legend right mouse menu. If multiple legend entries are selected, and
have a combination of Paper or View settings defined, neither option contains a check
mark when viewed in the legend right mouse menu.
See “Defining Map Window Display Properties” in this chapter.
6-10
Changing the Scale Range of a Map Object

One way to define the display in your map window is to set a scale range for map objects.
This means that, when the view scale of the map window falls within the scale range of a
legend entry, whether or not the object is displayed depends on whether or not the legend
right mouse Display by Scale command is on.
For example, interstate highways might be set to display at scales between 1:250,000 and
1:1,000,000. Zooming to a scale outside this range causes the display of interstate
highways to turn off.
You can also use this to display feature classes differently depending on the display scale.
For example, at 1:1,000,000 U.S. Interstates may be drawn as a single line, but as you
zoom in they could be drawn as thicker, double lines.
To set a scale range for a map object:

1. Select the appropriate legend entry.
2. From the legend right mouse menu, select Display Scale Range.
3. On the Scale Range dialog box, select a predefined range, select minimum and
maximum range values from the drop-down lists, or key in minimum and maximum
range values between 1 and 1,000,000,000.
4. Click OK.
Changing the Locatability of Map Objects
A map object must be locatable to be selected with the cursor. Turning off the locatability
setting helps when you have several feature classes clustered in one area but only want to
select from one feature class. Likewise, it makes no sense to select certain map objects,
such as backdrops or logos. You can turn its locatability off to prevent its being selected
accidentally.
An arrow next to the legend entry indicates that an object is locatable. You control this
through the legend right mouse menu Locatable On/Off commands.
6-11
Working with Styles

The styles capability in the software is very powerful. You can create and name a style,
modify an existing style, and create nested styles. In addition, you can store styles for
reuse as part of the GeoWorkspace and distribute these styles throughout your organization
through GeoWorkspace templates. You perform these and other style management tasks
through three main styles dialog boxes that work together: Styles, Style Properties, and
Select Style. The following discussion addresses styles types and style collections,
followed by the styles commands, interface, and workflows.
Looking at Style Classes

In general, styles are classified by geometry type. These classes include Point, Line, Area,
Compound, Image, Text, and Fill styles. Within each style class, there is a style type
definition that provides a further distinction of the characteristics of the given style. Some
style classes, such as Image Styles and Text Styles are limited to a single style type. While
other style classes, such as Point Styles and Line Styles provide multiple style types to
further define the style. For example, Point Style classes support Symbol, Font, and
Picture style types. Line Style classes support Simple and Pattern style types.
Generally, most style classes present a simple relationship between the style and the
geometry. But in the case of Area and Compound style classes, this relationship requires a
composite style definition. Compound features, for example, contain points, lines and
areas; all of which are unique style classes. Composite styles are presented in a
hierarchical treeview.
The following figure shows the Styles dialog box with a corresponding table listing the
style classes and below them the style types available for each of those style classes.
Composite style types are tagged with an asterisk (*). The first style type listed in each
column is the default style type when a new style is created for that style class.
6-12
Style types are always interchangeable within style classes. For example, a symbol style
can be used in all of the same places that a picture style can be used.
Style types may also be reused within other style types, even if they are in different style
classes. For example:
• Point style types are used for point geometry but also for patterns in line and fill types.
• Line types are used for linear geometry but also for boundaries in area types and for
hatches in fill types.
• Area types are used for area geometry but also for frames in text types.
Using Legacy Styles

Legacy GeoMedia style (*.gsd) files are still honored when adding legend entries. You
can easily bring these files into a GeoWorkspace by drag-and-drop of the style files or
folders containing style files from Windows Explorer onto the styles list of the style dialog
boxes. The sharing of style definitions through .gsd files is replaced by the library system
in GeoMedia version 6.0.
6-13
See the “Working with Libraries” chapter.
Style Types
The following section discusses each of the style types and their parameters, which you can
define through the Styles and Style Properties dialog boxes.
See corresponding GeoMedia Help topics for complete description of the styles, their
parameters, and how they are defined.
Picture Style—This point style class provides for the rendering of pictures at point
locations. The term picture is used in the Microsoft sense of the word, and encompasses a
wide range of common Microsoft-supported formats mostly, but not exclusively, of a raster
nature.
The following style properties exist for a picture style:
• Bitmap Image (*.bmp) • Portable Network Graphics Image (*.png)
• JPEG File Exchange Format Image • Graphics Interchange Format Image (*.gif).
(*.jpg, *.jpe, *.jpeg).
• TIFF Document (*.tif, *.tiff). • ICON Image (*.ico).
• Windows Metafile Image (*.wmf). • Enhanced Metafile Image (*.emf).
All pictures, symbols, and fonts used in point displays are externally referenced. You
cannot load a bitmap into the GeoWorkspace as an embedded picture; it is always a file
reference.
You can define the following picture style parameters: size, transparent color, override
color, translucency percentage, rotation, alignment, and offset.
Font Style—This point style class provides for the rendering of a character in a specified
font at point locations. All font characters are displayed through common Microsoft text-
rendering techniques. These techniques do not, however, recognize MicroStation-
proprietary font resource files. Thus, such files must be converted into a format
6-14
understood by GeoMedia 6.0, either a Microsoft-supported font or picture, or a GeoMedia-

supported symbol file format, for example a MicroStation cell file.
You can define the following font style parameters: font, character, size, color,
translucency percentage, halo, rotation, alignment, and offset.
Symbol Style—This default point style class provides for the rendering of symbols at point
locations. The term symbol indicates any of a number of data formats, produced by
GeoMedia and other software products, that contain symbolized vector drawings intended
for display at point locations within a larger drawing.
The following symbol types are supported:
• Predefined symbols—A set of simple, predefined symbols (circles and other shapes)
are built into the symbol style. It is not necessary to select an external symbol path.
Each predefined symbol has a name by which it is selected. The default symbol style
is a small, filled, black circle.
• GeoMedia Feature Symbol Files (*.fsm)—This is a multi-symbol type.
• MicroStation Cell Files (*.cel)—This is a multi-symbol type. With this type, it is not
necessary to convert cell files into .fsm format.
• AutoCAD Drawing Files (*.dwg)—This is a single-symbol type. The symbol name is
automatically determined from the symbol file name. With this type, it is not
necessary to convert drawing files into .fsm format.
• Scalable Vector Graphics (SVG) Files (*.svg)—This is an industry standard, multi-
symbol type. These symbols may contain embedded text elements within the symbol
that can be tied to attributes. This provides a parametric symbol capability in which
the symbol text changes based on the attribute value for each feature instance, for
example, Interstate Highway Shields.
See the “Supported SVG Element Types” appendix.
You can define the following symbol parameters: source, name, size, override color,
translucency percentage, rotation, alignment, offset, and attribute value.
In the case of SVG symbols, support is provided for a single text element within each
symbol. If a text element exists in the chosen symbol, an attribute may be chosen for
association with the text element. As the symbol is drawn for a feature, the designated text
within the symbol is substituted with the value of the designated attribute for that feature.
You can define the display behavior of all Point styles (Picture, Font, and Symbol) based
on the following different rotation scenarios available on the Symbol Style tab of the Style
Properties dialog box:
• Ignore map rotation—When unchecked, the style will rotate with all other graphics
as the map window is rotated. When checked, the style will not rotate, maintaining the
rotation angle specified.
6-15
• Ignore geometry orientation—When unchecked, the style will rotate based on the
orientation of the geometry of the point feature. When checked, the style will not
rotate, maintaining the rotation angle specified.
• Always keep upright—When combining map window rotations and geometry
orientations, it is quite possible that some of the styles will display upside down. This
option ensures that the style will always read right-side up.
Simple Line Style—This line style class provides basic linear rendering capability for
linear geometries and area boundaries. You can define the following simple line style
parameters: color, translucency percentage, width line type, interior boundary tint (area
boundary only), start and end cap (linear only), dash cap, mid-line joins, and offset.
The line type can be one of any number of predefined line types representing dash-gap
sequences, for example, solid, dotted, short dash, or long dash triple dot. A set of fourteen
predefined line types is available. A custom line type setting is also available for you to
enter a custom dash-gap sequence. In addition, you can indicate that the dash-gap
sequence should remain proportional to the line width. This setting is commonly used with
the predefined line types ensuring that the dash-gap ratio stays consistent as line widths
change.
The display of the start and end points of the line may be set independently of one another,
to any of the following:
• Round • Flat • Square • Triangle
• Round anchor • Square anchor • Diamond anchor • Arrow anchor
• No cap (the dash cap setting is used at the start and end instead)
The anchor choices generate a cap that is proportionally larger than the width of the line,
forming a knob at the start or end of the line.
The display of the ends of each dash in the dash-gap sequence of a line may be set to any
of the following: Round, Flat, or Triangle. The display of the joins that occur at each
bend/vertex in a multi-vertex geometry may be set to any of the following: Round, Miter,
or Bevel.
Pattern Line Style—This line style class provides the ability to render a pattern of point
styles along linear geometries, area boundaries, and area hatching. You can define the
following simple line style parameters: point style, position of point style along line,
insets, and offsets.
The point style can be any user-defined style that is of the point style class. You may use
the full range of point style types (picture style, font style, symbol style, or a collection of
any combination of these) to draw the pattern. You can then adjust this property through
the common properties interface.
You can use any combination of five different positioning options on the Pattern Style tab
of the Style Properties dialog box (Fix at start, Fix at end, Fix at center, Fix at vertex
with angle, or Repeat with spacing of) for how the pattern elements described by the
6-16
point style are to be placed along the line. You can choose each option independently;
however, their combined selection and subsequent suboptions may affect the overall point
style placement. For example, the Fix at vertex with angle option allows you to specify
what the minimum angle should be for where the point style should be placed. This
provides the flexibility for not only placing a point at every vertex (0 degrees), but also
allows point filtering so points are only placed on vertices where there is a specific change
in direction. When the Repeat with spacing of option is combined with any of the fixed
location options and a conflict or overprint occurs, the repeat point style that is in conflict
with the fixed point style will not be placed. For the best cartographic results, whenever
the Repeat with spacing of option is used in conjunction with any of the fixed” location
options, the Adjust to produce even spacing setting should be selected.
Note: Linear patterns such as railroads, that are depicted as a line with a point symbol
placed along that line, require two separate entries in the style: a Simple Line Style to
define the line’s characteristics, and a Pattern Line Style to define the point style’s
characteristics.
Simple Fill Style—This fill style class provides basic fill rendering capability for the
interiors of area geometries. You can define the following simple fill style parameters: fill
type, color, and translucency percentage.
Hatch Fill Style—This fill style class provides hatch display capability for the interiors of
area geometries. You can define the following hatch fill style parameters: line style,
spacing, and angle.
Pattern Fill Style—This fill style class provides pattern display capability for the interiors
of area geometries. You can define the following pattern fill style parameters: point style,
rotation, spacing, staggering, and fill mode.
The point style can be any user-defined style that is of the point style class. You may use
the full range of point style types (picture style, font style, symbol style, or a collection of
any combination of these) to draw the pattern. You can then adjust this property through
the common properties interface.
You can define the behavior of the symbol display when the symbol encounters the area
boundary as follows on the Pattern Fill Style tab of the Style Properties dialog box:
• Clip—Causes each patterned point element to be clipped to the boundary of the area.
• Inside—Draws each patterned point element only if the entire element falls within the
boundary of the area.
• Overlap—Allows each patterned point element to be drawn beyond the boundary of
the area, if its origin is within the area or on its boundary.
Text Style—This text style class provides for the rendering of the text within a graphic text
geometry. You can define the following text style parameters: font, font style
6-17
characteristics (bold, italic, underline), size, color, translucency percentage, frame, halo
around the text, alignment, offset, justification and line spacing.
You can define the display behavior of the text based on different rotation scenarios on the
Text Style tab of the Style Properties dialog box:
• Ignore map rotation—When unchecked, the text will rotate with all other graphics as
the map window is rotated. When checked, the text will not rotate, maintaining the
rotation angle specified for the text style.
• Ignore geometry orientation—When unchecked, the text will rotate based on the
orientation of the feature’s geometry. When checked, the text will not rotate,
maintaining the rotation angle specified for the text style.
• Always keep upright—When combining map window rotations and geometry
orientations, it is quite possible that some of the text will display upside down. This
option ensures that the text will always read right-side up.
Image Style—This image style class provides display capability for imagery. Images
participate in the display system exactly as do vectors. As with all other style types, the
impact of changes in the style definition are visible in the map window only after you have
dismissed the Styles or Style Properties dialog box. You can define the following image
style parameters: translucency percentage, contrast, brightness, invert image, transparent
color, transparent pixel values, binary foreground color, and binary background color.
See “Changing the Raster Image Display” in the “Working with Images” chapter.
Area Style—This area style class provides display capability for the boundary and interior
fill of area geometries. As a composite style, the area style has no style properties of its
own for drawing. Rather, it provides a hierarchical style composition tree that includes the
following style collections:
• Boundaries—A collection of zero or more line style types to use in drawing the
boundary of the geometry.
• Fills—A collection of zero or more fill style types to use in drawing the interior of the
geometry.
Area features also provide the ability to display the following:
• No boundary • Any number of line styles for a boundary
• Pattern line styles for a boundary • Any number of fill styles for an interior.
The following is an examples of area style usage for interior boundary tints:
6-18
Compound Style—This compound style class provides display capability for the point,
line, and area geometry members of compound geometries. As a composite style, the
compound style has no style properties of its own for drawing. Rather, it provides a
hierarchical style composition tree that includes the following style collections of:
• Points–Zero or more point style types to use in drawing the point geometries.
• Lines–Zero or more line style types to use in drawing the line geometries.
• Areas–Zero or more area style types to use in drawing the area geometries.
Compound features also provide the ability to perform the following:
• Display no points, no lines, and/or no areas.
• Display any number of point styles, line styles, and areas styles.
• Guarantee, through style collections, that points are on top of lines, which are on top of
areas.
Looking at Style Collections

This section discusses the creation and manipulation of collections of style types. Each
individual style type has unique capabilities and user interface as described in the previous
section. When these style types appear within collections, additional capabilities and user
interface are available.
When looking at the structure of styles, there are basically three types: simple, composite,
and collections. Simple structures involve a single definition within the style. Composite
structures (Area and Compound) involve multiple predefined definitions within the style.
The style below on the left illustrates a simple structure, a Simple Line Style representing a
shoreline. The style below on the right illustrates a composite structure; where the
predefined structure is the Boundary Styles and Fill Styles. The style is composed of a
Simple Line Style for the area boundary and a Hatch Fill Style for the fill, representing an
intermittent lake.
6-19
Collections are structures that occur when there are multiple definitions within a style
class. Collections can be created within a simple style structure, as illustrated in the style
below on the left. Or they can be created within a composite style structure, as illustrated
below on the right.
The style for the intermittent lake above does not contain any collections. While there are
multiple definitions in the style, there is only a single definition in each of the predefined
branches in the hierarchy. In contrast, the Fish Hatchery style above contains multiple Fill
Styles, and thus contains a collection. When the second Fill Style was added, the Fill
Styles branch became a collection.
Collections are optional and may be created at any time. You can create a user-defined
collection within the style composition tree of the Style Properties dialog box by right
clicking on a member of the tree to display the context menu and then selecting either the
New Style or Select Style options. This adds another member to the tree, and
automatically converts the chosen member to a collection, and puts the original style
definition and the newly created or selected style definition into that collection.
Once a style collection exists, the opportunities for manipulating that collection are the
same. More members may be added by right-clicking on the collection member and then
using the New Style and Select Style options as described. Additionally, each existing
member may individually be deleted, renamed, replaced, reordered, copied, changed to
another style type, or edited.
Like any other style type, a style collection has style properties that influence its behavior.
In the case of a style collection, these are not visual characteristics in themselves, but are
instructions for the order that the collection as a whole is to be drawn. When a style
collection is selected in the Style Properties dialog box, the following three options are
made available:
• Order by feature—This option draws the entire style collection one feature at a time
(Feature 1 – Style A, Style B. Feature 2 – Style A, Style B).
• Order by style—This option draws all of the features one style at a time within the
collection, (Style A – Feature 1, Feature 2, Style B – Feature 1, Feature 2). A common
6-20
use for this capability is for intersection clearing in the case of a multi-part linear
styles. This option is only available for style collections that occur at the root of the
style definition.
• Select single style component—This option draws one feature at a time, using only a
single designated style from the collection (Feature 1, Style B – Feature 2, Style B).
The preceding illustration shows the three distinct drawing orders available, from left to
right: Order by feature, Order by style, and Select single index component.
As with other style types, you can find and select a style collection on the Styles and Select
Style dialog boxes, where you can edit the most commonly used style properties, with a
focus on providing group editing of all members of the collection. In most cases, these
collection controls provide limited editing capabilities because the collection may contain a
mixture of different style types within that style class, and those style types may have
different properties, as follows:
Point Collection Style—Permits manipulation of the color and size of all point styles.
Line Collection Style—Permits manipulation of the color and width of a simple line style.
Fill Collection Style—Permits manipulation of the fill color and translucency percentage.
Area Collection Style—Permits manipulation of the fill color and translucency
percentage, and of the boundary color and width of the line style(s) associated with the
area boundary
Compound Collection Style—Permits manipulation of the following:
• Fill color and translucency percentage.
• Boundary/line color and width of the line style(s) associated with the boundary/line.
• Point color and size of the point style(s).
Text Collection Style—Permits the manipulation of the font, size, font style characteristics
(bold, italic, underline), and color.
Image Style—Collections are not supported for this style class. However, the common
controls permit the manipulation of translucency percentage, contrast, and brightness.
Rules for Synchronizing Elements of Composite Linear Style

Definitions
A composite linear style definition is one that contains two or more subordinate linear style
definition elements. When these subordinate elements involve either dash-gap
6-21
sequences (any non-solid Simple Line Style) or symbol spacing (any Pattern Line
Style), it can be important that the dashes, gaps, and symbols be placed consistently
relative to one another. Correctly spacing these elements produces complex lines that
are commonly referred to as being ‘in phase’ or ‘synchronized’.
For composite linear styles composed of non-solid simple line styles, GeoMedia’s
interpretation of the linear style definition requires that the shortest dash length in any
linear element be greater than or equal to the width of that linear element. Perceived errors
in the way composite linear style definitions are rendered are most commonly due to the
failure to take this requirement into consideration. Specifically, the following two cases
lead to style definitions that may be perceived as being incorrectly rendered:
• Use of style definitions (pre-defined or user-defined) that contain a ‘dot’—A dot is
specified by a dash length of 0 (zero). However, when drawn, it must be drawn with a
length equal to the width specified for the linear element. The difference between the
dash-length specified (0) and the actual length used to render the dot (line width) may
result in unexpected results when the linear style is rendered.
• Use of a dash length that is less than the line width—Because dash caps are included in
the total length of a dash, and because the length of a dash cap is half the width of the
line, the minimum length for any dash is the length of two dash caps, or the line width.
The use of explicit dash lengths (not zero-length dots) and dash lengths greater than or
equal to the width of the linear element ensures proper interpretation of composite linear
style definitions. Care must also be taken when changing line widths – such changes may
cause dash lengths to be less than the new line widths, resulting in the loss of proper
phasing.
Creating and Managing Named Styles

The Styles command lets you manage named style definitions through the Styles dialog
box. With this command, you can perform the following:
• Create new styles • Rename styles
• Change style properties • Preview styles
• Delete styles • Organize styles into folders
• Set units of measure for style • Browse styles, including sorting and filtering
properties by various style characteristics
See corresponding GeoMedia Help topics for more information.
You perform these and further management tasks through the three main styles dialog
boxes: Styles, Style Properties, and Select Style. There is a great deal of similarity in
design and function among these dialog boxes, as well as interplay among them, but they
are optimized for different workflows. The most apparent aspects of these three dialog
boxes to be shared are the styles list and the style preview.
6-22
The styles list provides a visual listing of the named styles available in the GeoWorkspace.
This list presents a folder-like hierarchy of style definitions in the familiar Explorer look.
The following three alternate views of the list are available:
• Details—Styles in a single list by name, with a small sample rendering of the style and
additional columns for name, style class, style type, description, and folder.
• List—Styles in columns by name, with a small sample rendering of the style.
• Icons—Styles in rows by name, with a large sample rendering of the style.
You can filter the list by style class, and sort it by name, style class, style type, description,
or folder. You can also select styles and style folders and manipulate them through a right
mouse menu, which provides capabilities for you to create new style folders and style
definitions, rename, change properties, delete, and cut, copy, paste within the style list.
For more information on style classes and style types, see “Style Types” earlier in this
section.
The style preview provides a flexible visualization capability for a single selected style. It
lets you control the background color and magnification of the preview, display the
location of the origin for point and text styles, and gives you a choice of sample geometries
to use in the preview for linear and area styles.
Working with the Styles Dialog Box

The Styles dialog box, displayed by the Legend > Styles command, is designed for
creating and managing named style definitions within the GeoWorkspace. You can edit
the common properties of a style on this dialog box, or access the Style Properties dialog
6-23
box through Properties to edit the complete properties. Additionally, clicking Units
displays the Style Units dialog box, which lets you specify the units of measure that style
properties are expressed in.
See the corresponding GeoMedia Help topics for complete information on these two dialog
boxes.
To create a named style:

1. Select Legend > Styles.
2. Click New; then select the appropriate style type from the drop-down list.
3. Edit the common properties for the new style as necessary; then click Close.
OR
Click Properties to open the Style Properties dialog box to view and edit the
complete set of properties for the new style.
4. After editing the complete properties, click OK to return to the Styles dialog box.
To rename a named style:

2. Select Legend > Styles; then from the Styles dialog box, right click on the style name
or icon and select Rename from the right mouse menu.
3. Type the new name in the highlighted name field.
To delete a named style:

1. Select Legend > Styles; then select the appropriate style in the styles list.
2. Click Delete from the toolbar, or select Delete from the right mouse menu.
6-24
Working with the Style Properties Dialog Box

The Style Properties dialog box lets you edit existing style definitions. These could be
named styles resident in the GeoWorkspace, or current styles associated with legend
entries. Your editing of a style definition can be something as simple as adjusting style
properties (for example, changing color), or something as powerful as changing the basic
style type (for example, change from a symbol to a picture), or changing the style
composition (for example, constructing a style collection). You can also replace the style
definition with a named style through the Select Style dialog box, which you can access
through the Style Properties dialog box.
See the corresponding GeoMedia Help topic for complete information on this dialog box.
Note: You can also create new styles from the Style Properties dialog box by selecting
Add Style (icon) > New Style. In this case, the new style of the current style type is
immediately added to the Style composition list on the Style Properties dialog box.
You can access the Style Properties dialog box from the Styles, the Select Style, the
Legend Entry Properties, and the Add Thematic Legend Entry dialog boxes, and from
the legend right mouse menu.
See “Adding Entries to the Legend” and “Creating Thematic Maps” in this chapter.
The style composition display on the Style Properties dialog box has a hierarchical
presentation of the style, with a dedicated rendering of each component in the style
definition. It permits the addition, replacement, removal, and reordering of component
members of the style definition.
6-25
The style preview display varies with the style type of the selected item in the style
composition tree. You can preview the entire style or any individual component of a style
definition.
You can review and edit the complete set of style properties on two tabs, available
depending on the style: the style-specific main style tab (for example, the Symbol Style
tab), which contains the commonly used style properties, and the Advanced tab.
See the corresponding GeoMedia Help topics for a complete description of the style-
specific parameters on both tabs and how they are defined.
The following example shows these two tabs for the symbol style.
The Advanced tab appears when any style is selected, except area and compound. This
tab is, however, available for the component parts of these two styles. The Advanced tab
gives you a style-specific comprehensive tabular view of all aspects of the style definition,
and the specifications of attribute-based display override rules for each. The grid contains
one row for each style property with three columns of information describing each
property. If animation is turned on, the grid contains a fourth column, Animation.
Clicking the button in this column displays the Animation dialog box for defining
animation frame sequence on the style property.
6-26
The grid also provides for the definition of a default or fallback value in case the attribute-
based assignment fails. You can edit the properties of the style in a generic fashion using
standard editors for known style property types such as color, style definition, or one of
several enumerated types. All unknown style properties are treated as a key-in field of the
appropriate type.
The Advanced tab columns are the following:
Property—Read-only column alphabetically listing all style properties of the selected
style (for example, Size, Color, and Rotation). Hovering over a cell in this column shows
the property name and data type (Boolean, Double, Text, and so forth) as a tooltip.
Default Value—Read-write column displaying the value of each style property used as the
default for displaying the feature. These values correspond directly to the settings
available on the main style tab for each style type, and serves as the backup value in the
event that an attribute-based assignment fails. Cells in this column are either a key-in field
or provide a drop-down list for you to choose from for the available options. For example,
when editing the Displayable property in the Default Value column, after selecting the
cell, a button appears that displays a drop-down list for you to make a selection.
Clicking in other cells might display a drop-down list of options or make the cell active for
direct key in. These values can optionally be overridden by an attribute-based expression
placed in the Attribute Based column.
Attribute Based—Empty column by default, but it can be populated with an existing
attribute value or an expression in the same grammar used with the Functional Attribute
system. The attribute value or expression is evaluated when used in display, with any non-
null result overriding the default property. When you click in this column, a drop-down
list appears from which you can select from a list of available attributes or select the
Expression option. Selecting Expression from the list displays the Expression dialog
box, which allows you to build an expression. Depending on the data type of the selected
property, an entry is added to the drop-down list for each available attribute that matches
that data type.
See “Working with Functional Attributes” in the “Analyzing GeoMedia Data” chapter.
The following example demonstrates how to use the Attribute Based definition to specify
which point symbol to display. The Symbol Style type has a source property that identifies
the symbol file to use. In the case of multi-symbol file types (*.fsm, *.cel, *.svg), the
symbol name is appended to this definition. The syntax for this property is
“Source;Name”. In our example, Source is the Symbol file name, and Name is the
Attribute. An expression can be built to construct the appropriate syntax required for the
Source property as follows:
6-27
CONCATENATE(";","Symbol file name",Attribute)

Symbol file name = "C:\Program Files\GeoMedia\Symbols\BaseMap.svg"
Attribute = Feature_Type
In this example, the symbol name in BaseMap.svg matches the value for the attribute
Feature_Type exactly, such as School, Church, Cemetery, and so forth.
Another example demonstrates how the Attribute Based definition can be used to control
the display status of a feature by using an expression to set the Displayable property. You
can turn on or off a legend entry based on the current map window display scale, or turn on
or off an individual feature instance based on the attribute of the feature. The Displayable
property is a Boolean data type, meaning it requires a True or False definition. A Logical
expression can be used to return a True value. The following syntax can be used to specify
that the feature should be displayed when the display scale is greater than 100,000.
DISPLAYSCALE() > 100000
You can also specify a scale range using the following syntax:
DISPLAYSCALE() > 100000 AND DISPLAYSCALE() < 500000
To test for an attribute value, the following syntax can be used:
IF (MyAttribute="Bridge", TRUE(), FALSE())
Or
IF (MyAttribute is null, TRUE(), FALSE())
In these examples, the feature has an attribute called “MyAttribute”. In the first test, the
feature is displayed only when that value is “Bridge”. In the second test, the feature is
displayed whenever “MyAttribute” has not been defined.
Note: When using Attribute Based definitions for the Displayable property in Composite
or Collection style structures, each of the leaf nodes in the structure needs to be defined.
For example, in an Area Style, the boundary style and the fill style both need to have their
Displayable property set with the appropriate expression.
Animation—Animating styles draws attention to critical features or situations as attribute

values change. Animation is more than attribute-based symbology; a change in the value
of an attribute may simply trigger the animation. Animation draws awareness or
emphasizes a particular feature by changing the style of the feature or simply modifying
the style properties of a feature through a sequence of values over time. You should only
6-28
use animation to provide emphasis of a small number of features within a map display; it is
not intended for application to a legend entry displaying a large number of features.
Misuse may result in poor map display performance.
This column displays the animation state button for each row, indicating the current
animation state for each style property. The three states are as follows:
Enabled but not defined Enabled and defined Not enabled
Clicking this button in any of the three states displays the Animation dialog box, which
lets you define the animation frame sequence. Each member of the sequence is a frame
with a designated style property value (or expression), as well as definition of the timing
and nature of the transition to the next frame in the sequence. Note that you cannot define
animation for the “Locatable” style property.
Clicking New or Properties on the Animation dialog box displays the Animation
Property dialog box, which lets you define the properties for a specific animation frame.
The options available vary with the selected style property.
In addition, the Animation icon on the Style Properties dialog box displays the Animate
Style dialog box, which lets you set the animation properties (Animated and StartTime) of
the root style for legend entries, except when the root style is a non-image style. This
dialog box also lets you enable/disable the animation.
See the corresponding GeoMedia Professional Help topics for complete information on the
animation user interface and its use.
6-29
To edit a style of a legend entry:

1. Double click on the style icon for the legend entry to open the Legend Entry
Properties dialog box; then click Properties to open the Style Properties dialog box.
OR
Right click on the legend entry, and select Legend Entry Properties from the right
mouse menu; then click Properties to open the Style Properties dialog box.
OR
Right click on the legend entry and select Style Properties from the right mouse menu
to open the Style Properties dialog box.
2. Edit the appropriate style properties.
3. Click OK to save your edits to the style properties.
Working with the Select Style Dialog Box

The Select Style dialog box lets you select an existing style definition from the named
styles in the GeoWorkspace. The Select Style dialog box is displayed when you choose
the Add Style > Select Style or Replace Style options on the Style Properties dialog box.
After selecting a named style, you can use it as is, or change the style definition before
using it. For simple changes, you can use the common properties directly on the Select
Style dialog box. Or, for more advanced changes, you can click Properties to display the
Style Properties dialog box. You can also make a new named style from what you have
selected/adjusted.
And, for more information on styles, see the “Style Types” in this section.
6-30
Working with the Legend Entry Properties Dialog Box

The Legend Entry Properties dialog box lets you define how a feature is represented in
the map window by editing an existing legend entry. The options and fields on this dialog
box vary depending on the style of the selected legend entry, and are the same options
available for each style on the Add Thematic Legend Entry dialog box, except for the
addition of the Apply button. This button lets you update the specified legend entry based
on the settings defined on the dialog box without dismissing the dialog box. From this
dialog box, you can access the Style Properties dialog box and the Named Style dialog
box. You can access the Legend Entry Properties dialog box by double clicking on the
style icon of a legend entry or from the right mouse menu.
Changing the Type of Style of Legend Entries:

There are three types of style presentations for legend entries available in the map window:
Standard, Range Thematic, and Unique Value Thematic as illustrated in the following
figures:
Standard Range Thematic Unique Value Thematic

The Standard type portrays all of the selected features with the same style definition,
whereas the Range Thematic and Unique Value Thematic types portray a classified
definition of the selected feature where each class has its own style definition. A legend
6-31
entry with a Standard definition can be expanded into a Thematic definition. Similarly, a
Thematic definition can be collapsed down to a Standard definition.
To change from one type of legend presentation to another:

1. Select a legend entry; then from the right mouse menu, select Legend Entry
Properties.
OR
Double click on a legend entry to display the Legend Entry Properties dialog.
2. On the Legend Entry Properties dialog, select the appropriate style Type.
3. Define the appropriate parameters; then click OK.
See the corresponding GeoMedia Help topic for complete information on this dialog box,
and the “Creating Thematic Maps” section in this chapter.
Obtaining Symbols for Feature Class Displays

The Define Symbol File utility provides the ability to translate symbols from several
different input formats into the GeoMedia Feature Symbol file (.fsm) format as well as
output to Scalable Vector Graphics (.svg).
The software delivers several symbol libraries that contain symbols you can use to
represent point-type features and to pattern linear and area features. The symbol libraries
are organized by industry, such as GIS (GISsym.fsm), Utilities (UTILsym.fsm), Recreation
(recreation.fsm), Transportation (transportation.fsm), and so forth. They are installed in
the <drive:>\Program Files\GeoMedia\Symbols folder. You can change this default
locations on the File Locations tab of the Options dialog box (Tools > Options).
If these symbol-library files do not contain the symbols you want, or you would like to
combine symbols from across multiple symbol files, you can create your own symbol
library file using the Define Symbol File utility. This utility supports assorted file types,
including: map window symbol (.fsm) files, layout window symbol (.sym) files,
MicroStation cell (.cel) files, AutoCAD block (.dwg) files, and Scalable Vector Graphics
(.svg).
See the Define Symbol File utility’s online Help for complete information.
To create your own symbol files:

1. From the Start menu of the Windows taskbar, select All Programs > GeoMedia >
Utilities > Define Symbol File.
6-32
2. To place map window symbols (.fsm), layout window symbols (.sym), AutoCAD
blocks (.dwg), or MicroStation cells (.cel), from an existing file into the new file:
− Click Add.
− Identify the appropriate file type, select a file from the list on the Add From File
dialog box, and then click Open.
− Use the SHIFT and CTRL keys to select symbols from the list.
− Click Insert.
− Click Close.
The symbols you selected are appended to the new library file. Symbol colors that
match the map-window background may be replaced with another color so they can be
seen against the software background.
3. To change the name or description of a symbol, select it, click Edit, make the changes,
and click OK on the Edit Symbols dialog box.
4. To remove a symbol from the library, select it and click Remove.
5. Click Save As, and save the opened file in the \symbols folder.
6. Close the Define Symbol File dialog box.
6-33
Note: 1 ) To have the correct color definition transferred from your MicroStation cell
library to the new GeoMedia symbol file, copy the MicroStation design-file color table
used when creating the cells to <drive>:\Program Files\GeoMedia\Program\Color.tbl.
The RGB definitions obtained from the color table will be used when creating the new
symbols. 2) If MicroStation fonts are used in the .cel files, for the correct translation of the
font, you must copy the font resource file into the <drive>:\Program
Files\GeoMedia\Program\Symtrans\font.rsc, and update the same location in ‘MS
Resource files’ entry under the [Options] section of <drive>:\Program
Files\GeoMedia\Program\Symtrans\DGNGT2D.ini.
Creating Symbols in Layout Windows to Use in Map

Windows
You can create your own symbols in the layout window through a two-step workflow.
You first create the required symbol with the layout window graphics commands as a
layout window symbol file (.sym), and then you add it to a map window symbol file (.fsm)
or scalable vector graphic file (.svg) with the Define Symbol File utility.
Note: Double clicking a .fsm file starts the Define Symbol File utility.
When creating the layout window symbol files, you should draw the graphics at the
appropriate output scale and size of intended use, using the appropriate line thickness and
colors. When converted to a map window symbol file, the size of the symbol and all of the
line thickness definitions are proportional. In other words, you can resize the symbols
during placement, but when you do, as the geometry scales, the line thickness scales as
well. If the symbol size defined with the utility is equivalent to the original layout window
symbol size, the symbol appears identical in the map window to the symbol drawn in the
layout window.
See “Obtaining Symbols for Feature-Class Displays” in this chapter and the Define
Symbol File utility’s online Help.
To create a layout window symbol file:

1. Draw the appropriate elements on a layout sheet using any of the drawing commands
located on the Drawing toolbox; then place them in a select set.
Note: When creating a symbol using different elements, press CTRL while choosing
elements with the Select Tool.
2. From the Drawing toolbox, select Draw > Create Symbol.
6-34
3. Click a point on the layout sheet to define the origin of the symbol.
4. On the Save As dialog box, select the directory, and then type an appropriate name.
The document is saved with a .sym extension.
To add a layout window symbol file to a map window symbol file:

1. From the Start menu of the Windows taskbar, select All Programs > GeoMedia >
Utilities > Define Symbol File.
2. To place a layout window symbols (.sym) into a new or existing file:
− Click Add.
− Select Layout Window Symbol Files (*.sym) as the file type, select a file from
the list on the Add From File dialog box, and then click Open.
− Select the symbols from the list.
− Click Insert.
− Click Close.
The symbol selected is appended to the new library file.
3. Click Save As, and save the opened file in the \symbols folder.
4. Close the Define Symbol File dialog box.
Working with Legends

The legend contains the following parts:
• A title bar.
• Two legend tabs, Display Order and Groups.
• Legend entries, which you use to control the display of the objects in the active map
window. Legend entries can have titles, subtitles, and headings.
Looking at the Two Legend Tabs

The legend contains two tabs that give you two ways of looking at your map window data.
The Display Order tab shows the display priorities of all the legend entries. This is the
traditional perspective in which the order of the legend entries, from bottom to top, dictates
the order in which data is displayed. The Groups tab shows the logical relationships (in
terms of groups or categories) among all the legend entries. This offers the opportunity to
group and order legend entries independently of their display order. Thus, you can impose
not only to impose a user-desired order on the legend entries independent of display order,
but also perform group manipulations (for example, turn display off) in a single step. This
capability is useful, for example, when you have a large number of legend entries in your
6-35
legend but you only need a limited number displayed for certain workflows. Grouping
legend entries on the Groups tab allows you to easily do this.
Hierarchical Display of Legend Entries

Both tabs contain a hierarchy of legend entries in a treeview and support similar
functionalities except that a change to the position of an legend entry on the Display
Order tab affects the display priorities of all the legend entries, while a change to the
position of a legend entry on the Groups tab does not.
Both tabs also contain two types of legend entries in the views: leaf, and group. The leaf
legend entry displays in the map window, and the group legend entry represents a
collection of (leaf/group) legend entries. A legend entry may be a group that contains
other legend entries, or a leaf that performs the display of data, but not both. Any level of
nesting is allowed. Group legend entries may be collapsed or expanded. While leaf legend
entries are commonly present in both tabs, and may be manipulated from either tab, group
legend entries are normally present only on the Groups tab. Thematic groups on the
Display Order tab are an exception to this rule.
The method used for creating the group dictates the types of changes available within the
group. For example, a group created by thematics only allows you to rearrange the order
of items within the group. A group created through the Categories command or the New
Group command allows you to rearrange the order as well as to add and to delete items in
the group. Modifying the contents of a group created by the Categories command only
impacts the legend; it has no affect on the original category.
Only one legend tab is visible at a time. However, you can easily switch tabs by clicking
the tabs at the bottom. In both tabs, arbitrary grouping is supported. When you make a
change to the properties of a legend entry, such as display mode or title, the change is
reflected in the corresponding legend entry on the other tab, if the legend entry is present
on the other tab (groups are commonly present in only one legend).
The two tabs share the same selection of legend entries. That is, when you select a legend
entry in one view, the corresponding legend entry is also selected (if present) on the other
tab. Any operation on a group item is applied to all of its child legend entries, regardless
6-36
of whether the child legend entries are selected. Also, when you delete a leaf legend entry
on one tab the corresponding legend entry on the other tab is also deleted.
Docking the Legend

You can dock the legend in the map window wherever appropriate for your workflow by
selecting Position Legend from the map window right mouse menu. This command lets
you place the legend in the following three positions within the map window:
Floating (the default) Left side docking Right side docking

When docked, you can control the relative size of the legend and map window. In this
configuration, the legend does not obscure any data in the map window. Its height is fixed
to that of the map window. When undocked, the legend occupies its traditional location as
a floating legend over the map window.
Note: When the map legend is floating, the caption of the named legend is shown. You
can edit this name through the Legend Properties dialog box.
The graphic key that accompanies each legend entry may take on your choice of large,
medium, or small icons, and may vary in size for point and graphic text features. Legend
entry statistics are provided, and statistics are turned on by default for new map windows.
Resizing the Legend

When the map legend is floating, you can resize the legend by dragging any corner or any
edge of its frame. When the map legend is docked on the left side of the map window, you
can resize the legend first by hovering the cursor over the right edge of the legend until the
cursor becomes , then by left clicking the mouse, and last by dragging the overlay
vertical bar and dropping it to any position of the map window. Similarly, you can resize
the right side docked legend by dragging and dropping the overlay vertical bar that
originates from the left edge. When dragging the edge of the docked legend, you can only
resize the width of the legend because the height of the legend is always same as that of the
map window.
In addition, you can select the Fit Legend from the legend right mouse menu to resize the
legend to the minimal bounding box of the legend entries. The behavior varies with the
6-37
docking state of the map legend. If it is floating, the size of the map legend is adjusted to
the minimum bounding box of all legend entries. If it is docked, the width of the map
legend is adjusted to the minimum width of all legend entries while the height of the map
legend is always the height of the map window.
Looking at Legend Style Keys

The following figure illustrated the various default legend entry style keys:
The legend contains a separate entry for each map object. When a feature class or query
has multiple geometry or text attributes, a separate entry is added to the legend for each of
these attributes.
Each entry contains a title and a style key. If statistics for a legend are turned on, the entry
displays the count of map objects in parentheses next to the title. Style keys for feature
classes and queries are dynamic and represent the geometry type of the feature class (point,
line, area, or compound). Style keys for thematic displays, images, and text are static and
represent the object type. You can change the style key by double clicking a style key to
open the Legend Entry Properties dialog box.
See “Working with Styles” this chapter.
Style keys include the following:
Style Key Object Type
Point feature class
Linear feature class
6-38
Area feature class

Text label
Compound feature class
Image feature class
Range thematic display
Unique-values thematic display
Style keys can also indicate the state of the following legend entries:
Style Key Indicates
The data is not loaded. Here are some possible causes:
• If you press ESC while the map object is being loaded, the legend
entry is created but the data are not loaded.
• If you turn off the display of a map object, close the warehouse
connection or the GeoWorkspace, and then reopen the connection or
the GeoWorkspace, the data are not loaded.
• If you replace a legend with a named legend, and the named legend
has the display of a map object turned off, the data for that map
object is not loaded.
• If you have checked the Do not load data when opening
GeoWorkspace option on the General tab of the Options dialog box
(Tools > Options), all legend entries are not loaded.
• If the map object is set to view by scale and not visible initially; the
legend entry is not within its display scale range.
The legend entry is in an invalid state. This could mean the feature table
has been deleted or that an attribute has been altered in such a way as to
prevent the display of data.
Map object is locatable, which means you can use the mouse to click on a
map feature and retrieve its attribute information.
Map object is displayed by scale, which means the feature will only
appear when the map window is displayed within a specific scale range.
Displaying or Hiding the Legend

If the legend is not displayed in the map window, you display it in one of the following
ways:
• From the GeoMedia menu, select View > Legend. A checkmark next to Legend on
the menu indicates that the legend display is turned on.
• Select Legend from the map window right mouse menu.
You hide the legend in one of the following ways:
• From the GeoMedia menu, select View, and deselect Legend.
6-39
• Deselect Legend from the map window right mouse menu.

• Double click the legend icon or the X on the legend title bar, if it is displayed.
Adding Map Objects to the Legend

When you add a map object, such as a feature class or raster image, to the legend, it also
appears in the active map window when it is in the display area. The legend entry controls
the style of the features, queries, categorized items, and reference features. You can add
the same map objects multiple times to create multiple legend entries with different styles.
However, the features , queries, categorized items, and spatial filter reference features
themselves are only loaded once. There is no feature, query, categorized item, or spatial
filter reference feature duplication, just different ways of visualizing the same items.
Note: If you interrupt the loading of map objects by pressing ESC, the entry will still
appear on the legend, but data for subsequent legend entries will not be loaded. To reload
the data, select Load Data from the Legend right mouse menu.
You can add the following types of map objects as entries to the legend:
• Feature classes (Legend > Add Legend Entries)
• Queries (Legend > Add Legend Entries or Analysis > Queries > Display, and most
other Analysis commands)
• Thematic displays (Legend > Add Thematic Legend Entry)
• Raster images (Legend > Add Legend Entries or Warehouse > Images)
See “Inserting Images into Warehouses” in the “Working with Images” chapter for
information on adding image entries.
Adding Entries to the Legend

Add Legend Entries lets you add multiple legend entries that span the set of all
connections and queries to the legend of the active map window. You can select the
feature class/query from warehouse connections, categorized features, reference features,
or queries nodes.
Note: The Categories node only appears in the list if categories have been created using
the Warehouse > Categories command. Likewise, the Reference Features node only
appears in the list if reference features have been created using the Warehouse > Spatial
Filter Reference Features command.
6-40
Each feature class/query is displayed through the default legend entry found in the
designated master legend. If a legend entry for a feature class or query is found in the
master legend, the this command makes a copy of the master legend entry and adds it to the
legend. If there are categorized items defined in the GeoWorkspace, you can automatically
create or add groups and subgroups of legend entries by category and subcategory.
After you select the items to add to the legend, the command creates a legend entry for
every selected feature class, query, categorized item, and reference feature. Additionally,
this command creates legend entries for all the secondary geometry fields of every selected
feature class or query. However, if the secondary geometry field is of type coverage, the
command does not create a legend entry for it.
Grouping legend entries by categories is a useful way to manage large numbers of features
and queries, organizing them into legend groups based on common properties. Categories
manage feature classes and queries into a single group, making it easier to work on them as
a whole, for example, when there is a buffer zone around a road feature. Legend groups
organize these legend entries into a single group for easier location and manipulation when
dealing with large legends. If you have created categories to organize your features, the
Group legend entries by category option uses these categories to automatically create
corresponding legend groups on the Groups tab of the legend when you add features to the
legend. All new groups are added alphabetically at the top of the legend. If a
corresponding legend group is already present on the Groups tab, the new legend entries
are added to it, rather than creating a duplicate group.
To add entries to the legend:

1. Select Legend > Add Legend Entries.
2. Expand the treeview nodes as needed; then select the categories, queries, reference
features, or connections nodes to select all features within that group, or select
6-41
individual features within each group by choosing the appropriate feature within each
node.
3. Optional: Check the Group legend entries by categories check box.

4. Click OK to add the selected legend entries.
To add image entries to the legend:

Image entries are added to the legend using the same procedure just described for adding
any other feature class. This procedure adds the entire image feature class. This means
that every image associated with the selected image feature class will be associated with
the new legend entry. If this is not appropriate, the Images command (Warehouse >
Images) lets you select specific image entries from within an image feature class to be
associated with the new legend entry.
Creating Thematic Maps

Thematic mapping is the process of classifying data based on the attribute values of a
selected feature class. For example, a feature class called states (as in
USSampleData.mdb) could be thematically mapped so that the states are classified into
discrete ranges based on their average temperature values, thereby allowing you to define
unique styles for each of the ranges defined. All geometry types, except image, can be
mapped thematically and will update when the source data changes. You can create and
edit thematic mappings with the Add Thematic Legend Entries command.
This command lets you map the attributes of graphic data and stylize the graphics based on
the value of a user-specified attribute column. In other words, GeoMedia can paint a
picture in the map window that represents attribute data in the feature class table. This
type of data presentation is more user friendly because it is easier to analyze a picture than
to analyze a column of random statistics.
You can create thematic legend entries for features of the following types: point, linear,
area, compound, coverage, and graphic text. Coverages only support default style
characteristics, and nongraphic types are not supported.
6-42
After selecting the feature class for your legend entry, you edit its display characteristics to
meet your requirements. These characteristics include the type of legend entry and style
definitions or thematic characteristics. The picture sample on the dialog box illustrates the
active display type and changes as the legend entry type changes, as do the available style
definitions or thematic characteristics.
The thematic map updates when changes occur in the source data. The timing as to when
the thematic changes occur varies based on the type of connection. A thematic from read-
write data updates automatically if the edit to the source data is done from the local client
machine. A thematic from read-only data updates when the GeoWorkspace is opened. If
the edit to the source data occurred on a different machine, the thematic updates when the
GeoWorkspace is opened or after selection of Warehouse > Refresh with Warehouse
Changes.
Legend Entry Types

You can choose one of three legend entry types: standard, unique value thematic, and
range thematic.
Standard
The Standard legend entry type symbolizes the feature with a style, letting you edit the
standard legend entry style. A standard legend entry is a single legend entry with no
hierarchy. It has a style, record, and geometry field name all used together to display data.
In defining this legend entry style, you can:
• Select a named style.
• Change the selected style.
• Save the current definition as a named style.
• Change the style properties.
6-43
See the Style Properties and Select Style dialog box topics in GeoMedia Help for complete
information on setting the Style.
Unique Value Thematic

You can use this command to classify a feature based on unique attribute values. This
unique value assignment may be used with numeric as well as character attribute data. The
Unique Value Thematic legend entry type is best used with attributes where the number
of unique values is small. For example, if an attribute column called Airport_Status has
valid values of on-time, delayed, or closed, then this can be used to quickly display
different symbols for each status.
This legend entry style creates a specified set of value classes each with their own style. It
does this by adding appropriate properties to the legend entry and structuring it in a two-
level hierarchy, where each sub-legend entry represents a thematic class based on a unique
value. Each leaf legend entry represents rows with a specific value for the selected
attribute. Every leaf legend entry is associated with a style. Typically, the sub-legend
entries are formatted using a color scheme.
• Select the unique value attribute.
• View unique values, corresponding labels (entry title), styles, and record counts.
• Edit styles and labels (entry title) of leaf legend entries.
• Add, edit, and remove leaf legend entries (unique values).
• Specify the sort order, ascending or descending.
6-44
• Specify an Other entry that contains all unclassified values.
Range Thematic
For numeric attributes, the Range Thematic legend entry can analyze the values and group
them into classes, with each class having a defined range. These ranges or classes may
then be displayed in the map window, each with its own style. For example, county
population values may be broken into ranges, and each county may be color-filled based
on the range its population is classified as.
This legend entry creates a specified set of range classes each with their own style. It does
so by adding appropriate properties to the legend entry and structuring it in a two-level
hierarchy, where each sub-legend entry represents a discrete range. Each leaf legend entry
represents a specific range of values for the selected attribute. Every leaf legend entry is
associated with a style. Typically, the sub-legend entries are formatted using a color ramp.
6-45

• Select an attribute to classify.
• Specify the classification method to calculate ranges.
• Specify number of ranges to distribute the values in.
• View the thematic statistics of the selected feature/attribute.
• Specify the sort order, ascending or descending.
• Specify the style scheme for the output legend entry, colors and weights.
• View ranges (calculated based on input method), corresponding labels (entry title),
styles, and record counts.
• Edit ranges, styles, and labels (entry title) of leaf legend entries.
• Remove or add leaf legend entries (ranges).
• Specify an Other entry that contains all unclassified values.
Setting Range and Unique Value Thematic Parameters

The Range and Unique Value Thematic legend entry styles have similar parameters on
the Add Thematic Legend Entry dialog box as detailed in the following discussion. For
both types, the right side of this dialog box contains Thematic classes and Thematic style
parameters, plus corresponding top and bottom grids.
6-46
Thematic Classes
The Thematic classes frame specifies what inputs are required to produce the range or
unique value thematic classes. To produce the classes, you first select the appropriate
attribute value from those available from the input legend entry. The data types supported
for range thematics are: byte, short, long, float, currency, and double; the data types
supported for unique value thematics are: text, memo, byte, short, long, float, and double.
After selecting the attribute, you select the appropriate classification through the Classify
button to populate the two grids with corresponding styles, values, labels, and counts. The
styles are derived from the current settings of the Thematic styles frame.
For the range style, clicking Classify displays the Classify dialog box.
This lets you create discrete ranges by the following classification techniques:
• Equal Range (the default)— Divides the ranges equally and distributes the values into
each range. The records, most likely, are distributed unevenly into equal ranges..
• Equal Count—Distributes the same number of records to each range. The range
values automatically adjust to distribute the records evenly.
• Standard Deviation—Calculates the standard deviation of all values and applies it to
the number of ranges.
Selecting Equal Range enables the Begin Value and End Value fields in which you type
values to limit the ranges created. If the classification type is not Equal Range, these
fields are disabled, but the minimum and maximum attribute values are displayed.
You also select the number of ranges to create from the Number of ranges drop-down list,
which contains numbers from 2-20 to give you a notion of what is considered reasonable,
but the number is not limited to these values. The value is defaulted to 4, with a minimum
value of 2.
Clicking the Statistics button displays the Statistics dialog box that lets you review the
statistics, such as the number of records, minimum and maximum values in the field, range,
standard deviation, and so forth.
6-47
See the corresponding topic in GeoMedia Help.

For the unique value style, clicking Classify populates the two grids with corresponding
styles, values, labels (entry title), and counts based on the selected attribute.
Thematic Styles
The Thematic styles frame specifies the styles for the leaf legend entries of the range and
unique value thematic classes through base style, colors, and size/width. Unlike the
Thematic classes, any change to any of the parameters in Thematic styles automatically
updates styles corresponding to each of the range and thematic classes, the effect being
immediately visible in top grid.
The Base style functions as a seed for all style-related activities. Clicking Base style
displays the Style Properties dialog box, which lets you modify the current style
parameters. For point geometries, the base style defines which point symbol to use. For
linear geometries, the base style defines the line’s characteristics (line type, caps and joins,
etc.). For area geometries, the base style defines the boundary / fill characteristics. For text
geometries, the base map defines the font characteristics. If the input legend entry is a
range or a unique value legend entry, the base style is obtained from the style property of
the root legend entry. When you edit the base style, it is immediately applied to all
thematic classes in the top grid, using the current color and size schemes. It is also set as
the style for the Other item in the bottom grid.
The Assign colors option lets you specify when colors are automatically assigned to the
thematic classes in the top grid. Automatic color assignment happens when you click
Classify, change the color scheme, or insert a new item into the top grid. In each case, the
active settings in the Thematic styles frame are applied. If this option is unchecked,
automatic assignment of style information to the thematic classes ignores the colors
schemes and defaults to the color of the base style for all thematic classes.
6-48
Note: When assigning colors to area features, the result varies based on the definition of
the Base style. If the base style of the area only contains a boundary definition, the
boundary color will be modified. If the base style of the area contains a fill and boundary
definition, only the fill color will be modified. If the base style of the area contains
multiple fill definitions, the fill color of all definitions will be modified.
The image drop-down list contains colored bands that represent a color scheme. The
name for the color scheme is not displayed in the list but as a tooltip for the active color
scheme. The ramp color schemes are all listed first and then the random colors, but the
order of both is dictated by the color schemes collection order.
When you select a color scheme, it is immediately applied to the styles in the top grid. The
first item in the grid gets the first color in the color scheme. The second item gets the
second color, and so on. If there are more items in the grid than color scheme colors, the
process of assigning colors wraps back to the first color in the color scheme. Selecting a
different color scheme does not re-apply the base style or size ramping to the top grid; only
the colors are adjusted.
The Assign sizes/widths options let you ramp the minimum/maximum size of a point style,
text style, or a compound style that has a point style in it (that is, size applies to point and
text styles only) or the minimum/maximum width of a linear style. Automatic size or
width assignment happens when you click Classify or Base style. In each case, the active
settings in the Thematic styles frame are applied. If you insert a new item, it gets assigned
the base styles width. The size and width check boxes are not displayed at the same time.
If the style is an area style, the check box and the minimum/maximum items are not
displayed. If this option item is unchecked, automatic assignment of style information to
the thematic classes ignores the size/width ramping and defaults to the width of the base
style for all thematic classes.
When selecting the minimum/maximum width, it is immediately applied to the styles in the
top grid. The first item in the grid is assigned the minimum width value. The second item
is assigned the next calculated width value, and so on. The act of assigning a
minimum/maximum width does not re-apply the base style or active color scheme to the
top grid. Only size ramping occurs.
6-49
Grids
The dialog box contains top and bottom grinds. The top grid displays a display state,
styles, values, labels (entry title), and counts. The bottom grid displays the Other class.
Range Legend Entry Type Unique Value Legend Entry Type
Top Grid
The columns in the top grid for range and unique values legend entry styles are populated
as follows:
Check box—Sets the display state of the legend entry in both the legend and the map
window. By default when new items are created, this is checked, meaning the items are
displayed.
Style—Displays a preview of the style for the thematic classes for each row, based on the
current settings in the Thematic styles frame. Double clicking the image displays the
Select Style dialog box, which lets you edit the style for the corresponding thematic class.
Values—These columns vary with the legend entry style. Range displays the Begin Value
and End Value columns, and unique value displays the Value column.
• Begin Value and End Value—Represent the minimum and maximum values of the
selected attribute. These columns let you edit existing ranges, which results in
validations and automatic adjustments with adjacent rows to prevent range overlap.
The Count column is updated automatically to reflect any change in the range. For
new rows, Begin Value has to be specified before the End Value.
• Value—Displays the unique values. This column lets you edit an existing row or add
a new row, which results in validation for uniqueness among all rows in the same
column. After validation, the Count column is updated with the record count
corresponding to the new value entered. The Label column is also updated with the
new value if the record is new (it is not updated if this is an edit). In addition to
impacts to this value, the Other class is updated (record count).
Label—Displays the label for the range or unique value legend entry styles sub-legend
entry. This editable column can have duplicate values; null values are not allowed. For
6-50
the range legend entry style, the label is set to [BeginValue] to [EndValue] by default.
For the unique value legend entry style, the unique value is set as the label.
Count—Displays the count of records associated to a range or unique value legend entry,
either as an absolute record count or a percentage, depending on the Show count as
percent check box setting. This column is updated automatically when the Begin Value
or End Value columns change or the Show count as percent check box setting changes.
Manipulating the Top Grid

You can insert new rows into the grid even when there are no rows existing in the grid
(that is, Classify or Base value have not been clicked). But before adding rows to the top
grid, you must select an attribute. The new row is entered at the bottom of the grid as
normal, and when the focus shifts to another row, the new row is positioned appropriately
in the grid as per the sort order. The number of rows in the top grid and the currently
selected row are indicated by the Class: # of # item at the bottom of the top grid.
The data is sorted by default in ascending order based on the unique values. You can,
however, change the sort order by selecting the following column headers: Begin Value
and End Value for range, Value for unique values, and Label and Count for both. The
Value, Begin Value, End Value, Label, and Count columns can be all resorted.
For ease of use within the grid, you can also display a right mouse menu with the following
commands:
Ramp Colors—Ramps the colors from top selected item to the bottom selected item.
Ramp Size/Width—Ramps the size or width from the top selected item to the bottom
selected item.
Select Style—Displays the Select Style dialog box, which lets you select or edit the style.
Delete—Deletes the selected items.
Bottom Grid
The bottom grid displays only one row, the Other class, which contains all of the
unclassified data and always exists. For the unique value legend entry style, the Value
column is not displayed; for the range legend entry style, the Begin Value and End Value
columns are not displayed. You cannot add new rows to the bottom grid nor delete the
single row. You cannot edit the columns, only check or uncheck the display check box.
To add standard thematic entries to the legend:

1. Select Legend > Add Thematic Legend Entry.
6-51
2. Select the feature class or query you want from the connections, queries, categories and
reference features in the Input features drop-down list.
3. Select the Standard legend entry Type.
4. Check the appropriate Named style from the Styles drop-down list.
5. Optional: Redefine the common properties of the Style.
6. Optional: Click Name Style to rename the style.
7. Optional: Click Properties to redefine the style.
6-52
8. Click OK on the Add Thematic Legend Entry dialog box to add the selected
thematic legend entries.
An entry is created and added to the top of the legend, and the active map window
reflects the changes.
To add range thematic entries to the legend:

2. Select the feature class or query you want from the connections, queries, categories
and reference features in the Input features drop-down list.
3. Select the Range Thematic legend entry Type.
4. From the Thematic classes frame, select the appropriate Attribute for classification
from the drop-down list.
5. Click Classify.
6. Select the appropriate Classification technique from the drop-down list.

If you select Equal Range, type appropriate values in the Begin value and/or End
value fields.
6-53
7. Select the Number of ranges from the drop-down list.

8. Click Statistics to review the contents of the attribute; then click Close.
9. Click OK on the Classify dialog box to populate the grids.
10. In the Thematic styles frame, click Base style to edit the style on the Style
Properties dialog box.
11. Check or uncheck the Assign colors check box; then if checked, select a color
scheme from the drop-down list.
12. For point style, text style, or a compound style that has a point style in it, or a linear
style, check or uncheck the Assign sizes/widths check box; then if checked, ramp the
minimum/maximum size/width values.
Note: You can also perform both of the Assign colors and Assign sizes/widths
operations before clicking Classify.
13. Edit the grid parameters as appropriate.

14. Check or uncheck the Show count as percent check box.
15. Click OK to add the selected thematic legend entries.
An entry is created and added to the top of the legend for each thematic display, and
the active map window reflects the changes.
To add unique value entries to the legend:

2. Select the feature class or query you want from the connections, queries, categories
and reference features in the Input features drop-down list.
3. Select the Unique Value legend entry Type.
4. From the Thematic classes frame, select the appropriate Attribute for classification
6-54
5. Click Classify to populate the grids.

6. In the Thematic styles frame, click Base style to edit the style on the Select Style
dialog box.
7. Check or uncheck the Assign colors check box; then if checked, select a color
scheme from the drop-down list.
8. For point style, text style, or a compound style that has a point style in it, or a linear
style, check or uncheck the Assign sizes/widths check box; then if checked, ramp
the minimum/maximum size/width values.
Note: You can also perform both of the Assign colors and Assign sizes/widths
operations before clicking Classify.
9. Edit the grid parameters as appropriate.

10. Check or uncheck the Show count as percent check box.
11. Click OK to add the selected thematic legend entries.
An entry is created and added to the top of the legend for each thematic display, and
the active map window reflects the changes.
Setting Defaults for Feature Class Legend Entries

You can set defaults for feature class legend entries through the master legend. The master
legend is any specially-designated named legend, as identified through the Legends
command. The master legend provides support for images, thematic displays, queries, and
secondary geometry fields. Also, any given named legend may serve as the master legend,
with the legend designated as the master changing from time to time. Because the master
legend is explicitly managed by you, no legend entry is ever added to the master legend
automatically by the software. To ensure consistent presentation of a data, you should
create a master legend entry for it.
The master legend serves as a template for map objects on all the legends in a
GeoWorkspace. Through the master legend, you can change the default properties for a
feature class so that it will display with the same properties each time it is added to any
legend in the GeoWorkspace.
When a feature class that already has a master legend entry is added to a legend, it is
displayed with the properties defined in the master legend. The master legend entries
override GeoMedia style files (.gsd). When you add features to the legend, the software
first checks if there is a master legend entry for the feature class or query. If there is no
entry in the master legend, the GeoMedia style file (.gsd) is used. If there is no match in
the GeoMedia style file (.gsd), the legend entry is given a default style.
6-55
Changes to the master legend do not affect existing legend entries, but do affect future
additions to legends. You can use the master legend to change the default legend
properties for a feature class, and still customize individual legends.
Note: When you open a GeoMedia 5.2 GeoWorkspace in 6.0, the existing master legend
is made available in the Legends collection, is given the name Master, and it is designated
as the master legend. This ensures that there is no loss from any previously-defined master
legend.
Customizing the Legend

You can move, resize, and close the legend as you would any standard window. In
addition, you can edit, replace, and append the contents of a named legend; rename and
delete a named legend; and select a named legend as the master legend or unselect the
existing master legend. After customizing a legend, you can save it by giving it a name,
and then you can use it in other map windows within the same GeoWorkspace. When you
create a new map window, the New Map Window dialog box presents a list of all the
named legends in the GeoWorkspace. You can select one of the named legends or an
empty one.
IMPORTANT: If you close a map window without naming the legend, the legend of the
map window is not saved.
In addition to the steps listed below, you can use certain shortcuts to change legend (and
thus map-object) properties.
• To edit the style of a map object, double click the style key on its legend entry.
• To copy a legend entry, drag-and-drop with the CTRL key pressed.
• To change a thematic-display attribute, double click the thematic style key.
6-56
• To edit a title or subtitle of a legend entry, double click the title or subtitle.
• To change the display priority of map objects, drag legend entries up or down the
legend with the cursor.
• To delete a map object, select its legend entry and press DELETE.
See “Using the Legend Right Mouse Menu” later in this chapter for complete right mouse
menu functionality.
If you have created and customized a legend that you want to use in other GeoWorkspaces,
save the GeoWorkspace in which you have customized the legend as a template. Then,
when you create a new GeoWorkspace, select that template and use the customized legend.
The legend right mouse menu Properties commands lets you customize various features of
the legend, such as:
• Legend title, which is visible when the legend is in its undocked position only.
• Font characteristics for the legend entry title and legend entry subtitle.
• Background color.
• Display of legend entry statistics. You can choose any combination of record count,
geometry count, and percentage (for thematic classifications only).
• Key size of each legend entry (small, medium, or large).
• Point and text styles fit to the key. You can choose to have point and graphic text
styles fit to the size of the graphic key, or have the size of the point or graphic text
style dictate the size of the graphic key.
To customize legend entries:

1. From the legend right mouse menu, select Properties.
2. Type a new legend Title.
6-57
3. Set the font characteristics of the Legend entry title and Legend entry subtitle by
clicking the corresponding Font button to display the Font dialog box.
4. Click the Background color button to select the background color of the legend from
the Color dialog box.
5. Select the appropriate Key size option.
6. Set the Fit point and text styles to key check box appropriately.
7. Check the appropriate Statistics check boxes to suit your preference. You specify the
type of statistics for thematic displays on the Add Thematic Legend Entry dialog
box.
8. Click OK or Apply to accept the changes.
To control the appearance/contents of a named legend:

The Properties command lets you manipulate the contents and properties of a named
legend. You can add new legend entries, delete existing legend entries, or change the
properties and style of existing legend entries.
1. Select Legend > Legends.
2. Select the appropriate legend name; then click Properties
6-58
3. Change the legend content as appropriate
To fit the legend:

You fit the legend in one of the following ways:
• From the GeoMedia menu, select Legend > Fit Legend.
• From the Legend right mouse menu, select Fit Legend.
To turn off the display of legend entries:

To gain space on the legend, you can turn off the display of some legend entries without
turning off the display of map objects in the map window. The Show Legend Entries
command from the legend right mouse menu controls whether the legend entry is visible or
hidden on the legend. This dialog box lists all legend entries in a hierarchical display. You
can control the display of each item by toggling the check box on and off. A check
indicates that the entry is visible.
6-59
To name a legend:
1. To name and thus save the legend in the active map window, select Legend > Name
Legend.
2. On the Name Legend dialog box, type a name for the legend.
3. Click OK.
To rename a legend:
2. Select the appropriate legend name; then click Rename.
3. Type the new name in the Name field; then click OK.
4. Close the Legends dialog box.
To replace a legend:
You can replace the contents of the legend in the active map window with the contents of
another selected named legend.
2. Select the legend that you want to use as the replacement on the Legends dialog box.
3. Click Replace.
To append a legend:
Append lets you append the contents of the selected named legend(s) to the legend of the
active map window. For each appended legend, a new group is created at the top of the
Groups tab, with the group name being the name of the named legend (with incremented
number appended if needed, to ensure uniqueness). The Display Order legend entries of
the appended legend are added within the new group on the Display Order tab with no
additional hierarchy, and its group legend entries are added within the new group on the
Groups tab. The active map window display is updated to reflect the change in the legend
contents.
6-60
2. Select the legend that you want to append on the Legends dialog box.
3. Click Append.
To delete a legend:
2. Select the legend that you want to delete on the Legends dialog box.
3. Click Delete.
Customizing the Legend Toolbar

The default Legend toolbar contains buttons for the most commonly used legend
operations, but you can customize it to suit your preferences.
To customize the Legend toolbar:

1. Select Tools > Customize.
2. On the Toolbars tab of the Customize dialog box, select Legend from the list of
categories.
3. Drag buttons for functions you do not want off the Legend toolbar.
4. Drag buttons for functions you do want from the grouping of available buttons onto the
Legend toolbar.
5. If you want to add the button that turns the legend on and off, select it from the View
category.
6. Close the Customize dialog box.
Using the Legend Right Mouse Menu

You display the legend right mouse (pop-up) menu by clicking the right mouse button with
your cursor on a legend entry. You can select multiple legend entries while holding down
the CTRL or SHIFT key. The status of the legend entry or entries that you select
determines which options are available on the pop-up menu. Some legend entries may be
read-only, in which case you may not be able to perform operations such as Display
On/Off, Locatable On/Off, Style Properties, and so forth.
Option Does this
Display On/Off Turns on/off the display of objects in the map window associated with the
selected legend entries.
Display by Scale Displays map objects associated with selected legend entries according to a
specified scale range.
Display Scale Displays the Scale Range dialog box to set a scale range for map objects.
Range
6-61
Option Does this

Locatable On Toggles locatability of map objects associated with the selected legend
entries. When enabled, Locatable On indicates that all map objects
associated with selected legend entries are locatable.
Locatable Off When enabled, Locatable Off indicates that one or more map objects
associated with selected legend entries have locatability turned off. When
a legend entry has locatability turned off, Locatable Off appears
disabled..
Add Subtitle Adds a subtitle to the selected legend entry.
Hide Hides selected legend entries on the legend without affecting the display of
associated objects in the map window. To display a hidden legend entry,
use the Show Legend Entries dialog box.
Show Legend Opens the Show Legend Entries dialog box to display selected legend
Entries entries.
Load Data Loads data that was previously in an unloaded state for the selected legend
entries.
Style Properties Opens the Style Properties dialog box to edit the style associated with the
selected legend entry.
Style Scaling Sets the scaling mode for the selected legend entries to Paper (adjusts
style size to nominal map scale) or View (adjusts style size to display
scale).
Map Window Specifies the map window tooltip of the selected legend entry to None
ToolTip (removes the tooltip), Name (sets the feature class or query name as the
tooltip), Attributes (sets the tooltip from a selected displayable attribute of
the legend entry), or Expression (opens the Map Window Tooltip dialog
box to edit the tooltip).
Cut, Copy, Delete Perform standard Windows command functions.
Paste Pastes the legend entries from the clipboard Into, Before, or After the
New Group (Only available from the Groups tab) Creates a new group legend entry at
the bottom of the legend if no item is selected, or as a sub-legend entry of a
Add Opens the Add Legend Entries dialog box to add legend entries into the
legend.
Fit by Legend Fits the contents of the selected legend entries to the map window.
Entry
Legend Entry Opens the Legend Entry Properties dialog box to set the properties of the
Properties selected legend entry.
6-62
Fit Legend Fits the legend to display all entries.

Properties Opens the Legend Properties dialog box to set the properties of the
legend.
Defining Map Window ToolTips

The Map Window ToolTip command on the legend right mouse menu lets you define the
map window tooltip of a selected legend entry. A map window tooltip displays the
information you define for a selected legend entry when you hover the cursor over a
feature in the map window, and as a tooltip in the PickQuick interface.
See “To select a hidden or overlapped feature” in the “Working with Features” chapter
for information about PickQuick.
You define the map window tooltip through the submenu, which provides you with the
following options:
None—Removes the map window tooltip definition, if there is one, of the selected legend
entry so that no tooltip is displayed for the features when the cursor hovers over them. If
no definition exists, None is marked with a dot beside it.
Name—Sets the name of the feature class or query as the map window tooltip. If the
format of the tooltip matches that of the query name, Name is marked with a dot beside it.
Attributes—Opens a submenu of attribute names created from the names of the

displayable attributes associated with the legend entry. Only attributes whose data type is
Text, Memo, number (AutoNumber/Byte/Integer/Long Integer/Single/Double/Currency),
Date, GUID, or Boolean are displayed in the submenu. You select the appropriate attribute
name to be the map window tooltip. If the format of the tooltip matches that of a selected
attribute, when the attributes submenu appears, the attribute found in the tooltip is marked
with a dot beside it to note it is the current tooltip content.
6-63
Expression—Opens the Map Window Tooltip dialog box from which you edit the map
window tooltip. If the tooltip is defined and it is neither the name of the feature class or
query nor the name of any displayable attribute, Expression is marked with a dot beside it.
See “Working with Functional Attributes” in the “Analyzing GeoMedia Professional
Data” chapter.
If no tooltip is defined, the map window displays nothing when you hover the cursor over a
feature, and the PickQuick interface displays only its tooltip.
Deleting Map Objects through the Legend

You remove an object from a map window and from a legend by deleting the associated
legend entry. Deleting the legend entry does not delete the data from the warehouse. To
delete map objects through the legend:
• Select the associated legend entry or entries, using the SHIFT key to select contiguous
entries and the CTRL key to select discontiguous entries or to deselect entries, and
press DELETE or select Delete from the legend right mouse menu.
Creating Additional Map Windows

You can create multiple map windows in a GeoWorkspace to display different views of
your map. Each map window contains its own legend, north arrow, and scale bar.
To create a map window:

1. Select Window > New Map Window.
6-64
2. Type a title for the map window in the Window name field.
3. Select a legend for the map window. The legend can be one that has already been
named (saved) in the GeoWorkspace, if one exists, or an empty legend.
4. Click OK.
Displaying the North Arrow

By default, the north arrow is not displayed. You can toggle the display on and off in the
active map window through View > North Arrow. You can display only one north arrow
in a map window.
You can click and drag the north arrow anywhere within the map window. The size of the
north arrow remains constant regardless of how the scale is changed in the map window. If
the azimuth is defined by the north arrow location, the north arrow is intelligent, that is, it
updates dynamically when you move it or when you zoom or pan through the window. If
the azimuth is user-defined, the north arrow does not update dynamically.
The direction of the north arrow is determined in the following manner:
1. The center of the north arrow window is calculated (the center of the square box
around the north arrow).
2. The position of this center point on the earth is determined.
3. The world coordinates for the center point are given to the Coordinate System
Manager and the azimuth of that point is returned.
4. The arrow is rotated about the center point to match the azimuth.
See the “Inserting North Arrows” section in the “Designing Map Layouts for Printing in
the Layout Window” chapter for information on using north arrows in the layout window.
6-65
To change the appearance of the north arrow:

You can change the symbol used, size, background color, position, and azimuth of the
north arrow. In addition, you can set the north arrow transparency, that is, whether the
north arrow background is transparent when the map window is printed. You can print the
north arrow without a background so that any items behind the north arrow are visible, or
you can print the north arrow so that it masks all the items behind and the background uses
the specified background color. The north arrow always masks when displayed in the map
window. You can also display a compass rose instead of a north arrow. As you make
changes in the symbol, north azimuth, and background color, they are displayed in the
Preview area. This display is always at a fixed size; it does not reflect changes made in the
Size field.
1. With the north arrow displayed in the active map window, select Edit > North Arrow
Properties, or right click the north arrow and select Properties from the pop-up menu.
2. To change the north-arrow symbol, browse to select a different one. The product
delivers .wmf files for north arrows and compass roses in the \GeoMedia\Program
folder, but you can also select another one if you have it.
Note: To see graphics of all the north arrows and compass roses, open the
NorthArrows.pdf file, which is also in the \GeoMedia\Program folder.
3. Select the size from the Size drop-down list, or type the appropriate value. The north
arrow is not defined in ground units; it is printed at the position and size specified in
the map window.
Note: The largest value in the drop-down list is 96, but you can type a larger value in
the Size field. The maximum size allowed is 32767 points.
4. Click the Color button to change the background color.

6-66
Note: If you want the arrow to appear transparent in the map window, select a color
that matches the background of the map window.
5. To make the background of the north arrow transparent during printing, check the
Print transparent check box.
Note: The north arrow appears in a printed copy exactly as it appears in the map
window.
6. Select Azimuth at north arrow location to draw the north arrow according to the
north azimuth of the north arrow location.
OR
7. Select Custom azimuth to define your own azimuth of north, by selecting or , typing
the appropriate degree value.
Note: The azimuth of north is measured clockwise from the vertical: 0 points straight
up, 90 points horizontally to the right, 180 points straight down, and so forth..
8. To save the settings on the North Arrow Properties dialog box as the default settings
for all map windows in the GeoWorkspace, click Save as Default If you do not, only
the properties and location of the north arrow in the active window are saved
9. Click OK.
Displaying the Scale Bar

The scale bar shows intervals in ground units to indicate the distance on a map. You
toggle the display of the scale bar on and off in the active map window through View >
Scale Bar.
The scale bar shows the scale for the window in which it is displayed. You can display
only one scale bar in a map window. You can click and drag the scale bar anywhere within
the map window. The scale that the scale bar uses is the scale of the map window. The
measurement unit of the scale bar is km by default, but you may change that using the Edit
> Scale Bar Properties command.
The scale bar provides great flexibility for changing its appearance through Scale Bar
Properties. You can easily change the scale bar displayed in the active map window by
selecting Edit > Scale Bar Properties or right clicking the scale bar and selecting
6-67
Properties from the pop-up menu, and then setting appropriately the options on the three
tabs of the dialog box. As you make changes, they are displayed in the Preview area.
See the “Inserting Scale Bars” section in the “Designing Map Layouts for Printing in the
Layout Window” chapter for information on using scale bars in the layout window.
The Style tab lets you define the display characteristics of the scale bar including the type,
color, and line widths.
You can choose from the following types of scale bars:

Single Block Double Block Single Block with Centerline
Single Ruler with Ticks Down Single Ruler with Ticks Up Double Ruler
Stepped Ruler
This tab also lets you select the color fill of odd- and even-numbered interval blocks and
the line work in the scale bar. In addition, you set the scale bar height, width, and
centerline. Finally, you can specify whether the scale bar background is transparent when
the map window is printed. You can print the scale bar without a background so that it lets
any items behind the scale bar be seen. Or you can have the scale bar mask all the items
behind it when printed with the background using the specified color. The scale bar
always masks when displayed in the map window.
6-68
The Intervals and Units tab lets you specify information such as the number of intervals,
interval length, and ground units represented by the scale bar. You can also define the text,
position, and font characters of the units label.
If you modify the extents of the map window, the scale bar automatically resizes to
indicate the correct scale bar length. The scale bar length and the number of displayed
intervals may be shortened or lengthened to maintain a length that is approximately one-
fifth the width of the map window. To ensure that information is displayed clearly, the
scale bar holds a minimum length.
You can define the interval properties for the scale bar or have them automatically
calculated based on the size of the map display associated with the scale bar. When you
specify the number of intervals and/or interval length, the scale bar maintains those values
regardless of the effects of resizing or rescaling. If the resulting display is inappropriate,
you can change the scale bar-interval properties.
You can choose from the following unit label positions on the Intervals and Units tab:
Above scale bar Below scale bar
Before interval labels After interval labels
Before and after interval labels Before scale bar
After scale bar Before and after scale bar
6-69
The Labels tab lets you specify the appearance of the scale bar numbers and caption and
where they are displayed.
You can choose from the following fixed interval label locations on the Labels tab:
Every interval Intervals and first subinterval
Intervals and all subintervals Intervals and first midpoint
Scale bar ends and zero
The following example shows displayed interval label ticks:
Note: For scale bars in the map window, the unit for this property is defined by the Line
weight field on the Style Units dialog box accessed through the found on the Style
Definition dialog box of the legend.
See the “Conversion Tables” appendix for converting from the International System of
Units (metric) to the U.S. Customary System, and vice versa.
6-70
Measuring Distances
The Measure Distance tool calculates the linear distance between two or more points.
The measurement interpretation option, the units of measure, and their precision are set on
the Units and Formats tab of the GeoWorkspace Coordinate System dialog box. In
addition, this tool updates the Precision Coordinates control with the coordinate values of
each snapped point found as you move the cursor in the active map window instead of the
coordinate values of the actual cursor position.
After you select the first point, the commands starts measuring the distance between that
point and the cursor location and draws a dynamic line. The distance is displayed on the
Measure Distance dialog box in the Distance field along with the chosen measurement
interpretation (True, Projected, or Paper) and the default unit in the Interpretation
(unit) field. The distance value and dynamic line segment are continuously updated as you
move the cursor.
When you select a second point, the distance between the first and second points is
displayed in the Total field, and the dynamic display between those two points is frozen.
The dynamic display resumes between the second data point and the current cursor
location. Subsequent selected points behave similarly, with the Total field containing the
cumulative distance between the first and last data points entered.
You can display the distances in paper units by clicking the Units and Formats button to
the right of the Interpretation (unit) field to display the Define Coordinate System File
dialog box. You can then use this dialog box to select the appropriate measurement
interpretation, display unit, and display precision. When the Paper (scaled) measurement
interpretation is used, the selections (unit and precision) for the Paper Distance unit type
apply to the display of distances of the Measure Distance command. If the selected
Measurement interpretation is Projected or True, then the Distance unit type applies to
the measurements. Changes to the unit types through the Measure Distance dockable
control do NOT change the units as defined by the View > GeoWorkspace Coordinate
System command.
See "Setting Units and Formats" in the “Working with Coordinate Systems” chapter.
To find the area of a feature, right click a single area feature that you have selected, and
select Select Set Properties from the pop-up menu. The area of the feature is listed on the
General tab.
When using Oracle and measuring areas of features that contain arcs, GeoMedia reads the
three points stored in Oracle to represent the arc and generates a GeoMedia ArcGeometry
object from them. Internally, this object consists of a start point, an end point, a radius, a
normal vector and a greater than PI flag. The GeoMedia ArcGeometry does not keep track
of the original point on the arc that is stored in Oracle (nor does it need to in order to do its
job).
6-71
For feature measurement involving an arc, GeoMedia Professional strokes the

representation of the arc to a polyline using a very fine tolerance, which is calculated by
the measurement software to ensure that the area measurements are correct to within 0.01
sq. m. The points resulting from stroking (perhaps thousands of them) are then used to
calculate the measurement. In GeoMedia Professional arcs are considered circular in the
X-Y plane. Feature length and area measurements within the Select Set Properties
command are always 2-D, so these measurements always use a (stroked) circular arc,
regardless of the Z-values for the start and end points of the arc.
To measure distance:
1. Select Tools > Measure Distance.
2. Optional: Click the Units and Formats button; then change the measurement
interpretation and units to be used to measured on the Units and Formats dialog box.
3. In the map window, click the starting point, and move the mouse to draw a dashed line
to the second point.
The dashed line moves with the mouse, and the Distance fields in the Measure
Distance dialog box is updated dynamically. If the Update coordinates on mouse
move option has been set on the Precision Coordinates control, its coordinate values
are also updated dynamically. The Interpretation (unit) field displays the chosen
measurement interpretation and the corresponding unit.
Note: You can use snaps during measurement to snap to specific locations.
6-72
4. Click the second point, and move the mouse to the third point, click it, and continue in
this fashion until you have the measurement you want. You can press the
BACKSPACE key to delete a previous point measurement, and right click to reset and
start over.
Now the Distance field shows the distance from the last point as you move the mouse,
and the Total field shows the cumulative distance between all points clicked (it does
not update dynamically as the mouse moves).
5. Press the right mouse button to clear the measure.
6. Leave the Measure Distance dialog box displayed while you work on other tasks, or
dismiss it by clicking the X on the title bar.
See the “Conversion Tables” appendix for converting from the International System of
Units (metric) to the U.S. Customary System, and vice versa.
Measuring Angles
The Measure Angle tool calculates the angle between any two selected linear or area
geometry segments (default Segment Mode, or between any two imaginary line segments
designated by four points placed in the map window (Four Point Mode). You can choose
either mode from the right mouse menu, which also contains the Copy To Clipboard and
Exit options. Measurements are displayed directly in the map window in the default unit
and format designated for the GeoWorkspace. Once the measurement has been calculated,
you can copy the angle value, in text format, to the clipboard through the Copy to
Clipboard on the right mouse menu or the <Ctrl>+C accelerator key. This command is
available for features from both read-write and read-only connections. The command also
identifies both parallel and collinear lines.
Measuring an angle with the Segment Mode requires you to define two line segment
portions (of a linear or area feature) as input. If the identified lines do not intersect, an
intersection point is computed to serve as the vertex of the measured angle. The selected
line segments are extended as required to show point intersection. As you move the
mouse, the measured angle value is displayed as a dynamic text at the midpoint of a
dynamic arc showing the angle value.
The command responds to the mouse move and calculates the appropriate angle
measurements. As you hover the mouse beyond the calculated intersection point, the
selected line segment portions are extended appropriately, and the corresponding
supplementary/vertical angle measurement is shown in the dynamics, as shown in the
6-73
following figures. Nothing is displayed when you place the mouse on the intersection
point of the two line segments.
Measuring an angle with the Four Point Mode requires you to define the starting point
and the end point of two line segments between which the angle is to be determined. These
two pairs of points can be points on existing features or points selected by clicking
anywhere in the map window. You can select the points within a pair in any order. The
line segments created by joining these two pairs of points are then extended to intersect at a
vertex point.
The angle between the two lines is shown dynamically. As you move the mouse, the
measured angle value is displayed as a dynamic text at the midpoint of a dynamic arc
showing the angle value. The command responds to mouse moves and calculates the
appropriate angle measurements. As you hover the mouse beyond the calculated
intersection point, the selected line segment portions are extended appropriately, and the
corresponding supplementary/vertical angle measurement is shown in the dynamics.
If the intersection point is off the map window, the command attempts to show the
dynamics (that is, angle value and arc). The command honors the auto pan option so that
by placing the mouse on the boundary of the active map window, you can adjust the map
window extent to see the dynamics and calculated intersection point.
The following figure shows angle measurement when a line segment portion of an area
feature and a linear feature are selected.
6-74
Taking a Snapshot of the Map Window

You can copy an image of the active map window to the Clipboard by selecting the
Snapshot tool from the GeoMedia Edit menu or from the map-window pop-up menu. Use
the Paste tool to paste it into any application that supports Object Linking and Embedding
(OLE), such as Word, MSPaint, or an HTML Web page.
Displaying CAD Files

Display CAD Files lets you quickly and easily display MicroStation V7/IGDS and
MicroStation V8 design files and AutoCAD drawing (.dwg/.dxf) files data in a map
window based solely on levels/layers. This command provides an alternative to using the
delivered Define CAD Server Schema File utility to specify the parameters the software
uses when creating connections with the CAD server. Thus, you do not need to have a
complete understanding of the CAD data or knowledge of the project, for example, how
the features are defined in the project and whether the graphics in the project have
attributes. This is useful for quick viewing or backdrop data. To make this command
easier to use, its dialog box separates functions on two tabs, General and Advanced.
This command automatically builds the CAD server schema (.csd) file based on the
levels/layers you select, makes a connection to that .csd file, and then it displays the data in
the active map window according to the display options set on the Advanced tab.
Depending on the display options set, there is one legend entry (feature class) displayed
per selected level/layer or a single legend entry (feature class) displaying data of all the
selected levels (if you want to see the entire map without style differentiation between
levels/layers). You may also choose to display empty levels/layers (by default empty
levels/layers are not displayed).
Note: You can change the selection of attributes exposed for all feature classes by editing
the .csd file created by this command.
If the GeoWorkspace options are set to match the GeoWorkspace and the default
warehouse coordinate systems when you first make a connection, and if there are no
connections in the GeoWorkspace, and if you have specified a coordinate system file - then
6-75
the GeoWorkspace coordinate system is changed to match the coordinate system you
specified.
To display CAD files:

1. Select Tools > Display CAD Files.
5. On the General tab, select the CAD type from the drop-down list.
6. In the Folder field, type the complete path of the folder containing the CAD files, or
use Browse to locate the folder.
7. From the Available files list, select one or more files you want to display.
8. Optional: Type the appropriate Files of type, or select it from the drop-down list - if
you need to see/select a specific type of files in the Available files list.
9. Optional: In the Coordinate system file field, type the complete path of the file to be
used for all selected design files, or use Browse to select the file.
10. Optional: On the Advanced tab, change the default in the CAD server schema file
field by typing the complete path of the CAD server schema output file or by using
Browse to specify the file.
11. Optional: In the Connection name field, change the default connection name.
12. Accept the default Display all levels/layers display option, or select Levels/Layers to
display and select the appropriate levels/layers in the Levels/Layers list.
13. Accept the default Create a single legend entry for all selected levels/layers legend
option, or select Create a separate legend entry for each selected level/layer.
6-76
14. Optional: Check/uncheck the default checked Do not create legend entries for
empty levels/layers check box to specify whether or not to create legend entries for
empty (no data/statistics) levels/layers.
15. Click OK.
The software creates a new CAD server schema file, a CAD server connection with
that file, and feature classes based on the options set on the Advanced tab; and then
(depending on your selection) displays the features on the specified levels/layers in the
active map window based on the options set on the Advanced tab.
See “Connecting to a CAD Warehouse” in the “Working with Warehouses” chapter and
the Define CAD Server Schema File utility’s online Help.
6-77
6-78
Working with Data Windows
Each data window contains the nongraphic attributes of a single feature class or query.
This equates to a feature table, with each column representing an attribute and each row
representing an instance—a feature—of the feature class. The data in each cell is called a
value or attribute value. Data windows display area, linear, point, image, compound,
graphics text, and nongraphic feature classes, but do not display geometry or spatial index
key attributes.
In a read-write warehouse, you can review and edit the features and values in a data
window, and any changes you make will be reflected in the map window. So, if you delete
a row in a data window, the corresponding feature is also deleted from the map.
You can use the layout window command Insert Data Table to display selected portions
of a data window in the layout window in a customized style.
See “Inserting a Data Table” in the “Designing Map Layouts for Printing in the Layout
Window” chapter.
The data window displays descriptions for attributes with PickLists defined. For editing
such an attribute, a drop-down list box is displayed in the cell. This list contains all the
available descriptions for the attribute values as well as a blank entry (available only if the
attribute is not required). You can insert a value of NULL for this attribute by selecting the
blank value. You can edit an attribute only by selecting a description from the list.
Opening a New Data Window

To open a new data window, you must be connected to a warehouse. Once you open a
warehouse connection, you can select a feature class or query result whose content to
7-1
display in a data window. The feature class or query can be from either a category,
reference features, connections, or queries.
To open a data window:

1. Select Window > New Data Window.
2. Type a title for the data window in the Window name field.
3. Click the plus sign next to the warehouse or query folder that contains the feature class
you want to display in the data window.
If you select a query that has not been run, the software runs the query and displays the
results in the data window. If you select a query that has been run, the existing results
are displayed in the data window.
4. Click OK.
The Data menu replaces the Legend menu.
7-2
Controlling the Data Window

To the left of a data-window title or in the upper-left corner of a maximized data window is
the data-window icon.
Clicking this icon displays a menu that allows you to control the data window. Depending
on the current state of the data window, this menu lets you do the following:
• Restore a minimized window.
• Move, restore, minimize, or maximize the window.
• Close the data window.
• Activate the next data or map window in the stack.
In addition, the GeoMedia Window menu contains tools for cascading or tiling windows
and for activating a different window. The bottom of this menu lists all the open windows
in the GeoWorkspace. A checkmark appears next to the title of the active window.
To change the title of a data window:

1. Select Window > Data Window Properties.
2. On the Data Window Properties dialog box, type a new title in the Data window
name field.
3. Click OK.
Using the Mouse in a Data Window
Note: If your mouse has been reconfigured so that the button functions are reversed, you
must reverse left and right mouse-button instructions in all the product’s documents.
In a data window, you use the left mouse button to do the following:
• Activate the window.
• Place the cursor.
• Create a select set.
7-3
• Select a table, row, column, or cell.

You use the right mouse button to open the data-window pop-up menu. This menu
contains tools commonly used in the data window.
Using an IntelliMouse
If you have a Microsoft IntelliMouse, you can use it to manipulate the display in your data
windows faster and more efficiently. Rolling the IntelliMouse wheel forward scrolls up at
the cursor location. Rolling the IntelliMouse wheel backward scrolls down at the cursor
location.
Using the Data View Tools

To adjust the display in a data window, you use the data view tools, which you access on
the Data menu, from the Data toolbar, or from the data-window pop-up menu. These
tools are available only when a data window is active. Before you use some of these
viewing tools, you generally have to select the entire table, one or more rows, one or more
columns, or one or more cells.
• To select the entire table, click the table button in the upper-left corner of the data
window, or select Edit > Select All Rows.
• To select cell contents, click the cell.

• To select a row, click the row selector. To select adjacent cells in a row, click and drag
the mouse cursor across the cells.
• To select a column, click the column header. To select adjacent cells in a column,
click and drag the mouse up or down.
You can use the SHIFT and CTRL keys to add and remove rows or columns to or from a
select set, but you cannot select a column and then add a row, or select a row and then add
a cell from another row.
You can use Data > Change Contents to replace the feature class or query shown in the
active data window. The feature class or query can be from either a category, reference
features, connections, or queries.
To show columns in the table:

1. Select Data > Show Columns.
7-4
2. On the Show Columns dialog box, toggle the display of individual columns
(attributes) on or off. A check beside a column name means that the column is shown
in the data window. Removing the check hides the column, but does not delete it.
3. Click OK.
To hide columns in the table:

You can hide columns in one of two ways. One way is to toggle it off on the Show
Columns dialog box. Here is another:
1. Select the column you want to hide by clicking its header cell. You can select multiple
contiguous cells by dragging the cursor across the column headers. You select
discontiguous columns by pressing the CTRL key while clicking the column headers.
2. Select Data > Hide Columns. This tool is only available when at least one column is
selected. You can hide all but one column.
To promote rows in the table:

1. Click the row selector(s) of the rows you want to promote to the top of the table.
2. Select Data > Promote Columns.
When multiple rows are promoted, they are displayed at the top, but they retain their
original order in the table.
To sort rows in the table:

1. Click the header of the column by which you want the rows sorted.
2. To sort rows in ascending order, select Data > Sort Ascending.
3. To sort rows in descending order, select Data > Sort Descending.
To display column statistics:

1. Click the header of the column for which you want statistics. The attribute must be
numeric.
7-5
2. Select Data > Column Statistics.
To change the contents of the active data window:

1. Select Data > Change Contents.
2. On the Change Data Window Contents dialog box, select another feature class or
query from either a category or reference features or connections or queries.
3. Click OK to update the active data window.
Editing Cells in the Data Window

When you edit a cell or field in the data window, you are changing the value of an attribute
of the affected feature. The software uses standard Windows editing tools and the
Clipboard to allow you to cut, copy, and paste text in the data window. These actions do
not affect hidden cells or cells containing hypertext. You can also use the Clipboard to
copy features in the data window, but associated graphics are not copied.
7-6
Edit > Cut deletes selected cell values. You cannot cut cells containing the
primary key or other required values.
Edit > Copy copies selected multiple cells, columns, and rows to the
Clipboard as text. For example, you can copy a data view into an Excel
spreadsheet. You can select cells directly as a range of one or more cells or
indirectly by selecting rows or columns, which you can select in various ways
including their buttons on the data window, the Select Tool in the map
window, Select by Legend Entry, and so forth. This command is enabled
when you select one or several cells, rows, or columns in the data window.
Both the Cut and Copy commands let you copy data window column headers
to the clipboard. You set this option through the Copy data window column
headers to clipboard check box on the General tab of the Options dialog
box (Tools > Options). The default (unchecked) is to not copy the headers.
If you are cutting or copying a single cell, the copy header setting is ignored
and the headers are not included. Also, if you have copied data to the
clipboard with column headers, the headers are removed before you paste the
cell data back into the data window.
Edit > Paste copies data from the Clipboard to the selected cell(s). When you
select a single cell, the data on the Clipboard is pasted to the right and down
from the selected cell, replacing the selected cell. When you select a
contiguous block of cells, the data on the Clipboard replaces each selected cell
with the corresponding entry on the Clipboard.
Paste will not work in the following circumstances:
• If the shape you want to paste does not match exactly the shape of the selected cell(s),
except when pasting to one cell.
• If pasting to the right and down would exceed the number of columns in the data
window.
• If pasting would create null values for required cells.
• If the primary key column is not displayed.
• If pasting would require an invalid data conversion, such as trying to paste a text string
containing letters into a numeric field.
• If pasting would require duplicate values for the primary key field or any other fields
requiring unique values.
• In pasting into the last row, the software tries to paste all cells from the Clipboard. If
you have selected multiple cells in the last row, the shapes must match exactly. If you
have selected a single cell, cells are pasted to the right of the selected cell, but not
down. If the paste would populate required fields and create a unique primary key, the
paste creates new features in the database corresponding to each row from the
7-7
Clipboard. Pasting does not occur if the paste would not populate the required fields,
or if the paste would create duplicate primary keys.
You can use Edit > Undo to undo changes made as in standard Microsoft
Office products. You cannot use Undo following a cut or paste operation.
Taking a Snapshot of the Data Window

You can copy an image of the active data window to the Clipboard by selecting the
Snapshot tool from the GeoMedia Edit menu or from the data-window pop-up menu.
Hidden columns and cells containing hypertext are not copied.
You can paste the snapshot into any application that supports OLE, such as Word,
MSPaint, or an HTML Web page.
7-8
Working with Features
A feature is represented in a map window by geometry and is further defined by
nongraphic attributes in the database. The values of these nongraphic attributes can be
viewed as cells in the data window view on the non-spatial data of the feature. For
example, a parcel of land—Parcel 126-A—is represented graphically in the map window
by area geometry.
The area geometry attributes for Parcel 126-A are part of a single row in the Parcels table.
The Parcels table contains information about all the members of the Parcels feature class.
Parcel 126-A is one of 15 members of this feature class. The Parcels table, therefore,
contains 15 rows, one for each parcel.
Among the nongraphic attributes of Parcel 126-A are its identification number (126A), the
name of its owner (P. Brown), and its assessed value ($10,000). Each of these attributes is
a column in the Parcels table. So, the Parcels table has at least the following three
columns: ID, OWNER, and ASSESSED_VALUE.
126A, P. Brown, and $10,000 are values (or cells) in the ID, OWNER, and
ASSESSED_VALUE columns of the row containing the geometry for the Parcel 126-A
geometry.
In a read-write warehouse, you can create a new feature class, delete a feature class, and
edit a feature class definition. You can edit a feature class in the following ways:
• By adding attributes (columns)
• By removing attributes
• By changing attributes
In a read-write warehouse, you can also manage feature data in the following ways:
• By changing attribute values (cells)
• By adding or deleting features (rows)
IMPORTANT: Changes to data in a read-write warehouse are automatically saved as

soon as you make them.
Understanding Geometry Types

Geometry refers to the graphic representation of a feature in the map window. Features are
represented by the following geometry types:
8-1
A point feature is represented by one or more points on a map that represent the
location of a feature. A point can also represent features that cannot be mapped at
the defined map scale. Points can have an orientation, that is, they can be rotated.
Elevation control points, oil wells, and manholes are all examples of point
features.
A linear feature is represented by one or more lines and/or arcs. What appears on
the map to be a single line may actually be line segments strung together to form a
single feature. Rivers, railroad tracks, utility lines, and roads are examples of
linear features.
An area feature is represented by closed boundaries. Each boundary may or may
not contain one or more holes, and the boundaries and holes themselves may be
composed of one or more lines and/or arcs. Counties and land parcels are
examples of area features.
A compound feature may have point, linear, and/or area geometry within the
feature class or even within a single feature.
A text feature is represented by text that appears at a point location on a map.
You can place text in an existing text feature class or create a new one to contain
it. Text can have an orientation, that is, it can be rotated.
An image feature is a raster image.
Features can be contiguous or discontiguous. A contiguous feature has a single geometry.
In a map data set, for example, California is a single contiguous feature that consists of one
geometry. A discontiguous feature consists of multiple geometries. For example, Hawaii
is a single discontiguous feature that consists of several islands, each island being a
separate geometry.
Note: When a discontiguous area is placed so that it completely encloses a second

discontiguous area, then the second discontiguous area becomes a hole inside the area
being placed. When the hole completely encloses a third discontiguous area, the third
discontiguous area becomes an island.
You can create a hole in an area geometry by adding a second area geometry that falls
entirely inside the boundary of the first area geometry. You can create an island inside the
hole by adding a third area geometry that falls entirely inside the boundary of the second
area geometry.
Working with Feature Classes

In GeoMedia, you can create a feature class from an active map window or data window,
and only in an open read-write Access warehouse. When you add a feature to a feature
class, you have the option of placing geometry. A feature does not need geometry to exist,
although most features do have geometry.
8-2
The software allows you to create feature classes in various ways:

• From scratch
• By copying some of the information from an existing feature class into a new feature
class in the same warehouse
• By importing data
• By outputting to feature classes
• By attaching an external data source
Coordinate Systems
When creating a feature class through the Feature Class Definition command, you select a
coordinate system to be assigned to the primary geometry field of the feature class from the
list of available warehouse coordinate systems. Upon starting this command, a coordinate
system is pre-selected on the General tab of New/Edit/Copy – <FeatureClass> dialog
box. For a new feature class, this is the inherent default coordinate system. For an existing
feature class being edited or reviewed, this is the coordinate system assigned to the primary
geometry field.
The available warehouse coordinate systems are listed alphabetically with an icon for each
to indicate its validity and default status, as follows:
Non-default coordinate system.
Default coordinate system, with Default appended to its name. If
the coordinate system name is blank, it is listed with <Unnamed #>,
where # is a number to make the name unique within the list. If the
coordinate system has a non-unique name within the list, the name is
appended with #, a number to make it unique within the list.
Temporary coordinate system. When a new coordinate system
definition is defined, it is added to the list and assigned this icon as
this coordinate system has not yet been written to the warehouse.
Invalid coordinate system. In cases where the coordinate system
environment is faulty such as the following:
• Client side coordinate system metadata table does not exist or
there is no reference to it in the server side table.
• The metadata table is properly set up (that is, it exists and is
referenced), but it is empty.
• The metadata table is populated but does not contain the
coordinate system referenced by the primary geometry field of
the feature class.
8-3
Clicking Save As Default on this tab lets you set the selected coordinate system to be the
default for the read-write warehouse and assign it to the feature class. Only one coordinate
system can be set as the default.
Clicking Properties on this tab lets you review the selected coordinate system definition
on the Coordinate System dialog box. If the coordinate system has not yet been written to
the warehouse, you can edit its definition. You can then save all of the changes to the new
coordinate system definition and assign the modified coordinate system to the primary
geometry field of the feature class. If the coordinate system was identified as the default
warehouse coordinate system, this information is also written to the warehouse.
Clicking New on this tab lets you define a new coordinate system on the Coordinate
System dialog box and assign it to the feature class. When a coordinate system in the
warehouse is modified, the new coordinate system definition is added to the list and is
assigned the temporary coordinate system bitmap as this coordinate system has not yet
been written to the warehouse. Once added, the new coordinate system can be edited
and/or set as default in the warehouse.
Key Attributes
Each feature class created from scratch or by copying must contain a key attribute and a
primary, unique index value on that key. You can define multiple key fields (up to ten) for
a feature class on the Attributes tab of the New/Edit/Copy – <FeatureClass> dialog box.
Note that there can only be one attribute with data type autonumber. You set the key
definition for the current or selected attribute row by clicking the Set Primary Key button
on this tab. This button appears when you select an attribute row. When the selected
attribute is already a part of the primary key, the button name changes to Unset Primary
Key.
Ordering of the attributes in defining the primary compound key is determined by the order
in which they are defined. As you define new keys, they are added at the next available
index. When a key is undefined, that key is removed, and all key indices below it are
adjusted accordingly. The Key column on this tab indicates the key priority ordering by
including the index number (1 to 10).
You cannot modify the key index order directly. However, by undefining and redefining
keys, you can move them to a different index position. For example, to move the key at
index 1 to index 2 when there are 2 keys defined, you have to undefine and redefine key 1.
When you undefine it, key 2 moves up to the first position. When you redefine it, it is
added at index 2.
8-4
Note: It is possible to hide the primary key column(s) from Feature Class Definition by
setting their Displayable flag to No in GeoMedia’s metadata tables. Feature Class
Definition will disable the Set Primary Key button if it determines there are hidden
primary key fields. If the primary key fields are not hidden, the Set Primary Key button is
enabled for Edit mode.
The ODBC Tabular Data Server allows you to create a connection to any nongraphic table
in an ODBC-compliant data source. Thus, you can access additional data stores containing
tabular-only data, such as coordinate locations, addresses, and additional attribute
information. In addition, you can attach one or more tabular-only feature classes from the
following external data sources with the Feature Definition command: a text file, an
Excel worksheet, or an Xbase database. You can, however, only attach an external data
source to a read-write Access warehouse connection.
You can view and handle the resulting table(s) in the target read-write connection similarly
to other tables except that the feature class is read-only. For example, you can edit the
name, description, and data source name of the attached table and copy an attached table.
When you copy an attached table, the software creates a local table without data. This
new, empty table then serves as a template into which you can add data.
The software also allows you to easily to review the general and attribute feature class
properties or an attached table definition, to delete a feature class, and to detach an attached
table.
You should use the Feature Class Definition command to add or to modify features in an
Access warehouse. Using Microsoft Access to modify features in a GeoMedia Access
warehouse can result in the improper operation of the feature class or corruption of the
warehouse.
You should never delete or modify the following tables with Microsoft Access:
• GcoordSystemTable • INGRFeatures
• Gmodifications • INGRGeometryProperties
• GmodifiedTables • INGRAttributeProperties
• INGRSQLOperatorsTable • INGRFieldLookup
8-5
The words in the following list are the keywords in SQL Parser. They are considered
GeoMedia Keywords. As such, they cannot be used in table or column names or anywhere
else in a given warehouse. They can only be used as part of SQL queries.
ABS ALL AND ANY ASC
AVG BETWEEN BY COMMIT COUNT
DATE DELETE DESC DISTINCT EXISTS
FLOAT FROM GROUP HAVING ININSERT
INTO IS LIKE MAX MIN
NOT NULL ON OR ORDER
ROLLBACK SELECT SET SOME SUM
TIME TIMESTAMP UNION UPDATE VALUES
WHERE WITH TO_DATE TO_CHAR TO_NUMBER
See the “Working with Feature Classes” topic in GeoMedia Help, and the “Defining
Attribute-Filter Queries” section in the “Analyzing GeoMedia Data” chapter.
To create a feature class from scratch:

Note: This dialog box is resizable for better viewing of long query names.
2. Select the connection to the read-write warehouse where you want to store the new
feature class; then click New.
8-6
3. On the General tab of the New - <FeatureClass> dialog box, type a name for the
feature class. The feature class name must be unique within a warehouse.
Note: When creating or editing attribute names, the Name column fields may
seem to become un-editable. If this occurs, toggle the Hypertext check box on
the Attributes tab on then off to edit the field.
4. Optional: Type a brief description of the feature class.
Note: The Description field has a maximum length of 255 characters. If you type
more, only the maximum number of characters is assigned to the Text property, and
the extra characters are truncated. Furthermore, in double-byte character set (DBCS)
systems like Chinese, each character can take up to two bytes instead of only one,
which further limits the number of characters you can type in this field.
5. From the Geometry type drop-down list, select a geometry type. To create a feature
class for labels or for inserting text, select a geometry type of Text.
6. For a feature class other than a nongraphic type (None):
To change the default coordinate system, select a coordinate system from the
Coordinate system drop-down list; then click Set As Default.
OR
To change the coordinate system, select a different coordinate system from the
Coordinate system drop-down list.
OR
8-7
To review and/or edit the coordinate system properties, click Properties; then make
the appropriate changes on the Coordinate Systems Properties dialog box.
See the “General Tab (Coordinate System Properties)” topic in GeoMedia Help for
information on using this dialog box.
OR
To define a new coordinate system and assign it to the feature class, click New; then
define the coordinate system on the Coordinate Systems Properties dialog box
7. Click the Attributes tab on the New - <FeatureClass> dialog box, which contains a
grid with a row for each attribute definition.
8. To define a unique primary key for the feature class, click in a cell in the Key column
or select the row; then click on the Set Primary Key button or press the space bar.
You can define multiple rows as key columns as described earlier in this section.
9. In the Name column, type attribute names. Each of these must be unique for the
feature class.
8-8
10. Click the cell in Type for each row to display the drop-down list of available data
types.
11. Select a data type, and define its parameters at the bottom of the Attributes tab,
which varies with the data type selected. The AutoNumber data type has no
parameters for you to define.
12. Optional: You can assign default values for attributes as long as the value is not a
function. Functional defaults are not supported in Feature Class Definition.
13. Optional: Type a brief description of the attribute in the Description cell of each
attribute.
14. Click OK.
15. Note the new feature class on the Feature Class Definition dialog box, and close the
dialog box.
To add, change, and delete attributes:
Note: You can change the geometry type of a feature class only if the feature class is
empty.

2. On the Feature Class Definition dialog box, select the connection to the warehouse
that contains the feature class you want to edit.
2. Select the feature class, and click Edit.
3. On the Edit - <FeatureClass> dialog box, click the Attribute tab.
4. To add an attribute, enter the attribute name, data type, and description in the bottom
row, and set a primary key.
5. To change an attribute, click the cell you want to change, and make the changes.
6. To delete an attribute, select the attribute row, and press DELETE.
7. Click OK to update the feature class.
8. Close the Feature Class Definition dialog box.
8-9
Note: Editing an existing Oracle feature class definition is an Oracle administrative task
and is, therefore, not allowed in the GeoMedia Feature Class Definition tool.
Outputting Feature Data to Warehouses

You can output feature data in any GeoMedia-supported format to a warehouse with the
Output to Feature Classes command. You must have at least one read-write open
connection to use this command.
Output to Feature Classes lets you perform the following:
• Output single and multiple feature classes, queries, categories, and reference features
• Output selected fields from a feature class, query, category, and reference feature
• Control output, key, and autonumber modes
• Review the coordinate system of the primary geometry of the source and target feature
classes
• Set the user-defined coordinate system for geometry of the new target feature classes
In addition, this command lets you create feature classes from existing feature classes or
queries. You should bear in mind that features are static and are stored in the database; in
contrast, queries are dynamic and are not stored in the database.
Output to Feature Classes lets you output a feature class from a connection back into
itself provided the target table name does not conflict with existing table names. However,
the command does not allow append, force append, update, or append-and-update
operations back into the same feature class.
Using the General Tab

To perform an output operation, you use the General and Advanced tabs of the Output to
Feature Classes dialog box. On the General tab, you first select the source feature data
warehouse—that is, the warehouse that contains the data you want to output. You can
select any mixture of feature classes, queries, categories, and reference features, across any
number of connections. If the source warehouse has a spatial filter applied, only those
features allowed by the filter can be output. You select the source from list of all open
connections (read-write and read-only) or the set of available queries, with a single
additional item Queries. Your selection populates the default values for the selected items
in the feature classes list on the Advanced tab.
You next select the target read-write connection, the name of the target warehouse—that
is, the warehouse into which the data is to be output. You can select this from a list of all
open read-write connections.
8-10
Using the Advanced Tab

The Advanced tab contains parameters in the Output settings grid as described in this
section. Rows are automatically added to this grid as features are selected in the feature
treeview on the General tab, and the rows are populated in the order: categories, queries,
reference features, and connections.
The read-only Source column is populated with the folder/path of the features selected in
the treeview. The read-only Features to Output is populated with the names of the
features selected in the treeview.
The Target Feature Class column lets you select a target feature class name. Each cell in
this column has a drop-down list to populate feature class names from the target
connection. You can select a feature class from the list, edit an exiting feature class name,
or type a new feature class name. The default name is the same name given for the source
features. If you choose a new target feature class name, new values are generated as
needed for all subsequent columns in the grid. In the case of a query, any embedded
spaces are replaced with an underscore (_).
You can output more than one source feature class to the same target feature class, even if
the target feature class does not exist. One feature class is processed with output mode set
to New, while all others are processed with output mode set to Append. If there are two or
more features with the same name and, if a feature class with that name does not exist in
the target connection, the output mode for the first selected feature class would be New.
The target feature class for the rest of the features is same as the first selected feature class
with Append as the output mode. If the output of the first selected feature class with the
output mode as New fails, all subsequent output operations to the same feature class with
Append as the output mode also fail. If there are two or more features in the column with
the same name and, if a feature class with that name exists in the target connection, the
output mode of all such features is Append.
If the target feature class name you supply or the default value does not conflict with a
name already in the target connection, the command populates the default values in
subsequent columns as is the following table. If multiple features are being output to the
8-11
same target feature class that does not exist in the target warehouse, the command
populates the default values for the first selected feature class as follows.
Column Name Default value
Output Mode New
Key Mode Preserve Key if the source has a displayable primary key, otherwise New
Key
AutoNumber Preserve Definition and Values (PD&V) if the target warehouse
Mode supports this capability, for example, OOM.
Preserve Values if target warehouse does not support PD&V, and the key
mode is New Key.
Preserve Definition if target warehouse does not support PD&V, and the
key mode is Preserve Key.
Target Coord For vector geometry, the default coordinate system of the target
System warehouse is populated.
For raster geometry, the source coordinate system is populated.
For nongraphic feature classes, this cell is empty.
For no default coordinate system in the target warehouse, the fall-back
logic (using MetadataService) is used to get the first coordinate system
from the GcoordSystem table.
For an empty target warehouse, the source coordinate system is assigned
to the target feature class. This similar to the raster case mentioned.
For an invalid or missing source coordinate system, no coordinate system
is populated.
If the target feature class name you supply or the default value conflicts with a name
already in the target connection, the command populates the default values in subsequent
columns as in the following table. If multiple features are being output to the same target
feature class that does not exist in the target warehouse, the command populates the default
values for all the features other than the first selected feature as follows.
Column Name Default value
Output Mode Append
Key Mode N/A (blank)
AutoNumber N/A (blank)
Target Coord Primary geometry's coordinate system of the target feature class of the
System target warehouse, if the target feature class exists in target warehouse. If
not, this is same as the target coordinate system of the first such target
feature class that has its output mode as New. For non-geometry feature
classes, this cell is blank.
The Output Mode column lets you set one output mode for a selected item, based on the
existence of the target feature class in the target warehouse: New, Append, Force
Append, Append and Update, and Update. The default is Append if the target feature
class exists, New if not. These modes are available on the right mouse menu after selecting
this column.
8-12
• New—New data.
• Append (default)—Appends new records by doing a primary key comparison. New
key values are added; existing key values are skipped.
• Force Append—Appends all records and re-sequences the primary key.
• Append and Update—Appends new records and updates existing records based on
primary key value.
• Update—Only updates existing records by comparing primary key values.
The Key Mode column lets you set one of the following key modes (only if the target
feature class does not exist in the target warehouse, that is, if the output mode is New).
• New Key—Creates a new primary key column.
• Preserve Key—Uses existing key column.
The default is New Key in the case of source data that has no key field(s) or hidden key
field(s), and Preserve Key in all other cases. These modes are available on the right
mouse menu after you select this column.
The AutoNumber column lets you set one of the following autonumber modes (only if the
target feature class does not exist in the target warehouse, that is, if the output mode is
New):
• Preserve Definition—Preserves the primary key column definition but not the data.
• Preserve Values— Preserves the existing data in the primary key column.
• Preserve Definition and Value (default)— Preserves key definition and data values.
These modes are available on the right mouse menu after you select this column.
The read-only Target Coord System column is populated with the coordinate system
name of the primary geometry field of the selected target feature class. If the name of the
coordinate system is blank, a temporary name is supplied. This cell is blank if the selected
target feature class is a nongraphic type or it has no coordinate system. If the selected
target feature class is a new feature class, the default coordinate system of the target
connection is populated for a vector type; otherwise, for a raster type the coordinate system
of the source feature class is populated by default.
Below the Output settings grid, you have the following additional options:
• Select Source Attributes—Opens the Attributes of <feature name> dialog box that
lets you select a subset of fields. You can use this option if only one record is selected
in the grid.
• Target Coordinate System—Opens a dialog box of the same name that lets you
perform the following:
8-13
− Review a coordinate system of a source feature class as well as the target

warehouse coordinate systems.
− Set a coordinate system for one or more new target feature classes at a time.
− Assign a new coordinate system to one or more new target feature classes at a
time.
− Set the source coordinate systems to the target feature classes for multiple selected
rows at a time, which are being output in New output mode.
You can use this option only if at least one record is selected in the grid.
• Display target feature classes in map window—Lets you display (the default) the
selected target feature classes in the active map window and add a new legend entry for
each selected feature class.
While processing, the application status bar displays the output feature class/query,
target feature class, progress, and number of features output.
Running Output To Feature Classes creates the log file gmotts.log in your \Warehouses
folder, if the file does not already exist, and appends log information to the contents of an
existing log file. The command always deletes the existing log file and creates a new one
for each run of the command.
To perform an output operation:

1. Select Warehouse > Output to Feature Classes.
2. On the General tab, select the appropriate items from the Source features to output
treeview.
8-14
Note: When you hover the mouse cursor over an entry in the treeview, a tooltip is
displayed indicating the geometry type.
3. Select the appropriate target connection from the Target connection drop-down list.
4. Select the Advanced tab; then for a selected source feature, select the appropriate
name from the corresponding Target Feature Class cell drop-down list, edit an
existing name, or type a new name.
5. If appropriate, change the Output Mode, Key Mode, and AutoNumber values.
Note: You can select these modes from the right mouse menu after you select a
column cell. You can also set a mode to all rows in bulk.
6. Optional: Click Select Source Attributes to select a subset of fields if only one record
is selected in the grid.
8-15
See the GeoMedia Help for information on using this dialog box.
7. Optional: Click Target Coordinate System to review, define, or assign a coordinate
system. Continue with Steps 8 through 9.
See the “Target Coord System” and the “Select Coordinate System” topics in the
GeoMedia Help for information on using these dialog boxes.
8. Select the appropriate name from the Coordinate systems list.
9. Click New to define a new coordinate system on the Define Coordinate System File
dialog box.
OR
Click Review to review the selected coordinate system.
OR
Click Assign to assign the selected coordinate system to the selected target feature
class(es) being output in New mode.
8-16
10. Optional: Check the Display target feature classes in map window check box to add
a new legend entry to the active map window for each selected feature class.
11. Click Apply.
The dialog box is dismissed, and a confirmation message box is displayed with the
following information:
The output process will result in:
<n> feature classes – New mode
<n> feature classes – Append mode
<n> feature classes – Force Append mode
<n> feature classes – Update mode
<n> feature classes – Append and Update mode
Do you want to continue?
12. Click Yes to output the data from the source connection/query to the target warehouse
The status information and progress during processing are displayed in the status bar,
and the log file gmotts.log is created. Optionally, new legend entries are added to the
active map window.
Selecting Features in the Map Window

You select features with a left mouse click or by drawing a fence on the map when the
Select Tool is active. The Select Tool is located on the Selection toolbar and is the default
active mode. When Select mode is active, the Select Tool button is depressed, and the tip
of the cursor has a circle around it called the locate zone.
The locate zone determines how close to a feature you must be to highlight it or to select it.
The size of the locate zone is set using the Size of cursor locate zone slider on the
SmartLocate tab of the Options dialog box (Tools > Options).
8-17
The size or tolerance is measured in screen pixels. You drag the slider to the right to
increase the size and to the left to decrease it. A preview of the locate zone is displayed
next to the slider.
The Selection toolbar supports Inside Fence, Overlap Fence, Rectangular Fence, and
Polygonal Fence selection modes, which are described later in this section.
A feature can be located (identified) only if it is displayed in the active map window and its
Locatable property is turned on. A feature within the locate zone of the cursor is not
located or highlighted until the cursor has been paused over the feature for a short time, but
you do not have to pause the cursor to select the feature. The duration of the pause interval
is set using the Delay before cursor highlights features slider on the SmartLocate tab.
When you select one or more features, they become a select set. A select set can contain
features from one or more sources. You create a select set to edit it. When the select set
contains more than one object, any Edit tool you select affects all objects in the select set
simultaneously.
A select set can also contain both read-write and read-only features. Objects in the select set
are distinguished as read-write or read-only by the display of handles in the map window
when an edit tool is selected. For example, if you select the Move tool when a select set is
active, handles appear on read-write objects but not on the read-only objects in the select
set.
8-18
Note: You change the highlight, select, and handles colors on the Map Display tab of the
Options dialog box.
You can have only one select set active in a GeoWorkspace at a time. The same select set
is visible in all displayed windows, both map windows and data windows.
You can also select a feature by selecting its row in the data window by clicking on the
row selector or using the CTRL or SHIFT keys to select multiple features.
See “Changing the Locatability of Map Objects” in the “Working with Map Windows”
chapter.
To select a single feature:

You select a single feature with a left mouse click when the Select Tool is active. The
feature is highlighted as long as any part of it is within the locate zone of the Select Tool.
The feature changes to the select color when you click it.
To add features to a select set:

Hold down the CTRL or SHIFT key while left clicking the highlighted feature. This also
works for data window record selects.
To select a hidden or overlapped feature:

When multiple features are under the cursor, the Always display Pick Quick dialog on
locate check box on the SmartLocate tab lets you control the Select Tool behavior.
When this check box is checked, the PickQuick dialog box is displayed whenever you do
a left mouse click and there is more than one object inside the locate tolerance. If there is
only one object inside the locate tolerance, the object is selected without the PickQuick
dialog box displaying.
When this check box is not checked, there are multiple features within the locate zone and
you pause the cursor over them, an ellipsis (three dots) appears at the lower-right edge of
the Select Tool. If you left click when the ellipsis is displayed, the PickQuick dialog box
appears.
You use PickQuick to select features that overlap each other or features that are hidden by
other features. A numbered button is displayed for each selectable feature. If there are
more than six features, the dialog box displays scroll buttons. Move the Select Tool over
the buttons without clicking to highlight the corresponding features. When the feature you
want to select is highlighted, click the corresponding button on the PickQuick dialog box.
8-19
PickQuick supports keyboard navigation. You can use the arrow keys to navigate among
the items, and the space bar to select\unselect items. You use the CTRL and SHIFT keys
in the conventional way to select and unselect groups of items in multi-select mode.
When you move the cursor over a numbered button representing a feature in the map view,
a tooltip appears showing the name of the feature class or query of the highlighted item. If
the Add connection prefix to feature names check box is selected on the General tab of
the Options dialog box, the feature class name is prefixed with the connection name. If a
map window tooltip has been defined for the legend entry associated with the highlighted
item, the text for the map window tooltip is displayed.
For more information on map window tooltips, see “Defining Map Window ToolTips” in
the “Working with Map Windows” chapter.
To select multiple features:

There are several ways to place multiple features in a select set. When the Select Tool is
active, you can:
• Hold down the CTRL or SHIFT key while left clicking the highlighted features.
• Draw a fence with the Select Tool that encompasses the area containing the features
you want in the select set.
The features included in the select set are determined by which Selection toolbar
button (fence modes) is depressed.
− Inside Fence selects all features that fall completely within the fence.
− Overlap Fence selects all features that fall inside and are overlapped by the fence.
– Rectangular Fence (the default) selects all features that fall completely inside the
rectangular fence.
– Polygonal Fence selects all features that fall completely inside the polygonal
fence.
To select all features for a legend entry:

Highlight the associated entries on the legend and select Edit > Select by Legend Entry.
8-20
This selects all map objects in the map window associated with highlighted legend entries,
regardless of whether objects are fitted in the map window. Legend entries must have the
display turned on and must be in the current view scale, but map objects do not need to be
locatable.
To select all features for a data window:

Click on the table selection button in the upper-left corner of the data window grid, or
select Edit > Select All Rows. This selects all features in the data window, whether they
are visible in the data window or not.
To clear a select set:

You can clear a select set in the following two ways:
• Select Edit > Unselect All.
• Left click an empty space on the map window.
To remove features from a select set:

You can remove a feature from a select set in the following two ways:
• Hold down CTRL or SHIFT while left clicking the feature you want to remove from
the select set.
• Hold CTRL or SHIFT while clicking and dragging to place a fence around the features
you want to remove from the select set.
Note: You must hold down CTRL or SHIFT, or the select set will be replaced.
Defining Queries from Select Sets

Select Set to Query lets you build a query from the contents of a select set that belongs to
a single feature or from a query participating in the select set. You cannot, however, use
heterogeneous select sets, that is, those with mixtures of different feature classes and
queries.
This command does not process features without primary keys. Due to an internal system
limitation, query objects in the select set are not processed directly. Instead, the original
feature class upon which the query is based is used. For this reason, only the fields from
the original feature class appear in the output query; any fields that were added by the
query in the select set do not appear in the output query, nor are any other changes in
8-21
schema apparent. Queries resulting from other GeoMedia analysis commands that
combine disparate feature classes (for example, Join and Spatial Difference) cannot be
processed. Only those feature classes in the select set that are valid for processing by the
command appear in the drop-down list.
The resulting query is a snapshot of the select set at the time you run the command. Any
subsequent changes made in the select set do not affect any queries previously created from
the select set.
Select Set to Query appends the query to the query folder and optionally outputs the
resultant query to a data window and/or map window. You can adjust the display style for
optimum viewing in the map window.
To define query from a select set:

1. Create a select set.
2. Select Analysis > Select Set to Query.
3. From the Select features from drop-down list, select a feature class or query within
the select set to be converted to a query.
Note: The Add connection prefix to feature names check box setting on the
General tab of the Options dialog box is honored. Also, the complete connection
name and feature class name appear as a tooltip when you hover the mouse cursor
over the list box.
4. Optional: Change the default name and/or type a description of the query.
5. Verify that the Display query in map window box is checked, and change in the Map
window name field, if appropriate, the map window in which to display the query
results.
OR
To not display the query results in a map window, click the Display query in map
window box to remove the checkmark.
8-22
7. Verify that the Display query in data window check box is selected, and change in
the Data window name field, if appropriate, the data window in which to display the
query results.
OR
To not display the nongraphic attributes of the query results in a data window, select
the Display query in data window check box to remove the checkmark.
8. Click OK to generate and to display the query results in the specified data window
and/or map window.
Note: If you do not select either a map window or a data window, the query is only
appended to the query folder.
See the “Analyzing GeoMedia Data” chapter for information on queries.
Inserting Features into a Feature Class

If a feature class exists in an open read-write warehouse, you can create new features
belonging to that feature class and place them on the map. You can insert a feature into a
feature class in two ways:
• From the map window, you place the geometry and type the attributes in the dialog
box that appears.
• From the data window, you supply attribute data and then place the geometry in the
map window.
If the feature class of the feature being placed is not on the legend or if the feature class
display is turned off, the feature is not displayed after it is placed.
You select the appropriate warehouse, feature class, and, if the feature is compound, the
geometry type from the Insert Feature dockable control, which is displayed when you
select Insert > Feature.
To insert a feature into a map window:

1. Select Insert > Feature.
8-23
Note: Pressing ESC does not cancel Insert Feature; you must select another
command, such as the Select Tool, to cancel the command.
2. Click the drop-down arrow on the Insert Feature dockable control to display the list
of feature classes in the read-write warehouses to which you are connected.
3. Click the feature class that will contain the new feature.
4. Place the geometry of the new feature in the map window.
Note: If the selected feature class has compound geometry, the buttons on the right of
the Insert Feature control enable to let you select the type of geometry to place.
Toggle between the feature’s Properties dialog box and the geometry-type buttons as
you place geometry.
5. In the feature’s Properties dialog box, type attribute values in the appropriate fields.
8-24
Note: When performing inserts into an Oracle Object Model warehouse, any default
values that you have will not appear on the Properties dialog box until after you have
inserted the feature.
6. Click OK.
7. Repeat Steps 4 - 6 to insert additional features.
8. To exit Insert Feature mode, press ESC in the Select Tool.
Note: If you dismiss the control by clicking the X on the title bar, the control
disappears, but Insert Feature mode remains active.
See “Adding Geometry” in this chapter
To insert a feature into a data window:

1. Select Window > New Data Window.
2. On the New Data Window dialog box, navigate to the appropriate connection, and
double click the feature class to which you want to add the feature.
3. In the row at the bottom of the table, type the values for each attribute of the new
feature.
New features are inserted with null geometry until you place geometry.
4. After you enter attribute values for the new feature, click the row selector of the new
feature.
5. Activate the map window by clicking the title bar. Clicking in the map window
instead of on the title bar clears the select set.
6. Select Edit > Continue Geometry, and place the new geometry in the map window.
See “Adding Geometry” in this chapter.
Inserting Text Features into a Feature Class

You can insert text features into a feature class and place them on the map interactively
with the Insert Text command. Text placement is dynamic, so that you can see characters
appear next to your cursor as you type. If you change the alignment set for the text after
typing your text, you can also see the position of the text change next to your cursor.
If you want to place multiple copies of the same text, you can do that with additional
mouse clicks. Insert Text is an interactive mode, and you have to press ESC or click the
Select Tool to return to select mode.
Starting Insert Text displays the following dockable control:
8-25
In addition to basic text insertion, Insert Text provides the following functionality:
• Applying instance-based symbology for text features—By default, placed text relies
on the Select Style parameters defined in the legend when displaying the text in the
map window. You may override these parameters on individual text instances
(instance-based symbology) by checking the Override style check box and defining
the appropriate text symbology. When the Override style check box is checked, the
entire text string will display using the defined format (bold, italic, or underline), color,
size, and font. To change instance-based text symbology, you need to use the Edit
Text command.
• Placing incremental numeric text—Type a numeric (integer or real) value into the
text-entry field, and then set the increment value to an integer or real number.
• Placing text at a user-defined rotation angle—Set the rotation mode to Place at
angle, set the appropriate angle for placing the text, and then click to place the text.
The controls on the dockable control remain as set.
• Placing text to rotate dynamically—Set the rotation mode to Rotate dynamically,
click for the location of the text origin, and then click for rotation.
• Placing text along an arc—Set the rotation mode to Place along arc, optionally
modifying the inter-character spacing, and then digitize three points to define the
curvature of the arc, in the order 1-2-3. Upon defining the third data point, the text
will be floating and oriented along the curvature of the arc defined. Click a fourth
point to place the text. Type additional text to continue the process, select another
command, or press ESC. Using this mode generates a composite text collection, which
lets other parts of GeoMedia recognize the resulting multi-part text as a single
composite string rather than individual characters.
• Placing along existing geometry—Set the rotation mode to Place along existing
geometry, type a single-line text, and then select a linear, area. or compound
geometry. This displays the text in dynamics, undulating along the curvature of the
selected geometry starting from the mouse cursor. You can control the distance of the
text from the geometry and the spacing of the characters, and influence the smoothness
of the flow of the text. Move the cursor above or below the geometry to get the
appropriate offset distance from the geometry, increasing the inter-character spacing by
using the mouse wheel or clicking the up arrow key. Tune the resulting text pattern by
changing the vertical offset or by using the down arrow key. Click on the map window
or type the location coordinates to place the text.
8-26
• Optionally modifying the inter-character spacing—Use character spacing

modifications to expand or to retract the text string, except when placing multi-line
text. If character spacing is adjusted with the Place at angle or Rotate dynamically
mode, a composite text collection is placed as with arcs. Otherwise, a simple multi-
character string is placed. You can use the mouse wheel and the + and - keys to
increase or to decrease the character spacing after the second click point and before the
fourth click point.
To insert text:
1. Select Insert > Text to display the Insert Text dockable control.
2. Click the drop-down arrow to display the list of text feature classes, queries, reference
features, and categories in the read-write warehouses to which you are connected. If
none of the open read-write warehouses contains a text feature class, create one
through Warehouse > Feature Class Definition.
3. Click the feature class you want to contain the text.
4. Optional: Check the Override Style check box; then define the appropriate text
symbology.
5. Select the text alignment you want from the drop-down list.
6. Type the text you want to place in the text-entry field. To create a new line in the text,
press CTRL+ENTER (except for curved text).
As you type, the text appears in the text field and in dynamics next to the cursor in the
map window.
7. Select the text placement rotation mode.
8. Position the text where you want it on the map; then click the left mouse button.
9. To place additional instances of the same text, repeat Step 8.
10. To place additional but different text, repeat Steps 7 - 9.
11. To exit Insert Text mode, press ESC or click the Select Tool.
Note: If you dismiss the control by clicking the X on the title bar, the control disappears,
but Insert Text mode remains active.
Editing Text
Edit Text lets you to interactively edit one or more instances of read-write text, and the
corresponding alignment and symbology, generated by the Insert Label command or
Insert Text command. You can select the text from a map window or a data window;
however, if from a data window, you must activate a map window to enable this command.
8-27
Also, if you select a mixture of read-only and read-write text, you can only edit the read-
write text.
This command lets you place the text with instance-based text symbology through the
Override style check box. When you select this option, the entire text string in the Edit
Text dialog box is placed with instance-based text symbology, and the active symbology
settings for text format (bold, italic, or underline), color, size, and font override the legend
display parameters set on the Select Style dialog box for the selected feature class.
Multiple Text Instances

When you select multiple instances of text, the Text and Alignment fields on the dialog
box are only populated if these properties are common across the selected labels.
For example, consider selecting two instances of the Tennessee River, each with an
alignment of Center center. When you start this command, the dialog box displays
Tennessee River and Center center as the text and alignment, respectively. However,
selecting an instance of Tennessee River and Flint River (assuming the same feature class),
each having different alignments, yields a dialog box displaying nothing for the Text or
Alignment fields. In the hybrid case where each river shared a common text or alignment,
the respective control would show the common value and not the other.
If you select multiple instances of text, and one or more instances are not instance-based
text symbology, the Override style check box is unchecked, and all of the options are
disabled.
If you select multiple instances of text that are instance-based text symbology, the
Override style check box is checked, and all of the options are enabled. If the font size
and font definitions are different for the items selected, these two fields are blank.
Furthermore, in the case of multiple instances, if you do not specifically change the text
and/or alignment settings, on clicking OK, these settings are left unchanged. Thus, in
certain cases of multiple selections, OK and Cancel can perform the same action.
However, once you make a specific selection for either text, alignment, or style override
options, OK updates all valid selections with the change(s).
Composite Text Collections

Edit Text lets you edit composite text collections as a single text string. The composite
text collection can consist of text placed along an arc, where each character is a component
of the collection, and text labeling multiple geometry in a collection such as the islands of
Hawaii, where each island name is a text component. This command presents such a
collection as single text string for you to edit and, to the extent possible, preserves the
original location information for each text point geometry. You cannot, however, edit
multi-line text. This command lets you change a particular aspect of a style of multiple
features even when Override style is turned on. For example, if you need to change just
the color of all selected text features without changing any other style parameters.
8-28
Portions of Text Style

When editing multiple text features, you can change individual text characteristics (text
string, alignment, style properties) rather than overwriting all characteristics for all selected
features. When the selected text features have differing values for text characteristics, that
is, if the select set contains at least one composite text collection indicating that it is not
possible to type a multi-line text, each control on the dialog box presents itself in a neutral
state to indicate that no change is applied.
Checking the Override style check box while in the neutral state changes the state to
checked. Clicking Bold, Italic, and/or Underline while in neutral state changes them to
the pressed state. However, once you change the state of a control from neutral, it
continues to maintain one of its two states only (that is, either checked/unchecked or
pressed/unpressed).
The dialog box appears as on the left if the select set does not contain any composite text
collections, indicating you can type multi-line text. It appears as on the right with the Size
and Font fields in neutral state if the select set contains at least one composite text
collection, indicating you cannot type a multi-line text.
To edit a text feature:
Note: The following behavior also applies to one or more instances of text selected from a
text collection. Basically, the Edit Text dialog only displays attributes if they are
common. Any edits are written to all of the items in the collection
1. Select the text feature class instance(s) in the map window.

2. Select Edit > Edit Text.
8-29
3. In the Text field, type the replacement text. If you are editing multiple text instances,
all instances are modified to reflect the new text.
4. Accept or select a different alignment from the Alignment drop-down list. If you are
editing multiple text instances, all instances are set to the new alignment.
5. Accept or change the Override style check box setting. If you are editing multiple text
instances, all instances will be modified to reflect the new text.
6. Accept the text symbology, or change it through the format (bold, italic, or underline),
color, size, and font controls.
7. Click OK.
Selecting and Searching for Text

Select Text lets you define the criteria to search for graphic text features, performing the
search as you can for text in a Microsoft Word file, according to any combination of their
text string and various style properties, and then select text features. Thus, you can
quickly find and update text to adjust to changing map specifications or to create new map
products.
This command uses a combination of both text string and style characteristics on all the
displayed graphic text legend entries within the legend of the active map window. In
addition, when you specify a text string as selection criteria, you can use wild cards and
perform sub-string selection. If you do not use a text string, the search is based on style
alone; if you do not specify style characteristics, the search is based on the text string
alone. In the search, this command finds those text feature instances displayed in the map
window that match the specified search criteria. The search results are output to a new
select set, whose rich text format parameters (color, font, size, and so forth) you can edit.
You can then immediately use this select set as input to other commands such as Edit Text
or Delete.
For those features with override style, selection is performed using the rich text format
information available in them. In the case of plain text, the default style property
information of the corresponding legend entry is used. For those features with override
style, the command assumes that the rich text style information is constant for the whole
text and always uses the rich text style of the first character. When an input geometry
8-30
contains a standard text collection, the geometry is selected if at least one of the items in
the collection matches the selection criteria.
Selecting Edit > Text > Select Text displays the Select Text dialog box for you to define
the appropriate search criteria. When you first start this command, all the dialog box
controls are in the neutral state as in the example on the left. To return to this neutral state
after setting any search parameters, as in the example on the right, you must exit and restart
the command.
You can type or select the text string you want to search for in the Text field. Note that the
search is not based on a case-sensitive text string. Checking the Match entire text check
box selects those graphic text features with their text having an exact match with the string
value entered in the Text field.
Checking the Use wildcards check box lets you use any of the listed special characters
entered in the Text field as wildcards and perform pattern matching using both regular
characters and wildcard characters as specified in the Text field. Regular characters must
exactly match the characters specified in the character string. Wildcard characters,
however, can be matched with arbitrary fragments of the character string based on the
wildcard character used. This command supports the following GeoMedia-recognized
wildcards only:
• % Any string of zero or more • _ (underscore) Any single character
characters
• [] Any single character within • [^] Any single character not within the
the specified range ([a-f]) specified range ([^a-f]) or set
or set ([abcdef]) ([^abcdef])
When the Use wild cards check box is checked, the Match entire text checkbox is
disabled automatically and cannot be checked.
You can also set the appropriate text Style characteristics, using any combination of bold,
italic, and underline, as well as font color, size, and name to define the selection criteria.
Adding Hypertext to a Feature Class

Hypertext is a link to an external file. Inserting hypertext into a feature table is essentially
attaching an external file or Web location to a feature in the read-write warehouse. Once
8-31
hypertext has been inserted into a table, you can invoke the external application associated
with the file and activate the file by clicking the hypertext cell in the data window.
If the feature table does not already have a hypertext attribute defined, you must define one
in the warehouse before inserting hypertext. Once you have a hypertext column in a table,
you can add hypertext links to as many features as the table contains.
To define a hypertext attribute in a read-write warehouse:

2. On the Feature Class Definition dialog box, navigate to the warehouse connection
that contains the feature class in which you plan to insert the hypertext, and select the
feature class.
3. Click Edit.
4. On the Attributes tab of the Edit - <FeatureClass> dialog box, click the bottom row
selector that contains an asterisk.
8-32
5. Click somewhere in the Name field, and replace the automatically generated attribute
name by typing a meaningful name, such as HYPERTEXT.
6. Click the Hypertext check box.
7. Click OK.
8. Close the Feature Class Definition dialog box.
To insert hypertext into the data window:

1. In the data window, select the empty cell in the hypertext column of the feature you
want linked to an external application.
2. Select Insert > Hypertext.
3. From the Insert Hypertext dialog box, navigate to the appropriate folder, and select the
file or Web location that you want to attach to the feature.
4. Click Open.
To insert or edit hypertext from the map window:

1. Select the feature in the map window.
2. Double click the selected feature, or select Edit > Select Set Properties.
3. On the Attributes tab of the feature’s Properties dialog box, click the hypertext cell in
the Value column, and type the path and name of the file or Web location. To edit,
highlight the file name or Web location, and type the new file name or Web location.
Note: You must highlight the text to edit it. If you just click on the text, the
hypertext link is invoked.
8-33
4. Click OK.
See “Attributes Tab” later in this chapter.
To designate a column in the database as a hypertext link in MGE or MGSM:

In MGE and MGSM, you must identify both the table and column names in the .ini file for
the MGE or MGSM data server using the HYPERTEXT: keyword. You can identify
several columns without repeating the keyword, but each table-column pair must appear on
a separate line.
For example, the Birds table contains a hypertext column linking a record to a photograph
of the species, one that references an audio clip of the bird's call, and one that identifies a
video clip of the bird in flight:
HYPERTEXT:Birds,Photo
Birds,Audio
Birds,Video
The MGE or MGSM data server looks for hypertext files in the multimedia folder of the
project unless the HYPERTEXT PATH: keyword appears in the .ini file. Use this
keyword to identify one or more folders in which to search for multimedia files.
If more than one folder is specified, the folders are searched in the order specified. You
may use either a comma (,) or a semicolon (;) to separate the path components. Path
components may contain UNC-style folder names:
HYPERTEXT PATH:C:\Images,D:\AudioClips,
\\BIGSERVER\VIDSHARE\Birds\Video
Adding Geometry
You can add geometry to an existing feature that does not have geometry, add holes to
existing geometry, and add geometry to existing geometry.
Here are some tips for placing geometry:
• Follow prompts in the status bar when placing geometry.
• Use the map view tools for more accurate placement.
• To place discontiguous geometry, press and hold the CTRL key while you place
geometry. When you have placed all segments of the feature, double click the left
mouse button.
• If you are placing a linear or area feature, press the back arrow key to delete the last
vertex.
• When you place linear or area features, double click to indicate you have placed the
last point.
8-34
Note: These tips also apply to inserting features.
For point and area geometry, the Continue Geometry tool adds only discontiguous
geometry. For line geometry, if the first or last point of the new geometry is within the
locate zone of an end point of the feature, the Continue Geometry tool adds contiguous
geometry; otherwise, it adds discontiguous geometry.
When the cursor is within the locate zone of any locatable map object, the pointer changes
to indicate when you can snap to an end point, snap to a line, or snap to a vertex, as
follows:
To add geometry to a feature, select the feature, select Edit > Continue Geometry, and
place the new geometry in the map window.
Note: If you select a feature from the data window that is not on the legend in the map
window, the geometry of the feature appears for the duration of the process. Once the
process is completed, the geometry disappears from the map view, although it is not
deleted. To display the geometry, add the feature class to the legend.
Changing Attribute Values of Features

You can change the attribute values of features either in a map window or in a data
window.
In a data window, you use standard Windows editing tools and the Clipboard to cut, copy,
and paste text in cells. You cannot, however, edit hidden cells or cells containing
hypertext.
In the map window, you use the Attributes tab of the Properties dialog box, displayed by
selecting Edit > Select Set Properties.
Attributes Tab
The Attributes tab lets you review and edit the attribute values of features. On this tab, all
required fields are indicated by the value in the Name column appearing in bold, red type.
All key fields are likewise indicated by the value in the Name column appearing in bold,
red type (because key fields are also required fields) and by the value’s being underlined.
8-35
Tooltips
When you hover the cursor over a cell in the Name column, a tooltip displays the attribute
description defined through the Feature Class Definition command. If no attribute
description was defined, no tooltip appears.
When you hover the cursor over a cell in the Value column, a tooltip displays the data type
and the default value of the column. If there is no default value, the tooltip displays only
the appropriate data type string from the table. If there is a default value, the data type
string is followed by the string “ : Default = “ and then by the actual default value string
supplied by the data server.
If the default value string is a literal value of the correct data type for the attribute, it is
formatted according to the display rules for the field (honoring the format and precision
properties, regional settings as appropriate, custom Boolean wording, and so forth), as seen
in the following example:
Text (20) : Default = Alabama
Memo : Default = This is a default value for a memo field.
Integer : Default = 5
Double : Default = 123.456,789
Currency : Default = $ 1,200.50
Boolean : Default = Yes
Date : Default = 01-May-2000
If the default value string is not a literal value of the correct data type for the attribute, it is
displayed in its native form as provided by the data server. This may occur when, for
example, the default value is an autonumber or is to be calculated through a database
procedure, as in the following example:
Integer : Default = AutoNumber
Date : Default = TRUNC(SYSDATE)
To use the Properties dialog box:

1. Select one or more features as a select set.
2. Select Edit > Select Set Properties.
3. Optional: Resize the dialog as desired through standard Windows resize operations.
4. Position the pointer over the appropriate item for your task to display the tooltip.
8-36
In this example, ID is a required field. The cursor is hovering over the word Alabama
in the Value column, thus the tooltip shows the data type of the field, the size (because
it is a text field), and the default value.
To change attribute values of features in a map window or data window:

1. In the map window, select a single feature you want to change.
OR
In the data window, select the row of the feature you want to change.
2. Select Edit > Select Set Properties.
3. On the Attributes tab of the feature’s Properties dialog box, edit the attribute values
and click OK.
Note: You could also double click the select set, which amounts to triple clicking a
feature, or right click a select set and select Properties from the right mouse menu.
8-37
4. Optional: Resize the dialog box to more easily view and change data in the Value
column of both tabs.
5. On the Attributes tab of the Properties dialog box, click the cell in the Value column
that you want to edit.
The arrow on the row selector moves to the row you clicked.
6. Type the new value in the cell.
If the warehouse is read-write, a pencil appears on the row selector when you begin to
type.
7. Click OK.
If the map window display check box was selected, the map window with the
geometries is displayed. If the data window display check box was selected, the data
window with the geometries is displayed.
See “Editing Cells in the Data Window” in the "Working with Data Windows" chapter.
Changing and Deleting Features

You can change the location of a feature, and you can change the orientation of text and
points by creating a select set in a map window or a data window and then activating the
appropriate tool.
• You can move one or more features together. Selected features can belong to different
feature classes. By selecting a geometry in the map window, you move only the
selected feature. By selecting the row for the feature in the data window, you move all
of the feature’s geometry and associated text as one.
• You can rotate one or more text and/or point features that are represented by symbols.
By selecting a geometry in the map window, you rotate only the selected geometry.
By selecting the row for the feature in the data window, you rotate all points and text
for that row as one.
8-38
To move features in a map window:

1. In a map window, create a select set containing the feature(s) you want to move.
2. Select Edit > Move.
Handles appear on the select set to indicate that it can be moved.
3. Click a select-set handle to attach it to the cursor, or click in the map window and drag
the select set to the new location.
To move features in a data window:

1. In a data window, click the row selector of the feature you want to move. Press and
hold the CTRL key while selecting multiple features.
2. Activate the map window by clicking the title bar.
3. Select Edit > Move.
Handles are displayed on all geometry and text associated with the selected rows to
indicate that they can be moved.
4. Click a select-set handle to attach it to the cursor, or click in the map window and drag
the select set to the new location.
To spin a point symbol or text:

1. In a map window, select the point symbols or text you want to spin; or select the row
for the point symbols or text in the data window, and activate the map window by
clicking the title bar.
2. Select Edit > Spin.
An origin handle appears in the map window for each selected point symbol or text.
3. Click the origin handle.
A baseline (dashed line) and reference line (solid) appear from the origin handle.
4. Move the cursor, using as a guide the dynamic spin of the reference line in the active
map window.
Moving the cursor in a clockwise direction counts degrees backwards (0, 360, 359, . . .
). Moving the cursor in a counterclockwise direction counts degrees forward (0, 1, 2,
3, . . . ).
8-39
When you click, the first reading before the cursor is moved shows the beginning
active angle. As you move the cursor in either direction, the active angle changes and
the readout in the status bar updates dynamically.
5. Click to accept the angle.
To insert, move, and delete vertices of feature geometry:

1. In a map window, create a select set containing the feature you want. Or, in a data
window, select the row for the feature and then activate the map window by clicking
the title bar.
2. Select Edit > Edit Geometry.
3. Activate the map window by clicking the title bar.
4. Handles appear on all geometries of the selected feature to indicate that the geometries
can be edited.
Note: You can use the CTRL or SHIFT key to select multiple handles (vertices).
5. To insert a vertex, select the point of the geometry where you want to insert the vertex.
6. To move a vertex, press and hold the left mouse button on the vertex you want to
move, drag it to the desired location, and release the mouse button.
7. To delete a vertex, select the vertex and press DELETE.
To delete geometry:
When you delete the geometry of a feature in a map window, the feature is no longer
displayed in the map window. Deleting geometry, however, does not delete the feature.
Attribute data still exists for the feature, which can be viewed in a data window.
IMPORTANT: When you select multiple rows in a data window, this procedure deletes
all the geometry and text for all selected rows, including those not displayed in the active
view.
1. In a map window, create a select set containing the feature(s) you want. Or, in a data
window, select the row(s) for the feature and then activate the map window by clicking
the title bar.
By creating a select set in the map window, you delete only the selected geometry.
2. Select Edit > Delete Geometry.
To delete a feature:
When you delete a feature, it is removed from the warehouse and from all windows.
However, the legend entry is not affected, and you must delete it separately.
8-40
IMPORTANT: This procedure deletes all selected features, including those not displayed
in the active view.
The mode in which the command is running depends on the contents of the select set. If
the select set is empty when you start the command, Delete runs in action-object mode,
which lets you delete multiple features (one after another) during a single instance of the
command. In this mode, you cannot clear the contents of the selected cells from data
window or use fence select or CTRL-Click select. If the select set contains one or more
features, or when the data window is active and there are cells selected, the command runs
in object-action mode, which lets you delete only the selected features or clear the selected
cells during the command instance.
1. In a map window, create a select set containing the feature(s) you want. Or, in a data
window, select the row(s) for the feature and then activate the map window by clicking
the title bar.
2. Select Edit > Delete.
Note: Through Tools > Options, you can specify whether the confirmation box is
displayed before processing.
All views that were displaying the deleted features are updated. If you selected
columns or cells instead of the row, the values in the cells are set to NULL.
Working with Categories

Categories lets you group feature classes and queries into categories in a structured way.
Thus, you can create your own customized logical model of your data as a complement to
the physical model represented by the warehouse-resident feature classes and the queries
built upon those feature classes. This lets you take control of what you want to see and
helps you organize your data. Once categorized, you need not bother about connections or
the source of your data. You can think of these categories as user interface shortcuts only;
they do not form actual parts of the warehouse data model.
You may want to, for example, create thematic categories to group Rail and Road features
under the category Transportation. Or you may want to create a category to just reflect the
priority or frequency of use, for example, you might want to work with only a fixed set of
feature classes and queries and not bother about others. The categories possibilities are
only limited by one’s imagination.
The Categories command provides you with great flexibility in category creation as you
group feature classes and queries. You can include a feature class or a query into more
than one category, and feature classes and queries can also appear in none of the
categories. When creating a new feature class or query, you cannot, however, assign them
8-41
to a category at that time. Categories can contain feature classes and queries from multiple
connections, including read-only connections, and the connections are hidden to simplify
category organization and presentation. No distinction is drawn between feature classes
and queries within a category. In addition, you can nest categories in folders that in turn
can have subfolders representing individual categories, and each such category subfolder
can in turn have sub-categories to continue the nesting as required for your organizational
plan. You also have flexibility in naming categories by the aliasing of feature class and
query names as well as the aliasing of attribute names. Finally, you can share your
categories within the enterprise.
Managing Categories
The Categories dialog box lets you easily manage your categories and their contents. You
can create and delete categories, add features and queries to them, edit their properties,
rename/alias categories and attributes, move and copy categories and their contents in the
treeview, and organize and expand the treeview nesting.
Central to the Categories command is the categories treeview. This treeview always
contains the root node Categories. To this you expand the treeview by adding category
folders as you create as many categories as you require. These category folders can in turn
have sub-folders that represent sub-categories, or feature classes or queries. Thus the
treeview contains three types of nodes: categories, feature classes, and queries. The items
at each level are displayed alphabetically. A category may be nested to any level. A
category node may contain its sub-category nodes or query or feature class nodes. The
query and feature class nodes themselves cannot have subfolders. If any of the source
connections of any of the categorized feature classes are closed, or if the categorized query
is closed or invalid, it is flagged with an icon indicating the feature class or query is not
accessible:
8-42
You can copy and move categories/sub-categories, feature classes, and queries to other
categories by using drag-and-drop. You cannot, however, drop feature classes and queries
on the root node Categories nor drag-and-drop this node. Drag-and-drop works similarly
to Windows Explorer’s folders treeview. While drag-and-drop is being done, if you press
Ctrl, a copy is performed; otherwise, a move operation is performed. Tooltips on the
treeview show the original feature class name (with or without the connection name, per
the Options > General tab setting Add connection prefix to feature names) or query
name.
Once defined, the category structure appears in treeviews across the product by the
commands, for example Attribute Queries and Join, and controls to support categories.
Categories are thus displayed in the treeviews along with all the connections, queries, and
reference features information, for example, in the New Data Window and Add Legend
Features dialog boxes. If, however, categories have not been defined, no empty
Categories node is displayed by other commands.
8-43
In creating categories under the Categories root node or subfolder, you use Create
Category to provide a unique name and an optional description, both of which you can
later change. You can delete a selected category, which also deletes all subfolders and
their contents by clicking Delete Category on the Categories dialog box or by pressing
the Delete key.
To add one or more sets of features (feature classes/queries) under a category, you select a
category and then use Add Features to make selections from all the features and queries in
the GeoWorkspace under the Queries node and the name of each connection in the
GeoWorkspace as a separate node at the first level, as displayed on the Add Features
dialog box. All connection nodes contain the feature classes available in that connection.
These are the physical connection, feature class, and query names, not the logical names as
categorized. You can add multiple items to a category by checking multiple item check
boxes or the Queries node and/or the connection node on the Add Features dialog box.
You can remove features or queries from a category by selecting the item then clicking
Remove Features on the Categories dialog box or by pressing the Delete key.
Once you have added feature classes and queries to a category, you can review and edit
their properties from the Categories dialog box. Selecting a feature class or query and
then clicking Attributes displays the Attributes of <feature name> dialog box, which lets
you choose, reorder, and rename attributes for the selected feature class or query.
Selecting a feature class or query in the Categories treeview and clicking Properties
displays the Properties of <feature name> dialog box, which lets you review and change
properties for both feature classes and queries. You can review the read-only original
name and description (as present in the warehouse - connection name of the feature class,
and as defined on the query, that is, the one with which the query is identified in the
Queries folder) as well as the current name and description (as categorized). You can edit
(rename) only the default/user-defined, categorized feature class and query names and
descriptions. Changing these names and descriptions does not change the original, read-
only values. You can also view the read-only feature class and query category names.
These names show the complete category hierarchy using the dot convention. For
example, a category C1.Sub_C1_1 indicates, that the feature class belongs to sub-category
Sub_C1_1 whose parent category is C1.
8-44
Feature Class Properties Query Properties

After you edit the properties, the command validates the new name for uniqueness at the
same level of hierarchy in the treeview, and the name and description of the categorized
feature class/query are updated.
To create a category and add features/queries:

1. Select Warehouse > Categories.
2. Click New Category.
3. Type the appropriate category Name.

4. Optional: Type a category Description.
5. Click OK to create the category.
8-45
Note: To create a sub-category, select the category and then repeat Steps 2 – 5.
6. Optional: To edit the name and/or add a description, select a category, click Properties,
and then click OK.
7. To add features to the category, select the category; then click Add Features.
8. Expand the appropriate feature class and/or query node(s); then check the appropriate
feature class and/or query check boxes.
8-46
9. Click OK to return to the Categories dialog box.
To edit feature class and query properties:

2. Select the appropriate feature class or query.
3. Click Properties.
4. Edit the Name and/or Description fields; then click OK.
8-47
To manage feature class and query attributes:

2. Select the appropriate feature class or query.
3. Click Attributes.
4. Check or uncheck the appropriate Attributes check box(es) for the selected feature class
or query.
Note: Graphic attributes, fields of type gdbSpatial or gdbGraphic, cannot be removed.
5. To reorder an attribute, select the attribute; then use the up/down arrows to the right of
the Attributes list.
6. To rename an attribute, select the attribute; then click Rename.
Note: Graphic attributes cannot be renamed.
7. Type the New name; then click OK.
8. Click OK on the Attributes of <feature class/query> dialog box.
8-48
Working with Catalogs
The Catalogs commands form a bridge between spatial data and the standard geospatial
catalog that describes that data. These commands support the integration of metadata
search, edit, and query functionality with other GeoMedia functions, and they also provide
complete spatial metadata functionality within GeoMedia. With these commands, you can
connect to geospatial catalogs, query for interesting catalog records (metadata items), and
open associated GDO connections (if the record is already associated to a feature class).
See “Catalog Features,” “What is Geospatial Metadata?,” and “Glossary of Catalog
Terminology” in this chapter.
In summary, the Catalogs commands let you catalog and open associated feature classes
and perform the following additional tasks in manipulating catalogs:
• Import metadata from other exchange formats.
• Associate a feature class to a metadata record.
• Update spatially related metadata elements from the associated feature class.
• Search catalogs for feature data and image files.
• Export to standard exchange formats.
• Generate catalog record reports.
9-1
The functional modules can be classified into the following three categories:
1. The first set interacts with the open catalogs and process metadata. Query/search,
import and export, and report generation are examples of this set.
2. The second set of modules has spatial data as input from warehouses and generates
metadata as output. Examples are capturing spatial attributes and creating skeleton
metadata records for selected feature classes.
3. The third set of modules has metadata records as input either directly from user-
selected metadata records, or as a result set from a query and open associated
connections in GeoMedia.
These modules, the Catalogs commands, thus form a bridge between spatial data sets and
their associated metadata sets.
The Catalogs commands are the following:
• New Catalog • Export Catalog Records
• New Catalog Connection • Associate Catalog Records
• Catalog Connections • Catalog Explorer
• Import Catalog Records
Catalog Features
Standards-compliant—GeoMedia Catalog makes it easy for anyone, regardless of prior
knowledge of the Federal Geographic Data Committee (FGDC) standard, to create,
manage, and publish FGDC-compliant metadata. Catalog also supports publication of
metadata records that conform to the ISO-19139 TS RC technical specification (May
2006).
Biological Data Profile—Create standardized metadata for your biological datasets
following the FGDC’s Biological Data Profile.
Data Layer Association—Catalog ties metadata to data by allowing you to associate a
metadata record with the GeoMedia feature class or image file that it describes.
Metadata Capture—Once you have associated a catalog record with a dataset, you can
extract metadata elements like bounding coordinates and attributes, directly from the
dataset into the metadata record.
Catalog Explorer—Bridges the gap between spatial data and metadata catalogs to provide
an unprecedented level of access to and control over your GIS data library. With the
Catalog Explorer, you can quickly locate and preview any dataset in your GIS data
library, and you can automatically load search results into a GeoMedia map window.
Browse Graphics—Include images of datasets in your Catalog reports.
9-2
Online Help with Real-world Metadata Samples—Context-sensitive online Help

provides FGDC definitions and real-world metadata samples.
Metadata Templates—Load one record with your organization's core metadata, save it,
and use it to create multiple metadata records, and thus instantly reduce data-entry time.
Import and Export—Load any metadata record that is FGDC compliant in ASCII text,
GeoMedia Catalog Exchange format(s), or XML format into GeoMedia Catalog.
Exchange your catalog records with others as ASCII text, in GeoMedia Catalog Exchange
format, or in XML (FGDC or ISO-19139) format.
Metadata publishing—Output attractive, Web-ready metadata reports to distribute or to
put on your website. Create and use your own enterprise style sheets to make published
XML files look just as you would like them to.
What Is Geospatial Metadata?

Geospatial Metadata is data that describes geospatial data. Geospatial metadata tells you
the who, what, and when of a geospatial dataset. Who created it? For what purpose?
When?
Geospatial metadata tells you what a dataset cannot show you—data quality, history, and
availability. Through metadata, you can answer the following questions to determine
whether a geospatial dataset suits your needs:
• Where did a dataset originate? • What geographic area does it cover?
• What steps were followed to create it? • How do I obtain the data?
• What attributes does it contain? • Will it cost me anything?
• How is the data projected? • Whom do I contact for more information?
Geospatial metadata has been compared to the nutrition label on a food package. Without
this label, you cannot be sure whether the food you are eating is good for you. Without
metadata, you do not know if the data you are considering using is good for your intended
use.
See the “GeoSpatial Metadata Profile: FGDC Dataset” document
(FGDCDatasetMetadataProfile.pdf in <HOME>\Program Files\GeoMedia Professional
or \GeoMedia).
Why Have Metadata?

Investing in geospatial metadata is a sound data management strategy because of the
following reasons:
• Metadata protects your investment in data and supports re-use of information already
acquired or developed within your enterprise.
9-3
• Metadata makes data sharing easier and less costly.

• Metadata helps minimize the costs incurred by data loss or by re-creating data that
already exists.
Some people see geospatial metadata as inconvenient and are reluctant to allocate time or
resources to a metadata project. No one has demonstrated to them that, when used
properly, metadata is a vital component to a successful GIS program.
• Metadata protects an organization's internal investment in data. Metadata is like a card
catalog for an organization's GIS data library. Through metadata, personnel within the
organization can see what data is available and how to obtain it. The risk of losing
data or re-creating existing data is minimized.
• Metadata promotes data sharing. Metadata helps GIS personnel share data by
providing the information that people need to locate, evaluate, and obtain data.
Without metadata, an organization often depends on employees to keep track of data
holdings. Sometimes persons store all this vital information in their, or perhaps in notes.
However, what if a person quits? Gets transferred? Falls ill?
People come and people go. With metadata, however, information vital to your GIS
program stays at your fingertips.
What Are FGDC Metadata Standards?

The FGDC is the Federal Geographic Data Committee—the U.S. federal government
committee responsible for creating and maintaining widely adopted standards for metadata.
FGDC geospatial metadata standards have been adopted by organizations that author
metadata within the U.S. and by many enterprises outside the U.S. as well.
GeoMedia Catalog commands support both the FGDC Content Standard for Digital
Geospatial Metadata, commonly called the FGDC standard, and the Biological Data
Profile of the CSDGM, which includes an extended set of specialized metadata content
elements.
The FGDC standard is like a style guide for metadata. It defines what information belongs
in a metadata record and the order in which it is presented.
The purpose of the FGDC standard is to provide a common definition for geospatial
metadata to the GIS community. Through the use of a common standard, it becomes easier
for those within and among different organizations to share data through metadata.
The FGDC standard organizes a metadata record into the following seven main sections:
1. Identification Information: Basic information about the dataset. Where did the data
originate? How current is it? For what purpose was it created? What geographic area
does it cover?
9-4
2. Data Quality Information: A data quality assessment. How accurate is the data?
What steps were followed to create the data? What sources were used to create the
data?
3. Spatial Data Organization Information: How is spatial data represented in the
dataset? What objects were used to represent space?
4. Spatial Reference Information: The description of the reference frame for, and the
means to encode, coordinates in the dataset. What are the projection parameters?
5. Entity and Attribute Information: What entity types and attributes does the data
describe?
6. Distribution Information: From whom may the data be obtained? In what media is
it available? How large is the dataset? Can it be downloaded? Does it cost anything?
7. Metadata Reference Information: Information about the metadata. When was the
metadata record created? Who is the responsible party? When was it last updated?
In addition, the FGDC standard defines three supporting sections, which are not used
alone, but rather are used within the seven main sections. The supporting sections are as
follows:
1. Citation Information: A recommended reference for the dataset.
2. Time Period Information: Information about the date and time of an event.
3. Contact Information: Information about the persons and organizations associated
with a dataset.
Each section is comprised of individual metadata elements, and of compound elements.
For example, the compound element address may include individual elements for street
address, city, state, or province.
9-5
Under the FGDC standard, there is a one-to-one relationship between a metadata record
and the GeoMedia feature class or image file that it describes. In other words, you should
have one metadata record per dataset.
What Are ISO Metadata Standards?

In 2003 the international community adopted the ISO-19115 Geospatial Metadata standard.
The objective of ISO-19115 is to provide a clear procedure for the description of digital
geographic datasets so that users can determine whether the data in a holding will be of use
to them and how to access the data. Like the FGDC metadata standard, the ISO-19115
model consists of multiple packages of geospatial metadata content elements.
ISO is also at work on ISO-19139, an XML schema for metadata implementation. ISO-
19139 is designed to provide a common specification for describing, validating, and
exchanging metadata about geographic datasets. It is intended to promote interoperability,
and to exploit ISO 19115’s advantages in a concrete implementation specification.
GeoMedia’s Catalog commands include support for exporting metadata records in an XML
format that conforms to the 19139 XSchemas TS RC (May 2006 ).
9-6
Updating Metadata Databases for GeoMedia 6.0 or

Higher
The following workflow allows users of the current software to update their databases to
the new format.
1. Open GeoMedia SMMS version 5.x before uninstalling the legacy product and before
installing GeoMedia 6.0 or a higher version.
2. Export all records to SEF format, and make a secure copy.
3. Uninstall GeoMedia SMMS version 5.x and GeoMedia version 5.x, and then install
GeoMedia 6.0 or a higher version.
4. Create one or more new catalogs.
5. Import SEF records exported from GeoMedia SMMS version 5.x.
Creating a New Catalog

New Catalog lets you create a new Access catalog compatible with Access2K using a
catalog template (.mdb). This new catalog has no catalog records when created from
delivered template. The command copies all existing records if created from a template
which has records. Creating a catalog is a two-step process. You first select and validate a
catalog template, and then you use that template to actually create the new catalog. This
command is similar to the Warehouses > New Warehouse command in GeoMedia.
See “Working with Connections” in the “Working with Warehouses” chapter.
By default, this command creates the catalog from the provided catalog template
CatalogTemplate.mdb located in the <Program Files>\GeoMedia\Templates\Catalogs
folder. This catalog template is an Access database with tables defined as per the metadata
model and containing no metadata. Only the system-specific tables having static data, like
the system parameters and field names, are populated. When you select a template, the
command checks whether it is a valid GeoMedia catalog template or not.
To create the new catalog after selecting the template, you specify a name for the catalog
or select an existing .mdb file in the default <warehouse location>\Catalogs folder. The
command then creates the catalog based on the selected template. If the template is valid
and it has some catalog records, all the records are copied into the new catalog. A template
can be created to easily enter metadata information for information that is the same.
When the catalog is created, a connection is opened for the new catalog, and it is added to
the CatalogConnections collection. The name of the catalog connection is set as the
catalog name itself. If a catalog connection exists with the same name, an incrementing
digit is added to the end of the name.
9-7
To create a new catalog:

1. Select Tools > Catalogs > New Catalog.
2. Select the appropriate catalog template; then click Open.
3. Type the appropriate File name; then click Save.

The template is validated, and if valid, the catalog is created.
Creating a New Catalog Connection

New Catalog Connection lets you connect to multiple geospatial catalogs that are
compatible with GeoMedia. This connection is then available for use with other catalog
commands. You can open a catalog in read-write, in read-only, or in closed states.
9-8
You can make the following two types of connections:

• Access database—Catalog is a Microsoft Access database (default), with the default
connection name Access Catalog Connection <Number starting from 1>, for example,
Access Catalog Connection 1.
• ODBC database—Catalog is located in an SQL Server or Oracle database, with the
default connection name ODBC Catalog Connection <Number starting from 1>, for
example, ODBC Catalog Connection 1.
For Access, you select the location of the Microsoft Access database file (.mdb) to which
you want to establish a connection. For ODBC, you select the data source name (DSN) of
the catalog to which you want to establish a connection. You then provide additional
parameters for the SQL or Oracle database.
The command makes the connection to the catalog with maximum permissions available to
you. Initially the command tries the connection in the read-write state. If this fails it tries
to open the connection in the read-only state. If a connection fails, it is added to the list of
the catalog connections, but its state is set to closed. If a connection to the same database
already exists, a message is displayed telling you to use the existing connection. In this
case, the connection is not made.
maintain these in separate folders in order to make the individual database type more easily
found. In addition, the software has separate folder locations for the Access versions of
these files, and you should add the word catalog, library, or warehouse to filenames in
To create a new catalog connection:

1. Select Tools > Catalogs > New Catalog Connection.
2. Select Access database as the Connection type.
OR
9-9
Select ODBC database as the Connection type.
3. Change the default connection Name if appropriate.

4. For Access, type the complete path of the .mdb file, or select the Database file name
through Browse.
OR
For ODBC, select the Data source name from the drop-down list.
5. Click OK.
For Access, the connection is made.
OR
For ODBC, type the username and password in the SQL or Oracle dialog boxes that
are displayed, and then the connection is made.
Managing Catalog Connections

Catalog Connections lets you manage the connection information of catalogs in a manner
similar to the Warehouse > Connections command of GeoMedia. This command lets you
perform the following:
• Make a new catalog connection.
• Review a list of all available catalog connections in a GeoWorkspace.
• Change the state of a catalog connection (open read-write, open read-only, or closed).
• Edit the catalog connection parameters of an existing connection.
• Delete an existing open or closed catalog connection.
All catalog connections present in the GeoWorkspace are displayed in the connection grid
on the Catalog Connections dialog box. The rows in the grid are sorted alphabetically
based on the Name column. You can resize this grid as appropriate.
The connection grid has the following read-only columns:
9-10
Name—Catalog connection names, with an icon at the start of the cell indicating the state:
Open Read-Write
Open Read-Only
Closed
Type—Catalog connection type, Access or ODBC.
Catalog—Location of the database .mdb file for an Access database or the data source
name for an Oracle or SQL Server database. You can edit the location of the catalog using
the Properties but not directly from the cell of the grid.
To create a new connection:

1. Select Tools > Catalogs > Catalog Connections.
2. Click New.
3. Select Access database as the Connection type.
OR
Select ODBC database as the Connection type.
9-11
4. Change the default connection Name if appropriate.

5. For Access, type the complete path of the .mdb file, or select the Database file name
through Browse.
OR
For ODBC, type the complete path of the Data source name, or select it from the
drop-down list.
6. Click OK.
For Access, the connection is made.
OR
For ODBC, type the username and password in the Oracle or SQL Server dialog boxes
that are displayed, and then the connection is made.
To open or close connections:

2. Select the row of the connection that you want to open or close.
3. Click Open Connection or Close Connection as appropriate.
To edit a catlog connection:

2. Select the row of the connection that you want to edit.
3. Click Close Connection if the connection is open.
9-12
5. Change the location of the .mdb file for an Access database or the data source name for
an Oracle or SQL Server database.
Importing Catalog Records

Import Catalog Records lets you import catalog records from multiple sources into a
read-write catalog. Thus, this command is a timesaving tool that allows the easy
integration, sharing, and storage of data. To use this command, at least one read-write
catalog connection must exist in the GeoWorkspace. When you select a catalog, a
connection is made to the catalog if it is not already open, that is, the catalog connection is
opened on-demand by the command but not during the GeoWorkspace load. You must
supply a password to establish a connection to the catalog if it is required.
Imported records can be from the following exchange formats: GCE (GeoMedia Catalog
Exchange Format), TXT (FGDC), and XML (FGDC). You can import multiple files of the
same format in a single import operation. In addition, you can apply a filter on the list of
selected files. Based on the selected import format, the filter is the selected format or all
files, as follows:
Selected Format Filter
GCE • GeoMedia Catalog Exchange Files (.gce)
• SMMS Exchange Format Files (.sef)
• All Files
TXT (FGDC) • FGDC Formatted Text files (.txt)
• All Files
XML (FGDC) • FGDC standard XML Documents (.xml)
• All Files
XML files can be used by different applications when they conform to a published
Document Type Declaration (DTD) file, which defines tag names and proper sequence, or
to an XML schema. For exporting metadata content, and for importing metadata generated
by other applications, Catalog uses the standard FGDC metadata DTD file: FGDC-STD-
001-1998 (Version 2) – http://www.fgdc.gov/metadata/fgdc-std-001-1998.dtd.
Other applications may generate XML files which use variants of this XML format.
Therefore, Catalog users will minimize potential errors in the import process by always
9-13
pre-processing a metadata XML file with the mp application available from the U.S.
Geological Survey. The no-cost mp utility can parse and output a metadata record into an
FGDC-compliant format that is acceptable for FGDC clearinghouse submission and for
import into Catalog. This and other metadata utilities are available for free download
through the USGS website at http://geology.usgs.gov/tools/metadata/.
Catalog users can process any XML metadata file through mp and can generate an output
XML file which is completely compliant, along with helpful information about metadata
fields which may be missing or incorrect.
This command Import Catalog Records creates one catalog record for each imported file.
The record is created in the catalog with a primary key consisting of the FGDC-standard
content field title as contained in the selected file. If a catalog record with same title exists
in the destination catalog, an error is generated, and the import process for that record is
aborted.
Each import generates log files (.log) listing the results of the import operation. There are
two types of log files, an individual log file for each input file and a summary log file for
the entire import operation. The log files are output to the folder in which the input files
reside, unless that folder is read-only. In this case, the log files are output to your \tmp
folder.
To import catalog records:

1. Select Tools > Catalogs > Import Catalog Records.
2. Type the location from where the import files are to be read, or use Browse to select
the location.
9-14
3. Select the appropriate file(s) from the Available files list.
Note: A tooltip is attached to the filenames so that long filenames can be read easily.
4. Select the appropriate Import format option.

5. Optional: Select a file type from the Files of type drop-down list to filter the
Available files list.
6. Select the appropriate Target catalog from the drop-down list; then click OK.
The status of the import for the selected set of files is displayed in the status bar, the
catalog records are imported from the selected source file(s) to the selected catalog,
and an Import complete message is displayed.
The target catalog connection is opened if it is in the closed state and it prompts for
the password in this process in the case of ODBC catalog. If the connection cannot be
opened in Read-Write mode, a message is displayed because the import cannot be
done on the Read-Only/Closed connection.
Hints about Importing Metadata

• The Catalog database structure will recognize contacts, citations, and other “re-usable”
components of imported metadata records if they have the same names as those
contacts, citations, and so on, that are already in the Catalog database. Catalog will not
update a contact, citation, or other component of existing metadata records when new
(records) contain the same “key” information.
• View the Importing Metadata dialog box to determine whether your record(s) was
imported successfully. You might want to view or save the import LOG file(s) that
results from the import operation in order to learn about any import errors or warning
conditions. If you choose to save the LOG file(s) for further use, Catalog will provide
a default filename, such as My_File.XML.ERR, and will default to the same folder
from which the import records were selected.
• If the Importing Metadata command is unable to import a file, you should consult
Catalog Help regarding the use of the mp utility to validate the file as part of your
preparation for importing data.
• The import process can be aborted pressing ESC.
Exporting Catalog Records

Export Catalog Records lets you output multiple catalog records for distribution of data,
for submission to a metadata clearinghouse, for exchange with other users, and for general
viewing outside of GeoMedia, that is, using Web browser software. This command
exports the catalog records from a specified catalog into files of a selected format in a
9-15
specified destination folder. The default destination folder is the \Catalogs subfolder of
your \Warehouses folder. The exported file is named are <Record title>.<export file type>.
In case the title of the exported record contains invalid characters for file naming in
Windows, these characters are replaced by an underscore ( _ ) in naming the exported file.
This command generates one or more files for each exported metadata record.
The Difference between Exporting and Publishing

The Export Catalog Records command produces two kinds of metadata files. While the
results may seem similar, the intent of the two groups of file types is different, as follows:
• Catalog records that are “exported” are intended for exchange with other Catalog users,
and for use in other software applications.
• Catalog records that are “published ” are intended for general viewing outside of
Catalog; usually with Web browser software.
HTML files are exclusively for viewing, and GCE files are exclusively for export to other
Catalog users. TXT files can be used for either, and XML files may be created for file
exchange or – when a style sheet reference is included – for viewing.
To use the Export Catalog Records command, at least one catalog must exist in the
GeoWorkspace. When you select a catalog, a connection is made to the catalog if it is not
already open, that is, the catalog connection is opened on-demand by the command but not
during the GeoWorkspace load. You must supply a password to establish a connection to
the catalog if it is required.
You can export catalog records into the following file formats selected on the Export tab
of the command dialog box: HTML, GCE, TXT (FGDC), XML (FGDC), and XML (ISO).
Each format lets you select different parameters on the Advanced tab, as follows:
Export Format: HTML TXT GCE XML XML

(FGDC) (FGDC) (ISO)
Sections to include:
User Defined √ √
Identification √ √
Data Quality √ √
Spatial Data Organization √ √
Entity and Attributes √ √
Distribution √ √
Metadata Reference √ √
Options:
Rollup empty fields √ √
Include biological profile √ √ √ √
Include map display √
Publish using style sheet √ √ √
Sections to include—Lets you select which FGDC metadata sections to export.
9-16
Options:
• Rollup empty fields—Lets you exclude all the empty metadata elements.
• Include biological profile—Lets you include the metadata content belonging to
biological profiles.
• Include map display—Lets you include a map display of the record. This option is
not applicable if the selected record is nongraphic.
Publish using style sheet, displayed only for the XML (FGDC) and XML (ISO)
formats—Lets you attach a style sheet to the exported data. You can type the style sheet
path or browse to select the style sheet.
A style sheet customizes the display of your catalog content. It is attached to the exported
XML file to view the XML data in a browser. For XML(ISO) only, the core elements are
published using a style sheet. Four style sheets are delivered in the \Program
Files\GeoMedia\stylesheets\catalogs folder: FGDC_classic.xsl, FGDC_FAQ.xsl,
ViewDetails.xsl, and ISO_Stylesheet1.xsl.
Note: XSL is a language for expressing style sheets. An XSL style sheet is a file that
describes how to display an XML document of a given type. The XSL style sheets used to
display GeoMedia catalog metadata records in your Web browser include bits of
programming known as scripts. Scripts are termed active content; examples of familiar
active content include stock tickers, video, and animated content on Web pages. In order
to properly display metadata in FGDC.XML or ISO.XML format, be sure that your Web
browser is set to allow the running of scripts.
Each export generates log files (.log) listing the results of the export operation. There are
two types of log files, an individual log file for each catalog record exported and a
summary log file for the entire export operation. In case the title of the exported record
contains invalid characters for file naming in Windows, these characters are replaced by an
underscore ( _ ) in naming the log file. The log files are output to the export folder.
To export catalog records:

1. Select Tools > Catalogs > Export Catalog Records.
9-17
2. On the General tab, select the appropriate Catalog connection from the drop-down
list.
3. Select the appropriate open catalog record(s) from the Records list.
4. Select the appropriate Export format option.
5. Type the appropriate location where the export files are to be saved in the Export
folder field, or use Browse to select it.
6. Select the Advanced tab; then set the available parameters appropriately.
(The following example is the Advanced tab for the HTML export format.)
9-18
(The following example is the Advanced tab for the XML (ISO) export format.)
If the style sheet you want to use is available on your network, browse to its location,
and select the XSL file you want to use. Click Open and OK. Until you change this
selection, Catalog will publish all XML (ISO) metadata records with a link to this style
sheet.
Some users map network drives to their machines with the possibility of remapping in
the future. If this applies to you, you may want to use a UNC pathname, for example,
9-19
\\gisdataserver\metadata\My_Style.XSL, as opposed to placing a drive letter in the

path. If you remap using a UNC, you will not have to re-attach to the database.
If you want to publish XML metadata on the Web and the style sheet you want to use
is available on a website, do not browse to its location—instead, type or paste in the
full URL for the style sheet, such as
http://www.gisdataserver.org/metadata/My_Style.XSL.
7. Click Apply.
The status of the export for the selected records is displayed in the status bar, the
selected catalog records are exported, and the files are stored in the destination folder.
Select Text Styles and Graphic File for XML Display

An XSL style sheet is a file that describes how to display an XML document of a given
type, and an accomplished XSL editor can control many aspects of the display of the
metadata content contained in an Catalog XML record. You can control the font, colors,
and size of text displayed in your XML metadata reports by editing a custom style sheet.
Each of the XSL (style sheet) files supplied with catalogs is located in the
<HOME>\StyleSheets\Catalogs folder, and contains identical code that defines text font,
color, and size used when that style sheet is used. XSL editors can use Notepad or another
tool to edit the class definitions that are encoded in the beginning of the style sheet. The
style sheet is initially delivered with following classes:
CLASS RENDERS
.title Title of the report
.contents List of sections
.sectionname Hyper linked section names
.tag Metadata element headings
.text Element content of type text
.biotag Biological element headings
.biotext Text of biological elements
XSL editors can also eliminate the GeoMedia graphic displayed at the top-left corner of
XML metadata reports, or replace it with the graphic identity of the enterprise graphic, by
editing any of the style sheets delivered with GeoMedia Catalog. The four XSL files
supplied with Catalog use the following graphic:
• <HOME>\StyleSheets\tech_geomedia.gif as the graphic file that displays by default.
XSL editors can create a graphic file of similar size, located in any convenient
pathname.
9-20
Associating Catalog Records

Associate Catalog Records lets you link a catalog record to the dataset, which is the
GeoMedia feature class or image that it describes. This allows you to do the following:
• Capture certain metadata elements automatically.
• Provide a visual view of your data.
• Export browse graphics on the fly when generating an HTML report.
To use this command, at least one catalog connection must exist in the GeoWorkspace.
When you select a catalog connection, the catalog will be opened if it is not already open,
that is, the catalog connection is opened on-demand by the command but not during the
GeoWorkspace load. You must supply a password to establish a connection to the catalog
if it is required.
To associate the catalog record, the catalog must be connected in the read-write state. The
association information of a dataset is persisted in the catalog. You can associate a feature
class or an image file. Supported image file formats are the same as those of the GeoMedia
raster system that are georeferenced.
You can associate a dataset with a catalog record as a foreground layer or as a background
layer. The first dataset associated is called the foreground layer. The catalog record can be
associated to a second dataset called the background layer, which helps provide a frame-of-
reference for the associated dataset. For example, a dataset that displays rivers in a state is
more useful if a background layer showing the state is displayed with it. Therefore, the
background layer must thus have the same projection as the foreground layer. This
command associates a dataset (foreground or background) to a catalog record and captures
spatial-related metadata from the associated (foreground) dataset. Each catalog record can
point to zero, one, or two GeoMedia feature classes, which are then used in map displays
of the spatial data described by the catalog record.
Associate Catalog Records also displays the available catalog record titles from the
connected catalogs before making an association. Catalog record titles are displayed along
with icons to indicate whether or not the catalog record already has an association with a
feature class as a foreground layer, as follows:
—With an associated dataset in the foreground layer
—Without an associated dataset in the foreground layer
In addition, this command lets you create a new catalog record. You can create an entirely
new catalog record, create a blank catalog record, or create one from an existing catalog
record. If the latter, the new catalog record is created, and the content of the existing
catalog record with any modified FGDC sections are copied into the new one. Once
created, you can then associate a dataset to the new catalog record.
You can also disassociate a dataset from a catalog record and re-associate a dataset with a
catalog record. Disassociating a dataset breaks the link between the dataset and a catalog
9-21
record, updating the relevant metadata record of the catalog. Once disassociated, the
dataset can no longer be previewed.
This command also captures spatially related metadata after associating a dataset
(foreground) to a catalog record. The captured information is stored in related fields in the
catalog record. This allows synchronizing the captured metadata stored in a catalog to
reflect changes to the associated dataset in the foreground. Captured metadata elements are
the following:
• Bounding coordinates—The limits of coverage of a dataset expressed by latitude and
longitude values. This compound metadata element is stored in the
Identification/Spatial domain section.
• Attribute name—The identity of all attributes associated with the feature class. This
metadata element is stored in the Entity and Attributes section.
• Point and vector object information—The type and number of vector or non-
gridded-point spatial objects in the dataset. This compound metadata element is stored
in the Spatial Data Organization section.
Finally, this command lets you view the associations and complete metadata content for a
selected catalog record. Thus, you can see the spatial data captured during a capture
operation.
To associate a catalog record as a foreground or background layer:

1. Select Tools > Catalogs > Associate Catalog Records.
9-22
2. Select the appropriate catalog connection to display the treeview of Available catalog
records.
3. Select the appropriate catalog record to associate.
4. Select the appropriate Dataset associations > Foreground layer/Background layer
option.
For Foreground layer, if a feature class is associated to the record, warehouse
connection and feature information is displayed. If an image is associated to the
record, the image folder and image file name are displayed.
For Background layer, if a feature class is associated to the record, warehouse
connection and feature information is displayed. If an image is associated to the
record, the image folder and image file name are displayed.
5. For a feature class, click Associate Feature Class.
OR
For an image file, click Associate Image File.
6. For a feature class, select the appropriate connection and Feature class to which the
catalog record needs to be associated; then click OK.
9-23
OR
For an image file, select the appropriate connection and image file to which the catalog
record needs to be associated; then click OK.
To create a new catalog record:

2. Click New Catalog Record.
9-24
Note: The width of the Catalog record field expands to fit the largest item in the list.
3. Type the Title of the new record. Go to Step 7.

OR
Type the Title of an existing record. Continue with Step 4.
4. Check the Create from check box.
5. Select the appropriate entry from the Catalog record drop-down list.
6. Check the appropriate Sections to include check boxes for the FGDC sections whose
contents are to be copied from the existing catalog record into the new one.
7. Click OK.
The new catalog record is created with the user-specified title in the selected catalog,
and the newly added catalog record is displayed in the Available catalog records
treeview under the relevant catalog.
To capture information:
records.
3. Select the appropriate catalog record.
4. Click Capture.
9-25
The metadata elements of the catalog record are updated by capturing relevant
information from the associated foreground layer.
To view catalog details:

records.
4. Click View Details.
A system-supported browser window is opened, and the metadata content is displayed
as an XML file using the ViewDetails.xsl style sheet.
Exploring Catalogs
Catalog Explorer provides a functional and practical means for you to manage your data
and metadata. This command provides a powerful tool for quickly locating and
previewing datasets in your GIS data library. You can browse catalog records from
multiple catalogs and locate datasets according to metadata keywords, attributes, time
period, or geographic area.
To use this command, at least one catalog connection must exist in the GeoWorkspace.
When you select a catalog connection, the catalog will be opened if it is not already open,
that is, the catalog connection is opened on-demand by the command but not during the
GeoWorkspace load. You must supply a password to establish a connection to the catalog
if it is required.
With this command, you can view a list of open catalogs and the catalog records that they
contain. You can then select one of the catalog records in the Windows Explorer-style
treeview, and view the important metadata content, as follows:
• Title and the contact persons for the metadata and the dataset
• Preview of the map if the catalog record is associated to a feature class
• Basic description
• Important spatial metadata content
You can define specific criteria for searching within open catalogs, and you can clear and
redefine a search. This search criteria for the selection of catalog records include the
following:
• Contains any or none of the listed keywords
• Contains any of the listed attributes
• Corresponds to the time period of content
9-26
• Contains the warehouse type of the associated dataset

• Contained in the bounding region you select
After you have executed a search based on the search criteria entered, you can view the
search results as a list of catalog records. You can then load the feature classes associated
with the selected catalog record(s) into an active map window. You can also view a
detailed display of a catalog record.
Looking at the Catalog Explorer Interface

You perform all of the previously discussed tasks through the Catalog Explorer dialog
box. This dialog box has three main sections. The treeviews section to the left contains
two treeview panels for displaying available catalog records and search results. The tabs
section to the right contains five tabs for viewing important catalog record content
summary, for entering search criteria, and performing a search. The commands section at
the bottom contains the commands for viewing catalog record details and for loading
feature data.
Catalog Record and Search Result Treeviews

In this section, the Available catalog records field displays all the catalog connections in
the GeoWorkspace in the collapsed mode. When you expand any catalog node, a
connection is made to the catalog if it is not already open, that is, the catalog connection is
opened on-demand by the command but not during the GeoWorkspace load. You must
9-27
supply a password to establish a connection to the catalog if it is required. A selected

catalog is highlighted to indicate that it is the active catalog and that it can be expanded to
view the catalog records. You can only select one catalog record at a time. When you
select a catalog record, the metadata summary of an active record is displayed in the first
four tabs to the right of the treeview.
The icon to the left of each catalog record indicates whether or not the item is already
associated with a feature class, as shown below:
—With associated dataset in the foreground. Both the

dataset and metadata are available to preview.
—Without an associated dataset in the foreground. Only

the metadata is available to preview.
The Search results treeview is populated with the list of titles of the search results when a
search is executed on all connected catalogs. The search operation is based on the search
criteria entered in the Search Criteria subtab of the Search tab. You can select one of the
catalog records in the list to view the metadata summary. The selection of the catalog
record in the Available catalog records treeview and in the Search results treeview is
synchronized. Thus, if you select one catalog record in the Search results treeview, the
same item is highlighted in the Available catalog records treeview and the metadata
summary of a selected record is displayed in the tabs to the right. Similarly, if you select a
catalog record in the Available catalog records treeview, the corresponding item in the
Search results treeview is selected if the item exists, and the metadata summary of a
selected record is displayed in the tabs to the right. When multiple catalog records are to
be selected for a load operation, you select them by selecting multiple items from the list.
When multiple items are selected in this list, however, there is no synchronization with the
Available catalog records treeview and the Search results treeview, and no metadata
summary is displayed in the tabs.
9-28
View Details and Load Feature Data Commands

In the bottom section, View Details lets you view the complete content of a selected
catalog record in a system-supported browser window. The catalog record content is
displayed as an XML file using the ViewDetails.xsl style sheet. This button is enabled
when you select one catalog record, with or without foreground association, from the
Available catalog records treeview or from the Search results treeview.
Note: The graphic file, style elements, and content displayed by the ViewDetails.xsl style
sheet can be modified to conform to your preferences and enterprise standards by anyone
who has the XML authoring tools and system privileges to modify this or other style sheets
delivered in the <HOME>\StyleSheets\Catalogs folder.
Load Feature Data lets you create, open, and use warehouse connection(s) and feature
classes in GeoMedia that are associated with the selected catalog record(s). This command
is enabled when you select one or more catalog records from the Available catalog
records treeview or from the Search results treeview. If you need to select a single
record, you can do so from the Available catalog records treeview or from the Search
results treeview.
Load Feature Data checks whether the selected catalog record(s) have associated feature
class(es). Catalog records that are not associated to a dataset, or that are associated to an
image file, are skipped. For each qualifying feature class, the command checks whether a
GDO warehouse connection is already established. To identify whether the warehouse
connection already exists or not, the command tries to match the location and the
connection information for each connection in the connection collection on the document
with that of the dataset of the selected catalog. If the command finds an exact matching
connection, with a closed status, it tries to open the connection in the read-only state. If
command does not find a matching connection already connected, a new connection is
created by generating a unique name for the connection based on the type of the dataset
(‘<Type> Connection <numeric>’) for example, ‘OracleORO Connection 1’. The new
connection is always opened in the read-only state, irrespective of the type of the dataset,
for example, Oracle read-write or read-only. If such a connection already exists but is
closed, the connection is opened. If it is possible to open the connection in the read-write
state, the connection is opened. If such a connection already exists and is open, no further
action related to the connection is required.
Once an open connection is established, the associated feature class is added to the active
map window legend, if a map window is indeed active and if the feature class in question is
a spatial feature class. A legend is created using the name of the feature class as the title,
and this name is added to the legend entries collection in the first position. This is repeated
for all the catalog records you select. The log file LoadFeatures.log is created in the user
\temp folder to log any errors in making connections.
9-29
Catalog Explorer Tabs

The five Catalog Explorer tabs in the left section of the dialog box let you browse and
search catalog records. These tabs are the following: Description, Identification,
Spatial, Attributes, and Search.
All the tabs except the Search tab are summary tabs. You define the search criteria on the
Search tab and review the results on the summary tabs. The Search tab is always enabled,
but the behavior of the summary tabs varies. The summary tabs are:
• Disabled when you only select a catalog connection node.
• Enabled when you select one catalog record having an association from the Available
catalog records or Search results.
• Enabled when you select one unbound record (having no foreground association) from
the Available catalog records or Search results.
• Enabled when multiple records are selected in Search results, and the content for the
selected catalog record of the available records treeview is displayed.
• Selecting a catalog record from the Available catalog records treeview, which does not
have a foreground and background association, the Summary map displays a message
saying “Map not Available.” In the case of an invalid dataset association (that is, the
dataset cannot be connected), the summary map displays a message saying “Unable to
connect to the database. Please verify that your warehouse-connection parameters are
correct and try again.”
Description tab—Displays the Abstract, Purpose, and Supplemental metadata elements.
These elements are displayed in their respective read-only fields.
9-30
Identification tab—Displays important metadata elements of the Identification section:

Dataset contact, Metadata contact, Theme keywords, Place keywords, keywords,
Stratum keywords, Temporal keywords, Time period, Access constraints, Use
constraints, Dataset credit, and Native dataset environment. Keywords may consist of
one or more words and are separated by commas (,).
9-31
Spatial tab—Displays a map preview of the associated feature class of the selected catalog
record. A catalog record can have two feature classes associated to it, one to display the
foreground layer and one to display the background layer. The map control is disabled if
either of the following two conditions exists:
• The metadata has no associated feature class for the foreground layer.
• The selection is on a catalog node in the Available catalog records treeview.
To the left of the map is a toolbar that lets you display and browse the map content.
Show Map—Display map or data, if available.
Zoom In—Zoom in on features.
Zoom Out—Zoom out from features.
Pan—Pan map features.
Full Extent—Display full extent (fit all) of the map.
This tab also displays read-only association details and spatial-related metadata elements of
the two feature class layers. For the foreground layer it displays the feature class name,
warehouse, number of features in the map, and map projection. For the background layer
it displays the image filename, image folder, and bounding coordinates.
Note: The projection of the displayed map is always predefined as geographic, and the
symbology is also predefined and hard coded.
9-32
Attributes tab—Displays all the Attribute labels and their Attribute definition for the
entity named captured. FGDC metadata can contain multiple entities for the dataset it is
explaining. An entity contains multiple attributes. Each attribute has a name, a value, and
several associated properties. The attributes of the associated feature class are captured
and placed under an entity named captured.
Search tab—Contains two subtabs, Text/Data Criteria and Spatial Criteria, that let you
enter search criteria to search for metadata. You can search on the following criteria:
• Keywords • Time period
• Attributes • Geographic area
The Text/Date Criteria tab contains the following frames: Keywords, Attributes, Not
containing keywords (excluded), Associated dataset type, and Time period of content.
The Keywords and Attributes frames let you enter a list of keywords or attributes. The
search process finds the catalog records containing one of the keywords or attributes from
the list. Clicking Add appends the new keyword or attribute to a list. The excluded frame
finds the catalog records not containing the keywords from the list.
The Associated dataset type frame lets you select catalog records associated with a
specific type of warehouse. The Time period of content frame lets you enter the time
period of interest to which the metadata corresponds.
9-33
The Spatial Criteria tab is for the interactive capture of bounding extents of the interested
spatial area for a search. The Bounding coordinates frame contains a feature class
(having geometry) selection field, a search graphic, and bounding extents fields. The
command automatically fills in the bounding coordinates based on the search area defined
and searches for corresponding bounding coordinates entered in the metadata records.
This tab gives you a geographic display so you can select a region to search for the data
you want. The catalog search is based on the spatial extent values that you enter manually
or that you capture from a map by rubber banding. The display contains the feature class
selected for reference in the map. To the left of the map is a toolbar that lets you display
and browse the map content, as described for the Spatial tab, and the Bounding Extent
button, which lets you rubber band on the map: .
9-34
Note: The projection of the displayed map is always predefined as geographic, and the
symbology is also predefined and hard coded.
The Search tab also has two command buttons, Search and Clear. Search lets you
perform the search on open catalogs to select catalog records satisfying the search criteria
entered in the Spatial Criteria tab, and it then lets you send the results to the Search
results treeview. To perform a search from this tab, you must either edit existing search
criteria to create new search criteria, or you must clear existing search criteria and search
results with Clear, and then enter the new search criteria. This command is enabled when
any of the controls on this tab are populated.
You can navigate through the search results by clicking the summary tabs and by clicking
the record of interest in the Search results list. This provides a quick means of locating a
dataset, especially for those organizations with hundreds or thousands of datasets to
manage.
To explore catalogs:
1. Select Tools > Catalogs > Catalog Explorer.
9-35
records.
4. Select the Description tab to view the corresponding information.
5. Select the Identification tab to view the corresponding information.
6. Select the Spatial tab to view the corresponding information.
7. To display the map/data if the map display area contains the message Click the Show
Map button to view the data, click Show Map on the toolbar.
8. Select the Attributes tab to view the corresponding information.
9. Select the Search tab to perform a metadata search.
10. Select the Text/Data Criteria bottom tab; then enter the appropriate search criteria.
11. Select the Spatial Criteria bottom tab; then enter the appropriate search criteria.
12. Click Search.
The results are displayed in the Search results treeview.
9-36
Sample Catalog Explorer Workflows

A client has called to ask if you have any data for highways in the U.S. You plan on trying
to do a GIS-based search for this data with no metadata. However, it is difficult to
navigate through the data because there are over 50 features on the legend with names that
are not descriptive. When you display a dataset in the map window, it is also difficult to
know its quality. Therefore, you have decided to perform a metadata-based search using
the Catalogs commands in the following workflow:
1. Start Catalog Explorer, which is your query and display tool for geospatial metadata
catalogs. The GIS data stored in the USSampleData.mdb warehouse is described by
metadata records that are stored in Catalog_Samples.mdb.
2. Next, use the Available catalog records treeview to expand the USSampleData
connection. This results in a list of the catalog records being displayed.
You can easily find datasets with this approach because the catalog record names are
more descriptive than the feature class names in the legend. In addition, the summary
tabs provide information about the dataset, such as abstract and purpose.
3. Select the record named Highway Interchanges -- USA_Sample_Data for GM6.0
to view the corresponding metadata elements.
4. To load the selected dataset into GeoMedia, use Load Feature Data.
Another client has called to ask if you have any U.S. data in your warehouses of worldwide
feature classes. To perform a search on all of the feature classes described in the catalog,
you select the Search tab and then the Spatial Criteria subtab. Define a region around the
U.S. in the displayed map – zoom in, if you would like. Then click Search, which
generates a search result set based on the bounding region.
9-37
1. To perform a related search using a keyword, select the Text/Date Criteria subtab of
the Search tab. Type highway in the Enter keywords field, click Add, and then
click Search.
Notice that the feature classes appearing as Search Results is reduced; you have
generated a search result set based on the spatial selection and on the keyword.
2. The client is happy you found the data, but now has asked you to provide a digital
copy of the data in HTML format. To do this, use the Export Catalog Record
command, selecting the catalog records included in your search results as the metadata
to export. Then select the HTML export format (keeping the advanced defaults and
including the map display), and then perform the export.
3. You were quickly able to query and to display for the client key information on U.S.
geospatial datasets that are related to highways. Your client is really seeing the value
of metadata management.
Glossary of Catalog Terminology

The following is a list of useful terms when working with catalogs:
Catalog: A database that serves as a repository of metadata records. Also termed a
metadata database.
Dataset: GeoMedia feature class or image file associated with a metadata record. The
metadata record stores the connection and other information related to the feature class
associated with a metadata record.
Note: According to the ISO-19115 Metadata standard: “A dataset may be a smaller

grouping of data which, though limited by some constraint such as spatial extent or feature
type, is located physically within a larger dataset. Theoretically, a dataset may be as small
as a single feature or feature attribute contained within a larger dataset. A hardcopy map or
chart may be considered a dataset.”
FGDC: U.S. Federal Geographic Data Committee, which supports the “Content Standard
for Digital Geospatial Metadata.” See http://www.fgdc.gov/metadata.
GCE: GeoMedia Catalog Exchange. A file format for the exchange (export and import)
of metadata records among GeoMedia Catalog users.
Geospatial Catalog: See Catalog.
Geospatial Metadata: Data that describes the content, quality, condition, and other
characteristics of geospatial data.
ISO: International Organization for Standardization, which is the world's largest
developer of standards. An ISO technical committee is responsible for the development of
ISO-19115 and ISO-19139, which are international standards and technical specifications
9-38
prescribing the content and expression of geospatial metadata. See

http://www.isotc211.org.
Metadata: Information about data. For the purposes of this document, see Geospatial
Metadata.
Metadata element: A data element is a logically primitive item of metadata. A
compound metadata element is a group of logically related data elements and other
compound elements.
Metadata record: A single logical entity, which is a collection of related data (metadata
elements) describing geospatial data. A key field (title) identifies each metadata record
uniquely within a catalog.
SEF: SMMS exchange format. A file format for the import of metadata generated from
legacy Intergraph metadata products.
Software Delivery
GeoMedia Catalog functions will be delivered as part of GeoMedia by using the default
delivery folder of C:\Program Files\GeoMedia. These are referenced as “<HOME>” in
the remainder of this section.
GeoMedia software components will be delivered to the folder <HOME>\Program.
GeoMedia Catalog functions require the delivery of database(s), style sheet(s), and other
files that will be located in the structure detailed in the following table.
Catalog Components Delivery Table
Files/Folders Description Location
CatalogTemplate.mdb Template access Catalog <HOME>\Templates\Catalogs
required for the New
Catalog command.
Catalog_Samples.mdb Sample Catalog required <Drive>:\Warehouses\Catalogs
for the New Catalog
Connection command.
World.mdb GeoMedia warehouse used <Drive>:\Warehouses
in the Catalog Explorer
command as the default
search map.
Oracle Scripts Template scripts required <Home>\Program
for creating Oracle
catalogs.
SQLServer Scripts Template scripts required <Home>\Program
for creating SQL Server
catalogs.
9-39
Files/Folders Description Location

FGDC_classic.xsl, Style sheets used to View <HOME>\StyleSheets\Catalogs
FGDC_FAQ.xsl, a Catalog Record, and to
ISO_Stylesheet1.xsl, publish record(s) using
View_Details.xsl the Export Catalog
Records command.
tech_geomedia.gif Default graphic file <HOME>\StyleSheets\Catalogs
displayed by XML style
sheets.
FGDC_to_ISO.xslt, FGDC content is <HOME>\Program
FGDC Dataset translated to XML(ISO)
Metadata Profile.pdf using the xslt in the
Export Catalog Records
command. An ISO
“profile” documents the
logic for transforming
FGDC metadata content to
ISO19139.XML structure,
as performed by the xslt
file.
9-40
Analyzing GeoMedia Data
GeoMedia provides various ways for you to analyze your data using queries. Broadly, a
query is a request for information. Specifically, it is a request for the features that meet the
conditions you define and/or a request for certain information about the features. The
software gives you several ways to define these conditions.
To find features that meet your conditions, you query feature classes in any open
warehouse in the GeoWorkspace or query previously built queries. Queries are stored in
the GeoWorkspace so that, if a warehouse changes, all queries are updated each time they
are displayed. If a default spatial filter is defined for the warehouse connection at the time
the query is defined, the query is limited to the geographic area defined by the spatial filter.
Furthermore, spatial filters, feature classes, interact in three scenarios. First, if a feature
class that has never been accessed in the GeoWorkspace, the feature class has never had a
spatial filter created for it and so gets the default spatial filter. Second, if the feature class
has already been accessed in the GeoWorkspace, it has its own spatial filter and so does not
get the default spatial filter. Third, a query always has its own spatial filter.
The software scans the query area for the features that meet your conditions and then
displays the results geographically in a map window or in tabular format in a data window.
An entry for the query result is added to the legend, and its display can be manipulated
through the legend properties like any other legend entry. In fact, once built, a query can
be treated just like a feature class.
Working with Filter Queries

Filter queries are distinguished primarily by the fact that they return a subset of the features
in a single feature class or query. You can build several types of filter queries although
they have much in common:
• An attribute-filter query allows you to limit the search to individual features whose
attributes contain values that meet the conditions specified by an operator. An
operator is a symbol or expression, such as = (equals) or > (is greater than), that
represents the relationship between two values.
For example, an attribute-filter query would return all parcels with an assessed value of
$50,000 or more.
• A spatial query allows you to limit the search to individual features whose geometry
has a spatial relationship to features from another feature class or query.
10-1
For example, a spatial query would return all parcels that are within 500 feet of a
railroad.
• A combined attribute and spatial query requests features with certain attribute values
that meet specified spatial conditions, such as overlapping or being contained by
another feature class or query.
For example, a combined attribute and spatial query would return all parcels with an
assessed value of $50,000 or more that are within 500 feet of a railroad.
Note: Attribute filtered spatial queries cannot be run against the results of a Spatial
Intersection query unless the results are first output to a feature class.
• To retrieve information from an MGSM warehouse, you build linear network queries.
MGSM stores distributed attributes that are linearly referenced to network linear
features such as roads, rivers, or pipelines. Linear network queries are a type of
combined spatial and attribute query.
For example, a linear network query would return all segments of a railroad that
intersect accident sites.
Defining Attribute-Filter Queries

In an attribute-filter query, you identify the features you want by defining an attribute
filter. A filter consists of one or more expressions, each consisting of an attribute, an
operator, and a value for the attribute. In a where statement, you can specify a specific
value or a range of values for one attribute or a combination of attributes.
For example, in an attribute-filter query to select all schools where enrollment is less than
400, schools is the feature class, enrollment is the attribute, less than (<) is the operator,
and 400 is the value.
The following operators are available for all attribute queries:
= Equals >= Greater than or equal to
<= Less than or equal to <> Not equal to
> Greater than < Less than
() Parentheses for grouping expressions
and Logical and between two expressions
or Logical or between two expressions
Additional operators, such as the wildcard character % and the Structured Query Language
(SQL) function AVG, are also available from a drop-down list on the Filter dialog box.
Just which operators are available depends on your warehouse connection type.
10-2
For example, the following query would find all parcels where the accessed value is greater
than the average accessed value for all parcels:
. . . where assessed_value > (select AVG (assessed_value) from
parcels);
You create compound expressions with the and or the or operator and group expressions
with parentheses ( ).
The and operator means that both statements must be true to produce a query result.
For example, the following query would find all parcels where the owner is J. Smith and
the assessed value is over $50,000:
. . . where parcel_owner = ‘J. Smith’ and assessed_value > 50000;
The or operator means that either statement can be true to produce a query result.
For example, the following query would find all parcels where the owner is either J. Smith
or M. Brown:
. . . where parcel_owner = ‘J. Smith’ or parcel_owner = ‘M. Brown’;
Parentheses can be used to control the order in which an expression is evaluated. By
default, all relational comparison operators (<, >, <>, =,<=, >=) are evaluated first, from
left to right. The logical and operator has a higher precedence than the logical or operator;
so all and operations are performed first. You can use parentheses to change the order.
For example, to find all roads with more than four lanes or divided roads that were paved
before 1994, you would create the following filter:
last_paved < 1994 and num_lanes > 4 or divided = ‘yes’;
Because of the precedence of the and operator, you would get all roads that are divided or
all roads where the number of lanes is greater than four and paved before 1994. To get the
correct results, you would use parentheses as follows:
last_paved < 1994 and (num_lanes > 4 or divided = ‘yes’);
The software uses SQL for creating attribute-filter queries, but its point-and-click interface
allows you to build a query without knowing SQL.
SQL Dialects
Different connection types require different SQL dialects. For example, Access
connections require pound sign (#) delimiters around date and time values, whereas
MGSM connections require the keyword TIMESTAMP followed by single-quote (‘)
delimiters.
The software formats SQL statements into the appropriate dialect for each connection type
except MGE and MGDM. The SQL dialect for MGE and MGDM connections depends on
the ODBC driver. For date and time queries—and possibly others—you must manually
edit the SQL text on the Filter dialog box to issue a successful query.
10-3
In addition, the Filter dialog box performs the following:

• Displays fields of date, currency, and Boolean data types in the attributes list when
performing a query on a query.
• Displays values for these fields when you click Show Values. These values are
formatted according to the standard attribute formatting rules (that is, they appear as
they appear in the data window, feature properties, and so forth. See table below).
• When you select a value for such an attribute the list and add it to the Filter field, it is
added with any necessary delimiters and with formatting compatible with the SQL
dialect of the AttributeFilterPipe or the GDO server being queried (See table below).
• When you type a value for such an attribute in the Values field above the list and add
it to the Filter field, it is validated in standard support of formatted data entry (that is,
as validated in the data window, feature properties, and so forth), and it is then added
with any necessary delimiters and with formatting compatible with the SQL dialect of
the AttributeFilterPipe or the GDO server being queried (See table below).
• When you type a value for such an attribute in the Filter field, it is interpreted as a
literal and is not reformatted.
• When you selectsfrom the PickList descriptions in the list (either by clicking on one or
by typing the description in the Values field) , the corresponding PickList value is
added to the filter string.
Note: Fields of type LongBinary, Spatial, Graphic, and GUID are not supported by the
Filter dialog box.
Field Value Handling by Field Type for Entry, Presentation, and SQL
Text, Memo Byte, Integer, Boolean Date
Long, Single,
Double, Currency
“Show Values” Standard format (not User-defined User-defined format User-defined
Display and hypertext) format (General (Yes/No, etc., format (Date,
Entry Number, Fixed, custom) Time, Date/Time)
Standard,
Currency, or
Percent)
Attribute Filter Standard format, General Number -1 for TRUE, 0 for See note below.
Pipe SQL delimit with single format, not FALSE, not
quotes, replace delimited delimited
embedded single quotes
with consecutive single
quotes
Note: If user-defined format is “Date”, keyword DATE followed by date value expressed as YYYY-MM-DD,
delimited by single quotes. If user-defined format is “Time”, keyword TIME followed by time value expressed
as HH:MM:SS, delimited by single quotes. If user-defined format is “Date/Time”, keyword TIMESTAMP
10-4
followed by date/time value expressed as YYYY-MM-DD HH:MM:SS, delimited by single quotes.

Access GDO See Attribute Filter See Attribute Filter See Attribute Filter See note below
server SQL Pipe Pipe Pipe
Note: If user-defined format is “Date”, date value expressed as MM/DD/YYYY, delimited by pound signs. If
user-defined format is “Time”, time value expressed as HH:MM:SS, delimited by pound signs. If user-defined
format is “Date/Time”, date/time value expressed as MM/DD/YYYY HH:MM:SS, delimited by pound signs.
ArcInfo GDO See Attribute Filter See Attribute Filter See Attribute Filter See Attribute
server SQL Pipe. Pipe. Pipe. Filter Pipe.
ArcView GDO See Attribute Filter See Attribute Filter See Attribute Filter See Attribute
MapInfo GDO See Attribute Filter See Attribute Filter See Attribute Filter See Attribute
CAD GDO See Attribute Filter See Attribute Filter See Attribute Filter See Attribute
FRAMME GDO See Attribute Filter See Attribute Filter Not supported See note below.
server SQL Pipe. Pipe.
Note: Date value expressed as MM/DD/YY, delimited by single quotes; time values are not supported.
MGE GDO See Attribute Filter See Attribute Filter TBD – See note See ODBC
server SQL Pipe Pipe below. Tabular GDO
server.
Note: Differs according to ODBC driver in use. Approach to be taken is TBD.
MGDM GDO See Attribute Filter See Attribute Filter See MGE GDO See MGE GDO
server SQL Pipe. Pipe. server. server.
MGSM GDO See Attribute Filter See Attribute Filter Not supported See note below.
server SQL Pipe. Pipe.
Note: Keyword TIMESTAMP followed by date/time value expressed as YYYY-MM-DD:HH:MM:SS,
delimited by single quotes.
Oracle Relational See Attribute Filter See Attribute Filter See Attribute Filter See Attribute
GDO server SQL Pipe. Pipe. Pipe. Filter Pipe.
Oracle Object See Attribute Filter See Attribute Filter See Attribute Filter See Attribute
GDO server SQL Pipe. Pipe. Pipe. Filter Pipe.
ODBC Tabular See Attribute Filter See Attribute Filter See Attribute Filter See note below.
GDO server SQL Pipe. Pipe. Pipe.
Note: For an ODBC Tabular GDO server, the ODBC escape sequence is used. The entire escape sequence is
enclosed in braces with an identifier for the type of expression (that is, keyword), followed by the expression: {
type expression }. If user-defined format is “Date”, the expression is defined by the keyword d followed by date
value expressed as YYYY-MM-DD, delimited by single quotes. If user-defined format is “Time”, the expression
is defined by the keyword t followed by time value expressed as HH:MM:SS, delimited by single quotes. If user-
defined format is “Date/Time”, the expression is defined by the keyword ts followed by date/time value
expressed as YYYY-MM-DD HH:MM:SS, delimited by single quotes.
10-5
SQL Server See Attribute Filter See Attribute See Attribute Filter See note below.
GDO server SQL Pipe. Filter Pipe. Pipe.
Note: If user-defined format is “Date”, the date value is expressed as YYYY-MM-DD, delimited by single
quotes. If user-defined format is “Time”, the time value is expressed as HH:MM:SS, delimited by single quotes.
If user-defined format is “Date/Time”, the date/time value is expressed as YYYY-MM-DD HH:MM:SS,
delimited by single quotes.
To define an attribute-filter query:

1. Select Analysis > Attribute Query.
2. On the Options dialog box (Tools > Options), select the Confirm show value
operations check box on the General tab to turn on or off the display of the
confirmation dialog box that appears if you click Show Values when you define a
filter; then click OK.
3. From the Select features in drop-down list, select a feature class or query.
4. If you know SQL and the attribute you want to query, type the where clause in the
Filter box and skip to Step 10. Otherwise, click Filter to display the Filter dialog
box.
10-6
5. Select an attribute from the selected feature class and click the down arrow below the
Attributes box, or double click an attribute.
Note: MGE features use the MSLINK value as an identifier. Features in an MGE
warehouse that have graphics but no attributes do not have an MSLINK value. When a
query is performed on such features, the MGE data server assigns them MSLINK
values that are numbered sequentially in the order that they are encountered—that is,
sequentially within each category in map-table order. The first MSLINK number
assigned is 16777217.
When you view attributes in a data window or on the Filter dialog box, non-attributed
features will have the MSLINK identifier assigned by the MGE data server, whereas
attributed features will have an MSLINK, a MAPID, and other attributes.
6. Select an operator. If you select an operator from the drop-down list, you must click
the down arrow to make it appear in the Filter box.
7. To see the list of values in the selected attribute, click Show Values.
If you checked Confirm show value operations on the Options dialog box, the
confirmation message appears.
8. Type a value for the attribute in the Filter box, or select one from the list of values and
click the down arrow, or double click an attribute. You can also type a value in the
Values box.
9. Verify that the SQL statement in the Filter box is correct, and click OK.
Note: For date and time queries—and possibly others—on MGE and MGDM
connections, you may have to manually edit the SQL text on the Filter dialog box to
issue a successful query. This is due to the varying SQL dialects of the various
available ODBC drivers.
10-7
10. On the Attribute Query dialog box, accept or override the default query name, and
optionally type a query description.
11. Verify that the Display query in map window check box is selected, and change in
the Map window name field, if appropriate, the map window in which to display the
query results.
OR
To not display the query results in a map window, uncheck the Display query in map
window check box.
13. Verify that the Display query in data window box is checked, and change in the Data
window name field, if appropriate, the data window in which to display the query
results.
OR
To not display the query results in a data window, uncheck the Display query in data
window box.
14. To display the query, click OK.
The query is displayed in accordance with the query options you set.
See the ODBC documentation for instructions.
Defining Spatial Queries

A spatial query defines the relationship between two feature classes using a spatial
operator. The spatial operator forms the that clause of the query statement.
For example in the following query, the word touch is the spatial operator because it
defines the relationship between the two-lane highways and interstate highways:
Find all two-lane highways that touch interstate highways;
The Not qualifier, if checked on the Spatial Query dialog box, simply returns the elements
from the first/top input feature class or query that were not found by the selected operator.
For best results when using Spatial Query, you should create and apply connection filters
to spatially constrain the search area. The spatial query alone does not spatially constrain
the search area of the subject feature class.
See “Working with Spatial Filters” in this chapter.
Available Spatial Operators

The available spatial operators and example graphics of their results areas follows:
10-8
Touch returns features that touch the defined features in any way—meeting, overlapping,
containing, or being contained by.
touch with the Not qualifier
Contain returns features that surround defined features. Contained features can touch but
not overlap the borders of the surrounding features. Points cannot contain other features.
contain with the Not qualifier
Are contained by returns features that fall completely within the defined features.
Contained features can touch but not overlap the borders of the surrounding features.
are contained by with the Not qualifier
Entirely contain returns features that surround defined features. Contained features
cannot touch or overlap the borders of the surrounding features. Points cannot entirely
contain other features.
entirely contain with the Not qualifier
Are entirely contained by returns features that fall completely within the defined features.
Contained features cannot touch or overlap the borders of the surrounding features.
are entirely contained by with the Not qualifier
Overlap returns features that overlap the defined features.

overlap with the Not qualifier
10-9
Meet returns features that fall next to the defined features, touching without overlapping.
meet with the Not qualifier
Are spatially equal returns features that occupy the same space and location. Features
must be of the same type to be spatially equal.
are spatially equal with the Not qualifier
Are within distance of returns features having any part located within the specified
distance of the defined features. If either the starting or ending point of a linear feature, for
example, falls within the specified distance, it is returned.
are within distance of with the Not qualifier
Note: The spatial operators used by Spatial Query are different from the Oracle Spatial
Cartridge specific operators used by the Native Query command when querying an Oracle
warehouse.
Spatial Queries and Tolerance

Spatial queries are now executed with a consistent millimeter-level tolerance in processing
geometry. Often, when calculating or storing geometries using floating-point accuracy,
coordinates that are supposed to be identical may in fact vary slightly.
This tolerance is used in determining coordinate equivalence, that is, vertices that are
within 0.1 millimeter of one another on the ground are assumed to be equal when
executing spatial queries.
To define a spatial or combined query:

1. Select Analysis > Spatial Query.
10-10
3. Optional: To create a combined query, define an attribute filter for either or both
feature classes or queries. Click Filter to display the Filter dialog box; then define the
appropriate attribute filter.
4. Accept the default spatial operator for the that clause or override it by selecting another
operator from the That drop-down list.
5. Accept or override the default not qualifier by checking or unchecking the Not check
box.
6. If you selected the are within distance of operator in Step 5, type the zoning distance
in the Distance field, and select the appropriate units from the Units drop-down list.
7. Select the second feature class or query from the Features in drop-down list.
8. Optional: Define an attribute filter as described in Step 4.
9. Accept or override the default query name, and optionally type a query description.
query results.
OR
To not display the query results in a map window, uncheck the Display query in map
window check box.
window name field, if appropriate, the data window in which to display the query
results.
OR
10-11
To not display the query results in a data window, uncheck the Display query in data
window box.
The query is displayed in accordance with the query options you set.
Defining Spatial Intersections

Spatial Intersection allows you to perform a spatial overlay on two feature classes or
queries to find the intersecting areas, or areas of coincidence. The spatial operators
available for this command are touch, contain, are contained by, entirely contain, are
entirely contained by, overlap, meet, and are spatially equal. After you choose the two
sets of input features to intersect and the type of spatial operation to perform, this
command outputs the results as a new query.
The results include the geometry for the points, lines, and areas of spatial coincidence as
well as the attributes for each pair of spatially intersecting features, that is, a spatial join.
The features can be point, line, area, or combinations of these feature types. You can
output the resultant new spatial intersection to a map window and/or data window.
Before Spatial Intersection After Spatial Intersection
In addition, you can set the style for the map window for optimum display results. One can
think of this command as producing results that are the opposite of those produced by
Spatial Difference as shown in the following two figures from the delivered Madison
County, Alabama sample data set.
Note: Attribute filtered spatial queries cannot be run against the results of a Spatial
Intersection query unless the results are first output to a feature class.
Map features before using Spatial Intersection:
10-12
Spatial Intersection results with the touch operator showing the intersection of the Major
Water Polygons features and the Parks features:
The following are two example workflows:
10-13
• Spatially intersect roads to districts; then use the spatial intersected roads to input to
Aggregation or Analytical Merge for total mileage of roads X district.
• Spatially intersect address points with voting districts to combine the attributes of both
the address and the district. The result can then be output to a warehouse such as
Access and used with Report Wizard to run a report on the addresses X district.
To use spatial intersection:

1. Select Analysis > Spatial Intersection.
2. Select the first feature class from the top Features in drop-down list.
3. Optional: Click Filter to define an attribute filter for the selected feature class on the
attribute filter dialog box.
4. Optional: Change the default spatial operator in the That drop-down list; then verify
the operator in the illustration below the operator field.
5. Select the second feature class from the bottom Features in drop-down list.
7. Optional: Change the default value in the Query name field.
8. Optional: Type a query description in the Description field.
9. Verify that the Display intersection in map window check box is selected, and
change in the Map window name field, if appropriate, the default active map window
in which to display the new spatial intersection.
OR
To not display the new spatial intersection in a map window, uncheck the Display
intersection in map window check box.
10-14
11. Verify that the Display intersection in data window box is checked, and change in
the Data window name field, if appropriate, the default new data window in which to
display the new spatial intersection.
OR
To not display the nongraphic attributes of the new spatial intersection in a data
window, uncheck the Display intersection in data window check box.
12. Click OK to generate and to display the new spatial intersection in the specified map
window and/or data window.
Note: You may need to adjust the style for better viewing.
See “Defining Spatial Queries” in this chapter for a description of the spatial
operators.
See “Defining Attribute-Filter Queries” in this chapter.
Defining Spatial Differences

Spatial Difference allows you to perform spatial masking, that is, to perform a difference
operation on two sets of areas to produce resultant geometries. You can output the
resultant new spatial difference to a map window and/or data window. In addition, you can
set the style for the map window for optimum display results.
This command takes as input two area feature classes or queries, the features to be masked
or cropped (the from-feature), and the features to be used as a mask (the subtract-feature).
After processing using the touch spatial operator, this command outputs the results as a
new query. This resultant geometry is calculated by removing all portions of each from-
feature that are overlaid by any subtract-feature. Thus, the output consists of any portion
of each from-feature not overlapped by the geometry of the subtract-feature. If a from-
feature is completely overlaid by the subtract-feature, the from-feature does not appear in
the output query.
The following cases are valid:

From-feature Subtract-feature Result
area area area or nothing
line area line or nothing
10-15
line line line or nothing

point area point or nothing
point line point or nothing
point point point or nothing
The following cases are not allowed as input:
From-feature Subtract-feature
area line
area point
line point
One can think of this command as producing results that are the opposite of those produced
by Spatial Intersection. Or, one can think of a cookie-cutter process, with the results
being the sheet of dough from which the cookies have been cut out, as shown in the
following example from the delivered Madison County, Alabama, sample dataset:
Map features before using Spatial Difference:
Spatial Difference results showing the difference of Major Water Polygons features and
the Parks features. The difference is shaded gray.
10-16
See “Defining Spatial Queries” in this chapter.
To use spatial difference:

1. Select Analysis > Spatial Difference.
2. Select the feature class to be masked from the From features in drop-down list.
4. Select the feature class to be used as a mask from the Subtract features in drop-down
list.
10-17

8. Verify that the Display difference in map window check box is selected, and change
in the Map window name field, if appropriate, the default active map window in
which to display the new spatial difference.
OR
To not display the new spatial difference in a map window, uncheck the Display
difference in map window check box.
10. Verify that the Display difference in data window box is checked, and change in the
Data window name field, if appropriate, the default new data window in which to
display the new spatial difference.
OR
To not display the nongraphic attributes of the new spatial difference in a data window,
uncheck the Display difference in data window check box.
11. Click OK to generate and to display the new spatial difference in the specified map
Note: You may need to adjust the style for better viewing.
Working with Native Queries

Native Query provides server-based native querying by performing a spatial query on an
Oracle data server and by performing a query on an MGSM data server to generate an
offset display. This allows you to take advantage of the particular capabilities of each data
server.
Native Query takes as input a connection to a warehouse that supports native-query
capability and an additional set of inputs specific to that type of connection. The command
then appends the query to the query folder and optionally outputs the resultant query to a
map window and/or data window. You can adjust the display style for optimum viewing
in the map window.
Defining Native Queries against an Oracle Warehouse

When working with a connection to an Oracle database (with Spatial Cartridge), this
command allows you to select the feature classes to query and an Oracle Spatial Cartridge
spatial operator. The query is executed on the Oracle database, taking full advantage of the
10-18
Spatial Cartridge engine and the speed of the hardware containing the database. The
performance of this command depends on how well you tune the Oracle database and the
Spatial Cartridge. Performance also depends on the nature of your query, for example, if
your query retrieves a small number of feature instances out of a large data set.
A spatial query defines the relationship between two feature classes using a spatial
operator. The spatial operator forms the that clause of the query statement.
The following spatial operators are available:
Touch—The boundaries intersect but the interiors do not.
Disjoint —The boundaries and interiors do not intersect.
Overlap Boundary Disjoint—The interior of one object

intersects the boundary and interior of the other object, but the
two do not intersect. This relation occurs, for example, when a
line originates outside a polygon and ends inside that polygon.
Overlap Boundary Intersect—The boundaries and interiors
of the two objects intersect.
Equal—The two objects have the same boundary and interior.
Contains—The interior and boundary of one object are

completely contained in the interior of the other.
Inside—The opposite of Contains. A Inside B implies B

Contains A.
Covers—The interior of one object is completely contained in

the interior of the other, and their boundaries intersect.
Covered By—The opposite of Covers. A Covered By B

implies B Covers A.
10-19
Any Interact—The objects are non-disjoint. This is the

default operator unless there is a valid session preference.
Note: The spatial operators used by Native Query when querying an Oracle warehouse
are specific to Oracle Spatial Cartridge and are different from those used by the Spatial
Query command.
To define an Oracle native query:

1. Select Analysis > Native Query.
2. From the Connection drop-down list, select an Oracle connection.

3. From the Select features in drop-down list, select the feature class on which to query.
10-20
5. From the That drop-down list, select the appropriate spatial operator(s).
6. From the Features in drop-down list, select the appropriate constraining feature class.
7. Optional: Click Filter to define an attribute filter for the selected constraining feature
class on the attribute filter dialog box.
8. Accept the default query name, or type an appropriate name in the Query name field.
9. Optional: Type an appropriate query description in the Description field.
the Map window name field, if appropriate, the default active map window in which
to display the query results.
OR
To not display the query results in a map window, select the Display query in map
window check box to remove the checkmark.
window name field, if appropriate, the default new data window in which to display
the query results.
OR
To not display the nongraphic attributes of the query results in a data window, click the
Display query in data window box to remove the checkmark.
13. Click OK to generate and to display the native query results in the specified map
10-21
Defining Native Queries against an MGSM Warehouse

When working with a connection to an MGSM dataset, Native Query allows you to
perform a query against an MGSM warehouse and have the results of the query displayed
offset from the original centerline. These queries can be from a single distributed attribute
table or from an overlay of multiple distributed attribute tables using the intersect and
difference overlay operators. The offset display can be a fixed offset, a scaled offset, or a
combination.
It is important to note that the offset display definition does not persist, that is, it is not
maintained beyond the initial definition of the query. If you save a GeoWorkspace with an
offset query, the next time you open the GeoWorkspace, the offset defined for the query is
lost, and the display reverts to the centerline of the control network as defined in the
coordinate file. Although the offset definition is not maintained, the offset geometry in the
query is maintained as long as the MGSM connection is open in the current session.
The software also allows you to edit a query to redefine the offset. When you bring up the
query in the Query Properties dialog box (even if the query is currently displayed with an
offset), the query has no offset defined for it because the offset display definition is not
maintained. If you define a native query with an offset and then edit the query through the
New Query command, the offset is not known to the query. When you edit an MGSM
native query, the offset definition reverts to zero, and you have to redefine the offset.
See “Editing Queries” and “Defining Attribute-Filter Queries” in this chapter.
Offset Display Concepts

Offsets let you display distributed attributes to the left or right of the Network Linear
Feature centerline. Offsets can be defined as fixed, scaled, or a combination of fixed and
scaled. A fixed offset is used to display the distributed attributes at a constant offset
distance from the centerline for all segments. A scaled offset is a ratio of a stored database
value that is used to display the distributed attributes at a scaled offset distance from the
centerline. The fixed offset value and the size of the scaled offset value are defined in
paper working units.
For example, you could define a fixed offset of 50 feet and a scaled offset of 25 feet
multiplied by the value stored in the LaneNumber field in the distributed attribute table. If
the LaneNumber was equal to two for a a particular segment, the display of that segment
would be offset 100 feet (50 + 25 * 2).
Offsetting to the Right or Left

Offsets can be positioned to the right or left of the centerline by typing a positive number
or a negative number, respectively, in the Offset field. If you use a fixed offset that is a
positive number, the offset is to the right of the centerline when you are looking in the
10-22
positive direction of a highway (the direction of increasing distance). If you use a fixed
offset that is a negative number, the offset is to the left of the centerline when you are
looking in the positive direction of a highway (the direction of increasing distance).
Scaled offsets are different because the offset display is depends on the value used in the
database offset column (Scale attribute). If you use a scaled offset size that is positive
and the offset value in the database is also positive, the offset is displayed on the right of
the centerline. If your database offset value is negative, the offset is displayed to the left of
the centerline. However, if you use a scaled offset size that is negative and the database
offset value is positive, then the offset is displayed to the left of the centerline. If your
database offset value is negative, the offset is displayed to the right of the centerline.
The command retrieves the scale attribute value from the database and multiplies it by the
scale factor to obtain the offset distance in the specified unit of measure. The scale factor is
the server the command applies to the value of the scale attribute of the segment.
To define an MGSM native query:

2. From the Connection drop-down list of the Native Query dialog box, select the
MGSM connection that supports native queries.
3. From the Select features in drop-down list, select the feature class on which to query.
4. Optional: Click Filter to define an attribute filter and/or an overlay filter for the
selected feature class on the Filter dialog box.
5. Select the appropriate offset type(s), Fixed offset and/or Scaled offset.
6. Enter the appropriate corresponding offset parameters.
10-23
the Map window name field, if appropriate, the default active map window in which
to display the query results.
OR
To not display the query results in a map window, select the Display query in map
window name field, if appropriate, the default new data window in which to display
the query results.
OR
To not display the nongraphic attributes of the query results in a data window, click the
Display query in data window box to remove the checkmark.
12. Click OK to generate and to display the native query results in the specified map
Defining Linear Network Queries

If you are using an MGSM warehouse, you can define the search conditions for a linear
network query by combining sets of segments in distributed attribute tables with overlay
operators. The distributed attribute values that the query returns are displayed as point or
linear segments along their respective network linear features. These new segments are
created dynamically when you display the query.
The following overlay operators are available:
• The intersect operator searches for segments that overlap.
For example, a query for accidents that intersect construction returns only segments
containing accidents where there is also construction.
• The difference operator searches for segments that differ.
10-24
For example, a query for accidents that differ from construction returns only segments
containing accidents where there is no construction.
You can also apply attribute filters and spatial queries to linear network queries. For
example, you can build a query to find roads that intersect construction and touch
wetlands where geese have nests.
The linear network query finds roads that intersect construction.

• The spatial query limits the search for roads that intersect construction to those that
touch wetlands.
• The attribute filter limits the search for roads that intersect construction to those where
geese have nests.
The procedures for creating a linear network query are the same as for any other query,
except that you can include intersect and difference overlay operators.
To define a linear network query:

4. Click Filter.
5. Select an attribute, and click the down arrow below the Attributes box.
6. Select an operator and, if necessary, click the down arrow in the Operators box.
7. To see the list of values in the selected attribute, click Show Values.
8. Type or select a value, and click the down arrow below the Values box.
9. Click Add Overlay to display the Add Overlay dialog box.
10-25
Note: The Add Overlay and Remove Overlay buttons only appear on the Filter
dialog box if you are querying a feature class from an MGSM warehouse.
10. Select an overlay operator from the drop-down list.

11. Select a distributed attribute table.
12. Click OK.
13. On the overlay tab, select an attribute, and click the down arrow below the Attributes
box.
14. Select an operator and, if necessary, click the down arrow in the Operators box.
15. To see the list of values, click Show Values.
16. Type or select a value, and click the down arrow below the Values box.
17. To add an additional overlay, click Add Overlay, and repeat Steps 9 - 15.
Note: Clicking Remove Overlay removes the overlay displayed on the active tab,
thereby removing that portion of the query statement.
18. Click OK.

19. On the Native Query dialog box, type a name and optional description for the query.
Manipulating Queries
The software provides various commands that allow you to manipulate queries in order to
obtain the exact results you need for each specific condition of your workflow.
10-26
Displaying Queries
In general, a query is displayed automatically when you build it. If you build a query
without displaying it—to use in another query or for creating a thematic display, for
example—there are many ways to display it later.
To display a query:
Add the query to the legend. This displays queries in the
active map window and ignores query option settings.
When a data window is active, select Data > Change

Contents, and select the query.
Open a new data window, selecting the query as the data
you want to display.
Or, use the Analysis > Queries command to display a query. This command also lets you
edit, delete, and unload queries. The icon beside each query name on the Queries dialog
box indicates information about the query, including its status and geometry type (if
available), as follows:
Closed query Nongraphic
AnySpatial Point
Areas Graphics Text
Image Unknown, graphic type cannot be determined
Line Invalid, query cannot be opened
Or, use the following procedure:
1. Select Analysis > Queries.
10-27
Note: This dialog box is resizable for better viewing of long query names.
Furthermore, you can use standard Microsoft procedures for multiple selections using
CTRL and SHIFT.
2. From the Queries dialog box, select the query you want to display, and click Display.
3. On the Display Query dialog box, select a window in which to display the query.
4. To display the query in a new window, type a name in the appropriate window name
field. To display the query in an open window, select it by name from the drop-down
list.
5. To change the style of a query display in a map window, click Style, define the style,
and click OK on the Style dialog box. The style of the query depends on the feature
class type returned by the query.
6. Click OK.
Editing Queries
Once a query has been defined, you can change everything except the feature class or
query on which it is built. If you change a query name, the new name is not changed in
any existing legend-entry titles, data-view captions, or dependent query names. Editing a
query that is used as input to other queries may affect the other queries.
If a feature class or query that is used in a query changes, the dependent query is also
affected:
• Changes to the definition of a feature class or query can invalidate a dependent query.
If the dependent query is an attribute-filter query, its display will be removed from the
map window. Data windows associated with the feature class will not contain any data
if the dependent query is rendered invalid by the change.
• If you close the connection to a warehouse containing a feature class on which a query
is dependent, the data will be removed from the display, but you will have to edit the
legend to remove the entry.
10-28
To edit a query:
2. On the Queries dialog box, select the query you want to edit and click Properties.
The type of query selected determines what is displayed on the Query Properties
dialog box.
For example, if you selected a query that is a label, the Query Properties dialog box
appears with the options that were available on the Join or the Label dialog box.
Note: The Query Properties dialog box has a different appearance with queries
generated from the following commands: Analyze Geometry, Attribute Filter,
Geocode Addresses, Geocode Coordinates, Join, Label, Native Query, Spatial
Difference, Spatial Intersection, and Spatial Query. This dialog box also varies if
the query was created with Spatial Query in GeoMedia version 4.0 and earlier or in
GeoMedia version 4.0 Service Pack 1.
See GeoMedia Help for more information.
3. Edit the items available for the specific selected query.

For example you can edit the query name or description, or click Filter to edit the
attribute filter for an attribute-filter query.
All existing displays of the edited query and any other query built upon that query will
be updated.
4. Click OK to accept the changes.
5. To create a new display for the query, click Display to bring up the Display Query
dialog box.
Deleting Queries
When you delete a query, you are deleting the query definition but not the data associated
with the query. Similarly, if you delete a legend entry for a query, you are removing the
display of the query in the map window but not deleting the query itself. Deleting a query
from the queries collection does not remove it or its name from legends, the data window,
use from other queries, or even the treeview on the Queries dialog box. You can delete
single or multiple queries.
To delete a query:
2. On the Queries dialog box, select the query or queries you want to delete and click
Delete.
10-29
Unloading Queries
Unload lets you unload the data associated with one or more queries and thus free up
memory by closing the selected queries.
To unload a query:
2. On the Queries dialog box, select the query or queries you want to unload; then click
Unload.
The bitmaps of the selected queries are updated to reflect the new unloaded status.
Working with Spatial Filters

To limit the geographical area and thus the number of features that can appear in the map
window, you can define a spatial filter in the GeoWorkspace and apply it to data in the
GeoWorkspace with the Spatial Filter command. Depending on the size of your data set,
spatial filters can save a great deal of processing time.
Spatial filters play two important roles in the GeoMedia system, often with two different
use patterns:
1. They are used to constrain data to be loaded, thus improving performance and
scalability. For this you would generally use a coarse spatial operator and a crude
spatial filter geometry, for example, a rectangle.
2. They are used to identify areas of interest/study for purposes of focused analysis. For
this you would generally use a more refined spatial operator, for example, inside, and a
more complex spatial filter geometry, for example, an actual area feature such as a
political state or natural resources zone.
This command performs GeoWorkspace-level spatial filtering by setting the spatial filter
and operator on all features and queries, including Geocode queries in the GeoWorkspace.
There can be only one active spatial filter definition at a time for the entire GeoWorkspace,
so setting or changing the spatial filter simply sets the geographic scope of all operations in
the GeoWorkspace. You can access this command from the Warehouse menu when you
have either an active map window or an active data window.
For best results when using the Spatial Query command, you should create and apply
filters to spatially constrain the search area. The spatial query alone does not spatially
constrain the search area of the subject feature class.
See “Defining Spatial Queries” in this chapter.
The Spatial Filter command lets you perform the following:
• Define filter geometry and perform spatial filtering at the GeoWorkspace level.
• Select filter options.
10-30
• Set the active filter to the map window.

• Use and manage named spatial filters.
Spatial Filter lets you perform all of these tasks though the Spatial Filter dockable
control, which puts filtering at your fingertips.
This dockable control displays the name of the currently active spatial filter (if any) in a
read-only field and contains command buttons for defining and managing spatial filters, as
discussed in the following sections. This control is persistable. Thus, if you save a
GeoWorkspace with the control hidden, when you next open this GeoWorkspace, the
control is not displayed. To display the control again, you must select Warehouse >
Spatial Filter, or select Spatial Filter from the right mouse menu.
Defining Spatial Filters

The flexibility of this command lets you define the filter geometry by the various following
methods:
• By placing a fence, which can be rectangular, polygonal, or circular.
• By selecting a reference feature by name from a feature class area, or by compound or
raster geometry type.
• By having area, compound, or image features in a select set.
• By using the active map window extent as filter geometry.
• By choosing not to have a spatial filter.
• By applying an existing spatial filter definition.
When you define a filter through any of these methods (except the last one), the software
automatically assigns a default name, displayed on the Spatial Filter dockable control,
based on the definition method, for example. You can later rename the filter through the
Named Spatial Filter command.
See “Named Spatial Filters” later in this section.
10-31
The default spatial filter names are as follows:

Filter Type Default Filter Name
Named Spatial Filter <actual name of spatial filter>
Select Reference Features Selected Reference Feature Filter
Select Set Select Set Filter
Active Map Window Extent Map Window Extent Filter
Rectangular Fence Rectangular Fence Filter
Polygonal Fence Polygonal Fence Filter
Circular Fence Circular Fence Filter
Remove Filter No Active Filter
By Placing a Fence
You can define a spatial filter by simply following the standard digitizing prompts to place
one of the following fence types in the active map window:
• Rectangular Fence – (Rectangular Fence Filter)
• Polygonal Fence – (Polygonal Fence Filter)
• Circular Fence – (Circular Fence Filter)
By Selecting Reference Features

You can use Select Reference Features (Selected Reference Feature Filter) to define a
spatial filter by selecting one or more reference features by name from a feature class of
area, compound, or raster geometry type whose geometry will be used as a spatial filter,
using the following dialog box. Spatial filter reference features are designated through the
Spatial Filter Reference Features command.
See “Designating Spatial Filter Reference Features” later in this section.
10-32
This method is similar in to filtering by select set, but lets you select a reference feature
instance by name attribute. This method is thus a flexible alternative to named spatial
filters, effectively allowing any named reference feature instance to serve as a spatial filter.
This permits the straightforward creation of attributed spatial filtering feature classes,
which are easier to manage than named spatial filters.
You first select the reference feature class from the list of reference feature classes. You
can only select features of type area or compound, or image geometry. This selection then
enables selection of an attribute from an alphabetical list of attribute names of the selected
feature class. After selecting the appropriate attribute, you display a list of the features to
use as a spatial filter. The command then creates the filter geometry and performs the
filtering. You can select multiple items, and the merged geometry of the selected reference
features is displayed in the active map window.
To create the final filter geometry, feature geometries that are not areas (for example, linear
or point geometries from a compound feature class) are first discarded. Then if the number
of selected feature instances is more than one, a single geometry is created by merging the
remaining feature instances’ geometries. In case the final geometry (single or merged)
does not contain area geometries, the command displays an error message.
By Using a Select Set

You can define a spatial filter by using a select set (Select Set Filter) created by any type of
selection you choose to use (click, fence drag in map window, data window, and so forth).
The bounding polygon of image features may be used as a spatial filter with this method.
The command creates the filter geometry from the select set and performs the filtering. All
select set object types are supported. To create the final filter geometry, feature geometries
that are not areas or images are first discarded. Then if the number of geometries
remaining is more than one, a single geometry is created by merging the remaining
geometries in the select set. In case the final geometry (single or merged) does not contain
area geometries, the command displays an error message.
By Using the Active Map Window Extent

You can define a spatial filter by simply using the active map window extent (Map
Window Extent Filter). Using this command when a map window is active performs
filtering by taking the current map window extent as the filter geometry for the filter. No
further inputs are required when using this method. The filter is automatically applied to
all existing feature classes and queries in the GeoWorkspace.
By Not Using a Filter or By Applying an Existing Filter

You can also define a spatial filter by choosing not to have a spatial filter (No Active
Filter), that is, removing any existing filter applied to the GeoWorkspace through the
Remove Filter command. Finally, you can define a spatial filter by applying an existing
spatial filter through the Named Spatial Filters command.
10-33
See “Managing Spatial Filters” later in this section.
Defining Spatial Filter Workflows

The following workflows show the procedures for defining spatial filters by the various
methods discussed.
To define a spatial filter by selected reference features:

1. Select Warehouse > Spatial Filter.
2. Click Select Reference Features on the dockable control.
3. Select the appropriate reference feature from the Select features from treeview.
4. Select the appropriate Feature name attribute from the drop-down list.
5. Click Show Values.
10-34
6. Select the appropriate attribute value(s) from the Features to use as spatial filter list;
then click OK.
Note: The Features to use as spatial filter list supports multiple selection.
The filter geometry is created, the dialog box is dismissed, and filtering is performed.
Merged geometry of the selected features is displayed in the active map window.
To define a spatial filter by select set:

1. Create a select set of the features needed for your workflow.
3. Click Select Set on the dockable control.
Filter geometry is created from the select set, and filtering is performed.
To define a spatial filter by active map window extent:

1. Adjust the map window so that it displays the data needed for your workflow
3. Click Active Map Window Extent on the dockable control.
Filter geometry is created from the active map window extent, and filtering is performed.
To define a spatial filter by fence:

2. Click Rectangular Fence on the dockable control; then draw a rectangular fence to
define the filter area.
OR
10-35
Click Polygonal Fence on the dockable control; then draw a polygonal fence to define
the filter area.
OR
Click Circular Fence on the dockable control; then draw a circular fence to define the
filter area.
Filter geometry is created from the digitized fence, and filtering is performed.
Managing Spatial Filters

After you have defined spatial filters, you can manage these filters by using the following
commands accessed from the Spatial Filter dockable control:
• Spatial Filter Options • Fit Spatial Filter
• Named Spatial Filters • Remove Filter
Spatial Filter Options

When you first define a spatial filter, it takes the default filter options. However, you can
easily change these to meet your specific workflow needs through the Spatial Filter
Options. These options let you control the behavior of spatial filtering by setting the
spatial operator, filter geometry, map window display and fit, and display style, using the
following dialog box, which shows the default options:
Note: Warehouse > Export to commands always honor the default spatial filter whether
or not the feature(s) have been previously referenced by the GeoWorkspace.
You can choose from the following available spatial operators:

Inside (the default)—Lets you access only data that is contained either entirely inside, or
inside and sharing part of the boundary of, your spatial filter geometry.
10-36
Entirely Inside—Lets you access only data that falls completely within the boundaries of
your spatial filter geometry.
No spatial filter applied Inside Entirely Inside
Coarse Overlap—Lets you access all data inside or overlapping the boundaries of your
filter, but it may also return some additional features. The purpose of this operator is to
allow the data server to quickly and efficiently return data according to its internal spatial
indexing system, without doing individual geometry comparisons against the boundaries of
your spatial filter geometry. This processing varies with server efficiency and data
complexity.
Overlap—Lets you access any feature that falls within or touches the boundaries of your
spatial filter geometry.
10-37
The Coarse Overlap spatial operator is available for Oracle, Access, MGDM, and SQL
data servers. If you choose this spatial operator with any other data server, it automatically
reverts to the Overlap spatial operator.
Each database has a different indexing system, so the spatial filtering results may vary
drastically. The Access data server employs a Quad-Tree algorithm for its spatial
indexing. When applying a spatial filter with the Coarse Overlap spatial operator to data
in an Access warehouse, the results returned include all features overlapping the spatial
filter boundary, and any features that lie on certain Quad-Tree boundaries. This often
includes strips of features that are at some distance from the spatial filter boundary,
particularly for linear and areal features.
The Oracle data server generally employs an R-Tree algorithm for its spatial indexing.
Oracle uses a two-pass filtering method, and Coarse Overlap is always used as the first
pass filter. The Coarse Overlap filter always provides the best performance in an Oracle
environment.
Spatial Filter Options also lets you choose to filter the geometry by using the minimum
bounding rectangle (MBR) of the defined geometry, the Geometry extent (MBR), which
is faster because filtering is not unnecessarily bogged down by very complex area
definitions, or by using on the default actual defined geometry (Actual geometry), which
is more precise.
This command also gives you the option of fitting (auto fit) the filter with the MBR value
of the active spatial filter, with a margin of 5% in the map window of your choice from all
those in the GeoWorkspace (Automatically fit filter in check box, off by default). And
you can optionally display the currently active spatial filter in the active map window at all
times (Display filter on by default). Finally, you can change the area style used to display
the active filter in the active map window through the Select Style dialog box.
To define spatial filter options:

2. Click Spatial Filter Options on the dockable control.
10-38
3. Select the appropriate Spatial operator from the drop-down list.

4. Select the appropriate Filter by option.
5. Optional: Check the Automatically fit filter in check box; then select the appropriate
item from the Map window drop-down list.
6. Optional: Uncheck the Display filter check box.
7. Optional: Click Style to change the style on the Select Style dialog box.
8. Click OK to dismiss the Spatial Filter Options dialog box.
Fit Spatial Filter

Fit Spatial Filter lets you easily fit the active map window with the minimum bounding
rectangle (MBR) value of the currently active filter, with a margin of 5%.
Remove Filter
Remove Filter (No Active Filter) simply removes the existing active named spatial filter
with a single click. The active filter can be a user-named filter or a system-defined filter.
Named Spatial Filters

Named Spatial Filters lets you choose an existing named spatial filter as the active filter,
rename the active filter for later use, and delete previously named filters, using the
following dialog box.
This dialog box displays the currently active spatial filter name in the Active filter field, in
the same manner as the dockable control. This field is always enabled, locked, and grayed
to indicate it is read-only.
Also displayed are the names of all the GeoWorkspace spatial filters, except the active
filter, in the Named filters list. The default spatial filter name is SpatialFilter<n>, where
n is a number determined at runtime to guarantee uniqueness. You can select a filter from
this list to perform filtering with the geometry and spatial operator of the selected item by
clicking Apply or double clicking on the item, and the filter definitions of the selected
10-39
items are displayed on the active map window. The Filter by geometry extent and
Spatial operator settings on the Spatial Filter Options dialog box are ignored.
You can change the name of a filter by selecting it from the list, clicking Name, and then
typing a new name on the Name dialog box. The Name button, however, is only enabled
if there is an active spatial filter that is not a user-named spatial filter. Thus, only system-
defined filters can be named and stored in the spatial filters collection. Also, you can never
rename a named spatial filter. This adds the active spatial filter definition to the filter list
with the name specified, and with the spatial operator currently defined for the command.
The filter geometry added is either the actual active filter geometry or the MBR of the
active filter geometry, according to the Filter by geometry extent setting from the Spatial
Filter Options dialog box.
You can easily delete spatial filters by simply selecting one or more names from the list of
named filters, and then clicking Delete. Deleting a spatial filter does not affect any
existing legend entries, data windows, or queries.
To manage spatial filters:

2. Click Named Spatial Filters on the dockable control.
3. To apply an existing filter, select a name from the Named filters list; then click Apply.
OR
Double click a filter name.
Filtering is performed with the filter geometry and spatial operator of the selected filter.
4. To rename the active filter (not a named spatial filter), click Name.
10-40
5. Type the new name in the Name field; then click OK.
6. To delete a filter, select the name(s) from the Named filters list; then click Delete.
Designating Spatial Filter Reference Features

Spatial Filter Reference Features lets you designate feature classes that will not be
subject to spatial filtering. These spatial filter reference features provide you with a visual
reference system for defining spatial filters. You can select a set of individual feature
classes from any number of warehouse connections, rather than a single, entire connection.
When a feature class is designated as containing spatial filter reference features, it plays
that role in addition to its routine role as a spatially-filtered feature class. It is available in
both filtered and unfiltered form. You can thus select the unfiltered form from the
Reference Feature node for use with other commands, for example Add Legend Entries
and Attribute Query.
To designate spatial reference features, you first select a connection to display the
corresponding feature classes from which you select those you want to designate. You
cannot designate nongraphic feature classes or queries as spatial filter reference features.
Spatial filtering is inherently performed through data servers, while queries inherit spatial
filtering through the filtering of their input data. However, you can create queries from
reference features, which yields essentially the same effect.
It is easy to identify all feature classes within a connection as being spatial filter reference
features. However, any feature classes subsequently added to the connection are not
automatically considered to be reference features. In other words, it is the feature classes
within the connection, not the connection itself, which are so designated.
Once defined, the reference features appear in treeviews across the product in the
commands, for example Attribute Queries and Join, and controls to support reference
features. Reference features are thus displayed in the treeviews along with all the
connections, queries, and categories information, If, however, reference features have not
been defined, no empty Reference Features node is displayed by other commands.
After designating your reference features, you would typically define a corresponding
spatial filter using the Select Reference Features command, as in the following workflow.
To designate spatial filter reference features:

1. Select Warehouse > Spatial Filter Reference Features.
10-41
2. Select the appropriate connection.

3. Check the appropriate Feature classes check box(es); then click OK.
All the selected feature classes are set as reference features. Any unselected feature
classes that were previously reference features are reset as non-reference features.
Note: If a connection node is checked/unchecked, all the feature classes available in the
connection are checked/unchecked.
4. Click Select Reference Features on the dockable control.

5. Select the States feature class from the Select Features from drop-down list.
6. Select STATE_NAME from the Feature name attribute drop-down list; then click Show
Values.
10-42
7. Select Alabama from as the feature to use as a spatial filter; then click OK to perform the
filtering.
Querying Graphics-Only Features in MGE and

MGSM
The MGE and MGSM data servers expect valid map ID values in attribute tables, which
means that the feature geometries actually exist in the design file identified by the map ID.
This allows the data servers to limit queries for geometry to the identified design file.
If a query on an MGE or MGSM warehouse includes graphics-only features (features that
have no associated attribute table) or if map IDs are not valid, the query could take a very
long time, depending on the number of design files that must be searched. This is because
the server has to search all design files allowed by the spatial filter.
See the “Creating Data Server .INI Files” topic in GeoMedia Help for setting the MAPID
IS RELIABLE keyword in the mge.ini file.
10-43
If a category contains design files for multiple feature types, then the MGE or MGSM
server will have to search design files that have no elements relevant to the query. So, if
you have multiple graphics-only features in a single category, a query will take longer than
if the features were separated into different categories. Furthermore, the MGDM server
uses additional memory when it must search for graphics-only features.
One way to improve the performance of queries on graphics-only features is to limit the
size of the categories. The best way, of course, is to clean up your MGE and MGSM data.
Working with Queued Edit

The Queued Edit command on the Tools menu lets you sequentially review selected items
for potential edit of the geometry and the non-graphical attributes of the located items.
Each item is thus presented in sequence, so you do not have to perform time-consuming
searches. Then as you review and/or fix each item, the queue is automatically updated.
Furthermore, if you fix an item in the data window, the solution is automatically reflected
in the map window and vice versa. You can use this command in two general workflows:
as a review and edit tool for an operator performing an operational task, and as a tool for
performing formal Quality Assurance/Quality Control tasks.
The review items located by this command may or may not have geometry, and they can
be of two kinds: standard review items available in the GeoWorkspace, that is, feature
classes, categories, and queries; and items in a previously created queue. A queue is a
special list of items selected for review, as generated by commands in GeoMedia Fusion
(for example, a queue of geometric anomalies produced by the Advanced Geometric
Validation >Advanced Validate Geometry command), PixelQue, Map Editor, or other
software, not by GeoMedia Professional. GeoMedia Professional currently does not have
any commands that generate queues. However, the process of locating and stepping
through selected items for review is similar for both standard review items and for queues.
When working with queues, nevertheless, the Queued Edit command has additional
capabilities, such as changing the status of queue items and creating subqueues. This
section describes the use of this command with standard items and with queues.
Note: The active queue may be closed by various actions. These include placing a spatial
filter in the GeoWorkspace, closing the connection containing the queue information, and
changing the attribute filter query if you are looking at a query through Queued Edit. If
this occurs, you need to re-open the queue to continue your workflow.
Dynamic and Static Queues

Queued Edit works with two types of queues, dynamic and static. In dynamic queues, if
you make changes to the original data, the queue updates to reflect the changes; and if you
make changes in the queue, the original data updates. For example, the number of items in
a validation queue decreases as the anomalies are reviewed and corrected. If a new
10-44
qualifying anomaly is created, a new item appears in the queue. Dynamic queues are
stored in the GeoWorkspace.
In static queues, if you make changes in the queue, the original data does not update. A
static queue is a snapshot of the original data; each item of the queue is maintained
independently. For example, the number of items in a validation static queue does not
decrease as the anomalies are corrected in the original data. Instead, the static queue
remains a record or snapshot of the problems found. Static queues are stored in the
warehouse.
Note: The dynamic and static queue concepts do not apply to the standard review items.
Looking at the Queued Edit User Interface

The Queued Edit command has three main interface components: the Queued Edit
dockable control, the Queued Edit Map Window, and the Queued Edit Data Window,
as seen in the following example.
Using the Queued Edit Dockable Control

Selecting Tools > Queued Edit opens the Queued Edit dockable control for selecting,
navigating, and managing standard review items and queues. Some non-GeoMedia
Professional commands automatically open this control when they create a queue.
10-45
In the following example, the queue is designated as a dynamic queue by the yellow icon
to the left of the queue name. A static queue is designated by a white icon.
You can use this control to select standard review items or a queue from the drop-down list
of feature classes, queries, categories, and queues available for review.
Immediately after you make a selection, by default the first item of the sequence is
displayed in the active Queued Edit Map Window and the active Queued Edit Data
Window (if displayed). However, if the selected queue has previously been active during
the session, the previously active item is remembered.
After displaying the first item you can perform the following management tasks:
• Navigate through the subsequent items • Set options for viewing the items
• Sort the items • Track the status of queue items
• Delete queue items by status • Delete queues
• Create subqueues • Show queue statistics
• Access additional options and commands to manipulate the standard review items and
queues
Navigating in Queued Edit

You can navigate through the standard review or queue items using the following control
options: Move First, Move Next, Move Current, Move Previous, and Move Last. Each
of these makes use of the appropriate view properties you set in the Queuing Options
dialog box, which is displayed by clicking the Options button on the control.
10-46
When the Queued Edit Data Window is present during a navigation (that is, a sequential
review of the selected items), this window is scrolled in such a way that the current item
(record) is shown as the first record in the visible data view grid, and the row selector
image points to this row.
Note: If you exit the GeoWorkspace while a queue is active, when you reopen the
GeoWorkspace, the queue is inactive until you reselect it.
The control provides circular queue navigation by default, where in navigating before
(beyond) the first (last) record moves to the last (first) record of the queue. When you
close a queue, the dockable control is cleared, and the review items are removed from the
Queued Edit Map Window legend. However, the Queued Edit Map Window and
Queued Edit Data Window remain open.
Reviewing and Updating the Status

The Status Review/Update field displays the status for the current queue item – for static
queues only, not for dynamic queues or standard review items. The status is generated by
the process that created the queue. You can change the status of the active queue item (for
example, from "Linked" to "Unlinked") by selecting a new value from the drop-down list.
When you change the value, the status is updated in the queue, and the queue advances to
the next item if you selected the Automatically advance when status changes check box
on the Queuing Options dialog box General tab.
Note: The Status Review/Update is disabled for queues generated by the GeoMedia
Fusion Advanced Geometric Validation > Validate Geometry command.)
Using the Queued Edit Map Window

The Queued Edit Map Window opens automatically when standard review items or a
queue is selected on the Queued Edit control or upon queue navigation. As seen in the
following example, this window contains two sections: the Queued Edit Map Window
legend on the left and the map display on the right. This map displays the graphic
attributes of the active review item. A legend entry is added to the Queued Edit Map
Window legend for each item geometry, and the current item is initially displayed in a
centered and fitted view in the Queued Edit Map Window.
10-47
The item graphics are displayed to the Queued Edit Map Window by placing each item
geometry in the Queued Edit Map Window legend. On initial creation, there is one
legend entry per geometry field identified, but you can add other feature classes or queries
to this legend. You can also change the order of item legend entries and style, and the
modified order and style is maintained upon a move next, move previous, move first, or
move last action in the sequence.
To customize the map, you can set options for defining an item locator and for viewing the
map window display on the Queuing Options dialog box, which is accessed by clicking
the Options button on the control.
Setting View Options

The View tab on the Queuing Options dialog box lets you define the view options. When
you zoom in, zoom out, or fit the view of an item in the Queued Edit Map Window, the
view adjusts according to these view options.
The Zoom In/Out and Fit current queue item buttons on the dockable control let you
control the map window view. They make use of the values on the View tab in the Zoom
factor field and the Fit and zoom out field, respectively. The appropriate view action is
based on the MBR of the current queued item as determined by the select set.
10-48
Optionally, you can let other map windows with the window properties of “center at
current scale” or “zoom and fit” to be honored by Queued Edit during navigation through
the review items. This works in the same way as when reviewing a query with the window
properties of center or zoom and fit enabled.
Note: The features or the geometry that make up the queued item are not required to be in
the legend of the other map windows for this to work as it does for a query.
The following example illustrates the view before selecting the Honor setting from Map
Window Properties during queue navigation check box.
The following example illustrates the view after selecting the check box during navigation,
with the Fit and zoom out map window property set to 500%.
Defining the Locator

The Locator tab on the Queuing Options dialog box lets you define the locator, which
consists of two graphical elements, the locator box and crosshairs. These two elements can
be displayed around the queued item to give a visual reference of the location of the item in
the Queued Edit Map Window and in other GeoMedia map windows. You can define
the style (color, line type, and line width) for the locator box and the crosshairs. The
default color is the GeoMedia highlight color.
10-49
Using the Queued Edit Data Window

The Queued Edit Data Window displays the nongraphic attributes of the active review
items. It does not display geometry attributes or spatial attributes.
The active row in this window indicates the item that is displayed in the Queued Edit
Map Window. If you change the active row in the data window, the map window view
moves to the location of that item, and the Queued Edit control shows the item number that
corresponds to the active row. You can sort the active items by attribute in ascending or
descending order through Additional Commands > Sort ascending/descending.
If you have a read-write warehouse connection, you can review and edit the features and
values in the Queued Edit Data Window. Any changes you make in the data window are
reflected in the Queued Edit Map Window and other map windows. In static queues, you
cannot delete rows from the data window. In dynamic queues, you may be able to delete
rows, depending on what command created the queue.
Displaying and Removing the Queued Edit Data Window

By clicking the Display/Remove Data Window button on the control, you can display the
Queued Edit Data Window when you select standard review items or a queue and also
remove the data window for the active items. If this toggle button is depressed and the data
window does not exist, a data window is created when standard review items or a queue is
made active. If you delete the window, the window is created the next time you advance in
10-50
the sequence of review items or make standard review items or a queue active. If the
button is raised and the data window exists, the window is deleted.
Using Queuing Options

You can set queuing options through the General tab on the Queuing Options dialog box,
which is displayed by clicking the Options button on the control. These options are
enabled when a GeoWorkspace is open, whether a queue is selected or not.
Show description box—Displays a description box on the control that contains an

optional description for each queue item. This option is for queues only.
Automatically advance when status changes—Advances the current queue item when
you change the status of a queue using the Status Review/Update field on the Queued Edit
control or the Queued Edit QuickStatus control. This field displays the current status
value and lets you update the status of the active queue item. This option is for queues
only.
Note: If the current queue item is deleted or removed from the queue, the next item
becomes current.
Add item to select set—Adds the graphic elements of the review items to a select set as
you navigate through the items. This option is for standard review items and for queues.
Clear Queuing Legend when queue closes—Clears all Queued Edit Map Window
legend entries when you close a queue. This option is for standard review items and for
queues.
Show number of items in a queue—Displays the number of located queue items next to
the corresponding name on the Queued Edit control. For dynamic queues from closed
connections, the number displays as (0). This option is for queues only.
10-51
Note: When this option is set, it may take longer for the queue name lists to display
because a count of each queue is being made. Therefore, when queues contain many items,
setting this option is not recommended.
Using Additional Commands

Clicking the Additional Commands button on the control displays a menu with the
following commands that let you manipulate queues according to your workflow. The
Sort ascending/descending commands also work with standard review items.
Note: Delete Queue, Create subqueue, and Show statistics are enabled when a
GeoWorkspace is open, whether a queue is selected or not.
Delete queue—Deletes one or more queues/subqueues in one operation according to your

selection on the Delete Queue dialog box. Deleting a queue also deletes its subqueues and
all associated metadata. This command is for queues only.
10-52
Create subqueue—Creates a subqueue for any queue through the Create Subqueues
dialog box. When you create a subqueue, it becomes the active queue. A subqueue is a
user-defined subset of a queue, that is, a view into a specific queue. You can create
subqueues for queues but not for subqueues. The items in the subqueue remain in the
parent queue. If you delete the parent queue, the subqueues are also deleted. Subqueues
are the same type of queue as parent queues. That is, if the parent queue is dynamic, the
subqueue is dynamic; if the parent queue is static, the subqueue is static. As with parent
queues, dynamic subqueues are designated on the Queued Edit control by a yellow icon,
static subqueues by a white icon.
To create a subqueue, you first select the parent queue and then name the subqueue. You
can create a subqueue based on one of two criteria: attribute filter (the default) or spatial
filter. If an attribute filter, you select the Attribute filter option and then click Define,
which displays the GeoMedia standard Attribute Filter dialog box for you to define an
attribute query filter. If a spatial filter, you select the Spatial filter option and then select a
filter from the corresponding drop-down list of spatial filters defined for the
GeoWorkspace. This command is for queues only.
Show statistics—Displays information about a queue and its items on the Show Statistics
dialog box. This information includes the name of the queue, the name of the process that
created the queue, and the number of items in the queue. If the Status field is defined for
the queue, the information includes the number of items with each defined status. If
subqueues have been created, the information includes the number of subqueues, the names
of the subqueues, and the number of items in the subqueues. You can also generate a
queue report that displays in your default text editor. This command is for queues only.
10-53
Delete queue items by status—Deletes all the items in the active queue that have a
particular status through the Delete Queue Items by Status dialog box. This command is
for queues only.
Queued Edit QuickStatus—Displays the Queued Edit QuickStatus dockable control,

which lets you quickly access and update the statuses of queue items by eliminating the
need to scroll through the drop-down list of statuses in the Status Review/Update field on
the Queued Edit control. This control is for use only with queues having a status defined.
A tooltip displays the text associated with each status number, which is the same text
displayed in the Status Review/Update field on the Queued Edit control. This command
is for queues only.
If you want to use this control to change a series of statuses, select the Automatically
advance when status changes option on the General tab of the Queuing Options dialog
box before beginning this procedure.
Sort ascending/descending—Sort the active review items or queue and the Queued Edit
Data Window in ascending or descending order by attribute. This command is for
standard review items and for queues.
10-54
Working with Searches

A search locates a point of interest in the map window. You can do this with a text string
to search the specified feature class, or with a query for features that have attribute values
that match this string. You can create and perform searches though two related commands,
Searches and Search. You use the Searches command to create, to change, and to
manage predefined searches. And, you use the Search command to perform these
predefined searches or to create and directly perform ad hoc searches. Both types of
searches locate the appropriate items and display them in the regular map window and the
Search Data Window, allowing you to then perform operations on the results according to
your workflow. This section discusses these two commands and how to create and to
perform the different types of searches.
Creating and Managing Predefined Searches

The Searches command lets you perform the following:
• Create predefined searches • Edit predefined search properties
• View predefined searches and their descriptions • Delete predefined searches
Selecting View > Searches displays the Searches dialog box containing a list of all
existing predefined searches in the active GeoWorkspace and, when one is selected, its
corresponding description.
10-55
To create a predefined search, click New to display the New Search dialog box on which
you define properties for the new search. A predefined, or named, search consists of
parameterized SQL filter string for which parameter values are supplied when you run the
Search command.
You first select the search input from the Search for features in treeview list. This list
contains the feature classes, queries, categories, and reference features from the current
GeoWorkspace. You can then define a search parameterized filter string, such as
CITY_NAME='[Name of city]', by typing the filter string directly into the Filter field or
through the Filter button. Clicking Filter displays the standard Filter dialog box, which
lets you select the appropriate column names and values for your filter.
With the filter text string, the command searches the specified feature class or query for
features that have attribute values that match this string.
You can create a filter string containing placeholders for values to be typed in the Search
command dockable control. For example, if the filter string is CITY_NAME='[Name of
city]', the Search command has a one-row, two-column grid on its control with the
Name of city prompt in the first column, for the value to be typed in the second column. If
the filter string requires value substitutions indicated by the brackets with a prompt such as
CITYNAME like '[Name of city]', the command makes the value substitutions in the
10-56
filter string before it performs the query. This is the usual case. If no substitutions are
required, the command uses the search filter string as it is.
Note: When creating a filter string for text attributes, the search definition uses single or
double quotes (depending on the database type of the warehouse) around the character.
For example: Attribute = '[prompt]'
However, when creating a filter string for numeric attributes, the numeric attribute should
not be enclosed in quotes. For example: Attribute = [prompt]
Finally, you define the search name and an optional search description; then click OK.
Once created, the searches are located in the Searches folder, which is integrated with the
library system for sharing predefined searches at the enterprise level or between users.
You can also view and edit existing searches by selecting a search on the Searches dialog
box and clicking Properties to display the Search Properties dialog box.
This dialog box displays the current properties of the selected search and lets you change
the input (feature class, query, category member, or reference feature), filter string, search
name, and search description.
10-57
Finally, selecting one or more searches on the Searches dialog box and clicking Delete
deletes the selected search(es).
Performing Searches
The Search command lets you perform a search to locate a point of interest in the regular
map window and display the results in the Search Data Window. For example, you can
easily navigate to Parcels by Parcel ID number through a search. You can type a text
string to search the specified feature class or query for features that have attribute values
that match this string. Once the items are located through the search, you can edit or
perform any other task appropriate for your particular workflow. This command is a
tracker command, that is, it can remain active at all times if appropriate.
You can start Search if the active window is a map window and if there is at least one
active connection. If the command is active and the active window becomes a data
window, the command remains active, and you can perform a search. The command uses
the original search map window as the search window. If you delete the original search
map window, change the active window to one that is not a map window, and select the
command, an error message informs you that you need an active map window. If the
layout window becomes the active window, this command is not displayed.
The Search command lets you perform two types of searches:
• Ad hoc searches, created with the search string entered directly in the Search dockable
control applied to all applicable attributes. All attributes in the feature class are
searched for the specified value.
• Predefined searches, previously created through the Searches command with your
control over the SQL used for the search, identification of the attribute(s) to be
searched, and provision of caption(s) for each search operand.
You can perform both types of searches on either a warehouse-resident feature class or a
GeoWorkspace-resident query on the Search dockable control, which is displayed when
you select View > Search. Any search results are immediately displayed, and you can also
set options for viewing the result items. The active map window is fit to, or centered on,
the first result and all results are available for navigation and are also displayed in the
Search Data Window.
Using the Search Dockable Control

The Search dockable control provides a field with a drop-down list from which you can
select the search input or a predefined search; a drop-down list, field, or grid for selecting
or typing the attribute value(s) if required by a search; and a Search button to execute the
search. It also contains the Queued Edit control for scrolling through the output of the
search and for setting viewing options.
10-58
To begin a search, you select one of the following:

• A feature class, query, category member, or reference feature for an ad hoc search.
• A predefined search, created through the Searches command, from the drop-down list,
located in the Searches branch of the treeview.
Depending on the search type selected, the dockable control takes one two forms, ad hoc or
predefined.
Performing Ad Hoc Searches

For an ad hoc search, the drop-down list, the key-in field, and the Options and Search
buttons are enabled.
To create an ad hoc search, you select a feature or query (from the features, queries,
categories, and reference features drop-down list) to search, type an appropriate text value,
and then click Search to perform the search and to display the results, as in the following
example. The Search command constructs an attribute query, executes it, and feeds the
results into the Queued Edit control.
10-59
If the attribute value entered is numeric, the constructed query searches all Text and Memo
fields for the entered value and compares all numeric fields to see if they are equal to the
entered value. If the attribute value entered is not numeric, the constructed query searches
all Text and Memo fields for the entered value. For the non-numeric comparisons, the
constructed string uses the like operator and assumes that you have entered the appropriate
wildcard characters if necessary.
For many database systems (Oracle, ArcView, and so forth) the percent sign (%) is the
multi-character wildcard character. For Access, the asterisk (*) is the multi-character
wildcard character. If the selected input is a query, the multi-character wildcard character
is the percent sign. Case sensitivity also varies depending on the database system. Access
queries are not case sensitive. Oracle queries are case sensitive. If the selected input is a
query, the new query is case sensitive.
Note: It may be helpful when first using this command to practice using the input query
you construct in the Analysis > Attribute Query command to ensure that it is correct and
returns appropriate results. You can then use it to perform your ad hoc search.
Performing Predefined Searches

For a predefined search, the dockable control appearance varies according to the type of
search. If the search does not require attribute value input, that grid does not appear, as in
the following example, with the Options and Search buttons enabled. To perform such a
search, you only need to click Search to display the results.
10-60
If the search does require input, an attribute (prompt)/value grid is displayed and enabled
along with the Options button. The Search button is enabled when you type a value for
the displayed attribute. To perform such a search, you type the appropriate value and then
click Search to display the results.
The number of rows in the grid is the same as the number of unique parameter values
defined when the search was created with the Searches command. The Search command
populates the left-hand column of the grid with parameter names extracted from the SQL
of the predefined search. The right-hand column is for your data entry. The command
substitutes the values entered for the SQL parameters, executes the query, and feeds the
results into the Queued Edit system. If the search requires more than two substitutions, the
grid has a vertical scroll bar, as in the following example.
Using the Queued Edit Control

Whether your search is ad hoc or predefined, the search output is displayed as a queue
using the Queued Edit control on the bottom of the Search dockable control in the map
window and in the Search Data Window. You can use this control for navigating among
multiple items returned by the search.
The Queued Edit control saves the map window name, Search Data Window, and the
legend, so that if you delete the Search map window or data window, it can create the
window again when you try to navigate the queue again. If you have deleted the map or
data window and created a new one (with the same name as the original Search window),
the Queued Edit control creates the window and adds “1”, or whatever number makes it
unique to the name. You can define the extent of the map window using Queued Edit
options and use the Spatial Filter Options to reset the spatial filter.
Navigating through Searches

You can navigate through the items in a search and adjust the view using the Queued Edit
control options: Move First, Move Next, Move Current, Move Previous, Move Last,
Zoom In/Out, and Fit current queue item. Each of these makes use of the view
properties you set in the Options > Queuing Options dialog box. When a Search Data
10-61
Window is present during a queue navigation, the data window is scrolled and the row
selector image points to the highlighted current queue item (record).
Setting Queuing Options

You can set options for viewing the map window display and for defining an item locator
through the two tabs on the Queuing Options dialog box, which is displayed by clicking
the Options button on the control.
The View tab lets you define the view options. When you zoom in/out or fit the view of an
item in the map window the view adjusts according to the view options. The Locator tab
lets you define the locator, which consists of two graphical elements, the locator box and
the crosshairs.
See “Setting View Options” in the “Working with Queued Edit” section of this chapter for
more information on using this dialog box.
Displaying the Search Data Window

You can also show or hide the data window for the active queue though the
Display/Remove Data Window button on the control. If this toggle button is depressed
and the Search Data Window does not exist, a data window is created when a queue is
made active. If you delete the data window, the window is created the next time you
advance the queue or make a queue active. If the button is raised and the data window
exists, it is deleted.
Working with Joins

A join query combines data from two feature classes or queries that have common
attribute values. For example, a join would return all attributes for parcels from the parcel
feature class along with parcel ownership information from another feature class, based on
a common parcel ID, even if the latter feature class is in another warehouse.
10-62
The Join command lets you specify feature classes or queries to join along with the
attributes within those feature classes or queries to join on, and the type of join operation to
perform. To create a join containing the appropriate features from each feature class, you
select the attribute in each feature class that contains the matching value. Attribute pairs
need not have the same name, but they must be the same data type. Only the values in
each attribute need to match.
Note: For values to match, they must be a perfect match. For example, “Kansas” is not a
perfect match for “Kansas<space>”.
You can also select and rename output columns in a join query through the Output
Attributes dialog box, which lists all the attributes. This enables you to see the final
resulting fields and to manipulate the field names and the order of the fields.
This command generates a read-write output query when at least one output attribute is
read-write. Output attributes are read-write when they come from a read-write attribute in
the input feature classes or queries, and when they are participating in an inner join or the
inner portion of a left outer or right outer join.
Defining Joins
You can create the following types of joins:
Inner join Records are added to the join only if the value from
the left field matches the corresponding value in the
right field. Records from either feature class that do
not match are not included in the join.
Left outer All records from the left feature class are included in
join the join, but only matching records from the right
feature class are included. Records from the right
feature class that do not match are not included.
Right outer All records from the right feature class are included in
join the join, but only matching records from the left
feature class are included. Records from the left
feature class that do not match are not included.
Full outer All records from both feature classes are included in
join the join.
In any of the outer joins, fields in records with unmatched values have null values.
Accordingly, join attributes with null values cannot be matched to any record in the other
feature class. If a record in one feature class contains a value that has a match in more than
one record in the other feature class, the query will return multiple copies of the first
record.
10-63
To display the join in a map window, the software uses the geometry from the left feature
class or query. So, when you create a join from two feature classes or queries that contain
geometries, select the feature class or query whose geometry you want from the left side of
the Join dialog box.
To create a join:
1. Select Analysis > Join.
2. From the Left side of join drop-down list, select the left feature class or query.
3. From the Right side of join drop-down list, select the right feature class or query.
4. From the lists of available attributes, select the attributes on which to create a join.
5. Click the down arrow to add the attribute pair to the Selected attribute pairs list.
Note: To remove an attribute pair, select it from the Selected attribute pairs list and
click the up arrow.
6. If the records have to match in more than one attribute, repeat Steps 2 - 5 to add
additional attribute pairs to the join.
7. Optional: Click Attributes to rename (click Rename) and/or to reorder the attributes
(using the arrow buttons and/or Select/Unselect All buttons to aid the
selecting/unselecting process).
10-64
See GeoMedia Help for more information on using this dialog box.
Note: When you hover over an entry in either list, a tooltip is displayed indicating the
name of the field.
8. Select the type of join to perform.

9. In the Query name field, type a name for the join or accept the default name.
10. Optional: Type a description for the join.
11. Select a window in which to display the join. If you select a map window, you can
also change the style of the join.
12. Click OK.
Analyzing Geometry
Analyze Geometry calculates geometric statistics for each feature instance of a selected
feature class or query and displays the output as a query, which can be displayed in a map
The statistics available are as follows:
2
• Area features—area, perimeter, area/perimeter
• Linear features—length, azimuth, bearing
• Point features—geographic coordinate, projection coordinate, height
2
• Compound features—area, length, perimeter, area/perimeter , length, azimuth, bearing,
geographic coordinate, projection coordinate, height
10-65
• Graphics text features—geographic coordinate, projection coordinate, height

• Raster features—none
In addition, you can use this tool as an analytical tool to find certain specified conditions.
For example, you could use it to locate all the parcel areas of a certain size or to prepare a
thematic map. You access Analyze Geometry from the Analysis menu.
This tool takes a feature class or query as input and outputs the results as a new query
containing all the fields from the input feature class, plus additional fields for each
appropriate geometry statistic selected on the dialog box. You can display this resultant
query in a map window and/or a data window. In addition, you can set the style for the
map window for optimum display results. A query or data window sort can be performed
to find small areas or short lines, which allows greater flexibility in the use of the tool. For
example, you may want to find all features with large area or those with areas within a
specific range. The default unit values are populated from the Units and Formats tab of
the Coordinate System Properties dialog box, but you can change them. The distance
and area units, however, are not displayed in the output query.
See GeoMedia Help for information on the Units and Formats tab.
The query is dynamically linked back to the input feature class or query and is
automatically updated when any changes are made. This means that you can select
features in the output query and delete them, and they will be deleted from the original
feature class. In this way, for example, you could find all areas less than a certain
minimum size or lines less than a minimum length and eliminate them.
Analyze Geometry performs calculations based on the options selected on the Units and
Formats tab of the Coordinate System Properties dialog box. You can change these
options by selecting different unit values on the tab.
For azimuth, bearing, geographic coordinate, projection coordinate, and height, the units
and format are taken directly from the settings on the dialog box. You cannot override
these settings through the Analyze Geometry dialog box. This means that once you
generate the query, you cannot change the units and format of the azimuth, bearing,
geographic coordinate, projection coordinate, and height. To change the settings, you must
generate a new query.
You also have the option of using a spheroidal or planar reference space when computing
the statistics. The default value is taken from the Units and Formats tab of the
Coordinate System Properties dialog box. All computations take place in the
GeoWorkspace coordinate system.
Note: Existing queries produced by this command in GeoMedia 3.0 continue to be

computed in the warehouse coordinate system. Only new (GeoMedia 4.0 and higher)
queries are computed in the GeoWorkspace coordinate system.
10-66
After running Analyze Geometry, you can perform maintenance on the detected
conditions. Any changes you make to the geometries of the features for which the
statistics were calculated update the statistics automatically in any open map window
and/or data window displaying the affected features.
For example, if you wanted to delete small areas found by Analyze Geometry, you would
do as follows:
1. Run Analyze Geometry to find the small areas.
2. Open a data window on the new query.
3. Sort the area column.
4. Select all rows with less than the appropriate area.
5. Delete the selected rows.
The data window and map windows are updated for the deletion.
Analysis Options
You can choose from among the following analysis options for the statistics you need:
• Area—Calculates the area of each feature with an area geometry and stores the value
in a new field called Area. The area is calculated only for those features with an area
geometry; any other geometries are ignored. If the input feature class or query is a
linear geometry, this option is ignored.
• Perimeter—Calculates the perimeter of discontiguous geometries, and holes are
accounted for in the area calculation each feature with an area geometry and stores the
value in a new field called Perimeter. The perimeter is calculated only for those
features with an area geometry; any other geometries are ignored. If the input feature
class or query is a linear geometry, this option is ignored.
• Area/Perimeter2—Calculates the area/perimeter_2 ratio for each instance of the
selected feature class or query with an area geometry. The value is stored in a new
field in the output query set called AreaPerimeterRatio. If the input data contains
compound feature classes, the statistic is calculated only for those features with an area
geometry. The statistic is not calculated for disjoint area geometries. If the feature is a
collection containing area and line or point geometries, the statistic is still calculated
for the area geometry, while the other geometries are ignored. If the input data is a
linear geometry, this option is ignored.
• Length—Calculates the length of discontiguous geometries, and holes are accounted
for in the area calculation each feature with a linear geometry and stores the value in a
new field called Length. The length is calculated only for those features with a linear
geometry; any other geometries are ignored. If the input feature class or query is an
area geometry, this option is ignored. Discontiguous geometries are accounted for in
the length calculation.
10-67
• Azimuth—Calculates the azimuth for each feature with a linear geometry and stores
the value in a new field called Azimuth. The azimuth is calculated only for compound
and linear features.
• Bearing—Calculates the bearing for each feature with a linear geometry and stores the
value in a new field called Bearing. The bearing is calculated only for compound and
linear features.
• Geographic Coordinate—Outputs the geographic coordinate for each feature with a
point or text geometry and stores the values in two new fields called
GeographicFirstCoord and GeographicSecondCoord. The geographic coordinate is
output only for compound, point, and text features.
• Projection Coordinate—Outputs the projection coordinate for each feature with a
point or text geometry and stores the values in two new fields called
ProjectionFirstCoord and ProjectionSecondCord. The projection coordinate is output
only for compound, point, and text features.
• Height—Calculates the height for each feature with a point geometry and stores the
values in a new field called Height. The height is calculated only for compound, point,
and text features.
The output feature class or query contains a new field for each selected analysis option that
applies to the geometry type of the input feature class or query. The default headings of
the new fields are those previously listed. If a column exists with one of these names, the
new name is the same but with a ## symbol appended to the end of the name, where ##
begins at 01 and is incremented until a unique name is found.
To analyze geometry:
1. Open a read-write warehouse.
2. Select Analysis > Analyze Geometry.
3. Select a feature class or query from the Features to analyze drop-down list.
10-68
4. Select the appropriate analysis statistics option(s) from the list in the Analysis options
selection area.
Note: The Analysis options list is populated based on geometry of selected feature
class or query. All available analysis options are off when a feature class or query is
first selected. When the feature class or query is changed, all available analysis
options are again turned off. However, if the geometry type of the new feature class or
query matches that of the old feature class or query, the user-selected options are
retained.
5. Type an appropriate name in the Query name field.

7. Optional: Click Units and Formats, and change the values appropriately on the Units
and Formats tab of the Coordinate System Properties dialog box.
8. Verify that the Display results in map window check box is selected in the Map
window name field, and change, if appropriate, the map window in which to display
the results.
OR
To not display the results in a map window, uncheck the Display results in map
window check box.
10. Verify that the Display results in data window box is selected in the Data window
name field, and change, if appropriate, the data window in which to display the results.
OR
To not display the results in a data window, uncheck the Display results in data
window check box.
11. Click OK to analyze the geometries.
Analysis processing is performed in the selected feature class or query, and an output
query is produced using the query name from the dialog box.
10-69
If the map window display check box was selected, the map window with the
geometries is displayed. If the data window display check box was selected, the data
window with the geometries is displayed.
Placing Buffer Zones Around Features

A buffer zone is a region around or within one or more features, generally used for spatial
analysis or as input to spatial queries. When you use the Analysis > Buffer Zone
command to place buffer zones, you are creating a query that is associated with an existing
feature class. These buffer zones are inserted as area features. You can define and place
buffer zones around point, linear, area, and compound feature classes (not graphics text,
raster, or nongraphic features) or around the results of a query. Buffer zones work best
when the coordinate systems of the GeoWorkspace and warehouse are matched and set to
an equal area projection. This command outputs the buffer zones to a map window and/or
data window. Buffer Zone is enabled when a map window is active and there is at least
one open warehouse connection.
10-70
You can specify the buffer zone distance (or the name of an attribute containing buffer
zone distances) on a per-feature basis. Many variations of input distance values are
supported, including stacks, rings, and buffer zones in the interior of areas. The buffer
zone distance can be of two kinds, constant or variable.
When using a constant distance, you set the distance value and unit. You must type the
distances as follows:
• Single—A simple number, for example: 10
• Stacked—Numbers separated by semicolons (;), for example: 10;20;30
• Ringed—Numbers separated by colons (:) and semicolons (;), for example:
(start/end) 10:20;30:40
The default value for unit is from the Unit setting on the Units and Formats tab of the
Define Coordinate System File dialog box.
When using a variable distance, you select an attribute that contains distance values that
may vary on a per-feature basis. Only attributes of type text, byte, integer, long, single,
double, and currency are available for selection. These values must be in the ground units
of the coordinates system of the data you are buffer zoning. If this is not the case, you can
construct an expression using the Functional Attributes command, which performs any
required unit conversion and formatting.
See “Working with Functional Attributes” in this chapter.
You have the option of setting the type of end caps to place around the ends of linear or
compound features, either rounded (default) or squared.
You can also set the output of the touching buffer zones as merged or unmerged (default).
Unmerged output contains one output buffer zone placed around or within each feature for
each input feature-distance combination. Overlapping buffer zones are not merged.
Diagram A below shows six unmerged buffer zone features. Merged output contains the
originally resulting output buffer zones merged in such a manner that overlapping sets of
buffer zone features are merged, but discontiguous buffer zones from a single input feature
retain their grouping. Diagram B below shows four buffer zone features, one of which
consists of three previously unmerged buffer zone features.
A B
10-71
In the case of merged output, the resulting query consists of a single output geometry field.
In the case of unmerged output, there is additionally a text attribute containing the distance
value at which the buffer zone was created.
The following diagrams show example buffer zones around different geometries and how
they vary with both positive and negative distance:
Working with Functional Attributes

The Functional Attributes command lets you create new query-based attributes. This
command supports the calculation of on-the-fly, dynamic attributes based on geometry
measurement and/or attribute values for one database table at a time. The command
returns all of the original attributes plus any new attributes defined on the Functional
Attributes dialog box as a new query. You can use this command on read-only data as
10-72
well as read-write data. Calculated output attributes can also be used as input for further
analysis within the same functional query. To use this command, you must have an active
map window or data window and at least one open connection.
After generating the functional attributes, the command stores the query in the
GeoWorkspace and displays the results in the map and/or data window. You can view and
manage queries by using the Analysis > Queries and Legend > Add Query commands.
The workflow for using this command is to first select the feature or query for which you
want to add functional attributes on the Functional Attributes dialog box.
You then use the New button to open the Functional Attribute dialog box to construct the
analysis expression. This second dialog box functions as a calculator that you can use to
provide calculated information for queries. This calculator provides standard operators and
context-sensitive syntax information.
10-73
See the GeoMedia Help for information on this dialog box.

You can also access the Functional Attribute dialog box to create, edit, review, and/or
delete functional attributes through the Aggregation and Analytical Merge commands on
the Analysis menu. The Analysis commands Functional Attributes, Aggregation, and
Analytical Merge are types of queries for forming additional data with the Functional
Attributes dialog box.
See “Aggregating Data” and “Merging Feature Classes and Queries” in this chapter.
Note: To avoid possible confusion, remember that there is a Functional Attributes

command that, when selected, opens the Functional Attributes dialog box. However,
from this dialog box, and from the other commands just discussed, you can access the
Functional Attribute dialog box.
Functional Attribute Expressions

Functional Attribute expressions are similar to the expressions used in Excel. They
consist of operands and operators that are evaluated in order to get a resulting value. An
expression can be just one operand or a combination of operands with one or more
operators. You can use expressions in many ways, for example, as part of the data to
retrieve in a query or as a search condition to look for data meeting a set of criteria.
See the “Functional Attribute Information” topic in GeoMedia Help for detailed
information on the expression components.
You can create or edit an expression by typing values and using operator buttons that
automatically insert the corresponding operator into the Expression field on the
10-74
Functional Attribute dialog box. You can also cut and paste function syntax into the
Expression field.
This dialog box provides categories, functions belonging to a selected function category,
and columns (attributes) that can be used as input parameters for functions. To help in the
creating and editing, the dialog box also displays the syntax definition for the selected
function and a tooltip that provides a brief description of the functionality of the selected
function. Once you insert text, the expression is validated. If there is a problem when
adding the function, an error message is displayed, and the position of the cursor in the
expression indicates the error location.
Note: You can select the syntax statement, displayed at bottom of the dialog box when
you select a function, and paste it elsewhere.
You can share expressions with others by emailing the GeoWorkspace, creating a
GeoWorkspace template file, creating a GeoMedia WebMap website, and cutting and
pasting expression strings.
Output Data Types

The output data type of the functional attribute is displayed in the Output type read-only
field only when the expression is currently valid, thus providing a valuable expression
check. In addition to standard numeric and text data type outputs, some (Geometry)
functions output geometry data types. Output geometry data types include the following:
• Area Geometry • Line Geometry
• Compound Geometry • Point Geometry
• Image Geometry • Text Geometry
Length
You can review and/or edit of the length of the output functional attribute in the Length
field when the output type is Text. The default value is 255, and you can edit this to any
value from 1-255, inclusive.
10-75
Format
You can review and/or edit the format of the output functional attributes in the Format
field for all data types except Geometry data types. The default format/value depends on
the output data type.
Precision
You can review and/or edit the display precision of the output functional attributes when
the format is Fixed, Standard, or Currency and the output type is Single, Double, or
Currency. The default value depends on the output type. For Single default will be 4, for
Double default will be 6 and for Currency default will be 2.
Operands
Operands are manipulated by the operators in an expression. The operands can be the
following:
Identifiers—References to fields in which values vary for each record.
Constants—Fixed values that are constant for each record.
Functions—Operations that take inputs and return values.
You can build an expression from combinations of these operands joined with operators.
For example, an expression can be a calculation, such as: (price * 1.5) or (price +
sales_tax).
In an expression, you enclose character data values in single quotation marks ('). In the
following expression, the character literal B% is used as the pattern for the LIKE clause:
LastName LIKE ‘B%’.
In the following expression, the date value is enclosed in single quotation marks:
OrderDate = 'Sep 28 2001'.
Operators
Operators are symbols specifying an action performed on one or more operands, that is,
how the operands are manipulated. The operator categories are the following:
• Arithmetic • Logical
• Bitwise • String
• Comparison • Unary
An expression can be built from several smaller expressions combined by operators. In
these complex expressions, the operators are evaluated based on operator precedence.
Operators with higher precedence are performed before operators with lower precedence.
Operators with the same precedence are performed from left to right.
The following are example expressions:
10-76
• AssessedVal = Area* Value

• TotalPop = sum(Pop)
• If MeanIncome > 30,000 then sum(Pop)
Functions
The Functional Attributes command provides the following types of functions to perform
operations:
• Scalar functions operate on a single value and then return a single value.
1:1 (1 record in, 1 record out) Example: Using the Functional Attributes command
to calculate the X or Y coordinates of a point geometry feature class.
• Aggregation functions operate on a collection of values but return a single,
summarizing value.
Many:1 (Many records in, 1 out) Example: Using the Analytical Merge command
with CREATEPOLYGON to merge points to a polygon.
• Expansion functions operate on a single value (usually a geometry value) and then
return multiple values.
1:Many (1 record in, Many records out) Example: Using the Functional Attributes
command to calculate SEGMENTS of lines.
In general, Aggregation functions are most often used with the Analytical Merge
command and the Aggregation command. The Functional Attributes command normally
uses only Scalar or Expansion functions.
All functions delivered with GeoMedia have unique names. These functions are organized
in the following categories:
• Date and Time • Miscellaneous
• Geometry • Statistical
• Logical • Text
• Math & Trig • View
The categories on the Functional Attributes dialog box simply organize the functions by
subject. If you select All Functions from the Categories list, all available functions are
displayed for selection in the Functions list. If you select Most Commonly Used
Functions, the Functions list contains only those functions that you have most recently
and most frequently used. The default content consists of fourteen pre-selected functions;
as you use this command, the list adjusts to include your own commonly used functions.
Operators and Constants display a list of operators and constants, respectively.
Attributes that can be used as input parameters for the functions are displayed in the
Attributes list.
10-77
Common Geometry Functions

Some of the most commonly used Geometry functions are AREA, COMPRESS,
CREATEPOLYLINE, MERGE, PERIMETER, and REVERSE.
Their specifications are as follows:
AREA—Returns the area of the specified geometry. The syntax for the AREA function is
similar to other functions such as LENGTH, PERIMETER, X, Y, and others.
Format: AREA(Geometry, RefSpace, UnitOfMeasure)
Geometry: The geometry for which you want to measure the area. The geometry can be
selected from the available input attributes section of the dialog box.
RefSpace: The active reference space used for performing measurements can be set to one
of two constants: Truemeas (True Measure) or Projectedmeas (Projected Measure). The
reference space constant determines if the measurement calculations should be made along
the curvature of the earth or the plane of the feature class projection. This parameter is
optional. If missing, Truemeas is used. Possible values are as follows:
Value Constant Meaning

0 Truemeas Measurements are computed on the surface of the ellipsoid
(taking the earth's curvature into account). Distances are
also referred to as geodesic distances.
1 Projectgedmeas Measurements are computed on the projection plane.
These measurements are affected by projection distortions.
UnitOfMeasure: The area unit in which the geometry is to be measured. This parameter is
optional. If missing, the geometry is measured in square meters. Valid area measurement
values can be selected from functions listed in the category Constants.
Remarks: The return value depends on the geometry type.
If the geometry is not defined (NULL value), the NULL value is returned.
Return Type: gdbDouble
COMPRESS—Returns a compressed form of the given geometry. The geometry does not
change visibly but is instead rewritten with efficient storage. It is sometimes used with
certain data originating from CAD (that is, derived from complexed lines or polygons).
The geometries are rewritten so they are easier to edit in GeoMedia. COMPRESS can be
used in the Update Attributes command to update the geometries in a read-write
warehouse directly. You can review information about a particular geometry by selecting
the geometry in the map window, then right clicking for the Geometry Information
command, as seen in the following examples of an inefficiently stored parcel before and
after COMPRESS:
10-78
BEFORE AFTER
Format: COMPRESS(Geometry)
Geometry: The geometry that you want to compress. The geometry can be selected from
the available input attributes section of the dialog box.
Remarks: The return value depends on the geometry type.
COMPRESS does not change the following geometry types: PointGeometry,
OrientedPointGeometry, LineGeometry, PolylineGeometry, ArcGeometry,
PolygonGeometry, RectangleGeometry, RasterGeometry, or TextPointGeometry. In all
such cases, the input geometry is returned unchanged.
COMPRESS is applicable only to CompositePolylineGeometry,
CompositePolygonGeometry, BoundaryGeometry, and GeometryCollection. These
geometry storage types may contain nested geometries and/or sequences of linear
geometries. In all such cases, the input geometry is returned in an efficiently stored
geometry. There is no loss in accuracy or visible change. See the following:
If the geometry is not defined (NULL value), then a NULL value is returned.
The act of compression involves three different activities:
1. Nested composites/collections are flattened. This eliminates geometry headers,
eliminates recursive processing, and (for composites) sets the stage for further
optimization in the next step.
2. Consecutive endpoint-matched lines/polylines within composites/collections are
stitched together into a single polyline. This eliminates geometry headers and
eliminates redundant vertices.
In the case of composites, it is expected that consecutive geometries match endpoint-
to-startpoint, in which case such geometries (if line/polyline) are stitched together with
the redundant vertex eliminated. In the event that they do not match endpoint-to-
startpoint, it is considered an invalid geometry. In this case there is no redundant
vertex, and no compression occurs between the two geometries.
In the case of collections, there is no expectation that consecutive linear geometries
match endpoint-to-startpoint, but we know from experience that such circumstances do
occur, and that when they occur, they are often meant to be treated as a single
10-79
continuous linear geometry. For this reason, the same processing will occur in this
step for collections as occurs for composites, as stated above.
3. Single-member composites/collections are flattened and replaced with the single
member primitive. This eliminates the parent geometry and simplifies future
processing and editing of the geometries.
Return Type: gdbSpatial
CREATEPOLYLINE—Creates a polyline from an ordered series of points. This is an
aggregating (that is, points stored in multiple records output to one linear record) or a
scalar (that is, multiple points stored in 1 record output to 1 linear record) function. If the
points for a single line are stored in multiple records, you should use CREATEPOLYLINE
with the Analytical Merge command and, more rarely, the Aggregation command. If the
points for a single line are stored in a single record (that is, a feature class or query that has
multiple point geometry columns), you can use Analytical Merge, Functional Attributes,
or Aggregation.
Format: CREATEPOLYLINE(Geometry, OrderBy) or CREATEPOLYLINE(Geometry1,
Geometry2, Geometry3, …)
Geometry: The point geometry that represents vertices from which a polyline is created.
OrderBy: The optional expression that is used for sorting the points. If it is missing, the
order is determined by the recordset and pipe that is hosting this function, and in this case,
the order of the vertices is not guaranteed.
Geometry 1, 2, …: The point geometries that represent vertices from which the polyline is
to be created. In the case of this format, the function becomes scalar.
Remarks: The input geometry type must be type of gdbPoint.
If the input field is a collection, each point of the collection will be handled separately in
the order of the items in the collection.
If any of the input geometries are not defined, the geometry is ignored. If the number of
points that creates the polyline is less then 2, the NULL value is returned.
Return Type: gdbLinear
MERGE—Returns the merged geometry. Commonly used with the Analytical Merge
command because this is an aggregating type function.
Format: MERGE(Geometry)
Geometry: The geometry for which you want to create merged geometry.
Return Type: gdbSpatial
PERIMETER—Returns the distance around the perimeter of the specified geometry. The
following format is similar to the AREA function (see also the previous AREA function).
10-80
Format: PERIMETER(Geometry, RefSpace, UnitOfMeasure)

Geometry: The geometry for which you want to measure the perimeter.
RefSpace: The active reference space used for performing measurements.
This parameter is optional. If missing, Truemeas is used. For possible values see the
AREA function.
UnitOfMeasure: The linear unit in which the geometry is to be measured. This parameter
is optional. If missing, the geometry is measured in meters. Valid linear units can be
selected from the list of constants (found under the Constants category).
Return Type: gdbDouble
REVERSE—Returns the original geometry with reversed vertex order. This is a scalar
function.
Format: REVERSE(Geometry)
Geometry: The geometry that you want to reverse. It must be of the subtype gdbLinear,
gdbAreal, or gdbAnySpatial.
Remarks: If the geometry contains point geometry, the point is returned without any
changes.
If the geometry contains linear geometry, the reversed linear geometry is returned.
If the geometry contains areal geometry, the reversed areal geometry is returned
If the geometry contains a collection of geometry, the reversed collection of reversed
geometry is returned. In other words, each individual geometry is reversed, and the items
in the collection are also reordered, from last to first, so that the overall vertex sequence is
retained.
Return Type: The same as the original geometry type.
Constants
A constant, also known as a literal or a scalar value, represents a specific data value that
does not change during the calculation of an expression. The format of a constant depends
on the data type of the value it represents. A full list of the available constants can be
found under the Constants category.
To create and to display functional attributes:

1. Select Analysis > Functional Attributes.
10-81
2. Select a feature class or query as input from the Add functional attributes for drop-
down list.
3. Click New to open the Functional Attribute dialog box to define at least one functional
attribute.
4. Type an appropriate value in the Functional attribute name field.
Note: The Output type field is read-only, and a Length field is enabled only for the
Text output type. When you create a valid expression, the Output type field is
automatically assigned.
5. Use the Expression field to create the expression to be calculated for the new
functional attribute. Expressions can be created by typing and/or pasting values, by
using the operator buttons, and by selecting values from the Categories,
Functions/Constants, and Attributes lists.
6. When you have completed entering the expression, click Add to create the functional
attribute.
Note: Once a functional attribute has been created, it is added to the list of available
attributes and can used as part of other functional expressions.
7. Optional: Use the Expression field and Add button to create more functional
attributes.
8. Click Close to return to the Functional Attributes dialog box.
10-82
11. Choose whether or not to display the resultant functional attribute query in a data
window or map window. You can change in the Map window name field, if
appropriate.
12. Optional: Click Style, and change the map window default style on the Select Style
dialog box.
13. Click OK.
To edit functional attributes:

2. Select the appropriate query from the list of query names.
4. Edit the expression for the functional attribute in the Expression field of the
Functional Attribute dialog box by typing and/or pasting values, by using the
operator buttons, and by selecting values from the Categories, Functions/Constants,
and Attributes lists.
5. When you have completed editing, click OK to return to the Queries dialog box.
Merging Feature Classes and Queries

The Analytical Merge command lets you dynamically merge features in a specified
feature class or query, as well as to aggregate the attributes for those features into a single
output feature. This output merge is a query that combines information from one specific
feature class. The output query is stored in the GeoWorkspace, and you can display it in
the map and/or data window. For example, you may have a series of individual line
segments making up an interstate highway alignment, and you would like this to be merged
into one continuous line, while also calculating the length of the merged segment and the
average speed limit along the entire length.
In the merge process, you specify the merge criteria and the output functional attribute(s)
to be computed from the input features. You can merge all feature classes except graphics
text or raster. To use this command, you must have an active map window or a data
window and have at least one warehouse connection open.
The following is an example of a merge of counties by district and population:
10-83
Additional merge examples are the following:

• Merge Parcels by Owner ID and/or Name and calculate the taxes owed.
• Merge Pipe Segments by pressure_zone id, and return the total length of pipes and
average pressure in each pressure zone.
• Merge Streets by street_name and calculate the total length (sum of segments)
• Merge Survey Points by Survey name to connect the stations with a line (connect the
dots) using the CREATEPOLYLINE function.
There are three possible queries, based on the merge criteria: attribute based, spatially
based, or both. You specify the criteria through the following options on the Analytical
Merge dialog box:
• All—Merges all input features.
• Touching—Merges features that touch.
• By attribute—Merges features that share one or more selected equivalent attribute
values.
• By attribute and touching—Merges features that share one or more selected
equivalent attribute values and that touch.
If you select either of the two attribute-based criteria, the Attributes list is populated with
the names of all displayable attributes of type Text, Byte, Integer, Long, Single, Double,
Currency, Boolean, Memo, and Date (but not LongBinary, and GUID), from which you
can select one or more attributes to be used for determining if features should be merged
based on equivalence of attribute values. Attribute-based merging requires that the values
of all attributes match, that is, there is no logical and between comparisons of the various
attribute values. If you select attribute-based merging but do not select an attribute, it is as
if attribute-based merging were not selected. Thus, the command behaves as if the All or
Touching option (as appropriate) were selected.
You must define at least one output functional attribute through the Functional Attributes
dialog box. For all input features except nongraphic, the default attribute name is
10-84
Geometry with the expression “MERGE(<Geometry>)”, where <Geometry> is the name

of the primary geometry field of the input feature class or query. If the input features are
nongraphic, no attribute name is displayed. You can also define additional output
functional attributes and review and/or edit their properties through the Functional
Attributes dialog box, and you can delete functional attributes through the Analytical
Merge dialog box.
See “Working with Functional Attributes” in this chapter for information on functional
attributes.
You can use Analytical Merge to operate on both input and output attributes. The
attribute fields from the input are prefixed by Input in the Functional Attributes dialog
box. When you create a functional attribute, the new attribute is prefixed by Output.
This allows you to perform analytical operations on previously defined functional
attributes with the same operation. For example, you can specify the following
expressions in one run of the command:
MergeGeometry = MERGE(Input.Geometry)
AreaOfMergedGeometry = AREA(Output.MergeGeometry)
SumOfAreas = SUM(AREA(Input.Geometry)
The last two lines give you the same results if the geometries are only touching (not
overlapping). If you have overlapped areas, you get different results, and, in this case, the
SumOfAreas will be greater than AreaOfMergedGeometry.
Using the Right Mouse Menu

In defining a functional attribute, you can use the buttons to the right of the Output
functional attributes field, or you can use its right mouse menu. The menu contains
shortcuts for creating common functional attribute definitions, as in the following example:
New—Opens a submenu with the following items:

• Custom—Opens the Functional Attribute dialog box for creating new functional
attributes, as does the New button.
• Count(*)—Adds a new functional attribute with a default name of
“CountOf<Feature>”, where <Feature> is the name of the feature class or query input
to the command. The expression for the functional attribute is “COUNT(*)”.
10-85
• [Function] > [Attribute]—Adds a new functional attribute with a default name of

“<Function>Of<Attribute>”, where <Function> is the name of the function
(AVERAGE, COUNT, FIRST, MAX, MEDIAN, MIN, SUM), and <Attribute> is
the name of the attribute chosen. For example, to obtain the sum of the “Population”
attribute, the default functional attribute name would be “SumOfPopulation”. The
expression for the functional attribute is “<Function>(<Attribute>)”, for example,
“SUM(Population)”.
• [Function] > Multiple Attributes—Opens the Multiple Attributes dialog box for
creating multiple new functional attributes as in the previous bulleted item, one per
chosen attribute from the list of all attributes from the input feature class or query that
is of a data type valid for the selected function. After checking appropriate attributes,
clicking OK dismisses the dialog box and returns one new output functional attribute
for each attribute chosen.
Properties—Opens the Functional Attribute dialog box for reviewing or editing

functional attributes, as does the Properties button.
Delete—Deletes selected functional attributes, as does the Delete button.
To perform analytical merge:

1. Select Analysis > Analytical Merge.
10-86
2. Select the feature class or query to merge from the Merge features in drop-down list.
3. Select the appropriate Merge criteria option.
4. If you select By attribute or By attribute and touching, select the appropriate
Attributes check box(es).
5. Optional: Click New to define additional functional attributes on the Functional

Attribute dialog box.
6. Optional: Change the default query name, and/or type a description in the Output
merge as query fields.
7. Verify that the Display merge in map window check box is checked, and change in
merge.
OR
To not display the merge in a map window, uncheck the Display merge in map
window check box.
10-87
9. Verify that the Display merge in data window check box is checked, and change in
the Data window name field, if appropriate, the data window in which to display the
merge.
OR
To not display the nongraphic attributes of the merge in a data window, uncheck the
Display query in data window check box.
10. Click OK to generate the merged features.
Workflow for Dashed and Patterned Linear Features

Applying a dashed line style or a patterned line style to linear features can often produce
undesirable results if the linear network is segmented, as in the following example.
In the preceding example, the railroad pattern is uneven because of the segmented network;
the pattern origin is redefined every time a new segment is encountered. This is easily
overcome using the Analytical Merge command, as in the following example.
In the preceding example, the pattern spacing is consistent, as opposed to the first example,
thereby producing the appropriate symbology, as specified on the Select Style dialog box.
This is because the Analytical Merge command has merged the linear network, thus
eliminating the problems associated with segmented displays. This workflow is also very
useful for multiple-line displays used to show cased road (parallel line) symbology,
especially at intersections.
Aggregating Data
The Aggregation command lets you copy attributes from features, including graphic text
feature classes and queries, in one feature class (the detail feature class) to related features
in another feature class (the summary feature class) in the form of a dynamic query. This
query is based on the spatial relation between two features and/or related table columns
(similar to a join) between two features. The detail feature class attributes are aggregated
into the summary feature class. Both summary and detail feature classes can be point,
linear, area, compound, and nongraphic, but not graphics text or image. The output
10-88
aggregation is a query, which is stored in the GeoWorkspace and which you can display in
the map and/or data window. All summary attributes will be included in the resultant
query, while only the calculated attributes from the detail feature class are included.
An example of using aggregation would be to combine calculated information from a detail
TAX_ASSESSMENT feature class with a summary PARCEL feature class. In another
example, you could have a TAZ (Transportation Analysis Zone) feature class and an
ACCIDENTS feature class, and then you could sum the total number of accidents
occurring in each TAZ and copy it to the TAZ features. Or, given SOILS and
VEGETATION feature classes, you could copy the total number of each type of tree
falling in each soil type and, at the same time, calculate the average age and size of trees in
each soil type.
Other examples for using this command would be providing answers to the following:
• What is the total length of each class of road for each transit zone?
• What is the average income for customers in three-mile market areas for several
proposed business locations?
• What is the total assessed value of parcels affected by a proposed road-widening
project?
• How many houses are located within 300 feet of each road segment?
Aggregation Types
There are three possible types of aggregation based on the merge criteria: attribute based,
spatially based, or both. You specify the criteria through the tabs on the Aggregation
dialog box. On these tabs, you also specify the resolution operator and the definition of
output functional attributes to be computed from the summary features and the detail
features.
Attribute Aggregation
This type of aggregation uses matching attribute values to determine how the information
in the detail table is aggregated into the summary table. For example, you could aggregate
two tables, one with parcel geometry (PARCEL) and one with nongraphic information
(PARCEL_INFO) that is related to the parcel features that have one common (identical)
PARCEL_ID column. Using attribute aggregation would allow you to combine specific
calculated information from the detail table (PARCEL_INFO) to the summary table
(PARCEL), where appropriate, based on the comparison of the common attribute. To this
join, you could use functional attribution to add calculated information between the two
sources.
From the Attribute Aggregation tab, you can select one or more summary and detail
attribute pairs from a list of all displayable attributes, to be used for determining if features
should be aggregated based on the equivalence of attribute values. Values of all attributes
must match, that is, there is a logical and between the comparisons of the various attribute
10-89
values. When you have selected a summary feature class or query, you must select at least
one attribute.
The selection button that lets you select an attribute pair is enabled only if the
conversion between the data types of the selected attributes is possible. This conversion
possibility is described in following table:
gdbCurrenc
gdbBoolean
gdbInteger
gdbDouble
gdbSingle
gdbLong
gdbDate
gdbText
gdbByte
y
gdbBoolean Y N N N N N N N N
gdbByte N Y Y Y Y Y N N N
gdbInteger N Y Y Y Y Y N N N
gdbLong N Y Y Y Y Y N N N
gdbSingle N Y Y Y Y Y N N N
gdbDouble N Y Y Y Y Y N N N
gdbCurrency N N N N N N Y N N
gdbDate N N N N N N N Y N
gdbText N N N N N N N N Y
Y = Selection button enabled. N = Selection button disabled.
Spatial Aggregation
When both summary and detail feature classes do not have a common (identical) database
column and they are spatial feature classes, you can still perform aggregation through
spatial criteria. For example, you could use spatial aggregation to find a site for a new
restaurant based on traffic volume, population income, and distance from a particular
intersection.
For spatial aggregation, you need to check the Aggregate where summary features check
box and to select an appropriate spatial operator on the Spatial Aggregation tab because
this type of aggregation is based on spatial proximity. If you select the are within
distance of operator, you also need to define the distance and distance unit.
10-90
The operators are as follows:

• accumulate nearest • contain
• are contained by • entirely contain
• are entirely contained by • meet
• are nearest to • overlap
• are spatially equal • touch
• are within distance of
accumulate nearest—Aggregates the closest detail feature(s) to each input (summary)
feature.
are nearest to—Aggregates the detail feature to the nearest of the identified input
(summary) features, using the minimum distance between each pair of features. Note that
this operator locates only the one feature that is closest. The minimum distance is zero for
features that actually touch.
See “Defining Spatial Queries” in this chapter for definitions of the other operators.
Attribute/Spatial Aggregation
You can also perform a combination attribute and spatial aggregation when there is at least
one common (identical) database column between the summary and detail features and
when the geometries touch. You perform this aggregation by using input from both the
Attribute Aggregation and Spatial Aggregation tabs.
Output
From the Output tab, you can select the output definition, which consists of an optional
resolution operator and at least one functional attribute.
Resolution operators indicate how to resolve the ambiguous cases in which a detail feature
can be aggregated to more than one summary feature. If both selected summary and detail
feature classes or queries are spatial, and the spatial aggregation check box is checked on
the Spatial Aggregation tab, the available operators are All, None, First, Largest,
Largest Overlap, Nearest, Are Nearest To, and Accumulate Nearest. If the spatial
aggregation check box is unchecked, or if at least one of the selected feature classes or
queries is nongraphic, the available operators are All, None, and First.
10-91
On the Output tab, you also have the option to create functional attributes and to review
and/or edit their properties through the Functional Attribute dialog box or to delete a
functional attribute. The functional attribute adds the calculated information to this join.
You can use Aggregation to operate on both input and output attributes. This allows you
to perform analytical operations on previously defined functional attributes with the same
operation. The summary features appear in the Attributes field of this dialog box as
Input.<attribute name> and the detail features appear as Detail.<attribute name>.
See the “Working with Functional Attributes” section of this chapter for more information
on functional attributes.
Aggregation Examples
The following are examples of using Aggregation with the USA and Madison County
sample data sets that were delivered with this product. The example problems listed here
are hypothetical, and there may be other valid workflow solutions to solve the problem.
Problem 1: Need to transfer the state abbreviation from the state to the counties that are
contained by the state.
Solution:
• Summary Feature: Counties
• Detail Feature: States
• Aggregation defined as Spatial
• Aggregate where summary features are contained by detail features
• Output Resolution Operator: All
• Output Expression: FIRST(Detail.STAABBRV)
Problem 2: Need the number of cities each state contains as an attribute of the state.
Solution:
• Summary Feature: States
• Detail Feature: Cities
• Aggregate where summary features touch detail features
• Output Expression: COUNT(*)
Problem 3: Need to calculate the number of people in each state who do not live in a city.
Solution:
• Summary Feature: States
• Detail Feature: Cities
10-92

• Aggregate where summary features touch detail features
• Output Expression: Input.POP-(SUM(Detail.POP))
Note: The output expression can be thought of as State.Pop-(SUM(City.Pop)).
Problem 4: Need to calculate the total number of miles of interstate in each county.
Solution:
• Must perform analysis on spatial intersection (Analysis > Spatial Intersection) of
Counties with Interstates, that is, Interstates overlap Counties.
• Summary Feature: Counties
• Detail Feature: Spatial Intersection of Interstates and Counties
• Aggregate where summary features overlap detail features
• Output Expression: SUM(LENGTH(Detail.IntersectionGeometry,TrueMeas,Mile))
Note: The value of miles will be expressed using double precision, but the results
could have been rounded using the expression. The following rounds the values to two
significant digits:
ROUND(SUM(LENGTH(Detail.IntersectionGeometry, TrueMeas, Mile)),2)
Using the Right Mouse Menu

In defining a functional attribute, you can use the buttons to the right of the Output
functional attributes field, or you can use its right mouse menu. The menu contains
shortcuts for creating common functional attribute definitions as in the following example:
New—Opens a submenu with the following items:
• Custom—Opens the Functional Attribute dialog box for creating new functional
attributes, as does the New button.
• Count(*)—Adds a new functional attribute with a default name of
“CountOf<Feature>”, where <Feature> is the name of the feature class or query input
to the command. The expression for the functional attribute is “COUNT(*)”.
• [Function] > [Attribute]—Adds a new functional attribute with a default name of
“<Function>Of<Attribute>”, where <Function> is the name of the function
10-93
(AVERAGE, COUNT, FIRST, MAX, MEDIAN, MIN, SUM), and <Attribute> is

the name of the attribute chosen. For example, to obtain the sum of the “Population”
attribute, the default functional attribute name would be “SumOfPopulation”. The
expression for the functional attribute is “<Function>(<Attribute>)”, for example,
“SUM(Population)”.
• [Function] > Multiple Attributes—Opens the Multiple Attributes dialog box for
creating multiple new functional attributes as in the previous bulleted item, one per
chosen attribute from the list of all attributes from the input feature class or query that
is of a data type valid for the selected function. After checking appropriate attributes,
clicking OK dismisses the dialog box and returns one new output functional attribute
for each attribute chosen.
Properties—Opens the Functional Attribute dialog box for reviewing or editing

functional attributes, as does the Properties button.
Delete—Deletes selected functional attributes, as does the Delete button.
To define aggregation:
1. Select Analysis > Aggregation.
10-94
2. Select a summary feature class or query from the Aggregate to summary features in
drop-down list.
3. Select a detail feature class or query from the From detail features in drop-down list.
4. Optional: On the Spatial Aggregation tab for spatial aggregation, check the
Aggregate where summary features check box; then select the appropriate spatial
operator from the drop-down list.
5. Optional: On the Attribute Aggregation tab, select the attribute pair(s) from the
Summary attributes and Detail attributes lists; then click the down arrow to add the
attribute pair(s) to the Selected attribute pairs list.
6. Optional: On the Output tab, select an operator from the Resolution operator drop-
down list.
7. On the Output tab, click New and define at least one output functional attribute on the
Functional Attribute dialog box.
8. Optional: Change the default query name and/or type a description in the Output
aggregation as query field.
9. Verify that the Display aggregation in map window check box is checked, and
change in the Map window name field, if appropriate, the map window in which to
display the aggregation.
OR
To not display the aggregation in a map window, uncheck the Display query in map
window check box.
10. Optional: Click Style, and change the default style on the Style Definition dialog box.
10-95
11. Verify that the Display aggregation in data window check box is checked, and
change in the Data window name field, if appropriate, the data window in which to
display the aggregation.
OR
To not display the nongraphic attributes of the aggregation in a data window, uncheck
the Display aggregation in data window check box.
12. Click OK to generate the aggregation.
Aggregation versus Analytical Merge

This section highlights the similarities and differences between Aggregation and
Analytical Merge.
Similarities of Aggregation and Analytical Merge

With both of these commands the following are true:
• The output is a query.
• You assign our own functional attribute name.
• Updates (notification) are dynamic.
• Queries update when the record set is created, when the connection is opened, and
when notification occurs.
Differences between Aggregation and Analytical Merge

The following are true for the Aggregation command:
• Two feature classes are used per query record sets, summary feature and detail feature
• No summary record is left out of the resultant query.
The following are true for the Analytical Merge command:
• One feature class is used per query record.
• The output attributes are limited to Geometry, ID, and user-defined functions.
• Each function takes multiple input, and outputs a single resultant value.
10-96
Generating Base Geometry

Generate Base Geometry generates topological base geometry (edges, faces, and nodes)
for point, linear, area, and compound feature classes; it decomposes these features into
topological pieces. For example, you could input Area boundaries representing Counties
and generate Edges that are lines (as opposed to areas).
The following table shows the topological types enabled for selection, and the default
selection, given the input feature type:
Input feature type Topological types Default selection
selectable
Point Nodes Nodes
Line Edges, Nodes Edges
Area Edges, Nodes, Faces Edges
Compound Edges, Nodes, Faces Edges
You can also select multiple output types when they are enabled.
This command takes a feature class or query as input and outputs a read-only query that is
appended to the query folder. The resultant query has a compound geometry type and
contains the following two attribute fields:
• OutputType (integer) — Indicates the output topological type; 1-Edge, 2-Face, 4-
Node.
• FeatureCount (integer) — Indicates the number of features that contribute to the given
base geometry.
Once you select a feature, a default query name, which you can override, is generated
automatically. You also have the option to display the query in a map window and/or a
data window.
10-97
To generate base geometry:

1. Select Tools > Generate Base Geometry.
2. Select the feature class from the Generate base geometry from drop-down list.
3. Check the appropriate Output types check box(es).
4. Accept or override the default query name (Base Geometry of <featurename>) in the
Query name field, and type an optional Description.
5. To display the base geometry in a map window, verify that the Display in map
window check box is checked.
6. Accept the default, select, or type a Map window name, and optionally the Style.
7. To display the base geometry in a data window, verify that the Display in data
window check box is checked.
8. Accept the default, select, or type a Data window name.
9. Click OK to generate and to display the base geometry in the specified map and/or
data window.
Workflow for Dashed and Patterned Area Boundaries

Applying a dashed line style or a patterned line style to area boundaries can often produce
undesirable results when the area boundaries are coincident, as in the following example.
10-98
In the preceding example, adjacent area boundaries have the boundary line dashed twice
where the coincidence is occurring. The end result is that the coincident boundary lines
rarely appear as defined by their style definition. This can happen within a feature class, or
across feature classes.
This problem can be rectified using the Generate Base Geometry command, as in the
following example.
.
In the preceding example, it is obvious that the coincident area boundaries are only being
dashed once, as opposed to the first example. This is because the Generate Base
Geometry command produces a query composed of compound geometries based on
topological edges; there are no linear duplicates in the output query. Instead of placing
duplicate geometries, a single geometry is placed and attributed with a feature count that
identifies the number of base features encountered.
The following example illustrates the result of running the Generate Base Geometry
command on the States feature class in the sample data set.
In the preceding example, because there are no duplicate geometries, any dashed or
patterned line styles applied will produce the appropriate symbology, as specified on the
Style Properties dialog box. However, you may want to separate the linear instances
based on their feature count, as seen in the following example.
10-99
In the preceding example, an Attribute Query was performed on the Base Geometry of
States query (produced by the Generate Base Geometry command). All interior lines
were coincident boundaries, thus their feature count was greater than one. None of the
exterior lines were coincident, thus their feature count was equal to one. Once the
geometry has been separated, it can be turned on or off as necessary to achieve the
appropriate result. This can be useful if you only want to portray a segment of the area
boundary. An example application of this would be to turn off state boundaries along coast
lines. The Generate Base Geometry command only supports a single feature class or
query as input. When trying to separate coincident boundaries across feature classes, you
can run the Generate Base Geometry command on the two feature classes, and then you
can use the Spatial Difference command to subtract one boundary from another.
Selecting Attributes
The Attribute Selection command lets you output a subset of input attribute fields from a
feature class or query. In addition, you can change the names of the fields and reorder the
fields. Thus, you can tailor your processing so that the results do not contain unnecessary
attribute data. This command will be enabled if at least one open connection exists in the
GeoWorkspace.
To select attributes:
1. Select Analysis > Attribute Selection.
10-100
2. Select the feature class or query whose schema needs to be altered from the Select
attributes from drop-down list.
3. Select the appropriate Attributes check boxes.
Note: You can use the Select/Unselect All buttons to aid the selecting/unselecting
process. Also, when you hover over an entry in the list, a tooltip is displayed
indicating the original name of the field.
4. Optional: Click Rename to rename an attribute.
10-101
Note: Double clicking on an entry in the Attributes list also opens this dialog box.
attribute selection as query fields.
8. Verify that the Display in map window check box is checked, and change in the Map
window name field, if appropriate, the map window in which to display the merge.
OR
To not display the merge in a map window, uncheck the Display in map window
check box.
10. Verify that the Display in data window check box is checked, and change in the Data
window name field, if appropriate, the data window in which to display the merge.
OR
Display in data window check box.
11. Click OK to generate the attribute selection query.
Editing Attribute Selection Queries through the Queries

Command
You can also edit attribute selection queries through the GeoMedia Analyze > Queries
command. To do this, you first select a attribute selection query from the list of queries
displayed on the Queries dialog box and then click Properties. This displays the
following form of the Queries Properties dialog box.
10-102
Combining Feature Classes and Queries

The Union command lets you combine multiple feature classes, categories, reference
features or queries from different warehouses and with different schemas. You can thus
use this command to combine different data sources into common views for analysis and
integration. For example, you could use this command to combine different sets road
features as in the following figure.
The functionality of this command parallels the union capability provided by SQL and
most relational database management systems. A union provides the ability to record-wise
append multiple tables/views (relations) in query results to create an output that is the
logical union of the input. It can be thought of as appending together the records of many
source inputs. In this sense, it is the record-wise equivalent to the column-wise
concatenation provided by the Join command capability.
10-103
Note: The Union command performs a relational union of the chosen feature classes and
queries. It does not perform a geometric union of features.
You would use the Union command, for example, in the following scenario. You have
feature classes of 100 different counties from 100 different database schemas, and you
would like to merge (record-wise) all 100 different counties records, and output the results
into one feature class. To do this, you would perform a union to create an output query and
then use the Output To Feature Classes command to output the results into a database
warehouse.
The Union command requires that the corresponding attribute columns from the selected
feature classes/queries should be of the same data type. This command raises the
following error when there is a mismatch in the common attributes for the selected feature
classes: “Unable to retrieve output query from union operation. The field’s size does not
match for field FIELD1.”
You need to resolve the disparities in the attribute data-types as raised by the Union
command.
See “Working with Joins” in this chapter.
Specifically, with this command you can perform the following:
• Select multiple feature classes, categories, and reference features from multiple
connections and queries.
• Select the output schema mode.
• Reorder records.
• Select, rename, and reorder output attributes.
You can select multiple feature classes, categories, and reference features across different
connections and queries for output, but you must select at least two feature classes/queries
to use this command.
The Advanced button on the Union dialog box lets you select the output schema mode.
You can do this only after the selected features (any corresponding attribute mismatches
should be resolved) have been determined to be correct for performing a union operation.
The following three output schema modes are available:
• Schema of the first selected feature class/query—The output attributes are
determined by the first of the selected feature classes/queries.
10-104
• Union of schemas from all selected feature classes/queries—The output attributes

are determined by all the features. The attribute appears in the resultant query if it is in
at least one of the selected feature class/queries.
• Intersection of schemas from all selected feature classes/queries—The output

attributes are determined by all the features. The attribute appears in the resultant
query if it is in all the selected features classes/queries.
This command raises an error when there are conflicts arising due to geometry field
mismatch.
10-105
In determining a match in geometry fields, the coordinate system definition of the fields is
disregarded – in other words, fields are allowed to form a union despite a difference in
coordinate system.
To combine feature classes and queries:

1. Select Analysis > Union.
2. Select the appropriate node(s) and/or feature check boxes in the Union features in list.
Note: If you want to output all feature, categories, and reference features classes from
a particular connection or query node, check the parent node. Similarly, if you
uncheck the parent node, all the subordinate nodes are unchecked. Also, each
feature/query node has a bitmap associated with it indicating the geometry type.
3. Optional: Click Attributes.
10-106
4. Select the appropriate Attributes check box(es).

5. Reorder the attributes (use the arrow buttons and/or Select/Unselect All buttons)
and/or Rename (click Rename and use the Rename Attribute box); then click OK on
the Attributes of <feature name> dialog box.
Note: Double clicking on an entry in the Attributes list also opens the Rename
Attributes dialog box.
6. Optional: Click Advanced, which is enabled when you check at least two feature or
query nodes in the Union features in list.
10-107
7. Select the appropriate Output schema mode, reorder the feature classes/queries as
needed by using the arrow buttons, and then click OK.
8. Optional: Click Attributes, which is visible only in query edit workflows. Follow the
workflow on the Attributes of <feature name> dialog box in Step 3.
union as query fields.
10. Verify that the Display in map window check box is checked, and change in the Map
window name field, if appropriate, the map window in which to display the merge.
OR
To not display the merge in a map window, uncheck the Display in map window
check box.
12. Verify that the Display in data window check box is checked, and change in the Data
window name field, if appropriate, the data window in which to display the merge.
OR
Display in data window check box.
13. Click OK to generate the attribute selection query.
Editing Union Queries through the Queries Command

You can also edit union queries through the GeoMedia Analyze > Queries command. To
do this, you first select a union query from the list of queries displayed on the Queries
dialog box and then click Properties. This displays the following form of the Queries
10-108
Properties dialog box, which you complete with a workflow similar to that used with the
Advanced dialog box and the Attributes of <feature name> dialog box.
10-109
10-110
Linear Referencing
This chapter outlines the basic concepts behind the linear referencing capabilities contained
in the LRS Precision Location and Dynamic Segmentation commands. This chapter
also describes the major components of a Linear Referencing System (LRS) and provides
table descriptions. Lastly, it discusses the LRS Precision Location and Dynamic
Segmentation commands
The intent of these commands is to extend the accessibility of basic linear referencing
capabilities within customers’ organizations. The available GeoMedia Transportation
Manager and GeoMedia Transportation Analyst products provide more full-featured linear
referencing capabilities as well as robust routing capabilities.
What is Linear Referencing?

Linear referencing is simply the tracking and analysis of data that is associated with
locations along a linear network. Some road transportation examples include tracking the
location of and condition of signage, the condition of pavement, and the location and
severity of accident occurrences. One of the biggest uses of linear referencing is Asset
Tracking.
Asset Tracking primarily encompasses the following
four items:
• What, where, and when of the assets (for example, a
pothole at kilometer post 41.7 along Route 66,
reported June 6th, 2007)
• Asset conditions (for example, a stretch of pavement
with rutting and cracking)
• Incidents along the network (for example, a traffic
accident)
• Activities along the network (for example,
construction projects)
11-1
LRS Terminology
In order to understand the functioning of the Linear Referencing System, you should
become familiar with its terminology, as follows:
LRS (Linear Reference System)—The total set of data and procedures for determining
specific points along a roadway.
LRS Datum—The basic, linear geometry of an LRS with its key identifiers and measures.
Event—Any feature, characteristic, or occurrence along a road (for example, accident,
bridge, road condition).
LRM (Linear Reference Method)—The technique used to specify where an event occurred
along a road (an accident occurs at kilometer marker 4, stop sign at the intersection of
Main Street and Elm).
Traversal/Route—Set of segments in a certain order and direction.
Milepoint/Kilometer Point/Log Mile—Distance measurement from the beginning of a
route.
Segment—Continuous section of roadway (that is, intersection to intersection).
Marker—Start and endpoint of segments, often Intersections. Events are frequently
measured as an offset of a marker.
Linear Referencing and Geospatial Technology

The main impetus to merge linear referencing with geospatial technology can be summed
up simply: it is often desirable to view location data on a map. It also opens up a lot of
other analysis capabilities, such as summing up data within an area feature (for example,
the kilometers of rail track that require maintenance within a given jurisdiction) or finding
data within a proximity of linearly referenced data (for example, finding residences within
a buffer zone of a construction project).
Using the Dynamic Segmentation command is not the only way to merge linear
referencing and geospatial technology, but it is certainly the easiest. This command
enables you to create map features, including pavement conditions, accident data, and
average daily traffic. This kind of information will help you plan improvements for
deteriorating assets, will identify where your organization is spending its money, and will
provide critical information clearly and accurately to all participants involved in your
projects. This can increase the value of your data by turning it into business-critical,
decision-support information.
11-2
Linear Referencing
The preceding diagram shows a portion of road on the left and its geospatial representation
on the right. The road has kilometer posts that indicate cumulative linear measures along
the road. It also has a road name, Highway 6 in this example. A section of fencing along
the road is also shown in both the left and right views. Based on the kilometer posts, it can
be determined in the field that this stretch of fence runs along Highway 6 from kilometer
measure 2.0 to 2.6.
On the geospatial side we have three linear features, known as LRS Linear Features, that
will all have a road name and begin and end measure attribution. These LRS Linear
Features are the backbone of the LRS and are used in automating the mapping of linearly
referenced data, such as this stretch of fencing, onto a map window.
Of course, this mapping of linearly referenced data does not have to be automated.
Without the Dynamic Segmentation command, you can estimate where kilometer
measures 2.0 and 2.6 are along the road, and then you can digitize a linear feature between
these two points and along the road. This is not too hard for a few features, but what if you
have a tabular report for hundreds or thousands of linearly referenced items that you want
to map? With the Dynamic Segmentation command, all of these items can be mapped
with a single command.
The methodology used to do this bulk mapping of linearly referenced tabular data is called
Dynamic Segmentation (or linear geocoding). This methodology interpolates the location
of linearly referenced data along the LRS Linear Features by making use of the road (or
rail, ferry line, and so on) name and the measurement attributes stored on those features.
11-3
LRS Linear Features and Event Data

As mentioned before, LRS Linear Features are the backbone of the LRS. But working
with the linearly referenced tabular data, known as Event Data, is the whole reason for
building the LRS in the first place. The following is a brief summary of the data structures
of these two components.
See the “LRS Data Structures” appendix for a detailed description.
The LRS Linear Features represent the network itself. Each LRS Linear Feature table is a
linear feature class that has the following fields:
• ID—This is a long integer value that uniquely identifies each feature within the table.
• LRSKeys1-4—This is one to four fields that together define the route that this feature
belongs to.
• StartMeasure—This is a numeric value that contains the measurement value for the
beginning of this feature.
• EndMeasure or Duration—This is a numeric value that contains either the
measurement value for the end of this feature or the length measurement for this
feature.
• BeginMarker (optional)—This field stores a name for the beginning position of this
feature. This is referred to as an internal marker.
• EndMarker (optional)—This field stores a name for the end position of this feature.
This is referred to as an internal marker.
• ReversedGeometry (optional)—This Boolean (True/False) field declares whether the
software should treat this linear feature as is it is (False) or as if its digitizing direction
were reversed and its beginning were its end, and vice-versa (True).
The Event Data represents the linearly referenced data. Note that Event Data can either be
point data (occurring at just one spot on the linear network) or linear data (occurring at a
span of distance along the linear network). Each Event Data table is (usually) a non-
graphic table that has the following fields:
• ID—This is a long integer value that uniquely identifies each record within the table.
• LRSKeys1-4—This is one to four fields that together define the route that this record
lies along.
• Measurement data (pick one of the following options):
o Measure Option—For point event data, this consists of one numeric Measure field
that indicates the relative location of the point event record on the route defined by
the LRS Key fields. For linear event data, this consists of two numeric fields: a
StartMeasure field and an EndMeasure field. These define the relative location of
11-4
Linear Referencing
the start and end points of the linear event record on the route defined by the LRS
Key fields.
o Marker Offset Option—For point event data, this consists of a Marker name field
and a numeric Offset distance field. The point event data is located by first locating
the marker and then by adding the offset distance to that location. For linear event
data, there are two Marker fields and two Offset fields defining the start and end of
the linear event record.
o Coordinate Option—For point event data, this consists of two fields that, depending
on the referenced Coordinate System File, may be either projected coordinates (for
example, Northing & Easting) or geographic coordinates (Latitude & Longitude).
For linear event data, there are four fields defining the coordinates for both the start
and the end of the linear event record.
o Duration Option—This is a slight variation on the Measurement Option and only
applies to linear event data. It consists of a StartMeasure field and a Duration (or
Length) field that together define the relative location of the record along its route.
• Other Attributes (optional)—These are optional, but they are also the whole reason for
doing linear referencing. For bridge events, these will store bridge data; for accident
events, they will store accident data; and for pavement events, they will store pavement
data.
Other optional components of the LRS are the External Markers. External Markers mark
points along the network just like the Internal Markers discussed earlier, but these are not
bound to just the beginning and end of LRS Linear Features. External Markers can occur
anywhere along the LRS network and are functionally equivalent to point-event data using
the Measure option. They are useful for modeling milestones and monuments that are
commonly used to measure locations from. They can be used, along with Internal
Markers, to locate event data using the Marker Offset option.
Each External Marker table is (usually) a non-graphic table that has the following fields:
• ID—This is a long integer value that uniquely identifies each record within the table.
• LRSKeys1-4—This is one to four fields that together define the route that this record
lies along.
• Measure—This is a numeric field that indicates the relative location of the External
Marker on the route defined by the LRS Key fields.
• MarkerName—This field stores a name for this Marker.
11-5
The GeoMedia Transportation Manager software, available separately, provides

specialized tools for creating and validating an LRS Linear Feature class as well as tools
for populating Event Data and External Marker tables. GeoMedia Transportation Manager
is an add-on product to GeoMedia.
Linear Referencing Commands

This section briefly describes the major LRS Analysis tools provided in this software.
Detailed instructions on how to use each of these commands is provided in the following
sections of this document.
LRS Precision Location – This command gets real-time LRS locations of your cursor
location in the map window. With it you can also use key-ins of LRS locations to place
points in the map window. You may use these points just for orientation, but you can also
use them for placing vertices of new geometry.
For more information, see the “Working with the LRS Precision Location Command” in
the next section of this chapter.
Dynamic Segmentation – This command, which has already been referred, takes linearly
referenced tabular data and creates a graphic query class from it that can be viewed in the
map window. You can thus visualize your organization's inventory of assets more clearly
than by simply reviewing tabular data.
For more information, see the “Working with the Dynamic Segmentation Command”
section of this chapter.
Working with the LRS Precision Location Command

The LRS Precision Location command allows you to determine the LRS position
corresponding to a point on the map or, alternately, to locate a point on the map according
to the LRS position you keyed in.
For LRS readout, as you move along or click on the LRS feature on the map window, the
corresponding LRS position consisting of LRS key fields, measure value, and marker
name/marker offset (if applicable) will be displayed in the LRS Precision Location
control. Similarly, for LRS key-ins, when you type the LRS information consisting of
LRS key fields, measure value, or marker name/offset in the dockable control, the
corresponding location is highlighted in the map window and is supplied to any active
GeoMedia command.
11-6
Linear Referencing
To perform precision location:

1. Open the GeoWorkspace connected to the data source containing the linear referenced
network.
2. Select Tools > LRS Precision Location.
3. From the LRS features drop-down list, select the appropriate linear network feature
class, reference feature, category, or query to be used for performing LRS Key-in or
Readout.
4. Select the appropriate model from the LRS model drop-down list.
For more information on the different LRS Models supported, see the “LRS Data
Structures” appendix.
Note: If the GeoMedia Transportation product is available, the LRS Model drop-down
list and the LRS properties are automatically filled out when a Display LRM query is
selected from the LRS features drop-down list. These restored properties are not
directly editable. They are defined using the GeoMedia Transportation LRS
Metadata Definition command.
5. Click LRS model > Properties.
11-7
6. In the LRS key fields, select the Primary, Secondary, Tertiary, and Quaternary
keys of the LRS feature class for as many keys as you use.
7. In the LRS unit field, select the unit for the measures of this LRS feature class.
8. In the LRS definition fields, if you selected a Measure model type, select the names of
the Start measure and End measure from the drop-down lists.
If you selected a Duration model type, select the names of the Start measure and
Duration (length) from the drop-down lists.
If you selected an Internal Marker model type, select the names of the Begin marker
and End marker (End marker is optional) from the drop-down lists.
9. Optional: In the Geometry reversed field, select the Boolean (true or false) field
name that defines whether to use the digitizing direction of each linear feature as its
direction (Geometry Reversed is False) or to assume that the direction of the linear
feature is the opposite of its digitizing direction (Geometry Reversed is True). This
field is optional and, if not used, it is assumed that the digitizing direction of each
linear feature is its direction of increasing measures.
10. Click OK after setting the appropriate values or Cancel to discard your changes.
If, in Step 3, you picked an LRS model that uses external measure markers, continue with
the following step. If not, skip to Step 17.
11. In the Marker features section of the LRS Precision Location dialog box, click
Properties.
11-8
Linear Referencing
12. In the Marker key fields, select the Primary, Secondary, Tertiary, and Quaternary
keys of the Marker feature class for as many keys as you use.
13. In the Name drop-down list, select the marker name for the Marker feature class.
14. In the Measure drop-down list, select the measure for the Marker feature class.
15. In the Marker unit drop-down list,, select the unit of measure for the Marker feature
class.
You are returned to the LRS Precision Location dialog box.
17. If you are using one of the LRS Models that makes use of Markers (LRS Measure
With Internal Measure Markers, LRS Measure With External Measure Markers,
LRS Duration With Internal Measure Markers, or LRS Duration With External
Measure Markers), select one of the two Marker measure options for Readout
options: Positive or negative offset from nearest marker or Positive offset only.
18. Select the size of the LRS Keys Field and the Measures and Markers Field from the
drop-down lists.
19. Select the Point style settings as follows:
• Check Display point on mouse move to display a point on a mouse move.
• Check Display point on mouse click to display a point on a mouse click.
• Check Display point on key-in to display a point on key-in.
The corresponding Style buttons display a default point style, which you can change
by clicking the appropriate Style button.
20. Check the Display Readout dialog for multiple LRS features check box if you want
to display the Readout dialog box on mouse click when there are multiple LRS
features within the tolerance zone at the specified point on the map.
21. Check the Display errors check box to display any errors on mouse click that may be
found while trying to specify the point on the map window.
11-9
22. Click OK.
The dialog box is dismissed, and the LRS Precision Location dockable control is
displayed.
23. You can display the LRS Precision Location dialog box again by clicking the dialog
box button . This dialog box lets you change the LRS model, LRS feature, LRS
Properties, the Marker measure options, LRS Keys field size, Measure and Markers
field size, point style settings, and/or Readout options on mouse click.
24. Select the down arrow button to the right end of the LRS Precision Location control,
and check the readout options you want.
The Update LRS position on mouse move option dynamically updates the LRS
readout as you move the cursor across the map window. The Update LRS position on
click option updates the LRS readout when you click the mouse in the map window.
You can select any combination of these options.
25. With the Update LRS position on mouse move option or the Update LRS position
on click option, a point is displayed (or not) based on the symbology chosen in Step
19. LRS keys are displayed in the first field separated by commas. The measure is
displayed in the second field. If the LRS Model selected was one of the Marker
models, the measure is followed by a comma, the marker name, a colon, and the offset
distance.
26. When there are multiple LRS features within the tolerance zone at the specified point
on the map, the LRS Readout dialog box is displayed based on the selection made in
11-10
Linear Referencing
Step 20. You can click Previous and Next to scroll through the various readout
possibilities found within the tolerance zone.
27. You can also use the LRS Precision Location control to supply data points to other
GeoMedia commands. First enter whatever GeoMedia command you want (for
example, Insert Feature). Next select the LRS Keyin button at the far right of the
LRS Precision Location control.
28. Type the Input LRS Key Values and Input Location Values into the LRS Keyin
dialog box. Click Apply when you are ready to process your typed values. The point
defined by your LRS reference is supplied to the GeoMedia command just as if you
had clicked in the map window. Repeat to create additional points. Click Close to exit
the LRS Keyin dialog box.
29. To exit LRS Precision Location and to dismiss the control, select the down arrow
button to the right end of the LRS Precision Location control; then select Exit LRS
Precision Location.
11-11
Working with the Dynamic Segmentation Command

This section provides an overview of the Dynamic Segmentation command. Dynamic
Segmentation is the process of generating geometry for events (event features) based on a
Linear Referencing System (LRS).
Event features contain sufficient LRS information such that they can be dynamically
segmented to produce geometry based on an LRS feature class. Typically, events do not
contain geometry, so they cannot be displayed in a map window unless dynamic
segmentation is performed. Events can be in a variety of formats, as described in the
following discussion.
The validation and correction of anomalies in the LRS should be performed before the
Dynamic Segmentation command is used. This ensures that the proper analysis results
are returned.
Note: Automated tools for LRS validation are available in the GeoMedia Transportation
Manager product.
The following capabilities are provided with the Dynamic Segmentation command:
• Use any linear feature for dynamic segmentation that exposes a measure from any data
connection that supports graphic features.
• Use a query of a linear feature for dynamic segmentation.
• Support for the LRS Measure, LRS Measure with Internal Markers, LRS Measure with
External Measure Markers, LRS Duration, LRS Duration with Internal Markers, and
LRS External Measure Markers models.
• Create dynamically segmented events that are laterally offset from the source linear
features. The lateral offset can be a distance defined by an entered constant, a variable
distance based on a database attribute, or a combination of both.
• Define up to four key fields for the LRS feature.
• Select an event table from any connection for dynamic segmentation.
• Use a query of an event table for dynamic segmentation.
• Dynamically segment linear and point event data.
11-12
Linear Referencing
• Support of the following event referencing methods:

o Measure o Longitude/Latitude o Duration
o Projected XY coordinates o Marker Offset
• Support of single and multi-level LRS features. For a multilevel LRS, you use a
Display LRM query as the LRS feature. The LRS model and LRS properties are set
using extensions on the Display LRM query and are read only.
• Support of datum-based events. To define datum-based events, you select a Display
LRM query as it has the required extensions to access LRS Metadata details. The
Datum based option on the Dynamic Segmentation dialog box is enabled only if the
selected LRS feature is a multi-level LRS Display LRM query. This option is
disabled if the selected LRS feature is not a Display LRM query or if it is a single level
LRS Display LRM query. The LRM based option is also enabled when the Datum
base option is enabled.
• Resolve multiple events that occur at the same location by assigning a different offset
distance value for each event so that events are not displayed on top of one another,
thus differentiating overlapping event records. Whenever linear or point events
overlap, the value of the Occurrence field is incremented for each successive linear
event. This occurrence value can be used in conjunction with the offset display
capability to show these events side by side to make the results clearer, as in the
following examples:
• Create dynamically segmented events that are laterally offset from the source linear
features. The lateral offset can be a distance defined by an entered constant, a variable
distance based on a database attribute, or a combination of both.
• Create dynamically segmented point events that are rotated. The rotation can be an
angle defined by an entered constant, a variable rotation based on a database attribute,
or a combination of both.
• Choose which of the event data attributes are passed through to the dynamically
segmented events, and to reorder and/or to rename these attributes.
• Choose to take the height (Z coordinates, 2D or 3D) into consideration when
performing linear referencing,
The results are output as a query to a map window and/or a data window.
11-13
To perform dynamic segmentation:

1. Open a GeoWorkspace; then connect to the warehouse containing the linear feature
class to be used for dynamic segmentation. If the event feature class is in a different
warehouse, make a connection to that warehouse also.
2. Select Analysis > Dynamic Segmentation.
3. Select the appropriate linear network feature class, reference feature, category, or
query to be used for dynamic segmentation from the LRS features drop-down list.
4. Select the appropriate model from the LRS Model drop-down list.
For more on the different LRS Models supported, see the “LRS Data Structures”
appendix.
Note: If the GeoMedia Transportation product is available, the LRS Model drop-down
list and the LRS properties are automatically filled out when a Display LRM query is
selected. These properties are not directly editable. They are defined using the
GeoMedia Transportation LRS Metadata Definition command.
5. Click LRS Model > Properties.
11-14
Linear Referencing
6. In the LRS key fields drop-down lists, select the Primary, Secondary, Tertiary, and
Quaternary keys of the LRS feature class for as many keys as you use.
7. In the LRS unit drop-down list, select the unit for the measures of this LRS feature
class.
8. In the LRS definition fields drop-down lists, select the names of the Start measure
and End measure if you selected a Measure model type.
If you selected a Duration model type, select the names of the Start measure and
Duration (length).
If you selected an Internal Marker model type, select the names of the Begin marker
and optional End marker.
9. In the Geometry reversed drop-down list, select the Boolean (true or false) name that
defines whether to use the digitizing direction of each linear feature as its direction
(Geometry Reversed is False) or to assume that the direction of the linear feature is the
opposite of its digitizing direction (Geometry Reversed is True). This field is optional
and, if not used, it is assumed that the digitizing direction of each linear feature is its
direction of increasing measures.
If, in Step 3, you picked an LRS model that uses external measure markers, continue with
the following step. If not, skip to Step 18.
11. In the Marker features section of the dialog box, click Properties.
11-15
12. In the Marker key fields drop-down lists, select the Primary, Secondary, Tertiary,
and Quaternary keys of the Marker feature class for as many keys as you use.
13. In the Name drop-down list, select the marker name for the Marker feature class.
14. In the Measure drop-down list, select the measure for the Marker feature class.
15. In the Unit drop-down list, select the unit of measure for the Marker feature class.
You are returned to the Dynamic Segmentation dialog box.
17. Select the appropriate Event feature option, LRM based or Datum based.
18. Select the connection and event feature class reference feature, category, or query to be
dynamically segmented from the Event feature drop-down list.
19. Optional: Click Filter to filter event features by specifying a filter string on the Filter
dialog box to select a subset of event features.
20. Click Event feature > Properties.
11-16
Linear Referencing
Note: Only those attributes selected in the Attributes dialog box are populated in the
Key fields and Measure fields. If you display the Properties dialog box before the
Attributes dialog box, all the attributes are populated.
21. Select the appropriate Event type option.

22. Select the appropriate Event reference type option.
23. In the Key fields drop-down lists, select the Primary, Secondary, Tertiary, and
Quaternary keys of the Event feature class for as many keys as you use.
24. In the Measure fields drop-down lists, select the available names that are appropriate
for your selection of the Event type and the Event reference type.
25. In the Unit drop-down lists, select the unit for the event feature class (the default is the
unit you set for the Distance on the Units and Formats tab of the GeoWorkspace
Coordinate System dialog box).
26. If your Event reference type is Coordinate, continue with the next step to set the
coordinate system information for the selected events. If not, go to Step 33.
27. Click Browse in the Event coordinate system section to locate and then to select an
existing coordinate system file (.csf file) from the Browse for Coordinate System File
dialog box.
OR
Click Define/Modify Coordinate System to define a new coordinate system file.
11-17
28. Select the Coordinate system type, and set or modify the coordinate system.
See the “GeoWorkspace Coordinate System Dialog Box” topic in GeoMedia Help for
more information.
If you want to use the coordinate system from the current GeoWorkspace, you can do
this by first saving it to a .csf file by selecting View > GeoWorkspace Coordinate
System from the GeoMedia menu bar. This displays the GeoWorkspace Coordinate
System dialog box on which you click Save As and then assign it a filename and
location.
You are returned to the Event Properties dialog box.
30. If your Event reference type is Coordinate, type a numeric value for the coordinate
tolerance in the Coordinate tolerance field (the unit for this value is the one you set for
the Distance on the Units and Formats tab of the GeoWorkspace Coordinate System
dialog box).
32. Click Event feature > Attributes.
11-18
Linear Referencing
33. Select those attributes that you want reflected in the output query, using Select All and
Unselect All to speed this process.
34. Optional: Use the up, down, move first, and move last arrow buttons to specify the
position of an attribute in the output, and/or click Rename to change the name of an
attribute in the list (Attributes specified for the Key fields and Measure fields cannot
be renamed.).
35. Click OK after setting the appropriate values.
36. Click Advanced Display Settings.
37. Check the Occurrence > Compute occurrence value; then type the Measurement
tolerance, and select a proper unit.
Use this option if you want to have the software calculate a field having an integer value
that increases for each overlapping event record. This can be used in conjunct with the
Offset capability in the next step to visually offset overlapping event data.
11-19
38. Check the Offset > Constant check box to display the result with a constant offset; then
type a value, and select a proper unit.
AND/OR
Check the Attribute check box to display the results with an offset from an attribute
field; then type an appropriate scale, and select a proper unit.
39. If the event is a point type, the Point Rotation section is enabled.
− Check the Align to LRS check box if you want the displayed result to be aligned
to the LRS feature.
− Check the Angle check box if you want to display the result in a fixed angle; then
type an appropriate value, and select a corresponding unit.
− Check the Attribute check box if you want to display the result in an angle from
an attribute field; then select an attribute.
40. In the Output results as query field on the Dynamic Segmentation dialog box, accept
the default, or type another query name in the Query name field, and, optionally, type a
description in the Description field.
41. To see the results in a map window, make sure that the check box to the left of the
Display results in map window field is checked and that the appropriate Map window
name is selected.
42. Optional: Click Style to define the display settings for the results in the map window.
43. To see the results in a data window, make sure that the check box to the left of the
Display results in data window field is checked and that the appropriate Data window
name is selected.
44. When you have made the appropriate settings, click OK.
45. When the results are returned, you can tile the windows vertically.
The workspace would then resemble the following:
11-20
Linear Referencing
46. After reviewing the result, you can change the advanced display settings by editing the
query. Do this by first selecting Analysis > Queries from the GeoMedia menu bar.
47. Select the query generated by the Dynamic Segmentation command, and then click
Properties.
48. Edit the Query name, the Description, and the Advanced Display Settings; then
click OK.
The results of the query are changed according to your new input.
11-21
11-22
Working with Labels
There are two different types of annotation in GeoMedia, text and labels. Text may be the
result of data displayed from a warehouse, or text may be created and interactively placed
with the Insert Text command. Labels may be the result of the batch labeling command
Insert Label, which lets you create and insert labels as dynamic label queries or static text
feature classes. The difference between the labeling tools and the Insert Text tool is that
the labeling tools automatically place text using feature attribute values. Insert Text
requires you to type in the text to be placed.
GeoMedia also provides two other label-related commands. The Resolve Text Conflicts
command lets you detect and resolve text overprints that occur in feature classes or queries.
The Insert Leader Line command lets you place leader lines/leader terminators for label
queries in the second part of a two-step workflow. In the first step, you use the Insert
Label command to create labels as a query and select the Enable leader lines option to set
up the leader line feature class and leader terminator query and to establish the underlying
relationships between these feature classes/queries. In the second step, you use Insert
Leader Line. Upon placement, the orientation of the leader terminator and the label
alignment setting are calculated automatically. Additionally, this command lets you move
labels and place multiple labels per feature if the Enable leader lines is selected.
See “Inserting Text Features into a Feature Class” in the “Working with Features”
chapter.
See “Resolving Text Conflicts” and “Inserting Leader Lines” later in this chapter.
Inserting Labels
With the Insert Label command, you can create labels as a query or as a feature class,
depending on how you want the labels to behave and what you want to do with them in the
map window. In both cases, the attributes of the original feature (the additional columns)
are copied to the label feature. However, in a query label the attributes are dynamically
linked so that a change made in the original feature attributes is reflected in the linked label
feature as well. In a feature class label, the attributes are static and not linked so that a
change in the original feature attributes is not reflected in the feature class label. Each
label creation method has its advantages.
Labels as Query—You can create labels as a query in the GeoWorkspace if you want each
label linked to the feature with which it is associated. As a query, the labels will be
updated each time you edit the labeled features or open the GeoWorkspace. When, for
example, a feature is deleted from the feature class, its label is deleted as well. Similarly,
when a new feature is inserted into the feature class, the new feature is appropriately
labeled. As a query, a label outputs as graphics text the values of the attributes you select
12-1
from a feature class or query, along with any constant text that you specify. For example, a
label query could return as text the names of each stop along a railroad route.
The content of a label output as a query is composed of text that you type and one or more
attribute values derived from attribute values stored in the warehouse. When an attribute
value changes, the text in the label associated with the feature whose attribute value has
changed will also change.
If you plan to place leader lines/leader terminators for the labels, you must create labels as
a query with the Enable leader lines option selected. If you do not, and subsequently
want to place leader lines/leader terminators for the labels, you will not be able to. In this
case, you would need to delete the labels and then insert them again as a query with the
Enable leader lines selected.
Labels as Feature Class—Labels created as a feature class do not have an active link to
attribute values or geometry. You can edit the text in the labels, and you can insert the
labels as features into a feature class in a read/write warehouse. In addition, like any other
feature you can move, rotate, and delete labels that are output as a feature class.
When you create labels as a feature class, you will not be able to place leader lines/leader
terminators for the labels. You can only place leader lines/leader terminators for labels
created as a query with the leader line option selected.
Whether you output labels as a query or as a feature class, you can define their content,
style, and layout for display in the map window. Among other things, you can display a
frame around the text in a label, give it a solid or transparent background, and define it so
its Paper (size is true at nominal map scale) (display scale dependent). By default, the
text style is defined such that its View (size is true at any display scale) (display-scale
independent).
See “Inserting Text Features into a Feature Class” in the “Working with Features”
chapter.
See “Working with Styles” and “Defining Map Window Display Properties” in the
“Working with Map Windows” chapter.
Label Placement
This command lets you set the label placement orientation, and alignment, offset, and
whether to place single or duplicate labels.
The available label placement orientation modes are as follows:
Place at angle—Places the label at the angle specified in the degrees field. This mode is
the default orientation mode, at 0 degrees. The valid range is –360 to 360 degrees. The
angle unit and precision settings are based on the default settings defined on the Units and
Formats tab of the GeoWorkspace Coordinate System dialog box.
Orient to geometry—Places the label rotated in the direction of the geometry being
labeled.
12-2
Working with Labels
The command displays the label with the rotation angle obtained from the geometry being
labeled, using the style taken from the legend entry. If there is more than one legend entry,
the style of the topmost entry is used.
The following rules for label placement apply:
• Point data—Orientation is based on the point rotation angle.
• Linear data—Orientation is based on the angle of the line from begin point to end
point.
• Area data—Orientation is based on the angle of the longest edge of the area boundary.
Labels are placed right side up and read as follows:
• 0, 180, 360 degrees—Text reads horizontal, left to right.
• 90, 270 degrees—Text reads vertical, bottom to top.
• > 0 degrees, < 90 degrees—Text reads southwest to northeast.
• > 90 degrees, < 180 degrees—Text reads northwest to southeast.
• > 180 degrees, < 270 degrees—Text reads southwest to northeast.
• > 270 degrees, < 0, < 360 degrees—Text reads northwest to southeast.
Map window rotation at the time of placement is honored. If the orientation of the
geometry is 30 degrees and the map window is rotated by 40 degrees, the labels is placed
at 70 degrees from the horizontal.
The available label alignments are as follows:
• Top left • Top center • Top right
• Center left • Center center • Center right
• Bottom left • Bottom center • Bottom right
You can specify the horizontal and vertical offsets to define the distance each label is
placed from its origin. For vertical offsets, positive values offset upward while negative
values offset downward. Similarly, for horizontal offsets, positive values offset to the right
while negative values offset to the left. The units are measured in ground units.
Finally, you can specify that duplicate labels should not be placed. This temporarily
merges contiguous multiple feature parts in a linear geometry collection to find the center
point in order to place a single label.
To create a label:
1. Select Insert > Label.
12-3
2. From the Label features in drop-down list, select a feature class from the connections,
queries, reference features, or categories for which you want to place labels.
3. To place an attribute variable in the Layout box, select it from the Attributes list.
Note: You can place as many attribute variables as you want. Values for each
attribute are extracted from the warehouse when the labels are created.
4. Place the insertion point in the Layout box where you want constant text to appear on
the label relative to the field, and type the text. For example:
The text Snow = is typed before the ANNULSNOW field, and ” is added after the
field.
In the map window, each feature with an ANNULSNOW value will display the constant
text Snow = xx”, with the variable xx displaying the value for the ANNULSNOW
attribute.
5. Select the appropriate label Orientation option, Orient to geometry or Place angle.
If you select the latter, type the appropriate label rotation angle in the deg field.
12-4
Working with Labels
6. Select the appropriate label alignment from the Alignment drop-down list.
7. Optional: To define the distance each label is placed from its origin, specify the
horizontal and vertical offsets.
8. Optional: To specify that duplicate labels should not be placed, check the Place single
label along contiguous linear features check box.
9. To output labels to a query, select the Query option. Continue with Step 10.
OR
To output labels to a feature class, select the Feature class option. Go to Step 12.
10. Accept or override the default query name in the Query name field; then type an
optional description in the Description field.
11. Optional: To enable leader lines, check the Enable leader lines check box.
12. Select the read/write connection to output the leader line feature class to from the
Connection drop-down list and select the leader line feature class name from the
Feature class drop-down list, or type in a new feature class name; then type an
optional description in the Description field.
13. Specify the map window in which to display the new labels by selecting a map
window name from the Map window name drop-down list.
14. Optional: Click Style to change the default text style.
15. Click OK to generate and to display the labels.
Inserting Leader Lines

The Insert Leader Line command lets you place leader lines/leader terminators for label
queries in the second part of a two-step workflow. In the first step, you use the Insert
Label command and select the Enable leader lines option to set up the leader line feature
class and leader terminator query and to establish the underlying relationships between
these feature classes/queries. In the second step, you use Insert Leader Line. Upon
placement, the orientation of the leader terminator and the label alignment setting are
calculated automatically. The Insert Leader Line command honors snaps and autopan.
The following illustration shows the placement of leader lines:
12-5
A leader line is composed of a minimum of two vertices, a start point and an end point.
The start point coincides with the coordinates used to define the placement of the leader
terminator. It is the first point you digitize and is the point nearest the original label
feature. The end point coincides with the coordinates of the last vertex digitized, and this
point is used to define the placement of the new position of the label at the end of the
leader line.
The following illustrates the workflow for placing leader lines:
1. Select the label to start the leader 2. Place the first vertex to place the
line. leader terminator, and the dynamic
label appears.
3. Place the end of leader line at the 4. Double click to remove the original
new location of label. label and to set the new label where
specified.
12-6
Working with Labels
Insert Leader Line performs the following tasks in placing a leader line:
1. Ensuring that the leader line feature class and leader terminator query associated with
the label selected are displayed in the legend of the active map window. It is assumed
that the label is already displayed because it must be selected.
• The leader terminator query is displayed in the active map window. The position in
the legend is right below the label selected.
• The leader line feature class is displayed in the active map window. The position
in the legend is right below its associated leader terminator query.
2. Digitizing the leader line geometry.
• The leader line can have multiple interior vertices.
• The start coordinates of the leader line are not fixed at the position of the
originating label; they can be moved by using Edit > Geometry on the leader line.
• The start point does not automatically move if the feature moves, except through
coincidence.
3. Calculating the orientation of the leader terminator point geometry at the leader line
start point.
• Leader terminators are placed as oriented point geometries. The orientation is
automatically calculated based on the angle of the leader line, from the second
vertex to the start point. This accommodates the use of arrowhead terminators to
ensure that the arrowheads align with the digitized leader lines. You should create
arrowheads with the tip of the arrow at zero degrees and the origin at the center of
the base of the arrowhead. A leader terminator symbol file (terminator.fsm) is
delivered with the software.
• Leader terminators are automatically displayed once the leader line geometry has
been digitized; otherwise, they do not exist.
4. Moving the original label from the originating start point to the newly digitized end
point.
• The new position of the label is determined by the leader line end point, that is, to
move the label once it has been placed, you must edit the leader line.
• The alignment of the newly positioned label is determined on a per-instance basis
to minimize the overlap between the label and the leader line. This is determined
by the angle calculated between the next-to-last vertex before the end point and the
end point as follows:
Degrees Alignment Degrees Alignment
>337.5 to 22.5 Center left >157.5 to 202.5 Center right
>22.5 to 67.5 Bottom left >202.5 to 247.5 Top right
>67.5 to 112.5 Bottom center >247.5 to 292.5 Top center
>112.5 to 145.5 Bottom right >292.5 to 337.5 Top left
12-7
• The originating label maintains its position and alignment until a leader line
geometry has been digitized.
• The rotation of the newly positioned label is automatically set to zero degrees
regardless of the current rotation angle of the original label (This varies based on
the orientation method used during the original placement.).
To insert leader lines:

1. In a map window with the leader line feature class and leader terminator query set up
through the Insert Label command, select the appropriate query label.
2. Select Insert > Leader Line.
3. Place the point nearest the labeled feature to begin digitizing the leader line.
As you move from the start point, a dynamic line segment is displayed, and the leader
terminator is dynamically displayed, taking into account the calculated orientation.
The label position remains fixed until the second point is digitized.
4. Place any additional leader line vertices.
After the second point has been placed, the leader terminator is placed in dynamics
using the calculated orientation. The label is displayed in dynamics at the cursor,
using the alignment calculated on the segment.
Note: Pressing BACKSPACE removes the previously placed vertex, including the
first point placed. Pressing ESCAPE before completing the leader line digitizing
opens a dialog box to stating Do you want to discard the current feature?. Click
Yes to return to the start point (Step 3). Click No to returns the previous digitizing
state.
5. Double click to end the leader line.

OR
Open the right mouse menu with the following options:
• End feature—Ends the leader line.
• Cancel feature—Same effect as pressing ESCAPE as described in the note in Step
4.
Dynamics are turned off, and the leader line is displayed from start point to end point.
The dynamic label is turned off, and the label is moved from the start point to the end
point using the appropriate calculated alignment setting. The rotation of the leader
terminator is calculated, and the newly rotated leader terminator is displayed.
See “Inserting Labels” earlier in this chapter.
12-8
Working with Labels
Moving Labels
The Insert Leader Line command also lets you move labels you have already placed with
the Insert Label command. The procedure is similar to that for placing a leader line
except that before starting the command you turn off the leader lines and leader terminators
in the legend. You then proceed as if you were placing leader lines and move the selected
label to an appropriate new location in the map window.
To move existing labels:

1. In a map window, turn off the leader line feature class and leader terminator query in
the legend.
2. Select the appropriate query label.
3. Select Insert > Leader Line.
4. Place a start point; then place as many vertices as necessary until the label is in the
correct new location.
After the second point has been placed, the label is displayed in dynamics at the
cursor, using the alignment calculated on the segment.
5. Double click to set the label in its new location.
The dynamic label is turned off, and the label is moved from the start point to the end
point using the appropriate calculated alignment setting.
Resolving Text Conflicts

The Resolve Text Conflicts command lets you detect and resolve text overprints that
occur in feature classes or queries. The origin of the conflicts primarily come from the
Insert Label command. However, any of the commands that generate text geometries into
feature classes or queries, such as the Insert Text command, are candidates for input. This
command is especially useful for resolving the text conflicts that occur when features
originate in read-only warehouses. You must have an active map window and at least one
read-only warehouse connection to use this command.
The purpose of Resolve Text Conflicts is to separate text geometries that do not overlap
from text geometries that do overlap. The overlap condition is determined by the original
location of the text geometry, the processing scale, and the font parameters.
This command supports the output of a non-conflicting text query and a conflicting text
query. You can select one of these outputs or both simultaneously. The resulting queries
automatically display in the active map window.
You have the option of using the results of the non-conflicting text output query to display
the text feature class, or of using the conflicting text output query to assist you in
12-9
identifying the text geometries that need to be moved or deleted from the input feature
class.
Legend entry definitions for the output text queries are as follows:
• Non-conflicting text output query—Uses all of the style parameters defined using the
Font button. The View (size is true at any display scale) check box is unchecked on
the Display Properties dialog box.
• Conflicting text output query—Uses all of the style parameters defined using the Font
button, except color, which will be red. The View (size is true at any display scale)
check box is unchecked on the Display Properties dialog box.
Note: The exception to the previous two statements occurs if style override has been
used. If it has, the text will be displayed in the override style in both queries.
The following examples show results from using this command:

Results from inserting labels:
Results from resolving text conflicts:
12-10
Working with Labels
Results with conflicting queries turned off:
You could then use leader lines to move the conflicting queries.
Workflow Options
There are two different workflow options, depending on the input. The output capabilities
of this command are two queries, but the input dictates the level of interactive editing and
dynamic behavior of the modified input text:
1. Input is a query or read-only feature class—The command identifies non-
conflicting text and conflicting text. The input query items cannot be moved or
deleted, but the text string updates dynamically when changes are made to the
originating feature’s label attributes in the database. For example, if the input is a
query, changing the State_Name attribute from al to AL in the original feature would
cause the query to change, which in turn would cause the output conflict queries to
change. If the input is a read-only feature class, you cannot edit the feature class, so
the output conflicts query will not change. You will likely use this command to filter
the overprints, displaying only the output non-conflicting query in the map window
instead of the input query or read-only feature class.
2. Input is a read-write feature class—The command identifies non-conflicting text and
conflicting text. The input feature class items can be moved or deleted, but the text
string will not update dynamically when changes are made to the originating feature’s
label attributes in the database. For example, in the case where the
State_Name_Labels text feature class was based on the States feature class, and the
Resolve Text Conflicts command was run on the State_Name_Labels feature class,
changing the attribute al to AL in States will have no affect on State_Name_Labels and
thus no affect on the conflicts query. But a change to the State_Name_Labels feature
class (using Edit Text) would affect the output conflicts query.
You will likely use this command to identify the overprints (through the conflicting
text query), to move or delete them from the input feature class, and to display the
modified input feature class in the map window. Because the input labels are static,
you will have to rerun this command whenever changes are made to the originating
label attributes in the database.
12-11
Note: The Resolve Text Conflicts command determines conflicts based on the
processing scale and font size settings. To accurately display the result, set the
Nominal Map Scale (Display Properties) equal to the Processing Scale, and make
sure the View (size is true at any display scale) check box is unchecked on the
Display Properties dialog box for both output queries.
To resolve text conflicts:

1. Select Tools > Resolve Text Conflicts.
2. Select the feature class from the connections, queries, reference features, or categories
from the Resolve text conflicts in drop-down list.
3. Select the appropriate Scaling method option.
Note: If you select User-defined, type a value in the Processing scale field to change
the default value display or Nominal map scale (from the previous scale setting
selection).
4. Click Font; then select the font style parameters.

5. In the Resolution criteria area, select the Attribute-based option to identify the
conflicting text attributes. Continue with Step 6.
Note: This option is only enabled when there are numeric attributes available for the
feature class/query selected.
OR
12-12
Working with Labels
Select the Automatic option to identify the conflicts by order of placement. Go to

Step 8.
6. Select the attribute to use to filter the text conflict from the Attribute drop-down list.
7. Select the appropriate Retain text with option.
8. Optional: Select the Output non-conflicting text as query check box to output non-
conflicting text as a query.
9. Optional: Override the default query name, and/or type a description.
10. Optional: Select the Output conflicting text as query check box to output conflicting
text as a query.
11. Optional: Override the default query name, and/or type a description.
12. Click OK to generate and to optionally display the non-conflicting and conflicting text
queries.
12-13
12-14
Geocoding
The software provides three commands to perform data geocoding of your data: Geocode
Addresses and Find Address for addresses and intersections, and Geocode Coordinates
for a feature class or query based on coordinate values.
Geocoding and Finding Addresses

GeoMedia Address Geocoding lets you generate Address Geocoding Index (AGI) files,
geocode addresses, take an address in text form and locate that address as point geometry,
and geocode an entire feature class or query rendering the addresses through the Geocode
Addresses command or just a single address text through the Find Address command.
This section discusses the following GeoMedia Address Geocoding topics:
• Overview of Address Geocoding.
• Types of address geocoding data sources.
• Use of the Find Address command.
• Use of the Geocode Addresses command.
• Principles of address standardization, parsing, and transformations.
• Building an Address Geocoding Index (AGI) file using the Publish Address
Geocoding Index utility.
See the “Publish Address Geocoding Index Help” delivered with the utility.
• Introduction to the Define Parsing Rules utility.
• Creating a geocoding directory.
These topics are organized to give you an idea of how the geocoding works from a user’s
perspective. Next follows a discussion of some details about how geocoding is configured
from a GIS administrator’s perspective. The related workflows involve creating the
configuration files required to publish GIS data into the new AGI file format used for
address geocoding.
Looking at GeoMedia Address Geocoding: An Overview

GeoMedia Address Geocoding provides two application commands to work with capturing
and presenting certain specific data: Find Address and Geocode Addresses. Find
Address is a view navigational tool that finds the location of an input address and displays
it as a point centered in a map window. Geocode Addresses provides basic functionality
for address geocoding by creating point geometries for a feature class or a query based on
13-1
the input addresses or intersections. You can then display the results in a map window
and/or data window.
Address Geocoding also provides two administrative utilities that configure the data:
Publish Address Geocoding Index and Define Parsing Rules. The Publish Address
Geocoding Index utility, delivered with this product, provides the ability to publish GDO
data (feature classes) to an AGI for subsequent geocoding. The Define Parsing Rules
utility, available from Intergraph Support, helps you create a well-formed set of modified
parsing rules files conforming to the requirements for address parsing.
Key Features
Address Geocoding Index
The cornerstone of the geocoding subsystem is that geocoding operations are performed
against an index file. This new file format, Address Geocoding Index (or AGI file), is a
portable, single file. It is optimized for fast searching and matching of records.
Additionally, it can optionally include spatial-index type of information to provide high
performance reverse geocoding operations.
Note: Reverse geocoding is not supported by the desktop GeoMedia Find Address and
Geocode Addresses commands. Reverse geocoding is supported through geocoding web
services.
Address Geocoding provides tools to let you create AGI files from street centerline and
rooftop (point) datasets accessible from GeoMedia by means of the GDO data servers.
Reference (Source) Data

The geographic data used for geocoding can comprise of two basic types:
Street Centerlines—This type of dataset uses street centerlines with attributes that can be
used for searching, as well as house number ranges. Centerline geocoding is where the
underlying geographic data consists mainly of a street network or other linear data that is
attributed with left/right address ranges. The processing required in this case basically
requires finding the correct street segment and then interpolating the position based on the
address range attributes.
Rooftop Data—This type of dataset uses point features that represent discrete addresses.
Additionally, this type of dataset can be used where each valid address point (that is, a
letter box, house, apartment, delivery point) has been previously determined and is
represented by a point geometry. Rooftop geocoding is where the underlying geographic
data is represented by features of any geometry type that have identifying attributes. The
processing required in this case is basically a parse and a search for a record whose
attributes match the input.
13-2
Geocoding
The software requires that all attributes used with geocoding (that is, for matching
purposes) are present in the feature class used to build the AGI file.
Geocoding Engine
A geocoding engine is a software component designed to work with a particular data
format. Address Geocoding delivers the GeoMedia geocoding engine based on the AGI
file format. This new geocoding system provides a means whereby a third-party
geocoding engine may be plugged in.
Geocoding Dataset
A geocoding dataset is the data used by a geocoding engine. A number of datasets may be
configured to cover a large area and provide scalability. The architecture of the system
allows bulk geocoding operations to be performed across multiple geocoding datasets and
geocoding engines. The standard geocoding dataset format provided with Address
Geocoding is the AGI file.
Geocoding Directory
As the architecture of the geocoding subsystem allows for multiple datasets to be used at
one time, a simple means to refer to these is needed. A geocoding directory is an XML file
that contains information to allow geocoding engines to connect to their datasets. Each
dataset has a name, and this name is used in conjunction with a geocoding directory to use
the appropriate geocoding engine with the appropriate dataset.
Address Standardization
To allow your input to be matched with source data, both need to be standardized so more
accurate matching can be performed. An example of address standardization operations
would be to convert elements of an address to UPPER CASE, and to convert street type
to/from abbreviations (for example, Smith Street > SMITH ST).
Address Parsing
Address parsing is a technique whereby complex address text can be split into the discrete
fields that comprise the address. This process uses an advanced technique known as
Hidden Markov Modeling (HMM) to intelligently decompose, or to parse, an address into
the correct fields. These fields are commonly referred to throughout the geocoding system
as address elements.
Address Transformation
An address transformation is a slight expansion to the concept of parsing in which a
mapping between different address formats is expressed or defined.
13-3
Getting Started
To start the two geocoding commands, select View > Find Address, and Analysis >
Geocode Addresses from the GeoMedia menu bar.
To start the Publish Address Geocoding Index utility, select GeoMedia > Utilities >
Publish Address Geocoding Index from the Start menu. See the information provided
by Intergraph Support for starting the Define Parsing Rules utility.
Address Geocoding - User Concepts

Address Geocoding Terminology
In order to understand the functioning of Address Geocoding, you should become familiar
with its terminology, as follows:
Address—Description of a place that can be used to determine the location of that place in
world coordinates. An address in its most common form has a systematic structure
involving building numbers, street names, municipalities, postal codes, and so forth.
However, it may also be a much simpler description, for example, a city name, a postal
code, or a parcel ID. An address, whether simple or complex, may be expressed as a single
text string requiring highly sophisticated parsing or as a fully normalized set of atomic
values for each element in the address structure.
Address elements—Atomic units forming an address. Output elements of the parsing
rules are used to represent address elements in the address definition.
Address geocoding index (AGI)— Binary file (.agi), in a GeoMedia-proprietary format,
highly optimized and indexed for rapid geocoding. It is created by the Publish Address
Geocoding Index utility.
Address geocoding profile—XML file (.agp) containing the complete profile of a
publishing process. This file can be used to launch the Publish Address Geocoding Index
utility, or as input from the command line in batch usage.
Address matching—Process that takes a fully parsed input address and finds the best
match in the index.
Address parsing rules—Defined in files, these rules can be created either manually or
through the Define Parsing Rules utility. They are used to transform a single input string
to the address elements used in the matching operation.
Address transformation (includes address parsing)—Process that decomposes the address
into the matching attributes used (a) to build the index file, and (b) to match against the
index during geocoding operations.
13-4
Geocoding
Find Address command—A View command that geocodes an address entered through
dialog boxes, producing a dynamic point on the map display and panning to the location of
that point.
GDO warehouse—The source GeoMedia-accessible dataset that contains the features the
geocoding index is derived from.
Geocode Addresses command—An Analysis command that geocodes all of the features
in an input (normally nongraphic) feature class or query containing address information,
producing a query on output with point geometries.
Geocoding—The process of taking an address and generating a location for it.
Geocoding dataset—A dataset used as reference to perform geocoding or reverse
geocoding. The GeoMedia-delivered implementation of a geocoding dataset is the Address
Geocoding Index (AGI) file. The term geocoding dataset is used as a generic term, as this
design allows for third-party geocoding engines (and their data) to be used.
Geocoding directory—An XML document that defines the reference dataset location and
other characteristics for various geocoding engines. It consists of one or more defined
geocoding datasets, each of which has a unique identifier for the applicable runtime engine
and an associated connection string intended to link the object to its reference data source
data.
Geocoding engine interface—A COM (dispatch) interface definition that provides a
generic interface by which any number of independent (Intergraph-developed or third-
party) geocoding implementations may be written, using alternate data structures and/or
underlying software/services, and which can be plugged into the GeoMedia geocoding
system. Address Geocoding delivers an implementation of this interface specific to AGI
files.
Geocoding model—An XML document describing a geocoding model. A geocoding
model (GCM) definition describes user-recognizable address components (or fields) and
their correlation to the various elements of an address, that is, a comprehensive description
of address elements that make up a particular address structure. The relationship between
the attributes of the source data used to create the index (AGI) file, and the internal address
definition of the dataset is also defined in the GCM file. Additionally, various
AddressTransformations are defined in the GCM.
Index building—Processing the source data and building an Address Geocoding Index
file. Part of processing of the index data also involves address transformation and
standardization. The index is build with the Publish Address Geocoding Index utility.
Location—A point on the earth, which may be expressed in world coordinates (textual or
numeric) or as a point geometry.
Matching—Comparing standardized address elements in a common structure (one may
have been transformed) and selecting one or more successful or candidate matches.
13-5
Matching index—Maximum eight-character text string composed of portions of selected

address elements or their sound-like equivalents. It serves to improve geocoding
performance by limiting the elements searched within the AGI file. The matching index is
calculated for every address in a reference dataset and for every address to be matched.
During matching, the address is compared with all reference addresses having the same
value as the matching index. If the value of the matching index is the same for all
reference addresses or varies too little, the address is compared with a large number of
reference addresses and it significantly degrades the geocoding performance. An
appropriate selection of matching index is, therefore, essential to achieving an optimum
balance between geocoding performance and the matching rate.
Parsing—Decomposing the textual representation of an address into constituent address
elements according to various rules.
Reverse geocoding—Taking a location (that is, a coordinate or a point) and generating an
address for it.
Rooftop dataset—Type of dataset using point features that represent discrete addresses.
This type of dataset can be used where each valid address point (that is, a letter box, house,
apartment, delivery point) has been previously determined and is represented by a point
geometry.
Source data—The original data used to build the geocoding dataset. It contains features
such as street centerlines, which are used to convert between descriptions and locations.
Standardization—Evaluating and adjusting the parsed address elements according to
addressing rule standards.
Street centerlines dataset—Type of dataset using street centerlines with attributes that
can be used for searching, as well as using house number ranges.
Transformation—Transformation of an address with elements in one structure, for
example, an address to be geocoded to a standardized address with elements in another
structure, for example, a geocoding dataset.
Functional Overview
There are three basic operations involved in Address Geocoding:
1. Index Building—Processing the source data and building an Address Geocoding
Index file. Part of processing the index data also involves address transformation and
standardization.
2. Address Transformation (includes address parsing)—Decomposing the address into
the matching attributes used to build the index file.
3. Address Matching—Taking a fully parsed input attribute and finding the best match
in the index.
13-6
Geocoding
Finding an Address
The Find Address command lets you find the location of an input address and display it as
a point in the map window. This command performs address matching of an address that
has a defined transformation between the source (user input) and target (geocoding engine
expectant) address formats.
Specifying the input for this command is a two-step process in which you first define
parameters on the Find Address Options dialog box. You then provide additional address
details and perform the actual find through the Find Address dialog box. The Find
Address dialog box is displayed only if the geocoding directory has first been defined. If
you try to start this command and no geocoding directory is known to the command (or a
previously specified one does not exist), the Find Address Options dialog box is
displayed first to let you define the geocoding directory. (Clicking Options on the Find
Address dialog box also displays the Find Address Options dialog box.).
The Find Address Options dialog box lets you specify the following parameters used in
the geocoding process:
• Geocoding directory—Selected geocoding directory file (XML) that has information
for one or more geocoding datasets, by default in the GeoMedia Warehouses folder.
• Geocoding dataset—Dataset name to geocode against, containing all the dataset
names from the specified geocoding directory file.
If there is more than one dataset, the additional item <By address element> is added
to the top of the drop-down list. You then have the option (Address element name) of
specifying an address element whose corresponding value is used for determining the
geocoding dataset (that is, the specified address element defines the geocoding dataset
name to be used to find the address location). For example, you might use a regional
name, such as the city name, when geocoding adjacent city street networks.
• Address element name—Address element to be used to specify the name of the
geocoding dataset to be used (if a geocoding directory contains a number of named
geocoding datasets). This drop-down list is enabled only if the Geocoding dataset has
been set to <By address element>.
13-7
• Input address format—Address format supported by the selected Geocoding dataset

drop-down list box. By default, the first input address format is selected. If <By
address element> is the selected dataset, this list is populated with all the input
address formats listed in the geocoding directory.
• Minimum match score—Value (in the range 0-100) that determines if an address has
been successfully matched. If a match operation obtains a match score of at least this
value, the match status is displayed as Matched. If the match score obtained is less
than this value, the match status contains descriptive text detailing the mismatch. The
default value is 100.
• Offset distance and unit—The default offset value is two meters for centerline
geocoding. Offset is not used for intersection or rooftop geocoding. The units drop-
down list contains all available linear units and is initially set to the default linear unit
as specified by the GeoWorkspace Coordinate System command.
• Style—Point style geometry. The style can be set for optimum map window display of
the geocoded address point geometry results through the GeoMedia Select Style and
Style Properties dialog boxes, with the point style being enabled. The default style is
the default point geometry style.
The Find Address dialog box lets you specify the following parameters used in the
geocoding process and lets you start the process and view the resulting match details:
• Address element/Value grid—Contains the read-only Address element column
listing the source address elements of the chosen Input address format. The number
and name of the elements of this column are determined and populated at runtime by
your selection of the Input address format on the Find Address Options dialog box.
If an address element name is set as a required element, it is displayed in bold and red
font. If the <By address element> option is chosen for the geocoding dataset, the
address element as specified by the Address element name list is also displayed in
bold and red font.
The read-write Value column contains fields for specifying values for each of the
corresponding address elements.
• Find—After all the parameters have been defined, clicking this button starts the Find
Address geocoding operation. If an address match is returned, the map window is
13-8
Geocoding
centered at the current scale on the point geometry that is the location of the returned
address match. The match status details are populated in the Match details field.
• Options—Displays the Find Address Options dialog box, which lets you specify the
geocoding directory and other parameters used in the address geocoding process.
• Match details—Displays the following match status details returned from a geocoding
operation: Match Score, Match Status, Standardized Address, and Matched
Address.
In displaying the results, the command locates the point geometry at the center of your map
window that best matches the source address. The Find Address Options dialog box lets
you define the output minimum match score, offset distance and unit, and the style of the
point geometry using the GeoMedia Select Style and Style Properties dialog boxes.
Using the Find Address Command

The following sample workflow gives you an introduction to finding an address. The
objective is to find the location of the following address in Knox County, Tennessee:
1818 Lake Ave

Knoxville, TN 37916
1. Start GeoMedia, and then create a new GeoWorkspace.

2. Create an Access warehouse connection to:
C:\Warehouses\GMAGTrainingCenterlineStreetData.mdb.
3. Add a legend entry for the NCStreets and the TNStreets feature classes.
13-9
This is the data that was used to generate the geocoding dataset used in this workflow.
Zoom in to a neighborhood area of the street data display.
Note: You do not need to connect to this warehouse for the purpose of geocoding;
doing so helps you visualize the data and verify relative position in the current
coordinate system for the GeoWorkspace.
4. Select Analysis > Find Address.
The first time you run this command, the Find Address Options dialog box should be
displayed. If not, click Options on the Find Address dialog box to display it.
5. For the Geocoding directory field, click Browse; then select:
C:\Warehouses\GMAGTrainingCenterlineStreetData.xml.
6. From the Geocoding dataset drop-down list, select TN, which is referenced in the
directory selected in the previous step.
7. From the Input address format drop-down list, select Street Address : City : State :
ZIP.
Note: This is one of the input address formats supported by the dataset being used; you
may choose a different format to use to enter the address information.
8. You can type appropriate values in the Minimum match score and the Offset distance
fields, and then select the offset unit from the drop-down list. For this workflow, you
accept the default values.
9. Optional: Click Style to define the point display settings for the results in the map
window.
10. Click OK to confirm the options selected and to display the Find Address dialog box.
13-10
Geocoding
The column of Address element names match the input address format selected in Step
7.
11. In the Address element/Value grid, type the following values:
Street Address: 1818 Lake Ave
City: Knoxville
State: TN
ZIP: 37916
12. Click Find.
The address is located and displayed in the map window with a point symbol. Also, the
geocoded location of the address is centered in the map window at the current display
scale.
13. Note the matched values in the Match details field.
Note: To show this information, you may need to resize the dialog box or to scroll the
match details vertically.
13-11
14. Note the Match Score of 100 and the Match Status message Matched : OK, indicating
the quality of the match of the input address with the geocoding dataset. If the match is
less than the Minimum Match Score, the status message includes information about
which fields contributed to the mismatch.
15. Change the City name in the Value column to Maryville; then note the result when
you click Find.
No address will be located, and the message Unmatched:City name mismatched is
displayed.
16. Change the name back to Knoxville, pan to a different area, and then click Find again
to check out the centering.
17. To use a different input address format, first click Options; then change the Input
address format on the Find Address Options dialog box to Post address.
18. Next, type 1818 Lake Ave, Knoxville, TN 37916 as the Value for Post address
on the Find Address dialog box.
19. Click Find.
Notice the match information and the geocoded location. It should be the same as
before.
Also, notice how you used the same input address in two different forms. This feature
gives you a great deal of flexibility in how you can enter an address to find.
Geocoding Multiple Addresses

The Geocode Addresses command lets you perform address geocoding of an entire feature
class or query and then output the geocoding results as a new query of the geocoded points.
The input for this command consists of the following items on the Geocode Addresses
dialog box:
• Geocode addresses in—Feature class or query selected from the drop-down list of all
open connections, queries, categories, and reference features as parent nodes, and all
the feature classes/queries as child nodes. This list contains the feature classes/queries
of all types (including and especially nongraphic).
• Geocoding directory file—Selected geocoding directory file (XML) that has
information for one or more geocoding datasets, by default in the geocoding directory
file.
• Geocoding dataset—Dataset name to geocode against, containing all the dataset
names from the specified geocoding directory file.
If there is more than one dataset, the additional item <By address element> is added
to the drop-down list. You then have the option (Address element name) of
specifying an address element whose corresponding attribute is used for determining
13-12
Geocoding
the geocoding dataset (that is, one field of the input feature class/query defines the
geocoding dataset name to be used to switch between geocoding engines or instances
of a geocoding engine).
• Input address format—Address format supported by the selected Geocoding dataset

drop-down list. By default, the first input address format is selected. If <By address
element> is the selected dataset, this list is populated with all the input address formats
listed in the geocoding directory.
• Address attributes—Attributes that form the address elements of the displayed source
address definition. These attributes are presented in a grid that lets you easily specify
the mapping between the address elements of the source address definition and the
address attributes from the input feature class/query.
The read-only Address element column is populated with the address elements from
the specified input address format. The read-write Attribute name column has a drop-
down list that is populated with all the attributes from the input feature class/query that
are of type Text, Memo, Byte, Integer, or Long. If the suggested field names are
present in the input feature class/query, the command populates the second column
with those names. However, you can change the default values.
Note: Suggested field names are defined in the geocoding model (GCM) file before
the dataset is published.
See “Geocoding Models and Parsing Rules” in the “Additional Geocoding

Information” appendix.
All the required address elements are displayed in bold and red font to indicate that the
address fields must be specified for all such address elements. If <By address
element> is chosen as the geocoding dataset, the address element specified in the
Address element name drop-down list also is displayed in bold and red font on the
grid. The controls on the right-hand side are enabled only on a tab out from this
control on the condition that you provide all the required fields.
13-13
• Output Attributes—All the available fields in the input feature class/query, along
with the fields generated by the Geocode Addresses command (like GeometryField,
MatchScoreField, MatchStatusField, StandardizedAddressField, and
MatchedAddressField). Clicking Attributes displays this dialog box so that you can
select, rename, and re-order the output attributes as necessary.
• Advanced Properties—Minimum match score plus the Offset distance and
corresponding unit. Clicking Advanced displays this dialog box so that you can
change these values as necessary.
The minimum match score value (in the range 0-100) determines if an address is
successfully geocoded. Records that have a match score less than this value have a
null geometry value generated and so do not appear in the map window. The default
value is 100. All input record match statistics can be viewed by displaying the
geocode addresses query in a data window.
The default offset value is two meters for centerline geocoding. Offset is not used for
intersection or rooftop geocoding. The units drop-down list contains all available
linear units and is initially set to the default linear unit as specified by the
GeoWorkspace Coordinate System command.
The Geocode Addresses command outputs the results as a new query set of the geocoded
points. You can display these resultant points in a map window and/or the nongraphic
attributes of the geocoded points in a data window. For map window optimum display
results, you can define the output minimum match score, offset distance and unit, and the
style of the point geometry using the GeoMedia Select Style and Style Properties dialog
boxes.
Using the Geocode Addresses Command

The following sample workflow gives you an introduction to bulk geocoding, a process
whereby you can geocode many addresses at the same time. This workflow uses the
familiar GeoMedia query workflow.
1. Start GeoMedia, and create a new GeoWorkspace.
C:\Warehouses\GMAGTrainingCenterlineStreetData.mdb
3. Add a legend entry for the NCStreets and TNStreets feature classes.
This is the data that was used to generate the geocoding dataset used in this workflow.
Note: You do not need to connect to this warehouse for the purpose of geocoding;
doing so here helps you visualize the data.
13-14
Geocoding

C:\Warehouses\GMAGExercisesAddress.mdb
5. Select Analysis > Geocode Addresses.
6. From the Geocode addresses in drop-down list, select the table BulkAddressList,
which contains 61 rows, each having an address to be geocoded.
7. For the Geocoding directory file field, click Browse; then select:
7. From the Geocoding dataset drop-down list, select TN.
8. From the Input address format drop-down list, select Street Address : City : State :
ZIP.
Note: This is one of the input address formats supported by the dataset being used; it
matches the selected table containing the addresses to be geocoded.
9. For Address attributes, ensure that the Address element names match the correct
field (Attribute name) names from the input data.
Note: The correct names are used automatically when the geocode configuration files
contain enough information, such as in this exercise.
10. Optional: Click Attributes to change query properties, that is, some or all of the
attributes of the query results.
13-15
11. Optional: Click Advanced to set the advanced properties: a Minimum match score
and an Offset distance and corresponding unit. For this workflow, accept the default
values.
12. Optional: Change the Query name and/or Description on the Geocode Addresses
dialog box.
13. To see the results in a map window, check the Display geocode points in map window
check box; then select the appropriate Map window name.
14. Optional: Click Style to define the display settings for the results in the map window.
15. To see the results in a data window, check the Display geocoded points in data
window check box; then select the appropriate Data window name.
16. When you have defined the appropriate settings, click OK to see the results.
13-16
Geocoding
The added columns in the data window show the match Score, match Status,
StandardizedAddress, and MatchedAddress.
17. Review the results, paying particular close attention to the data view. Examine the
match score and the match status, and then compare the input attributes to the
StandarizedAddress and MatchedAddress attributes for some of the records.
18. Select the GeoMedia command Analysis > Queries.
19. On the Queries dialog box, select the geocode addresses query; then click Properties.
20. On the Query Properties dialog box, click Advanced.
21. On the Advanced Properties dialog box, change the minimum match score from 100 to
50.
22. Click OK on this dialog box, and on the Query Properties dialog box, and then click
Close on the Queries dialog box.
Note that by reducing the match score, the number of matched addresses has increased.
Note: The results are a query in GeoMedia, and thus this query can be edited in the
usual manner. It can also be placed in part of a series of queries, as well as being
persisted with the GeoWorkspace.
Geocoding Addresses with Multiple Datasets

This sample workflow demonstrates a more advanced use of the Geocode Addresses
command. You may have noticed the option on the Geocode Addresses dialog box to
select the dataset to use based on an attribute of the input. For this example, you use the
following geocoding directory that references multiple geocoding datasets:
<?xml version="1.0" encoding="UTF-8"?>

<GeocodingDirectory xmlns="http://www.intergraph.com/GeoMedia/agc" version="1.0">
13-17
<GeocodingDataset>
<Name>NC</Name>
<Description>North Carolina Centerline TIGER/Line data</Description>
<ForwardEngineProgID>GeoMedia.AGIGeocodingEngine</ForwardEngineProgID>
<ConnectString>c:\warehouses\GMAGTrainingCenterlineStreetData.agi</ConnectString>
<AddressTransformations source="AGIEmbedded"/>
</GeocodingDataset>
<GeocodingDataset>
<Name>TN</Name>
<Description>Tennessee Centerline TIGER/Line data</Description>
<ForwardEngineProgID>GeoMedia.AGIGeocodingEngine</ForwardEngineProgID>
<ConnectString>c:\warehouses\GMAGTrainingCenterlineStreetData.agi</ConnectString>
<AddressTransformations source="AGIEmbedded"/>
</GeocodingDataset>
</GeocodingDirectory>
In this geocoding directory, you can see there are two datasets referenced, and they can be
referred to by the dataset names TN and NC. These names were chosen because they
match the way that datasets might be subdivided – in this case, by the state abbreviations.
1. Open a new GeoWorkspace, and then connect to
GMAGTrainingCenterlineStreetData.mdb and GMAGExerciseAddresses.mdb in
C:\Warehouses.
2. To put the data into perspective, ensure that the feature classes TNStreets and
NCStreets are displayed in the map window.
3. Display the MultiStateAddresses table from GMAGExerciseAddresses.mdb
connection in the data window; then inspect the table and note that there is a State
column.
In the sample addresses, there are records in the State of NC (North Carolina) and
others in the State of TN (Tennessee). Also note the address fields available in the
input addresses: Address, Zip, City, and State.
4. Close the data window, and then make a map window the active view.
5. Select Analysis > Geocode Addresses.
6. From the Geocode addresses in drop-down list, select the MultiStateAddresses table
as the input to the query.
7. For the Geocoding directory file, select
Note: The content of this XML file is the example given at the beginning of this
workflow.
13-18
Geocoding
8. From the Input address format drop-down list, select the format that matches the test
addresses: Address : City : State: ZIP:.
9. From the Geocoding dataset drop-down list, select <By address element>; then
select State from the Address element name drop-down list.
10. In the Address attributes grid, note that the address elements have a field mapped
automatically for the attribute. This was defined through the Geocoding Model file
used to build the Address Geocoding Index file (AGI).
11. Tab out of the grid control to enable the remainder of the Geocode Addresses data.
12. Verify that the check boxes to display the output to the map window and to the data
window are checked and that the map window display style is appropriate.
13. Click OK to see the results.
14. Inspect the results, and note that there extra attributes added by the Geocode
Addresses query.
Note: Before clicking OK, you could have clicked Attributes and then have selected
the contents of the output query, and also have renamed any of the attributes.
Defining Parsing Rules

Many data sources are human-generated as plain text, such as postal addresses and
bibliography records. The data has the implicit schema consisting of a set of attributes, for
example, postal addresses consist of elements like house number, street, and so forth. The
text string itself is generated by concatenating values of different attributes without any
explicit separator between them. The order of attributes is not fixed and not all of them are
present in all instances.
However, convenient usage of data in computing requires it to be organized as structured
records. Therefore, an approach is needed to convert unstructured data into some
appropriate consistent format automatically. This approach should be generic, allowing
development of a flexible software solution applicable to different data schemas/data sets
available.
From a practical point of view, it is desirable to have configurable parser software such that
for a given dataset it might be tuned (probably with some effort) to become able to reveal
the implicit structure of the data. Then the parser can process raw text strings, recognize
structural elements and optionally standardize them with little or no user interaction.
The address geocoding system provided with GeoMedia performs such parsing. The
approach used exploits the theory of Hidden Markov Model (HMM). Hidden Markov
models present a general approach that is widely used for recognition problems, for
13-19
example, speech recognition. The system uses an adaptation of HMM technique for
normalization of human-written addresses.
The system is initialized by an XML initialization file that contains address parsing rules.
The Define Parsing Rules utility, available from Intergraph Support, is an interactive
program for composing, editing, and testing these address parsing rules. There are several
predefined sets of rules delivered with the utility, and you can create additional ones.
See “Geocoding Models and Parsing Rules” in the “Additional Geocoding Information”
appendix for the description of the parsing rules delivered with this software.
Overview
The address parsing rules are described by a parsing rules file, which includes:
• Definition of HMM states, that is tokens.
• Standardization rules for every HMM state/token.
• Pre-parsed samples that define typical order of the tokens.
• Mapping from tokens to output entities and elements. Output elements of the parsing
rules are used to represent address elements in the address definition.
Every token describes some atomic attribute of the input data. In the U.S. Street addresses,
for example, good candidates for the tokens are:
• Street prefix (‘E’ in ‘E Main Street’)
• Street name (‘Second’ in ‘N Second Ave’)
• Street type (‘Road’ in ‘Forrest Road’)
• Street suffix (‘NW’ in ‘MLK Blvd NW’)
During parsing, all characters or words in the input string are assigned to tokens. For this,
the characters or words that can be contained within every token should be defined. In the
present implementation of the parsing rules, the definition can be done in five different
ways, each corresponding to a different token type:
1. ‘Dictionary’ token type—This element type is defined by enumeration of all values it
can contain.
2. ‘Pattern’ token type—The values of this element are defined by a single regular
expression. A good example of the ‘pattern’ token is the base U.S. ZIP, which always
contains exactly five digits and can be described by the “\d{5}” regular expression.
3. ‘External Rules’ token type—The values of this token are defined by some other
parsing rules. It is a convenient way to embed an existing set of parsing rules into the
current parsing rules.
13-20
Geocoding
4. ‘Reference’ token type—This token is exactly the same as some other token. It is
possible, for example, to define the ‘Street suffix’ token from the U.S. Street example
as a reference to the ‘Street prefix’ token.
5. ‘Characters’ token type—This is the most generic notion. It should be used if none of
the previous token types can fully describe the values that can be assigned to the token.
This token definition takes values that are similar to the given samples. This type is
the most suitable for the ‘Street name’ element.
Optionally, the system can perform standardization. The standardization is performed as
defined in the parsing rules. Every token’s value is replaced with its standard form. Then,
these values are taken to form the standardized output entity(entities). The standard form
is defined separately for every token, as follows:
1. ‘Dictionary’ token type—All dictionary items are combined in groups, with every
group consisting of some standard form value and its aliases. During standardization,
all aliases are replaced with the standard form of the group.
2. ‘External Rules’ token type—The standardization is performed by the embedded
parsing rules.
3. ‘Reference’ token type—The standardization is defined in the referenced token
definition.
4. ‘Pattern’ and ‘Characters’ token types—Tokens of this type contain standardization
rules. Every rule contains the following: what to replace (a substring or regular
expression), a replacement (a substring or regular expression), and several flags that
affect the standardization process.
Besides the tokens themselves, their characteristic sequences should be defined. This is
done by providing training samples. Every training sample is a manually parsed string
along with the sequence of tokens that form this string. For the U.S. Streets address
parsing rules with the elements discussed above, such training sequences can be the
following:
Address Sample Token Sequence
1st Ave E Street name Street type Street suffix
E Main Street Street prefix Street name Street type
Broadway Street name - -
Military Way Street name Street type -
Every training sequence has a weight that shows how often such a sequence appears in the
real addresses. The more the weight, the more common this sequence is in real life. As the
HMM technique is a probabilistic one, the quality of parsing can significantly benefit from
the proper weights. The Define Parsing Rules utility itself provides a way to estimate the
weights of the sequences by parsing the large number of addresses and providing statistics
for different sequences.
13-21
The parsing rules can contain many tokens. In the previous U.S. Streets example it is
worthwhile to:
• Introduce tokens to parse local highway addresses (for example, ‘Interstate 60’).
• Introduce a special token to take values of the ‘numeric’ street names, for example,
‘89th street’ or ‘Fifth Blvd’.
Introducing such tokens results in better parsing, as it is possible to:
• More precisely define the values of each token.
• Define better standardization rules. For example, ‘12 street’ should be standardized to
‘12TH ST’, but ’12 oaks blvd’ should be standardized to ‘12 OAKS BLVD’.
The sample parsing rules file for U.S. street names delivered with the utility, for example,
contains 30 tokens. Outputting all tokens values is usually overkill, so the parsing rules
file also defines the output rules.
The system returns the parsed string as output entities; each of them consists of several
output elements. Each output entity has one or more associated tokens, called required
tokens. If at least one of these tokens participates in the result of parsing a string (that is, a
sequence of tokens along with associated values), the entity is output by the system.
Otherwise, the entity is skipped. Every entity consists of several output elements, and the
value of each of these elements is formed from the values of one or more tokens. Each
token can participate in different output entities or its value can be ignored in output. The
token can participate only once in every entity.
Input
A set of tokens, training samples, and the definition of output entities.
Output
A parsing rules file.
General Workflow
To create parsing rules the following steps must be performed:
1. Define tokens. The parsing rules must have at least one token.
2. Add necessary training samples. At least one training sample is required.
3. Define output entities that the parsing system should produce for the user.
4. Optional: Perform testing of the parsing rules using appropriate data sources, and then
analyze the results.
13-22
Geocoding
Geocoding Coordinates
Geocode Coordinates creates point geometries for a feature class or query based on
projected or geographic coordinate values stored in the attributes of the input tables of that
input feature class or query. For example, you can use a data table containing latitude and
longitude values to place points. This command outputs the results as a new query that is
dynamic. Thus, you can display the resultant geocoded points in a map window and/or the
attributes of the geocoded points in a data window, and if the source warehouse changes,
the resultant points also change. For example, if new storm tracks or tract data is added to
a text file with storm data, then the points update to reflect the current storms and storm
positions. In addition, you can set the style for the map window for optimum display
results.
Geocode Coordinates supports:

• 2-D and 3-D coordinate attributes.
• Geographic or projected coordinates in any GeoMedia coordinate system.
• Field types: text, integer, long, single, and double.
• Coordinate units (for example: degrees, radians) and formats (for example: decimal
degrees, d:m:s) of all types supported by GeoMedia coordinate systems.
• Definition of the coordinate system through the Coordinate System Properties dialog
box.
13-23
• Output of a status indicator for troubleshooting bad coordinate data.
Note: If the resultant coordinate values are suspect or problematic, you can review the
resulting Geocode query in a data window to inspect a newly created column called
GeoCode_Status. If for some reason a point could not be placed, this field records the
problem. You can then sort on the column or run attribute queries to locate the
problem coordinate records.
To geocode coordinates:
1. Select Analysis > Geocode Coordinates.
See the GeoMedia Help for complete information on the parameters of this dialog box.
2. In the Geocode attributes in field, select the feature class or query containing
attributes to be geocoded.
3. Optional: Click Coordinate System to review and/or to change the default
coordinate-system definition, to browse for and save coordinate system files, and to set
and modify the units and formats on the Coordinate System Properties dialog box.
4. In the Coordinate attributes area, select the attribute to be used for the first coordinate
Note: The names of the first and second coordinate fields vary dynamically with the
selected coordinate system, units, and format.
5. Select the attribute to be used for the second coordinate from the drop-down list.
13-24
Geocoding
6. Optional: Select the attribute to be used for the height value from the drop-down list.
9. Verify that the Display points in map window check box is selected, and change in the
Map window name field, if appropriate, the default active map window in which to
display the geocoded points.
OR
To not display the geocoded points in a map window, select the Display points in map
11. Verify that the Display points in data window box is checked, and change in the Data
window name field, if appropriate, the default new data window in which to display the
nongraphic attributes of the geocoded points.
OR
To not display the nongraphic attributes of the geocoded points in a data window, click
the Display points in data window box to remove the checkmark.
12. Click OK to generate and to display the points in the specified map window and/or data
window.
13-25
13-26
Working with Layout Windows
Layout Window Overview

The layout window always exists, with a minimum of one layout sheet. Unlike the map
window and data window, the layout window only supports a single instance; it is either
open or closed. However, multiple layout sheets can exist in the layout window, exposed
as pages or sheets in the same manner as in the Excel or SmartSketch products. A default
sheet setup and a few GeoMedia layout templates provide examples and a starting point for
the layout and plotting environment.
Accessing the Layout Window

You access the layout and plotting environment from a map window or a data window by
selecting Window > Layout Window from the GeoMedia pull-down menu bar or the
Standard toolbar. Similarly, you can dismiss the layout window by selecting Window >
Hide Layout Window. The command button on the Standard toolbar toggles back and
forth depending on the active window. When the active window is a map or a data
window, the command is Show Layout Window. When the active window is the layout
window, the command is Hide Layout Window. When the layout window is hidden, the
last used window is made active. When the layout window is active, you can append new
layout sheets to it in two ways. First, you can create a new layout sheet by selecting
Sheets > Insert Sheet from the layout window pull-down menu or by selecting Insert
from the right mouse menu of the sheet tab. New sheets are added after the active sheet.
Second, you can import external files as new layout sheets by selecting Sheets > Import
Layout from the layout window pull-down menu or by selecting Import Layout from the
layout toolbar. File types supported by Import Layout include GeoMedia layout sheets or
templates, Imagineer or SmartSketch drawing files or templates, and MicroStation layout
templates.
Setting Layout Window Options

The Layout tab on the Options dialog box (Tools > Options) lets you set various controls
for the appearance of the layout window and the behavior of some of the graphics
commands.
14-1
Layout Tab
The Layout tab lets you set controls for the layout window graphics commands relating to
the layout grid and length readout. This tab is displayed on top when the Options dialog
box is opened in the layout window.
The Units selection area lets you set up the units for defining Distance and Style values in
the layout sheet. The Style setting is used for defining line widths for the drawing
commands (Line, Circle, and so forth), and for north arrow and scale bar style properties.
The Distance setting supports up to seven-decimal precision and is used for precision key-
in control in the drawing commands (Line, Circle, and so forth), the Measure Distance
command, the Legend Properties command, and the grid subinterval spacing. The
precision readout sets the number of significant figures to display the accuracy of the unit
readout value. The precision setting does not alter the numbers that you type into the
fields, only the display of the numbers in the field. Values ending in five are rounded up.
For example, if the precision readout is 0.123 and you draw a line that is 2.1056 inches
long, the line value length is rounded. The length value appears as 2.106 inches long. If
you are using millimeters as your drawing sheet units, you can have the values display in
the fields as 3.5 mm or 3.50 mm.
Note: When you set options on the Layout tab for the units in a document, the settings do
not affect the dimensional values or sheet size for the document.
The Grid and Nudge selection area lets you set options for using the Grid Display and
Grid Snap capabilities as follows:
• Grid display—Displays a grid for precision element placement. The grid lines
themselves are not considered part of the document and do not print.
14-2
• Grid snap—Aligns elements with the grid, which is an invisible set of lines in the
document that helps you align elements. When you select this option, elements always
align with the grid lines or the nearest intersection of the grid lines.
• Subinterval spacing—Sets the spacing of the grid lines.
• Subintervals per interval—Determines the number of index grid lines. The read-only
unit is set by the layout window Page Setup command. The size of each grid cell is
determined by the Subinterval spacing. The Subintervals per interval determines
the number of minor grid lines to display between the major grid lines. If the grid
spacing is set to 0.25 inches and the grid index is set to four inches, then the minor grid
lines display as dashed gray lines at 0.25 inch intervals, and the major grid lines
display as solid gray lines at 1.0 inch intervals, per the following formula:
major grid line interval = grid spacing X grid index
Page Setup
The page setup parameters for layout sheets created using the Insert Sheet command are
based on the current settings of the active sheet when the command is started. The page
setup parameters of the active sheet are copied to the new sheet. If the page setup
parameters have been defined as the default, the page setup parameters are based on the
saved default settings. The page setup parameters for imported files or templates are based
on the parameters defined for the imported sheet.
When you open the layout window for the first time in a new GeoWorkspace, the page
setup parameters are obtained from the delivered GeoMedia template file normal.glt. You
can bring this file into the layout window with Import Layout and then modify it to reflect
your default layout parameters.
See “Defining the Layout Window Page Setup” in the “Printing in GeoMedia” chapter for
more information.
Plotting
Upon completion of your map design, you can submit the plot to a plotter or an offline file,
such as PDF, through the standard Windows printing interface. The layout window and all
of its associated layout sheets are automatically saved in the GeoWorkspace when you save
the GeoWorkspace. If you do not want to save the plot session, you can manually delete
the plot upon completion.
See “Printing Layout Sheets from the Layout Window” in the “Printing in GeoMedia”
chapter for more information.
14-3
Starting the Layout Window

Select Window > Show Layout Window from the GeoMedia pull-down menu to display
the layout window. When you display the layout window, it becomes active, and the
menus and toolbars change to enable the layout commands. If you select Hide Layout
Window when the layout window is already displayed, the layout window becomes
hidden, and the menus and toolbars revert to their former states.
Inserting Layout Sheets

Insert Sheet inserts (adds) a new layout sheet using the page setup parameters of the active
sheet. You can change the parameters with the Layout Window Page Setup command.
When a new sheet is inserted, it is placed after the sheet that was active when the command
was started.
To insert layout sheets:

1. Make the appropriate layout sheet active.
2. Select Sheets > Insert Sheet.
OR
14-4
Place the cursor over the layout sheet tab, right click, and then select Insert from the
right mouse menu.
Note: The page setup for the first sheet in the layout window is based on parameters
defined for the layout sheet in normal.glt. However, this is not automatically so for
subsequent sheets. The page setup parameters for each new sheet are based on the active
sheet when this command is started. Thus, if the first sheet is a C Size Sheet and is the
active sheet when the command is started, then the new sheet inserted will also be a C Size
Sheet. But if you then create a D Size Sheet, and it is active when you start the command,
then the new sheet inserter will be a D Size Sheet, not the initial default C Size Sheet.
Importing Layout Sheets and Layout Templates

Import Layout lets you add external files to the layout window in the GeoWorkspace as
new layout sheets, supporting the following file types:
• GeoMedia Layout Sheets (.gls)
• GeoMedia Layout Templates (.glt), the default for first-time use
• Imagineer or SmartSketch Drawing Files (.igr)
• Imagineer or SmartSketch Templates (.igt)
• MicroStation Layout Templates (.dgn)
GeoMedia Layout Sheets

GeoMedia layout sheets are fully composed plot layout sheets stored as an external disk
file outside the originating GeoWorkspace. They contain the layout graphics and map
graphics. The status of the map graphics in the sheet, static mode or dynamic mode, is
maintained during the export and import process. GeoMedia layout sheets are limited to a
single layout, supporting background and working sheets. The layout sheets should be
imported into the originating GeoWorkspace, where they can then be updated, and plotted,
which provides a useful mechanism for maintaining dynamic plot files outside the
GeoWorkspace.
A distinction is made between layout graphics and map graphics. Map graphics are those
graphics that originated in the map window, and they include a map, legend, scale bar, and
north arrow. Layout graphics are those graphics that originated in the layout window
(Version 4.0 and above) or in SmartSketch, and they include SmartFrames, borders, titles,
logos, and so forth.
To support importing .gls files, both interactively and in batch plotting, the Export Layout
command assigns custom attributes to the GeoMedia layout sheet file that defines
particular characteristics of the sheet being exported. When importing .gls files, all effort
14-5
is made to reproduce the originating map window of each map SmartFrame found in the
.gls file. If the originating map window is not found, the software looks for a named
legend whose name is the same as the originating map window, and uses that named
legend to create an originating map window.
See the next section, “Exporting Layout Sheets and Templates”, for information on this
command.
Note: Problems may arise when trying to import pre-GeoMedia 5.2 .gls files, or if named
legends no longer exist. In such cases, error messages are displayed to provide the needed
information.
Layout templates and drawing files are also external files that you can import into the
layout window. The location of the templates is defined as \Templates on the File
Locations tab of the Options dialog box (Tools > Options). The default location is
<drive:>\Program Files\GeoMedia\Templates\Layouts.
GeoMedia Layout Templates

If you require a predefined layout template, you have two options. You can import an
Imagineer or SmartSketch template file (.igt) created from legacy workflows in GeoMedia
2.0 or 3.0, or you can import a GeoMedia layout template file (.glt) created in GeoMedia
4.0 or above.
When you import a GeoMedia layout template file (.glt), you copy the layout graphics
from an external file stored on disk to a new layout sheet stored in the layout window.
This template is limited to a single layout sheet, supporting background and working
sheets.
A GeoMedia layout template is intended to store standard title block type graphics used
across an enterprise. It only contains layout graphics, including frames, generated with the
Insert Layout Frames command. A layout frames function as containers that identify the
type of content and the physical extent of the map graphics being placed into the layout
sheet. Layout frames are intelligent, that is, they know what type of map graphic they
contain. A GeoMedia layout template does not contain GeoWorkspace connections.
Imagineer or SmartSketch Template and Drawing Files

Similarly to importing a GeoMedia layout sheet or a GeoMedia layout template, you can
copy the graphics from an external Imagineer or SmartSketch template file (.igt) or
drawing file (.igr) and place them as a new layout sheet in the layout window. This option
supports legacy workflows in case you have invested a lot of time building Imagineer or
SmartSketch plot layout drawings and templates. Unlike the import of a GeoMedia layout
sheet or a GeoMedia layout template, the import of a .igt template file or a .igr drawing file
brings all the sheets contained in the drawing or template, including multiple working
sheets and background sheets.
14-6
Note: Some SmartSketch components are not supported within the GeoMedia
environment. The .igt and .igr files containing components such as Connectors and
Smartlabel controls should not be used when importing into GeoMedia.
GeoMedia layout templates created with GeoMedia 4.0 (or above) using the Export
Layout command contain only layout graphics. Imagineer or SmartSketch files or
templates created using GeoMedia 2.0 or GeoMedia 3.0 plotting workflows may contain a
combination of map graphics and layout graphics. When importing these Imagineer or
SmartSketch file types, only the layout graphics are imported. Map graphics are ignored,
but the layout frames used to contain the map graphics are imported to provide a point of
reference in the layout design. Because the GeoMedia 2.0 and 3.0 style of layout frames is
not associated as a group, they will need to be redrawn using the Insert Layout Frames
command.
MicroStation Layout Templates

MicroStation layout templates (.dgn) are limited to a single design plane, so when this file
type is imported, a single sheet is created. The graphics located in the specified .dgn file
are imported as layout graphics into the current GeoWorkspace as a new sheet, and that
sheet is made active. The sheet background color is always white. Only MicroStation
Version 7 or older design files are supported; if you attempt to import a Version 8
design file, you receive an error message.
You do not have to reset the global origin of the design file in MicroStation; instead, the
command scans the graphics in the design file, determines the MinX and MinY, and uses
these values as the offsets to the origin of the paper space. Thus, the point you want as the
lower-left corner in the paper layout is located at the MinX, MinY coordinate in the design
plane. This command also scales the graphics in the design plane to the layout sheet paper
space. The scaling is based on the size of the currently active layout sheet; therefore, you
need to set the active layout sheet size properly according to the map scale of the
MicroStation layout template to be imported before running the command to get the
expected layout result. MicroStation elements being imported from different levels are
generated on layers with the layer name matching the level. The index 0 color in the color
table is always set to black (RGB(0,0,0)). All other colors are imported using their
absolute RGB definition. Furthermore, cells always come across as groups.
Hint: To ensure proper scaling of the design file elements into the layout sheet, it is
advisable to place a rectangle in the design file that produces a particular sheet size when
plotted at a given scale. For example, a Bsize sheet (11 inches x 17 inches) portraying
1:50,000 scale graphics can accommodate an area on the ground of 550,000 inches x
850,000 inches. Therefore, a rectangle of this size should be placed in the design file
before the import, where the desired graphics are contained within the rectangle. If there
are any graphics in the design file that extend beyond the rectangle, they should be deleted.
14-7
To import a layout sheet or template:

1. Select Window > Show Layout Window.
2. Select Sheets > Import Layout.
3. Select GeoMedia Layout Sheets (*.gls) from the Files of type drop-down list; then
select the appropriate .gls layout sheet file.
OR
Select GeoMedia Layout Templates (*.glt) from the Files of type drop-down list;
then select the appropriate .glt template file.
OR
Select SmartSketch Template Files (*.igt) from the Files of type drop-down list; then
select the appropriate .igt template file.
OR
Select SmartSketch Files (*.igr) from the Files of type drop-down list; then select the
appropriate .igr drawing file.
OR
Select MicroStation Layout Templates (*.dgn) from the Files of type drop-down
list; then select the appropriate .dgn template file.
Note: Before selecting a MicroStation layout template (.dgn) for import, you must
first determine the necessary sheet size for the file and set it on the active layout sheet
(either existing or newly inserted) accordingly.
4. Click Open.
14-8
The sheet(s) located in the selected file is appended (copied) into the current
GeoWorkspace as a new layout sheet and is made active. When multiple sheets are
imported, the last sheet added is made active.
Note: If the sheet you are importing has the same name as an existing sheet, you have
the option to overwrite the existing sheet or to import the sheet with a different name.
Exporting Layout Sheets and Templates

Export Layout lets you export the active layout sheet in the layout window to any of the
following external file types:
• GeoMedia Layout Sheet (.gls)
• GeoMedia Layout Template (.glt), the default for-first time use
• Bitmap (.bmp)
• JPEG File Interchange Format (.jpg)
• TIFF Tagged Image File Format (.tif)
You can insert GeoMedia layout sheets and templates back into the layout window using
the Import Layout command. Thus, you can create a layout sheet to reproduce the design
of an existing plot.
With GeoMedia layout sheets, Export Layout exports the populated map graphic layout
frames, with the map graphics maintaining their current mode, either static or dynamic.
Map graphics maintain the information about themselves, so they can be re-imported back
into the originating GeoWorkspace using Import Layout and can be updated using
14-9
Update Map Graphics. This workflow provides a useful mechanism for maintaining
dynamic plot files outside of the GeoWorkspace.
To support importing .gls files, both interactively and in batch plotting, the Export Layout
command assigns custom attributes to the GeoMedia layout sheet file that define particular
characteristics of the sheet being exported. You can access these attributes by selecting a
GeoMedia layout sheet in Windows Explorer, clicking the right mouse button, and then
selecting the properties of the file. On the Custom tab, the attributes are listed as follows:
• Name of the originating GeoWorkspace (drive:\folder\name)—When shared
network drives are referenced, the attribute value reflects the Universal Naming
Convention (UNC). This is required primarily for batch plotting workflows, but it is
also necessary for interactive workflows to verify that the selected .gls file is being
imported into the GeoWorkspace from which it was originally exported.
o Attribute:
o Name: GeoWorkspace
o Type: Text
o Value: C:\GeoWorkspaces\USSampleData.gws (for example)
• SheetName of the exported file
o Attribute:
o Name: SheetName
o Type: Text
o Value: Illinois (for example)
When importing .gls files, all effort is made to reproduce the originating map window of
each map layout frame found in the .gls file. The Batch Plotting utility (GeoMedia
Professional) workflows require a named legend for the composition, so a named legend
should exist in the GeoWorkspace for any exported .gls files, enabling the import to
reproduce the originating map window with the appropriate content.
Interactive .gls file export workflows may not contain map frames that were populated
using a named legend (whose name matches the map window name), making it difficult to
reproduce the originating map window of the map SmartFrame during the import. For
each map SmartFrame in the imported .gls file, the command checks to see if there is a
map window in the GeoWorkspace that matches the name of the map window defined in
the map layout frame moniker. If the map window exists, no further map window actions
are required. If the map window does not exist, import attempts to create a new map
window based on the map frame moniker, as previously noted.
With GeoMedia layout templates, Export Layout only exports layout graphics (titles,
borders, logos, and so forth) and layout frames placed with Insert Layout Frames; it does
not export map graphics (map, legend, north arrow, and scale bar) contained in the layout
frames. This command only exports one sheet at a time, and it includes a background sheet
if one is referenced by the layout being exported.
14-10
Export Layout also exports the layout sheet to several raster file formats (.bmp, .jpg, and
.tif). These files are typically fully composed layouts that can be stored as external disk
files, providing a useful mechanism for maintaining static plot files outside of the
GeoWorkspace. These are standard industry file formats that can be opened and
manipulated in third-party applications, such as word processing or desktop publishing.
File resolutions supported include 72, 100, 200, 300, and 600 dpi.
Note: Before exporting a sheet, you can use Update Map Graphics to update the
graphics with any changes in the map window, including the addition or removal of legend
entries as well as any style modifications.
To export a layout sheet or template:

1. Verify that you have the appropriate information in the active layout sheet or template.
2. Select Sheets > Export Layout.
3. For .gls and .glt files, select the appropriate folder and file type, and type the name of
the file to export in the File name field; then click Save to write the active layout sheet
to the specified name and to exit the command.
OR
For .bmp, tiff, and .jpg, . files, select the appropriate folder and file type, and type the
name of the file to export in the File name field; then click Save.
4. For .bmp and tiff files, select the appropriate File resolution on the <file type> Export
Options dialog box; then click OK to write the active layout sheet to the specified
name and to exit the command.
14-11
For .jpg files, select the appropriate File resolution and JPEG Quality Factor on the
JPEG Export Options dialog box; then click OK to write the active layout sheet to
the specified name and to exit the command.
Selecting and Manipulating Layout Sheets

To display or to manipulate a layout sheet, you select a layout sheet tab from those
displayed at the bottom of the layout window. There is a tab available for each layout
sheet.
To select a layout sheet:

To select a layout sheet, select its tab from the bottom of the layout window. You can
select both working sheets and background sheets.
The layout sheet is displayed as the active sheet with its name on the tab.
Renaming Layout Sheets

Rename Sheet renames the active layout sheet. You can rename both working sheets and
background sheets.
To rename a layout sheet:

1. Make the appropriate layout sheet active.
2. Select Sheets > Rename Sheet.
OR
Place the cursor over the layout sheet tab, right click, and select Rename from the right
mouse menu.
14-12
3. Type the new name; then click OK.
Deleting Layout Sheets

Delete Sheet deletes the active layout sheet. You can delete both working sheets and
background sheets. You cannot, however, delete all sheets because a minimum of one
layout sheet must be visible at all times. If there is only one sheet and you want to delete
that one, you must first insert another sheet.
To delete layout sheets:

1. Make the appropriate layout sheet(s) active.
2. Select Sheets > Delete Sheet.
OR
Place the cursor over the layout sheet tab, right click, and select Delete from the right
mouse menu.
Viewing Background and Working Sheets

The working sheet and a background sheet are components of each layout sheet.
Background sheets are optional and can be attached to multiple working sheets through the
Page Setup. Typically, the working (foreground) sheet is where you place the map
graphics and the additional layout graphics that are unique to each map layout. The
background sheet is typically used for graphics that you want to display on more than one
layout, such as a border, title block, company logo, or raster background picture
(watermark). The background sheet is displayed behind the layout sheet, and its features
cannot be selected unless the background sheet is the active sheet. A background sheet can
be displayed and printed along with any layout sheet to which it is attached.
Selecting View > Background Sheets switches the view from the active working sheet to
the background sheet. When you select this command, all of the background sheets in the
document are displayed as tabs at the bottom of the window, and all the working sheet tabs
are hidden. You can display background sheet graphics on any or all working sheets with
the Layout Window Page Setup command.
Selecting View > Working Sheets displays all working (foreground) sheets in a document.
If a background sheet is attached to the working sheet, the graphics on the background
sheet are displayed on the working sheet. When you attach a background sheet to a
14-13
working sheet, the software automatically adjusts the size and the margin of the working
sheet to match the size and the margin of the background sheet.
Viewing Layout Window Properties

Layout Windows Properties lets you manage the display of multiple layout sheets by
changing the display status of a sheet in the layout window to either hide the layout sheet
or to make it visible. Because all layout sheets can potentially be saved in the
GeoWorkspace, a large number of sheets might become a management problem. To
minimize the problem of having to sort through all the saved layout sheets stored in the
layout window when it is opened, the Visible property lets you reduce the number of
exposed layout sheets. Only those sheets flagged as visible (Yes) appear in the layout
window when it is opened. You can turn saved layout sheets on and off one at a time.
Sheets must have their visible status set to Yes for you to be able to modify and/or to plot
them.
This command provides a list of all of the layout sheets currently stored in the layout
window, sequentially listing the visible sheets followed by the invisible sheets. The
information available for each layout sheet includes the name, logical number, description,
and visible status, most of which are defined on the General tab of the Layout Window
Page Setup dialog box. The logical number is automatically assigned as new layout sheets
are added to the layout window. You can use the logical number to define print ranges in
the Print Layout Window dialog box. You can only change the visible status with
Layout Windows Properties. However, double clicking on a listed layout-sheet row
opens the Layout Window Page Setup dialog box, which lets you change the sheet name
and/or description for the layout sheet identified in the active row.
To view layout window properties:

1. With an active layout window displayed, select Window > Layout Window
Properties.
2. Review the information for the listed layout sheets.

3. Change the Visible settings as appropriate by toggling the value to Yes (visible) or No
(hidden).
14-14
Note: A minimum of one layout sheet must be visible at all times.
4. Optional: Double click on a row to open the Layout Window Page Setup dialog box,
and then change the page setup on the Layout Window Page Setup dialog box.
Manipulating Layers
The Layers command (Layout > Layer) displays the Layer toolbar, which lets you view
and set the active layer, display or hide layers on the active layout sheet, and change the
layer of an element.
The Layer field displays the active layer on the layout sheet. You can change the active
layer by selecting an existing layer from a list of all the layers on the active sheet or by
typing a new layer name to create a new layer. You can create as many layers on a layout
sheet as you need, but you cannot give the same name to two layers on the same layout
sheet. The layer definitions and display status can be defined independently for the
working sheet and its attached background sheet.
Change Layer lets you change the layer for all of the elements you select. Although you
can assign an element to only one layer, you can change the layer to which an element is
assigned. The dialog box of this command displays the current (source) layer for all the
selected elements, and you can then select the (target) layer to which you want to change
them from a list of all the layers for the active sheet.
Layer Status lets you set the display criteria for the layers in the current layout sheet,
displaying or hiding layers in a list of all available layers on the active layout sheet
through the Layer Display dialog box. This dialog box also lets you set the display of
layer groups.
To create a layer:
1. Select Layout > Layer.
2. Type the name of the new layer in the Layer field; then press TAB.
Note: You can also create a layer using the Layer Groups command.
To change the layer of an element:

1. Select the appropriate element(s).
14-15

3. Click Change Layer on the Layer toolbar.
4. Select the target layer from the Change all to list; then click OK.
To display or hide layers:

2. Click Layer Status on the Layer toolbar.
Note: The layer name displayed in black text shows that the layer is displayed on the
layout sheet. The layer names displayed in gray are hidden or turned off, and the layer
name displayed in red preceded by an asterisk is the active layer.
3. Optional: Check the Active layer only check box to hide all layers except the active
layer.
4. Optional: Check the Occupied only check box to display only names of layers
containing elements in the Layers list. Empty layers do not appear on the list.
5. Select a layer name in the Layers list to display or hide the layer on the layout sheet.
14-16
Note: Double clicking on a layer name makes it the active layer (red). A single click
on a layer toggles the display status from on (black) to off (gray), or vice versa.
6. Click Apply to make the selected layer the active layer.

The active layer is changed, the new active layer is displayed, and all the other layers
(including the previous active layer) are hidden.
Manipulating Layer Groups

While layers provide a way to control the display of elements on a layout sheet, layer
groups let you combine layers into common themes, giving you another way to control the
display of elements on layout sheets by turning on and off the appropriate themes. This is
especially useful when there are a large number of layers defined in a layout sheet. The
Layer Groups command lets you create, modify, and delete layers and layer groups.
The Layer Groups dialog box consists of two areas, Layers and Groups. The Layers
area displays a table of all the layers on the current layout sheet. In the Layers table you
can create a new layer or delete an existing layer. To create a new layer, type the name of
a layer in the Layers field and press ENTER or TAB. To delete a layer, select that row,
and press DELETE. You can only work with layers on the current layout sheet. You
cannot delete the active layer or a layer that has elements placed on it.
The Grouped column of the Layers table indicates the status of the layers, once a group
has been selected in the Groups table. If the check box is checked, it indicates that the
layer is a member of the group that you selected in the Groups table. If the check box is
cleared, the layer is not a member of the selected group. It is important to note that a row
in the Groups table must be selected to let you change the value of the Grouped column
in the Layers table. If no group is selected in the Groups table, the Grouped check boxes
for the layers listed in the Layers table all appear unchecked.
The Groups area displays all layer groups for the current layout sheet. You can create a
new group by typing a name in the Groups field and then by adding layers to the group
from the Layers table. You can select a group from the Groups table to display the layers
in the group in the Layers table. To select a group, you must click the button on the left
side of the row for a group. You can use the Description column to add a description to
the layer group. Typing a name of an existing layer group makes that group active. You
can then add or remove layers in a group as described above.
14-17
Note: You can also create a layer using the Layer Groups command. On the Layer
Groups dialog box, type the name of a new layer in the Layers field and press ENTER.
The name of the new layer is displayed at the bottom of the Layers table.
To create a layer group:

1. Select Layout > Layer Groups.
2. In the Groups field on the Layer Groups dialog box, type the name of the new group,
and then press ENTER.
3. In the Layers table, in the Grouped column, click each check box to include the layers
in the group.
Note: In the Grouped column, if the check box beside the layer name already has a
check, the layer is a member of the current layer group. You cannot give the same
name to two layers on the same layout sheet.
4. Optional: Type a description in the Description field.
14-18
To change layers in a layer group:

2. In the Groups area of the Layer Groups dialog box, select the group you want to
change by clicking the button on the left side of the row. In the Layers table, if the
check box by the layer name is set, the layer is in the layer group.
3. In the Layers table, set or clear the check box of each layer to add or remove it from
the layer group.
Note: When moving an area element and its corresponding fill to a different layer, the
Top Down and Bottom Up buttons on the ribbon bar function as follows: If the Top
Down button is depressed, only the rectangle is selected, and thus has its layer changed.
However, if the Bottom Up button is depressed, both the rectangle and its fill are selected,
and thus both have their layers changed.
To delete a layer group:

2. In the Groups table of the Layer Groups dialog box, select the layer group you want
to delete; then press DELETE.
To delete a layer:
2. In the Layers table of the Layer Groups dialog box, select the layer you want to
delete; then press DELETE.
To display or hide the Layer Groups list and layers on the layout sheet:
2. Click Layer Status on the Layer toolbar.
3. Click Groups.
14-19
4. Select a group from the Layer Groups list.

5. Click On to display the layers in the selected layer group.
6. Click Off to hide the layers in the selected group.
7. Click Apply to apply the current display settings to the active sheet in the layout
window and to leave the dialog box displayed.
OR
Click Close to apply the current display settings to the active sheet in the layout
window and to dismiss the dialog box.
14-20
Designing Map Layouts for Printing
in the Layout Window
Designing Map Layouts Overview
After defining the page setup, you can begin placing graphics in the layout sheet. You can
place two kinds of graphics, layout graphics and map graphics. Layout graphics are
graphics such as borders, titles, company logos, and so forth. Map graphics consist of an
extracted subset of the map window (a map) and supporting marginalia (legend, north
arrow, and scale bar).
See “Page Setup” in the “Working with Layout Windows” chapter.
The order of placement is up to you; there are no requirements to place map graphics
before layout graphics, or vice versa. All marginalia placed in the layout are associated
with the originating map. This means that the legend automatically reflects the graphic
symbology used to define the map in the layout sheet. The north arrow automatically
reflects the projection parameters and view rotation of the map in the layout sheet, and the
scale bar automatically reflects the plot scale in the layout sheet. Placing marginalia is
possible only if a map exists in the layout sheet. In addition, you can place multiple maps
in a layout sheet when appropriate. To place layout graphics, you use the drawing
commands available in the layout window.
In terms of map graphics placement, there are two basic workflows: placing map graphics
using layout frames, and placing map graphics without using layout frames. Each
workflow is accomplished using different commands. Once the map graphics have been
placed, there are several tools and commands available for modifying the size and position
of the map graphics items and for placing a cartographic grid or reference grid on the map.
Map Window Considerations When Printing from

the Layout Window
The plotting workflow assumes that you perform all map design work with regard to
symbology settings in the map window before transferring the data to the layout window.
With this workflow in mind, the software provides some additional tools to help you
visualize what the map data looks like (in the map window) when plotted at a given map
scale.
15-1
Defining Map Specifications in the Map Window

The Display Properties command lets you define the following properties that affect the
way in which the map graphics are displayed: display scale, nominal map scale, rotation
angle, angular units, and legend entry display. You access this command in an active map
window by selecting View > Display Properties.
See “Defining Map Window Display Properties” in the “Working with Map Windows”
chapter for more information on this command.
Requirements for data display and presentation for analysis are generally quite different
from those for output. In analysis, the display scale is constantly changing as you zoom in
and out. Feature symbology settings are generally defined so they produce legible results
at multiple display scales. In some cases, the data may be viewed in its raw geometric
form as non-symbolized point, line, and area data. In output, the data presentation is
typically defined to support a particular plot scale. The symbology settings are defined so
they produce the optimal results when they are applied at a fixed scale. The data are
usually fully symbolized for cartographic display.
Support for these two scenarios can be seen in several areas of the interface, beginning
with the Display Properties dialog box, which provides the ability to specify how the
feature is displayed. The View (size is true at any display scale) setting specifies that the
symbology remains fixed, regardless of the display scale – a suitable option for analysis.
When this setting is turned off, it specifies that the symbology is rendered at a specific
scale. As you zoom in and out, the symbology of the feature increases or decreases relative
to the change in the display scale – a suitable option for output.
See “Working with Styles” in the “Working with Map Windows” chapter and the “Style
Definition Dialog Box” topic in GeoMedia Help for more information.
The feature symbology settings on the Display Properties dialog box may contain a
mixture of display settings. The View (size is true at any display scale) setting may be
turned on for some features, and turned off for others. This scenario may provide a
suitable working environment for analysis as display scales constantly change when you
zoom in and out. However, this approach may produce undesirable results because the
symbology may not be appropriate for the output plot scale, as seen in the following
figures. It may be beneficial to create a map window that is devoted entirely to plotting,
15-2
Designing Map Layouts for Printing in the Layout Window
where unique legend settings can be applied independently of the settings used for
analysis.
Paper (size is true at nominal map scale)
View (size is true at any display scale)
When defining the symbology settings for output, the size of point, text, and patterned area
fill features and the weight for the line and area boundary features should all be defined
with the output plot scale in mind. Scale ranges are enforced as the data are transferred
from the map window to the layout window, so it may be advisable to disable any scale
range settings and only display the features that you want on the plotted map. This
minimizes any surprises in the final output. Once this is done, achieving a WYSIWYG
(What You See Is What You Get ) display can easily be accomplished using the Display
Properties command.
For WYSIWYG displays, you set the Display scale and Nominal map scale to the
intended plot scale. When these two settings are the same, there is consistency between the
symbology rendering, regardless of what the individual settings are on the Display
Properties dialog box for the View (size is true at any display scale) option.
Note: In general, the nominal map scale should not exceed the plot scale because, if it
does, it affects the accuracy and reliability of the data plotted.
Once this is done, you would select the Paper (size is true at nominal map scale) option
on the Display Properties dialog box. This ensures that all feature symbology definitions
are rendered at the specified nominal map scale (which should, in this example, be the
same as your plot scale). You then click Apply and close the Display Properties dialog
box. If you are not satisfied with the display characteristics of a particular feature class,
you can go back to the Select Style dialog box to modify the symbology settings.
Once you are satisfied with the results, you can use the Pan command to move about the
map window to preview what the map will look like. When you are satisfied, you can then
zoom out to the scale necessary for you to define the Geographic Extent used by the
Insert Map and Insert Graphics into Layout Frames commands.
15-3
Note: The rendering of map graphics takes into account the View (size is true at any
display scale) setting on the Display Properties dialog box for each legend entry. When
the View (size is true at any display scale) setting is unchecked, the graphics are rendered
at the nominal map scale, increasing or decreasing in size as the display scale or plot scale
fluctuates away from the nominal map scale. As the data are transferred from the map
window to the layout window, the size of the text, the symbols, and the line widths are set
at the nominal map scale and are then scaled accordingly based on the variation between
the nominal map scale and the plot scale. When the View (size is true at any display
scale) setting is checked, the graphics are rendered at the display scale, remaining
consistent as the display scale changes. As the data are transferred from the map window
to the layout window, the size of the text, the symbols, and the line widths are set at the
plot scale. In this manner, regardless of the discrepancy between the display scale and the
plot scale, the size will remain constant.
Applying a dashed line style or pattern line style to a linear feature can often produce
undesirable results if the linear network is segmented. Similarly, applying a dashed line
style or patterned line style to area boundaries can often produce undesirable results when
the area boundaries are coincident. Fortunately, there are tools available in the map
window to help you manipulate the geometry so it is suitable for applying dashed or
patterned styles.
See “Merging Feature Classes and Queries” and “Generating Base Geometry” in the
“Analyzing GeoMedia Data” chapter for more information.
Previewing the Map in the Map Window

Once you have defined the display properties (as defined in the Display Properties dialog
box), you can easily obtain a WYSIWYG preview of your map data in the map window by
using the View > Zoom > to Nominal Map Scale command. This command adjusts the
map view by zooming in or out to the defined nominal map scale, maintaining the view
center of the window. The legend, north arrow, and scale bar are also adjusted if they are
displayed. The nominal map scale is set on the Display Properties dialog box (View >
Display Properties).
To zoom to nominal map scale:

1. Select the appropriate map window.
2. Select View > Display Properties; then set the map scale for the GeoWorkspace.
3. Click Apply; then click Close.
4. Optional: Set the appropriate view-dependent style sizes for each legend entry in the
Select Style dialog box.
15-4
5. Select View > Zoom > to Nominal Map Scale.
Defining Marginalia Specifications in the Map Window

Marginalia items in the layout window consist of the legend, north arrow, and scale bar.
The symbology for the marginalia being transferred from the map window to the layout
window is based on the current settings for each of the marginalia items. Whatever the
active parameters are for these marginalia items in the map window, the same parameters
are used to render these items in the layout window. In the case of the north arrow and
scale bar, each corresponding Properties dialog box in the map window contains a Save as
Default option. If this option is selected, the default settings, not the active settings, are
used when placing the north arrow and scale bar into the layout window. This ensures
consistency across layout sheets. If necessary, you can further customize the marginalia in
the layout window itself through various layout window commands, as explained later in
this chapter.
• Legend—The symbology for each of the legend components is based on the settings
defined on the Select Style, Legend Entry Properties, and Style Properties dialog
boxes for each of the legend items. Legend definitions in the map window have an
impact on what legend entries will be rendered in the layout window. If you do not
want a particular legend item to appear in the layout window legend, you should use
Hide Legend Entry (right mouse menu) in the map window legend.
See “Customizing the Legend“ in the “Working with Map Windows” chapter.
Legends are placed in the layout window with all default settings, regardless of the
changes made to the map window legend properties (such as changes to the
background color or the fonts of the title, subtitle, or heading).
• North Arrow—To display the north arrow in the map window, you select View >
North Arrow. On the shortcut menu (right mouse click) of the north arrow, you next
select Properties. You can then define the size of the arrow by selecting a point size
from the drop-down list or by typing the appropriate size. The drop-down list only
goes to 96 points, but you can type larger values, such as 288 points (4 inches). The
maximum size allowed is 32,767 points. You can also define the background color,
position, symbol used, and azimuth of the north arrow .
See “Displaying the North Arrow“ in the “Working with Map Windows” chapter.
There is a large assortment of predefined north arrows and compass roses available for
use in the map window. By default, they are delivered in the ..\Program
Files\GeoMedia\Program folder. You can refer to the file NorthArrows.pdf in this
folder for a graphic portrayal of the arrows and compass roses. As with the rest of the
marginalia, the north arrow placed in the layout window is based on settings defined in
the map window. The size of the north arrow typically found in the map window is
generally too small for a plotted map. It is likely that you will need to increase the size
of the north arrow for plotting.
15-5
• Scale Bar—To display the scale bar in the map window, you select View > Scale Bar.
On the shortcut menu (right mouse click) of the scale bar, you then select Properties
and make the appropriate changes. Use Define intervals on the Intervals and Units
tab to define a fixed size scale bar. When this option is not selected, the size of the
scale bar will be 20% of the width of the map window.
See “Displaying the Scale Bar“ in the “Working with Map Windows” chapter.
Basic Map Layout Workflows

The flexibility of the Layout Window commands lets you tailor the actual workflow you
use to your exact requirements. The following workflows illustrate the typical uses of
these commands.
Placing Map Graphics in Layout Sheets Using Layout

Frames
This workflow is commonly used for producing a quick plot of data displayed in a map
window, where the map scale can vary and the size of the marginalia items do not have to
conform to pre-defined specifications. This workflow basically fits the map graphics into
pre-defined layout frames.
1. Set up your map window with the specific data you want displayed at the appropriate
zoom level, and define the appropriate marginalia settings.
2. Open the layout window, and using the Sheets > Insert Sheet command, insert a blank
layout sheet.
3. Optional: Use the assortment of drawing commands available in the layout window
for placing title blocks, additional text, company logos, and so forth, to embellish the
map.
4. Using the Insert > Layout Frames command, select the marginalia items to place, and
identify the location for each of the layout frames in the layout sheet.
See the “Layout Graphics Components” section in this chapter and GeoMedia Help
for more information on the drawing commands.
5. Select the previously placed layout frame group, and select Insert > Graphics into
Layout Frames. Identify the appropriate map window, geographic extent, plot scale,
and mode.
6. Modify the size and position of the map graphics as necessary.
7. Optional: Place a cartographic grid using the Insert > Cartographic Grid command.
8. Optional: Place a reference grid and reference index using the Insert > Reference
Grid and the Insert > Reference Index commands.
15-6
9. Select View > Zoom > to Actual Size to preview the map layout.
10. Select File > Print to plot the layout sheet.
OR
Using the Sheets > Export Layout command, export the layout sheet to one of the
available export formats.
Placing Map Graphics in Layout Sheets Without Using

Layout Frames
This workflow is commonly used for producing a plot of data displayed in a map window,
where the map and its associated marginalia must conform to pre-defined specifications.
1. Set up your map window with the specific data you want displayed at the appropriate
zoom level, and define the appropriate marginalia settings.
2. Open the layout window, and using the Sheets > Import Layout command, import a
layout template.
3. Optional: Use the assortment of drawing commands available in the layout window
for placing title blocks, additional text, company logos, and so forth, to embellish the
map.
4. Select the Insert > Map command. Identify the appropriate map window, geographic
extent, plot scale, and mode.
See the “Layout Graphics Components” section in this chapter and GeoMedia Help
for more information on the drawing commands.
5. Select the previously placed map, and then select the Insert > Legend command, and
identify the location for the placement of the legend in the layout sheet.
6. Select the previously placed map, and then select the Insert > North Arrow
command, and identify the location for the placement of the north arrow in the layout
sheet.
7. Select the previously placed map, and then select the Insert > Scale Bar command,
and identify the location for the placement of the scale bar in the layout sheet.
8. Modify the size and position of the map graphics as necessary.
9. Optional: Place a cartographic grid using the Insert > Cartographic Grid command.
10. Optional: Place a reference grid and reference index using the Insert > Reference
Grid and the Insert > Reference Index commands.
11. Select View > Zoom > to Actual Size to preview the map layout.
12. Plot the layout.
OR
15-7
Using the Sheets > Export Layout command, export the layout sheet to one of the
available export formats.
Components of the Map Layout

As discussed earlier, there are two kinds of graphic components in the map layout, map
graphics and layout graphics. Map graphics consist of an extracted subset of the map
window (a map) and supporting marginalia (legend, north arrow, and scale bar). Layout
graphics are graphics such as borders, titles, and company logos. This section discusses
both kinds of components.
Map Graphics Components

You can insert maps or maps and their associated marginalia into layout sheets with the
Insert Map and the Insert Graphics into Layout Frames commands, respectively.
These commands let you insert maps and selected marginalia into the location you want on
a layout sheet in the layout window. You can review the status of the placed map graphics
using the Map Properties command.
Insert Map inserts a single map into an empty layout sheet, without predefined layout
frames. You can then place marginalia for the map with the individual commands for their
respective placements: Insert Legend, Insert North Arrow, and Insert Scale Bar. The
graphic size of the marginalia is determined by the current map window settings for each
marginalia item. Insert Graphics into Layout Frames inserts a map and its associated
marginalia in a single step into existing layout frames, which were previously placed in the
layout sheet with the Insert Layout Frames command. This command places marginalia
to fit into all drawn layout frames.
Map Specifications
Map specifications for the Insert Map and Insert Graphics into Layout Frames
commands are defined in terms of a map window, a geographic extent, a plot scale, and a
static/dynamic mode setting.
Map Window
The map window definition identifies the content of the map to be portrayed in the layout
window by using the legend settings of the map window to define feature symbology and
to display priority. The default map window is the last one used with either of these two
commands, or it is the first map window in the alphabetical drop-down list if it is the first
time either command is used or if the last used map window no longer exits.
Geographic Extent
The geographic extent defines the geographic footprint, or coverage, of the map to be
portrayed in the layout window. In many cases, the geographic extent you want is a subset
15-8
of the map window, which can be defined in a variety of ways. You can select the method
for defining the geographic extent for the map from the following methods, and you can
provide any additional necessary parameters:
• Existing Shape—Uses an existing, user-defined area geometry type or compound
geometry type (containing an area definition) in the map window to identify the
geographic extent. When a compound feature is selected that contains multiple
polygons, the largest polygon is used to define the existing shape. The area between
the outside of the area feature and the layout frame limits is cropped.
• Geographic Frame—Requires a user-defined entry of the upper-left and lower-right
corners of the quadrangle, defined using geographic coordinates (for example, d:m:s)
to identify the geographic extent. This option is valid for projected or geographic
coordinate systems defined in the GeoWorkspace coordinate system settings. The area
between the outside of the quadrangle and the layout frame limits is cropped.
• Map Window (the default method)—Uses the area currently displayed in the selected
map window to identify the geographic extent.
The map window display area is defined by the window extent when the map window
is in the Restored state. This is because only one window can be maximized at a time,
and when the active window is maximized, all other non-minimized windows revert to
their Restored state. This behavior may give the perception that this selection is
producing the wrong result.
To illustrate this behavior, open a single map window (with data) and the layout
window. Make the map window active, and maximize the window. Fit the map data
to the window by selecting View > Fit All. Next, select Window > Tile Horizontally.
The map window and layout window are now both currently being displayed in their
Restored states. However, the displayed data extent in the Restored map window is
half of the displayed data extent of the maximized map window. If the windows are in
their maximized state, and the layout window is active, the map window will appear
Restored in the background. If the map window active, it will appear maximized, and
the layout window will be Restored in the background. Only one window can be
maximized at a time, so to get around this behavior, minimize all windows except the
map window you want, and select Window > Tile Horizontally. The map window
will be made as large as possible within the application, displaying the Restored state.
• Paper Size—Requires a user-specified paper size. The units for the Height and Width
values are based on the Distance unit defined on the Layout tab of the Options dialog
box. The unit type (inches, centimeters, and so forth.) is displayed to the right of the
fields. By default, the height and width are equivalent to the sheet size. The
geographic extent varies based on the plot scale selected.
• Polygon—Requires a user-defined digitizing of a polygon to define the geographic
extent. The area between the outside of the polygon and the layout frame limits is
cropped.
15-9
• Projected Frame—Requires a user-defined diagonal entry of the upper-left and lower-

right corners of the frame or rectangle, defined using projected coordinates to identify
the geographic extent. This option is valid for projected coordinate or geographic
systems defined in the GeoWorkspace coordinate system settings.
• Rectangle—Requires a user-defined, two-point rectangle definition in the map window
to define the geographic extent.
• Spatial Filter—Requires an existing, user-selected spatial filter to define the
geographic extent. The area between the outside of the spatial filter and the layout
frame limits is cropped.
Plot Scale
The plot scale of the map defines the relationship between ground units and the paper units
used when portraying the geographic extent on the paper. You can select the method for
defining the plot scale using one of the following methods:
When you start either command, the default plot scale is equal to the display scale defined
in the map window on the Display Properties dialog box.
• User-defined —This option is available with the Insert Graphics into Layout
Frames and Insert Map commands. The size of the resulting map is predetermined
based on the combination of the geographic coverage selected and the plot scale
defined. This is true for all geographic extent methods using the Insert Map
command and for most geographic extent methods using the Insert Graphics into
Layout Frames command. The one exception is the Map Window geographic extent
method in the Insert Graphics into Layout Frames command. When this geographic
extent method is used, the size of the resulting map will be based on the original layout
frame, where the map will be placed in the layout frame at the specified scale, and then
cropped to fit the original frame.
Note: If the size of the map placed exceeds the size of the paper (defined on the
Layout Window Page Setup dialog box), you must do one of two things. You can
either increase the size of the paper on the Layout Window Page Setup dialog box, or
you can crop the map placed so that it fits the paper.
• Fit to frame—This option is only available with the Insert Graphics into Layout
Frames command. The plot scale is automatically calculated to perform a best-fit of
the geographic extent into the existing layout frame. This option ensures that the map
fits within the limits of the current layout design.
15-10
Static and Dynamic Modes

The mode of the map graphics determines the relationship and behavior between the map
graphics portrayed in the layout window and their originating map window. You can
select from the following modes:
• Static mode captures a snapshot in time, that is, what the data looked like when it was
placed into the layout sheet. Any changes made in the originating map window are not
automatically reflected in the layout window. With this mode, you must use the
Update Map Graphics command to update the map. When Static mode is selected,
the originating map window of the map graphics can be deleted without affecting the
map layout.
• Dynamic (the default) mode permits automatic updates, that is, certain types of
modifications made in the map window are automatically reflected in the layout
window, such as symbology changes or the addition or removal of feature classes.
When Dynamic mode is selected, the originating map window of the map graphics is
required to maintain the link with the map layout.
You can switch from dynamic mode to static mode using the Map Properties command,
but you cannot switch from static mode to dynamic mode.
See the “Modifying Maps” section in this chapter for information.
Note: Plotting performance and quality may be affected by the Static or Dynamic mode
selection. When map graphics are placed in the layout window using Static mode, they are
rendered at the screen resolution, which is usually less than the plotting device resolution.
In general, Static mode graphics plot faster than Dynamic mode graphics, but Static mode
graphics produce a reduced overall quality (when compared to Dynamic mode graphics).
The degree of improved performance or quality degradation using Static over Dynamic
mode is based on the density of the data being plotted relative to the resolution of the
plotter device selected. This is especially evident when plotting high-resolution raster
images in the layout window.
Marginalia Specifications
Marginalia items placed in the layout sheet are always associated with a map. The
marginalia specifications for the Insert Graphics into Layout Frames, Insert Legend,
Insert North Arrow, and Insert Scale Bar commands are defined in terms of a legend,
north arrow, and scale bar. The display parameters used for rendering the marginalia in the
layout sheet are based on the command used to place them and their respective properties
defined in the map window.
Legend
When placed using the Insert Legend command, the legend is placed in the layout sheet
using a fixed size based on a combination of the number of columns, the size of the legend
15-11
keys, and the size of the feature text. When placed into an existing layout frame using the
Insert Graphics into Layout Frames command, the single column legend is scaled to fit
in the vertical direction. In the event that scaling in the vertical direction causes the
horizontal direction dimension to exceed twice (2X) the size of the original layout frame,
the scaling will be based on the horizontal direction.
Placement of the legend into a legend layout frame will use the lower-left corner of the
layout frame as the point of origin. Legends can be edited, moved, and scaled after
placement. Legends associated with dynamic maps are also dynamic, meaning that as
symbology modifications are made to the map, the legend is automatically updated to
reflect any changes in the map. Legends can be modified to change the number of
columns, the key styles, and so forth, and they still maintain their dynamic association with
the map. However, if the legend is converted to graphics using the Convert to Graphics
command on the right mouse menu, the dynamic link is lost and all components are
converted to standard layout graphics, the same as if they were placed using the drawing
commands.
North Arrow
When placed using the Insert North Arrow command, the north arrow is placed in the
layout sheet using the size parameters defined in the North Arrow Properties dialog box
of the originating map window. When placed into an existing layout frame using the
Insert Graphics into Layout Frames command, the north arrow is scaled to fit the
smaller of the two “X” or “Y” layout frame directions.
Placement of the north arrow into north arrow layout frames will be such that the center of
the north arrow will be coincident with the center of the original layout frame, adjusting
the layout frame to match the newly calculated size of the north arrow. North arrows can
be edited, moved, and scaled after placement, but they cannot be rotated.
Scale Bar
When placed using the Insert Scale Bar command, the scale bar is placed in the layout
sheet using the parameters defined in the Scale Bar Properties dialog box of the
originating map window. When placed into an existing layout frame using the Insert
Graphics into Layout Frames command, the size of the scale bar varies based on the
settings defined in the Scale Bar Properties dialog box of the originating map window.
If the properties are defined as automatic (the Define intervals check box is unchecked on
the Intervals and Units tab), the scale bar will be scaled so it fits within the extent of the
layout frame’s “X” direction, (plus/minus one interval – to allow for round off). If the
properties are defined as fixed (the Define intervals check box is checked), the scale bar
will be sized according to the pre-defined interval setting.
Placement of the scale bar into scale bar layout frames will be such that the center of the
scale bar will be coincident with the center of the original layout frame, adjusting the
layout frame to match the newly calculated size of the scale bar. Scale bars can be edited,
moved, and scaled after placement, but they cannot be rotated.
15-12
There are assorted tools and commands available that can be used to adjust the graphic
display of the marginalia items after they have been placed in the layout sheet.
See the “Modifying Map Graphics in Layout Sheets” section in this chapter for
information.
Layout Graphics Components

You can place and edit layout graphics components with the Layout Window Graphics
commands, or drawing commands, that are enabled when you select Window > Show
Layout Window to display the layout window. You access these commands from the
various layout window toolbars and menus. This section discusses these commands and
provides an example workflow that illustrates the use of various commands. Complete,
detailed documentation of all these commands is available in the context-sensitive online
GeoMedia Help.
See the “Layout Window Graphics Commands” appendix for a complete list of these
commands.
Looking at the Drawing Toolbox

Most of the layout window graphics commands are found on or accessed through the
Drawing toolbox, which is displayed by default at the bottom of the layout window.
These commands let you place, edit, and symbolize layout graphics. In addition, this
toolbox lets you define the active linear and fill styles and lets you apply those styles to
elements in a select set. You can turn this toolbox on or off through View > Drawing
Toolbox.
For various placement and editing commands, additional fields are displayed on the right
side of an expanded Drawing toolbox. For example, when you select the Circle
command, a Radius field is added.
• Draw—Displays an assortment of menus of commands that operate on graphic

elements in a select set, and provides additional commands to create symbols and to
define the active symbol for placement.
• Select Tool—Selects elements in the active layout sheet, and terminates any other
active commands. This is the default active command in the layout window.
15-13
• Placement and Editing tools—Available from corresponding drop-down menus.

These commands are also available on their corresponding toolbars.
• Text—Places one or more text boxes into which you can place text.
• Delete—Deletes the objects in a select set.
• Linear Controls—Define an active linear style by defining the color, width, pattern,
and terminators, end cap, and join settings; and apply the style.
• Caps and Join Controls—Applies the active linear end cap and join style to objects in
a select set.
• Fill Controls—Apply a solid color fill to rectangles, circles, ellipses, and polygons.
Note: If the layout window Drawing toolbox and Ribbon toolbar are deleted, and the
session is exited and saved, and then GeoMedia is reopened, the toolbox and toolbar are
displayed again in the new session.
Draw Menu Commands

Clicking Draw displays menus of the following commands for fine tuning layout window
graphics (some commands are also available on their corresponding toolbars):
See the corresponding topics in GeoMedia Help for information on using these commands.
Group
Ungroup
Order > Bring to Front
Send to Back
Bring Forward
Send Backward
Nudge > Up – Up Arrow
Down – Down Arrow
Left – Left Arrow
Right – Right Arrow
Align > Left
Center
Right
Top
Middle
Bottom
Distribute > Horizontally
Vertically
15-14
Spin or Flip > Spin

Spin Left
Spin Right
Flip Horizontally
Flip Vertically
Create Symbol
Set Active Symbol
See “Creating Symbols” later in this section.
Placement and Editing Commands

The Drawing toolbox always displays the icon for the active placement command and the
active editing command. You can either click on the button to start the corresponding
placement or editing command or click on the drop-down button to select another
command from a palette of commands. These commands are also available on layout
window menus.
Placement Menu Editing Menu

See the corresponding topics in GeoMedia Help for information on using these commands.
Additional Placing and Editing Toolbars

The following additional toolbars provide easy access to commands for placing and editing
layout window graphics. These command are also available on layout window menus.
See the corresponding topics in GeoMedia Help for information on using these
commands.
15-15
The Ribbon toolbar contains the options for the layout window Select Tool when you first
open the layout window because it is the default active command. This toolbar appears by
default in the upper-left corner below the menu bar. When a command is active that does
not use this toolbar, it is collapsed as in the figure to the right above. When a command is
active that does use the toolbar, it contains the options for that command, for example the
Text command, as seen in the following figure.
See the GeoMedia Help for information on the Select Tool.
The Layout Toolbar

The Layout toolbar appears by default at the left side of the layout window. This toolbar
contains commands for working with both map graphics and layout graphics, as described
in this chapter. The Select Tool is the default active command in the layout window.
Changing Graphic Element Properties

Once graphic elements are placed in the layout window, you can easily display and change
their properties by selecting an element and then by starting its corresponding Properties
command from the right mouse menu.
Graphic elements can be divided into four categories:
• Linear (line, arc, curve, and polyline)
• Symbol
15-16
• Area (circle, ellipse, rectangle, and polygon)

• Group
The properties for each element can in turn be divided into general properties and
geometry properties, which are set on the corresponding two tabs of the various Properties
dialog boxes. For group elements, however, this dialog box does not have tabs. The
General tab is the same within each category. The General tab for linear and area
geometries contains an option to toggle between a Simple Style and a Map Window
Style. Note that some dialog boxes (for example, legend, mapframe, object, and text) do
not have the Simple/Map window style option. You can define simple line styles or select
a map window style from the named styles of the GeoWorkspace. When choosing a
named style, the remainder of the controls in the Style definition frame are disabled. Also
in this case, the style definition is converted to a layout window style definition. Some
aspects of a complex style definition may be lost during this process, and special handling
is required for point style types used in pattern line styles.
The Geometry tabs are different for each element type. When you select this command,
all the fields on this dialog box are initially populated with the properties of the currently
selected element.
For example, the following Line Properties dialog box is displayed for line elements:
15-17
See the corresponding topics in GeoMedia Help for information on the various Properties
dialog boxes.
The general properties typically include layer, line color, line width, and line style. For
linear elements, they also include begin and end terminators as well as caps and joins. For
area elements, they also include fill properties, that is, if it has solid fill and fill color. For
symbols, they only include layer and symbol file. You can edit all the properties except
the symbol file, which is read-only. All of the properties of a group are general in nature;
no geometry properties are shown for a group.
The geometry properties vary according to the different elements and can include
coordinates, height, width, and rotation angle. For ease of editing, the command supports
both move and edit modes. In move mode, you can only change the position of the
element, not its shape. In edit mode, you can change both the shape and the position of the
element. You can use either mode, or you can switch between them.
The following table lists the elements and their geometry properties:
Element Geometry Properties
Arcs Center, start, and end coordinates; radius; start and sweep angle
Curves All the nodes
Ellipses Center point, primary and secondary axes, and rotation angle
Lines Start and end coordinates, length, and angle
Polygons All the vertices
Polylines All the vertices
Rectangles Four coordinates representing the four corners, height, width, and angle
15-18
Symbols Origin coordinates, scale factor, and angle

The Properties command also lets you delete vertices or nodes of polyline, polygon, and
curve elements.
Groups are a special element type in that they are collections of elements from the other
element types and group properties. Thus they are different from other graphic element
properties.
After changing the appropriate properties and clicking OK, the selected element is
displayed on the specified layer with the specified sheet position, size, and angle. For
linear types, the selected element is also displayed with the specified line color, style,
width, and terminators. For area types, the selected element is also displayed with the
specified line color, style, width, and fill color. If a group, the map frame name is updated
appropriately.
Changing Group Properties

Only groups constructed using the Insert Layout Frames command are eligible for
editing, specifically the map frame name used by the Batch Plotting utility. You can
change the properties of a group through the Group Properties dialog box. You start this
command by selecting the layout frame group and then Properties from the right mouse
menu. The read-only properties listed are the following: number of items in the group, if
the group is nested within another group, and if the group contains nested groups. The
Batch Plotting-related map frame name is only enabled on valid layout frame groups.
See GeoMedia Help for complete information on this dialog box.
Placing Text
Clicking the Text button on the Drawing toolbox lets you place text elements by either of
two methods, single point placement or rectangle placement. In the single point placement
method, you click on the layout window, and a text box is placed with an initial size of a
single character. As you type, the text box expands horizontally to accommodate the
characters typed. Once the text box has been placed, the size of the box cannot be
modified except by changing the font size. In the rectangle placement method, you use a
15-19
mouse down, mouse drag, mouse up sequence to define the dimensions of the text box.
Then as you type, the text box never expands horizontally, but may expand vertically to fit
the text. With this placement method, you can later modify the size of the box.
You can move text by selecting anywhere in the text box or on the outline of the text box,
provided you are not selecting a solid-filled handle. You can also change the size of the
text box containing the text, provided you select and drag a solid-filled handle. While
placing or editing the text, you can change the characteristics of the text (font, size, color,
bold, italic, underline, and justification) by using the Ribbon toolbar that is automatically
displayed.
Note: For all new text inserted, the layout window defaults to igTextSizeTypeTile. All
old text that was placed at another standard is interpreted using this standard.
Changing Text Properties

After placing the text, you can later change its properties by selecting the text and then by
selecting Properties from the right mouse menu to display the Text Properties dialog box,
which has three tabs.
See GeoMedia Help for information on using this dialog box.
The Text tab lets you change the font, text direction, text alignment, margins, and line
spacing.
15-20
The General tab lets you change information for layer and textbox style, such as border,
fill, and shadow. The Geometry tab lets you change the position and size of the text box,
such as lower-left coordinates, width, height, and angle.
Working with Linear Styles

Various controls on the Drawing toolbox let you review, define, and apply an active linear
style. This active style includes the color, width, pattern, terminator, end cap, and join
settings. When you open the layout window, the controls on the Drawing toolbox are
initialized to reflect the properties of the active linear style, which is displayed on the
Apply Linear Style button in the middle of the toolbox.
Clicking the Apply Linear Style button applies the linear style to the objects in the select
set. This button also provides a preview for the linear style. The preview is updated when
a change is made to the linear color, width, type, terminator, end cap, or join settings, or
when a map window style is selected.
You can define simple line styles or select a map window style from the named styles of
the GeoWorkspace through the active style menu, which displays when you click the
corresponding arrow button. This menu contains two options: Use Simple Style and
Select Map Window Line Style. The first option enables all the controls on the toolbox
and sets the active style to a Simple line style defined by those controls, that is, you can
edit simple styles at the component (color, width, and so on) level using the toolbox. The
second option displays the Select Style dialog box, which is restricted to linear styles in
this context. When choosing a named style, the remainder of the toolbox buttons are
disabled, so you cannot edit the style as with the first option. Also in this case, the style
definition is converted to a layout window style definition. Some aspects of a complex
15-21
style definition may be lost during this process, and special handling is required for point
style types used in pattern line styles. These conversion issues are discussed in the
following section.
Note: You can also define simple line styles or select a map window style from the named
styles of the GeoWorkspace through the Line Properties dialog box options. When
choosing a named style, the remainder of the controls in the Style definition frame are
disabled. Also in this case, the style definition is converted to a layout window style
definition.
See “Changing Graphic Element Properties” earlier in this chapter.
Styles Conversion
The map window styles system and the layout window style system differ enough that the
conversion from one to another is not complete. The following tables describe what
converts, what partially converts, and what does not convert. Entries that do not convert
have a note to describe what is done under that condition.
Point styles are a special case. Because the layout window can only use .sym files for
symbol styles, all non-sym symbols need to use a substitute .sym. The
SymbolRendererName and Source property are used to parse the cell/symbol/filename.
Then the software looks for a .sym matching the name of the symbol in the folder in which
the source resides. If a suitable .sym is not found, the symbols folder is searched. If a
matching .sym still is not found, a default symbol is used and an error message is
displayed. For predefined symbols, a matching .sym is delivered. Font styles are
simulated by creating a .sym containing a field.
Style Properties – Simple Line Style
Functional Capability Convert? Notes
Color Yes —
Translucency Yes —
Width Yes Converted internally to mm.
Line type Yes —
Dash-gap sequence Yes —
Dash-gap sequence No Always uses igPhaseNormal.
proportional to width
Start cap Partially Square, round, triangle, and no cap are supported.
The four Anchor types are converted as no cap
with a corresponding terminator and scale based on
line width.
End cap Partially The four Anchor types are converted with a
corresponding terminator and scale based on line
width. The actual cap is set to the same value as
the start cap.
15-22
Dash cap No The dash cap cannot be defined independent of the

start cap. The actual cap is set to the same value as
the start cap.
Midline join Yes —
Offset – left/right Yes Direction determined by positive/negative value
Offset distance Yes —
Advanced tab - ABS No Ignored
Style Properties – Pattern Line Style
Point style Partially Styles are converted by .sym. Font styles are
emulated by .sym containing a field.
Position – Fix at start Yes Accomplished by Start terminator option.
Position – Fix at end Yes Accomplished by End terminator option.
Position – Fix at center No Ignored.
Position – Fix at vertex Yes Using ‘break on changes in direction’.
with angle
Position – Repeat with Yes —
spacing
Adjust to produce even Yes Gaps are set to stretchable.
spacing
Starting inset No This is problematic but may be added as a future
enhancement. Ignored
Ending inset No Ignored.
Offset – left/right Yes —
Offset distance Yes —
Advanced tab - ABS No Ignored.
Style Properties –Symbol Style
Type No These attributes are used to find a suitable
Source No substitute .sym.
Name No
Size Yes Symbol is scaled when converted.
Define override color Yes Accomplished on the Line Style dialog box.
Translucency No Ignored.
Rotation Yes Accomplished on the Line Pattern dialog box.
Alignment No Ignored.
Offset X distance Yes —
Offset Y distance Yes —
Display attribute value No Ignored.
in symbol
Ignore map rotation No Ignored.
15-23
Ignore geometry Yes Accomplished by Relative/Absolute orientation

rotation setting.
Always keep upright Yes —
Advanced tab - ABS No Ignored.
Style Properties – Font Style (simulated by a field in a symbol)
Font Partial Strikeout is not supported.
Size Yes —
Character Yes —
Color Yes —
Translucency Partial Only on border and fill.
Rotation Yes —
Alignment Partial Mapped.
Offset X distance Partial Simulated by symbol origin.
Offset Y distance Partial Simulated by symbol origin.
Display halo No —
Halo color No —
Halo size No —
Ignore map rotation No —
Ignore geometry Yes Accomplished by Relative/Absolute orientation
rotation setting.
Always keep upright No —
Advanced tab - ABS No —
Defining the Line Color

To define the color, click the Line Color arrow button to open the Select Color dialog
box, on which a thick black border around a color indicates the active color. You can
select the color from this palette; however, if you require more colors, you can select More
Colors to open the Color – DefaultColorPalette.xml dialog box, the standard GeoMedia
color dialog box used to define and select a custom color. The active line color is
displayed in the area below the paint brush on the button. In addition, clicking the paint-
brush button applies the active linear color to the objects in a select set. If you do not want
a line color for linear geometries (including area boundaries), you can select No Line.
See the GeoMedia Help Topics for complete information on using these dialog boxes.
15-24
Defining the Line Width

To define the width, click the Line Width arrow button to open the list of available line
widths from which to choose. In addition, clicking the width button applies the active
width to the objects in a select set.
Defining the Line Pattern

To define the pattern, click the Line Pattern arrow button to open the list of line patterns
from which to select the appropriate value. In addition, clicking the pattern button applies
the active pattern to the objects in a select set.
Defining the Line Terminators

To define the active set of terminators, click the Line Terminators arrow button to open
the Line Termintaors dialog box. Choose the Begin drop-down list to select the
terminator begin style, and choose the End drop-down list to select the terminator end
style. Terminator styles cannot be applied to rectangles, circles, ellipses, or polygons. In
15-25
addition, clicking the terminator button applies the active terminator set style to the objects
in a select set.
Defining End Cap and Join Styles

Clicking the End cap and Join button applies the active linear end cap and join style to
objects in the select set. The end cap and join settings can be applied to linear geometries
(including area boundaries) but cannot be applied to rectangles, circles, ellipses, or
polygons. You can change the active set of linear end cap and join by clicking the
corresponding arrow button, which displays the Select Caps and Joins dialog box for
defining the start and end cap and mid-line join types for the active style.
Start and end caps – Square

Mid-line join – Miter
Start cap – Triangle; End cap –

Triangle
This dialog box lets you select the end cap and mid-line join styles from its two drop-down
lists. The Start and end cap list contains for items: Round (the default), Square, Flat,
and Triangle. The Mid-line join list contains three options: Round (the default), Miter,
and Bevel). The cap and join settings should match for closed shapes, or the vertex where
the begin and end points meet will look odd.
15-26
Color Filling Objects

The Color Fill button lets you apply a solid color fill to rectangles, circles, ellipses, and
polygons. To define the color, click the Fill arrow button to open the Select Color dialog
box, on which a thick black border around a color indicates the active color. You can
select the color from this palette; however, if you require more colors, you can select More
Colors to open the Color – DefaultColorPalette.xml dialog box, the standard GeoMedia
color dialog box used to define and select a custom color. The active fill color is displayed
in the area below the paint can on the button. In addition, clicking the paint-can button
applies the solid fill style to the objects in a select set. If you do not want a fill color, you
can select No Fill.
See the GeoMedia Help Topics for complete information on using these dialog boxes.
Looking at the Standard Toolbar

There are two commands on the Standard toolbar to note for special use in the layout
window.
Zoom to Actual Size—Displays the active layout sheet at a 1:1 paper scale.
Hide Layout Window—Hides the layout window and shows the previously active
window, either the map window or the data window.
TIP: If you right click with the cursor on this toolbar, a menu of the layout toolbars is
available for selection and display.
Creating Symbols
Symbols used in the layout window are stored as symbol files, which are documents with
an .sym extension. You can insert these symbols into layout sheets for various map
15-27
compositions. Create Symbol lets you create a layout window symbol by saving selected
graphics as a symbol file. You can create a symbol by first selecting any geometry and
then by clicking the Create Symbol command button on the Drawing pull-down menu.
You next define the origin by clicking the point that you want in the select set and then
save the select set as a symbol.
Note: You cannot create a symbol containing a map graphic because the dynamic nature
of a map graphic makes it unsuitable for use as a symbol. You cannot insert a layout
window symbol file (.sym) into a GeoMedia symbol file (.fsm) file. This is a currently an
unsupported workflow.
Symbols that you create display the following default behaviors:

• 90-degree rotation angles.
• Automatic alignment with a target element or object when the symbol is placed in a
document.
• No inherited size from their source definition; size is determined by the Styles dialog
box, not the size the symbol was created with.
Note: You can add a layout window symbol file (.sym) to the GeoMedia symbol file
(.fsm) with the Define Symbol File utility.
See the Define Symbol File Help for more information.

To place these symbols in the layout window, you must first set an active symbol with the
Set Active Symbol command on the Drawing pull-down menu, unless you want to use the
default symbol. Then, you place the symbol with the Symbol command on the Placement
menu. These two symbol commands are discussed in the following sections.
To create a symbol:
1. Select a set of elements on the layout sheet.
2. From the Drawing toolbox, select Draw > Create Symbol.
3. Click a point on the layout sheet to define the origin of the symbol.
4. On the Save As dialog box, select the directory, and then type an appropriate name.
TIP: When creating a symbol using different elements, press CTRL while choosing
elements with the Select Tool.
15-28
Setting an Active Symbol

The Set Active Symbol command, accessed from the Draw menu on the Drawing
toolbox, lets you specify a symbol and an appropriate scale factor to be placed one or more
times in a layout window readily and interactively. This command works with the Symbol
command to place the symbol.
To set an active symbol, you select a symbol filename, which provides a preview of the
specified symbol, and an appropriate scale factor. The scale factor is a double value
greater than zero, with a default value of 1. Modifying the scale factor does not affect the
look of the symbol displayed in the preview box. If you start the Symbol command before
setting an active symbol, the default symbol Point.sym (delivered in the
GeoMedia\Symbols\Geometry folder) is placed.
To set an active symbol:

1. Open a layout window and make it active.
2. Select Draw > Set Active Symbol from the Drawing toolbox or from the Symbol
toolbar.
3. Click Browse.
15-29
4. Select an appropriate symbol file; then click Open.

5. Type a value greater than 0 in the Scale factor field of the Set Active Symbol dialog
box; then click OK.
Placing a Symbol
The Symbol command lets you place the active symbol interactively with a mouse click.
The active symbol can be one you have defined with the Set Active Symbol command or
the default symbol, Point.sym. The origin of the symbol being placed is attached to the
cursor when you move the cursor, and the symbol is placed at the cursor location upon
clicking. You can place multiple symbols until you exit the command.
TIP: You can also drag and drop symbols (.sym) into the layout sheet from Windows
Explorer.
To place a symbol:
1. Open a layout window and make it active.
2. Select an active symbol using the Symbol command from the Drawing, Placing, or
Symbol toolbar.
OR
Use the default symbol, Point.sym.
3. Select the Symbol command from the Drawing, Placing, or Symbol toolbar.
The symbol is displayed in dynamics and attached to the cursor as the cursor moves.
4. Click to place the symbol.
15-30
The symbol is placed, and another symbol is displayed in dynamics and attached to the
cursor.
5. Click to place the symbol again, and continue doing so as appropriate.
OR
Press ESC or select Exit from the right mouse menu to exit.
Changing Symbol Properties

After placing a symbol, you can later change its properties by selecting the symbol and
then by selecting Properties from the right mouse menu to display the Symbol Properties
dialog box, which has two tabs. The General tab lets you define the layer and review the
source file of the selected symbol. The Geometry tab lets you move the symbol by
changing the origin values, lets you change the symbol size by changing the scale factor,
and lets you rotate the symbol by changing the angle. You can also set the mode to move,
rather than edit by checking the check box. In the move mode, you can only change the
position of the element, not its shape. In edit mode, you can change both.
Zooming to Actual Size

Zoom to Actual Size lets you preview the plotted area at the paper size on the screen.
This command lets you rescale the view in the active layout sheet to the actual size as if it
were printed on paper, thus functioning similarly to the Print Preview command in
Word®. Obviously, most plots exceed the size of the monitor, so you need to use the Pan
command or horizontal and vertical scroll bars to move about in the layout window. You
can access this command from the Standard tool bar or the View menu.
Zoom to Actual Size is useful in the plotting workflow to let you see the layout at actual
size before printing, that is, it lets you have a WYSIWYG view or plot preview of your
15-31
layout window. This command affects the entire active sheet; the center of the sheet view
is maintained, but the graphic contents are scaled. This command assumes that you have
defined the logical dimensions for the layout sheet in the Page Setup command and that
the appropriate extent of the data is displaying properly in the layout sheet. If graphics are
falling outside the sheet limits, you should increase the size of the layout sheet.
Zoom to Actual Size gives a 1:1 representation. However, this may not necessarily be
completely accurate in the final output. Printers usually give the resolution in dots-per-
inch (DPI), so it is easy to convert pixels to real inches. In contrast, video displays give the
resolution only in pixels. Video displays are a certain number of pixels wide but are
without any information about the real display-area dimensions. It is impossible for a
program to determine the real output dimensions because there is no way for it to
determine the real dimensions of the viewable area on a video display. When output is
destined for a printer, an application can determine dots per real inch; however, for a video
display, these numbers define a logical inch, which is almost never equal to a real inch.
Toggling Windows
The Hide Layout Window command is enabled when the layout window is active and
hides the layout window and shows the previously active window, either the map window
or the data window. You can also switch between windows through commands on the
Windows pull-down menu.
The corresponding Show Layout Window command is enabled when either a map or data
window is active. It creates the layout window (if necessary), displays it, and makes it the
active window.
Setting SmartSnap
As you move the pointer in the layout sheet, the software automatically updates values in
the ribbon bar, giving you constant feedback on the size and position of the element you
are drawing. As you draw, the software also shows next to the pointer a temporary,
dynamic display of the element you are drawing––this feedback is called a relationship
indicator. When the software recognizes a relationship, it displays a relationship indicator
at the pointer. As you move the pointer, the software updates the indicator to show new
relationships. If a relationship indicator appears by the pointer when you click to draw the
element, the software applies that relationship to the element. The software can recognize
one or two relationships at a time. When the software recognizes two relationships, it
displays both relationship indicators at the cursor, as seen in the example on the right.
15-32
The Tools > SmartSnap Settings command lets you define which relationships are
recognized by the software as you draw. On the SmartSnaps tab you can set these
relationships and clear those you do not want so that the software does not place
relationship handles. A relationship handle, or glyph, is a graphic used to represent a
geometric relationship between elements, showing that the designated relationship is being
maintained. You set these relationships by selecting the appropriate check boxes on the tab
The Cursor tab lets you define the sizes of the Locate zone around the pointer in pixels.
The locate zone is a circular area at the center of the crosshair cursor or at the end of the
arrow cursor that specifies how close the cursor must be to an element you want to
recognize or select. When using the placement and editing commands and the cursor is
within this distance of a graphic element in the layout window, the element is snapped to if
the appropriate snap has been turned on. The software recognizes relationships based on
elements within the locate zone so that you do not have to move the cursor to an exact
position. For example, if part of an element is within the locate zone, the software
recognizes a Point On relationship. The size of the locate zone is indicated by a circle
around the center of the pointer crosshair.
The Preview display shows the size of the locate zone.
Inserting Non-Map Graphics

The Insert Object command lets you insert non-map graphics, such as logos and tabular
data, into a layout window through linking and embedding. The difference between
linking and embedding is how the data are stored and updated. This command inserts any
OLE 2.0-enabled object, such as a Word or .avi document, or a CAD document, such as a
.dwg document.
15-33
• When you link an object to a document, the document stores information about where
the object is located—the object is not stored in the document. When you embed an
object in a document, a copy of the object is stored in the document.
• When you make changes to a linked object, all documents that have links to that object
update. When you make changes to an embedded object, only the copy of the object
that is stored in the document updates.
Inserting raster files as objects into the layout window with this command involves various
complexities. The following discussion addresses raster images as objects, but it applies to
other types of objects as well.
When inserting OLE/COM raster objects, the appearance of the object is dependent on the
serving application. If you encounter display errors, convert your image to a .bmp file
using Microsoft Paint, and then insert the .bmp as an object.
To insert a new object:

1. Select Insert > Object.
2. Select the Create New option.
3. In the Object Type list, select the type that describes the software in which you want
to create the object, and then click OK.
15-34
Note: The contents of the list depend on which applications installed on your
computer support linking and embedding.
4. To return to the layout window, do one of the following:

• If the object was created in another application in a separate window, select Exit or
Update on the File menu in that application. If a message appears asking if you
want to update the document, click Yes.
• If the software temporarily replaces some of the GeoMedia or GeoMedia
application menus and toolbars, click anywhere outside the embedded object.
• When you return to GeoMedia or to a GeoMedia-based application, a box the size
of the object appears beside the pointer. You can click on the layout sheet to place
the object that you edited or created.
To insert an existing object:

1. Select Insert > Object.
2. Select the Create from File option.
3. In the File field, type or select the name of the object you want to embed, and then
click OK.
4. When a box the size of the object appears beside the pointer, you can click on the
layout sheet to place the object that you edited or created.
Note: If you are working in the source software, you can embed an existing object
with the Paste Special command on the Edit menu. In addition, you can embed an
object by dragging and dropping a document from Windows Explorer into a layout
sheet in the layout window.
display of an object after it has been placed in the layout sheet.
See the “Changing Object Properties” section in this chapter for more information.
Using the Layout Window Graphics Commands

This section illustrates the use of some of the previously discussed layout window graphics
commands. In this example, various layout window graphics are placed and manipulated
in a layout sheet into which a template and map window graphics (a map, legend, north
arrow, and scale bar) have already been placed, as seen in the following figure.
15-35
Creating a Map Title

To begin, create and place a map title. Select the Text button on the Drawing toolbox, and
use the rectangle method to place text.
Use a mouse down, mouse drag, mouse up sequence to define a rectangle. Next, select the
appropriate text characteristics from the text Ribbon toolbar, and then type the map title
text in the rectangle.
Tip: To see the name of an option on the ribbon bar, pause the pointer over an option and
read the ToolTip.
Select the text, and use the Move/Copy and/or Nudge commands to center the position of
the text.
Tip: With Move/Copy, you can copy selected graphic elements by selecting the element(s),
pressing CTRL, and then placing the copied element.
To make the map title stand out, place a frame around the text. Select the Rectangle
command from the Placement menu on the Drawing toolbox. Use a mouse down, mouse
drag, mouse up sequence to define the frame.
15-36
Now, select the previously placed frame, and then from the right mouse menu select
Properties. On the Rectangle Properties dialog box, adjust the frame properties by
changing the line width and color.
Inserting a Logo
Next, insert the city logo into the layout sheet. A logo is an non-map graphic that is
inserted as an object. Select Insert > Object from the layout window menu bar.
Ensure that the Create from File option is selected, and click Browse to find the logo file;
then click OK. When a box the size of the object appears beside the pointer, position the
logo, and then click on the layout sheet to place the logo.
To accurately align the logo with the north arrow above it, first create a select set
containing both items. Then select Draw > Align > Center from the Drawing toolbox.
15-37
Inserting a Symbol
Next, insert several layout window symbols (.sym files) to indicate a new recreation area in
the map. Before inserting a non-default symbol, you must first set an active symbol with
the Set Active Symbol command.
Select Draw > Set Active Symbol from the Drawing toolbox.
Click Browse to locate an appropriate symbol.
Next, select the symbol file, and then click Open. On the Set Active Symbol dialog box,
type a value greater than 0 in the Scale factor field, and then click OK.
To place the symbol that was set, select the Symbol command from the Placement menu
on the Drawing toolbox.
With the symbol displayed in dynamics attached to the cursor, position the symbol, and
then click to place the symbol. Another symbol is displayed in dynamics attached to the
cursor, but only one symbol is to be placed, so press ESC to exit the command. Then set
and place the other symbols in the same way.
15-38
Placing a Refernce Grid

The next step in this workflow is to place a reference grid in the map, although this does
not involve layout window graphic commands. The Insert Reference Grid command is
used to place this grid.
First, select the map layout frame in the layout sheet, and then Insert > Reference Grid
from the layout window menus.
See “Inserting References Grids and Indexes” later in this chapter for complete
information on using this command.
Select and type the appropriate grid parameters, and then click OK to insert the grid.
15-39
Removing Lines
In the final steps in this example, first remove various grid lines to make way for redlining
to highlight the new recreation area.
Select the Trim to Intersection command from the Editing menu on the Drawing
toolbox.
Use a mouse down, mouse drag, mouse up sequence to define the grid sections to be
cleared with a red line, as seen in the following figure on the left. Then, release the left
mouse button, and all the grid lines intersected by the redline are trimmed, as seen in the
following figure on the right.
15-40
Inserting Redlines
Now to add a redline indicator and identifying text, first select the Line command from the
Placement menu on the Drawing toolbox. Note the precision placement control that has
been added to the right side of the Drawing toolbox.
Next, change the line color by selecting the Line Color arrow button and then by selecting
red from the Select Color dialog box.
Then, increase the line width by selecting the Line Width arrow button and a value from its
displayed width list. The default line pattern is Solid, so it does not have to be changed to
draw the redline indicator.
Next, select an appropriate end terminator style by selecting the Line Terminator arrow
button to open the Terminator Styles dialog box and then by selecting a style from the
End Style list.
15-41
Note that as you make the changes in the line style, the line on the Apply Linear Style
button changes accordingly.
Now, draw a line from outside the map layout frame to the recreation area border, and then
identify it with text by using the text placement procedure previously used to complete this
example workflow.
TIP: Instead of clicking several points to draw a line, you can drag the pointer to draw a
line.
Workflows for Placing Map Graphics Using Layout

Frames
Inserting Layout Frames
Insert Layout Frames lets you design a map layout by placing layout frames for the
required map and optional marginalia items into the layout sheet. Layout frames are
containers that define the location you want in the map layout for the map, legend, north
arrow, and scale bar. The layout frames placed for a set of map graphics are automatically
associated with one another. Multiple maps and their corresponding marginalia items may
be placed in a map layout, with each map having its own associated marginalia. This
command lets you create templates and other plot layouts requiring map graphics to be
placed in fixed locations on the layout sheet.
You would typically use this command when you are starting from scratch and designing a
map layout, for example, for presentation graphics with multiple maps within one layout
15-42
sheet. You use the Insert Layout Frames command with the Insert Graphics into
Layout Frames command by using the former to define the placement location for the
map graphics with layout frames and then by using the latter to populate the layout frames
with the actual map graphics. After inserting the new group of layout frames, the group is
left in the select set, which lets you directly proceed to insert a map (and marginalia) into
the empty frames.
When designing a map layout, it is important to consider the relationship between the map
graphic being placed into the layout frames using the Insert Graphics into Layout
Frames command and the corresponding layout frames drawn using the Insert Layout
Frames command. The size and shape of the map graphic items may not always fit the
drawn layout frames exactly, potentially requiring minor adjustments to the map graphics
after they have been placed into the layout sheet. For the map being placed in the map
layout frame, the Plot Scale is the main consideration. With the Fit to frame plot scale
option, the map will automatically be sized to fit the frame, performing a best fit of the
geographic extent of the map into the drawn layout frame. The layout frame should never
be enlarged as it is populated, but it will likely be reduced in size in either the X or Y
direction. With the User defined plot scale option, the layout frame will be enlarged or
reduced in size to correspond with the keyed in plot scale. For marginalia items being
placed into layout frames, the marginalia item is sized based on a best fit into the existing
marginalia layout frame. The size of the placed marginalia item is likely to be moderately
adjusted during the Insert Graphics into Layout Frames process, and therefore
placement of marginalia layout frames should approximate the desired location of the
marginalia item. Marginalia items can be scaled after placement, but they cannot be
rotated.
To insert layout frames:
1. Select Insert > Layout Frames.
2. Select the appropriate marginalia check boxes.
15-43
Note: When the dialog box is displayed, you can exit the command by pressing ESC.
When you are in the process of drawing layout frames after the dialog box has been
dismissed, you can exit the command by pressing the right mouse button twice. Also,
at the prompt for the second point of a layout frame, you can undo the selected first
point and move back to the prompt for the first point by pressing the right mouse
button.
3. Click OK.
You are prompted to place the first point to indicate the extent of the map.
OR
Click Cancel to exit the command.
4. Move the cursor to the location where you want to place the map layout frame (a
dynamic rectangle appears anchored at the placed point); place the second point
diagonal to the first to place a layout frame for the map; then click the left mouse
button.
If you selected marginalia in Step 2, you are prompted to place points to indicate the
extent of each marginalia item selected.
5. Repeat the procedure of Step 4 until you have placed all the marginalia layout frames.
15-44
The newly inserted layout frame group is left in the select set.
Inserting Graphics into Layout Frames

Insert Graphics into Layout Frames automatically places map graphics into existing
layout frames defined with the Insert Layout Frames command into the layout sheet.
With this command, you select the appropriate layout frame group or map layout frame
before starting the command. The layout frames are intelligent; they know what type of
map graphic item should be placed in each layout frame.
When you start the command, the Insert Graphics into Layout Frames dialog box
indicates which marginalia items are included in the layout frame group. The checked
items were selected and placed with Insert Layout Frames, and the unchecked items did
not have the marginalia layout frames placed, or they have since been deleted. This dialog
box also lets you define the map definition consisting of the originating map window, the
geographic extent, the plot scale, and the static/dynamic status, as previously discussed.
See the “Map Specifications” section earlier in this chapter.
The command places new 5.2 marginalia controls for the legend as well as north arrow and
scale bar, honoring any Save as Default preferences. If the legend preferences indicate
multiple columns, the entries are distributed evenly across the columns.
You can also use this command on existing populated layout frames to replace existing
map graphics. Populated marginalia frames are updated as follows:
Update Condition What Is Updated

When the source map window name was A default legend control is placed. The
changed on the command dialog box. upper-left corner of the legend frame is
The command only updates 5.2 legend maintained.
frames; those placed before the 5.2 release
are not processed.
15-45
A change in the center point or rotation of Only north arrow’s angle is updated. The
the map. The command update north size, position, symbol file etc. will not be
arrow frames only if the north arrow changed.
azimuth was defined by the map center. If
it was user-defined, it is not processed.
When there is a change in the map scale. Only the scale of the scale bar is updated.
Fill colors, font, caption, units, and so forth
are not changed. The center point of the
scale bar frame is maintained.
Note: Map graphics layout frames inserted into the layout window with the Insert Layout
Frames command are composed of layout frames for a map and its associated marginalia.
Before these layout frames are populated, they are stored in the layout window as a group
element type, even if the map graphics consist of only a map with no marginalia. After
using the Insert Graphics into Layout Frames command to populate the layout frames,
the group element type is removed. When selecting a group element, you will notice that
the full set of handles is not available. When trying to edit or to manipulate any of the
individual items (empty layout frames) in the group, you must first use PickQuick to select
an item to process. This enables you to select the item to edit, upon which all of the
handles appear and can then be used to adjust or to crop the map layout frame. To delete a
scale bar, north arrow, or legend layout frame within a group, it is best to select the layout
frame using PickQuick. Ungrouping the frames lets you select individual layout frames
for deletion; however, ungrouping the frames breaks the group intelligence for the
remaining frames. In the layout window, the PickQuick dialog box displays elements
based on Z order, that is, objects on top are displayed before objects below regardless of
the top-down/bottom-up modifier.
See “To select a hidden or overlapped feature” in the “Working with Features” chapter
for information on using PickQuick.
To insert graphics into layout frames:

1. Verify that there is an active map window for the insert, that the marginalia properties
have been properly defined, and that the layout frames have been placed using the
Insert Layout Frames command.
2. Select the appropriate layout frame group or map layout frame in the layout window
into which you want to insert the new map graphics.
15-46
3. Select Insert Graphics into Layout Frames.
4. Select the appropriate map window from the Map window drop-down list.
5. Select the appropriate Geographic extent method, and select and/or type any
corresponding required parameters.
6. Select the appropriate Plot scale method; then type the corresponding plot scale value.
7. Select the Static or Dynamic mode.
8. Click OK.
OR
Click Cancel to exit the command.
Note: You should not place a map frame that exceeds the layout sheet size. If it
exceeds the layout sheet size, you should reduce the plot scale and/or geographic
extent or increase the paper size through Layout Window Page Setup.
15-47
9. If the geographic extent method selected is Map Window, Spatial Filter, Geographic
Frame, or Projected Frame, there is no need for interaction in the map window.
OR
If the geographic extent method selected is not one of these four, continue with this
step as follows, according to the selected method:
– For the Rectangle method, identify the first point of the rectangle in the map
window, move the cursor and attached rubber-banding rectangle to the opposing
diagonal corner, and then place a second point to define the extent of the rectangle.
– For the Polygon method, identify the first point of the polygon in the map window,
move the cursor and attached rubber-banding polygon to another location, and then
select a second point. Continue selecting points until the polygon has been defined;
then double click to end.
– For the Existing Shape method, select a shape in the map window to identify the
extent that you want, and then identify the appropriate snap point.
When you are in the process of defining the geographic extent in the map window after
the dialog box has been dismissed, you can return the dialog box by pressing the right
mouse button twice. At the prompt for the second point of a layout frame, you can
also undo the selected first point and move back to the prompt for the first point by
pressing the right mouse button.
The map and any selected marginalia items are automatically placed into their
appropriate layout frames. The newly inserted map is left in the select set.
display of the map and marginalia after they have been placed in the layout sheet.
Workflows for Placing Map Graphics Without Using

Layout Frames
Inserting Maps into Layout Sheets
Insert Map places a single map into a layout sheet without using previously placed layout
frames. With this command, you specify the map definition and then identify the location
for placement of the map. The map definition consists of the originating map window, the
geographic extent, the plot scale, and the static/dynamic status. The size of the map is
calculated automatically based on the geographic extent and plot scale settings. As you
drag your cursor across the layout sheet, an empty rectangle appears to identify the
physical extent of the map being placed. After the map has been inserted, it remains in the
15-48
select set, enabling you to move on to additional insert operations, such as the placement of
marginalia or grids
display of the map after the map has been placed in the layout sheet.
To insert a map into a layout sheet:

1. Verify that there is an active map window with map graphics for the insert.
2. Select Insert > Map.
3. Select the appropriate map window from the Map window drop-down list.
4. Select the appropriate Geographic extent method, and select and/or type any
corresponding required parameters.
5. Type the appropriate plot scale value in the User-defined field.
6. Select the Static or Dynamic mode.
7. Click OK.
OR
Click Close to exit the command.
Note: You should not place a map frame that exceeds the layout sheet size. If it
exceeds the layout sheet size, you should reduce the plot scale and/or geographic
extent or increase the paper size through Layout Window Page Setup.
8. If the geographic extent method selected is Map Window, Spatial Filter, Geographic
Frame, or Projected Frame, go to Step 9 because there is no need for interaction in
the map window with these methods.
15-49
OR
If the geographic extent method selected is not one of these four, continue with the
steps as follows, according to the selected method:
– For the Rectangle method, identify the first point of the rectangle in the map
window, move the cursor and attached rubber-banding rectangle to the opposing
diagonal corner, and then place a second point to define the extent of the rectangle.
– For the Polygon method, identify the first point of the polygon in the map window,
move the cursor and attached rubber-banding polygon to another location, and then
select a second point. Continue selecting points until you have defined the
polygon; then double click to end.
– For the Paper Size method, move the cursor and attached fixed rectangle in the
map window to the desired location; then place a point to identify the origin of the
extent.
– For the Existing Shape method, select a shape in the map window to identify the
extent that you want; then identify the appropriate snap point.
You are prompted to place the origin of the map in the layout window.
When you are in the process of defining the geographic extent in the map window after
the dialog box has been dismissed, you can return to the dialog box by pressing the
right mouse button. When digitizing a rectangle or polygon in the map window, you
can undo the previously placed point by pressing the right mouse button.
9. Move the cursor and attached rectangle to the location where you want to place the
map; then click the left mouse button.
15-50
The rectangle defines the maximum extent of the map frame before clipping occurs.
After the map has been placed, it is populated with the graphics of the map, and
clipping is performed if necessary. The map is left in the select set.
Inserting Marginalia into Layout Sheets

You can insert the marginalia items (legend, north arrow, and scale bar) into a layout sheet
that is associated with a previously placed map through the following commands: Insert
Legend, Insert North Arrow, and Insert Scale Bar. The marginalia parameters are
obtained from their respective commands. You can delete marginalia items with the layout
window Delete command.
To insert any marginalia item, there must be a single populated map graphic Group in the
select set (from GeoMedia 4.0), or there must be a populated map frame in the select set
(from GeoMedia 5.0 and above). In the latter scenario, you cannot use these commands by
selecting the associated marginalia of a map.
Inserting Layout Legends

Insert Legend lets you insert a map legend from the map window into a layout sheet by
using the legend of the map window referred to in the selected map frame. When you
select this command, it displays the Insert Legend dialog box, through which you can
insert the layout legend as is or review and customize it. When satisfied with the legend
appearance, you place it by a single point. The legend is associated with the map, which
allows for automatic updates of the layout legend when changes are made to the map
content (such as the style of the legend entries). You can also create multiple legends for a
single map frame. Furthermore, you can store the default settings for all the properties of a
legend; and each time a legend is placed, the default settings are used regardless of the
current map window settings.
See the “Working with Map Windows” chapter for information on legends and using them
in the map window.
15-51
The legend treeview on the Insert Legend dialog box lists all the displayed features from
the legend in the map window, except raster. Features not displayed in the treeview can be
accessed on the Add Legend Entries dialog box. The treeview displays the number of
columns, in which each column entry is displayed, the order of the features within that
column, and a thumbnail of the legend key.
By default, the treeview is expanded, displaying one column with the entries in the order
they appear in the map window legend. The hidden attribute is set according to the
properties of the map window legend (show legend entry, collapse legend entry, and
display by scale). By default, if an entry is hidden in the originating map window, it is not
displayed on the treeview. If an entry is displayed in the treeview and its corresponding
feature has its display turned off in the legend of the originating map window legend, the
entry remains in the treeview. The treeview does not support multi-select.
The top node in the treeview contains the legend title. The next level in the treeview
denotes columns with the text Column X (Y entries), where X is the column number, and
Y is the number of entries in that column. The third level represents the legend entries and
contains the key of the legend entries followed by the text of the feature name. In the case
of range headings, the key is blank.
Customizing the Layout Legend

The default layout legend properties are taken from the map window legend. You can
customize these properties, which include multi-column legends, legend title and
properties, prioritization of legend entry order, control of sizes and spacing, selection from
multiple styles for legend keys, and control of thematic legend entries.
The flexibility of this command lets you customize the layout legend through various
workflows using dialog boxes, right mouse menus, and drag-and-drop functionality. From
the Insert Legend dialog box you can display the resizable Legend Properties dialog box
by selecting the Legend name in the treeview and then either clicking Properties or
selecting Prosperities from the right mouse menu. This dialog box and those displayed
from it let you view and modify layout legend properties.
15-52
You can customize the layout legend treeview items through their respective right mouse
menus as follows:
Item Command Lets You
Legend Properties Customize the legend properties on the Legend
Rename Legend Type a new legend title.
Title
Add Column Add an empty column below the legend title.
Distribute Entries Distribute all displayed legend entries evenly across
Evenly available columns.
Column Remove Column Remove a column, transferring its contents to the
previous column. (Press DELETE as a shortcut.)
Add Entries Add legend entries on the Add Legend Entries
dialog box.
Sort Entries Perform an ascending alphabetic sort of all legend
Alphabetically entries in the selected column.
Sort Entries by Perform a geometric sort in the following order: text,
Geometry point, line, compound, area.
Entries Properties Customize the entry properties on the corresponding
Legend Entry Properties dialog box.
Rename Entry Type a new feature name.
15-53
Add Entries Add legend entries on the Add Layout Legend

Entries dialog box.
Remove Entry Remove the selected entry from the treeview,
transferring it to the Add Legend Entries dialog
box. (Press DELETE as a shortcut.)
Selecting Properties on the legend entry right mouse menu displays a Legend Entry
Properties dialog box, which lets you change the corresponding entry properties. The
available parameters of this dialog box change with the entry type, which can be text,
point, line, area, compound point, compound line, compound area, or thematic. The
following example is for area:
See the corresponding GeoMedia Help topics for complete information on these dialog
boxes.
In addition to the various dialog boxes and right mouse menus, you can customize the
legend treeview by drag-and-drop. Nodes in the treeview that are available to drag-and-
drop include legend columns and legend entries. You can move or copy them within a
column or across columns, but you cannot move or copy the legend title node. You can
also drag-and-drop nodes onto another node. The selected node is then moved below the
destination node it was dropped upon. If you press CTRL when dragging the node, a copy
of the selected node is dropped below the destination node.
If you drop a column node onto the legend title node, the selected node and all its entries
are dropped below the legend title node, becoming the first column in the treeview. If you
drop a column node onto another column node, the selected node and all its entries are
dropped below the destination column. If you drop a column node onto an entry node, the
selected node and all its entries are dropped below the column where the destination entry
node resides. As column nodes are shifted within the treeview, the software automatically
renumbers the columns to reflect their new positions within the treeview.
display of the legend after it has been placed in the layout sheet.
See the “Modifying Legends” section in this chapter for more information.
15-54
Looking at Legend Examples

The following example shows the minimum column width based on the sum of the longest
key width, the longest name width, and the width of the spacing between the two. The
minimum column width defines the width of the column before the wrapping of the names
occurs, as seen in the example on the left. The example on the right shows the column
spacing between the two columns.
The following example shows the columns depicting the name position. The column on
the left has the names to the right of the key; the column on the right has the names to the
left of the key.
The following example shows the row spacing depicted between two rows, where the row
height is based on the larger of either the legend graphic key or the entry name.
15-55
The example on the left shows the row spacing based on the Maintain uniform row
height check box on the Legend Properties dialog box. The legend on the left does not
have this check box checked, resulting in variable spacing between the names because the
heights of the individual rows vary. The legend on the right has the check box checked,
resulting in even spacing between the names. The graphic on the right shows the available
shapes for area and linear features.
To insert a legend:
1. Select the map frame in the layout window.
2. Select Insert > Legend.
15-56
Note: You can resize this dialog box, and you can use the Up/Down arrows to move
entries.
3. To review and customize the overall legend properties, select the legend title node, and
then click Properties.
4. Set the legend properties appropriately on the Legend Properties dialog box.
Note: You can also use right mouse menus and the Legend Entry Properties dialog
boxes to customize individual legend entries.
5. To add a legend entry, click Add.

If the legend title node is selected, an empty column is added below this node,
becoming the first column in the treeview.
If a column or entry node is selected, the Add Legend Entries dialog box is displayed.
6. Select the appropriate Available entries.
Note: The names and the order in which the features are listed on the Available
Legend Entries dialog box are based on the original map window. Check the Sort
alphabetically check box to sort the entries. Thematic headings are sorted such that
the thematic heading is considered in the sort, and its corresponding entries remain
grouped and indented just below the heading within the sorted list. Thematic entries
are not sorted within the group and always maintain their original order.
If a column node was selected, upon returning to the treeview, any entries selected are
added below the column node, becoming the first entry(s) within the column.
15-57
If an entry node was selected, upon returning to the treeview, any entries selected are
added below the currently selected entry.
7. To save the defined legend as the default, click Save as Default.
8. Click OK on the Insert Legend dialog box.
The dialog is dismissed, and a rectangle that represents the size of the legend is placed
in dynamics.
9. Click on the layout sheet to define the location for the legend.
The lower-left corner of the legend is placed where you clicked.
Inserting North Arrows

Insert North Arrow lets you insert a north arrow into the layout sheet, based on the map
selected before starting the command. When you select this command, it displays the
Insert North Arrow dialog box, through which you can insert the default north arrow,
browse to select another, and/or customize its properties. The product delivers .wmf files
for north arrows and compass roses in the \GeoMedia\Program folder, but you can also
select another north arrow or compass rose if you have one. When satisfied with the north
arrow appearance, you place it by a single point. The north arrow is associated with the
map. You can also insert multiple north arrows for a single map frame.
See the “Displaying the North Arrow” section in the “Working with Map Windows”
chapter for information on using north arrows in the map window.
The North Arrow Properties dialog box lets you change the symbol file used, its size, and
its azimuth of the north arrow (drawn according to the north azimuth of the center of the
associated map or the user-defined direction in degrees). Furthermore, you can store the
default settings for all the properties of a north arrow; and each time a north arrow is
placed, the default settings are used regardless of the current map window settings. As you
make changes in the symbol and north azimuth, they are displayed in the Preview area.
This display is always at a fixed size; it does not reflect changes made in the Size field of
the North Arrow Properties dialog box.
15-58
Note: In the layout window, the unit for the Size is defined by the Style field on the
Layout tab (Tools > Options).
display of the north arrow after it has been placed in the layout sheet.
See the “Modifying North Arrows” section in this chapter for more information.
To insert a north arrow:

2. Select Insert > North Arrow.
3. To change the North arrow file, browse to select a different one.
Note: To see graphics of all the north arrows and compass roses, open the
NorthArrows.pdf file, which is in the \GeoMedia\Program folder.
15-59
4. To review and customize the north arrow properties, click Properties.

5. Set the north arrow properties appropriately on the North Arrow Properties dialog
box.
6. To save the defined north arrow as the default, click Save as Default.
7. Click OK to close the North Arrow Properties dialog box.
8. Click OK on the Insert North Arrow dialog box to insert the north arrow.
The dialog is dismissed, and a rectangle that represents the size of the north arrow is
placed in dynamics.
9. Click on the layout sheet to define the location for the north arrow.
The lower-left corner of the north arrow is placed where you clicked.
Inserting Scale Bars

Insert Scale Bar lets you insert a scale bar into the layout sheet, based on the map selected
before starting the command. When you select this command, it displays the Insert Scale
Bar dialog box, through which you can insert the default scale bar or define a new one and
customize its properties. When satisfied with the scale bar appearance, you place it by a
single point. The scale bar is associated with the map. You can also insert multiple scale
bars for a single map frame.
See the “Displaying the Scale Bar” section in the “Working with Map Windows” chapter
for information on using scale bars in the map window and examples of scale bars you can
define.
You can change the properties of the scale bar through the three tabs of the Scale Bar
Properties dialog box. Furthermore, you can store the default settings for all the
properties of a scale bar, and each time a scale bar is placed, the default settings are used
regardless of the current map window settings.
The Style tab lets you define the display characteristics of the scale bar, including the type,
color, and size.
15-60

position, and font characters of the unit labels on this tab. The Labels tab lets you specify
the appearance of the scale bar numbers and caption and where they are to be displayed.
Note: For scale bars in the layout window, the unit for the Size on the Style tab and Tick
length on the Labels tab is defined by the Style field on the Layout tab (Tools >
Options).
15-61
As you make changes in the scale bar, they are displayed in the Preview area on the Insert
Scale Bar dialog box.
display of the scale bar after it has been placed in the layout sheet.
See the “Modifying Scale Bars” section in this chapter for more information.
To insert a scale bar:

2. Select Insert > Scale Bar.
3. Select the appropriate Type from the drop-down list.

4. To review and customize the scale bar properties, click Properties.
5. Set the scale bar properties appropriately on the three tabs of the Scale Bar Properties
dialog box.
6. To save the defined scale bar as the default, click Save as Default.
7. Click OK to close the Scale Bar Properties dialog box.
8. Define the appropriate Unit and Unit label on the Insert Scale Bar dialog box.
9. Click OK to insert the scale bar.
The dialog is dismissed, and a rectangle that represents the size of the scale bar is
placed in dynamics.
10. Click on the layout sheet to define the location for the scale bar.
The lower-left corner of the scale bar is placed where you clicked.
Updating Map Graphics in Layout Sheets

Update Map Graphics lets you manually update static maps in the layout window,
regenerating the raster snapshot based on the current settings of the originating map
window. To use this command, the originating map window must not have been deleted or
15-62
renamed. In the update, the existing map and legend are replaced with new graphics based
on the settings currently defined in the originating map window. However, old-style
legends (before GeoMedia 5.2) are not updated in any way; you must delete and reinsert
them. Furthermore, the north arrow and the scale bar are not updated; you must use their
respective Properties commands to update them. To use Update Map Graphics, you
select a populated map layout frame (or old-style group of frames, that is, map and
marginalia) and then run the command.
Any changes to the content of the originating map window (adding feature classes or
queries, changing styles of legend entries, and so forth) are automatically updated in the
layout window map unless one of the following conditions exists:
• The Insert Map or Insert Graphics into Layout Frames command was used to insert
map graphics into a layout frame in the layout window using the Static mode, not the
Dynamic mode.
• The Map Properties command was used to change a populated map frame from
Dynamic to Static.
When the update is performed, the size of the layout frame always remains the same. If
you have scaled, cropped, or expanded the map layout frame before the update using the
Scale command (from the Editing toolbar or menu) or the file handles of the map object,
the update honors the current layout frame settings. If you have rotated the map window
after the initial placement and before the update, the update ignores the map window
rotation, only refreshing the contents of the map frame. The update result never alters the
current map layout frame settings (size, rotation, and so forth). The placement of the
updated map is such that the center of the map being updated within the layout frame is
coincident with the center of the layout frame that was originally placed for all extraction
methods.
In terms of the map definition specified in the Insert Map or Insert Graphics into
Layout Frames commands, the following conditions are applied during the update:
• The originating map window selection is maintained.
• The size, rotation, and origin of the current map frame are maintained regardless of the
extraction method used during the original map placement.
• The originating plot scale (User-defined or Fit to Frame) setting is maintained.
• After the map graphics are updated, any associated layout window marginalia are
synchronized with the map graphics using the same rules that are followed when
dynamic maps are updated automatically.
To update map graphics:

1. Verify the following conditions:
− A selected, populated map frame or selected, populated frame group with the map
graphics to be updated exists in the layout sheet.
15-63
− The map window that was used for the original placement of the static map exists.
2. Select the static map frame.
3. Select Layout > Update Map Graphics to update the map graphics in the selected
map frame and to exit the command.
Modifying Map Graphics in Layout Sheets

Modifying Maps
Maps placed with the Insert Graphics into Layout Frames or Insert Map commands can
be modified after their initial placement. The types of modifications that can be made vary
based on several factors, such as the static versus dynamic mode and the geographic extent
method used during placement. Maps placed in dynamic mode can be changed to static
mode using the Map Properties command. All maps can be scaled regardless of the
geographic extent method used during placement, uniformly scaling the map frame and its
contents using the corner handles of the selected map frame or by typing a new scale on the
Map Properties dialog box. If the geographic extent of the map is rectangular (Map
Window, Rectangle, Paper Size), the map frame can be enlarged or reduced without
affecting the map scale using the side handles of the selected map frame or by typing new
height and width values on the Map Properties dialog box. In addition, the map contents
can be scaled (zoomed in or out) by using the Map Zoom In or Map Zoom Out command
and can be moved within the map frame without affecting the map frame extent by using
the Map Pan command.
Changing the Status from Dynamic to Static

Maps that were originally placed in dynamic mode can be modified to static node using the
Geometry and Content tab of the Map Properties command. Before starting this
command, you may have placed the map graphics as either static or dynamic, which
dictates the properties you can edit. For map graphics placed as dynamic, you can switch
the mode from dynamic to static. Map graphics placed as static cannot be switched from
static to dynamic mode. This limitation on static map graphics is due to potential problems
in maintaining the association between the map graphics in the layout window and the
originating map graphics in the map window. Difficulties may occur when modifications
are made in the originating map window after the static map graphics have been placed.
Problematic modifications include the removal of the originating map window and changes
in warehouse connections.
To change from dynamic to static mode:

1. Select the appropriate layout frame group.
2. Select Properties from the right mouse menu.
15-64
3. Select the Static mode from the Geometry and Content tab; then click OK.
The map becomes static and cannot be made dynamic again, and the contents of the
Mode frame are disabled. The ability to have the height, width, and scale operate
independently is also disabled.
Scaling Map Extents and Enlarging or Reducing Map Frames

Resizing the map frame involves either scaling the map frame extent and its contents or
enlarging or reducing the size of the selected map frame. You can either do this by
selecting the map frame, which displays the file handles, and then by dragging the cursor
over the file handles to resize the map frame, or you can modify the appropriate properties
on the Map Properties dialog box.
You can scale map frames placed with all geographic extent methods, but you can only
enlarge or reduce map frames placed with the Map Window, Rectangle, and Paper Size
geographic extent methods. Map frame scaling maintains the geographic extent, changing
the map scale. Map frame enlargement or reduction does not impact the map scale, but
changes the visible geographic extent.
Once you select the map frame, the handles appear as solid black squares. Boundary types
(Existing Shape, Polygon, Spatial Filter, Geographic Frame, and Projected Frame) will
only have file handles on the corners, whereas rectangle types (Map Window, Paper Size,
and Rectangle) will have them on the corners and on the sides.
15-65
Boundary type Rectangle type

When you pass the cursor over the handles, the cursor changes from the Select Tool arrow
to the appropriate glyph – a line with arrowheads at both ends for corner file handles to
scale and an open box for side file handles to enlarge or to reduce.
Corner file handle Side file handle

As you click the cursor and drag the mouse, the map frame is resized accordingly.
Map frame scale enlargement has no limits. However, map frame scale reduction is limited
such that the corner being reduced can never touch or pass its opposing corner file handle,
leaving a minimum width/height map frame.
Enlarging or reducing operations are designed to fine tune the geographic extent of the
map. You can increase the size of the map frame on all sides by 20% in each direction.
Map frame size reduction is limited such that the side being reduced can never touch or
pass the file hand of its opposing side, leaving a minimum width/height map frame.
To scale map frames:

1. Select a valid map frame (all geographic extent methods).
All file handles appear as solid black squares.
2. Pass the cursor over any one of the four corner file handles.
The cursor changes from the Select Tool arrow to a line with arrowheads on both
ends.
3. While the cursor is changed, click and drag in the direction you want to rescale the
map, making the map frame larger or smaller.
4. Release to complete the scaling definition.
The map is scaled accordingly, and a new scale bar is generated to reflect the new
map scale.
15-66
OR
1. Select the appropriate map frame group.
3. Uncheck the Modify width, height, and map scale independently check box.
4. Type the appropriate map scale.
5. Click OK.
The map is scaled accordingly, and a new scale bar is generated to reflect the new
map scale.
To enlarge or reduce map frames:

1. Select a valid map frame (Map Window, Rectangle, or Paper Size geographic extent
method).
All file handles appear as solid black squares.
2. Pass the cursor over any one of the four side file handles.
The cursor changes from the Select Tool arrow to an open box.
3. While the cursor is changed, click and drag in the direction you want to resize the map,
making the map frame larger or smaller.
4. Release to complete the resizing definition.
The map is resized accordingly on the side selected.
OR
15-67
3. Check the Modify width, height, and map scale independently check box.
4. Type the appropriate height or width.
5. Click OK.
The map is resized accordingly, maintaining the lower-left origin and map scale.
Zooming In/Out and Panning Maps within Map Frames

Four map frame viewing commands let you zoom and pan on the contents of the map
frame without changing the view settings of the layout sheet within the layout window.
You can also zoom the contents of the map frame using the Map Properties command.
Thus, you can fine-tune the map after it has been placed in the layout sheet. These
commands are the following:
• Map Zoom In
• Map Zoom Out
• Map Zoom Previous
• Map Pan
These command function in the same way other zoom and pan commands do, except that
they only apply to the contents of the selected map frame. This means that if you fit the
layout sheet within the layout window, you can zoom or pan within the map frame, altering
the scale or position of map frame’s contents, while the layout sheet remains fit within the
layout window. Once a map frame has been selected, you can access these commands
from the layout toolbar or from the right mouse menu. You can only zoom and pan on the
map frames placed with rectangular (Map Window, Rectangle, and Paper Size) geographic
extent methods.
The Map Zoom In, the Map Zoom Out and the Map Zoom Previous commands have an
effect on the scale bar if one is present when the commands are selected. If you perform a
Map Zoom In, Map Zoom Out, or a Map Zoom Previous, the scale bar is re-generated
to conform to the new map scale.
Pan has two modes, dynamic and fast, which are set through the When panning map
windows options on the Map Display tab of the Options dialog box (Tools > Options).
While the Pan command is active, you can switch between dynamic and fast panning by
changing the selected option.
The Use dynamic pan option means that all the graphics in the map window move
continuously in unison with the mouse cursor when panning is performed as you press and
hold the left mouse button.
The Fast pan option means that the graphics in the map window remain fixed while
panning is performed, thus limiting the number of map window redraw operations.
15-68
To zoom in/out or pan maps within map frames:

1. Select an eligible map frame (Map Window, Rectangle, or Paper Size geographic
extent method).
2. Select Map Zoom In, Map Zoom Out, Map Zoom Previous, or Map Pan from the
Layout toolbar or right mouse menu.
3. Zoom or pan as necessary.
4. Press the right mouse button to exit the command.
The map is redrawn according to your actions.
OR
3. Check the Modify width, height, and map scale independently check box.
4. Type the appropriate map scale.
5. Click OK.
The map is scaled accordingly within the extent of the map frame, and a new scale bar
is generated to reflect the new map scale.
Modifying Map Properties

Layout Map Properties lets you review and modify the position, size, scale, rotation, and
boundary style of a selected map in the layout window, and, as described earlier, change
the static/dynamic mode. You start this command by selecting the map layout frame and
then Properties from the right mouse menu. You can review and modify these map
properties through the two tabs on the dialog box of this command.
The Geometry and Content tab lets you modify information about the map and its
position, size, and scale in the map in the layout window.
15-69
As previously discussed there are eight different ways (geographic extent) of selecting map
information for display in the layout window through the Insert Map and Insert Graphics
into Layout Frames commands. Five of these methods (Polygon, Existing Shape, Spatial
Filter, Geographic Frame, and Projected Frame) have distinct boundaries, so a relationship
exists between the height, width, and map scale. The ratio of height to width always
remains the same, so that a change to one automatically changes the other. The
relationship between size (height and width) and map scale is inverse, increasing the width
decreases the scale. Changing the height or width automatically changes the scale, and
changing the scale changes the height and width.
See the “Inserting Maps into Layout Sheets” section earlier in this chapter.
The three remaining map selection methods (Map Window, Paper Size, and Rectangle) can
be sized and scaled like the others (default behavior). But, because the boundary is not
fixed, the height, width, and scale can modified independently of each other. For these
cases, you use the Modify width, height, and map scale independently check box.
For the Map Window, Paper Size, and Rectangle selection methods, the default behavior
preserves any crops that you make, while the independent behavior causes the map to be
resampled and the crops to be reset to 20%. In all cases, the position of the lower-left
corner of the map frame on the layout sheet can be moved precisely by typing the X and Y
coordinates in paper units. The Mode frame lets you change the status of the map from
dynamic to static; however, once a map becomes static, it cannot be made dynamic again,
and the contents of this frame are disabled. Changing the mode to static also disables the
ability to have the height, width, and scale operate independently.
The General tab lets you change the layer on which the map is displayed and controls the
display of the boundary around the map, including color, width, and style.
15-70
The Rotation tab lets you rotate the map. The method used for the map placement using
the Insert Map command or the Insert Graphics into Layout Frames command
determines the results of the map rotation. Maps are placed with either a Boundary or
Rectangular frame type. For those methods that produce a frame that is a Boundary type
(Existing Shape, Polygon, Spatial Filter, Geographic Frame, and Projected Frame), the map
rotation includes the map frame and its contents. For the remaining methods, that is, those
that produce a frame that is a Rectangular type (Map Window, Rectangle, and Paper Size),
the map frame remains fixed, staying orthogonal to the layout sheet, and contents of the
map frame are rotated.
In the examples above, the map was placed using the Existing Shape method, a Boundary
frame type. The map on the left depicts the original placement, a rotation of 0 degrees.
The map on the right depicts the results of a 15-degree rotation. The Boundary map frame
and all of its contents have been rotated 15 degrees.
15-71
In the examples above, the map was placed using the Map Window method, a Rectangular
frame type. The map on the left depicts the original placement, a rotation of 0 degrees.
The map on the right depicts the results of a 15-degree rotation. The Rectangular map
frame has remained fixed, while its contents have been rotated 15 degrees.
You can type a rotation angle or select a directional button to display a calculated angle so
that north on the map is rotated to the top, bottom, left, or right of the sheet. These
directional buttons provide a quick and easy method for orienting North based on paper
space independent of the workspace’s geographic or projected space, which generally leads
to improved layout and design.
• Map frames must be in dynamic mode; you cannot rotate static maps.
• Rotation angles are in degrees.
• Rotation point is the center of the map frame.
Rotation is measured counter clockwise from the x-axis.
Upon clicking OK, the map is positioned at the correct coordinates on the sheet, the map
size and scale are set appropriately, the boundary is displayed in the correct color, width,
and style (if the boundary is to be displayed), the map is rotated, and the map and boundary
are placed on the correct layer.
Modifying Legends
The Layout Legend Properties command lets you view and modify information about a
legend in the layout window, including the position, number of columns, title, font, key
styles, layer, and boundary style of the legend frame. You start this command by selecting
the legend frame and then selecting Properties from the right mouse menu. You can
review and modify these legend properties through the two tabs on the dialog box of this
command.
The Legend tab lets you control what is displayed on the legend and how it is presented,
such as the title, number of columns, fonts, key styles, and so forth. This tab functions the
same as the Insert Legend dialog box. You can change these properties through the
Legend Properties dialog box; the Legend Entry Properties dialog boxes; the right
mouse menus of the legend title, columns, and entries in the treeview; and the drag-and-
drop functionality as previously described in the “customizing the legend” discussion.
See the “Inserting Layout Legends” section earlier in this chapter for complete
information on using the Legend tab.
15-72
The General tab lets you change the layer on which the legend is displayed and controls
the display of the boundary around the legend, including color, width, and style. This tab
also lets you position the lower-left corner of the layout frame geometry in the layout
window by typing the X and Y coordinates in paper units.
Upon clicking OK, the updated legend is positioned at the specified origin, the legend size
is calculated appropriately based upon the parameters entered, the boundary is displayed
with the correct color, width, and style (if the boundary is to be displayed), and the legend
and boundary are placed on the correct layer.
Converting Layout Legend to Raster Graphics

In case you need to perform additional modification of the layout legend beyond that
provided by the Layout Legend Properties command, you can use the Convert to
15-73
Graphics command. This command lets you convert the layout legend into a set of raster
legend keys and simple text strings, which you can edit as needed. These graphics are
generated at the same location and layer as the layout legend, and the existing layout
legend is removed. You perform this conversion by selecting the legend layout frame and
then Convert to Graphics from the right mouse menu. Once the legend has been
converted, it is no longer dynamic and associated with the originating map.
Modifying Map Window Legend Properties

The Map Window Legend Properties command lets you modify the contents of the map
display in a selected dynamic map frame within the layout window. You can thus directly
adjust certain legend properties without having to return to the map window of origin.
Specifically, you can add, move, and remove legend entries, and you can change the style,
display, and priority of the legend entries. You start this command by selecting the
dynamic map frame and then Map Window Legend Properties from the right mouse
menu or from the Layout toolbar.
This command lets you control the display of a dynamic map frame by manipulating the
contents of its associated map window legend. Each dynamic map frame is aware of its
associated map window, thus enabling you to access the originating map window legend
while working in the layout window. The map window legend contents are displayed in
the Map Window Legend Properties dialog box. Any changes made on the dialog box
are reflected in the referenced map window, the selected map frame in the layout window,
the associated layout window legend (if there is one), and any other map layout frames and
legends on any other sheets in the layout window that refer to the same map window.
See the “Changing Display Characteristics of Map Objects” in the “Working with Maps”
chapter and GeoMedia Help for information on using this dialog box.
15-74
Modifying North Arrows

You can change the properties of the north arrow through the two tabs of the North Arrow
Properties dialog box. Furthermore, you can store the default settings for all the
properties of a north arrow. You start this command by selecting the north arrow frame
and then Properties from the right mouse menu.
The Style tab lets you change the file used, its size, and azimuth of the north arrow (drawn
according to the north azimuth of the center of the associated map or the user-defined
direction in degrees).
Note: The unit for the Size is defined by the Style field on the Layout tab (Tools >
Options).
The General tab lets you change the layer on which the north arrow is displayed, define a
boundary to display around the north arrow, and set the lower-left origin position of the
north arrow in paper units. If an empty north arrow layout fame is selected as input, the
General tab is activated by default, and the Style tab is disabled.
15-75
Note: The X and Y units are defined by the Distance field on the Layout tab (Tools >
Options).
As you make changes in the symbol and north azimuth, they are displayed in the Preview
area on the Insert North Arrow dialog box. This display is always at a fixed size; it does
not reflect changes made in the Size field of the Style tab of the North Arrow Properties
dialog box.
Note: The unit for the Width is defined by the Style field on the Layout tab (Tools >
Options). The unit for the X and Y values is defined by the Distance field on the Layout
tab.
Modifying Scale Bars

You can change the properties of the scale bar through the four tabs of the Scale Bar
Properties dialog box. This dialog box is the same as the one accessed through the Insert
Scale Bar dialog box except that it has the additional General tab. Both dialog boxes let
you store the default settings for all the properties of a north arrow. You start this
command by selecting the scale bar frame and then Properties from the right mouse menu.
The Style tab lets you define the display characteristics of the scale bar, including the type,
color, and size. The General tab lets you change the layer on which the scale bar is
displayed, define a boundary display around the scale bar, and set the lower-left origin
position of the scale bar in paper units.
15-76

position, and font characters of the unit labels on this tab. The Labels tab lets you specify
the appearance of the scale bar numbers and caption and where they are displayed.
Note: The units for the Size on the Style tab and the Tick length on the Labels tab are
defined by the Style field on the Layout tab (Tools > Options).
As you make changes in the scale bar, they are displayed in the Preview area on the Insert
Scale Bar dialog box.
15-77
Changing Object Properties

You can change the properties of an object through the two tabs of the Object Properties
dialog box. You start this command by selecting the object frame and then Properties
from the right mouse menu.
The Geometry and Content tab lets you position the lower-left corner of the frame
geometry in the layout window and change the size or scale of the frame. For all frames,
there is a relationship between the height, width, and scale. Modifying any one of the
values automatically updates the other two. Any crops that you make to the frame are
retained when the size or scale changes. The General tab lets you change the layer on
which the object is displayed and define a boundary to display around the object.
See GeoMedia Help for complete information on using this dialog box.
Inserting Cartographic Grids

The Insert Cartographic Grid command lets you create and insert cartographic grids that
can be comprised of any combination of a neatline, grid lines, ticks and crosses, their
corresponding labels, and a border in the layout window. This command also lets you
specify unit settings for Geographic, Projection, and paper parameters, but it does not
support map graphics from Geocentric coordinate systems. To use this command, you
must first have placed map graphics in the active layout sheet with the Insert Map and
Insert Graphics into Layout Frames commands, that is, you must have a populated map
layout frame in the select set.
15-78
After placing the map, you use the tabs on the Insert Cartographic Grid dialog box to
define the grid components. The sequence of defining the grid components through the
tabs depends upon your specific workflow. This command allows you to experiment with
the grid definition and to get a visual result before proceeding. When you have finished
defining the grid, you can use the Preview button, which places a temporary grid and
keeps the dialog box displayed.
Preview lets you can check the results and adjust the grid definition and perform additional
previews before clicking OK to accept the final grid or Cancel to remove it. Both OK and
Cancel dismiss the dialog box. Consequently, you can refine your grid definition until you
have exactly what you need before you insert and save the grid.
Note: The grid placed by this command is static; it is not updated automatically in the
layout window when view rotations or coordinates transformation occur in the map
window. In such cases, the grid must be regenerated.
Defining a Neatline
The neatline is the set of lines drawn that typically correspond with the extent of the map
graphics. The neatline placed by the Insert Cartographic Grid command will always be
an orthogonal rectangle regardless of the extraction method used by the Insert Map or
Insert Graphics Into Layout Frames commands, with the exception of the Geographic
Frame extraction method. When the map has been placed using a Geographic Frame, the
15-79
neatline is drawn to approximate the clipped shape defined by the Geographic coordinates.
By default, all other non-orthogonal map extractions (Polygon, Existing Shape, and so
forth) will produce an orthogonal neatline based on the maximum horizontal and vertical
extents of the clipped map graphics. Optionally, you can type the neatline extents on the
dialog box, or you can interactively specify a neatline extent by selecting the Define
Extent option, upon which you are prompted to identify the limits of the appropriate
neatline on the layout sheet. In defining a neatline on the Neatline tab, you set the
parameters for the type and the extents, and the options for the neatline placement and
corner label placement.
Neatline Parameters
The neatline parameters consist of the neatline coordinate system, type, and the upper-left
corner and lower-right corner, which allow you to specify the neatline extents. You can
define these extents in Geographic or Projection coordinate space, with the default value
matching the current GeoWorkspace coordinate system setting. The neatline extents can
be smaller or larger than the current map graphic extent.
You can also define the neatline extents in a coordinate space other than the current
GeoWorkspace coordinate system setting (without modifying the GeoWorkspace
coordinate space) through the Neatline Coordinate System dialog box. If the current
GeoWorkspace coordinate system is Projection – Rectangular Grid, the Geographic option
is disabled, and you cannot access the Neatline Coordinate System dialog box.
15-80
You set the upper-left and lower-right corner values according to the selected coordinate
space. For Geographic, these are Longitude and Latitude; for Projection these are X
(Easting/Westing) and Y (Northing/Southing). The Coordinate Format settings and the
Unit and Precision settings for each is based on the settings defined on the Units and
Formats tab on the Neatline Coordinate System dialog box. The default coordinate
readouts are based on the current extents of the map graphic selected in the coordinate
space you defined.
Neatline Placement
You can place (or not place) a neatline by selecting or deselecting the check box. The
default is to place a neatline. With this option selected, you can define the neatline style
(color, weight, and type). The default style settings match the active settings for these
items in the layout window.
When placing neatlines on rotated map graphics, the neatline is only rotated on maps
placed with the Geographic Frame or the Projected Frame placement method. For all other
placement methods (Map Window, Polygon, Existing Shape, and so forth), the neatline
matches the MBR (minimum bounding rectangle) of the selected map graphics, which is
parallel to the sheet edges.
Corner Label Placement

Corner labels are placed on the corners of the neatline, and show the coordinate values at
the corners. You can place (or not place) corner labels by selecting or deselecting the
check box. With this option selected, you can define the corner label orientation, font, and
advanced label formatting. Corner labels are placed using a center justification so the label
itself is centered on each corner. To minimize overprinting of labels, whenever an edge
label overlaps a corner label, the edge label is not placed.
For corner label orientation, the available label placement options are as follows:
15-81
Parallel / Perpendicular (the default)—Parallel to the neatline on the top and bottom
edges and perpendicular to the neatline on the left and right edges. All labels read
horizontally.
Parallel—Parallel to the neatline on all edges. Labels on the left read bottom to top, labels
on the right read top to bottom, and labels on the top and bottom read left to right.
Perpendicular—Perpendicular to the neatline on all edges. Labels on the left and right
read left to right, and labels on the top and bottom read from bottom to top.
You can define the font through the standard Microsoft Font dialog box to set the font,
font style, font size, format, and script.
You can also define advanced label formatting options through the Advanced Neatline
Label Options dialog box. The style, format, and placement options on this dialog box
vary for Geographic labels and for Projection labels. The following example is for
Geographic labels:
Defining Grids
The grid (grid lines) is a set of horizontal and vertical lines that are placed over the map
within the neatline extents, never extending past the neatline. They are typically used for
locating specific points or quadrants on a map. In defining a grid on the Grid tab, you set
the parameters for the type and the intervals, and the options for the grid placement and
edge label placement.
15-82
Grid Parameters
The grid parameters consist of the grid coordinate system, grid type, grid intervals, and
skip intervals. You can define these parameters in Geographic or Projection coordinate
space, with the default value matching the current GeoWorkspace coordinate system
setting. There is a limit of 250 total grid lines, both horizontal and vertical, that can be
placed with the Insert Cartographic Grid command.
You can also define the grid parameters in a coordinate space other than the current
GeoWorkspace coordinate system setting (without modifying the GeoWorkspace
coordinate space) through the Grid Coordinate System dialog box. If the current
GeoWorkspace coordinate system is Projection – Rectangular Grid, the Geographic option
is disabled and you cannot access the Grid Coordinate System dialog box.
You define the grid and skip intervals in the unit specified on the Units and Formats tab
of the Grid Coordinate System dialog box for the particular grid coordinate space used to
generate the grid.
Grid intervals define the interval at which grid lines are placed. The intervals always
begin at 0,0. For Projection settings, this is the origin of the projected coordinate system.
For Geographic settings, this is the Greenwich Meridian and the Equator. The intervals
correspond to Longitude and Latitude for Geographic and X (Easting/Westing) and Y
(Northing/Southing) for Projection. The Coordinate Format settings and the Unit and
Precision settings for each is based on the settings defined on the Units and Formats tab
on the Grid Coordinate System dialog box.
15-83
Note: The default interval for gridlines for both Projection and Geographic coordinate
systems is set to reasonable values – producing roughly 10 gridlines at an appropriate
round interval.
Skip intervals define the interval at which grid lines will not be placed. The intervals
always begin at 0,0. For Projection settings, this is the origin of the projected coordinate
system. For Geographic settings, this is the Greenwich Meridian and the Equator. The
default value for Projection is 0, and the default value for Geographic is 00:00:00 d:m:s.
When 0 is defined for the skip interval, no grid line skipping occurs.
You can also define intervals in paper units for the Projection grid type. When you choose
this option, the grid and skip interval units and precision settings used on the dialog box
are obtained from the current settings defined for the Distance unit on the Layout tab of
the Options dialog box. During placement, the paper interval will be converted
automatically to the appropriate ground interval based on the current map scale.
Grid Placement
You can place (or not place) a grid by selecting or deselecting the check box. With this
option selected, you can define the grid style (color, weight, and type). The default is
dependent on the active setting for the neatline type defined on the Neatline tab. When the
neatline type is Projection, the default is to place a grid. When the neatline type is
Geographic, the default is to not place a grid. The default style setting matches the active
settings for these items in the layout window. Grid lines are rotated appropriately on
rotated map graphics.
Edge Label Placement

You can place (or not place) edge labels by selecting or deselecting the check box. With
this option selected, you can define the edge label orientation, font, and advanced label
formatting options.
The edge label placement default is dependent upon the active setting for the neatline type
defined on the Neatline tab. When the neatline type is Projection, the default is to place
edge labels. When the neatline type is Geographic, the default is to not place edge labels.
Corner labels are placed using a center justification so the label itself is centered on each
corner. To minimize overprinting of labels, whenever an edge label overlaps a corner
label, the edge label is not placed.
For edge label orientation, the available options for label placement are as follows:
horizontally.
15-84
You can define the font through the standard Microsoft Font dialog to set the font, font
style, font size, format, and script.
You can define advanced label formatting options through the Advanced Grid Label
Options dialog box. The style, format, and placement options on this dialog box vary for
Geographic labels and for Projection labels.
Defining Ticks and Crosses

Ticks are lines placed along the neatline at the intersections of the specified intervals and
the neatline. Crosses are lines placed within the neatline at the intersections of the
specified interval. Ticks and crosses are placed at constant intervals from each other and
are typically used for locating specific points on a map. In defining ticks and crosses on
the Ticks and Crosses tab, you set the parameters for the type and the intervals, and you
set the options for tick and cross placement and for edge label placement.
Tick and Cross Parameters

The tick and cross parameters consist of the tick and cross coordinate system, tick and
cross type, tick and cross intervals and of the skip intervals. You can define these
parameters in Geographic or Projection coordinate space, with the default value matching
the current GeoWorkspace coordinate system setting.
15-85
You can also define the tick and cross parameters in a coordinate space other than the
current GeoWorkspace coordinate system setting (without modifying the GeoWorkspace
coordinate space) through the Tick and Cross Coordinate System dialog box. If the
current GeoWorkspace coordinate system is Projection – Rectangular Grid, the Geographic
option is disabled and you cannot access the Tick and Cross Coordinate System dialog
box.
You define the tick and cross intervals and the skip intervals in the unit specified on the
Units and Formats tab of the Ticks and Crosses Coordinate System dialog box for the
particular ticks and crosses coordinate space used to generate the ticks and crosses.
Crosses are placed at all interval intersections within the neatline definition. Ticks are
placed at the interval intersections on the neatline.
Tick and cross intervals define the interval that ticks and crosses are placed. The intervals
always begin at 0,0. For Projection settings, this is the origin of the projected coordinate
system. For Geographic settings, this is the Greenwich Meridian and the Equator. The
intervals correspond to Longitude and Latitude for Geographic and X (Easting/Westing)
and Y (Northing/Southing) for Projection.
The Coordinate Format settings and the Unit and Precision settings for each is based on
the settings defined on the Units and Formats tab of the Ticks and Crosses Coordinate
System dialog box.
Note: The default interval for ticks and crosses for both Projection and Geographic
coordinate systems are set to reasonable values – producing roughly 10 gridlines at an
appropriate round interval.
Skip intervals define the interval at which ticks and crosses will not be placed. The
intervals always begin at 0,0. For Projection settings, this is the origin of the projected
coordinate system. For Geographic settings, this is the Greenwich Meridian and the
Equator. The default value for Projection is 0, and the default value for Geographic is
00:00:00 d:m:s. When 0 is defined for the skip interval, no tick and cross skipping occurs.
You can also define intervals in paper units for the Projection ticks and crosses type.
When you choose this option, the tick and cross interval and the skip interval units and
precision settings used on the dialog box are obtained from the current settings defined for
the Distance unit on the Layout tab of the Options dialog box. During placement, the
paper interval will be converted automatically to the appropriate ground interval based on
the current map scale.
Tick Placement
You can place (or not place) ticks by selecting or deselecting the check box. With this
option selected, you can define the tick style, length, and position. The default is
15-86
dependent on the active setting for the neatline type defined on the Neatline tab. When the
neatline type is Projection, the default is to not place ticks. When the neatline type is
Geographic, the default is to place ticks.
For the style, you can define the line color, weight, and type; the default setting matches
the active settings for these items in the layout window. For the length, the unit and
precision is based on the current settings defined for the Distance unit on the Layout tab
on the Options dialog box. For the position, you can set the tick placement to be either
inside the neatline (the default) or outside the neatline.
Cross Placement
You can place (or not place) crosses by selecting or deselecting the check box. With this
option selected, you can define the cross style and length. The default is dependent on the
active setting for the neatline type defined on the Neatline tab. When the neatline type is
Projection, the default is to not place crosses. When the neatline type is Geographic, the
default is to place crosses.
For the style, you can define the line color, weight, and type; the default setting matches
the active settings for these items in the layout window. For the length, the unit and
precision is based on the current units and precision settings defined for the Length
readout on the Layout tab on the Options dialog box.
Edge Label Placement

You can place (or not place) edge labels for ticks and cross by selecting or deselecting the
check box. With this option, you can define the edge label orientation, font, and advanced
formatting options.
The edge label placement default is dependent on the active setting for the neatline type
defined on the Neatline tab. When the neatline type is Projection, the default is to not
place edge labels. When the neatline type is Geographic, the default is to place edge
labels.
For edge label orientation, the available options for label placement are as follows:
horizontally.
You can define the font through the standard Microsoft Font dialog to set the font, font
style, font size, format, and script.
15-87
You can define advanced label formatting options through the Advanced Ticks and
Crosses Label Options dialog box. The style, format, and placement options on this
dialog box vary for Geographic labels and for Projection labels.
Defining a Border
The border is an orthogonal rectangle drawn around the exterior of the cartographic grid.
You can place (or not place) a border by selecting or deselecting the check box; the default
is to not place a border. In defining a border on the Border tab, you set distance
parameters to specify the distance from the neatline and to specify the border style.
The distance parameters from the neatline are top, bottom, left, and right margins. The
default values for these, calculated based on the largest label size and the tick length if the
ticks are placed outside the neatline, should ensure that the border does not overprint the
corner or edge labels (neatline, grid, ticks and crosses). The default units and precision are
based on the current settings defined for the Distance unit on the Layout tab on the
Options dialog box. For the style, you can define the line color, weight, and type; the
default style values match the active settings for these items in the layout window.
To define cartographic grids:

1. Insert the appropriate map into the layout sheet.
2. Select the populated map frame, and then select Insert > Cartographic Grid.
3. Define the appropriate parameters on the appropriate tabs.
4. Click Preview to display the grid; then click OK or Cancel.
OR
15-88
Click OK to accept the grid and to dismiss the dialog box.

OR
Click Cancel to remove the grid and to dismiss the dialog box.
To define a neatline:
1. Select the Neatline tab.
2. Optional: Click Neatline Coordinate System to define the neatline extents in a
coordinate space other than the current GeoWorkspace coordinate system setting.
3. Select the neatline type as Geographic or Projection to define the extents of the
neatline.
4. Optional: Type changes in the Upper left corner and Lower right corner fields.
5. Optional: Click Define Extent to interactively define the neatline extent in the layout
sheet.
6. Optional: Check the Place neatline check box; then specify the neatline Style
settings.
7. Optional: Check the Place corner labels check box; then select the Orientation from
the drop-down list.
8. Optional: Click Font to change the font values.
9. Optional: Click Advanced to set the advanced label formatting options.
To define a grid:
1. Select the Grid tab.
2. Optional: Click Grid Coordinate System to define the grid extents in a coordinate
space other than the current GeoWorkspace coordinate system setting.
3. Select the grid type as Geographic or Projection for defining the grid intervals.
4. Optional: Type changes in the Grid intervals fields.
5. Optional: Type changes in the Skip intervals fields.
6. Optional: Check the Define intervals in paper units check box; then specify the
Grid intervals and Skip intervals in paper units.
7. Optional: Check the Place grid check box; then specify the grid Style settings.
8. Optional: Check the Place edge labels check box; then specify the Orientation from
the drop-down list.
15-89
To define ticks and crosses:

1. Select the Ticks and Crosses tab.
2. Optional: Click Ticks and Crosses Coordinate System to define the ticks and
crosses in a coordinate space other than the current GeoWorkspace coordinate system
setting.
3. Select the Tick and crosses type as Geographic or Projection to define the ticks and
crosses intervals.
4. Optional: Type changes in the Tick and cross intervals fields.
5. Optional: Type changes in the Skip intervals fields.
6. Optional: Check the Define intervals in paper units check box; then specify the Tick
and cross intervals and Skip intervals in paper units.
7. Optional: Check the Place ticks check box; then specify the grid Style, Length, and
Position settings.
8. Optional: Check the Place crosses check box; then specify the grid Style and Length
settings.
9. Optional: Check the Place edge label check box; then specify the Orientation from
the drop-down list.
To define a border:
1. Select the Border tab.
2. Check the Place border around neatline check box.
3. Type the appropriate values settings for the Top margin, Bottom margin, Left
margin, and Right margin fields.
4. Specify the Style settings.
To save a cartographic grid definition:

2. Select the map frame, and then select Insert > Cartographic Grid.
3. Define the appropriate settings on the Neatline, Grid, Ticks and Crosses, and Border
tabs.
4. Click Save As.
5. Browse for the appropriate folder, type a name for the Cartographic Grid Definition
File (*.xml), and then click Save.
15-90
Note: When saving a cartographic grid definition file, you are prompted to save the grid
definition file (.csf) file if you have changed any of the coordinate systems. This action is
required to ensure a valid grid definition file. If you cancel out of the Save Cartographic
Grid Definition dialog box, it invalidates the grid definition file. This means that when
you attempt to reuse the grid definition file, there will be no reference to the changed
coordinate system. This is only required if you have changed one of the coordinate
systems for the grid generation.
To load a saved cartographic grid definition:

2. Select the map frame, and then select Insert > Cartographic Grid.
3. Click Load.
4. Browse for a Cartographic Grid Definition File (*.xml), and then click Open.
To modify cartographic grids:

1. Place a cartographic grid.
2. Select the cartographic grid and ungroup the components using the Ungroup
command.
3. Remove or adjust the position of the labels as necessary.
4. Select the grid line(s) to edit with the Select Tool. On the right mouse menu, select
Drop Polyline. Using the Select Tool, draw a fence around the grid line segments to
remove, and press the Delete key. Clean-up grid lines as necessary using the Extend
to Intersection or Trim to Intersection command.
Inserting Reference Grids and Indexes

The Insert Reference Grid and Insert Reference Index commands let you create and
place bingo grids (grid labeled along sides by letters and numbers, with one or more
indexes of features) in the layout window by placing a reference grid and a corresponding
reference index on the active layer of the layout window. After you have placed the grid
and its labels on the active layer, you can select the grid and insert the reference index.
15-91
Inserting a Reference Grid

Insert Reference Grid lets you place a grid, place a border around the grid, and define the
symbology. You can define the size of the grid squares (intervals) by entering the number
of rows and columns, or you can define the height and width in ground units or in paper
units. When specifying the grid interval in ground units, you can define a grid origin so
that the grid may be tied to a particular set of coordinates. The default origin in projected
(not geographic) ground units is the value corresponding to the upper-left corner of the
map visible in the selected map frame. The origin is disabled for paper units and number
of rows and columns. To use this command, you must have a valid static or dynamic map
in the select set.
In placing the label letters and numbers on the grid, you can set their orientation by placing
horizontal letters and vertical numbers, or vice versa. You specify the starting letter, so
you could have, for example, a grid starting at J and going to Z. The collating sequence
defaults to the English A, B, ...Z; AA, BB, …ZZ; and AAA, BBB, …ZZZ. You also
specify the starting number, so you could have, for example, a grid starting at 7 and going
to 20. Additionally, this command lets you specify where the labels should be placed with
respect to the border, inside or outside, as well as the distance from the border. The
distance unit is based on the current setting defined for the Distance unit on the Layout tab
on the Options dialog box (for example, mm, cm, or in).
After the grid and labels are inserted, the grid is left in the select set so that the Insert
Reference Index command can be easily run next if appropriate.
15-92
To insert a reference grid:

1. Make a layout window active.
2. Select an active sheet that contains a map frame.
3. Select the map frame.
4. Select Insert > Reference Grid.
5. Select the appropriate Intervals defined by (interval mode) option.

6. Type the size of the grid in the Interval value fields, which vary depending on the
selected interval mode.
7. Optional: Type the origin of the grid in the Origin fields.
8. Select the grid lines Place border check box if appropriate; then set its style.
9. Select the grid lines Place grid lines check box if appropriate; then set its style.
10. Type the grid Start letter.
11. Type the grid Start number.
12. Click Font to specify the label font on the standard Microsoft Font dialog box.
13. Select the appropriate orientation option for the letters and numbers.
14. Select the label Position inside or outside the grid from the drop-down list.
15. Type the Distance from border (positive only) at which to place the labels.
16. Click OK on the Insert Reference Grid dialog box to insert the grid.
The grid and labels are placed in the active layer, and the grid is left in the select set.
15-93
Inserting a Reference Index

After you have placed a reference grid on the active layer of the layout window with the
Insert Reference Grid command, the Insert Reference Index command lets you generate
a corresponding reference index. To use this command, you must have generated a
reference grid on a valid static or dynamic map in the select set. You can run this
command multiple times for the same reference grid.
This command lets you specify which point features and graphic text features to index.
The available features to index are compiled from a list of features and queries that are
present in the originating map window of the map being processed. For text features, the
indexing is based on the graphic text string. In this scenario, the contents of the index
correspond with the labels in the map. For point features, the indexing is based on an
attribute of the point feature. In this scenario, the contents of the index corresponds with
text attributes of point data. So the map would contain school symbols, and the index
would contain school names, for example.
You can define a title to be placed at the top center of the index. To improve legibility and
organization of the index, you can insert subheadings (123…; A, B, C …) inserted at the
appropriate places in the index. If no items fall under a subheading, that heading is not
used. The subheadings for numbers come first, followed by characters sorted
alphabetically. Note that these additional subheadings increase the number of items in the
index, which is calculated once the feature to index is selected, and can therefore affect the
column and row calculation. Additionally, you can define font characteristics for the title,
subheadings, and feature text. In placing columns or rows, you specify the number of
columns and then the number of rows is calculated automatically (values are calculated
using the number of features and the presence of subheadings). You also define the
column width and the spacing between columns. The inter-column order is feature/grid.
The alignment of the two parts of the column is seen in the following example:
The following example shows an index where duplicates were found:
15-94
This command lets you adjust the prefixes in two ways. You can ignore them when
sorting, which, for example, places Rue de Orleans with the Os rather than the Rs. You
also can specify a list of strings to be ignored or removed from the index, which, for
example, places Rue de Orleans as Orleans. Note that choosing to ignore or remove
prefixes when sorting can affect the number of items in the index.
You can place an index by one point (using font and spacing information) or by two points
(overriding font and spacing to fit the two points, forming a rectangle), or you can output
the index to a text file, which may override some parameters.
To insert a reference index:

1. Make a layout window active.
2. Select an active sheet that contains at a dynamic map frame.
3. Select a map frame.
4. Create and insert a grid with the Insert Reference Grid command.
5. Select the grid just placed.
6. Select Insert > Reference Index.
15-95
7. Select the Features to index from the drop-down list.

8. Select a corresponding Attribute from the drop-down list.
9. Select the Title check box to display a title; then type in the title.
10. Select the Alphabetic sub-heading check box to display the sub-headings.
11. Specify the font of all text items – Title, Alphabetic sub-heading, and Feature text.
12. Specify the Prefix options, typing any prefixes to be ignored and/or removed.
13. Specify the Index format parameters.
14. Select one of the following Index placement options:
– Place by point (by a single point) – Continue with Step 15.
– Place by rectangle (by two points) – Go to Step 17.
– Output to file – Go to Step 20.
15. Click OK.
16. When prompted to Click to place the upper-left corner of the index, click the mouse
to place the index.
A box the size of the index is displayed in dynamics. After the mouse click, the index is
placed in the active layer at that location.
17. Click OK.
18. When prompted to Click to place the upper-left corner of the index, click the mouse
to indicate the upper-left corner of the index.
A dynamic rectangle is displayed as the mouse is moved after the click.
19. When prompted to Click to place the lower-right corner of the index, click the
mouse to indicate the upper-right corner of the index.
15-96
After the second click, the index is fit to that rectangle.

20. On the standard Open dialog box, select where the text file is to be placed; then click
OK.
After the dialog box is dismissed, the file is written and the command is ended.
Inserting a Data Table

The Insert Data Table command lets you display selected portions of a data window in
the layout window in a customized style. To use this command, you must have first
defined the data window area to be inserted. You can only place static data with this
command.
You can select the data window portion you want to display by a single cell, a contiguous
rectangle of cells, one or more rows (not necessarily contiguous), or one or more columns
(not necessarily contiguous).
You can customize the appearance of the data window insert by adjusting the title, column
headers and widths, and cells. You have the option to display the title of the data window
and the column headers. You can also change the title and its font and the font of the
headers and cells through the standard Font dialog box.
Additionally, you determine the column width by one of the following methods:
• Based on data window (default)—Each column width is based on that column’s width
in the data window.
• Based on longest text—Each column width is based on the longest string in that
column.
• User-defined—All columns have the same user-defined width.
Note: With the first and third options, column width might be too short, in which case the
string is truncated.
15-97
The width units are based on the distance units set on the Layout tab of the Tools >
Options dialog box.
You can further customize the data window display by using the Properties command to:
• Reorder columns • Hide/Show columns
• Change column widths • Change data values
• Re-sort data
To insert a data table:

1. Open the appropriate data window.
2. Format the data as you want it displayed.
3. Highlight the data to be displayed.
4. Activate the layout window
5. Select Insert > Data Table.
.
6. Select the appropriate Data window from the drop-down list.
7. Check the Title check box to display a title; then optionally change the title text and
font.
8. Check the Column headings check box to display headings; then optionally change
the heading font.
9. Optional: Click Cells > Font to change the cell font.
10. Select appropriate Column widths option.
If you select User-defined, type a positive value for the column width in the key-in
field.
11. Press OK; then click to place the data window grid.
15-98
Note: A right mouse click lets you return (backup) to the dialog box without placing
the data window grid.
15-99
15-100
Printing in GeoMedia
Printing Overview
Printing in GeoMedia can be performed in any of its three windows: map window, data
window, or layout window. Due to the difference in the types of data within each window
and the difference in their respective environments, each window has a unique set of
paper-related parameters that must be defined before printing. The map window and data
window contain data on a sort of virtual canvas. The data of the map window are
geographic, typically stored in ground units without any reference to a paper layout.
Similarly, the data of the data window are tabular, without any reference to a paper layout.
In contrast, the sheets in the layout window are specifically referenced to a paper layout.
Although each window has its own subtleties due to its data type and environment, before
printing, the paper layout parameters must be defined through the Page Setup of each
window.
Defining the Map Window Page Setup

The map window Page Setup contains the parameters necessary to transform the virtual
canvas of the map window into paper space suitable for printing or plotting. The
parameters are presented on the Map Window Page Setup dialog box on its four tabs:
Size and Scale, Margins, Units, and Printer.
Size and Scale—This tab contains the settings for defining the Paper Size, the paper
Orientation, and the Print Scale. Once these parameters have been set, the results of
these settings are displayed in the Print Range and Output sections.
• Paper Size > Size—This drop-down list provides a list of all of the paper sizes
supported by the printer specified on the Printer tab. Width and Height of the
selected paper size are expressed in the units defined for paper units on the Units tab.
• Orientation—Options include Portrait and Landscape.
• Print Scale—This can be defined by selecting a predefined scale, by defining a custom
scale, or by defining the output to fit a specific number of pages wide by pages tall.
Print scale represents the relationship between paper units and ground units. This
relationship can be expressed in the following ways:
− Scale—Defined as a fractional equivalent, such as 1/25,000, commonly expressed
as 1:25,000. This method states that one unit on the paper is equivalent to 25,000
units on the ground. The units are irrelevant as long as they are the same; one
centimeter on the paper is equivalent to 25,000 centimeters on the ground, or one
inch on the paper is equivalent to 25,000 inches on the ground.
16-1
− Custom—Defined as a verbal description. This method states that some unit on

the paper is equivalent to some unit on the ground, such as “one inch equals one
mile”, or “one inch to the mile.” The units on either side are typically different.
“One inch equals one mile” is simply another way of expressing 1:63,360 – that is,
there are 63,360 inches in a mile. The left field defines paper units, and the right
field defines ground units, as specified on the Units tab.
− Fit to—Defined by stating that the geographic extent of the map window will be
fit into a particular page definition. This method automatically calculates the
fractional equivalent scale. If you select Fit to and specify a number of pages wide
and tall, the printout will not be distorted to fit the specified number of pages. For
example, for a map window whose defined geographic extent and scale would
result in output that is two pages wide and one page tall, and you specify four
pages wide and four pages tall, the resulting output would be twice as wide—four
pages—but only two pages tall, and eight pages would be blank.
• Print Range—Reports the Width and Height of the geographic extent of the
print/plot in ground units, as specified on the Units tab.
• Output—Reports the following assorted information pertaining to the paper output:
Width, Height, Scale, Pages wide, and Pages tall. The width and height are reported
in the units specified on the Units tab.
Margins—This tab contains the settings for the position of the plot relative to the paper
upon which it is printed. Options include specifying a fixed distance between the edge of
the paper and the data on the Left, Right, Top, and Bottom, or specifying that you want to
center the plot to the page. Margin settings will impact the overall size of the plot,
especially when the plot requires multiple pages, as displayed in Pages wide and Pages
tall in the Output section on the Size and Scale tab.
• Center to page(s)—Select this option to center the output on the page. Normal
justification is bottom left.
• Overlap Page Margins—If turned on, this option causes the margins to be duplicated
so they can be overlapped. This is useful for aligning tiles so they can be spliced
together later.
Units—This tab contains the settings for defining the Paper Units, Ground Units, and
Scale Precision. These units are necessary for defining the manner in which the
relationship between ground units and paper units is expressed throughout the Map
Window Page Setup dialog box. The paper unit selected is used when displaying the
Width and Height of the selected Paper Size, the Width and Height of the Output, and
the first field of the Custom print scale on the Size and Scale tab. It is also used for
defining margins on the Margins tab. The Ground Unit selected is used when displaying
the Print Range and the second field of the Custom print scale on the Size and Scale tab.
The ground units in the GeoWorkspace are not affected by this setting. The Scale
Precision setting is used for the Print Scale on the Size and Scale tab.
16-2
Printer—This tab contains a drop-down list of all of the available printing devices resident
on the machine, including local and network printers. Once a printer has been selected,
information regarding its status, the type of device, and where it is located is displayed.
Each printer in the list has a set of default parameters that can be modified for the printing
session by clicking Properties. The available Paper Sizes listed in the Size drop-down list
on the Size and Scale tab are determined by the paper sizes supported by the printer
selected on this tab.
To define the map window page setup:

1. Select File > Page Setup.
2. On the Printer tab of the Map Window Page Setup dialog box, select the printer or
plotter for your output.
3. On the Units tab, select the desired paper units, ground units, and scale precision.
4. On the Margins tab, optionally set the margins, and turn on or off the center and
overlap options.
5. On the Size and Scale tab, select the desired paper size, define the orientation, and
define the print scale for your output.
6. Click OK.
Printing a Map Window

If the map, legend, north arrow, and scale bar are displayed when you print the contents of
a map window, they appear on the printout. The map and legend print just as they appear
in the map window. The north arrow prints at the size specified on the North Arrow
Properties dialog box. The drop-down list of available north arrow sizes ranges from 8 to
96 points, but you can also type values that exceed 96 points. The scale bar prints using
either automatic sizing or the size set on the Scale Bar Properties dialog box. The
16-3
preferred method for the scale bar properties is to use a fixed interval definition. This
approach produces predictable results, generating a scale bar at a fixed size. Automatic
sizing creates a scale bar that is twenty percent of the width of the plot, which may be too
large for some plots.
See the “Working with Layout Windows” and “Designing Map Layouts for Printing in the
Layout Window” chapters.
To print a map window:

1. Configure the map, legend, north arrow, and scale bar so that they look the way you
want them to print.
2. Select File > Print.
3. Select a printer from the Name drop-down list.

4. Specify the Number of copies to print.
5. If you want Draft Quality and your printer supports that option, check that option.
6. Click OK.
Printing to a File
Printing to a file is similar to printing a hard copy, except it generates a printer file instead
of routing the document directly to a printer. This provides a method for generating soft-
copy files that can be stored on disk and printed or plotted as necessary without having to
be in the application to resubmit the plots. The document is by default saved with printer
formatting to a file with the .prn (printer driver) extension. The format of this reserved
name file is device dependent, and it is derived from the printer driver of the printer
selected in the Printer > Name field on the Print dialog box.
To print to a file:
16-4
2. On the Print Map Window dialog box, select a printer; then select the Print to file
check box.
3. Click OK to open the Print to File dialog box.
4. Navigate to the appropriate folder; then in the File name field, type the name of the
file you want to save.
5. Click Save.
Note: To submit a .prn file, type at a DOS prompt: copy filename

path_to_queue, where filename = the name of the *.prn file, and where
path_to_queue = the name of the printer and queue (for example,
\\b17bpn\hp_101).
Defining the Data Window Page Setup

The data window Page Setup contains the parameters necessary to transform the virtual
canvas of the data window into paper space suitable for printing. The parameters are
presented on the Data Window Page Setup dialog box on its four tabs: Size and Scale,
Margins, Units, and Printer.
Size and Scale—This tab contains the settings for defining the Paper Size, the paper
Orientation, and the Print Scale. Once these parameters have been set, the results of
these settings are displayed in the Print Range and Output sections.
• Paper Size > Size—This drop-down list provides a list of all of the paper sizes
supported by the printer specified on the Printer tab. Width and Height of the
selected paper size are expressed in the units defined for paper units on the Units tab.
• Print Scale—This enables you to specify the scale of the output expressed as a
percentage of its normal size.
If a print scale of 100% would split a column across more than one page, the highest
percentage possible to fit the entire column on the page will be less than 100%. You
16-5
can reduce or enlarge the size of the output by selecting a percentage above or below
100%; this represents a scale in which the point size of the cell text in the data window
is enlarged or reduced for the printed output. For example, if the point size of the cell
text in the data window is ten, a print scale of 50% reduces the size of the printed
output by 50%. Thus, the point size of the cell text on the output would be five.
Conversely, a point scale of 200% doubles the size of the output so that the point size
of the text on the output is 20.
• Print Range—Reports the Width and Height of the tabular extent of the print in
paper units, as specified on the Units tab.
• Output—Reports assorted information pertaining to the paper output: Width, Height,
Pages wide, and Pages tall. The width and height are reported in the units specified
on the Units tab.
Margins—This tab contains the settings for the position of the plot relative to the paper
upon which it is printed. Options include specifying a fixed distance between the edge of
the paper and the data on the Left, Right, Top, and Bottom. Margin settings will impact
the overall size of the print, especially when the print requires multiple pages, as displayed
in Pages wide and Pages tall in the Output section on the Size and Scale tab.
Units—This tab contains the settings for defining the Paper Units that are expressed
throughout the Data Window Page Setup dialog box. The Paper Unit selected is used
when displaying the Width and Height of the selected Paper Size, the Print Range, and
the Width and Height of the Output on the Size and Scale tab. It is also used for
defining margins on the Margins tab.
Printer—This tab contains a drop-down list of all of the available printing devices resident
on the machine, including local and network printers. Once a printer has been selected,
information regarding its status, the type of device, and where it is located is displayed.
Each printer in the list has a set of default parameters that can be modified for the printing
session by clicking Properties. The available Paper Sizes listed in the Size drop-down list
on the Size and Scale tab are determined by the paper sizes supported by the printer
selected on this tab.
To define the data window page setup:

16-6
2. On the Printer tab of the Data Window Page Setup dialog box, select the printer or
plotter for your output.
3. On the Units tab, select the paper units.
4. On the Margins tab, set the margins.
5. On the Size and Scale tab, set the paper size, orientation, and print scale for your
output.
6. Click OK.
Printing a Data Window

You can print what is displayed in the data window, all rows or a range of rows.
To print a data window:
1. Configure the data window so that it looks the way you want it to print, hiding
columns you do not want to print and showing those you do.
3. Select a printer from the Name drop-down list.

16-7
4. Identify the Print Range of the rows you want to print.

6. If you want Draft Quality and your printer supports that option, check that option.
7. Click OK.
Printing to file provides a method for generating soft-copy files that can be stored on disk
and printed as necessary without having to be in the application to resubmit the prints.
See the “Printing to a File” section in this chapter for complete information.
Defining the Layout Window Page Setup

The layout window Page Setup contains the parameters necessary to define the layout
window so it is suitable for printing. Unlike the map window and data window, whose
contents are not referenced to paper space, the layout window environment is defined in
terms of paper space. Data placed on layout sheets in the layout window are scaled as they
are placed, minimizing the need to transform or to scale the data through the page setup.
The layout window Page Setup lets you define a unique page setup for each layout sheet
in the layout window. The parameters are presented on the Layout Window Page Setup
dialog box, which contains the settings for defining the sheet name, description,
background sheet, visible status, paper size, image quality, and layout orientation. It also
lets you save the current settings as the default.
• Name—Lets you specify unique sheet names. This name appears on the layout sheet
tab. By default, the sheets are named Sheet1, Sheet2 and so forth and are incremented
as sheets are inserted.
• Description—Lets you provide a detailed description of the content and purpose of
each layout sheet.
• Background—This setting is optional, letting you attach a single background sheet to
multiple working sheets. When selected, the background sheet is displayed behind the
layout sheet, and its features cannot be selected unless the background sheet is the
active sheet. A background sheet can be displayed and printed along with any layout
sheet to which it is attached.
• Visible—Lets you turn on and off individual layout sheets in the layout window. This
setting can be beneficial when the layout window contains a large amount of layout
sheets, providing a useful method for reducing the amount of layout sheets to sort
through. This option is also accessible on the Layout Window Properties dialog box.
• Paper Size—Settings include Size, Width, Height, and Units.
− Size—Provides a list of commonly used paper sizes supported by printers and
plotters. If the appropriate paper size in not in the list, you can select Custom
from the drop-down list, specify the desired Units, and type in the appropriate
16-8
Width and Height values. When Custom is selected, the Orientation options are
disabled. Instead, the Orientation is determined by the Width and Height values.
When the Width value is greater than the Height value, the Orientation will be
Landscape. Conversely, when the Width value is less than the Height value, the
Orientation will be Portrait.
− Width—This is a read-only field for all Size definitions except Custom. When
Custom is selected, this field is enabled.
− Height—This is a read-only field for all Size definitions except Custom. When
Custom is selected, this field is enabled.
− Units—This is a read-only field for all Size definitions except Custom. When
Custom is selected, this field is enabled. Options include centimeters, millimeters,
and inches.
• Save as Default—Enables you to configure the default settings used when adding or
inserting a new layout sheet. This ensures that all new layouts are created using the
same parameters. If this option has not been selected, the default Page Setup of newly
inserted sheets will be based on the Page Setup parameters of the active sheet when
the Insert Sheet command was selected. If you need to insert multiple sheets that have
a page setup description different from the current active sheet, changing the page
setup description and then selecting Save as Default causes the layout window to use
the currently saved parameters when inserting the new sheets. The Save as Default
parameters are used for the current working session, and they are persisted if you save
the GeoWorkspace. Saving the GeoWorkspace saves the new parameters as the
default page setup description.
To define the layout window page setup:

1. Select Window > Layout Window, and open the appropriate layout sheet.
16-9
Note: You can also access this command by double clicking on the row of a listed
layout sheet on the Layout Windows Properties dialog box. The Layout Window
Page Setup dialog box is automatically populated with the parameters of the selected
sheet.
3. Optional: Edit the layout sheet name in the Name field.

4. Check the Visible check box.
Note: If this check box is unchecked, the sheet will not be displayed when you select
OK.
5. Optional: Edit the description in the Description field.

6. Optional: Select an appropriate background sheet from the Background drop-down
list.
The background sheet is displayed under the layout sheet, and its features cannot be
selected unless the background sheet is active.
OR
Select none, which is displayed as a blank Background field.
7. Select the appropriate Paper Size from the drop-down list.
OR
Select Custom from the Size drop-down list, type in the appropriate Width and
Height values, and then select the appropriate Units from the drop-down list.
8. Select the appropriate layout Orientation option.
9. Optional: Click Save as Default.
The current settings are saved as the default plot layout page setup.
10. Click OK.
Printing Layout Sheets from the Layout Window

Printing layout sheets follows standard Windows printing procedures and interfaces;
however, printing layout sheets is somewhat different from printing map windows and data
windows. Print Layout Window options include defining the printer, print range, number
of copies, print multiple sheets per page, and additional properties and settings. For the
print range, you can choose the active layout sheet, all visible layout sheets, or selected
visible layout sheets by using the logical numbers identified on the Layout Window
Properties dialog box. For multiple sheets per page, you can perform plot nesting;
16-10
choosing the finished paper size, where the selected sheets will be grouped together on a
single plot. The parameters available in the Properties dialog box are determined by the
printer driver used when creating the printer. Once you have chosen the appropriate
options and parameters, you can print the layout sheet to a printer, a plotter, or a file.
The Settings options let you edit scale and origin information, including margins and print
magnification. The Print magnification pertains to all graphics on the layout sheets
included in the print and is defined in terms of percentage. The default is 100% for full-
size, 1:1 plots. You can make reductions and enlargements by changing the print
magnification. A value of 50% produces a half-size drawing, and a value of 200%
produces a double-size drawing. The Origin offset lets you specify additional margins and
displays a preview of how the layout sheet fits on the paper form selected.
Note: Print magnifications have no cartographic intelligence. They are equivalent to

enlargements or reductions performed by a photocopy machine. When print magnification
is other than 100%, the scale bar is invalidated if it includes a fractional equivalent or ratio
(for example, 1:24,000) or a description (for example, 1 inch = 1 mile). This situation can
produce erroneous scale information in which the text no longer matches the scale bar.
Consequently, if you use a print magnification other than 100%, the scale bars should omit
any reference to fractional equivalents or descriptions.
You can print a subset of a layout sheet by selecting the Print area option on the Print
Layout Window dialog box. If you select this option, you are prompted to identify a
rectangular area on the active layout sheet, and then the Print Area dialog box opens for
the input of relevant parameters.
You can combine multiple sheets into a single plot by selecting the Print multiple sheets
per page on check box on the Print Layout Window dialog box, and then defining the
finished paper size. This option is only enabled if more than one sheet is selected for
printing, that is, if you select all-sheets mode, specify more than one sheet (for example, 1-
4,5,10), or set the number of copies to more than one.
Note: When printing multiple sheets, the graphic preview on the Settings dialog box
provides a preview of each of the sheets that it can fit on the defined paper size. If only
one sheet is visible in the preview, it means that the size of the finished paper defined can
only accommodate a single layout sheet. To get around this, either increase the finished
paper size on the Print Layout Window dialog box, or change the plot scale by reducing
the print magnification on the Settings dialog box until multiple sheets appear in the
preview.
The Print Quality slider lets you choose any of five settings ranging from Draft to Best,
allowing you to control the trade-off between print quality and print performance
(speed/scalability).
16-11
The function of the Print Quality slider depends on the content of the layout sheet being
plotted. If the sheet contains no images, no translucent or transparent features, and no
bitmap-patterned areas, the Print Quality slider has no function whatever.
However, if images are present in the layout sheet, but there is no translucency or
transparency of feature data (raster or vector), and there is no contrast or brightness
adjustments active on the displayed images, and there are no bitmap patterned areas, the
slider causes the raster image to be decimated according to the following rules:
• The Best setting processes the images at full resolution (every pixel up to the limit of
the dpi of the device is sent to the printer).
• The Draft setting effectively reduces the resolution of the printer by a factor of 5 (but
only for the images!).
• The intermediate settings from Best to Draft cause GeoMedia (Professional) to

generate sufficient raster resolution to match the printer resolution reduced by 1/2, 1/3,
and 1/4, respectively (again, this only applies to any images in the plot).
If the layout contains transparent or translucent features, or images with contrast and
brightness adjustments, or bitmap-patterned area features, the Print Quality slider behaves
quite differently. In these cases, GeoMedia (Professional) pre-processes the map graphics,
generating a raster bitmap at a specific spatial and spectral resolution. This bitmap is then
submitted to the device, along with the rest of the sheet content.
At the Best setting, you create a 24-bit color bitmap of the map graphic at the full
resolution reported by the plotting device. This will typically be a very large raster, and it
may cause problems for some plotting configurations. The default (center) setting creates a
16-bit color bitmap at resolution equal to 50% of the plotter’s reported value. The Draft
setting reduces the target plot resolution to one-tenth the dpi reported by the device and
creates the bitmap with only 8-bit color (256 total colors).
Color Depth Resolution % of Printer Default Slider Setting
24-bit 100% Best
16-bit 100%
16-bit 50% (default)
8-bit 50%
8-bit 10% Draft
Both the Settings dialog box and the Print Area dialog box contain a color-coded preview
area. This useful feature lets you easily view the relationship between the document print
range, the printer paper size, and the actual printing area on the final plot before you
actually print it. It also provides a preview of the graphics on the sheet for visual
assistance.
To print a layout sheet:

1. Select the appropriate layout window as the active window.
16-12
See GeoMedia Help for complete information on this dialog box and dialog boxes
accessed from it.
3. Select the appropriate Printer from the Name drop-down list.
4. Optional: Click Properties to review and/or change the printer-specific properties.
5. Identify the Print Range that you want to print.
Note: Selecting the Print area option disables the Print multiple sheets per page on
check box and the Settings button.

7. Optional: Set the Print Quality slider appropriately.
8. Optional: Check the Print multiple sheets per page on check box; then select the
Size from the drop-down list.
Note: This option is only available if more than one sheet has been selected for
printing.
9. Optional: Check the Pure Black And White check box.

10. Optional: Click Settings to edit scale and origin information.
16-13
11. Type the appropriate Print magnification.

12. Select the Center check box to position the center of the print area to the center of the
printer paper. Otherwise, the paper is positioned according to the X,Y settings, whose
default is 0,0 (the upper left being the default origin).
Note: Center is disabled if you check the Print multiple sheets per page on check
box.
OR
Type the appropriate X value to set a shift in the X direction from the origin and/or the
Y value to set a shift in the Y direction from the origin.
13. Click OK.
The Settings dialog box is dismissed, and the Print Layout Window dialog box
reappears.
14. After you have set all the parameters on the Print Layout Window dialog box, click
OK.
If you are printing to a printer or plotter, the selected layout sheet or sheets are
printed, and the command is exited.
OR
If you selected Print area as the Print Range in Step 5, a set of crosshairs is
displayed, and you are prompted to identify the area to print.
15. Identify the print area with a rectangle.
16-14
16. Type the appropriate Print magnification.

17. Select the Center check box to position the center of the print area to the center of the
printer paper. Otherwise, the paper is positioned according to the X,Y settings, whose
default is 0,0 (the upper left is the default origin).
OR
Type the appropriates X value to set a shift in the X direction from the origin and/or
the Y value to set a shift in the Y direction from the origin.
18. Optional: Click XY Range to clear the previously defined print area; then define a
new area to print by placing two data points.
19. Click OK.
If you are printing to a printer or plotter, the selected layout sheet or sheets are
printed, and the command is exited.
Printing to file provides a method for generating soft-copy files that can be stored on
disk and printed or plotted as necessary without having to be in the application to
resubmit the plots.
See the “Printing to a File” section in this chapter for complete information.
Plotting
Upon completion of your map design, you can submit the plot to a plotter or an offline file,
such as PDF, through the standard Windows printing interface. The layout window and all
of its associated layout sheets are automatically saved in the GeoWorkspace when you save
the GeoWorkspace. If you do not want to save the plot session, you can manually delete
the plot upon completion.
16-15
See the “Printing Layout Sheets from the Layout Window” and the “Outputting PDF from
GeoMedia” sections in this chapter for more information.
GeoMedia Professional also provides batch plotting through the Batch Plotting utility.
There are two types of batch plotting files, compose and select. Compose batch plotting
files store the information necessary for the composition of new layout sheets, such as the
GeoWorkspace, the layout template and the named legend. Select batch plotting files store
the information necessary to simply plot multiple layout sheets from multiple
GeoWorkspaces in a batch process. This utility supports a graphical user interface (Start >
All Programs > GeoMedia Professional > Utilities > Batch Plotting) and a command
line interface.
See the Batch Plotting utility’s online Help for complete information.
Printing Transparent or Translucent Graphics

Microsoft Windows operating systems are designed with a modular printing capability to
accommodate many different printing capabilities and devices. Though many Windows
users may not be aware of it, different printers use different graphics languages, that is, the
graphical image to be printed may be passed from the computer to the printer in any of
several popular printing languages. By virtue of its robust integration with Windows,
GeoMedia products can output virtually any plot format used by a printer for which a
Windows printer driver is available.
Some printers support more than one printing language. For example, a popular plotter
among GIS users is the Designjet series of large-format plotters from Hewlett Packard
(HP). Most Designjet plotters are capable of interpreting print jobs in several different
languages or formats, for example, PostScript, HPGL (a graphics language developed by
HP), and TIFF raster images. In some cases, the capabilities of a printer depend on options
selected when you purchased the printer. When you plot from a Windows application, the
language sent to the printer is determined by the Windows printer driver that was selected
when the printer was added to the client computer. One printer driver may enable
Windows to send PostScript language to the printer, while another printer driver may
enable Windows to send HPGL language to the printer. It is possible to have multiple
printer drivers installed on the same computer, enabling you to send the same graphics job
to the printer using any of several different languages.
At this time, there are some known limitations with the way Windows uses the PostScript
language when transparent or translucent graphics are included in print graphics. PDF and
PostScript are closely related languages (both developed by Adobe), so many of these
limitations also apply to PDF file generation and plotting. If your print job includes
transparent or translucent graphics and you do not see the expected results in a plot, you
should look at your printer setup to determine whether a PostScript-based printer driver
was used to send the job to your printer. If so, you may be able to work around this
problem by installing and using a different printer driver to send the job to the same printer
using a different graphics language. In most cases, the practical approach is simply to add
a second printer definition to your Windows system and to use the different printer driver
16-16
when setting up the new printer. You can then reprint your job from GeoMedia, selecting
the new printer definition.
This type of problem that exists today between Windows printing and PostScript printer
drivers is not uncommon in the computer business. Such problems are typically resolved
over time by fixes and new releases of software, or by the evolution of language
specifications. If not, you should not give up on using PostScript for printing from
GeoMedia. You should try again periodically to see if some upgrade on your system may
have solved the problem.
Outputting PDF from GeoMedia

GeoMedia does not provide native authoring functionality to write PDF files. As with
PostScript output, PDF output is generated from GeoMedia through the Windows PRINT
interface. In the case of PDF, Adobe® (the originator of the PDF language) makes a
business of selling a PDF driver for Windows systems. This PDF driver is known as the
Acrobat® Distiller and is delivered with the full version of Adobe Acrobat. Many
computer users have installed the Acrobat Reader, typically at no cost through Internet
download or delivered with some PDF-format documents. But this does not include the
authoring capability, only the ability to view existing PDF files. There are also several
third-party PDF drivers available as alternatives to the Adobe product. But for the
examples in this appendix, we will use the Adobe Acrobat product. When Adobe Acrobat
is installed on a computer, a new printer driver is automatically installed on the computer.
The printer is named Acrobat Distiller on the Windows Printers dialog box.
When you print to the Acrobat Distiller driver from GeoMedia using the File > Print
command, a PDF file is generated containing the printed page. It is valuable to note that
the Acrobat Distiller allows you to generate PDF files from almost any Windows software
application – not just GeoMedia.
Setting Acrobat Distiller Parameters

There are several parameters or properties that may be set to control PDF output from the
Acrobat Distiller. The recommended choices depend on the ultimate purpose of the PDF
document. These properties are set by starting Acrobat Distiller from the Windows Start
menu. Acrobat is delivered with four sets of parameters pre-determined for compatibility
with common applications. If you plan to publish a map using an offset printing press, the
recommended Default Setting is Press Quality.
16-17
You may set other individual properties for the Acrobat Distiller, as well as reviewing the
details of the default properties, by using the Settings menu on this same dialog box. See
the documentation delivered with the purchased product for detailed instructions for
installing and configuring Adobe Acrobat.
16-18
Working with Libraries
A library is a repository of sharable GeoWorkspace objects designed especially for the
enterprise user. With the library commands, you can easily and directly share the contents
of your GeoWorkspace. You can create new libraries, connect to and manage libraries,
and organize libraries.
The library commands give you the ability to save the following object types:
• Catalog Connections • Searches
• Warehouse Connections • Categories
• Legends • Spatial Filters
• Queries • Styles
• Queues
Once you have saved these objects, any user can connect to the library and copy the
appropriate objects into the active GeoWorkspace.
For example, a large enterprise might have specific corporate standards for symbolizing
each type of feature. Road features might be black with a dashed white centerline and
rivers might be blue. The GIS administrator for such an enterprise might create a
corporate style library that all GIS users would use to get copies of all of the official styles
to be used in their GeoWorkspaces.
But what if the official style for Road features changes? The GIS administrator can easily
replace the Road style in the library, and users can then simply connect to the updated
library and refresh the objects whose definitions have changed.
Note that most of the sharable objects reference other objects. For example, a legend
contains Legend Entries, each of which refers to one or more Style Definitions and
Queries. The Queries can refer to other Queries and/or Feature Classes. Feature Classes in
turn refer to Connections. And, of course, Style Folders contain Style Definitions, and
Query Folders contain Queries.
When you save one of these objects to a library, the system automatically saves all of the
objects in the reference tree. Then when the object is copied to a GeoWorkspace, all of the
required objects underneath it are also copied. This ensures that the copied object will be
fully functional in the active GeoWorkspace.
The library commands are the following:
• New Library • Library Connections
• New Library Connection • Library Organizer
These commands are discussed in the following sections of this chapter.
17-1
Creating a New Library

The New Library command lets you create a new read-write library in an Access database
file (.mdb) only. This command provides a simple way of creating a library schema layout
in a new database while needing minimal input from you. You do not need a warehouse
connection to create a library; however, you do need such a connection to carry out all
library-related workflows.
Creating a library is a two-step process. You first select and validate a library template,
and then you use that template to actually create the new library. This command is similar
to the Warehouses > New Warehouse command in GeoMedia.
By default, this command creates the library from the provided library template
LibraryTemplate.mdb located in the <Program Files>\GeoMedia\Templates\Libraries
folder. You can, however, choose a different template from those available in the product
template folder. This template file acts as a seed for creating the library.
To create the new library after selecting the template, you specify a name for the library or
select an existing .mdb file in the default <Program
Files>\GeoMedia\GeoWorkspaces\Libraries folder or in any other location of your choice.
The command then creates the library based on the selected template. If there is no
coordinate system in the template, the command automatically configures the coordinate
system of the library using the active coordinate system of the active GeoWorkspace.
Note: The principal use of the library coordinate system is to transform spatial filters into
the GeoWorkspace coordinate system. The GCoordSystem table that may be present in the
.mdb of the library is not used to store the coordinate system of the library.
When the library is created, a connection is automatically opened for the new library. The
name of the library connection is set as the library name itself. If a library connection
exists with the same name, an incrementing digit is added to the end of the name.
To create a new library:

1. Select Tools > New Library.
17-2
2. Select the appropriate library template; then click Open.
3. Type the appropriate File name; then click Save.

The template is validated, and if valid, the library is created.
Creating a New Library Connection

The New Library Connection command lets you connect to libraries that are compatible
with GeoMedia. This connection is then available for use with other library commands.
You can open a library in read-write or in read-only states.
17-3
Concerning compatibility of the library data store with the library software, the command
informs you of the need to upgrade the schema while connecting in read-write mode and in
the case of failure to connect due to forward incompatibility, as follows:
• When connecting in read-write mode, if the version of the library is lower than the
schema version supported by the software, a message asks whether you want to
upgrade the schema or not. If the schema of the library is not upgraded, the library is
opened in read-only mode.
• If the schema version of the library is higher than the version supported by the
software, a message tells you that that the library cannot be opened.
You can make the following types of connections:
• Access • Access Read-Only
• Oracle Object Model Read-Write • Oracle Object Model Read-Only
• SQL Server Read-Write • SQL Server Read-Only
For Access, you select the location of the Microsoft Access database file (.mdb) to which
you want to establish a connection. For Oracle and SQL Server, you select the mode of
authentication, username, password, and host string.
For Oracle, MSSQL and DB2, which allow table and column level permissions, library
connections are made with whatever database permissions are available to the user making
the connection. When using the read-write servers, if the permissions are not available for
read-write access, the connection will revert to a read-only state. If a connection to the
same database already exists, a message is displayed telling you to use the existing
connection. In this case, the connection is not made. When making a library
connection to a read-only Access library using the read-write server the connection
will fail. To make a connection to a read-only Access library the read-only server
must be used instead.
You can also create a new connection to a library by the same procedure through the New
button of the Library Connections command dialog box described later in this chapter.
See “Managing Library Connections” in this chapter.
maintain these in separate folders in order to make the individual database type more easily
found. In addition, the software has separate folder locations for the Access versions of
these files, and you should add the word catalog, library, or warehouse to filenames in
17-4
To create a new library connection:

1. Select Tools > New Library Connection.
Select Access or Access Read-Only as the Connection type; then:
• Change the Connection name or keep the default,
Note: The comma ( , ) character is not allowed in the Connection name.
• Type an optional Connection description, and then

• Type the complete path of the .mdb Access Database file or select it by clicking
Browse.
OR
Select Oracle Object Model Read-Only/Read-Write as the Connection type; then:
• Type an optional Connection description,
• Select the Server and mode of authentication, and then
• Type the User name, Password, and Host string.
17-5
OR
Select SQL Server Read-Only/Read-Write as the Connection type; then:
• Type an optional Connection description,
• Select the Server and mode of authentication,
• Type the User name and Password, and then
• Select the Database.
3. Click OK to make the connection.
Note: Both SQL Server and Oracle require that the GeoMedia’s standard metadata
structure be present before establishing a library connection. For SQL Server, this
metadata resides in the database. In Oracle, it is contained in the GDOSYS metadata
schema. The specific tables required by the library commands are created automatically if
the tables do not already exist.
17-6
Managing Library Connections

The Library Connections command manages the connection information of a library
connection in a manner similar to the Warehouse > Connections command of GeoMedia.
The Library Connections command lets you do the following:
• Make a new library connection.
• Review a list of all available library connections in a GeoWorkspace.
• Change the state of a library connection (open read-write, open read-only, or closed).
• Edit the library connection parameters (properties) of an existing library connection for
the data server involved.
• Delete an existing open or closed library connection.
All library connections present in the GeoWorkspace are displayed in the connection grid
on the Library Connections dialog box. The rows in the grid are sorted alphabetically
based on the Name column. You can resize this grid as appropriate.
The connection grid has the following read-only columns:
Name—Library connection names, with an icon at the start of the cell indicating the state:
Open Read-Write
Open Read-Only
Closed
Type—Library connection type.
Library—Location of the library, that is, the database .mdb file for an Access database or
the data source name for an Oracle Object Model or SQL Server database. You can edit
the location of the library using Properties but not directly from the cell of the grid.
17-7
Note: By default, library connections are kept in a closed state. They are opened
automatically when used by the Library Organizer command.
To open or close connections:

1. Select Tools > Library Connections.
2. Select the row selector of the row(s) whose open/close status you want to change.
Note: Use Shift/Ctrl to select multiple rows; click the top left-corner grid button, to
the left of the Name row, in order to select all rows.
3. Click the appropriate open, reopen, or close button.
To create a new connection:

2. Click New.
3. Using the previously described procedure, select the Connection type; then enter the
appropriate parameters.
4. Click OK to make the connection.
To view or edit library connection properties:

17-8
2. On the Library Connections dialog box, select the row of the connection whose
properties you want to view or edit; then click Properties.
3. Edit the server-specific properties appropriately.

4. Click OK.
Organizing Libraries
The Library Organizer command lets you copy the following objects between the active
GeoWorkspace and a library attached to it:
• Catalog Connections • Searches
• Categories • Spatial Filters
• Legends • Styles
• Queries • Warehouse Connections
• Queues
Support for queues is limited to dynamic queues, which are displayed in the dialog box
treeviews on the Library Organizer dialog box. Static queues are thus not displayed in
these treeviews. Support for queues also includes support for subqueues. Subqueue
objects are not individually selectable but always move in and out of libraries with their
parent queues; thus, child subqueues are not displayed in the treeviews.
All the objects that can be copied are displayed on the Library Organizer dialog box in
two treeviews. The Library contents treeview on the left shows the objects that reside in
the library. The GeoWorkspace contents treeview on the right shows objects that reside
in the active GeoWorkspace. The icon next to each object indicates the type of the object.
You can thus easily browse and directly manipulate any of these objects and then copy the
selected objects from the active GeoWorkspace to a read-write library or from a library to
the active GeoWorkspace. You can select an individual or multiple objects for copy from
both treeviews. After selecting the objects you want to copy, you use the left or right
arrow buttons to perform the copy operation. Clicking the right arrow copies the checked
17-9
library objects to the GeoWorkspace. Clicking the left arrow copies the checked
GeoWorkspace objects to the library.
After copying, a glyph (like the Explorer glyph for a shortcut) is added to the icons to
indicate that the same object resides in both the GeoWorkspace and the library, that is, the
object in the GeoWorkspace is a copy and a reference of one in the library.
These glyphs are added in pairs - one in each treeview - to indicate the associated objects.
This visual cue enables you to easily refresh the state of common objects.
The Select Reference button lets you check such common objects to easily refresh all
common objects. When you click this button, the Overwrite option is automatically
selected, and you perform a basic refresh that automatically selects all of the referenced
items in both the library and GeoWorkspace treeviews. You can perform a copy operation
to the active GeoWorkspace as a way of refreshing the state of referenced items in the
active GeoWorkspace. An administrator can also perform a copy operation to the library
to refresh the library contents. Furthermore, after a successful copy, rename, or delete
operation, the command refreshes the GeoWorkspace and the library appropriately.
You can also choose the behavior when an object with the same name as an object to be
copied already exists. By default, copy works with the Overwrite option, which
overwrites the existing object instances (except for connections), if any, in the target space.
The Copy with new name option lets you append the existing instances in the target object
space. If an object with the same name exists in the target object space, an incrementing
digit is added to the end of the name so as not to conflict with the existing object. Finally,
the read-only Description field displays the description of the currently highlighted object
if it has a description.
In copying to the library, it is possible that updating (that is, overwriting) an existing object
instance in the library has an implication of version conflicts. While overwriting an object
instance in the library, the command does the following:
• If the object instance in the library is not updatable, then:
o In the case of single object copy, the command displays an error message.
17-10
o In the case of bulk mode, the command continues to copy the objects that are
updatable, and displays an error message after completing the copy process.
• If a lower version of the object instance (or its references) in the library is being
updated, the command displays an error message as needed and proceeds based on
your response.
In copying from the library, if the object instance being copied is not loadable, then:
• In the case of single object copy, the command displays an error message.
• In the case of bulk mode, the command continues to copy the objects that are loadable,
and displays an error message after completing the copy process.
Because a library can contain objects that are not version-compatible with the version of
object type currently registered on the target system, this command displays overlay icons
on the primary icons in both the Library contents and the GeoWorkspace contents
treeviews based on the version compatibility status of the library objects, as follows:
• If the compatibility status is read-only or read-write, no overlay symbol is displayed.
• If the compatibility status is read-write backward, the updatable overlay symbol ( ) is
displayed.
• If the compatibility status is incompatible, the incompatible overlay symbol ( ) is
displayed.
To organize libraries:
1. Select Tools > Library Organizer.
17-11
2. Select the appropriate Library connection from the drop-down list.

The available library and GeoWorkspace contents are displayed.
3. Select the Copy with new name option.
4. Select one or more objects in GeoWorkspace contents that do not exist in the active
library; then click the left-arrow button (<) to copy to the active read-write library.
During the copy process, the status bar is updated.

5. Select one or more objects in the GeoWorkspace contents that already exist in the
active library; then click the left-arrow button (<) to copy to the library.
During the copy process, the status bar is updated. All the selected objects are
appended to the same position within the folders of active read-write library as it
occupied in the GeoWorkspace with a decorated name.
6. Select the appropriate If an item exists with the same name option, Copy with new
name or Overwrite.
7. Click Select References to select the items common to the library and to the active
GeoWorkspace.
8. Click the right-arrow button (>) to copy the selected items to the same position within
the folders of active GeoWorkspace as they occupied in the library.
9. Edit the objects as necessary.
10. Click on left-arrow button (<) to copy the selected items back to the same position
within the folders of the active read-write library as they occupied in the
GeoWorkspace.
11. To delete, select one or more objects in the active library; then click Delete.
During the delete process, the status bar is updated.
12. To rename, select one object in the active library; then click Rename.
13. Type a new name not existing in the hosting collection of the library; then click OK.
17-12
Note: The name should not contain the character ‘|’(OR), and length of the name
should not exceed 255 characters.
14. Click Close to exit Library Organizer.
Note: Internally, the libraries make use of the | character. This character is considered
reserved, do not use it in any GeoMedia object that you want to store in the library.
17-13
17-14
Exporting Data to Other Systems
GeoMedia provides commands for exporting data to other GIS. You can export the
following:
• Feature data into shapefile (.shp) format.
• Feature data into MapInfo Interchange Format (.mif /.mid)
• Feature geometry and attribute linkage into MicroStation design file (.dgn) format.
• Feature geometry and attribute data into AutoCAD .dwg or binary .dxf format or
ASCII .dxf format.
• Feature geometry and attribute data into GML format.
Exporting to Shapefile
Use the Export to Shapefile command to export feature data (geometry and attributes) ,
including categories and reference features, from any read-write or read-only warehouse
connection into shapefile format. You can select any mixture of feature classes, queries,
categories, and reference features, across any number of connections. This command
outputs dBase IV version 2.0 and ArcView version 3.0 compatible files.
Export to Shapefile supports null geometry and arcs (converted to polylines). For
compound feature class, the command exports only the geometries of the geometry type
you select: point, line, area (the default), or all. If you specify that the compound features
are to be exported to all three shape file types, three shape files are created in the output
folder, one each for point, line, and area geometry types. The names of the output files are
suffixed by the geometry type names. Arcs and composite polylines are converted to
stroked polylines, and composite polygons are converted to polygons. This command also
lets you export the rotation angle when you are exporting a feature class with oriented
point geometry. Text feature classes cannot be exported because the shapefile format does
not support them.
You can create a new shapefile or append to an existing one. When appending to an
existing shapefile, the feature-class definition of the features being exported and the
shapefile to which you are exporting data must be identical because a shapefile can contain
only a single feature class. By default, this command appends to any existing shapefile(s)
present in the output subfolder. If any error is found during appending, it is reported in the
log file.
When exporting a feature class with Oriented Point geometries, the orientation information
is preserved by adding a numeric field to the output shapefile definition. This extra field is
not added only when DWORD value AVExportPreserveRotation under the registry key
18-1
“HKEY_LOCAL_MACHINE\SOFTWARE\Intergraph\Applications\” is present and is set

to 0. This additional field, named GMRotation, can then be associated to the exported
point geometry in the output shapefile through an ArcView .avl file. This field contains
the angle value representing the orientation of the point in decimal degrees relative to
horizontal. Positive angles represent a counterclockwise rotation from horizontal, and
negative angles represent a clockwise rotation from horizontal. The valid range of the
angle values is –360 to +360.
By default, point feature classes with or without collections are exported as
MultiPoint/MultiPointZ shape type. When DWORD value
“AVExportPointAsPointShape” under the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Intergraph\Applications\ is present and set to 1
(non-zero), the export point features are forced to be exported as Point/PointZ shape type,
instead of MultiPoint/MultiPointZ.
The Text encoding drop-down list lets you specify the text encoding format used to
encode the destination text field values from the following formats:
• ANSI (the default)
• Unicode (UTF-8) - (UTF-8, use variable number of 8-bit sequences)
• Unicode (UTF-16) - (UTF-16 Little Endian, Windows default)
• Unicode (UTF-16BE) - (UTF-16 Big Endian)
The coordinate system of the exported shapefile is determined by the GeoWorkspace
coordinate system. Therefore, to export the shapefile into a different coordinate system,
you must use the GeoWorkspace Coordinate System command to change the
GeoWorkspace coordinate system. The coordinate system of the exported shapefile is
written to the output folder, in the Export.csf file.
The warehouse configuration file (.ini) is also written in the output folder with
“COORDINATE SYSTEM”, “TEXT ENCODING”, “SERVE NUMERIC WIDTH AS
INTEGER”, “SERVE NUMERIC WIDTH AS LONG”, and “SERVE NUMERIC WIDTH
AS SINGLE” keywords as per the export settings. “SERVE NUMERIC WIDTH AS
INTEGER”, “SERVE NUMERIC WIDTH AS LONG”, and “SERVE NUMERIC WIDTH
AS SINGLE” keywords are included based on the presence of DWORD values
“AVExportIntegerWidth”, “AVExportLongWidth” , and “AVExportSingleWidth” under
the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Intergraph\Applications\,
respectively. The name of the file is the same as the output folder name. When export is
performed to a root folder, the name of exported file is Export.ini.
You also have the option to export 3-D coordinate information or not; the default is to
export 2-D coordinate information. Additionally, you can specify whether coded PickList
values need to be exported as descriptions if PickList fields are present in the selected
features. The default is to not export them.
For each feature class/query, the following three output files are created during export:
• <FeatureclassName>/<QueryName>.shp
18-2
• <FeatureclassName>/<QueryName>.shx
• <FeatureclassName>/<QueryName>.dbf
Note: The ExportToShapefileService object outputs main (.shp) files and index (.shx) files
in conformance with the “ESRI Shapefile Technical Description - an ESRI White Paper –
July 1998”, and dBASE table (.dbf) files in conformance to dBase IV Version 2.0 and
ArcView Version 3.0 compatible file formats. Furthermore, in shapefiles, attribute data is
stored in a DBF file. Truncation of attribute names to 10 characters is not a limitation of
the export service; it is enforced by the dBase IV Version 2.0 DBF file format.
The default output folder to which the exported shapefiles are to be written is taken from
the GeoMedia \Warehouses folder specified on the File locations tab (Tools > Options);
however, you can specify another output folder. The feature classes of that connection or
queries are exported to the specified output folder. The command does not allow exporting
from multiple connections in a single export operation.
For each export operation, this command generates a log file (Export.log) in the output
folder. If this file already exists, the log information is appended.
To export data to shapefile format:

1. Connect to the existing warehouse from which you want to export data.
2. Select Warehouse > Export to > Shapefile.
18-3
3. Select the appropriate items from the Features to export treeview.
Note: Holding the cursor over an entry displays a tooltip describing the geometry
type.
The default path of the file to contain the exported data is taken from the \Warehouses
folder and displayed in the Export folder field.
4. Optional: Change the default path of the warehouse folder in the Export folder field.
5. Select the appropriate Output geometry type for the highlighted features option.
Note: These options are enabled only when a treeview entry is highlighted. For
feature classes/queries of the compound geometry type, all the options in the frame are
enabled (with Area as the default), and for other feature classes/queries, only the
corresponding geometry type is enabled.
6. Check the appropriate Export options check box(es).

7. Select the appropriate format from the Text encoding drop-down list.
8. Click Apply to begin exporting.
18-4
If the Append to existing shapefile(s) check box is not checked, and if the shapefile for
at least one feature class already exists in the export folder, a confirmation message is
displayed stating that at least one output shapefile will be overwritten, asking if you
want to continue. If you do, the existing shape files is overwritten; otherwise, the
export process does not take place.
If the Append to existing shapefile(s) check box is checked, and if the shapefile for at
least one feature class already exists in the export folder, a confirmation message is
displayed stating that at least one output shapefile will be appended, and asking if you
want to continue. If you do, the existing shape files is appended (only when the feature
class definition of the input feature class record set must match that of the existing
output shapefile); otherwise, the export process does not take place.
If the Export picklist values as descriptions check box is checked, the command
removes the coded picklist value fields and replaces them with the corresponding
description fields.
After completing the export process without any warnings or errors, the Export
complete message is displayed.
9. Continue the export process until complete; then click Close to dismiss the Export to
Shapefile dialog box.
Exporting to MapInfo Interchange Format

Use the Export to MapInfo Interchange Format to export feature data (geometry and
attributes) from any read-write or read-only warehouse connection into MapInfo
Interchange Format files (.mif and .mid) that are compatible with MapInfo Professional 4.5.
You can create a new MapInfo file, but you cannot append to or edit an existing one. The
selected feature class will be written to the .mif (graphics) and .mid (database) files in the
specified folder.
Simple arcs are exported as arcs. However, arc geometry is stroked when present in
compound features and exported.
The following list describes characteristics of MapInfo that impact the exported files:
• Geometry data is exported using the Geographic coordinates (base storage type
Geographic in terms of a horizontal storage unit of 1 decimal degree using geodetic
datum WGS84 with no shifts) or the GeoWorkspace coordinate system. A MapInfo
Interchange Format file (.mif) is an editable text file that contains a section for defining
the coordinate system. Export to MapInfo Interchange Format does not populate
this section.
If no coordinate system is specified in the .mif file MapInfo assumes that the
coordinate system is Geographic with degrees as the unit. If you chose to export the
geometry data using the GeoWorkspace coordinate system option and your
GeoWorkspace was set to a different coordinate system during the export process, you
18-5
must enter the correct coordinate system information in the .mif file before importing it
into MapInfo.
Export to MapInfo Interchange Format in such a case creates a GeoMedia .csf file
containing the coordinate system information of the exported data with the same root
name as the output .mif file, which you can use as a reference when creating the
coordinate system entry in the .mif file. See MapInfo documentation for information
on the .mif format and how to populate the coordinate system information.
• MapInfo does not support point-collection geometries (a single feature consisting of
multiple-point geometry), so each point is exported as an individual feature. The
attributes of the entire collection will be replicated for each exported point of the
collection.
• The MapInfo file format does not support gdbmemo field types. Export to MapInfo
Interchange Format exports these fields as normal character type, and they are
truncated to 255 characters.
• Hypertext is treated as normal character type and is truncated to 255 characters.
• Export To MapInfo Interchange Format generates MIF and MID files that
are compatible with MapInfo Professional 4.0.
The following table defines the MapInfo geometry generated from each of the GeoMedia
geometry types:
GeoMedia Geometry MapInfo Description
Type Geometry
Point Point Point
Line Line Line
Arc Arc Arc
Polyline Polyline Polyline
Polygon Polygon Polygon
Composite Polyline Multipolyline A collection of linear features
(polylines only). Arcs in composite
polylines are stroked during
export.
Composite Polygon Polygon Arcs in GeoMedia are stroked
before export.
Boundary Geometry Region/Multipolyg Region object contains collection
on of polygons with or without
corresponding holes.
Text Geometry Text Geometry Graphic Text
18-6
Point Collection Individual Points MapInfo does not support

collection of points.
Linear Feature Collection Multipolyline Previously defined. See
Composite Polyline.
Areal Feature Collection Region/Multipolyg Previously defined. See Boundary
on Geometry.
Heterogeneous collection As individual MapInfo does not support
(point, line, and/or area features collection of heterogeneous type.
together)
To export data to MapInfo Interchange Format:

2. Select Warehouse > Export to > MapInfo Interchange Format.
3. Select the feature class or query to be exported using the Features to export drop-
down list. You can export only one feature class at a time.
4. In the Export to field, select or type a filename to contain the exported data.
5. Select the appropriate Export geometry data in coordinates option.
6. Click Apply to begin exporting.
Note: Different feature classes and queries can be exported by selecting the feature
class or query and clicking Apply in a single session.
If the filename already exists, you will be prompted to replace. If a new filename was
entered, a new MapInfo file is created.
The following message appears after export: Selected feature class exported.
7. If you select the GeoWorkspace coordinate system option and the GeoWorkspace
coordinate system base storage type is not Geographic or the horizontal storage unit is
not in terms of 1 decimal degree (using geodetic datum “WGS84” with no shifts), enter
18-7
the coordinate system information in the .mif file. For example, if the coordinates are
in meters, the coordinate system is projected, and the projection algorithm is 'State
Plane Coordinate System 1983 (102 – Alabama West)' using the datum North
American 1983, then the coordinate system information should be set to "CoordSys
Earth Projection 8, 74, "m", -87.5, 30.0, 0.9999333333, 600000, 0".
8. Click Close to dismiss the dialog box.
Note: After using this command, you must use the Import command in MapInfo in
order to use the output created from Export to MapInfo Interchange Format.
Exporting to Design File

The Export to Design File command lets you export the primary geometry field of
multiple feature classes/queries, including categories and reference features, and attribute-
linkage data from any read-write or read-only warehouse connection into design file (.dgn)
format, MicroStation® Version 4 files. This format can be either MicroStation V7 or
MicroStation V8. This command writes the selected feature classes/queries to the design
files (new, append, or overwrite) that you specify. Writing to a new file requires a graphic
seed file to write the required header information in the creation of the output design files,
which provides the coordinate system for the output files. Appending causes the old files
to be appended and new files to be freshly created. Overwriting causes the old files to be
overwritten and the new files to be freshly created. With this command, you can only
export from one warehouse at a time, or from queries in one run, and each warehouse in
following runs. Append lets you output several runs to the same design file.
See “Element Types” at the end of this section for a table of the IGDS element types
generated from each of the GeoMedia geometry types:
When exporting to MicroStation V8 format, the input data are transformed to the
GeoWorkspace coordinate system. When exporting to MicroStation V7 format, the input
data are transformed to the seed file coordinate system. If the seed file does not contain a
coordinate system, the input data are transformed to the GeoWorkspace coordinate system.
In either case, an accompanying .csf file is generated in the same folder as the output file(s)
that represents the coordinate system used during the transformation. When only one
output file is produced, the name of the generated .csf file is the same as the name of the
output file, but with a .csf extension. When multiple output files are produced, only one
.csf file, named ExportDGN.csf, is generated.
This command lets you export different sets of feature classes to different files in the same
export session. You can use the feature class name or query name as the output design
filename for the exported features, or export all features to a single design file. You can
also assign the symbology (graphic and text properties) individually based on the geometry
type to all the selected feature classes/queries; otherwise, the default values are taken.
You can have additional data in the seed file, which will be copied into the output file. In
the case of MicroStation V7 format, GeoMedia’s double precision floating-point
18-8
representations of values are stored in the target design file as design file positional units.
The default seed file folder is pointed to the ..Templates\ExportToDGN folder.
See “Notes on Seed Files” later in this section for information on seed files, including
those delivered with the product.
For exporting text and symbol features, the font has to be chosen from the MicroStation
font resource files (.rsc). For exporting points as cells, with the MicroStation V7 export
format only, the MicroStation cell library filename has to be chosen.
To optionally set attribute-linkage information to be exported, you must select the
MicroStation V7 export format and specify the seed file, output file, and feature class to
export. The exporting of attribute-linkage data can be useful in many ways. For example,
a design file can be exported to be used with a database in MicroStation or with an
application built on top of MicroStation. Applications can read the linkages on the design
file elements and associate a record in the database with the element in the design file.
The Export to Design File dialog box is has two tabs. On the General tab, you first set
global settings, that is, input data common to all the feature classes to be exported, from the
Select features to export treeview. This selection can be of any mixture of feature
classes, queries, categories, and reference features, across any number of connections. You
also select the graphic properties for individual queries and feature classes, and linkage
properties (if applicable).
Next, you add the selected feature class/query to the Features to export grid with the
assigned graphic properties. This grid reflects the current state of feature class-to-
properties associations. You can select multiple feature classes/queries to add, in which
case all the items are loaded into the grid. If you have already defined the graphic
properties for the feature classes/queries, the selected items have those properties when
added to the grid. Otherwise, the feature classes/queries are loaded with the default
settings.
18-9
Integer fields for the feature or query can be used to define values for color, weight, style,
and fill color of the output graphics. These are the Graphic properties fields with a pull-
down list beside them. You can either type a value or select an integer column.
The export grid is read only; it cannot be edited. However, you do have the option to
remove a selected feature class/query row from the grid. To change the properties for any
feature class/query, you must select it in the feature classes/queries control and change the
properties, which then are automatically updated in the grid. Changing the connection or
selecting queries clears any items entered into the grid. Returning to the original
connection does not restore the original contents of the grid because you can only export
from a single connection at a time. The graphic properties for previously defined feature
classes are retained so that you do not have to redefine them if they are added to the grid
again.
You have the option to save the contents of the grid to a settings file (a user-specified XML
file). This file can contain properties for feature classes from multiple connections. You
can also append to an existing file when saving. However, when loading this settings file,
its contents only apply to the feature classes in the currently selected connection. Only the
feature classes whose name and geometry type match with those in the settings file will be
added to the grid. However, referenced attribute names need not match. If a referenced
attribute is not present, or has a NULL value, the appropriate default value will be applied
during processing. The missing attribute name will be displayed and saved unless you edit
the value. Substitution of the default value is an execution-time behavior. Thus, for
example, if you have selected Access Connection 1 and had previously saved settings for
roads and rivers from Access Connection 1, and then appended Alleys and parcels from
Access Connection 2. When this settings file is loaded, the properties for roads and rivers
are added to the grid as Access Connection 1 is selected. To see the settings for Alleys and
18-10
parcel, Access Connection 2 has to be selected. In this way you can generate a single
settings file containing definitions for all feature classes and queries originating in multiple
connections, and they all are available, regardless of which connection is selected; but only
the pertinent ones for the selected connection are shown.
When you load the contents of a settings file, they are applied to the feature classes in the
selected connection/queries. If those feature classes/queries are selected to export, the
graphic properties from these settings are applied to the selected feature classes/queries
while exporting. For example, if you load a settings file containing settings for roads,
rivers, and states, these feature classes are added to the grid, and when any of those feature
classes are selected in the feature classes/queries list or the grid, the graphics properties
reflect the loaded settings. If you select a different connection containing roads, rivers,
and states, the graphics properties still reflect the loaded settings as the association is based
on feature class or query name.
To export to a design file, saving the grid settings:

2. Select Warehouse > Export to > Design File.
3. On the General tab, select the appropriate Export format option.

4. Select the appropriate Output file option.
5. For Use feature class or query name as output design file, browse for the
appropriate folder for the Folder field.
18-11
OR
For Output all feature classes to a single design file, browse for the appropriate
filename for the Filename field. (The default is Export.dgn.)
6. Check the Append to existing design files check box to append all existing files;
when unchecked, the existing files are overwritten.
7. In the Graphic seed file name field, type or select the name of the seed file to be used
in the creation of the output design files. (This field requires the complete path to the
seed file that you want to use as the starting point of the output design file.)
8. For text or symbols only, in the Resource file name field, type or select the resource
filename (.rsc).
9. Optional: To export points as cells, for MicroStation V7 format only, type or select
the filename in the Cell library name field.
10. Select the Criteria tab; then select the appropriate items from the Select features to
export treeview.
The Graphic properties controls are enabled based on the geometry type of the
selected feature class/query. Selecting multiple feature classes/queries disables the
edit controls. If the selected feature class is already added to the grid, the
corresponding item in the grid is highlighted.
11. Select the appropriate Graphic properties.
18-12
12. Optional: Click Attributes; then check the Add linkage check box.
13. Check the Add linkage check box.

14. Type the appropriate value in the Entity number field.
15. Select the appropriate value from the Linkage type drop-down list.
16. Select the appropriate value from the Occurrence number drop-down list; then click
OK to save the linkage values for the selected feature class/query.
17. Click Add.
The selected feature class/query is added to the features to Features to export grid
with the graphic properties assigned in Step 11, or if none were assigned, with the
default values.
18. Optional: Select a feature class/query in the Features to export grid; then click
Remove to remove it from the grid.
19. Click Save As; then select or type the appropriate filename to save the settings to.
The contents of the grid are saved to a settings file (a user-specified XML file). If an
existing settings file is selected, you are prompted to overwrite or append and update.
20. Click Apply to start the export process.
All the feature classes/queries are exported from the Features to export grid, with the
settings in the grid.
If the Use feature class/query name as output design file name option is selected, all
the feature classes from the grid are exported to their respective design files into the
specified folder.
If the design file already exists, and if the Append to existing output files check box is
checked, the existing design files are appended. If unchecked, the existing files are
deleted, and a new design file with the same name is created using the specified seed
file.
If a new filename was entered with the Output all features to a single design file
option, the design file is created using the seed file specified and opened for export.
When exporting to MicroStation V8 format, the input data are transformed to the
GeoWorkspace coordinate system. When exporting to MicroStation V7 format, the
18-13
input data are transformed to the seed file coordinate system. An accompanying .csf
file is generated in the same folder as the output file that represents the coordinate
system used during the transformation.
The message Export complete is displayed once all the selected feature classes are
exported. The dialog is not dismissed, and all the output files are closed.
Note: Pressing ESC aborts the export processing and results in exporting up to the
current record and closing the output file.
To export to a design file without saving the grid settings:

3. Set the appropriate items on General tab.
4. On the Criteria tab, select a connection or queries.
5. Select a feature class/query.
The default Graphic properties are displayed.
6. Optional: Change the graphic properties.
7. Click Add.
The feature class/query is added to the Features to export grid with the specified
properties.
8. Repeat Steps 3-7.
Note: You can select multiple items and add them to the grid together. In this case,
they all get the default properties, if you have not edited any of those properties.
9. Click Apply to export the items in the grid.
To export to a design file, loading the grid settings:

3. Set the appropriate items on General tab.
4. On the Criteria tab, select a connection or queries.
5. Click Load; then select the appropriate settings filename to load.
The settings are loaded, and all the matching feature classes from the selected
connection/queries are added to the grid with the graphic properties from the
18-14
symbology settings file. The settings are loaded into memory and are available when
appropriate.
6. Select a feature class/query.
If the feature class/query name was among the settings previously loaded, the graphics
properties are updated to reflect these settings.
7. Click Add.
The feature class/query, if not already added to the grid, is now added to the grid with
the defined properties.
Note: The load operation merely seeds the values for the dialog box, so you can
change the graphic properties (not on the grid) if appropriate. Such changes are
remembered until the dialog box is dismissed. To save them permanently, click Save
As so that the grid settings are saved.
8. Click Apply to export the items in the grid.

9. Select another connection.
The grid is cleared, and the matching feature classes from the new connection are
added to the grid.
10. Select a feature class.
If the name matches a name in the loaded settings file, the graphic properties are
populated from the loaded file. If not, the default properties are displayed.
11. Click Add.
The feature class/query, if not already added to the grid, is now added to the grid with
the defined properties.
Note: At this point you can edit the contents of the grid by selecting the feature class
in the list box (or the grid) and modifying the properties. The modification is
automatically reflected in the grid. You do not have to click Add again to update the
grid. he grid reflects the current setting of the particular feature class.
Notes on Seed Files

• The first time you run Export to Design File, the default seed file will be seedgeo.dgn
for MicroStation V7 format and seedgeo_v8.dgn for MicroStation V8 format. This
seed file is a 2-D geographic file that uses the WGS84 geodetic datum, which is
delivered with the product along with three other seed files.
18-15
• For MicroStation V7 export, if a coordinate system (type-56 element) has not been
defined for the seed file used, the output design file will be created in the same
coordinate system as the current GeoWorkspace. In this case, GeoWorkspace double-
precision geometry coordinates will be copied (after rounding off) to the integer UORs
of the resultant design file graphic elements. Therefore, it is important to set the
GeoWorkspace Storage Space resolution (select View > GeoWorkspace Coordinate
System, on the Storage Space tab under Advanced Parameters) so that no great loss
of precision in the data will occur. For example, if a seed file with no type-56 element
is used, and if the GeoWorkspace horizontal resolution is set to one meter, then the
resultant design file graphic elements could have no finer precision than one meter. If
this is unacceptable, you could select a horizontal resolution of one centimeter.
In transforming the data from a GeoWorkspace to a design file, the command performs
the following workflow in the absence of a type-56 element in the seed file:
− Uses the type-9 element (design file header) of the seed file, which is always
present irrespective of whether the type-56 element is present or not.
− Gets Master Units (mu), Sub Units (su), and Positional Units (pu) from the type-9
element, and sets up storage parameters accordingly.
− Sets the projection algorithm to undefined, which the legacy code calls rectangular
grid.
− Sets the horizontal/vertical resolution based on the master unit (mu) of the seed
file.
Using this information, the command makes the required transformation equation to
transform GeoWorkspace coordinates to the corresponding seed file. Because the
projection is undefined or rectangular grid, no transformation actually takes place, but
the conversion of coordinate values to their corresponding UOR equivalents occurs.
This is actually a scaling activity resulting in less precise data, sometimes, because of
the rounding off activity to make UORs.
• If you select a 3-D seed file, then the output will be 3-D. If you select a 2-D seed file,
then the output will be 2-D.
• Eight seed files are delivered with the product in the <drive>\Program
Files\GeoMedia\Templates\ExportToDGN folder. The MicroStation V7 seed files
each contain a type-56 element that defines the coordinate system information
(projection, geodetic datum, and so forth) for that seed file.
− seedgeo.dgn is defined as a 2-D geographic coordinate system with a WGS84
geodetic datum (which matches the default GeoWorkspace coordinate system).
− seedgeo_v8.dgn is defined as a 2-D geographic coordinate system with a WGS84
geodetic datum (which matches the default GeoWorkspace coordinate system) for
MicroStation V8.
− seedzgeo.dgn is a 3-D version of the seedgeo.dgn file.
− seedzgeo_v8.dgn is a 3-D version of the seedgeo_v8.dgn file for MicroStation V8.
18-16
− seedprj.dgn is defined as a 2-D projected (Cylindrical Equirectangular) coordinate

system with a WGS84 geodetic datum.
− seedprj_v8.dgn is defined as a 2-D projected (Cylindrical Equirectangular)
coordinate system with a WGS84 geodetic datum for MicroStation V8.
− seedzprj.dgn is a 3-D version of the seedprj.dgn file.
− Seedzprj_v8.dgn is a 3-D version of the seedpr_v8j.dgn file for MicroStation V8.
Element Types
The following table defines the IGDS element types generated from each of the GeoMedia
geometry types:
GeoMedia IGDS Element Type Number
Geometry Type
Point Symbol / Degenerate line / Shared cell instance 17 / 3 / 35
(only for MicroStation v7 format)
Text Text 17
Line Line 3
Linear Linestring or complex linestring 4 or 12, 4, 4, …
Area Shape or complex shape 6 or 14, 4, 4, …
Compound One or more of the previously defined types based 3, 4, 6, 12, 14
on the content of the collection. The elements are and/or 17
assigned the same graphic group number in order
to maintain their group identification.
Exporting to AutoCAD
Use the Export to AutoCAD command to export spatial data from any read-write or read-
only warehouse connection into AutoCAD Release Version 14 .dwg, or binary .dxf, or into
ASCII .dxf format. This command writes the selected feature class to a new output file in
the folder you specify, overwrites the data in an existing file, or appends the data to an
existing .dwg or .dxf file.
This command lets you set the layer name by either typing or selecting it from the existing
drawing file in append mode, or you can specify an attribute field from the input feature
class by selecting By attribute from the Layer name drop-down list. Selecting this option
enables the Attribute name drop-down list for you to select an existing attribute. Each
new layer name created during a feature class export is also available as an existing layer
name for subsequent exports in a session.
Additionally, you set the layer visibility parameters, that is, whether the layer is on or off,
frozen or thawed, and locked or unlocked. If the layer is on, objects on that layer are
visible. When a layer is off, objects on that layer are invisible and do regenerate. If the
layer is frozen, objects on that layer are invisible and do not regenerate during zoom and
pan operations, thus improving object selection performance and reducing regeneration
18-17
time for complex drawings, whether the objects in the layer are editable or not. If a layer is
locked, all of the objects on that layer are not editable or locatable, but they are visible.
You can also set the AutoCAD graphic and text properties. Graphic properties include line
type file name; line type name; and line width, thickness, and color. Text properties
include text style name, font name, color, and height.
Export to AutoCAD lets you export in the following two ways:
• Export attributes—Exports attribute information in the input feature class as extended
data to the corresponding entity in the output .dxf or .dwg file, or as block attributes
and all the geometries (of any type) as BLOCKs in the output .dxf or .dwg file. The
default is to not export the attribute information for each graphic object.
In addition, you can export attribute information as database linkages. This option
exports only the linkage information to the output drawing file, not the actual attribute
data. Selecting this option enables the Linkage Details button to display the Linkage
Details dialog box, which lets you set the values used to write the linkage information
to the drawing file.
See the corresponding topic in GeoMedia Help Topics for information on this dialog
box.
• Export 3D coordinates—Exports 3-D or 2-D features; the default is 2-D (unchecked).
If you are exporting a point feature class/query or a compound feature class/query as block
references, you have the option to specify the following:
• Block AutoCAD drawing filename (.dwg or .dxf).
• Block name from all the block names available in the specified block drawing file and
the output file (in append mode), along with a special block name DWGFilename that
indicates the entire block drawing file is to be exported as a single block definition. If
the block drawing file already contains a block with the name DWGFilename, the
block name listed refers to the block within the file, and not the entire drawing file.
18-18
Note: If the DWGFilename exceeds 26 characters in length, it is truncated to 26

characters. All the special characters within the DWGFilename that are not allowed for
a block name (like the space character ‘ ’) are replaced with an underscore character
‘_’.)
• Block scale factor, which can be any positive value. This scaling value, with the
orientation of the point geometry, is applied on the specified block while exporting the
point features. The default value is 1.0.
In the export process, the input features are transformed to the GeoWorkspace coordinate
system. Also, an accompanying .csf file is generated in the same folder as the output file
that represents the coordinate system used during the transformation. The name of the
generated .csf file is the same as the name of the output file, but with a .csf extension.
To export data to AutoCAD:

2. Select Warehouse > Export to > AutoCAD.
3. Select the appropriate feature class/query from the Features to export drop-down list.
Note: The dialog box items enabled or disabled vary depending on whether you select
for export a linear or an area feature class or query or select a compound or text feature
class or query.
18-19
4. In the Output file name field, if an output filename other than the default (selected
feature class name with default .dxf extension in the warehouse location) is required,
select or type the name of a file to contain the exported data.
5. Select the appropriate Output file type option.
6. Select the appropriate Output file mode option.
Note: The Output file mode options are enabled only if the output file name is an
existing file.
7. Optional: Check the Export attributes check box; then select the appropriate
attribute option.
If you select As database linkages, click Linkage Details; then set the appropriate
values on the corresponding dialog box.
8. Optional: Check the Export options / 3D coordinates check box.
9. In the Layer name drop-down list, if a layer name other than the default (selected
feature class name) is required, select or type the name of a layer to contain the
exported data.
If you select By attribute from the Layer name drop-down list, select the appropriate
existing attribute from the Attribute name drop-down list.
10. Set the appropriate layer visibility check box(es): Layer on, Layer frozen, and/or
Layer locked.
11. If a line type other than the default CONTINUOUS is required, select or type an
AutoCAD line type filename (.lin) in the Line type file name field.
12. Select the Line type name from the drop-down list.
13. Type the appropriate values in the Line width, Color, and Thickness fields.
14. If you are exporting text features, if a text style other than the default STANDARD is
required, select or type an AutoCAD text style name in the Text style name field.
15. Type the corresponding text font name (.shx) in the Text font name field.
16. Type the appropriate values in the Text color and Text height fields.
17. Optional for point or compound feature/query: Check the Export point as block
reference check box; then type or select the appropriate Block drawing file name.
18. Select or type the Block name; then type the Block scale.
19. Optional: Check the Export 3D coordinates check box.
20. Click Apply to export the data.
18-20
The features are exported and transformed to the GeoWorkspace coordinate system.
An accompanying .csf file is generated in the same folder as the output file that
represents the coordinate system used during the transformation.
21. Continue the export process until complete; then click Close to dismiss the Export to
AutoCAD dialog box.
Exporting to GML
Use the Export to GML command to export feature class geometry and its attribute data
to GML (Geography Markup Language) format. The selected feature classes (including
queries, categories, and reference features) are written to a GML Version 2.1.2, 3.0, 3.1.1
GML data file (.gml), and the corresponding XML Schema definition is written to the
GML Version 3.2 base schema GML schema (.xsd) file. This command exports all
supported feature and geometry types with no data loss including but not limited to arcs,
compound geometry, composite geometry, and graphics text. You should use this
command as a tool for migrating data from any data store accessible by GeoMedia to a
GML data file and a GML schema file.
To use this command you select any mixture of feature classes, queries, categories, and
reference features, across any number of connections. You also specify an appropriate
target coordinate system file for the export process. The command transforms the input
data to this coordinate system as the data is exported. In addition, you can swap, that is,
reverse, the order of the coordinate values reversed during the export process.
The coordinate system in GML data is identified using an EPSG code, and the
Georeference service (GRS) provides a valid EPSG code for a coordinate system. This
command transforms and exports the data in the GeoWorkspace coordinate system or in a
user-defined coordinate system, depending on the two Target Coordinate System options
on the command dialog box.
• Use GeoWorkspace coordinate system—This option exports the data in the
GeoWorkspace coordinate system. The default state of the this option to use the
GeoWorkspace coordinate system as the target coordinate system depends on GRS and
the GeoWorkspace coordinate system. This option is enabled and selected if GRS
returns a valid ESPG code for the GeoWorkspace coordinate system, and the input data
is then transformed to this coordinate system as the data is exported. If GRS does not
return a valid ESPG code, this option is disabled, and you must use the second option.
• Use the coordinate system file—This option transforms the input data from the
GeoWorkspace coordinate system to the target coordinate system specified in the
coordinate system file field. The coordinate system file must be an EPSG-named
coordinate system file, that is, EPSGxxxxx.csf, where xxxxx can be any positive integer,
and must be present in the \EPSG folder under the location where the host
product is installed. GRS provides a valid EPSG code for this file, and the input data
is then transformed to this coordinate system as the data is exported. This option is
18-21
always enabled and is by default selected if GRS does not return a valid SPG code for
the GeoWorkspace coordinate system.
This command outputs one GML data file and one GML schema file per export operation.
The default names are GMLData.gml and GMLData.xsd, respectively. The default
location for both is the GeoMedia \Warehouses folder. You can, however, change these
names and locations as needed.
The GML data file and the GML schema file contain all the selected feature classes with
names as follows:
• Feature Class: <feature class name> • Categorized Item: <item name>
• Query: <query name> • Reference Feature: <feature class name>
You also set the following other parameters before exporting.
• The appropriate GML version that is exported, by default, GML version 3.1.1.
• The namespace and the prefix for the output GML data/schema file in the format:
xmlns:<prefix>=’<uri>.
See the next section for more information on prefixes.
• The location and name of the GML base schema file.
• Whether or not the bounding box is output for every record in the output GML file.
• Whether or not the sequence of fields output in the GML data/schema file is the same
as that of the input feature class/query.
• Whether or not the 3-D coordinates are exported in the GML data file.
• Whether or not to swap the order of the coordinate values during the export process.
Using Prefixes
When a recordset is exported in GML with default settings, the default namespace (or
target namespace) for an application schema is taken as
"xmlns:gmgml='http://www.intergraph.com/geomedia/gml'" and so the schema and data
are encoded using the "gmgml", which refers to the target namespace.
The following is an example excerpt taken from the output GML file exported using the
default settings:
<gmgml:FeatureCollection xmlns="http://www.intergraph.com/geomedia/gml"
xmlns:gml="http://www.opengis.net/gml"
xmlns:gmgml="http://www.intergraph.com/geomedia/gml"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation='http://www.intergraph.com/geomedia/gml d:\warehouses\GMLData.xsd'>
<gml:boundedBy>
<gml:Envelope srsName="EPSG:4269">
<gml:lowerCorner>34.665793 -86.776129</gml:lowerCorner>
18-22
<gml:upperCorner>34.777847 -86.564569</gml:upperCorner>
</gml:Envelope>
</gml:boundedBy>
<gml:featureMember>
<gmgml:Exit gml:id="Exit.1">
<gmgml:FROM_NAME>STATE HWY 255</gmgml:FROM_NAME>
<gmgml:EXIT></gmgml:EXIT>
<gmgml:TO_NAME>STATE HWY 255</gmgml:TO_NAME>
<gmgml:ID>1</gmgml:ID>
<gmgml:Geometry>
<gml:Point srsName="EPSG:4269">
<gml:pos>34.777847 -86.672915</gml:pos>
</gml:Point>
</gmgml:Geometry>
</gmgml:Exit>
</gml:featureMember>
</gmgml:FeatureCollection>
If you want to specify the default namespace (or target namespace) for an application
schema that overrides the default behavior, you use the Output namespace and prefix
field.
In the following example, the value for Output namespace and prefix is defined as
xmlns:test='http://www.test.com'
The following is the excerpt taken from output GML file created using the previous
settings. In this case, the default namespace (or target namespace) for the schema is taken
as "xmlns:test='http://www.test.com'", and the data and schema are encoded using "test",
which refers to the target namespace.
<test:FeatureCollection xmlns='http://www.test.com' xmlns:gml='http://www.opengis.net/gml'
xmlns:test='http://www.test.com' xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation='http://www.test.com d:\warehouses\GMLData.xsd'>
<gml:boundedBy>
18-23
<gml:Envelope srsName="EPSG:4269">
<gml:lowerCorner>34.665793 -86.776129</gml:lowerCorner>
<gml:upperCorner>34.777847 -86.564569</gml:upperCorner>
</gml:Envelope>
</gml:boundedBy>
<gml:featureMember>
<test:Exit gml:id="Exit.1">
<test:FROM_NAME>STATE HWY 255</test:FROM_NAME>
<test:EXIT></test:EXIT>
<test:TO_NAME>STATE HWY 255</test:TO_NAME>
<test:ID>1</test:ID>
<test:Geometry>
<gml:Point srsName="EPSG:4269">
<gml:pos>34.777847 -86.672915</gml:pos>
</gml:Point>
</test:Geometry>
</test:Exit>
</gml:featureMember>
</test:FeatureCollection>
To export data to GML:

2. Select Warehouse > Export to > GML.
3. Select the appropriate entries from the Features to export treeview.

4. Use the appropriate Target Coordinate System option.
If Use GeoWorkspace coordinate system is enabled and selected, go to Step 6.
OR
If Use the coordinate system file is enabled and selected, continue with Step 5.
18-24
Note: The Target EPSG code: <EPSG Code> read-only field contains the EPSG
code of the target coordinate system. If no EPSG code can be derived from the
selected coordinate system, Undefined is displayed in the field.
5. Type or select through Browse the location and name of an appropriate coordinate
system file.
6. In the GML data file field, select or type the appropriate path/location to which the
exported GML data file is written.
7. In the GML schema file field, select or type the appropriate path/location to which the
exported GML schema file is written.
8. Select the GML version to be output from the GML version drop-down list, if
appropriate.
9. Type the output namespace and prefix in the Output namespace and prefix field, if
appropriate.
10. In the GML base schema location field, select or type the appropriate location of the
GML base schema file, if appropriate.
11. Check the Bounding box per record and/or Preserve input field sequence and/or
Export 3D coordinates checkboxes, if appropriate.
12. Depending upon the target coordinate system file selected, the Swap coordinate order
check box is checked or unchecked. Check/Uncheck the check box as appropriate.
Note: In the case of a Geographic coordinate system in the default unchecked state,
the coordinates are written as Latitude-Longitude, that is, Y-X. If checked, the
coordinates are written as Longitude-Latitude, that is, X-Y. In the case of a Projection
coordinate system in the default unchecked state, the coordinates are written as X-Y.
If checked, the coordinates are written as Y-X.
13. Click Apply to export the selected features.
18-25
18-26
How to Reach Intergraph
Electronic Self-Help Support

Intergraph provides several electronic self-help support tools to answer your support questions 24
hours a day, seven days a week. Using any web browser, you can access Security, Government &
Infrastructure User Support on the World Wide Web at http://support.intergraph.com.
The Knowledge Base and Technical Notes are available at
http://support.intergraph.com/KnowledgeBase/kb.asp under the Knowledge Base link.
For additional product information, please visit our product web site at
http://www.intergraph.com/products/.
Frequently Asked Questions (FAQs)

You can access a helpful list of frequently asked questions about GeoMedia at
http://support.intergraph.com/KnowledgeBase/kb.asp
Select GeoMedia from the list of available Product Families, set the Product to GeoMedia , and
then set the search Type to FAQ. Type a keyword to search for a specific article, or type FAQ,
and then click GO to see a list of all available articles.
GeoMedia 6.1 Release Notes and Issues Resolved

To learn about changed and new features in GeoMedia 6.1, see the GeoMedia Professional 6.1
Release Notes (which includes GeoMedia and GeoMedia Viewer) and the Issues Resolved.
1. Go to the “SG&I Support” page at http://support.intergraph.com.
2. Under Product Support, select GeoMedia from the Products drop-down list; then click Go.
3. On the "Customer Log In" page, enter your User ID and Password; then click Log In. If you
do not have a user login, click the link to request one.
4. On the “GeoMedia Support” page, scroll down to the Product Versions table; then click the
Release Notes arrow and/or Issues Resolved arrow for the latest 06.01 version information.
A-1
A-2
Coordinate System Information
Projection Algorithms
Albers Equal Area New Brunswick Stereographic (ATS77)
Azimuthal Equidistant New Brunswick Stereographic (NAD83)
Bipolar Oblique Conic Conformal New Zealand Map Grid
Bonne North Polar Stereographic
British National Grid Oblique Mercator
Cassini-Soldner Orthographic
Cylindrical Equirectangular Polyconic
Eckert IV Rectified Skew Orthomorphic
Equidistant Conic (Simple Conic) Robinson
Gauss Conformal (South Africa) Simple Cylindrical (Plate Carree)
Gauss-Kruger (3-degree) Sinusoidal
Gauss-Kruger (6-degree) South Polar Stereographic
Gnomonic State Plane Coordinate System 1927
Indonesian Polyhedric State Plane Coordinate System 1983
Japan Plane Rectangular (Tokyo) Stereographic
Krovak Switzerland LV03
Laborde Switzerland LV95
Lambert Azimuthal Equal-Area Three-Step Stereographic
Lambert Conformal Conic Transverse Mercator
Local Space Rectangular Undefined (Rectangular Grid)
Mercator Universal Polar Stereographic
Miller Cylindrical Universal Transverse Mercator
Modified Polyconic (IMW Series) Van der Grinten
Mollweide
Datum Transformation Models

Bursa-Wolf
Canadian National Transformation (2.0)
Complex Polynomial
GEOID (NGS hybrid geoid)
Molodensky (standard)
Multiple Regression
NADCON North American Datum 1927 to North American Datum 1983 (NGS Version 2.10)
B-1
NADCON North American Datum 1983 to High Accuracy Reference Network (NGS Version
2.10)
NGA Earth Gravity Model (EGM96)
Second Degree Conformal Polynomial
Second Degree (General) Polynomial
User-Supplied
USGG (NGS gravimetric geoid)
VERTCON (NGS Version 2.10)
Functional Categories of Datum Transformation Models
Some datum transformation models transform between horizontal geodetic datums in the horizontal plane
while ignoring (copying) height coordinates. These transformations will be used with coordinates having
orthometric height type and will not be used with coordinates having geometric height type (since they do
not correctly transform ellipsoid-based height). These models include:
2nd Degree (General) Polynomial
2nd Degree Conformal Polynomial
Canadian National Transformation (2.0)
Complex Polynomial
NADCON NAD27 to NAD83 (NGS Version 2.10)
NADCON NAD83 to HARN (NGS Version 2.10)
Some datum transformation models transform between horizontal geodetic datums and may be used with
either orthometric or geometric height coordinates. They copy height coordinates when given orthometric
height coordinates and correctly transform geometric height coordinates. These models include:
Bursa-Wolf
Molodensky (standard)
Multiple Regression
Some datum transformation models transform between vertical datums, which may or may not involve
changing the height type of the coordinates. These models copy the horizontal coordinates. They include:
VERTCON (NGS Version 2.10)
NGA Earth Gravity Model (EGM96)
GEOID (NGS hybrid geoid)
USGG (NGS gravimetric geoid)
The User-Supplied datum transformation model may be configured in any of the above ways.
Notes for the Canadian National Transformation 2.0 Datum Transformation Model
The Canadian National Transformation is a datum transformation model for the conversion of geographic
points from the NAD27 horizontal datum to the NAD83 horizontal datum, or vice versa, to match points
obtained from the Canadian National Transformation PC program INTGRID version 2.0. This model was
obtained from the Geodetic Survey Division, Geomatics Canada, and has been implemented in GeoMedia.
To use the Canadian National Transformation, you must obtain the grid file ntv2_0.gsb and place it in the
…\cfg\canada folder. You can obtain this grid file from:
B-2
Geodetic Survey Division, Geomatics Canada

Natural Resources Canada
615 Booth Street
Ottawa, Ontario K1A0E9 CANADA
Disclaimer by the Minister of Natural Resources (NRCan) for the Canadian National Transformation version 2.0
(NTv2) software:
The NTv2, or any part thereof, is licensed on an "as is" basis and NRCan makes no guarantees, representations, or
warranties respecting the NTv2, either expressed or implied, arising by law or otherwise, including but not limited to,
effectiveness, completeness, accuracy or fitness for a particular purpose.
NRCan shall not be liable in respect of any claim, demand, or action, irrespective of the nature of the cause of the claim,
demand, or action alleging any loss, injury or damages, direct or indirect, which may result from Intergraph's, or
Intergraph’s clients’, use or possession of the NTv2, or any part thereof. NRCan shall not be liable in any way for loss of
profits or revenue, or any other consequential loss of any kind resulting from the Intergraph's, or Intergraph’s clients’, use
or possession of the NTv2 or any part thereof.
The Canadian National Transformation (version 2.0) has been adopted by the Intergovernmental Committee
on Surveying and Mapping (ICSM) as the official high-accuracy transformation between the old Australian
horizontal datums (AGD66 or AGD84, depending upon location) and the new official horizontal datum
(GDA94). Grid files are published on the World Wide Web. The use of the Canadian National
Transformation model for Australia has been included in the default entries in the autodt.ini configuration
file. However, users will need to obtain the desired grid file from the Australian authorities, place it in the
…\cssruntm\cfg\canada folder, and edit the …\cssruntm\cfg\canada\area.ini file to reference the grid file by
name.
The Canadian National Transformation (version 2.0) has also been adopted by the Intergovernmental
Committee on Surveying and Mapping (ICSM) and Land Information New Zealand (LINZ) as the official
high-accuracy transformation between the old (New Zealand) Geodetic Datum 1949 and the new official
datum, New Zealand Geodetic Datum 2000. Grid files are published by LINZ and are available on the
World Wide Web. The use of the Canadian National Transformation model for New Zealand has been
included in the default entries in the autodt.ini configuration file. However, users will need to obtain the
desired grid file from Land Information New Zealand, place it in the …\cssruntm\cfg\canada folder, and edit
the …\cssruntm\cfg\canada\area.ini file to reference the grid file by name.
When the Canadian National Transformation model interpolates a given point, it checks a configurable text
file, …\cssruntm\cfg\canada\area.ini, for the name of the grid file to use. Only the first valid grid file found
will be used during point conversions. The file extension .gsb should be left off the entry in the area.ini file.
Notes for the NADCON NAD27 to NAD83 and NADCON NAD83 to HARN (NGS
Version 2.10) Models
NADCON is a datum transformation model for the conversion of point coordinates from the North American
Datum of 1927 (NAD27) to the North American Datum of 1983 (NAD83), and vice versa, and from the
NAD83 datum to the state High Accuracy Reference Network (HARN), and vice versa.
The NADCON model (NGS version 2.10) is public-domain software from the National Geodetic Survey.
This program transforms latitude and longitude coordinates between NAD27 and NAD83, and vice versa,
and between the North American Datum of 1983 (NAD83) and the High Accuracy Reference Network
(HARN), and vice versa. This model can also transform data originally expressed in old island datums, such
as exist in Alaska and Hawaii, into data referenced to NAD83. Data for the following areas is provided in
GeoMedia.
B-3
Grid files for going between NAD27 and NAD83:

Area Description File Name
Alaska Alaska, including Aleutian Islands alaska
Alaska: St. George Island Old island datum within Alaska stgeorge
Alaska: St. Lawrence Island Old island datum within Alaska stlrnc
Alaska: St. Paul Island Old island datum within Alaska stpaul
CONUS Conterminous U.S. (lower 48 states) conus
Hawaiian Islands Old Hawaiian datum hawaii
Puerto Rico and V.I. Puerto Rico and Virgin Islands prvi
Data used in the above files for NADCON datum transformations is selected on an area-by-area basis. For
example, if you are performing a datum transformation within the U.S., data contained in the conus file is
used in the transformation. However, the island datums of Alaska (St. Lawrence, St. George, and St. Paul)
fall within the larger Alaska datum. When a point being transformed from NAD27 to NAD83 falls within
multiple datums, the datum corresponding to the first file found in the list of file names in the
…\cssruntm\cfg\nadcon\area.ini file is used. This is the default file list in area.ini: conus, prvi, stlrnc,
stgeorge, stpaul, alaska, hawaii. To perform datum transformations for the three Alaska island datums using
the Alaska datum instead of the island datums, the alaska entry must come before the island datum entries
stlrnc, stgeorge, and stpaul.
IMPORTANT: St. George Is. and St. Paul Is. are part of the Pribilof Islands. Two separate datums, one for
each island, that were available before NAD83 are significantly different from NAD27. Be sure that the
input data are consistent with the identified transformation data sets. The transformation of misidentified
data can result in very large errors on the order of hundreds of meters.
Grid files for going between NAD83 and HARN:

Area File Name
Alabama alhpgn
American Samoa eastern islands eshpgn
American Samoa western islands wshpgn
Arkansas arhpgn
Arizona azhpgn
California above 37 deg. latitude cnhpgn
California below 37 deg. latitude cshpgn
Colorado cohpgn
Florida flhpgn
Georgia gahpgn
Guam guhpgn
Hawaii hihpgn
Idaho – Montana east of –113 deg. longitude emhpgn
Idaho – Montana west of –113 deg. wmhpgn
longitude
Illinois ilhpgn
Area File Name
Kansas kshpgn
B-4
Indiana inhpgn
Iowa iahpgn
Kentucky kyhpgn
Louisiana lahpgn
Maine mehpgn
Maryland - Delaware mdhpgn
Michigan (except Isle Royale) mihpgn
Minnesota mnhpgn
Mississippi mshpgn
Missouri mohpgn
Nebraska nbhpgn
Nevada nvhpgn
New England (CT, MA, NH, RI, VT) nehpgn
New Jersey njhpgn
New Mexico nmhpgn
New York nyhpgn
North Carolina nchpgn
North Dakota ndhpgn
Ohio ohhpgn
Oklahoma okhpgn
Pennsylvania pahpgn
Puerto Rico and Virgin Islands pvhpgn
South Carolina schpgn
South Dakota sdhpgn
Tennessee tnhpgn
Texas east of –100 deg. longitude ethpgn
Texas west of –100 deg. longitude wthpgn
Utah uthpgn
Virginia vahpgn
Washington - Oregon wohpgn
West Virginia wvhpgn
Wisconsin wihpgn
Wyoming wyhpgn
The area.ini file for NAD83 to HARN datum transformations is …\cssruntm\cfg\harn\area.ini. The default
file list is alphabetical. Because many regions overlap, you may need to rearrange the list to ensure that the
desired region is being used for your area. Note that the HARN files for American Samoa and Guam are an
exception to the general application of the NAD83 to HARN datum transformation, in that these grid files
transform directly from the old island datum (American Samoa 1962 or Guam 1963) to the NAD83 HARN
datum (the original NAD83 datum was never applied to American Samoa or Guam).
The accuracy of the transformations should be viewed with some caution. At the 67-percent confidence
level, this method introduces approximately 0.15 meter uncertainty within the conterminous United States,
0.50 meter uncertainty within Alaska, 0.20 meter uncertainty within Hawaii, and 0.05 meter uncertainty
within Puerto Rico and the Virgin Islands. In areas of sparse geodetic data coverage, NADCON may yield
B-5
less accurate results, but seldom in excess of 1.0 meter. Transformations between NAD83 and
States/Regions with High Accuracy Reference Networks (HARNs) introduce approximately 0.05 meter
uncertainty.
Transformations between old datums (NAD27, Old Hawaiian, Puerto Rico, and so forth) and HARN could
combine uncertainties (for example, NAD27 to HARN equals 0.15m + 0.05m = 0.2m). In near offshore
regions, results will be less accurate, but seldom in excess of 5.0 meters. Farther offshore NAD27 was
undefined. Therefore, the NADCON computed transformations are extrapolations and no accuracy can be
stated.
NADCON cannot improve the accuracy of data. Stations that are originally third-order will not become
first-order stations. NADCON is merely a tool for transforming coordinate values between datums.
This program is based exclusively upon data within the official National Geodetic Reference System
(NGRS). Data originating from stations not part of this official reference may not be compatible. Be sure
that the data to be transformed is actually referenced to the NGRS.
Disclaimer published by the National Geodetic Survey in the public domain software package:
The attendant software and any associated data were developed for use by the National Ocean Service under
controlled conditions of software maintenance, input quality, processing configurations, and output data utilization.
Any use of this software by other than the National Ocean Service would be under conditions not necessarily subject
to such control. Therefore, the National Ocean Service makes no warranties, expressed or implied, concerning the
accuracy, completeness, reliability, or suitability for any particular purpose of the information and data contained in
or generated by this software or furnished in connection therewith. Furthermore, the National Ocean Service assumes
no liability associated with the use of such software, information, and data, and assumes no responsibility to maintain
them in any manner or means. Any exceptions to these conditions of release must be formally established through
negotiated agreements with the National Ocean Service.
Since this software and associated information and data were developed and compiled with U.S. Government funding,
no proprietary rights may be attached to them, nor may they be sold to the U.S. Government as part of any
procurement of ADP products or services.
Notes for the NGA Earth Gravity Model

The NGA Earth Gravity Model (EGM96) model is a datum transformation model for the conversion of
elevation (height) values between the EGM96 (orthometric) and Ellipsoid (geometric) vertical datums, based
upon interpolation in a grid file using WGS84 geographic coordinates. This model uses algorithms found in
the National Geospatial Intelligence Agency (NGA) public-domain "INTPT" executable. Comments in the
source give original credit for the program to Professor Richard H. Rapp of The Ohio State University. The
ASCII grid file published by NGA has been converted into a binary format and is delivered with the product
in the …\cssruntm\cfg\EGMGeoid folder. The area.ini file in this folder references the binary grid file.
NGA publishes the following disclaimer, which was worded when they were known as NIMA:
B-6
Disclaimer of Liability
With respect to documents and products available from this server, neither the United States Government nor the National
Imagery and Mapping Agency nor any of their employees, makes any warranty, express or implied, including the
warranties of merchantability and fitness for a particular purpose, or assumes any legal liability or responsibility for the
accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, or represents that its
use would not infringe privately owned rights.
Notes for the GEOID (NGS Hybrid Geoid) Model

The GEOID (NGS hybrid geoid) model is a datum transformation model for the conversion of elevation
(height) values between the North American Vertical Datum 1988 (orthometric) and Ellipsoid (geometric)
vertical datums, based upon interpolation in a grid file using NAD83 geographic coordinates. This model
uses algorithms found in the National Geodetic Survey (NGS) public-domain "intg" executable. You must
obtain the desired .bin binary grid files from NGS (they are available from their website), place them in the
…\cssruntm\cfg\NGSGEOID folder, and edit the area.ini file found in that folder so that it contains the
names of the binary grid files (with no path). NGS publishes .bin files for the conterminous USA for the
GEOID03 model. Grid files for other regions (Alaska, Hawaii, Puerto Rico, and U.S. Virgin Islands)
published for the GEOID99 model may also be loaded to this folder and used concurrently with the
GEOID03 files. The "intg" source contains the following disclaimer:
Disclaimer
This program and supporting information is furnished by the government of the United States of America, and is accepted
and used by the recipient with the understanding that the United States government makes no warranties, express or
implied, concerning the accuracy, completeness, reliability, or suitability of this program, of its constituent parts, or of
any supporting data. The government of the United States of America shall be under no liability whatsoever resulting
from any use of this program. This program should not be relied upon as the sole basis for solving a problem whose
incorrect solution could result in injury to person or property. This program [intg] is property of the government of the
United States of America. Therefore, the recipient further agrees not to assert proprietary rights therein and not to
represent this program to anyone as being other than a government program.
By inclusion of the intg algorithms in GeoMedia software, Intergraph asserts no proprietary rights on the
algorithms used by our NGS GEOID and NGS USGG implementations, which are based upon the intg
algorithms, and furthermore, acknowledges intg as a government program.
Notes for the USGG (NGS Gravimetric Geoid) Model

The USGG (NGS gravimetric geoid) model is a datum transformation model for the conversion of elevation
(height) values between the United States Gravimetric Geoid (orthometric) and Ellipsoid (geometric) vertical
datums, based upon interpolation in a grid file using NAD83 geographic coordinates. This model uses
algorithms found in the National Geodetic Survey (NGS) public-domain "intg" executable. You must obtain
the desired .bin binary grid files from NGS (they are available from their website), place them in the
…\cssruntm\cfg\ NGSUSGG folder, and edit the area.ini file found in that folder so that it contains the names
of the binary grid files (with no path). NGS publishes .bin files for the conterminous USA for the USGG
2003 model. Note that the disclaimer information found above for the NGS GEOID geoid undulation model
applies to the NGS USGG geoid undulation model also.
B-7
Notes for the VERTCON (NGS Version 2.10) Model

The VERTCON (NGS Version 2.10) model is a datum transformation model for the conversion of elevation
(height) values between the National Geodetic Vertical Datum 1929 and North American Vertical Datum
1988 (both orthometric) vertical datums, based upon interpolation in a grid file using NAD83 or NAD27
geographic coordinates. This model uses algorithms found in the National Geodetic Survey (NGS) public-
domain "vertcon" executable. You must obtain the desired .bin binary grid files from NGS (they are
available from their website), place them in the …\cssruntm\cfg\vertcon folder, and edit the area.ini file
found in that folder so that it contains the names of the binary grid files (with no path). NGS publishes .bin
files for the conterminous USA for the VERTCON model. The "vertcon" source contains the following
disclaimer:
Disclaimer
This program and supporting information is furnished by the government of the United States of America, and is
accepted/used by the recipient with the understanding that the U. S. government makes no warranties, express or implied,
concerning the accuracy, completeness, reliability, or suitability of this program, of its constituent parts, or of any
supporting data. The government of the United States of America shall be under no liability whatsoever resulting from
any use of this program. This program should not be relied upon as the sole basis for solving a problem whose incorrect
solution could result in injury to person or property. This program [vertcon] is the property of the government of the
United States of America. Therefore, the recipient further agrees not to assert proprietary rights therein and not to
represent this program to anyone as being other than a government program.
By inclusion of the vertcon algorithms in GeoMedia, software Intergraph asserts no proprietary rights on the
algorithms used by our NGS VERTCON implementation, which are based upon the vertcon algorithms, and
furthermore, acknowledges vertcon as a government program.
Notes for the User-Supplied Datum Transformation Model

The User-Supplied datum transformation model allows users to write a program to perform a datum
transformation. The program must implement a simple, well-defined point transformation interface defined
by GeoMedia. Please consult the Automation Help documentation for the DatumTransformation object for
details.
B-8
Standard Geodetic Datums

The definitions of these datums come primarily from two sources: National Geospatial-
Intelligence Agency (NGA) Technical Report 8350.2, Third Edition Amendment 2 (June 2004),
and the EPSG Geodetic Parameters Dataset, version 6.5.3 (June 2004) , published by the Surveying
and Positioning Committee of the International Association of Oil and Gas Producers. Where
conflicts between these two sources exist, both definitions are provided, and the names indicate the
source.
Adindan Campcupa European 1979
AFG (Afgooye) Camp Area Astro European 1987
Agadez Campo Inchauspe Fahud
Ain el Abd 1970 Canton Astro 1966 Fort Thomas 1955
American Samoa Datum 1962 Cape (EPSG Definition) Gan 1970
Amersfoort Cape (NGA Definition) Garoua
Ancienne Triangulation Cape Canaveral Geocentric Datum of Australia
Francaise (ATF) Carthage (EPSG Definition) (GDA94)
Anna 1 Astro 1965 Carthage (NGA Definition) Geodetic Datum 1949
Antigua Island Astro 1943 CH1903 Graciosa Base SW 1948
Aratu CH1903+ Greek
Arc 1950 (EPSG Definition) Chatham Island Astro 1971 Greek Geodetic Reference
Arc 1950 (NGA Definition) CHTRF95 System 1987
Arc 1960 Chua Astro Guam 1963
Ascension Island 1958 Conakry 1905 Gunung Segara
Astro Beacon "E" 1945 Co-Ordiante System 1937 of GUX 1 Astro
Astro DOS 71/4 Estonia Guyane Francaise
Astro Tern Island (FRIG) 1961 Corrego Alegre Hartebeesthoek 94
Astronomical Station 1952 Cote d’lvoire Herat North
Australian Geodetic 1966 Dabola Hermannskogel
Australian Geodetic 1984 Datum 73 Hito XVIII 1963
Average Terrestrial System Dealu Piscului 1933 Hjorsey 1955
1977 (ATS77) Dealu Piscului 1970 Hong Kong 1963
Ayabelle Lighthouse Deception Island (Antarctica) Hong Kong 1980
Barbados Deir ez Zor Hungarian Datum 1972
Batavia Deutsche Hauptdreiecksnetz (HD72)
Beduaram (DHDN) Hungarian Fasching 1909
Beijing 1954 Djakarta (Batavia) Hungarian Stereo Datum 1863
Bellevue (IGN) DOS 1968 Hu-Tzu-Shan
Bermuda 1957 Douala Indian
Bern 1898 Easter Island 1967 Indian 1954
Bern 1938 EUREF-FIN Indian 1960
Bissau European Terrestrial Reference Indian 1975
Bogota Observatory System 1989 Indian (India and Nepal)
Bukit Rimpah European 1950 Indian (Pakistan)
B-9
Indonesian 1974 MGICS (equivalent to S-JTSK) Porto Santo 1936

International Terrestrial Mhast Potsdam
Reference Frame 2000 Midway Astro 1961 Provisional South Chilean
(ITRF 2000) Militar-Geographische Institut 1963
Ireland 1965 (MGI) Puerto Rico
IRENET95 Minna Pulkovo 1942
ISTS 061 Astro 1968 Monte Mario Pulkovo 1995
ISTS 073 Astro 1969 Montserrat Island Astro 1958 Qatar 1948
Jamaica 1875 Nahrwan Qatar National
Jamaica 1969 Naparima, BWI Qornoq
Japan Geodetic Datum 2000 National Geodetic Network Reseau Geodesique Francais
Johnston Island 1961 (NGN) 1993 (RGF93)
Kalianpur 1880 New Zealand Geodetic Datum Reseau National Belge 1950
Kalianpur 1937 2000 (Belge 1950)
Kalianpur 1962 NGO 1948 Reseau National Belge 1972
Kalianpur 1975 Nord de Guerre (Belge 1972)
Kandawala North American 1927 Reunion
Kartastokoordinaattijarjestelma North American 1983 Rome 1940
(KKJ) North American 1983 – HARN S-42 (Pulkovo 1942)
Kerguelen Island 1949 Upgrade S-JTSK (equivalent to MGICS)
Kertau 1948 North Sahara 1959 (EPSG Samboja
Korean Datum 1995 Definition) Santo (DOS) 1965
Kusaie Astro 1951 North Sahara 1959 (NGA Sao Braz
Kuwait Oil Company (KOC) Definition) Sapper Hill 1943
Kuwait Utility (KUDAMS) Nouvelle Triangulation Schwarzeck
L. C. 5 Astro 1961 Francaise (NTF) Segora
La Canoa NSWC 9Z-2 Selvagem Grande 1938
Lake Observatorio Meteorologico Serindung
Leigon 1939 Sierra Leone 1960
Liberia 1964 Old Egyptian 1907 South American 1956
Lisbon Old Hawaiian South American 1969
Lithuania 1994 (ETRS89), a Oman South Asia
densification from ETRS89 Ordnance Survey of Great Sudan
Loma Quintana Britain 1936 Swedish RT38
Lome OS (SN) 1980 Swedish RT90
Luzon OSGB 1970 (SN) Taiwan (TWD67)
M'Poraloko (EPSG Definition) Padang 1884 Taiwan (TWD97)
M'Poraloko (NGA Definition) Palestine 1923 Tananarive Observatory 1925
Mahe 1971 Pico de las Nieves Timbalai 1948
Makassar Pitcairn Astro 1967 TM65
Malongo 1987 Point 58 TM75
Manoca Pointe Noire 1948 (EPSG Tokyo
Massawa Definition) Trinidad 1903
Merchich (EPSG Definition) Pointe Noire 1948 (NGA Tristan Astro 1968
Merchich (NGA Definition) Definition) Trucial Coast 1948
B-10
United States Standard Voirol 1960 (Obsolete EPSG WGS 72 Transit Broadcast
User-defined (non-standard) Definition) Ephemeris (WGS 72BE)
Viti Levu 1916 Wake Island Astro 1952 WGS84
Voirol 1874 (NGA Definition) Wake-Eniwetok 1960 Yacare
Voirol 1875 (EPSG Definition) WGS60 Yoff
Voirol 1960 (NGA Definition) WGS66 Zanderij
WGS72
Named Geodetic Datums

Users may add named datums to the product using an ASCII configuration file. Each such named
datum is based upon one of the standard geodetic datums listed above (the user-defined datum is
valid for this purpose). Named datums are defined in the ...\cssruntm\cfg\NamedHDatum.ini file.
See the comments in this file for further details. Datums defined in this file may be referenced
from the autodt.ini configuration file. A named datum may be used with a coordinate system that
presets the horizontal geodetic datum, provided that the base standard datum referenced by the
named datum is the standard datum preset by the coordinate system.
B-11
Vertical Datums
You can reference and transform data between different vertical datums including ellipsoid-geoid
conversion. Vertical datums may reference the geoid (orthometric height), the ellipsoid (geometric
height), or be undefined. Geoid undulation is handled as a vertical datum transformation.
Vertical datum information is carried with the definition of a coordinate system, through the user
interface (for more information see the GMDefCoordSystem control sections), the programmer
interface (for more information see the GeogSpace and CoordSystem sections), and the storage
system (for more information see the GeogSpace and GDO specification section).
Note: The sections referred to are in the GeoMedia Object Reference Help.
The following vertical datums are supported. The height type is orthometric for all cases, except
where noted.
Australian Height Datum 1971 Tsingtao
Canadian Vertical Reference 1928 United European Leveling Network 1955
Earth Gravitational Model (EGM96) United European Leveling Network 1973
Ellipsoid (geometric)1 United European Leveling Network 73-81
International Great Lakes 1955 United European Leveling Network 95-98
International Great Lakes 1985 United States Gravimetric Geoid 2003
National Geodetic Vertical Datum 1929 Unspecified2
North American Vertical Datum 1988 User-defined (non-standard)
Ordnance Newlyn Third Geodetic Leveling
1
Causes the height storage type of the containing CoordSystem to be geometric, referencing the ellipsoid of the horizontal geodetic
datum.
2
Causes the height storage type to be unspecified.
Ellipsoids
Ellipsoid Earth Radius Earth-Flattening
Denominator
Airy 1830 6377563.396 m. 299.3249646
Australian National Spheroid 6378160 m. 298.25
Average Terrestrial System 1977 6378135 m. 298.257
Bessel 1841 6377397.155 m. 299.1528128
Bessel 1841 (Namibia) 6377483.865 m. 299.1528128
Clarke 1858 (EPSG Definition) 6378293.639246834 m 294.2606763692611
Clarke 1866 6378206.4 m. 294.9786982139058
B-12
Clarke 1880 (Arc) 6378249.145 m. 293.4663077

Clarke 1880 (Benoit) 6378300.79 m. 293.4662345705142
Clarke 1880 (EPSG Definition) 6378249.138846127 m. 293.4663076556299
Clarke 1880 (IGN) 6378249.2 m. 293.4660212936294
Clarke 1880 (NGA Definition) 6378249.145 m. 293.465
Clarke 1880 (SGA 1922) 6378249.2 m. 293.46598
Danish 6377104.43 m. 300
Everest (Brunei and East Malaysia 6377298.556 m. 300.8017
1967) – also referenced as “Everest
1830 (1967 Definition)”
Everest (Pakistan) 6377309.613 m. 300.8017
Everest (Singapore and W. Malaysia 6377304.063 m. 300.8017
1948) - also referenced as “Everest
1830 Modified”
Everest (West Malaysia 1969) 6377295.664 m. 300.8017
Everest 1830 (1865 Indian Feet) 6377299.365595379 m. 300.8017255433728
Everest 1830 (1937 Adjustment) 6377276.345 m. 300.8017
Everest 1830 (1956 Definition) 6377301.243 m. 300.8017
Fischer 1960 (Mercury) 6378166 m. 298.3
Fischer 1968 6378150 m. 298.3
GEM 10C 6378137 m. 298.2572236
GRS 1967 6378160 m. 298.247167427
GRS 1967 (Rounded) 6378160 m. 298.25
GRS80 6378137 m. 298.257222101
Helmert 1906 6378200 m. 298.3
Hough 6378270 m. 297
Indonesian National 1974 6378160 m. 298.247
International 1924 6378388 m. 297
Krassovsky 1940 6378245 m. 298.3
Modified Airy - also referenced as 6377340.189 m. 299.3249646
“Airy Modified 1849”
Modified Bessel 6377492.0176 m. 299.152812849997
Modified Fischer 1960 (South Asia) 6378155 m. 298.3
NWL 10D 6378135 m. 298.26
NWL 9D 6378145 m. 298.25
OSU86F 6378136.2 m. 298.2572236
OSU91A 6378136.3 m. 298.2572236
Plessis 1817 6376523 m. 308.64
South American 1969 6378160 m. 298.25
B-13
Struve 6378298.3 m. 294.73

Struve 1860 6378297 m. 294.73
Unit Sphere 1 m. 0
User-defined (non-standard)
War Office 6378300.583 m. 296
WGS60 6378165 m. 298.3
WGS66 6378145 m. 298.25
WGS72 6378135 m. 298.26
WGS84 6378137 m. 298.257223563
Units of Measure (UOM)

Linear Units
Alias UOM Conversion Factor
’ feet 0.3048 (m/ft)
” inches 0.0254 (m/in)
chain chain 20.1168 (m/chain)
cm centimeters 0.01 (m/cm)
ft feet 0.3048 (m/ft)
furlong furlong 201.168 (m/furlong)
hundredth hundredth 0.000254 (m/100th)
in inches 0.0254 (m/in)
kft kilofeet 304.80 (m/kft)
km kilometers 1000.0 (m/km)
link link 0.201168 (m/link)
m meters 1.0
mi miles 1609.344 (m/mi)
mm millimeters 0.001 (m/mm)
nm nanometer 0.000000001 (m/nm)
nmi nautical miles 1852.0 (m/nmi)
pole pole 5.0292 (m/pole)
pt point 0.000352777777777778 (m/pt)
rod rod 5.0292 (m/rod)
sf survey feet 0.304800609601219 (m/sf)
si survey inches 0.025400050800102 (m/si)
sk survey kilofeet 304.800609601219 (m/sk)
svy_ft survey feet 0.304800609601219 (m/sf)
B-14
svy_in survey inches 0.025400050800102 (m/si)

svy_kft survey kilofeet 304.800609601219 (m/svy_kft)
tenth tenth 0.00254 (m/tenth)
thousandth thousandth 0.0000254 (m/1000th)
yd yard 0.9144 (m/yd)
Angular Units
’ minutes 0.000290888208665722 (rad/min)
” seconds 0.00000484813681109536 (rad/sec)
° degrees 0.0174532925199433 (rad/deg)
dd.mmss degrees minutes seconds See individual units.
deg degrees 0.0174532925199433 (rad/deg)
d:m degrees:minutes See individual units.
d:m:s degrees:minutes:seconds See individual units.
gr grads 0.0157079632679490 (rad/gr)
min minutes 0.000290888208665722 (rad/min)
rad radians 1.0
rev revolutions 6.28318530717959 (rad/rev)
sec seconds 0.00000484813681109536 (rad/sec)
Area Units
ac acres 4046.8564224 (m^2/ac)
ares ares 100.0 (m^2/are)
centare centares 1.0 (m^2/centare)
chain^2 square chains 404.68564224 (m^2/chain^2)
cm^2 square centimeters 0.0001 (m^2/cm^2)
deciare deciares 10.0 (m^2/deciare)
ft^2 square feet 0.09290304 (m^2/ft^2)
hectare hectares 10000.0 (m^2/hectare)
in^2 square inches 0.00064516 (m^2/in^2)
km^2 square kilometers 1000000.0 (m^2/km^2)
link^2 square links 0.040468564224 (m^2/link^2)
m^2 square meters 1.0
mi^2 square miles 2589988.110336 (m^2/mi^2)
B-15
mm^2 square millimeters 0.000001 (m^2/mm^2)

perch perches 25.29285264 (m^2/perch)
rod^2 square rods 25.29285264 (m^2/rod^2)
yd^2 square yards 0.83612736 (m^2/yd^2)
State Plane Zone Codes—NAD27 and Old Island

Datums
Zone Code Projection
Alabama (E,W) 101, 102 Transverse Mercator
Alaska 1 5001 Oblique Mercator
Alaska (2-9) 5002-5009 Transverse Mercator
Alaska 10 5010 Lambert
Arizona (E,C,W) 201-203 Transverse Mercator
Arkansas (N,S) 301-302 Lambert
California (I-VII) 401-407 Lambert
Colorado (N,C,S) 501-503 Lambert
Connecticut 600 Lambert
Delaware 700 Transverse Mercator
Florida (E,W) 901, 902 Transverse Mercator
Florida North 903 Lambert
Georgia (E,W) 1001, 1002 Transverse Mercator
Hawaii (I-V) 5101-5105 Transverse Mercator
Idaho (E,C,W) 1101-1103 Transverse Mercator
Illinois (E,W) 1201, 1202 Transverse Mercator
Indiana (E,W) 1301, 1302 Transverse Mercator
Iowa (N,S) 1401, 1402 Lambert
Kansas (N,S) 1501, 1502 Lambert
Kentucky (N,S) 1601, 1602 Lambert
Louisiana (N,S) 1701, 1702 Lambert
Louisiana Offshore 1703 Lambert
Maine (E,W) 1801, 1802 Transverse Mercator
Maryland 1900 Lambert
Mass. (Main, Isle) 2001, 2002 Lambert
Mich. (old) (E,C,W) 2101-2103 Transverse Mercator
Mich. (N,C,S) 2111-2113 Lambert
Minnesota (N,C,S) 2201-2203 Lambert
B-16
Mississippi (E,W) 2301, 2302 Transverse Mercator

Missouri (E,C,W) 2401-2403 Transverse Mercator
Montana (N,C,S) 2501-2503 Lambert
Nebraska (N,S) 2601, 2602 Lambert
Nevada (E,C,W) 2701-2703 Transverse Mercator
New Hampshire 2800 Transverse Mercator
New Jersey 2900 Transverse Mercator
New Mexico (E,C,W) 3001-3003 Transverse Mercator
New York (E,C,W) 3101-3103 Transverse Mercator
N.Y. Long Island 3104 Lambert
North Carolina 3200 Lambert
North Dakota (N,S) 3301, 3302 Lambert
Ohio (N,S) 3401, 3402 Lambert
Oklahoma (N,S) 3501, 3502 Lambert
Oregon (N,S) 3601, 3602 Lambert
Pennsylvania (N,S) 3701, 3702 Lambert
Puerto Rico, Virg.I. 1 5201 Lambert
Puerto Rico, Virg.I. 2 5202 Lambert
Rhode Island 3800 Transverse Mercator
Samoa 5300 Lambert
South Carolina (N,S) 3901, 3902 Lambert
South Dakota (N,S) 4001, 4002 Lambert
Tennessee 4100 Lambert
Texas (N,NC,C,SC,S) 4201-4205 Lambert
Utah (N,C,S) 4301-4303 Lambert
Vermont 4400 Transverse Mercator
Virginia (N,S) 4501, 4502 Lambert
Washington (N,S) 4601, 4602 Lambert
West Virginia (N,S) 4701, 4702 Lambert
Wisconsin (N,C,S) 4801-4803 Lambert
Wyoming (E,EC,WC,W) 4901-4904 Transverse Mercator
State Plane Zone Codes—NAD83 Datum

Zone Code Projection
Alabama (E,W) 101, 102 Transverse Mercator
Alaska 1 5001 Oblique Mercator
Alaska (2-9) 5002-5009 Transverse Mercator
Alaska 10 5010 Lambert
Arizona (E,C,W) 201-203 Transverse Mercator
B-17
Arkansas (N,S) 301, 302 Lambert

California (I-VI) 401-406 Lambert
Colorado (N,C,S) 501-503 Lambert
Connecticut 600 Lambert
Delaware 700 Transverse Mercator
Florida (E,W) 901, 902 Transverse Mercator
Florida North 903 Lambert
Georgia (E,W) 1001, 1002 Transverse Mercator
Hawaii (I-V) 5101-5105 Transverse Mercator
Idaho (E,C,W) 1101-1103 Transverse Mercator
Illinois (E,W) 1201, 1202 Transverse Mercator
Indiana (E,W) 1301, 1302 Transverse Mercator
Iowa (N,S) 1401, 1402 Lambert
Kansas (N,S) 1501, 1502 Lambert
Kentucky (N,S) 1600-1602 Lambert
Louisiana (N,S) 1701, 1702 Lambert
Louisiana Offshore 1703 Lambert
Maine (E,W) 1801, 1802 Transverse Mercator
Maryland 1900 Lambert
Mass, (Main, Isle) 2001, 2002 Lambert
Michigan (N,C,S) 2111-2113 Lambert
Minnesota (N,C,S) 2201-2203 Lambert
Mississippi (E,W) 2301, 2302 Transverse Mercator
Missouri (E,C,W) 2401-2403 Transverse Mercator
Montana 2500 Lambert
Nebraska 2600 Lambert
Nevada (E,C,W) 2701-2703 Transverse Mercator
New Hampshire 2800 Transverse Mercator
New Jersey 2900 Transverse Mercator
New Mexico (E,C,W) 3001-3003 Transverse Mercator
New York (E,C,W) 3101-3103 Transverse Mercator
N.Y. Long Island 3104 Lambert
North Carolina 3200 Lambert
North Dakota (N,S) 3301, 3302 Lambert
Ohio (N,S) 3401, 3402 Lambert
Oklahoma (N,S) 3501, 3502 Lambert
B-18
Oregon (N,S) 3601, 3602 Lambert

Pennsylvania (N,S) 3701, 3702 Lambert
Puerto Rico, Virg.I. 5200 Lambert
Rhode Island 3800 Transverse Mercator
South Carolina 3900 Lambert
South Dakota (N,S) 4001, 4002 Lambert
Tennessee 4100 Lambert
Texas (N,NC,C,SC,S) 4201-4205 Lambert
Utah (N,C,S) 4301-4303 Lambert
Vermont 4400 Transverse Mercator
Virginia (N,S) 4501, 4502 Lambert
Washington (N,S) 4601 4602 Lambert
West Virginia (N,S) 4701, 4702 Lambert
Wisconsin (N,C,S) 4801-4803 Lambert
Wyoming (E,EC,WC,W) 4901-4904 Transverse Mercator
B-19
UTM Zones
Zone Meridian Longitude Range Zone Meridian Longitude Range
1 177W 180W-174W 32 9E 6E-12E
2 171W 174W-168W 33 15E 12E-18E
3 165W 168W-162W 34 21E 18E-24E
4 159W 162W-156W 35 27E 24E-30E
5 153W 156W-150W 36 33E 30E-36E
6 147W 150W-144W 37 39E 36E-42E
7 141W 144W-138W 38 45E 42E-48E
8 135W 138W-132W 39 51E 48E-54E
9 129W 132W-126W 40 57E 54E-60E
10 123W 126W-120W 41 63E 60E-66E
11 117W 120W-114W 42 69E 66E-72E
12 111W 114W-108W 43 75E 72E-78E
13 105W 108W-102W 44 81E 78E-84E
14 99W 102W-96W 45 87E 84E-90E
15 93W 96W-90W 46 93E 90E-96E
16 87W 90W-84W 47 99E 96E-102E
17 81W 84W-78W 48 105E 102E-108E
18 75W 78W-72W 49 111E 108E-114E
19 69W 72W-66W 50 117E 114E-120E
20 63W 66W-60W 51 123E 120E-126E
21 57W 60W-54W 52 129E 126E-132E
22 51W 54W-48W 53 135E 132E-138E
23 45W 48W-42W 54 141E 138E-144E
24 39W 42W-36W 55 147E 144E-150E
25 33W 36W-30W 56 153E 150E-156E
26 27W 30W-24W 57 159E 156E-162E
27 21W 24W-18W 58 165E 162E-168E
28 15W 18W-12W 59 171E 168E-174E
29 9W 12W-6W 60 177E 174E-180E
30 3W 6W-0 All values are expressed in full degrees east
31 3E 0-6E (E) or west (W) of Greenwich (0), Central
Meridians, and Longitude Ranges.
B-20
GeoTIFF Capabilities
Output to GeoTIFF - Projection Systems
The GeoMedia Professional Output to GeoTIFF functionality supports a limited number of
predefined projection coordinate systems. These predefined projection systems are combinations
of projection algorithms with predefined parameters (typically they are zones within zoned
projections such as UTM) and preset datums. Additionally, the GeoTIFF specification assumes
that these predefined systems are defined with specific model (storage) units and are centered at
(0,0) (they have no storage origin offset defined in the GeoMedia coordinate system). When the
horizontal storage unit for the Output to GeoTIFF coordinate system differs from the specified
GeoTIFF model storage unit in the table below, the GeoTIFF GeoKey for the specified unit will be
used, and an appropriate scaling for the units difference will be applied to the model-to-pixel
transformation matrix that is written concurrently with the coordinate system GeoKeys.
The projected type coordinate systems supported for the GeoMedia Professional Output to
GeoTIFF functionality are as follows:
Note: The UTM entries are sorted alphabetically by geodetic datum name.
Projection Definition Geodetic Datum Storage

Unit
British National Grid Ordnance Survey of Great Britain 1 meter
1936
Gauss-Kruger (3-degree) zones 1-5 Deutsche Hauptdreiecksnetz 1 meter
Gauss-Kruger (3-degree) zones 5-8 Militar-Geographische Institut (MGI) 1 meter
Gauss-Kruger (3-degree) zones 9-15 European 1950 1 meter
Gauss-Kruger (3-degree) zones 7-64 Pulkovo 1942 1 meter
Gauss-Kruger (3-degree) zones 7-64 Pulkovo 1995 1 meter
Gauss-Kruger (3-degree) zones 25-45 Beijing 1954 1 meter
Japan Plane Rectangular (Tokyo) zones 1-19 Tokyo 1 meter
Laborde Grid (Default Madagascar Tananarive Observatory 1925 1 meter
parameters)
New Zealand Map Grid Geodetic Datum 1949 1 meter
State Plane Coordinate System 1927 (all NAD 27 (or preset old island datums 1
zones) for some zones) Survey
Foot
State Plane Coordinate System 1983 (all NAD 83 1 meter
zones)
B-21
State Plane Coordinate System 1983 (all NAD 83 – HARN Upgrade 1 meter
zones except Alaska, North and South
Carolina, and Pennsylvania)
Switzerland LV03 CH1903 1 meter
Switzerland LV95 CH1903+ 1 meter
Universal Polar Stereographic, both Northern WGS 84 1 meter
and Southern Hemisphere cases
UTM zones 37-38, Northern Hemisphere Adindan 1 meter
UTM zones 38-39, Northern Hemisphere AFG (Afgooye) 1 meter
UTM zones 37-39, Northern Hemisphere Ain el Abd 1970 1 meter
UTM zones 22-24, Southern Hemisphere Aratu 1 meter
UTM zones 34-36, Southern Hemisphere Arc 1950 (EPSG Definition) 1 meter
UTM zones 35-37, both Northern and Arc 1960 1 meter
Southern Hemisphere
UTM zones 48-58, Southern Hemisphere Australian Geodetic 1966 1 meter
(Australian Map Grid)
UTM zones 48-58, Southern Hemisphere Australian Geodetic 1984 1 meter
(Australian Map Grid)
UTM zones 19-20, Northern Hemisphere Average Terrestrial System 1977 1 meter
UTM zones 48-50, Southern Hemisphere Batavia 1 meter
UTM zones 17-18, Northern Hemisphere Bogota Observatory 1 meter
UTM zones 32-33, Southern Hemisphere Camacupa 1 meter
UTM zones 34-36, Southern Hemisphere Cape (EPSG Definition) 1 meter
UTM zone 32, Northern Hemisphere Carthage (EPSG Definition) 1 meter
UTM zones 23-24, Southern Hemisphere Corrego Alegre 1 meter
UTM zone 29, Northern Hemisphere Datum 73 1 meter
UTM zone 32, Northern Hemisphere Douala 1 meter
UTM zones 28-38, Northern Hemisphere EUREF89 (ETRS89) 1 meter
UTM zones 28-38, Northern Hemisphere European 1950 1 meter
UTM zones 39-40, Northern Hemisphere Fahud 1 meter
UTM zone 33, Northern Hemisphere Garoua 1 meter
UTM zones 48-58, Southern Hemisphere Geocentric Datum of Australia 1 meter
(Map Grid of Australia 1994) (GDA94)
UTM zone 50, Southern Hemisphere Gunung Segara 1 meter
UTM zones 47-48, Northern Hemisphere Indian 1954 1 meter
UTM zones 46-54, Southern Hemisphere Indonesian 1974 1 meter
B-22
UTM zones 46-53, Northern Hemisphere Indonesian 1974 1 meter

UTM zone 29, Northern Hemisphere IRENET95 1 meter
UTM zones 45-46, Northern Hemisphere Kalianpur 1937 1 meter
UTM zones 47-48, Northern Hemisphere Kertau 1948 1 meter
UTM zones 20-21, Northern Hemisphere La Canoa 1 meter
UTM zone 31, Northern Hemisphere Lome 1 meter
UTM zone 32, Southern Hemisphere Malongo 1987 1 meter
UTM zone 37, Northern Hemisphere Massawa 1 meter
UTM zone 32, Southern Hemisphere Mhast 1 meter
UTM zones 31-32, Northern Hemisphere Minna 1 meter
UTM zone 32, both Northern and M’Poraloko (EPSG Definition) 1 meter
Southern Hemispheres
UTM zones 3-22, Northern Hemisphere NAD27 1 meter
UTM zones 3-23, Northern Hemisphere NAD83 1 meter
UTM zone 2, Southern Hemisphere NAD83-HARN 1 meter
UTM zones 38-40, Northern Hemisphere Nahrwan 1 meter
UTM zone 20, Northern Hemisphere Naparima, BWI 1 meter
UTM zones 38-39, Northern Hemisphere National Geodetic Network 1 meter
UTM zones 58-60, Southern Hemisphere New Zealand Geodetic Dataum 2000 1 meter
UTM zones 29-32, Northern Hemisphere North Sahara 1959 (EPSG Definition) 1 meter
UTM zone 32, Southern Hemisphere Pointe Noire 1948 (EPSG Definition) 1 meter
UTM zone 28, Northern Hemisphere Porto Santo 1936 1 meter
UTM zone 20, Northern Hemisphere Puerto Rico 1 meter
UTM zones 22-23, Northern Hemisphere Qornoq 1 meter
UTM zone 50, Southern Hemisphere Samboja 1 meter
UTM zones 20-21, Southern Hemisphere Sapper Hill 1943 1 meter
UTM zone 33, Southern Hemisphere Schwarzeck 1 meter
UTM zone 28, Northern Hemisphere Selvagem Grande 1938 1 meter
UTM zones 17-20 and 22, Southern South American 1956 1 meter
Hemisphere
UTM zones 18-21, Northern Hemisphere South American 1956 1 meter
UTM zones 17-25, Southern Hemisphere South American 1969 1 meter
UTM zones 18-22, Northern Hemisphere South American 1969 1 meter
UTM zones 35-36, Northern Hemisphere Sudan 1 meter
UTM zones 38-39, Southern Hemisphere Tananarive Observatory 1925 1 meter
B-23
UTM zones 49-50, Northern Hemisphere Timbalai 1948 1 meter

UTM zones 39-40, Northern Hemisphere Trucial Coast 1948 1 meter
UTM zones 1-60, both Northern and WGS 72 1 meter
Southern Hemisphere
UTM zones 1-60, both Northern and WGS 72 Transit Broadcast Ephemeris 1 meter
Southern Hemisphere
UTM zones 1-60, both Northern and WGS 84 1 meter
Southern Hemisphere
UTM zone 28, Northern Hemisphere Yoff 1 meter
UTM zone 21, Northern Hemisphere Zanderij 1 meter
Geographic Systems
The GeoMedia Professional Output to GeoTIFF functionality also supports writing geographic
coordinate systems on certain available datums. The GeoTIFF specification assumes that these
predefined systems are defined with specific model (storage) units and are centered at (0,0) (they
have no storage origin offset defined in the GeoMedia coordinate system). When the horizontal
storage unit for the Output to GeoTIFF coordinate system differs from the specified GeoTIFF
model storage unit in the table below, the GeoTIFF GeoKey for the specified unit will be used, and
an appropriate scaling for the units difference will be applied to the model-to-pixel transformation
matrix that is written concurrently with the coordinate system GeoKeys.
The geographic type coordinate systems supported for the GeoMedia Professional Output to
GeoTIFF functionality are as follows:
Geodetic Datum Storage Unit

Adindan 1 degree
AFG (Afgooye) 1 degree
Agadez 1 degree
Ain el Abd 1970 1 degree
American Samoa Datum 1962 1 degree
Amersfoort 1 degree
Ancienne Triangulation Francaise 1 grad
Aratu 1 degree
Arc 1950 (EPSG Definition) 1 degree
Arc 1960 1 degree
Australian Geodetic 1966 1 degree
B-24

Australian Geodetic 1984 1 degree
Average Terrestrial System 1977 1 degree
Barbados 1 degree
Batavia 1 degree
Beduaram 1 degree
Beijing 1954 1 degree
Bermuda 1957 1 degree
Bern 1898 1 degree
Bern 1938 1 degree
Bogota Observatory 1 degree
Bukit Rimpah 1 degree
Camacupa 1 degree
Campo Inchauspe 1 degree
Cape (EPSG Definition) 1 degree
Carthage (EPSG Definition) 1 degree
CH1903 1 degree
CH1903+ 1 degree
CHTRF95 1 degree
Chua Astro 1 degree
Conakry 1905 1 degree
Corrego Alegre 1 degree
Cote d’Ivoire 1 degree
Datum 73 1 degree
Dealul Piscului 1933 1 degree
Dealul Piscului 1970 1 degree
Deir ez Zor 1 degree
Deutsche Hauptdreiecksnetz 1 degree
Douala 1 degree
EUREF89 (ETRS89) 1 degree
European 1950 1 degree
European 1987 1 degree
Fahud 1 degree
Gan 1970 1 degree
Garoua 1 degree
Geocentric Datum of Australia (GDA94) 1 degree
B-25

Geodetic Datum 1949 1 degree
Greek 1 degree
Greek GRS 1987 1 degree
Gunung Segara 1 degree
Guyane Francaise 1 degree
Hartebeesthoek 94 1 degree
Herat North 1 degree
Hito XVIII 1963 1 degree
Hong Kong 1980 1 degree
Hungarian Datum 1972 1 degree
Hu-Tzu-Shan 1 degree
Indian 1954 1 degree
Indonesian 1974 1 degree
IRENET95 1 degree
Jamaica 1875 1 degree
Jamaica 1969 1 degree
Japan Geodetic Datum 2000 1 degree
Kalianpur 1880 1 degree
Kandawala 1 degree
Kartastokoordinaattijarjestelma (KKJ) 1 degree
Kertau 1948 1 degree
Korean Datum 1995 1 degree
Kuwait Oil Company 1 degree
Kuwait Utility 1 degree
La Canoa 1 degree
Lake 1 degree
Leigon 1 degree
Liberia 1964 1 degree
Lisbon 1 degree
Lithuania 1994 (ETRS89) 1 degree
B-26

Loma Quintana 1 degree
Lome 1 degree
Luzon 1 degree
Mahe 1971 1 degree
Makassar 1 degree
Malongo 1987 1 degree
Manoca 1 degree
Massawa 1 degree
Merchich (EPSG Definition) 1 degree
Mhast 1 degree
Militar-Geographische Institut 1 degree
Minna 1 degree
Monte Mario 1 degree
M’Poraloko (EPSG Definition) 1 degree
NAD 27 1 degree
NAD 83 1 degree
NAD 83 – HARN 1 degree
Nahrwan 1 degree
Naparima, BWI 1 degree
National Geodetic Network 1 degree
New Zealand Geodetic Datum 2000 1 degree
NGO 1948 1 degree
Nord de Guerre 1 grad
North Sahara 1959 (NGA Definition output same as 1 degree
EPSG Definition)
North Sahara 1959 (EPSG Definition) 1 degree
Nouvelle Triangulation Francaise 1 degree
NSWC 9Z-2 1 degree
Old Egyptian 1907 1 degree
Old Hawaiian 1 degree
Ordnance Survey of Great Britain 1936 1 degree
OS (SN) 1980 1 degree
OSGB 1970 (SN) 1 degree
Padang 1884 1 degree
Palestine 1923 1 degree
B-27

Pointe Noire 1948 (EPSG Definition) 1 degree
Porto Santo 1936 1 degree
Provisional South Chilean 1963 (output as Hito XVIII 1 degree
1963 as per NGA)
Puerto Rico 1 degree
Pulkovo 1942 1 degree
Pulkovo 1995 1 degree
Qatar 1948 1 degree
Qatar National 1 degree
Qornoq 1 degree
Reseau Geodesique Francais 1993 (RGF93) 1 degree
Reseau National Belge 1950 1 degree
Reseau National Belge 1972 1 degree
Samboja 1 degree
Sapper Hill 1943 1 degree
Schwarzeck 1 degree
Segora 1 degree
Selvagem Grande 1938 1 degree
Serindung 1 degree
S-JTSK 1 degree
South American 1956 1 degree
South American 1969 1 degree
Sudan 1 degree
Swedish RT38 1 degree
Swedish RT90 1 degree
Tananarive Observatory 1925 1 degree
Timbalai 1948 1 degree
TM65 1 degree
TM75 1 degree
Tokyo 1 degree
Trinidad 1903 1 degree
Trucial Coast 1948 1 degree
Voirol 1875 (EPSG Definition) 1 degree
Voirol 1960 (Obsolete EPSG Definition – now equated 1 degree
with North Sahara 1959)
B-28

WGS 72 1 degree
WGS 72 Transit Broadcast Ephemeris 1 degree
WGS 84 1 degree
Yacare 1 degree
Yoff 1 degree
Zanderij 1 degree
Read from GeoTIFF (Image Placement)

GeoMedia and GeoMedia Professional read GeoTIFF information and use it to georeference
images when the coordinate system described by the GeoTIFF tags meets certain criteria.
Generally, the coordinate system must be one that is defined by the GeoTIFF specification and also
is defined within the GeoMedia Coordinate Systems Services Automation model.
The specific coordinate systems read from GeoTIFF by GeoMedia include the following:
1. All coordinate systems described above in the Output to GeoTIFF functionality, both
Projection and Geographic systems.
2. Projection system codes for some zones of the State Plane Coordinate System 1983 that do not
reference 1 meter as the storage unit, but instead use either international or survey feet. As
described above, it is not necessary for us to use the codes in the Output to GeoTIFF
functionality but we will read them if other vendors produce images that use them.
3. Customized geographic systems that define their datum and resolution separately. Such cases
are allowed to use a user-defined datum and ellipsoid and may define a resolution different
from the predefined geographic systems found in the Output to GeoTIFF functionality.
4. Zoned projection systems based upon any of the available geodetic datums found in the
Output to GeoTIFF functionality, using 1-meter resolution. These include Universal
Transverse Mercator, Universal Polar Stereographic, and the 3-degree Gauss-Kruger system.
Note that the geodetic datums may include any found in the above Output to GeoTIFF
capability lists for geographic as well as projection systems. The geodetic datum may also be
defined using a user-defined datum and ellipsoid.
5. Projection systems with customized parameters, resolution, and datum. Datum possibilities
include any of the above-mentioned predefined datums plus user-defined datums.
The list of projection algorithms includes the following:
• Albers Equal Area
• Azimuthal Equidistant
• Cassini Soldner
• Cylindrical Equirectangular
B-29
• Equidistant Conic
• Gnomonic
• Laborde
• Lambert Azimuthal Equal Area
• Lambert Conformal Conic
• Mercator
• Miller Cylindrical
• Oblique Stereographic (GeoTIFF code limited to oblique aspect, not polar)
• Orthographic
• Polar Stereographic
• Polyconic
• Robinson
• Sinusoidal
• Stereographic
• Transverse Mercator
• Undefined (Rectangular Grid)
• Van der Grinten
B-30
Raster Information
Raster Formats Supported in GeoMedia

Place: G = Georeferenced (if georeferencing information is available)
W = Georeferenced through World File support (*.tfw, *.sdw, *.jgw)
H = By header (requires .csf or .dgn file)
I = Interactively
Format/Type Ext. Comp. Tiles Bits Main Use/Notes Place
Bitmap 1 .bmp - No 1 B/W I, W
Bitmap 2 .bmp - No 8 Grayscale I, W
Bitmap 9 .bmp RLE No 1 B/W I, W
Bitmap 28 .bmp - No 24 RGB color I, W
Bitmap 29 .bmp RLE, PB No 8 Grayscale I, W
CALS 24 (1A) .cal CCITTG4 No 1 B/W high-res line drawings I, W
CALS 24 (1B) .cal CCITTG4 No 1 B/W high-res line drawings I, W
CALS 24 (2B) .cal CCITTG4 Yes 1 B/W high-res line drawings I, W
GeoTIFF .tif Yes Georeferenced TIFF G, I
Hitachi 1 .hrf - No 1 B/W AutoCAD applications I
Hitachi 2 .hrf - No 8 Grayscale AutoCAD applications I
Hitachi 9 .hrf RLE No 1 B/W AutoCAD applications I
Hitachi 27 .hrf RLE No 24 Color AutoCAD applications I
Hitachi 28 .hrf - No 24 Color AutoCAD applications I
Hitachi 29 .hrf RLE, PB No 8 Grayscale AutoCAD applications I
IGS 9 .rlc RLE No 1 B/W advanced CAD applications I
IGS 29 .igs RLE No 8 Grayscale advanced CAD I
applications
Intergraph 2* .cot - Yes 8 Grayscale G, H, I
Intergraph 9 .rle RLE No 1 B/W G, H, I
C-1
Raster Formats Supported in GeoMedia (continued)

Format/Type Ext. Comp. Tiles Bits Main Use/Notes Place
Intergraph 24* .cit CCITTG4 Yes 1 B/W facsimile images G, H, I
Intergraph 27* .rgb RLE Yes 24 RGB color G, H, I
Intergraph 28* .rgb - Yes 24 RGB color G, H, I
Intergraph 29* .rgb RLE, PB Yes 8 Grayscale G, H, I
Intergraph 30* JPEG Yes 8 Grayscale G, H, I
Intergraph 31* JPEG Yes 24 RGB color G, H, I
JFIF .jpg JPEG No 8/24 Greyscale/RGB W, I
PCX 9 .pcx RLE No 1 B/W I
PCX 27 .pcx RLE No 8 Palette color I
PCX 29 .pcx RLE, PB No 8 Grayscale I
TIFF 1 .tif - Yes 1 B/W G, W, I
TIFF 2 .tif - Yes 8 Grayscale G, W, I
TIFF 9 .tif PB Yes 1 B/W G, W, I
TIFF 24 .tif CCITTG4 Yes 1 B/W facsimile images G, W, I
TIFF 27 .tif PB Yes 24 RGB color G, W, I
TIFF 28 .tif - Yes 24 RGB color G, W, I
TIFF 29 .tif PB Yes 8 Grayscale G, W, I
USGS DOQ .doq None No 8 OrthoQuads G, I
MrSID, ECW .sid, Wavelet Yes 8/24 Grayscale/RGB W, I
.ecw
ESRI .bip None No 8 Satellite data W, I
ESRI .bil None No 8 Satellite data W, I
PNG 9 .png RLE/ZIP No 1 B/W W, I
PNG 29 .png RLE/ZIP No 8 Grey or Palette W, I
PNG 27 .png RLE/ZIP No 24 RGB color W, I
JPEG 2000 .jp2 Wavelet Y 8 Greyscale G, W, I
JPEG 2000 .jp2 Wavelet Y 24 RGB Color G, W, I
* With or without geo-tie application packets
C-2
Raster Information
Compression Techniques
Format Description
CCITTG4 Consultative Committee on International Telephone and Telegraph
Group 4 format is standard for transmission and storage of bilevel
facsimile images.
JPEG Joint Photographic Experts Group format uses a block-by-block
conversion to frequency space and stores a discrete cosine series
representation of the frequency space.
LZW Lempel-Ziv & Welch algorithm compresses binary, grayscale, or
color data. This method was not used for a time because of patent
and licensing issues.
PB Packbits algorithm compresses binary, grayscale, or color data.
Packbits and Intergraph Type 29 are good for general-purpose
raster data, continuous-tone imagery, and RLE data. For certain
types of images, such as map images, significantly better disk
compression is achieved with a different RLE format, such as
Intergraph Type 9.
RLE Run-Length Encoded. A run length is a unit that describes a series
of contiguous pixels in a raster line that all have the same value.
Run lengths are used to achieve data compression in binary
scanned data and color run-length data. Long sequences of 0s, 1s,
or identical color indexes are identified and recorded using less
data than would otherwise be required to list the individual values
of the series of pixels.
Wavelet An algorithm for grayscale and color data. Used by MrSID, ECW,
and JPEG2000 format images.
ZIP Similar to LZW, it was developed as a legal replacement for LZW.
C-3
Tiling
Format Description
Tiling When raster data becomes large, it may be necessary to subdivide
it into smaller sections that can be loaded into memory and
manipulated individually. These sections are called tiles. A tiled
raster file consists of the standard raster-file header, immediately
followed by additional data specifying the tile information. Tiling
does not make the raster file smaller, so it is not a compression
technique. Rather, it breaks a raster file into manageable parts that
the system can use more easily. Tiling a file often speeds up
interactive display and editing operations. But tiling a run-length-
encoded file can make the file much larger on the disk because any
given run-length may be no longer than the relatively small tile
dimension. Therefore, many short run-length entries may be
required in place of a previous single, long entry.
Data Types
Data Type Description
Binary Consists of pixels that are either on or off to represent the
foreground and background data. Uncompressed binary data
requires one bit to store each pixel.
Grayscale or Contains coded intensity values usually ranging from 0 to 255.
continuous tone Generally uses one byte (8 bits) of data to represent each pixel.
8-Bit Color Uses a color table in the file header to identify the color of each
pixel. As with grayscale data, each uncompressed pixel is
represented by one byte of data. This byte of data points to a
color-table entry containing a 24-bit color definition. There may
be up to 256 slots in a color table, although all of the slots may not
necessarily be used.
24-Bit Color Requires three bytes of data to represent the color of each pixel.
Each byte represents the intensity of a color: one byte for red, one
byte for green, and one byte for blue. The different intensities of
all three colors combine to create all other possible colors. For
example, a lemon-yellow pixel might be stored with an intensity
value of 255 red, 219 green, and 109 blue.
C-4
Raster Information
File Types and Categories Listed for Inserting a

Georeferenced Image
File Types and Extensions
TIFF JFIF MrSID ECW INGR USGS DOQ
.tif, .tiff .jpg, .jpeg .sid .ecw .cot, .rgb, .cit .doq, .key
Placement Mode
Intergraph Geo-Tie Information - - - - X -
GeoTIFF X - - - - -
Intergraph Header Matrix X - - - X -
USGS DOQ - - - - - X
World File X X X - - -
Other with Internal Coordinate - - - - - -
System
Other with External Coordinate - - - X - -
System
Note: Most ECW files do not require a World file. Use the Other with external
coordinate system file mode of georeferencing, and provide a .csf that defines the
coordinate system of the ECW files. This is the preferred method for georeferenced
placement of ECW. Also, be sure to use ISRU's "Display Header" to determine file
format; file extensions are often incorrect or misleading.
C-5
C-6
Layout Window Graphics
Commands
The Layout Window Graphics commands, or drawing commands, are enabled when you
select Window > Show Layout Window to display the layout window. You access these
commands from the various layout window toolbars and menus.
This appendix simply lists these commands following their menu groupings. For ease of
use, complete documentation for these commands consists of a context-sensitive online
Help topic for each command, which you can access by pressing the F1 key. This
appendix also lists the commands used for placing and manipulating map graphics in a
layout window; these commands are described in the “Designing Map Layouts for Printing
in the Layout Window” chapter.
See the “Working with Layout Windows”, “Designing Map Layouts for Printing in the
Layout Window”, and “Printing in GeoMedia” chapters for information on layout
windows.
Placing Graphics into a Layout Sheet

Line Circle
Polyline Ellipse
Arc Polygon
Curve Symbol
Rectangle
Editing Graphics in a Layout Sheet

Move Trim to Intersection
Spin Extend to Intersection
Scale
Aligning Graphics in a Layout Sheet

Align Left Align Top
Align Center Align Middle
Align Right Align Bottom
Distributing Graphics in a Layout Sheet

Distribute Horizontally Distribute Vertically
D-1
Grouping Graphics in a Layout Sheet

Group Ungroup
Ordering Graphics in a Layout Sheet

Bring to Front Bring Forward
Send to Back Send Backward
Spinning or Flipping Graphics in a Layout Sheet

Spin Flip Horizontally
Spin Left Flip Vertically
Spin Right
Nudging Graphics in a Layout Sheet

Up Left
Down Right
Working with Symbols in a Layout Sheet

Create Symbol Symbol (Place Active Symbol)
Set Active Symbol
Inserting Objects into a Layout Sheet

Insert > Object
Additional Layout Window Tools

Text Delete
Apply Linear Style Line Color
Line Width Line Pattern
Line Terminators Fill
Edit Commands in the Layout Window

Edit >
Undo Select All
Redo Delete
Cut Links
Copy
Paste
Paste Special
D-2
Layout Window Graphics Commands
View Commands in the Layout Window

View > Grid Display
Zoom > Grid Snap
In Working Sheets
Out Background Sheets
Previous Drawing Toolbox
to Actual Size Toolbars
Fit
Update
Sheet Commands in the Layout Window

Sheets >
Insert Sheet Import Layout
Delete Sheet Export Layout
Rename Sheet
Insert and Layout Commands in the Layout Window

Insert > Layout >
Layout Frames Layers
Graphics Into Layout Frames Layer Groups
Map Update Map Graphics
Legend
North Arrow
Scale Bar
Data Table
Cartographic Grid
Reference Grid
Reference Index
Object
Tool Commands in the Layout Window

Tools >
Measure Distance
SmartSnap Settings
Options
D-3
Window Commands in the Layout Window

Window >
New Map Window Cascade
New Data Window Tile Horizontally
Hide Layout Window Tile Vertically
Layout Window Properties
D-4
Conversion Tables
The following tables contain the multiplication factors for converting from the
International System of Units (metric) to the United States Customary System and from the
United States Customary System to the International System of Units (metric). These
tables are useful with various GeoMedia functions, such as the Measure Distance and
Scale Bar Properties commands and the Units and Formats tab of the Define
Coordinate System File dialog box.
International System of Units to United States

Customary System
To Convert from To
Multiply by
International System of Units United States Customary System
Meters Feet 3.280840
Meters Yards 1.093613
Centimeters Inches 0.3937008
Centimeters Feet 0.03280840
Kilometers Miles (U.S. statute) 0.6213711
Kilometers Miles (international nautical) 0.5399568
Square meters Square feet 10.76391
Square meters Square yards 1.195990
Square centimeters Square inches 0.1550003
Square centimeters Square feet 0.00107639
Square kilometers Square miles (U.S. statute) 0.3861021
Hectares Acres 2.471054
Hectares Square miles 0.00386102
E-1
United States Customary System to International

System of Units
To Convert from To
Multiply by
United States Customary System International System of Units
Feet Meters 0.3048
Yards Meters 0.9144
Inches Centimeters 2.54
Feet Centimeters 30.48
Miles (U.S. statute) Kilometers 1.609344
Miles (international nautical) Kilometers 1.852
Square feet Square meters 0.09290304
Square yards Square meters 0.83612736
Square inches Square centimeters 6.4516
Square feet Square centimeters 929.0304
Square miles (U.S. statute) Square kilometers 2.589988
Acres Hectares 0.4046856
Square miles Hectares 258.9988
E-2
Catalogs: Installing, Setting Up,
and Upgrading Oracle and MS-SQL
Servers
This appendix provides information on installing, setting up, and upgrading Oracle and
MS-SQL Server for use with Catalogs. The dialog boxes and graphics in this appendix
reflect the use of Oracle 9i and MS-SQL Server 2000; the user interface may differ if you
are using different versions of Oracle or MS-SQL Server.
Note: The OracleCatalogScripts and the SqlServerCatalogScripts folders are delivered in

the product \Scripts folder.
See the “Working with Catalogs” chapter for related information about creating new
catalog connections and managing catalog connections.
Creating a Catalog Using Oracle

Enterprises can tie multiple GeoMedia catalog users to a single database using Oracle. The
following steps describe the procedure for installing the Oracle catalog, including creating
the Oracle database and creating a new Catalog connection.
Note: The following shows a typical installation and configuration of an Oracle catalog.
Your steps may vary depending on your organization's Oracle protocol. It is strongly
recommended that this function be performed by a qualified Oracle database administrator.
Quick Steps
Server:
1. Run the ora.sql script to create an Oracle database. This script is in the Oracle
folder of your GeoMedia distribution media.
Client:
2. Set up a service name.
3. Create an ODBC DSN.
4. Create a new Catalog connection.
F-1
Step One: Create an Oracle Catalog database.

The first step is to create the Oracle catalog database where metadata records are stored and
which will be used by GeoMedia Catalog functions.
The following are required to perform this step:
• Tablespace—At least one Oracle tablespace must exist for Catalog data and temporary
data. The preferred setup is to have two separate tablespaces, one for data and another
for temporary data.
Scripts:
• ora.sql—the master Oracle SQL script. Calls the following scripts in the order listed:
O CUSER.SQL—Creates the Catalog schema owner (user name).
O CTABLE.SQL—Creates all tables in the Catalog schema owner (user name).
O CINDEX.SQL—Creates all indexes.
O CREL.SQL—Creates foreign key relationships.
O CSCD.SQL—Creates triggers and sequences.
Other:
• Oracle SQL*Plus and SQLNet installed on the client machine
• Oracle database instance
• System password
1. Start SQL*Plus, and log in to the database as a user with database administrator
permissions.
2. Run the ora.sql script, and type @some_path\ora.sql, where some_path is the
path to the ora.sql file). Include the entire path, for example:
SQL> @c:\ora.sql
3. Follow the SQL prompts to create the database. You will be prompted for the
following:
• Enter the name of the schema that will be created. This is the name of the Oracle
schema that will be created when the script is run.
• Enter the name of the default tablespace used by the schema. All objects created
by the script will live in this tablespace. It must exist before the script is run.
• Enter the name of the temporary tablespace used by the schema. This is the
tablespace used for the schema's temporary segments. It must exist before the
script is run.
F-2
Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers for Catalogs
• Enter the Service Name (Alias) used to connect to the database. This is the Net
Service Name that will connect to the Oracle Instance. This must exist before the
script is run.
Note: The password of the new Catalog database is the same as the user name.
4. After the script has run, a log file will be generated. The log file is named
SMMSOracle.logand is placed in your Temp folder as defined by the TEMP User
environment variable. This directory is typically found at <System Drive
Letter>:\Documents and Settings\<User Name>\Local Settings\Temp on Windows
XP systems. Review this file for errors.
Note: With GeoMedia Catalog and Oracle, you may only log in to the database as the
database owner. Read-only and read-write users are not supported.
Step Two: Set up a service name for the client.

The next step is to set up a service name, or database alias, to identify and to attach the
client to the Oracle database.
The following steps demonstrate one of several available options for setting up a database
alias. You may follow a different method, depending on your organization's Oracle
protocol.
Before performing this task, verify that the following are installed for the client:
• Net Configuration Assistant
• The most recent Oracle ODBC drivers. See http://technet.oracle.com/.
1. Run Net Configuration Assistant.
2. Select the Local Net Service Name configuration
3. Select Add.
4. Click Next.
5. Select the proper Oracle version option.
6. Click Next.
7. Choose a networking protocol to connect to and communicate with the Oracle Catalog
database. Your choice will depend on your organization's protocol.
8. Click Next.
F-3
9. Enter the Host name of the computer where the Oracle Catalog database is stored. If
the Port Number is different from the default, enter the correct Port Number as well.
10. Click Next.
11. It is recommended that you run the user connection test before completing the Oracle
service configuration process.
12. Accept the Net Service name, or enter a new one.
13. Click Next.
14. Click Next.
15. When you are finished, click Next; then click Finish.
Step Three: Create ODBC DSN for the client.

The final step before attaching the GeoMedia Catalog client to the Oracle Catalog database
is to create an ODBC DSN.
1. Run Data Sources (ODBC) in the Administrative Tools folder of your Control Panel.
2. Choose User DSN or System DSN, following your organization's Oracle protocol.
3. Click Add.
4. Select Oracle ODBC Driver.
F-4
5. Enter a Data Source Name name, a TNS Service Name, and a User ID. Select the
remaining settings, following your organization's Oracle protocol. If the Oracle 9i
client is configured on the system, select the Workaround tab at the bottom of the
ODBC Oracle Driver Configuration dialog box, and be certain to check the Set
Metadata Id Default to SQL_True check box. Click OK when you are finished.
Step Four: Create a New Catalog Connection

The final step is to create a new catalog connection.
See the “Working with Catalogs” chapter for procedures for creating new catalog
connections.
Server Database Upgrades

Intergraph recommends the following workflow as a method to upgrade Oracle or MS-
SQL Server software versions.
F-5
1. Select Tools > Catalogs > Export Catalog Records.
2. On the General tab, select the appropriate Catalog connection from the drop-down
list.
3. Click Select All, or select all records that are to be saved/backed up for the update
process.
4. Select the GCE Export format option.
5. Type the appropriate location where the export files are to be saved in the Export
folder field, or use Browse to select it.
6. Click Apply.
The status of the export for the selected records is displayed in the status bar, the
selected catalog records are exported, and the files are stored in the destination folder.
7. Use ODBC Data Source Administrator to remove the DSN you created by using the
older version ODBC driver for Oracle or MS-SQL Server.
8. Uninstall the current version of your server database.
9. Install the new version of your server database.
10. Use either the Intergraph Oracle or the MS-SQL Server Catalog database scripts to
create the required metadata database tables and related database configuration.
11. Create a new DSN using a compatible version of the Oracle or MS-SQL Server ODBC
driver.
F-6
12. Select Tools > Catalogs > Import Catalog Records.
13. Type the location from where the import files are to be read, or use Browse to select
the location.
14. Click Select All, or select the appropriate file(s) from the Available files list.
Note: A tooltip is attached to the filenames so that long filenames can be read easily.
15. Select the GCE Import format option.

16. Select the appropriate Target catalog from the drop-down list; then click OK.
The status of the import for the selected set of files is displayed in the status bar, the
catalog records are imported from the selected source file(s) to the selected catalog,
and an Import complete message is displayed.
Creating a Catalog Using MS-SQL Server

Larger organizations can tie multiple GeoMedia Catalog users to a single database using
MS-SQL Server. To create an MS-SQL database for use with the GeoMedia Catalog, you
must have the MS-SQL Server Scripts that are provided by Intergraph. These scripts are in
the MS-SQL folder of your GeoMedia distribution media.
F-7
Important: These instructions follow the basic steps associated with an MS-SQL Server
Catalog installation, but they are not meant to provide an introduction to or a discussion of
the MS-SQL Server. Your installation may vary according to your organization's MS-SQL
Server configuration. It is strongly recommended that an experienced MS-SQL Server
administrator perform the installation.
Quick Steps
The following are the basic steps for installing an MS-SQL Server Catalog database:
1. Create a SQL database.
2. Run the MS-SQL Server Scripts as Administrator. These scripts are in the
MSSQL2000 folder or the MSSQL7.0 folder of your GeoMedia distribution media.
3. Create user accounts.
4. Set user permissions.
5. Create an ODBC connection for clients.
6. Create a new Catalog connection.
Step One: Create a SQL database.

The first step is to create an MS-SQL Server database to which your GeoMedia Catalog
users will attach and from where the metadata files will be accessed.
1. Open the MS-SQL Server Enterprise Manager.
2. Select Databases from the Manage menu (version 6.5 only).
3. Click the New Database icon.
4. Enter a Name for the database.
5. Select the Data Device and, optionally, the Log Device to which this database will be
assigned.
For more information on Data Device and Log Device, refer to your MS-SQL Server
documentation.
6. Select the desired database size settings.
Size will vary according to your MS-SQL configuration. Consult your MS-SQL
Server Administrator for an appropriate size setting.
7. Click OK.
F-8
Step Two: Run the MS-SQL Catalog scripts.

The next step is to run the MS-SQL Catalog scripts. These scripts enables your MS-SQL
database to work with the GeoMedia Catalog.
1. Open the MS-SQL Server Enterprise Manager.
2. Select SQL Server Query Analyzer from the Tools menu.
3. Select the database you created in Step 1 from the DB lookup list.
4. Click the Load SQL Script icon.
5. In the standard dialog box that opens, locate and select the main MS-SQL Server
Catalog script file, named sql.sql.
6. Click the Execute Query icon.
The database is created and configured for use with GeoMedia. Now you are ready to
create users.
Step Three: Create user accounts.

After creating the MS-SQL Catalog database, the next step is to create your MS-SQL
Catalog users and to grant them permissions based on the access to the MS_SQL Catalog
data you want them to have.
Note: It is advised that a qualified SQL database administrator create user accounts
following your organization’s SQL protocol.
The following steps provide a basic approach to creating user accounts. A qualified SQL
administrator may be able to identify a more efficient way of account creation that best
suits your organization’s needs.
The following are basic steps to creating MS-SQL user accounts. You may create read-
only and read-write users.
To create a user account for MS-SQL:

Here is a basic method for creating a user account for use with the MS-SQL Catalog
database.
You can follow these steps whether you are creating a read-write or read-only user. The
distinction between the two user types will be made when you set the permissions.
1. Open the MS-SQL Enterprise Manager.
First, you will define a login to be used by GeoMedia Catalog users to access the MS-
SQL Catalog database.
F-9
2. Expand the Security folder.

3. Right click the Logins icon.
4. Select New Login from the shortcut menu.
5. Type a name, such as catalog_user, in the Name field on the SQL Server
6. Click the SQL Server Authentication option.
7. Optionally, type a Password to accompany the login name.
8. Choose the MS-SQL Catalog database from the Database drop-down list.
9. Click the Database Access tab.
10. In the Permit column, click the check box next to the MS-SQL catalog database.
11. Click OK.
Step Four: Set user permissions.

Once you have created user accounts, the next step is to set permissions to grant your users
a level of access to Catalog data. You may grant a user read-only access or data
administrator (read-write) access.
Important: It is recommended that an account be granted the same permissions on all

tables. An account that is provided with different permissions on different tables may
result in errors in GeoMedia.
To set read-write permissions for MS-SQL:

1. Expand the Databases folder in the MS-SQL Enterprise Manager.
2. Expand the Users icon.
3. Right click the read-write user for which you want to assign permissions.
4. Select All Tasks | Manage Permissions from the shortcut menu.
5. In the Database User Properties dialog box, in the Object column, starting with the
table AT and ending with User_Defined, choose the Select, Insert, Update, Delete,
and DRI options for each table.
Note: Ignore objects that have the owner Information Schema.
F-10
6. Click Execute for the IsReadOnly, IsThesaurusKeywordAdmin, and

ISWebPublishAdmin stored procedures.
7. Finally, you must decide whether or not to provide read-write permission to two
Catalog features which are generally reserved for administrative-level personnel: the
Thesaurus/Keyword Admin and Web Publish features of the GeoMedia Catalog.
• The Thesaurus Keyword Admin tool allows the user to create and edit
organizational keyword lists within the Catalog.
• The Web Publish feature allows the user to manually provide or block Web search
access to Catalog records using Intergraph Catalog server applications in
GeoMedia WebMap.
As the permissions are set, the user will have access to these features. If you want to
change the permissions, do the following:
• If you want to deny the user read-write access to the Thesaurus Keyword Admin
tool, deselect the Insert, Update, and Delete permissions on the table
ID_Thesaurus_Lookup.
• If you want to deny the user read-write access to the GeoMedia Catalog Web
Publish feature, deselect the Insert, Update, and Delete permissions on the table
ID_Web_Publish.
8. Click Apply.
9. Click OK.
To set read-only permissions for MS-SQL Catalog:

1. Expand the Databases folder in the MS-SQL Server 7 Enterprise Manager.
2. Expand the Users icon.
3. Right click the user to whom you want to assign read-only permissions.
4. Select All Tables > Manage Permissions from the shortcut menu.
5. In the Database User Properties dialog box, in the Object column, starting with the
table AT and ending with User_Defined, choose only the Select option for each table.
Note: Ignore objects that have the owner Information Schema.
6. Click Execute for the ISReadOnly, ISThesaurusKeywordAdmin, and

ISWebPublishAdmin stored procedures.
7. Click Apply when you are finished.
F-11
Step Five: Create an ODBC connection for GeoMedia

Catalog users.
The next step is to create an ODBC data source (DSN) to be used to connect GeoMedia
Catalog users to the SQL database.
The following steps show a typical Catalog ODBC connection. Your selections may vary
according to your organization's SQL protocol.
Follow these steps for each client:
1. Run Data Sources (ODBC) in the Administrative Tools folder of your Control Panel.
2. Choose either the User DSN or the System DSN tab, following your organization's
SQL protocol.
3. Click the Add button to create a new DSN.
4. Select SQL Server from the list of drivers.
5. Click Finish.
The Data Source Wizard launches.
6. Enter a data source name in the Name field.
This name will be used by the GeoMedia Catalog as the DSN to connect to the MS-
SQL Catalog database.
7. Optional: Enter a description of the data source in the Description field.
8. Enter the name of an MS-SQL Server on your network in the Server field.
You can either select an existing server name from the list or enter a new name. If you
select an existing server name, no further configuration is needed.
9. Click Next.
The second wizard screen opens, allowing you to select a method of authentication
when a GeoMedia Catalog user attaches to the MS-SQL Catalog database.
10. Choose the With SQL Server authentication using a login ID and password
entered by the user option, and enter a valid Login ID below. Leave the Password
field blank.
Reminder: These steps are intended to outline a typical configuration. Your MS-SQL
protocol may differ.
11. Click Next.
F-12
12. Click Change the default database to, and select the MS-SQL Catalog database from
the drop-down list.
13. Click Next.
The fourth wizard screen opens.
14. Choose Let SQL Server ODBC driver choose the translation method if not already
selected).
15. Leave the default selections on the next wizard screen as they are, and click Finish.
The ODBC Microsoft SQL Server Setup dialog box will then display. You can use
this dialog box to verify the ODBC DSN by testing the connection.
16. Click Test Data Source to test the data source configuration settings.
17. Upon successful results, click OK.
Step Six: Create a New Catalog Connection

The final step is to create a new catalog connection.
See the “Working with Catalogs” chapter for procedures for creating new catalog
connections.
F-13
F-14
LRS Data Structures
This appendix describes the Linear Referencing System (LRS) data structures that are directly
supported.
Overview
Data for Transportation Asset systems (using dynamic segmentation) generally falls into two
categories: LRS data and Event data. LRS data describes the naming, measurement system, and
geometry of the linear network. Event data describes attributes of the linear network, such as
pavement conditions, roadway inventory data (for example, guardrails and signage), and accident
occurrences. This software provides great flexibility in the structuring of both of these data types,
as shown below:
LRS Data Structure Options Event Data Structure Options
• Measure • Measure
• Measure with Internal Markers • Marker Offset
• Measure with External Measure Markers • Coordinate
• Duration • Duration
• Duration with Internal Markers
• Duration with External Measure Markers
Note: There are additional data structures associated with Multilevel LRS. These options are
available if you also have GeoMedia Transportation installed. The details of these additional data
structures are described in the “LRS Data Structures” appendix of the Working with GeoMedia
Transportation document.
Single-Level LRS Data Structures

An LRS data structure is typically made up of a number of geometric segments that together define
the entire LRS. All but the two External Marker options, described in the following subsections,
consist only of a table describing those segments. The External Marker options have an additional
table that describes marker points. Note that all of the field names used in the subsections to follow
are representative only. You are free to name the fields as you please.
G-1
Option 1 – Measure
The segments in this option are defined by a set of up to four LRS keys to name the route, a start
and an end measure value, and geometry.
BeginMeasure
EndMeasure
Direction of Segment
LRS Feature Class

Field Sample Description
PrimaryKey US The LRS key fields identify the "route" that this segment of the LRS
belongs to. This identification can be done with anywhere from 1 to 4
fields within the LRS feature class. These fields are the same fields the
event features will use to identify the "route".
In the sample shown PrimaryKey identifies the roadway system,
SecondaryKey contains the route number, TertiaryKey identifies whether
the segment is part of a spur, and QuatenaryKey identifies whether this
segment is part of an alternative route. All together the route name is
"US6SA".
SecondaryKey 6 This is the 2nd key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
TertiaryKey S This is the 3rd key field that can be used to identify the "route" that this
QuatenaryKey A This is the 4th key field that can be used to identify the "route" that this
BeginMeasure 12.3 This is the measurement value for the beginning position of this feature.
EndMeasure 18.2 This is the measurement value for the ending position of this feature.
Geometry blob This field contains the linear geometry that describes the linear segment
geometrically.
Geometry True This Boolean (True/False) field declares whether the software should treat
Reversed this linear feature as is (False) or as if its digitizing direction were reversed
and its beginning were its end and vice-versa (True).
RegionID ORA This text field contains an identifier as to which region a particular
segment resides in. It is used to subdivide an LRS into more manageable
subsets. Its use is optional. The “ORA” in the sample shown is an ID code
for “Orange County”.
G-2
LRS Data Structures
Option 2 – Measure with Internal Measure Markers

and an end measure value, a Begin Marker name, an optional End Marker Name, and geometry.
The markers allow this structure to be used with event data using the Marker Offset option.
BeginMeasure EndMarker
BeginMarker EndMeasure
LRS Feature Class

"US6SA".
BeginMarker M45 This field stores a name for the beginning position of this feature.
EndMarker M46 This field stores a name for the ending position of this feature. Its use is
optional.
geometrically.
and its beginning were its end and vice-versa (True). The default value
should be set to False.
G-3
LRS Feature Class

subsets. Its use is optional. The “ORA” in the sample shown is an ID
code for “Orange County”.
G-4
LRS Data Structures
Option 3 – Measure with External Markers

and an end measure value, and geometry. This option also requires markers that are defined by up
to four LRS keys, a marker name, and a measure value. The markers allow this structure to be used
with event data using the Marker Offset option.
BeginMeasure Marker
Marker EndMeasure
LRS Feature Class

"US6SA".
geometrically.
G-5
Marker Feature Class

"US6SA".
MarkerName M34 This is the identifying name of the marker.
MarkerMeasure 17.5 This is the measurement value at the marker.
G-6
LRS Data Structures
Option 4 – Duration
measure value, a duration (length) value, and geometry.
BeginMeasure
Duration
LRS Feature Class

"US6SA".
Duration 5.9 This is distance value from the beginning position to the ending position
of this feature.
geometrically.
G-7
Option 5 – Duration with Internal Markers

measure value, a duration (length) value, a Begin Marker name, an optional End Marker Name, and
geometry. The markers allow this structure to be used with event data using the Marker Offset
option.
BeginMeasure EndMarker
BeginMarker Duration
LRS Feature Class

the segment is part of a spur, and LRSkey4 identifies whether this segment
is part of an alternative route. All together the route name is "US6SA".
of this feature.
BeginMarker M45 This field stores a name for the beginning position of this feature.
EndMarker M46 This field stores a name for the ending position of this feature. Its use is
optional.
geometrically.
G-8
LRS Data Structures
LRS Feature Class

G-9
Option 6 – Duration with External Measure Markers

measure value, a duration (length) value, and geometry. This option also requires markers that are
defined by up to four LRS keys, a marker name, and a measure value. The markers allow this
structure to be used with event data using the Marker Offset option.
BeginMeasure Marker
Marker
Duration
LRS Feature Class

"US6SA".
of this feature.
Geometry Blob This field contains the linear geometry that describes the linear segment
geometrically.
G-10
LRS Data Structures
LRS Feature Class

segment resides in. It is used to subdivide a LRS into more manageable
Marker Feature Class

"US6SA".
MarkerName M34 This is the identifying name of the marker.
MarkerMeasure 17.5 This is the measurement value at the marker.
G-11
Event Data Structures

Note that these structures have no geometry. The whole purpose of the dynamic segmentation
process is to combine the LRS data structure and the Event data structure to create a new geographic
feature. Note that all of the field names used in the subsections to follow are representative only.
You are free to name the fields as you please.
Option 1 – Measure
The events in this option are defined by a set of up to four LRS keys to name the route, a start
measurement, and for linear events only, an end measure value.
Event Feature Class

the segment is part of a spur, and LRSkey4 identifies whether this
"US6SA".
BeginMeasure 14.4 This is the measurement value for the beginning position of this event.
This field is required for both point and linear events.
EndMeasure 16.2 This is the measurement value for the ending position of this event. This
field is used for linear events only.
G-12
LRS Data Structures
Option 2 – Marker Offset

The events in this option are defined by a set of up to four LRS keys to name the route, a begin
marker name and an offset value, and for linear events only, an end marker name and offset value.
Event Feature Class

"US6SA".
BeginMarker M34 This is the name of the marker from which the beginning point of the
event is measured. This field is required for both point and linear events.
BeginOffset 0.6 This is distance value from the Begin Marker to the beginning position of
this event. This field is required for both point and linear events.
EndMarker M35 This is the name of the marker from which the ending point of the event
is measured. This field is used for linear events only.
EndOffset 0.4 This is distance value from the End Marker to the ending position of this
event. This field is used for linear events only.
G-13
Option 3 – Coordinates
The events in this option are defined by a set of up to four LRS keys to name the route, a begin X/Y
or Longitude/Latitude coordinate, and for linear events only, an end X/Y or Longitude/Latitude
coordinate.
X,Y
Event Feature Class

"US6SA".
BeginX 2546234.2 This is the X or Longitude coordinate for the beginning position of this
event. This field is required for both point and linear events.
BeginY 753124.4 This is the Y or Latitude coordinate for the beginning position of this
event. This field is required for both point and linear events.
EndX 2584123 This is the X or Longitude coordinate for the ending position of this
event. This field is used for linear events only.
EndY 745654.6 This is the Y or Latitude coordinate for the ending position of this event.
This field is used for linear events only.
G-14
LRS Data Structures
Option 4 – Duration
The events in this option are defined by a set of up to four LRS keys to name the route, a begin
measure, and a duration (length) value. The Duration option applies to linear events only.
Event Feature Class

"US6SA".
BeginMeasure 14.4 This is the measurement value for the beginning position of this event.
of this event. Note: The Duration option is for linear events only.
G-15
G-16
Supported SVG Element Types
Background
GeoMedia 6.1 offers a means of supporting symbols definitions from numerous formats
through implementation of a common symbol-serving interface. This appendix describes
the implementation of such an interface for the support of symbols that are created in an
SVG structure, which is XML based. This open format provides the user with the ability
to create new symbols and to convert existing symbols. These symbols can be used in
GeoMedia within styles to render points, lines, and areas.
Discussion
An SVG document is created according to the standard W3C SVG specifications, which
allow support for certain attributes and elements to make parametric behavior easier.
The following are the major sections of an SVG document relevant to symbol usage:
• XML version and encoding – A standard XML header. This header is not required.
Whether the header is provided or not, UTF-8 encoding is always assumed.
• Reference namespaces – Identify namespaces in use within the document. If
GeoMedia-structured symbol parameters are to be used, the gmsvgsym namespace
must be referenced.
For more information, see the “Metadata Element” section of this appendix.
• SVG – This root element for the document holds the sections for metadata (metadata),
graphics definitions (symbol), and drawing objects (use).
• Metadata – May include the GeoMedia SVG Symbol Metadata extension.
For more information, see the “Metadata Element” section of this appendix.
• Symbol – Contains symbols definitions. This section is used to segregate symbol
definitions from actual drawing requests.
• Use – Specifies actual use of a symbol definition at a particular coordinate location for
visualization within an SVG viewer. This element is not required by GeoMedia’s SVG
interpreter, but it is required by SVG viewers.
The symbol section contains the actual symbol definitions. Symbols may be composed of
various SVG geometry elements.
H-1
The following elements are supported by the GeoMedia SVG Symbol Server:
• svg • metadata • polygon • ellipse
• symbol • line • rect • path
• use • polyline • circle • text
• g
The nature of these elements, the attributes of these elements, and the components of those
attributes are discussed in the following discussion. Elements in the SVG file other than
these are ignored.
All distance and coordinate values, including those of fonts, are given in the unit of pixels,
which are defined as being 1/96th of an inch. Because the XML is structured as UTF-8,
the GeoMedia symbol interpreter will also handle Unicode symbols.
Versions and Variations

SVG documents in SVG 1.1 format are supported.
Supported Types
Refer to the W3C SVG specifications for further details on each element.
General Elements
As a general rule, if elements contain other elements, the contained elements (components)
inherit information defined on the container element (composite). One of the more
common uses of this inheritance is with styles. A characteristic of a style can be inherited
from the symbol, group, use, and like elements. As with any inheritance, inherited values
from the composite can be overwritten by values set on the component.
SVG Element
The <svg> element is the root for the SVG-structured contents to follow. The attributes of
the SVG element that will be supported are as follows:
Attribute Value Description
xmlns "http://www.w3.org/2000/svg" Defines the default
namespace of the XML
document.
xmlns:xlink "http://www.w3.org/1999/xlink" Defines the xlink namespace
and sets it to the xlink prefix.
It is only required if someone
uses the namespace.
H-2
xmlns:svg "http://www.w3.org/2000/svg” Defines the namespace for

SVG elements. This is not
required if SVG namespace is
the default.
xmlns:gmsvgsym "http://www.intergraph.com/GeoM Used to defined SVG
edia/gmsvgsym" metadata that is specific to
GeoMedia’s use. This is not
required if parametric
behavior is not required by
the symbol.
The following is an example of an svg element:
<svg xmlns="http://www.w3.org/2000/svg"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:gmsvgsym="http://www.intergraph.com/GeoMedia/gmsvgsym">
…
</svg>
Symbol Element
The <symbol> element is used to logically collect elements together to form a symbol. It
is much like a <g> element, with the exception that a symbol does not render. To use a
symbol element within an SVG viewer, it should be referenced by a use element. The
symbol defines its size using the viewBox attribute. Multiple symbols can exist within an
SVG document to provide a symbol library.
viewBox X origin, y origin, width, This defines the bounding box of the
and height. view port and is in the default units. The
user cannot specify units for any of the
four properties. The viewBox attribute is
required.
id String The identifier for the element. Although
not required by SVG, the GeoMedia
symbol interpreter requires it to exist.
style Font, stroke, and fill The attribute is not required. See the
characteristics supported. “Style Attribute” section for details.
Scaling or non-scaling of the gmscalepen:0 will mean that pen size
pen based on size, can be will be constant when the size of the
specified using the symbol changes. gmscalepen:1 will
“gmscalepen” flag. Valid mean that pen size will be scaled based
values are 0 and 1. Default on the size of the symbol.
value is 1.
H-3
transform Varies The attribute is not required. See the

“Transform Attribute” section for
details.
The following is an example of a symbol element:
<symbol id="RoadShield" viewBox="0 0 500 500" style="font-
size:50;font-family:Arial">
…
</symbol>
Use Element
The <use> element is used to define which symbols to actually use in an SVG display.
The user specifies a URI in an xlink:href attribute and specifies the x and y location where
the item’s (0,0) point should be moved to. This component is not used by the GeoMedia
symbol interpreter, and if included as a part of the symbol definition, it will be ignored.
The following is an example of a use element:
<symbol id="RoadShield" viewBox="0 0 500 500" style="font-
…
</symbol>
<use xlink:href="#RoadShield"/>
G Element
The <g> element gathers all of its child elements as a group and has an id attribute to give
that group a unique name.

id String The identifier for the element. Not required.
style Font, stroke, and fill The attribute is not required. See the “Style
characteristics supported. Attribute” section for details.
“Transform Attribute” section for details.
H-4
The following is an example of a group element:

<g id="Group1" style="font-size:50;font-family:Arial">
…
</g>
Metadata Element
Metadata included in the SVG content is specified within the <metadata> element and
allows symbol creators to define their own metadata for the symbol file. GeoMedia has
introduced the following new namespace to address parametric behavior:
xmlns:gmsvgsym=”http://www.intergraph.com/GeoMedia/svgsym”
The XML schema for this namespace defines a root element symbolParameters, which
may contain zero or more individual symbol parameters for influencing the symbol
content.
For the symbol to be parametric:
• Metadata should be defined as per the schema specified in the
SVGSymbolMetadataXMLSchema.doc document.
• Metadata should be placed before symbol definition(s) and optionally can go inside it.
Each successive metadata definition overrides the previous one based on the scope.
• Parametric criteria defined in metadata should match. That is, the “replaceID” attribute
value of the active (latest definition of) metadata should match with the “ID” attribute
value of the “text” element in a symbol. If it matches, the symbol is treated as a
parametric symbol; otherwise, it is not.
For more information on the SVG Symbol Metadata XML Schema for GeoMedia, see the
“SVG Symbol Metadata XML Schema” section of this appendix.
Geometry Elements
Line Element
The following section defines the attributes of a line element. These are the only attributes
supported, and all other attributes will be ignored.
x1 X start point The x value for the start point of the line. No
units can be given with the value.
y1 Y start point The y value for the start point of the line. No
H-5
x2 X end point The x value for the end point of the line. No
y2 Y end point The y value for the end point of the line. No
style Stroke characteristics The attribute is not required. See the “Style
supported. Attribute” section for details.
transform Varies The attribute is not required. See the “Transform
Attribute” section for details.
The following is an example of a line element:
<line id="Line1" x1=”100" y1=”50” x2=”320” y2=”240”
style="stroke-width:1; stroke-linecap:round;
stroke:#e1e100; fill:none;"/>
Polyline and Polygon Elements

The following section defines the attributes of polyline and polygon elements. The
distinction between the polygon and polyline elements is that the polygon element is
closed. These are the only attributes supported, and all other attributes will be ignored.
points “x1,y1 x2,y2 … xn,yn” A set of white-space-separated
coordinate pairs. No units can be given
with the value.
id String The identifier for the element. Not
required.
style Stroke and fill (polygon only) The attribute is not required. See the
characteristics supported. “Style Attribute” section for details.
“Transform Attribute” section for
details.
The following are examples of polyline and polygon elements:
<polyline id="Polyline1" points=”195,10 195,200”
stroke:#e1e100; fill:none;"/>
H-6
<polygon id="Polygon1" points=”150,0 150,200 300,100”

stroke:#e1e100; fill:#ff0000;"/>
Rect Element
The following section defines the attributes of a rect element. These are the only attributes
x x-upper-left The horizontal coordinate of the upper-left
point of the rectangle. No units can be given
with the value. Note that if x is not given, it
defaults to the viewBox x value.
y y-upper-left The vertical coordinate of the upper-left
point of the rectangle. No units can be given
with the value. Note that if y is not given, it
defaults to the viewBox y value.
width Width The width of the rectangle, which must be a
positive value. No units can be given with the
value.
height Height The height of the rectangle, which must be a
positive value. No units can be given with the
value.
style Stroke and fill The attribute is not required. See the “Style
The following is an example of a rect element:
<rect id="Rectangle1" x=”20” y=”20” width=”100”
height=”50” style="stroke-width:2; stroke:#e1e100;
fill:#ff00ff;"/>
Circle Element
The following section defines the attributes of a circle element. These are the only
attributes supported, and all other attributes will be ignored.
H-7

cx X center The horizontal coordinate of the center of the
circle. No units can be given with the value.
cy Y center The vertical coordinate of the center of the
r Radius The radius of the circle, which must be
positive. No units can be given with the value.
The following is an example of a circle element:
<circle id="Circle1" cx=”20” cy=”20” r=”10”
style="stroke-width:2; stroke:#e1e100; fill:#ff00ff;"/>
Ellipse Element
The following section defines the attributes of an ellipse element. These are the only
attributes supported, and all other attributes will be ignored.
cx X center The horizontal coordinate of the center of the
cy Y center The vertical coordinate of the center of the
rx X Radius The radius of the ellipse along the x-axis,
and the radius value must be positive. No
ry Y Radius The radius of the ellipse along the y-axis,
and the radius value must be positive. No
H-8
The following is an example of an ellipse element:

<ellipse id="Ellipse1" cx=”150” cy=”150” rx=”100”
ry=”50” style="stroke-width:2; stroke:#e1e100;
fill:#ff00ff;"/>
Path Element
The following section defines the attributes of a path element. These are the only attributes
d The set of flags and coordinates that describe
the path being drawn. No units can be given
with the value. See the “D Attribute”
section for details
D Attribute
The d attribute is used in the context of the path element. The following describes the
format of the d attribute. If the characteristic is uppercase, the position values are absolute,
but if the characteristic is lowercase, the position values are relative to the current point.
d Characteristics Value Description
M x1,y1 Sets the current location to a value defined by the x1,

y1 parameters. The “M” characteristic is like a move
to command.
m dx1,dy1 Sets the current location to a value defined by the
dx1 + the current x location, and dy1 + the current y
location. The “m” characteristic is like a move from
the current location by the offset value.
L x1,y1 Draws a line from the current point to x1, y1.
l dx1,dy1 Draws a line from the current point to the pointed
defined by the offset values of dx1, dy1.
H-9
A rx ry x- Draws an elliptical arc from the current point to x,y.

axis- The points are on an ellipse with x-radius rx and y-
rotation radius ry. The ellipse is rotated x-axis-rotation
large-arc degrees. If the arc is less than 180 degrees, the large-
sweep x y arc is 0; if greater than 180 degrees, the large-arc is 1.
If the arc is to be drawn in the positive direction, the
sweep is 1; otherwise, it is 0.
a rx ry x- Draws an elliptical arc from the current point to the
axis- relative location defined by the offset dx,dy. The
rotation points are on an ellipse with x-radius rx and y-radius
large-arc ry. The ellipse is rotated x-axis-rotation degrees. If
sweep dx the arc is less than 180 degrees, the large-arc is 0; if
dy greater than 180 degrees, the large-arc is 1. If the arc
is to be drawn in the positive direction, the sweep is
1; otherwise, it is 0.
z Closes the path by drawing a straight line where this
subpath began.
The following is an example of a path element:
<path id="Path1" d=”M6,199 L200,199 L200,5 L6,5z”
style="stroke-width:2; stroke:#e1e100; fill:#ff0000;"/>
Text Element
The following section defines the attributes of a text element. These are the only attributes
x x-upper-left The horizontal coordinate of the upper-left point of
the text. No units can be given with the value.
y y-upper-left The vertical coordinate of the upper-left point of the
text. No units can be given with the value.
text- “start”, “middle”, or The text-anchor attribute controls the horizontal
anchor “end” location of the anchor point. This is a left, center, or
right alignment for the text at the x and y origin.
style Font, stroke, and fill The attribute is not required. See the “Style
characteristics Attribute” section for details.
supported.
H-10
transform Varies The attribute is not required. See the “Transform

Attribute” section for details.
The following is an example of a text element:
<text id="Text1" x=”20” y=”20” style="font-
Here is the text
</text>
Common Attributes
Style Attribute
SVG specifies the presentational aspects of graphic elements using inline styles. We set
the value of the style attribute to a series of visual properties, and their values as described
in the following sections. The format of a style attribute is
“stylecharacteristic1:value;stylecharacteristic2:value2;…”. An example would be:
style=”stroke:#e1e100;stroke-width:1;stroke-opacity:0.5;”. For more information refer to
the W3C specification.
Stroke Characteristics: Lines are considered to be strokes of a pen drawn to a canvas.
The size, color, and style of the pen stroke are considered to be part of the line’s
presentation.
Stroke Value Description
Characteristics
stroke Color of line Specifies the color for a linear element. The color
value supported is RGB-encoded using two
hexadecimal digits per primary-color component, in
the order Red, Green, Blue, prefixed with a hash (#)
sign. For example, full red is encoded as “#ff0000”
(with no quotation marks). Note that this is the only
format supported. The exception is the word
“none,” which implies an opacity value of 0.
stroke-width Stroke width Specifies the width of the rendered line. No units
can be specified for this object.
stroke-dasharray Dash gap Specifies a series of numbers that tell the length of
sequence of dashes and gaps with which a line is to be drawn.
line Format is dash length, space, gap length, space, etc.
No units can be given with the values, and the
values are in quotes.
H-11
stroke-opacity Stroke Controls the opacity of a linear element by giving

opacity stroke-opacity a value ranging from 0.0 to 1.0; 0.0 is
entirely transparent, and 1.0 is entirely opaque.
stroke-linejoin “miter”, Specifies the shape of the corners of a polygon or
“bevel”, or series of lines. There are three types supported,
“round” which are listed in the value column.
stroke-linecap “butt”, Specifies an end cap of a line. There are three types
“round”, or supported, which are listed in the value column.
“square”
Fill Characteristics: Specifies the way in which the interior of a shape is to be filled.
Fill Value Description
Characteristics
fill Fill color Specifies the fill color for closed symbols like
boundaries and complex strings. The color value
supported is RGB-encoded using two hexadecimal
digits per primary-color component, in the order
Red, Green, Blue, prefixed with a hash (#) sign. For
example, full red is encoded as “#ff0000” (with no
quotation marks). Note that this is the only format
supported. The exception is the word “none,” which
implies an opacity value of 0.
fill-rule ”nonzero” The 'fill-rule' property indicates the algorithm that is
or “even- to be used to determine what parts of the canvas are
odd” included inside the shape. For a simple, non-
intersecting path, it is intuitively clear what region
lies "inside"; however, for a more complex path,
such as a path that intersects itself or where one
subpath encloses another, the interpretation of
"inside" is not so obvious.
The 'fill-rule' property provides two options for how
the inside of a shape is determined, nonzero and
evenodd.
nonzero:
This rule determines the "insideness" of a point on
the canvas by drawing a ray from that point to
infinity in any direction and then examining the
places where a segment of the shape crosses the ray.
Starting with a count of zero, add one each time a
path segment crosses the ray from left to right, and
subtract one each time a path segment crosses the ray
H-12
from right to left. After counting the crossings, if the

result is zero, the point is outside the path; otherwise,
it is inside.
Evenodd:
This rule determines the "insideness" of a point on
the canvas by drawing a ray from that point to
infinity in any direction and counting the number of
path segments from the given shape that the ray
crosses. If this number is odd, the point is inside; if
even, the point is outside.
fill-opacity Fill opacity Controls the opacity of an area by giving fill-opacity
a value ranging from 0.0 to 1.0; 0.0 is entirely
transparent, and 1.0 is entirely opaque.
Font Characteristics: Specifies the way that text will be drawn.
Font Value Description

Characteristics
font-size Size of font The property is the size of the font. User units
(points) are assumed, and no other units are
supported.
font-family Family The generic family names are “serif”, “sans-serif”,
name and “monospace”. Also supported are the standard
fonts available on the system.
font-style “italic” or There are two types of font styles that are supported,
“normal” which are listed in the value field.
font-weight “bold” and There are two types of font weights that are
“normal” supported, which are listed in the value field.
text-decoration “none”, There are three types of text decorations that are
“underline”, supported, which are listed in the value field.
or “line-
through”
H-13
Transform Attribute
The value of the transform attribute is a <transform-list>, which is defined as a list of
transform definitions which are applied in the order provided. The individual transform
definitions are separated by white space and/or a comma. The available types of transform
definitions include the following:
Transform Value Description
Characteristics
matrix matrix(a,b,c, Specifies a transformation in the form of a
d,e,f) transformation matrix of six values. Matrix
(a,b,c,d,e,f) is equivalent to applying the
transformation matrix [a b c d e f].
translate translate(<tx Specifies a translation by tx and ty. If <ty> is not
> [<ty>]) provided, it is assumed to be 0.
scale scale(<sx> Specifies a scale operation by sx and sy. If <sy> is
[<sy>]) not provided, it is assumed to be equal to <sx>.
rotate rotate(<rotat Specifies a rotation by <rotate-angle> degrees about
e-angle> a given point. If optional parameters <cx> and <cy>
[<cx> are not supplied, the rotate is about the origin of the
<cy>]) current user coordinate system. The operation
corresponds to the matrix [cos(a) sin(a) -sin(a)
cos(a) 0 0]. If optional parameters <cx> and <cy>
are supplied, the rotate is about the point (<cx>,
<cy>). The operation represents the equivalent of the
following specification: translate(<cx>, <cy>)
rotate(<rotate-angle>) translate(-<cx>, -<cy>).
skewX “skewX(ske Specifies a skew transformation along the x-axis.
w-angle)”
skewY “skewY(ske Specifies a skew transformation along the y-axis.
w-angle)”
All numeric values are real numbers.
If a list of transforms is provided, the net effect is as if each transform had been specified
separately in the order provided. For example,
<g transform="translate(-10,-20) scale(2) rotate(45)
translate(5,10)">

</g>
H-14
is functionally equivalent to:

<g transform="translate(-10,-20)">
<g transform="scale(2)">
<g transform="rotate(45)">
<g transform="translate(5,10)">

</g>
</g>
</g>
</g>
The transform attribute is applied to an element before processing any other coordinate or
length values supplied for that element. In the element
<rect x="10" y="10" width="20" height="20"
transform="scale(2)"/>
the x, y, width, and height values are processed after the current coordinate system has
been scaled uniformly by a factor of 2 by the transform attribute. Attributes x, y, width,
and height (and any other attributes or properties) are treated as values in the new user
coordinate system, not the previous user coordinate system. Thus, the above 'rect' element
is functionally equivalent to:
<g transform="scale(2)">
<rect x="10" y="10" width="20" height="20"/>
</g>
SVG Symbol Metadata XML Schema

The SVG Symbol Metadata XML schema provides extensions to the SVG schema to
support the use of parametric characteristics within an SVG file. These elements are only
understood by GeoMedia’s SVG interpreter, but the format conforms with the SVG
specification. As new releases come out, we expect additional elements to be added to the
.xsd. With the original version of this schema released with GeoMedia 6.0, only one
parametric element is supported (textContent).
There are several means of identifying an XML schema definition. For GeoMedia we have
these design goals for schema definitions:
• Short namespace prefixes so as not to burden the XML (and your vision), and for
consistency with other prefixes.
H-15
• Consistent names to ensure ease in correlation of schema file, namespace, and

namespace prefix.
• A form of designation specific to GeoMedia so that we can recognize our own
constructs.
To this end a single base schema name must be provided, which is no greater than six
characters in length, and which uniquely identifies this XML schema within the GeoMedia
product line. The length limit is imposed in order to ensure that the target name space
prefix, which appears repeatedly in XML, is not unduly long.
The base schema name has no meaning of its own, but it is used in automatically
constructing the name of the schema file to be delivered with the product(s), the string for
the target namespace, and the abbreviated prefix used for that target namespace. These
values are given, and calculated, in this table:
The schema identifier information used to identify the XML schema definition for
GeoMedia is as follows:
Identifier Value
Base schema name svgsym
Schema file name gmsvgsym.xsd
Target namespace URI http://ww.intergraph.com/GeoMedia/svgsym
Namespace prefix gmsvgsym

The XML schema definition references the following external schema definition:
Namespace Prefix Target Namespace
xs http://www.w3.org/2001/XMLSchema
Header Information
The XML schema includes the following header information:
• XML version and encoding
• Target and reference namespaces
• Version information
H-16
XML
=version 1.0
=encoding UTF-8
xs:schema
= targetNamespace http://www.intergraph.com/GeoMedia/svgsym
= elementFormDefault qualified
= attributeFormDefault unqualified
= xmlns:gmtbar http://www.intergraph.com/GeoMedia/svgsym
= xmlns:xs http://www.w3.org/2001/XMLSchema
xs:simpleType
= name VersionType
xs:restriction
= base xs:string
xs:enumeration
= value 1.0
For additional information, see the Scalable Vector Graphics (SVG) 1.1 specification at
http://www.w3.org/TR/SVG11/.
The following sections describe elements that do not conform to standard XML name
casing, but instead follow SVG name casing standards (the first letter is lowercase rather
than uppercase).
The following diagram is a graphical presentation of the main schema elements:
Element Descriptions
The following material captures the details of each element of the XML schema:
Schema gmsvgsym.xsd
element symbolParameters
Description: The symbolParameters element is a grouping element and specifies
the version of the GeoMedia SVG parametric metadata.
Parameters
Content: complex
Attributes:
Name: version
Type: gmsvgsym:VersionType
Use: optonal
Default: 1.0
element symbolParameters/textContent
H-17
Description: The textContent element defines a relationship between a style

property object and a text element in the SVG file. The textContent element
indicates to the GeoMedia symbol interpreter to update the contents of the text
section of the text element with the string pulled from the style property. The
replaceID holds the id of the text item to be replaced, with the string returned from
the style property. The styleProp holds the name of the style property whose
contents are used to update the string of the SVG text component.
Parameters
isRef: 0
Content: complex
Attributes:
Name: replaceID
Type: xs:string
Use: required
Name: styleProp
Type: xs:string
Use: required
element Toolbar/Button/ProgID
Description: The ProgID of the command.
Type: xs:string
stimpeType VersionType
Type: restriction of xs:string
Used By: attribute symbolParameters/@version
Facets: enumeration 1.0
H-18
XML Source
The following is the XML source code for this schema definition:
<xs:schema
targetNamespace="http://www.intergraph.com/GeoMedia/svgsym"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:gmsvgsym="http://www.intergraph.com/GeoMedia/svgsym">
<xs:simpleType name="VersionType">
<xs:restriction base="xs:string">
<xs:enumeration value="1.0"/>
</xs:restriction>
</xs:simpleType>
<xs:element name="symbolParameters">
<xs:annotation>
<xs:documentation>A set of parameters used to control the
contents of SVG symbols via style properties</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element name="textContent" minOccurs="0"
maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>A symbol parameter that replaces the
text content of a text element with the value of a style
property</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:attribute name="replaceID" type="xs:string"
use="required"/>
<xs:attribute name="styleProp" type="xs:string"
use="required"/>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="version" type="gmsvgsym:VersionType"
use="optional" default="1.0"/>
</xs:complexType>
</xs:element>
</xs:schema>
H-19
Example
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.0//EN"
"http://www.w3.org/TR/SVG/DTD/svg10.dtd">
<svg xmlns="http://www.w3.org/2000/svg"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:gmsvgsym="http://www.intergraph.com/GeoMedia/svgsym">

<metadata>
<gmsvgsym:symbolParameters gmsvgsym:version="1.0">
<gmsvgsym:textContent gmsvgsym:styleProp="TextProperty1"
gmsvgsym:replaceID="Text_1"/>
</gmsvgsym:symbolParameters>
</metadata>

<symbol id="Symbol_1" viewBox="0 0 400 388" style="stroke-
linejoin:round">
<g id="Group_1" style="stroke-width:1; stroke:#000000; fill:none;">
<path id="LineString2d_1" d="M164,199 L141,128 L201,83 L126,83
L103,11 L80,83 L4,83 L66,127 L43,198 L103,155 L164,199 z" />
<path id="LineString2d_2" d="M139,164 L125,123 L161,96 L117,96
L103,54 L90,96 L45,96 L81,122 L68,164 L103,139 L139,164 z" />
<circle id ="Circle2d_1" cx="103" cy="115" r="15"/>

<text id="Text_1" x="103" y="119" style="font-size:10;text-
anchor:middle;font-family:Arial;fill:#0000ff;" >
DPW
</text>
</g>
</symbol>

<use xlink:href="#Symbol_1" x="100" y="100"/>
</svg>
H-20
H-21
H-22
Additional Geocoding Information
This appendix contains information of the following geocoding items:
• Address Geocoding - Administrator Concepts and Workflows
• Geocoding Models and Parsing Rules
• Intersection Geocoding
• Sound Like Algorithm
Address Geocoding - Administrator Concepts and

Workflows
This section discusses various important concepts that administrators need to be familiar
with when working with Address Geocoding.
Functional Overview
The following diagram shows the basic operations involved with address geocoding when
using the AGI geocoding engine:
I-1
Architectural Overview
To better depict the various processes involved with the architecture in more detail, these
processes are described using separate sections and diagrams.
Address Parsing Rules

The first thing that must be determined is what constitutes an address for a given
geocoding action. An address is made up of a number of elements, and the geocoding
system includes components that can recognize a textual input structure and determine the
elements of the address. The parsing technique uses a state recognition algorithm based on
the Hidden Markov Modelling (HMM).
The Define Parsing Rules utility builds and tests the XML-formatted file that describes an
address parsing rules in terms of an HMM. For higher-order address constructs, address
parsing rules can reference other parsing rules.
Address Transformations
The parsing rules file contains rules for transforming a single string into several fields.
Often the address is defined by two or even more strings. The address transformation
contains a set of Address Parsing Rules that provides a way to transform addresses from
one (source) format to another (target) format. Both source and target formats can consist
of multiple strings. The address transformations provide a way to transform addresses
from different source formats to the same target format.
Geocoding Model
The address transformation is an essential part of a geocoding model (GCM). Once a
geocoding model has been built and saved (XML), you can get back to the address parsing
rules, and thus do address parsing.
The GCM file exists initially as an independent XML document before building the
geocoding index. This file is needed only to build the Address Geocoding Index. Once the
I-2
index has been built, the original GCM file is no longer required to be kept – allowing the
index to be portable. This is done by embedding all the necessary data from the geocoding
model to perform geocoding into the Address Geocoding Index. This includes the
definitions provided by the referenced files that describe the parsing rules for individual
address elements used in the geocoding model.
Index Building
The following diagram shows the automation objects used in the AGI file creation process.
Data from a GDO warehouse is processed, and an AGI file is created. During the building
of the AGI, all reference data addresses are converted to the base address format according
to the rules described in the index configuration of the geocoding model. The address rules
and transformations for the user addresses to be geocoded are encapsulated in the AGI file
for later use.
I-3
Address Transformation
Once the AGI file exists, the AddressTransformation object is used to expose the available
transformations that exist and are applicable to the data contained in the file. This object
provides a way to transform postal addresses from one (source) format to the format of the
data stored in the AGI (base address format). It can also perform the reverse
transformation, that is, from the base address format to source formats. The
AddressTransformation object can be initialized by means of the AGI file or from XML
conforming to the AddressTransformations XML Schema.
The AddressTransformations object is a collection of the address transformations
(AddressTransformation objects). All of them have the same target address format, that is,
the object can transform addresses from different formats to the same target format. This
object can be initialized by an AGI filename or an XML document and provides access to
predefined transformations stored in the AGI file/XML document. If the object is
initialized by an AGI file, the target format is the base address format of the AGI. The
object can also be created by the GeocodingModel object. In this case it contains the
predefined address transformations from the geocoding model that can be applied to the
geocoding dataset.
These transformation objects expose the address structure and provide a means of
performing the transformation from the source element(s) to the target element(s).
An address transformation is a slight expansion to the concept of parsing in which a

mapping between different address formats is expressed, for example:
I-4
Reference Data Example Address Elements Example

Street Name Main Street Directional Prefix
Street Name Main
Street Type Street
Street Type Suffix
City MILTONS City Miltons
State Queensland State QLD
Postcode 4064 PostalCode 4064
User Input Example Address Elements Example

Street Address 1299 Main Street House Number 1299
Directional Prefix
Street Name Main
Street Type Street
Street Type Suffix
City MILTONS City Miltons
State Queensland State QLD
Postcode 4064 PostalCode 4064
User Input Example Address Elements Example

Full Address 1299 Main Street House Number 1299
MILTON QLD 4064 Directional Prefix
Street Name Main
Street Type Street
Street Type Suffix
City Milton
State QLD
PostalCode 4064
Address Matching
A private, low-level component known as GMAddressMatcher is used as the core
geocoding technology used in GeoMedia. To allow for additional or third-party geocoding
technologies to be used, a public interface (IGMGeocodingEngine) has been defined and is
known as the Geocoding Engine interface. The geocoding engine provided with the
GeoMedia product family is one such implementation of the interface, and is called the
AGI Geocoding Engine. The AGI Geocoding Engine wraps the functionality provided by
the GMAddressMatcher object.
I-5
Reverse Geocoding
Reverse geocoding takes a geographic point as input, and determines the most appropriate
(nearest) address for that point. An interface is defined to allow implementations of an
engine to provide reverse geocoding operations.
This public interface (IGMReverseGeocodingEngine) has been defined and is known as
the ReverseGeocodingEngine interface. The geocoding engine provided with the
GeoMedia product family is one such implementation of the interface, and is called the
AGIReverseGeocodingEngine. The AGIReverseGeocodingEngine wraps the functionality
provided by the private, low-level GMReverseGeocoder object.
Note: Reverse geocoding is not supported by the desktop GeoMedia Find Address and
Geocode Addresses commands.
I-6
Geocoding Directory Service

The Geocoding Directory is used to allow a single name to be used to identify an instance
of an address geocoding engine and its associated dataset. In the following example, an
identifier of “AL” has been supplied as the named identifier for a particular geocoding
engine and geocoding dataset. The GeocodingDirectoryService (GDS) can then check the
directory and expose the unique identifier (through the Type property) for the correct
engine to instantiate and the initialization string for the engine. In the case of the
AGIGeocodingEngine, the string is a path to the required AGI file. This approach allows
for third-party engines to be plugged in. Such third-party engines must conform to the
IGMGeocodingEngine interface as mentioned previously.
The GeocodingDirectoryService also exposes address transformations that can be used for
this geocoding dataset. The AGI file contains these named transformations and all the data
required to instantiate the objects that perform the transformations. The transformations
required for a particular dataset are exposed through various methods of the GDS.
Further metadata about the dataset, such as the BoundingBox, the Coordinate System, and
which operations are supported are exposed as properties on the GeocodingDataset object
that is returned from the GeocodingDirectoryService.
I-7
I-8
Component Interaction
The following diagram depicts the geocoding subsystem as a whole:
I-9
Design Elements
The overall design of the geocoding system, as represented by the components in the
previous systems diagram, can be broken down into several distinct families:
• Address Geocoding Index components—Generate datasets for geocoding and reverse
geocoding.
• Geocoding Model components—Generate rules for performing geocoding according to
dataset address configuration, input data configuration, and locale-specific addressing
rules.
• Address Transformation components—Describe the schema of incoming or outgoing
addresses, both the elements of the addresses and their storage normalization.
• Geocoding components—Perform geocoding using input address elements already
parsed and transformed into the format required for the dataset.
• Reverse Geocoding components—Perform reverse geocoding using an input
coordinates and address transformation rules.
Within these families are found several different types of components:
• Data components
• Configuration components
• Software components (services, pipes, commands, utilities, and web services)
Data Components
The data components consist of the GDO warehouse and the Address Geocoding Index
(AGI).
GDO Warehouse
The GDO warehouse is the source GeoMedia-accessible dataset that contains the features
the geocoding index is derived from. Typically this would contain the street centerline
data, but it could also contain data suitable for rooftop geocoding.
This data is read and stored to an Address Geocoding Index (AGI) through the Publish
Address Geocoding Index utility.
Address Geocoding Index (AGI)

The Address Geocoding Index (AGI) is a binary file, in a GeoMedia-proprietary format,
optimized and indexed for rapid geocoding. It is created by the Publish Address
Geocoding Index utility. This file is used by the AGIGeocodingEngine and the
AddressTransformations object. The publishing utility also persists address
transformations information internally to the AGI file. This ensures the AGI file is fully
I-10
transportable, as it allows address transformations applicable to the data to be performed

without having to maintain a link between the AGI file and other configuration files. This
file can also be used for reverse geocoding operations.
Configuration Components
The Configuration components consist of the Geocoding Model, Geocoding Dataset,
Geocoding Directory, and the Address Parsing Rules.
Geocoding Model
The Geocoding Model is an XML document describing a geocoding model. A geocoding
model (GCM) definition describes user-recognizable address components (or fields) and
their correlation to the various elements of an address, that is, a comprehensive description
of address elements that make up a particular address structure. This includes suggested
field names that can be used by a graphical user interface to help one match up database
fields to the address component fields. Fields may be represented by either database fields
in a recordset or data entry/readout controls on a user interface.
The Geocoding Model specifies the address format of the geocoding dataset. This includes
the transformation rules required to convert from the fields in the input data to the address
elements used in the matching process.
The Geocoding Model also specifies a collection of named address transformations. These
transformations specify the field mapping between various address definitions suitable for
input and the address definition supported by the Address Geocoding Index (AGI file).
A Geocoding Model definition might, for example, identify a field called Address as
containing address elements such as house number, street name, street type, and directional
suffix, while another field called City contains the single address element of city name.
No utility currently exists to create the Geocoding Model XML files. These must be
produced manually for the time being.
Geocoding Dataset
The Geocoding Dataset is a COM object used for convenience to refer to a ProgID of a
GeocodingEngine, and the connection string used to refer to the data source. This object
covers a geographic area against which geocoding operations can be performed. It also
exposes an AddressDefinition property so that the input requirements for the dataset can be
discovered. The GeocodingDirectoryService is the service object that provides these
objects from information stored in a Geocoding Directory. Also exposed by the
GeocodingDataset object is coordinate system information, bounding box details, and if the
dataset supports reverse geocoding operations.
A GeocodingDataset object is a simple object that has properties to allow for the
instantiation of any implementation of IGMGeocodingEngine interface, and to connect to
the relevant data source as required by that implementation. The implementation of the
interface delivered with GeoMedia is based around the high-performance AGI file. The
I-11
contents of the Geocoding Directory, in relation to the datasets contained within, are
contained in an XML configuration file. This file conforms to the Geocoding Directory
XML Schema.
This object is not creatable directly. The GeocodingDirectoryService object is responsible
for the creation of the GeocodingDataset object.
Geocoding Directory
The Geocoding Directory is an XML file that defines the dataset location and other
characteristics for various geocoding engines. It is a convenient storage mechanism to
house a number of geocoding datasets and also to store information about the various
address formats supported by each of them. For GeoMedia’s implementation of the
GeocodingEngine, these datasets each consist of a single, portable file known as an AGI
file. This GeocodingDirectoryService object allows client software to easily obtain
information about the geocoding datasets contained in the directory, along with address
format definitions. The GeocodingDirectoryService also specifies a number of address
transformations available to transform input addresses conforming to various definitions
into the required fields for address matching against a particular dataset.
The Geocoding Directory consists of one or more defined geocoding datasets, each of
which has a unique identifier for the applicable engine, and an associated connection string
intended to link the object to its source data. This design is intended to allow a multi-row
processing operation (that is, a pipe) to geocode each record against a different geocoding
engine as necessary, based on an identifying field (database attribute or user interface data
entry control). For example, addresses in Alabama may be geocoded against an Alabama
AGI, while those for Georgia would be geocoded against a Georgia AGI where the
StateName field of the input recordset contained the identifying name for the applicable
dataset.
The Publish Address Geocoding Index utility can create a single-dataset directory, and
also has the capability to alter an existing dataset entry in an existing multi- or single-
dataset Geocoding Directory. A Geocoding Directory may also be created manually and/or
edited using an appropriate text/XML editor.
The Geocoding Directory and the GeocodingDirectoryService provide an advanced
geocoding capability. They are used by GeocodePipe to direct operations to the correct
address geocoding engine implementation and the correct data source through the
GeocodingDataset. In a similar way, the Find Address command uses the
GeocodingDirectoryService to access information in the Geocoding Directory.
I-12
Address Parsing Rules
The Address Parsing Rules are in an XML document conforming to the Parsing Rules
XML Schema. The parsing rules are created either manually or through the Define
Parsing Rules utility. They are used by the AddressTransformations object to instantiate
AddressTransformation objects used to transform input address types to the correct field
format used in matching operations. The AddressTransformation operations wrap a lower
level private API that uses the Hidden Markov Modelling (HMM) technique for
identifying patterns in unstructured text. This technique has been implemented and used
successfully as a generic address parsing operation in the private API. This API requires
the rules for such transformations to be initially stored in an XML document. An XML
schema describing this file format forms part of the system.
For the Intergraph implementation of the geocoding engine interface
(AGIGeocodingEngine), the AGI files contain information that is extracted by the service
layer to create the correct transformation objects.
Software Components – Services

The software components consist of the Geocoding Engine interface, the Reverse
Geocoding Engine interface, and the GeocodingDirectoryService.
Geocoding Engine Interface

This COM (dispatch) interface definition provides a generic interface by which any
number of independent (Intergraph-developed or third-party) geocoding implementations
may be written, using alternate data structures and/or underlying software/services, and
which can be plugged into the GeoMedia geocoding system. This interface may be made
available to individual partners with sufficient business justification. At this time only a
single geocoding engine implementation is planned for delivery with GeoMedia, the
AGIGeocodingEngine based on AGI files.
GeocodingResults Interface
The GeocodingEngine interface conveys its geocoding results through a GeocodePoints
object. This object provides, for each input address, geocoding results such as the
following:
• Point geometry • Match score • Match status
• Standardized address • Matched address
GeocodingDirectoryService
The GeocodingDirectoryService is an API that provides an advanced helper mechanism to
allow system components to use the Geocoding Directory without having to be concerned
about the internal XML semantics of the XML formatted file. It exposes the
I-13
GeocodingDataset object and also the AddressTransformation object as a public API, and
in turn its member objects. This component is public.
Software Components – Pipe

The pipe consists of the GeocodePipe.
GeocodePipe
This pipe geocodes addresses from a recordset, using the GeocodingEngine interface to
generate locations from addresses, and adding fields for an output point geometry and
other geocoding status information and match characteristics. It is of the base table/add
fields pipe design family, and supports notification and persistence. This component is
public.
Software Components – Commands

There are two commands, Geocode Addresses and Find Address.
Geocode Addresses Command

The Geocode Addresses command is an Analysis command that geocodes all of the
features in an input (normally nongraphic) feature class or query containing address
information, producing a query on output with point geometries.
Find Address Command

The Find Address command is a View command that geocodes an address hand-entered
through a dockable control, producing a dynamic point on the map display and panning to
the location of that point.
Software Components – Utilities

There are two utilities, the Publish Address Geocoding Index utility and the Define
Parsing Rules utility.
Publish Address Geocoding Index Utility

This standalone utility provides the ability to publish GDO data (single feature class) to an
AGI for subsequent geocoding. It provides both a graphical user interface, as well as a
command-line interface for automated publishing.
See the “Publish Address Geocoding Index Utility Help” for information on this utility.
I-14
Define Parsing Rules Utility

The Parsing Rules files needed for the address parsing components are generated by a
graphical user interface utility (Define Parsing Rules) to guide one in building such files.
This utility helps one create a well-formed HMM (Hidden Markov Model) definition file
conforming to the requirements of the private API for address parsing. The user of the
utility would generally be a system administrator type of person.
See the “Defining Parsing Rules” section of the “Geocoding” chapter for information on
this utility.
Geocoding Models and Parsing Rules

This section discusses and provides examples of geocoding models and parsing rules.
Geocoding Models
US_Cities_gcm.xml
A rooftop geocoding model for geocoding US cities.
Reference Data address format(s):
• Full city name (for example, Madison, AL)
Full city name is parsed with the US_Cities.xml parsing rules.
Geocoding address format(s):
• City name with state name (for example, Madison, AL)
City name with state name is parsed with the US_Cities.xml parsing rules.
• City name + separate state name (for example, Madison + AL)
Values are not parsed/standardized.
Referenced Parsing Rules:
• US_cities.xml
US_Post_gcm.xml
A centerline geocoding model for US post addresses.
• Street name + left/right City + left/right State + left/right ZIP (for example, E Main
Street + Madison + AL + 12345)
Can be used with GDT data.
I-15
• Street name is parsed with the US_street.xml parsing rules.

City is concatenated with State and then parsed with the US_Cities.xml parsing rules.
The city and state names are defined separately for left and right sides of the street
centerline.
ZIP is parsed with US_ZIP.xml.
ZIP is defined separately for left and right sides of the street centerline.
• Prearranged street name + left/right City + left/right State + left/right ZIP (for example,
E + Main + ST + Madison + AL + 12345)
Can be used with GDT data (though not recommended as their data are structured in a
different way than we expect).
• Prearranged street name is not parsed/standardized. It is supposed to consist of:
Street Prefix, Street Pretype, Street Name, Street Type and Street Suffix.
• City is concatenated with State and then parsed with the US_Cities.xml parsing rules.
centerline.
• ZIP is parsed with US_ZIP.xml.
• Re-joined street name + left/right City + State + left/right ZIP (for example, E + Main
+ ST + Madison + AL + 12345).
(This was used with Northeast Mississippi sample dataset by Mark on GSW.)
• Re-joined street name is supposed to consists of prefix, name, type, and suffix. These
values are concatenated and parsed with the US_street.xml parsing rules.
centerline.
• ZIP is parsed with US_ZIP.xml.
• Street name + City + State + ZIP (for example, E Main ST + Madison + AL + 12345)
(This was used with SFOStreets sample dataset by Mark on GSW.)
Street name is parsed with the US_street.xml parsing rules.
I-16
Both the city and state names and ZIP cannot be defined separately for left and right
sides of the street centerline.

• Post address (for example, 12 E Main St Madison AL, 12345)
Post address is parsed with the US_Post.xml parsing rules. Intersections cannot be
parsed.
• Post address or intersections (for example, 12 E Main St Madison AL, 12345 or Main
St & Shiny BLVD, Venice Ca, 12345)
Post address or intersections is parsed with the US_Post_c.xml parsing rules.
Intersections can have the following format:
Street1 & Street2, City State Zip
Where all elements besides Street1 and Street2 are optional; City, State, and Zip can be
present in arbitrary order and, if present, are applied to both street addresses.
• Street Address, City, State, ZIP (for example, 12 E Main St + Madison + AL + 12345)
Street Address is parsed with the US_Streets.xml parsing rules.
• City is concatenated with State and then parsed by the US_Cities.xml.
• ZIP is parsed with the US_ZIP.xml parsing rules.
• US_street.xml
• US_Cities.xml
• US_ZIP.xml
• US_Streets.xml
• US_Post.xml
• US_Post_c.xml
US_rooftop_gcm.xml
A rooftop geocoding model for US addresses.
I-17
• House number + Street name + Crossing street name + City + ZIP (for example, 12
+ Main Street + Madison + 12345 or Main Street + Coronation Drive Moscow +
98765).
Both Street name and Crossing street name are parsed with the US_street.xml
parsing rules.
All other address elements are used “as is”.
• House number + Street name + Crossing street name + City + ZIP
Both Street name and Crossing street name are parsed with the US_street.xml
parsing rules.
All other address elements are used “as is”.
• US_street.xml
US_StreetsWithZone_gcm.xml
A centerline geocoding model for US street addresses (without city and state names).
• Full street address + ZIP (for example, E Main Street + 12345)
Can be used with GDT and TeleAtlas data.
Full street address is parsed with the US_street.xml parsing rules.
It is also possible to define alternative street name.
• Prefix,Name,Type,Suffix + ZIP (for example, E + Main + ST + 12345)
Can be used with MadisonCountyAL database delivered with GeoMedia.
Prefix,Name,Type,Suffix are concatenated and then parsed with US_street.xml.
• Prefix + Pretype + Name + Type + Suffix + ZIP (for example, E + Main + ST +
12345)
Can be used with GDT data (though not recommended as their data are structured in a
different way than we expect).
Prefix, Pretype, Name, Type and Suffix are taken "as is" and not standardized.
I-18


• Post address (for example, 12 E Main St, 12345)
Post address is parsed with the US_Streets.xml parsing rules. Intersections cannot be
parsed.
• Post address or intersections (for example, 12 E Main St, 12345 or Main St & Shiny
BLVD)
Post address or intersections is parsed with the US_Streets_c.xml parsing rules.
Intersections can have the following format:
Street1 & Street2, Zip
Where Zip is optional and, if present, is applied to both street addresses.
• Street address + ZIP (for example, 12 E Main St + 12345)
Street Address is parsed with the US_Streets.xml parsing rules.
ZIP is parsed with the US_ZIP.xml parsing rules.
• House number + Street name + Crossing street + ZIP (for example, 12 + E Main St +
12345 or Main St + Shiny BLVD)
House number is not parsed/standardized.
Street name is parsed with the US_Street.xml parsing rules.
Crossing street is parsed with the US_Street.xml parsing rules.
If you enter a cross street name, then the address is considered to be an intersection.
ZIP is parsed with the US_ZIP.xml parsing rules.
• US_street.xml
• US_Cities.xml
• US_ZIP.xml
• US_Streets.xml
• US_Streets_c.xml
I-19
Parsing Rules
US_Cities.xml
This file contains parsing rules for US city name, which can be optionally postfixed with
the US state name. It is used by the US_Post.xml and US_Post_c.xml address parsing
rules.
Sample text recognized by the rules:
• Madison, AL.
• Madison
Output record consists of two fields:
• City name
• State name
US_POBox.xml
This file contains parsing rules for US PO box addresses. It is used by the US_Post.xml
and US_Post_c.xml address parsing rules.
• P O. BOX 34
Output record contains a single field:
• PO BOX (PO BOX 34)
US_Post.xml
This file contains parsing rules for US post addresses. It recognizes PO Boxes, Rural
Routes, phone numbers, and secondary unit designators.
• 1000 AVENUE E
• 1000 AVENUE E SHERMAN, TX
• 1000 AVENUE E 76943
• 1000 AVENUE E SHERMAN, TX 76943
• 1400 S COMMERCIAL AVENUE, PO BOX 72, SHERMAN, TX 79501-0072
• RR 1 BOX 82, SHERMAN, TX 76653
• 2530 UNIVERSITY BLVD SHERMAN TX 77005 713.522.2660
I-20
• 9077 FLAGSTONE #2118 MADISON AL 35758

Output record consists of nine fields:
• House number
• Street prefix
• Street pretype
• Street name
• Street type
• Street suffix
• City name
• State name
• ZIP
US_Post_c.xml
This file contains parsing rules for US post addresses. It supports intersections, recognized
PO Boxes, Rural Routes, phone numbers, and secondary unit designators.
• 1000 AVENUE E
• 1000 AVENUE E SHERMAN, TX
• 1000 AVENUE E 76943
• 1000 AVENUE E SHERMAN, TX 76943
• 1400 S COMMERCIAL AVENUE, PO BOX 72, SHERMAN, TX 79501-0072
• RR 1 BOX 82, SHERMAN, TX 76653
• 2530 UNIVERSITY BLVD SHERMAN TX 77005 713.522.2660
• WALNUT & 6TH, PO BOX 39, SHERMAN, TX 79001-0039
• CORNER OF WASHINGTON AVENUE AND MEMORIAL PARKWAY
• 9077 FLAGSTONE #2118 MADISON AL 35758
Output record consists of nine fields:
• House number
• Street prefix
• Street pretype
I-21
• Street name
• Street type
• Street suffix
• City name
• State name
• ZIP
If an intersection is recognized, the output contains two records (one for every crossing
street). The intersection addresses can have the following format:
Street1 & Street2, City State ZIP
City, State, and ZIP can be present in arbitrary order. In this case, the 'House number' field
in both output records is empty and ‘City name’, ‘State name’, and ‘ZIP’ are the same for
both records.
US_RR.xml
This file contains parsing rules for US rural route and highway contract addresses. It is
used by the US_Post.xml and US_Post_c.xml address parsing rules.
• RURAL ROUTE 54 BOX 34
• STAR ROUTE 3 BOX 1
Output record consists of three fields:
• Box number (34)
• RR identifier (RR)
• RR number (54)
US_street.xml
This file contains parsing rules for US street names. It is referenced from the US_Post.xml
and US_Post_c.xml address parsing rules.
• WASHINGTON COUNTY RD 354
• US-45
• AVE J N
• 1000TH ST
I-22
• BOB WALLACE AVE SW

Output record consists of five fields:
• Street prefix
• Street pretype
• Street name
• Street type
• Street suffix
US_Streets.xml
This file contains parsing rules for US street addresses. It recognized PO Boxes, Rural
Routes, phone numbers, and secondary unit designators. It is identical to US_Post.xml but
does not output the City and State names (if any).
US_Streets_c.xml
This file contains parsing rules for US street addresses. It supports intersections,
recognized PO Boxes, Rural Routes, phone numbers, and secondary unit designators. It is
identical to US_Post_c.xml but does not output the City and State names (if any).
US_ZIP.xml
This file contains parsing rules for US ZIP codes. It is used by the US_Post.xml and
US_Post_c.xml address parsing rules.
• 12345-6789
• 12345
Output record consists of two fields:
• ZIP or first part of ZIP+4 code
• Second part of ZIP+4 code
Files Referenced by the Parsing Rules

Numeric.csv
List of numeric street names with aliases. It is referenced from US_street.xml.
I-23
US_Cities_sp1.csv
A list of US cities that can confuse the parser, for example:
• 'EAST HAMPTON' ('East' can be erroneously reported as street suffix.)
• 'FORT WORTH' ('Fort' can be erroneously reported as street type.)
It is referenced from US_Cities.xml.
US_secondary_units.csv
List of secondary units designators in the US addresses ('FLOOR', 'ROOM', and so forth).
It is referenced from US_Post.xml and US_Post_c.xml.
US_states.csv
List of US state names. It is referenced from US_Cities.xml.
US_street_types.csv
List of street types with aliases ('ST', 'FREEWAY', and so forth). It is referenced from
US_street.xml.
Intersection Geocoding
This section discusses intersection address geocoding in centerline geocoding models.
There are two basic facts about intersection geocoding:
1. Intersection geocoding is only possible in centerline geocoding models.
2. Intersection geocoding is done on the fly by intersecting two sets of matched street
centerlines. There is no way to pass pre-calculated intersection points to the AGI file
along with centerline data. However, one could try to create a separate AGI file with
pre-calculated intersection points based on a rooftop geocoding model (but it is not
what we currently call intersection geocoding).
Internally (at the matching stage, that is, at input to GMAddressMatcher after being
processed by an AddresssTransformation), ordinary addresses are defined by a set of
base address element values. The house number address element should be specified for
proper location of the matched point along a street centerline. In contrast with ordinary
addresses to be geocoded, an intersection address consists of two complete sets of base
address elements for the primary street and the crossing street, respectively. The value of
the house number address element can be specified in both the street and intersecting
street, but it is not used in the location of the matched point.
The geocoding system provides two basic ways to specify intersections at the user level:
I-24
1. To define an input address format where there is an input address field with special
address parsing rules, automatically disambiguating it as an ordinary address or an
intersection address.
2. To define an input address format where the crossing street is provided as an
independent input address element.
The following are the examples from the delivered configuration files along with technical
details:
Automatic disambiguation of the intersection addresses from the ordinary addresses
The parsing rules must be designed so that they can recognize intersections in the input
string and report them by returning two output entities to the containing address
transformation. The first output entity contains values for the primary street (first set of
base address element's values), and the second for the crossing street (second set of base
address element's values). The street separators in the intersection addresses are defined in
the parsing rules. An example of such intersection detection is found in the US_Post
geocoding model (US_Post_gcm.xml).
The second address transformation (Post address of intersection) refers to the
AddressParsingRules\US_Post_c.xml parsing rules, which are responsible for intersection
detection. There is a dedicated dictionary token that accepts only street separators. Its
name is 'CAND' and it accepts '&', 'AND', 'AT', and '@'. To adjust the parsing rules for
another language, you have to modify at least the contents of the dictionary (for example,
with Spanish addresses, the 'AND' dictionary entry must be replaced with 'Y'). This can
be done by using the Define Parsing Rules Utility or by direct editing of the XML file with
parsing rules (US_Post_c.xml in case of US addresses) in any text editor.
Intersection addresses do not have to be passed as a single string. For example, the
Intersecting streets, City, State, ZIP source address format can be geocoded this way. If
Intersecting streets is parsed into two output entities, the following two records will form
the intersection:
• Primary street, City, State, ZIP, and
• Crossing street, City, State, ZIP.
That is, if parsing rules produced only one output entity in intersection address, the
returned values are copied to both the street and the crossing street address element sets.
However, none of the delivered geocoding models has an input format supporting
intersections to be disambiguated, but with some explicitly separated input address
elements.
Crossing street is provided as an independent input address element
An example can be seen in the US_StreetsWithZone geocoding model
(US_StreetsWithZone_gcm.xml) in the House number + Street name + Crossing street +
ZIP source address transformation. The address transformation has mappings with a
special intersectionRole attribute, described in the gmagctrn.xsd file:
I-25
• Mapping that handles the Street name address element has the intersectionRole
attribute set to "first". This means that if the address element is present, its value
defines values only in the primary street (the first set of the base address elements).
Thus, it defines street name in ordinary address or the first street in intersection.
• Mapping that handles the Crossing street address element has the intersectionRole
attribute set to "second". This means that if the address element is present, it defines
the crossing street (that is, values in the second set of the base address elements). The
mappings that have no intersectionRole attribute define values for both the primary
street and the crossing streets. There is no street separator in this case.
To conventionally localize the street delimiters, you can use the external dictionary in the
US_Post_c.xml parsing rules instead of storing street separators in XML. In this case, the
'AND' should be replaced with 'Y' in a one-line CSV file. Having changed this, you can
partially succeed in parsing Spanish intersection addresses because many Spanish street
types were added to the parsing rules. But generally, localization of the parsing rules
should be started with an analysis of the local address structure to determine whether the
parsing rules for US addresses can be adopted to the local language. They can certainly be
adopted for Spanish addresses, but cannot be adopted, for example, for Russian.
Sound Like Algorithm

The Publish Address Geocoding Index utility uses the official Soundex algorithm (as
described in this appendix as sound like) slightly modified so that it can process non-
English letters and other characters.
The algorithm is the following:
1. Retain the first letter of the word.
2. Remove all occurrences of the A, E, H, I, O, U, W, Y letters.
3. Map the rest of letters using the following ruleset:
English letters Soundex code Code used by the utility
B, F, P, V 1 B
C, G, J, K, Q, S, X, Z 2 C
D, T 3 D
L 4 L
M, N 5 M
R 6 R
Note: Actually, the utility uses letter-to-letter mapping (depicted at the last column)
instead of letter-to-digit mapping of original Soundex (just in order to obtain
alphabetical code, not alpha-numeric).
I-26
All other characters are retained.

4. If two or more letters with the same code were adjacent in the original name, or
adjacent except for any intervening H and W, omit all but the first.
5. If the length of the code is less than requested, pad it with spaces.
Soundex was designed for English words. An attempt to code the non-English words but
written with English letters will produce some code. Such code can be different for the
similar words and equal for the completely different words. This, in turn, will result in
situations when:
• Similar addresses have different matching index. Thus, during the matching, even a
minor misspelling can result in failure to match the address.
• Completely different addresses have the same matching index. In this case, there will
be some match candidates (with low-match score) that are surely incorrect.
If the string to be coded contains only non-English characters, the returned value is
identical to the original string (cut to the requested number of characters or padded with
spaces). Thus, for non-English words it acts as an original value instead of the Soundex
code is returned.
I-27
I-28
File Types
GeoMedia products introduce file types that must be registered with Windows. The
following file types are exposed to the user with GeoMedia Professional, and they must
have an associated description, icon, and open action. The items with a single ampersand
(&) are omitted from the GeoMedia Objects delivery. The items with a single asterisk (*)
are omitted from the GeoMedia Viewer delivery. The items with a double asterisk (**) are
omitted from both the GeoMedia Viewer and GeoMedia deliveries.
The open action is normally the executable to be invoked for opening the file, when the file
is opened from Windows, usually by double-click. Some file types are designated as “No
action”, meaning that the file type has been designated as not to be opened directly through
Windows.
Extension Description Open Action

AGI Intergraph GeoMedia Address Geocoding No action
Index
AGP Intergraph GeoMedia Address Geocoding Publish Address Geocoding Index
Profile utility
CSC* Intergraph GeoMedia CAD Server Cache File No action
CSD* Intergraph GeoMedia CAD Schema Definition Define CAD Server Schema File
File utility
CSF Intergraph GeoMedia Coordinate System File Define Coordinate System File
utility
FSM Intergraph GeoMedia Feature Symbol File Define Symbol File utility
&
GBP** Intergraph GeoMedia Batch Plotting File Batch Plotting utility
GCE* Intergraph GeoMedia Catalog Exchange File No action
GLS*& Intergraph GeoMedia Layout Sheet No action
GLT*& Intergraph GeoMedia Layout Template No action
GSD Intergraph GeoMedia Style Definition File1 Internet Explorer
GWS& Intergraph GeoMedia GeoWorkspace GeoMedia Professional
1
The .gsd file extension has a registered “icon handler”, so that each file instance will have a
uniquely rendered icon in Windows Explorer showing the style definition, rather than an icon based
upon the .gsd file type.
J-1
Extension Description Open Action

&
GWT Intergraph GeoMedia GeoWorkspace GeoMedia Professional
Template
MDT* Intergraph GeoMedia Access Warehouse No action
Template
SSP* Intergraph GeoMedia SmartStore Profile Publish to GeoMedia SmartStore
Warehouse utility
SYM*& Intergraph GeoMedia Layout Symbol File No action
TFD* Intergraph GeoMedia Text Format Definition Define Text File Server Format File
File utility
TRV*& Intergraph GeoMedia Traverse File NotePad
J-2
Index
address transformation, 13-3, 13-4, I-2,
. I-4
.ini files administrator concepts, I-1
autodt.ini, 3-2, 3-14, 3-15, B-3 AGI file, 13-1
coordinate system, 5-7 dataset, 13-3, I-12
defining parsing rules, 13-19
directory, 13-3, I-8, I-13
A
engine, 13-3
Access, 4-2 finding addresses, 13-7
catalogs, 9-9 functional overview, 13-6
data, 4-4 index building, 13-5, I-3
default template, 4-3 index matching, 13-4, 13-6, I-6
normal.mdt, 4-3 intersection, I-25
PickLists, 4-21 model, 13-5, I-2, I-12
server, 4-4 multiple addresses, 13-12
default coordinate system, 4-4 multiple datasets workflow, 13-17
spatial operators, 10-39 overview, 13-1, I-1
warehouses parsing rules, I-2
changing coordinate system for parsing rules workflow, 13-22
template, 4-20 rooftop data, 13-2
creating, 4-3 sound like algorithm, I-27
default coordinate system, 4-4 starting, 13-4
templates for, 4-20 street centerline data, 13-2
accessing warehouses, 4-2 system diagram, I-10
adding terminology, 11-2, 13-4
feature class attributes, 8-9 workflow, 13-14, I-1
features parsing, 13-3
from data window, 8-26 Address Geocoding Index (AGI) file, 13-1, I-
from map window, 8-24 11
geometry to features, 8-37 Address Geocoding Profile (AGP) file, 13-4
hypertext to feature classes, 8-34 aggregating
image entries to legend, 6-43 attribute and spatial, 10-94
legend entries, 6-41 creating, 10-97
thematic, 6-44 data, 10-91
address vs. merging, 10-99
finding, 13-1, 13-7 defining, 10-91
sound like algorithm, I-27 expressions, 10-95
Soundex algorithm, I-27 functional attribute, 10-95
geocoding, 13-1 right mouse menu, 10-96
address parsing, 13-3, I-14 spatial, 10-93
address standardization, 13-3 types, 10-92
IN-1
algorithms warehouse, 4-5

projection, B-1 area
Quad-Tree, 10-39 features, 8-2
sound like, I-27 measuring, 6-73
Soundex, I-27 units of measure, B-15
analyzing, 10-1 arrow, north, 6-67, 15-5
aggregation, 10-91 associating catalog records, 9-21
buffer zones, 10-72 attributes
combining feature classes and queries, 10- adding, changing, deleting, 8-9
106 based style, 6-28
functional attribute, 10-75 changing values, 8-38
generating base geometry, 10-100 tooltips, 8-38
GeoMedia data, 10-1 functional, 10-75
geometry, 10-67 offset display concepts, 10-23
options, 10-69 outputting from feature class/query, 10-
Units and Formats tab, 10-68 103
joins, 10-64 queries, 10-2
linear referencing, 11-6 editing selection, 10-105
merging operators, 10-2
feature classes and queries, 10-86 selecting, 10-103
vs. aggregating, 10-99 AutoCAD, 4-2
queries .dwg file, 18-17
filter, 10-1 .dxf file, 18-17
native, 10-19 exporting to, 18-17
select set, 8-22 autodt.ini, 3-2, B-3
spatial, 10-8 autodt.ini file, 3-14
selecting attributes, 10-103 azimuth
spatial north arrow, 6-67, 15-59, 15-76
differences, 10-15 settings, 3-14
filters, 10-31
intersections, 10-12 B
union, 10-106 background sheets, 14-13, 16-8
angles, measuring, 6-75 backing up, GeoWorkspaces, 2-4
animation, style, 6-30 base geometry, generating, 10-100
annotation, 12-1 Batch Plotting, 14-10, 16-16
arc group properties, 15-19
exporting to MapInfo file, 18-5 border, grid, 15-89
measuring, 6-73 defining, 15-91
ARC/INFO, 3-16, 4-2, 4-5 buffer zones, 10-72
displaying, 3-17 defining, 10-73
server, 4-5 examples, 10-74
warehouse, 4-5 placing around features, 10-72
ArcView, 3-16, 4-2, 4-5 Building on the GeoMedia Engine, 1-3
displaying, 3-18
server, 4-5
IN-2
Index
C style sheet, 9-17, 9-20, 9-26, 9-29

CAD, 3-16 template, 9-7
data server, 4-6 terminology, 9-38
displaying updating metadata databases, 9-7
data, 3-18 categories, 8-43
file, 6-77 creating, 8-47
schema-definition file, 4-6, 6-77 editing, 8-49
Server Setup File, online documentation, legend entries, 6-41
1-3 managing, 8-44
supported MicroStation element types, 4-6 cells
warehouse, connecting to, 4-6 editing in data window, 7-7
cartographic grids, 15-79 hypertext, 8-34
border, 15-89 center at current scale, 6-3
defining, 15-83 central meridians, B-20
inserting, 15-79 changing
neatline, 15-80 attributes, 7-7, 8-9
placing, 15-85 coordinate system for Access warehouse
ticks and crosses, 15-86 template, 4-20
catalogs, 9-1 data window contents, 7-6
Access, 9-7 feature, 8-40
associating records, 9-21 attributes, 8-38
creating, 9-7 class attributes, 8-9
connections, 9-8 style, 6-32
exploring, 9-26 layout window properties, 14-14
exporting records, 9-16 legend
format, 9-16 display, 15-53
XML display, 9-20 entry style, map, 6-32
features, 9-2 map object
FGDC, 9-2, 9-4 display, 6-9
geospatial metadata, 9-3 display priority, 6-9
importing records, 9-13 locatability, 6-11
managing connections, 9-10 style, 6-12
metadata, 9-1 map window properties, 6-2
ODBC, 9-9 north arrow display, 6-68, 15-59
Oracle, 9-9, F-1 scale bar display, 6-69, 15-61
installing, setting up, upgrading, F-1 closing
publishing, 9-16 GeoWorkspace, 2-4
sample workflow, 9-37 warehouse connections, 4-18
software delivery, 9-39 collections
SQL, F-1, F-8 catalog, 9-7
installing, setting up, upgrading, F-1 styles, 6-19
Server, 9-9 color
standards fill in layout window, 15-28
FGDC, 9-4 line in layout window, 15-25
ISO, 9-6 map, 8-20
IN-3
symbol, 6-34, 6-36 for feature classes, 3-7

combined queries, 10-2, 10-11 for GeoWorkspaces, 3-5
combining feature classes and queries, 10- for MapInfo, 4-9
106 for warehouses, 4-4
compass rose, 6-68, 15-5, 15-59 online documentation, 1-3
compound displaying data that has none specified, 3-
expressions, 10-3 16
features, 8-2, 18-17 ellipsoids, B-12
compression techniques, raster data, C-3 feature classes, 3-7, 4-4, 8-3
configuring for datum transformations, 3-14 files
connecting to warehouses, 4-4 defining, 3-16
connections editing, 3-19
catalogs geographic, 3-1
Access, 9-9 systems, B-24
creating, 9-8 GeoTIFF capabilities, B-21
managing, 9-10 GeoWorkspace, 3-5, 4-4
ODBC, 9-9 getting coordinates readouts, 3-11
closing, 4-18 grids, 15-84
library images, 5-1, 5-6
creating, 17-3 information, B-1
managing, 17-7 linking geometry data, 5-8
opening, 4-18 matching
warehouses, 2-1, 4-1 default GeoWorkspace and warehouse,
coordinate system, 4-4 3-9
creating, 4-3 for digitizing, 4-4
managing, 4-15 named geodetic datums, B-11
working with, 4-15 neatline, 15-81
constants, functional attribute, 10-84 projected, 3-1
continuing geometry, 8-37 projection algorithms, B-1
controlling setting units and display preferences, 3-12
data windows, 7-3 standard geodetic datums, B-9
layout windows, 14-1 state plane zone codes, B-16
legend entries, 6-58 ticks and crosses, 15-87
map windows, 6-2 units of measure, B-14
conventions, documents, 1-4 UTM zones, B-20
coordinate systems, 3-1, B-1 warehouse, 4-4
.ini files, 5-7 working with, 3-1
Access warehouses, template, 4-20 coordinates
creating from design files, 3-19 geocoding, 13-23
datum transformation models, B-1 Precision Coordinates control, 3-11
default settings, 3-2 copying
Access server, 4-4 coordinate system definition, 3-11
defining GeoWorkspace, 2-4
for ArcView, 4-5 course overlap spatial operator, 10-38
for AutoCAD, 4-6
IN-4
Index
creating map window, 6-68

Access warehouse template, 4-20 scale bar
attribute filter queries, 10-3 layout window, 15-61
catalogs, 9-7 map window, 6-69
connections, 9-8 software, 1-3, 1-5
coordinate systems from design files, 3-20
expressions, functional attribute, 10-77 D
feature classes data
attaching external data source, 8-5 Access, 4-2, 4-4
from scratch, 8-6 aggregating, 10-91
ODBC Tabular data server, 8-5 analyzing, 10-1
functional attribute, 10-85 ARC/INFO, 4-2, 4-5
GeoWorkspace, 2-1 ArcView, 4-2, 4-5
template, 2-6 AutoCAD, 4-2
image footprints, 5-15 compression techniques, C-3
joins, 10-66 delaying loading, 2-3
labels views, 12-3 displaying accurately, 3-16
layout sheets, 14-1 exporting to other systems, 18-1
library, 17-2 FRAMME, 4-2, 4-7
connections, 17-3 geographic, 6-1
linear network queries, 10-25 MapInfo, 4-9
map windows, 6-66 MGDM, 4-10
read-write warehouses, 4-3 MGE, 4-2
searches MGSM, 4-2, 4-10
ad hoc, 10-61 MicroStation, 4-2
predefined, 10-58 outputting feature to warehouses, 8-10
styles, 6-22 raster
symbol files, 6-33, 6-36 tiling, C-4
in layout window, 6-35 types, C-4
thematic maps, 6-44 servers, 4-2, 10-45
crosses, grid, 15-86 coordinate systems, 5-6
defining, 15-91 structure, LRS, G-1
parameters, 15-86 table, inserting into layout window, 15-98
placing, 15-88 windows
ticks, 15-86 changing contents, 7-6
customizing changing name, 7-3
datum transformation, 3-2 columns, statistics in, 7-6
legend controlling, 7-3, 7-4
layout window, 15-53 editing cells in, 7-7
map window, 6-1, 6-57 hiding columns, 7-5
toolbar, map window, 6-62 inserting into layout window, 15-98
menus and toolbars, 1-7 opening new, 7-1
customized settings, 1-8 page setup, 16-5
north arrow printing, 16-7
layout window, 15-59 Queued Edit, 10-52
IN-5
showing table columns, 7-4 linear network queries, 10-25

taking a snapshot of, 7-8 map
using mouse, 7-3 object display properties, 6-10
working with, 7-1 window display properties, 15-2
database window properties, 6-4
Access, 4-3 window tooltip, 6-65
Oracle, 4-12 native queries, 10-19, 10-22
SQL, 4-13 parsing rules, 13-2, 13-4, 13-19, I-2, I-14,
Text File, 4-13 I-16, I-21
WFS, 4-14 reference
WMF, 4-14 grids, 15-92
datum index, 15-95
geodetic select set queries, 8-22
named, B-11 spatial
standard, B-9 filters, 10-32
NAD 27, B-16 queries, 10-8
NAD 83, B-17 units of measure, 6-73
transformations delaying GeoWorkspace data loading, 2-3
configuring for, 3-14 deleting
customizing, 3-2 feature class attributes, 8-9
models, B-1 features, 8-40, 8-42
Define Coordinate System File, 3-1 geometry, 8-42
online documentation, 1-3 layout sheets, 14-13
Define Symbol File, 6-33, 6-36 map objects, 6-66
online documentation, 1-3 queries, 10-30
Define Text File Server Format File, 4-13 searches, predefined, 10-60
online documentation, 1-3 design file, 5-3, 10-45
Define Warehouse Configuration File creating coordinate systems from, 3-20
online documentation, 1-3 exporting to, 18-8
defining IGDS element types generated from
aggregation, 10-91, 10-97 GeoMedia, 18-8, 18-17
attribute filter queries, 10-2 images, 5-7
cartographic grids, 15-79, 15-89, 15-90, MicroStation layout templates, 14-7
15-91, 15-92 designing map layouts for printing, 15-1
coordinate systems developer documentation, 1-2
for ARC/INFO, 4-5 digitizing
for ArcView, 4-5 coordinate systems matching, 4-4
for AutoCAD, 4-6 SmartSnap, 15-33
for GeoWorkspaces, 3-5 display scale, 6-4
for MapInfo, 4-9 displaying
for warehouses, 4-4 CAD files, 6-77
expressions, functional attribute, 10-77 functional attribute, 10-85
functional attribute, 10-85 geographic data, 6-1
grid border, 15-91 legend, 6-40
joins, 10-64 entry, 6-5
IN-6
Index
map functional attribute, 10-86

objects, 6-9 label text, 8-28
window properties, 15-2 queries, 10-29
north arrow, 6-67 Queued Edit, 10-45
priority, map objects, 6-9 searches, predefined, 10-59
queries, 10-27 speedup with tiling, C-4
raster images, 3-19 text features, 8-28
scale bar, 6-69 union query through Queries command,
selected images, 5-17 10-111
thematic map, 6-39, 6-44, 6-57 electronic self-help support, A-1
warehouse images, 5-9 element types
WYSIWYG, 15-3 MicroStation supported, 4-6
distance SVG supported, H-1
measuring, 6-73 ellipsoids, 3-2, B-12
offset, 10-23 e-mailing GeoWorkspaces, 2-5
scale bar, 6-69 embedding GeoWorkspace, 2-7
document environment, multi-user, 4-19
.pdf, 1-3 event
conventions, 1-4 data, linear referencing, 11-4
developer, 1-2 features, dynamic segmentation, 11-12
FAQs, A-1 Excel, 1-7
Help, 1-5 attaching external data source, 8-5
interactive, 1-4 exploring catalogs, 9-26
provided with GeoMedia, 1-2 exporting
Release Notes, 1-5 catalog records, 9-16
user, 1-3 format, 9-16
utilities, 1-3 XML display, 9-20
Drawing toolbox, 15-13 data, 18-1
dynamic to AutoCAD, 18-17
queues, 10-46 to design file, 18-8
segmentation, 11-2, 11-6, 11-12 to MapInfo Interchange Format, 18-5
capabilities, 11-12 to other systems, 18-1
event features, 11-12 to shapefile, 18-1
marker model, 11-12 layout sheets, 14-9
measure model, 11-12 expressions
aggregation, 10-95
E analytical merge, 10-88
Edit MGSM Parameter File, online functional attribute, 10-77
documentation, 1-3 style, 6-28
editing Extensible Markup Language, images, 5-8
attribute selection query through Queries
command, 10-105 F
cells in data window, 7-7 FAQs, A-1
coordinate system files, 3-19 feature classes, 8-2
feature attributes, 8-38 adding hypertext to, 8-34
IN-7
aggregation, 10-91 spinning, 8-41

vs. merging with queries, 10-99 text, 8-2, 8-26
categories, 8-43 types, 8-1
combining with queries, 10-106 working with, 8-1
coordinate system, 4-4, 8-3 Federal Geographic Data Committee, 9-4
creating fence
by attaching external data source, 8-5 modes, 8-21
from scratch, 8-6 select features, 8-18
ODBC Tabular data server, 8-5 Select Tool, 8-21
defining, 8-6 FGDC, 9-2, 9-4
coordinate system for, 3-7 Content Standard for Digital Geospatial
images, 5-1, 5-6 Metadata, 9-4
inserting files
features into, 8-24 .agi, 13-1
text features into, 8-26 .agp, 13-4
labels, 12-2 .bak, 2-4
legend entry defaults, 6-56 .bmp, 14-9
merging with queries, 10-86 .cel, 6-15, 6-33
outputting to warehouses, 8-10 .crd, 4-11
symbols for, 6-33 .csd, 6-77
union with queries, 10-106 .csf, 3-16, 3-17, 3-18, 3-19, 4-5
working with, 8-2 .ddc, 4-13
features .dgn, 3-18, 3-19, 4-11, 5-7, 14-5
adding .dwg, 6-15, 6-33, 6-77, 18-17
from data window, 8-26 .dxf, 6-77, 18-17
from map window, 8-24 .fsm, 6-15, 6-33, 6-35
geometry to, 8-37 .gls, 14-5, 14-9
aggregating attributes, 10-91 .glt, 14-5, 14-9
vs. merging with queries, 10-99 .gml, 18-21
analyzing geometry, 10-67 .gws, 2-1, 2-2
catalogs, 9-2 .igr, 14-5
changing, 8-40 .igt, 14-5
attributes, 8-38 .ini
style, 6-32 auto.ini, 3-14
deleting, 8-40, 8-42 autodt.ini, 3-15
event, 11-12 MGE, 8-36
exporting data, 18-5 rulebase, 4-7
geometry types, 8-1 .jgw, 5-3
graphics-only, 10-45 .mdb, 9-7
image, 8-2 .mge, 4-10
linear referencing, 11-4 .pdf, 1-3, 16-16
moving, 8-40, 8-41 .prm, 4-11
outputting to warehouses, 8-10 .prn, 16-4
reference, spatial filter, 10-33, 10-42 .sdw, 5-3
selecting in map window, 8-18 .svg, 6-15, 6-33, 6-35
IN-8
Index
.sym, 6-15, 6-35 named, 10-40

.tfd, 4-14 operators, 10-37
.tfw, 5-3 options, 10-37
.xls, 9-17, 9-20 removing, 10-40
.xsd, 18-21 with layout windows, 15-10
autodt.ini, 3-2 workflows, 10-35
CAD finding addresses, 13-1, 13-7
displaying, 6-77 Publish Address Geocoding Index Utility,
schema definition, 4-6 I-27
coordinate, 4-11 sound like algorithm, I-27
system, 4-6 Soundex algorithm, I-27
design, 10-45 fit
external, 8-34 all, 6-7
File Locations tab, Options dialog box, 2-5 select set, 6-7
FSA.gtw, 4-7 spatial filters, 10-40
gateway, 4-7 footprints
Jpeg, 5-3 creating image, 5-15
MapInfo, 18-5 geographic, 15-9
MGE project, 4-10 formats
MrSid, 5-3 raster, supported in GeoMedia, C-1
multimedia, 8-36 setting, 3-12
normal.gwt, 2-1 Units and Formats tab, Define Coordinate
normal.mdt, 4-3 System dialog box, 3-12
parameter, 4-11 FRAMME, 3-16, 4-2, 4-7
printing to, 16-4 displaying, 3-18
seed, 4-11, 18-15 server, 4-7
symbol library, 6-33 warehouse, 4-7
text, 4-11, 4-13 frequently asked questions, A-1
format definition, 4-14 functional attribute
TIFF, 5-3 aggregation, 10-95
types, J-1 analytical merging, 10-88
world, 5-2 creating, 10-85
filters displaying, 10-85
attribute in queries, 10-1, 10-2 editing, 10-86
SQL, 10-3 expressions, 10-77
spatial, 10-31 constants, 10-84
by existing filter, 10-34 functions, 10-79
by map window extent, 10-34 operands, 10-78
by not using filter, 10-34 operators, 10-79
by reference features, 10-33 format, 10-78
by select set, 10-34 Functional Attribute dialog box, 10-76
defining, 10-32 Functional Attributes
designating reference features, 10-42 command, 10-75
fitting, 10-40 dialog box, 10-75
managing, 10-37 output types, 10-78
IN-9
precision, 10-78 programming guides, 1-5

style, 6-28 Release Notes, 1-5, A-1
working with, 10-75 SmartStore Server, 1-4
functions, functional attribute, 10-79 supported MicroStation element types, 4-6
Technical Notes, A-1
G template files, 14-9
gateway files, 4-7 exporting to, 14-9
generating base geometry, 10-100 types of windows in, 1-7
workflow, 10-101 what you need to know to work in, 1-2
geocoding, 13-1 What’s New, A-1
addresses, 13-1 GeoMedia Command Wizard Help Topics, 1-
AGI file, 13-1 2
terminology, 11-2 GeoMedia Fusion, 10-45
coordinates, 13-23 GeoMedia Object Reference, 1-3
dataset, I-12 GeoMedia PublicWorks Manager, enabling
defining parsing rules, 13-19 AFM proxy servers for, 4-15
design elements, I-11 GeoMedia Transportation, 11-1, 11-6
directory, I-13 geometry, 8-1
intersections, I-25 adding, 8-37
models, I-16 analyzing, 10-67
parsing rules, I-21 options, 10-69
sound like algorithm, I-27 base, generating, 10-100
system diagram, I-10 workflow, 10-101
geodetic datums, 3-2, 18-16 continuing, 8-37
named, B-11 data, linking, 5-8
standard, B-9 deleting, 8-42
geographic feature types, 8-1
coordinate systems, 3-1 layout window, properties, 15-70
data, displaying, 6-1 vertices, 8-42
extent methods, 15-9 georeferenced image
GeoGraphics, 4-2 placement, 5-2
Data Server, 4-7 raster placement, file types and categories,
warehouse, 4-7 C-5
GeoMedia geospatial metadata, 9-3
as development environment, 1-1 geo-tie packets, 5-2, C-2
as OLE server, 2-7 GeoTIFF
documents provided with, 1-2 capabilities, B-21
getting around in, 1-6 geographic systems, B-24
getting started in, 1-6 image placement, B-29
Help, 1-3, 1-5 projection systems, B-21
interactive documents in, 1-4 reading from, B-29
Issues Resolved, A-1 tags, 5-2
layout sheets, 14-5 GeoWorkspaces
overview, 1-1 backing up, 2-4
printing in, 16-1 closing, 2-5
IN-10
Index
coordinate system, 4-4, 5-3 ticks and crosses, 15-86

defining, 3-5 coordinate system, 15-87
matching default, 3-9 defining, 15-91
copying, 2-4, 2-5 parameters, 15-86
creating, 1-1, 2-1 placing, 15-88
delaying data loading, 2-3
e-mailing, 2-5 H
embedding, 2-7 Help
linking, 2-7 Command Wizard, 1-2
opening, 2-2 displaying, 1-5
saving, 2-5 GeoMedia Help, 1-3
storing, 2-5 topics, 1-5
templates, 2-1, 2-6 Hidden Markov Model (HMM), 13-3, 13-19
creating, 2-6 hiding
workflow for creating, 2-1 layout window, 14-1
working with, 2-1 legend, 6-40
GIS, 1-1 how to reach Intergraph, A-1
applications, 1-14 hypertext
concepts and terms, 1-10 adding, 8-34
overview, 1-9 inserting, 8-35
GML, 4-2
.gml file, 18-21
I
.xsd file, 18-21
Data Server, 4-8 I/CAD MAP, 4-2
exporting to, 18-21 IGDS, element types generated from
warehouse, 4-8 GeoMedia, 18-8, 18-17
grids, 15-79, 15-92 images, 5-1
border, 15-89 adding entries to legend, 6-43
placing, 15-89 changing raster display, 5-12
cartographic, 15-79 coordinate systems, 5-1, 5-6
coordinate system, 15-84 creating footprints, 5-15
crosses, 15-86 deleting, 5-11
defining, 15-83, 15-89, 15-90, 15-91, 15- displaying, 3-19, 5-9
92 selected, 5-17
neatline, 15-80 feature classes, 5-1, 5-6
coordinate system, 15-81 features, 8-2
defining, 15-90 footprints, 5-15
parameters, 15-81 georeferenced placement, 5-2
placing, 15-82 GeoTIFF, B-29
parameters, 15-84 inserting into warehouses, 3-19, 5-1
placing, 15-85 interactive placement, 5-2
reference, 15-92 managing, 5-8
index, 15-95 raster, 5-1
ticks, 15-86 redisplaying, 5-12
placing, 15-87 removing, 5-12
IN-11
snapshot of data window, 7-8 reference

style, 6-18 grid, 15-93
supported raster formats, C-1 index, 15-95
updating, 5-10 scale bar, layout window, 15-61
validating, 5-11 text features into feature class, 8-26
XML, 5-8 inside spatial operator, 10-38
Imagineer Installing GeoMedia, 1-3
drawing file, 14-5 IntelliMouse, 1-7, 6-7
template file, 14-5 Intergraph, 1-1
importing how to reach, A-1
catalog records, 9-13 Knowledge Base, A-1
data, workflow, 4-2 support, A-1
drawing files, 14-5 intersection geocoding, I-25
layout templates, 14-5
index J
building, geocoding, 13-5, I-3 joins, 10-64, 10-65
matching, geocoding, 13-4, 13-6, I-6 creating, 10-66
reference, 15-95 defining, 10-64
defining, 15-95 Jupiter, 1-1
inserting, 15-95
indexing reference map features, 15-95
K
inserting
data table into layout window, 15-98 Knowledge Base, A-1
features into feature class, 8-24
grids, 15-79 L
cartographic, 15-79 labels, 12-1
reference, 15-92 creating, 12-3
reference index, 15-95 inserting, 12-1
hypertext, 8-34, 8-35 as feature class, 12-2
images as query, 12-1
georeferenced, 5-2 leader lines, 12-5
interactive, 5-2 moving, 12-9
into warehouses, 3-19, 5-1 placement, 12-2
labels, 12-1 text, 6-40
layout frames, 15-43 editing, 8-28
leader lines on labels, 12-5 resolving conflicts, 12-9
legends, layout window, 15-52 layers, 14-15
maps layer groups, 14-17
graphics into layout sheets, 15-49 manipulating, 14-17
into layout sheets, 15-49 manipulating, 14-15
marginalia into layout sheets, 15-52 layout frames, 14-6, 15-6, 15-43
non-map graphics into layout window, 15- layout sheets, 14-1
34 background, 14-13
north arrow, layout window, 15-59 deleting, 14-3, 14-13, 16-16
object, layout window, 15-34 exporting, 14-9
IN-12
Index
GeoMedia, 14-5 map window display properties, 15-2

inserting, 14-4 plot scale, 15-10
legends, 15-52 reference grids, 15-92
maps into, 15-49 reference index, 15-95
marginalia, 15-52 symbology, 15-3
north arrows, 15-59 deleting
scale bars, 15-61 layout sheets, 14-3, 14-13, 16-16
layout frames, 14-6, 15-6 marginalia, 15-47, 15-52
manipulating, 14-12 designing map layout, 15-8
modifying map graphics, 15-65 drawing commands, 15-13, D-1
page setup, 14-3 Drawing toolbox, 15-13
default, 16-9 elements, changing properties, 15-17, 15-
for printing, 16-8 26
placing graphics with layout frames, 15-43 exporting layout sheets, 14-9
printing, 14-3, 16-10 geographic extent methods, 15-9
renaming, 14-12 GeoMedia
saving, 14-3, 16-16 layout sheet, 14-5
selecting, 14-12 layout template file, 14-5
updating map graphics in, 15-63 graphics
viewing, 14-13 commands, 14-1, 15-13, D-1
workflows, 15-6 components, 15-13
working, 14-13 converting legend to raster, 15-74
layout window inserting, 15-8
.pdf file, 16-16 modifying, 15-65
background sheet, 14-13 non-map, 15-34
changing updating, 15-63
element properties, 15-17 workflow, 15-36
group properties, 15-19 grids, 14-2, 15-79
legend properties, 15-53, 15-73 reference, 15-92
legend properties, map, 15-75 reference index, 15-95
map properties, 15-70 group, changing properties, 15-19
general, 15-71 hiding, 14-1
geometry and content, 15-70 Imagineer
rotation, 15-72 drawing file, 14-5
north arrow properties, 15-76 template file, 14-5
object properties, 15-79 importing
symbol properties, 15-32 drawing file, 14-5
text properties, 15-21 template file, 14-5
color inserting
fill, 15-28 data table, 15-98
line, 15-25 grids, 15-79
converting legend to raster graphics, 15-74 layers, 14-15
creating symbols in, 6-35 layout frames, 15-43
defining layout sheet, 14-4
cartographic grids, 15-79 legends, 15-52
IN-13
map graphics, 15-8, 15-44 inserting, 15-59

maps into, 15-49 object, 15-34
marginalia, 15-11, 15-52 changing properties, 15-79
non-map graphics, 15-34 outputting PDF from, 16-17
north arrows, 15-59 overview, 14-1
objects, 15-34 page setup, 14-3
reference grids, 15-92 default, 16-9
reference index, 15-95 for printing, 16-8
scale bars, 15-61 placing
layer groups, 14-17 and editing commands, 15-15
layers, 14-15 lines, 15-22
layout frames, 14-6, 15-43 text, 15-20
layout graphics components, 15-13 plot scale, 15-10
Drawing toolbox, 15-13 plotting, 14-3, 16-16
layout toolbar, 15-16 previewing map in map window, 15-4
placing and editing commands, 15-15 printing
layout sheet, 14-1 graphics, 16-16
layout toolbar, 15-16 layout sheets, 16-10
legend, 15-5, 15-12 to file, 16-8
changing properties, 15-53, 15-73 properties, 14-14
converting to raster graphics, 15-74 element, 15-17
customizing, 15-53 group, 15-19
examples, 15-56 legend, 15-53, 15-73
inserting, 15-52 legend, map, 15-75
map, changing properties, 15-75 map, 15-70
line terminators, 15-26 map graphics, 15-65
map frame north arrow, 15-76
map pan, 15-69 object, 15-79
map zoom in/out/previous, 15-69 scale bar, 15-77
map graphics symbol, 15-32
static and dynamic modes, 15-11, 15-65 text, 15-21
updating, 15-63 visible status, 14-14
map layout components, 15-8 reducing map frames, 15-66
map properties, changing, 15-70 reference
map window, 15-8 grids, 15-92
components, 15-8 index, 15-95
printing considerations, 15-1 renaming layout sheets, 14-12
marginalia saving layout sheets, 14-3, 16-16
inserting, 15-43, 15-52 scale bar, 15-6, 15-12
specifications, 15-11 changing properties, 15-77
MicroStation, layout template file, 14-5 inserting, 15-61
non-map graphics, 15-34 scaling map extents, 15-66
normal.glt, 14-5 selecting sheets, 14-12
north arrow, 15-5, 15-12 setting display controls, 14-1
changing properties, 15-76
IN-14
Index
SmartSketch controlling appearance of, 6-58

drawing file, 14-5 customizing, 6-57
template file, 14-5 deleting, 6-62
SmartSnap, setting, 15-33 deleting map objects through, 6-66
starting, 14-1, 14-4 displaying, 6-40, 15-5
symbols docking, 6-38
changing properties, 15-32 entry display, 6-5
creating, 15-28 entry properties, 6-32
placing, 15-31 fitting, 6-60
setting active, 15-30 group entries, 6-37
text, 15-20 hiding, 6-40
changing properties, 15-21 hierarchical entry display, 6-37
update mode naming, 6-61
dynamic, 15-11, 15-65 renaming, 6-61
static, 15-11, 15-65 replacing, 6-61, 6-62
updating map graphics in, 15-63 resizing, 6-38
visible sheet status, 14-14 right mouse menu, 6-63
workflows, 15-6, 15-36, 15-43, 15-49 setting
working sheet, 14-13 defaults for, 6-56
working with, 14-1 entry styles, 6-5, 15-2
zooming style keys, 6-39
map zoom in/out/previous, 15-69 tabs, 6-36
to actual size, 15-32 thematic classes, 6-48
to nominal map scale, 15-4 thematic entries, 6-44
leader lines thematic entries, types, 6-44
inserting on labels, 12-5 thematic styles, 6-49
moving labels, 12-9 toolbar, 6-62
terminator symbol, 12-7 understanding, 6-36
Learning GeoMedia, 1-3, 1-4 master, 6-56
legend named, 6-56, 6-57, 6-59, 6-62
adding map objects, 6-41 libraries, 17-1
editing entry style, 6-31 creating, 17-2
layout connections, 17-3
changing, 15-73 managing connections, 17-7
converting to raster graphics, 15-74 organizing, 17-9
customizing, 15-53 symbol, 6-33
displaying, 15-12 template, 17-2, 17-4
examples, 15-56 Licensing Utility, online documentation, 1-3
inserting, 15-52 line
map placing in layout window, 15-22
adding entries, 6-41 terminators in layout window, 15-26
adding entries, image, 6-43 linear
adding entries, thematic, 6-44 features, 8-2
adding entries, thematic displays, 6-57 network queries, 10-2, 10-25
changing style, 6-32 referencing
IN-15
analysis, 11-6 manipulating

data structures, G-1 layers, 14-15
duration, G-8 groups, 14-17
duration with external markers, G-11 layout sheets, 14-12
duration with internal markers, G-9 map
event, G-14 colors, 8-20
event, duration, G-17 graphics, updating in layout sheet, 15-63
event, marker offset, G-15 grids, 15-79
event, measure, G-14 reference, 15-92
event, XY, G-16 reference index, 15-95
measure, G-3 objects
measure with external markers, G-6 adding to legend, 6-41
measure with internal markers, G-4 deleting, 6-66
dynamic segmentation, 11-6, 11-12 display properties, 6-10
event data, 11-4, 11-6 displaying, 6-1, 6-9
event features, 11-12 locatability, 6-11
features, 11-4 priority, 6-9
Geospatial Technology, 11-2 setting scale range for, 6-11
introduction, 11-1 style of, 6-12
LRS, 11-1 scale
marker model, 11-12 nominal, 6-5
measure model, 11-12 zoom to nominal, 6-7, 15-4
precision location, 11-6 thematic, 6-44
units of measure, B-14 classes, 6-48
linking display, 6-39, 6-57
geometry data to coordinate systems, 5-8 legend entry types, 6-44
GeoWorkspace, 2-7 Range Thematic, 6-46
loading Standard, 6-44
customized settings, 1-8 styles, 6-49
data, delaying GeoWorkspace, 2-3 Unique Value, 6-45
locatability, map objects, 6-11 viewing tools, 6-7
locate zone, 8-19, 15-34 windows
location, precision, 11-6 by extent, spatial filter, 10-34
longitude ranges, B-20 changing legend properties in layout
LRS, G-1, See linear referencing window, 15-75
components, 15-8
M controlling, 6-2
managing creating, 6-66
catalog connections, 9-10 north arrow, 6-67
categories, 8-44 properties, 6-67
library connections, 17-7 page setup, 16-1
metadata, 9-26 previewing before printing, 15-4
searches, 10-57 printing, 16-3
spatial filters, 10-37 properties, changing, 6-2
warehouse images, 5-8 properties, defining, 6-4
IN-16
Index
Queued Edit, 10-49 catalogs, 9-1

selecting features, 8-18 managing, 9-26
tooltip, 6-64, 6-65, 8-21 geospatial, 9-3
using the mouse in, 6-6 queries, 9-26
working with, 6-1 SVG Symbol Metadata XML schema, H-
MapInfo, 3-16, 4-9 19
displaying, 3-19 updating databases, 9-7
Interchange Format, exporting to, 18-5 MGDM, 3-16, 4-10, 10-45
server, 4-9 MGE, 3-16, 4-2, 4-10, 8-36, 10-45
table defining MapInfo geometry from MGE Segment Manager. See MGSM
GeoMedia Professional, 18-6 MGSM, 3-16, 4-2, 4-10, 8-36, 10-2, 10-45
warehouse, 4-9 linear network queries, 10-25
marginalia, 6-1 native queries, 10-22
layout Parameter File, online documentation, 1-3
inserting, 15-11, 15-52 server, 4-10
legend, 15-12, 15-73 warehouse, 4-10
north arrow, 15-5, 15-12, 15-76 Microsoft, 1-1
scale bar, 15-6, 15-12, 15-77 MicroStation, 4-2, 4-6, 5-7, 14-5
specifications, 15-11 layout templates, 14-7
map supported element types, 4-6
legend, 6-36, 15-5 model
north arrow, 6-67 geocoding, 13-5, I-2, I-12
scale bar, 6-69 marker, dynamic segmentation, 11-12
marker model, dynamic segmentation, 11-12 measure, dynamic segmentation, 11-12
master legend, 6-56 Modular GIS Environment. See MGE
measure model, dynamic segmentation, 11- mouse
12 IntelliMouse, 1-7, 6-7
measuring using, 1-7
angles, 6-75 in a data window, 7-3
area, 6-73 in a map window, 6-6
conversion tables, E-1 moving
distance, 6-73 features, 8-41
setting options, Units and Formats tab, 3- labels, 12-9
12 multimedia files, 8-36
menus, customizing, 1-7 multi-user environment, 4-19
merging
analytical, 10-86 N
functional attribute, 10-88 named
performing, 10-89 geodetic datums, B-11
right mouse menu, 10-88 legend, 6-56, 6-57, 6-59, 6-62
workflow, 10-91 spatial filters, 10-40
feature classes with queries, 10-86 native queries, 10-19
vs. aggregating, 10-99 defining, 10-19
metadata MGSM, 10-22
AFM, 4-15 Oracle, 10-20
IN-17
neatline, 15-80 for linear network queries, 10-25

coordinate system, 15-81 for native spatial queries, 10-19
defining, 15-90 for spatial filters, 10-37
parameters, 15-81 for spatial queries, 10-9, 10-12
placing, 15-82 Options
normal.glt, 14-5 changing
normal.gwt, 2-1 default folder, 2-4
normal.mdt, 4-3 GeoWorkspace location, 2-5
north arrow map display, 8-20
displaying, 6-67 measurement, 6-73
layout template location, 2-6
changing, 15-76 File Locations tab, 2-4
displaying, 15-12 General tab, 2-3
inserting, 15-59 Layout tab, 14-2
properties, 15-59 Map Display tab, 6-2
map setting
changing, 6-68 delete confirmation box, 8-43
displaying, 15-5 layout window controls, 14-1
properties, 6-67, 6-68 query display location, 10-6
SmartLocate, 8-18
O status bar display, 6-8
objects, layout sheet Oracle, 4-10
changing, 15-79 catalogs, F-1
inserting, 15-34 native queries, 10-19
properties, 15-79 Object
ODBC Model, 4-2
catalogs, 9-9 server, 4-12
Tabular warehouse, 4-12
data server feature classes, 8-5 spatial operators, 10-10, 10-39
server, 4-11 organizing libraries, 17-9
warehouse, 4-2, 4-11 outputting
offset feature data to warehouses, 8-10
display concepts, 10-23 PDF from layout window, 16-17
origin in layout window printing, 16-11 overlap spatial operator, 10-39
OLE, 7-8 overlay operators, 10-25
server, 2-7
opening P
GeoWorkspace, 2-2 page setup for printing, 16-1
layout windows, 14-4 data window, 16-5
map window, 6-1 layout window, 14-3, 14-13, 16-8
warehouse connections, 4-18 map window, 16-1
operands, functional attribute, 10-78 pan, 6-8
operators dynamic mode, 6-8, 15-69
for attribute queries, 10-2 fast mode, 6-8, 15-69
for functional attribute, 10-79 layout window, 15-69
IN-18
Index
map, 15-65 .prn, 16-4

parameter files, 4-11 workflows, 15-6
parsing priority, changing display, 6-9
addresses, 13-3, I-14 programming guides, 1-5
Define Parsing Rules utility, 13-2, 13-4, I- projected coordinate systems, 3-1
2, I-14, I-16 projection algorithms, B-1
defining rules, 13-19 properties
rules, I-21 elements, 15-17
PDF, outputting from layout window, 16-17 geometry, 15-19
PickLists, Access, 4-21 group, 15-19
PickQuick, 8-20, 15-47 layout
map window tooltip, 8-21 legend, 15-73
placing window, 14-14
grids, 15-79 legend, 15-53
reference, 15-92 entry, 15-55
reference index, 15-95 map, 15-65, 15-70
labels, 12-2 general, 15-71
plotting geometry and content, 15-70
.pdf file, 16-16 objects, 6-10
batch, 14-10, 15-19, 16-16 rotation, 15-72
layout window, 14-3, 16-16 window, 6-2, 6-4
workflows, 15-6 window display, 15-2
point features, 8-2 window legend, 15-75
Precision Coordinates, dockable control, 3- north arrow, 6-68, 15-59, 15-76
11 object, 15-79
precision location, linear referencing, 11-6 scale bar, 6-70, 15-61, 15-77
preparing to connect to warehouse, 4-4 select set, 8-39
printing, 16-1 symbols, 15-32
.pdf file, 16-16 text, 15-21
data window, 16-7 Publish Address Geocoding Utility, online
page setup, 16-5 documentation, 1-4
graphics Publish to GeoMedia SmartStore
translucent, 16-16 online documentation, 1-4
transparent, 16-16
in GeoMedia, 16-1 Q
layout sheets, 16-10 Quad-Tree algorithm, 10-39
layout window, 16-10 queries, 10-1
page setup, 16-8 aggregation, 10-91
map window, 16-3 attribute
page setup, 16-1 editing selection through Queries
page setup, 16-1 command, 10-105
data window, 16-5 filter, 10-1, 10-2
layout window, 16-8 buffer zones, 10-72
map window, 16-1 categories, 8-43
to a file, 16-4 combination, 10-11
IN-19
combined, 10-2 queue

combining with feature classes, 10-106 dynamic, 10-46
deleting, 10-30 static, 10-46
displaying, 10-27 statistics, 10-55
editing, 10-29 subqueues, 10-55
filter, 10-1 viewing options, 10-50, 10-53
graphics-only features, 10-45 queues
joins, 10-64, 10-65 dynamic, 10-46
labels, 12-1 Queued Edit, 10-45
linear network, 10-2, 10-25 static, 10-46
manipulating, 10-27
merging with feature classes, 10-86 R
metadata, 9-26 Range Thematic legend entry type, 6-46
native, 10-19 raster data, 3-16
MGSM, 10-22 changing image display, 5-12
Oracle, 10-19 compression techniques, C-3
operators converting layout window legend to, 15-74
for attribute queries, 10-2 displaying, 3-19
for native spatial queries, 10-19 file types and categories, georeferenced
for spatial queries, 10-9 image, C-5
searches, 10-57 formats supported in GeoMedia, C-1
select set, 8-22 information, C-1
spatial, 10-1, 10-8, 10-12, 10-15 inserting, 5-1
analysis tiling, C-4
spatial difference, 10-15 types, C-4
spatial intersections, 10-12 read-only warehouses, 2-2, 4-2
difference, 10-15 readouts
intersections, 10-12 coordinate, 3-11
SQL filter, 10-3 precision coordinates control, 3-11
union read-write warehouses, 1-2, 8-1, 18-5
editing through Queries command, 10- creating, 4-3
111 reference
with feature classes, 10-106 ellipsoid. See ellipsoids
working with, 10-1 features, spatial filter, 10-33, 10-42
Queued Edit, 10-45 grids, 15-92
additional commands, 10-54 index, 15-95
control, searches, 10-60, 10-63 referencing systems, linear, 11-1
data window, 10-52, 10-64 refreshing
delete queue, 10-54 map display, 6-8
dockable control, 10-47 with warehouse changes, 4-19
interface, 10-46 Release Notes, A-1
map window, 10-49, 10-64 resolving text conflicts, labels, 12-9
legend, 10-49 reviewing coordinate systems for feature
navigating queues, 10-48 classes, 3-7
right mouse menu, 1-7
IN-20
Index
analytical merging, 10-88 data window, 10-64

map window legend, 6-63 managing predefined, 10-57
RIS, 4-11 map window, 10-64
rooftop data, geocoding, 13-2 navigating, 10-63
rotation performing, 10-60
angle, 15-2 predefined, 10-60
layout window, properties, 15-72 creating, 10-58
map view angle, 6-5 deleting, 10-60
editing, 10-59
S performing, 10-62
saving Queued Edit control, 10-60, 10-63
customized settings, 1-8 viewing options, 10-64
GeoWorkspace, 2-4 seed files, 4-11, 18-15
plot sessions, 14-3, 16-16 segmentation, dynamic, 11-6, 11-12
warehouse, 4-3 select set, 8-20
scale clearing, 8-22
display, 6-4 editing properties, 8-39
map nominal, 6-5 queries from, 8-22
plot, 15-10 spatial filter, 10-34
range, setting, 6-11 Select Tool, 8-20, 15-14, 15-16
viewing, 6-2 selecting
zoom to nominal map, 15-4 attributes, 10-103
scale bar, 15-6 data window contents, 7-4
displaying, 15-6 features in map window, 8-18
examples, 6-70 layout sheets, 14-12
layout selection buttons, 8-21
changing, 15-77 self-help support, A-1
displaying, 15-12 sending GeoWorkspace, 2-5
inserting, 15-61 servers
map Access, 4-4
changing, 6-70 AFM proxy, 4-15
displaying, 6-69 ARC/INFO, 4-5
inserting, 6-69 ArcView, 4-5
properties, 6-70 AutoCAD, 4-6
scanner exporting to, 18-17
AutoCAD, 3-18 FRAMME, 4-7
IGDS, 3-18 GeoGraphics, 4-7
schema GML, 4-8
CAD server, 3-18, 6-77 exporting to, 18-21
definition file, 4-6 MapInfo, 4-9
SVG Symbol Metadata XML, H-19 exporting to, 18-5
searches, 10-57 MGE, 4-10
ad hoc, 10-60 MGSM, 4-10
creating, 10-61 ODBC Tabular, 4-11
performing, 10-61 OLE, 2-7
IN-21
Oracle Object Model, 4-12 by select set, 10-34

SmartStore, 4-13 defining, 10-32
SQL, 4-13 designating reference features, 10-42
Text File, 4-13 fitting, 10-40
WFS, 4-14 managing, 10-37
WMS, 4-14 named, 10-40
setting units and formats, 3-12 operators, 10-37
setting up options, 10-37
page for printing, 16-1 removing, 10-40
SmartSnap, 15-33 with layout windows, 15-10
settings, customized menus and toolbars, 1-8 workflows, 10-35
shapefiles, 4-2, 4-5 intersection, 10-12
exporting to, 18-1 operators, 10-9, 10-12, 10-19
sheets queries, 10-1, 10-8
background layout, 14-13 spinning features, 8-41
exporting layout, 14-9 SQL, 10-8
inserting layout, 14-4 catalogs, F-1, F-8
layout, 14-1 Data Server, 4-2, 4-13
style, 9-17, 9-20 warehouse, 4-13
working layout, 14-13 dialects, 10-3
SmartLocate, 8-18, 8-19 in queries, 10-3
PickQuick, 8-20 standard
SmartSketch geodetic datums, B-9
drawing file, 14-5 legend entry type, 6-44
template file, 14-5 style, 6-32
SmartSnap State Plane zone codes
locate zone, 15-34 NAD 27 Datum, B-16
setting in layout window, 15-33 NAD 83 Datum, B-17
SmartStore statistics
.ddc Profile files, 4-13 data window, 7-6
online documentation, 1-4 Queued Edit, 10-55
Server, 4-2 thematic style, 6-48
warehouse, 4-13 street centerline data, geocoding, 13-2
snaps, SmartSnap, 15-33 Structured Query Language. See SQL
snapshot style
of data window, 7-8 animation, 6-30
of map window, 6-77 attribute-based, 6-28
spatial changing
aggregation, 10-93 feature, 6-32
difference, 10-15 legend entry, 6-32
filters, 10-31 classes, 6-12
by existing filter, 10-34 collections, 6-19
by map window extent, 10-34 synchronizing elements, 6-22
by not using filter, 10-34 creating, 6-22
by reference features, 10-33 editing legend entry, 6-31
IN-22
Index
expressions, 6-28 layout window

legacy, 6-13 changing properties, 15-32
legend keys, 6-39 creating, 15-28
managing, 6-22 placing, 15-31
named, 6-22, 6-24 setting active, 15-30
of map objects, 6-12 leader line terminator, 12-7
presentation libraries, 6-33
Range Thematic, 6-32 predefined, 6-15
Standard, 6-32 spinning, 8-41
Unique Value Thematic, 6-32 styles, 6-15
properties, 6-25 SVG
selecting, 6-31 supported element types, H-1
setting legend entry, 6-5, 15-2 Symbol Metadata XML schema, H-19
sheet
.xls, 9-17, 9-20 T
catalog, 9-17, 9-20 technical
synchronizing elements, 6-22 notes, A-1
thematic, 6-49 support, A-1
types, 6-12, 6-14 templates
area, 6-18 catalog, 9-7
compound, 6-19 creating
font, 6-14 Access warehouse, 4-20
hatch fill, 6-17 from layout window, 14-9
image, 6-18 GeoWorkspace, 2-6
pattern, 6-16 default Access, 4-3
pattern fill, 6-17 exporting from layout window, 14-9
picture, 6-14 GeoMedia layout, 14-5
simple fill, 6-17 GeoWorkspace, 2-1, 2-6
simple line, 6-16 Imagineer, 14-5
symbol, 6-15 importing into layout window, 14-5
text, 6-18 library, 17-2, 17-4
thematic, 6-44 MicroStation layout, 14-5
support, Intergraph, A-1 normal.gwt, 2-1
SVG normal.mdt, 4-3
example, H-24 SmartSketch, 14-5
files, 6-15 warehouse, 4-3, 4-20
supported element types, H-1 text
Symbol Metadata XML schema, H-19 adding hypertext to feature classes, 8-34
symbol cells, 7-7
files features, 8-2
creating in layout window, 6-35 editing, 8-28
creating with Define Symbol File, 6-33, inserting, 8-26
6-36 files, 4-11, 4-13
for feature-class displays, 6-33 attaching external data source, 8-5
label, 6-40
IN-23
editing, 8-28 displaying, 1-7

resolving conflicts, 12-9 layout window, 15-15, 15-28
MapInfo warehouse, 4-10 tools
placing in layout window, 15-20 data view, 7-4
properties, 15-21 defining coordinate systems, 4-5, 4-6, 4-9
spinning, 8-41 map viewing, 6-7
SQL, 10-3 resolving text conflicts, labels, 12-9
style, 6-18 tooltips, 8-38
Unicode, 1-7 map window, 6-64, 6-65
Text File PickQuick, 8-21
Server, 4-13 transformation
Format File, 4-13 datum, 3-14
warehouse, 4-13 models, B-1
thematic triggers, Oracle Object Model modification
display, 2-4, 6-39, 10-27 log, 4-19
change attributes, 6-58 typeface conventions, 1-4
to legend, 6-57 types
maps, 6-44, 6-57, 10-68 aggregation, 10-92
adding legend entries, 6-44 style, 6-12
classes, 6-48
creating, 6-44 U
legend entry types, 6-44 Unicode, 1-7
Range Thematic, 6-46 union
Standard, 6-44 editing query, 10-111
styles, 6-49 feature classes/queries, 10-106
Unique Value, 6-45 Unique Value legend entry type, 6-45
Range Thematic, 6-32 units of measure, B-14
ranges, 6-40 angular, 6-5, B-15
Unique Value Thematic, 6-32 area, B-15
ticks and crosses conversion tables, E-1
coordinate system, 15-87 linear, B-14
defining, 15-91 setting, 3-12
parameters, 15-86 Units and Formats tab, Define Coordinate
ticks, grid, 15-86 System dialog box, 3-12
crosses, 15-86 updating
defining, 15-91 image records, 5-10
parameters, 15-86 map
placing, 15-87 graphics in layout sheets, 15-63
tiling raster data, C-4 windows, all, 6-8
tolerance metadata databases, 9-7
locate zone, 8-19, 15-34 USGS DOQ header, 5-2
spatial queries, 10-11 utilities
toolbars, 1-7 Define CAD Server Schema File, 6-77
customizing, 1-7 Define Coordinate System File, 3-1, 3-18,
legend, 6-62 3-19, 4-5, 5-7, 10-73, E-1
IN-24
Index
Define Parsing Rules, 13-2, 13-4, I-2, I-14, MGSM, 4-10

I-16 ODBC Tabular, 4-11
Define Text File Server Format File, 4-13 opening connections, 4-18
documentation, 1-3 Oracle Object Model, 4-12
Publish Address Geocoding Index, 13-2, outputting feature data to, 8-10
13-4, I-13, I-15 proxy, 4-15
Publish to GeoMedia SmartStore read-only, 4-2
Warehouse, 4-13 read-write, 8-2
UTM zones, B-20 SmartStore, 1-4
SQL Server, 4-13
V templates for, 4-20
values, map ID, 10-45 Text File Server, 4-13
vertices of feature geometry, 8-42 WFS Server, 4-14
view WMS, 4-14
at current scale, 6-2 working with connections, 4-15
data tools, 7-4 WFS, 4-2
legend, 6-41 Data Server, 4-14
scale bar, 6-69 warehouse, 4-14
viewing windows
changes in multi-user environment, 4-19 data, 7-1
tools, 6-7 layout, 14-1
Visual Basic, 1-1 map, 6-1
Visual C++, 1-1 Windows
Vista, 1-1
XP, 1-1
W
wizard, GeoMedia Command Wizard Help
warehouses, 4-1 Topics, 1-2
Access, 4-4 WMS, 4-2
ArcView, 4-5 Data Server, 4-14
CAD, 4-6 warehouse, 4-14
closing connections, 4-18 workflow
connecting to, 4-4, 4-17, 4-19 accessing warehouses, 4-2
creating read-write, 4-3 address geocoding, I-1
data-display workflow, 4-2 catalogs, 9-37
defining coordinate systems for, 4-4 creating a GeoWorkspace, 2-1
FRAMME, 4-7 displaying geographic data, 6-1
GeoGraphics, 4-7 for using GeoMedia, 1-9
GML, 4-8 generating base geometry, 10-101
importing into, 4-2 geocoding addresses, 13-14
inserting images into, 5-1 multiple datasets, 13-17
managing images, 5-8 parsing rules, 13-22
MapInfo, 4-9 importing data, 4-2
matching default GeoWorkspace layout window graphics commands, 15-36
coordinate systems, 3-9 performing analytical merge, 10-91
MGDM, 4-10 placing map graphics, 15-43, 15-49
IN-25
spatial filter, 10-35 XML

using layout window, 15-6 catalogs, 9-17
working sheets, 14-13 images, 5-8
working with SVG Symbol Metadata schema, H-19
coordinate systems, 3-1
data windows, 7-1 Z
feature classes, 8-2 zone
features, 8-1 buffer, 10-72
functional attribute, 10-75 codes, state plane, B-16, B-17
GeoWorkspaces, 2-1 locate, 8-18
layout windows, 14-1 UTM, B-20
map windows, 6-1 zoom
queries, 10-1 in, 6-7
warehouse connections, 4-15 map zoom in, 15-69
Working with GeoMedia, 1-3 map zoom out, 15-69
world file, 5-2 map zoom previous, 15-69
WYSIWYG, 6-5, 15-3, 15-33 out, 6-7
to actual size, 15-32
X to nominal map scale, 6-7, 15-4
Xbase, attaching external data source, 8-5 to previous, 6-7
IN-26
Additional information on Intergraph Support and Services is available on the Internet. Use a
web browser to connect to Intergraph Online at http://www.intergraph.com/.
For general Intergraph information, call 1-800-791-3357 (U.S. and Canada) or 001-256-730-2000
(international).

01/2008
DJA0628D0

WorkingwithGeoMedia PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

WorkingwithGeoMedia PDF

Hochgeladen von

Copyright:

Verfügbare Formate

Working with GeoMedia®

Working with GeoMedia

1. How much of this document have you worked through? 1. 1 - 2 - 3 - 4 - 5

2. How easy was this document to read and understand? 2. 1 - 2 - 3 - 4 - 5

3. How easy was it to find specific information in this document? 3. 1 - 2 - 3 - 4 - 5

4. What was your primary intent in using this document? 4. 1 - 2 - 3 - 4 - 5

5. How well did this document satisfy this intent? 5. 1 - 2 - 3 - 4 - 5

6. Have you used Intergraph software before? (1=yes, 2=no) 6. 1 - 2

7. What percentage of your work time is spent using Intergraph software? 7. 1 - 2 - 3 - 4 - 5

8. How would you rate your level of software use? 8. 1 - 2 - 3 - 4 - 5

13. How would you improve this document?

BUSINESS REPLY MAIL

POSTAGE WILL BE PAID BY ADDRESSEE

Security, Government & Infrastructure (SG&I) Division

Working with Images ................................................................................................................. 5-1

Associating Catalog Records ............................................................................................... 9-21

Working with Layout Windows .............................................................................................. 14-1

Exporting Data to Other Systems .......................................................................................... 18-1

Conversion Tables .....................................................................................................................E-1

LRS Data Structures ................................................................................................................. G-1

Index .......................................................................................................................................... IN-1

Looking at GeoMedia: An Overview

What You Need to Know to Work

• Publish Address Geocoding Index

Typeface Conventions Used in the Documents

What’s New in GeoMedia 6.1

Getting Around in the Software

Customizing the Menus and Toolbars

Using the Customize Command

Using the Save/Load Customized Settings Commands

Note: A standard menus and toolbars customized settings file,

The Product Workflow

What Can I Do with a GIS ?

• Visualize information more effectively and intuitively.

GIS Concepts & Terminology

Features—Features are digital representations for real-world entities.

• Features can represent almost anything.

• Features can be organized into categories, themes, or layers.

Coordinate Systems and Projections—Mathematical transformations must take place to

Analytical Commands—Complex analyses and processing of the contents of the GIS.

The software assigns a default title of GeoWorkspace1 to each new GeoWorkspace.

2. Select the GeoWorkspace you want.

Delaying Data Loading

Automatically Backing Up GeoWorkspaces

Saving, Closing, and Copying a GeoWorkspace

To change the location of your GeoWorkspace files:

1. Select File > Send.

Creating a GeoWorkspace Template

To create a GeoWorkspace template:

Linking and Embedding a GeoWorkspace

Note: To customize the datum transformation, edit the datum-transformation-building

You can change coordinate-system settings in an individual GeoWorkspace at any time.

Defining a Coordinate System for a GeoWorkspace

To define a GeoWorkspace coordinate system:

Note: Changing the coordinate system type from Projection or Geocentric to

Note: Changing the coordinate system type from Projection or Geographic to

8. On the GeoWorkspace Coordinate System dialog box, click OK.

Defining a Coordinate System for a Feature Class

To define a coordinate system for a new feature class:

Note: Changing the coordinate system type from Projection or Geocentric to

Note: Changing the coordinate system type from Projection or Geographic to

13. Click OK on the New <feature class name> dialog box..

Matching GeoWorkspace and Default Warehouse