Professional Documents
Culture Documents
Professional
1. 1 - 2 - 3 - 4 - 5
2. 1 - 2 - 3 - 4 - 5
3. 1 - 2 - 3 - 4 - 5
4. 1 - 2 - 3 - 4 - 5
5. 1 - 2 - 3 - 4 - 5
6.
6. 1 - 2
7. 1 - 2 - 3 - 4 - 5
8. 1 - 2 - 3 - 4 - 5
9. Did this document help you learn to use the software in a satisfactory way?
(1=yes, 2=no)
9. 1 - 2
10. How would you rate this document overall? (1=poor . . . 5=excellent)
10. 1 - 2 - 3 - 4 - 5
11. 1 - 2
12. Please describe and note page numbers of any errors or inconsistencies in this document.
Name
Date
Organization
Phone
Address
City
Thanks again for your time and effort.
State
Zip Code
--------------------------------------------------------------------------------------------------
HUNTSVILLE, AL
--------------------------------------------------------------------------------------------------
Table of Contents
Start Here .................................................................................................................................... 1-1
Looking at GeoMedia Professional: An Overview ............................................................... 1-2
What You Need to Know to Work......................................................................................... 1-3
Documents Provided .............................................................................................................. 1-3
Getting Started ....................................................................................................................... 1-7
Getting Around in the Software ............................................................................................. 1-7
Customizing the Menus and Toolbars.................................................................................... 1-8
The Product Workflows ....................................................................................................... 1-10
What is a GIS? ..................................................................................................................... 1-16
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-15
Viewing Changes in a Multi-User Environment.................................................................. 4-19
Creating an Access Warehouse Template............................................................................ 4-19
Changing the Coordinate System of a New Access Warehouse Template .......................... 4-20
Configuring PickLists with Access Warehouses ................................................................. 4-21
Table of Contents
Table of Contents
vi
Table of Contents
vii
viii
Start Here
Welcome to GeoMedia Professionalthe 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.
This product is the perfect tool for collecting GIS data, populating an enterprise
database, and turning information into precise finished maps for distribution and
presentation.
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 software, 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.
As a data capture and maintenance tool, this product allows you to capture and to edit data
more easily, faster, and with more intelligence than other products. Its integrated vector
and raster snaps allow you to capture vector data from raster images, automatically
identifying snap points to ensure accurate heads-up digitizing. The software also provides
table-top digitizing and vector transformation for data requiring geometry transformation.
Using the software, you can capture clean, accurate data the first time, thus minimizing
editing. Automatic vector breaking and coincident geometry digitizing allow you to avoid
traditional data-capture problems. However, you can locate data-capture problems with
automatic error detection and then correct them with intelligent feature placement and
editing tools. Furthermore, you can quickly annotate the data with powerful labeling and
text-placement tools.
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++.
1-1
1-2
Start Here
You can also perform tasks, such as capturing new data, performing maintenance on
existing data, and inserting images or buffer zones. Furthermore, you can view data
written to a read-write warehouse 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.
Documents Provided
The documents provided with GeoMedia Professional are delivered into three groups:
Developer Documentation, User Documentation, and Utilities Documentation.
Note: The way your user interface looks will depend on your operating system and how
your System Administrator and you have configured your software. What you see at your
workstation may differ slightly from the examples shown in online Help or other product
documents.
Developer Documentation
Document
GeoMedia Professional
Command Wizard Help
GeoMedia Professional
Object Reference
Description
Information about using the Command Wizard to create
Visual Basic commands for the GeoMedia-based application
and to edit or to delete Visual Basic or Visual C++ commandset information. Access through the Command Wizard.
Programmer's guide to the objects, methods, and properties in
the softwares automation layer. Access through Start > All
Programs > GeoMedia Professional > Developer
Documentation.
Information about customizing the software and building your
own applications with the GeoMedia engine. Access through
Start > All Programs > GeoMedia Professional>
Developer Documentation.
1-3
User Documentation
Document
Description
GeoMedia
Professional Help
Installing
GeoMedia
Professional
Learning GeoMedia
Professional
Working with
GeoMedia
Professional
Utilities Documentation
Utilities Documentation consists of online-only documentation for the following delivered
utilities (Start > All Programs > GeoMedia Professional > Utilities):
1-4
Batch Plotting
Database Utilities
Licensing Utility
Start Here
Selecting the utility document name in the GeoMedia Professional Help menu; then
Selecting online Help from the utility Help menu in the Batch Plotting, Define CAD
Server Schema File, Define Text File Server Format File, and Publish to GeoMedia
SmartStore Warehouse utilities.
Keyboard keys.
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
unserifed
type
Courier
type
Italic type
Interactive Documents
This product provides an interactive tutorial to help you learn how to perform the basic
tasks. If you are new to the software, you should work through Learning GeoMedia
Professional first.
Help is available online if you need step-by-step instructions, and other documents are
available for programmers who want to customize the software.
After you have worked through the tutorial, use Working with GeoMedia Professional 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
Professional CD in your CD-ROM drive or be connected to the network node containing
the Help files.
To display Help when GeoMedia Professional is active, select Help > GeoMedia
Professional Help from the menu. To display Help when GeoMedia Professional is
not active, select Start > All Programs > GeoMedia Professional > User
Documentation > GeoMedia Professional 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.
GeoMedia Professional Object Reference covers the objects, methods, and properties
available through automation.
You access these documents by selecting All Programs > GeoMedia Professional >
Developer Documentation from the Start menu.
Start Here
Getting Started
To start this product, select Start > All Programs > GeoMedia Professional >
GeoMedia Professional. If the introductory GeoMedia Professional dialog box has not
been turned off, this 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 Dont show this dialog box again check box.
Note: To exit the software at any time, select File > Exit from the GeoMedia Professional
menu.
See the Working with GeoWorkspaces chapter for complete information on using
GeoWorkspaces.
Still, the GeoMedia Professional working environment does have some special
characteristics:
GeoMedia Professional 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 right mouse
menus by pressing the right mouse button. The tools on the menu vary with the
location of your cursor.
The products 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.
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.
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.
1-8
Start Here
1-9
1-10
Start Here
Data-Capture Workflows
This section presents workflows for building an enterprise GIS with GeoMedia
Professional. Whether you digitize from a paper map or an on-screen image, or
incorporate data from other digital sources, this product has the right tools for your
particular needs. Furthermore, the data-capture and clean-up tools have been optimized for
GIS workflows to increase your productivity. The workflows are as follows:
Manual input
Scanned maps
Satellite or photogrammetric images
CAD data
Attribute data in databases
Legacy GIS data
1-11
For information on data-capture and clean-up tools, see the Registering Data,
Validating and Fixing Data, Working with Features, and Editing Features and
Geometries chapters.
Manual Input
1. Select the digitizer input.
2. Set up the map on the digitizing table.
3. Register the map coordinates to a GeoWorkspace with the registration tools.
4. Select the vector feature class from a warehouse, or create new feature classes with
their own unique database properties.
5. Digitize selected features from the paper map.
6. Clean up the data with the validating and editing tools.
Scanned Maps
1. Select the scanned paper maps.
2. Place the raster image on the screen, and use the registration tools to display the raster
in the correct geographic position.
3. Select the vector feature class from a warehouse, or create new feature classes with
their own unique database properties.
4. Digitize the features on-screen with the raster image of the scanned map as the
background, using the raster snap tools to speed data capture.
Note: Raster snap can be used on binary raster data only.
1-12
Start Here
CAD Data
Into GeoMedia Professional:
1. Create a CAD data-server schema to define the folder, maps, coordinate system, and
features.
2. Connect to one or more CAD files.
3. Import the CAD features into a read-write warehouse (Access, Oracle, or Oracle
Spatial Cartridge).
4. Edit and add the GIS features in GeoMedia Professional.
OR
Build area features from the CAD linework in GeoMedia Professional.
1-13
1-14
Start Here
3. Import the selected features into a read-write warehouse (Access, Oracle, or Oracle
Spatial Cartridge).
4. Edit and add the GIS features in GeoMedia Professional.
Note: You can import GIS data into any GeoMedia Professional-supported format into an
Access or an Oracle warehouse. You can import an entire feature class or only those
features meeting the conditions that you define with an attribute filter. When you import
features, the software copies the data from the source warehouse to a target read-write
warehouse.
1-15
1. Capture GIS features using GeoMedia Professional, and store them in Access or
Oracle.
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 and graphic and
nongraphic data.
Locate information spatially for example, find a site by latitude and longitude or by
proximity to other features.
Aspects of a GIS
The following are some important aspects of a GIS system:
1-16
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.
Start Here
Types of Information
A GIS may contain the following types of information:
TextualReports, tabular data, and data streams.
Image FilesAerial 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 DocumentsOffice automation: presentations, spreadsheets, web pages, and so
forth.
1-17
1-18
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.
Start Here
Features can be represented in the GIS as points, lines, polylines, areas, arcs, text, and
images.
Queries and Spatial QueriesQueries 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
containing cities where the total crime rate is greater than 125. Spatial queries supplement
relational operators with spatial operators.
GIS Applications
A GIS can be productively used in many endeavors, including the following:
1-20
Agriculture
Business
Cartography
Meteorology
Geology
Tourism
Education
Archeology
Facilities Management
Asset Management
Environmental Management
Utilities Management (water and sewer, electric, communication systems, cable, cell
phone coverage areas, and so forth)
State and local government Land Information Systems (LIS): parcels, right-of-way,
and so forth.
Start Here
Benefits of GIS
Some of the benefits of using a GIS are the following:
Reduces Operations and Maintenance CostsAs 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 EffectivenessA 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 AidsEffective 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 HarmonyBy providing a standard set of data and tools for modeling and
analysis, major alternatives for a project can be consistently produced and analyzed. This
capability helps bring teams together with the increased job satisfaction associated with the
feeling of effective group participation.
Provides a Repository of Institutional KnowledgeBy incorporating as much
knowledge as possible into standard GIS functions, the loss of key personnel knowledge
can be minimized.
1-21
1-22
Creating a GeoWorkspace
You create a GeoWorkspace using normal.gwt or another template in the \GeoMedia
Professional\Templates\GeoWorkspace folder. The available templates are displayed
when you select File > New GeoWorkspace from the GeoMedia Professional menu or
Create new GeoWorkspace using from the introductory GeoMedia Professional dialog
box.
2-1
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 Professional 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
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 reexecuted. 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.
2-4
To save changes to a GeoWorkspace any time during a session, select File > Save
GeoWorkspace. This saves but does not close the GeoWorkspace.
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.
E-Mailing a GeoWorkspace
When you select File > Send from the GeoMedia Professional 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
2-6
2-7
2-8
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 earths 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:
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 unitFor 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 Professional 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 Professional is telling you when it says
you have a horizontal resolution of 0.001 ft. (1 ft./1000 UORs). GeoMedia Professional 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 Professional 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 whateverwhole units, usually).
3-4
Likewise, data in GeoMedia Professional'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 unitFor 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 unitFor 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 centerThis 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 Professional 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.
Storage center
See the "Coordinate System Information" appendix for the settings available in the
software.
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 (nonstandard) ellipsoid, you can change ellipsoid parameters as well.
7. Optional: On the Geographic Space tab, select the vertical datum from the Vertical
datum drop-down list.
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.
Storage center
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.
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.
5. 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 resets 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).
6. 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.
7. Optional: On the Geographic Space tab, select the geodetic datum from the Geodetic
datum drop-down list.
8. 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 (nonstandard) ellipsoid, you can change ellipsoid parameters as well.
3-8
9. Optional: On the Geographic Space tab, select the vertical datum from the Vertical
datum drop-down list.
Note: Changing the coordinate system type from Projection or Geographic to
Geocentric resets the vertical datum to Ellipsoid (geometric).
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.
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.
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:
Clear coordinates after enter (this option applies to precision keyins, not to precision
readouts)
See the Precision Coordinates Help topic in GeoMedia Professional Help for complete
information.
3-12
These are the options you can set on the Units and Formats tab:
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.
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.
Measurement interpretation specifies how Earth curvature and nominal map scale
are accounted for in measurements and coordinate calculations.
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.
3-13
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.
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.
3-14
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.
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.
When you make changes to the autodt.ini file, they do not affect any GeoMedia
Professional or GeoMedia Professional 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 Professional
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.
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 resets 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.
5. Optional: To change parameters, click Projection Parameters. Depending on the
projection algorithm selected, some text boxes may be read-only.
6. Optional: On the Geographic Space tab, select the geodetic datum from the Geodetic
datum drop-down list.
7. 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 (nonstandard) ellipsoid, you can change ellipsoid parameters as well.
8. Optional: On the Geographic Space tab, select the vertical datum from the Vertical
datum drop-down list.
Note: Changing the coordinate system type from Projection or Geographic to
Geocentric resets the vertical datum to Ellipsoid (geometric).
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:
3-16
The folder containing the specific warehouse for which the coordinate-system file
defines coordinate data. This is the preferred location.
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 coordinatesystem file.
13. Verify that the Save as type is set to Coordinate System File (*.csf).
14. Click Save.
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
3-19
3-20
4-1
Note: Access-based warehouses, catalogs, and libraries all use *.mdb files. You should
maintain these in separate directories 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 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.
This version of the software lets you connect to data created in the following formats:
Access
ARC/INFO
ArcView shapefile
CAD AutoCAD and MicroStation/IGDS
FRAMME
GeoGraphics
GML (Geography Markup Language)
I/CAD MAP
MapInfo
Modular GIS Environment (MGE)
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.
See the Working with Map Windows and Working with Data Windows chapters for
more information.
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 softwareto add new features or change
attributes of existing ones, for exampleyou 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.
4-2
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.
If you plan to use multiple coordinate systems in your Access warehouse, you need to
assign one coordinate system to use as the default through Database Utilities or through
the Features Definition command.
When digitizing in GeoMedia Professional, 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 Professional 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.
4-4
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.
A coordinate-system file (.csf) for the ARC/INFO data must be created with Define
Coordinate System File.
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.
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.
4-5
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.
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 Professional Help.
.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 Professional 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 Creating Data Server .INI Files topic in GeoMedia Professional Help.
See the Define CAD Server Schema File utilitys online Help for complete information
about this utility.
See the Creating Data Server .INI Files topic in GeoMedia Professional Help.
Type
2
Name
Cell (named)
2
2
3
Cell (orphaned)
Cell (unnamed)
Line
4
6
7
11
12
14
15
16
LineString
Shape
TextNode
Curve
Complex String
Complex Shape
Ellipse
Arc
17
22
35
Text
Point
Shared Cell
See the Creating Data Server .INI Files topic in GeoMedia Professional Help
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.
Abort the connection and report an error about the missing coordinate system
file.
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 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.
Swap the coordinate order for the following coordinate system types: Geographic
and Projected.
You must replace the parts enclosed by angle brackets (< >) with appropriate values. The
following example (VB code snippet) illustrates usage of GeoMedias 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
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
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.
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 Professional Help.
4-10
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
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.
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 Microsofts
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.
4-11
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 Professional. 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.
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.
4-12
User name.
Password.
Host string. The host string is the Oracle database alias/service name that you create
with the Oracle network configuration utility.
OR
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.
4-13
WFS URL
Advanced options:
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.
file.
o
Swap the coordinate order for the following coordinate system types: Geographic
and Projected.
4-14
Advanced options:
file.
Closed
Open read-write
No action status
remains unchanged.
Open read-only
N/A
read-write:
No action status
remains unchanged.
No action status
remains unchanged.
Open read-write
No action status
remains unchanged.
No action status
remains unchanged.
Open read-only
Open read-write
Open read-only
Open read-only
Open read-only
Closed
Open read-write
Open read-only
Closed
N/A
Closed
Closed
No action status
remains unchanged.
N/A
Closed
Closed
No action status
remains unchanged.
Open read-write
Open read-only
Open Read-Only
Closed
Open read-write
Open read-only
Reopen Connection
Close Connection
read-only:
N/A
No action status
remains unchanged.
Open read-only
N/A
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
4-16
4-17
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.
2.
Click New to display the New Connections dialog box; then follow the previously
described procedure to create a new warehouse connection.
4-18
7. Click Save.
4-20
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.
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):
GPickListTable
Column Name
FeatureName
FieldName
PickListTableName
ValueFieldName
DescriptionFieldName
FilterClause
Datatype
Varchar(255)
Varchar(255)
Varchar(255)
Varchar(255)
Varchar(255)
Varchar(255)
4-21
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.
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 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.
The following is an example of tables, columns, and values that could be defined for
PickLists:
GAliasTable
TableType
INGRPickLists
TableName
GPickListTable
GPickListTable
FeatureName
FieldName
PickListTableName
Buildings
Buildings
Buildings
Name
PL_Building
State
PL_State
Type
PL_Building
DescriptionFieldName
ValDescription
Desc
ValDescription
4-22
ValueField
Name
CodeValue
StateName
CodeValue
FliterClause
Bld_Type =
'NAME'
Bld_Type =
'TYPE'
PL_Building
CodeValue
0
1
2
3
ValDescription
MOTEL
MARRIOT
HOLIDAY INN
BED AND BREAKFAST
Bld_Type
TYPE
NAME
NAME
TYPE
PL_State
StateName
Alabama
Arkansas
Colorado
Texas
Florida
Desc
ALABAMA
ARKANSAS
COLORADO
TEXAS
FLORIDA
4-23
4-24
5-1
Automatic (the default) lets the command choose the georeference mode based on the
images you select.
USGS DOQ
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 Professional.
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
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.
5-3
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.
5-4
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 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.
4. 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.
5. Optional: In the Extensions field, type or select from the drop-down list a new
extension to change the default *.*. You can specify multiple extensions, separated by
a semicolon (*.tif;*.bmp).
If you enter a new extension, the Available files list is updated accordingly, and any
selected image files are unselected.
6. 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.
7. From the Warehouse drop-down list, select the read-write warehouse where you want
to store the path to the image.
5-5
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.
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 appropriate.
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.
that GeoMedia Professional 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,
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 Professional, 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).
5-7
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
cannot, however, update multiple images entries that contain both filenames and XML
monikers, nor single or multiple XML monikers, which are always valid. GeoMedia
Professional 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.
All image records of the selected image feature class are displayed in the Images list.
5-9
3. To display selected images, select the valid image record(s) from the Images list; then
click Display.
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.
5-10
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. Click Close.
To delete an image feature class with Warehouse > Feature Class Definition:
1. Select 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.
5-11
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.
5-12
Translucency percentageThe degree to which the image is to be translucent or seethrough, with 0% indicating totally opaque and 100% indicating totally transparent. It is
applicable to all image types.
ContrastThe 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.
BrightnessThe 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 ImageIndicates 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 colorA 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 valuesA 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 colorThe color with which the foreground pixels of a binary image
are to be displayed, applicable only to binary images.
Binary background colorThe 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.
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.
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.
SeeDisplaying Selected Images in the next section in this chapter.
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.
7. Optional: Click Style, and change the default style on the Select Style dialog box.
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
5-17
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
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.
5-18
6-1
Depending on the current state of the map window, this menu lets you do the following:
The GeoMedia Professional 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.
6-2
View at current scale (the defaultFeatures in the select set are highlighted, but the
map window does not shift or change scale.)
Center at current scaleFeatures in the select set are highlighted and centered in the
map view, but the map window does not change scale.
Fit and zoom outFeatures 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
This command lets you define the following properties that affect the way the map
graphics are displayed:
Display scaleTypically 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 scaleTypically 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 angleRotation 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.
UnitsAngular units. Changing the units converts the rotation value to the new units.
Set style scaling for all legend entries toLegend entry display in the map window.
View (size is true at any display scale)The styles on all legend entries are displayscale 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:
6-6
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.
Zoom Out
Zoom
Previous
Zoom to
Nominal
Map Scale
Fit All
Fit Select
Set
Note: This command generates expected results only when the selected features are
within the defined display scale range of the legend entry.
Update
All
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
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.
6-8
Display priority. Which map objects are displayed on top of other map objects?
Locatability. Can the map object be selected or highlighted in the map window?
Cut/Copy selected multiple legend entries; all are inserted consecutively at the drop
point.
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.
6-9
See the Working with Legends section later in this chapter for information.
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
6-10
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.
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.
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.
6-13
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 Professional Help topics for complete description of the
styles, their parameters, and how they are defined.
Picture StyleThis 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:
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 StyleThis 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 textrendering techniques. These techniques do not, however, recognize MicroStationproprietary font resource files. Thus, such files must be converted into a format
6-14
Predefined symbolsA 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.
MicroStation Cell Files (*.cel)This is a multi-symbol type. With this type, it is not
necessary to convert cell files into .fsm format.
Scalable Vector Graphics (SVG) Files (*.svg)This is an industry standard, multisymbol 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 rotationWhen 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 orientationWhen 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.
Simple Line StyleThis 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 StyleThis 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 lines characteristics, and a Pattern Line Style to define the point styles
characteristics.
Simple Fill StyleThis 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 StyleThis 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 StyleThis 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:
ClipCauses each patterned point element to be clipped to the boundary of the area.
InsideDraws each patterned point element only if the entire element falls within the
boundary of the area.
Text StyleThis 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 rotationWhen 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 orientationWhen unchecked, the text will rotate based on the
orientation of the features geometry. When checked, the text will not rotate,
maintaining the rotation angle specified for the text style.
Image StyleThis 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 StyleThis 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:
BoundariesA collection of zero or more line style types to use in drawing the
boundary of the geometry.
FillsA collection of zero or more fill style types to use in drawing the interior of the
geometry.
No boundary
The following is an examples of area style usage for interior boundary tints:
6-18
Compound StyleThis 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:
PointsZero or more point style types to use in drawing the point geometries.
LinesZero or more line style types to use in drawing the line geometries.
AreasZero or more area style types to use in drawing the area geometries.
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.
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:
6-20
Order by featureThis 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 styleThis 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
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 componentThis 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 StylePermits manipulation of the color and size of all point styles.
Line Collection StylePermits manipulation of the color and width of a simple line style.
Fill Collection StylePermits manipulation of the fill color and translucency percentage.
Area Collection StylePermits 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 StylePermits manipulation of the following:
Boundary/line color and width of the line style(s) associated with the boundary/line.
Text Collection StylePermits the manipulation of the font, size, font style characteristics
(bold, italic, underline), and color.
Image StyleCollections are not supported for this style class. However, the common
controls permit the manipulation of translucency percentage, contrast, and brightness.
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, GeoMedias
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 a dash length that is less than the line widthBecause 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.
Rename styles
Preview styles
Delete styles
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:
DetailsStyles 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.
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.
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 Professional Help topics for complete information on
these two dialog boxes.
See the corresponding GeoMedia Professional 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 Professional 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 attributebased 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:
PropertyRead-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 ValueRead-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 BasedEmpty 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 nonnull 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 Professional
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
6-27
Attribute. An expression can be built to construct the appropriate syntax required for the
Source property as follows:
CONCATENATE(";","Symbol file name",Attribute)
Symbol file name = "C:\Program Files\GeoMedia Professional\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.
AnimationAnimating styles draws attention to critical features or situations as attribute
values change. Animation is more than attribute-based symbology; a change in the value
6-28
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, clicking 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
See the corresponding GeoMedia Professional Help topic for complete information on this
dialog box. And, for more information on styles, see the Style Types in this section.
6-30
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.
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 Professional symbol file, copy the MicroStation design-file
color table used when creating the cells to <drive>:\Program Files\GeoMedia
Professional\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 Professional\Program\Symtrans\font.rsc, and update
the same location in MS Resource files entry under the [Options] section of
<drive>:\Program Files\GeoMedia Professional\Program\Symtrans\DGNGT2D.ini.
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.
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.
Click Insert.
Click Close.
A title bar.
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.
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.
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.
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.
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.
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
6-38
Object Type
Point feature class
Linear feature class
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 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.
From the GeoMedia Professional menu, select View > Legend. A checkmark next to
Legend on the menu indicates that the legend display is turned on.
6-39
From the GeoMedia Professional menu, select View, and deselect Legend.
Double click the legend icon or the X on the legend title bar, if it is displayed.
Queries (Legend > Legend Entries or Analysis > Queries > Display, and most other
Analysis commands)
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.
6-40
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.
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.
6-41
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
individual features within each group by choosing the appropriate feature within each
node.
See the Style Properties and Select Style dialog box topics in GeoMedia Professional 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 twolevel 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.
In defining this legend entry style, you can:
6-44
View unique values, corresponding labels (entry title), styles, and record counts.
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
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.
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 CountDistributes the same number of records to each range. The range
values automatically adjust to distribute the records evenly.
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
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.
Top Grid
The columns in the top grid for range and unique values legend entry styles are populated
as follows:
Check boxSets 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.
StyleDisplays 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.
ValuesThese 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 ValueRepresent 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.
ValueDisplays 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).
LabelDisplays 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.
CountDisplays 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 ColorsRamps the colors from top selected item to the bottom selected item.
Ramp Size/WidthRamps the size or width from the top selected item to the bottom
selected item.
Select StyleDisplays the Select Style dialog box, which lets you select or edit the style.
DeleteDeletes 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.
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.
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.
6-53
If you select Equal Range, type appropriate values in the Begin value and/or End
value fields.
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.
4. From the Thematic classes frame, select the appropriate Attribute for classification
from the drop-down list.
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.
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.
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.
6-56
To edit the style of a map object, double click the style key on its legend entry.
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).
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.
6-57
6-58
From the GeoMedia Professional menu, select Legend > Fit Legend.
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:
1. Select Legend > Legends.
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.
1. Select Legend > Legends.
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.
1. Select Legend > Legends.
6-60
2. Select the legend that you want to append on the Legends dialog box.
3. Click Append.
To delete a legend:
1. Select Legend > Legends.
2. Select the legend that you want to delete on the Legends dialog box.
3. Click Delete.
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
Display Scale
Range
Displays the Scale Range dialog box to set a scale range for map objects.
6-61
Option
Does this
Locatable On
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
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
Entries
Opens the Show Legend Entries dialog box to display selected legend
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
ToolTip
Specifies the map window tooltip of the selected legend entry to None
(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 Functional Attribute dialog
box to edit the tooltip).
Paste
Pastes the legend entries from the clipboard Into, Before, or After the
selected legend entry.
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
selected legend entry.
Add
Opens the Add Legend Entries dialog box to add legend entries into the
legend.
Fit by Legend
Entry
Fits the contents of the selected legend entries to the map window.
Legend Entry
Properties
Opens the Legend Entry Properties dialog box to set the properties of the
selected legend entry.
Fit Legend
6-62
Properties
Opens the Legend Properties dialog box to set the properties of the
legend.
NameSets 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.
6-63
ExpressionOpens the Functional Attribute 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.
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.
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.
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
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
Professional\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 Professional\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.
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.
Double Block
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 onefifth 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
The Labels tab lets you specify the appearance of the scale bar numbers and caption and
where they are displayed.
6-69
You can choose from the following fixed interval label locations on the Labels tab:
Every interval
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.
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.
6-70
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. 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.
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
Professional 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).
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.
6-71
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.
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.
6-72
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
following figures. Nothing is displayed when you place the mouse on the intersection
point of the two line segments.
6-73
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
6-75
6. On the General tab, select the CAD type from the drop-down list.
7. In the Folder field, type the complete path of the folder containing the CAD files, or
use Browse to locate the folder.
8. From the Available files list, select one or more files you want to display.
9. 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.
10. 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.
11. 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.
12. Optional: In the Connection name field, change the default connection name.
13. 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.
14. 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.
15. 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.
16. Click OK.
6-76
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 utilitys online Help.
6-77
6-78
7-1
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.
7-2
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:
In addition, the GeoMedia Professional 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.
2. On the Data Window Properties dialog box, type a new title in the Data window
name field.
3. Click OK.
7-3
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.
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 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.
7-4
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.
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.
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.
7-6
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 require an invalid data conversion, such as trying to paste a text string
containing letters into a numeric field.
7-7
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
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.
You can paste the snapshot into any application that supports OLE, such as Word,
MSPaint, or an HTML Web page.
7-8
By removing attributes
By changing attributes
In a read-write warehouse, you can also manage feature data in the following ways:
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.
8-2
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
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 GeoMedias 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
Gmodifications
GmodifiedTables
INGRSQLOperatorsTable
INGRFeatures
INGRGeometryProperties
INGRAttributeProperties
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
AVG
DATE
FLOAT
INTO
NOT
ROLLBACK
TIME
WHERE
ALL
BETWEEN
DELETE
FROM
IS
NULL
SELECT
TIMESTAMP
WITH
AND
BY
DESC
GROUP
LIKE
ON
SET
UNION
TO_DATE
ANY
COMMIT
DISTINCT
HAVING
MAX
OR
SOME
UPDATE
TO_CHAR
ASC
COUNT
EXISTS
ININSERT
MIN
ORDER
SUM
VALUES
TO_NUMBER
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
Professional 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.
Note: Editing an existing Oracle feature class definition is an Oracle administrative task
and is, therefore, not allowed in the GeoMedia Professional Feature Class Definition tool.
Output single and multiple feature classes, queries, categories, and reference features
Output selected fields from a feature class, query, category, or reference feature
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.
8-10
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
8-11
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.
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.
NewNew data.
Append and UpdateAppends new records and updates existing records based on
primary key value.
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).
The default is Preserve Key if the source has a displayable primary key, otherwise it is
New Key. 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 DefinitionPreserves 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. See the
table in the next section for the default column values.
8-12
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. See the table in the next section
for the default column values.
Default value
New
Preserve Key if the source has a displayable primary key, otherwise
New Key
AutoNumber
Preserve Definition and Values (PD&V) if the target warehouse
supports this capability, for example, OOM.
Mode
Preserve Values if the target warehouse does not support PD&V, and
the key mode is New Key.
Preserve Definition if the 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.
8-13
Column Name
Output Mode
Key Mode
AutoNumber
Target Coord
System
Default value
Append
N/A (blank)
N/A (blank)
Primary geometry's coordinate system of the target feature class of the
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.
Additional Options
Below the Output settings grid on the Advanced tab, you have the following two options:
Select Source AttributesOpens 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 SystemOpens a dialog box of the same name that lets you
perform the following:
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.
At the bottom of the dialog box, you have the following option:
Display target feature classes in map windowLets you select whether to add the
legend entries (the default) for the selected feature classes or to not add the legend
entries.
While processing, the application status bar displays the output feature class/query,
target feature class, progress, and number of features output.
8-14
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.
2. On the General tab, select the appropriate items from the Source features to output
treeview.
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.
8-15
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.
See the GeoMedia Professional 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.
8-16
See the Target Coord System and the Select Coordinate System topics in the
GeoMedia Professional 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.
11. Optional: Check the Display target feature classes in map window check box to add
the legend entries for the selected feature classes.
12. 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?
13. 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.
8-17
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).
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.
8-18
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.
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.
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.
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.
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.
8-20
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.
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.
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.
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
schema apparent. Queries resulting from other GeoMedia Professional 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.
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
8-22
results.
OR
To not display the query results in a map window, click the Display query in map
window box to remove the checkmark.
6. Optional: Click Style, and change the default style on the Select Style dialog box.
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 Professional Data chapter for information on queries.
Collecting Data
GeoMedia Professional supports several methods of collecting data. You can digitize
features directly on screen, digitize features using a digitizing table, digitize features onscreen off a scanned image, or enter features using precision keyins plus coordinate
geometry input.
In addition, you can bring in data from outside sources using GeoMedia Professionals
import capabilities, and you can bulk create features from existing linework. You may also
want to collect the geometry first and populate the attribute information later, or vice versa.
Alternatively, you may want to collect attribute information as you digitize a feature.
GeoMedia Professional supports all of these workflows. This section describes the tools
and capabilities available to address these workflows. It begins with a description of
specialized productivity tools that are common to multiple placement and edit commands.
SmartSnap
Coincidence
Default Height
There are two ways to specify the default height during any placement and editing
operations. On the Placement and Editing tab, you can type the height value into the
Default height value field. Alternatively, you can select View > Default Height to open
the Default Height dockable control whose value is taken from the Placement and
Editing tab.
You can type a different height value, and press ENTER or click in the map window to set
the value. The dockable control provides more ease of use while you are doing placement
or editing operations The units on the tab and the dockable control box are taken from the
height unit type on the Units and Formats tab of the Define Coordinate System File
dialog box.
See the Define Coordinate System File utilitys online Help.
8-24
SmartSnap
As you digitize and move the cursor within a tolerance distance of locatable features in the
map window, a glyph is displayed on the cursor. (The glyph is the same as the symbol on
the corresponding SmartSnap button on the SmartSnap toolbar.) If you click to a place a
vertex when the glyph is displayed, that vertex will be automatically snapped to the feature
based on the type of SmartSnap glyph that was displayed (example shows vector snap
glyphs only).
Rapid digitizing by removing the need to set snaps, to tentative click, or to check
connectivity after snapping.
Correct connectivity, thus greatly reducing the number of digitizing errors, such as
undershoots and overshoots. In this way, the data is collected cleanly and require little
or no post-collection cleanup.
GeoMedia Professional provides both vector and raster snaps for simple digitizing and for
digitizing over an image. Raster snaps speed up digitizing over an image by reducing the
need for constant zooming in and out and panning, which is typically necessary in this kind
of data capture. The automatic visual display of potential snap points allows you to zoom
out farther and work on a larger area.
The SmartSnap toolbar contains buttons that allow you to turn vector and raster snaps on
and off as you work. Individual snaps can be turned on and off anytime a map window is
active, but the settings apply only to placement tools, such as Insert Feature, and to
editing tools, such as Edit Geometry and Continue Geometry.
The vector snap and raster snap icons on the SmartSnap toolbar are the following:
Vector Snaps
All vector snaps are on by default.
Intersection SnapDisplayed when the cursor is within the locate tolerance of
the intersection point of two geometries.
8-25
End Point SnapDisplayed when the cursor is within the locate tolerance of an
end point of a line feature.
Vertex SnapDisplayed when the cursor is within the locate tolerance of a
vertex of a line or area feature.
On Element SnapDisplayed when the cursor is within the locate tolerance of
any point on a line or area feature.
Origin SnapDisplayed when the cursor is within the locate tolerance of the
origin point of a text object or a symbol.
Midpoint SnapDisplayed when the cursor is within the locate tolerance of the
midpoint of a single segment in a line or area feature.
Tangent SnapLets you create a snap point that is tangent to an existing arc
segment.
Perpendicular SnapLets you create a snap point that is perpendicular to an
existing arc or line segment.
Raster Snaps
All raster snaps are turned off by default. To use raster snaps, the raster image must be in
binary format.
Intersection SnapDisplayed when the cursor is within the locate tolerance of
the intersection point of two geometries.
End of Line SnapDisplayed when the cursor is within the locate tolerance of
the end of a raster line.
Corner SnapDisplayed when the cursor is within the locate tolerance of a
corner. A corner is the point where a raster line changes direction abruptly at an
angle close to 90 degrees. (The farther from 90 degrees the angle is, the less
likely a corner snap will find it.)
Open Symbol SnapAn open symbol refers to an unfilled circle. When you
click within the open symbol snap tolerance, a point is placed in the center of the
circle.
Closed Symbol SnapA closed symbol refers to a filled circle. When you click
within the closed symbol snap tolerance, a point is placed in the center of the
circle.
Center SnapDisplayed when the cursor is within the locate tolerance of the
center of a raster line. A point is placed at the center of the raster line.
See the Raster Information appendix for supported formats.
Setting Tolerances
Snap tolerances are set by using SmartSnap Tolerances. You can define tolerances for
the snap zone, the noise size, the open symbol size, and the closed symbol size.
8-26
The search distance tolerance for raster and vector snaps is set using Locate zone. The
distance is measured in pixels. Clicking Locate zone opens the Options dialog box with
the SmartLocate tab selected.
Note: This is the same setting that defines the locate zone when highlighting or selecting
features. Changing the Locate Zone setting when defining snap tolerances changes the
locate zone used when highlighting or selecting features.
The size of small raster elements to be ignored when snapping to raster data is set using
Noise size. To determine the tolerance, you should measure across any pieces of raster
data considered to be noise. The tolerance is measured in the defined GeoWorkspace
distance units (as defined on the Units and Formats tab of the Define Coordinate System
File dialog box). For example, when the tolerance is set to a value that is equivalent to two
pixels, any isolated clump of raster data that is less than or equal to two pixels wide will be
ignored during snapping.
The size of raster symbols that contain holes (for example, a circle) is set using Open
symbol size. A raster image can have multiple open symbols of varying sizes. The size is
defined by a minimum and a maximum tolerance. The minimum value is the smallest size
of the holes of open symbols that SmartSnap detects. The maximum value is the largest
size. Both values are measured in GeoWorkspace distance units.
The size of closed (solid) raster symbols is set using Closed symbol size. A raster image
can have multiple closed symbols of varying sizes. The size is defined by a minimum and
a maximum tolerance. The minimum value is the smallest size of closed symbols that
SmartSnap detects. The maximum value is the largest size. Both values are measured in
GeoWorkspace distance units.
Note: Measuring slightly smaller and slightly larger than the actual hole for the open
symbols allows for variations in the raster symbols and improves the software's ability to
locate the symbol. The same applies when measuring the size of closed (solid) raster
symbols.
8-27
You can set the snap zone by clicking Locate zone and then by using the Size of cursor
locate zone slider on the SmartLocate tab of the Options dialog box to define the size of
the snap zone.
You type the tolerance values for Noise size, Open symbol size, and Closed symbol size.
Or you can click the corresponding Define button to set the tolerances interactively by
clicking two points in the map view.
The units are set on the Units and Formats tab of the Define Coordinate System File
dialog box, which you can change appropriately.
Note: When digitizing a new feature or using any other placement or editing tool, you can
turn snapping on and off as necessary using the icons on the SmartSnap toolbar. For
example, you can snap to vector end points and vertices and to raster intersections and line
ends. You can also turn the automatic display of the Properties dialog box on and off, and
you can set other placement options by using the Placement and Editing tab of the
Options dialog box.
See the "SmartSnap" and "Using the Placement and Editing Tab" sections in this chapter.
8-28
This option allows you to click two points along the existing feature to copy all the vertices
between those two points to the new feature.
The Use existing geometry when digitizing option affects the following tools when you
create new features or edit existing features:
Geometry >
Continue
Edit >
Redigitize
Insert >
Feature
Note: This option also applies when digitizing with offset.
This option is on by default, but you can turn it off on either the Placement and Editing
tab of the Options dialog box or on the Options toolbar.
The following examples illustrate the use of this option:
Using existing geometry to place a new feature:
Turning off Using existing geometry when digitizing from the toolbar has the following
result:
This is an example workflow used to add an adjacent feature to the following figure:
8-29
3. Place the second point of the feature, and the point snaps to geometry according to the
snap type displayed.
4. Move the cursor to another location on the geometry that has just been snapped to, and
the geometry is highlighted.
5. Click the third point along the geometry, and the geometry between the last two points
is duplicated on the feature being placed.
Maintaining Coincidence
Coincidence refers to the relationship of features to each other, whether it be a connectivity
relationship such as Feature 1 connecting to Feature 2 or a spatial equality relationship in
which two features share common geometry.
In the following two cases, the features share common vertices:
If this relationship is broken, errors will be introduced into your spatial database, and you
have to spend time cleaning them up.
Sliver Polygon
Gap Polygon
8-30
Undershoots
Overshoots
In traditional GIS systems the relationship can easily be broken when placing and editing
features, for example, if you do not snap in correctly when digitizing, or if you edit
features in one layer and do not edit common boundaries in a second layer. GeoMedia
Professional makes it easy to maintain these relationships by implementing SmartSnap and
the automatic maintenance of coincidence throughout the placement and editing
commands. This means that when you edit a common boundary, all boundaries are edited
simultaneously or if you move a vertex that is connected to another feature, all connected
features are edited.
This behavior is optional and is controlled by the Maintain coincidence check box on the
Placement and Editing tab of the Options dialog box or through the Maintain
Coincidence option on the Options toolbar.
by selecting the Segment arcs when inserting vertex check box on the Options dialog
box.
If both Maintain coincidence and Segment arcs when inserting vertex are turned on,
snapping to an arc divides the arc into two parts at the snapped point. The arcs are still part
of the original feature; they are not split. The composite feature (a single feature
containing more than one piece of geometry) formed by the two new arcs replaces the
original arc.
If Maintain coincidence is turned on but Segment arcs when inserting vertex is turned
off, snapping to an arc opens a dialog box with the following message:
A vertex cannot be inserted in an arc geometry without converting it into a composite
geometry consisting of two arcs. Do you want to convert the current arc?
Click Yes or No. Clicking Yes divides the arc as previously described. Clicking No
results in the arcs not being divided nor made coincident.
Note: If Maintain coincidence or Segment arcs when inserting vertex is turned off, this
dialog box opens every time you snap to an arc. To stop the dialog box from opening,
select the Do not display this message again check box.
If Maintain coincidence is turned off, the Segment arcs when inserting vertex option is
disabled, and arcs are not divided nor made coincident.
If intersecting features do not have vertices at the intersection (because they were not
snapped when digitized, or because they were collected in another software package and
imported into GeoMedia Professional), you can use Insert Intersection to insert a vertex,
or you can use Edit Geometry to add a vertex. If Maintain coincidence is on when you
add a vertex, a vertex is also added at coincident features. If several intersections exist
without vertices, you can use Validate Geometry to locate all non-coincident intersecting
features, and then you can use Insert Intersection to connect them.
8-32
Note: You can find unbroken intersecting lines by using Validate Connectivity, and then
you can fix them by using Insert Intersection with the Break linear features option
turned on or by using Fix Connectivity.
When the Break linear features is turned on, you have two options for breaking linear
features: Break same feature class only and Break all feature classes.
Break same feature class only determines whether the break capability breaks all linear
features coincident at the snap point or just those belonging to the same feature class as the
feature being edited. When this option is turned on, any placement or edit operation that
involves snapping to another feature only breaks features in the same feature class as the
feature being edited.
Break all feature classes determines whether the break capability breaks all linear features
coincident at the snap point or just those belonging to the same feature class as the feature
being edited. When this option is turned on, any placement or edit operation that involves
snapping to another feature breaks features in all feature classes at the snap point.
The Break linear features option affects the following tools:
Geometry > Edit (only on end point vertex edit)
Edit >
Continue
Redigitize
Trim
Trim to Intersection
Extend
Extend to Intersection
Construct Circular Fillet
Insert Intersection
Insert >
Feature (including digitizing with offset)
Break Conditions
The Break linear features capability:
Must snap to the feature to be broken. All snaps are valid, but the type of snap and
type of geometry snapped to will modify the behavior of a break.
Breaks all coincident features, that is, they do not have to be in the select set.
Result: No break occurs, regardless of the current break setting. A break only occurs on a
snap.
Case 2: Area breaking.
Setting: Break all feature classes.
Result: The operation places a vertex at the snap point on the area geometry. The area
features cannot be broken.
Note: An area feature can break a linear feature, but a linear feature cannot break an area
feature.
Case 3: Break between coincident line features.
Setting: Break same feature class.
Results: All coincident features are broken at the snap point, not just the Highway feature.
8-34
Solution: Lines A and B are broken at the snap point, regardless of the coincidence setting.
Case 2: Snapping to coincident features B.
Break: In same feature class only.
Coincidence: On
Solution: Line B is broken into two features at the snap point because it is the same feature
class as line C. Line A is a different feature class, and because the setting is to break
within a single feature class only, it is not broken. Line A, however, is split with a vertex
at the snap point.
Note: You can control which features get broken or which features have a vertex inserted
into them by turning locatability on/off for a specific feature class. For example, suppose
you have Break all feature classes turned on, but you do not want road features to break
river features. To prevent roads from breaking rivers, select the rivers legend entry, click
the right mouse button, and select Locatable. (A menu item is deselected when the
checkmark disappears.) Also note that each time you place a feature with Break linear
features turned on, the Properties dialog box displays if you turned on Display
Properties dialog box for new features on the Placement and Editing tab of the
Options dialog box, or if there are required values. This is because you are creating a new
feature.
If, however, you used Move to move several features in a select set, multiple database
changes would occur (the change of the geometry of every feature instance in the select
set). In this case, using Undo once moves all the features back to their original locations.
Because Undo can store multiple operations, you can use this command repeatedly until all
operations have been undone. For example, using Undo once would undo the last
operation; using Undo a second time would undo the next to the last operation, and so
forth up, to the limit set through the Placement and Editing tab of the Options dialog
box.
You access Undo and Redo from the Edit menu, from their toolbar buttons,
or by pressing CTRL+z and CTRL+y, respectively.
You can use Undo and Redo with the following placement and editing commands in map
and data windows:
Map Window
Insert > Feature
Traverse
Text
Label
Interactive Label
Leader Line
Interactive Area By Face
8-36
Note: The Undo/Redo commands in the layout window pertain to the layout window
graphics commands, which are accessible only when the layout window is the active
window.
You set the Undo and Redo parameters through the Placement and Editing tab of the
Options dialog box. The Undo check box turns Undo and Redo on and off; the default is
on, checked. The Limit undo operations check box lets you set a limit for the number of
operations that you can undo; the default is on, with a value of 5. Turning off this option
makes Undo unlimited, except by your system memory, for the current session.
If any feature class or query that has been edited is closed, the Undo buffer is cleared. The
primary case in which this would happen is when the GeoWorkspace coordinate system is
changed. The Undo buffer can become very large during a long work session and thus
begin to affect software performance, especially if a large number of bulk operations have
been performed, for example, deleting a large number of features. If memory usage or
performance degrades in a long session or after large numbers of database modifications,
you should try reducing the Undo buffer size or turning Undo off and then on again to
clear the buffer.
Note: If autonumber fields are defined for a feature class in an SQL Server or Access
2000 warehouse, using Undo/Redo on features from the feature class causes the
autonumber fields to be incremented in certain cases. The previous autonumber field
values are not be preserved.
Coordinate keyin
Placement of areas with holes, discontiguous feature placement
Placement of line tangent to arc or arc tangent to arc or line
Placement by length
Placement of orthogonal features
These capabilities and others are discussed in detail in the following sections.
To more effectively place features, you can use construction aids, which let you construct a
geometry through a specific method and then use that geometry during placement, without
having to exit and restart the placement or editing command.
See Using Construction Aids later in this chapter for information.
Insert Feature allows you to digitize a new feature and, optionally, to define its attributes.
To do this, you must have a connection to a read-write warehouse. You must also have
created a new feature class and have added a new feature class entry to the legend in your
map window.
You select the appropriate warehouse connection, category, reference feature, or 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. You can select a feature
from a warehouse connection, catalogs, or reference features.
Note: This dockable control is also used by the Continue Geometry and Redigitize
Geometry commands; only the name of the control and its default values are different.
If there is one and only one read-write feature in the select set when you start Insert
Feature, the connection and feature class on the feature selection field are set to match the
feature in the select set. You can also click on a feature in the map window to select
another feature class to place while in the command. The Insert Feature control is
populated with the feature class of the selected feature and the command starts at the
beginning of digitizing a new feature. This saves you time from not having to scroll
through a list of features on the control to get another feature class while in the command.
The geometry types that you can place are point, line, and area. For point, line, and area
features, the geometry type icons only indicate the geometry type of the selected feature
class; all other icons are disabled. For example, suppose you select a feature class that
consists of area features, such as counties. In that case, the geometry type is area, the area
icon is selected, and all three iconspoint, line, and areaare disabled. However, if the
geometry type of the selected feature class is compound (meaning that features of this
8-38
feature class can consist of point, line, or area geometry), all three icons are enabled so that
you can select the geometry type of the feature you want.
For more information on geometry types, see "Understanding Geometry Types in this
chapter.
The Placement Mode drop-down list lets you choose the appropriate placement mode
from those available for the selected feature class.
Selecting the Options button opens the Options dialog box with three accessible tabs:
Placement and Editing, General, and SmartLocate. This provides a convenient way for
you to set up the options for placement and editing inside the Insert Feature command.
GeoMedia Professional lets you enter new features for feature classes that have not been
added to the legend. However, because the legend controls what is displayed in the map
window, these features are not be displayed until you add the legend entry. Setting the
Automatically add legend entries option on the Placement and Editing tab of the
Options dialog box automatically adds a legend entry for a feature class when it does not
exist on the legend, or setting this option turns on the display mode when it is turned off on
an existing entry. This option is set on by default.
See Using the Placement and Editing Tab, Using the General Tab, and Selecting
Features in the Map Window in this chapter for information on these tabs.
Selecting the GeoWorkspace Coordinate System button opens the GeoWorkspace
Coordinate System dialog box. This provides a convenient way for you to set the options
for the GeoWorkspace coordinate system inside the Insert Feature command.
8-39
See Working with Coordinate Systems chapter for information on this dialog box.
8-40
Note: If you are in the middle of placing a feature, pressing ESC results in a prompt to
discard the current feature and to remain in the command. Otherwise, it will terminate
the command. Pressing BACKSPACE lets you back up one line.
9. Double click the left mouse button to end the feature.
Note: You can also end a feature by selecting End Feature on the right mouse menu.
10. Place the next feature. The command remains active until you press ESC or click the
Select Tool button on the main toolbar; thus you can continue placing features without
having to re-execute the command.
Note: When using Insert Feature, Continue Geometry, or Redigitize Geometry,
use the back arrow key to sequentially remove previously placed points.
Placement Modes
The previous insert feature workflow showed a simple capture workflow. The following
section describes additional placement modes for digitizing features.
You can easily switch between the placement modes by using the drop-down list on the
Insert Feature dockable control or by using keyboard shortcut keys. In this way, you can
create features containing polyline geometry, arcs, and/or angle constraints. The placement
modes are as follows:
Arc by centerPlaces arc geometry by specifying the arc center and other arc parameters,
radius and sweep angle. When you select this mode, the Arc Placement dockable control
appears for you to type specific arc placement parameters. (Shortcut key C)
Arc by start, end, point on edgePlaces arc geometry by entry in the following order:
the arc start point, the arc end point, and a point along the arc. When you select this mode,
the Arc by start, end, point on edge dockable control appears for you to type specific arc
placement parameters. (Shortcut key A)
8-41
Arc by start, point on edge, endPlaces arc geometry by entry in the following order:
the arc start point, a point along the arc, and the arc end point. When you select this mode,
the Arc by Start, Point on Edge, End dockable control appears for you to type specific
arc placement parameters. (Shortcut key R)
Orient to GeometryWhen selected, snapping to a feature places the point rotated to the
same direction of the feature that it is snapped to. If no geometry is snapped to, the
placement is at zero-degrees rotation. When you digitize a symbol in this mode, the
symbol appears dynamically before it is placed. You can reverse the direction of the point
by pressing TAB. (Shortcut key SHIFT+G)
Place at anglePlaces polyline geometry by placing each point at a user-specified angle,
depending on cursor location, relative to the last segment placed by digitizing in this mode.
If the previous geometry is an arc, the previous segment is considered to be that tangent to
the arc at the arc end point. By default, this is the active rotation mode, and the active
angle is zero degrees. When you select this mode, the Place Point at Angle dockable
control appears for you to type the specific angle value. (Shortcut key SHIFT+A)
8-42
Point by PointPlaces lines and area features one vertex at a time, resulting in a single
feature with multiple vertices. You can also use this mode for placing individual point
features. (Shortcut key L)
Rotate dynamicallyPlaces a point with two clicks in the map window. The first click
displays a temporary feature and a dynamic crosshair that you move to define the rotation
angle. When the feature is displayed at the appropriate angle, a second click places the
feature. (Shortcut key SHIFT+R)
Two-point linePlaces a two-point line feature using two clicks without having to double
click to end the line. In this mode, after placing a feature with two clicks, you can continue
to place additional features with subsequent pairs of clicks. Each instance placed in this
mode is not necessarily contiguous with the previous instance placed. (Shortcut key W)
Consecutive two-point linePlaces consecutive two-point line strings where each click
after the first click results in a new instance of a feature being created with a two-point line.
In this mode, the first two clicks create an instance of a feature, and each subsequent click
creates a new feature that is contiguous with the previous feature (that is, the start point of
the feature is coincident with the end point of the previous feature placed). (Shortcut key
V)
See the corresponding GeoMedia Professional Help topics for a complete information on
the placement mode dockable controls and workflows.
The following are several example workflows for using the placement modes.
2.
3.
Right click to open the Insert Feature right mouse menu; then verify that the Arc
Tangency Constraint item is checked.
4.
5.
8-43
A circle is displayed in dynamics. The radius and start angle parameters on the
dockable control are dynamically updated as you move the cursor.
6. Click to digitize the start point of the arc.
7. Click the Switch direction button on the dockable control.
The arc switches direction, and the sweep angle parameter is updated
dynamically to reflect the new sweep angle value.
8. Click in the map window to place the arc.
9. Press the Lock on the first row of the dockable control; then type the radius.
10. Press the Lock on the last row of the dockable control; then type the start angle value.
11. Click the Switch direction button.
12. Click to place the arc; then double click to end.
A feature composed of the two arcs previously digitized is placed.
8-44
Rotate dynamically:
1. Set the rotation mode to Rotate dynamically.
2. Click to place the origin point of the symbol.
The symbol is displayed in dynamics in the selected point style and highlight color.
3. Move the cursor to rotate the point symbol dynamically.
8-45
4. When you have adjusted the point symbol to the appropriate rotation angle, click to
place the feature.
Orient to geometry:
1. Set the rotation mode to Orient to geometry.
The point symbol is displayed in dynamics as you move the cursor around the map
window.
2. Move the cursor into the snap zone of the line segment.
The symbol is displayed dynamically oriented to the segment based on the direction in
which it was digitized.
3. Press TAB to switch the alignment if required.
4. Click to place the point that is oriented to the direction of the line.
Note: If you click without snapping, the point is placed at zero-degrees rotation. If the
snap zone includes more than one potential snap point location, the closest will be the
chosen location.
Placing by Circle
Place by circle lets you insert a circle in the following three circle placement modes:
By Center PointRequires the definition of a center point and a radius. You can
specify the radius dynamically or by key-in.
Selecting the Place by circle placement mode displays the Place Circle dockable control,
which dynamically shows the radius based on the cursor location. The diameter is shown
instead of the radius while in By Diameter mode. In By Center Point mode, you can type
a distance of the radius of the circle being placed in the Radius field, which is enabled by
selecting (pressing) the Lock. Key-in units are determined by the distance units on the
Units and Formats tab of the GeoWorkspace Coordinate System dialog box. You
cannot type a negative radius or a non-numeric value.
8-46
For all circle placement modes, the circle is shown dynamically as the mouse cursor
moves, as long as the required information for constructing a circle has been defined, as
seen in the following examples:
By Center Point
By Diameter
By 3 Points
For example, in the By Center Point mode, a dashed line is shown dynamically from the
center first point to the cursor location to represent the radius, and a circle is shown
dynamically as you move the mouse cursor for placement of the second point.
Likewise, the By Diameter mode shows the circle dynamically after you define the first
point of the diameter as you move the mouse cursor for placement of the second point.
In By 3 Points mode, a dashed triangle whose vertices represent the three points on the
edge of the circle is shown dynamically once two points have been defined, as in the
following figure:
The CTRL-Click key combination may be used at the last step of any circle placement
workflow to enable the placement of geometry collections. For example, if you want to
place two disjointed circles as a geometry collection using the By Diameter mode, you
would click to specify the first point of the diameter of the first circle in the geometry
collection, and then you would use CTRL-Click to specify the second point of the diameter
of the first circle. At this stage, you would click to specify the first point of the diameter of
the second circle in the geometry collection, and then you would click to specify the
second point of the diameter of the second circle in the geometry collection, at which time
the geometry collection would be placed. However, you cannot use CTRL-click to place a
circle as a hole within another circle; the capability of generating a hole inside a circle is
currently not supported.
This command supports coincidence, break, and properties settings. In addition, you can
access the viewing commands while the command is active. The AutoPan setting is also
honored, as are vector and raster snaps when moving the mouse cursor. You can
undo/redo the insert circle operation with the Undo/Redo commands. Pressing
BACKSPACE reverts the placement state to the previous step.
8-48
8-49
See the corresponding GeoMedia Professional Help topics for a complete information on
the construction aid dockable controls and workflows.
Delta X and Delta YConstructs a point at specified distances in the horizontal and
vertical directions from the last point digitized by the command. You can change the
distance values, and a point is displayed dynamically in the map window to reflect the
specified distances from the last point. You can then click in the map window or press
Enter to return the point to the command. (Shortcut key Y)
8-50
Distance and DirectionConstructs a point at the specified distance and direction from
the last point digitized by the command. You can change the distance and direction values,
and a point is displayed dynamically in the map window to reflect the specified distance
and direction from the last point. You can then click in the map window or press ENTER
to return the point to the command. (Shortcut key D)
If the command in use only supplies one point (for example, only one point has been
digitized in Insert Feature, or you are editing a vertex in Edit Geometry), you can
specify the direction in one of two ways, an azimuth or a bearing. However, if the
command supplies a geometry that contains at least two points(for example, two or more
points have been digitized with Insert Feature), you can also specify the direction by a
deflection angle. The deflection angle is the angle relative to the last (previous) line
segment formed from the next-to-last point to the last point of the geometry supplied by the
command. The azimuth direction setting, clockwise or counterclockwise, from the Units
and Formats tab on the GeoWorkspace Coordinate System dialog box is used to specify
whether the positive deflection angle goes in the clockwise or counterclockwise direction
relative to the last line segment.
Distance and Direction from PointConstructs a point at the specified distance and
direction from a specified location. You can specify the direction in one of two ways, an
azimuth or a bearing. You can change the distance and direction values, and a point is
displayed dynamically in the map window to reflect the specified distance and direction
from the supplied reference location. You can then click in the map window or press Enter
to return the point to the command. You might use this aid, for example, if you were
placing a parcel feature and you knew that the next vertex was located N40E and 30 meters
from the corner of another parcel feature. (Shortcut key M)
Distance Along FeatureLets you to type the distance along a feature from a snap point
where a point will be placed on the on the Distance Along Feature dockable control. The
8-51
displayed unit of measure is set on the Units and Format tab of GeoWorkspace
Coordinate System dialog box. You can switch the direction of traversal along the feature
by clicking the Switch direction button. (Shortcut key G)
Deflection AngleLets you to type an angle for placement in the Deflection Angle
dockable control. This construction aid restricts the dynamic cursor location to a single
deflection angle relative to the last line segment. The angle must be between -360 and 360
degrees (or the equivalent in the current unit), inclusive. This construction aid is only
available when at least a line segment has been digitized. (Shortcut key F).
You can restrict the placement of the next point (Reverse direction check box), either
along a deflection angle measured from the reverse of the direction of the last segment
placed, or in the angular direction (clockwise versus counter-clockwise) opposite the
default direction (Reverse angle check box), or both. The following examples show the
four different deflection angles when the check boxes are checked versus unchecked:
AzimuthLets you restrict placement to an absolute azimuth angle for linear and area
geometries. You type the angle in the Azimuth dockable control. The default angle is 0.
(Shortcut key Z)
BearingLets you restrict placement to an absolute bearing angle for linear and area
geometries. You type the angle in the Bearing dockable control. The default angle is 0.
(Shortcut key B)
8-53
Parallel ToLets you construct a point that creates a segment from the last digitized point
that is parallel to a specified feature, or is parallel to the tangent at the point where you
selected the feature, if the segment is an arc geometry. The end point of the parallel
segment is displayed dynamically in the map window during mouse move to reflect the
specified location. You can then click in the map window to return the point to the
command. (Shortcut key SHIFT+L)
8-54
The temporary placement mode is active for only the next vertex placed, after which
the previous placement mode is resumed. When the option is on, it applies to every
snapped vertex as long as it is on. You must turn the option off in order to cancel its
effect.
The Use existing geometry when digitizing option highlights the geometry between
the last vertex and the cursor snap point on every mouse move, which can cause
significant display delays with geometries containing many vertices. The temporary
placement mode highlights the geometry between the first point and the second point
one time (once the second point is entered), and maintains the highlight until the third
data point is entered to accept the geometry. This allows the cursor to be moved
without any display delays.
OffsetPlaces a feature offset a specified distance from another feature. This construction
aid places a temporary feature at a distance specified on the Offset dockable control from a
user-selected feature. You can then use the use existing geometry when digitizing option
on the Placement and Editing tab or the Use existing geometry option on the Options
toolbar to use all or part of the temporary feature to create a new feature. (Shortcut key
SHIFT+O)
The following are several example workflows for using the construction aids.
8-55
8-56
The feature is drawn in dynamics from the last point placed to the specified distance
along the feature from the current cursor snap point.
8-57
The dynamic segment/arc connecting the last point placed and a point the specified
distance along the area feature is moved as the cursor is moved.
9. Click Switch Direction on the control to highlight the opposite direction (or the switch
direction button on the dialog box or TAB on the keyboard).
8-58
This construction aid does not automatically snap into the feature, but is dynamically
extended as you move the cursor. You can use SmartSnap to ensure that you snap into any
other feature along the perpendicular extension. Once the point is placed, the
perpendicular placement mode is ended.
The Perpendicular From construction aid is only enabled if the last vertex is currently
snapped to a non-point feature. As you move the cursor, the next segment is drawn in
dynamics at 90 degrees from the feature currently snapped to.
You can use Perpendicular From at any non-corner point on the edge, but for corner or
endpoints you should use Perpendicular To. After digitizing the first point at the corner
of the two edges, you select Perpendicular To and then select which edge to digitize
perpendicular to/from. You can use Perpendicular From for those cases where it is clear
which segment was being chosen and thus save an extra click.
8-59
UsingOffset
Offset is very useful if you want to place a feature parallel to an existing feature, but offset
at a certain distance. For example, you might want to digitize a utility line offset twenty
feet from a property boundary. Offset mode will place a temporary feature at a specified
offset distance from a user-selected feature. You can then use the Options toolbar Use
Existing Geometry When Digitizing option (or the Use existing geometry when
digitizing option on the Placement and Editing tab of the Options dialog box) to quickly
use all or part of the temporary feature to create a new feature.
Offset mode remains on until you turn it off, at which point the temporary feature is
deleted. While offset mode is on, all the SmartSnap tools and all the placement and editing
options are available for use with the temporary feature.
8-60
5. Snap to and click on the first point and the last point of the temporary feature to copy it
to the new feature.
6. Press ESC to dismiss the dockable control and to turn off the offset mode.
8.
Select Offset from the right mouse menu to turn on the offset mode.
The offset distance field remains populated with the previously entered value.
9.
Select Line C.
8-61
10. Again, use Use Existing to snap to the first point and the last point of the temporary
feature and to copy it to the new features.
8-62
Figure 1
Figure 2
8-63
The Arc Tangency Constraint may be useful in conjunction with a construction aid when
placing an arc that is tangent to the previous segment. For example, the construction aid
can be used to determine an end point of an arc that lies on a line that is tangent to the
previous segment.
8-64
To place by length:
1. Select Insert Feature.
2. Select a non-point feature class to place.
3. Digitize a few segments/arcs.
4. Select Segment Length Constraint from the right mouse menu.
Stream Tolerances
Stream tolerances control how many vertices are created as you stream digitize. If you
have the tolerances set too large, you will need to weed out too many vertices, and your
digitized line will not have enough detail. If you set the tolerances too small, your features
will contain a large number of unnecessary vertices, negatively affecting performance. The
distance and delta of the stream tolerance are described in the following discussion. It is
recommended that you experiment with different tolerance values to determine which is
most appropriate for your data.
You set stream tolerances on the Placement and Editing tab of the Options dialog box.
The Distance tolerance is the distance the cursor must move before a new point will be
placed. For example, if this tolerance is set to one meter, the vertices will not be placed
closer than one meter apart.
The Delta value sets the stream digitizing thinning tolerance for stream digitizing. After
you place geometry, the tolerance reduces the number of streamed linear or area feature
vertices by filtering out unneeded vertices. A high filter value results in the removal of
many vertices. The valid range of numeric values is greater than zero, with no upper limit.
The filter moves along the placed vertices as follows:
8-66
Relative Placement
You can use the relative placement commands with the placement and editing commands
when you know the location of the next point only by its relationship to another known
location. There are two types of relative placement:
Place the next point at the user-specified distance and direction from a known
location.
Add new geometry to an existing feature using the Continue Geometry command.
Use the Insert Feature command with the CTRL key modifier.
Note: In the following workflows, left double click is the same as ALT-click (pressing
ALT while left clicking), except that ALT-click places a point at the location of the click,
and left double click does not.
The following is a Continue Geometry workflow:
1. Select the feature you want to continue in the map window.
2. Select Edit > Geometry > Continue.
3. Place additional geometry using the normal tools.
Note: Continue Geometry uses the same toolbar as Insert Feature, so all the same tools
are available.
The following is a workflow for digitizing discontiguous features with Insert Feature:
8-67
It is easy to model these features in GeoMedia Professional. The workflows are the same
as those for creating discontiguous features except that when you add the additional
geometry in this case a hole you place it inside an existing area feature. The software
is smart enough to recognize this and will automatically create a hole in the containing area
feature.
8-68
5. Switch to one of the arc placement modes, and enter the arc points in the appropriate
order.
Note: The last vertex placed is used as the start point of the arc.
6. Double click to end the feature.
Note: This works for linear features also.
Latitude,Longitude(d:m:s),[Height(m)] (optional)
Easting,Northing(m),[Height(m)] (optional)
Distance(m),Azimuth(deg) (Geodesic or Planar)
Distance(m),Bearing(deg) (Geodesic or Planar)
8-69
You can set preferences for the coordinate formats and readouts on the Precision
Coordinates dockable control by using the Units and Formats tab on the Define
Coordinate System File dialog box. This tab contains controls for setting the order to use
when displaying geographic coordinates; the hemisphere and quadrant to use when
displaying projected coordinates; the coordinate type, units, and precision; the distance and
starting point to use when displaying azimuths; and the default height to use when placing
and editing features.
The active update setting on the Precision Coordinates control drop-down list is Update
coordinates on mouse move by default. This setting displays the coordinates
dynamically; when you move the mouse over the map window, the coordinates update.
The other settings are Update coordinates on click, which updates the coordinates when
you click the left mouse button in the map window, and Clear coordinates after entry,
which tells the software to clear the entry field after you enter the coordinate values.
You display the dockable control by selecting View > Precision Coordinates.
To change the default update setting, you click the down arrow next to the coordinate
display, and you select a setting from the menu.
To display the list of available coordinate formats, you click the drop-down arrow, and you
select the appropriate format.
After you type the coordinate values that correspond to the location of the input point in
the field to the right of the format field, you press ENTER.
See the Inserting Traverses chapter for additional precision entry tools.
See Setting Units and Formats in the Working with Coordinate Systems chapter.
8-70
Collecting Attributes
Attribute information can be added or updated at anytime using either the data window or
the feature Properties dialog box.
See the Working with Data Windows chapter.
Using this tool ensures that attribute information is always entered when new features are
created.
8-71
Setting required values on default values on the Feature Class Definition dialog box.
In addition, other tools described in separate sections of this document allow you to
populate the attributes of multiple features after collection. These include Update
Attributes, Update Attributes Using Text, Join features, and Output to Feature
Classes. The last two are used to bring in attribute information from other sources and to
connect it to existing feature geometry. This section describes the copying of attributes
from previous features.
See Updating Feature Attributes and Updating Feature Attributes Using Text in the
Editing Features and Geometries chapter, Working with Joins in the Analyzing
GeoMedia Professional Data chapter, and Outputting Feature Data to Warehouses in
this chapter.
8-72
8-73
Note: Both tools preserve the original linear or area features used as components of the
new area feature. Therefore, you may want to delete the component features manually.
2. Click the Feature class drop-down arrow to display the list of feature classes in the
read-write warehouses to which you are connected.
3. Click the feature class in which you want to create area features.
4. Select the appropriate Hole processing option.
5. Click OK.
If Display Properties dialog for new features is on, or if input is required for the
selected feature class, specify attribute values for each feature on the <Feature>
Properties dialog box; then click OK.
If Display Properties dialog for new features is off, all potential area features are
highlighted in the highlight color.
8-74
6. When prompted, click Yes to place the highlighted features in the database. Or, click
No to reject the highlighted features and to exit the command.
3. Click the drop-down arrow to display the list of feature classes, queries, reference
features, and categories in the read-write warehouses to which you are connected.
4. Click the feature class in which you want to create area features.
5. To include holes, select Include holes.
6. Pause the cursor over each closed region of linework.
For each closed region over which you pause, the new feature is highlighted.
7. Click to accept the feature.
If Display Properties dialog for new features is on, or if input is required for the
selected feature class, specify the feature attributes on the <Feature> Properties
dialog box; then click OK.
If Display Properties dialog for new features is off, the feature is written to the
database immediately after you click to accept. The following message is displayed:
Writing area feature to database.
8. Continue until all area features have been created.
8-75
In addition to basic text insertion, Insert Text provides the following functionality:
8-76
Applying instance-based symbology for text featuresBy 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 textType 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 along an arcSet 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 geometrySet 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.
Placing along existing geometrySet 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.
Placing along existing geometrySet 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.
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).
8-77
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, Insert
Interactive Label, and Insert Text commands. 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. 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.
8-78
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).
8-79
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.
8-80
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.
8-81
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:
(underscore) Any single character
% Any string of zero or more
_
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.
Redigitizing Text
Redigitize Text lets you redigitize a single text point geometry or curved text, that is, a
composite text collection, while retaining its identity and attributes. Curved text is
represented as an ordered collection of text point geometries in which each text point
geometry represents a single character placed at a different location and possibly with a
different orientation. Two text collection types exist: 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 lets you perform textual editing of such a curved text representation. For
example, the textual editing may change the number of characters in the curved text as the
result of the addition or deletion of text characters. Or it is possible that an individual text
character has been moved or spun. The resulting geometry curvature of such curved text
may either lose the display fidelity or may not properly undulate with the shape of the
geometry for which it was initially placed. This command supports resolving these
problems by letting you redefine geometry curvature and location using an existing
geometry or a user-defined arc.
Redigitize Text distributes each character in the text string so as to undulate along the
geometry, orienting each character as required. This command honors the alignment of the
input text string. However, for better display, the resulting text string is always center
horizontal aligned by allowing all three vertical alignments (Top, Center, Bottom) when
the resulting output is a composite text collection. For example an input text string with
Top left or Top right alignment is converted to Top center after redigitizing.
This command deals only with the location, curvature, and inter-character spacing of the
selected text geometry, and it does not support redigitizing a multi-line text. You can
8-82
specify any existing linear or area geometry or define an arc for redistributing the text
along.
After selecting Edit > Text > Redigitize Text to start this command, you click to identify
a feature, which also identifies the start point of the segment to be redigitized. The right
click menu lets you choose among the following placement modes:
Place at point
Placing at Point
The Place at Point placement mode lets you change the location, control the intercharacter spacing, and convert a composite text collection to a single text point geometry.
In the case of redigitizing a single text point geometry, the orientation is preserved. When
you redigitize a composite text collection, it is converted to a single text point geometry
with an orientation of zero.
that was selected. While showing dynamics, the position of the text is to the right of the
mouse location. This mode is always enabled and is selected by default when you first
start the command in a session.
If the geometry used for redigitizing is small in its length, or it cannot accommodate the
entire text string for a given inter-character spacing, the orientation of those additional
characters is defined using the last two points in the input geometry.
The following figure shows the text geometry placed along an existing linear feature.
The following table describes the type of resultant text geometry for different types of
input geometries:
Input
Output
Remarks
Single-unit text.
(Single text point
geometry)
Composite text
collection, or
single-unit text
Composite text
collection
Composite text
collection, or
single-unit text
Standard text
collection. (Only a
single item at a
time is allowed to
redigitize.)
Nested text
collection, or
standard text
collection
Nested text
collection. (Only a
single item at a
time is allowed to
redigitize.)
8-84
Nested text
collection, or
standard text
collection
While redigitizing text, you can use the Up/Down arrows to decrease or increase
smoothing. The command also accepts key-ins from the Precision Coordinates control.
Additionally, you can use Backspace to revert the workflow to the previous state. For
example, after selecting a geometry (for place along), pressing Backspace clears the current
geometry selection and prompts you to select the geometry again to place along.
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-85
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.
8-86
3. On the Attributes tab of the features 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.
4. Click OK.
HYPERTEXT PATH:C:\Images,D:\AudioClips,
\\BIGSERVER\VIDSHARE\Birds\Video
2.
Type the attribute information for the feature in the last row of the data window.
8-88
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-89
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 Explorers 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.
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.
8-90
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, readonly 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.
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.
8-91
8-92
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-93
8-94
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-95
8-96
In summary, the Catalogs commands let you catalog and open associated feature classes
and perform the following additional tasks in manipulating catalogs:
Update spatially related metadata elements from the associated feature class.
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 userselected 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
Catalog Connections
Catalog Explorer
Catalog Features
Standards-compliantGeoMedia 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 ProfileCreate standardized metadata for your biological datasets
following the FGDCs Biological Data Profile.
Data Layer AssociationCatalog ties metadata to data by allowing you to associate a
metadata record with the GeoMedia feature class or image file that it describes.
Metadata CaptureOnce 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 ExplorerBridges 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 GraphicsInclude images of datasets in your Catalog reports.
9-2
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).
Metadata protects your investment in data and supports re-use of information already
acquired or developed within your enterprise.
9-3
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 promotes data sharing. Metadata helps GIS personnel share data by
providing the information that people need to locate, evaluate, and obtain data.
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.
ISO is also at work on ISO-19139, an XML schema for metadata implementation. ISO19139 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 19115s advantages in a concrete implementation specification.
GeoMedias Catalog commands include support for exporting metadata records in an XML
format that conforms to the 19139 XSchemas TS RC (May 2006 ).
9-6
9-7
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-8
See the Using Oracle Connections and Using SQL Server Connections appendices,
which discuss how to create Oracle and SQL Server Catalog data bases.
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.
Note: Access-based warehouses, catalogs, and libraries all use *.mdb files. You should
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
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.
OR
Select ODBC database as the Connection type.
9-10
Change the state of a catalog connection (open read-write, open read-only, or closed).
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:
NameCatalog connection names, with an icon at the start of the cell indicating the state:
Open Read-Write
Open Read-Only
Closed
2. Click New.
3. Select Access database as the Connection type.
9-11
OR
Select ODBC database as the Connection type.
5. Change the location of the .mdb file for an Access database or the data source name for
an Oracle or SQL Server database.
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-STD001-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
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.
9-14
2. Type the location from where the import files are to be read, or use Browse to select
the location.
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.
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
9-15
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.
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
9-16
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:
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
HTML
TXT
(FGDC)
GCE
XML
(FGDC)
XML
(ISO)
Rollup empty fieldsLets you exclude all the empty metadata elements.
Include map displayLets 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)
formatsLets 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\GeoMediaProfessional\stylesheets\catalogs folder: FGDC_classic.xsl,
FGDC_FAQ.xsl, ViewDetails.xsl, and ISO_Stylesheet1.xsl.
9-17
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.
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.
9-18
6. Select the Advanced tab; then set the available parameters appropriately.
(The following example is the Advanced tab for the HTML export format.)
(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
9-19
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,
\\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 locationinstead, 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.
RENDERS
Title of the report
List of sections
Hyper linked section names
Metadata element headings
Element content of type text
Biological element headings
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:
9-20
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-ofreference 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
9-21
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
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:
Attribute nameThe identity of all attributes associated with the feature class. This
metadata element is stored in the Entity and Attributes section.
Point and vector object informationThe type and number of vector or nongridded-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.
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.
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:
1. Select Tools > Catalogs > Associate Catalog Records.
2. Select the appropriate catalog connection to display the treeview of Available catalog
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.
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
Basic description
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:
9-26
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.
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
9-29
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.
9-30
9-31
Spatial tabDisplays 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.
To the left of the map is a toolbar that lets you display and browse the map content.
Show MapDisplay map or data, if available.
Zoom InZoom in on features.
Zoom OutZoom out from features.
PanPan map features.
Full ExtentDisplay 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 tabDisplays 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 tabContains 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
2. Select the appropriate catalog connection to display the treeview of Available catalog
records.
3. Select the appropriate catalog record.
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
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.
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.
Software Delivery
GeoMedia Catalog functions will be delivered as part of GeoMedia and GeoMedia
Professional by using the default delivery folder of C:\Program Files\GeoMedia
Professional or 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.
Files/Folders
CatalogTemplate.mdb
Catalog_Samples.mdb
World.mdb
Oracle Scripts
SQLServer Scripts
9-39
Files/Folders
FGDC_classic.xsl,
FGDC_FAQ.xsl,
ISO_Stylesheet1.xsl,
View_Details.xsl
tech_geomedia.gif
FGDC_to_ISO.xslt,
FGDC Dataset
Metadata Profile.pdf
9-40
Description
Style sheets used to View
a Catalog Record, and to
publish record(s) using
the Export Catalog
Records command.
Default graphic file
displayed by XML style
sheets.
FGDC content is
translated to XML(ISO)
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.
Location
<HOME>\StyleSheets\Catalogs
<HOME>\StyleSheets\Catalogs
<HOME>\Program
Delete features
Edit geometry
Spin geometry
Rotate geometry
Copy features
Move geometry
Continue geometry
Merge features
Redigitize geometry
Split features
Delete geometry
These editing tools work with the settings on the Placement and
Editing tab of the Options dialog box (Tools > Options).
See Using the Placement and Editing Tab in the Working with Features chapter.
10-1
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 values being underlined.
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)
10-2
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.
10-3
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.
Update Attributes logs errors encountered (due to division by zero, creation of duplicate
values in the index, primary key, or relationship, network problems, and so forth) while
updating database with specified value in the log file. This file is created in your
warehouse folder with the root name the same as the feature class name with a .txt
extension.
The Enable undo and logging check box lets you enable/disable logging (undo group
creation and modification logging) when updates are being performed. When checked, the
command creates an Undo group for the updates and enables modification logging, which
causes all affected records to be refreshed and allows undo to be available for the updates
after the command processing is complete.
When this option is unchecked, the command does not create an Undo group, and
modification logging is disabled. The affected records are closed and reopened after
processing is completed, and the select set is cleared. Because the time taken to refresh the
affected records through modification logging increases exponentially with the number of
records being updated, you may want to uncheck this option for large datasets to improve
performance. In this case, however, you cannot undo the updates after processing.
Creating Expressions
In creating the functional attribute expression, you can use the attributes and all functions
and operators that evaluate to a single value. This command does not, however, store
expressions created on the Expression dialog box.
The Expression dialog box in this command for functional attribute expressions appears
and functions somewhat differently from the Functional Attribute dialog box used for
10-5
Using Literals
Update Attributes allows literals for the following data types:
Boolean Currency Double Long
Single
Byte
Date
Integer Memo Text
You must enclose literals in single quotes (for example, ALABAMA for a text attribute) if
the attribute being updated is Text, Memo, Date, or Boolean. If you do not enclose the
value for these data types in single quotes, it is validated and evaluated as an expression.
For numeric data types (including Currency), you type literals as they are, without quotes.
If the value does not evaluate to a numeric value, it is validated and evaluated as
expression.
This command also lets you update geometry (corresponding to data types Graphic and
Spatial). However, only functions provided by the Expression dialog box (and no literals)
are allowed for update of geometry.
See Working with Functional Attributes in the Analyzing GeoMedia Professional
Data chapter for information on functional attributes.
10-6
Note: Holding the cursor over an attribute name displays its data type.
AND/OR
Select the appropriate attribute(s) from the Attributes to update list; then click
Expression or double click the attribute field to open the Expression dialog box.
See the GeoMedia Professional Help for information on this dialog box.
4. On the Expression dialog box, create the expression for the selected attribute; then
click OK to write the expression back to the selected attribute field on the Update
Attributes dialog box.
10-7
This command updates the target attribute with the entire composite text string, when
dealing with a composite text collection. For a standard text collection or nested text
collection, the command updates the target attribute with the first text item in the
collection.
An example workflow involves data captured in a CAD system. Frequently in a datacollection workflow, the geometry and attributes are collected separately, and the
conversion operator types text that represents the key for joining them together.
This command allows you to load text onto spatially related features so that you can use
this as the key for joining to a database table.
This command detects the following error conditions and writes them to a log file:
Area Features
10-9
Copying Attributes
The creation of a spatial database not only includes capturing the map data but also
integrating the associated attribute information. GeoMedia Professional provides the
functionality to bring in the tabular attribute information from a wide variety of data
10-10
sources. The copy attribute function provides the tool for such integration of spatial CAD
data with tabular attribute data where there is no common attribute key field. This copy
attribute function is performed through a two-step process of using the Copy Attributes
Definition and Copy Attributes commands, letting you link, then, copy existing features
and existing attributes.
Group 1Attributes that exist only in the source feature class. In this case the
attribute metadata is copied over from the source feature class to the target feature
class.
Group 2Attributes that exist in both the source and the target feature classes with a
definition exactly/partially matching, that is, either the data type is the same for both
fields or the data type of the field in the target feature class has greater storage
capacity. In this case the values are copied directly.
After selecting the source and the target feature class, the command provides a list of
attribute fields for selection. If you select a feature class as the target, the command lists
both Group 1 and Group 2 fields. However, if you select a query as the target, the
10-11
command lists only Group 2 fields because queries are read-only so there can be no editing
of the attribute metadata. The following are not displayed:
Hidden fields
Fields that already exist in the target feature class with the auto increment property
Fields that already exist in the target feature class but are not updateable
If any of the selected fields do not exist in the target feature class (from Group 1), the
command attempts to create the new field metadata in the target feature class for these
fields. While creating the field metadata, the command makes use of the field properties of
the field that exists in the source feature class/query. However, in the two following cases,
the command does not preserve some properties of the field being added:
A field acting as a primary key in the source feature class loses its primary key nature
in the target class.
A field acting as an auto number in the source feature class loses its auto increment
property in the target class.
When this command prepares the required copy definition when new attributes are to be
created in the target feature class, the command displays the New Attributes dialog box
listing all the new fields. You then confirm that the field metadata in the target feature
class should be created. Upon confirmation, the command creates the field metadata in the
target feature class, and both dialog boxes are dismissed. If you do not confirm the
metadata creation, no action is taken, the New Attributes dialog box is dismissed, and the
Copy Attributes Definition dialog box is redisplayed.
When creating a new geometry field in the target feature class:
If the target feature class does not have an existing geometry field, the new copied
geometry field is set as the primary geometry field, and the coordinate system of the
new geometry field is set to the default coordinate system of the target warehouse.
If the target feature class does have an existing geometry field, the new copied
geometry field is not set as the primary geometry field, and the coordinate system of
the new geometry field is set to match the coordinate system of the existing geometry
field.
Copying Attributes
Copy Attributes performs the actual copy, that is, it copies the row values of the selected
attributes from a feature instance of the source feature class to that of one or more feature
instances of the target feature class or query. This command uses the required copy
information that was defined using the Copy Attributes Definition command. Only those
values of the attributes fields present in the copy definition are copied.
The following are two rules for selecting feature instances for a copy:
10-12
A single feature instance from the source feature class must be selected from a data
window or a map window.
One or more feature instance(s) from the target feature class must be selected from a
data window or a map window.
When you start this command after making the required select set, the features in the select
set are validated with the copy information, and any mismatch that occurs during
validation is displayed to you. Then, the row values of the selected attributes from the
source feature class are copied to the feature instance(s) in the target feature class. The
command performs the required type/data conversion wherever required. When copying a
numeric value to a numeric field, data conversion is performed if the field type is not the
same and the type of the target feature class has a greater storage capacity than the type in
the source feature class.
To copy attributes:
1. Create a read-write connection to a GDO warehouse containing the target feature class
to which attributes are to be copied.
2. Create a read-write or read-only connection to the warehouse containing the source
feature class from which attribute fields are to be copied.
3. Select Edit > Attribute > Copy Attributes Definition.
4. Select the appropriate feature class, reference feature, category, or query from the
Target features drop-down list.
5. Select the appropriate feature class, reference feature, category, or query from the
Source features drop-down list.
6. Check the appropriate Attribute to copy check boxes; then click OK.
10-13
7. Click OK to create metadata in the target feature class. Continue with Step 8.
OR
Click Cancel to redisplay the Copy Attributes Definition dialog box.
8. Place one or more features from the target feature class and one feature from the source
feature class into the select set.
9. Select Edit > Attribute > Copy Attributes to complete the copy.
10. Optional: Select Edit > Attribute > Copy Attributes Definition to redefine copy
definition.
Manipulating Features
You can easily manipulate features by moving, merging, splitting, copying, copying
parallel, and deleting selected features.
10-14
You can change the location of a feature and change the orientation of text and point
symbols by creating a select set in a map window or a data window and then activating
the appropriate tool.
You can move a single feature, multiple features, or an entire feature class together.
Selected features can belong to different feature classes.
You can rotate one or more text and/or point features that are represented by symbols.
Merging Features
Merge allows you to take two or more features in a select set and merge them into a single
output feature. This tool works with features that are of the geometry types point, line,
area, or compound and that are of the same feature class. Merging features copies the
attributes from the first input feature in the select set to the merged output feature.
Merging also deletes the input features and outputs the new feature with merged geometry
(with a new feature ID). The resultant merged geometry is discontiguous if the original
geometries cannot be merged into a single geometry.
Merge honors the height settings on the Placement and Editing tab of the Options dialog
box. Merge modifies existing geometry, so it uses the height values of the existing
geometry. If the input geometries have different height values, the resulting merged
geometry will have different height values as well.
The following are examples of area merge conditions:
If the features are not adjacent, merging the features creates a single feature with
discontiguous geometry.
10-15
To merge two or more features of the same feature class into one feature:
1. Select two or more features of the same feature class.
2. Select Edit > Feature > Merge.
If the Properties dialog box option is off, the features are merged and the new feature
is written to the database, and the original features are deleted.
If the Properties dialog box option is on, the features are merged, and the dialog box is
opened with the properties of the first input feature for entry of new attribute values.
Once the attribute values have been specified, the new feature is written to the
database, and the original features are deleted.
See Merging Feature Classes and Queries in the Analyzing GeoMedia Data chapter
for information on the Analytical Merge command.
Splitting Features
Split Feature allows you to split one or more features, copying the attributes from the old
feature(s) to the new feature(s). You can split features having a single linear or areal
geometry (polygon, boundary, composite polygon, polyline, composite polyline, and arc)
or a feature comprised of a collection of discontiguous geometries.
This command gives you a choice in the type of split geometry to digitize during a split
operation by using split by polyline mode, split by polygon mode, split by point mode, or
split by existing features. You set the digitizing mode through the commands dockable
control.
You can also use construction aids to construct the points for digitizing the split geometry.
See Using Construction Aids in the Working with Features chapter.
10-16
You can split an area feature using the geometry of a second feature with the Use existing
geometry when digitizing option from the Placement and Editing tab of the Options
dialog box. Clicking two points on the intersecting feature indicates the start and end
points of the intersection.
You split line features by snapping to a selected line and double clicking or digitizing a
split line.
This tool does not honor the break setting on the Placement and Editing tab, but it does
honor the coincidence setting and the automatic pan map window setting on the
SmartLocate tab of the Options dialog box. Any features coincident to the split feature
will have vertices inserted at the snap points.
When splitting a feature, the Z value you receive is always the interpolated Z value of the
existing data, except for when you are splitting areas. For areas, the split line is new data,
so the Z value you receive is always the default Z value you specified on the Default
height value field of the Placement and Editing tab or the Default Height dockable
control. When digitizing the split line using precision key-ins, you can override the default
Z value by typing a different value in the Precision Coordinates dockable control.
Snapping to an existing feature takes the Z value of the snapped point unless the Use
default height value instead of height at snap point option is set on the Placement and
Editing tab.
See the Working with Features and Working with Coordinate Systems chapters for
more information on these tabs.
10-17
Solution: This is a value split. The area is split into three area features.
Case 3: A split line intersects two area boundaries at two points each.
Solution: Invalid split. The larger area would share the middle vertex, resulting in invalid
topology.
Case 6: Given an area with a hole, the split line crosses the boundary multiple times and
has its end points outside the boundary.
Solution: The feature is split into two features at the intersection point.
Case 2: The splitting line can be digitized using stream digitizing and can cross the
feature(s) multiple times to split it into more than one feature.
10-18
Solution: The line is split into multiple lines at the intersection points.
Solution with coincidence off: Line B is not split in any way; coincidence is broken.
10-19
A
B
C
AOriginal feature, containing a homogeneous geometry collection of four discontiguous
area geometries.
BOriginal feature geometry with a split polygon shown, specifying the desired
partitioning of the geometries.
CResult of the split operation. The shaded areas represent a geometry collection
belonging to the new feature created by the split (portions of the original geometry that
were external to the split polygon). The cross-hatched areas are the geometry collection
now associated with the original feature (portions of original geometry that were internal to
the split polygon).
To complete the split you simply click to split the geometry at the highlighted point.
10-20
Copying Features
Copy (features) lets you make multiple copies of one or more selected features to new
features of the same feature class from a read-write connection. The copied features are
identical to the originals except that any autonumber field is incremented automatically. If
there are required fields or key fields on the features to be copied that are not autonumbers,
the Properties dialog box opens for each copied feature, letting you resolve these values.
The Properties dialog box also opens if you have selected the Display Properties dialog
for new features option on the Options dialog box (Tools > Options).
You can copy features from multiple feature classes in a single operation just by placing
them in a select set, which must contain at least one feature from a read-write connection.
You can designate the source point and destination point for the copy with the cursor or by
typing values on the Precision Coordinates dockable control.
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, Copy runs in action-object mode,
which lets you copy 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
10-22
in object-action mode, which lets you copy only the selected features or copy the selected
cells during the command instance.
All writable features in the select set appear in dynamics on the cursor again.
8. Perform another copy.
OR
Select the Select Tool or press ESC to exit the command.
The copied feature parallels the shape, angles, and lengths of the original feature
proportionally, including preserving arc geometry during the copy. You can copy a feature
to the same feature class as the selected feature or copy the feature to a different feature
class. The copied feature is created in the active destination feature class selected in the
feature selection control of the Copy Parallel dockable control, which opens when you
select this tool. Changing the Target feature class in this window changes the feature class
of the copied feature. Only feature classes from read-write connections appear in this
control.
Copy Parallel also honors the Display Properties dialog for new features and
Automatically add legend entries settings on the Placement and Editing tab of the
Options dialog box.
You can specify the offset copy distance by either typing the distance in the Offset field or
by picking data points with your cursor. The unit and precision for the offset distance
comes from the Units and Formats tab of the Define Coordinate System File dialog box.
See the Working with Features and Working with Coordinate Systems chapters for
more information on these tabs.
You can also lock in the current distance value by selecting the Lock offset check box.
This locks the feature in dynamics at the offset distance value, and the feature no longer
moves with the cursor. You can then place the new feature on either side of the original
feature with a click. When the offset value is not locked, the feature is displayed in
dynamics at the cursor location, and the offset value is automatically updated as you move
your cursor.
10-24
If the Preserve height check box is checked (the default), the command maintains the
height values of points in the original feature that correspond to points in the target feature.
If unchecked, the command sets the height of every point of the new geometry to the
height of the target point. If the target point comes from the mouse, the value is the default
height. If the target point comes from a keyin, the value could either be the default height
(if no Z value is specified) or the height value that you enter in the Precision Coordinates
dockable control.
You can also place multiple parallel copies of the selected features at different offsets.
You can easily do this with the CTRL+click keystroke combination to place multiple
features, each at the specified offset from the last copied feature. The additional features
are always placed on the same side as the original.
Copy Parallel sets the height of every vertex of the new geometry to the height of the
input point. If the input comes from the mouse, the value is the default height. If the input
comes from a keyin, the value could either be the default height or the height value you
type.
To copy parallel:
1. Select Edit > Feature > Copy Parallel.
2. Select a feature, reference feature, category, or query to copy parallel from the Target
drop-down list.
The feature is displayed in dynamics, and the Offset field is updated based on the
cursor location.
3. Optional: Select the Lock offset check box to maintain the offset at the given value;
then type a new value in the Offset field and press ENTER.
4. Optional: Uncheck the Preserve height check box.
5. Click to place the copy of the feature.
The feature is copied to the specified location with no change in feature class,
displayed in its correct style, and written to the database.
The Properties dialog box is opened if the setting of the Placement and Editing tab is
on or if the new feature has required values.
6. Select a different feature class in the Target drop-down list.
7. Click to place the feature.
The feature is copied and changed to the specified feature class.
8. Click to select another feature to copy parallel.
The feature selection control is not populated with the feature class of the selected
feature.
9. Click to place the feature.
10-25
Deleting Features
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.
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.
10-26
Manipulating Geometry
Edit Geometry allows you to edit (insert, move, and delete) vertices on the selected
features. This tool honors the break and coincidence settings on the Placement and
Editing tab of the Options dialog box (Tools > Options).
Edit Geometry modifies existing data, so it uses the height values of the existing
geometry. Moving a vertex only affects the height and width coordinates of the vertex.
Inserting a new vertex gets the height value by interpolating between the height values of
the two bounding vertices. This command also allows you to edit the height value.
When you select at least one vertex, you can use construction aids with this command to
construct a geometry by a specific method and then return the constructed geometry to the
command. If you select multiple vertices, the last selected vertex is used as the reference
point, and all vertices are moved by the offset defined by the reference point and the
constructed point.
See Using Construction Aids in the Working with Features chapter.
Manipulating tips:
You can have multiple features selected for editing, but you can only edit vertices from
a single feature at any one time. The exception to this is if there are coincident
vertices, which are edited automatically if coincidence is turned on.
You can select all the vertices in a geometry by selecting a vertex and then pressing
CTRL+A, or by selecting Select All from the right mouse menu when a vertex is
selected.
You can select all the vertices between two vertices in a geometry by selecting a vertex
(1) and then selecting another vertex (2), while pressing SHIFT, as shown in the
following example:
If you want to move multiple vertices, select the vertices and then hold down CTRL on
the last one while dragging them.
You can undo the last edit performed and redo the last undone edit without exiting the
command by selecting Undo and Redo, respectively, from the right mouse menu.
However, you can only undo/redo changes made by this command.
You can right click and Select All, use CTRL+A, or SHIFT click to select multiple
handles. However, if you select multiple handles and the geometry contains a large
number of vertices, you will have to wait a long time for all the handles to be selected.
You can interrupt this vertex selection process by pressing ESC. The command then
remains active, and the handles selected before pressing ESC remain selected.
10-27
Editing Circles
When editing a circle (that is, a composite polygon that represents a circle), the circle is
highlighted with handles that you can drag to increase or to decrease the radius. The eight
handles represent the four corners and four mid-points of the MBR. Additionally, a
dockable control is displayed, letting you type a precise new radius value.
The diametrically opposite handle of the handle being dragged is used as an anchor point
such that it is always fixed in the new MBR. As you drag one of the handles, the new
radius is shown in the radius field. To change the radius by keyin, you must first depress
the lock button to change to lock mode, whose default is locked/unpressed.
The circle is modified dynamically from the center when you press ENTER after typing
the new radius. Although the handles are still shown when the radius is locked, you cannot
drag the handles to modify the radius dynamically.
You can select one handle to edit the circle or all handles to move the circle. The dockable
control is not displayed when handles from more than one circle are selected. If handles
from more than one circle are selected, dragging any handle edits all circles.
Although the circle consists of arcs, each individual arc cannot be edited separately. You
cannot remove a vertex or break an arc by inserting a vertex. Finally, editing the height of
any handle edits the height of all.
Editing Arcs
You can edit arcs by typing a parameter or by dragging a handle while keeping a parameter
locked, the default mode. When you select a handle on the arc to edit, a dockable control
is displayed, letting you precisely control of the edit through keyin for different arc
parameters. The ten arc parameters you can lock and modify are as follows: radius, sweep
angle, chord length, arc length, tangent length, chord direction, start radial, end radial, start
tangent, and end tangent. These parameters are available on the drop-down list of the
control.
10-28
When you type in a new value and press ENTER or you drag a handle to modify the arc
while keeping a parameter locked, the arc is modified. The result varies depending on the
locked parameter and the handle dragged. If the parameter is not locked, the value is
updated dynamically. When a parameter is locked, the origin of the arc and two dashed
lines, which represent the start tangent and end tangent, are displayed. Two arrows along
the arc are also displayed to indicate the direction of the arc. When a handle shared by two
arcs in a composite geometry is selected, the first arc is edited. To edit the second arc, you
must hold down ALT when selecting or dragging the shared handle.
If a you selected a single vertex, the field displays the current height value. If you
selected multiple vertices, the field is blank.
5. Type the new value in the Height field.
6. Click OK to update the coordinates of the selected vertex(es).
See the Validating and Fixing Data chapter for tools to trim and to extend geometry and
to insert intersections.
4. Using the Precision Coordinates control, type the coordinates of the new location to
move the selected vertex; then press ENTER.
10-30
5. Repeat Steps 3 and 4 until the appropriate edits have been made.
10-31
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.
OR
To delete a vertex, select the vertex and press DELETE.
The selected vertex and coincident geometry are edited.
The features are split into two features when snapped to by the edited feature with
break on, and the attributes are copied.
Note: This is true only for end points. In this example, you would not break line 1
because the edit was not done at an end point on line:
5. Select Tools > Options > Placement and Editing; then turn off Break linear
features, and turn on Maintain coincidence.
6. Select a vertex, and move it so that it snaps to another feature.
10-32
The feature is not split into two features when snapped to by the edited feature. A
vertex is placed on the geometry snapped to by the digitized line, but the snapped-to
feature is not split in two.
4. Press CTRL+a.
5. Press DELETE.
5. Press DELETE.
10-33
Continuing Geometry
Continue Geometry allows you to digitize additional geometry for a selected feature or to
add new geometry to a feature that has no geometry. In the latter case, you would select
the feature from a data window. This command, like many of the placement and editing
commands, honors the settings on the Options dialog box (Tools > Options) for
controlling default height values, automatic breaking of features, and maintenance of
coincidence when snapping to other features.
When you select a feature to be continued and select Continue, the Continue Geometry
dockable control opens. This control is similar to the Insert Feature and Redigitize
Geometry command controls, except in this case it opens with the feature class field filled
in with the name of the feature class of the selected feature to be continued and the
appropriate geometry type icon pressed to indicate the geometry type of the selected
feature class.
The Placement Mode drop-down list lets you choose the appropriate placement mode
from those available for the selected feature class. Selecting the Options button opens the
Options dialog box with three accessible tabs: Placement and Editing, General, and
SmartLocate. This provides a convenient way for you to set up the options for placement
and editing inside the Continue Feature command. In addition, you can use any of the
available construction aids to assist in digitizing by clicking the right mouse menu and
selecting the appropriate construction aid.
See Inserting Features in a Map Window in the Working with Features chapter for
information on using placement modes and construction aids.
Note: By default, the Arc Tangency Constraint is on indicating the arc tangency state
when you start this command for the first time.
To continue geometry:
1. Select the feature to be continued.
2. Select Edit > Geometry > Continue to display the control with the feature class of the
selected feature.
3. Place the new geometry in the map window.
2. Select Edit > Geometry > Continue to display the control with the feature class of the
selected feature.
3. Select Options > Placement and Editing; then turn on Display Properties dialog for
new features and Break linear features with, and the appropriate break option.
Verify that Maintain coincidence is turned off.
4. Digitize the geometry.
The features are split into two features when snapped to by the digitized feature with
breaks on, and the attributes are copied.
5. On the Placement and Editing tab, turn off Break linear features, and turn on
Maintain coincidence.
6. Continue the geometry.
The feature is not split into two features when snapped to by the digitized feature. A
vertex is placed on the geometry snapped to by the digitized line, but the snapped-to
feature is not split into two features.
The temporary placement mode is active for only the next vertex placed, after which
the previous placement mode is resumed. When the option is on, it applies to every
snapped vertex as long as it is on. You must turn the option off in order to cancel its
effect.
The Use existing geometry when digitizing option highlights the geometry between
the last vertex and the cursor snap point on every mouse move, which can cause
10-35
significant display delays with geometries containing many vertices. The temporary
placement mode highlights the geometry between the first point and the second point
one time (once the second point is entered), and maintains the highlight until the third
data point is entered to accept the geometry. This allows the cursor to be moved
without any display delays.
Note: The Use Existing construction aid is also available on the right mouse menu with
the Insert Feature command.
Moving Geometry
Move allows you to easily move selected feature geometry, images, or labels from one
location to another in a map window or a data window. You can select the command first
and then the geometry to be moved or vice versa. In the first mode, this command remains
active after a move is complete so that you can select and move additional features, though
you can select one feature at a time. In the second mode, you can select multiple features
and then start this command. This command supports construction aids that return a point
geometry and require no input geometry while identifying both the from point and the to
10-36
point, that is, defining the origin and the new location. You can end this command with
ESC, Exit from the right mouse menu, and invoking certain other commands.
Features to be moved can be selected using a map window, a data window (in case of
object-action mode only), or a query. All read-write objects in the select set are moved by
this command.
To move a geometry:
1. In a data window, click the row selector of the feature geometry you want to move.
Press and hold the CTRL key while selecting multiple features.
2. Activate the map window.
3. Select Edit > Geometry > 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 and drag the select set to the new
location.
Spinning Geometry
Spin allows you to spin individual graphic text or oriented point geometries (or sets of
geometries) within a geometry collection. For a composite text collection, this provides
the ability to spin individual letters. You can select the command first and then the
geometry to be spun or vice versa. This command remains active after a move is complete
so that you can select and spin additional features. You can end this command with ESC,
Exit from the right mouse menu, and invoking certain other commands.
You have two spin options on the Spin dockable control, Relative and Absolute.
Relative: This option spins the results in an orientation relative to the original orientation
of the selected feature(s). The features are spun to the angle determined by the position of
the cursor or by exact key-in on the control. The resulting orientation is the angle made by
the line joining the cursor and the base point with respect to the current orientation of the
feature.
10-37
The following figures show the result of the spin operation with the relative angle
specification.
The geometry is oriented at Resulting orientation of the geometry after being spun at a
90 degrees before the spin.
relative angle of 45 degrees.
Absolute: This option spins features with an absolute angle mode. The features are spun
to the absolute angle, which is the angle made by a line joining the cursor and the base
point with respect to the positive X-axis or by exact key-in on the control.
The following figures show the result of the spin with the absolute angle specification:
The geometry is oriented at Resulting orientation of the geometry after being spun at an
90 degrees before the spin.
absolute angle of 45 degrees.
The Angle field on the control displays the spin angle with unit and precision set for the
angle as specified on the Unit and Formats tab of the GeoWorkspace Coordinate
System dialog box. The control also contains a Lock button When selected (pressed), you
can type an angle value in the Angle field. When not selected (unpressed), as you move
the mouse in the map window with the spin in progress, the corresponding value is updated
in the read-only Angle field. This is the default setting.
An origin handle appears in the map window for each selected point symbol or text.
10-38
Rotating Geometry
Rotate lets you interactively rotate one or more selected feature geometries or labels from
a read-write connection. You can rotate all geometry types except coverages and
rectangles. You can select the command first and then the geometry to be rotated or vice
versa.
This command displays a dockable control to view the current rotation angle and also to
define the angle to which the selected features are to be rotated. During rotation, the angle
shown in the dockable control is in the unit and precision set on Units and Formats tab
(View > GeoWorkspace Coordinate System), but if you snap the cursor to some feature,
the actual angle is shown, ignoring the precision setting. You can lock the displayed angle
value by selecting the control lock (unpressed), or you can type a new angle value for
rotation after selecting the control lock (pressed). If you need to undo rotation, the Undo
command lets you undo all rotated features in a single rotate operation. When you select
the command first, followed by the geometry, the command remains active after a rotate is
complete so that you can select and rotate additional features. You can end this command
with ESC, Exit from the right mouse menu, and invoking certain other commands.
10-39
This displays the feature(s) able to be rotated in dynamics and the dockable control.
3. Type the rotation angle in the Rotate Geometry dockable control.
4. Select a base point about which to rotate the feature(s) by snapping to an existing
feature, or by typing a value in the dockable control.
5. Move the mouse cursor to display the feature(s) rotated in dynamics about the base
point. The rotated angle is the angle made by the line joining the mouse cursor and the
base point with respect to the positive X-axis.
Snap glyphs are displayed as the mouse moves over the existing feature(s).
6. Click to accept the end point and to rotate the feature(s).
If you selected the geometry first and then the command, the command terminates once
the rotate is complete. In this mode, selecting Cancel from the right click menu lets
you select another base point for rotation.
If you selected the command first and then the feature, the command remains active,
letting you select other features to rotate. In this mode, selecting Cancel from the right
click menu lets you select another feature for rotation.
Redigitizing always begins from the start point. If the end point is snapped to an end point
of a line, you can continue digitizing without being constrained by the end point as if you
were extending the feature.
When you select a feature to be redigitized and then select Redigitize Geometry, the
Redigitize Geometry command dockable control opens. This identifies the selected
feature class and geometry type of the selected feature. The Redigitize Geometry control
is similar to the Insert Feature and Continue Geometry controls.
The Placement Mode drop-down list lets you choose the appropriate placement mode
from those available for the selected feature class. Selecting the Options button opens the
Options dialog box with three accessible tabs: Placement and Editing, General, and
SmartLocate. This provides a convenient way for you to set up the options for placement
and editing inside the Redigitize Geometry command. In addition, you can use any of the
available construction aids to assist in digitizing by clicking the right mouse menu and
selecting the appropriate construction aid.
See Inserting Features in a Map Window in the Working with Features chapter for
information on using placement modes and construction aids.
Redigitize Geometry also allows you to use the back arrow key to undo previously placed
point, and it supports stream digitizing by holding down the left mouse button and
dragging the mouse.
This command, like Insert Feature and many other placement and editing commands,
honors the settings on the Options dialog box (Tools > Options) for existing geometry,
automatically breaking features, and maintaining coincidence. Redigitize Geometry uses
the height value you specify for new points in the Default height value field of the
Placement and Editing tab. Finally, you can digitize in stream mode by holding down the
left mouse button.
The snap glyph is displayed, and the geometry is highlighted between the start and end
points.
5. Place the end point.
(a = highlight color, of what will be placed; b = select color)
The section of geometry between the start and end points is deleted, and the line
feature is displayed in dynamics from the start point.
6. Place the next point.
7. Double click to end.
The snap glyph is displayed, and the geometry is highlighted between the start and end
points.
5. Press the TAB key.
The section of geometry between the start and end points is deleted, and the area
feature is displayed in dynamics from the start point to the end point.
7. Click to place the next point.
10-43
Note: The break only occurs if the geometry being redigitized is a line and if the end point
for redigitizing is snapped into another line. Then the line that is snapped into is broken,
the Properties dialog box is displayed for the new piece, and the redigitize operation is
ended. If the end point for redigitizing is not the end point of the line, the break option is
ignored when snapping into another feature, and the command continues normally.
If the Display Properties dialog for new features option is turned on (Tools > Options,
Placement and Editing tab), the Properties dialog box displays for each feature that has
changed, allowing you to enter attribute values.
Note: If the target feature class contains required attribute fields for which values cannot
be automatically calculated, the Properties dialog box displays regardless of whether or
not the Display Properties dialog for new features option is turned on.
This command also uses the Copy attributes from previous feature option on Placement
and Editing tab. When this option is on, in case of multiple source features, the values of
the attribute field that you have accepted for the previous feature are copied to current
feature. By checking the Copy values from matching attributes check box on the
Change Feature Class dialog box, you can also copy matching attribute values along with
the geometry to the destination feature class. When on, this option takes precedence over
the Copy attribute values from previous feature option (Placement and Editing tab,
Options dialog box). However, if the Copy values from matching attributes option is
not on, and the Copy attribute values from previous feature option is on, for the case
where there are multiple features in the select set, the values entered for the attributes (both
matching and non-matching) are carried over to subsequent features.
On the Options dialog box, click the Placement and Editing tab.
Check the Display Properties dialog for new features check box.
Click OK.
3. Select Edit > Feature > Change Feature Class.
10-46
4. From the Target feature class drop-down list, navigate to the warehouse connection
or the category that contains the target feature class or the reference feature that you
want; then select the feature class.
Note: The Target feature class field is blank the first time you use this command.
5. Optional: Check the Copy values from matching attributes check box.
6. Optional: Check the Delete original feature check box.
7. Click OK.
Note: If the select set contains features of different geometry types that cannot be
converted/copied to a single target feature class, a message displays; click OK and
reselect your features.
Each feature in the select set is highlighted and converted/copied from the current
class to the target class as follows: a new record is created in the target class for all
features in the select set, the records in the source class for all read-write features in
the select set are deleted, depending on the Delete original feature option setting, and
all open windows and queries displaying the target class are updated.
If Display Properties dialog for new features is turned on, or if the target class
contains attribute fields for which values cannot be automatically calculated, the
Properties dialog box is displayed for each feature. Type the required attribute values,
and click OK to process the next feature.
Note: If the select set contains features of the same geometry type but that belong to
different feature classes, the Properties dialog box updates with the attribute values of
the next feature. Type the required attribute values, and click OK to process the next
feature.
If Copy values from matching attributes is turned on, the values of those attribute
fields (present in source and destination), which satisfy the matching criteria, are
copied to destination feature.
See "Selecting Features in the Map Window" in the Working with Features chapter.
10-47
10-48
Registering Data
GeoMedia Professional provides you with easy-to-use tools to capture new data. These
tools reduce the number of steps required to accomplish every task. With integrated vector
and raster snaps, you can capture vector data from raster images with accurate heads-up
digitizing. This product also allows table-top digitizing and vector transformation for
existing vector data that requires geometry transformation to match your database. This
chapter deals with tools that provide data registration: Digitizer Setup, Image
Registration, Output to GeoTIFF, and Vector Registration. These tools follow a
similar source-and-target data collection workflow with a similar graphic interface.
See the SmartSnap section in the Working with Features chapter.
Supported Digitizers
GeoMedia Professional supports all digitizer tablets that are Wintab32 compliant. This
means that if your digitizer was delivered with a Wintab32 driver (typically named
wintab32.dll) for Microsoft 32-bit operating systems (such as Windows XP), you should
be able use it with this product.
11-1
Note: GeoMedia works with any digitizer tablet that supports Wintab driver 1.0 or higher.
GeoMedia is designed to take advantage of enhanced button function assignments. Wintab
1.1 supports these enhanced functions, Wintab 1.0 does not. In addition, if Wintab 1.0
driver is in use, the operator can expect two additional limitations. First, there is no ability
to stream digitize with the tablet. Second, there are problems with double-clicking,
depending on the mode and the command being used. You cannot end a feature being
digitized by double clicking with the puck; double-clicking on the puck acts like a right
mouse click and sometimes exits the digitizer mode. There is, however, a workaround,
which is to use the mouse for double clicking. You should visit you tablet vendor's support
site for additional information.
The following list contains various manufacturers and their models of Wintab32-compliant
digitizers. However, you should contact your hardware vendor for a complete, current list.
Manufacturer
Acecad
Aristo
Calcomp
Digirule
Gtco
Hitachi
Kurta
Numonics
Summagraphics
Wacom
11-2
Models
A-1812
Geo Board
3300 series (DrawingBoard III)
3400 series (DrawingBoard II)
3100 series (DrawingSlate)
3200 series (DrawingSlate II)
EstiMat Roll-up
The RAT Model 1000
Ultima II
Roll-up
Sketch Master
AccuTabSuper L II
HDG 1212E
XGT series
SummaExpression
SummaExpert
SummaFlex
SummaPad
SummaSketch II
SummaSketch III
SummaSketch FX
SummaSketch LC961
SummaGrid IV
MicroGrid III
ArtZ II series
Registering Data
Note: To avoid the most common digitizer problems, verify that you install the latest
available Wintab32 driver and perform the installation according to the vendors
instructions.
You can collect the control-point pairs in several different ways, depending on your
workflow:
Collect all the digitizer (source) control points, and then collect all the corresponding
(target) control points, or vice versa.
Collect the control-point pairs by clicking Add Points on the New Digitizer Setup
dialog box and then following the prompts.
Collect control points graphically by clicking on the map in the map view (target) and
on the digitizer tablet (source). This automatically populates the grid on the New
Digitizer Setup dialog box with the corresponding values.
11-3
Type them directly into the grid on the dialog box or cut and paste them into the
Precision Coordinates dockable control if you know the actual coordinates of the
target control point.
After you collect all of your control-point pairs, you need to check their accuracy with the
Root Mean Square (RMS) value on the New Digitizer Setup dialog box. The RMS value
is a measure of the fit of the transformed source points as a whole for the whole set of
control-point pairs whenever their number meets or exceeds the minimum number for the
transformation. If the RMS error is too high, you need to experiment with the
Control/Check toggle of the Type column on the suspect pairs.
A control-point pair of the type Control is used in the registration calculation and
contributes to the overall RMS error value. A control-point pair of the type Check is
saved, but it is not used in the registration or RMS value calculation. Once you have found
the inaccurate control-point pair, you can either modify or delete it. Click Edit Source or
Edit Target to edit the respective control points by selecting a row and then clicking on a
new location for the control point.
Note: You need to have a digitizer installed at startup, and a digitizer tablet and digitizer
cursor attached to perform digitizer setup.
To create a new digitizer setup by entering all source control points first:
1. Secure your paper map to the digitizing surface of your digitizer.
2. Select Tools > Digitizer Setup to display the Registrations dialog box.
3. Click New to display the New Digitizer Setup dialog box.
4. Click Edit Source to close the dialog box and to display placement prompts.
5. Click an appropriate point on the digitizer to place digitizer control point 1.
Note: It is recommended that you mark your paper map with the control-point number
assigned by the software (in the # column on the New Digitizer Setup dialog box) for
later reference when entering the target control-point values.
6. Click the next appropriate point to place digitizer control point 2.
7. Continue placing control points until you have entered them all; then press the mouse
key assigned to the left double click action to complete source point placement.
The New Digitizer Setup dialog box is opened, with the X,Y coordinates of the placed
digitizer control point displayed.
8. Type the corresponding map control points directly into the control point grid on the
New Digitizer Setup dialog box.
11-4
Registering Data
9. Check the automatically calculated error in the Residuals field after you have entered
at least three control-point pairs. If it is not acceptable, use the Control/Check toggle
of the Type column to examine the effect each control point has on the total RMS
error.
Note: Those control points that reduce the total RMS error when toggled to Check
should be kept that way. Those control points that increase the total RMS error should
be toggled back to Control. The goal is to have the smallest RMS error that can be
obtained with a reasonable amount of time and effort. Also, you must have a
minimum of three control-point pairs with their type being Control.
10. Select the Type column in the grid to remove pairs with a high calculation error.
11. Type an appropriate name and an optional description for the digitizer setup in the
Name field on the New Digitizer Setup dialog box.
12. Click Register to save and to apply the digitizer setup.
13. Verify that the setup was successful with the name appearing in the list on the
Registrations dialog box.
11-5
9. Select the Type column in the grid to remove pairs with a high error from the
calculation; then edit individual control-point pairs using the editing steps that follow.
10. Type an appropriate name and an optional description for the digitizer setup.
11. Click Register to save and to apply the digitizer setup.
12. Verify that the setup was successful with the name appearing in the list on the
Registrations dialog box.
Select and delete a row in the control-point grid; then type the appropriate
information in a new row placed in the grid using Append.
Type edits directly into the control-point grid.
Select a row with the control points to be edited; then click Edit Source (to update
the digitizer control-point source value) or Edit Target (to update the map controlpoint target value).
11-6
Registering Data
Buttons 0, 1, and 2
When there are only three buttons on the cursor, you must be able to use the keyboard
simultaneously to carry out all the placement and editing tools. For example, to enter a
CTRL+Double Click, required for discontinuous feature placement, you would need to
hold down the CTRL key while pressing button 1 on the cursor.
11-8
Registering Data
Simulate metakey presses SHIFT and CTRL. For example, if the button assigned to
CTRL is pressed, all events coming from the cursor, until and including the next button
key pressed, will have a CTRL metakey mask.
Initiate and terminate tools commonly used during placement or editing actions, such
as Zoom In and Zoom Out.
Note: Command mapping is done at a level of indirection, thus allowing you more
flexibility. Instead of calling commands directly, the tracker command sends unused key
strings to the application, such as CTRL+ALT+w, which you can map through Tools >
Customize.
Button Number
3
4
5
6
7
8
9
10
11
12
13
14
15
Registering Images
Image Registration allows you to register a selected image by creating a new registration
or applying an existing registration. Creating a new image registration involves registering
an image to its real-world coordinates, that is, transforming raster points to map control
points. You can enter these points in any order and can collect them by placing data points
or by precision keyins.
This tool also allows you to re-register a selected image by editing the registration
originally used to register the image. In the process of creating or editing image
registration, you create or edit the control-point pairs. This tool is different from Digitizer
Setup and Vector Registration in that it changes the display matrix of the image but does
not change the data itself. In addition, this tool allows you to report on and to delete
11-9
previously saved image registrations. Image Registration currently uses only the Affine
transformation model.
To create a new image registration, a single image must be in the select set before you
select Image Registration. You must select an image to re-register it, and you must
register it manually with the Register button; the tool does not do it automatically.
After you collect all of your control points, you need to check their accuracy with the RMS
(Root Mean Square) value on the New Digitizer Setup dialog box. The RMS value is a
measure of the fit of the transformed source points as a whole for the whole set of control
points whenever the number of control points meets or exceeds the minimum number for
the transformation. If the RMS error is too high, you need to experiment with the
Control/Check toggle of the Type column on the suspect pairs. A control-point pair of
the type Control is used in the registration calculation and contributes to the overall RMS
error value. A control-point pair of the type Check is saved, but not used in the
registration or RMS value calculation. Once you have found the inaccurate control point,
you can either modify or delete it. Click Edit Source or Edit Target to edit the respective
control points by selecting a row and clicking on a new location for the control point.
Note: You must have at least one map view open during image registration and interactive
selection of control-point pairs. Also, control-point icons are displayed in all appropriate
open map windows.
4. Click New.
11-10
Registering Data
Click Add Points; then follow the prompts for adding control-point pairs. When
complete, double click to fill the grid with control-point pair coordinates.
Type the coordinates directly into the grid.
Click Add Points; then type the coordinate values into the Precision Coordinates
dockable control.
Collect all source points by clicking Edit Source; then add the target points by
typing them directly into the grid or by clicking Edit Target.
Collect all target points by clicking Edit Target; then add the source points by
typing them directly into the grid or by clicking Edit Source.
6. Check the calculated error in the Residuals field after you have entered at least three
control-point pairs. If it is not acceptable, use the Control/Check toggle of the Type
column to examine the error for individual control-point pairs.
7. Select the Type column in the grid to remove pairs with a high error from the
calculation; then edit individual control-point pairs using the editing steps that follow.
8. Type an appropriate name and an optional description for the registration.
9. Click Register to register the image.
OR
Click Save to save the registration without registering the image.
Registering Data
Outputting to GeoTIFF
Output to GeoTIFF takes a selected TIFF image and writes it out to a new GeoTIFF
image file containing geographic header information. The selected TIFF image is assumed
to display in the correct location. The image could have been inserted with Insert
Interactive Image and registered with Image Registration, or it could have been placed
using the Insert Georeferenced Images command. The output header information (also
called GeoTIFF tags) in the GeoTIFF file allows the image to be inserted in another
GeoWorkspace in the correct geographic location automatically with Insert
Georeferenced Images or to be used in other software packages that accept GeoTIFFformatted image files.
You can only select one raster at a time. Output to GeoTIFF makes a copy of the
originally selected file to the directory and filename specified. The original file is not
modified in any way. Then, the command writes new GeoTIFF tags (overwriting any
existing ones) to the header of the new image file. The command takes the coordinate
system of the GeoWorkspace and the associated raster matrix as input to write these
GeoTIFF tags.
By default, a companion world file is also created for the GepoTIFF file being output. The
world file has the same name as the new file, except with a .tfw extension. Thus, if an
application does not support GeoTIFF placement, it can use the world file. A world file is
simply the six necessary components of an Affine matrix that define the mapping from
pixel to world coordinates. Unlike the GeoTIFF tags, the world file does not include any
coordinate system information.
Output to GeoTIFF can write out to only certain projections and datums of coordinate
systems. Insert Georeferenced Images can, however, read almost any data that is
correctly defined within the GeoTIFF specifications. You can use GeoMedia and
GeoMedia Professional to insert any GeoTIFF image with Insert Georeferenced Images.
You can use GeoMedia Professional to output some TIFF images as GeoTIFF images as
long as the coordinate system is one of those supported by Output to GeoTIFF.
See the Coordinate System Information appendix for a list of supported coordinate
systems for writing GeoTIFF files.
To output to GeoTIFF:
1. To insert a TIFF image without any existing GeoTIFF tags, select either Insert >
Interactive Image (Continue with Step 2.).
OR
Select Insert > Georeferenced Images (Go to Step 3.).
2. Register the image with Image Registration to the correct geographic location.
11-13
OR
Move the image to the correct location.
3. Select the image.
4. Select Warehouse > Output to GeoTIFF.
5. On the Save As GeoTIFF dialog box, select the appropriate folder to which to save the
file.
6. Type an appropriate filename; then click OK.
Registering Data
unique key field cannot have duplicates in the target feature after the new features have
been added.
Note: For this command to work properly, the features being transformed must have a
coordinate system defined. If you are using ARC/INFO, ArcView, or MapInfo as a data
source, you must specify in an .ini file a coordinate system file that matches the coordinate
system the features were originally collected in.
This is a representative workflow for registering vector data:
1. Input the features to be transformed and the features for identifying the target
transformation location.
2. Specify the transformation parameters.
3. Identify the source and destination control points.
4. Review the transformation, and make corrections if necessary.
5. Perform the actual transformation.
To create a new vector registration and to register source vector data for
review and output feature:
1. Connect to an appropriate source warehouse.
2. Open a source map view, and display the source features you want to transform in the
source map view.
Note: You can further specify features with connection filters or any query conditions.
3. Connect to the target warehouse/server as read-write.
4. Open a target map view.
5. Display various target features in the target map view.
6. Select Tools > Vector Registration.
11-15
7. Click New.
8. Click Add Points; then follow the prompts to register the source features against the
target features by choosing corresponding control-point pairs.
9. Check the residual errors, and make corrections if necessary.
10. Click Transform.
11-16
Registering Data
11. Select the correct source feature class from the Transform features in drop-down list.
12. Verify that the Output as option is set to Review.
13. Optional: Click Style to open the Style Definition dialog box and customize your
display; then click OK.
14. Select the appropriate map window from the Map window name drop-down list to
display the source features and target features in a map view.
15. Click Apply on the Vector Transformation dialog box to review the transformation.
16. Visually check the placement of the transformed feature against the base feature
display.
17. If the transformation is not acceptable, edit the transformation control points, repeat the
process, and again check the results.
OR
If the transformation is acceptable, press ESC to return the Vector Transformation
dialog box; then select the Feature class output option.
18. Select the appropriate connection from the Connection drop-down list.
19. Select the appropriate feature class from the Feature class drop-down list, or type a
new feature class name in the field.
20. Optional: Type a description in the Description field.
21. Click Apply to perform the transformation.
22. Click Close to close the Vector Transformation dialog box.
OR
Continue by specifying each additional source feature class in turn, and use the
specified registration to transform it directly into the output feature table.
11-17
11-18
The display of the anomalies in the map and data windows allows you to make use of the
powerful GeoMedia Professional function, dynamic queued editing. Dynamic queued
editing presents each problem in sequence, so you do not have to perform time-consuming
searches. Then as you fix each problem, the queue is automatically updated. If you fix a
problem in the data window, the solution is automatically reflected in the map window and
vice versa. Also, if you create a feature or an error while editing in one window, this is
reflected in the other window, too.
When you are validating or editing, the GeoWorkspace coordinate system and the
warehouse coordinate system should be the same. All calculations are performed in the
warehouse coordinate system. It is possible that anomalies between two geometries in the
warehouse may not visually look like anomalies when displayed on a map that is in a
different coordinate system. Also, an edit that looks good on a map may not be sufficient
to resolve an anomaly in the warehouse.
An output query produced by Validate Geometry and Validate Connectivity remains
dynamic until you:
If you do not perform the above, leaving active queries lowers system performance,
especially when you have several active queries running at the same time.
See Changing Map Window Properties in the Working with Map Windows chapter.
12-2
Determine the geometry type of a feature, for example, a polyline, two-point line, arc,
polygon boundary, or hole in a polygon.
Determine if a feature consists of more than one geometry. For example, a feature can
be a composite geometry made up of a polyline and an arc.
To display the geometry information, you select a feature from a map window or a data
window, and the corresponding geometry highlights in all windows. You can configure
the style of the highlight display and the format of the coordinate information. As
individual pieces of the geometry are selected and highlighted in the treeview, they are also
highlighted in the map window as in the following figure.
This command honors the Maintain coincidence option on Placement and Editing tab
(Tools > Options). If this option is checked, and a vertex of geometry is selected in the
treeview, the command highlights all the other geometries that are coincident with the
selected vertex as in the following figure. If a coincident vertex is deleted, this vertex is
deleted from all the editable coincident geometries.
12-3
Displays
Start Point, Origin Point, End Point, Mid Point,
Normal Vector, Radius, Sweep Angle, Arc Length,
Chord Length
Exterior Geometry, Geometry Collection of Holes
List of Geometries
List of Geometries
List of Geometries
Start Point, End Point
Four Column Vectors
Origin Point, Orientation Vector
x, y, z
List of Points
List of Points
Filename, Display Matrix, Raster Polygon
Origin Point, Height, Width, Rotational Vector,
Normal Vector
Text String and x, y, z
i, j, k
Editing Geometry
The right mouse editing menu lets you edit the selected geometry in the treeview of the
Geometry Information dialog box, but only if the selected feature is from a read-write
warehouse. For each valid edit operation, all the associated views are refreshed to reflect
the change.
12-4
Supported
Geometry Types
Delete
(vertex)
A vertex from a
supported geometry
type is selected on
the dialog box, if
standalone or part
of a geometry
collection.
Geometry
collection
Boundary
geometry
holes
collection
Standard text
collection
Nested text
collection
Polyline
Polygon
Boundary
Composite
polyline
Composite
polygon
Processing
Constituent
geometry is
deleted.
Vertex is
deleted from
the geometry.
Special Rules
If the edited geometry
may result in a
conversion to a simpler
geometry, single
member collections and
zero member holes
collections (that is,
boundary converted to
polygon or composite
polygon) are converted.
If the selected vertex of
a composite polyline or
composite polygon is
on an arc, or is a vertex
shared by consecutive
members of the
composite, this
command is disabled.
12-5
Reverse
Move
One of the
supported
geometry types is
selected on the
dialog box, if
standalone or part
of a geometry
collection.
Constituent
geometry of a
supported
geometry type is
selected on the
dialog box.
Line
Arc
Polyline
Composite
polyline
Geometry
collection
Boundary
geometry
holes
collection
Standard text
collection
Nested text
collection
See Reversing Direction in this chapter.
Order of the
vertices is
reversed.
N/A
Order of the
constituent
geometry
within the
collection is
altered as
specified.
N/A
Text collection handling recognizes a composite text collection, and the full text string is
presented at the collection level of the treeview, while each letter is also presented with its
own origin and orientation.
The color and the weight of the highlight display in map windows.
12-6
Note: This dialog box is resizable, and wraps tooltip text to multiple lines when
needed for exceptionally lengthy text.
5. Optional: Click the right mouse button to open the edit menu; then make the
appropriate edits.
For each valid edit operation, all the associated views are refreshed to reflect the
change.
Note: You can also perform deletes by pressing the DELETE key.
6. Optional: Click Options to change the map window and coordinate displays.
7. Repeat Steps 4 through 6 until the appropriate results have been displayed.
12-7
Validating Geometry
Validate Geometry finds geometry errors in the GeoMedia Professional data model that
will cause problems in other processes. For example, you cannot perform buffer zoning on
an area with a loop. These errors may not prevent subsequent processing from running
successfully because some error conditions are ignored; however, the results may be
unexpected.
Examples of such errors are areas closing on themselves, coincident sequential points in
linestrings, and holes crossing area boundaries. You should run this tool on all your data
as an initial cleanup step, especially if you import the data from another source, such as
design files, ARC/INFO, and ArcView. You then need to fix the detected geometry errors
by using the appropriate editing tools.
You access Validate Geometry from the Tools menu and input a feature class or query
containing the features for which geometry is to be validated. Each record from the input
feature class or query may have zero, one, or more anomalies. Next, you specify the output
query and its display. This tool displays the output query to a map window containing
geometric depictions of the location and nature of the anomalies and/or a data window
containing a text description of the anomalies. You also have the option of changing the
default display style of the map window for optimum results.
Definition
Kickback and
Duplicate
Point
Loop
Unclosed
Area
12-8
An area boundary or hole that does not close on itself, that is, the last
vertex does not equal the first vertex.
Error
Definition
Uncontained
Hole
Overlapping
Holes
Invalid
Geometry
Type
Actual geometry stored in a GDO field that does not match the GDO
type/subtype definition.
Empty
Geometry
Collection
Too Few
Vertices
Unknown
Geometry
Type
Invalid
Coordinates
To validate geometry:
1. Connect to a read-write warehouse.
2. Select Tools > Validate Geometry.
3. Select the feature class or query for which to validate geometry from the Validate
geometry contained in drop-down list.
12-9
4. Verify, and change if appropriate, the default name <Feature> anomalies assigned to
the output record set in the Query name field.
5. Optional: Type a query description in the Description field.
6. Verify that the Display results in map window box is checked in the Map window
name area, and change, if appropriate, the default active map window in which to
display the results.
OR
To not display the results in a map window, click the Display results in map window
box to remove the checkmark.
7. Optional: Click Style, and change the default style on the Select Style dialog box.
8. Verify that the Display results in data window box is checked in the Data window
name area, and change, if appropriate, the default new data window in which to
display the results.
OR
To not display the results in a data window, click the Display results in data window
box to remove the checkmark.
9. Click OK to perform geometry validation.
Validation processing is performed in the selected feature class or query, and an
output query is produced with the query name from the dialog box.
If the map window display check box was selected, the map window with the anomalies
is displayed. If the data window display check box was selected, the data window with
the anomalies is displayed.
10. If you have a map window, set its properties for display of each error found. If you
have two windows, you can tile them vertically for ease of use. Perform the
appropriate maintenance on the errors found.
12-10
Fixing Geometry
Fix Geometry allows you to automatically correct duplicate points and kickbacks
geometry problems found by having first run the Validate Geometry command, which
outputs the errors as a query. There must be at least one such query to be able to run Fix
Geometry. Thus, the Validate Geometry query becomes the input for Fix Geometry.
Fix Geometry fixes what it can and leaves the residual problems for manual fixing. The
automatic fixing process is similar to the manual fixing process in that it makes edits to the
original geometry, broadcasts changes to the database, re-evaluates the edited geometry
through notification, and, if the anomaly has been fixed, it removes the anomaly from the
Validate Geometry query.
Other errors found by Validate Geometry cannot be automatically corrected; they require
your intervention to be resolved. You can use the output query with the Map Window
Properties command and the data window to set up a queuing workflow for scrolling
through the list of anomalies and for correcting them with Extend to Intersection, Trim
to Intersection, Insert Intersection, and other geometry editing commands if necessary.
To fix geometry:
1. Run Tools > Validate Geometry to determine the types of problems associated with
your data.
2. Select Tools > Fix Geometry.
3. Select a query from the Fix geometry errors in drop-down list of Validate Geometry
anomaly queries.
4. Select the appropriate Errors to fix check box(es), Duplicate points and/or
Kickbacks.
Note: If there are no duplicate points or kickbacks, an error message is displayed.
5. Click OK.
The message Fixing <query name> and a progress bar are displayed as the geometry
problems are automatically fixed; then a message is displayed with statistics on the
number of problems fixed per selected option.
12-11
Note: You can stop processing at any point by pressing ESC; however, this does not
undo any fixes that have already been made.
6. Optional: Manually fix those problems that could not be fixed automatically.
Validating Connectivity
Validate Connectivity finds anomalous conditions caused by inaccurate digitizing, such as
undershoots and overshoots. These conditions are not necessarily errors, but they should
be examined to see if they need to be corrected to ensure that your data are clean. You
access Validate Connectivity from the Tools menu.
The digitizing and editing tools of the software (such as SmartSnap, automatic break, and
automatic maintenance of coincidence) are designed to allow you to collect clean data the
first time rather than having to clean up problems as a post-process. Thus, creating and
editing features within the software usually result in a relatively small number of
connectivity errors. Some errors are inevitable, however, especially those involving
coincidence and automatic breaking. The connectivity validation tools are designed to find
these problems.
Data brought in from other sources, such as CAD files, that have been spaghetti digitized
without much attention to connectivity often include a large number of connectivity errors
such as undershoots, overshoots, node mismatches, and slivers. Validate Connectivity
also locates these problems.
This command takes two feature classes and/or queries as input and creates a new query
containing any connectivity errors as output. The input can be the same feature class or
query (for example, Street versus Street, in which case you validate connectivity between
features within the same feature class) or a combination (for example, Street versus
Railroad).
You can display the output query in a map window or in a new data window containing a
text description of the anomalies. When outputting to a map window, you have the option
of changing the default display style of the connectivity errors.
You can use the output query with the Map Window Properties command and the data
window to set up a queuing workflow for scrolling through the list of anomalies and for
correcting them with Extend to Intersection, Trim to Intersection, Insert Intersection,
and other geometry editing commands if necessary. You can also use the Fix
Connectivity command to automatically correct connectivity problems.
Because the query is dynamic, the software automatically removes errors from the map
window and the data window as they are corrected so you do not have to run the validation
command again to see the updates. Similarly, a placement or edit operation that creates a
new error is automatically displayed without having to run the validation command again.
Validate Connectivity detects the following potential error conditions:
12-12
Undershoots
Overshoots
Node mismatches
Note: If you select both the unbroken intersecting geometry and the non-coincident
intersecting geometry conditions, the unbroken intersecting geometry takes precedence.
It is strongly recommended that you use Validate Connectivity in an iterative manner.
You should first select one validation condition most appropriate for your purposes, run the
command, and then change the query parameters by editing the query to further refine the
validation. Thus, you would alternate commands, checking one validation condition at a
time. If you use Validate Connectivity with many validation conditions in one run, the
output query may contain an excess of anomalies for you to work with at one time.
See Fixing Connectivity in this chapter.
Connectivity Conditions
Validate Connectivity allows you to choose from among six connectivity conditions to be
found for the selected feature classes/queries and to define the distance tolerance to be used
to search for errors.
Note: In the following examples, the squares represent how the different conditions are
symbolized. You can select any point style with the style dialog box for the legend entry.
Overshoot
This condition occurs when the end of a linear geometry extends beyond the point at
which it should intersect with, and stop at, another geometry.
Undershoot
This condition occurs when the end of linear geometry or a point geometry falls short of
intersecting another geometry.
Node Mismatch
12-13
This condition occurs when the end of a linear or point geometry falls short of intersecting
with the end of another linear or point geometry.
(Intersection not broken, intersection not coincident. If all these switches are on, overshoot
takes precedence.)
Undershoot
Node Mismatch
Node Mismatch Undershoot
Nearly Coincident
Nearly Coincident
Intersection Not Broken
Overshoot
Node Mismatch
Nearly Coincident
Undershoot
Nearly Coincident
Node Mismatch
Nearly Coincident
Intersection Not Broken
Nearly Coincident
Nearly Coincident
Intersections Not Coincident
Nearly Coincident
Nearly Coincident
12-16
Node Mismatch
Node Mismatch
Undershoot
To validate connectivity:
1. Open a read-write warehouse.
2. Select Tools > Validate Connectivity.
12-17
3. Select the feature class(es) or the quer(ies) for which geometry is to be validated from
the Features in drop-down lists, in the Validate connectivity between selection area.
4. If you want to validate connectivity within a single feature class/query, you must enter
the same feature class or query in the two input fields. (The only way to validate
within a feature class is to enter the same one in both fields.)
5. Select the appropriate Find check boxes for the conditions to be found.
6. Type the appropriate tolerance value in the Tolerance field, and select the appropriate
unit of measure.
7. Verify, and change if necessary, the default query name for the output query in the
Query name field.
8. Optional: Type a query description in the Description field.
9. Verify that the Display results in map window check box is checked 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. Optional: Click Style, and change the default style on the Style Definition dialog box.
11. Verify that the Display results in data window check box is checked 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.
12. Click OK to validate connectivity.
Validation processing is performed in the selected feature class and/or query, and an
output query is produced with the query name from the dialog box.
12-18
If the map window display check box was selected, the map window with the anomalies
is displayed. If the data window display check box was selected, the data window with
the anomalies is displayed.
13. If you have a map window, set its properties for display of each error found. If you
have two windows, tile them vertically for ease of use. Perform the appropriate
maintenance of the conditions found.
14. Optional: Change the query parameters to further refine the validation.
Select Analysis > Queries, select the query on the Queries dialog box; then click
Edit. Edit the query, and run Validate Connectivity again.
Fixing Connectivity
Fix Connectivity allows you to automatically correct connectivity problems for polylines,
polygons, and boundary geometries by:
Trimming overshoots
Extending undershoots
You identify these problems by having first run Validate Connectivity, which outputs an
anomaly query. There must be at least one such query to be able to run Fix Connectivity.
The Validate Connectivity query in turn becomes the input for Fix Connectivity, which
fixes what it can and leaves the residual problems for manual fixing. The automatic fixing
process is similar to the manual fixing process in that it makes edits to the original
geometry, broadcasts the changes to the database, re-evaluates the edited geometry through
notification, and, if the anomaly has been fixed, it removes the anomaly from the Validate
Connectivity query. Fix Connectivity honors the Break linear features options on the
Placement and Editing tab of the Options dialog box (Tools > Options).
12-19
12-20
Line A was broken into two segments, A and C, at the intersection with line B. Because
Line C is now a separate feature, it is no longer detected as an overshoot.
Infinite Loops
In a few situations, Fix Connectivity can get caught in an infinite loop. If this happens,
you can easily exit the command by pressing ESC. You can then restart the command
using different options. You may also want to change the detection options on the query
through the Edit Query command.
The following is an example that results in an infinite loop:
Line A overshoots line B. Line A is trimmed to Line B. Line A undershoots line C. Line
A is extended to Line C. Line A overshoots Line B, and so forth into an infinite loop.
To fix conectivity:
1. Run Tools > Validate Connectivity to determine the types of problems associated
with your data.
2. Use Edit Query to change parameters and/or tolerances for the Validate Connectivity
output query.
3. Select Tools > Fix Connectivity.
12-21
4. Select a query from the Fix connectivity errors in drop-down list of Validate
Connectivity anomaly queries.
5. Select any or all of the Connectivity errors to fix check boxes.
Note: Depending on the types of problems, fixing one type at a time may reduce
possible errors.
6. Click OK.
The message Fixing <query name> and a progress bar are displayed as the
connectivity problems are automatically fixed; then a message is displayed with
statistics on the number of problems fixed per selected option.
Note: You can stop processing at any point by pressing ESC; however, this does not
undo any fixes that have already been made.
7. Optional: Manually fix those problems that could not be fixed automatically.
Extending Geometry
Extend lets you extend linear features the exact distance you need. You can specify this
distance dynamically by moving the cursor in the map window or by typing the distance on
the command dockable control. Extend is similar to the Extend to Intersection
command, but it does not require that the extension occur to the point of intersection with
another feature in the map window.
You can click in any open map window to determine the extension. Clicking selects the
feature, the geometry of the feature to be extended, and the end of the geometry to be
extended. The feature being processed extends dynamically as you move the cursor. The
distance of the extension is determined by a perpendicular projection of the current
location of the cursor to the imaginary extension of the linear segment.
The Extend dockable control dynamically shows the distance based on the cursor location.
This control also allows you to type the extension distance. The distance units on the
12-22
control are determined by the distance units set on the Units and Formats tab of the
GeoWorkspace Coordinate System dialog box.
This command supports the extension of lines (converts to polyline), polylines, composite
polylines, and arcs. When an arc is extended, the sweep angle of the arc is increased as the
cursor is moved, up to the maximum sweep angle. Geometry collections are also
supported.
Extend honors the coincident settings, properties, and break settings on the Placement
and Editing tab of the Options dialog box. It also honors auto pan and on-element
snapping when extending, and you can undo/redo the results of an extend operation with
the Undo/Redo commands.
To extend geometry:
1. Connect to a read-write warehouse.
2. Select Edit > Geometry > Extend.
8. Click to extend.
The feature is extended the specified distance, and a vertex is placed at the point of
extension. If the new vertex was snapped onto an existing feature (though an onelement snap only), coincidence and/or break processing are performed if those
options are set.
9. Select another feature, or press ESCAPE to exit the command.
If you place the cursor on a linear feature that has no close features in both directions, the
figure does not highlight.
12-24
12-25
The figure on the left shows the case where the intersection lies within the end segment of
one of the linear features. In this case, one linear feature will be trimmed and one linear
feature will be extended as shown in the highlighted path. The figure on the right shows
the tentative path where both linear features are extended to the intersection point.
This command supports the extension of lines (converts to polyline), polylines, composite
polylines, arcs, and geometry collections. When an arc is extended, the tangent to the end
point is extended from the end point to the intersection, and the arc geometry becomes a
composite polyline. When an arc is trimmed, the sweep angle of the arc is simply
decreased.
When you move the mouse cursor with this command active, if only one feature is within
the locate tolerance at the cursor location, that feature is highlighted. If multiple features
are within the locate tolerance at the cursor position, none of the features are highlighted,
and an ellipsis is displayed for you to select the appropriate feature through the PickQuick
dialog box.
The location of the click selects the feature to be extended, the particular component
geometry of the feature to be extended (in the case of a geometry collection), and the end
of the geometry to be extended. When you select two valid linear features, the
extended/trimmed path is shown in the map window, and you are prompted to click to
accept.
This command supports the AutoPan, coincidence, and break settings. In order to make
feature selection easier in congested areas, it also supports PickQuick. You can also
access viewing commands while the command is active, and you can undo/redo the results
of an extend operation with the Undo/Redo commands. Pressing ESC deselects features.
The end of the selected linear feature that is closest in proximity to the cursor location
at the time of the click is the end that is extended/trimmed to intersect with another
linear feature.
OR
If multiple features are within the locate tolerance, click to display the PickQuick
dialog box, and choose the appropriate feature.
The end of the selected linear feature closest in proximity to the cursor location at the
time PickQuick displays is the end that is extended/trimmed.
4. Repeat Steps 2 and 3 to select another linear feature. However, it is not necessary to
click to select the highlighted feature; simply hover the cursor over the other linear
feature to be extended.
If a projected intersection point can be computed for the two selected features, the
tentative extensions of the selected features are highlighted.
However, if no intersection point can be computed, you are prompted to select another
feature (repeat Steps 2 and 3).
5. Click to accept the extensions of the selected features to the projected intersection
point.
Trimming Geometry
Trim allows you to trim linear features the exact distance you need. You can specify this
distance dynamically by moving the cursor in the map window or by typing the distance on
the command dockable control. Trim is similar to the Trim to Intersection command,
but it does not require that the trimming occur at the intersection of another feature in the
map window.
You can click in any open map window to determine the trim. Clicking selects the feature,
the geometry of the feature to be trimmed, and the end of the geometry to be trimmed. The
feature being processed trims dynamically as you move the cursor. Trimming is not
limited to the selected end segment of the linear feature.
The Trim dockable control dynamically shows the distance based on the cursor location.
This control also allows you to type the trim distance. The distance is a negative value
when the feature is being trimmed. If you type a negative distance greater than the length
of the feature, a message is displayed and the trim does not occur. The distance units on
the control are determined by the distance units set on the Units and Formats tab of the
GeoWorkspace Coordinate System dialog box.
This command supports the trimming of lines, polylines, composite polylines, and arcs.
When an arc is trimmed, the sweep angle of the arc is decreased as the cursor is moved.
Geometry collections are also supported.
12-27
Trim honors the coincident settings, properties, and break settings on the Placement and
Editing tab of the Options dialog box. It also honors auto pan, vector snap with snap
glyphs displayed, and on-element snapping when trimming.
To trim geometry:
1. Connect to a read-write warehouse.
2. Select Edit > Geometry > Trim.
Intersecting feature =
If you place the cursor on a linear feature that has no intersection points on both directions,
the feature is not highlighted and there is no trim action.
Case 2. Intersection: One linear feature intersecting with another linear feature.
12-29
If the break option is on, the intersecting feature has to break with respect to the
intersection point into two linear features. These two broken features take the attributes
that you or the software enter.
Inserting Intersections
Insert Intersection inserts a vertex at the intersection point of two or more crossing
geometries. The geometries can be from a linear feature, a point feature, or an area
boundary. This tool is modeless, so you can process multiple inserts without restarting it.
You access Insert Intersection from the Edit menu.
Selecting this tool clears the select set of any selected items. You then move the cursor
over a feature in the area of the intersection with another feature. If the feature classes are
editable, the tool highlights and calculates the closest intersection point. The search for an
12-30
intersection stops at the boundary of the active map view; if there is no intersection, no
highlighting occurs. You use a data point to accept the intersection.
If one or more of the intersecting features is read-only, the tool inserts the intersection into
all features that can be written to and ignores the read-only features. This tool modifies
existing geometry, so it uses the height values of the existing geometry. The height value
for the inserted points will be on the original geometries.
Insert Intersection honors the settings on the Placement and Editing tab except
coincidence. If coincidence is turned off, this tool still places a vertex at the intersection.
Insert Intersection overrides coincidence because it is intended to insert vertices.
This tool honors the Break linear features settings as follows:
Break all feature
classes
Break same
feature class only
Action
Yes
Yes
No
Yes
Yes
No
You also have the option to type the attributes of the broken features on the Properties
dialog box or to let the software do it automatically. You can set these provisions on the
Placement and Editing tab of the Options dialog box. This tool does not honor the
coincidence setting on this tab. It always inserts a vertex on all features at the located
intersection regardless of the coincident setting.
12-31
Solutions
For all the following cases, assume F1 to be the located feature.
Case 1. Same feature class (linear).
Break same feature class: F1 is broken at the intersection; F2 is not broken but a vertex is
inserted at the intersection.
Break all feature classes: F1 and F2 are broken at the intersection.
Break off: Vertex is inserted on F1 and F2 at the intersection.
Case 3: Line and area features.
Break same feature class: Neither F1 or F2 is broken, but a vertex is inserted at the
intersection on both features.
Break all feature classes: F2 is broken at the intersection; F1 is not broken, but a vertex is
inserted at the intersection.
Break off: Vertex is inserted on F1 and F2 at the intersection.
Case 4: Two area features.
Break same feature class: Neither F1 or F2 is broken, but a vertex is inserted at the
intersection on both features.
Break all feature classes: Neither F1 or F2 is broken, but a vertex is inserted at the
intersection of both features.
12-32
To insert intersections:
1. Connect to a read-write warehouse.
2. Display the linear features in a map window.
3. Optional: Select Tools > Options, and set the appropriate Placement and Editing tab
options.
4. Select Edit > Geometry > Insert Intersection.
5. Hold the cursor over the feature near the intersecting geometry.
A point is placed in dynamics at the closest intersection.
6. Click the highlighted feature to accept the intersection.
Vertices are added to all features at the intersection point regardless of coincidence
setting.
If the Break within same feature class only option is on and the intersecting features
are the same feature class, they are broken into two features. If the Break all feature
classes option is on, all features that intersect are broken into two features at the
intersection point.
If the Display Properties dialog for new features option is on, the Properties dialog is
opened for each new feature created by a break operation, and the new feature is
highlighted in the map window. The dialog box is displayed whether the setting is on
or off if there are required values that cannot be automatically populated for the new
feature.
The relevant map window, data window, and queries are updated, and the cursor waits
for further input for inserting intersections.
7. Double click to exit Insert Intersections.
You can also choose to trim the excess of both segments at their point of tangency with the
fillet.
12-33
Starting this command displays its dockable control, which contains a feature selection
drop-down list of the linear feature classes available for the constructed fillet. It also
contains a Radius field and a Lock check box. If the Lock check box is unchecked, the
Radius field provides a dynamic readout of the radius of the fillet being constructed,
based on the cursor location. If the Lock check box is checked, the radius of the fillet
being constructed is restricted to the value in the Radius field and does not change as the
cursor is moved. Additionally, the Trim excess check box let you choose to trim the
excess of both selected segments at their point of tangency with the fillet.
Note: The arc created can be a member of a new feature class or the same feature class as
the feature being edited. This is controlled by the Trim excess check box.
Construct Circular Fillet supports the construction of a fillet between two line segments
that can be lines, polylines, composite polylines, polygons, composite polygons, and
geometry collections. In the cases of polygons or composite polygons, if you choose to
trim the excess, and the two line segments that you select to construct the circular fillet
cannot be trimmed in the context of polygons or composite polygons (for example, the two
line segments are contained in different polygons), the fillet is inserted as a standalone
feature, and the original selected feature(s) is not trimmed.
The selected two segments can be on the same feature instance. In this case, if you choose
to trim the excess, the constructed fillet merges with the selected trimmed segments into
the same feature instance, and no new feature instance is generated. However, if you
choose to not trim the excess, a new standalone feature instance is inserted for the
constructed fillet. You can select the feature class for the new segment.
In addition, this command supports the following functionality:
12-34
Coincidence and break settings when you choose not to trim the excess
Properties settings
AutoPan
Undo/Redo commands
Clicking in any open map window to select a segment and to determine and to place a
fillet
Reversing Direction
The Reverse Direction command allows you to resolve digitizing problems in geometry
by reversing the direction of a geometry or composite geometry of a selected feature. This
command is useful, for example, in the maintenance of sewer data, where the digitizing
order defines the flow of water.
You must have a select set containing at least one feature from a read-write connection to
use this command; geometries from read-only connections are ignored. However, you can
specify one or more features from multiple feature classes from more than one read-write
warehouse connection in a select set as the input.
Reverse Direction only reverses the direction for each of the linear features that exists in
an input select set; it ignores other geometry types if any are present. If no linear features
exist in the select set, the command displays an information message and terminates.
The reversal performed by this command may not, however, change the display in the map
window, depending on the style of the linear feature class. Consequently, you can use the
Geometry Information command before and after changing the line orientation to verify
that the order of the vertices has indeed changed and for viewing the linear direction for
single edges.
An alternative to using Geometry Information is to change the line style of the linear
feature so that you can more easily view the direction. If you change the style to include
an arrow symbol, the arrows are reversed so that you can easily verify the change in line
orientation.
To reverse direction:
1. Select the appropriate linear feature(s).
2. Select Edit > Geometry > Reverse Direction.
Note: You can also access this command from the right mouse edit menu within the
Geometry Information command. However, when accessed this way, it behaves
differently, being restricted to the single element already highlighted.
12-36
3. Optional: Select Tools > Geometry Information to verify that the order of the
vertices has been reversed if you have not changed the line style to aid in visual
verification.
12-37
12-38
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.
13-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.
Equals
>=
Less than or equal to
<>
Greater than
<
Parentheses for grouping expressions
Logical and between two expressions
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.
13-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;
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 queriesand possibly othersyou must manually
edit the SQL text on the Filter dialog box to issue a successful query.
13-3
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,
Long, Single,
Double, Currency
Boolean
Date
Show Values
Display and
Entry
User-defined
format (General
Number, Fixed,
Standard,
Currency, or
Percent)
User-defined format
(Yes/No, etc.,
custom)
User-defined
format (Date,
Time, Date/Time)
Attribute Filter
Pipe SQL
Standard format,
delimit with single
quotes, replace
embedded single quotes
with consecutive single
quotes
General Number
format, not
delimited
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
13-4
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
server SQL
See Attribute
Filter Pipe.
ArcView GDO
server SQL
See Attribute
Filter Pipe.
MapInfo GDO
server SQL
See Attribute
Filter Pipe.
CAD GDO
server SQL
See Attribute
Filter Pipe.
FRAMME GDO
server SQL
Not supported
Note: Date value expressed as MM/DD/YY, delimited by single quotes; time values are not supported.
MGE GDO
server SQL
See ODBC
Tabular GDO
server.
MGSM GDO
server SQL
Not supported
See Attribute
Filter Pipe.
Oracle Object
GDO server SQL
See Attribute
Filter Pipe.
ODBC Tabular
GDO server SQL
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 userdefined 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.
13-5
SQL Server
GDO server SQL
See Attribute
Filter 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.
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.
13-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 encounteredthat 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 queriesand possibly otherson 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.
13-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.
12. Optional: Click Style, and change the default style on the Select Style dialog 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.
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.
13-8
Touch returns features that touch the defined features in any waymeeting, 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
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
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
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
13-9
Meet returns features that fall next to the defined features, touching without overlapping.
meet
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
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
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.
2. From the Select features in drop-down list, select a feature class or query.
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.
10. 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.
11. Optional: Click Style, and change the default style on the Select Style dialog box.
12. 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
13-11
To not display the query results in a data window, uncheck the Display query in data
window box.
13. To display the query, click OK.
The query is displayed in accordance with the query options you set.
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:
13-12
Spatial Intersection results with the touch operator showing the intersection of the Major
Water Polygons features and the Parks features:
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.
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.
6. Optional: Click Filter to define an attribute filter for the selected feature class on the
attribute filter dialog box.
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. Optional: Click Style, and change the default style on the Select Style dialog box.
13-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.
Subtract-feature
area
area
Result
area or nothing
line or nothing
13-15
line
point
point
point
line
area
line
point
line or nothing
point or nothing
point or nothing
point or nothing
Subtract-feature
line
point
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.
13-16
2. Select the feature class to be masked from the From 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. Select the feature class to be used as a mask from the Subtract features in drop-down
list.
5. Optional: Click Filter to define an attribute filter for the selected feature class on the
attribute filter dialog box.
13-17
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:
TouchThe boundaries intersect but the interiors do not.
13-19
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.
13-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.
10. Verify that the Display query 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 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.
11. Optional: Click Style, and change the default style on the Select Style dialog box.
12. Verify that the Display query 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 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
window and/or data window.
Note: If you do not select either a map window or a data window, the query is only
appended to the query folder.
13-21
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.
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.
7. Accept the default query name, or type an appropriate name in the Query name field.
8. Optional: Type an appropriate query description in the Description field.
13-23
9. Verify that the Display query 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 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.
10. Optional: Click Style, and change the default style on the Select Style dialog box.
11. Verify that the Display query 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 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
window and/or data window.
Note: If you do not select either a map window or a data window, the query is only
appended to the query folder.
13-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.
13-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.
20. To display the query, click OK.
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.
13-26
Displaying Queries
In general, a query is displayed automatically when you build it. If you build a query
without displaying itto use in another query or for creating a thematic display, for
examplethere 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
Line
13-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:
13-28
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.
To edit a query:
1. Select Analysis > Queries.
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 Professional version 4.0 and
earlier or in GeoMedia Professional version 4.0 Service Pack 1.
See GeoMedia Professional 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:
1. Select Analysis > Queries.
2. On the Queries dialog box, select the query or queries you want to delete and click
Delete.
13-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:
1. Select Analysis > Queries.
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.
13-30
Define filter geometry and perform spatial filtering at the GeoWorkspace level.
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.
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.
13-31
Select Set
Rectangular Fence
Polygonal Fence
Circular Fence
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:
13-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.
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.
13-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.
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.
Remove Filter
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.
13-36
Entirely InsideLets you access only data that falls completely within the boundaries of
your spatial filter geometry.
Inside
Entirely Inside
Coarse OverlapLets 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.
OverlapLets you access any feature that falls within or touches the boundaries of your
spatial filter geometry.
13-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.
13-38
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.
13-39
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
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 systemdefined 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.
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.
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.
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.
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.
13-42
7. Select Alabama from as the feature to use as a spatial filter; then click OK to perform the
filtering.
13-43
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 Professional Help for setting
the MAPID IS RELIABLE keyword in the mge.ini file.
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.
13-44
13-45
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:
Delete queues
Create subqueues
Access additional options and commands to manipulate the standard review items and
queues
13-46
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.
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.
13-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%.
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.
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.
13-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.
Note: Delete Queue, Create subqueue, and Show statistics are enabled when a
GeoWorkspace is open, whether a queue is selected or not.
Delete queueDeletes 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.
13-52
Create subqueueCreates 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 statisticsDisplays 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
13-53
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.
Delete queue items by statusDeletes 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.
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/descendingSort 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.
13-54
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.
13-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
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.
13-56
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.
Finally, selecting one or more searches on the Searches dialog box and clicking Delete
deletes the selected search(es).
13-57
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.
13-58
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.
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.
13-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.
13-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.
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).
See Setting View Options in the Working with Queued Edit section of this chapter for
more information on using this dialog box.
13-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
Left outer
join
Right outer
join
Full outer
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.
13-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).
13-64
See GeoMedia Professional 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
window and/or data window.
The statistics available are as follows:
2
13-65
Raster featuresnone
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 Professional 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 Professional 3.0 continue
to be computed in the warehouse coordinate system. Only new (GeoMedia Professional
4.0 and higher) queries are computed in the GeoWorkspace coordinate system.
13-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:
AreaCalculates 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.
AzimuthCalculates 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.
BearingCalculates 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.
HeightCalculates 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.
13-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.
6. Optional: Type an appropriate query description in the Description 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.
9. Optional: Click Style, and change the default style on the Select Style dialog 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.
13-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.
13-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:
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.
13-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:
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.
13-73
See the GeoMedia Professional 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 and the Update Attributes command on the Edit menu. The Analysis
commands Functional Attributes, Aggregation, and Analytical Merge are types of
queries for forming additional data with the Functional Attributes dialog box. The Edit
command Update Attributes is different in that it is a database update tool for changing
the original data and requires a read-write connection. When displayed through the
Update Attributes command, the title of this dialog box is Expression for <attribute
name>, and it does not have the Functional attribute name or Output type fields.
See Aggregating Data and Merging Feature Classes and Queries in this chapter and
Updating Feature Attributes in the Editing Features and Geometries 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.
See the Functional Attribute Information topic in GeoMedia Professional 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
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.
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.
13-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:
IdentifiersReferences to fields in which values vary for each record.
ConstantsFixed values that are constant for each record.
FunctionsOperations 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
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.
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 Professional have unique names. These functions
are organized in the following categories:
Miscellaneous
Date and Time
Geometry
Statistical
Logical
Text
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.
13-77
Constant
Meaning
Truemeas
Projectgedmeas
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
COMPRESSReturns 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 Professional.
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:
13-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 endpointto-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-tostartpoint, 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
13-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
CREATEPOLYLINECreates 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 the geometry is not defined (NULL value), the NULL value is returned.
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
MERGEReturns 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
PERIMETERReturns the distance around the perimeter of the specified geometry. The
following format is similar to the AREA function (see also the previous AREA function).
13-80
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.
13-81
2. Select a feature class or query as input from the Add functional attributes for dropdown 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.
9. Accept the default query name, or type an appropriate name in the Query name field.
10. Optional: Type a query description in the Description field.
13-82
11. Choose whether or not to display the resultant functional attribute query in a data
window and/or map window. You can change the map window or data window name
if appropriate.
12. Optional: Click Style, and change the map window default style on the Select Style
dialog box.
13. Click OK.
13-83
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:
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
13-84
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.
CustomOpens the Functional Attribute dialog box for creating new functional
attributes, as does the New button.
[Function] > Multiple AttributesOpens 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.
13-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).
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.
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,
13-88
linear, area, compound, and nongraphic, but not graphics text or image. The output
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?
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
13-89
must match, that is, there is a logical and between the comparisons of the various attribute
values. When you have selected a summary feature class or query, you must select at least
one attribute.
gdbBoolean
gdbByte
gdbInteger
gdbLong
gdbSingle
gdbDouble
gdbDate
gdbText
gdbCurrenc
y
gdbBoolean
gdbByte
gdbInteger
gdbLong
gdbSingle
gdbDouble
gdbCurrency
gdbDate
gdbText
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.
13-90
contain
entirely contain
meet
overlap
touch
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.
13-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
Problem 2: Need the number of cities each state contains as an attribute of the state.
Solution:
Summary Feature: States
Problem 3: Need to calculate the number of people in each state who do not live in a city.
Solution:
Summary Feature: States
13-92
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.
CustomOpens the Functional Attribute dialog box for creating new functional
attributes, as does the New button.
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 AttributesOpens 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.
To define aggregation:
1. Select Analysis > Aggregation.
13-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 dropdown 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.
See the GeoMedia Professional Help for information on this dialog box.
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.
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.
13-95
Queries update when the record set is created, when the connection is opened, and
when notification occurs.
Two feature classes are used per query record sets, summary feature and detail feature.
13-96
The output attributes are limited to Geometry, ID, and user-defined functions.
Each function takes multiple input, and outputs a single resultant value.
Topological types
selectable
Nodes
Edges, Nodes
Edges, Nodes, Faces
Edges, Nodes, Faces
Default selection
Nodes
Edges
Edges
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, 4Node.
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.
13-97
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.
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
13-98
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.
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.
13-99
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.
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.
13-100
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.
Note: Double clicking on an entry in the Attributes list also opens this dialog box.
7. Optional: Change the default query name, and/or type a description in the Output
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.
9. Optional: Click Style, and change the default style on the Select Style dialog 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
To not display the nongraphic attributes of the merge in a data window, uncheck the
Display in data window check box.
11. Click OK to generate the attribute selection query.
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.
13-102
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 fields 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.
Reorder records.
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:
13-103
This command raises an error when there are conflicts arising due to geometry field
mismatch.
13-104
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.
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 classes, categories, and reference features 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.
13-105
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.
13-106
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.
9. Optional: Change the default query name, and/or type a description in the Output
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.
11. Optional: Click Style, and change the default style on the Select Style dialog 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
To not display the nongraphic attributes of the merge in a data window, uncheck the
Display in data window check box.
13. Click OK to generate the attribute selection query.
13-107
13-108
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.
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.
14-1
LRS DatumThe basic, linear geometry of an LRS with its key identifiers and measures.
EventAny 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/RouteSet of segments in a certain order and direction.
Milepoint/Kilometer Point/Log MileDistance measurement from the beginning of a
route.
SegmentContinuous section of roadway (that is, intersection to intersection).
MarkerStart and endpoint of segments, often Intersections. Events are frequently
measured as an offset of a marker.
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
14-2
Linear Referencing
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.
IDThis is a long integer value that uniquely identifies each feature within the table.
LRSKeys1-4This is one to four fields that together define the route that this feature
belongs to.
StartMeasureThis is a numeric value that contains the measurement value for the
beginning of this feature.
BeginMarker (optional)This field stores a name for the beginning position of this
feature. This is referred to as an internal marker.
14-3
EndMarker (optional)This field stores a name for the end position of this feature.
This is referred to as an internal marker.
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 nongraphic table that has the following fields:
IDThis is a long integer value that uniquely identifies each record within the table.
LRSKeys1-4This is one to four fields that together define the route that this record
lies along.
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
14-4
Linear Referencing
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:
IDThis is a long integer value that uniquely identifies each record within the table.
LRSKeys1-4This is one to four fields that together define the route that this record
lies along.
MeasureThis is a numeric field that indicates the relative location of the External
Marker on the route defined by the LRS Key fields.
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.
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.
14-6
Linear Referencing
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.
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.
14-7
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.
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.
16. Click OK after setting the appropriate values or Cancel to discard your changes.
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:
The corresponding Style buttons display a default point style, which you can change
by clicking the appropriate Style button.
14-8
Linear Referencing
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.
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.
14-9
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
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
at the far right of the
example, Insert Feature). Next select the LRS Keyin button
LRS Precision Location control.
14-10
Linear Referencing
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.
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.
14-11
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.
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.
14-12
Projected XY coordinates
Longitude/Latitude
Marker Offset
Duration
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.
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.
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:
Linear Referencing
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.
The results are output as a query to a map window and/or a data window.
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.
14-13
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.
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.
10. Click OK after setting the appropriate values or Cancel to discard your changes.
14-14
Linear Referencing
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 dialog box, click Properties.
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.
16. Click OK after setting the appropriate values or Cancel to discard your changes.
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.
14-15
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 32.
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.
14-16
Linear Referencing
28. Select the Coordinate system type, and set or modify the coordinate system.
See the GeoWorkspace Coordinate System Dialog Box topic in GeoMedia
Professional 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 Professional menu bar. This displays the GeoWorkspace
Coordinate System dialog box on which you click Save As and then assign it a
filename and location.
29. Click OK after setting the appropriate values or Cancel to discard your changes.
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).
31. Click OK after setting the appropriate values or Cancel to discard your changes.
You are returned to the Dynamic Segmentation dialog box.
32. Click Event feature > Attributes.
14-17
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.
You are returned to the Dynamic Segmentation dialog box.
36. Optional: Click Advanced Display Settings.
37. Check the Occurrence > Compute occurrence value check box; 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.
14-18
Linear Referencing
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:
14-19
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 Professional
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.
14-20
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 QueryYou 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,
15-1
15
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
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 ClassLabels 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 anglePlaces 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.
15-2
Orient to geometryPlaces the label rotated in the direction of the geometry being
labeled.
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:
15
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.
15-3
To create a label:
1. Select Insert > Label.
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.
15-4
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.
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.
15
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.
15-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:
15-6
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.
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 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.
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
15-7
15
>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
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.).
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.
15-8
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.
15-9
15
Orientation
The available label placement orientation modes are as follows:
Place at anglePlaces 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 current settings defined for the Angle
type in the default units and precision settings on the Units and Formats tab of the
GeoWorkspace Coordinate System dialog box.
Rotate dynamicallyPlaces the label, allowing you to specify rotation angle dynamically
for each label instance. This mode labels by two clicks. The first click places the label; the
second determines the label rotation. Rotation is dynamically displayed until the second
click.
Orient to geometrySnapping to a geometry places the label rotated to the direction of
the geometry snapped to. If no geometry is snapped to, placement is at 0 degrees rotation.
Place along arcPlaces a curved label where the curvature of the text string is defined by
a user-defined three-point arc.
Place along existing geometryLets you select a linear or area geometry along which to
undulate the text being placed. You can control the distance of the text from the geometry
and can 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. You can smooth the
curvature of the text by increasing the offset or by using the up and down arrow keys.
For all orientation modes, you can control inter-character spacing to expand or retract the
text string. If you need to control spacing, you can use the mouse wheel or the + and keys to increase or to decrease the character spacing. Multi-line labeling is not supported
when adjusting the inter-character spacing.
Using the Place along arc and Place along existing geometry modes always generates a
composite text collection. Using the Place at angle, Rotate dynamically, or Orient to
geometry modes generates a simple multi-character string, unless inter-character spacing is
used. In that case, a composite text collection is generated. Composite text collections let
other parts of GeoMedia recognize the resulting multi-part text as a single composite string
rather than individual characters.
The command displays the label WYSIWIG with the correct text, where the rotation angle
is obtained from the selected snap point, using the style taken from the legend entry. If
there is more than one legend entry, the style of the topmost entry is used. If you select the
Override style option, the label is displayed with the override options selected.
The following rules for label placement apply:
15-10
Linear dataOrientation is based on the angle of the line from begin point to end
point.
Area dataOrientation is based on the angle of the longest edge of the area boundary.
> 270 degrees, < 0, < 360 degreesText 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.
Alignment
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
2. Select the feature class from the connections, queries, reference features, or categories
to be labeled from the Label features in drop-down list. If this is the first time the
command has been run in this session, the default alignment changes based on the
feature type selected.
15-11
15
3. From the Output labels to drop-down list, select the feature class in which you want
to place labels.
4. To place an attribute variable in the Layout box, select it from the Attributes list.
You can place as many attribute variables as you want. Values for each attribute are
extracted from the warehouse when the labels are created.
5. Place the cursor in the Layout box where you want common text to appear on the label
relative to the field, and type the text.
6. To define the position of each label relative to its origin, select the alignment from the
Alignment drop-down list.
7. Select the label Orientation from the drop-down list.
8. Optional: If you selected Place at angle in Step 7, type the rotation angle in the
degrees field.
9. Optional: Select the Override style check box; then define the appropriate text style
settings.
10. Click OK.
The layout definition is displayed WYSIWYG dynamically on the cursor for any feature
highlighted.
11. Click to identify the feature to be labeled. Optionally, modify the inter-character
spacing using the mouse wheel or up and down arrow keys.
12. To place the label at a user-defined rotation angle, click to place the label.
OR
To place the label to rotate dynamically, click for the location for the label origin; then
click for rotation and placement.
OR
To place the label to orient to geometry, click to identify the feature to be labeled at the
location where the orientation should be calculated; then click to place the label.
OR
To place the label along an arc, digitize three points to define the curvature of the arc,
in the order 1-2-3. Optionally, modify the inter-character spacing using the mouse
wheel or up/down arrow keys. Upon defining the third data point, the label will be
floating and oriented along the curvature of arc defined. Finally, click a fourth point to
place the label.
OR
To place the label along existing geometry, move the cursor along the geometry. The
text will float along the curvature of the geometry defined. Optionally, smooth the
curvature of the text using the up and down arrow keys. Click to place the label.
15-12
Non-conflicting text output queryUses 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 queryUses 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.
15-13
15
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:
You could then use leader lines to move the conflicting queries.
15-14
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 classThe command identifies nonconflicting 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 features 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 classThe 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 features
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.
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.
15-15
15
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
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.
15-16
8. Optional: Select the Output non-conflicting text as query check box to output nonconflicting 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.
15
15-17
15-18
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.
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.
These topics are organized to give you an idea of how the geocoding works from a users
perspective. Next follows a discussion of some details about how geocoding is configured
from a GIS administrators perspective. The related workflows involve creating the
configuration files required to publish GIS data into the new AGI file format used for
address geocoding.
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.
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.
16-3
Getting Started
To start the two geocoding commands, select View > Find Address, and Analysis >
Geocode Addresses from the GeoMedia Professional menu bar.
To start the Publish Address Geocoding Index utility, select GeoMedia Professional >
Utilities > Publish Address Geocoding Index from the Start menu. See the
information provided by Intergraph Support for starting the Define Parsing Rules utility.
16-4
Geocoding
Find Address commandA 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 warehouseThe source GeoMedia-accessible dataset that contains the features the
geocoding index is derived from.
Geocode Addresses commandAn 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.
GeocodingThe process of taking an address and generating a location for it.
Geocoding datasetA 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 directoryAn 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 interfaceA COM (dispatch) interface definition that provides a
generic interface by which any number of independent (Intergraph-developed or thirdparty) 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 modelAn 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 buildingProcessing 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.
LocationA point on the earth, which may be expressed in world coordinates (textual or
numeric) or as a point geometry.
MatchingComparing standardized address elements in a common structure (one may
have been transformed) and selecting one or more successful or candidate matches.
16-5
Functional Overview
There are three basic operations involved in Address Geocoding:
1. Index BuildingProcessing 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 MatchingTaking a fully parsed input attribute and finding the best match
in the index.
16-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:
16-7
Minimum match scoreValue (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 unitThe default offset value is two meters for centerline
geocoding. Offset is not used for intersection or rooftop geocoding. The units dropdown list contains all available linear units and is initially set to the default linear unit
as specified by the GeoWorkspace Coordinate System command.
StylePoint 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:
16-8
FindAfter 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
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.
OptionsDisplays the Find Address Options dialog box, which lets you specify the
geocoding directory and other parameters used in the address geocoding process.
Match detailsDisplays 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.
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.
16-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
Knoxville
City:
TN
State:
37916
ZIP:
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.
16-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.
Geocode addresses inFeature 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).
16-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).
Address attributesAttributes 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 dropdown 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.
16-13
Output AttributesAll 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.
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.
16-14
Geocoding
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:
C:\Warehouses\GMAGTrainingCenterlineStreetData.xml.
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.
16-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.
16-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.
16-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
C:\Warehouses\GMAGTrainingCenterlineStreetData.xml.
Note: The content of this XML file is the example given at the beginning of this
workflow.
16-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.
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:
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:
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 typeThis element type is defined by enumeration of all values it
can contain.
2. Pattern token typeThe 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 typeThe 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.
16-20
Geocoding
4. Reference token typeThis 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 typeThis 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 tokens 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 typeAll 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 typeThe standardization is performed by the embedded
parsing rules.
3. Reference token typeThe standardization is defined in the referenced token
definition.
4. Pattern and Characters token typesTokens 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
1st Ave E
E Main Street
Broadway
Military Way
Street name
Street prefix
Street name
Street name
Token Sequence
Street type
Street suffix
Street name
Street type
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.
16-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,
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.
16-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.
Coordinate units (for example: degrees, radians) and formats (for example: decimal
degrees, d:m:s) of all types supported by GeoMedia Professional coordinate systems.
Definition of the coordinate system through the Coordinate System Properties dialog
box.
16-23
To geocode coordinates:
1. Select Analysis > Geocode Coordinates.
See the GeoMedia Professional 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
from the drop-down list.
Note: The names of the first and second coordinate fields vary dynamically with the
selected coordinate system, units, and format.
16-24
Geocoding
5. Select the attribute to be used for the second coordinate from the drop-down list.
6. Optional: Select the attribute to be used for the height value from the 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 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
window check box to remove the checkmark.
10. Optional: Click Style, and change the default style on the Select Style dialog box.
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.
16-25
16-26
Inserting Traverses
Insert Traverse provides coordinate geometry key-in and digitizing tools for input and
maintenance of linear and area feature data sources in the GeoMedia Professional
environment. Examples of such data sources are registered survey/plat maps, parcel deeds,
and title documents.
An area feature generally consists of one primary feature class (for example, parcel) and
various component feature classes (for example, the individual boundaries as separate
feature classes). In addition to area features, you can precisely insert and maintain linear
features. You select both primary and component feature classes from a list of all writable
linear/compound features from all the open connections, reference features, and categories.
When you select a compound geometry feature class as the primary feature class, this
command creates an area geometry for the primary feature. When you select a compound
geometry feature class as the component feature class, this command creates a linear
geometry for each component feature. In addition, this command dynamically displays the
feature geometry in the map window as you define the geometry.
You have the option to add the traverse to the primary feature class or not through the
Primary feature class check box on the Insert Traverse dialog box. When checked, it
lists all writeable compound, area, and linear features, and lets you select the primary
feature class for the traverse to be placed. When unchecked, the primary feature class is set
to None, and the component feature class is populated by selecting a linear feature class.
As a result, you can continue adding the line segments to the component feature class(es)
and can optionally select the Primary feature class when required.
Once defined, you can save the geometry definition data to a .trv file and/or insert the
geometry into a read-write warehouse. The .trv files have many uses. You can save
coordinate geometry input from many different input/editing sessions into a .trv file until
the geometry for an entire region or area is captured. You can then Load and Apply this
data to a read-write warehouse. This provides both an audit trail of the data and an ASCII
archive. Also, you can use .trv files as templates in which the data are loaded and edited
for the creation of subsequent geometry features.
Note: Double clicking on a .trv file opens Notepad.
The primary area and component feature-class definition capability provides a dual
analysis capability. In a parcel data capture workflow, there is a need for both area-based
(that is, parcel polygon area computations, spatial analysis, thematic mapping, and so
forth) and component-based (that is, frontage boundary length, interior parcel boundary
parameter, spatial referencing, and so forth) segregation and analysis. To do this, the
software stores the parcel as an area feature and stores the component parts separately.
17-1
Using the unique coincidence capability of this product, you can edit the component
features separately (automatically editing the underlying area feature), while still allowing
for area analysis. For example, when defining a rectangle parcel feature, you could define
the eastern boundary to be a street, the northern boundary to be a country line, the western
boundary to be a street, and the southern boundary to be a highway.
The type of information entered depends on the feature being created and on the traverse
type (Start_Point, Point, Line, Jump_Line, Arc, or End).
In general, you can enter traverse information by one of three methods:
Typing the traverse data directly into the grid or dimension frame of the Insert
Traverse dialog box.
You can also use a combination of these input methods for coordinate geometry input.
Defining a Traverse
Depending on your particular workflow, you may switch between these three methods
while defining a traverse.
Typing Data
This method involves direct typing of point coordinate, distance, bearing, azimuth,
deflection, and/or arc parameter values into the dialog box fields. The dimension frame for
data entry on the Insert Traverse dialog box switches according to the type of traverse
you are placing. You can enter the data for both linear and point coordinates.
Linear Dimensions
For linear (Line or Jump_Line) input, you enter the parameters for one of the three lineplacement methods, distance/bearing, distance/azimuth, or distance/deflection. The default
is distance/bearing. The name of the direction field changes with each method.
17-2
Inserting Traverses
Point Dimensions
For a point, you enter the point coordinates for one of the two point-placement methods,
geographic or projected. The default method is based on the coordinate readout control
setting.
17-3
17
Note: Precision key-ins from outside the dialog box are not supported. To use point input,
set the traverse type to Point and use the Longitude/Latitude or East/North fields to
enter the point position.
Arc Dimensions
To define an arc, you must select one of the four arc-placement methods (arc, chord, delta,
or end point) and enter the required (enabled) parameters.
The following table shows the four arc placement methods and their required input:
Arc
Length
Arc
Chord
Delta
End Point
Chord
Directio
n
Chord
Length
Delta
Directio
n
Path
4
4
4
4
4
4
Radius
Tangent
Direction
4
4
Selecting Data
In selecting points/features from a map window (Use Map), the Insert Traverse dialog
box closes, and you provide input by clicking on a geometry displayed in a map window.
Insert Traverse computes the values (that is, coordinates, direction, distances, and so
forth) needed and automatically populates the dimension information frame on the dialog
box.
Your input and the type of coordinate information gathered depends on the particular
traverse geometry type being defined. This method is useful when you want to use an
existing geometry that forms a common boundary with the features you are creating or
17-4
Inserting Traverses
when you want to use the coordinates of a displayed control point rather than typing them
into the dialog box.
For Start_Point, Point, and End coordinates, simply click on an existing point or vertex in
the map window to retrieve the coordinates.
For Arcs, click two points on an existing arc geometry in the map window to add
coordinate information. Insert Traverse retrieves the arc definition parameters and inserts
these into the arc input fields of the dialog box. The two points are not used as start and
end points; only the arc definition parameters are retrieved from the selected geometry.
The start point of the arc being defined is the last point entered on the dialog box, as shown
in the following figure of arc placement:
Disconnected arc
identified
Resulating arc
placement
In selecting data in the map window, you can also copy existing geometry information into
a geometry type, as when designating a common geometry. In this case, you do not select
the geometry itself, but SmartSnap is active so that you can snap to two points on the
geometry to copy the definition values to the dialog box. However, the command draws a
straight line between the two points and does not follow along any geometry when
determining the distance and direction, as shown in the following figure of line placement:
The following figure shows the resulting placement if a disconnected line is defined by two
clicks:
Disconnected
line Identified
Resulating
line placement
17-5
17
Importing Data
In importing (Load) data from an ASCII text file, you select the appropriate file from the
common file-selection dialog box to populate the Insert Traverse dialog box with the
traverse definition. You can import a .trv format file. When you save a traverse definition,
the command saves it as a .trv file. This file contains all point, line, and arc definition
information, from the start point through feature creation.
You can also modify a saved traverse definition and save it as a new traverse file. When
you load a traverse from a .trv file, the unit values are taken from the file rather than from
the Options dialog box (Tools > Options).
17-6
Inserting Traverses
During an adjust operation, you can exclude (Lock) individual traverse legs/points from
being altered. Any traverse in the edit grid populated by clicking in the map view is
automatically locked, so any adjustment does not break coincidence conditions.
Additionally, each traverse leg can have a linear feature placed for it. You can toggle
between locked and unlocked while defining a traverse. (To lock or unlock a traverse, you
must click the Lock check box twice.)
The Display label option allows you to automatically display labels for the bearing
distance in the start, end, or center position of each traverse leg, as the traverse is being
defined. The labels are not written to the database. They are only used to allow a quick
reference between the map view and the grid to determine which row in the grid goes with
which leg of the traverse in the map view.
When you have completed traverse definition, clicking Apply places the
primary/component feature(s) into the map window. The coordinates of the traverse are
calculated based on the Start_Point coordinates. Linear features are created in the
respective component feature classes. Area/Linear features are created corresponding to
the primary feature class selected for that feature.
During Apply, the Properties dialog box opens to allow input of attribute values if there
are required values or if the Display Properties dialog for new features option on the
Placement and Editing tab of the Options dialog box (Tools > Options) is turned on.
When the Properties dialog box opens, the Insert Traverse dialog box closes until you
have input all the attribute values, at which time the Insert Traverse dialog box again
opens.
Insert Traverse honors the Measurement interpretation setting on the Units and
Formats tab of the Define Coordinate Systems dialog box. If set to True (spheroidal),
the distances for all subsequent traverse segments are computed with the curvature of the
earth taken into account. If set to Projected (planar), the distances for all subsequent
traverse segments are computed as planar distances.
17
Secondary Workflow
A secondary workflow is the collection of area features without components for each
traverse leg. This command also allows the collection of linear features; however, Close
Feature and Adjust are not enabled for such features.
3. Select the Start_Point traverse type from the Traverse type drop-down list.
Note: You must always start a new traverse with Start_Point.
4. Type the coordinates for the start point directly into the grid for the first traverse leg.
OR
Type the coordinates for the start point into the Point dimensions frame fields; then
click Add to Grid.
Note: Point dimension method defaults to the coordinate readout control setting, that
is Lat/Long or Projected coordinates.
17-8
Inserting Traverses
A new row is added to the grid with the traverse type of line, and the dimension frame
switches to show line dimensions.
5. Type the appropriate traverse coordinates.
6. Check the Primary feature class check box.
7. Select the primary feature class (area, linear, or compound) of the feature being
digitized from the Primary feature class drop-down list.
8. Select the traverse type.
The Component feature class field is enabled for selection of the component feature
class (linear or compound feature only) for the selected traverse.
For Point, enter the coordinates as in the previous steps.
For Line, enter the legal distance and bearing or distance and azimuth values in the
line dimensions frame.
For Arc, use one of the four placement methods for entering the arc dimensions.
The dynamics of the feature are shown upon clicking Add to Grid unless the traverse
type is Jump_Line.
9. Repeat these steps for all traverses forming the feature.
10. Click Close Feature to join the end and start points of the feature being digitized with
a new line when the points are close together.
A line is shown joining the end point of the previous linear feature and the start point
of the feature. Two new rows are added to the feature detail grid with traverse type as
Line, the distance and bearing values are populated, and the second has the traverse
type set to End. Select the feature class of the line that closes the feature from the
Component feature class drop-down list.
OR
Click Adjust to adjust the closing error if the primary feature is an area feature class
and the feature is not closed, and verify that the closure error is within your specified
tolerance limit.
The Calculated traverse columns in the feature detail grid are populated with the
corrected values of bearing and distances or coordinates of the Line/Point or Arc
length features.
11. When finished, click Apply to insert the traverse geometry and to hide the dialog box
during feature placement.
If Display Properties dialog for new features is on, or if input is required for the
selected feature class, specify the feature attributes on the Properties dialog box; then
click OK to exit and to again open the Insert Traverse dialog box.
17-9
17
17-10
18-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 keyin 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:
18-2
Grid displayDisplays a grid for precision element placement. The grid lines
themselves are not considered part of the document and do not print.
Grid snapAligns 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.
Subintervals per intervalDetermines 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 Professional 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
Professional 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
Professional chapter for more information.
18-3
18-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.
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 Professional\Templates\Layouts.
18-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 Professional layout templates created with GeoMedia Professional 4.0 (or
above) using the Export Layout command contain only layout graphics. Imagineer or
SmartSketch files or templates created using GeoMedia Professional 2.0 or GeoMedia
Professional 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 Professional 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.
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.
18-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.
Bitmap (.bmp)
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
18-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:
Attribute:
Name: GeoWorkspace
Type: Text
Attribute:
Name: SheetName
Type: Text
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 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.
18-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.
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.
18-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.
18-12
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.
18-14
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.
4. Select the target layer from the Change all to list; then click OK.
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.
18-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.
18-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.
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.
18-18
To delete a layer:
1. Select Layout > Layer Groups.
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:
1. Select Layout > Layer.
2. Click Layer Status on the Layer toolbar.
3. Click Groups.
18-19
18-20
19-1
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 Professional 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,
19-2
where unique legend settings can be applied independently of the settings used for
analysis.
Paper (size is true at nominal map 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.
19-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 Professional Data chapter for more information.
LegendThe 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 ArrowTo 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 Professional\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.
19-5
Scale BarTo 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.
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.
Using the Sheets > Export Layout command, export the layout sheet to one of the
available export formats.
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
19-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:
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 SizeRequires 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.
Projected FrameRequires a user-defined diagonal entry of the upper-left and lowerright 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.
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.
See Defining Map Window Display Properties in the Working with Map Windows
chapter for more information.
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.
19-10
Fit to frameThis 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.
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
19-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 frames 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.
19-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.
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.
Select ToolSelects elements in the active layout sheet, and terminates any other
active commands. This is the default active command in the layout window.
19-13
TextPlaces one or more text boxes into which you can place text.
Linear ControlsDefine an active linear style by defining the color, width, pattern,
terminators, end cap, and join settings; and apply the style.
Caps and Join ControlsApplies the active linear end cap and join style to objects in
a select set.
Fill ControlsApply 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 Professional is reopened, the toolbox and
toolbar are displayed again in the new session.
Nudge >
Align >
Distribute >
19-14
Bring to Front
Send to Back
Bring Forward
Send Backward
Up Up Arrow
Down Down Arrow
Left Left Arrow
Right Right Arrow
Left
Center
Right
Top
Middle
Bottom
Horizontally
Vertically
Spin
Spin Left
Spin Right
Flip Horizontally
Flip Vertically
Create Symbol
Set Active Symbol
See Creating Symbols later in this section.
Placement Menu
Editing Menu
See the corresponding topics in GeoMedia Professional 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 Professional Help for information on using
these commands.
19-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 Professional Help for information on the Select Tool.
19-16
Symbol
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:
19-17
See the corresponding topics in GeoMedia Professional 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:
19-18
Element
Geometry Properties
Arcs
Center, start, and end coordinates; radius; start and sweep angle
Curves
Ellipses
Lines
Polygons
Polylines
Rectangles
Four coordinates representing the four corners, height, width, and angle
Symbols
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 Professional 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
mouse down, mouse drag, mouse up sequence to define the dimensions of the text box.
19-19
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.
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.
19-20
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
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.
19-21
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?
Color
Yes
Translucency
Yes
Width
Yes
Line type
Yes
Dash-gap sequence
Yes
Dash-gap sequence
No
proportional to width
Start cap
Partially
End cap
19-22
Partially
Notes
Dash cap
No
Ignored
Midline join
Yes
Offset left/right
Yes
Offset distance
Yes
Advanced tab - ABS
No
Style Properties Pattern Line Style
Functional Capability Convert? Notes
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
Offset Y distance
Yes
19-23
Ignore geometry
Yes
Accomplished by Relative/Absolute orientation
rotation
setting.
Always keep upright
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 geometry
Yes
Accomplished by Relative/Absolute orientation
rotation
setting.
Always keep upright
No
19-24
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 Professional Help Topics for complete information on using these
dialog boxes.
Zoom to Actual SizeDisplays the active layout sheet at a 1:1 paper scale.
Hide Layout WindowHides 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
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.
19-27
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:
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.
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
Professional\Symbols\Geometry folder) is placed.
3. Click Browse.
19-29
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.
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.
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
19-31
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 drawingthis 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.
See the SmartSnap section in the Working with Features chapter for information on
using SmartSnaps in digitizing in the map window.
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
19-32
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.
When you link an object to a document, the document stores information about where
the object is locatedthe 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.
19-33
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.
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:
19-34
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.
19-35
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.
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.
19-36
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.
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.
19-37
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.
19-38
Select and type the appropriate grid parameters, and then click OK to insert the grid.
19-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.
19-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.
19-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.
19-42
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
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.
19-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.
19-44
The newly inserted layout frame group is left in the select set.
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.
19-46
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.
19-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.
Note: When the dialog box is displayed, you can exit the command by pressing ESC.
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.
There are assorted tools and commands available that can be used to adjust the graphic
display of the map and marginalia after they have been placed in the layout sheet.
See the Modifying Maps section in this chapter for information.
select set, enabling you to move on to additional insert operations, such as the placement of
marginalia or grids
There are assorted tools and commands available that can be used to adjust the graphic
display of the map after the map has been placed in the layout sheet.
See the Modifying Maps section in this chapter for information.
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.
19-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.
Note: When the dialog box is displayed, you can exit the command by pressing ESC.
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.
19-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.
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.
19-52
See the corresponding GeoMedia Professional Help topic for complete information on this
dialog box.
You can customize the layout legend treeview items through their respective right mouse
menus as follows:
Item
Command
Lets You
Legend
Properties
Rename Legend
Title
Add Column
Distribute Entries
Evenly
Remove Column
Add Entries
Sort Entries
Alphabetically
Sort Entries by
Geometry
Column
19-53
Item
Entries
Command
Properties
Rename Entry
Add Entries
Remove Entry
Lets You
Customize the entry properties on the corresponding
Legend Entry Properties dialog box.
Type a new feature name.
Add legend entries on the Add Layout Legend
Entries dialog box.
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 Professional 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-anddrop 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.
19-54
There are assorted tools and commands available that can be used to adjust the graphic
display of the legend after it has been placed in the layout sheet.
See the Modifying Legends section in this chapter for more information.
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.
19-55
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.
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.
19-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.
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.
19-58
See GeoMedia Professional Help for complete information on this dialog box.
Note: In the layout window, the unit for the Size is defined by the Style field on the
Layout tab (Tools > Options).
There are assorted tools and commands available that can be used to adjust the graphic
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.
19-60
See GeoMedia Professional Help for complete information on this dialog box.
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 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).
19-61
As you make changes in the scale bar, they are displayed in the Preview area on the Insert
Scale Bar dialog box.
There are assorted tools and commands available that can be used to adjust the graphic
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.
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 Professional 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 size, rotation, and origin of the current map frame are maintained regardless of the
extraction method used during the original map placement.
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.
A selected, populated map frame or selected, populated frame group with the map
graphics to be updated exits in the layout sheet.
19-63
The map window that was used for the original placement of the static map exists.
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.
19-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.
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.
OR
1. Select the appropriate map frame group.
2. Select Properties from the right mouse menu.
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.
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.
Map Zoom In
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 frames 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.
19-68
19-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.
19-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 the contents of the
map frame are rotated.
In the following example, the map was placed using the Existing Shape method, a
Boundary frame type. The map depicts the original placement, a rotation of 0 degrees.
Note: In this case, the boundary frame is the outline of the state of New Mexico.
To this placemen, a rotation of 15 degrees was done, as seen in the following example in
which the Boundary map frame and all of its contents have been rotated 15 degrees.
19-71
In the next example, the map was placed using the Map Window method, a Rectangular
frame type. This example depicts the original placement, a rotation of 0 degrees.
Finally, a rotation of 15 degrees was done. 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
19-72
space independent of the workspaces geographic or projected space, which generally leads
to improved layout and design.
Map frames must be in dynamic mode; you cannot rotate static maps.
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-anddrop 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.
19-73
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.
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.
19-75
See GeoMedia Professional Help for complete information on this dialog box.
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.
19-76
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.
19-77
See GeoMedia Professional Help for complete information on this dialog box.
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 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.
19-78
See GeoMedia Professional Help for complete information on using this dialog box.
19-79
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
19-80
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.
See the Working with Coordinate Systems chapter.
Note: You can save the cartographic grid definition to an .xml file. By design, the saved
information in the .xml does not include the projected versus geographic setting of the neat
line.
19-81
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.
19-82
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.
ParallelParallel 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.
PerpendicularPerpendicular 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:
See GeoMedia Professional Help for information on using this dialog box.
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.
19-83
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.
See the Working with Coordinate Systems chapter.
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.
19-84
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.
19-85
ParallelParallel 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.
PerpendicularPerpendicular 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 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.
See GeoMedia Professional Help for information on using this dialog box.
19-86
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.
See the Working with Coordinate Systems chapter.
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
19-87
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.
19-88
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.
See GeoMedia Professional Help for information on using this dialog box.
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 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.
9. Optional: Click Font to change the font values.
10. Optional: Click Advanced to set the advanced label formatting options.
19-90
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.
19-91
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.
19-92
19-93
19-94
19-95
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.
19-96
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 columns width
in the data window.
Based on longest textEach column width is based on the longest string in that
column.
Note: With the first and third options, column width might be too short, in which case the
string is truncated.
19-98
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
Re-sort data
.
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.
19-99
Note: A right mouse click lets you return (backup) to the dialog box without placing
the data window grid.
19-100
Paper Size > SizeThis 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.
OrientationOptions include Portrait and Landscape.
Print ScaleThis 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:
20-1
Fit toDefined 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 widefour
pagesbut only two pages tall, and eight pages would be blank.
Print RangeReports the Width and Height of the geographic extent of the
print/plot in ground units, as specified on the Units tab.
MarginsThis 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 MarginsIf 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.
UnitsThis 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
20-2
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.
PrinterThis 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.
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.
20-3
20-4
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 softcopy 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:
1. Select File > Print.
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).
20-5
Paper Size > SizeThis 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 ScaleThis 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
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 RangeReports the Width and Height of the tabular extent of the print in
paper units, as specified on the Units tab.
MarginsThis 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.
20-6
UnitsThis 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.
PrinterThis 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.
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.
20-7
background sheet, visible status, paper size, image quality, and layout orientation. It also
lets you save the current settings as the default.
NameLets 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.
VisibleLets 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.
WidthThis is a read-only field for all Size definitions except Custom. When
Custom is selected, this field is enabled.
HeightThis is a read-only field for all Size definitions except Custom. When
Custom is selected, this field is enabled.
UnitsThis 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 DefaultEnables 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
20-9
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.
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.
20-10
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, 14,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).
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!).
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.
20-12
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 plotters 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
24-bit
16-bit
16-bit
8-bit
8-bit
Slider Setting
Best
(default)
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.
See GeoMedia Professional 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.
20-13
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.
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 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 utilitys online Help for complete information.
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
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.
20-17
When you print to the Acrobat Distiller driver from GeoMedia Professional 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 Professional.
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.
20-18
Feature geometry and attribute linkage into MicroStation design file (.dgn) format.
Feature data into an ASCII format that can be loaded into an Oracle Object Model
database.
Feature data into an ASCII format that can be loaded into an SQL Server database.
Feature geometry and attribute data into AutoCAD .dwg or binary .dxf format or
ASCII .dxf 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.
21-1
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
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.
See the Working with Coordinate Systems chapter.
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.
21-2
For each feature class/query, the following three output files are created during export:
<FeatureclassName>/<QueryName>.shp
<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 Professional \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.
21-3
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 is 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 is appended, 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.
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
21-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.
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.
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
Professional geometry types:
21-6
GeoMedia Professional
Geometry Type
MapInfo
Geometry
Description
Point
Point
Point
Line
Line
Line
Arc
Arc
Arc
Polyline
Polyline
Polyline
Polygon
Polygon
Polygon
Composite Polyline
Multipolyline
Composite Polygon
Polygon
Boundary Geometry
Region/Multipolyg
on
Text Geometry
Text Geometry
Graphic Text
Point Collection
Individual Points
Multipolyline
Region/Multipolyg
on
Heterogeneous collection
(point, line, and/or area
together)
As individual
features
3. Select the feature class or query to be exported using the Features to export dropdown 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
21-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.
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, such as
export format, output file options, and filenames. Then on the Criteria tab, you select 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-toproperties 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.
21-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 pulldown 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
21-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.
21-11
5. For Use feature class or query name as output design file name, browse for the
appropriate folder for the Folder field.
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
21-12
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.
12. Optional: Click Attributes; then check the Add linkage check box.
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 is transformed to the
GeoWorkspace coordinate system. When exporting to MicroStation V7 format, the
input data is 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.
21-14
4. On the Criteria tab, select the appropriate items from the Select features to export
treeview.
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
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.
21-15
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.
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 doubleprecision 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.
21-16
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 Professional\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).
Element Types
The following table defines the IGDS element types generated from each of the GeoMedia
Professional geometry types:
GeoMedia Professional
Geometry Type
Point
Text
Line
Linear
Area
Compound
IGDS Element
Symbol / Degenerate line / Shared cell
instance (only for MicroStation v7 format)
Text
Line
Linestring or complex linestring
Shape or complex shape
One or more of the previously defined types
based on the content of the collection. The
elements are assigned the same graphic group
number in order to maintain their group
identification.
Type Number
17 / 3 / 35
17
3
4 or 12, 4, 4,
6 or 14, 4, 4,
3, 4, 6, 12, 14
and/or 17
user, you must ensure that the feature classes are assigned from only one schema. In
addition, you have the option of exporting 3-D coordinate information. If you do not
choose this option, the height information for each coordinate is not written to the output
.dat files. Furthermore, queries are exported using the name of the underlying table rather
than the query name. This is done to ensure that the name of the exported table conforms
to Oracles rules for table names. You can change this after export by directly editing the
export files for the specific query.
There are two export options available; 3-D coordinates and 10g point format.
Export 3D coordinatesThis option allows you to choose whether or not to export 3D coordinate information. If you do not choose this option, only 2-D coordinates are
written to the database and the height information is discarded. Once data has been
loaded to the feature class, you cannot change its dimensions without recreating the
entire table. If you plan to eventually use all three dimensions, you should choose to
output the z values here. By default, 3-D coordinates will be written.
Export 10g point formatIf you are using Oracle 10G or later, you can export point
feature classes (or compound feature classes containing points) using Oracles new
native oriented point format. If you choose this option, the point data will not be
compatible with earlier versions of GeoMedia. The default is to use GeoMedias
proprietary oriented point format. This will allow for backward compatibility.
See the Using Oracle Connections appendix for more information.
Any default values assigned to the columns in the native data is also preserved as part of
the export process, however, these defaults will be in their native format and may need to
be modified depending on the target database.
You should have your Oracle DBA set up GeoMedias GDOSYS metadata schema before
importing data created by Export to Oracle Object. This can be done using the Create
Metadata command in Database Utilities, or by using the CreateGDOSYS.sql script that is
delivered in the GeoMedia Professional\Program folder.
Exporting to Oracle Object Model creates the following files based on the coordinate
system of the GeoWorkspace:
21-18
The full path of a feature is prefixed to the output filename to avoid overwrite of files
created in the same session to handle cases where you select features with the same
name under more than one path in the treeview. In these cases, the table names
referenced within the output files do not contain the full path, however. As a result,
during subsequent loading of the data into Oracle, there is an attempt to append the
data. The append operation succeeds if the metadata of the features match and fails if
the metadata does not match.
Import.batCommand file that controls the loading process. It will contain references
for all the files created during the Export to Oracle Object Model process.
Export.logLog file that contains either the cause of failures if error conditions arise
or the number of features successfully exported per selected feature class during the
export process.
By default, the data is exported to the \Warehouses folder. You can change this location
on the dialog box, and this location is then remembered as a session preference.
Error Reporting
Error conditions are not reported to you while the Export to Oracle Object Model
command is being run. This is to improve performance and to ensure uninterrupted
exports of large sets of data. Please review the export.log file at the completion of the
export to determine if any errors occurred during the export process.
One common error that can occur when loading large geographic datasets is the following:
SQL*Loader-510: Physical record in data file is longer than
the maximum
This indicates that the amount of data exceeds the SQL*Loaders default capability. To
solve the problem, the READSIZE/BINDSIZE variable needs to be increased by manually
editing the import.bat file.
For example, if import fails on the ROADS feature class, find the following entry in the
import.bat file:
SQLLDR %1 CONTROL=ROADS
And change it to:
SQLLDR %1 CONTROL=ROADS READSIZE=4000000
21-19
Exporting to SQL Server creates the following files based on the coordinate system of the
GeoWorkspace:
FeatureClassName.bcp (one for each feature class or query exported)data file for
loading data.
FeatureClassName.datcontains the attribute and geometry data for use with bulk
load processor.
Import.batscript file with all of the above files, which uses common defaults and can
be edited for handling specific options.
Export.logLog file that contains either the cause of failures if error conditions arise
or the number of features successfully exported per selected feature class during the
export process.
By default, the data is exported to the \Warehouses folder. You can change this location
on the dialog box, and this location is then remembered as a session preference.
Additionally, you can specifiy whether the exported data should be suitable for a target
SQL Server 2000 or SQL Server 2005 database. For example, if you specify SQL Server
2005, gdbSpatial/gdbGraphic/gdbLongBinary source data is exported to SQL Server data
type VARBINARY(MAX). And, if you specifiy SQL Server 2000,
gdbSpatial/gdbGraphic/gdbLongBinary source data is exported to SQL Server data type
IMAGE.
Note: Error conditions are not reported to you while the Export to SQL Server command
is being run. This is to improve performance and to ensure uninterrupted exports of large
sets of data. Please review the export.log file at the completion of the export to determine
if any errors occurred during the export process.
Exporting to AutoCAD
Use the Export to AutoCAD command to export spatial data from any read-write or readonly warehouse connection into AutoCAD Release Version 14 .dwg, binary .dxf, or 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
21-22
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
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:
See the corresponding topic in GeoMedia Professional Help Topics for information on
this dialog box.
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 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
21-23
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.
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.
3. Select the appropriate feature class/query from the Features to export drop-down list.
21-24
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.
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. 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.
21-25
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.
21-26
Use the coordinate system fileThis 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
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:
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.
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:
<?xml version="1.0" encoding="UTF-8"?>
<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'>
21-27
<gml:boundedBy>
<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>
<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.
<?xml version="1.0" encoding="UTF-8"?>
21-28
OR
If Use the coordinate system file is enabled and selected, continue with Step 5.
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.
21-30
Catalog Connections
Searches
Categories
Spatial Filters
Legends
Styles
Queries
Warehouse Connections
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
Library Organizer
22-2
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.
Access
Access 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.
Note: Access-based warehouses, catalogs, and libraries all use *.mdb files. You should
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
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.
22-4
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:
22-5
OR
Select SQL Server Read-Only/Read-Write as the Connection type; then:
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.
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.
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:
NameLibrary connection names, with an icon at the start of the cell indicating the state:
Open Read-Write
Open Read-Only
Closed
22-7
Note: By default, library connections are kept in a closed state. They are opened
automatically when used by the Library Organizer command.
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.
2. On the Library Connections dialog box, select the row of the connection whose
properties you want to view or edit; then click Properties.
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 of 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
22-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.
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.
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:
22-10
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
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:
To organize libraries:
1. Select Tools > Library Organizer.
22-11
13. Type a new name not existing in the hosting collection of the library; then click OK.
22-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.
22-13
22-14
A-1
A-2
Read-Only Connections
To make a read-only connection to an Oracle warehouse, you must provide a valid Oracle
connection string, which usually consists of an Oracle username, password, and net service
name. Net service names are created using Oracles Net Configuration Assistant and
reflect the database you are trying to connect to (the information is stored in the
tnsnames.ora file). Read-only connections rely completely on Oracles native data model;
no specific GeoMedia metadata information is required. There will be limits on what
GeoMedia can interpret from existing spatial data, but metadata itself is not a requirement
B-1
for display. In fact, you can use the Oracle Object Model data server to view and to use
any tables within the GeoMedia environment as long as the connection is read-only.
If you are working without metadata, the GeoWorkspace must be assigned a coordinate
system that matches the spatial data that is being displayed. This ensures that the data is
displayed in the correct spatial location. GeoMedia will interpret all geometry types as
Compound. For best results with data access and performance, you should always
configure GeoMedias metadata. If GeoMedias metadata is detected, all read-only
connections will require metadata entries.
Read-Write Connections
A read-write connection to an Oracle warehouse requires the same connection parameters
as the read-only connection. However, read-write connections also require a metadata
schema to be present in the Oracle database instance. The user for this schema must be
called GDOSYS, and it can reside on any Oracle tablespace. For best results and for
performance reasons, assign GDOSYS to its own tablespace. The metadata tables in
GDOSYS store information used by all the schemas that require read-write access from
GeoMedia applications. The GDOSYS schema is also used to store coordinate system
information for all feature classes.
During the connection to Oracle, the Oracle data server will scan all accessible database
objects. If the data server detects the existence of the GALIASTABLE table in the
GDOSYS schema, metadata entries for all spatial tables, standard tables, and views will be
required before GeoMedia Professional will display them.
For more information, see GeoMedias GDOSYS Metadata Schema in this appendix.
Password Persistence
By default, GeoMedia stores the Oracle connection password in the GeoWorkspace. This
is meant as a convenience and allows users to open existing GeoWorkspaces containing
Oracle connections without having to re-enter connection passwords. However, this is a
drawback to those users wanting higher levels of security. The option to turn off password
persistence is in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\GDO\Oracle Object Read-Only\1.0\Store Password
HKEY_LOCAL_MACHINE\SOFTWARE\GDO\Oracle Object Read-Write\1.0\Store
Password
The default setting is 1, which means that connection passwords will be stored. To force
the user to enter a password for each Oracle connection, change the (default) setting to 0.
Password persistence is not an issue if you are using Windows domain authentication for
your connections.
B-2
Domain Authentication
Connections to Oracle based schemas can utilize either Oracle authentication (the default
mode) or Windows domain authentication. To use Windows domain authentication, you
need to first set some Oracle configuration parameters.
In the SPFILE or the initialization file, INIT.ORA, you need to set the following:
REMOTE_OS_AUTHENT=TRUE
this enables remote authentication in the instance.
OS_AUTHENT_PREFIX=<auth_prefix>
this sets the prefix Oracle will use for domain authenticated user names. GeoMedia
does not support the default prefix OPS$. You will need to choose a prefix that does
not contain the $ character. The only special character allowed here is the underbar(_).
For example:
REMOTE_OS_AUTHENT=TRUE
OS_AUTHENT_PREFIX="DA_"
You may need to restart the database instance after setting these values.
Create you user account in Oracle using the OS_AUTHENT_PREFIX, and specify
External Authentication for the password. For example, if your domain account is
JSMITH, your Oracle user name is DA_JSMITH. As with normal Oracle user accounts,
you need to assign the appropriate roles and privileges to this user, typically connect and
resource, but that is up to the Database Administrator (DBA). To connect in GeoMedia,
set the connection option to User Windows authentication, and enter the database service
name.
If your domain authenticated username contains any special characters (such as / or -), you
can still use it to connect, but it will not be able to own any database objects. GeoMedia
uses an OWNER.TABLE syntax when working with tables, and views and special
characters will cause this to fail.
All spatial filter operations are performed on the Oracle Server, which requires spatial
indexes to exist for all feature classes. This greatly improves spatial filter performance
for filter areas that are less than 70% of the total area covered by the feature class.
Spatial indexes require the presence of Oracle's spatial metadata in
USER_SDO_GEOM_METADATA. GeoMedia requires entries in this metadata view
for all tables and views containing geometries.
Mixed-case table and column names are not allowed. All values representing database
object must be in uppercase and must conform to the standard Oracle conventions for
table names. Oracle has many reserved words and these must not be used for table or
column names. Using reserved words can have unpredictable results.
When creating feature classes using Feature Class Definition, table names are
restricted to 24 characters. GeoMedia Professional reserves six characters for
index/sequence names. The use of the $ character in table names is supported, but you
should not use $ in column names. If you are planning to use Oracles Workspace
Manager, you are restricted to 22-character table names.
If your tables are created directly in Oracle, you can use Oracle's limit of 30 characters
per table and column name and any sequences and indexes must also be created
manually. For Workspace Manager, the Oracle-imposed limit is 25.
In order to be editable, all tables must have a primary key. If the table does not have a
primary key, it will be read-only.
Multiple column primary keys are allowed (up to 7), and they can have both a numeric
or character datatype, or any combination thereof.
Primary keys can be numeric or alphanumeric. Integer-based primary keys, populated
by an associated sequence, are recommended and will provide the best results.
For views, a primary key is required for at least one of the tables that will be used in
the view definition. This is known as a key preserved view. The key column must be
indicated to GeoMedia through the GDOSYS metadata table GINDEX_COLUMNS.
In order to be insertable, GeoMedia must furnish the key value, either through direct
key-in or through autonumber assigned sequence.
For more information on the format and contents of this table, see
GINDEX_COLUMNS in this appendix.
The Oracle Object Model data server supports the use of sequences for each field that
needs to be treated as AutoNumber. The most common use of AutoNumber is primary
key fields. GeoMedia determines the existence of the sequence by looking in the
GDOSYS metadata table GFIELDMAPPING. Use Database Utilities to create and/or
assign sequences to the appropriate fields.
For more information on the format and contents of this table, see
GFIELDMAPPING in this appendix.
B-4
Note: These sequences will be used by inserts made within the GeoMedia
environment. If you want to use the sequences for edits made outside of GeoMedia,
you will need to set up an insert trigger. See Triggers in this appendix for more
information.
The Oracle Object Model Data Server is designed for multi-schema support. All Oracle
DCL privileges are fully supported. Use the GRANT command in SQL to allow one
user to connect to another users schema. The minimum level of privilege required is
SELECT. To facilitate this in GeoMedia, all table names are prefixed with the name of
the schema from which the table came, for example, INGR.ROADS.
The use of table and view synonyms is not supported at this time.
Oracle spatial data that utilizes LRS geometry is supported in a read-only mode. You
are allowed to view the associated geometry in GeoMedia Professional, but the measures
are ignored. You must use Oracle views to directly access the measured values.
All views that are updateable in Oracle are updateable in GeoMedia Professional. The
GDOSYS metadata table GINDEX_COLUMNS needs an entry for the view that tells
GeoMedia Professional what the primary key of the views base table is. This can
actually be any column in the view that behaves like a key column (unique and not null).
You can also use multi-column primary keys here. If the view is not key preserved, it
will be read-only.
For more information on the format and contents of this table, see
GINDEX_COLUMNS in this appendix.
For more detailed, up-to-date information, see the Oracle Spatial Users Guide and
Reference.
SDO_GTYPE The GTYPE indicates the geometry type (point, line, area, and so
forth) and the dimension (2-D or 3-D) of the entire feature class.
SDO_SRID The SRID is used to identify the native Oracle coordinate system (spatial
reference system). GeoMedia Professional uses its own coordinate system indicator
and ignores this field. The field is NULL by default but may contain values. In the
case of geodetic data, an SRID is required by Oracle. Consult the Oracle Spatial Users
B-5
Guide and Reference document for more information on the SRIDs. If you plan to do
any server-side analysis on spatial data, you should assign an SRID.
SDO_POINT For storing a single point in X, Y, Z. GeoMedia uses oriented point
geometry and does not use SDO_POINT. It will read data written to SDO_POINT but
will not write data there. There is no advantage in using the native point geometry
versus using oriented point geometry. By default, this field will be NULL.
SDO_ELEM_INFO This field is a variable length array of type NUMBER
(maximum size 1048576). The values that make up this array are composed of triplets
that describe how the ordinates are stored in the SDO_ORDINATES array. Each
triplet is interpreted as follows:
OFFSET - Indicates the offset within the SDO_ORDINATES array where the first
ordinate for this element is stored.
ETYPE - Indicates the type of the individual element.
INTERPRETATION - Determines how the ETYPE value is interpreted.
SDO_ORDINATES This field is a variable-length Oracle array of type NUMBER
(maximum size 1048576) that stores the coordinate values that make up a spatial object.
The limit on the number of 2-D coordinate pairs (X,Y) is 524288. For 3-D data, the
limit on the number of coordinate triplets (X,Y,Z) is 349525. This limit is fixed by
Oracle and cannot be changed. This array is always used in conjunction with the
SDO_ELEM_INFO array. The values in the array are ordered by dimension in X, Y,
and Z.
For example, a polygon whose boundary has four two-dimensional points is stored as:
SDO_ORDINATE(X1,Y1,X2,Y2,X3,Y3,X4,Y4,X1,Y1)
Oracle
Gtype
d001
d002
d002
d002
d003
d003
d003
d003
d003
d003
d004
d007
The following table identifies the mapping used when converting from GeoMedias
geometry types to Oracle geometry types (applies only to data changes through the readwrite data server).
GeoMedia to Oracle Element Type Conversion
GeoMedia
Oracle Oracle
Oracle
Oracle Meaning
Geometry Type
Gtype
Etype Interpretation
SpatialPoint
d001
1
1
Point
Orientation Matrix
0
6000
Application-defined
Orientation Matrix
1
0
10g Point Orientation
GraphicText
d001
0
6001
Application-defined
SpatialLine
d002
2
1
Polyline
Spatial Line (Arc)
d002
2
2
Linear arcs only
Composite
d002
4
2
Linear straight line
Polyline
segments and arcs
Boundary
d003
1003
Exterior Ring
Boundary
d003
2003
Interior Ring
Composite
d003
1005
Composite Exterior Ring
B-7
GeoMedia
Geometry Type
Polygon
Composite
Polygon
Raster Polygon
2005
d003
6002
In versions of Oracle prior to 10g, GeoMedia uses its own format for oriented points.
GeoMedias oriented point format adds an application defined Etype of 0 and a custom
GeoMedia Interpretation of 6000 in the ELEM_INFO_ARRAY prior to the definition of
the point. The corresponding entry in the ordinates array will contain the orientation of the
point. An example of the SDO_ELEM_INFO_ARRARY containing a GeoMedia oriented
point is shown below:
SDO_ELEM_INFO_ARRAY(1, 0, 6000, 4, 1, 1)
Oracle 10g introduces a native oriented point format. GeoMedia will automatically use this
format if it detects 10g. In a native oriented point, the rotation matrix uses an
interpretation of 0 and follows the point definition. An example of the
SDO_ELEM_INFO_ARRARY containing a native oriented point is shown below:
SDO_ELEM_INFO_ARRAY(1, 1, 1, 3, 1, 0)
For polygon ring elements, 4-digit ETYPE values are required with the first digit
indicating exterior (1) or interior (2). Ordering the storage of ordinates is also very
important. The basic Eytypes for polygons are as follows:
ETYPE values 4 and 5 are compound elements. They contain at least one header triplet
with a series of triplet values that belong to the compound element. ETYPE 4 is a
compound line string, and the following two 4-digit types represent compound polygons:
B-8
If the ETYPE is a compound element (#005), this field specifies how many
subsequent triplet values are needed to define the element.
If the ETYPE is not a compound element (1, 2, or 3), the interpretation attribute
determines how the sequence of ordinates for this element is interpreted. For
Oriented Points
Simple point features do not convey much information other than a location on a map.
Adding symbols or fonts to a point adds specific meaning and in most cases, these symbols
and fonts have specific orientations. All point features in GeoMedia are symbolized
oriented points rather than simple points.
Prior to 10g, Oracle included only a simple point format that utilized the SDO_POINT
array in the SDO_GEOMETRY object, similar to the following example:
SDO_GEOMETRY (3001, NULL,
SDO_POINT(861906,-482832, 0),NULL,NULL)
In this format, Oracles SDO_POINT array did not store any information about the
orientation of the point. For this reason, GeoMedia's handling of Oracles native point
format, is strictly read-only. For any database server version less than 10g, GeoMedia will
preserve point orientation using a custom format in SDO_GEOMETRY. Here is an
example:
SDO_GEOMETRY (3001, NULL, NULL,
SDO_ELEM_INFO_ARRAY (1,0,6000, 4,1,1),
SDO_ORDINATE_ARRAY (0,0,1, 861906,-482832,0))
The geometrys GTYPE remains the same, 3001, but the SDO_POINT array is now
NULL. In the ELEM_INFO_ARRAY, the triplet 1,0,6000 describes a user-defined
ETYPE (0) with an INTERPRETATION (6000), which GeoMedia interprets as its oriented
point format. The triplet 4,1,1 describes the location of the coordinates in the
SDO_ORDINATE array at OFFSET 4 and indicates a point with the ETYPE of 1 and an
INTERPRETATION of 1. Oracle will skip the user defined ETYPE and will see the
SDO_GEOMTRY as just a standard point. GeoMedia will read the orientation matrix
(0,0,1) and give the point the correct rotation. Rotation matrices are used to improve the
accuracy of calculations. A standard 2D rotation matrix is i,j and to convert this to radians
or degrees, you would use the following:
radians=ATAN2(j/i);
degrees=ATAN2(j/i)*(180/PI);
Oracle introduced a native oriented point format in 10g. This is very similar to
GeoMedias oriented points with the main difference being the location of the rotation
matrix. An example of a geometry containing a native 10g oriented point is shown below:
B-9
If GeoMedia detects 10g or later, it will automatically write oriented points using Oracles
native format. For databases prior to 10g, GeoMedia will continue to write oriented points
using its own format.
In whatever format they are stored, oriented points are treated just like standard point
feature, so entries are required in Oracles USER_SDO_GEOM_METADATA, and a
spatial index must be present.
The geometrys GTYPE is that of a standard three-dimensional point: 3001. Both the
SRID and SDO_POINT fields are NULL. In the ELEM_INFO_ARRAY, the triplet
1,0,6001 describes a user-defined ETYPE (0) with an INTERPRETATION (6001), which
GeoMedia interprets as its text format. The triplet 10,1,1 describes the location of the text
as a point feature at OFFSET 10 with an ETYPE of 1 and an INTERPRETATION of 1.
SDO_GEOMETRY(3001,NULL,NULL,SDO_ELEM_INFO_ARRAY(1,0,6001, 10,1,1),
In the ORDINATE_ARRAY, the first value contains the rotation of the text about the
rotation matrix; the next three values (0,0,1) represent the text rotation matrix. The fifth
value (in this case, 65536) is an integer representation of the format and alignment of the
text. The sixth value, in this case 11, is the number of characters of text being stored
(including spaces). This is followed by integer representations of the actual text where
each integer decomposes into 4 bytes of text. The last 3 values (1919397.1, 680897.264,
0) is the XYZ location of the text (based on the text justification point). Here is the
breakdown:
SDO_ORDINATE_ARRAY(
0, -- Text Rotation Normal
1, -- Point rotation matrix i
0, -- Point rotation matrix j
0, -- Point rotation matrix k
B-10
65536, -- Formatting
11,
A text feature is treated just like a point feature, so entries are required in
USER_SDO_GEOM_METADATA and in the GDOSYS metadata. In addition to the
metadata, a spatial index is also required.
Raster Images
GeoMedia Professional has its own format for the storage of raster images and it also
supports Oracle Spatial's GeoRaster format. Oracle's GeoRaster format,
SDO_GEORASTER, was introduced in 10g. It is a component of Oracle spatial; you
cannot use it with Oracle Locator.
When using its own format, GeoMedia Professional stores rasters similar to the way it
stores text. GeoMedia stores the footprint or MBR of raster images as polygon features
and includes some additional information about the display matrix and the full path to the
image filename. The actual raster image is not stored in the database and is retrieved
through its filename. An example is as follows:
SDO_GEOMETRY (2003, NULL, NULL,
SDO_ELEM_INFO_ARRAY (1, 0, 6002, 22, 2003, 1),
SDO_ORDINATE_ARRAY (112.3,15452.2,15781.3,5124.3,
112.3,15452.2,15781.3,5124.3,112.3,15452.2,15781.3,
112.3,15452.2,15781.3,5124.3,112.3,15452.2,
27,1242134123,134123411,13412341234,13241234123,
1000,1000,1000,10000,10000,10000,10000,1000,1000,1000))
The first 16 values in the ORDINATE_ARRAY store the display matrix for the raster
image. The eighteenth value stores the length of the filename. The integers following the
length are the actual filenames decomposed into four-byte integers. The number of
integers used will depend on the length of the filename. This is followed by the five
coordinate pairs that make up the polygonal outline of the raster image.
By treating the raster image outline as a polygon feature, GeoMedia can make full use of
Oracles spatial filtering capability. Because the raster image is treated a polygon, entries
are required in the USER_SDO_GEOM_METADATA and in the GDOSYS metadata.
Either a Quad-Tree or an RTree spatial index is also required.
GeoRaster is a feature of Oracle Spatial introduced in 10g that will let you store, index,
query, and analyze any raster image or gridded data. Oracle uses two new database objects
to store raster images: SDO_GEORASTER and SDO_RASTER. The use of GeoRaster
data in GeoMedia should be transparent to the user as long as the standard raster metadata
is assigned to the table containing the SDO_GEORASTER datatype. GeoMedia
Professional treats GeoRaster data as read-only. GeoMedia Professional will not write to
Oracle's GeoRaster format but will load and display the data if it is available. For more
information on Oracle's GeoRaster format see the document Oracle Spatial GeoRaster
10g Release 2.
INTEGER (p is null, s = 0)
FLOAT
RAW
BLOB
CLOB
NCLOB
SDO_GEOMETRY
B-12
If your data is three dimensional, you need to include a dimension statement for the Zvalue as follows:
INSERT INTO USER_SDO_GEOM_METADATA VALUES
(TABLE_NAME','GEOMETRY_COLUMN', MDSYS.SDO_DIM_ARRAY (
MDSYS.SDO_DIM_ELEMENT('X',-2147483648,2147483647,0.00005),
MDSYS.SDO_DIM_ELEMENT('Y',-2147483648,2147483647,0.00005),
MDSYS.SDO_DIM_ELEMENT('Z',-2147483648,2147483647,0.00005)),
NULL);
The default values assigned by GeoMedia should fit data for any projection and will work
fine for RTree spatial indexes. For Quad Tree indexes, the default extents are not optimal
for either spatial filtering or analysis. Quad Tree indexes require you to calculate the
actual extents of your data and update the metadata view to reflect those values. Whether
you are using Oracles spatial or locator, the following command will calculate the actual
extent of your data:
SELECT SDO_AGGR_MBR(<sdo_geometry_col>) FROM <table_name>;
The result of this query is a simple polygon in SDO_GEOMETRY format that contains the
lower and upper bounds of the <sdo_geometry_column> in the selected <table_name>.
The values in the SDO_ORDINATE array correspond to the &Xlo, &Xhi, &Ylo, &Yhi
values required in the USER_SDO_GEOM_METADATA view. Extents are never
calculated for Z. If your data is 3-D, just make sure you enter a Z range that you know will
fit your data. For example:
B-14
When assigning the extents, always leave some margin, or buffer, around the outer edge.
This gives your data room to grow without have to re-calculate the MBR and re-index the
feature. A good rule of thumb here is 10%.
For geodetic data using longitude and latitude coordinates, the metadata range must be +/180 and +/-90 similar to that shown below:
INSERT INTO USER_SDO_GEOM_METADATA VALUES
(TABLE_NAME','GEOMETRY_COLUMN', MDSYS.SDO_DIM_ARRAY (
MDSYS.SDO_DIM_ELEMENT('X',-180,180,0.0005),
MDSYS.SDO_DIM_ELEMENT('Y',-90,90,0.0005)),
NULL);
Failure to assign the correct metadata range for geodetic data will lead to incorrect results
for both spatial filter queries and spatial indexing.
The tolerance value used in the SDO_DIM_ARRAY in the above examples is set to
0.0005. The tolerance is used to associate a level of precision with spatial data. For
geodetic data (longitude, latitude), the tolerance value is in meters (a tolerance of 1 would
mean 1 meter). For non-geodetic data, the tolerance value must be a non-negative number
greater than zero that refers to the decimal fraction of the distance unit being used. Oracle
uses the tolerance in its own internal calculations to determine the relationship between
vertices; it has no effect on GeoMedias own tolerance or on internal calculations.
However, tolerance is important when using spatial analysis filters such as INSIDE. For
best results, the tolerance used in Oracle should be very close to GeoMedia's fixed
tolerance of .0005 m.
To use one of Oracles coordinate systems, the SRID of the coordinate system must be
loaded into both the USER_SDO_GEOM_METADATA view and the SDO_SRID
component of the geometry column containing the spatial data. For example, given a
feature class called ROADS containing a GEOMETRY column that requires a SRID of
8307, you could use the following to populate the required column:
UPDATE USER_SDO_GEOM_METADATA SET SRID=8307
WHERE TABLE_NAME=ROADS
AND COLUMN_NAME=GEOMETRY;
UPDATE ROADS A SET A.GEOMETRY.SDO_SRID=8307;
B-15
For the SRID to function correctly, it has to be present in both locations. Once the SRID is
set, the spatial indexes will need to be re-created on the geometry column.
GeoMedia Professional ignores the SRID value used by Oracle because it already has
built-in support for most coordinate systems. There is no direct mapping between Oracles
SRIDs and GeoMedias coordinate systems. You can use the SRID for compatibility with
other applications, and GeoMedia will pass through the value like any other attribute.
In most cases, the SRID is not required and can be left as NULL. In the case of geodetic or
geographic data, Oracle requires the use of the SRID for its own internal calculations with
spatial filters and indexes. If you are using geographic data, you must remember to set the
SRID to the correct value. For example, if your data uses geographic coordinates with a
datum of WGS84, you could use the following query to bring up a list of available SRIDs:
COLUMN
SELECT
FROM
WHERE
AND
RTree Indexes
An RTree index approximates stored geometry by using a minimum bounding rectangle, or
MBR.for each geometry.
B-16
For any given feature class (or layer), the RTree index consists of a hierarchical index on
all the MBRs of the geometries in the feature class.
For example, if the areas 1 through 9 are the geometries (or features) in a given feature
class, then a, b, c, and d are the leaf nodes of the RTree index. The leaf nodes contain the
MBRs of the geometries and the link to the actual geometry. In this case, a contains the
MBR of geometries 1 and 2, b contains the MBR of geometries 3 and 4, and so on. A
contains the MBR of a and b, and B contains the MBR of c and d. The root of the RTree
contains the MBR of A and B, which is the MBR of the entire feature class.
A large number of insert and delete operations on a feature class that uses an RTree index
may degrade the quality of the RTree structure and will adversely affect performance.
Periodically rebuilding the index may be required to improve query performance. Oracle
provides commands that can determine the level of degradation within an RTree index and
can help to determine if a rebuild is required.
To create an RTree index, the rollback segments should be 100*n bytes, where n is the
number of rows of data to be indexed. In Oracle 9i or later, the rollback segments are
managed by the database, so this should no longer be an issue. The amount of time
required to create the index is dependent on the SORT_AREA_SIZE parameter. The
optimal value depends on the database size, but a good guideline is to make it at least 20
MB when you create an RTree index. To change the SORT_AREA_SIZE value
dynamically, use the ALTER SESSION statement. An SQL example is as follows:
ALTER SESSION SET SORT_AREA_SIZE = 20000000;
default spatial index is an RTree index. If you create your own tables, you need to create
the RTree index. The example syntax to create an RTree index is shown below:
CREATE INDEX <index_name>
ON <tablename> (<sdo_geometry_col>)
INDEXTYPE IS MDSYS.SPATIAL_INDEX;
There are other parameters available for the RTree index. These include the ability to
choose the index tablespace and other index optimization parameters. This are covered
thoroughly in Oracles documentation.
For more detailed, up-to-date information, see the Oracle Spatial Users Guide and
Reference.
Spatial indexes are made up of several different database objects. If the CREATE INDEX
statement fails for any reason, you may end up with a partial spatial index. Attempts to reindex or to delete the existing index will return an error stating that the index is marked as
LOADING/ UNLOADING. If this occurs, you will need to add the FORCE keyword to
the DROP INDEX command. Here is an example:
DROP INDEX <index_name> FORCE;
Oracle allows geometries to contain up to four dimensions. The GeoMedia Object Model
Data Server supports both 2-D and 3-D data for read-write operations, but only read-only
operations on 4-D data (LRS). All data is served to the client as 3-D. In the case of 2-D,
the third dimension is assigned a value of zero when reading the data. In the case of 4-D
Oracle data, the fourth dimension is ignored when reading.
RTree indexes can operate in all three dimensions. You can assign 2-D RTree indexes to
3-D data, but if you use true 3-D RTrees, you need to pass spatial filter volumes rather than
a filter area. GeoMedia only supports the ability to pass 2-D filter areas. If your data is
indexed in 3-D, only geometries with a Z value of zero will be returned. Native spatial
analysis tools may also fail if 3-D RTrees are used. It is recommended that you only use 2D RTree indexes at this time even if your data is in 3-D.
Spatial Filtering
Spatial filtering is critical when using large datasets. The more limitations placed on the
amount of data passed to the client, the better the performance will be. When using the
Oracle, all spatial filtering initiated within GeoMedia is actually processed on the database
server. This includes both the coarse first-pass filter and the finer second-pass filter.
Attempting to use a spatial filter without having the required spatial indexes will result in
the following error:
Recordset is invalid.
MORE:
ORA-13226: Interface not supported without a spatial index.
The spatial filter operators in GeoMedia Professional are mapped to the Oracle spatial
filters in the following way (listed in order of performance):
B-18
Coarse Overlap is the fastest performing filter because it uses Oracles single pass
SDO_FILTER function, but the results may exceed the boundary of the filter area. This is
the best filter to use when performance is the only consideration. The other three filters are
treated as standard spatial queries with the filter area being passed to Oracles
SDO_RELATE operator in a bind variable. SDO_RELATE uses a two-pass filter and
produces more accurate results. Of the SDO_RELATE based filters, INSIDE is the
slowest because it is processing a combination of filter masks. It will also give the best
visual results because it will return everything up to and including the boundary of the
filter area.
Native Queries
Native query operations within GeoMedia Professional require the presence of valid spatial
indexes on the tables being queried. Native spatial queries also require significant space in
the TEMPORARY tablespace. The Native Query interface actually builds SQL
statements using Oracles SDO_RELATE function. This is very similar to the spatial filter
command except that, in this case, two feature classes are used as input.
There are three main differences between the spatial querying capability in GeoMedia and
that used by Oracle:
B-19
If you are using attribute filters with your native queries, you must manually insert a table
alias identifier in the query statement. Filters on the Select Features in table must be
prefixed with A, and B must prefix filters on the second Features in table. The Filter
dialog box will let you interactively enter columns, operators, and values, but it is up to
you to enter the appropriate table alias whether it is A or B.
In the following example, an attribute filter is being applied to the Select Features in table.
The prefix A. has to be added to the query string in order for the attribute query to be
properly applied. The result is A. COUNTY_NAME.
to be run from SQL*Plus while connected as a system DBA. The syntax of the create
metadata script is:
@CreateGDOSYS <NET_SERVICE> <GDOSYS_PSWD> <ORA_PROFILE>
<USER_TABLESPACE> <TEMP_TABLESPACE>
where:
<NET_SERVICE> is the Oracle service name.
<GDOSYS_PSWD> is the password to use for the GDOSYS user.
<ORA_PROFILE> is the profile to use when creating the user account.
<USER_TABLESPACE> is the tablespace where the schema will be created.
<TEMP_TABLESPACE> is the temporary tablespace to use.
For example:
@CreateGDOSYS ORCL GDOSYS DEFAULT USERS TEMP
You can also update GDOSYS to the current version using the UpdateGDOSYS.sql script
in the ../GeoMedia Professional/scripts folder. You must connect as DBA to run this
script as well.
The current GDOSYS is backward compatible to GeoMedia Professional 5.2; however,
you must update GDOSYS with every new release of GeoMedia Professional.
Type
ATTRIBUTEPROPERTIES
Table
FIELDLOOKUP
Table
GEOMETRYPROPERTIES
Table
GALIASTABLE
Table
GCOORDSYSTEM
Table
GEXCLUSIONS
Table
GFEATURES
View
GFEATURESBASE
Table
GFIELDMAPPING
Table
GINDEXCOLUMNS
Table
GPARAMETERS
Table
GPICKLISTS
Table
B-21
GDOSYS Object
Type
GQUEUE
View
GQUEUEBASE
Table
MODIFIEDTABLES
Table
MODIFICATIONLOG
Table
GMODLOG
Sequence
GAUTONUMBERSEQUENCE
Sequence
FIELDLOOKUPINDEXID1
Sequence
DELETEMETADATAGMT
Trigger
ATTRIBUTEPROPERTIES
The ATTRIBUTEPROPERTIES metadata table describes the attribute types for the fields
listed in the FIELDLOOKUP table. The common link between this table and
FIELDLOOKUP is the INDEXID column. The definition of the table is:
B-22
FIELDFORMAT Determines the general format of the data being displayed. Format
types include General Number and Date/Time.
FIELDPRECISION Represents the number of decimal places exposed in GeoMedia
Professional. For numeric data types, the default is 6. Usually, this is the same as the
scale defined for the number field.
ISFIELDDISPLAYABLE Determines whether a column is displayed in GeoMedia
Professional. The default value is -1 (TRUE). Use 0 (FALSE) to hide the column.
FIELDLOOKUP
The FIELDLOOKUP metadata table provides a unique identifier (INDEXID) for every
column in every table (feature class) in the users schema. These identifiers are then used
by other metadata tables. The definition of the table is:
INDEXID This field stores the unique identifier for every column in every
table/view. The INDEXID is used as a reference by other metadata tables such as
ATTRIBUTEPROPERTIES and GEOMETRYPROPERTIES. The value is generated
from the GDOSYS sequence FIELDLOOKUPINDEXID1.
FEATURENAME This field stores the table name in the format OWNER.TABLE.
This format is required.
FIELDNAME This field stores each of the column names that are in the associated
field name.
GALIASTABLE
The GALIASTABLE metadata table determines the names used by other metadata tables. It
must be located in the GDOSYS schema, and it must have the specific name
GALIASTABLE. All other metadata tables are referenced via GALIASTABLE. It is the
only table required to be in GDOSYS. If a given user sees the GDOSYS.GALIATABLE,
that user will require metadata for all tables that will be exposed as feature classes in
GeoMedia. The definition of this table is:
B-23
TABLENAME Actual metadata table name as stored. The table names in this field
must be in the format OWNER.TABLE.
Note: One mechanism for allowing different users to have different GALIASTABLES (and,
therefore, different metadata systems) is to have GALIASTABLE actually be a
parameterized view of another table, with the view definition based on the user name so
that each user sees different contents in the view.
GCOORDSYSTEM
GCOORDSYSTEM stores coordinate system definitions. If this table is not present, no
coordinate system transformation will occur, and the GeoWorkspace coordinate system
will be used. This table is not typically user editable because of the large number of
columns and types of parameters required to define a coordinate system. There are four
columns worth noting:
CSGUID A special value used to uniquely identify the coordinate system parameters.
The CSGUID is what associates a geometry object to a GeoMedia coordinate system.
The CSGUID is also used in GEOMETRYPROPERTIES and in GFIELDMAPPING to
associate the coordinate system with the SDO_GEOMETRY field.
CSGUIDTYPE An indicator for whether the coordinate system is permanent or not.
This is really used by the GeoMedia API. In the database table, it should always be set
to 2.
NAME The name the user has assigned to this coordinate system. It is an optional
parameter but should be used because it makes the coordinate system easier to identify,
particularly in the Oracle environment.
DESCRIPTION An optional user-provided description of the coordinate system.
The other attribute fields in GCOORDSYSTEM are not user editable and should not be
modified in any way.
B-24
GEOMETRYPROPERTIES
The GEOMETRYROPERTIES metadata table stores the geometry type, primary geometry
flag, and the coordinate system ID for the SDO_GEOMETRY fields in each feature
classes. The common link between this table and FIELDLOOKUP is the INDEXID
column. This table determines the coordinate system that is assigned to each feature class.
The definition of this table is:
GEXCLUSIONS
The GEXCLUSIONS metadata table is specific to the Oracle Object Model Data Server and
is used to exclude schemas from the initial connection scan. When establishing an Oracle
connection, any schema that the connected user has privileges to see will be scanned for
compatibility. The more schemas that are available to the connected user, the longer the
connection takes. This is one reason it is not recommended to connect as a user with the
DBA role.
The values in GEXCLUSIONS do not hide schemas from GeoMedia; they are only used to
exclude schemas from the initial connection scan. If the table does not exist, the data
server will assume a hard-coded list of Oracle schemas to exclude. If the table does exist,
only those schemas listed in the table will be excluded. The default list of schemas to
exclude if the table is not present is as follows: CTXSYS, MDSYS, OLAPSYS, ORDSYS,
OUTLN, SH, SYS, SYSTEM, WMSYS, WKPROXY, WKSYS, and XDB. The definition
of this table is:
B-26
FEATURENAME This field is the name of the feature class in the format
OWNER.FEATURENAME.
GEOMETRYTYPE This field determines how the data server maps the geometry:
1 Line
2 Area
3 AnySpatial
4 Coverage
5 GraphicsText
10 Point
Refer to the section on Oracle to GeoMedia Element Type conversion for more
information on the values used here.
This view only serves up the feature classes that the connected user has privileges to select.
All other feature classes are hidden. You can set up the GFEATURES view as you see fit;
however, it must have the same definition as the GFEATURESBASE table. If you are
using only one GeoMedia warehouse or want to expose all GeoMedia feature classes to all
users, you do not need to use the view; simply rename GFEATURESBASE to
GFEATURES.
GFIELDMAPPING
The GFIELDMAPPING metadata table is specific to the Oracle Object Model Data
Servers, and it is not used directly by GeoMedia. The values in this table are used to
override various aspects of field definitions. Information stored here typically consists of
the primary key column and the primary geometry with their associated GeoMedia data
types, coordinate system IDs, and any assigned sequences. The definition of this table is:
B-27
B-28
DATA_SUBTYPE This field is used when the DATA_TYPE is 32 or 33; the subtype
determines the graphic type.
1 Linear
2 Areal
3 AnySpatial
4 Coverage
5 - GraphicsText
10 - Point
See the GeoMedia Type Mapping section for more information on the values used
here.
CSGUID This field is the coordinate system assigned to the primary geometry field.
It corresponds to the CSGUID in the GCOORDSYSTEM table.
SEQUENCE_OWNER This field is the database owner of the sequence used for the
autonumber field.
GINDEX_COLUMNS
The GINDEX_COLUMNS metadata table is specific to the Oracle Object Model Data
Servers. The values in the table are used to specify the primary or unique key fields of
views that are to be used in GeoMedia. This table is populated using Database Utilities.
The only limitation to using GINDEX_COLUMNS is that only one column may be
specified as a primary key for the view. The definition of this table is:
If a view does not have a key defined in the GINDEX_COLUMNS, the Oracle Object data
server will attempt to determine the underlying table for the view and will use any primary
key defined for that table. In this case, only simple views will be editable. All other views
will be read-only.
GPARAMETERS
The GPARAMETERS metadata table contains parameter/value pairs. GPARAMETERS is
used by the data server (never directly by GeoMedia) when a geometry field is created.
The values in this table are used to set various parameters in Oracle as the geometry field is
created and indexed. It consists of two columns, GPARAMETER and GVALUE.
B-29
The default GPARAMETER values for the Oracle Object Model Data Servers are the
following:
GParameter
SpatialIndexLevel
NumberOfTiles
MaxLevel
X_LowerBound
X_UpperBound
X_Tolerance
Y_LowerBound
Y_UpperBound
Y_Tolerance
Z_LowerBound
Z_UpperBound
Z_Tolerance
Type
Long
Long
Long
Double
Double
Double
Double
Double
Double
Double
Double
Double
Default GValue
1
1
1
-2147483648
2147483647
.000005
-2147483648
2147483647
.000005
-2147483648
2147483647
.000005
Comments
Tessellation (Index) Level
Maximum Number of Tiles
Maximum Level (for Hybrid)
X Minimum of MBR
X Maximum of MBR
X1=X2 if |X1-X2| < X_Tolerance
Y Minimum of MBR
Y Maximum of MBR
Y1=Y2 if |Y1-Y2| < Y_Tolerance
Z Minimum of MBR
Z Maximum of MBR
Z1=Z2 if |Z1-Z2| < Z_Tolerance
Although GVALUE values are strings, the types listed above are what the string is
converted to during processing.
If this table does not exist or does not have an entry in GALIASTABLE, the data server
cannot create geometry fields. If the table exists, has an entry in GALIASTABLE, and is
populated with at least every parameter except for the Z entries, then the geometry fields
can be created and indexed. If Z parameters are absent, 2-D geometries are created. If Z
parameters are present, 3-D geometries are created.
The default coordinate system assigned to a schema is also listed here. The format for
default coordinate system entries is as follows:
GPARAMETER: <USER>.DEFAULTCOORDINATESYSTEM
GVALUE: <CSGUID>
GPICKLISTS
The GPICKLISTS metadata table contains the Pick Lists assignements used by the
Attribute Properties dialog box in GeoMedia Professional. Also known as domains, Pick
Lists allow for a pre-defined list of values to be used when updating attribute fields.
GPICKLISTS is defined as follows:
B-30
FEATURENAME Refers to the feature class that will use the PickList. The
FEATURENAME should be in the format OWNER.FEATURECLASS.
FIELDNAME Refers to the specific attribute field in the feature class that will use
the Pick List.
PICKLISTTABLENAME Specifies a table in the schema containing the PickList
values. This could be a new or an existing feature class.
VALUEFIELDNAME Specifies the field in the Pick List table that contains the
values to be stored in the database. The datatype of the field in the Pick List table
specified here must match the datatype of the attribute assigned in the FIELDNAME.
DESCRIPTIONFIELDNAME Specifies the field that contains PickList descriptions
to be displayed in the pop-up menu on the Properties dialog box.
Note: 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 PickList. The filter allows a single Pick List table to be
used when creating multiple PickLists.
Pick List 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 values and
description entries) or as a domain list (when value and description entries are the same).
Ranges are not supported. It is up to the DBA to populate the PickList metadata table with
the appropriate entries for the various schemas containing feature classes.
B-31
FIELDNAME
PICKLIST
TABLENAME
VALUE
FIELDNAME
OWNER.BUILDINGS
NAME
OWNER.PL_BUILDING
CODE_VALUE
OWNER.BUILDINGS
STATE
OWNER.PL_STATE
STATE_NAME
OWNER.BUILDINGS
TYPE
OWNER.PL_BUILDING
CODE_VALUE
DESCRIPTION
FIELDNAME
FILTERCLAUSE
VAL_DESCRIPTION
BLD_TYPE = 'NAME'
DESC
VAL_DESCRIPTION
BLD_TYPE = 'TYPE'
OWNER.PL_BUILDING
CODE_VALUE
VAL_DESCRIPTION
BLD_TYPE
MOTEL
TYPE
MARRIOT
NAME
HOLIDAY INN
NAME
TYPE
DAYS INN
NAME
OWNER.PL_STATE
B-32
STATE_NAME
DESC
ALABAMA
ALABAMA
ARKANSAS
ARKANSAS
COLORADO
COLORADO
TEXAS
TEXAS
FLORIDA
FLORIDA
The Queued Edit process accesses GQUEUEBASE through a view called GQUEUE that
is defined as follows:
CREATE OR REPLACE VIEW GQUEUE AS
SELECT QUEUENAME,TABLENAME,QEDITEMDCSFIELDNAME,QEDSTSFIELDNAME,QEDCREATOR,
QEDNUMGEOMFIELDNAMES,QEDUSEFORMBRGEOMFIELDNAMES,QEDADDGEOMFIELDNAMES,
QEDNUMSTATUSLIST,QEDSTATUSLISTNAMEVALUE,QEDSORTFIELDNAME,QEDSORTASCENDING,
READONLYFIELDNAMES,NONDISPLAYABLEFIELDNAMES,NONLOCATABLEFIELDNAMES
FROM GDOSYS.GQUEUEBASE
WHERE EXISTS
(SELECT 1 FROM ALL_OBJECTS
WHERE OBJECT_TYPE = 'TABLE'
AND OWNER = SUBSTR(TABLENAME,1,INSTR(TABLENAME,'.',1)-1)
AND OBJECT_NAME = SUBSTR(TABLENAME,INSTR(TABLENAME,'.',1)+1))
This view ensures that the user sees only the queues for the tables or views they have
privilege on. By default, privileges on both GQUEUEBASE and GQUEUE are granted to
PUBLIC. The DBA can change this if needed. Any user that needs to create static queues
must have SELECT, INSERT, UPDATE and DELETE privileges on both GQUEUEBASE
B-33
and GQUEUE. Users who review static queues will require SELECT privilege on both
GQUEUEBASE and GQUEUE.
MODIFIEDTABLES
The MODIFIEDTABLES is a required metadata table that lists the tables that are tracked in
the MODIFICATIONLOG. As tables are edited, entries are automatically added to the
MODIFIEDTABLES table if they do not already exist. The definition of this table is as
follows:
MODIFIEDTABLEID This field contains the OBJECT ID for the tables and views
that will be tracked in the MODIFICATIONLOG table.
TABLENAME - This field contains the table/view name in the format of
OWNER.TABLENAME.
KEYFIELD1-KEYFIELD16 KEYFIELD1 contains the primary key identifier for
the table ( or view). If multi-column primary keys are used, the other KEYFIELDs
will store each column making up the primary key.
This table is never cleared and over time, as tables are deleted, may contain orphans. To
improve performance, this table can be periodically truncated. However, do not clear this
table while there are open GeoMedia Professional sessions. The Clear Modification Log
command in Database Utilities will truncate this table and the MODIFICATIONLOG
table.
B-34
MODIFICATIONLOG
The MODIFICATIONLOG metadata table tracks modifications made to all GeoMedia
feature classes. This required table is used to track all inserts, updates, and deletes made to
the tables listed in MODIFIEDTABLES. This table is defined as:
B-35
Because all edits made to all feature classes in the Oracle instance are tracked in the
MODIFICATIONLOG table, this table can grow very large very quickly. The size of the
MODIFICATIONLOG table can negatively impact editing performance in GeoMedia
Professional, so the table should be periodically truncated. However, do not clear this table
while there are open GeoMedia Professional sessions. The Clear Modification Log
command in Database Utilities will truncate this table and MODIFIEDTABLES. You can
also use the following SQL to clear this table:
TRUNCATE TABLE GDOSYS.MODIFICATIONLOG
For best results, set up an Oracle job that will automatically truncate the
MODIFICATIONLOG table on a periodic basis. Following is an example of this type of
job:
CREATE OR REPLACE PROCEDURE CLEAR_MODLOG is
BEGIN
EXECUTE IMMEDIATE 'TRUNCATE TABLE GDOSYS.MODIFICATIONLOG';
END;
/
-- Create the job
BEGIN
dbms_job.isubmit(1,'CLEAR_MODLOG;',SYSDATE,+1/24,'SYSDATE+1');
END;
/
If you do create a job for this process, make sure you schedule it to run when no GeoMedia
sessions are active.
Modification logging can be performed with triggers as an alternative to the automatic
logging done by GeoMedia Professional. These triggers also allow tracking of changes
made outside of GeoMedia Professional. This ensures that GeoMedia Professional
sessions are aware of any data changes being made by other non-GeoMedia Professional
sessions. Use Database Utilities to set up these modification log triggers.
Sequences in GDOSYS
GDOSYS uses three sequences to populate specific fields used by the metadata tables.
Never use these sequences for your own purposes. These sequences are as follows:
B-36
Triggers in GDOSYS
DELETEMETADATAGMT is the only trigger maintained in GDOSYS. This trigger checks
for and deletes the associated metadata entries in GDOSYS whenever a table or column is
deleted anywhere in the Oracle database.
Not all metadata tables are cleared by this trigger. Any references to the deleted table in
MODIFIEDTABLES or MODIFICATIONLOG will still exist. The Clear Modification
Log command in Database Utilities should be used to clear these tables of entries. The
coordinate system used by the deleted table is also retained in the GCOORDSYSTEM
table. This is important because tables in this and other schemas may use the same
coordinate system as the deleted table.
Oracle metadata entries are not affected by this trigger. A deleted table will still have
entries in USER_SDO_GEOM_METADATA. This can cause a problem if you are
creating a new table using the same name as one previously deleted. You must manually
clear the entry from Oracles metadata or define a trigger in the affected schema that will
handle this automatically. An example of this trigger is as follows:
CREATE or REPLACE TRIGGER DROP_USGM_TRIG
AFTER DROP ON SCHEMA
DECLARE
v_EXIST INTEGER;
BEGIN
SELECT COUNT(1) into v_EXIST
FROM USER_SDO_GEOM_METADATA
WHERE TABLE_NAME = sys.dictionary_obj_name;
IF v_EXIST >0 THEN
DELETE FROM USER_SDO_GEOM_METADATA
WHERE TABLE_NAME = sys.dictionary_obj_name;
END IF;
END;
/
GCOORDSYSTEM.CSGUID = GFIELDMAPPING.CSGUID =
GEOMETRYPROPERTIES.GCOORDSYSTEMGUID
GEOMETRYPROPERTIES.INDEXID =
ATTRIBUTEPROPERTIES.INDEXID =
FIELDLOOKUP.INDEXID
FIELDLOOKUP.FEATURENAME =
GFEATURES.FEATURENAME
MODIFIEDTABLES.MODIFIEDTABLEID=
MODIFICATIONLOG.MODIFIEDTABLEID
Exercise caution when making direct edits to the metadata tables in GDOSYS. If you do
not include all the required information, you may get strange results in the GeoMedia
environment. For best results, any metadata changes should be made using Database
Utilities.
where <user> is the username you want to create and <pswd> is the password for that user
account. If this is the account that will contain the spatial data, tables, views and other
objects, you will need to assign specific privileges to give the account that capability. The
following privileges are just an example:
GRANT
GRANT
GRANT
GRANT
GRANT
GRANT
The UNLIMITED TABLESPACE role is optional but can be useful when creating and
populating spatial tables. The CONNECT and RESOURCE roles are common and are
required if your user needs to create database objects. The CREATE TABLE and
CREATE SEQUENCE privileges are required in order to use spatially related PL/SQL
functions and procedures. These must be granted explicitly and cannot be granted as part
of a role. The MERGE ANY VIEW privilege is required if you are using Oracle 10.2 or
later and it also must be granted explicitly. MERGE ANY VIEW allows the optimizer to
improve query performance and is essential when dealing with spatial data.
Two main rules apply to user account creation:
B-38
Never create a user account in the SYSTEM Tablespace. Typically, a user is created in
the USER tablespace with temporary storage in TEMP. The actual tablespace used is
up to the DBA.
Never assign the DBA role to a master or standard user account if you plan to use it
with GeoMedia. The DBA role can have serious performance implications for
GeoMedia connections.
Satellite user accounts generally contain no database objects. They exist to allow a specific
user varying degrees of privilege on the master schema, which hold the database objects
(tables, views, and so forth.). All users that need to access a spatial schema need to have,
at a minimum, SELECT privilege on all the objects in both GDOSYS and in the master
schema. In addition to SELECT, here are some typical configurations and the required
privileges:
Master User and Schema Schema objects can only be created by master user.
Admin User Has full control of master schema.
o GRANT ALL on all database objects in GDOSYS.
o GRANT ALL privileges on the master schema.
Viewing User Has read-only access to all objects.
o SELECT on all GDOSYS objects.
o SELECT on all master schema objects.
Editing User Has edit capability on some feature classes but not others and cannot
remove or delete data. Cannot create objects.
o Grant INSERT and UPDATE on GDOSYSs MODIFIEDTABLES AND
MODIFICATIONLOG
o Grant INSERT and UPDATE on GDOSYSs GQUEUE AND GQUEUEBASE so
the user can create and modify static queues in GeoMedia.
o INSERT and UPDATE on all read-write tables and sequences in master schema.
Add DELETE for the ability to delete data.
Tables
Tables can be created using GeoMedia Professionals Feature Class Definition or using
native Oracle commands. The benefit of using Feature Class Definition is that the
maintenance of the metadata is handled transparently. However, data types assigned via
Feature Class Definition have to be converted to native Oracle data types. This is not the
case if you create tables directly in Oracle. Using SQL, you can create spatial tables just
like standard tables, the difference is that you include a column using the spatial datatype.
Here is an example of creating a table called STATES that contains two separate geometry
fields.
CREATE TABLE STATES (
PID NUMBER(38) NOT NULL PRIMARY KEY,
ST_NAME VARCHAR2(64),
GEOM1 MDSYS.SDO_GEOMETRY,
GEOM2 MDSYS.SDO_GEOMETRY);
B-39
When creating tables, make sure you use a primary key column(s). Primary keys are
required for read-write access and will also improve performance.
If you have existing tables, you can add a field to hold the geometry using Oracles
ALTER table command:
ALTER TABLE STATES ADD (GEOMETRY MDSYS.SDO_GEOMETRY);
If you create tables outside of GeoMedia Professional, you will need to assign the required
metadata for both Oracle and for GeoMedia. You will also need to spatially index your
geometry fields.
Non-spatial attribute only tables can also be created and used. In this case, GeoMedia still
requires metadata but Oracle does not.
Table and column names must always be expressed in upper case. Mixed case and lower
case names are not allowed. When using Feature Class Definition, table names are
restricted to 24 characters. If you create the tables directly in Oracle, you can use the full
30 character maximum allowed by Oracle. Keep in mind that other applications may also
impose length restrictions.
Default Values
Default values can simplify data entry and supply values for columns that are either
required or just need to have a specific entry. Default values are honored by GeoMedia but
not directly. When inserting a new record with the option to display the Attribute
Properties dialog box turned on, the default values are not shown in the dialog box even
though they are available at the database level. They will be used when the insert occurs.
If the fields are required, you will not see an error, instead, the insert will pick up the
default values. However, if the option Copy Attribute Values from Previous Feature is
enabled, you will no longer be able to use the default value. Instead, the value used in the
previous insert will be used. If you delete the previous value used in a required field, the
default value will still not be used and you will get an error message.
For best results with defaults, either turn off the Copy Attribute Values from Previous
Feature option or do not make the fields required. Functional based defaults will work but
again, you must turn off Copy Attribute option. This same problem will occur if you are
using triggers to populate required fields.
and still be updatable. In addition, only the side of the join containing the key will be
updatable.
To determine whether a view/join-view is updatable or not, you can check the Oracle view
USER_UPDATABLE_COLUMNS:
SELECT * FROM USER_UPDATABLE_COLUMNS
WHERE TABLE_NAME=view_name;
Views can be added to the GDOSYS metadata using Database Utilities. As with tables,
views that contain a column of type SDO_GEOMETRY must also have an entry in
USER_SDO_GEOM_METADATA (Oracle does not require this, but GeoMedia does).
All references to views in GALIASTABLE, MODIFIEDTABLES, GFEATURES, and
FIELDLOOKUP will be expressed as OWNER.VIEW.
The following three steps are required to make a view compatible with GeoMedia
Professional:
1. Creating a View Create a view in Oracle. For read-write capabilities, the view
definition must contain a primary key column from the underlying base table. Multicolumn primary keys are allowed.
2. Update USER_SDO_GEOM_METADATA All views that contain a column of type
SDO_GEOMETRY need to have an entry in Oracle's spatial metadata view
USER_SDO_GEOM_METADATA.
3. Run GeoMedia Professional's Database Utilities The Oracle Object Model data
server treats Oracle views as standard GeoMedia feature classes. The views are
handled in a special way through Database Utilities.
While inserting feature class metadata, the Attributes tab of the feature class
Properties dialog box of the view will have a special button for selecting the primary
key for the view. The column selected must be unique, not null, and should be the
same as the key column in the base table. This pseudo-key column makes the view
key preserved. Database Utilities will populate the GDOSYS.GINDEXCOLUMNS
table with the necessary information to make the view read-write inside GeoMedia
Professional.
4. For insert operations, GeoMedia must populate the primary key value itself; it cannot
be populated through a trigger. To force this, assign the datatype for the column
selected to be the key (in Step 3) to autonumber, and pick the sequence associated with
the same column in the base table.
Modifiable join-views are the most difficult to work with. In this case, the primary and
foreign keys should be explicitly defined in the underlying base tables. The concept of
key-preserved tables is fundamental to understanding the restrictions on modifying join
views. For more information, refer to Oracle's documentation on modifiable join-views. If
you need to have full edit capability on your join views, you need to make use of instead
of triggers.
B-41
The following is an example of a join-view that has a join relation between a graphic
feature class (PARCEL_GEOM) and a non-graphic feature class (PARCEL_INFO):
CREATE VIEW PARCEL_GEOM_AREA_INFO AS
SELECT G.GEOMETRY, G.PARCEL_ID, G.AREA, G.PID, P.LOCNO,
P.RECTYPE, P.YEARBUILT, P.API_VALUE1, P.LANDUSE_CODE
FROM PARCEL_GEOM G, PARCEL_INFO P
WHERE G.PID = P.PID
AND G.AREA >= 100000
AND G.AREA <= 200000;
If you plan to edit join-views, you should ensure that the autonumber sequence assigned to
the key on the base table key is also assigned to the same key used in the view. This will
ensure that the base table sequence remains in sync. Also, GeoMedia must be able to
populate this pseudo key field in order to perform inserts. This can be done manually or by
changing the datatype of the key field to autonumber and using the sequence assigned to
the base table. Use Database Utilities for sequence assignments.
When you inset, update, or delete a record from a view, the underlying base table is
modified by Oracle. If you are displaying both the base table and the view in the
GeoMedia map window, only the view will be updated. This happens because Oracle, not
GeoMedia Professional, is updating the base table. For notification of the change to reach
GeoMedia Professional, you will need to set up Modification Log Triggers on the base
table. These triggers ensure that changes to the base table made outside of GeoMedia are
reflected inside of GeoMedia Professional without having to close and re-open the
database connection. Manually adding the views information to the Modification Log
Trigger of the base table will also ensure proper notification for the view when the base
table is updated. Modification Log Triggers are optional and can be created using
Database Utilities.
See Modification Logging in this appendix for more information.
Materialized views can be used through the OOM server to increase the speed of queries,
especially native queries, on very large datasets. Rewriting queries to use materialized
views rather than detail tables (feature classes) greatly improves response time. However,
materialized views are treated as snapshots (by both Oracle and GeoMedia) and are
considered read-only. An example of a materialized view is the following:
CREATE MATERIALIZED VIEW CITIES_INSIDE_STATES AS
SELECT A.STATE_NAME, B.GEOMETRY, A.ID, B.CITY_NAME
FROM STATES A, CITIES B
WHERE SDO_RELATE(B.GEOMETRY,A.GEOMETRY,'MASK=INSIDE
QUERYTYPE= JOIN')='TRUE'
AND A.STATE_NAME LIKE 'A%';
Triggers
Database triggers can be an extremely useful tool to manage and control data and to
enforce data rules and logic. Some of the more commonly used areas include logging,
DML operations, and the enforcement of data rules.
B-42
Modification Logging
GeoMedia Professional automatically records insert, update, and delete operations on
features in the GDOSYSs MODIFICATIONLOG table. Changes to the schema made
outside GeoMedia Professional are not recorded. To make external changes visible to
GeoMedia Professional while in a session, you need to set up modification triggers. These
triggers are assigned to table-based feature classes using the GeoMedia Professional
Database Utilities. The trigger name will be <FEATURE_CLASS>GMT. For example,
the trigger on STATES would be STATESGMT. A single trigger handles the insert,
update, and delete operations.
If GeoMedia Professional detects the presence of the modification log triggers, it will use
them rather than its own internal logging. The use of triggers may improve performance in
editing operations because modification logging is being done by the server.
Views pose a different kind of problem because normal triggers cannot be assigned to
views. When a view is edited, Oracle is actually editing the underlying base table.
GeoMedia will automatically log modifications for the view, but will not show an update
for the base table unless a modification log trigger is created on the base table.
Another issue arises when both the view and the base table are displayed on the legend in
GeoMedia. If a change is made to the view and a modification log trigger is active on the
base table, updates to the view will also cause an update on the base table. The changes
will be immediately visible in the map window. If the base table is updated, the view will
also be updated at the database level. GeoMedia will not be aware of that change and will
not show it in the map window unless the warehouse is closed and re-opened. There are
two ways to avoid this issue:
You can add entries for the view to the base tables modification log trigger. These
can be quite complicated to set up and requires knowledge of PL/SQL. They can also
lead to a redundant entry for the view in the MODIFICATIONLOG table because both
GeoMedia and the trigger will add an entry for the view.
The best solution here is to create another trigger on the base table that uses the name
of the view. For example, the trigger for STATES_VIEW would be called
STATES_VIEWGMT. The trigger would fire for the base table STATES but would
update the MODIFCATIONLOG table for the view. The trigger itself would be nearly
identical to the base table's trigger STATESGMT, which would also fire. To do this,
make a copy of the trigger used for the base table, rename it to reflect the view's name,
and then change the references to the base table in the body of the trigger to reference
the view instead.
Sequences
Another important use of triggers is to automatically utilize the sequence when using an
integer-based primary key. GeoMedia will use the sequence automatically if the metadata
B-43
for the key field is set to Autonumber. If you edit the table outside of GeoMedia, the
sequence will not be automatically used unless you create a trigger to handle it. An
example of this type of trigger for a feature class called STATES is shown below:
CREATE OR REPLACE TRIGGER STATES_INSERT_TRIG
BEFORE INSERT ON STATES
REFERENCING OLD AS OLD NEW AS NEW FOR EACH ROW
BEGIN
IF :NEW.ID IS NULL THEN
SELECT STATES_ID_SEQ.NextVal
INTO :NEW.ID FROM dual;
END IF;
END;
/
You can assign sequence for use with any numeric field, but only one field can have the
distinction of being autonumber.
INSTEAD OF Triggers
INSTEAD OF triggers are special types of trigger used to maintain views, specifically join
views. These triggers are nothing more than a PL/SQL procedure that uses the columns of
the view as the input parameters. Using this type of trigger allows you to edit join views
by managing the insert, update, and delete operations for the underlying base tables. This
is the only way to have full read write access to join views.
Remember, for inserts to be successful, GeoMedia must populate the primary key
automatically. If the 'instead of' trigger populates the primary key, the insert will fail.
Using GeoMedia Professional's Database Utilities, change the datatype for the column in
that is the pseudo key to autonumber and assign the base table's sequence to the column.
When modifying the data in a join view using GeoMedia Professional, the software will
first attempt to write directly to the view. If an INSTEAD OF trigger is available, the
trigger will process the insert, update, or delete operation. If a trigger is not available,
Oracle will attempt to write directly to the underlying tables. This may return an error
result from Oracle. If you are using triggers to populate required fields, make sure you
turn off the Copy Attribute Values from Previous Feature option.
Database Utilities
The Database Utilities tool consists of several utilities for managing and updating
GeoMedia metadata in Access, Oracle, and SQL Server databases. These utilities are
delivered with GeoMedia Professional and GeoMedia Web Map. These are DBA utilities
and should not be used by normal database users.
See the Database Utilities online Help for complete information on these utilities.
You can access Database Utilities from Start > Programs > GeoMedia Professional >
Utilities > Database Utilities.
B-44
To use Database Utilities to create the GDOSYS schema, you will need to log in to Oracle
as a DBA or system/manager to create and to populate the necessary GeoMedia metadata.
For operations involving a specific schema, you can log in as the user who owns the
schema if that user has full privileges on the GDOSYS metadata schema.
If the GDOSYS schema does not exist in your Oracle database, you will need to create it
before any of the commands will work. Use the Create Metadata Tables button to create
and populate the GDOSYS schema. You will need to be connected as DBA for this to
work correctly. This command is useful in two ways: 1) It creates metadata tables for
native databases, and 2) it checks and repairs sparse metadata or updates metadata for new
releases. Once the GDOSYS schema is created, you will not be prompted to create it again.
The Oracle 10g Client software has been loaded, and a host has been configured using
Oracles Network Configuration Utility.
The database schema resides in Oracle 9.2 or later.
USER_SDO_GEOM_METADATA is populated with the extents of the data stored in
all SDO_GEOMETRY columns in the schema.
An RTree index has been created for every geometry field.
The GeoWorkspace coordinate system used to view the data is in the same coordinate
system as the data.
The metadata schema, GDOSYS, has been created in the database instance, and
appropriate privileges have been assigned.
All the tables in the schema that that will be used in GeoMedia have the appropriate
metadata entries in GDOSYS, including a coordinate system. Metadata is required for
both graphic and non-graphic tables. Adding the appropriate entries and the associated
coordinate systems can be done using Database Utilities.
Here is an example of the steps required to make an existing schema available in the
GeoMedia environment. In this example, you have an existing spatial schema in Oracle
called USA_DATA containing two feature classes, STATES and COUNTIES.
For read-only connections to USA_DATA, you need to ensure that the Oracle metadata
view USER_SDO_GEOM_METADATA has been populated with the correct values. Use
the following SQL to see if there are existing entries:
SELECT * FROM USER_SDO_GEOM_METADATA;
If there are no entries, you will need to create them. The simplest way is to just insert the
default range:
B-45
The next step in preparing data is to create the spatial indexes that are required for spatial
filters. The easiest index to create is an RTree index, and the syntax is shown below:
CREATE INDEX STATES_RT ON STATES(GEOMETRY)
INDEXTYPE IS MDSYS.SPATIAL_INDEX;
CREATE INDEX COUNTIES_RT ON COUNTIES(GEOMETRY)
INDEXTYPE IS MDSYS.SPATIAL_INDEX;
These feature classes are now ready for display in GeoMedia Professional through a readonly connection. Because the coordinate system is not known, you will need to ensure that
the workspace contains the correct coordinate system for your data. Features will be
displayed as a spatialAny or a Compound data type.
For a read-write connection, GeoMedia metadata must be present and populated with the
correct values. This requires the existence of the GDOSYS metadata schema. Create and
populate the GDOSYS schema using the following steps:
1. Open Database Utilities and connect to your Oracle instance as system/manager (or
any DBA user).
2. Click Create Metadata Tables.
GDOSYS should be created.
3. Once GDOSYS has been created, click Change to connect the schema containing your
data (in this case, USA_DATA).
4. On the Database Utilities dialog box, click Insert Feature Class Metadata.
A list of available features is listed on the left side of the dialog box.
5. Select the features to add by moving them to the right side of the dialog box.
6. Select each feature class on the right, and then click Properties.
7. If you need to assign/create a sequence for a primary key or other column, select the
Attributes tab; then set the data type of the column you want to sequence to
Autonumber.
You are prompted to select and assign a sequence to that column.
B-46
8. Select an existing sequence, or create and assign a new sequence. Sequences can only
be assigned to integer data types.
9. On the Feature Class Properties dialog box, select the Geometry tab, and assign the
correct geometry type to the Geometry column using the spatial data types wherever
possible.
10. Continue assigning the appropriate properties to each feature you want to add.
11. When finished, click OK on the Insert Feature Class Metadata dialog box.
You are prompted to assign a coordinate system to the list of features.
12. Pick an existing coordinate system, or create and assign a new coordinate system.
Optionally, set the coordinate system as the default coordinate system for the schema.
After metadata has been assigned, you can establish read-write connections to the schema
through GeoMedia.
Use Oracle statements to construct the table definitions and to insert the required data.
Once the schema is defined and loaded, you will need to populate the Oracle metadata
USER_SDO_GEOM_METADATA, index the data, and then use the Database
Utilities to populate the required metadata in the GDOSYS schema (for read-write
access).
Use the GeoMedia Professional Output to Feature Classes command to import table
definitions and data from other data warehouses, for example, ArcView or MGE. In
this case, Oracle metadata, indexes, and the GDOSYS metadata are populated for you.
The spatial indexes will not be optimal, so re-indexing will probably be required.
Use the GeoMedia Professional Export to Oracle Object Model command to output a
set of SQL Loader files that will construct the database tables and bulk load the data.
In this case, both Oracle metadata and the GDOSYS metadata are populated for you.
The data will need to be spatially indexed.
Create new feature classes using the GeoMedia Professional Feature Class Definition
command, and populate the data by digitizing new elements in the map window. In
this case, Oracle metadata, indexes, and the GDOSYS metadata are populated for you.
Because the default index is RTree and the newly created table is empty, the table will
need re-indexing once data is loaded.
B-47
B-48
Connections
GeoMedia applications require specific metadata tables to exist in the SQL Server database
before connection. This metadata is created during the bulk import of data (from
GeoMedia Professionals Export to SQL Server command) or by using GeoMedia
Professionals Database Utilities.
See the GeoMedia Metadata Requirements section of this appendix for a list of the
required tables.
In order to make a connection to SQL Server, you must provide a valid username, the
database name, and the name or address of the server that houses SQL Server. SQL Server
has two modes for validating users: Windows domain authentication and SQL Server
authentication.
If the SQL Server connection is set to use Windows authentication (the default), your
domain login account will need to be added to SQL Server by a database administrator,
and appropriate privileges will need to be granted on the databases you want to access. On
connection, you will only need to supply the server name and the database name.
C-1
If you are using SQL Server authentication, you will need to have a valid SQL Server user
account and password as well as the appropriate privileges on the database you want to
connect to. When connecting, you will need to enter your SQL Servers server name, your
user name and password, and the name of the database to use.
Password Persistence
When using SQL Server authentication, GeoMedia stores the SQL Server connection
password in the GeoWorkspace. This is meant as a convenience and allows users to open
existing GeoWorkspaces containing SQL Server connections without having to re-enter
connection passwords. However, this is a drawback to those users wanting higher levels of
security. If you do not want the passwords to be persisted in the GeoWorkspace, you must
use domain authentication. Domain authenticated connections do not store any user or
password information in the GeoWorkspace and have the added benefit of not prompting
you to re-enter passwords.
Permissions
In SQL Server warehouses, access to database objects is controlled by the objects owner
through the use of permissions. GeoMedia requires all objects in your SQL Server
database to be owned by a Database Owner (DBO). Objects that are not owned by DBO
will not be accessible or visible in GeoMedia except by the user who created them.
When creating database objects using GeoMedia Professionals Feature Class Definition
command, the user account must be assigned either the db_owner role or the db_ddladmin
role. For database objects created outside of GeoMedia Professional, only a user account
with the role db_owner will ensure that the resulting objects are owned by DBO.
Users that need read access should be assigned the db_datareader role. Users that need
write access should be assigned the db_datawriter role. All other specific SQL Server
privileges are honored as long as the DBO ownership criterion is met.
C-2
All SQL Server database objects must be owned by DBO. Users that create objects in
the database must have the db_owner role.
Names of tables, views, indexes, and fields are always expressed in their defined cases.
The server will preserve the case of identifiers but will be case-insensitive on
comparisons.
A local SQL Server client is not required; however, client-side tools are required in
order for the server field to be automatically populated on the New Connection dialog
box. These tools are also required when importing data generated by the Export to
SQL Server command. If the client is not loaded, you will need to manually enter the
server name where indicated.
Do not use SQL Servers TIMESTAMP datatype. This datatype is not related to
date/time functions and is not supported. A list of supported data types is presented in
the SQL Server data model section. Datatypes that do not appear in the list are not
supported.
For read-write access to tables, a primary key must be defined. Multi-column primary
keys are allowed. Use auto-increment primary key columns for the best results.
Views are editable as long as they are key preserved and have the appropriate metadata
entries in GindexColumns.
GeoMedia metadata must be present prior to making a connection to the database. The
required metadata can be created using GeoMedia Professional's Database Utilities.
Metadata entries must exist for all table or views in order for them to be visible in the
GeoMedia environment. Database Utilities can be used to make the metadata
assignments.
<Geometry>_XLO
float(8)
<Geometry> _YLO
float(8)
<Geometry> _XHI
float(8)
<Geometry> _YHI
float(8)
<Geometry>
varbinary(max) or image(16)
The <Geometry> column is a binary image that stores information required to reconstruct
the spatial feature associated with this table. Depending on how it was created, it may have
C-3
a different name from Geometry. In SQL Server 2000, the datatype of the geometry
column was image(16). This datatype has been de-supported in SQL Server 2005, and the
new preferred geometry datatype is varbinary(max). Legacy datasets can still use
image(16), but behind the scenes they are being interpreted as the new datatype.
The XLO, XHI, YLO, and YHI columns contain the minimum bounding rectangle (MBR) or
extents of the data stored in the Geometry column. These will always be prefixed by
whatever name is used for the Geometry field. As the data in the Geometry column is
updated or new data is inserted, the ranges of values in XLO, XHI, YLO, and YHI are
automatically updated by GeoMedia Professional.
The MBR columns are used for spatial indexing, and they provide a convenient means of
coarse filtering. When spatial filter queries are composed, the MBR of the spatial filter is
computed and added to the where clause. This ensures that only geometries with
intersecting MBRs are returned. A second pass filter is then applied on the client to return
the spatially correct results.
Primary key columns are required for all tables that will be used for editing operations in
GeoMedia. Failure to use a primary key will cause problems with edit and update
notification. For best results, use an integer-based primary key, and assign it an
autonumber datatype using Database Utilities. This identifies the column as autonumber
for GeoMedia, but not necessarily for SQL Server. For SQL Server to treat the column as
an autonumber, you will also need to use the SQL Server Management Studio to assign the
Identity Increment property for the column. Other columns can be added as needed to store
the various attribute data associated with the geometry.
If you create spatial tables in your SQL Server database outside of GeoMedia
Professionals Feature Class Definition, you will need to ensure that the five columns that
define a spatial geometry are included in the table definition. The following shows the
example syntax for creating a table with the minimum requirements for use as a spatial
feature class:
CREATE TABLE [Example1] (
[ID] [int] IDENTITY (1, 1) NOT NULL ,
[Geometry_XLO] [float] NULL ,
[Geometry_YLO] [float] NULL ,
[Geometry_XHI] [float] NULL ,
[Geometry_YHI] [float] NULL ,
[Geometry] [varbinary(max)] NULL,
PRIMARY KEY ( [ID] )
)
GO
If you create tables (or views) manually, whether or not they are spatially enabled, you will
have to manually insert the required metadata using Database Utilities before GeoMedia
will recognize these as feature classes.
C-4
binary
image
LongBinary
bit
Boolean
char(size)
varchar(size)
nchar(size)
nvarchar(size)
ntext*
datetime
smalldatetime
Date
decimal(p,s) or
numeric(p,s)
p is precision
s is scale
float
Double
int
Long
money
Currency
real
Single
smallint
Integer
tinyint
Byte
uniqueidentifier
Guid
varbinary
LongBinary
*Memo only
C-5
Required Metadata
Boolean
bit
No
Byte
tinyint
No
Integer
smallint
Long
int
No
Single
real
No
Double
float
No
Currency
money
No
Date
datetime
No
Text
nvarchar
No
LongBinary
image
No
Memo
ntext
No
Guid
uniqueidentifier
No
Spatial
Image(16)/varbinary(max)
Yes
Graphic
Image(16)/varbinary(max)
Yes
C-6
Type
AttributeProperties
Table
FieldLookup
Table
GAliasTable
Table
GCoordSystem
Table
GeometryProperties
Table
Type
GFeatures
Table
GFieldMapping
Table
GIndexColumns
Table
GParameters
Table
GPickLists
Table
GQueue
Table
GTileIndexes
Table
ModifiedTables
View
ModificationLog
Table
The metadata tables are not manually created; you must use one of the two methods listed
below to create the metadata:
1. Use the Database Utilities in the GeoMedia Professional program group. You will
need to log in as the database owner (or administrator) to create and populate the
necessary metadata. If it is a new database, Database Utilities will detect the absence
of the metadata and will prompt you to create it. This is the preferred method.
2. Use the import.bat command created by the Export to SQL Server process. Make
sure you set the sixth parameter to Y. Read the usage notes for the import command
for more information.
AttributeProperties
The AttributeProperties metadata table describes the attribute types for the columns listed
in the FieldLookup table. The common link between this table and FieldLookup is the
IndexID column. The AttributeProperties table is defined as follows:
IndexID Uniquely identifies the column being described. The IndexID value comes
from the FieldLookup table.
C-7
IsKeyField Determines whether a column is a primary key field. The default value is
0 for FALSE. Use -1 (TRUE) if the column is a primary key.
FieldType Determines how GeoMedia interprets the datatype used in the column
definition. These are based on the conversion from SQL Server to GeoMedia
datatypes. Typical field type values include:
1 Boolean
2 Byte
3 Integer
4 Long
5 Currency
6 Single
7 Double
8 Date
10 Text
11 Binary
12 Memo
15 GUID
32 Spatial geometry
33 Graphic geometry
FieldFormat Determines the general format of the data being displayed. Format
types include General Number, Date/Time, and Currency.
FieldLookup
The FieldLookup metadata table provides a unique identifier (IndexID) for every column
in every table (feature class) in the users schema. The table definition is shown below:
IndexID This key column contains a unique identifier for every column in every
feature class in the schema. It is populated using an identity increment.
FieldName Stores all the column names that are in the associated table.
The IndexID is used as a reference by other metadata tables like AttributeProperties and
GeometryProperties, which are used to describe the columns and their contents.
C-8
GAliasTable
The GAliasTable metadata table determines the names of the other metadata tables used by
GeoMedia Professional. The GAliasTable is the only metadata table whose name is hardcoded. This table must exist and cannot be modified or altered in any way. The table
definition is shown below:
GCoordSystem
GCoordSystem stores coordinate system definitions. If this table is not present, no
coordinate system transformation will occur, and the GeoWorkspace coordinate system
will be used. This table is not user editable because of the large number of columns and
types of parameters required to define a coordinate system. It should never be populated
manually. There are three columns worth noting:
Name The name the user has assigned to this coordinate system. It is an optional
parameter, but it should be used because it makes the coordinate system easier to
identify, particularly in the Oracle environment.
CSGUID The CSGUID is a special value used to uniquely identify the coordinate
system parameters. The CSGUID is what associates a geometry object to a GeoMedia
coordinate system. The CSGUID is also used in GeometryProperties and in
GFieldMapping.
coordinate system is allowed per schema. The CSGUID of the default coordinate system is
stored in the GParameters table along with the schema name.
When digitizing in GeoMedia Professional, 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 Professional 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.
GeoMedia Professional 6.0 requires an additional column in the GCoordSystem metadata
table called NamedGeodeticDatum. This column was optional in GeoMedia Professional
5.2. The existence of this column may cause problems with GeoMedia Professional 5.1
users.
GeometryProperties
The GeometryProperties metadata table stores the geometry type, primary geometry flag,
and the coordinate system ID for geometry columns contained by feature classes. The
common link between this table and FieldLookup is the IndexID column. This table
determines the coordinate system that is assigned to each feature class. The table
definition is shown below:
IndexID This key field links the information to the actual column defined in the
FieldLookUp table.
PrimaryGeometryFlag A feature class can contain multiple geometry fields, but only
one field is allowed to be primary. The primary geometry field is the field that allows
for editing. A value of -1 means the geometry column is the primary geometry. All
other geometry columns in the feature class should be assigned 0. Only one primary
geometry field is allowed.
GeometryType This field determines how the data server maps the geometry:
C-10
1 Line
2 Area
3 AnySpatial
4 Coverage
5 GraphicsText
10 Point
GCoordSystemGUID This field contains the CSGUID from the GCoordSystem table.
It tells the data server what coordinate system is assigned to the geometry.
GFeatures
The GFeatures metadata table stores the table names of all user tables (feature classes). By
manipulating the tables listed here, you can make feature classes visible or invisible in
GeoMedia. The table definition is shown below:
FeatureName This key column contains the name of the table that will be exposed as
a feature class in GeoMedia applications.
GeometryType This field determines how the data server maps the geometry.
1 Line
2 Area
3 AnySpatial
4 Coverage
33 GraphicsText
10 Point
GFieldMapping
The GFieldMapping metadata table is used to override various aspects of field definitions.
Information stored here typically consists of the primary key column and the primary
geometry with their associated GDO data types, coordinate system ID, and any assigned
autonumber types. The table definition is shown below:
COLUMN_NAME The column in the table that this information apples to.
C-11
DATA_TYPE Determines how GeoMedia interprets the datatype used in the column
definition. Field type values include the following types (these are derived from the
SQL Server to GeoMedia datatype matching table):
1 Boolean
8 Date
2 Byte
10 Text
3 Integer
11 Binary
4 Long
12 Memo
5 Currency
15 GUID
6 Single
32 Spatial geometry
7 Double
33 Graphic geometry
2 Area
3 AnySpatial
4 Coverage
5 GraphicsText
10 Point
GIndexColumns
The GIndexColumns metadata table is used to specify the primary or unique key fields of
views that are to be used by GeoMedia applications. This table is populated using
Database Utilities. The table definition is shown below:
C-12
nvarchar(255)
BASE_OBJECT_NAME
nvarchar(255)
BASE_COLUMN_NAME
nvarchar(255)
INDEX_NAME The primary key index name from the base table.
COLUMN_NAME The name of the column in the view that will use the index in
INDEX_NAME.
INDEX_TYPE The type of the index: P for primary, U for unique. The default
value is P. If this field is missing, the first index will be assumed to be the primary
index. If a view does not have a key defined in the GIndexColumns, it will be readonly.
COLUMN_POSITION This field is the order of the column within the index. The
default value is 1.
BASE_OBJECT_SCHEMA This field is the owner of the table (view) on which the
view is based. If this field is missing or contains NULL (empty string), notification
will not be supported. Only triggers can support notification in this case.
BASE_OBJECT_NAME This field is the name of the table (view) on which the view
is based. If this field is missing or contains NULL (empty string), notification will not
be supported. Only triggers can support notification in this case.
GParameters
The GParameters metadata table contains the overrides for the default values of the
parameters needed to create new columns. It is be used only by the data server when
creating a geometry field and to obtain other server-specific configuration information.
The Type information in the GPARAMETER filed should not be modified. This table is
also used as the repository for the default warehouse coordinate system.
C-13
This table contains two fields, GPARAMETER and GVALUE. Currently, the following
values are used by default:
GPARAMETER
GVALUE
TypeForBinaryStorage
image
TypeForGeometryStorage
image
TypeForMemoStorage
ntext
TypeForTextStorage
nvarchar
TypeForDateTimeStorage
datetime
TypeForGUIDStorage
uniqueidentifier
DefaultCoordinateSystem
GPickLists
The GPickLists metadata table contains the PickList assignments used by the Properties
dialog box and the data window in GeoMedia Professional. Also known as domains,
PickLists allow for a predefined list of values to be used when updating attribute fields.
GPickLists is defined as follows:
C-14
The primary key is a combination of the FeatureName and FieldName fields. These
columns refer to the Feature Class and the specific attribute field for which the
PickList is to be used.
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 the 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 FilterClause is optional and may contain an SQL where clause that will be used to
filter the records in 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.
It is up to the dbo to populate the PickList metadata table with the appropriate entries for
those feature classes requiring the use of PickLists.
The following is an example of tables, columns, and values that could be defined for
PickLists:
C-15
GPickLists
FeatureName
FieldName
PickListTableName
ValueFieldName
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
MOTEL
TYPE
MARRIOT
NAME
HOLIDAY INN
NAME
TYPE
DAYS INN
NAME
PL_State
StateName
Desc
Alabama
ALABAMA
Arkansas
ARKANSAS
Colorado
COLORADO
Texas
TEXAS
Florida
FLORIDA
GQueue
The GQueue metadata table is used to store the static queues for the Queued Edit
command. The columns in GQueue are populated through commands in GeoMedia
Professional and are used solely by the Queued Edit command. This table is not user
editable. The table definition is provided for information only.
C-16
ModifiedTables
ModifiedTables is a join view that provides the object id for each table/view. The view
uses an inner join between the sysobjects table and the sysindexes table in conjunction with
a union. Do not modify or change this view. The ModifiedTableID in this view provides
the values for the ModifiedTableID used in the ModificationLog table. This value is used
to identify the edited table in the ModificationLog table. You should never modify this
view yourself.
ModificationLog
The ModificationLog metadata table tracks modifications made from the GeoMedia
environment for all feature classes in the connected schema. Specifically, it is used to
track all inserts, updates, and changes made to the tables listed in ModifiedTables. The
ModifiedTableID is the common link between ModificationLog and ModifiedTables. The
definition of the ModificationLog table is shown below:
C-17
Type The type of edit that has occurred; 1 for insert, 2 for update, 3 for delete.
KeyValue1 to KeyValue10 These fields store the primary key column values for the
edited row. If there is only one primary key column, only KeyValue1 is used. For
multi-column primary keys, the values from each field that makes up the key are stored
here. A primary key can be made up of a maximum of 10 columns.
SESSIONID Identifies the SQL Server session making the edit. This field is
populated automatically from a function based default value.
ModifiedDate Identifies the date and time of the edit. This field is populated
automatically from a function based default value.
All edits made to feature classes within the connected SQL Server database are tracked in
the ModificationLog table. Over time, this table can grow very large very quickly.
Because the size of the ModificationLog table can negatively affect editing performance in
GeoMedia applications, the table should be periodically truncated. However, do not clear
this table while there are open GeoMedia sessions. The Clear Modification Log
command in Database Utilities will truncate this table. You can also use the following
SQL to clear this table:
Truncate Table ModificationLog
Go
C-18
You could also set up a SQL Server job to automatically do this for you on a periodic
basis.
The ModificationLog table is currently only configured to track modifications made
through the GeoMedia environment. Modifications to the data made outside of GeoMedia
do not update the ModificationLog table; thus GeoMedia sessions are not notified of those
changes.
To solve this issue, you can create triggers that will automatically provide modification
logging. In order to prevent insert events from happening twice, the triggers must have
names that are recognized by the SQL Server data server:
The trigger for insert must have a name that corresponds to the feature class name
appended by GMTI.
The trigger for update must have a name that corresponds to the feature class name
appended by GMTU.
The trigger for delete must have a name that corresponds to the feature class name
appended by GMTD.
For example, if the feature class is States, the triggers must have the name StatesGMTI,
StatesGMTU, and StatesGMTD. This rule hold true regardless of whether the feature class
is a table or a view. When the triggers are detected, GeoMedia will offload all the
modifications for the specific feature class to the trigger.
Each trigger fires on the specific editing event and writes an entry in the ModificationLog
table. The trigger should populate the following fields:
ModifiedTableID is populated with the object ID of the object for which the entry is
created. This field comes from the ModifiedTables view.
If the primary key is user editable (non-composite or does not contain an identity field),
then all modifications must create two entries, one for the old key value and one for the
new key value. Here are simple examples of the insert, update, and delete triggers for a
feature class called States:
CREATE TRIGGER [dbo].[StatesGMTI] ON [dbo].[States] FOR INSERT AS
DECLARE @TableID INT
if object_id('tempdb..#DisableModificationLog') is null
SELECT @TableID=id FROM SYSOBJECTS WHERE name='States'
INSERT INTO ModificationLog([Type], [ModifiedTableID],KeyValue1)
SELECT 1, convert(nvarchar(20),@TableID),
convert(nvarchar(255), inserted.[ID]) FROM inserted
GO
CREATE TRIGGER [dbo].[StatesGMTU] ON [dbo].[States] FOR UPDATE AS
C-19
The same method will work for views, except that the trigger should still fire on the
underlying base table. For example, if you have a simple view on States called
STATES_VIEW, you could use the following trigger to handle notification for inserts:
CREATE TRIGGER [dbo].[States_View_GMTI] ON [dbo].[States] FOR INSERT
AS
DECLARE @TableID INT
if object_id('tempdb..#DisableModificationLog') is null
SELECT @TableID=id FROM SYSOBJECTS WHERE name='STATES_VIEW'
INSERT INTO ModificationLog([Type], [ModifiedTableID],KeyValue1)
SELECT 1, convert(nvarchar(20),@TableID),
convert(nvarchar(255), inserted.[ID]) FROM inserted
GO
And a similar trigger would work for updates and deletes as long as you adhere to the
naming convention. Note that the trigger itself is still on the base table States; it is only the
name and the contents of the trigger that refer to the view.
You could also combine a trigger that handles the view with the base table's trigger similar
to that shown below:
CREATE TRIGGER [dbo].[StatesGMTI] ON [dbo].[States] FOR INSERT AS
DECLARE @TableID INT
DECLARE @ViewID INT
if object_id('tempdb..#DisableModificationLog') is null
SELECT @TableID=id FROM SYSOBJECTS WHERE name='States'
INSERT INTO ModificationLog([Type], [ModifiedTableID],KeyValue1)
SELECT 1, convert(nvarchar(20),@TableID),
convert(nvarchar(255), inserted.[ID]) FROM inserted
SELECT @ViewID=id FROM SYSOBJECTS WHERE name='STATES_VIEW'
C-20
However, this method will lead to a double entry for the view in the ModificationLog table.
This does not necessarily cause a problem; it is just something to be aware of and is not a
recommended practice.
When you edit through a view, it is the underlying base table that is actually edited, and in
that case, a modification log trigger is required. This becomes more complicated as more
views are added on the same base table. Every update to the base table should also update
the ModificationLog table for every view that is dependent on the base table. For join
views, you will need to take into account all the base tables and associated views. In the
case of join views, most editing would be handled through instead of triggers. In this case,
you could embed the insert into the ModificationLog table directly using the instead of trigger
as long as the trigger name adheres to the rules listed above.
C-21
Never change the primary key column of a table after the table has been created. This
could make the table inaccessible by GeoMedia Professional. If you need to do this,
use Database Utilities to drop the metadata before altering the table via SQL Servers
own tools. You can re-add the metadata after making the table change.
Do not change data types on existing columns using Feature Class Definition. If you
need to do this, drop the metadata first, make the changes, and then add the metadata
back.
Renaming a table can take a long time if the table contains a lot of data. The rename
process creates a copy of the existing table, deletes the original, re-creates the table
with a new name, and then populates the data back to the newly named table.
You can set a column to be treated as autonumber by GeoMedia, but this will not set
the column to an auto-increment in the database. This will have to be done manually
in the SQL Server Management Studio.
Undo/Redo
If you use the Undo/Redo commands while editing the geometry or attributes associated
with tables that contain an auto-increment field, be aware that the numeric sequence is not
preserved. Auto-increment columns are usually assigned as primary key columns, and they
should not be used as part of a foreign key. Failure to heed this warning could invalidate
view-join definitions.
For example, a row of your data consists of an auto-increment field called ID that contains
the value 10, and there are 300 total records in this table such that max(ID)=300. If you
accidentally delete this row and use the Undo command to get it back, ID will now be
assigned the next available number in the auto-increment sequence, in this case 301.
In all cases, the next available autonumber value will be obtained on an undo/redo
operation; the previous autonumber value will not be preserved. This is actually by design;
it is how Microsoft intends the auto-increment field to be used. This only occurs when
using undo/redo operations on data in Access or SQL Server databases.
C-22
Default Values
Default values can simplify data entry and supply values for columns that are either
required or just need to have a specific entry. Default values are honored by GeoMedia but
not directly. When inserting a new record with the option to display the Attribute
Properties dialog box turned on, the default values are not shown in the dialog box even
though they are available at the database level. They will be used when the insert occurs.
If the fields are required, you will not see an error; instead, the insert will pick up the
default values. However, if the option Copy Attribute Values from Previous Feature is
enabled, you will no longer be able to use the default value. Instead, the value used in the
previous insert will be used. If you delete the previous value used in a required field, the
default value will still not be used, and you will get an error message.
For best results with defaults, either turn off the Copy Attribute Values from Previous
Feature option or do not make the fields required. Functional-based defaults will work,
but again, you must turn off the Copy Attribute option. This same problem will occur if
you are using triggers to populate required fields.
Spatial Filtering
Spatial filtering is done in two passes. The first pass is a coarse filter that operates as a
query on the server. The SQL Data Server uses a where clause on the four range (MBR)
columns that acts as a coarse filter, for example:
SELECT * FROM Parcels WHERE
Geometry _XLO>22000 AND
Geometry _YLO>44000 AND
Geometry _XHI<88000 AND
Geometry _YHI<62000
With simple spatial filters like Active Map Window Extent or Rectangular Fence, the
actual coordinates of the filter area are used in the where clause. With complex polygon
filters, as with all spatial filters, the data server gets the MBR of the filter geometry to
compare with the MBR of the feature geometry in the where clause. This provides a
coarse filter.
The results from the first pass filter is passed to the client and processed locally. This
second pass filter provides the final result.
Because spatial filters make heavy use of the Geometry_XLO, Geometry_XHI,
Geometry_YLO, and Geometry_YHI columns in queries, you may be able to improve
spatial filter performance by indexing these columns in each of your feature classes.
For example:
CREATE INDEX Parcel_SIDX ON [dbo].[Parcels]
([Geometry_XLO] desc , [Geometry _YLO] desc ,
[Geometry _XHI] desc , [Geometry _YHI] desc )
C-23
WITH
DROP_EXISTING
ON [PRIMARY]
Database Utilities
Database Utilities consist of several utilities for managing and updating Access, Oracle,
and SQL Server databases for use with GeoMedia products. These utilities are delivered
with GeoMedia Professional and are accessible from the Start menu.
See the Database Utilities online Help for complete information.
Database Utilities includes seven separate database tools, but only six of these are
available for SQL Server. Here are the six basic tools:
C-24
You can connect to SQL Server databases using either Windows domain authentication
or SQL Server authentication. For best results, all Database Utilities operations should
be performed by a database administrator login such as sa or by any other user who has
been assigned the db_owner role.
For new databases, you will need to select the Create Metadata Tables command
before any other GeoMedia operation can take place. This only needs to be done once
per database.
For tables or views created in SQL Server, use the Insert Feature Class Metadata
command to add the metadata required to see these as feature classes in GeoMedia.
To alter metadata already entered for existing feature classes, use the Edit Feature
Class Metadata command.
To delete the metadata for an existing feature class, use the Delete Feature Class
Metadata command. This is also used if you need to make any DDL modification to
tables or views. In this case, you would need to first delete the current metadata and
then re-insert it after performing the DDL operation.
C-25
C-26
D-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
\cssruntm\cfg\canada folder. You can obtain this grid file from:
D-2
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
\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.
Grid files for going between NAD27 and NAD83:
D-3
Area
Alaska
Alaska: St. George Island
Alaska: St. Lawrence Island
Alaska: St. Paul Island
CONUS
Hawaiian Islands
Puerto Rico and V.I.
Description
Alaska, including Aleutian Islands
Old island datum within Alaska
Old island datum within Alaska
Old island datum within Alaska
Conterminous U.S. (lower 48 states)
Old Hawaiian datum
Puerto Rico and Virgin Islands
File Name
alaska
stgeorge
stlrnc
stpaul
conus
hawaii
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
Alabama
American Samoa eastern islands
American Samoa western islands
Arkansas
Arizona
California above 37 deg. latitude
California below 37 deg. latitude
Colorado
Florida
Georgia
Guam
Hawaii
Idaho Montana east of 113 deg. longitude
Idaho Montana west of 113 deg.
longitude
Illinois
File Name
alhpgn
eshpgn
wshpgn
arhpgn
azhpgn
cnhpgn
cshpgn
cohpgn
flhpgn
gahpgn
guhpgn
hihpgn
emhpgn
wmhpgn
Area
Kansas
Indiana
File Name
kshpgn
inhpgn
D-4
ilhpgn
Iowa
Kentucky
Louisiana
Maine
Maryland - Delaware
Michigan (except Isle Royale)
Minnesota
Mississippi
Missouri
Nebraska
Nevada
New England (CT, MA, NH, RI, VT)
New Jersey
New Mexico
New York
North Carolina
North Dakota
Ohio
Oklahoma
Pennsylvania
Puerto Rico and Virgin Islands
South Carolina
South Dakota
Tennessee
Texas east of 100 deg. longitude
Texas west of 100 deg. longitude
Utah
Virginia
Washington - Oregon
West Virginia
Wisconsin
Wyoming
iahpgn
kyhpgn
lahpgn
mehpgn
mdhpgn
mihpgn
mnhpgn
mshpgn
mohpgn
nbhpgn
nvhpgn
nehpgn
njhpgn
nmhpgn
nyhpgn
nchpgn
ndhpgn
ohhpgn
okhpgn
pahpgn
pvhpgn
schpgn
sdhpgn
tnhpgn
ethpgn
wthpgn
uthpgn
vahpgn
wohpgn
wvhpgn
wihpgn
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
less accurate results, but seldom in excess of 1.0 meter. Transformations between NAD83 and
D-5
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.
D-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.
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.
D-7
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.
D-8
Indonesian 1974
International Terrestrial
Reference Frame 2000
(ITRF 2000)
Ireland 1965
IRENET95
ISTS 061 Astro 1968
ISTS 073 Astro 1969
Jamaica 1875
Jamaica 1969
Japan Geodetic Datum 2000
Johnston Island 1961
Kalianpur 1880
Kalianpur 1937
Kalianpur 1962
Kalianpur 1975
Kandawala
Kartastokoordinaattijarjestelma
(KKJ)
Kerguelen Island 1949
Kertau 1948
Korean Datum 1995
Kusaie Astro 1951
Kuwait Oil Company (KOC)
Kuwait Utility (KUDAMS)
L. C. 5 Astro 1961
La Canoa
Lake
Leigon
Liberia 1964
Lisbon
Lithuania 1994 (ETRS89), a
densification from ETRS89
Loma Quintana
Lome
Luzon
M'Poraloko (EPSG Definition)
M'Poraloko (NGA Definition)
Mahe 1971
Makassar
Malongo 1987
Manoca
Massawa
Merchich (EPSG Definition)
Merchich (NGA Definition)
D-10
D-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 Professional Object Reference Help.
The following vertical datums are supported.
where noted.
Australian Height Datum 1971
Canadian Vertical Reference 1928
Earth Gravitational Model (EGM96)
Ellipsoid (geometric)1
International Great Lakes 1955
International Great Lakes 1985
National Geodetic Vertical Datum 1929
North American Vertical Datum 1988
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
Ellipsoids
Ellipsoid
Earth Radius
Airy 1830
Australian National Spheroid
Average Terrestrial System 1977
Bessel 1841
Bessel 1841 (Namibia)
Clarke 1858 (EPSG Definition)
Clarke 1866
6377563.396 m.
6378160 m.
6378135 m.
6377397.155 m.
6377483.865 m.
6378293.639246834 m
6378206.4 m.
D-12
Earth-Flattening
Denominator
299.3249646
298.25
298.257
299.1528128
299.1528128
294.2606763692611
294.9786982139058
6378249.145 m.
6378300.79 m.
6378249.138846127 m.
6378249.2 m.
6378249.145 m.
6378249.2 m.
6377104.43 m.
6377298.556 m.
293.4663077
293.4662345705142
293.4663076556299
293.4660212936294
293.465
293.46598
300
300.8017
6377309.613 m.
6377304.063 m.
300.8017
300.8017
6377295.664 m.
6377299.365595379 m.
6377276.345 m.
6377301.243 m.
6377301.243 m.
6377299.151 m.
6378166 m.
6378150 m.
6378137 m.
6378160 m.
6378160 m.
6378137 m.
6378200 m.
6378270 m.
6378160 m.
6378388 m.
6378245 m.
6377340.189 m.
300.8017
300.8017255433728
300.8017
300.8017
300.8017255433728
300.8017255433728
298.3
298.3
298.2572236
298.247167427
298.25
298.257222101
298.3
297
298.247
297
298.3
299.3249646
6377492.0176 m.
6378155 m.
6378135 m.
6378145 m.
6378136.2 m.
6378136.3 m.
6376523 m.
6378160 m.
299.152812849997
298.3
298.26
298.25
298.2572236
298.2572236
308.64
298.25
D-13
Struve
Struve 1860
Unit Sphere
User-defined (non-standard)
War Office
WGS60
WGS66
WGS72
WGS84
6378298.3 m.
6378297 m.
1 m.
6378300.583 m.
6378165 m.
6378145 m.
6378135 m.
6378137 m.
294.73
294.73
0
296
298.3
298.25
298.26
298.257223563
chain
cm
ft
furlong
hundredth
in
kft
km
link
m
mi
mm
nm
nmi
pole
pt
rod
sf
si
sk
svy_ft
D-14
UOM
feet
inches
chain
centimeters
feet
furlong
hundredth
inches
kilofeet
kilometers
link
meters
miles
millimeters
nanometer
nautical miles
pole
point
rod
survey feet
survey inches
survey kilofeet
survey feet
Conversion Factor
0.3048 (m/ft)
0.0254 (m/in)
20.1168 (m/chain)
0.01 (m/cm)
0.3048 (m/ft)
201.168 (m/furlong)
0.000254 (m/100th)
0.0254 (m/in)
304.80 (m/kft)
1000.0 (m/km)
0.201168 (m/link)
1.0
1609.344 (m/mi)
0.001 (m/mm)
0.000000001 (m/nm)
1852.0 (m/nmi)
5.0292 (m/pole)
0.000352777777777778 (m/pt)
5.0292 (m/rod)
0.304800609601219 (m/sf)
0.025400050800102 (m/si)
304.800609601219 (m/sk)
0.304800609601219 (m/sf)
svy_in
svy_kft
tenth
thousandth
yd
survey inches
survey kilofeet
tenth
thousandth
yard
0.025400050800102 (m/si)
304.800609601219 (m/svy_kft)
0.00254 (m/tenth)
0.0000254 (m/1000th)
0.9144 (m/yd)
Angular Units
Alias
dd.mmss
deg
d:m
d:m:s
gr
min
rad
rev
sec
UOM
minutes
seconds
degrees
degrees minutes seconds
degrees
degrees:minutes
degrees:minutes:seconds
grads
minutes
radians
revolutions
seconds
Conversion Factor
0.000290888208665722 (rad/min)
0.00000484813681109536 (rad/sec)
0.0174532925199433 (rad/deg)
See individual units.
0.0174532925199433 (rad/deg)
See individual units.
See individual units.
0.0157079632679490 (rad/gr)
0.000290888208665722 (rad/min)
1.0
6.28318530717959 (rad/rev)
0.00000484813681109536 (rad/sec)
Area Units
Alias
ac
ares
centare
chain^2
cm^2
deciare
ft^2
hectare
in^2
km^2
link^2
m^2
mi^2
UOM
acres
ares
centares
square chains
square centimeters
deciares
square feet
hectares
square inches
square kilometers
square links
square meters
square miles
Conversion Factor
4046.8564224 (m^2/ac)
100.0 (m^2/are)
1.0 (m^2/centare)
404.68564224 (m^2/chain^2)
0.0001 (m^2/cm^2)
10.0 (m^2/deciare)
0.09290304 (m^2/ft^2)
10000.0 (m^2/hectare)
0.00064516 (m^2/in^2)
1000000.0 (m^2/km^2)
0.040468564224 (m^2/link^2)
1.0
2589988.110336 (m^2/mi^2)
D-15
mm^2
perch
rod^2
yd^2
square millimeters
perches
square rods
square yards
0.000001 (m^2/mm^2)
25.29285264 (m^2/perch)
25.29285264 (m^2/rod^2)
0.83612736 (m^2/yd^2)
Code
101, 102
5001
5002-5009
5010
201-203
301-302
401-407
501-503
600
700
901, 902
903
1001, 1002
5101-5105
1101-1103
1201, 1202
1301, 1302
1401, 1402
1501, 1502
1601, 1602
1701, 1702
1703
1801, 1802
1900
2001, 2002
2101-2103
2111-2113
2201-2203
Projection
Transverse Mercator
Oblique Mercator
Transverse Mercator
Lambert
Transverse Mercator
Lambert
Lambert
Lambert
Lambert
Transverse Mercator
Transverse Mercator
Lambert
Transverse Mercator
Transverse Mercator
Transverse Mercator
Transverse Mercator
Transverse Mercator
Lambert
Lambert
Lambert
Lambert
Lambert
Transverse Mercator
Lambert
Lambert
Transverse Mercator
Lambert
Lambert
Mississippi (E,W)
Missouri (E,C,W)
Montana (N,C,S)
Nebraska (N,S)
Nevada (E,C,W)
New Hampshire
New Jersey
New Mexico (E,C,W)
New York (E,C,W)
N.Y. Long Island
North Carolina
North Dakota (N,S)
Ohio (N,S)
Oklahoma (N,S)
Oregon (N,S)
Pennsylvania (N,S)
Puerto Rico, Virg.I. 1
Puerto Rico, Virg.I. 2
Rhode Island
Samoa
South Carolina (N,S)
South Dakota (N,S)
Tennessee
Texas (N,NC,C,SC,S)
Utah (N,C,S)
Vermont
Virginia (N,S)
Washington (N,S)
West Virginia (N,S)
Wisconsin (N,C,S)
Wyoming (E,EC,WC,W)
2301, 2302
2401-2403
2501-2503
2601, 2602
2701-2703
2800
2900
3001-3003
3101-3103
3104
3200
3301, 3302
3401, 3402
3501, 3502
3601, 3602
3701, 3702
5201
5202
3800
5300
3901, 3902
4001, 4002
4100
4201-4205
4301-4303
4400
4501, 4502
4601, 4602
4701, 4702
4801-4803
4901-4904
Transverse Mercator
Transverse Mercator
Lambert
Lambert
Transverse Mercator
Transverse Mercator
Transverse Mercator
Transverse Mercator
Transverse Mercator
Lambert
Lambert
Lambert
Lambert
Lambert
Lambert
Lambert
Lambert
Lambert
Transverse Mercator
Lambert
Lambert
Lambert
Lambert
Lambert
Lambert
Transverse Mercator
Lambert
Lambert
Lambert
Lambert
Transverse Mercator
Code
101, 102
5001
5002-5009
5010
201-203
Projection
Transverse Mercator
Oblique Mercator
Transverse Mercator
Lambert
Transverse Mercator
D-17
Arkansas (N,S)
California (I-VI)
Colorado (N,C,S)
Connecticut
Delaware
Florida (E,W)
Florida North
Georgia (E,W)
Hawaii (I-V)
Idaho (E,C,W)
Illinois (E,W)
Indiana (E,W)
Iowa (N,S)
Kansas (N,S)
Kentucky (N,S)
Louisiana (N,S)
Louisiana Offshore
Maine (E,W)
Maryland
Mass, (Main, Isle)
Michigan (N,C,S)
Minnesota (N,C,S)
Mississippi (E,W)
Missouri (E,C,W)
Montana
Nebraska
Nevada (E,C,W)
New Hampshire
New Jersey
New Mexico (E,C,W)
New York (E,C,W)
N.Y. Long Island
North Carolina
North Dakota (N,S)
Ohio (N,S)
Oklahoma (N,S)
D-18
301, 302
401-406
501-503
600
700
901, 902
903
1001, 1002
5101-5105
1101-1103
1201, 1202
1301, 1302
1401, 1402
1501, 1502
1600-1602
1701, 1702
1703
1801, 1802
1900
2001, 2002
2111-2113
2201-2203
2301, 2302
2401-2403
2500
2600
2701-2703
2800
2900
3001-3003
3101-3103
3104
3200
3301, 3302
3401, 3402
3501, 3502
Lambert
Lambert
Lambert
Lambert
Transverse Mercator
Transverse Mercator
Lambert
Transverse Mercator
Transverse Mercator
Transverse Mercator
Transverse Mercator
Transverse Mercator
Lambert
Lambert
Lambert
Lambert
Lambert
Transverse Mercator
Lambert
Lambert
Lambert
Lambert
Transverse Mercator
Transverse Mercator
Lambert
Lambert
Transverse Mercator
Transverse Mercator
Transverse Mercator
Transverse Mercator
Transverse Mercator
Lambert
Lambert
Lambert
Lambert
Lambert
Oregon (N,S)
Pennsylvania (N,S)
Puerto Rico, Virg.I.
Rhode Island
South Carolina
South Dakota (N,S)
Tennessee
Texas (N,NC,C,SC,S)
Utah (N,C,S)
Vermont
Virginia (N,S)
Washington (N,S)
West Virginia (N,S)
Wisconsin (N,C,S)
Wyoming (E,EC,WC,W)
3601, 3602
3701, 3702
5200
3800
3900
4001, 4002
4100
4201-4205
4301-4303
4400
4501, 4502
4601 4602
4701, 4702
4801-4803
4901-4904
Lambert
Lambert
Lambert
Transverse Mercator
Lambert
Lambert
Lambert
Lambert
Lambert
Transverse Mercator
Lambert
Lambert
Lambert
Lambert
Transverse Mercator
D-19
UTM Zones
Zone
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
D-20
Meridian
177W
171W
165W
159W
153W
147W
141W
135W
129W
123W
117W
111W
105W
99W
93W
87W
81W
75W
69W
63W
57W
51W
45W
39W
33W
27W
21W
15W
9W
3W
3E
Longitude Range
180W-174W
174W-168W
168W-162W
162W-156W
156W-150W
150W-144W
144W-138W
138W-132W
132W-126W
126W-120W
120W-114W
114W-108W
108W-102W
102W-96W
96W-90W
90W-84W
84W-78W
78W-72W
72W-66W
66W-60W
60W-54W
54W-48W
48W-42W
42W-36W
36W-30W
30W-24W
24W-18W
18W-12W
12W-6W
6W-0
0-6E
Zone
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Meridian
9E
15E
21E
27E
33E
39E
45E
51E
57E
63E
69E
75E
81E
87E
93E
99E
105E
111E
117E
123E
129E
135E
141E
147E
153E
159E
165E
171E
177E
Longitude Range
6E-12E
12E-18E
18E-24E
24E-30E
30E-36E
36E-42E
42E-48E
48E-54E
54E-60E
60E-66E
66E-72E
72E-78E
78E-84E
84E-90E
90E-96E
96E-102E
102E-108E
108E-114E
114E-120E
120E-126E
126E-132E
132E-138E
138E-144E
144E-150E
150E-156E
156E-162E
162E-168E
168E-174E
174E-180E
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
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 Survey
Foot
1 meter
1 meter
D-21
CH1903
CH1903+
WGS 84
1 meter
1 meter
1 meter
Adindan
AFG (Afgooye)
Ain el Abd 1970
Aratu
Arc 1950 (EPSG Definition)
Arc 1960
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
IRENET95
Kalianpur 1937
Kalianpur 1962
Kalianpur 1975
Kertau 1948
La Canoa
Lome
Malongo 1987
Massawa
Mhast
Minna
MPoraloko (EPSG Definition)
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
NAD27
NAD83
NAD83-HARN
Nahrwan
Naparima, BWI
National Geodetic Network
New Zealand Geodetic Dataum 2000
North Sahara 1959 (EPSG Definition)
Pointe Noire 1948 (EPSG Definition)
Porto Santo 1936
Puerto Rico
Qornoq
Samboja
Sapper Hill 1943
Schwarzeck
Selvagem Grande 1938
South American 1956
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
1 meter
D-23
1 meter
1 meter
1 meter
WGS 84
1 meter
Yoff
Zanderij
1 meter
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
Adindan
AFG (Afgooye)
Agadez
Ain el Abd 1970
American Samoa Datum 1962
Amersfoort
Ancienne Triangulation Francaise
Aratu
Arc 1950 (EPSG Definition)
Arc 1960
Australian Geodetic 1966
D-24
Storage Unit
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 grad
1 degree
1 degree
1 degree
1 degree
Geodetic Datum
Australian Geodetic 1984
Average Terrestrial System 1977
Barbados
Batavia
Beduaram
Beijing 1954
Bermuda 1957
Bern 1898
Bern 1938
Bogota Observatory
Bukit Rimpah
Camacupa
Campo Inchauspe
Cape (EPSG Definition)
Carthage (EPSG Definition)
CH1903
CH1903+
CHTRF95
Chua Astro
Conakry 1905
Corrego Alegre
Cote dIvoire
Datum 73
Dealul Piscului 1933
Dealul Piscului 1970
Deir ez Zor
Deutsche Hauptdreiecksnetz
Douala
EUREF89 (ETRS89)
European 1950
European 1987
Fahud
Gan 1970
Garoua
Geocentric Datum of Australia (GDA94)
Storage Unit
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
D-25
Geodetic Datum
Geodetic Datum 1949
Greek
Greek GRS 1987
Gunung Segara
Guyane Francaise
Hartebeesthoek 94
Herat North
Hito XVIII 1963
Hong Kong 1980
Hungarian Datum 1972
Hu-Tzu-Shan
Indian 1954
Indian 1960
Indian 1975
Indonesian 1974
IRENET95
Jamaica 1875
Jamaica 1969
Japan Geodetic Datum 2000
Kalianpur 1880
Kalianpur 1937
Kalianpur 1962
Kalianpur 1975
Kandawala
Kartastokoordinaattijarjestelma (KKJ)
Kertau 1948
Korean Datum 1995
Kuwait Oil Company
Kuwait Utility
La Canoa
Lake
Leigon
Liberia 1964
Lisbon
Lithuania 1994 (ETRS89)
D-26
Storage Unit
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
Geodetic Datum
Loma Quintana
Lome
Luzon
Mahe 1971
Makassar
Malongo 1987
Manoca
Massawa
Merchich (EPSG Definition)
Mhast
Militar-Geographische Institut
Minna
Monte Mario
MPoraloko (EPSG Definition)
NAD 27
NAD 83
NAD 83 HARN
Nahrwan
Naparima, BWI
National Geodetic Network
New Zealand Geodetic Datum 2000
NGO 1948
Nord de Guerre
North Sahara 1959 (NGA Definition output same as
EPSG Definition)
North Sahara 1959 (EPSG Definition)
Nouvelle Triangulation Francaise
NSWC 9Z-2
Old Egyptian 1907
Old Hawaiian
Ordnance Survey of Great Britain 1936
OS (SN) 1980
OSGB 1970 (SN)
Padang 1884
Palestine 1923
Storage Unit
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 grad
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
D-27
Geodetic Datum
Pointe Noire 1948 (EPSG Definition)
Porto Santo 1936
Provisional South Chilean 1963 (output as Hito XVIII
1963 as per NGA)
Puerto Rico
Pulkovo 1942
Pulkovo 1995
Qatar 1948
Qatar National
Qornoq
Reseau Geodesique Francais 1993 (RGF93)
Reseau National Belge 1950
Reseau National Belge 1972
Samboja
Sapper Hill 1943
Schwarzeck
Segora
Selvagem Grande 1938
Serindung
S-JTSK
South American 1956
South American 1969
Sudan
Swedish RT38
Swedish RT90
Tananarive Observatory 1925
Timbalai 1948
TM65
TM75
Tokyo
Trinidad 1903
Trucial Coast 1948
Voirol 1875 (EPSG Definition)
Voirol 1960 (Obsolete EPSG Definition now equated
with North Sahara 1959)
D-28
Storage Unit
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
Geodetic Datum
WGS 72
WGS 72 Transit Broadcast Ephemeris
WGS 84
Yacare
Yoff
Zanderij
Storage Unit
1 degree
1 degree
1 degree
1 degree
1 degree
1 degree
Azimuthal Equidistant
Cassini Soldner
Cylindrical Equirectangular
D-29
Equidistant Conic
Gnomonic
Laborde
Mercator
Miller Cylindrical
Orthographic
Polar Stereographic
Polyconic
Robinson
Sinusoidal
Stereographic
Transverse Mercator
D-30
Raster Information
Raster Formats Supported in GeoMedia
Professional
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
B/W
I, W
Bitmap 2
.bmp
No
Grayscale
I, W
Bitmap 9
.bmp
RLE
No
B/W
I, W
Bitmap 28
.bmp
No
24
RGB color
I, W
Bitmap 29
.bmp
RLE, PB
No
Grayscale
I, W
CALS 24 (1A)
.cal
CCITTG4
No
I, W
CALS 24 (1B)
.cal
CCITTG4
No
I, W
CALS 24 (2B)
.cal
CCITTG4
Yes
I, W
GeoTIFF
.tif
Georeferenced TIFF
G, I
Hitachi 1
.hrf
No
Hitachi 2
.hrf
No
Hitachi 9
.hrf
RLE
No
Hitachi 27
.hrf
RLE
No
24
Hitachi 28
.hrf
No
24
Hitachi 29
.hrf
RLE, PB
No
IGS 9
.rlc
RLE
No
IGS 29
.igs
RLE
No
Intergraph 2*
.cot
Yes
Grayscale
G, H, I
Intergraph 9
.rle
RLE
No
B/W
G, H, I
Yes
E-1
Ext.
Comp.
Tiles
Bits
Main Use/Notes
Place
Intergraph 24*
.cit
CCITTG4
Yes
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
Grayscale
G, H, I
Intergraph 30*
JPEG
Yes
Grayscale
G, H, I
Intergraph 31*
JPEG
Yes
24
RGB color
G, H, I
JFIF
.jpg
JPEG
No
PCX 9
.pcx
RLE
No
B/W
PCX 27
.pcx
RLE
No
Palette color
PCX 29
.pcx
RLE, PB
No
Grayscale
TIFF 1
.tif
Yes
B/W
G, W, I
TIFF 2
.tif
Yes
Grayscale
G, W, I
TIFF 9
.tif
PB
Yes
B/W
G, W, I
TIFF 24
.tif
CCITTG4
Yes
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
Grayscale
G, W, I
USGS DOQ
.doq
None
No
OrthoQuads
MrSID, ECW
.sid,
.ecw
Wavelet
Yes
ESRI
.bip
None
No
Satellite data
W, I
ESRI
.bil
None
No
Satellite data
W, I
PNG 9
.png
RLE/ZIP
No
B/W
W, I
PNG 29
.png
RLE/ZIP
No
Grey or Palette
W, I
PNG 27
.png
RLE/ZIP
No
24
RGB color
W, I
JPEG 2000
.jp2
Wavelet
Greyscale
G, W, I
JPEG 2000
.jp2
Wavelet
24
RGB Color
G, W, I
E-2
8/24 Greyscale/RGB
8/24 Grayscale/RGB
W, I
G, I
W, I
Raster Information
Compression Techniques
Format
Description
CCITTG4
JPEG
LZW
PB
RLE
Wavelet
ZIP
E-3
Tiling
Format
Description
Tiling
Data Types
E-4
Data Type
Description
Binary
Grayscale or
continuous tone
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
Raster Information
JFIF
MrSID
ECW
INGR
USGS DOQ
.tif, .tiff
.jpg, .jpeg
.sid
.ecw
.doq, .key
GeoTIFF
USGS DOQ
World File
Placement Mode
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.
E-5
E-6
Circle
Ellipse
Polygon
Symbol
Trim to Intersection
Extend to Intersection
Align Top
Align Middle
Align Bottom
Distribute Vertically
F-1
Ungroup
Bring Forward
Send Backward
Flip Horizontally
Flip Vertically
Left
Right
Delete
Line Color
Line Pattern
Fill
Select All
Delete
Links
Grid Display
Grid Snap
Working Sheets
Background Sheets
Drawing Toolbox
Toolbars
Import Layout
Export Layout
Layout >
Layers
Layer Groups
Update Map Graphics
F-3
F-4
Cascade
Tile Horizontally
Tile Vertically
Layout Window Properties
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.
To
United States Customary System
Feet
Meters
Yards
1.093613
Centimeters
Inches
0.3937008
Centimeters
Feet
0.03280840
Kilometers
0.6213711
Kilometers
0.5399568
Square meters
Square feet
Square meters
Square yards
1.195990
Square centimeters
Square inches
0.1550003
Square centimeters
Square feet
0.00107639
Square kilometers
0.3861021
Hectares
Acres
2.471054
Hectares
Square miles
0.00386102
Multiply by
3.280840
10.76391
G-1
G-2
To Convert from
United States Customary System
Feet
To
International System of Units
Meters
Yards
Meters
0.9144
Inches
Centimeters
2.54
Feet
Centimeters
30.48
Kilometers
1.609344
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 kilometers
2.589988
Acres
Hectares
0.4046856
Square miles
Hectares
Multiply by
0.3048
258.9988
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.
H-1
TablespaceAt 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.sqlthe master Oracle SQL script. Calls the following scripts in the order listed:
O
Other:
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:
H-2
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.
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.
H-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.
3. Click Add.
4. Select Oracle ODBC Driver.
H-4
Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers for Catalogs
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.
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.
H-6
Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers for Catalogs
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.
H-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.
Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers for Catalogs
H-10
Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers for Catalogs
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.
H-11
H-12
Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers for Catalogs
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.
H-13
H-14
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
Measure
Measure
Marker Offset
Coordinate
Duration
Duration
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.
I-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
I-2
Sample
Description
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
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
This is the 3rd key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
QuatenaryKey
This is the 4th key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
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
Reversed
True
This Boolean (True/False) field declares whether the software should treat
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
BeginMarker
EndMarker
EndMeasure
Direction of Segment
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
This is the 3rd key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
QuatenaryKey A
This is the 4th key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
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.
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.
Geometry
blob
This field contains the linear geometry that describes the linear segment
geometrically.
Geometry
Reversed
True
This Boolean (True/False) field declares whether the software should treat
this linear feature as is (False) or as if its digitizing direction were reversed
and its beginning were its end and vice-versa (True). The default value
should be set to False.
I-3
I-4
Field
Sample
Description
RegionID
ORA
Marker
EndMeasure
Marker
Direction of Segment
Sample
Description
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
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
This is the 3rd key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
QuatenaryKey
This is the 4th key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
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
Reversed
True
This Boolean (True/False) field declares whether the software should treat
this linear feature as is (False) or as if its digitizing direction were reversed
and its beginning were its end and vice-versa (True). The default value
should be set to False.
RegionID
ORA
I-5
I-6
Sample
Description
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
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
This is the 3rd key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
QuatenaryKey
This is the 4th key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
MarkerName
M34
MarkerMeasure
17.5
Option 4 Duration
The segments in this option are defined by a set of up to four LRS keys to name the route, a start
measure value, a duration (length) value, and geometry.
BeginMeasure
Duration
Direction of Segment
Sample
Description
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
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
This is the 3rd key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
QuatenaryKey
This is the 4th key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
BeginMeasure
12.3
This is the measurement value for the beginning position of this feature.
Duration
5.9
This is distance value from the beginning position to the ending position
of this feature.
Geometry
blob
This field contains the linear geometry that describes the linear segment
geometrically.
Geometry
Reversed
True
This Boolean (True/False) field declares whether the software should treat
this linear feature as is (False) or as if its digitizing direction were reversed
and its beginning were its end and vice-versa (True). The default value
should be set to False.
RegionID
ORA
I-7
BeginMarker
EndMarker
Duration
Direction of Segment
I-8
Sample
US
Description
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 LRSkey4 identifies whether this segment
is part of an alternative route. All together the route name is "US6SA".
SecondaryKey
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
This is the 3rd key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
QuatenaryKey
This is the 4th key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
BeginMeasure
12.3
This is the measurement value for the beginning position of this feature.
Duration
5.9
This is distance value from the beginning position to the ending position
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.
Geometry
blob
This field contains the linear geometry that describes the linear segment
geometrically.
Geometry
Reversed
True
This Boolean (True/False) field declares whether the software should treat
this linear feature as is (False) or as if its digitizing direction were reversed
and its beginning were its end and vice-versa (True). The default value
should be set to False.
Sample
ORA
Description
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.
I-9
Marker
Marker
Duration
Direction of Segment
Sample
Description
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
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
This is the 3rd key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
QuatenaryKey
This is the 4th key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
BeginMeasure
12.3
This is the measurement value for the beginning position of this feature.
Duration
5.9
This is distance value from the beginning position to the ending position
of this feature.
Geometry
Blob
This field contains the linear geometry that describes the linear segment
geometrically.
Geometry
Reversed
True
This Boolean (True/False) field declares whether the software should treat
this linear feature as is (False) or as if its digitizing direction were reversed
and its beginning were its end and vice-versa (True). The default value
should be set to False.
I-10
Sample
ORA
Description
This text field contains an identifier as to which region a particular
segment resides in. It is used to subdivide a LRS into more manageable
subsets. Its use is optional. The ORA in the sample shown is an ID
code for Orange County.
Sample
Description
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
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
This is the 3rd key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
QuatenaryKey
This is the 4th key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
MarkerName
M34
MarkerMeasure
17.5
I-11
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.
Sample
Description
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 LRSkey4 identifies whether this
segment is part of an alternative route. All together the route name is
"US6SA".
SecondaryKey
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
This is the 3rd key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
QuatenaryKey
This is the 4th key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
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.
I-12
Sample
Description
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
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
This is the 3rd key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
QuatenaryKey
This is the 4th key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
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.
I-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
Sample
Description
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
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
This is the 3rd key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
QuatenaryKey
This is the 4th key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
BeginX
2546234.2
BeginY
753124.4
EndX
2584123
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.
I-14
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.
Sample
Description
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
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
This is the 3rd key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
QuatenaryKey
This is the 4th key field that can be used to identify the "route" that this
segment of the LRS belongs to. Its use is optional.
BeginMeasure
14.4
This is the measurement value for the beginning position of this event.
Duration
1.8
This is distance value from the beginning position to the ending position
of this event. Note: The Duration option is for linear events only.
I-15
I-16
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.
SVG This root element for the document holds the sections for metadata (metadata),
graphics definitions (symbol), and drawing objects (use).
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 GeoMedias 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.
J-1
The following elements are supported by the GeoMedia SVG Symbol Server:
svg
symbol
use
g
metadata
line
polyline
polygon
rect
circle
ellipse
path
text
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.
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:
J-2
Attribute
xmlns
Value
"http://www.w3.org/2000/svg"
xmlns:xlink
"http://www.w3.org/1999/xlink"
Description
Defines the default
namespace of the XML
document.
Defines the xlink namespace
and sets it to the xlink prefix.
It is only required if someone
uses the namespace.
xmlns:svg
"http://www.w3.org/2000/svg
xmlns:gmsvgsym
"http://www.intergraph.com/GeoM
edia/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.
Attribute
viewBox
Value
X origin, y origin, width,
and height.
id
String
style
Description
This defines the bounding box of the
view port and is in the default units. The
user cannot specify units for any of the
four properties. The viewBox attribute is
required.
The identifier for the element. Although
not required by SVG, the GeoMedia
symbol interpreter requires it to exist.
The attribute is not required. See the
Style Attribute section for details.
gmscalepen:0 will mean that pen size
will be constant when the size of the
symbol changes. gmscalepen:1 will
mean that pen size will be scaled based
on the size of the symbol.
J-3
transform
Varies
</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 items (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="fontsize:50;font-family:Arial">
</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.
J-4
Attribute
Value
Description
id
String
style
transform
Varies
</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 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.
Attribute
Value
Description
x1
X start point
y1
Y start point
x2
X end point
y2
Y end point
id
String
style
Stroke characteristics
supported.
transform
Varies
Value
Description
points
A set of white-space-separated
coordinate pairs. No units can be given
with the value.
id
String
style
transform
Varies
J-6
Rect Element
The following section defines the attributes of a rect element. These are the only attributes
supported, and all other attributes will be ignored.
Attribute
Value
Description
x-upper-left
y-upper-left
width
Width
height
Height
id
String
style
transform
Varies
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.
J-7
Attribute
cx
Value
X center
cy
Y center
Radius
id
style
String
Stroke and fill
characteristics supported.
Varies
transform
Description
The horizontal coordinate of the center of the
circle. No units can be given with the value.
The vertical coordinate of the center of the
circle. No units can be given with the value.
The radius of the circle, which must be
positive. No units can be given with the value.
The identifier for the element. Not required.
The attribute is not required. See the Style
Attribute section for details.
The attribute is not required. See the
Transform Attribute section for details.
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.
Attribute
cx
Value
X center
cy
Y center
rx
X Radius
ry
Y Radius
id
style
String
Stroke and fill
characteristics supported.
Varies
transform
J-8
Description
The horizontal coordinate of the center of the
circle. No units can be given with the value.
The vertical coordinate of the center of the
circle. No units can be given with the value.
The radius of the ellipse along the x-axis,
and the radius value must be positive. No
units can be given with the value.
The radius of the ellipse along the y-axis,
and the radius value must be positive. No
units can be given with the value.
The identifier for the element. Not required.
The attribute is not required. See the Style
Attribute section for details.
The attribute is not required. See the
Transform Attribute section for details.
Path Element
The following section defines the attributes of a path element. These are the only attributes
supported, and all other attributes will be ignored.
Attribute
d
Value
id
style
String
Stroke and fill
characteristics supported.
Varies
transform
Description
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
The identifier for the element. Not required.
The attribute is not required. See the Style
Attribute section for details.
The attribute is not required. See the
Transform 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
x1,y1
dx1,dy1
x1,y1
dx1,dy1
J-9
rx ry xaxisrotation
large-arc
sweep x y
rx ry xaxisrotation
large-arc
sweep dx
dy
Text Element
The following section defines the attributes of a text element. These are the only attributes
supported, and all other attributes will be ignored.
J-10
Attribute
x
Value
x-upper-left
y-upper-left
textanchor
start, middle, or
end
id
style
String
Font, stroke, and fill
characteristics
supported.
Description
The horizontal coordinate of the upper-left point of
the text. No units can be given with the value.
The vertical coordinate of the upper-left point of the
text. No units can be given with the value.
The text-anchor attribute controls the horizontal
location of the anchor point. This is a left, center, or
right alignment for the text at the x and y origin.
The identifier for the element. Not required.
The attribute is not required. See the Style
Attribute section for details.
transform
Varies
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 lines
presentation.
Stroke
Characteristics
Value
Description
stroke
Color of line
stroke-width
Stroke width
stroke-dasharray
Dash gap
sequence of
line
stroke-opacity
Stroke
opacity
stroke-linejoin
miter,
bevel, or
round
stroke-linecap
butt,
round, or
square
Fill Characteristics: Specifies the way in which the interior of a shape is to be filled.
J-12
Fill
Characteristics
fill
Value
Description
Fill color
fill-rule
nonzero
or evenodd
fill-opacity
Fill opacity
Value
Description
font-size
Size of font
font-family
Family
name
font-style
italic or
normal
font-weight
bold and
normal
text-decoration
none,
underline,
or linethrough
J-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
Characteristics
Value
Description
matrix
matrix(a,b,c,
d,e,f)
translate
translate(<tx
> [<ty>])
scale
scale(<sx>
[<sy>])
rotate
rotate(<rotat
e-angle>
[<cx>
<cy>])
skewX
skewX(ske
w-angle)
skewY
skewY(ske
w-angle)
Short namespace prefixes so as not to burden the XML (and your vision), and for
consistency with other prefixes.
J-15
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
svgsym
gmsvgsym.xsd
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:
J-16
Version information
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
J-17
J-18
XML Source
The following is the XML source code for this schema definition:
<?xml version="1.0" encoding="UTF-8"?>
<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>
J-19
Example
<?xml version="1.0" encoding="UTF-8"?>
<!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">
<!--Added the following metadata for text replacement in example
Symbol_1-->
<metadata>
<gmsvgsym:symbolParameters gmsvgsym:version="1.0">
<gmsvgsym:textContent gmsvgsym:styleProp="TextProperty1"
gmsvgsym:replaceID="Text_1"/>
</gmsvgsym:symbolParameters>
</metadata>
<!--Example symbol graphics for symbol called Symbol_1 follows-->
<symbol id="Symbol_1" viewBox="0 0 400 388" style="strokelinejoin: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"/>
<!--Added the following for Symbol_1 text replacement of the
example DPW String-->
<text id="Text_1" x="103" y="119" style="font-size:10;textanchor:middle;font-family:Arial;fill:#0000ff;" >
DPW
</text>
</g>
</symbol>
<!-- The following is optional and defines which symbol should be
used as the preview in Adobe SVG Viewer -->
<use xlink:href="#Symbol_1" x="100" y="100"/>
</svg>
J-20
J-21
J-22
Intersection Geocoding
Functional Overview
The following diagram shows the basic operations involved with address geocoding when
using the AGI geocoding engine:
K-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 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
K-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.
K-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).
K-4
Reference Data
Street Name
Example
Main Street
City
State
Postcode
User Input
Street Address
MILTONS
Queensland
4064
Example
1299 Main Street
City
State
Postcode
MILTONS
Queensland
4064
User Input
Full Address
Example
1299 Main Street
MILTON QLD 4064
Address Elements
Directional Prefix
Street Name
Street Type
Street Type Suffix
Example
Main
Street
City
State
PostalCode
Miltons
QLD
4064
Address Elements
House Number
Directional Prefix
Street Name
Street Type
Street Type Suffix
City
State
PostalCode
Example
1299
Address Elements
House Number
Directional Prefix
Street Name
Street Type
Street Type Suffix
City
State
PostalCode
Example
1299
Main
Street
Miltons
QLD
4064
Main
Street
Milton
QLD
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.
K-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.
K-6
K-7
K-8
Component Interaction
The following diagram depicts the geocoding subsystem as a whole:
K-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:
Data components
Configuration components
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
K-10
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
K-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 GeoMedias 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 singledataset 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.
K-12
Point geometry
Match score
Standardized address
Matched address
Match status
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
K-13
GeocodingDataset object and also the AddressTransformation object as a public API, and
in turn its member objects. This component is public.
K-14
Geocoding Models
US_Cities_gcm.xml
A rooftop geocoding model for geocoding US cities.
Reference Data address format(s):
US_cities.xml
US_Post_gcm.xml
A centerline geocoding model for US post addresses.
Reference Data address format(s):
Street name + left/right City + left/right State + left/right ZIP (for example, E Main
Street + Madison + AL + 12345)
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).
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.
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.
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.
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.
City is concatenated with State and then parsed with the US_Cities.xml parsing rules.
ZIP is parsed with US_ZIP.xml.
K-16
Both the city and state names and ZIP cannot be defined separately for left and right
sides of the street centerline.
Geocoding address format(s):
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.
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.
Reference Data address format(s):
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.
K-17
US_street.xml
US_StreetsWithZone_gcm.xml
A centerline geocoding model for US street addresses (without city and state names).
Reference Data address format(s):
K-18
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.
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
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.
K-19
Madison
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.
Sample text recognized by the rules:
P O. 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.
Sample text recognized by the rules:
1000 AVENUE E
K-20
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.
Sample text recognized by the rules:
1000 AVENUE E
House number
Street prefix
Street pretype
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:
K-21
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.
Sample text recognized by the rules:
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.
Sample text recognized by the rules:
US-45
AVE J N
1000TH ST
K-22
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.
Sample text recognized by the rules:
12345-6789
12345
US_Cities_sp1.csv
A list of US cities that can confuse the parser, for example:
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.
K-23
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:
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
K-24
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:
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:
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
K-25
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.
Soundex code
1
2
3
4
5
6
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).
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:
K-26
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.
K-27
K-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
No action
AGP
CSC*
No action
CSD*
CSF
GCE*
No action
GLS*&
No action
GLT*&
No action
GSD
Internet Explorer
GWS&
GeoMedia Professional
FSM
GBP**
&
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.
L-1
Extension
Description
Open Action
GeoMedia Professional
MDT*
No action
SSP*
SYM*&
No action
TFD*
TRV*&
NotePad
GWT
L-2
&
Index
.
.ini files
autodt.ini, 3-2, 3-14, 3-15, D-3
coordinate system, 5-7
A
Access, 4-2
catalogs, 9-9
data, 4-5
default template, 4-3
normal.mdt, 4-3
PickLists, 4-21
server, 4-5
default coordinate system, 4-4
spatial operators, 13-38
warehouses
changing coordinate system for
template, 4-20
creating, 4-3
default coordinate system, 4-4
templates for, 4-19
accessing warehouses, 4-2
adding
feature class attributes, 8-9
geometry to features, 8-71
hypertext to feature classes, 8-85
image entries to legend, 6-42
legend entries, 6-40
thematic, 6-43
address
finding, 16-1, 16-7
sound like algorithm, K-26
Soundex algorithm, K-26
geocoding, 16-1
address parsing, 16-3, K-13
address standardization, 16-3
address transformation, 16-3, 16-4, K-2,
K-4
administrator concepts, K-1
AGI file, 16-1
Soundex, K-26
analyzing, 13-1
aggregation, 13-88
buffer zones, 13-70
combining feature classes and queries, 13102
functional attribute, 13-72
generating base geometry, 13-97
GeoMedia Professional data, 13-1
geometry, 13-65
options, 13-67
Units and Formats tab, 13-66
joins, 13-62
linear referencing, 14-5
merging
feature classes and queries, 13-83
vs. aggregating, 13-96
queries
filter, 13-1
native, 13-18
select set, 8-21
spatial, 13-8
selecting attributes, 13-100
spatial
differences, 13-15
filters, 13-30
intersections, 13-12
union, 13-102
angles, measuring, 6-73
animation, style, 6-28
annotation, 15-1
arc
constructing circular fillets, 12-33
exporting to MapInfo file, 21-5
measuring, 6-71
segment when inserting vertex, 8-32
ARC/INFO, 3-15, 4-2, 4-5
displaying, 3-17
server, 4-5
warehouse, 4-5
ArcView, 3-15, 4-2, 4-5
displaying, 3-17
server, 4-5
warehouse, 4-5
IN-2
area
features, 8-2
inserting by face, 8-73
measuring, 6-71
units of measure, D-15
arrow, north, 6-65, 19-5
associating catalog records, 9-21
attributes
adding, changing, deleting, 8-9
based style, 6-27
changing values, 10-1
tooltips, 10-2
collecting, 8-71
copying from features, 10-10
automatically, 8-72
defining, 10-11
functional, 13-72
offset display concepts, 13-22
outputting from feature class/query, 13100
populating automatically, 8-72
queries, 13-2
editing selection, 13-101
operators, 13-2
selecting, 13-100
updating
functional attribute, 10-5
values, 10-4
values using text, 10-8
AutoCAD, 4-2
.dwg file, 21-22
.dxf file, 21-22
exporting to, 21-22
autodt.ini, 3-2, D-3
autodt.ini file, 3-14
azimuth
construction aids, 8-53
north arrow, 6-65, 19-58, 19-76
precision coordinates, 8-56
settings, 3-13
B
background sheets, 18-13, 20-9
backing up, GeoWorkspaces, 2-4
base geometry, generating, 13-97
Index
C
CAD, 3-15
data
capture workflow, 1-13
server, 4-6
Define Server Schema File, online
documentation, 1-4
displaying
data, 3-17
file, 6-75
schema-definition file, 4-6, 6-75
supported MicroStation element types, 4-6
warehouse, connecting to, 4-6
cartographic grids, 19-79
border, 19-89
defining, 19-83
inserting, 19-79
neatline, 19-80
placing, 19-85
ticks and crosses, 19-86
catalogs, 9-1
Access, 9-7
associating records, 9-21
creating, 9-7
connections, 9-9
exploring, 9-26
exporting records, 9-16
format, 9-17
XML display, 9-20
features, 9-2
FGDC, 9-2, 9-4
geospatial metadata, 9-3
importing records, 9-13
style, 12-36
map object
display, 6-9
display priority, 6-9
locatability, 6-11
style, 6-12
map window properties, 6-2
north arrow display, 6-66, 19-58
scale bar display, 6-67, 19-60
circles, inserting, 8-46
circular fillet, constructing, 12-33
closing
GeoMedia Professional, 1-7
GeoWorkspace, 2-4
warehouse connections, 4-18
coincidence, 10-19, 10-31, 12-1, 12-31
and break, 8-34
maintaining, 8-30
collecting
attribute data, 8-71
feature data, 8-23
collections
catalog, 9-8
styles, 6-19
color
fill in layout window, 19-26
line in layout window, 19-24
map, 8-19
symbol, 6-33, 6-35
combined queries, 13-2, 13-11
combining feature classes and queries, 13102
compass rose, 6-66, 19-5, 19-58
compound
expressions, 13-3
features, 8-2, 21-17
compression techniques, raster data, E-3
configuring for datum transformations, 3-14
connecting to warehouses, 4-4
connections
catalogs
Access, 9-9
creating, 9-9
managing, 9-10
ODBC, 9-9
IN-4
closing, 4-18
library
creating, 22-3
managing, 22-7
opening, 4-18
Oracle, B-1
SQL, C-1
warehouses, 2-1, 4-1
coordinate system, 4-4
creating, 4-3
managing, 4-15
working with, 4-15
connectivity
fixing, 12-19
validating, 12-12
conditions, 12-13
constants, functional attribute, 13-81
constructing, circular fillets, 12-33
construction aids, 8-49
continuing
features, 10-34
geometry, 10-34
digitizing with offset, 8-61
Use Existing Geometry temporary, 1035
controlling
data windows, 7-3
layout windows, 18-1
legend entries, 6-57
map windows, 6-2
control-point pairs, 11-3, 11-5
conventions, document, 1-5
coordinate systems, 3-1, D-1
.ini files, 5-7
Access warehouses, template, 4-20
creating from design files, 3-19
datum transformation models, D-1
default settings, 3-2
Access server, 4-4
defining
for ArcView, 4-5
for AutoCAD, 4-6
for feature classes, 3-7
for GeoWorkspaces, 3-5
for MapInfo, 4-10
Index
parallel, 10-24
GeoWorkspace, 2-4
course overlap spatial operator, 13-37
creating
Access warehouse template, 4-19
attribute filter queries, 13-3
catalogs, 9-7
connections, 9-9
coordinate systems from design files, 3-19
digitizer setup, 11-4
expressions, functional attribute, 13-74
feature classes
attaching external data source, 8-5
from scratch, 8-6
ODBC Tabular data server, 8-5
functional attribute, 13-81
GeoWorkspace, 2-1
template, 2-6
image
footprints, 5-15
registration, 11-10
joins, 13-64
labels views, 15-4
layout sheets, 18-1
library, 22-2
connections, 22-3
linear network queries, 13-25
map windows, 6-64
Oracle Spatial Object database, B-47
read-write warehouses, 4-3
searches
ad hoc, 13-59
predefined, 13-56
styles, 6-22
symbol files, 6-32, 6-34
in layout window, 6-34
thematic maps, 6-43
vector registration, 11-15
crosses, grid, 19-86
defining, 19-91
parameters, 19-86
placing, 19-88
ticks, 19-86
customizing
datum transformation, 3-2
IN-5
D
data
Access, 4-2, 4-5
aggregating, 13-88
analyzing, 13-1
ARC/INFO, 4-2, 4-5
ArcView, 4-2, 4-5
AutoCAD, 4-2
CAD, 1-13
capture workflows, 1-11
collecting, 8-23
compression techniques, E-3
delaying loading, 2-3
displaying accurately, 3-15
exporting to other systems, 21-1
FRAMME, 4-2, 4-8
geographic, 6-1
inserting traverses, 17-1
legacy, 1-14
manual-input workflow, 1-12
MapInfo, 4-10
MGDM, 4-2, 4-10
MGE, 4-2
MGSM, 4-2, 4-11
MicroStation, 4-2
Oracle, B-1
outputting feature to warehouses, 8-10
raster
tiling, E-4
IN-6
types, E-4
registering, 11-1
servers, 4-2, 13-43
coordinate systems, 5-6
Oracle, B-1
SQL, C-1
SQL, C-1
structure, LRS, I-1
table, inserting into layout window, 19-98
validating, 12-1
windows
changing contents, 7-6
changing name, 7-3
columns, statistics in, 7-6
controlling, 7-3, 7-4
editing cells in, 7-7
hiding columns, 7-5
inserting features, 8-88
inserting into layout window, 19-98
opening new, 7-2
page setup, 20-6
printing, 20-8
Queued Edit, 13-50
showing table columns, 7-5
taking a snapshot of, 7-8
using mouse, 7-4
working with, 7-1
database
Access, 4-3
Oracle, 4-12, B-1
Spatial Object, B-47
SQL, 4-13, C-1
Text File, 4-14
WFS, 4-14
WMF, 4-14
Database Utilities, C-24
changing coordinate system of Acccess
warehouse template, 4-20
online documentation, 1-4
Oracle Object Model, B-45
datum
geodetic
named, D-11
standard, D-9
NAD 27, D-16
Index
queries, 13-8
units of measure, 6-70
delaying GeoWorkspace data loading, 2-3
deleting
feature, 10-26
class attributes, 8-9
geometry, 10-44
partial, 10-44
geometry, 10-33
layout sheets, 18-13
map objects, 6-64
queries, 13-29, 13-30
searches, predefined, 13-57
vertices, 10-29
design file, 5-3, 13-43
creating coordinate systems from, 3-19
exporting to, 21-8
IGDS element types generated from
GeoMedia Professional, 21-8, 21-17
images, 5-7
importing data from, 12-8
MicroStation layout templates, 18-7
designing map layouts for printing, 19-1
digitizer
button mapping, 11-8
mode, 11-7
setting, 11-8
mouse, 11-3, 11-8
setup, 11-1
control-point pairs, 11-3
creating, 11-4
deleting, 11-7
editing control points, 11-6
reporting, 11-7
workflow, 11-1
tablet, 11-3
digitizing
automatically splitting features, 8-32
breaking linear features, 8-33
circles, 8-46
collecting attributes, 8-71
construction aids, 8-49
coordinate systems matching, 4-4, 10-1, C10
copying attributes automatically, 8-72
IN-7
FAQs, A-1
Help, 1-6
interactive, 1-5
provided with GeoMedia Professional, 1-3
Release Notes, 1-6
user, 1-4
utilities, 1-4
Drawing toolbox, 19-13
dynamic
queued editing, 12-2
queues, 13-45
segmentation, 14-2, 14-5, 14-11
capabilities, 14-12
event features, 14-11
marker model, 14-12
measure model, 14-12
E
Edit MGSM Parameter File, online
documentation, 1-4
editing
attribute selection query through Queries
command, 13-101
cells in data window, 7-7
coincident geometry, 10-31
coordinate systems
files, 3-19
matching, 10-1
dynamic queued, 12-2
extending
geometry, 12-22
to intersections, 12-24
two lines to intersection, 12-26
features, 10-1
attributes, 10-1
copying, 10-22
parallel, 10-24
deleting, 10-26
merging, 10-15
partial deleting, 10-44
splitting, 10-16
functional attribute, 13-83
geometry, 10-1, 10-27
coincident, 10-31
construction aids, 8-49
Index
deleting, 10-33
snap-and-break workflow, 10-32
inserting intersections, 12-30
label text, 8-78
queries, 13-28
Queued Edit, 13-44
redoing, 8-35
reversing line direction, 12-36
searches, predefined, 13-57
speedup with tiling, E-4
text features, 8-78
trimming geometry, 12-27
to intersections, 12-29
undoing, 8-35
union query through Queries command,
13-108
validating tools, 12-1
electronic self-help support, A-1
element types
MicroStation supported, 4-6
SVG supported, J-1
ellipsoids, 3-2, D-12
e-mailing GeoWorkspaces, 2-5
embedding GeoWorkspace, 2-7
environment, multi-user, 4-19
event
data, linear referencing, 14-3
features, dynamic segmentation, 14-11
Excel, 1-8
attaching external data source, 8-5
exiting GeoMedia Professional, 1-7
exploring catalogs, 9-26
exporting
catalog records, 9-16
format, 9-17
XML display, 9-20
data, 21-1
import.bat, 21-19, 21-21, C-7
to AutoCAD, 21-22
to design file, 21-8
to MapInfo Interchange Format, 21-5
to Oracle Object Model, 21-17, B-48
to other systems, 21-1
to shapefile, 21-1
to SQL Server, 21-20, C-7
F
FAQs, A-1
feature classes, 8-2
adding hypertext to, 8-85
aggregation, 13-88
vs. merging with queries, 13-96
categories, 8-88
changing, 10-45
combining with queries, 13-102
coordinate system, 4-4, 8-3, C-10
creating
by attaching external data source, 8-5
from scratch, 8-6
ODBC Tabular data server, 8-5
defining, 8-6
coordinate system for, 3-7
SQL Data Server, C-22
images, 5-1, 5-6
inserting text features into, 8-75
labels, 15-2
legend entry defaults, 6-55
merging with queries, 13-83
outputting to warehouses, 8-10
symbols for, 6-32
union with queries, 13-102
working with, 8-2
features
aggregating attributes, 13-88
vs. merging with queries, 13-96
analyzing geometry, 13-65
attributes, 8-71
automatically splitting, 8-32
IN-9
Index
.ini
auto.ini, 3-14
autodt.ini, 3-15
MGE, 8-87
rulebase, 4-8
.jgw, 5-3
.mdb, 9-7
.mge, 4-10
.pdf, 1-4, 20-16
.prm, 4-11
.prn, 20-5
.sdw, 5-3
.svg, 6-15, 6-32, 6-34
.sym, 6-15, 6-34
.tfd, 4-14
.tfw, 5-3
.trv, 17-1
.xls, 9-17, 9-20
.xsd, 21-26
autodt.ini, 3-2
CAD
displaying, 6-75
schema definition, 4-6
coordinate, 4-11
system, 4-6
design, 13-43
external, 8-85
File Locations tab, Options dialog box, 2-5
FSA.gtw, 4-8
gateway, 4-8
GeoTIFF, 11-13
Jpeg, 5-3
MapInfo, 21-5
MGE project, 4-10
MrSid, 5-3
multimedia, 8-87
normal.gwt, 2-1
normal.mdt, 4-3
parameter, 4-11
printing to, 20-5
seed, 4-11, 21-16
symbol library, 6-32
text, 4-11, 4-14
format definition, 4-14
TIFF, 5-3
types, L-1
world, 5-2
filters
attribute in queries, 13-1, 13-2
SQL, 13-3
spatial, 13-30
by existing filter, 13-33
by map window extent, 13-33
by not using filter, 13-33
by reference features, 13-32
by select set, 13-33
defining, 13-31
designating reference features, 13-41
fitting, 13-39
managing, 13-36
named, 13-39
operators, 13-36
options, 13-36
Oracle data server, B-19
removing, 13-39
with layout windows, 19-10
workflows, 13-34
finding addresses, 16-1, 16-7
Publish Address Geocoding Index Utility,
K-26
sound like algorithm, K-26
Soundex algorithm, K-26
fit
all, 6-7
select set, 6-7
spatial filters, 13-39
fixing
connectivity, 12-19
geometry, 12-11
footprints
creating image, 5-15
geographic, 19-8
formats
raster, supported in GeoMedia, E-1
setting, 3-12
Units and Formats tab, Define Coordinate
System dialog box, 3-12
FRAMME, 3-15, 4-2, 4-8
displaying, 3-18
server, 4-8
IN-11
warehouse, 4-8
frequently asked questions, A-1
functional attribute
aggregation, 13-92
analytical merging, 13-84
creating, 13-81
displaying, 13-81
editing, 13-83
expressions, 13-74
constants, 13-81
functions, 13-77
operands, 13-76
operators, 13-76
format, 13-76
Functional Attribute dialog box, 13-74
Functional Attributes
command, 13-72
dialog box, 13-72
output types, 13-75
precision, 13-76
style, 6-27
updating feature attributes, 10-5
working with, 13-72
functions, functional attribute, 13-77
G
gateway files, 4-8
GDOSYS, B-47
schema, B-20
table relationships, B-37
generating base geometry, 13-97
workflow, 13-98
geocoding, 16-1
addresses, 16-1
AGI file, 16-1
terminology, 14-1
coordinates, 16-23
dataset, K-11
defining parsing rules, 16-19
design elements, K-10
directory, K-12
intersections, K-24
models, K-15
parsing rules, K-19
sound like algorithm, K-26
IN-12
Index
georeferenced image
placement, 5-2
raster placement, file types and categories,
E-5
geospatial metadata, 9-3
geo-tie packets, 5-2, E-2
GeoTIFF
capabilities, D-21
file, 11-13
geographic systems, D-24
image, 11-13
placement, D-29
outputting to, 11-13
projection systems, D-21
reading from, D-29
tags, 5-2, 11-13
GeoWorkspaces
backing up, 2-4
closing, 2-5
coordinate system, 4-4, 5-3, C-10
defining, 3-5
matching default, 3-9, 10-1
copying, 2-4, 2-5
creating, 1-2, 2-1
delaying data loading, 2-3
e-mailing, 2-5
embedding, 2-7
linking, 2-7
opening, 2-2
saving, 2-4
storing, 2-5
templates, 2-1, 2-6
creating, 2-6
workflow for creating, 2-1
working with, 2-1
GIS, 1-1
applications, 1-20
concepts and terms, 1-17
legacy data, 1-14
overview, 1-16
GML, 4-2
.gml file, 21-26
.xsd file, 21-26
Data Server, 4-8
exporting to, 21-26
IN-13
warehouse, 4-8
grids, 19-79, 19-92
border, 19-89
placing, 19-89
cartographic, 19-79
coordinate system, 19-84
crosses, 19-86
defining, 19-83, 19-89, 19-90, 19-91, 1992
neatline, 19-80
coordinate system, 19-81
defining, 19-90
parameters, 19-81
placing, 19-82
parameters, 19-84
placing, 19-85
reference, 19-92
index, 19-95
ticks, 19-86
placing, 19-87
ticks and crosses, 19-86
coordinate system, 19-87
defining, 19-91
parameters, 19-86
placing, 19-88
H
height value, 10-15, 10-24, 10-27, 10-41, 1229
default, 8-24
Help
Command Wizard, 1-3
displaying, 1-6
GeoMedia Professional Help, 1-4
topics, 1-6
Hidden Markov Model (HMM), 16-3, 16-19
hiding
layout window, 18-1
legend, 6-39
holes, 8-68, 8-73, 12-8, 12-14
how to reach Intergraph, A-1
hypertext
adding, 8-85
inserting, 8-86
IN-14
I
I/CAD MAP, 4-2
IGDS, element types generated from
GeoMedia Professional, 21-8, 21-17
images, 5-1
adding entries to legend, 6-42
changing raster display, 5-12
coordinate systems, 5-1, 5-6
creating footprints, 5-15
deleting, 5-11
displaying, 3-18, 5-9
selected, 5-17
feature classes, 5-1, 5-6
features, 8-2
footprints, 5-15
georeferenced placement, 5-2
GeoTIFF, 11-13, D-29
inserting into warehouses, 3-18, 5-1
interactive placement, 5-2
managing, 5-8
raster, 5-1
symbols, 8-27
redisplaying, 5-12
registration, 11-9
creating, 11-10
deleting, 11-12
editing, 11-12
reporting, 11-12
removing, 5-12
satellite or photogrammetric, 1-13
snapshot of data window, 7-8
style, 6-18
supported raster formats, E-1
TIFF, 11-13
updating, 5-10
validating, 5-11
XML, 5-8
Imagineer
drawing file, 18-5
template file, 18-5
import.bat, 21-19, 21-21, C-7
importing
catalog records, 9-13
data
traverse, 17-6
Index
workflow, 4-3
drawing files, 18-5
layout templates, 18-5
table definitions, B-47, B-48
index
building, geocoding, 16-5, K-3
matching, geocoding, 16-4, 16-6, K-5
reference, 19-95
defining, 19-95
inserting, 19-95
RTree, B-17
spatial data, B-18
indexing
geometry, B-16
reference map features, 19-95
information, geometry, 12-2, 12-36
inserting
circles, 8-46
data table into layout window, 19-98
features, 8-37
area, 8-73
construction aids, 8-49
digitizing with offset, 8-61
in data window, 8-88
placement modes, 8-63
grids, 19-79
cartographic, 19-79
reference, 19-92
reference index, 19-95
hypertext, 8-85, 8-86
images
georeferenced, 5-2
interactive, 5-2
into warehouses, 3-18, 5-1
interactive labels, 15-9
intersections, 12-30
cases, 12-31
labels, 15-1, 15-2
layout frames, 19-42
leader lines on labels, 15-5
legends, layout window, 19-51
maps
graphics into layout sheets, 19-48
into layout sheets, 19-48
marginalia into layout sheets, 19-51
J
joins, 13-62, 13-63
creating, 13-64
defining, 13-62
views and view joins, Oracle Object
Model, B-40
K
keyins, Precision Coordinate, 8-69
Knowledge Base, A-1
L
labels, 15-1
creating, 15-4
interactive, 15-9
inserting, 15-1, 15-2
IN-15
Index
map frame
map pan, 19-68
map zoom in/out/previous, 19-68
map graphics
static and dynamic modes, 19-11, 19-64
updating, 19-62
map layout components, 19-8
map properties, changing, 19-69
map window, 19-8
components, 19-8
printing considerations, 19-1
marginalia
inserting, 19-42, 19-51
specifications, 19-11
MicroStation, layout template file, 18-5
non-map graphics, 19-33
normal.glt, 18-5
north arrow, 19-5, 19-12
changing properties, 19-76
inserting, 19-58
object, 19-33
changing properties, 19-79
outputting PDF from, 20-17
overview, 18-1
page setup, 18-3
default, 20-9
for printing, 20-8
placing
and editing commands, 19-15
lines, 19-21
text, 19-19
plot scale, 19-10
plotting, 18-3, 20-16
previewing map in map window, 19-4
printing
graphics, 20-16
layout sheets, 20-11
to file, 20-8
properties, 18-14
element, 19-16
group, 19-19
legend, 19-52, 19-73
legend, map, 19-75
map, 19-69
map graphics, 19-64
IN-17
Index
understanding, 6-35
master, 6-55
named, 6-55, 6-56, 6-58, 6-60
libraries, 22-1
creating, 22-2
connections, 22-3
managing connections, 22-7
organizing, 22-9
symbol, 6-32
template, 22-2, 22-4
Licensing Utility, online documentation, 1-4
line
changing
direction, 12-36
style, 12-36
extending two to intersection, 12-26
placing in layout window, 19-21
terminators in layout window, 19-25
linear
features, 8-2
breaking, 8-33
partial deleting, 10-44
network queries, 13-2, 13-24
referencing
analysis, 14-5
data structures, I-1
duration, I-7
duration with external measure
markers, I-10
duration with internal markers, I-8
event, I-12
event, duration, I-15
event, marker offset, I-13
event, measure, I-12
event, XY, I-14
measure, I-2
measure with external markers, I-5
measure with internal measure
markers, I-3
dynamic segmentation, 14-5, 14-11
event data, 14-3, 14-5
event features, 14-11
features, 14-3
Geospatial Technology, 14-2
introduction, 14-1
LRS, 14-1
marker model, 14-12
measure model, 14-12
precision location, 14-5
units of measure, D-14
linking
geometry
and attributes, 8-72
data to coordinate systems, 5-8
GeoWorkspace, 2-7
loading
customized settings, 1-9
data
delaying GeoWorkspace, 2-3
large amounts of, 21-17, 21-20
traverse, 17-6
SQL Server Bulk Loader, 21-20
text, 10-9
locatability
feature class, 8-35
map objects, 6-11
locate zone, 8-18, 19-32
location, precision, 14-5
longitude ranges, D-20
LRS, I-1, See linear referencing
M
maintaining coincidence, 8-30
and break, 8-34
managing
catalog connections, 9-10
categories, 8-89
library connections, 22-7
metadata, 9-26
searches, 13-55
spatial filters, 13-36
warehouse images, 5-8
manipulating
features, 10-14
copying, 10-22
deleting, 10-26
merging, 10-15
partial deleting, 10-44
rotating, 10-39
splitting, 10-16
IN-19
geometry, 10-27
continuing, 10-34
deleting, 10-44
editing, 10-31
moving, 10-36
redigitizing, 10-40
rotating, 10-39
spinning, 10-37
layers, 18-15
groups, 18-17
layout sheets, 18-12
map
colors, 8-19
graphics, updating in layout sheet, 19-62
grids, 19-79
reference, 19-92
reference index, 19-95
objects
adding to legend, 6-40
deleting, 6-64
display properties, 6-10
displaying, 6-1, 6-9
locatability, 6-11
priority, 6-9
setting scale range for, 6-11
style of, 6-12
scale
nominal, 6-5
zoom to nominal, 6-7, 19-4
scanned, 1-12
thematic, 6-43
classes, 6-47
display, 6-38, 6-56
legend entry types, 6-43
Range Thematic, 6-45
Standard, 6-43
styles, 6-48
Unique Value, 6-44
viewing tools, 6-7
windows
by extent, spatial filter, 13-33
changing legend properties in layout
window, 19-75
components, 19-8
controlling, 6-2
IN-20
creating, 6-64
north arrow, 6-65
properties, 6-65
page setup, 20-1
previewing before printing, 19-4
printing, 20-4
properties, changing, 6-2
properties, defining, 6-4
Queued Edit, 13-47
selecting features, 8-18
tooltip, 6-62, 6-63, 8-20
using the mouse in, 6-6
working with, 6-1
MapInfo, 3-15, 4-2, 4-10
displaying, 3-18
Interchange Format, exporting to, 21-5
server, 4-9
table defining MapInfo geometry from
GeoMedia Professional, 21-6
warehouse, 4-9
marginalia, 6-1
layout
inserting, 19-11, 19-51
legend, 19-11, 19-73
north arrow, 19-5, 19-12, 19-76
scale bar, 19-6, 19-12, 19-77
specifications, 19-11
map
legend, 6-35, 19-5
north arrow, 6-65
scale bar, 6-67
marker model, dynamic segmentation, 14-12
master legend, 6-55
measure model, dynamic segmentation, 1412
measuring
angles, 6-73
area, 6-71
conversion tables, G-1
distance, 6-70
setting options, Units and Formats tab, 312
menus, customizing, 1-8
merging
analytical, 13-83
Index
N
named
geodetic datums, D-11
legend, 6-55, 6-56, 6-58, 6-60
spatial filters, 13-39
native queries, 13-18
defining, 13-18
MGSM, 13-22
Oracle, 13-20
Oracle Object Model, B-19
neatline, 19-80
coordinate system, 19-81
defining, 19-90
parameters, 19-81
placing, 19-82
normal.glt, 18-5
normal.gwt, 2-1
normal.mdt, 4-3
north arrow
displaying, 6-65
layout
changing, 19-76
displaying, 19-12
inserting, 19-58
properties, 19-58
map
changing, 6-66
displaying, 19-5
properties, 6-65, 6-66
IN-21
O
objects, layout sheet
changing, 19-79
inserting, 19-33
properties, 19-79
ODBC
catalogs, 9-9
Tabular
data server feature classes, 8-5
server, 4-11
warehouse, 4-2, 4-11
offset
digitizing with, 8-61
display concepts, 13-22
mode, 8-60
origin in layout window printing, 20-11
OLE, 7-8
server, 2-7
opening
GeoMedia Professional, 1-7
GeoWorkspace, 2-2
layout windows, 18-4
map window, 6-1
warehouse connections, 4-18
operands, functional attribute, 13-76
operators
for attribute queries, 13-2
for functional attribute, 13-76
for linear network queries, 13-24
for native spatial queries, 13-19
for spatial filters, 13-36
for spatial queries, 13-8, 13-12
Options
changing
default folder, 2-4
GeoWorkspace location, 2-5
map display, 8-19
measurement, 6-70
template location, 2-6
File Locations tab, 2-4
General tab, 2-3
Layout tab, 18-2
Map Display tab, 6-2
Placement and Editing tab, 8-24, 8-37, 121, 12-31, 17-7
IN-22
setting
layout window controls, 18-1
query display location, 13-6
SmartLocate, 8-18, 10-17
status bar display, 6-8
Oracle, 4-10
catalogs, H-1
Connections, B-1
native queries, 13-18
Object
server, 4-12
warehouse, 4-12
Object Model, 4-2
Database Utilities, B-45
delivery and connection, B-1
exporting to, 21-17
geometry indexing, B-16
native data model, B-5
native queries, B-19
raster images, B-11
requirements, B-3
SRID, B-16
triggers, B-43
views and join-views, B-40, C-24
Spatial Object database, B-47
spatial operators, 13-10, 13-38
organizing libraries, 22-9
outputting
feature data to warehouses, 8-10
GeoTIFF, 11-13
PDF from layout window, 20-17
overlap spatial operator, 13-38
overlay operators, 13-24
P
page setup for printing, 20-1
data window, 20-6
layout window, 18-3, 18-13, 20-8
map window, 20-1
pan, 6-8
dynamic mode, 6-8, 19-68
fast mode, 6-8, 19-68
layout window, 19-68
map, 19-64
parameter files, 4-11
Index
parsing
addresses, 16-3, K-13
Define Parsing Rules utility, 16-2, 16-4,
K-2, K-13, K-15
defining rules, 16-19
rules, K-19
partial deleting linear features, 10-44
PDF, outputting from layout window, 20-17
PickLists
Access, 4-21
PickQuick, 8-19, 19-46
map window tooltip, 8-20
placing
features, 8-37
grids, 19-79
reference, 19-92
reference index, 19-95
labels, 15-2
modes, 8-41
right mouse menu, 8-63
redoing, 8-35
undoing, 8-35
plotting
.pdf file, 20-16
batch, 18-10, 19-19, 20-16
layout window, 18-3, 20-16
workflows, 19-6
point
features, 8-2
symbol, spinning, 10-38
populating attributes automatically, 8-72
Precision Coordinates
dockable control, 1-8, 3-11, 8-69
keyins, 8-69
precision location, linear referencing, 14-5
preparing to connect to warehouse, 4-4
printing, 20-1
.pdf file, 20-16
data window, 20-8
page setup, 20-6
graphics
translucent, 20-16
transparent, 20-16
in GeoMedia Professional, 20-1
layout sheets, 20-11
IN-23
Q
Quad-Tree algorithm, 13-38
queries, 13-1
aggregation, 13-88
attribute filter, 13-1, 13-2
attribute selection, editing through Queries
command, 13-101
buffer zones, 13-70
categories, 8-88
combination, 13-11
combined, 13-2
combining with feature classes, 13-102
deleting, 13-29, 13-30
displaying, 13-27
editing, 13-28
filter, 13-1
graphics-only features, 13-43
joins, 13-62, 13-63
labels, 15-1
linear network, 13-2, 13-24
manipulating, 13-26
merging with feature classes, 13-83
metadata, 9-26
native, 13-18
MGSM, 13-22
Oracle, 13-18
Oracle Object Model, B-19
operators
for attribute queries, 13-2
for native spatial queries, 13-19
for spatial queries, 13-8
searches, 13-55
select set, 8-21
spatial, 13-1, 13-8, 13-12, 13-15
analysis
spatial difference, 13-15
spatial intersections, 13-12
difference, 13-15
intersections, 13-12
SQL filter, 13-3
union
editing through Queries command, 13108
with feature classes, 13-102
IN-24
R
Range Thematic legend entry type, 6-45
raster data, 3-15
changing image display, 5-12
compression techniques, E-3
converting layout window legend to, 19-74
displaying, 3-18
file types and categories, georeferenced
image, E-5
formats supported in GeoMedia, E-1
image symbols, 8-27
information, E-1
inserting, 5-1
Oracle Object Model, B-11
snaps, 8-25
tiling, E-4
types, E-4
read-only warehouses, 2-2, 4-2, 12-6
readouts
coordinate, 3-11
precision coordinates control, 3-11
read-write warehouses, 1-2, 8-1, 12-6, 21-5
creating, 4-3
Index
redigitizing
area features, 10-42
features, 10-40
with a break, 10-43
geometry, 10-40
line features, 10-41
redoing, placement and editing, 8-35
reference
ellipsoid. See ellipsoids
features, spatial filter, 13-32, 13-41
grids, 19-92
index, 19-95
referencing systems, linear, 14-1
refreshing
map display, 6-7
with warehouse changes, 4-19
registering data, 11-1
digitizer
button mapping, 11-8
mode, 11-7
setup, 11-1
image registration, 11-9
vector registration, 11-14
Release Notes, A-1
resolving text conflicts, 15-13
workflows, 15-15
reversing, line direction, 12-36
reviewing coordinate systems for feature
classes, 3-7
right mouse menu, 1-8
analytical merging, 13-85
map window legend, 6-61
placement modes, 8-63
RIS, 4-11
rooftop data, geocoding, 16-2
Root Mean Square (RMS), 11-4
rotation
angle, 19-2
feature, 8-45, 10-39
geometry, 10-39
layout window, properties, 19-71
map view angle, 6-5
Rtree indexes, B-17
S
saving
customized settings, 1-9
GeoWorkspace, 2-4
plot sessions, 18-3, 20-16
warehouse, 4-3
scale
display, 6-4
map nominal, 6-5
plot, 19-10
range, setting, 6-11
viewing, 6-2
zoom to nominal map, 19-4
scale bar, 19-6
displaying, 19-6
examples, 6-68
layout
changing, 19-77
displaying, 19-12
inserting, 19-60
map
changing, 6-67
displaying, 6-67
inserting, 6-67
properties, 6-67
scanner
AutoCAD, 3-17
IGDS, 3-17
schema
CAD server, 3-17, 6-75
definition file, 4-6
GDOSYS, B-20, B-21
SVG Symbol Metadata XML, J-16
searches, 13-55
ad hoc, 13-58
creating, 13-59
performing, 13-59
data window, 13-62
managing predefined, 13-55
map window, 13-62
navigating, 13-61
performing, 13-58
predefined, 13-58
creating, 13-56
deleting, 13-57
IN-25
editing, 13-57
performing, 13-60
Queued Edit control, 13-58, 13-61
viewing options, 13-62
seed files, 4-11, 21-16
segmentation, dynamic, 14-5, 14-11
select set, 8-19, 10-15, 12-6, 12-29, 12-30
clearing, 8-21
editing properties, 10-3
queries from, 8-21
spatial filter, 13-33
symbols, 10-15
Select Tool, 8-19, 19-13, 19-16
selecting
attributes, 13-100
data window contents, 7-4
features in map window, 8-18
layout sheets, 18-12
selection buttons, 8-20
self-help support, A-1
sending GeoWorkspace, 2-5
servers
Access, 4-5
AFM proxy, 4-15
ARC/INFO, 4-5
ArcView, 4-5
AutoCAD, 4-6
exporting to, 21-22
FRAMME, 4-8
GeoGraphics, 4-7
GML, 4-8
exporting to, 21-26
MapInfo, 4-9
exporting to, 21-5
MGE, 4-10
MGSM, 4-11
ODBC Tabular, 4-11
OLE, 2-7
Oracle Object Model, 4-12
connections, B-1
exporting to, 21-17
SmartStore, 4-13
SQL, 4-13, C-1
exporting to, 21-20
Text File, 4-14
IN-26
WFS, 4-14
WMS, 4-14
setting units and formats, 3-12
setting up
digitizer, 11-1
mode, 11-7
page for printing, 20-1
SmartSnap, 19-32
settings, customized menus and toolbars, 1-9
shapefiles, 4-2, 4-5
exporting to, 21-1
sheets
background layout, 18-13
exporting layout, 18-9
inserting layout, 18-4
layout, 18-1
style, 9-17, 9-20
working layout, 18-13
SmartLocate, 8-18, 10-17
PickQuick, 8-19
SmartSketch
drawing file, 18-5
template file, 18-5
SmartSnap
locate zone, 19-32
raster snaps, 8-25
setting in layout window, 19-32
tolerances, 8-26
toolbar, 8-25
vector snaps, 8-25
SmartStore
.ddc Profile files, 4-13
online documentation, 1-4
Server, 4-2
warehouse, 4-13
snaps
raster, 8-25
SmartSnap, 8-25, 19-32
tolerances, 8-26
vector, 8-25
snapshot
of data window, 7-8
of map window, 6-75
spatial
aggregation, 13-90
Index
difference, 13-15
filters, 13-30
by existing filter, 13-33
by map window extent, 13-33
by not using filter, 13-33
by reference features, 13-32
by select set, 13-33
defining, 13-31
designating reference features, 13-41
fitting, 13-39
managing, 13-36
named, 13-39
operators, 13-36
options, 13-36
Oracle data server, B-19
removing, 13-39
with layout windows, 19-10
workflows, 13-34
indexing data, B-18
intersection, 13-12
operators, 13-8, 13-12, 13-19
queries, 13-1, 13-8
spinning geometry, 10-37
splitting
features, 10-16
area, 10-17
automatically, 8-32
geometry collections, 10-21
point mode, 10-20
polygon mode, 10-19
polyline mode, 10-16
simple geometries, 10-21
line features, 10-18
maintain coincidence, 10-19
SQL, 13-7
catalogs, H-1, H-7
connections, C-1
Data Server, 4-2, 4-13, B-1, C-1
Bulk Loader, 21-20
connecting, C-1
exporting to, 21-20
Feature Class Definition, C-22
metadata, C-6
requirements, C-2
views, C-24
warehouse, 4-13
dialects, 13-3
in queries, 13-3
standard
geodetic datums, D-9
legend entry type, 6-43
style, 6-31
State Plane zone codes
NAD 27 Datum, D-16
NAD 83 Datum, D-17
statistics
data window, 7-6
Queued Edit, 13-53
thematic style, 6-47
street centerline data, geocoding, 16-2
Structured Query Language. See SQL
style
animation, 6-28
attribute-based, 6-27
changing
feature, 6-31
legend entry, 6-31
classes, 6-12
collections, 6-19
synchronizing elements, 6-21
creating, 6-22
editing legend entry, 6-30
expressions, 6-27
legacy, 6-13
legend keys, 6-38
managing, 6-22
named, 6-22, 6-24
of map objects, 6-12
presentation
Range Thematic, 6-31
Standard, 6-31
Unique Value Thematic, 6-31
properties, 6-25
selecting, 6-30
setting legend entry, 6-5, 19-2
sheet
.xls, 9-17, 9-20
catalog, 9-17, 9-20
synchronizing elements, 6-21
thematic, 6-48
IN-27
T
technical
notes, A-1
support, A-1
IN-28
templates
catalog, 9-7
creating
Access warehouse, 4-19
from layout window, 18-9
GeoWorkspace, 2-6
default Access, 4-3
exporting from layout window, 18-9
GeoMedia layout, 18-5
GeoWorkspace, 2-1, 2-6
Imagineer, 18-5
importing into layout window, 18-5
library, 22-2, 22-4
MicroStation layout, 18-5
normal.gwt, 2-1
normal.mdt, 4-3
SmartSketch, 18-5
warehouse, 4-3, 4-19
tessellation, B-30
text
adding hypertext to feature classes, 8-85
cells, 7-7
features, 8-2
editing, 8-78
inserting, 8-75
updating attributes, 10-8
files, 4-11, 4-14
attaching external data source, 8-5
label, 6-39
editing, 8-78
resolving conflicts, 15-13
MapInfo warehouse, 4-10
placing in layout window, 19-19
properties, 19-20
resolving conflicts, labels, 15-13
spinning, 10-38
SQL, 13-3
style, 6-17
Unicode, 1-8
Text File
Server, 4-2, 4-14
Format File, 4-14
warehouse, 4-14
thematic
display, 2-4, 6-38, 13-27
Index
registering, 11-1
resolving text conflicts, labels, 15-13
to speed up digitizing, 8-23
validating, 12-1
tooltips, 10-2
map window, 6-62, 6-63
PickQuick, 8-20
transformation
datum, 3-14
models, D-1
Affine, 11-9, 11-14
Helmert, 11-14
traverses
.trv file, 17-1
command features, 17-6
defining, 17-2
importing data, 17-6
inserting, 17-1
selecting data, 17-4
workflows, 17-7
triggers, Oracle Object Model, B-37, B-43
modification log, 4-19
trimming geometry, 12-27
cases, 12-29
to intersections, 12-29
typeface conventions, 1-5
types
aggregation, 13-89
style, 6-12
U
undoing
features, 8-35
placement and editing, 8-35
Unicode, 1-8
union
editing query, 13-108
feature classes/queries, 13-102
Unique Value legend entry type, 6-44
units of measure, D-14
angular, 6-5, D-15
area, D-15
conversion tables, G-1
linear, D-14
setting, 3-12
IN-29
V
validating
connectivity, 12-12
conditions, 12-13
data, 12-1
using editing tools, 12-1
dynamic queued editing, 12-2
geometry, 12-8
error conditions, 12-8
information, 12-2
values, map ID, 13-43
vector
registration, 11-14
creating, 11-15
deleting, 11-18
reporting, 11-17
IN-30
workflow, 11-15
snaps, 8-25
vertices
deleting, 10-29
inserting, 10-29
moving, 10-29
view
and view joins, Oracle Object Model, B-40
at current scale, 6-2
data tools, 7-4
legend, 6-39
scale bar, 6-67
SQL Data Server, C-24
viewing
changes in multi-user environment, 4-19
tools, 6-7
Visual Basic, 1-1
Visual C++, 1-1
W
warehouses, 4-1
Access, 4-5
ArcView, 4-5
CAD, 4-6
closing connections, 4-18
connecting to, 4-4, 4-17, 4-18
creating read-write, 4-3
data-display workflow, 4-2
defining coordinate systems for, 4-4
FRAMME, 4-8
GeoGraphics, 4-7
GML, 4-8
importing into, 4-3
inserting images into, 5-1
managing images, 5-8
MapInfo, 4-10
matching default GeoWorkspace
coordinate systems, 3-9
MGDM, 4-10
MGSM, 4-11
ODBC Tabular, 4-11
opening connections, 4-18
Oracle, B-1
Object Model, 4-12
outputting feature data to, 8-10
Index
proxy, 4-15
read-only, 4-2
read-write, 8-2
SmartStore, 1-4
SQL Server, 4-13, C-1
templates for, 4-19
Text File Server, 4-14
WFS Server, 4-14
WMS, 4-14
working with connections, 4-15
WFS, 4-2
Data Server, 4-14
warehouse, 4-14
windows
data, 7-1
layout, 18-1
map, 6-1
Windows
XP, 1-1, 11-1
wizard, GeoMedia Professional Command
Wizard Help Topics, 1-3
WMS, 4-2
Data Server, 4-14
warehouse, 4-14
workflow
accessing warehouses, 4-2
address geocoding, K-1
capture and maintenance, 1-11
catalogs, 9-37
creating a GeoWorkspace, 2-1
data-capture, 1-11
attribute data, 1-14
CAD data, 1-13
manual input, 1-12
satellite or photogrammetric images, 113
scanned maps, 1-12
digitizer setup, 11-1
digitizing using existing geometry, 8-29
displaying geographic data, 6-1
editing geometry, 10-32
generating base geometry, 13-98
geocoding addresses, 16-14
multiple datasets, 16-17
parsing rules, 16-22
X
Xbase, attaching external data source, 8-5
XML
catalogs, 9-17
images, 5-8
SVG Symbol Metadata schema, J-16
Z
zone
buffer, 13-70
codes, state plane, D-16, D-17
locate, 8-18
UTM, D-20
IN-31
zoom
in, 6-7
map zoom in, 19-68
map zoom out, 19-68
map zoom previous, 19-68
IN-32
out, 6-7
to actual size, 19-31
to nominal map scale, 6-7, 19-4
to previous, 6-7
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).