Geo Media Professional Guide 3g4q3b

‖. During GeoMedia initialization, this option is read, and the menus and toolbars are loaded, for example: GeoMedia.exe /custom “D:\xmlfiles\MySettings.xml”.

The Product Workflows These are simplified example workflows for the most common GeoMedia Professional tasks. Your workflow, of course, will vary with the needs of your project.

General Viewing and Analysis Workflow 1. Create a GeoWorkspace. See the “Working with GeoWorkspaces" section. 2. Define a coordinate system for the GeoWorkspace. See the "Working with Coordinate Systems” section. 3. Create warehouse connections. See the "Working with Warehouses” section. 4. Display data in your map window. See the "Working with Map Windows” section. 5. Change the appearance of the map-window contents. See the "Working with Map Windows” section. 6. Display a data window. See the "Working with Data Windows" section. 7. Build and run a query. See the "Analyzing GeoMedia Professional Data” section.

GeoMedia Professional 's Guide

23

Start Here 8. Create a thematic display. See the "Working with Map Windows" section. 9. Add labels to the map. See the “Analyzing GeoMedia Professional Data” section. 10. Display a layout window. Display a layout window. See the “Working with Layout Windows” section. 11. Prepare the map for printing. See the “Deg Map Layouts for Printing in the Layout Window” section.

General Data-Capture and Maintenance Workflow 1. Create or open a GeoWorkspace. See the "Working with GeoWorkspaces‖ section. 2. Define a coordinate system for a new GeoWorkspace. See the "Working with Coordinate Systems‖ section. 3. Create warehouse connections. See the "Working with Warehouses" and the “Working with Features‖ section. 4. Display data in your map window. See the "Working with Map Windows‖ section. 5. Change the appearance of the map-window contents. See the "Working with Map Windows‖ section. 6. Work with existing features. See the "Working with Features‖ section. 7. Create new features. See the "Working with Features‖ section. 8. Edit features. See the "Editing Features and Geometries‖ section. 9. data. See the "ing Data‖ section. 10. Validate data. See the "Validating and Fixing Data‖ section. 11. Export data. See the "Exporting Data to Other Systems‖ section.

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

24


Start Here

For information on data-capture and clean-up tools, see the “ing Data,” “Validating and Fixing Data,” “Working with Features,” and “Editing Features and Geometries” sections.

Manual Input 1. 2. 3. 4.

Select the digitizer input. Set up the map on the digitizing table. the map coordinates to a GeoWorkspace with the registration tools. 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. Raster snap can be used on binary raster data only. 5. Clean up the data with the validating and editing tools.

Satellite or Photogrammetric Images 1. Select the satellite or photogrammetric images. 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 images as the background, using the raster snap tools to speed data capture.


25

Start Here Raster snap can be used on binary raster data only. 5. Clean up the data with the validating and editing tools.

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.

Into CAD Applications: 1. Return the new and edited features to the CAD applications. 2. Export the features as design (.dgn) files.

Attribute Data in Databases 1. Prepare the attribute data in databases for features with a unique identifier, for example, a Parcel Identification Number (PIN).

2.

Connect to the external data source (database, ASCII file, Excel spreadsheet), using database tools from Access, Oracle, and so forth.

2 In the external source: . Display the attribute data using a database or Excel. Sort the rows by a common identifier, for example, a PIN. Copy the attribute values into a paste buffer.

3.

Execute a Query/Update in 3 In GeoMedia Professional: the database to load the . Display the feature table in a columns based on a common data window. identifier, for example, a PIN. Sort the data window rows by a common identifier. Paste the attribute values from the paste buffer into the data window to populate the features.

Legacy GIS Data Data in legacy systems, like Intergraph's MGE and ESRI's ARC/INFO and ArcView, already represent the graphic location (the map) and information (the database attributes ing the location) for each item on a map. So, for a red line on a map that represents a U.S. Highway, the Department of Transportation may have database attributes that tell the resurfacing, accident, or

26


Start Here bridge-maintenance records. One problem with systems like these is that they do not talk well to each other. GeoMedia Professional provides a platform where you can easily display and manipulate data from all three legacy systems. For an enterprise that wants to migrate part or all of their current GIS to GeoMedia Professional, the workflow uses Intergraph's powerful data-server technology combined with industry-standard databases. Operators can then add or edit data in the new environment.

Migrating Legacy GIS Data into GeoMedia Professional: 1. Connect to the legacy data source (MGE, ArcView, or ARC/INFO). 2. Select the features to migrate. 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. You can import GIS data into any GeoMedia Professional-ed 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.

Using GeoMedia Professional to Maintain a Legacy GIS: With its powerful data-capture abilities, enterprises appreciate GeoMedia Professional's open architecture. This means that they can maintain their investment in a legacy GIS system while capitalizing on the unique productivity tools in the software. 1. Connect to the legacy data source (MGE, ArcView, or ARC/INFO). 2. Select the features to migrate. 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.

5.

Export the GIS features as 5. shapefiles.

6.

Use ArcView or 6. ARC/INFO tools to merge the new and edited features into the legacy GIS.

Use MGE to import warehouse data into an MGE project. Use MGE tools to merge the new and edited features into the legacy GIS.

Capturing Data for a Legacy GIS: GeoMedia Professional's open architecture means that you can use its powerful data-capture abilities to populate a legacy system with new data. The use of industry-standard databases s data-capture, wherever the data are ultimately going to be stored. This means that an enterprise can continue to use their legacy GIS system while capitalizing on the unique productivity tools in GeoMedia Professional.


27

Start Here 1. Capture GIS features using GeoMedia Professional, and store them in Access or Oracle.

2.

Export the GIS features as shapefiles.

2.

Use MGE to import warehouse data into an MGE project.

3.

Use ArcView or ARC/INFO tools to merge the new and edited features into the legacy GIS .

3.

Use MGE tools to merge the new and edited features into the legacy GIS.

What is a GIS? A GIS (geographic information system) is a computer system capable of assembling, storing, manipulating, analyzing, and displaying geographically referenced information. This system contains both data identified according to their locations as well as graphic and nongraphic data.

What Can I Do with a GIS? A GIS allows you to perform the following functions:  Locate information spatially - for example, find a site by latitude and longitude or by proximity to other features.  Visualize information more effectively and intuitively.  Spatially analyze information from many integrated data sources.  Graphically navigate through data sets, for example, drill downs.  Answer questions more quickly and accurately.  Plan work and activities more effectively.  Save resources on construction, maintenance, management, surveying, and similar activities.

Aspects of a GIS The following are some important aspects of a GIS system:  A GIS knows where things are, which is essential to rational decision making in many cases.  A GIS is only as useful and accurate as the information you put into it.  Proper implementation of the technology is critical to the system's success  A map itself is not a GIS; a map is a derived output product of a GIS.  A map is to a GIS as a report is to a database.

Types of Information A GIS may contain the following types of information:  Textual-Reports, tabular data, and data streams.  Image Files-Aerial photos, scanned images, and photographs.  CAD (Vector)-Drawings containing linework, such as floor plans, schematics, and diagrams, which are sometimes drawn to scale and sometimes not.  GIS (Smart Vectors)-Maps, properly scaled and properly oriented, and for multiple projections. Map feature definitions also include nongraphic data (attributes).

28


Start Here 

Other Documents-Office automation: presentations, spreadsheets, web pages, and so forth.

GIS Concepts & Terminology The following are several important GIS concepts and terminology that are used when describing GeoMedia. They are discussed at greater length in their respective parts of this document. Warehouses-Collections of GIS data, for example Oracle, ArcInfo, and CAD databases. GeoMedia establishes connections to warehouses to gain access to the GIS information.

Features-Features are digital representations for real-world entities.



Features have attributes. A feature class definition defines all of the attributes and associated data types. Specific instances of the feature class have unique values for the attribute fields.


29

Start Here

30



Features can represent almost anything.



Features can be represented in the GIS as points, lines, polylines, areas, arcs, text, and images.



Features can be organized into categories, themes, or layers.


Start Here Legends-Legends control what information appears in a map window, including symbology, render order, and interactive characteristics.

Queries and Spatial Queries-Queries are questions, some complex, some simple, that you can pose to the GIS. For example, a simple query might be to see all cities with more than 100,000 people. Or, you may ask to see all states with a population over 100,000 containing cities where the total crime rate is greater than 125. Spatial queries supplement relational operators with spatial operators.

Coordinate Systems and Projections-Mathematical transformations must take place to represent the Earth in two-dimensional space. It is the same source information in each case, just represented differently. This is the primary cause for data from disparate sources not to overlay properly.

Analytical Commands-Complex analyses and processing of the contents of the GIS.


31

Start Here

GIS Applications A GIS can be productively used in many endeavors, including the following: 

Agriculture



Business



Cartography



Meteorology



Geology



Tourism



Education



Archeology



Facilities Management



Military installation management



Asset Management



Environmental Management



Utilities Management (water and sewer, electric, communication systems, cable, cell phone coverage areas, and so forth)



Natural Resources and Resource Conservation



Public Safety (emergency dispatch management)



Disaster planning (hurricane evacuation, earthquake)



Health Care Industry (disease outbreak studies, epidemics)



Industrial (plants, pipelines, storage tanks, and so forth)



Aeronautical (Airport GIS, airspace management)



Marine Engineering (biology, soundings)



State and local government - Land Information Systems (LIS): parcels, right-of-way, and so forth.



Transportation Industry (highways, railroads, planning and analysis)

Benefits of GIS Some of the benefits of using a GIS are the following: Reduces Operations and Maintenance Costs-As a productivity multiplier, a GIS enables less-skilled personnel to complete sophisticated analyses, as well as expanding the output of the technical staff. Improves Mission Effectiveness-A GIS provides command and management personnel with the opportunity to rapidly analyze multidisciplinary sets of data and to arrive at the best solution with complete ing documentation. Provides Rapid Modeling Capabilities for Analyzing Alternative Strategies- A GIS provides the capability for command personnel to make the best and most cost-effective decisions in tight budget environments. Greatly Improved Communication Aids-Effective communication is essential for managing an infrastructure, whether it be a college campus, military installation, or a city. GIS visualization tools are fast and easy to use. Promotes Harmony-By providing a standard set of data and tools for modeling and analysis, major alternatives for a project can be consistently produced and analyzed. This capability helps bring teams together with the increased job satisfaction associated with the feeling of effective group participation. Provides a Repository of Institutional Knowledge-By incorporating as much knowledge as possible into standard GIS functions, the loss of key personnel knowledge can be minimized.

32


SECTION 2

Working with GeoWorkspaces A GeoWorkspace is the container for all your work in this product. Within its confines are the warehouse connections to your data, map windows, data windows, layout windows, toolbars, coordinate-system information, and queries you have built. The first thing you do is open an existing GeoWorkspace or create a new one. Once you are in a GeoWorkspace, you can change its coordinate system, establish warehouse connections, run queries, display data, and perform spatial analyses. The settings and connections you define in a GeoWorkspace are saved in a .gws file, although the actual data remains stored in warehouses. The software is delivered with an example GeoWorkspace, USSampleData.gws. The U.S. Sample Data Set contains a shaded relief image of the United States, complete with hypsometric tints. The data consist of a 1000-meter pixel resolution RGB GeoTIFF file. Every GeoWorkspace is built on a template, and you can create your own templates or use an existing one. The software is delivered with a default GeoWorkspace template, normal.gwt, which contains an empty map window, an empty legend, and a predefined coordinate system. If you accidentally delete the normal.gwt file, you must reinstall the software to restore the template; so it is a good idea to back up this file. This is a representative workflow for creating and configuring a GeoWorkspace: 1. Select File > New GeoWorkspace. 2. Select a template. 3. If the coordinate system you want differs from the one in the template, define a different coordinate system for the GeoWorkspace. 4. Make warehouse connections; configure map and data windows (topics covered in other sections). 5. Save the GeoWorkspace.

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. The software assigns a default title of GeoWorkspace1 to each new GeoWorkspace. When you save a GeoWorkspace, you assign it a filename, and the software automatically adds a .gws extension.


33

Working with GeoWorkspaces

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. GeoWorkspace (*.gws) files created in GeoMedia applications that are saved to disk with queries specific to those applications, such as geometry validation queries, will not open in GeoMedia Professional.

To open a GeoWorkspace: 1. Select File > Open GeoWorkspace.

2. Select the GeoWorkspace you want. 3. Click Open. If a connection fails while attempting to open a GeoWorkspace, an error dialog box appears prompting you to that your warehouse connection parameters are correct.

34



Delaying Data Loading Depending on your data, opening an existing GeoWorkspace may take a long time. The amount of time varies with the number of feature classes being loaded into displays, the amount of data per feature class, and the processing time of any queries. To improve performance, you can delay the loading of data by selecting the Do not load data when opening GeoWorkspace check box on the General tab of the Options dialog box (Tools > Options). If this check box is not selected, which is the default, the software loads all data when opening a GeoWorkspace.

Upon selecting this option, the map windows and data windows are empty when you open a GeoWorkspace. The legend entries in the map view are created but not in a loaded state; the data view shows a title but displays no records. Any existing queries are not re-executed. Also, any subsequent opening of an existing GeoWorkspace, in the same session or future sessions, does not load the data. After opening a GeoWorkspace, you can selectively load its data as follows:

Legend Entries  

Select View > Update All to update all legend entries in all map windows and all data windows. 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.


35


Data Windows  

Select View > Update All to update all legend entries in all map windows and all data windows. Display the right mouse menu, and select Load Data. This is enabled only when the data window is in an unloaded state.

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

Saving, Closing, and Copying a GeoWorkspace In addition to saving GeoWorkspaces automatically through the backup function, there are several ways to save or to close one. When you save or copy a GeoWorkspace, you are saving all its settings—the window configuration, the coordinate system, queries, legends, thematic displays, and warehouse connections—even if you are connected to a read-only warehouse. The default location for GeoWorkspaces is specified during installation, usually the \GeoWorkspaces folder of your root folder. You can change the default folder through the File Locations tab of the Options dialog box. The default file extension for GeoWorkspaces is .gws.  To save changes to a GeoWorkspace any time during a session, select File > Save GeoWorkspace. This saves but does not close the GeoWorkspace.  To save a new GeoWorkspace, select File > Save GeoWorkspace As, and type a name for the GeoWorkspace in the File name field.





36

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.


Working with GeoWorkspaces To change the location of your GeoWorkspace files: The default storage location of your GeoWorkspace files is established when the software is installed, but you can change it from the File Locations tab of the Options dialog box.

E-Mailing a GeoWorkspace When you select File > Send from the GeoMedia 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. 1. Select File > Send. 2. Fill in the To and Subject fields as you would for any e-mail message. 3. Send the message.

Creating a GeoWorkspace Template The default location for GeoWorkspace templates is \Program Files\GeoMedia Professional\Templates\GeoWorkspaces. You can specify a different folder through Tools > Options > File Locations.

To create a GeoWorkspace template: 1. 2. 3. 4.

Select File > New GeoWorkspace. On the New dialog box, select the Template option. Select the normal.gwt template, and click New. Define the GeoWorkspace coordinate system (View > GeoWorkspace Coordinate System). 5. Make the warehouse connections you want for this template (Warehouse > New Connection). 6. Turn on and position—or turn off—the legend, north arrow, and scale bar (View menu).


37

Working with GeoWorkspaces 7. 8. 9. 10.

Adjust the size and locations of the map and data windows. In the map window, display the features and background images you want. Build the queries you want saved with the template. Select File > Save GeoWorkspace As.

If you have named an alternate file location for GeoWorkspace templates, that location appears in the Save in field of the Save GeoWorkspace As dialog box. Then if you want to store the new template in the main templates folder, click the drop-down arrow and browse to the \Program Files \GeoMedia Professional\Templates\GeoWorkspaces folder. 11. that GeoWorkspace Template appears in the Save as type field. 12. Type a name for the template in the File name text box. The file extension must be .gwt. 13. Click Save.

Linking and Embedding a GeoWorkspace GeoMedia Professional can act as an OLE server, which means you can insert a GeoWorkspace as an object into a container application that s OLE. All such applications have an Insert Object command, or something equivalent, that lets you link or embed objects. You can also embed a GeoWorkspace by dragging and dropping the .gws file name from Windows Explorer into a container application. Only one view in a link can be active, and the container application shows the active view by default when you link a GeoWorkspace. However, in some container applications, you can edit the link and change the item part of the link source to a named view, which is the title on a map or data window (by default, MapWindow1 or DataWindow1, for example). When you embed a GeoWorkspace, the entire GeoWorkspace is embedded, not just a single map or data window, although you can see only the active view of the embedded GeoWorkspace in the document of the container document. The embedded GeoWorkspace can be edited in one of two ways. First, you can in-place activate GeoMedia within the container application. When you do this, the container application displays its own File and Windows menus, but all other menus and tools belong to GeoMedia. Clicking outside the embedded GeoWorkspace takes you back to the container document. Second, you can open the embedded document in a separate GeoMedia window. This allows access to the other windows in the embedded GeoWorkspace.

38


SECTION 3

Working with Coordinate Systems This application displays all data—even data from different sources—using the coordinate system defined for the GeoWorkspace. Each feature class stored in a warehouse can have its own unique coordinate system and is transformed on the fly into the GeoWorkspace coordinate system when you display them in the map window. To accurately display raster images, FRAMME data, or data from many non-Intergraph proprietary formats in a GeoWorkspace, the coordinate system of the GeoWorkspace must either match that of the feature data in the warehouse or you must define a coordinate system file for the feature data so that it can be correctly converted for you. Asg a coordinate system to your source data is the only way to ensure that GeoMedia Professional understands the source projection of your data. Data servers that use coordinate system files typically specify the association of feature name to coordinate system file in their .ini file. In some cases these data servers allow the same coordinate system file to be shared by all features in the warehouse. To create a coordinate system file (*.csf), you use the Define Coordinate System File utility that is delivered with the software. A common method to create the .ini file is the Define Warehouse Configuration File utility. See "Displaying Data That Has No Coordinate System Specified" in this section and the Define Coordinate System File utility’s online Help. A coordinate system provides the mathematical basis for relating the features in your study area to their real-world positions. The software s the following types of coordinate systems:  A geographic coordinate system (the default) references a spheroid, expressing coordinates as longitude, latitude, where longitude is the angular distance from a prime meridian, and latitude is the angular distance from the equator.  A projected coordinate system references a projection plane that has a well-know relationship to a spheroid, expressing coordinates as X,Y, where X normally points east on the plane of the map, and Y points north at the point chosen for the origin of the map. The X coordinate is called easting, and the Y coordinate is called northing.  A geocentric coordinate system references an earth-centered Cartesian system, expressing coordinates as defining the position of a specific point with respect to the center of the earth. These coordinates are Cartesian (X, Y, Z) where the X axis of the geocentric system es through the intersection of the prime meridian and the equator, the Y axis es through the intersection of the equator with 90 degrees East, and the Z axis corresponds with the earth‘s polar axis. The X and Y axes are positive pointing outwards, while the Z axis is positive towards the North Pole. 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 the geographic, projected, and geocentric reference spaces. A paper reference space, which is a scaled representation of the projection plane, is also ed. Because the shape of the earth's surface varies from one geographic area to another, the software interprets horizontal coordinates with reference to a network of geodetic control points called the geodetic datum. The horizontal geodetic datum in turn defines the reference ellipsoid, which is the model used to represent the shape of the earth‘s surface. Vertical coordinates


39

Working with Coordinate Systems (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 ed horizontal geodetic datums, vertical datums, and ellipsoids. If you change the coordinate system after displaying data, the data is 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. To customize the datum transformation, edit the datum-transformation-building algorithm in the file …\cssruntm\cfg\autodt.ini. The default coordinate system in the software contains the following settings:  Base storage type—Geographic  Horizontal storage unit—1 degree  Vertical storage unit—1 meter  Projection algorithm—Cylindrical Equirectangular  Projection parameters—Centered at the equator and the prime meridian  Horizontal geodetic datum and ellipsoid—WGS84  Vertical datum—Earth Gravitational Model (EGM96)  Nominal map scale—1:50,000 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 -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 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.

40


Working with Coordinate Systems 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:

For the geographic base storage type, you also define the horizontal and vertical storage units, but the storage center options are longitude, latitude, and height. For the geocentric base storage type, you define the geocentric storage unit and the storage center options of X, Y, and Z. Horizontal storage unit—For the coordinate system of a data source, the horizontal storage unit defines what the distance between sequential integer X or Y coordinate values is when the base storage type is geographic or projection. For example, if the resolution is 0.001 ft., and then the X coordinate of a point changes from 1 to 2, the distance in the X direction of the change is 0.001 ft. This is very important for data sources that store coordinates as integers (MGE, MGDM, MGSM, and CAD with .dgn files) because for these data types, you cannot go between 1 and 2. Thus, the smallest distance that will resolve two values as being separate is 0.001 ft., which leads to the term resolution being applied to integer storage. In the context of IGDS/MGE, this concept was presented with the term UOR (Unit of Resolution), whereas GeoMedia 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 ading 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 s, the horizontal resolution is expressing the very real limitations of the data. For example, you cannot draw a line and measure between two UORs. For other data sources that use floating point, these limitations do not exist (within reason). Much ArcInfo and MapInfo data are defined with a horizontal storage unit of 1 meter (or for geographic data, 1 degree). That just means that the data source chose to store the coordinates in those units. It is not necessary for floating point data to be stored as hundredths of a foot, for example, which would be wasted calculation; they just store it as feet (or meters, or whatever—whole units, usually). 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


41

Working with Coordinate Systems 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). If you are exporting data from an integer-based storage format to a floating-point storage format, you should set the horizontal resolution for the coordinate system in the target warehouse to 1. This ensures that the coordinates stored reflect the actual coordinates of the data rather than the UOR values. Vertical storage unit—For the coordinate system of a data source, the vertical storage unit defines what the distance between sequential Z coordinate values is, when the base storage type is geographic or projection. Geocentric storage unit—For the coordinate system of a data source, the geocentric storage unit defines what the distance between sequential X, Y, or Z coordinate values is, when the base storage type is geocentric. For a geocentric coordinate system, the geocentric storage unit takes the place of both horizontal and vertical storage units because the geocentric storage space has uniform scaling in all directions. The description of how the horizontal storage unit relates to integer and floating point data storage applies also to the vertical storage unit and the geocentric storage unit parameters. Storage center—This is another legacy from integer storage. Integer storage mechanisms such as MGE and CAD .dgn files can only store so many UORs. In some cases, s need to offset the range of UORs that is used (some s 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. If you are exporting data from an-integer based storage format to a floating-point storage format, you should set the storage center for the coordinate system in the target warehouse to 0. This ensures that the coordinates stored reflect the actual coordinates of the data rather than the shifted values.

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

To define a GeoWorkspace coordinate system: 1. Select View > GeoWorkspace Coordinate System.

42


Working with Coordinate Systems 2. On the General tab of the GeoWorkspace Coordinate System dialog box, select the Geographic, Projection, or Geocentric coordinate system type.

3. Optional: To change the storage units and storage center, select the Storage Space tab.

4.

5. 6.

7.

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). 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. Optional: On the Geographic Space tab, select the geodetic datum from the Geodetic datum drop-down list. Optional: If you select a -defined (non-standard) geodetic datum, you can change the ellipsoid on the Geographic Space tab; and if you select a -defined (non-standard) ellipsoid, you can change ellipsoid parameters as well. Optional: On the Geographic Space tab, select the vertical datum from the Vertical datum drop-down list.

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.


43

Working with Coordinate Systems

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

To define a coordinate system for a new feature class: 1. Create or connect to a read-write warehouse. 2. Select Warehouse > Feature Class Definition. 3. On the Feature Class Definition dialog box, click New; then define new feature class name, optional description, and data type. 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. 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

44



6.

7. 8.

9.

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). 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. Optional: On the Geographic Space tab, select the geodetic datum from the Geodetic datum drop-down list. Optional: If you select a -defined (non-standard) geodetic datum, you can change the ellipsoid on the Geographic Space tab; and if you select a -defined (non-standard) ellipsoid, you can change ellipsoid parameters as well. Optional: On the Geographic Space tab, select the vertical datum from the Vertical datum drop-down list.

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 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. You can assign only one default coordinate system per warehouse. 13. Click OK on the New dialog box.


45


Matching GeoWorkspace and Default Warehouse Coordinate Systems The General tab of the Options dialog box (Tools > Options) provides two options to match the GeoWorkspace and default warehouse coordinate systems. These options improve performance when loading and displaying data by not imposing unnecessary coordinate-system transformations. Both options are selected by default.

The default warehouse coordinate system is assigned by clicking the Set As Default button on the New / Edit / Review 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 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.

46


Working with Coordinate Systems The When creating a new warehouse option does not apply to the Oracle Object Model. When using the Oracle Object Model, you need to that the coordinate system is set to what you want it to be; it is not automatically set by the software.

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 for the new coordinate system and display scale.

Copying the GeoWorkspace Coordinate-System Definition onto the Default Coordinate System of a New (Access) Warehouse If you select the matching options, the software copies the definition of the coordinate system of the GeoWorkspace into the warehouse and marks it as the default coordinate system for the warehouse. This definition is written into the GCoordSystem table of the database. The software creates a new row if necessary. You can actually use the New Warehouse command in two slightly different ways to create 1) a new Access warehouse (.mdb – the default), or 2) a new Access warehouse template (.mdt). Only when creating a new warehouse (.mdb) does the command establish a connection to the new warehouse. Because an open connection is required to update or to add a row to the GCoordSystem table of the warehouse, it is only when a new warehouse (not warehouse template) is created (and the preference is set) that the New Warehouse command copies the GeoWorkspace coordinate system to the warehouse and marks it as the default coordinate system. The impacts of copying the GeoWorkspace coordinate-system definition onto the coordinate system of a new (Access) warehouse affect the optimum workflow. The optimum workflow in many situations is to first use New Connection to connect to your data source, thus setting the GeoWorkspace coordinate system, and then to use New Warehouse to create any new warehouse(s). This ordering ensures that the new warehouse shares the same coordinate-system definition with the data source and GeoWorkspace.

Getting Coordinate Readouts To see the coordinates of any location in the map window, turn on the Precision Coordinates display (View > Precision Coordinates).

This control displays the precision coordinates for the current cursor position in the map window. The current coordinate format drop-down list determines if the displayed 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


47

Working with Coordinate Systems have the option to update coordinates with a mouse move (the default) or with a click. The coordinate display and entry options drop-down menu displays options that include the following:  Update coordinates on mouse move  Update coordinates on click  Clear coordinates after enter (this option applies to precision keyins, not to precision readouts) See the Precision Coordinates Help topic in GeoMedia Professional Help for complete information.

Setting Units and Formats When setting a GeoWorkspace coordinate system, the Units and Formats tab of the GeoWorkspace Coordinate System dialog box allows you to set default measurement options for all commands that involve measuring, for example, Measure Distance/Area and Analyze Geometry. This tab also allows you to control the way coordinate readout information appears on the Precision Coordinates dockable control. When setting the coordinate system of a feature class, the Units and Formats tab allows you to set the units and formats parameters on the tab; however, when the dialog box is displayed from the Feature Class Definition command, these parameters only have an effect on this dialog box or its subdialog boxes (for example, the Projection Parameters dialog box). Specific units and formats are not stored for individual features, only the coordinate system and the master unit are stored. This is also true for other commands (commands other than the GeoWorkspace Coordinate System command) that use this dialog box.

These are the options you can set on the Units and Formats tab:

  

48

Type specifies the type of unit for which to set the default unit and precision. Each unit type used by the software is listed. When the software outputs values of the specified unit type, those values by default are displayed using the units and precision specified here. Some commands allow you to override these defaults. Unit sets the linear, areal, or angular unit of measure. The choices vary with the unit type. Precision defines the number of decimal places of precision in the coordinate-readout applicable commands. A separate precision may be specified for each unit type. Geographic coordinate format defines the ordering of longitude and latitude values and the definition of the positive direction of the two axes (including the option for using character designators) when geographic coordinates are formatted or parsed as ASCII strings.


Working with Coordinate Systems 



Projection coordinate format defines the ordering of projection east/west and north/south values and the definition of the positive direction of these two axes used in projection coordinate strings that are formatted for output or parsed for input. Measurement interpretation specifies how Earth curvature and nominal map scale are ed for in measurements and coordinate calculations.  True (spheroidal) specifies that distance/area/azimuth(bearing) measurements are taken on the surface of the ellipsoid by taking the curvature of the Earth into . These measurements do not contain any projection distortions.  Projected (planar) specifies that distance/area/azimuth(bearing) measurements are taken on the projection plane without taking the curvature of the Earth into . These measurements do contain projection distortions. This is the default setting.  Paper (scaled) specifies that distance measurements are computed on the paper plane that is scaled in relation to the projection plane at the current nominal map scale.

This option is available only when the Units and Formats dialog box is displayed with the Tools > Measure Distance/Area dialog box.  Azimuth settings specify the direction and starting point when setting and displaying azimuths. An azimuth is a way of specifying an angle by measuring either clockwise or counterclockwise from 0 to 360 degrees. These options apply to the distance and azimuth readouts and keyins, and to some coordinate system projection parameters. See the “Conversion Tables” appendix for multiplication factors for converting from/to the International System of Units (metric) to/from the United States Customary System. Units and formats can be temporarily set when displaying the Units and Formats dialog box from the Tools > Measure Distance/Area dialog box and the Insert > Feature dockable control. The Paper (scaled) measurement interpretation is only available with the Tools > Measure Distance/Area dialog box. See "Measuring Distances" in the "Working with Map Windows" section.

Configuring for Datum Transformations To convert data between two coordinate systems that are based on different horizontal or vertical geodetic datums, you need one or more datum transformations. The software uses the autodt.ini file to generate datum transformations during the building of coordinate-system transformation paths, such as the path between the GeoWorkspace coordinate system and a warehouse coordinate system. The autodt.ini file is in the …\cssruntm\cfg folder. When datum transformation is needed to go between a specific set of datums, the entries from this file are used to create a network graph of the datum transformation possibilities and the shortest path through the graph is used to choose the set of datum transformations that you want. When building the graph, the software processes this file in order from top to bottom. Where more than one file entry exists to transform between a given set of datums, only the first entry will be used. You can cause a different model or definition to be used by changing the order of the entries in the autodt.ini file. You can also define new entries for many models, if you have access to the parameters for these models that suit your needs. The Second Degree Conformal Polynomial model may be used to achieve a Helmert transformation. All datum transformation models can transform in both the forward and inverse directions. For example, an entry that begins "csgdNAD27, csvdNAVD88,csgdNAD83,csvdNAVD88, . . ." will match a search for a transformation to go from NAD83 to NAD27 as well as a transformation from NAD27 to NAD83. Details of the syntax for model-specific parameters are included as comments in the autodt.ini file. The general syntax for all entries in this file is as follows:


49

Working with Coordinate Systems ForwardInputHorizontalDatum,ForwardInputVerticalDatum,ForwardOutputHori zontalDatum,ForwardOutputVerticalDatum,DatumTransModelType[,model-speci fic-parameters...]   

  



Fields are separated by a comma (,). A semicolon (;) in the first column denotes a comment line. Horizontal datums are defined using the ASCII mnemonics from the CSGeodeticDatumConstants enumeration and named horizontal datum names from the NamedHDatum.ini configuration file. Vertical datums are defined using the ASCII mnemonics from the CSVerticalDatumConstants enumeration. Datum-transformation-model types are defined using the ASCII mnemonics from the CSDatumTransformationModelConstants enumeration. This file is never localized for different languages, rather, it is always interpreted in English (it uses the comma for the field separator and the dot for the decimal character). No thousands grouping character is used. Floating point values are never written in scientific notation.

When you make changes to the autodt.ini file, they do not affect any GeoMedia 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 s.

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

To define a coordinate-system file: 1. From the Windows Start menu, select All Programs > GeoMedia Professional > Utilities > Define Coordinate System File. 2. On the General tab of the Define Coordinate System File dialog box, select the base storage type—Geographic, Projection, or Geocentric—of the coordinate-system that is to be saved to the file. 3. Optional: To change the storage units and storage center, select the Storage Space tab.

50



4. 5. 6. 7.

8.

9.

10. 11.

12. 13. 14.

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). For projected coordinate systems only: On the Projection Space tab, select a projection algorithm from the Projection algorithm drop-down list. Optional: To change parameters, click Projection Parameters. Depending on the projection algorithm selected, some text boxes may be read-only. Optional: On the Geographic Space tab, select the geodetic datum from the Geodetic datum drop-down list. Optional: If you select a -defined (non-standard) geodetic datum, you can change the ellipsoid on the Geographic Space tab; and if you select a -defined (non-standard) ellipsoid, you can change ellipsoid parameters as well. Optional: On the Geographic Space tab, select the vertical datum from the Vertical datum drop-down list. Changing the coordinate system type from Projection or Geographic to Geocentric resets the vertical datum to Ellipsoid (geometric). 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. On the Define Coordinate System File dialog box, click Save As. On the Save Coordinate System File As dialog box, select the drive and folder where you want to save the coordinate-system file. If you do not select a path, the coordinate-system file will be saved in the root folder of your active drive. Select one of the following locations:  The folder containing the specific warehouse for which the coordinate-system file defines coordinate data. This is the preferred location.  The folder where the warehouses are stored. The default is \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. In the File name text box, type the name that you want to give to the coordinate-system file. that the Save as type is set to Coordinate System File (*.csf). Click Save.

To display ArcInfo data: (.csf) You identify the coordinate-system file for the ArcInfo data by creating a <workspace>.ini file, where <workspace> is the name of the ArcInfo GeoWorkspace data folder. Within this file, you specify the coordinate-system file to be used. Place the <workspace>.ini file in the ArcInfo GeoWorkspace folder, or if that is not possible, in the software‘s \Warehouses folder specified during installation. See the “Creating Data Server .INI Files” topic in GeoMedia Professional Help.


51

Working with Coordinate Systems To display ArcView data: You identify the coordinate-system file for the ArcView data by creating a <workspace>.ini file, where <workspace> is the name of the ArcView GeoWorkspace data folder. Within this file, you specify the coordinate-system file (.csf) to be used. Place the <workspace>.ini file in the ArcView GeoWorkspace folder, or if that is not possible, in the software‘s \Warehouses folder specified during installation ($/GeoMedia Professional/bin is the one specified for the .ini file). See the “Creating Data Server .INI Files” topic in GeoMedia Professional Help.

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

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

To display MapInfo data: You identify the coordinate-system file for the MapInfo data by creating a <workspace>.ini file, where <workspace> is the name of the MapInfo GeoWorkspace folder. Within this file, you specify the coordinate-system file (.csf) to be used. Place the <workspace>.ini file in the MapInfo GeoWorkspace folder, or if that is not possible, in the software‘s \Warehouses folder specified during installation. If there is no .ini file, the data server will look for a .csf file in the MapInfo GeoWorkspace folder that bears the same name as the MapInfo table and use that .csf file for the corresponding GeoMedia Professional feature class. This way, you need one .csf file for one feature class in the

52


Working with Coordinate Systems GeoWorkspace folder. You cannot use a single .csf file for the whole folder unless you specify it in the .ini file. See the “Creating Data Server .INI Files” topic in GeoMedia Professional Help.

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

To edit a coordinate-system file: To edit an existing .csf file, double click the file name. This opens the Define Coordinate System File dialog box. Make changes to the file, and click OK.

Creating Coordinate-System Files from Design Files You can easily create a coordinate-system file (.csf) from an IGDS design file (.dgn) with Define Coordinate System File. This utility can read a .dgn file if you: 1. Drag the .dgn file from Explorer onto the Define Coordinate System File icon. OR 2. Rename the file from a .dgn extension to a .csf extension and then double click to open the file in Define Coordinate System File. OR After invoking the Define Coordinate System File utility from the Start menu, select the Load button. Then on the Load Coordinate System From File dialog box, change the Files of type selection to Design Files (*.dgn). Note that Define Coordinate System File can only read .dgn files, not write to them. The only format this utility can write to is the .csf (OLE compound files structured-storage) format. If you want to write coordinate-system information into a type-56 element of a design file, you need to use MGE. Also, in this 6.1 version of the software, MicroStation Version 8 .dgn files can be read. Define Coordinate System File reads .dgn files with or without a type-56 element. Without a type-56 element, it reads only the information on working units (storage units) and global origin (storage center) from the type-9 element. It then sets the projection to Rectangular Grid, which means no algorithm is defined to get from Projection to Geographic coordinates. With a valid type-56 element, in addition to reading the type-9 element, this utility reads projection and datum information from the type-56 element. A potential workflow to use this capability would be with CAD server when you have .dgn data, and 1) the .dgn data does not contain a type-56 element with projection information, and 2) the information of the .dgn about working units (storage units) and global origin (storage center) is valid. In this case, if you know the projection information, but for example were digitizing with vanilla MicroStation, you may want to use Define Coordinate System File to read the working units and global origin information of the .dgn. You would then use it to define the projection and datum, and you would save the information out to a .csf file.


53


54


SECTION 4

Working with Warehouses You display feature geometries and attribute data in a GeoWorkspace through connections to warehouses where the data is stored. Each warehouse connection uses a data server to convert the data into a format that the software can display. Connections are links that allow the transfer and translation of feature data from the various ed data warehouse types.

You can output feature data in any GeoMedia Professional-ed format to a warehouse with the Output to Feature Classes command. You must have at least one read-write open connection to use this command. See the “Outputting Feature Data to Warehouses” section of the “Working with Features” section. The New Connection command lets you easily create warehouse connections. This command guides you through the process of entering the information necessary to define and to make the connection to your data. You specify the name and location of the connection and all the necessary connection parameters. This command lets you specify a warehouse configuration (.ini) file for many data connections. You can create the .ini files using the Define Warehouse Configuration Utility before connecting to the data. See the “Creating Data Server .INI Files” and the “New Connection Dialog Box” topics in GeoMedia Professional Help and the Define Warehouse Configuration File utility's online Help for complete information. 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



MGE Data Manager (MGDM)



ARC/INFO



MGE Segment Manager (MGSM)



ArcView shapefile



ODBC Tabular


55

Working with Warehouses ®



CAD - AutoCAD and MicroStation /IGDS



®



Oracle Object Model

FRAMME



SQL Server



GeoGraphics



SmartStore Server



GML (Geography Markup Language)



Text File Server



I/CAD MAP



WCS (Web Coverage Service)



KML (Keyhole Markup Language)



WFS (Web Feature Server)



MapInfo



WMS (WebMap Server)



Modular GIS Environment (MGE)

™

All warehouse types are read-only, except for Access, Oracle, SQL Server, and WFS. 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 “Working with Map Windows” and “Working with Data Windows” 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). Display the feature data.Whether you are displaying data or writing it, your GeoWorkspace can contain data from many different sources, even those whose native data types are incompatible. This is a representative workflow for importing data into a read-write warehouse: 1. Follow the steps in the preceding workflow to identify the area for which data are to be imported. 2. Optional: Define a coordinate system for the empty warehouse. (The GeoWorkspace defaults to the coordinate system from the first feature added to the legend.) Import feature classes from the connected warehouses into your read-write warehouse (Access, Oracle Object Model, or SQL Server).

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

56


Working with Warehouses To create a read-write Access warehouse: 1. 2. 3. 4. 5.

Select Warehouse > New Warehouse. On the Warehouse Template dialog box, select a template. The default is normal.mdt. that the Document option is selected. Click New. On the New Warehouse dialog box in the Save in field, select a storage location. The default is \Warehouses.

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.

Defining a Coordinate System for a Warehouse Normally, you define a warehouse coordinate system only for an empty read-write Access warehouse that you just created. You can view but cannot change the coordinate system in a warehouse in which feature classes already exist, but you can accomplish a change to the coordinate system with the following procedure: 1. Create a new read-write Access warehouse. 2. Change the coordinate system. 3. Import the data into the new warehouse. 4. Delete the old warehouse. If you plan to use multiple coordinate systems in your Access warehouse, you need to assign one coordinate system to use as the default 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” section.

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.


57

Working with Warehouses

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

Connecting to an ArcInfo Warehouse To connect to an ArcInfo, you must identify or select an ArcInfo warehouse folder. Before trying to connect, check the following:  ArcInfo 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 ArcInfo data must be created with Define Coordinate System File.  The coordinate-system file for the ArcInfo data must be identified in a .ini file, which should be stored in the ArcInfo GeoWorkspace folder, or if that is not possible, in the software's \Warehouses folder.  For ease of maintenance, you should store the .csf and .ini files along with the data in the ArcInfo warehouse folder as the primary location. When this is not possible (due to read-only media, for example), you should store these files in the default warehouse location, and the software will find them there. The software does not the PC version of ArcInfo. See the “Displaying Data That Has No Coordinate System Specified” section in the “Working with Coordinate Systems” section and the “Creating Data Server .INI Files” topic in GeoMedia Professional Help.

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

58



Connecting to a CAD Warehouse To connect to a CAD warehouse, you must identify or select a CAD Server Schema file. Before trying to connect, check the following: For AutoCAD and MicroStation V8 data, a coordinate-system file (.csf) must have been created with Define Coordinate System File. See the “Displaying Data That Has No Coordinate System Specified” section in the “Working with Coordinate Systems” section. 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. 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. To use the Define CAD Server Schema File utility, you must have clear and complete understanding of your CAD data.. To use the Define CAD Server Schema File utility, you must have clear and complete understanding of your CAD data. See the “Creating Data Server .INI Files” topic in GeoMedia Professional Help. See the Define CAD Server Schema File utility's online Help for complete information about this utility.

ed MicroStation Element Types The following table lists the MicroStation element types ed by GeoMedia Professional: Type

Name

GDO Geometry Type

2

Cell (named)

OrientedPointGeometry, TextPointGeometry, and Collection Geometry. This is served based on the .ini file variables.

2

Cell (orphaned)

BoundaryPolygonGeometry

2

Cell (unnamed)

BoundaryPolygonGeometry

3

Line

PolylineGeometry and OrientedPointGeometry. In case of degenerate lines, OrientedPointGeometry is served.

4

LineString

PolylineGeometry

6

Shape

PolygonGeometry

7

TextNode

TextPointGeometry (collection)

11

Curve

Stroked PolylineGeometry

12

Complex String

CompositePolylineGeometry

14

Complex Shape

CompositePolygonGeometry


59

Working with Warehouses Type

Name

GDO Geometry Type

15

Ellipse

PolygonGeometry

16

Arc

Stroked PolylineGeometry for elliptical arcs. ArcGeometry for circular arcs.

17

Text

TextPointGeometry

22

Point

OrientedPointGeometry (collection)

35

Shared Cell

OrientedPointGeometry, TextPointGeometry, and CollectionGeometry. This is served based on the .ini file variables.

Connecting to a FRAMME Warehouse To connect to FRAMME data, the software needs a valid FRAMME gateway file (.gtw). You specify the location of the FRAMME Gateway file and select the FRAMME segments you want. Identifying a warehouse configuration (.ini) file is optional. If necessary, use Define Coordinate System File to create a coordinate-system-file for your FRAMME data. Also, certain data configurations may require a .ini file for your FRAMME data server. See the “Displaying Data That Has No Coordinate System Specified” section in “Working with Coordinate Systems” and the “Creating Data Server .INI Files” topic in GeoMedia Professional Help.

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

60



Connecting to a GML Warehouse To connect to a GML (Geography Markup Language) Server warehouse, you must indicate the following:  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:  When the GeoReferenceService (GRS) fails to return the coordinate system (CS) object for a given EPSG code and a matching coordinate system file is not found for a feature class in the default \EPSG folder, the options are:  Ignore the coordinate system, that is, serve the feature class data without the coordinate system.  Skip the feature class.  Abort the connection and report an error about the missing coordinate system file.  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.

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

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


61


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

Connecting to a KML Warehouse To connect to a KML (Keyhole Markup Language) Server warehouse, you must indicate the following:  KML connection name and optional description.  KML file. Type or browse for the KML or KMZ (zipped KML files) file path and name.  Warehouse configuration file (optional). Type or browse for the .ini file that may contain the parameters required for the configuration of geometry types for feature classes. See the ―Creating Data Server .INI Files” topic in GeoMedia Professional Help.

Connecting to a MapInfo Warehouse To connect to a MapInfo warehouse, you must specify the folder location of the MapInfo files, the MapInfo Tables folder with valid MapInfo tables (.tab or .txt files). The server can then read the MapInfo tables in the folder and create the feature classes. Before trying to connect, check the following:  A coordinate-system file (.csf) for the MapInfo data must be created with Define Coordinate System File and be referenced by the .ini file. There can be one .csf file for the entire MapInfo dataset or one .csf file created for each MapInfo table.  MapInfo data must be in native format (not exported). There should be a table file (.tab), an index file (.id), a map file (.map), and/or an info file (.dat/.dbf or .xls). All four files are needed for both geometry and attribution.

62


Working with Warehouses 

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 the “Displaying Data That Has No Coordinate System Specified” section in the “Working with Coordinate Systems” section and the “Creating Data Server .INI Files” topic in GeoMedia Professional Help.

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

Connecting to an MGSM Warehouse To connect to MGSM data, you will need to identify the following:  MGE project file (.mge)  Warehouse configuration file (.ini) See the ―Creating Data Server .INI Files” topic in GeoMedia Professional Help.  Parameter file (.prm)  Seed file (.dgn)  Coordinate file (.crd)  RIS schema (if using RIS and the schema is ed) Use your ODBC 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.


63


Connecting to an ODBC Tabular Warehouse Before you try to connect to an ODBC Tabular Model warehouse, you must set up an ODBC connection through the ODBC Data source . You will need to choose the correct ODBC driver for the database you want to connect and enter the appropriate information. To connect to ODBC Tabular Model data, you will need to identify the following:  ODBC connection name.  ODBC Data source (from the ODBC ).  ID (as required by data source).  (as required by data source). Using the ODBC Tabular read-only data server is an alternative to using the Attach table command (Warehouse > Feature Class Definition). This data server uses Microsoft's ODBC and ADO technology to create a warehouse connection and to serve up any type of data that can be used with the Settings > Control , Data Sources (ODBC) command. If you are connecting to text files, you place the files in a folder to themselves and then use the Data Sources (ODBC) command to create a Data Source Name (DSN) that points to the folder containing the data. The connection will read the Schema.ini file found in the folder to determine the format of the text file(s). You can create the Schema.ini file manually or use the Data Sources command to create the file. See the “Working with Feature Classes” section in the “Working with Features” section 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. 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 the Microsoft link (http://www.microsoft.com).

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

64


Working with Warehouses   

name. . Host string. The host string is the Oracle database alias/service name that you create with the Oracle network configuration utility.

Connecting to a SQL Server Warehouse Before you try to connect to a SQL Server warehouse, you must set up a SQL Server database. To connect to SQL Server data, you will need to indicate the following:  SQL connection name.  Server name.  SQL Server database name.  Whether to use Windows to authenticate the network ID or to use SQL Server to authenticate the ID and .  .  .

Connecting to a SmartStore Server Warehouse The GeoMedia SmartStore warehouse is a spatially indexed cache of 2-D geometry and significant attributes used to facilitate the quick generation of maps without querying the original warehouse database. It s all of the GeoMedia GDO-based warehouse types. The GeoMedia SmartStore data server s read-only access to the SmartStore warehouse. See the Publish to GeoMedia SmartStore Warehouse utility's online Help for complete information on this server and its limitations. Before you try to connect to a GeoMedia SmartStore warehouse, you must indicate the following:  A single GeoMedia SmartStore file (.ddc) OR  A GeoMedia SmartStore GeoWorkspace folder containing one or more GeoMedia SmartStore files. The Select a folder containing GeoMedia SmartStore files option on the New Connection dialog box assumes that the .ddc files you have published to this folder came from a single source warehouse. If your folder contains .ddc files from multiple source warehouses, you will encounter errors. You have the option of using the coordinate system of the input warehouse, or of specifying that SmartStore is to transform the data to a different coordinate system.

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


65


Connecting to a WCS Warehouse To connect to a WCS (Web Coverage Server) warehouse, you must indicate the following:  WCS connection name and optional description.  Web Coverage Server (WCS) URL  Type the WCS URL in the format http://host[:port]/path?{name[=value]&}. If the name-value parameters are specified, the request type should be 'GetCapabilities', and the REQUEST parameter should be specified only as "REQUEST=GetCapabilities". Example formats are: http:// host[:port]/path, OR http://host[:port]/path?REQUEST=GetCapabilities&SERVICE=WCS&VERSION=1.0.0  Example URL: http://lapserv/CoverageWebService/coverage.aspx  If you do not specify a version parameter, the data server issues the request with version 1.0.0. If the WCS does not this version, then the connection fails and an error is presented as: "Version negotiation failed. The WCS does not the versions ed by the data server (1.0.0)."  Warehouse configuration (.ini) file (optional)  Advanced options:  If no matching coordinate system is found for a feature class (coverage), select one of the following options that give the connect command instruction for cases where no matching coordinate system is found for a feature class:  Ignore coordinate system If the software cannot automatically translate the given EPSG code into a coordinate system definition and if a matching coordinate system file is not found in the default \Program\EPSG folder, the feature class will be served without a coordinate system.  Skip feature class If the software cannot automatically translate the given EPSG code into a coordinate system definition and if a matching coordinate system file is not found in the default \Program\EPSG folder, the feature class is not shown (that is, no tabledef is created by the data server for this feature class).  Abort connection and report error If the software cannot automatically translate the given EPSG code into a coordinate system definition and if a matching coordinate system file is not found in the default \Program\EPSG folder, an error is displayed that indicates the location and name of the missing coordinate system file. Also, the connection fails. The ..\Program Files\GeoMedia <product>\Program\EPSG folder is designated to be the default folder for coordinate system files (CSF).

Connecting to a WFS Server Warehouse Before you try to connect to a WFS (Web Feature Server) warehouse, you indicate the following: For GeoMedia Professional, WFS is both read-write and read-only; for GeoMedia and GeoMedia Viewer, it is read-only.  WFS connection name and optional description  Web Feature Server (WFS) URL  Type the WFS URL in the format http://host[:port]/path?{name[=value]&}. If the name-value parameters are specified, the request type should be 'GetCapabilities', and

66



 

the REQUEST parameter should be specified only as "REQUEST=GetCapabilities". Example formats are: http:// host[:port]/path, OR http://host[:port]/path?REQUEST=GetCapabilities&SERVICE=WFS&VERSION=(1.1.0/1 .0.0/0.0.14/0.0.13)  Example URL: http://lapserv/ManipulateFeatureService/request.aspx  If you do not specify a version parameter, version negotiation takes place between the WFS and the data server for a mutually agreeable version. If the WFS does not any of the versions ed by the data server (1.1.0/1.0.0/0.0.14/0.0.13), an error is presented as: "WFS does not the versions ed by the data server (1.1.0/1.0.0/0.0.14/0.0.13)." Warehouse configuration (.ini) file (optional) Advanced options:  When a matching coordinate system file is not found for a feature class in the default \EPSG folder, the options are:  Ignore the coordinate system, that is, serve the feature class data without coordinate system.  Skip the feature class.  Abort the connection and report an error about the missing coordinate system file.  Swap the coordinate order for the following coordinate system types: Geographic and Projected.

Connecting to a WMS Warehouse Before you try to connect to a WMS (WebMap Server) warehouse, you need to indicate the following:  WMS connection name and optional description  Web Map Server (WMS) URL  Type the WMS URL in the format http://host[:port]/path?{name[=value]&}. If the name-value parameters are specified, the request type should 'GetCapabilities', and the REQUEST parameter should be specified only as "REQUEST=GetCapabilities". For WMS 1.1.0, 1.1.1 and 1.3.0, "SERVICE=WMS" parameter is mandatory. Example formats are: http:// host[:port]/path, OR http://host[:port]/path?REQUEST=GetCapabilities&SERVICE=WMS&VERSION=(1.3.0/ 1.1.1/1.1.0/1.0.0) Example URL: http://lapserv/GenerateMapService/request.aspx  If you do not specify a version parameter, version negotiation takes place between the WMS and the data server for a mutually agreeable version. If the WMS does not any of the versions ed by the data server (1.3.0/1.1.1/1.1.0/1.0.0), an error is presented as: "WMS does not the versions ed by the data server (1.3.0/1.1.1/ 1.1.0/1.0.0)."  Warehouse configuration (.ini) file (optional)  Advanced options:  When the GeoReferenceService (GRS) fails to return a 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:  Skip feature class.


67


 

 Abort the connection and report an error about the missing coordinate system file. In the case of secured sites, you can type the name and . You can choose the file format from the drop-down list that has two items – image/png and image/jpeg. If you do not make a selection, the format defaults to image/png.

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

Enabling AFM Proxy Servers for GeoMedia PublicWorks Manager One of the connection parameters lets you enable a data server to use an AFM (Advanced Feature Model) proxy server to proxy the warehouse connection. An AFM proxy server is one that is AFM aware or enabled so that it can process AFM metadata if it is present. See the GeoMedia PublicWorks Manager documentation for more information on proxy servers (available with GeoMedia PublicWorks Manager). You enable this capability by checking the Enable advanced feature model check box, below the Connection type list, on the New Connection dialog box. You can later change this setting through the Connections command on the Properties dialog box, displayed when you click the Properties button. This check box is enabled if the following criteria are met.  The AFM proxy server is available.  The data server is one of the following servers: 

Access read-only



Oracle Object Model read-only



Access read-write



Oracle Object Model read-write



Oracle Object LTT read-onl



SQL Server read-only



Oracle Object LTT read-write



SQL Server read-write

For all other cases, the connection is not proxied. While using the Connections command, if the connection type is AFM.GDatabase. In such case, instead of displaying the data server type as AFM, the underlying data server name is determined and populated.

68



Setting Connection Status The Connections command lets you set the connection status by opening, closing, and reopening connections. The dialog box of this command displays all the connections present in the GeoWorkspace in a grid, sorted in alphabetical order by name. The read-only columns display the name, connection type, and warehouse. GeoMedia Viewer only allows read-only connections; however, GeoMedia Professional and GeoMedia allow both read-only and read-write connections. The status of a connection is indicated by an icon to the left of the connection name as follows:

Your choices of status are summarized in the following table: Command Button

Open Connection

Open Read-Only

Reopen Connection

Close Connection

Initial Connection Status

Final Connection Status If the data server is read-only:

If the data server is read-write:

Open read-write

N/A

No action - status remains unchanged.

Open read-only



Closed

Open read-only

Open read-write

Open read-write

N/A


Open read-only



Closed

Open read-only

Open read-only

Open read-write

N/A

Open read-write

Open read-only

Open read-only

Open read-only

Closed

N/A

N/A

Open read-write

Closed

Closed

Open read-only

Closed

Closed

Closed



If you choose an open status, the software creates a physical connection to the warehouse. If you choose a closed status, you will not have immediate access to the data. Later you can change the status simply by editing the warehouse connection status. Reopening connection(s) closes and then automatically reopens the selected connection(s) as a shortcut for refreshing their contents. The Library and Catalogs commands use a similar connection system and interface. (The Library command is not available in GeoMedia Viewer.)


69


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

To create a new warehouse connection: 1. Select Warehouse > New Connection.

2. 3. 4. 5. 6.

Select the Connection type appropriate for your data. Optional: Check the Enable advanced feature model check box if available. Type a Connection name, or keep the default. Optional: Type a Connection description. Provide the remaining required information, which varies with each connection type; then click OK. Avoid opening more than one connection to a single warehouse.

To open, reopen, or close a warehouse connection: 1. Select Warehouse > Connections.

70


Working with Warehouses 2. Select the row selector of the row(s) whose open/close status you want to change.

Use Shift/Ctrl to select multiple rows; click the top left-corner grid button, to the left of the Name row, in order to select all rows. 3. Click the appropriate open, reopen, or close button.

To create a new warehouse connection: 1. Select Warehouse > Connections. 2. Click New to display the New Connections dialog box; then follow the previously described procedure to create a new warehouse connection.

To view or edit warehouse connection properties: 1. Select Warehouse > Connections. 2. On the Connections dialog box, select the row of the connection whose properties you want to view or edit; then click Properties.

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

Creating an Access Warehouse Template The default location for warehouse templates is \Program Files\GeoMedia Professional\Templates\Warehouses. You can specify a different folder through Tools > Options > File locations.


71

Working with Warehouses To create an Access warehouse template: 1. 2. 3. 4.

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

Changing the Coordinate System of a New Access Warehouse Template Because the New Warehouse command does not establish a connection when you use it to create a new Access warehouse template (.mdt), you should use the following workflow to change the coordinate system of such a new template. See the “Working with Coordinate Systems” section.

To change the coordinate system of a new access warehouse template: 1. Using the procedure from the previous section, create and save a new Access warehouse template, selecting normal.mdt as the template on the New dialog box.

2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13.

Because you are creating a template, no GeoWorkspace coordinate-system matching occurs, regardless of the preference setting. From the Start menu, select All Programs > GeoMedia Professional > Utilities > Database Utilities. On the Database Connection dialog box, that the Database type is Access. Click Browse to display the Open dialog box; then set the Files of type filter to All files (*.*) to display the template file. Select the appropriate Access warehouse template name; then click Open. On the Database Connection dialog box, click OK. On the Database Utilities dialog box, click Assign Coordinate System. On the Assign Coordinate System dialog box, click Select Coordinate System. On the Select Coordinate System dialog box, click New. Define the coordinate system on the Coordinate Systems Properties dialog box; then click OK. On the Select Coordinate System dialog box, select the coordinate system you just defined; then click Assign. On the Assign Coordinate System dialog box, click OK. On the Database Utilities dialog box, click Close. See the Database Utilities online Help for complete information on using this utility.

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 >

72


Working with Warehouses Options), the coordinate system defined in the template by the previous procedure will be the coordinate system of the newly created Access warehouses.

Configuring PickLists with Access Warehouses GeoMedia Professional includes for the use of PickLists through the Properties dialog box (Edit > Select Set Properties). PickLists allow for a predefined list of values to be used when updating attribute fields. For Oracle and SQL Server, see the "Using Oracle Connections" and "Using SQL Server Connections" appendices, respectively. GeoMedia Professional determines if an attribute has a PickList by querying a preconfigured metadata table. The name of the table that stores the PickList configuration must be defined in GAliasTable with a TableType of INGRPickLists. You can use any name you want for the PickList definition table as long as it is referenced in the GAliasTable. Use Microsoft Access to make the necessary changes to the GAliasTable. For example, if the PickList definition table were called GPickListTable, the following entries would need to be added to GAliasTable: GAliasTable TABLETYPE

TABLENAME

INGRPickLists GPickListTable The table referred to by the GAliasTable entry for INGRPickLists must contain the following fields: FeatureName, FieldName, PickListTableName, ValueFieldName, DescriptionFieldName, and FilterClause. Use the New Table command in Access to create the PickList metadata table using the following provided definitions (the table itself can be called anything as long as it is referenced in the GAliasTable): GPickListTable Column Name

Datatype

FeatureName

Varchar(255)

FieldName

Varchar(255)

PickListTableName

Varchar(255)

ValueFieldName

Varchar(255)

DescriptionFieldName

Varchar(255)

FilterClause

Varchar(255)

In the table definition:  FeatureName and FieldName refer to the Feature Class and the specific Attribute field for which the PickList is to be used.  PickListTableName specifies a table in the schema containing the PickList values.  ValueFieldName and DescriptionFieldName refer to the name of the fields in the table containing the PickList values.  The ValueFieldName specifies the field in the PickList table that contains values to be stored in the database. The datatype of the field in the PickList table specified here must match the datatype of the Attribute assigned in the FieldName.


73

Working with Warehouses 

The DescriptionFieldName specifies the field that contains PickList descriptions to be displayed in the pop-up menu on the Attribute tab of the Properties dialog box.  The values stored in ValueFieldName and DescriptionFieldName could be the same when the displayed values are the same as the stored values.  The FilterClause is optional and may contain a 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 ed. The following is an example of tables, columns, and values that could be defined for PickLists:

GAliasTable TableType

TableName

INGRPickLists

GPickListTable

GPickListTable FeatureName

FieldName

PickListTableName

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

74

CodeValue

ValDescription

Bld_Type

0

MOTEL

TYPE

1

MARRIOT

NAME

2

HOLIDAY INN

NAME

3

BED AND BREAKFAST

TYPE


Working with Warehouses PL_State StateName

Desc

Alabama

ALABAMA

Arkansas

ARKANSAS

Colorado

COLORADO

Texas

TEXAS

Florida

FLORIDA


75


76


SECTION 5

Working with Images In GeoMedia Professional, raster images, such as a scanned map sheet, an aerial photograph, or a satellite image, reside in image feature classes. Image feature classes are distinguished from one another based on the coordinate system of the feature class. You can only insert images into an existing feature class when the coordinate systems of the image and the feature class are in agreement. All the images in an image feature class can be represented by a either a single legend entry or multiple legend entries. You can add images to existing feature classes as needed, without the images being displayed, thereby managing system resources more efficiently.

Inserting Images into Warehouses You can insert a raster image into a read-write warehouse and use it as a logo or a backdrop in your GeoWorkspace. The image file is not moved from its location on your hard disk, but the paths to the image and the geometry of the image are saved in the warehouse. To edit or to change the actual image content (image pixels), you must edit the source file. Image linkage and geometries are stored in the database tables (warehouse feature classes) and are managed like any other feature. While multiple images can be represented by a single legend entry, they must be images from the same feature class. Avoid inserting multiple images with the same filename into a single warehouse, even if the images are stored in different folders. The file type, associated metadata, and ancillary information contained in the file determine whether the file must be inserted by interactive placement or, optionally, by georeferenced placement. Before inserting the image(s), you should determine the appropriate warehouse, feature class, and placement method. You should define the image feature class name for the specified image(s). This feature class name is actually the table name in the warehouse in which the specified image(s)‘s information will be placed. A valid image feature class must have a primary key of type autonumber. The Insert > Interactive Image and the Insert > Georeferenced Image commands automatically insert this key into any new image feature classes they create. Image feature classes created with other tools are not usable unless they also have a primary key of type autonumber. Interactive Image placement—Requires you to draw a dynamic rectangle by placing two points in the map window to define the size and the location of the image. With Interactive Image placement, the coordinate system of the inserted image is identical to the GeoWorkspace coordinate system, as is the coordinate system of the target image feature class. The aspect ratio (ratio of width to height) of this rectangle is determined by the number of lines and pixels per line in the image (the image pixels are assumed to be square). It is possible to insert images interactively into an image feature class without displaying the image because the visibility of any feature class is dependent on the legend status of the feature class. Georeferenced Image placement—Inserts geoed images directly into an image feature class in a -specified warehouse. All the selected images must share the same coordinate system. When you select a new georeference mode, you must select the coordinate system file if the mode requires an externally defined coordinate system. This placement method lets you insert one image file or multiple image files into either an existing image feature class or a new


77

Working with Images image feature class. The georeferencing mode is determined by those available for the selected file(s) and the operator‘s choice when multiple modes are available. Some georeferencing modes require you to define the correct coordinate system using external files – either a .dgn or a .csf file can be used. Georeferenced placement uses the following georeference modes:  Automatic (the default) lets the command choose the georeference mode based on the images you select.  GeoTIFF tags - if a well-defined set of GeoTIFF tags is available in the header.  Intergraph GeoTie information  Intergraph header matrix  Other with internal coordinate system  Other with external coordinate system  USGS DOQ  Associated world file In all cases, when the raster image is displayed, the appropriate affine transformation is applied to warp the image into the GeoWorkspace coordinate system. This is only an approximation; rigorous re-projection through samplings of the raster image is not available in GeoMedia 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 selected. This selection is handled automatically by the command during the error checking for the > and >> file selection buttons. The GeoTIFF (http://www.remotesensing.org/geotiff/geotiff.html) Website contains the GeoTIFF specification, details about who is ing GeoTIFF, source code, and sample images. 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 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.

78


Working with Images With the georeferenced placement mode using a world file, you must supply a design file to which the image was originally ed 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.

Using ERDAS IMG Files with Insert Georeferenced Images ®

Most ERDAS IMG files do not have EPSG codes stored in the file to define the coordinate system for GeoMedia to locate the image. So, you may supply an appropriate coordinate system file to load the image. GeoMedia‘s Define Coordinate System File utility can create a .csf file if needed. ERDAS s who create IMG files for GeoMedia may need to change the ways they create the files to avoid this and other GeoMedia raster requirements. ERDAS IMG files can only be loaded by installing the Intergraph ERDAS Image File expansion pack with GeoMedia Professional 6.1.11 or any higher 6.1 minor release. If the expansion pack is installed, the command will display *.img in the Extensions drop-down list on the Insert Georeferenced Images dialog box. The Intergraph ERDAS Image File expansion pack is available from the GeoMedia Professional page. Go to the Security, Government & Infrastructure page at http://.intergraph.com/ to access the GeoMedia Professional page; then go to the s section, Expansion Packs tab to the software.

Before Inserting Images Before inserting images, you may need to prepare files to display subject to the following GeoMedia data requirements:  Some image files have color bands with more than 8 bits per pixel. GeoMedia requires histogram data to display them with the optimal contrast. ERDAS IMG files that contain multibyte data must have a separate histogram file. Intergraph‘s Image Station Raster Utilities (ISRU) product includes a histo utility you can use to create the required histogram file.  Large raster image files should be tiled and overviewed to improve performance. ISRU can be used to do this.  Color image band information is processed in RGB order. Other band orders, such as BGR, display with unexpected colors because the bands are interpreted as RGB.  Color images with more than three bands only have the first three bands displayed in RGB order. This may result in displays with unexpected colors.

Workflows for Inserting Interactive and Georeferenced Images This section contains the workflows for inserting images with the Insert Interactive Image command and the Insert Georeferenced Images command.

To insert an interactive image: 1. Select Insert > Interactive Image.


79

Working with Images 2. In the Image name field, type the name of the image you want to insert, or click Browse to select the image from the standard Open dialog box.

3. From the Warehouse drop-down list, select the read-write warehouse where you want to store the path to the image and other associated attributes. 4. From the Feature class drop-down list, select the feature class to add the image to, or type a new feature class name. , 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.

80


Working with Images To insert georeferenced images: 1. Select Insert > Georeferenced Images.

2. From the Georeference mode drop-down list, select the appropriate mode (Automatic is the default). If your Georeference mode is USGS DOQ, GeoTIFF, Other with internal coordinate system, or GeoTie, no coordinate system file is required; go to Step 4. 3. In the 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). Available extensions are the following: *.tif; *.btf, *.jpg; *.jp2, *.ecw, *.sid, *.bmp, *.cot, *.rlt, *.cit, *.rgb, *.doq, *.bip, and *.bil.

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. 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. 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.


81

Working with Images 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 the “Adding Entries to the Legend” section in the “Working with Map Windows” section.

Images and Coordinate Systems In GeoMedia Professional, each data source has its own coordinate system. This coordinate system is defined in a variety of ways. In the case of GeoMedia feature data in Access, SQL Server, or Oracle databases, the feature class coordinate system is defined when the feature class is created. Data in non-GeoMedia based warehouses, such as ArcView, ARC/INFO, MapInfo, FRAMME, and MGE data, can be imported to GeoMedia feature classes or served directly from the warehouse. These data sources may or may not have their coordinate system explicitly defined. If GeoMedia Professional is unable to determine the coordinate system of a dataset, you must provide this information by associating a coordinate system definition file with the data source. This is the case when serving CAD data that specify an XY coordinate for a feature but do not provide coordinate system, projection, unit, and datum. When importing vector features to a GeoMedia Professional read-write warehouse, the coordinate system file is used for the one-time transformation of the data to the coordinate system of the new feature class. Leaving the vector data in the native warehouse means that GeoMedia 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

82


Working with Images context. This file can be either a MicroStation design file that contains a coordinate system element (.dgn) or a GeoMedia Coordinate System File (.csf).

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

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

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

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


83

Working with Images This command displays selected images from an image feature class in an open warehouse connection in the active map window. You can choose one or more valid image entries (which can be filenames, XML monikers, or both) and display these images using a single legend entry or separate legend entries for each selected image. Alternatively, you can create a query from selected images, to be added to the legend at a later time. The selected images are stored in a query based on the values of their primary key field(s). This query contains a fixed and permanent list of images, referenced by keys. This list is not editable. However, you can use the Queries command to edit the query, but only to edit the query name and description. The image files of the selected filename entries are automatically validated and their associated icons are updated after the display operation. See “Adding Entries to the Legend” in the “Working with Map Windows” section. 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.

To display selected warehouse images in a map window (as a single legend entry, or multiple legend entries), or to group images as a query that can be added to the legend at any time: 1. Select Warehouse > Images. 2. Select the appropriate image record from the Feature class drop-down list, which only displays image feature classes.

All image records of the selected image feature class are displayed in the Images list.

84


Working with Images 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. To update image records: 1. Select Warehouse > Images. 2. Select the appropriate image feature class from the Feature class drop-down list. 3. To update a single image record with the invalid filename icon, select the appropriate record from the Images list; then click Update to open the standard Open file dialog box, from which you choose a valid path and filename. 4. To update a single valid or unknown-state image record or multiple image records (regardless of the icon) from the Images list, select the entry or entries; then click Update to open the standard Browse for Folder dialog box, from which you choose a valid folder.

Once the update is finished and the dialog dismissed, the image entries are updated with the new folder and the warehouse is updated. The Images list is then refreshed so that the appropriate icons are displayed for any updated entries. 5. Click Close.

To delete image records: 1. Select Warehouse > Images. 2. Select the appropriate image feature class from the Feature class drop-down list. 3. Select the image record(s) that you want to delete from the Images list.


85

Working with Images 4. Click Delete. You can also delete an image as any other legend entry by selecting the image name on the legend using the Select by Legend Entry and Delete commands on the Edit menu.

To delete an image feature class with Warehouse > Feature Class Definition: 1. 2. 3. 4.

Select Warehouse > Feature Class Definition. Select the image feature class to delete from the Feature Classes drop-down list. Click Delete. Click Yes to confirm the deletion of the image feature class.

The image feature class is deleted from the warehouse, and any images in that feature class that were displayed are removed from the map window. Notice that the name of the image feature class may still be on the legend. 5. Click Close. 6. Delete the old image feature class entry from the legend.

To validate image records: 1. 2. 3. 4.

Select Warehouse > Images. Select the appropriate image feature class from the Feature class drop-down list. Select the image record filename(s) you want to validate from the Images list. Click Validate.

All files of the selected entries are validated and their associated icons are updated accordingly.

Removing Images from a View and Redisplaying Them Deleting an image feature class or query from the legend removes its images from the view but does not alter the contents of the image feature class in the warehouse. If you remove an image feature class from the legend, the Legend > Add Legend Entries command lets you redisplay the entire contents of the image feature class. When inserting large numbers of images, it may be to your advantage to not add the entire feature class to the legend. This allows the use of a spatial filter to restrict image display as appropriate. If you want to display only selected images from the image feature class, use the Warehouse > Images command as previously described.

To remove an image feature class or query from a view and redisplay it: 1. Select the image feature class or query name on the legend. 2. Press DELETE on the keyboard; then confirm the deletion from the legend and map window by clicking Yes. 3. Select Legend > Add Legend Entries. 4. Select the appropriate categories, queries, reference features, or connections node from the Features treeview to display all feature classes within that group. 5. Select the appropriate image feature class check box from the treeview; then click OK to redisplay the image.

86


Working with Images

Changing the Raster Image Display An image style is of the image style class. As such, it provides display capability for imagery. Raster image data is now ed through the same mechanisms as vector data, for consistency and simplicity. You can change the image display through the image Legend Entry Properties dialog box and the Style Properties dialog box. As with all other style types, you must dismiss the dialog box before you can see the style definition changes in the map window. See the “Working with Styles” section in the “Working with Map Windows” section for more information on styles. You define the following style properties on the Image Style tab of the Style Properties dialog box:

Translucency percentage—The degree to which the image is to be translucent or see-through, with 0% indicating totally opaque and 100% indicating totally transparent. It is applicable to all image types. Contrast—The contrast of the image display on a scale of –100 to 100, applicable to all image types, including 8-bit color index imagery, however, not binary. Brightness—The brightness of the image display on a scale of –100 to 100, applicable to all image types, including 8-bit color index imagery, however, not binary. Invert Image—Indicates whether the image display should be inverted (creates the effect of a negative) , applicable to all image types, including 8-bit color index imagery, however, not binary. Transparent color—A color within the image that is to be treated as transparent (not drawn). This is an actual color value (R,G,B), not a color index or pixel value. It is applicable to all image types except binary. Transparent pixel values—A set of pixel values within the image that are to be treated as transparent (not drawn), applicable only to color index and grayscale images. These are color index or pixel values, not an actual color value (R,G,B). The pixel values are presented as comma (,) and a hyphen (-), separated values from 0-255. Binary foreground color—The color with which the foreground pixels of a binary image are to be displayed, applicable only to binary images. Binary background color—The color, if any, with which the background pixels of a binary image are to be displayed, applicable only to binary images. The background may be made transparent by not specifying a background color.


87

Working with Images 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. You can also use the Advanced tab to change attribute-based symbology. This tab redisplays some of the information from the Image Style tab in a grid format with the Default Value column containing the values from the Image Style tab. The Attribute Based column lets you drive the value of a given property from a field value or from an expression.

To change the raster image display: 1. On the legend, double click the style key of the image feature class you want to change to display the Legend Entry Properties dialog box.

2. Make the appropriate change; then click Apply.

The changes are saved and reflected in the display of the image(s) in the associated map window. OR

88


Working with Images Click Properties to display the Style Properties dialog box.

The first image type associated with the raster legend entry determines which tab is available. 3. On the Image Style tab, change the characteristics of the selected image(s). 4. Optional: On the Advanced tab, change the attribute-based symbology. 5. Click OK to dismiss the dialog box and display the changes.

The changes are saved and reflected in the display of the image(s) in the associated map window.

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


89

Working with Images To create image footprints: 1. Select Analysis > Image Footprints.

2. Select an image feature class, query, category, or reference feature from the Create image footprints for drop-down list.

3. 4. 5. 6. 7. 8. 9.

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. Optional: Change the output Query name and/or optional Description. Optional: Check the Display footprints in map window check box; then optionally change the name in the Map window name field. Optional: Click Style, and change the default style on the Select Style dialog box. Optional: Check the Display labels in map window check box; then optionally change the name in the Map window name field. Optional: Click Style, and change the default style on the Select Style dialog box. Optional: Check the Display results in data window check box; then optionally change the name in the Data window name field. 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.

90


Working with Images

Displaying Selected Images The Display Selected Images command displays images from those features in a select set that have image geometries. Objects in the select set that do not have an image geometry are skipped. This command is designed to be used in conjunction with the Image Footprints command, which creates image footprint polygons of an image feature class or query, although it can also be used in other contexts. The Display Selected Images command loads only those images that have been placed in the select set, whether they have been placed by selection of their footprints in a map window, their rows in a data window, or some other technique. To use this command, which has no graphical interface, you must have a select set, and an active map window. In a typical workflow, you would use Image Footprints to generate footprints (image shapes) for an image feature class. A subset of these footprints is placed into a select set, and the images are then displayed through Display Selected Images. Alternatively, footprints may have been created through the Functional Attributes command, through custom software, provided directly through a data server, and so forth. In another workflow, Display Selected Images may operate without footprints, for example, through image features selected in a data window. This command has no graphical interface. See the previous “Creating Image Footprints” section. See the “Working with Functional Attributes” section in the “Analyzing GeoMedia Professional Data” section. Once all the image geometries in the select set are found, a legend entry is created. If image geometries from multiple feature classes are found in the select set, multiple legend entries are created. The title of each legend entry will be Selected images of <X> where X is the feature class or query from the select set that contains the image geometry. Legend entries for a given feature are reused if they exist. That is, for the existing legend entry, the previous selected images are unloaded and the newly selected images are displayed. If no newly selected images match an existing legend entry, the legend entry 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 the “Defining Queries from Select Sets” section in the “Working with Features” section.

To display selected images: 1. Generate a select set of objects that have image geometries. 2. Make a map window active.


91

Working with Images 3. Select View > Display Selected Images.

92


SECTION 6

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

Controlling the Map Window To the left of a map-window title or in the upper-left corner of a maximized map window is the map-window icon. Clicking this icon displays a menu that allows you to control the map window.

Depending on the current state of the map window, this menu lets you do the following:  Restore a minimized window.  Move, restore, minimize, or maximize the window.


93

Working with Map Windows  Close the map window.  Activate the next map or data window in the stack. 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.

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

94


Working with Map Windows 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:

To change the properties of a map window: 1. Select Window > Map Window Properties.

2. Type a new title in the Map window name field if appropriate.


95

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

Defining Map Window Display Properties View > Display Properties helps you visualize what your map data in the map window will look like when viewed or plotted at a given map scale.

This command lets you define the following properties that affect the way the map graphics are displayed: Display scale-Typically associated with screen displays, display scale is the scale factor with which to view the map data in a map window. This factor is flexible, changing every time you zoom in or out. The current display scale is shown in the GeoWorkspace in the lower-right corner of the Status bar. Nominal map scale-Typically associated with style scaling, the nominal map scale is the scale factor that serves as the base or reference scale. It is referenced when legend entries have their style scaling set to Paper. When defining the style of a feature (for example, 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, th 1:100,000. The text is thus being displayed at 1/20 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).

96


Working with Map Windows Rotation angle-Rotation angle of the map view. When the units are degrees (deg), the values in the drop-down list are: -90, -75, -60, -45, -30, -15, 0, 15, 30, 45, 60, 75, and 90. When the units are not degrees, the values are the preceding degree values converted to the current angular units. Units-Angular units. Changing the units converts the rotation value to the new units. Set style scaling for all legend entries to-Legend entry display in the map window.  View (size is true at any display scale)-The styles on all legend entries are display-scale independent, overwriting the setting of the legend right mouse menu Style Scaling > View command.  Paper (size is true at nominal map scale)-The styles on all legend entries are display-scale dependent, overwriting the legend right mouse menu Style Scaling > Paper command. To achieve a WYSIWYG (What You See Is What You Get) display in the map view, you set the Display scale and Nominal map scale to the intended plot scale, set the Set style scaling for all legend entries to setting to Paper (size is true at nominal map scale), and 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 section and “Defining Map Specifications in the Map Window” and “Previewing the Map in the Map Window” in the “Deg Map Layouts for Printing in the Layout Window” section. 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:


97

Working with Map Windows

Using the Mouse in a Map Window If your mouse has been reconfigured so that the button functions are reversed, you must reverse left and right mouse-button instructions in all the product's documents. In a map window, you use the left mouse button to do the following:  Activate the window.  Create a select set.  Place or edit a map object.  Zoom and pan when the appropriate viewing tool is selected.  Invoke a hypertext link. You use the right mouse button to click in an empty space in the map window and invoke the map-window pop-up menu. This menu contains tools most commonly used in the map window.

Using an IntelliMouse If you have a Microsoft IntelliMouse, you can use it to manipulate the display in your map windows faster and more efficiently. Rolling the IntelliMouse wheel forward causes the view to zoom in at the current cursor location, and rolling the IntelliMouse wheel backward causes the view to zoom out at the current cursor location.

Using Map Viewing Tools The following viewing tools are available only when a map window is active. You exit persistent viewing tools by pressing ESC, by selecting another viewing command, or by selecting the Select Tool. Zoom In

Zoom in on a point you identify with a single mouse click or on an area you define by pressing and holding the left mouse button on one corner of the area, dragging the fence to the diagonally opposite corner, and then releasing the mouse button. A right mouse click exits this command.

Zoom Out

Zoom out on a point you identify with a single mouse click or on an area you define with a dynamic two-point line. A right mouse click exits this command.

Zoom Previous

Return a map window to its previous zoom scale and view extents.

Zoom to Zoom the display scale of the map window to the current nominal map Nominal scale as specified on the Display Properties dialog box. Map Scale Fit All

Fit all displayable objects to the active window.

Fit Select Set

Fit the contents of a select set to the active window.

This command generates expected results only when the selected features are within the defined display scale range of the legend entry.

98


Working with Map Windows Update All

Load unloaded legend entries and refresh the display in all map windows.

This command redraws the graphics in all map windows in which the loading of data in the legend was terminated by the ESC key, beginning at the point in the legend where the interruption occurred. This command does NOT refresh the map window if the legend content has not changed. It does not repaint the window after any view process has been interrupted; this applies only to the interrupting of the loading of legend entry data. Pan

Drag the display in the direction of the cursor. A right mouse click exits this command.

Pan has two modes, dynamic and fast, which are set through the When panning map windows use 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 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 right-most at the bottom of the GeoWorkspace window. To see the display scale change, select it on the Options dialog box, and zoom in or out in the map window.

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


99


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

Defining Map Objects Display Properties The legend right mouse menu Style Scaling > Paper/View commands let you define the display behavior of the style of a feature. The Paper setting is the same as the Paper (size is true at nominal map scale) option on the View > Display Properties dialog box, and the View setting is the same as the View (size is true at any display scale) option. To maximize you workflow, you can select multiple legend entries at a time and change this setting. For global changes (all legend items), you can still use the Display Properties dialog box. The styles of legend entries that are defined as View maintain their size definition when you change the display scale in the map window. Line weight, text size, and symbol size definitions are always rendered at the current display scale. When you zoom in on a linear feature that has its legend entry defined as View, the line remains the same width in the display. The following diagram shows the affect of having the View setting defined for text features at three different display scales. The text remains the same size in all of the displays.

The styles of legend entries that are defined as Paper are display scale dependent, meaning that its display is associated with a particular scale. Line weight, text size, and symbol size are rendered at the nominal map scale defined on the Display Properties dialog box. The display appears larger as you zoom in and smaller as you zoom out.

100


Working with Map Windows The following diagram shows the affect of having the Paper setting defined for text features at three different display scales. The size of the text varies as the window is zoomed out but remains proportionate to the map.

The active Style Scaling setting for any given legend entry appears with a check mark when viewed in the legend right mouse menu. If multiple legend entries are selected, and have a combination of Paper or View settings defined, neither option contains a check mark when viewed in the legend right mouse menu. See “Defining Map Window Display Properties” in this section.

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

To set a scale range for a map object: 1. Select the appropriate legend entry. 2. From the legend right mouse menu, select Display Scale Range.

3. On the Scale Range dialog box, select a predefined range, select minimum and maximum range values from the drop-down lists, or key in minimum and maximum range values between 1 and 1,000,000,000. 4. Click OK.


101


Changing the Locatability of Map Objects A map object must be locatable to be selected with the cursor. Turning off the locatability setting helps when you have several feature classes clustered in one area but only want to select from one feature class. Likewise, it makes no sense to select certain map objects, such as backdrops or logos. You can turn its locatability off to prevent its being selected accidentally. An arrow next to the legend entry indicates that an object is locatable. You control this through the legend right mouse menu Locatable On/Off commands.

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

Looking at Style Collections This section discusses the creation and manipulation of collections of style types. Each individual style type has unique capabilities and interface as described in the previous section. When these style types appear within collections, additional capabilities and interface are available. When looking at the structure of styles, there are basically three types: simple, composite, and collections. Simple structures involve a single definition within the style. Composite structures (Area and Compound) involve multiple predefined definitions within the style. The style below on the left illustrates a simple structure, a Simple Line Style representing a shoreline. The style below on the right illustrates a composite structure; where the predefined structure is the Boundary Styles and Fill Styles. The style is composed of a Simple Line Style for the area boundary and a Hatch Fill Style for the fill, representing an intermittent lake.

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

102


Working with Map Windows 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 -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 may be added by right-clicking on the collection member and then using the New Style and Select Style options as described. Additionally, each existing member may individually be deleted, renamed, replaced, reordered, copied, changed to another style type, or edited. Like any other style type, a style collection has style properties that influence its behavior. In the case of a style collection, these are not visual characteristics in themselves, but are instructions for the order that the collection as a whole is to be drawn. When a style collection is selected in the Style Properties dialog box, the following three options are made available:  Order by feature-This option draws the entire style collection one feature at a time (Feature 1 - Style A, Style B. Feature 2 - Style A, Style B).  Order by style-This option draws all of the features one style at a time within the collection, (Style A - Feature 1, Feature 2, Style B - Feature 1, Feature 2). A common use for this capability is for intersection clearing in the case of a multi-part linear styles. This option is only available for style collections that occur at the root of the style definition.  Select single style component-This option draws one feature at a time, using only a single designated style from the collection (Feature 1, Style B - Feature 2, Style B).

The preceding illustration shows the three distinct drawing orders available, from left to right: Order by feature, Order by style, and Select single index component. As with other style types, you can find and select a style collection on the Styles and Select Style dialog boxes, where you can edit the most commonly used style properties, with a focus on providing group editing of all of the collection. In most cases, these collection controls provide limited editing capabilities because the collection may contain a mixture of different style types within that style class, and those style types may have different properties, as follows: Point Collection Style-Permits manipulation of the color and size of all point styles. Line Collection Style-Permits manipulation of the color and width of a simple line style. Fill Collection Style-Permits manipulation of the fill color and translucency percentage. Area Collection Style-Permits manipulation of the fill color and translucency percentage, and of the boundary color and width of the line style(s) associated with the area boundary. Compound Collection Style-Permits manipulation of the following:  Fill color and translucency percentage.  Boundary/line color and width of the line style(s) associated with the boundary/line.  Point color and size of the point style(s). Text Collection Style-Permits the manipulation of the font, size, font style characteristics (bold, italic, underline), and color.


103

Working with Map Windows Image Style-Collections are not ed for this style class. However, the common controls permit the manipulation of translucency percentage, contrast, and brightness.

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

Creating and Managing Named Styles The Styles command lets you manage named style definitions through the Styles dialog box. With this command, you can perform the following: Create new styles

Rename styles

Change style properties

Preview styles

Delete styles

Organize styles into folders

Set units of measure for style properties

Browse styles, including sorting and filtering by various style characteristics

See corresponding GeoMedia Professional Help topics for more information. You perform these and further management tasks through the three main styles dialog boxes: Styles, Style Properties, and Select Style. There is a great deal of similarity in design and function among these dialog boxes, as well as interplay among them, but they are optimized for different workflows. The most apparent aspects of these three dialog boxes to be shared are the styles list and the style preview. 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:

104


Working with Map Windows 

Details-Styles in a single list by name, with a small sample rendering of the style and additional columns for name, style class, style type, description, and folder.



List-Styles in columns by name, with a small sample rendering of the style.



Icons-Styles in rows by name, with a large sample rendering of the style.

You can filter the list by style class, and sort it by name, style class, style type, description, or folder. You can also select styles and style folders and manipulate them through a right mouse menu, which provides capabilities for you to create new style folders and style definitions, rename, change properties, delete, and cut, copy, paste within the style list. For more information on style classes and style types, see “Style Types” earlier in this section. The style preview provides a flexible visualization capability for a single selected style. It lets you control the background color and magnification of the preview, display the location of the origin for point and text styles, and gives you a choice of sample geometries to use in the preview for linear and area styles.

Working with the Styles Dialog Box The Styles dialog box, displayed by the Legend > Styles command, is designed for creating and managing named style definitions within the GeoWorkspace. You can edit the common properties of a style on this dialog box, or access the Style Properties dialog 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.


105


See the corresponding GeoMedia Professional Help topics for complete information on these two dialog boxes.

To create a named style: 1. 2. 3. OR 1.

Select Legend > Styles. Click New; then select the appropriate style type from the drop-down list. Edit the common properties for the new style as necessary; then click Close.

Click Properties to open the Style Properties dialog box to view and edit the complete set of properties for the new style. 2. After editing the complete properties, click OK to return to the Styles dialog box.

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

To delete a named style: 1. Select Legend > Styles; then select the appropriate style in the styles list. 2. Click Delete from the toolbar, or select Delete from the right mouse menu.

106



Working with the Style Properties Dialog Box The Style Properties dialog box lets you edit existing style definitions. These could be named styles resident in the GeoWorkspace, or current styles associated with legend entries. Your editing of a style definition can be something as simple as adjusting style properties (for example, changing color), or something as powerful as changing the basic style type (for example, change from a symbol to a picture), or changing the style composition (for example, constructing a style collection). You can also replace the style definition with a named style through the Select Style dialog box, which you can access through the Style Properties dialog box.

See the corresponding GeoMedia Professional Help topic for complete information on this dialog box. 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 section. 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 of the style definition.

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.


107

Working with Map Windows 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.

The grid also provides for the definition of a default or fallback value in case the attribute-based assignment fails. You can edit the properties of the style in a generic fashion using standard editors for known style property types such as color, style definition, or one of several enumerated types. All unknown style properties are treated as a key-in field of the appropriate type. The Advanced tab columns are the following: Property-Read-only column alphabetically listing all style properties of the selected style (for example, Size, Color, and Rotation). Hovering over a cell in this column shows the property name and data type (Boolean, Double, Text, and so forth) as a tooltip. Default Value-Read-write column displaying the value of each style property used as the default for displaying the feature. These values correspond directly to the settings available on the main style tab for each style type, and serves as the backup value in the event that an attribute-based assignment fails. Cells in this column either are 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.

108


Working with Map Windows Attribute Based-Empty column by default, but it can be populated with an existing attribute value or an expression in the same grammar used with the Functional Attribute system (available in GeoMedia and GeoMedia Professional). The attribute value or expression is evaluated when used in display, with any non-null result overriding the default property. When you click in this column, a drop-down list appears from which you can select from a list of available attributes or select the Expression option. Selecting Expression from the list displays the Expression dialog box, which allows you to build an expression. Depending on the data type of the selected property, an entry is added to the drop-down list for each available attribute that matches that data type. See the “Working with Functional Attributes" section in the “Analyzing GeoMedia Professional Data” section. The following example demonstrates how to use the Attribute Based definition to specify which point symbol to display. The Symbol Style type has a source property that identifies the symbol file to use. In the case of multi-symbol file types (*.fsm, *.cel, *.svg), the symbol name is appended to this definition. The syntax for this property is ―Source;Name‖. In our example, Source is the Symbol file name, and Name is the Attribute. An expression can be built to construct the appropriate syntax required for the Source property as follows: 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. 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.


109

Working with Map Windows Animation-Animating styles draws attention to critical features or situations as attribute values change. Animation is more than attribute-based symbology; a change in the value of an attribute may simply trigger the animation. Animation draws awareness or emphasizes a particular feature by changing the style of the feature or simply modifying the style properties of a feature through a sequence of values over time. You should only use animation to provide emphasis of a small number of features within a map display; it is not intended for application to a legend entry displaying a large number of features. Misuse may result in poor map display performance. This column displays the animation state button for each row, indicating the current animation state for each style property. The three states are as follows: Enabled but not defined

Enabled and defined

Not enabled

Clicking this button in any of the three states displays the Animation dialog box, which lets you define the animation frame sequence. Each member of the sequence is a frame with a designated style property value (or expression), as well as definition of the timing and nature of the transition to the next frame in the sequence. Note that you cannot define animation for the ―Locatable‖ style property.

Clicking New or Properties on the Animation dialog box displays the Animation Property dialog box, which lets you define the properties for a specific animation frame. The options available vary with the selected style property. In addition, 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 interface and its use.

To edit a style of a legend entry: 1. Double click on the style icon for the legend entry to open the Legend Entry Properties dialog box; then click Properties to open the Style Properties dialog box. OR Right click on the legend entry, and select Legend Entry Properties from the right mouse menu; then click Properties to open the Style Properties dialog box.

110


Working with Map Windows OR Right click on the legend entry and select Style Properties from the right mouse menu to open the Style Properties dialog box. 2. Edit the appropriate style properties. 3. Click OK to save your edits to the style properties.

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

See the corresponding GeoMedia Professional Help topic for complete information on this dialog box. And, for more information on styles, see “Style Types” in this section.


111


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

112


Working with Map Windows If WMS legend entries have been added by the Add WMS Legend Entry command, the Legend Entry Properties dialog box contains the WMS Legend Entry Control that lets you edit the WMS legend entries. You can change the WMS layers to be used, ordering of the layers, SLD URL, styles to be used for the selected layers, and the time parameter.

See the "Adding a WMS Legend Entry" section for information on using this control.

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

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 entry with a Standard definition can be expanded into a Thematic definition. Similarly, a Thematic definition can be collapsed down to a Standard definition.

To change from one type of legend presentation to another: 1. Select a legend entry; then from the right mouse menu, select Legend Entry Properties. OR Double click on a legend entry to display the Legend Entry Properties dialog. 2. On the Legend Entry Properties dialog, select the appropriate style Type. 3. Define the appropriate parameters; then click OK. See the corresponding GeoMedia Professional Help topic for complete information on this dialog box, and see “Creating Thematic Maps” in this section.


113


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

To create your own symbol files: 1. From the Windows Start menu, navigate to GeoMedia Professional > Utilities > Define Symbol File.

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.

114


Working with Map Windows 6. Close the Define Symbol File dialog box. 1 ) To have the correct color definition transferred from your MicroStation cell library to the new GeoMedia symbol file, copy the MicroStation design-file color table used when creating the cells to :\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 :\Program Files\GeoMedia Professional\Program\Symtrans\font.rsc, and update the same location in 'MS Resource files' entry under the [Options] section of :\Program Files\GeoMedia Professional\Program\Symtrans\DGNGT2D.ini.

Looking at Style Classes In general, styles are classified by geometry type. These classes include Point, Line, Area, Compound, Image, Text, and Fill styles. Within each style class, there is a style type definition that provides a further distinction of the characteristics of the given style. Some style classes, such as Image Styles and Text Styles are limited to a single style type. While other style classes, such as Point Styles and Line Styles provide multiple style types to further define the style. For example, Point Style classes Symbol, Font, and Picture style types. Line Style classes Simple and Pattern style types. Generally, most style classes present a simple relationship between the style and the geometry. But in the case of Area and Compound style classes, this relationship requires a composite style definition. Compound features, for example, contain points, lines and areas; all of which are unique style classes. Composite styles are presented in a hierarchical tree view. The following figure shows the Styles dialog box with a corresponding table listing the style classes and below them the style types available for each of those style classes. Composite style types are tagged with an asterisk (*). The first style type listed in each column is the default style type when a new style is created for that style class.


115

Working with Map Windows Style types are always interchangeable within style classes. For example, a symbol style can be used in all of the same places that a picture style can be used.

Style types may also be reused within other style types, even if they are in different style classes. For example:  Point style types are used for point geometry but also for patterns in line and fill types.  Line types are used for linear geometry but also for boundaries in area types and for hatches in fill types.  Area types are used for area geometry but also for frames in text types.

Using Legacy Styles Legacy GeoMedia style (*.gsd) files are still honored when adding legend entries. You can easily bring these files into a GeoWorkspace by drag-and-drop of the style files or folders containing style files from Windows Explorer onto the styles list of the style dialog boxes. The sharing of style definitions through .gsd files is replaced by the library system in GeoMedia version 6.0.

See the “Working with Libraries” section.

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 Style-This point style class provides for the rendering of pictures at point locations. The term picture is used in the Microsoft sense of the word, and encomes a wide range of common Microsoft-ed formats mostly, but not exclusively, of a raster nature. The following style properties exist for a picture style:

116



Bitmap Image (*.bmp)





JPEG File Exchange Format Image (*.jpg,  *.jpe, *.jpeg).



TIFF Document (*.tif, *.tiff).



ICON Image (*.ico).



Windows Metafile Image (*.wmf).



Enhanced Metafile Image (*.emf).

Portable Network Graphics Image (*.png) Graphics Interchange Format Image (*.gif).

All pictures, symbols, and fonts used in point displays are externally referenced. You cannot load a bitmap as an embedded picture to the map view; it is always a file reference. You can define the following picture style parameters: size, transparent color, override color, translucency percentage, rotation, alignment, and offset. Font Style-This point style class provides for the rendering of a character in a specified font at point locations. All font characters are displayed through common Microsoft text-rendering techniques. These techniques do not, however, recognize MicroStation-proprietary font resource files. Thus, such files must be converted into a format understood by GeoMedia Professional 6.0, either a Microsoft-ed font or picture, or a GeoMedia-ed symbol file format, for example a MicroStation cell file. You can define the following font style parameters: font, character, size, color, translucency percentage, halo, rotation, alignment, and offset. Symbol Style-This default point style class provides for the rendering of symbols at point locations. The term symbol indicates any of a number of data formats, produced by GeoMedia Professional and other software products, that contain symbolized vector drawings intended for display at point locations within a larger drawing. The following symbol types are ed:  Predefined symbols-A set of simple, predefined symbols (circles and other shapes) are built into the symbol style. It is not necessary to select an external symbol path. Each predefined symbol has a name by which it is selected. The default symbol style is a small, filled, black circle.  GeoMedia Feature Symbol Files (*.fsm)-This is a multi-symbol type.  MicroStation Cell Files (*.cel)-This is a multi-symbol type. With this type, it is not necessary to convert cell files into .fsm format.  AutoCAD Drawing Files (*.dwg)-This is a single-symbol type. The symbol name is automatically determined from the symbol file name. With this type, it is not necessary to convert drawing files into .fsm format.  Scalable Vector Graphics (SVG) Files (*.svg)-This is an industry standard, multi-symbol type. These symbols may contain embedded text elements within the symbol that can be tied to attributes. This provides a parametric symbol capability in which the symbol text changes based on the attribute value for each feature instance, for example, Interstate Highway Shields.

See the “ed 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, 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:


117


Ignore map rotation-When unchecked, the style will rotate with all other graphics as the map window is rotated. When checked, the style will not rotate, maintaining the rotation angle specified.  Ignore geometry orientation-When unchecked, the style will rotate based on the orientation of the geometry of the point feature. When checked, the style will not rotate, maintaining the rotation angle specified.  Always keep upright-When combining map window rotations and geometry orientations, it is quite possible that some of the styles will display upside down. This option ensures that the style will always read right-side up. Simple Line Style-This line style class provides basic linear rendering capability for linear geometries and area boundaries. You can define the following simple line style parameters: color, translucency percentage, width line type, interior boundary tint (area boundary only), start and end cap (linear only), dash cap, mid-line s, 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



Round anchor

Flat 

Square anchor

Square 

Diamond anchor

Triangle 

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 s that occur at each bend/vertex in a multi-vertex geometry may be set to any of the following: Round, Miter, or Bevel. Pattern Line Style-This line style class provides the ability to render a pattern of point styles along linear geometries, area boundaries, and area hatching. You can define the following simple line style parameters: point style, position of point style along line, insets, and offsets. The point style can be any -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 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.

118


Working with Map Windows Linear patterns such as railroads, that are depicted as a line with a point symbol placed along that line, require two separate entries in the style: a Simple Line Style to define the line's characteristics, and a Pattern Line Style to define the point style's characteristics. Simple Fill Style-This fill style class provides basic fill rendering capability for the interiors of area geometries. You can define the following simple fill style parameters: fill type, color, and translucency percentage. Hatch Fill Style-This fill style class provides hatch display capability for the interiors of area geometries. You can define the following hatch fill style parameters: line style, spacing, and angle. Pattern Fill Style-This fill style class provides pattern display capability for the interiors of area geometries. You can define the following pattern fill style parameters: point style, rotation, spacing, staggering, and fill mode. The point style can be any -defined style that is of the point style class. You may use the full range of point style types (picture style, font style, symbol style, or a collection of any combination of these) to draw the pattern. You can then adjust this property through the common properties interface. You can define the behavior of the symbol display when the symbol encounters the area boundary as follows on the Pattern Fill Style tab of the Style Properties dialog box:  Clip-Causes each patterned point element to be clipped to the boundary of the area.  Inside-Draws each patterned point element only if the entire element falls within the boundary of the area.  Overlap-Allows each patterned point element to be drawn beyond the boundary of the area, if its origin is within the area or on its boundary. Text Style-This text style class provides for the rendering of the text within a graphic text geometry. You can define the following text style parameters: font, font style characteristics (bold, italic, underline), size, color, translucency percentage, frame, halo around the text, alignment, offset, justification, rotation, and line spacing. You can define the display behavior of the text based on different rotation scenarios on the Text Style tab of the Style Properties dialog box:  Ignore map rotation-When unchecked, the text will rotate with all other graphics as the map window is rotated. When checked, the text will not rotate, maintaining the rotation angle specified for the text style.  Ignore geometry orientation-When unchecked, the text will rotate based on the orientation of the feature's geometry. When checked, the text will not rotate, maintaining the rotation angle specified for the text style.  Always keep upright-When combining map window rotations and geometry orientations, it is quite possible that some of the text will display upside down. This option ensures that the text will always read right-side up. Image Style-This image style class provides display capability for imagery. Images participate in the display system exactly as do vectors. As with all other style types, the impact of changes in the style definition are visible in the map window only after you have dismissed the Styles or Style Properties dialog box. You can define the following image style parameters: translucency percentage, contrast, brightness, invert image, transparent color, transparent pixel values, binary foreground color, and binary background color. See the “Changing the Raster Image Display” section in “Working with Images.” Area Style-This area style class provides display capability for the boundary and interior fill of area geometries. As a composite style, the area style has no style properties of its own for drawing. Rather, it provides a hierarchical style composition tree that includes the following style collections:


119


Boundaries-A collection of zero or more line style types to use in drawing the boundary of the geometry.  Fills-A collection of zero or more fill style types to use in drawing the interior of the geometry. Area features also provide the ability to display the following: 

No boundary



Any number of line styles for a boundary



Pattern line styles for a boundary



Any number of fill styles for an interior.

The following is an example of area style usage for interior boundary tints:

Compound Style-This compound style class provides display capability for the point, line, and area geometry of compound geometries. As a composite style, the compound style has no style properties of its own for drawing. Rather, it provides a hierarchical style composition tree that includes the following style collections of:  Points-Zero or more point style types to use in drawing the point geometries.  Lines-Zero or more line style types to use in drawing the line geometries.  Areas-Zero or more area style types to use in drawing the area geometries. Compound features also provide the ability to perform the following:  Display no points, no lines, and/or no areas.  Display any number of point styles, line styles, and areas styles.  Guarantee, through style collections, that points are on top of lines, which are on top of areas.

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

120


Working with Map Windows To create a layout window symbol file: 1. Draw the appropriate elements on a layout sheet using any of the drawing commands located on the Drawing toolbox; then place them in a select set. When creating a symbol using different elements, press CTRL while choosing elements with the Select Tool. 2. From the Drawing toolbox, select Draw > Create Symbol. 3. Click a point on the layout sheet to define the origin of the symbol. 4. On the Save As dialog box, select the directory, and then type an appropriate name.

The document is saved with a .sym extension. To add a layout window symbol file to a map window symbol file: 1. From the Start menu of the Windows taskbar, select All Programs > GeoMedia Professional > Utilities > Define Symbol File. 2. To place a layout window symbols (.sym) into a new or existing file: a. Click Add. b. 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. c. Select the symbols from the list. d. Click Insert. e. Click Close.

The symbol selected is appended to the new library file. 3. Click Save As, and save the opened file in the \symbols folder. 4. Close the Define Symbol File dialog box.

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


121


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

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

122


Working with Map Windows operation on a group item is applied to all of its child legend entries, regardless of whether the child legend entries are selected. Also, when you delete a leaf legend entry on one tab the corresponding legend entry on the other tab is also deleted.

Docking the Legend You can dock the legend in the map window wherever appropriate for your workflow by selecting Position Legend from the map window right mouse menu. This command lets you place the legend in the following three positions within the map window:

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. When the map legend is floating, the caption of the named legend is shown. You can edit this name through the Legend Properties dialog box. The graphic key that accompanies each legend entry may take on your choice of large, medium, or small icons, and may vary in size for point and graphic text features. Legend entry statistics are provided, and statistics are turned on by default for new map windows.

Resizing the Legend When the map legend is floating, you can resize the legend by dragging any corner or any edge of its frame. When the map legend is docked on the left side of the map window, you can resize the legend first by hovering the cursor over the right edge of the legend until the cursor becomes , then by left clicking the mouse, and last by dragging the overlay vertical bar and dropping it to any position of the map window. Similarly, you can resize the right side docked legend by dragging and dropping the overlay vertical bar that originates from the left edge. When dragging the edge of the docked legend, you can only resize the width of the legend because the height of the legend is always same as that of the map window. In addition, you can select Fit Legend from the legend right-mouse menu to resize the legend to the minimal bounding box of the legend entries. The behavior varies with the 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.


123


Looking at Legend Style Keys The following figure illustrated the various default legend entry style keys:

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

Object Type Point feature class Linear feature class Area feature class Text label Compound feature class Image feature class Range thematic display

124


Working with Map Windows Style Key

Object Type Unique-values thematic display

Style keys can also indicate the state of the following legend entries: Style Key

Indicates The data is not loaded. Here are some possible causes:  If you press ESC while the map object is being loaded, the legend entry is created but the data are not loaded.  If you turn off the display of a map object, close the warehouse connection or the GeoWorkspace, and then reopen the connection or the GeoWorkspace, the data are not loaded.





If you replace a legend with a named legend, and the named legend has the display of a map object turned off, the data for that map object is not loaded. If you have checked the Do not load data when opening GeoWorkspace option on the General tab of the Options dialog box (Tools > Options), all legend entries are not loaded. If the map object is set to view by scale and not visible initially; the legend entry is not within its display scale range.

The legend entry is in an invalid state. This could mean the feature table has been deleted or that an attribute has been altered in such a way as to prevent the display of data. Map object is locatable, which means you can use the mouse to click on a map feature and retrieve its attribute information. Map object is displayed by scale, which means the feature will only appear when the map window is displayed within a specific scale range.

Displaying or Hiding the Legend If the legend is not displayed in the map window, you display it in one of the following ways:  From the GeoMedia Professional menu, select View > Legend. A checkmark next to Legend on the menu indicates that the legend display is turned on.  Select Legend from the map window right mouse menu. You hide the legend in one of the following ways:  From the GeoMedia Professional menu, select View, and deselect Legend.  Deselect Legend from the map window right mouse menu.  Double click the legend icon or the X on the legend title bar, if it is displayed.


125


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

Adding Entries to the Legend Add Legend Entries lets you add multiple legend entries that span the set of all connections and queries to the legend of the active map window. You can select the feature class/query from warehouse connections, categorized features, reference features, or queries nodes. The Categories node only appears in the list if categories have been created using the Warehouse > Categories command (available only in GeoMedia Professional and GeoMedia). 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, 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

126


Working with Map Windows 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. The Tools > Options > Map Display tab lets you set the scaling when you add legend entries through the When adding legend entries options. By default adding legend entries use View scaling, but you can also use Paper scaling.

To add entries to the legend: 1. Select Legend > Add Legend Entry.

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.

3. Optional: Check the Group legend entries by category check box. 4. Click OK to add the selected legend entries.

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


127


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

Legend Entry Types You can choose one of three legend entry types: standard, unique value thematic, and range thematic. Standard The Standard legend entry type symbolizes the feature with a style, letting you edit the standard legend entry style. A standard legend entry is a single legend entry with no hierarchy. It has a style, record, and geometry field name all used together to display data. In defining this legend entry style, you can:  Select a named style.  Change the selected style.  Save the current definition as a named style.

128



Change the style properties.

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 two-level hierarchy, where each sub-legend entry represents a thematic class based on a unique value. Each leaf legend entry represents rows with a specific value for the selected attribute. Every leaf legend entry is associated with a style. Typically, the sub-legend entries are formatted using a color scheme. In defining this legend entry style, you can:  Select the unique value attribute.  Retain existing styles.  Save thematic styles.  Loads styles with a matching geometry type.  View unique values, corresponding labels (entry title), styles, and record counts.  Edit styles and labels (entry title) of leaf legend entries.  Add, edit, and remove leaf legend entries (unique values).  Specify the sort order, ascending or descending.


129


Specify an Other entry that contains all unclassified values.

Range Thematic For numeric attributes, the Range Thematic legend entry can analyze the values and group them into classes, with each class having a defined range. These ranges or classes may then be displayed in the map window, each with its own style. For example, county population values may be broken into ranges, and each county may be color-filled based on the range its population is classified as.

130


Working with Map Windows 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.

In defining this legend entry style, you can:  Select an attribute to classify.  Retain existing styles.  Specify the classification method to calculate ranges.  Specify number of ranges to distribute the values in.  View the thematic statistics of the selected feature/attribute.  Specify the sort order, ascending or descending.  Specify the style scheme for the output legend entry, colors and weights.  Save thematic styles.  Loads styles with a matching geometry type.  View ranges (calculated based on input method), corresponding labels (entry title), styles, and record counts.  Edit ranges, styles, and labels (entry title) of leaf legend entries.  Remove or add leaf legend entries (ranges).  Specify an Other entry that contains all unclassified values.


131

Working with Map Windows Setting Range and Unique Value Thematic Parameters The Range and Unique Value Thematic legend entry styles have similar parameters on the Add Thematic Legend Entry dialog box as detailed in the following discussion. For both types, the right side of this dialog box contains Thematic classes and Thematic style parameters, plus corresponding top and bottom grids. 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 ed for range thematics are: byte, short, long, float, currency, and double; the data types ed 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. When you click Classify, the check box for the Other entry in the bottom grid is checked by default. For the range style, clicking Classify displays the Classify dialog box.

This lets you create discrete ranges by the following classification techniques:  Equal Range (the default)-Divides the ranges equally and distributes the values into each range. The records, most likely, are distributed unevenly into equal ranges.  Equal Count-Distributes the same number of records to each range. The range values automatically adjust to distribute the records evenly.  Standard Deviation-Calculates the standard deviation of all values and applies it to the number of ranges. Selecting Equal Range enables the Begin Value and End Value fields in which you type values to limit the ranges created. If the classification type is not Equal Range, these fields are disabled, but the minimum and maximum attribute values are displayed. You also select the number of ranges to create from the Number of ranges drop-down list, which contains numbers from 2-20 to give you a notion of what is considered reasonable, but the number is not limited to these values. The value is defaulted to 4, with a minimum value of 2.

132


Working with Map Windows 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.

See the corresponding topic in GeoMedia Professional Help. For the unique value style, clicking Classify populates the two grids with corresponding styles, values, labels (entry title), and counts based on the selected attribute. The Retain existing styles check box retains the existing styles for the matching thematic classes, when the Classify button is clicked. The unique values are used to determine if the new thematic class is equivalent to the older one. The range values (both the begin and end values) are used to determine if the new thematic class is equivalent to the older one. If the values are equivalent, the older style is retained; otherwise, the new style is applied to the thematic class. Thematic Styles The Thematic styles frame specifies the styles for the leaf legend entries of the range and unique value thematic classes through base style, colors, and size/width. Unlike the Thematic classes, any change to any of the parameters in Thematic styles automatically updates styles corresponding to each of the range and thematic classes, the effect being immediately visible in top grid. The Base style functions as a seed for all style-related activities. Clicking Base style displays the Style Properties dialog box, which lets you modify the current style parameters. For point geometries, the base style defines which point symbol to use. For linear geometries, the base style defines the line's characteristics (line type, caps and s, and so forth). For area geometries, the base style defines the boundary / fill characteristics. For text geometries, the base map defines the font characteristics. If the input legend entry is a range or a unique value legend entry, the base style is obtained from the style property of the root legend entry. When you edit the base style, it is immediately applied to all thematic classes in the top grid, using the current color and size schemes. It is also set as the style for the Other item in the bottom grid. The Assign colors option lets you specify when colors are automatically assigned to the thematic classes in the top grid. Automatic color assignment happens when you click Classify, change the color scheme, or insert a new item into the top grid. In each case, the active settings in the Thematic styles frame are applied. If this option is unchecked, automatic assignment of style information to the thematic classes ignores the colors schemes and defaults to the color of the base style for all thematic classes. When asg 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


133

Working with Map Windows 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 asg 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 asg a minimum/maximum width does not re-apply the base style or active color scheme to the top grid. Only size ramping occurs. Grids The dialog box contains top and bottom grids. The top grid displays a display state, styles, values, labels (entry title), and counts. The bottom grid displays the Other class.

Range Legend Entry Type

134

Unique Value Legend Entry Type


Working with Map Windows Top Grid The columns in the top grid for range and unique values legend entry styles are populated as follows: Check box-Sets the display state of the legend entry in both the legend and the map window. By default when new items are created, this is checked, meaning the items are displayed. Style-Displays a preview of the style for the thematic classes for each row, based on the current settings in the Thematic styles frame. Double clicking the image displays the Select Style dialog box, which lets you edit the style for the corresponding thematic class. Values-These columns vary with the legend entry style. Range displays the Begin Value and End Value columns, and unique value displays the Value column.  Begin Value and End Value-Represent the minimum and maximum values of the selected attribute. These columns let you edit existing ranges, which results in validations and automatic adjustments with adjacent rows to prevent range overlap. The Count column is updated automatically to reflect any change in the range. For new rows, Begin Value has to be specified before the End Value.  Value-Displays the unique values. This column lets you edit an existing row or add a new row, which results in validation for uniqueness among all rows in the same column. After validation, the Count column is updated with the record count corresponding to the new value entered. The Label column is also updated with the new value if the record is new (it is not updated if this is an edit). In addition to impacts to this value, the Other class is updated (record count). Label-Displays the label for the range or unique value legend entry styles sub-legend entry. This editable column can have duplicate values; null values are not allowed. For the range legend entry style, the label is set to [BeginValue] to [EndValue] by default. For the unique value legend entry style, the unique value is set as the label. Count-Displays the count of records associated to a range or unique value legend entry, either as an absolute record count or a percentage, depending on the Show count as percent check box setting. This column is updated automatically when the Begin Value or End Value columns change or the Show count as percent check box setting changes. Manipulating the Top Grid You can insert new rows into the grid even when there are no rows existing in the grid (that is, Classify or Base value have not been clicked). But before adding rows to the top grid, you must select an attribute. The new row is entered at the bottom of the grid as normal, and when the focus shifts to another row, the new row is positioned appropriately in the grid as per the sort order. The number of rows in the top grid and the currently selected row are indicated by the Class: # of # item at the bottom of the top grid. The data is sorted by default in ascending order based on the unique values. You can, however, change the sort order by selecting the following column headers: Begin Value and End Value for range, Value for unique values, and Label and Count for both. The Value, Begin Value, End Value, Label, and Count columns can be all resorted. For ease of use within the grid, you can also display a right mouse menu with the following commands: Ramp Colors-Ramps the colors from top selected item to the bottom selected item. Ramp Size/Width (name in menu is dertermined by geometry type)-Ramps the size or width from the top selected item to the bottom selected item. Select Style-Displays the Select Style dialog box, which lets you select or edit the style. Save Styles-Saves the thematic styles in a style folder, which is saved with the -specified name under the root Styles folder, on the Name Style Folder dialog box.


135

Working with Map Windows Load Styles-Loads styles with a matching geometry type from the specified folder on the Select Style Folder dialog box. Delete-Deletes the selected items. Bottom Grid The bottom grid displays only one row, the Other class, which contains all of the unclassified data and always exists. For the unique value legend entry style, the Value column is not displayed; for the range legend entry style, the Begin Value and End Value columns are not displayed. You cannot add new rows to the bottom grid nor delete the single row. You cannot edit the columns, only check or uncheck the display check box.

To add standard thematic entries to the legend: 1. Select Legend > Add Thematic Legend Entry.

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.

136


Working with Map Windows 7. Optional: Click Properties to redefine the style.

8.

Click OK on the Add Thematic Legend Entry dialog box to add the selected thematic legend entries.

An entry is created and added to the top of the legend, and the active map window reflects the changes. To add range thematic entries to the legend: 1. Select Legend > Add Thematic Legend Entry. 2. Select the feature class or query you want from the connections, queries, categories and reference features in the Input features drop-down list. 3. Select the Range Thematic legend entry Type. 4. From the Thematic classes frame, select the appropriate Attribute for classification from the drop-down list. 5. Click Classify.

6. Optional: Check the Retain existing styles check box. 7. Select the appropriate Classification technique from the drop-down list. If you select Equal Range, type appropriate values in the Begin value and/or End value fields. 8. Select the Number of ranges from the drop-down list. 9. Click Statistics to review the contents of the attribute; then click Close.


137

Working with Map Windows 10. Click OK on the Classify dialog box to populate the grids.

11. In the Thematic styles frame, click Base style to edit the style on the Style Properties dialog box. 12. Check or uncheck the Assign colors check box; then if checked, select a color scheme from the drop-down list. 13. 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. You can also perform both of the Assign colors and Assign sizes/widths operations before clicking Classify. 14. Edit the grid parameters as appropriate. 15. Check or uncheck the Show count as percent check box. 16. Click OK to add the selected thematic legend entries.

An entry is created and added to the top of the legend for each thematic display, and the active map window reflects the changes. To add unique value entries to the legend: 1. Select Legend > Add Thematic Legend Entry. 2. Select the feature class or query you want from the connections, queries, categories and reference features in the Input features drop-down list. 3. Select the Unique Value legend entry Type. 4. From the Thematic classes frame, select the appropriate Attribute for classification from the drop-down list. 5. Click Classify to populate the grids. 6. Optional: Check the Retain existing styles check box. 7. In the Thematic styles frame, click Base style to edit the style on the Select Style dialog box. 8. Check or uncheck the Assign colors check box; then if checked, select a color scheme from the drop-down list. 9. 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. You can also perform both of the Assign colors and Assign sizes/widths operations before clicking Classify. 10. Edit the grid parameters as appropriate. 11. Check or uncheck the Show count as percent check box. 12. Click OK to add the selected thematic legend entries.

138


Working with Map Windows An entry is created and added to the top of the legend for each thematic display, and the active map window reflects the changes.

Adding WMS Legend Entries Web Map Service (WMS) is one of the georeferenced information access services developed as part of the OGC Web Services (OWS) suite. WMS produces maps of georeferenced data. Maps are generally rendered in a pictorial format such as PNG, JPEG, or GIF, or occasionally as vector-based graphical elements in Scalable Vector Graphics (SVG) or Web Computer Graphics Metafile (WebCGM) format. There are two kinds of WMS: basic WMS and Styled Layer Descriptor (SLD) WMS. Basic WMS defines three operations to retrieve maps offered by a service instance: GetCapabilities, GetMap, and GetFeatureInfo. Basic WMS classifies its georeferenced information holdings into Layers and offers a finite number of predefined Styles in which those layers will be displayed. SLD WMS is an extension of the basic WMS to allow -defined symbolization of feature data instead of named Layers and Styles, that is, the features in the map rendered contain the explicit styling information provided by the . The additional operations ed by the SLD WMS in addition to those ed by the basic WMS are: DescribeLayer, GetLegendGraphic, GetStyles, and PutStyles. The Add WMS Legend Entry command lets you display the native WMS hierarchy, as d in the capabilities response of the WMS, and generate legend entry groups from the hierarchical WMS layers in the GeoMedia legend. This command lets you display the WMS layers in a hierarchical manner by your selecting the appropriate WMS layers and the corresponding named styles, as d in the capabilities response for the selected layer. The styles for the selected layer can be basic either WMS or SLD WMS. A capabilities response is the response given by the service for that particular WMS. This response will not be same for all WMS services because it varies from one WMS service to another. A capabilities response contains the following information:  Capabilities ed by the WMS service  Layers present in the service and its hierarchy order  Operations ed by that WMS service  SRS values ed by the service and bbox values for each layer. The Add WMS Legend Entry command issues a single GetMap request for all the selected layers and creates a hierarchical legend entry on the GeoMedia legend. On the Display Order tab of the legend view control, one legend entry is created with the title that matches the title input on the dialog box. On the Groups tab, the same legend entry is also added. Under this legend entry, sub-legend entries are created that depict the hierarchy of the selected layers. You cannot, however, perform any standard legend entry operation on these sub-legend entries. At least one open WMS connection is required in the GeoWorkspace to use this command.


139

Working with Map Windows Selecting Legend > Add WMS Legend Entry displays the command dialog box. Upon selecting the appropriate WMS connection in the GeoWorkspace from the Connection drop-down list, its layers are displayed in the WMS layers treeview, which you can reorder.

Right clicking on a treeview layer displays a right mouse menu from which you can select Show Capabilities to display the Capabilities of dialog box. This read-only dialog box contains the capabilities of the layer: the name, title, abstract, online resources URL, queryable, and time request ed.

For basic WMS, you select the appropriate treeview item(s) as displayed and then select the appropriate style for the selected WMS layer from the list of available styles. For SLD WMS, you first must provide the appropriate SLD URL, which is treated as a style library, to populate the list of available styles and then select the appropriate style before selecting a WMS layer(s). You can accept the default legend entry title or provide a different one. You can also select a date/time value to be used as the time dimension in the GetMap request to WMS by checking the

140


Working with Map Windows Include time parameter check box and then selecting the temporal value from the drop-down list or by selecting the Use current option. Clicking OK then creates the hierarchical legend entry on the GeoMedia legend and displays the image in the map window, as in the following examples. Editing of queries created by this command is not ed at this time. Output in the Legend View Control and Map Window

Zoomed in View of Legend View


141

Working with Map Windows Once created, you can edit a legend entry as needed (change ordering, style, time parameter, or SLD URL). Simply select a legend entry from the Legend Entry Properties command from the right click menu to display the Legend Entry Properties dialog box, edit the legend entry definition using the various controls on the dialog box, and then click OK.

See the “Working with the Style Properties Dialog Box” section for more information on using the Legend Entry Properties dialog box.

Setting Defaults for Feature Class Legend Entries You can set defaults for feature class legend entries through the master legend. The master legend is any specially-designated named legend, as identified through the Legends command. The master legend provides for images, thematic displays, queries, and secondary geometry fields. Also, any given named legend may serve as the master legend, with the legend designated as the master changing from time to time. Because the master legend is explicitly managed by you, no legend entry is ever added to the master legend automatically by the software. To ensure consistent presentation of a data, you should create a master legend entry for it. The master legend serves as a template for map objects on all the legends in a GeoWorkspace. Through the master legend, you can change the default properties for a feature class so that it will display with the same properties each time it is added to any legend in the GeoWorkspace. When a feature class that already has a master legend entry is added to a legend, it is displayed with the properties defined in the master legend. The master legend entries override GeoMedia style files (.gsd). When you add features to the legend, the software first checks if there is a master legend entry for the feature class or query. If there is no entry in the master legend, the GeoMedia style file (.gsd) is used. If there is no match in the GeoMedia style file (.gsd), the legend entry is given a default style.

142


Working with Map Windows 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.

When you open a GeoMedia 5.2 GeoWorkspace in 6.0, the existing master legend is made available in the Legends collection, is given the name Master, and it is designated as the master legend. This ensures that there is no loss from any previously-defined master legend.

Customizing the Legend You can move, resize, and close the legend as you would any standard window. In addition, you can edit, replace, and append the contents of a named legend; rename and delete a named legend; and select a named legend as the master legend or unselect the existing master legend. After customizing a legend, you can save it by giving it a name, and then you can use it in other map windows within the same GeoWorkspace. When you create a new map window, the New Map Window dialog box presents a list of all the named legends in the GeoWorkspace. You can select one of the named legends or an empty one. If you close a map window without naming the legend, the legend of the map window is not saved. In addition to the steps listed below, you can use certain shortcuts to change legend (and thus map-object) properties.  To edit the style of a map object, double click the style key on its legend entry.  To copy a legend entry, drag-and-drop with the CTRL key pressed.  To change a thematic-display attribute, double click the thematic style key.  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 section 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.


143

Working with Map Windows    

Background color. Display of legend entry statistics. You can choose any combination of record count, geometry count, and percentage (for thematic classifications only). Key size of each legend entry (small, medium, or large). Point and text styles fit to the key. You can choose to have point and graphic text styles fit to the size of the graphic key, or have the size of the point or graphic text style dictate the size of the graphic key.

To customize legend entries: 1. From the legend right mouse menu, select Properties.

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

To control the appearance/contents of a named legend: The Properties command lets you manipulate the contents and properties of a named legend. You can add new legend entries, delete existing legend entries, or change the properties and style of existing legend entries.

144


Working with Map Windows 1. Select Legend > Legends.

2. Select the appropriate legend name; then click Properties

3. Change the legend content as appropriate.

To fit the legend: You fit the legend in one of the following ways:  From the GeoMedia Professional menu, select Legend > Fit Legend.  From the Legend right mouse menu, select Fit Legend.


145

Working with Map Windows To turn off the display of legend entries: To gain space on the legend, you can turn off the display of some legend entries without turning off the display of map objects in the map window. The Show Legend Entries command from the legend right mouse menu controls whether the legend entry is visible or hidden on the legend. This dialog box lists all legend entries in a hierarchical display. You can control the display of each item by toggling the check box on and off. A check indicates that the entry is visible.

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.

146



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. 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.

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

To customize the Legend toolbar: 1. 2. 3. 4.

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

Using the Legend Right Mouse Menu You display the legend right mouse (pop-up) menu by clicking the right mouse button with your cursor on a legend entry. You can select multiple legend entries while holding down the CTRL or SHIFT key. The status of the legend entry or entries that you select determines which options are available on the pop-up menu. Some legend entries may be read-only, in which case you may not be able to perform operations such as Display On/Off, Locatable On/Off, Style Properties, and so forth. Option

Does this

Display On/Off

Turns on/off the display of objects in the map window associated with the selected legend entries.

Display by Scale

Displays map objects associated with selected legend entries according to a specified scale range.

Display Scale Range

Displays the Scale Range dialog box to set a scale range for map objects.


147

Working with Map Windows Option

Does this

Locatable On

Toggles locatability of map objects associated with the selected legend entries. When enabled, Locatable On indicates that all map objects associated with selected legend entries are locatable.

Locatable Off

When enabled, Locatable Off indicates that one or more map objects associated with selected legend entries have locatability turned off. When a legend entry has locatability turned off, Locatable Off appears disabled.

Add Subtitle

Adds a subtitle to the selected legend entry.

Hide

Hides selected legend entries on the legend without affecting the display of associated objects in the map window. To display a hidden legend entry, use the Show Legend Entries dialog box.

Show Legend 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 Map Window Tooltip dialog box to edit the tooltip).

Cut, Copy, Delete

Perform standard Windows command functions.

Paste

Pastes the legend entries from the clipboard Into, Before, or After the 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.

148

Legend Entry Properties

Opens the Legend Entry Properties dialog box to set the properties of the selected legend entry.

Fit Legend

Fits the legend to display all entries.

Properties

Opens the Legend Properties dialog box to set the properties of the legend.



Defining Map Window ToolTips The Map Window ToolTip command on the legend right mouse menu lets you define the map window tooltip of a selected legend entry. A map window tooltip displays the information you define for a selected legend entry when you hover the cursor over a feature in the map window, and as a tooltip in the PickQuick interface. 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. See “To select a hidden or overlapped feature” in the “Working with Features” section for information about PickQuick. You can set the map window tooltip on the Thematic Legend (top level) Entry and in doing so set all the thematic legend entries under the top level thematic. You define the map window tooltip through the submenu, which provides you with the following options: None-Removes the map window tooltip definition, if there is one, of the selected legend entry so that no tooltip is displayed for the features when the cursor hovers over them. If no definition exists, None is marked with a dot beside it.

Name-Sets the name of the feature class or query as the map window tooltip. If the format of the tooltip matches that of the query name, Name is marked with a dot beside it.

Attributes-Opens a submenu of attribute names created from the names of the displayable attributes associated with the legend entry. Only attributes whose data type is Text, Memo, number (AutoNumber/Byte/Integer/Long Integer/Single/Double/Currency), Date, GUID, or Boolean are displayed in the submenu. You select the appropriate attribute name to be the map window tooltip. If the format of the tooltip matches that of a selected attribute, when the attributes submenu appears, the attribute found in the tooltip is marked with a dot beside it to note it is the current tooltip content.

Expression-Opens the Map Window Tooltip dialog box from which you edit the map window tooltip. If the tooltip is defined and it is neither the name of the feature class or query nor the name of any displayable attribute, Expression is marked with a dot beside it.


149

Working with Map Windows See the “Working with Functional Attributes” section in the “Analyzing GeoMedia Professional Data” section.

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

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

To create a map window: 1. Select Window > New Map Window.

2. Type a title for the map window in the Window name field. 3. Select a legend for the map window. The legend can be one that has already been named (saved) in the GeoWorkspace, if one exists, or an empty legend. 4. Click OK.

Displaying the North Arrow By default, the north arrow is not displayed. You can toggle the display on and off in the active map window through View > North Arrow. You can display only one north arrow in a map window.

You can click and drag the north arrow anywhere within the map window. The size of the north arrow remains constant regardless of how the scale is changed in the map window. If the azimuth is defined by the north arrow location, the north arrow is intelligent, that is, it updates dynamically when you move it or when you zoom or pan through the window. If the azimuth is -defined, the north arrow does not update dynamically. The direction of the north arrow is determined in the following manner:

150


Working with Map Windows 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.

To change the appearance of the north arrow: You can change the symbol used, size, background color, position, and azimuth of the north arrow. In addition, you can set the north arrow transparency, that is, whether the north arrow background is transparent when the map window is printed. You can print the north arrow without a background so that any items behind the north arrow are visible, or you can print the north arrow so that it masks all the items behind and the background uses the specified background color. The north arrow always masks when displayed in the map window. You can also display a com rose instead of a north arrow. As you make changes in the symbol, north azimuth, and background color, they are displayed in the Preview area. This display is always at a fixed size; it does not reflect changes made in the Size field. 1. With the north arrow displayed in the active map window, select Edit > North Arrow Properties, or right click the north arrow and select Properties from the pop-up menu.

2. To change the north-arrow symbol, browse to select a different one. The product delivers .wmf files for north arrows and com roses in the \GeoMedia Professional\Program folder, but you can also select another one if you have it. To see graphics of all the north arrows and com 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. 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. 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. The north arrow appears in a printed copy exactly as it appears in the map window.


151

Working with Map Windows 6. Select Azimuth at north arrow location to draw the north arrow according to the north azimuth of the north arrow location. OR Select Custom azimuth to define your own azimuth of north, by selecting or , typing the appropriate degree value. 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. 7. 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. 8. Click OK. See the “Inserting North Arrows” section in the “Deg Map Layouts for Printing in the Layout Window” section for information on using north arrows in the layout window.

Displaying the Scale Bar The scale bar shows intervals in ground units to indicate the distance on a map. You toggle the display of the scale bar on and off in the active map window through View > Scale Bar.

The scale bar shows the scale for the window in which it is displayed. You can display only one scale bar in a map window. You can click and drag the scale bar anywhere within the map window. The scale that the scale bar uses is the scale of the map window. The measurement unit of the scale bar is km by default, but you may change that using the Edit > Scale Bar Properties command. The scale bar provides great flexibility for changing its appearance through Scale Bar Properties. You can easily change the scale bar displayed in the active map window by selecting Edit > Scale Bar Properties or right clicking the scale bar and selecting 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 “Deg Map Layouts for Printing in the Layout Window” section for information on using scale bars in the layout window.

152


Working with Map Windows The Style tab lets you define the display characteristics of the scale bar including the type, color, and line widths.

You can choose from the following types of scale bars:

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. The Intervals and Units tab lets you specify information such as the number of intervals, interval length, and ground units represented by the scale bar. You can also define the text, position, and font characters of the units label. If you modify the extents of the map window, the scale bar automatically resizes to indicate the correct scale bar length. The scale bar length and the number of displayed intervals may be shortened or lengthened to maintain a length that is approximately one-fifth the width of the map window. To ensure that information is displayed clearly, the scale bar holds a minimum length.


153

Working with Map Windows 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:

The Labels tab lets you specify the appearance of the scale bar numbers and caption and where they are displayed.

You can choose from the following fixed interval label locations on the Labels tab:

154


Working with Map Windows Every interval

Intervals and first subinterval

Intervals and all subintervals

Intervals and first midpoint

Scale bar ends and zero

The following example shows displayed interval label ticks:

For scale bars in the map window, the unit for this property is defined on the Style Units dialog box accessed by clicking Units on the Styles Definition dialog box toolbar. 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/Areas tool interactively calculates the 2D or 3D linear distance, elevations, and slopes between two or more points or the perimeter and area of a polygon in the map window. For linear measurements, after you enter the first data point, the command begins measuring the distance between that point and the current cursor location. For area measurements, the values are calculated only after you enter two or more points. The measurement values are displayed as always upright, dynamic text labels at the current cursor location (for linear distance and area perimeter), and at the center of the measurement polygon for total planar area. For both linear and area measurements, dynamic lines are drawn in the current highlight color, using a medium-dash linear style. The measurement values and the dynamic line segments are continuously updated with cursor movement. For linear measurements, when you enter a second data 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 text label is then fixed adjacent to the segment at the center location between those two points. The dynamic display resumes between the second data point and the current cursor location. Subsequent data points behave similarly, with the Total field containing the cumulative distance between the first and last data points entered. Additional linear measurement results are displayed in the Elevation delta (the elevation difference between the first and last points entered) field and in the Slope (the slope value calculated using the first and last points entered) field when the Measure in 3D check box is selected to measure the distances in 3D. These fields are also continuously updated with cursor movement. 3D measurement has relevance only when you snap to the points on the geometry feature (with Z values). For area measurements, the result fields are Perimeter (the value of the perimeter of the area polygon, calculated using 2D or 3D distances) and Area (planar) (the total planar area in square units within the polygon, always a planar calculation using 2D points). These values are displayed only after you have entered a second (or subsequent) data point. The chosen measurement interpretation option and its precision are set on the Units and Formats tab of the GeoWorkspace Coordinate System dialog box. The measurement interpretation (True, Projected, or Paper) is displayed in the Interpretation field for both linear


155

Working with Map Windows and area measurement. 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. You can display the distances in paper units by clicking the Units and Formats button to the right of the Interpretation field to display the Define Coordinate System File dialog box. You can then use this dialog box to select the appropriate measurement interpretation, display unit, and display precision. When the Paper (scaled) measurement interpretation is used, the selections (unit and precision) for the Paper Distance unit type apply to the display of distances of the Measure Distance/Area command. If the selected Measurement interpretation is Projected or True, the Distance unit type applies to the measurements. Changes to the unit types through the Measure Distance/Area dialog box do not change the units as defined by the View > GeoWorkspace Coordinate System command. See the "Setting Units and Formats" section in the "Working with Coordinate Systems" section. To find the area of a feature, right click a single area feature that you have selected, and select Select Set Properties from the pop-up menu. The area of the feature is listed on the General tab. When using Oracle and measuring areas of features that contain arcs, GeoMedia reads the three points stored in Oracle to represent the arc and generates a GeoMedia ArcGeometry object from them. Internally, this object consists of a start point, an end point, a radius, a normal vector and a greater than PI flag. The GeoMedia ArcGeometry does not keep track of the original point on the arc that is stored in Oracle (nor does it need to in order to do its job). For feature measurement involving an arc, GeoMedia 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 arcs are considered circular in the X-Y plane. Feature length and area measurements within the Select Set Properties command are always 2-D, so these measurements always use a (stroked) circular arc, regardless of the Z-values for the start and end points of the arc.

To measure distance/area: 1. Select Tools > Measure/Area Distance.

156


Working with Map Windows 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. Optional: Check the Measure in 3D check box to show 3D measurements in the Total, Elevation delta, and Slope fields. 3D measurement has relevance only when you snap to the points on the geometry feature (with Z values). 4. Select the appropriate measuring Method: Linear (the default) or Area. 5. In the map window, click the starting point, and move the mouse to draw a dashed line to the second point. Use snaps during measurement to snap to specific locations. When the cursor nears the edge of the map window, the auto-pan feature automatically activates. 6. 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. Press BACKSPACE to delete a previous point measurement. 7. Right click to clear the measure to start over. 8. Leave the Measure Distance/Area 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 +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


157

Working with Map Windows 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.

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 ing 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.

158


Working with Map Windows The following figure shows angle measurement when a line segment portion of an area feature and a linear feature are selected.

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

Working with the Overview Window Show Overview Window displays a high-level map containing reference polygons that depict the location and coverage of all open map windows in your current session. The overview window thus provides you with a unified view of all open map windows with relevant context of their spatial relationships to each other and their associated data content. In other words, if you have several map windows, the overview window provides the context for each map window. This allows you to quickly select the proper map window to do your work given the geographic area of that map window.


159

Working with Map Windows The following example depicts the spatial location and coverage of three separate map windows:

The display of each map window polygon within the read-only overview window is optional, and the display is automatically updated when the extents of the associated map window are modified. The overview window is resizable and its view stays centered on its data and maintains the current view range whenever its window extents are modified. The map window polygons optionally contain an associated text label displaying the window title. When you first start this command, the overview window is fit to the spatial extents of the background data and the included map window polygons. This -specified background data content provides context for each map window‘s display. The overview window displays background reference features, which are defined by individual legend entries and/or named legend selections, and polygons that represent the extent and location of each open map window. Additionally, the styles of the map window polygons and the background data features default to a standard initial configuration (polygons to solid line, translucent fill, and the background features based on a named legend) through selection of a named legend. The overview window is not linked to standard map view commands. Instead, it has a right-click menu with the basic window navigation (zoom in/out, fit, and pan) and a display option (map window name label), plus links to the Legend and the Select Named Legend dialog boxes, which are used to manage the content and style of the overview window data. The overview window dynamically updates based on the presence of map windows and changes to the display scale in the various map windows. These dynamic updates occur based on the addition of a new map window to the GeoWorkspace and the removal/deletion of a map window from the GeoWorkspace.

160


Working with Map Windows There is only one instance of an overview window within the system at any given time; therefore, it does not placement and editing or analysis capabilities. For ease of use, you can move the overview window outside the GeoMedia GeoWorkspace framework for placement anywhere on the desktop or on a secondary monitor.

To display and manipulate the overview window: 1. With an active map window displayed, select Window > Show Overview Window.

2. Right click to display the right-click menu.

3. Select the appropriate navigation commands to adjust the display. 4. Select Display Map Window Name Label to display the map window name labels associated with each map window polygon.


161

Working with Map Windows 5. Select Legend to display all legends in the overview window in the Legend dialog box, which corresponds to the Legend of the active map window, and then select the appropriate legend to display.

6. Select Select Named Legend to display all named legends in the Select Named Legend dialog box, which corresponds to the Named Legend of the active map window, and then select the appropriate legend to display.

Working with Map Locations The map location commands let you create, display, and manage named locations. Named locations are areas of a map that are of interest to you and to which you have assigned unique names. These commands are as follows:  Name Locations  Display Locations  Locations A named location allows you to quickly display a particular location and is particularly helpful when you work with specific areas on a frequent basis. You can create a named location such that only you can access it, or you can create a named location so that anyone can access it. Once

162


Working with Map Windows locations are named, you can manage them by changing properties, manipulating the display scale, and deleting. You can access these commands from the View menu. You can also access the Locations and the Name Location commands from the Display Location dockable control, which is displayed by the Display Location command.

Naming Locations Name Location lets you name a predefined area of interest that is currently displayed in the map window. You can then quickly return to the view of that location as needed by selecting it from a list without having to use the navigation tools (zoom in, zoom out, zoom previous, and pan) to locate the area on the map. GeoMedia saves the named view information as an XML file. The coordinates of a location are always stored in the geographic coordinate system with the WGS84 geodetic datum and horizontal storage unit of degrees. If necessary, when a new location is created, the command transforms the input point from a GeoWorkspace coordinate system to the geographic coordinate system. When an existing named location is displayed, the command transforms the input point from the geographic coordinate system to the GeoWorkspace coordinate system.

To name a location: 1. Center the map area that you want to name as a specific location. 2. Select View > Name Location, or click the Name Location button Location dockable control.

on the Display

3. Type a unique and meaningful name in the Location name field, or select an existing named location. The maximum number of characters allowable is 255. 4. Click OK to save the new view and dismiss the dialog box. In a 2D view, the tilt value defaults to -90. In a 3D view, the current location, display scale, and camera information are stored.

Displaying Named Locations Display Location lets you display a selected named location in the map window through the Display Location dockable control. Selecting a location switches the view in the map window by centering on the location and zooming to the predefined display scale. The selected location is also added to the history of selected locations. If Zoom Previous is run while a GeoWorkspace is open, nothing will change in the map window when a location is selected. In the 3D Map window, the tilt and direction are also applied. Display Location displays the Display Location dockable control.


163

Working with Map Windows This control lets you select the named location to display, display the Display Location Options dialog box, and start the Locations and the Name Location commands. The Locations and Name Location buttons are not enabled if there is no open warehouse connection.

To display a location: 1. Select View > Display Location.

You can also display a named location through the Display button on the Locations dialog box. 2. Select the appropriate named location from the drop-down list to display the location. If the map view extent changes after you select a named location, the specified location is cleared. For example, if you use a command such as fit, zoom, or pan, this changes the map view extent, and the Display Location control clears the box.

To use the Display Location Options: 1. Select the Display Location Options button dialog box.

to display the Display Location Options

2. Use the Show this number of recent locations history up-and-down arrows to save 0 to 10 recently selected locations. You can disable this feature by setting the value to 0. 3. Click Clear History to clear the history of recently selected locations. 4. The Locations file field contains the location of the XML that specifies the predefined locations. Type the path of a different Location file or click Browse to select the file to load a different set of named locations, to change the value initially shown when the dialog box is displayed, and to clear the recent history. If you change the Locations file and make no other changes on the dialog box, you must click OK to save the change because you will not be notified to do so, and all changes will be lost. 5. Click OK to store the modified settings and to dismiss the Options dialog box, or click Cancel to dismiss the dialog box without saving any changes. If the filename does not exist, a new empty locations file will be created.

164



Managing Named Locations Locations lets you manage a set of locations stored to an XML file. This command lets you do the following:  Display a named location by zooming to it  Change the properties of a named location  Delete named locations

To display a named location by zooming to it: 1. Select View > Locations, or click the Locations button dockable control.

on the Display Locations

2. Select the appropriate location(s), and then click Display. The view of the active map window changes to reflect the map center and display scale of your selected location.

To change the properties of a named location: 1. Select View > Locations, or click the Locations button on the Display Locations dockable control. 2. In the Locations dialog box, select a location, and then click Properties.


165

Working with Map Windows 3. 4. 5. 6.

Type an appropriate unique name, or edit the existing name in the Location name field. Type an appropriate value in the Display scale field. Select a Geographic or a Projection coordinate type. the named locations center point value in the format specified by the Coordinate type option buttons in the read-only Map center coordinate field. Note that the height is not shown. 7. Type or select with the up-and-down arrows in the Rotation field a new rotation value for the selected location. This field contains values in 15-degree increments from -360 to 360 (where 0 is North, and 90 is looking East). 8. Type or select with the up-and-down arrows a new tilt value for the selected location in the Tilt field, which is only displayed if the GeoMedia 3D product is installed on your system. This field contains values in 15-degree increments from -90 to +90, where -90 is looking down at the earth, 0 is looking at the horizon, and +90 is looking straight up. 9. Click OK to save the new properties.

To delete a named location: 1. Select View > Locations, or click the Locations button on the Display Locations dockable control. 2. In the Locations dialog box, select the appropriate location(s), and then click Delete. 3. Click Yes on the confirmation message to delete the named location. Deleting a location from this list does not delete an area from the map.

Displaying External Maps GeoMedia allows you to use external mapping products, such as Microsoft Bing™ or Pictometry Intelligent Images® georeferenced aerial, oblique imagery of related areas. You can use these products in the GeoMedia active map window through the View > External Maps > Bing Maps and Pictometry commands that display the Bing Maps and Pictometry Map external map dockable controls, respectively. The external map window is displayed on top of any other window in the GeoWorkspace (data, layout, or map window). The following examples show the Bing Maps and Pictometry Map controls in separate GeoMedia active map windows:

166



The following example shows the two separate controls in one GeoMedia active map window:


167


Displaying Bing Maps The View > External Maps > Bing Maps command allows you to display and to manipulate the Bing Maps map content and images in GeoMedia. With Bing Maps, you can find a location, get directions (routing), search, and create and share information about specific locations.

Before Using the Command Before you can use Bing Maps, you must perform the following istrative tasks for Bing Maps authentication: Bing Maps Keys A Bing Maps key (Token) file is required to authenticate the application in which the Bing Maps control is used. These keys are authenticated when the Bing Maps control makes any request to the Bing Maps servers. The Bing Maps control has to set the key before sending any request to the Bing Map server; and every time a Bing Maps control request is made, the key that was set is ed to the Bing Maps server for identification and validation. To obtain Bing Maps keys, you have to create a Bing Maps Developer at the Bing Maps s Center https://www.bingmapsportal.com. For further details, visit this Microsoft Web site for Getting a Bing Maps Key http://msdn.microsoft.com/en-us/library/ff428642.aspx. When you select the Bing Maps command, the Bing Maps dockable control is displayed only if a valid Bing Maps key was provided earlier. If no valid Bing Maps key file was provided earlier or if the Bing Maps key provided earlier has expired, the Bing Maps Credentials dialog box is displayed first to allow you to specify a file containing the Bing Maps key.

On this dialog box, you type an appropriate Bing Maps key file filename containing a valid Bing Maps key to be set on the Bing Maps control for authentication purposes, or click Browse to for the location of the appropriate file. Then you click OK to validate the Bing Maps key. Microsoft Bing Maps Licensing and Pricing To use Bing Maps, and the Bird‘s Eye View capability, you must agree to and abide by the Microsoft Bing Maps licensing and pricing . To review these licensing and pricing and for details regarding the Bing Maps keys for enterprise-wide applications, visit this Microsoft Web site for Bing Licensing http://www.microsoft.com/maps/product/licensing.aspx#. Bird‘s Eye View is not available to Public Sector customers within the U.S. and Canada. You should visit the Microsoft End s of Agreement http://www.microsoft.com/maps/assets/docs/.aspx Web site to make sure that you understand the of use for Bing Maps.

168



Using the Command Selecting the Bing Maps command displays the Bing Maps dockable control that contains the Web browser to display the Bing Maps images. At the lower left of the control is the the map navigation tool bar that lets you track BIng Maps, the GeoMedia active map window, or both; and lets you specify control options.

Clicking Track with Bing Maps refreshes the active map window contents to be synchronized with the Bing Maps data. The control also refreshes the active map window with the appropriate zoom scale factor. Clicking Track with active map window refreshes the Bing Maps data to be synchronized with the contents of active map window and with the appropriate zoom scale factor. By selecting the two track buttons, you can synchronize both the Bing Maps data and the active map window contents. Changes to either the active map window or Bing Maps control are reflected in the other. To have a better display match between the Bing Maps content and the active map window content, the GeoWorkspace coordinate system should match the Bing Maps coordinate system. Clicking Options displays the Options dialog box to specify two control options.

Checking Active map view center lets you display the center of the active map window using the specified graphic (of size 16x16 pixels) on the control. After checking, you type or select the name of the associated image file to be displayed on the control. Checking Active map view extent lets you display the extent (in red) of the active map view on the control.

Displaying Pictometry Maps The View > External Maps > Pictometry command allows you to display georeferenced aerial, oblique images in GeoMedia. Using the Pictometry Map dockable control you can choose a particular image locally available or on an NIW (Network Image Warehouse, a server-side application). If images are available on an NIW, you have to provide an appropriate URL.

Before Using this Command Before you can use Pictometry, you must have a valid license file. The Pictometry Map control requires a valid license file before loading an image. You can obtain the license file when you obtain the Pictometry warehouse data from Pictometry (http://www.pictometry.com).


169

Working with Map Windows When you select the Pictometry command, the Pictometry Map dockable control is displayed if a valid license file and a Pictometry image warehouse file of file type *.PIW were provided earlier. If no valid Pictometry license was provided, the Pictometry Licensing dialog box is displayed first to let you to specify a valid license file.

On this dialog box, you type a valid license filename, or click Browse to locate the appropriate file. Then you click OK to accept the license file and to display the image warehouse file. If no image warehouse file is known to the command (or a previously specified one does not exist), the Options dialog box is displayed to let you define the image warehouse file of type *.PIW and specify the options used on the Pictometry Map control.

. You can type the Pictometry image warehouse filename, or click Browse to locate the appropriate file. You must type the http protocol when referring to the image warehouse files that are available on NIW, for example: http://ImageSvr/NIW/New York 2006 Data/ALMADI019014.PIW. Checking Active map view center lets you display the center of the active map window on the Pictometry map. If checked, a red cursor symbol, the plus sign (+), is displayed on the center of the Pictometry Map control, indicating the center of map window. Checking Active map view extent lets you display the extent of a map view. If checked, the map view extent is displayed in red.

Using the Command Selecting the Pictometry command displays the Pictometry Map control and es the map view extent to the Pictometry Map control so that the best image that corresponds to the lat/long values can be loaded. Once the image is loaded, the control optionally displays a bounding rectangle that represents the extent of the map view on the control. If the image file corresponding to the lat/long value is not available, the map is not displayed, and an error message is displayed. When you start Pictometry, if the control loads the image (corresponding to map view center‘s lat/long values) successfully, but fails to get the image corresponding to the directional view that is stored in the Preference set, the control loads the image corresponding to View From South, the default directional view. If the control fails to load the image for this direction also, the appropriate directional view button in the toolbar is depressed corresponding to the direction of the image that is loaded by the control. In subsequent runs, if the control fails to get the image corresponding to the -specified directional view, the image corresponding to the previous state of directional view is retained, and the corresponding directional view button in the toolbar is depressed accordingly. The command displays an appropriate message with the details of the directional view of the loaded image.

170


Working with Map Windows The Pictometry toolbar at the bottom of the Pictometry Map control lets you perform map navigation, measuring, and view manipulation with the following commands:

These commands are from left to right, as follows: Track with Pictometry Map lets you specify whether to track the Pictometry data. If selected, the active map window contents are refreshed to be synchronized with the Pictometry map. Track with active map window lets you specify whether to track the center of the active map window and to load the Pictometry map based on the map view center. If selected, the Pictometry data is refreshed to be synchronized with the contents of active map window. Options displays the Options dialog box to select an image warehouse file of type *.PIW and to specify the options used on the Pictometry Map control. Zoom In, Zoom Out, and Pan let you navigate the displayed image. Measure Distance lets you measure distance. After clicking the command, you select a start point on the Pictometry Map control, drag the cursor along a straight line (which draws a blue line as you move the cursor), and the measurement is displayed dynamically on the Pictometry Map control as a tooltip. Measure Height lets you measure height. After clicking the command, you select a start point on the Pictometry Map control, drag the cursor (which draws a blue line as you move the cursor), and the measurement is displayed dynamically on the Pictometry Map control as a tooltip. You must always start at the ground and measure up, or an incorrect negative value is displayed. Measure Area lets you measure an area in the Pictometry Map control by using one of three modes: parallelogram, freeform, and straight-sided shape. To measure an area by using a parallelogram: 1. Click the Measure Area button.

The letter A appears at the lower right of the cursor crosshair. 2. Select one of the area corners as the start point, press and hold the left mouse button, and then drag the dynamically displayed gray line across one side of the area to the second corner. Do not release the mouse button. 3. Press and hold CTRL, and then drag the cursor along an adjacent side.

The gray outline of a parallelogram appears as you drag the cursor. 4. When the gray parallelogram surrounds the area you are measuring, release both CTRL and the mouse button.

The gray outline turns blue and the area value is displayed as a tooltip. To measure an area by using a freeform shape: 1. Click the Measure Area button.

The letter A appears at the lower right of the cursor crosshair 2. To define the shape, you can draw any combination of straight lines, freeform lines, and corners (vertices) as appropriate, but the area value will not be accurate if you cross over the path. Select the shape start point, and then trace the outline of the area you want to measure using the following:  For a straight line, press and hold the mouse button, and then drag the cursor to draw the straight line part of the shape.


171

Working with Map Windows  

For a freeform line, press and hold ALT while dragging the cursor to draw the freeform part of the shape. For a corner (vertex), release ALT, press and release the V key, press and hold ALT, and then continue tracing the outline in the new direction with either a straight or a freeform line.

A gray line is drawn as you trace the outline of the shape. 3. After drawing the complete outline of the shape, release the mouse button.

The shape is automatically completed in a blue line, even if you release the button before returning to the start point, and the area value is displayed as a tooltip. To measure an area using a straight-sided shape: 1. Click the Measure Area button.

The letter A appears at the lower right of the cursor crosshair. 2. Select one of the corners of the shape as the start point, press and hold the left mouse button, and then drag the dynamically displayed gray line across one side of the shape to the second corner. Do not release the mouse button. 3. Press and release the V key, to create a corner (vertex), and then drag the cursor to the next corner. 4. Repeat Step 3 for the next corner. 5. After drawing the whole shape, release the cursor.

The shape is automatically completed in a blue line, even if you release the button before returning to the start point, and the area value is displayed as a tooltip. View Commands For the view commands, the Pictometry Map control loads the best image corresponding to the appropriate view direction and to the preserved navigation direction. The state is preserved even when there is a change in the map view extent. Ortho View lets you change the directional view to Ortho. View From North, View From South (default view-from direction), View From East, and View From West let you change the directional view, as if you are viewing the image from each of those directions.

Workflows for Using Bing Maps and Pictometry Maps You can use the following workflows with the Bing Maps and Pictometry Map external map dockable controls.

Displaying the Active GeoMedia Map Window in the External Map Controls 1. Connect to a valid GeoMedia data source, and then display an appropriate feature class in the GeoMedia active map window. 2. Display the Bing Maps control. The Bing Maps control is displayed based on the extent of the active map window. By default, the active map window and the Bing Maps control are synchronized, and the imagery is displayed at the predefined zoom level. OR Display the Pictometry Map control. (You must first enter the folder or the network location of the Pictometry files.)

172


Working with Map Windows The Pictometry Map control is displayed based on the extent of the active map window. By default, the active map window and the Pictometry Map control are synchronized. An error message is displayed if there is no Pictometry data for the requested area.

Tracking the GeoMedia Active Map Window in the External Map Controls 1. Display an external map control and a GeoMedia active map window. 2. Select the option to track with the active map window. When the view is changed in the active map window, the view is also changed in the external map control. The tracking remains selected until you manually turn it off.

Tracking with the External Map Controls 1. Display an external map control and a GeoMedia active map window. 2. Select the option to track with the external map control. When the view is changed in the external map control, it is also changed in the active map window. The tracking remains selected until you manually turn it off.

Manually Synchronizing External Map Controls to a GeoMedia Active Map Window 1. Display an external map control and a GeoMedia active map window. By default, the synchronize option is enabled. 2. Turn off both the options to track, and then move in the active map window. 3. When you reach the appropriate location, turn on the option to track with the active map window.

Manually Synchronizing the GeoMedia Active Map Window to External Map Controls 1. Display an external map control and a GeoMedia active map window. An external map control and an active map window are displayed. By default, the synchronize option is enabled. 2. Turn off the synchronize option on the external map control, and then move in the external map control. 3. When you reach the appropriate location, turn on the synchronize option and the option to track with the external map control.

Displaying the Extent of the GeoMedia Active Map Window in the External Map Controls 1. Display an external map control and a GeoMedia active map window. 2. Turn on the display of the extent of the active map window. The extent of the active map window is identified in the external map control by an outline of the extent.


173


Displaying the GeoMedia Active Map Window "Window Center" Graphic in the External Map External Map Controls 1. Display an external map control and a GeoMedia active map window. 2. Turn on the display of the window center graphic in the external map control. The center of the active map window is identified in the external map control by a cross hair (by default) or a -selected graphic.

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

To display CAD files: 1. Select Tools > Display CAD Files.

174



2. On the General tab, select the CAD type from the drop-down list. 3. In the Folder field, type the complete path of the folder containing the CAD files, or use Browse to locate the folder. 4. From the Available files list, select one or more files you want to display. 5. 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. 6. 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. 7. 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. 8. Optional: In the Connection name field, change the default connection name. 9. 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. 10. 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. 11. 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. 12. Optional: Check/uncheck the Display with native symbology check box to specify whether or not to display the features with native symbology. 13. Click OK.

The software creates a new CAD server schema file, a CAD server connection with that file, and feature classes based on the options set on the Advanced tab; and then (depending on your selection) displays the features on the specified levels/layers in the active map window based on the options set on the Advanced tab. See the “Connecting to a CAD Warehouse” section in the “Working with Warehouses” section and the Define CAD Server Schema File utility's online Help.


175


Publishing Map Window Data This section discusses two View menu commands, Configure KML Publishing and Publish Map, that work together to configure and publish map window content.

Configuring KML Publishing Configure KML Publishing lets you configure the behavior of the Publish Map command for KML output to be other than the default configuration. You can configure the following:  Placemark names in the output KML file. This can either be the map window tooltip, any attribute of the legend entry, or an expression.  Publish the legend entry attributes or not. This command does not image and text features. Using this command is optional because there is a default configuration that is used if you never run this command. Use this command before using the Publish Map command for its settings to take effect.

To configure KLM publishing: 1. Select File > Publish > Configure KML Publishing. If the command is not listed in the noted path, use Tools > Customize to add the command to the menus.

2. In the Legend entries treeview, select the legend entry for publishing. The treeview lists all display entries of the legend associated with the active map window – except those of type Image and Text. 3. Specify the option for the placemark names (in the output KML file) for the selected legend entry from the Get placemark names from drop-down list. 4. Optional: Check the Publish attributes check box to publish the attribute data for the selected legend entry. If the check box is checked, all the attribute values are also published to the output KML file, along with the geometry data displayed in the map window. 5. Click OK.

Publishing Map Window Data Publish Map lets you publish map window data to a KML format. The published data is based on the the data that is within the visible extent of the map window. Data that is outside the current map window is not published. Also, data that is not visible in the map window because of the display scale range of the legend entry is not published.

To publish map window data: 1. Select File > Publish > Publish Map.

176


Working with Map Windows If the command is not listed in the noted path, use Tools > Customize to add the command to the menus.

2. In the Target format drop-down list, select the format to which the data is to be published from the drop-down list of available formats. 3. Enter the full path of the output file to be published in the Publish to text box. The default entry is GeoMedia GeoWorkspaces folder>\<mapwindow name>. . You can edit the default path, type a new path, or click Browse to open a dialog box that lets you find and specify an output file. 4. Click to check the Display in target application check box and to open the default application associated with the file extension (for example, Google Earth for a .kml file). 5. Click OK to publish the data to the specified output file and to display the published data.

Getting WMS Feature Information WMS Get Feature Information lets you see the set of attributes that are associated with a particular geographic location for a locatable, displayable, and queryable legend entry or entries originating from a WMS connection in the active map window. Before using this command, you need an open WMS connection and at least one legend entry (that is queryable) from that connection displayed in the active map window. The WMS Get Feature Info dialog box consists of three sectionS for easy use.  At the top are two read-only fields containing the connection name for the legend entry for which the feature information is displayed, and the legend entry name and the name of the WMS layer for which the feature information is displayed for that legend entry.  In the middle is the browser that shows the command's response from the WMS service for the respective legend entries, either success or failure. There are various navigations buttons below the respond display that let you move between the command responses of different legend entries in the browser.  At the bottom of the dialog box are the following controls:  Request layers by connection check box - If unchecked (the default), one request per legend entry is generated. If checked, all queryable legend entries originating from a WMS connection that are locatable and visible in the active map window are grouped by their connection. Only one request per connection is generated.  Point color - Selects the color of the selected point on the map. The default color is red with the point shown as a filled circle.  Point size - Selects the point size from a drop-down list of predefined sizes ranging from 3 to 25 pts. The default selected value is 8 pts.  ed formats - Selects the appropriate output format from the drop-down list. The list contains all the formats that the selected connection s. By default, the first item in the drop-down list is selected.  XML style sheet - Optionally selects an XSL (XML style sheet) file or browses to find one using the Browse button. The XSL file is used to transform the output only if the output


177






format is in XML format; thus, you must select an XML format from the ed formats drop-down list. The XSL file controls the appearance of the XML data display in the dialog box browser. By selecting an appropriate style sheet, you can transform and format the XML data so that its presentation meets your requirements. Select Location - Selects another location on the active map window. Once clicked, the control returns to the dialog box showing the command response for the selected point. The previously selected point is cleared from the map window. Close - Dismisses the dialog box, and clears the previously selected points in the map window.

To get WMS feature information: 1. Select View > WMS Get Feature Info. If the command is not listed in the noted path, use Tools > Customize to add the command to the menus. 2. Click the appropriate location on the WMS image in the active map window to retrieve the attribute information.

The point is highlighted in the map window and the response from the WMS server is shown in the WMS Get Feature Info dialog box. The connection name and legend entry/layer are shown in the dialog box. 3. Use the left and right arrow buttons on the dialog box to scroll between the information responses of different legend entries. 4. Optional: Check the Request layers by connection check box to make all queryable legend entries that are locatable and visible in the active map window be grouped by their connection. Only one request per connection is generated.

178


Working with Map Windows 5. 6. 7. 8.

Click Point color to change the color of the point in the map window from the default color. Click the drop-down list to change the Point size. Select the appropriate output format from the ed formats drop-down list. Optional: Select an XML style sheet (XSL file) to transform the output for the XML output format.

9. Click Select Location to hide the dialog box and let you select another point location in the active map window. 10. Click Close to exit the dialog box and command.


179


180


SECTION 7

Working with Data Windows Each data window contains the nongraphic attributes of a single feature class or query. This equates to a feature table, with each column representing an attribute and each row representing an instance-a feature-of the feature class. The data in each cell is called a value or attribute value. Data windows display area, linear, point, image, compound, graphics text, and nongraphic feature classes, but do not display geometry or spatial index key attributes. In a read-write warehouse, you can review and edit the features and values in a data window, and any changes you make will be reflected in the map window. So, if you delete a row in a data window, the corresponding feature is also deleted from the map. You can use the layout window command Insert Data Table to display selected portions of a data window in the layout window in a customized style. See the “Inserting a Data Table” section in the “Deg Map Layouts for Printing in the Layout Window” section. The data window displays descriptions for attributes with PickLists defined. For editing such an attribute, a drop-down list box is displayed in the cell. This list contains all the available descriptions for the attribute values as well as a blank entry (available only if the attribute is not required). You can insert a value of NULL for this attribute by selecting the blank value. You can edit an attribute only by selecting a description from the list.


181

Working with Data Windows

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

To open a data window: 1. Select Window > New Data Window.

2. Type a title for the data window in the Window name field. 3. Click the plus sign next to the warehouse or query folder that contains the feature class you want to display in the data window. If you select a query that has not been run, the software runs the query and displays the results in the data window. If you select a query that has been run, the existing results are displayed in the data window. 4. Click OK.

The Data menu replaces the Legend menu.

182



Controlling the Data Window To the left of a data-window title or in the upper-left corner of a maximized data window is the data-window icon.

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

To change the title of a data window: 1. Select Window > Data Window Properties.

2. On the Data Window Properties dialog box, type a new title in the Data window name field. 3. Click OK.

Using the Mouse in a Data Window If your mouse has been reconfigured so that the button functions are reversed, you must reverse left and right mouse-button instructions in all the product‘s documents. In a data window, you use the left mouse button to do the following:  Activate the window.  Place the cursor.  Create a select set.  Select a table, row, column, or cell. You use the right mouse button to open the data-window pop-up menu. This menu contains tools commonly used in the data window.


183


Using an IntelliMouse If you have a Microsoft IntelliMouse, you can use it to manipulate the display in your data windows faster and more efficiently. Rolling the IntelliMouse wheel forward scrolls up at the cursor location. Rolling the IntelliMouse wheel backward scrolls down at the cursor location.

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

 

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

To show columns in the table: 1. Select Data > Show Columns.

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.

184


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

To promote rows in the table: 1. Click the row selector(s) of the rows you want to promote to the top of the table. 2. Select Data > Promote Columns.

When multiple rows are promoted, they are displayed at the top, but they retain their original order in the table. To sort rows in the table: 1. Click the header of the column by which you want the rows sorted. 2. To sort rows in ascending order, select Data > Sort Ascending. 3. To sort rows in descending order, select Data > Sort Descending.

The order of the displayed data is changed in the data window only; the order of the rows in the warehouse remains unchanged. To display column statistics: 1. Click the header of the column for which you want statistics. The attribute must be numeric. 2. Select Data > Column Statistics.


185

Working with Data Windows To change the contents of the active data window: 1. Select Data > Change Contents.

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

Editing Cells in the Data Window When you edit a cell or field in the data window, you are changing the value of an attribute of the affected feature. The software uses standard Windows editing tools and the Clipboard to allow you to cut, copy, and paste text in the data window. These actions do not affect hidden cells or cells containing hypertext. You can also use the Clipboard to copy features in the data window, but associated graphics are not copied. Edit > Cut deletes selected cell values. You cannot cut cells containing the primary key or other required values. Edit > Copy copies selected multiple cells, columns, and rows to the Clipboard as text. For example, you can copy a data view into an Excel spreadsheet. You can select cells directly as a range of one or more cells or indirectly by selecting rows or columns, which you can select in various ways including their buttons on the data window, the Select Tool in the map window, Select by Legend Entry, and so forth. This command is enabled when you select one or several cells, rows, or columns in the data window. Both the Cut and Copy commands let you copy data window column headers to the clipboard. You set this option through the Copy data window column headers to clipboard check box on the General tab of the Options dialog box (Tools > Options). The default (unchecked) is to not copy the headers. If you are cutting or copying a single cell, the copy header setting is ignored and the headers are not included. Also, if you have copied data to the clipboard with column headers, the headers are removed before you paste the cell data back into the data window. Edit > Paste copies data from the Clipboard to the selected cell(s). When you select a single cell, the data on the Clipboard is pasted to the right and down from the selected cell, replacing the selected cell. When you select a contiguous block

186


Working with Data Windows of cells, the data on the Clipboard replaces each selected cell with the corresponding entry on the Clipboard. Paste will not work in the following circumstances:  If the shape you want to paste does not match exactly the shape of the selected cell(s), except when pasting to one cell.  If pasting to the right and down would exceed the number of columns in the data window.  If pasting would create null values for required cells.  If the primary key column is not displayed.  If pasting would require an invalid data conversion, such as trying to paste a text string containing letters into a numeric field.  If pasting would require duplicate values for the primary key field or any other fields requiring unique values.  In pasting into the last row, the software tries to paste all cells from the Clipboard. If you have selected multiple cells in the last row, the shapes must match exactly. If you have selected a single cell, cells are pasted to the right of the selected cell, but not down. If the paste would populate required fields and create a unique primary key, the paste creates new features in the database corresponding to each row from the Clipboard. Pasting does not occur if the paste would not populate the required fields, or if the paste would create duplicate primary keys. You can use Edit > Undo to undo changes made as in standard Microsoft Office products. You cannot use Undo following a cut or paste operation.

Taking a Snapshot of the Data Window You can copy an image of the active data window to the Clipboard by selecting the Snapshot tool from the GeoMedia Edit menu or from the data-window pop-up menu. Hidden columns and cells containing hypertext are not copied.

You can paste the snapshot into any application that s OLE, such as Word, MSPaint, or an HTML Web page.


187


188


SECTION 8

Working with Features A feature is represented in a map window by geometry and is further defined by nongraphic attributes in the database. The values of these nongraphic attributes can be viewed as cells in the data window view on the non-spatial data of the feature. For example, a parcel of land-Parcel 126-A-is represented graphically in the map window by area geometry. The area geometry attributes for Parcel 126-A are part of a single row in the Parcels table. The Parcels table contains information about all the of the Parcels feature class. Parcel 126-A is one of 15 of this feature class. The Parcels table, therefore, contains 15 rows, one for each parcel. Among the nongraphic attributes of Parcel 126-A are its identification number (126A), the name of its owner (P. Brown), and its assessed value ($10,000). Each of these attributes is a column in the Parcels table. So, the Parcels table has at least the following three columns: ID, OWNER, and ASSESSED_VALUE. 126A, P. Brown, and $10,000 are values (or cells) in the ID, OWNER, and ASSESSED_VALUE columns of the row containing the geometry for the Parcel 126-A geometry. In a read-write warehouse, you can create a new feature class, delete a feature class, and edit a feature class definition. You can edit a feature class in the following ways:  By adding attributes (columns)  By removing attributes  By changing attributes In a read-write warehouse, you can also manage feature data in the following ways:  By changing attribute values (cells)  By adding or deleting features (rows) Changes to data in a read-write warehouse are automatically saved as soon as you make them.

Understanding Geometry Types Geometry refers to the graphic representation of a feature in the map window. Features are represented by the following geometry types: 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.


189

Working with 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. When a discontiguous area is placed so that it completely encloses a second discontiguous area, then the second discontiguous area becomes a hole inside the area being placed. When the hole completely encloses a third discontiguous area, the third discontiguous area becomes an island. You can create a hole in an area geometry by adding a second area geometry that falls entirely inside the boundary of the first area geometry. You can create an island inside the hole by adding a third area geometry that falls entirely inside the boundary of the second area geometry.

Working with Feature Classes In GeoMedia Professional, you can create a feature class from an active map window or data window, and only in an open read-write Access warehouse. When you add a feature to a feature class, you have the option of placing geometry. A feature does not need geometry to exist, although most features do have geometry. The software allows you to create feature classes in various ways:  From scratch  By copying some of the information from an existing feature class into a new feature class in the same warehouse  By importing data  By outputting to feature classes  By attaching an external data source

Coordinate Systems When creating a feature class through the Feature Class Definition command, you select a coordinate system to be assigned to the primary geometry field of the feature class from the list of available warehouse coordinate systems. Upon starting this command, a coordinate system is pre-selected on the General tab of New/Edit/Copy - 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.

190


Working with Features 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 , 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. 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 - 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


191

Working with Features 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.

It is possible to hide the primary key column(s) from Feature Class Definition by setting their Displayable flag to No in GeoMedia's metadata tables. Feature Class Definition will disable the Set Primary Key button if it determines there are hidden primary key fields. If the primary key fields are not hidden, the Set Primary Key button is enabled for Edit mode. The ODBC Tabular Data Server allows you to create a connection to any nongraphic table in an ODBC-compliant data source. Thus, you can access additional data stores containing tabular-only data, such as coordinate locations, addresses, and additional attribute information. In addition, you can attach one or more tabular-only feature classes from the following external data sources with the Feature Definition command: a text file, an Excel worksheet, or an Xbase database. You can, however, only attach an external data source to a read-write Access warehouse connection. You can view and handle the resulting table(s) in the target read-write connection similarly to other tables except that the feature class is read-only. For example, you can edit the name, description, and data source name of the attached table and copy an attached table. When you copy an attached table, the software creates a local table without data. This new, empty table then serves as a template into which you can add data. The software also allows you to easily to review the general and attribute feature class properties or an attached table definition, to delete a feature class, and to detach an attached table. You should use the Feature Class Definition command to add or to modify features in an Access warehouse. Using Microsoft Access to modify features in a GeoMedia Access warehouse can result in the improper operation of the feature class or corruption of the warehouse. You should never delete or modify the following tables with Microsoft Access: 

GcoordSystemTable



INGRFeatures



Gmodifications



INGRGeometryProperties



GmodifiedTables



INGRAttributeProperties



INGRSQLOperatorsTable



INGRFieldLookup

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.

192


Working with Features ABS

ALL

AND

ANY

ASC

AVG

BETWEEN

BY

COMMIT

COUNT

DATE

DELETE

DESC

DISTINCT

EXISTS

FLOAT

FROM

GROUP

HAVING

ININSERT

INTO

IS

LIKE

MAX

MIN

NOT

NULL

ON

OR

ORDER

ROLLBACK

SELECT

SET

SOME

SUM

TIME

TIMESTAMP

UNION

UPDATE

VALUES

WHERE WITH TO_DATE TO_CHAR TO_NUMBER See “Connecting to an ODBC Tabular Warehouse” in “Working with Warehouses” and the “Working with Feature Classes” topic in GeoMedia Professional Help and the “Defining Attribute-Filter Queries” in the “Analyzing GeoMedia Professional Data" section.

To create a feature class from scratch: 1. Select Warehouse > Feature Class Definition.

This dialog box is resizable for better viewing of long query names.


193

Working with Features 2. Select the connection to the read-write warehouse where you want to store the new feature class; then click New.

3. On the General tab of the New - dialog box, type a name for the feature class. The feature class name must be unique within a warehouse. 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. 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 To review and/or edit the coordinate system properties, click Properties; then make the appropriate changes on the Coordinate Systems Properties dialog box.

194


Working with Features 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 - 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.


195

Working with Features 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 ed in Feature Class Definition. 13. Optional: Type a brief description of the attribute in the Description cell of each attribute. 14. Click OK. 15. Note the new feature class on the Feature Class Definition dialog box, and close the dialog box.

To add, change, and delete attributes: 1. 2. 3. 4. 5. 6. 7. 8. 9.

You can change the geometry type of a feature class only if the feature class is empty. Select Warehouse > Feature Class Definition. On the Feature Class Definition dialog box, select the connection to the warehouse that contains the feature class you want to edit. Select the feature class, and click Edit. On the Edit - dialog box, click the Attribute tab. To add an attribute, enter the attribute name, data type, and description in the bottom row, and set a primary key. To change an attribute, click the cell you want to change, and make the changes. To delete an attribute, select the attribute row, and press DELETE. Click OK to update the feature class. Close the Feature Class Definition dialog box.

Editing an existing Oracle feature class definition is an Oracle istrative task and is, therefore, not allowed in the GeoMedia Professional Feature Class Definition tool.

Outputting Feature Data to Warehouses You can output feature data in any GeoMedia Professional-ed format to a warehouse with the Output to Feature Classes command. You must have at least one read-write open connection to use this command. Output to Feature Classes lets you perform the following:  Output single and multiple feature classes, queries, categories, and reference features  Output selected fields from a feature class, query, category, or reference feature  Control output, key, and autonumber modes  Review the coordinate system of the primary geometry of the source and target feature classes

196


Working with Features  Set the -defined coordinate system for geometry of the new target feature classes In addition, this command lets you create feature classes from existing feature classes or queries. You should bear in mind that features are static and are stored in the database; in contrast, queries are dynamic and are not stored in the database. Output to Feature Classes lets you output a feature class from a connection back into itself provided the target table name does not conflict with existing table names. However, the command does not allow append, force append, update, or append-and-update operations back into the same feature class.

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


197

Working with Features

Using the Advanced Tab The Advanced tab contains parameters in the Output settings grid as described in this section. Rows are automatically added to this grid as features are selected in the feature treeview on the General tab, and the rows are populated in the order: categories, queries, reference features, and connections.

The read-only Source column is populated with the folder/path of the features selected in the treeview. The read-only Features to Output column 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 the output mode set to New, while all others are processed with the 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.  New-New data.  Append (default)-Appends new records by doing a primary key comparison. New key values are added; existing key values are skipped.  Force Append-Appends all records and re-sequences the primary key.  Append and Update-Appends new records and updates existing records based on primary key value.  Update-Only updates existing records by comparing primary key values.

198


Working with Features The Key Mode column lets you set one of the following key modes (only if the target feature class does not exist in the target warehouse, that is, if the output mode is New).  New Key-Creates a new primary key column.  Preserve Key-Uses existing key column. The default is 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 Mode column lets you set one of the following autonumber modes (only if the target feature class does not exist in the target warehouse, that is, if the output mode is New):  Preserve Definition-Preserves the primary key column definition but not the data.  Preserve Values- Preserves the existing data in the primary key column.  Preserve Definition and Value (default)- Preserves key definition and data values. These modes are available on the right mouse menu after you select this column. See the table in the next section for the default column values. 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.

Advanced Tab Default Column Values If the target feature class name you supply on the Advanced tab or the default value does not conflict with a name already in the target connection, the command populates the default values in subsequent columns as is the following table. If multiple features are being output to the same target feature class that does not exist in the target warehouse, the command populates the default values for the first selected feature class as follows. Column Name

Default value

Output Mode

New

Key Mode

Preserve Key if the source has a displayable primary key, otherwise New Key

AutoNumber Mode

Preserve Definition and Values (PD&V) if the target warehouse s this capability, for example, OOM. Preserve Values if the target warehouse does not PD&V, and the key mode is New Key. Preserve Definition if the target warehouse does not PD&V, and the key mode is Preserve Key.


199

Working with Features Column Name

Default value

Target Coord System

For vector geometry, the default coordinate system of the target warehouse is populated. For raster geometry, the source coordinate system is populated. For nongraphic feature classes, this cell is empty. For no default coordinate system in the target warehouse, the fall-back logic (using MetadataService) is used to get the first coordinate system from the GcoordSystem table. For an empty target warehouse, the source coordinate system is assigned to the target feature class. This similar to the raster case mentioned. For an invalid or missing source coordinate system, no coordinate system is populated.

If the target feature class name you supply or the default value conflicts with a name already in the target connection, the command populates the default values in subsequent columns as in the following table. If multiple features are being output to the same target feature class that does not exist in the target warehouse, the command populates the default values for all the features other than the first selected feature as follows. Column Name

Default value

Output Mode

Append

Key Mode

N/A (blank)

AutoNumber

N/A (blank)

Target Coord System

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 Attributes-Opens the Attributes of dialog box that lets you select a subset of fields. You can use this option if only one record is selected in the grid.  Target Coordinate System-Opens a dialog box of the same name that lets you perform the following:  Review a coordinate system of a source feature class as well as the target warehouse coordinate systems.  Set a coordinate system for one or more new target feature classes at a time.  Assign a new coordinate system to one or more new target feature classes at a time.  Set the source coordinate systems to the target feature classes for multiple selected rows at a time, which are being output in New output mode. You can use this option only if at least one record is selected in the grid. At the bottom of the dialog box, you have the following check box:  Display target feature classes in map window-Lets you select whether to add the legend entries (the default) for the selected feature classes or to not add the legend entries.

200


Working with Features While processing, the application status bar displays the output feature class/query, target feature class, progress, and number of features output.

Running Output To Feature Classes creates the log file gmotts. your \Warehouses folder, if the file does not already exist, and appends formation to the contents of an existing log file. The command always deletes the existing log file and creates a new one for each run of the command.

To perform an output operation: 1. Select Warehouse > Output to Feature Classes.

2. On the General tab, select the appropriate items from the Source features to output treeview. When you hover the mouse cursor over an entry in the treeview, a tooltip is displayed indicating the geometry type. 3. Select the appropriate target connection from the Target connection drop-down list. 4. Select the Advanced tab; then for a selected source feature, select the appropriate name from the corresponding Target Feature Class cell drop-down list, edit an existing name, or type a new name.

5. If appropriate, change the Output Mode, Key Mode, and AutoNumber values.


201

Working with Features 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. 9.

10. 11.

202

See the “Target Coord System” and the “Select Coordinate System” topics in the GeoMedia Professional Help for information on using these dialog boxes. Select the appropriate name from the Coordinate systems list. 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. Optional: Check the Display target feature classes in map window check box to add the legend entries for the selected feature classes. Click Apply.


Working with Features The dialog box is dismissed, and a confirmation message box is displayed with the following information: The output process will result in: feature classes - New mode feature classes - Append mode feature classes - Force Append mode feature classes - Update mode feature classes - Append and Update mode Do you want to continue? 12. Click Yes to output the data from the source connection/query to the target warehouse

The status information and progress during processing are displayed in the status bar, and the log file gmotts.log is created. Optionally, new legend entries are added to the active map window.

Selecting Features in the Map Window You select features with a left mouse click or by drawing a fence on the map when the Select Tool is active. The Select Tool is located on the Selection toolbar and is the default active mode. When Select mode is active, the Select Tool button is depressed, and the tip of the cursor has a circle around it called the locate zone.

The locate zone determines how close to a feature you must be to highlight it or to select it. The size of the locate zone is set using the Size of cursor locate zone slider on the SmartLocate tab of the Options dialog box (Tools > Options).

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.


203

Working with Features The Selection toolbar s Inside Fence, Overlap Fence, Rectangular Fence, and Polygonal Fence selection modes, which are described later in this section.

A feature can be located (identified) only if it is displayed in the active map window and its Locatable property is turned on. A feature within the locate zone of the cursor is not located or highlighted until the cursor has been paused over the feature for a short time, but you do not have to pause the cursor to select the feature. The duration of the pause interval is set using the Delay before cursor highlights features slider on the SmartLocate tab. When you select one or more features, they become a select set. A select set can contain features from one or more sources. You create a select set to edit it. When the select set contains more than one object, any Edit tool you select affects all objects in the select set simultaneously. A select set can also contain both read-write and read-only features. Objects in the select set are distinguished as read-write or read-only by the display of handles in the map window when an edit tool is selected. For example, if you select the Move tool when a select set is active, handles appear on read-write objects but not on the read-only objects in the select set. 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 the “Changing the Locatability of Map Objects" section in the “Working with Map Windows” section.

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

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

To select a hidden or overlapped feature: When multiple features are under the cursor, the Always display Pick Quick dialog on locate check box on the SmartLocate tab lets you control the Select Tool behavior. When this check box is checked, the PickQuick dialog box is displayed whenever you do a left mouse click and there is more than one object inside the locate tolerance. If there is only one object inside the locate tolerance, the object is selected without the PickQuick dialog box displaying. When this check box is not checked, there are multiple features within the locate zone and you pause the cursor over them, an ellipsis (three dots) appears at the lower-right edge of the Select Tool. If you left click when the ellipsis is displayed, the PickQuick dialog box appears.

204



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 s 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 the “Defining Map Window ToolTips” section in “Working with Map Windows”.

To select multiple features: There are several ways to place multiple features in a select set. When the Select Tool is active, you can:  Hold down the CTRL or SHIFT key while left clicking the highlighted features.  Draw a fence with the Select Tool that encomes the area containing the features you want in the select set. The features included in the select set are determined by which Selection toolbar button (fence modes) is depressed.

   

Inside Fence selects all features that fall completely within the fence. Overlap Fence selects all features that fall inside and are overlapped by the fence. Rectangular Fence (the default) selects all features that fall completely inside the rectangular fence. Polygonal Fence selects all features that fall completely inside the polygonal fence.

To select all features for a legend entry: Highlight the associated entries on the legend and select Edit > Select by Legend Entry.

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


205

Working with Features display turned on and must be in the current view scale, but map objects do not need to be locatable.

To select all features for a data window: Click on the table selection button in the upper-left corner of the data window grid, or select Edit > Select All Rows.

This selects all features in the data window, whether they are visible in the data window or not.

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

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

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

To define query from a select set: 1. Create a select set.

206


Working with Features 2. Select Analysis > Select Set to Query.

3. From the Select features from drop-down list, select a feature class or query within the select set to be converted to a query.

4. 5.

6. 7.

8.

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. Optional: Change the default name and/or type a description of the query. that the Display query in map window box is checked, and change in the Map window name field, if appropriate, the map window in which to display the query results. OR To not display the query results in a map window, click the Display query in map window box to remove the checkmark. Optional: Click Style, and change the default style on the Select Style dialog box. 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. Click OK to generate and to display the query results in the specified data window and/or map window.

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” section for information on queries.

Collecting Data GeoMedia Professional s several methods of collecting data. You can digitize features directly on screen, digitize features using a digitizing table, digitize features on-screen 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 Professional's 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 s 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.


207


Tools for Speeding Up the Digitizing Workflow GeoMedia Professional provides several unique tools for speeding up traditional capture and edit workflows. All of GeoMedia Professional's commands are optimized to reduce the number of mouse clicks required for common tasks, but there are four additional tools that work in conjunction with other commands to speed up workflows even more. These tools are the following: 

SmartSnap



Coincidence



Using Existing Geometry



Automatic Feature Breaking

Using the Placement and Editing Tab The Placement and Editing tab on the Options dialog box (Tools > Options) contains options for settings to use with these tools for speeding up digitizing. It also is used for controlling editing behavior and tolerances and for various other commands as described in this chapter.

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 utility's online Help.

208


Working with Features Default Direction Type When you specify a new value for the Default direction type field for placement and editing operations, the new value is stored as a long integer in the preference set. The default setting for this preference is be 0, which indicates Azimuth. This setting is used during data capture in the context of certain construction aids.

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).

See “Setting Tolerances” in this section. SmartSnap, therefore, provides two important benefits:  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 Snap-Displayed when the cursor is within the locate tolerance of the intersection point of two geometries. End Point Snap-Displayed when the cursor is within the locate tolerance of an end point of a line feature. Vertex Snap-Displayed when the cursor is within the locate tolerance of a vertex of a line or area feature. On Element Snap-Displayed when the cursor is within the locate tolerance of any point on a line or area feature.


209

Working with Features Origin Snap-Displayed when the cursor is within the locate tolerance of the origin point of a text object or a symbol. Midpoint Snap-Displayed when the cursor is within the locate tolerance of the midpoint of a single segment in a line or area feature. Tangent Snap-Lets you create a snap point that is tangent to an existing arc segment. Perpendicular Snap-Lets 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 Snap-Displayed when the cursor is within the locate tolerance of the intersection point of two geometries. End of Line Snap-Displayed when the cursor is within the locate tolerance of the end of a raster line. Corner Snap-Displayed 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 Snap-An 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 Snap-A 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 Snap-Displayed 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 ed 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. 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. 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

210


Working with Features 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. 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.

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. 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 "SmartSnap" and "Using the Placement and Editing Tab" in this section.


211


Reusing Geometry to Digitize New Features In many digitizing workflows, features will share common boundaries or geometry. For example, adjacent parcel features, or a political boundary that follows the course of a river. In these cases you do not want to have to digitize the geometry twice because it is time consuming and likely to introduce errors, such as gaps between features, that will have to be cleaned up later. Using the Options tool bar option Use existing geometry when digitizing in conjunction with SmartSnap allows you to reuse existing features when placing a new feature or editing existing features.

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: Edit >

Geometry >

Continue Redigitize

Insert >

Feature

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:

The shortest distance between the two points highlights by default. Pressing TAB highlights the feature in the opposite direction:

Turning off Using existing geometry when digitizing from the toolbar has the following result:

212


Working with Features This is an example workflow used to add an adjacent feature to the following figure:

1. Place the first point of the feature. 2. Move the cursor within the snap tolerance of an existing feature from a locatable feature class, and the appropriate snap glyph is displayed.

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.

6. Click to place the fourth point.

7. Double click to end the feature.

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:


213


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

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.

Maintain Coincidence affects the following commands in GeoMedia Professional: Edit >

Feature >

Merge Split

Edit >

Geometry >

Edit Continue Redigitize Trim Trim to Intersection Extend Extend to Intersection Extend Two Lines to Intersection Construct Circular Fillet

Insert >

Feature

(including digitizing with offset)

Maintain Coincidence will modify placement and edit commands so that they add a vertex to all displayed and locatable features at the location of a snap when any action occurs that involves snapping to another geometry. This does not mean that the feature is split into two or that its shape is modified. All it means is that an additional shape point is added to the feature. It also

214


Working with Features means that if you delete or move a vertex, all coincident vertices will be deleted or moved at the same time. In this way, feature relationships can be automatically maintained within and across feature classes whenever an edit or placement operation occurs. It is important to note that coincidence only applies to features that are displayed and locatable. You can use the locatable setting for a legend entry to control which features participate in coincidence. An exception to the normal behavior for coincidence is ed when using arc geometry. By default, you cannot insert a vertex into an arc because it would require that they are automatically modified - arcs do not additional vertices. Therefore, if you commonly use arcs in your spatial database, you can control how they react to coincidence 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 arc's not being divided nor made coincident. 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.

Automatically Splitting Features Some data-capture workflows require features to be modeled using polylines with only start points and end points and no intermediate shape vertices. This is common, for example, in many land parcel and utility network databases. To maintain this model anytime a new feature is snapped into an existing linear feature, the existing feature must be split into two at the snap point. This has often been a cumbersome workflow in GIS and CAD systems requiring several steps to achieve the result. GeoMedia Professional provides the Break linear features option for automatically splitting features on a snap. When this option is selected, any edit or placement operation that snaps into an existing feature will split the feature into two features at the snap point. This option is off by default, but you can turn it on by selecting its check box on the Placement and Editing tab of the Options dialog box or its button on the Options toolbar.


215

Working with Features 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 option will not apply to the area or compound features, or to geometry collections. Also, linear features in geometry collections cannot be broken. The Break linear features option affects the following tools: Edit >

Geometry >

Edit (only on end point vertex 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:  Works on any locatable feature class from a read-write warehouse.  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. The following are cases of specific break conditions: Case 1: Create crossing geometry without snapping to existing geometry. Setting: Break same feature class.

Result: No break occurs, regardless of the current break setting. A break only occurs on a snap.

216


Working with Features 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. 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: Only the Highway feature is broken at the snap point. Case 4: Break between coincident line features. Setting: Break all feature classes.

Results: All coincident features are broken at the snap point, not just the Highway feature.

Interaction between Coincidence and Break The following cases show the interaction between coincidence and break: Case 1: Snapping to coincident features A. Break: Across all feature classes. Coincidence: Off

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


217

Working with Features 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. 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.

Undoing and Redoing Placement and Editing The Undo and Redo commands allow you to sequentially undo or redo database changes that you have made with placement and editing commands in the current session. When you open the Edit menu after you have made a database change, the commands appear followed by the type of undo or redo to be made. For example, if the last operation was moving a feature with the Move command, the menu would display Undo Move or Redo Move. Undo restores all database changes made by a single operation. A single operation consists of one or more database changes, depending on the placement or editing command. For example, if you use Move to move a single feature, Move makes a single database change (the change of the geometry of a single feature instance). Undo then moves the single feature back to its original position. 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 Edit > Select Set Properties Feature > Delete

218


Working with Features Merge Split Copy Copy Parallel Change Feature Class Geometry > all commands Attribute > Update Attributes Copy Attributes Edit Text Data Window Edit > Cut Paste See the corresponding layout window topics in the GeoMedia Professional Help. 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. If autonumber fields are defined for a feature class in a 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.

Inserting Features in a Map Window Once you have made a connection to a read-write warehouse containing feature classes, or you have created a new feature class from scratch, you can begin to create new features using the Insert Feature command. Insert Feature is a very powerful command that gives you access to a wide range of placement tools, including the following:  Point, line, area, and compound feature placement  Arc placement modes  Placement constraint to -specified azimuth or bearing angle  Stream digitizing  Rotation modes for point symbol placement  Ability to constrain placement to a specific angle  Offset digitizing  Perpendicular placement


219

Working with Features  Relative placement  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 section for information. You can enable or disable self-snapping during placement by checking or unchecking Allow Snap to Same Feature on the Insert Feature right mouse menu. 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.

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 icons-point, line, and area-are disabled. However, if the geometry type of the selected feature class is compound (meaning that features of this 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 section. The Placement Mode drop-down list lets you choose the appropriate placement mode from those available for the selected feature class.

220


Working with Features 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 section 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.

See the “Working with Coordinate Systems” section for information on this dialog box.

To insert a feature into a map window: 1. Select Insert > Feature.


221

Working with Features Pressing ESC does not cancel Insert Feature; you must select another command, such as the Select Tool, to cancel the command. 2. Click the drop-down arrow on the Insert Feature dockable control to display the list of feature classes in the read-write warehouses to which you are connected.

3. 4. 5. 6.

Click the feature class of the new feature. Optional: Select a different placement mode from the drop-down list. Optional: Click the Options button to change the placement parameters. Optional: Click the GeoWorkspace Coordinate System button to change coordinate system parameters. 7. Click the left mouse button to place the first vertex of the feature. 8. Continue left clicking until you have finished the feature. 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. 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. 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 center-Places 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 edge-Places 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

222


Working with Features start, end, point on edge dockable control appears for you to type specific arc placement parameters. (Shortcut key ―A‖)

Arc by start, point on edge, end-Places 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 Geometry-When 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 angle-Places polyline geometry by placing each point at a -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‖)

If there is no previous geometry, the point is placed at a -specified angle, depending on cursor location, relative to the horizontal. You can type any angle value in the angle field of the control to restrict placement. The default angle for this placement mode is 90 degrees. Place by circle-Places a circle that is a composite polygon consisting of two arcs. When you select this mode, the Place Circle dockable control appears for you to select the circle placement and to type specific radius or diameter value. (Shortcut key ―SHIFT+C‖)

Place by rectangle-Places a rectangular-shaped polygon feature using two clicks, specifying two diagonally opposite corners of the rectangle. (Shortcut key ―E‖) Place by rotated rectangle-Places a rotated rectangular-shaped polygon feature using three clicks. The first click defines the anchor corner point of the rectangle. The second click defines the rotation angle of the rectangle and an adjacent corner point of the rectangle. The third click defines the corner point of the rectangle, which is diagonally opposite to the point placed with the first click. The point at the third click location defines the edge that is perpendicular to the first two edges. (Shortcut key ―SHIFT+E‖)


223

Working with Features Point by Point-Places 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 dynamically-Places 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 line-Places 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 line-Places 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.

To insert a feature in “Arc by center” mode: 1. Select Insert > Feature. 2. Select a feature class with linear, area, or compound feature to place. 3. Right click to open the Insert Feature right mouse menu; then that the Arc Tangency Constraint item is checked. 4. Select the Arc by center placement mode. 5. Click to define the arc center.

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.

224


Working with Features To insert a feature in “Place at angle” mode: 1. 2. 3. 4.

Select Insert > Feature. Select a feature class with linear or area geometry to place. Digitize a few vertices. Select the Place at angle placement mode from the dockable control.

The default angle is 90o, relative to the last segment placed. If there is no previous segment, the angle is relative to horizontal. 5. Type an appropriate angle value in the placement angle field.

The next points placed are constrained to a multiple of the typed angle, based on the cursor position and relative to the last segment placed. 6. Move the cursor over the map window.

A line is shown in dynamics that is constrained to a multiple of the specified angle, based on cursor position, and relative to the last segment placed. So, for example, if you entered 45o, the segment will dynamically snap to an angle of 0o, 45o, 90o, 135o, 180o, 225o, or 270o as you move the cursor. 7. Click in the map window.

The next point is constrained to a multiple of the specified angle, based on cursor position, and relative to the last segment placed.

Using Rotation Modes When placing a point feature class consisting of points, you can select a rotation mode for placing the point feature. These modes are useful for placing point features that are displayed as symbols. By default, the active rotation mode is Place at angle, and the active angle is zero degrees. In this mode, the new feature is placed at the specified angle. The other rotation modes are Orient to geometry and Rotate dynamically. In Orient to geometry mode, the new feature is oriented in the same direction as the existing geometry to which you snap. If no geometry is snapped to, the placement is at zero-degrees rotation. In Rotate dynamically mode, the new feature is placed using two clicks of the left mouse button. 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 in the map window. When you digitize a symbol in Orient to geometry mode, the symbol appears dynamically before it is placed. You can also switch the orientation based on the direction of the line by pressing TAB.

To digitize oriented points: 1. that the legend entry style is set to something that will show rotation, such as a symbol or font.

2. Choose a point feature class to insert. Place at angle: 1. Set the rotation mode to Place at angle.


225

Working with Features o

2. Type an angle in the angle field. Use 180 , for example, and each time you click to place a o point feature, it will be placed at an angle of 180 .

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. 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. 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 Point-Requires the definition of a center point and a radius. You can specify the radius dynamically or by key-in.  By Diameter-Requires the definition of two diametrically opposed points.  By 3 Points-Requires the definition of three points on the edge of the circle to be inserted. 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.

226


Working with Features 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:

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 disted 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 ed. This command s 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.

To insert a circle by center point: 1. 2. 3. 4. 5.

6. 7. 8. 9. 10.

Select Insert > Feature. Select a feature class on the dockable control. Select Place by circle from the placement mode drop-down list. Select By Center Point from the Place Circle dockable control. Click (or type precision coordinates) to define the center point. Continue with Step 5. OR Press the Lock. Go to Step 7. Move the cursor to dynamically define the radius of the circle; then click to insert the circle. Go to Step 10. Click to define the center point. Type the radius on the Radius field; then press ENTER. Click to insert circle Press ESC to exit the command, or click again to define the center point and to insert another circle.


227

Working with Features To insert a circle by diameter: 1. 2. 3. 4. 5. 6. 7.

Select Insert > Feature. Select a feature class on the dockable control. Select Place by circle from the placement mode drop-down list. Select By Diameter from the Place Circle dockable control. Click to define the first point of the diameter. Click to define the second point of the diameter and to insert the circle. Press ESC to exit the command, or return to Step 5 to place another circle using this mode.

To insert a circle by 3 points: 1. 2. 3. 4. 5. 6. 7. 8.

Select Insert > Feature. Select a feature class on the dockable control. Select Place by circle from the placement mode drop-down list. Select By 3 Points from the Place Circle dockable control. Click to define the first point on the edge of the circle. Click to define the second point on the edge of the circle. Click to define the third point on the edge and to insert the circle. Press ESC to exit the command, or return to Step 5 to place another circle using this mode.

Using Construction Aids To more effectively use the placement and editing commands, such as Insert Feature, Continue Feature, Redigitize Geometry, Split Feature, and Edit Geometry, you can use construction aids. Construction aids provide the ability to calculate or construct a geometry through a specific method and then use that geometry during placement or editing - without exiting the command and interrupting your workflow. After using the construction aid, you are returned to the command from which it was started so that you can continue your placement or editing workflow. For example, while placing a linear feature, you may want the next point to be at specified distances along horizontal and vertical directions from a specified location. To achieve this, you can use the Delta X and Delta Y construction aid while in the Insert Feature command to construct such a point, and then resume the normal placement of a linear feature. If appropriate for the command, some construction aids are automatically repeated by the command without the need to reselect them manually through the right mouse menu or shortcut key. For example, it makes sense for the Delta X and Delta Y construction aid to repeat in the Insert Feature command until you complete a particular feature or feature part, but the Edit Geometry command would not automatically restart this construction aid once it completes because it does not usually make sense to repeatedly modify the x,y location of a vertex. Much of the functionality in the placement and editing commands is implemented as construction aids and is readily available from the right mouse menu and through shortcut keys during digitizing. The shortcut keys are listed per construction aid on the right mouse menu. The construction aid prompts and, in some cases, a dockable control, guide you through the workflow of the construction aid. While a construction aid is in use, options on the right mouse menu allow you to cancel a construction aid or back up a step if appropriate. The list of construction aids available on the right mouse menu varies with the feature being placed and the placement step in progress. During a placement and editing command operation, the construction aids function as follows, with examples shown from using the Insert Feature command:

228


Working with Features X and Y-Lets you type an X Easting value and a Y Northing value (Projection) or a Longitude and a Latitude (Geographic) and then construct a point at the specified location (X, Y). You can change the Easting and/or Northing (or Longitude and/or Latitude) values and a point is displayed dynamically in the map window to reflect the specified location. You can then click in the map window or press Enter to return the point to the command. This aid honors the settings on the Units and Formats tab of the GeoWorkspace Coordinate System dialog box. (Shortcut key ―X‖)

See the corresponding GeoMedia Professional Help topics for a complete information on the construction aid dockable controls and workflows. Delta X and Delta Y-Constructs 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‖)


229

Working with Features Delta X and Delta Y From Point-Constructs a point at specified distances in the horizontal and vertical directions from a specified location. You can change the distance values, and a point is displayed dynamically in the map window to reflect the specified distances from the reference location. You can then click in the map window or press Enter to return the point to the command. (Shortcut key ―P‖)

Distance and Direction-Constructs 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.

230


Working with Features Distance and Direction from Point-Constructs 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 Feature-Lets 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 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‖)

Distance/Distance Intersection-Constructs a point at the intersection of specified distances from two different locations that may or may not be snapped to existing features. This construction aid lets you define two overlapping circles, and then returns a point geometry at either intersection of the two circles. This intersection is commonly referred to as a Distance/Distance intersection; two fixed points and two distances from each of the points describe two intersecting circles. You define each circle by specifying an origin point, either by clicking the mouse in the map window, while possibly snapping to an existing feature, or by precision keyin using the Precision Coordinates dockable control. You then specify the radius of the circle by either dragging the mouse or by keyin of the radius value. Vector and raster snaps are honored when you are placing circle origins and specifying radii. The intersection point is then chosen and returned to the command by clicking the mouse while within the locate tolerance of the intersection you want. (Shortcut key ―I‖)


231

Working with Features The dockable control of this aid has two lock buttons that let you lock in the distance value that you type into the two distance fields. When this lock button is pressed down, the distance field is enabled and the distance value is used to construct the circle. In this case, the radius of the circle does not change as the cursor is moved. The circle remains at the constant radius specified in the field, regardless of the position of the cursor. If the lock button is up or not pressed down, the radius of the circle changes as the cursor is moved. By default, the lock buttons are down (locked).

Bearing/Bearing Intersection-Constructs a point at the intersection of two lines defined by specified bearing directions from two different locations, which may or may not be snapped to existing features. You can change the bearing values for these two bearing lines until they intersect, and then click in the map window or press ENTER to return the intersection point to the command. Each bearing line is defined by specifying an origin point, by clicking the mouse in the map window, while possibly snapping to an existing feature, or by keyin on the Precision Coordinates dockable control. (Shortcut key ―SHIFT+I‖)

Deflection Angle-Lets 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‖).

232


Working with Features 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:

Azimuth-Lets 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‖)

Bearing-Lets 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‖)

Parallel To-Lets 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‖)

Perpendicular To-Lets you digitize the next segment of a feature perpendicular to another feature. Upon selection of this mode, you are prompted to select the non-point feature to be perpendicular to. You can also snap to an arc to place the next segment perpendicular to the tangent to the arc at the snap point. As you move the cursor, the segment is drawn in dynamics. You can snap to any feature along the perpendicular extension at this point (the vertex is not automatically snapped to the selected feature). After the segment is placed, the aid returns you to the command from which it was started so you can continue your placement or editing workflow. This construction aid is not available unless you have digitized at least one point. (Shortcut key ―SHIFT+T‖)


233

Working with Features Perpendicular From-Lets you digitize the next segment of a feature perpendicular from another feature. This aid is not available unless you have digitized at least one point, and the last point digitized was snapped to an existing feature. You can snap from an arc to place the next vertex perpendicular from the tangent to the arc at the snap point. As you move the cursor, the segment or arc is drawn in dynamics, and the next vertex is displayed at 90 degrees from the feature currently snapped to. (Shortcut key ―SHIFT+F‖) Use Existing-Lets you digitize the next segment of a feature using existing geometry. This is useful when two features share all or part of a boundary because you do not have to redigitize the entire boundary between features. You can click two points along the existing geometry, and all the vertices between those points are copied to the feature being placed. This ensures clean data without slivers or gaps. (Shortcut key ―U‖) This construction aid differs from the Use existing geometry when digitizing option on the Placement and Editing tab of the Options dialog box in two important ways:  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. Offset-Places 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 -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‖)

Orthogonal-Lets you digitize a line segment that is perpendicular to the previous segment. The end point of the perpendicular segment is displayed dynamically in the map window during the cursor movement to reflect the specified location. After the point is placed, the aid returns you to the command from which it was started so that you can continue your placement or editing workflow. (Shortcut key ―H‖) Close Orthogonal-Inserts a feature through closing the geometry being digitized by making its last segment to be perpendicular to its first segment, which may be trimmed or extended to make the geometry closed. The trimmed or extended portion of the first segment of the geometry, and the projection line of the last point of the geometry projected onto the first segment of the geometry, are drawn in dynamics to signal what would be added or truncated by the insert orthogonal operation before you click to accept. (Shortcut key ―O‖)

234


Working with Features The following are several example workflows for using the construction aids.

Using Distance and Direction The Distance and Direction construction aid lets you place the next vertex of a feature at a location that is a specified distance and direction from a known location. For example, you would use this command 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. You type the distance, direction (distance bearing and distance azimuth), or deflection angle in the Distance and Direction dockable control. You first specify the source point, which can be a mouse click snapped to a location on a feature or a point in space, or it can be a keyin. The source point is then shown in dynamics. Next, you type a distance and direction in the dockable control, and the vertex is placed at the specified location.

To insert a feature with relative placement: 1. 2. 3. 4. 5. 6.

Select Insert > Feature. Select a feature class to place. Digitize a few vertices. Select Distance and Direction from the right mouse menu. Click or type a value to place a temporary point. Change the coordinate format in the Distance and Direction control to distance/azimuth or to distance/bearing. 7. Type the distance and direction values in the precision coordinate control.

A segment is connected from the last point placed to the point that is, the specified distance and direction from the temporary point. See “Using Precision Keyins” in this section.

Using Distance Along Feature The Distance Along Feature construction aid lets you snap to a location at a specified distance along a feature. For example, you would use this construction aid if you were digitizing a parcel and you knew that the next vertex of the parcel was located along the boundary of a second parcel 20 meters from the parcel corner. You first type a distance into the Distance Along Feature dockable control and then hover over the feature at the start point. As the dynamic cursor snaps to the feature, a segment is shown in dynamics from the last vertex placed to the proposed point along the feature.

Place the next point 20 meters from the parcel corner.


235

Working with Features If the distance is greater than the feature length or the area perimeter of an area, no dynamics display. Highlighting is in the direction in which the feature was digitized unless the line is too short in this direction. However, you can switch the direction by clicking the Switch Direction button on the control or by pressing TAB. You do not have to snap to the start point or end point of the feature; you can snap to any vertex or the midpoint on the feature. Distance Along Feature does not work with the On Element Snap vector snap.

To insert a feature with relative placement: 1. Select Insert > Feature. 2. Select a feature class to place. 3. Place the first point.

4. Place the second point.

5. Select Distance Along Feature from the right mouse menu. 6. Type the appropriate value in the Distance field on the Distance Along Feature control. 7. Identify the source location by hovering over the vertex you want to place the next point a distance from.

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. Move the cursor along the feature.

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).

10. Click to accept and to determine direction.

236


Working with Features The control is dismissed, and focus is returned to the mode that was active before the distance/direction option was chosen. OR

If multiple features are within the locate tolerance of the cursor, the PickQuick (ellipsis) cursor displays. Continue to Step 11. 11. Click to display the PickQuick dialog box. 12. Move the cursor over a number on the PickQuick dialog box to select a feature.

The feature is drawn in dynamics from the last point placed to the specified distance and direction along the corresponding selected feature from the current cursor snap point. 13. Click the selected number on the PickQuick dialog box to place the next vertex at the specified distance and direction along the corresponding selected feature.

The PickQuick dialog box and the Distance Along Feature dockable control are dismissed, and focus is returned to the mode that was active before the Distance Along Feature construction aid was chosen.

Using Perpendicular Placement Perpendicular placement allows you to place a segment of a feature at a 90-degree angle from or to an existing feature. This placement also lets you snap from an arc to place the next vertex perpendicular from or to the tangent to the arc at the snap point. The Perpendicular To construction aid prompts you to select the non-point feature to be perpendicular to. At this point, the next segment will be displayed in dynamics at a 90-degree angle to the selected feature. 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.

To insert a feature with perpendicular placement: 1. 2. 3. 4. 5.

Select Insert > Feature. Select a feature class with linear or area geometry to place. Digitize a few vertices. Select Perpendicular To from the right mouse menu. Select the vertex you want to be perpendicular to.

The next vertex is drawn in dynamics at a 90o angle to the selected vertex. 6. 7. 8. 9.

Move the mouse cursor into the snap zone on the feature you want to be perpendicular to. o Click to place the next vertex at a 90 angle to the selected vertex. Digitize a few more segments. Snap to a non-point feature.


237

Working with Features 10. Select Perpendicular From from the right mouse menu. 11. Move the cursor.

The next segment is drawn in dynamics that are constrained to be at a 90o angle from the segment snapped to in Step 8. 12. Click to place.

The segment is placed at a 90o angle, and you are returned to the previous mode. You can cancel the perpendicular mode without placing a segment from the right mouse menu.

Using Existing Geometry Use Existing geometry lets you to digitize the next segment of a feature using existing geometry. This option is useful when two features share all or part of a boundary because you do not have to redigitize the entire boundary between features.

To insert a feature with existing geometry: 1. 2. 3. 4.

Select Insert > Feature. Select a feature class to place. Place a point on a linear or area feature. Select the Use Existing from the right mouse menu; then place the next point.

If the previous vertex is snapped to a single feature, that feature is highlighted. Go to Step 6. Otherwise, the previous vertex is snapped to multiple features, so the PickQuick dialog box is displayed. 5. Select the feature whose geometry will be used.

The selected feature is highlighted. 6. Place the next point on the highlighted coincident feature.

The point is constrained to the coincident feature, and the geometry from the first point to the second point is highlighted. 7. If the coincident geometry is an area feature, press TAB to switch to the path you want to use.

The other path (from the second point to the first point) is highlighted. 8. Click another point to accept the highlighted geometry. 9. Return to Step 3 or Step 4, or continue placing additional points.

Using Offset 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 -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.

To digitize with offset: 1. Select Insert > Feature.

238


Working with Features 2. Select the feature class of the feature to be placed. 3. Select the appropriate placement mode. 4. Select Offset from the right mouse menu.

5. Type the offset value in the dockable control. 6. Select the feature to offset from (Line A in the example).

A temporary offset feature is displayed around the selected feature. 7. Select Use Existing from the right mouse menu.

8. Snap to and click on the first point and the last point of the temporary feature to copy it to the new feature. 9. Press ESC to dismiss the dockable control and to turn off the offset mode.

10. Digitize normally, with offset turned off.

11. Select Offset from the right mouse menu to turn on the offset mode.

The offset distance field remains populated with the previously entered value. 12. Select Line C.

13. 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.

14. Double click to end digitizing.


239


Inserting Orthogonal Features Close Orthogonal (right mouse menu) lets you insert an orthogonal feature through closing the geometry being digitized by making its last segment to be perpendicular to its first segment, which may be trimmed or extended to make the geometry closed. The trimmed or extended portion of the first segment of the geometry, as well as the projection line of the last point of the geometry projected onto the first segment of the geometry, are drawn in dynamics to signal what would be added or truncated by the insert orthogonal operation before you click to accept. Close Orthogonal is applicable to the Insert Feature and Continue Geometry commands, but not to the Redigitize Geometry command.

To insert orthogonal features: 1. 2. 3. 4. 5. 6. 7.

Select Insert Feature. Select a non-point feature class to place. Select the Point by point placement mode from the dockable control Digitize a line segment (1 in Figure 1). Select an arc placement mode; then digitize an arc (2 in Figure 1). Select the Point by point placement mode; then digitize a line segment (3 in Figure 1). Select the Close Orthogonal from the right mouse menu.

The projection point (P in Figure 1) is computed by projecting the last point of the geometry onto the first segment of the geometry. Two lines are then constructed by connecting the projection point and the last point, and by connecting the projection point and the first point. These two lines are drawn in dynamics (dashed line in Figure 1) to show what would be added or truncated by the Close Orthogonal operation. 8. Click to accept.

The geometry is closed (Figure 2).

Figure 1

Figure 2

Using the Right Mouse Menu At anytime while you are digitizing a feature, you can click the right mouse button to bring up the Insert Feature right mouse menu. This menu includes construction aids and temporary placement modes that suspend the current placement mode while the next vertex is placed (using the selected temporary placement mode). Once the next vertex is placed, the current placement mode resumes. When this menu is displayed, dynamics and autopan are suspended. You can select a menu entry or press ESC to dismiss the menu and to return to dynamics. The right mouse menu contains the following items: End Feature-Completes a feature. Cancel Feature-Cancels the feature currently being digitized, or if no feature is currently being digitized, it cancels the Insert Feature.

240


Working with Features Select Feature Class-Lets you click on a feature to select another feature class to place while in the command. Once a feature is selected, the feature selection field on the Insert Feature dockable control shows the feature class of the selected feature, and the command starts at the beginning of digitizing a new feature. Remove Last Vertex-Removes the last vertex from the current digitization. -Lists available construction aids for the selected feature, depending on the current state of digitization. Only pertinent construction aids are added to the list. See “Using Construction Aids” in this section for more information on these aids. Arc Tangency Constraint-Lets you to digitize a line tangent to an arc and an arc tangent to a line (or an arc). See “Using Arc Tangency Constraint” in the next section. Segment Length Constraint-Lets you place features by a specified length. See “Using Segment Length Constraint” later in this section. Allow Snap to Same Feature Allows you to either enable or disable self snapping during placement, as needed. The menu entry can either be checked (the default) or unchecked. While hovering the mouse on the feature being digitized with snap options ON, appropriate snap glyphs are shown in dynamics when this menu option is checked, and no snap glyphs are shown when this menu option is unchecked. While hovering the mouse on any existing feature with snap options ON, appropriate snap glyphs are always shown irrespective of whether this menu option is checked or unchecked. The following example shows the right mouse menu in when two or more points have been digitized with the last point snapped.


241


Using Arc Tangency Constraint Arc Tangency Constraint (right mouse menu) lets you digitize a line tangent to an arc and an arc tangent to a line (or an arc). Thus if a line and an arc or two arcs are sequentially placed, they are tangent. You easily switch between the arc tangency state (indicated by a check beside Arc Tangency Constraint on the right mouse menu) and the regular placement state (indicated by no check beside Arc Tangency Constraint). This constraint is turned on by default, indicating the arc tangency state, when Insert Feature is started the first time. The tangent segment/arc is drawn in dynamics as you move the cursor. You can snap into any feature along the tangent direction while a tangent line is being dynamically constructed and snap into any feature while a tangent arc is being dynamically constructed.

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.

To place a line tangent to arc or an arc tangent to line or arc: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15.

Select Insert Feature. Select a non-point feature class to place. Select the Point by point placement mode from the Insert Feature dockable control. Digitize a few line segments. Select Arc Tangency Constraint from the right mouse menu. Select the Arc by start, end, point on edge placement mode; then move the cursor. Click to place the tangent arc being dynamically displayed. Move the cursor in the map window. Click to place the tangent arc being dynamically displayed. Select the Point by point placement mode. Move the cursor in the map window. Click to place the tangent line being dynamically displayed. Select Arc Tangency Constraint from the right mouse menu to turn it off. Select Arc by start, end, point on edge placement mode. Digitize a regular arc in Arc by start, end, point on edge placement mode.

Using Segment Length Constraint Segment Length Constraint (right mouse menu) lets you place features by length through the Segment Length Constraint dockable control. When the Lock is unselected (not pressed), the Length field is disabled and is updated dynamically with the length of the dynamically constructed segment or arc. Selecting (pressing) the Lock enables the Length field so that you can type any valid segment length value. The Length field is then locked in the current value, and the dynamically constructed segment or arc is constructed and displayed with the locked length. You select to confine the next point to the distance defined by this constraint, but in the direction of the point returned by the construction aid. This constraint is turned off by default.

242


Working with Features The Segment Length Constraint may be useful in conjunction with construction aids that construct a point in some direction, such as the Azimuth, Bearing, Deflection Angle, Perpendicular From, Perpendicular To, and Orthogonal construction aids.

To place by length: 1. 2. 3. 4.

Select Insert Feature. Select a non-point feature class to place. Digitize a few segments/arcs. Select Segment Length Constraint from the right mouse menu.

5. Check the Lock check box. 6. Type a length value in the Length field. 7. Move the cursor around, and notice that the dynamic segment/arc is displayed with the locked length rather than attached to the cursor. 8. Click to accept and to place the segment/arc with the locked length.

Stream Digitizing Mode In stream digitizing mode (no toolbar button), you press and hold the left mouse button while moving the mouse to place the feature using a continuous stream of points. Releasing the button puts you back into the mode that was active before you began stream digitizing. This mode is especially useful for digitizing features with a lot of detail. By dragging the cursor over the feature, either on a paper map attached to a digitizing tablet or a scanned image displayed in the map view, you can quickly add the feature to your digital database.

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:


243

Working with Features Middle vertex is not dropped. Middle vertex is dropped.

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 a -specified distance along a feature.  Place the next point at the -specified distance and direction from a known location.

Digitizing Discontiguous Features and Features with Holes Discontiguous Features As stated at the beginning of this chapter, GeoMedia Professional s modeling features with multiple unconnected geometries, such as the islands of Hawaii, as a single feature or multiple separate features. If you choose to model them as a single feature with multiple geometry, it will have a single set of attributes, as opposed to separate attributes for each geometry. It will also behave as a single feature when you select it in the map window, that is, clicking on any one geometry will highlight all geometries. There are two ways to create discontiguous features:  Add new geometry to an existing feature using the Continue Geometry command.  Use the Insert Feature command with the CTRL key modifier. 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. 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: 1. Digitize vertices normally using left mouse button clicks. 2. Instead of completing the first geometry with a double click, press and hold CTRL while double clicking to complete the geometries.

The status bar prompts you to place the first point of additional geometry. 3. Digitize the next geometry in the normal way. By holding down CTRL each time you complete a geometry, you can add as many additional geometries as needed.

244



Areas with Holes Often real word area features will contain holes, as in the following example:

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.

Creating Features with More than One Geometry Type It is possible that you may have features that contain both arc geometry and linear geometry. An example is a parcel that has its corner defined as an arc, as in the following example:

GeoMedia Professional s the placement of these features - called composite features by allowing you to switch between placement modes when you are digitizing individual features.

To digitize a composite polygon: 1. Select Insert > Feature. 2. Click the drop-down arrow to display the list of feature classes, queries, reference features, and categories; then click the appropriate area feature. 3. Click the appropriate placement mode to place for the first geometry. 4. For Point by Point Placement or Place at Angle, enter each point of the polygon. 5. Switch to one of the arc placement modes, and enter the arc points in the appropriate order. The last vertex placed is used as the start point of the arc. 6. Double click to end the feature. This works for linear features also.

Using Precision Keyins When digitizing new features, or when editing existing features or geometry, you can use precision keyins to specify the map coordinates of input points. A precision coordinate is the exact real-world coordinate location of a vertex. They are used as an alternative method of data capture in which instead of clicking with the mouse to place a point, you use the keyboard to type its actual coordinate location. This may be in one of several formats, such as latitude/longitude coordinate, an easting/northing, or a distance and direction from the last vertex. Although they can be used for the capture of any feature type, precision coordinates are often used as a way of entering parcel features where the information is provided in coordinate and/or bearing/distance format. In GeoMedia Professional, you can use the Precision Coordinates dockable control to type a coordinate anytime you are prompted to enter a point. This includes placing features, editing vertices, and editing control points for image and vector registration. The advantage of this method of data entry is that it is much more accurate than digitizing off a paper map or a scanned image. The disadvantage is that it is a somewhat slower technique.


245

Working with Features The Precision Coordinates dockable control provides dynamic readout of the cursor location. You select the appropriate coordinate format, type the coordinate values, and select an update setting using the Precision Coordinates dockable control. The map coordinates corresponding to the current location of the screen cursor are displayed next to the formats list. Some of the coordinate formats and units that you can select are, for example:  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) 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” section for additional precision entry tools. See “Setting Units and Formats” in the “Working with Coordinate Systems” section.

246



Tools for Collection of Attribute Information So far the discussion of data collection tools has focused mostly on geometry. The following section describes some of the tools for collecting the information about the features - the attributes. Some capture workflows involve capturing the geometry first and adding the attributes later; others focus on collecting the attributes and geometry separately and combing them at a later stage. Still others call for collecting the attributes of a feature at the time it is digitized.

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” section.

Collecting Attributes as the Feature is Digitized This workflow is ed by the use of the Display Properties dialog for new features option on the Placement and Editing tab of the Options dialog box, which determines whether the Properties dialog box automatically displays when you create a new feature with a placement or editing tool. For example, this option affects any operation when you create a new feature, such as Insert > Feature. When turned off, the dialog box does not display, except when the newly created feature has required attribute values that must be populated. In that case, the dialog box always displays regardless of the check box setting. You can also turn this option on and off from the Options toolbar.

Using this tool ensures that attribute information is always entered when new features are created.

Adding Geometry to Features If you have created new features by adding rows in a data window, you can add geometry to those features using the Continue Geometry command, as follows: 1. In the data window, select the feature for which you want to create new geometry. 2. Digitize the geometry in the map window to automatically add the geometry to the existing feature.

Linking Existing Geometry to Existing Attributes If you have created attributes and geometry separately, you can link this information by creating a between the two on a common key value and outputting the result of the to a new feature class. If there is no common key value, there is no way to automatically link the two sources of information, and you then must perform this task manually. See “Working with s” in the “Analyzing GeoMedia Professional Data” section.

Automatically Populating Attributes GeoMedia Professional provides two ways of automatically populating attribute values as you digitize:  Setting required values on default values on the Feature Class Definition dialog box.


247

Working with Features  Copying attributes from the last feature placed. 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, 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” section, “Working with s” in the “Analyzing GeoMedia Professional Data” section, and “Outputting Feature Data to Warehouses” in this section.

Automatically Copying Attributes from Previous Features When successively placing two or more features of the same feature class with Insert Feature, Insert Text, or Interactive Label, you can automatically copy the attribute values of the record of the first feature to the record of the second feature, and so forth. Thus, when features have many attributes that do not change from feature to feature, you only have to edit those attributes that do change. To copy attribute values from previous features, you turn on the Copy attribute values from previous feature check box on the Placement and Editing tab of the Options dialog box (Tools > Options). By default this check box is unchecked. If the Properties dialog box is open for the second feature you are placing, the attribute values are displayed.

Inserting Area Features Automatically The Insert Area By Face and Insert Interactive Area By Face tools each allow you to create multiple area features from existing linear or area features, categories, reference features, and queries. These commands are useful in two data-capture workflows. First, when converting large amounts of area data, it is often more efficient to collect the lines that make up the areas rather than digitizing each area one at a time. These commands allow you to collect the linework in the most efficient way and then to convert it into area features. Second, a data-capture workflow often requires integrating line data collected in a CAD system. You can use these commands to automatically convert this linework into area features. Because you are creating new data, the Z value you receive is the height value of the original features in the select set. With these commands, you create a select set of component linear/area features, select an area feature class for the new features (which must be a writeable feature), and decide in the creation of new area features to ignore holes, to include holes, or to include holes as features. These two commands use the software's topology-on-the-fly concept to generate the area features. You should use the Validate Geometry command to ensure that no invalid geometry conditions exist in the input features before running the area creation commands. When using Insert Area By Face, clicking OK on the dialog box begins processing. A new area feature is automatically created for each closed region in the select set. Because you are creating new data, the height value you receive is always the default height value you specified on the Units and Formats tab of the Define Coordinate System File dialog box. When using Insert Interactive Area By Face, pause the cursor over a proposed area feature. When the feature highlights, click the left mouse button to create the new area feature. In both tools, no extrapolation of data is performed; that is, no gaps in the select set are closed. When the Include holes option is turned on, holes are formed by feature geometries that form polygons within closed regions in the select set. However, nested holes and islands are not

248


Working with Features detected. When Include holes as features option is turned on, holes are converted into features. The following examples show the results of using these commands:

Area data collected as lines.

Area inserted including holes.

Area inserted ignoring holes.

Area inserted including holes as features.

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.

To insert an area feature: 1. Select the appropriate linear/area features, categories, reference features, and queries to place them in a select set. 2. Select Insert > Area By Face.

3. Click the Feature class drop-down arrow to display the list of feature classes in the read-write warehouses to which you are connected. 4. Click the feature class in which you want to create area features. 5. Select the appropriate Hole processing option. 6. 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 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. 7. 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.


249

Working with Features To insert an area feature interactively: 1. Select the appropriate linear/area features, categories, reference features, and queries to place them in a select set. 2. Select Insert > Interactive Area By Face.

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 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.

Inserting Text Features into a Feature Class You can insert text features into a feature class and place them on the map interactively with the Insert Text command. Text placement is dynamic, so that you can see characters appear next to your cursor as you type. If you change the alignment set for the text after typing your text, you can also see the position of the text change next to your cursor. If you want to place multiple copies of the same text, you can do that with additional mouse clicks. Insert Text is an interactive mode, and you have to press ESC or click the Select Tool to return to select mode. Starting Insert Text displays the following dockable control:

In addition to basic text insertion, Insert Text provides the following functionality:  Applying instance-based symbology for text features-By default, placed text relies on the Select Style parameters defined in the legend when displaying the text in the map window. You may override these parameters on individual text instances (instance-based symbology) by checking the Override style check box and defining the appropriate text symbology. When the Override style check box is checked, the entire text string will display using the defined format (bold, italic, or underline), color, size, and font. To change instance-based text symbology, you need to use the Edit Text command.

250


Working with Features  

 





Placing incremental numeric text-Type a numeric (integer or real) value into the text-entry field, and then set the increment value to an integer or real number. Placing text at a -defined rotation angle-Set the rotation mode to Place at angle, set the appropriate angle for placing the text, and then click to place the text. The controls on the dockable control remain as set. Placing text to rotate dynamically-Set the rotation mode to Rotate dynamically, click for the location of the text origin, and then click for rotation. Placing text along an arc-Set the rotation mode to Place along arc, optionally modifying the inter-character spacing, and then digitize three points to define the curvature of the arc, in the order 1-2-3. Upon defining the third data point, the text will be floating and oriented along the curvature of the arc defined. Click a fourth point to place the text. Type additional text to continue the process, select another command, or press ESC. Using this mode generates a composite text collection, which lets other parts of GeoMedia recognize the resulting multi-part text as a single composite string rather than individual characters. Placing along existing geometry-Set the rotation mode to Place along existing geometry, type a single-line text, and then select a linear, area. or compound geometry. This displays the text in dynamics, undulating along the curvature of the selected geometry starting from the mouse cursor. You can control the distance of the text from the geometry and the spacing of the characters, and influence the smoothness of the flow of the text. Move the cursor above or below the geometry to get the appropriate offset distance from the geometry, increasing the inter-character spacing by using the mouse wheel or clicking the up arrow key. Tune the resulting text pattern by changing the vertical offset or by using the down arrow key. Click on the map window or type the location coordinates to place the text. Optionally modifying the inter-character spacing-Use character spacing modifications to expand or to retract the text string, except when placing multi-line text. If character spacing is adjusted with the Place at angle or Rotate dynamically mode, a composite text collection is placed as with arcs. Otherwise, a simple multi-character string is placed. You can use the mouse wheel and the + and - keys to increase or to decrease the character spacing after the second click point and before the fourth click point.

To insert text: 1. Select Insert > Text to display the Insert Text dockable control. 2. Click the drop-down arrow to display the list of text feature classes, queries, reference features, and categories in the read-write warehouses to which you are connected. If none of the open read-write warehouses contains a text feature class, create one through Warehouse > Feature Class Definition. 3. Click the feature class you want to contain the text. 4. Optional: Check the Override Style check box; then define the appropriate text symbology. 5. Select the text alignment you want from the drop-down list. 6. Type the text you want to place in the text-entry field. To create a new line in the text, press CTRL+ENTER (except for curved text).

As you type, the text appears in the text field and in dynamics next to the cursor in the map window. 7. 8. 9. 10. 11.

Select the text placement rotation mode. Position the text where you want it on the map; then click the left mouse button. To place additional instances of the same text, repeat Step 8. To place additional but different text, repeat Steps 7 - 9. To exit Insert Text mode, press ESC or click the Select Tool.


251

Working with Features 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.

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

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

252


Working with Features Portions of Text Style When editing multiple text features, you can change individual text characteristics (text string, alignment, style properties) rather than overwriting all characteristics for all selected features. When the selected text features have differing values for text characteristics, that is, if the select set contains at least one composite text collection indicating that it is not possible to type a multi-line text, each control on the dialog box presents itself in a neutral state to indicate that no change is applied. Checking the Override style check box while in the neutral state changes the state to checked. Clicking Bold, Italic, and/or Underline while in neutral state changes them to the pressed state. However, once you change the state of a control from neutral, it continues to maintain one of its two states only (that is, either checked/unchecked or pressed/unpressed). The dialog box appears as on the left if the select set does not contain any composite text collections, indicating you can type multi-line text. It appears as on the right with the Size and Font fields in neutral state if the select set contains at least one composite text collection, indicating you cannot type a multi-line text.

To edit a text feature: The following behavior also applies to one or more instances of text selected from a text collection. Basically, the Edit Text dialog only displays attributes if they are common. Any edits are written to all of the items in the collection. 1. Select the text feature class instance(s) in the map window. 2. Select Edit > Edit Text.

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.


253

Working with Features 6. Accept the text symbology, or change it through the format (bold, italic, or underline), color, size, and font controls. Click OK.

Selecting and Searching for Text Select Text lets you define the criteria to search for graphic text features, performing the search as you can for text in a Microsoft Word file, according to any combination of their text string and various style properties, and then select text features. Thus, you can quickly find and update text to adjust to changing map specifications or to create new map products. This command uses a combination of both text string and style characteristics on all the displayed graphic text legend entries within the legend of the active map window. In addition, when you specify a text string as selection criteria, you can use wild cards and perform sub-string selection. If you do not use a text string, the search is based on style alone; if you do not specify style characteristics, the search is based on the text string alone. In the search, this command finds those text feature instances displayed in the map window that match the specified search criteria. The search results are output to a new select set, whose rich text format parameters (color, font, size, and so forth) you can edit. You can then immediately use this select set as input to other commands such as Edit Text or Delete. For those features with override style, selection is performed using the rich text format information available in them. In the case of plain text, the default style property information of the corresponding legend entry is used. For those features with override style, the command assumes that the rich text style information is constant for the whole text and always uses the rich text style of the first character. When an input geometry contains a standard text collection, the geometry is selected if at least one of the items in the collection matches the selection criteria. Selecting Edit > Text > Select Text displays the Select Text dialog box for you to define the appropriate search criteria. When you first start this command, all the dialog box controls are in the neutral state as in the example on the left. To return to this neutral state after setting any search parameters, as in the example on the right, you must exit and restart the command.

You can type or select the text string you want to search for in the Text field. Note that the search is not based on a case-sensitive text string. Checking the Match entire text check box selects those graphic text features with their text having an exact match with the string value entered in the Text field. Checking the Use wildcards check box lets you use any of the listed special characters entered in the Text field as wildcards and perform pattern matching using both regular characters and wildcard characters as specified in the Text field. Regular characters must exactly match the characters specified in the character string. Wildcard characters, however, can be matched with arbitrary fragments of the character string based on the wildcard character used. This command s the following GeoMedia-recognized wildcards only: 

254

%

Any string of zero or more



_

(underscore) Any single character


Working with Features characters 

Any single character not within the Any single character within the  [^] specified range ([a-f]) or set specified range ([^a-f]) 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 s resolving these problems by letting you redefine geometry curvature and location using an existing geometry or a -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 redigitizing a multi-line text. You can 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  Place along arc  Place along existing geometry

Placing at Point The Place at Point placement mode lets you change the location, control the inter-character 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.


255


Placing along Arc The Place along arc placement mode lets you replace the curvature of the text geometry with the curvature defined by a -defined three-point arc. This mode s Start Point, Point on Edge, End Point (1-2-3) arc placement. You should digitize the three points to define the curvature of the arc in this order. Upon defining the third data point, the text is shown in dynamics oriented along the curvature of the arc defined. This command responds to mouse moves by floating the text dynamics accordingly. Clicking a fourth point places the text at that point. The following figures show the text being displayed in dynamics when defining the arc and the resulting text geometry.

Placing along Existing Geometry The Place along existing geometry placement mode lets you select an existing geometry, so that the text is undulated along the selected geometry and is shown in dynamics. You can place the text at the location of your choice, undulating the text along the geometry 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:

256

Input

Output

Remarks

Single-unit text. (Single text point geometry)

Composite text collection, or single-unit text

If the single-unit text contains only a single character and the placement mode is either Place along existing geometry or Place along arc, the resulting text geometry remains as single-unit text with the orientation of the character adjusted accordingly. If the placement mode is Place at point with normal character spacing, it also results in single-unit text.


Working with Features Input

Output

Remarks

Composite text collection

Composite text collection, or single-unit text

If the placement mode is Place at point with normal character spacing, it results in single-unit text with an orientation of zero.

Standard text collection. (Only a single item at a time is allowed to redigitize.)

Nested text collection, or standard text collection

Standard text collection contains only single-unit text items, thus: If redigitizing an individual item results in a composite text collection, the output is a nested text collection. If redigitizing an individual item results in a single-unit text, the output is a standard text collection.

Nested text collection. (Only a single item at a time is allowed to redigitize.)

Nested text collection, or standard text collection

If redigitizing an individual item converts a composite text collection to a single-unit text, it might result in a standard text collection.

While redigitizing text, you can control inter-character spacing by using the mouse wheel or the + and – keys. 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.

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

To define a hypertext attribute in a read-write warehouse: 1. Select Warehouse > Feature Class Definition.


257

Working with Features 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 - dialog box, click the bottom row selector that contains an asterisk.

5. Click somewhere in the Name field, and replace the automatically generated attribute name by typing a meaningful name, such as HYPERTEXT. 6. Click the Hypertext check box. 7. Click OK. 8. Close the Feature Class Definition dialog box.

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

To insert or edit hypertext from the map window: 1. Select the feature in the map window.

258


Working with Features 2. Double click the selected feature, or select Edit > Select Set Properties.

3. On the Attributes tab of the feature's Properties dialog box, click the hypertext cell in the Value column, and type the path and name of the file or Web location. To edit, highlight the file name or Web location, and type the new file name or Web location. You must highlight the text to edit it. If you just click on the text, the hypertext link is invoked. 4. Click OK.

To designate a column in the database as a hypertext link in MGE or MGSM: In MGE and MGSM, you must identify both the table and column names in the .ini file for the MGE or MGSM data server using the HYPERTEXT: keyword. You can identify several columns without repeating the keyword, but each table-column pair must appear on a separate line. For example, the Birds table contains a hypertext column linking a record to a photograph of the species, one that references an audio clip of the bird's call, and one that identifies a video clip of the bird in flight: HYPERTEXT:Birds,Photo Birds,Audio Birds,Video The MGE or MGSM data server looks for hypertext files in the multimedia folder of the project unless the HYPERTEXT PATH: keyword appears in the .ini file. Use this keyword to identify one or more folders in which to search for multimedia files. If more than one folder is specified, the folders are searched in the order specified. You may use either a comma (,) or a semicolon (;) to separate the path components. Path components may contain UNC-style folder names: HYPERTEXT PATH:C:\Images,D:\AudioClips, \\BIGSERVER\VIDSHARE\Birds\Video

Inserting Features in a Data Window You can also insert features into a read-write feature class using an active data window by typing in its attribute information. When you insert a feature using this method, it does not have any associated geometry. You can, however, use the Continue Geometry command to subsequently add geometry to the feature in a map window.


259

Working with Features To add a feature in a data window: 1. Activate the data window in which you want to insert a feature. 2. Type the attribute information for the feature in the last row of the data window.

Working with Categories Categories lets you group feature classes and queries into categories in a structured way. Thus, you can create your own customized logical model of your data as a complement to the physical model represented by the warehouse-resident feature classes and the queries built upon those feature classes. This lets you take control of what you want to see and helps you organize your data. Once categorized, you need not bother about connections or the source of your data. You can think of these categories as interface shortcuts only; they do not form actual parts of the warehouse data model. You may want to, for example, create thematic categories to group Rail and Road features under the category Transportation. Or you may want to create a category to just reflect the priority or frequency of use, for example, you might want to work with only a fixed set of feature classes and queries and not bother about others. The categories possibilities are only limited by one's imagination. The Categories command provides you with great flexibility in category creation as you group feature classes and queries. You can include a feature class or a query into more than one category, and feature classes and queries can also appear in none of the categories. When creating a new feature class or query, you cannot, however, assign them to a category at that time. Categories can contain feature classes and queries from multiple connections, including read-only connections, and the connections are hidden to simplify category organization and presentation. No distinction is drawn between feature classes and queries within a category. In addition, you can nest categories in folders that in turn can have subfolders representing individual categories, and each such category subfolder can in turn have sub-categories to continue the nesting as required for your organizational plan. You also have flexibility in naming categories by the aliasing of feature class and query names as well as the aliasing of attribute names. Finally, you can share your categories within the enterprise.

Managing Categories The Categories dialog box lets you easily manage your categories and their contents. You can create and delete categories, add features and queries to them, edit their properties, rename/alias categories and attributes, move and copy categories and their contents in the treeview, and organize and expand the treeview nesting.

260


Working with Features 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:

You can copy and move categories/sub-categories, feature classes, and queries to other categories by using drag-and-drop. You cannot, however, drop feature classes and queries on the root node Categories nor drag-and-drop this node. Drag-and-drop works similarly to Windows Explorer's folders treeview. While drag-and-drop is being done, if you press Ctrl, a copy is performed; otherwise, a move operation is performed. Tooltips on the treeview show the original feature class name (with or without the connection name, per the Options > General tab setting Add connection prefix to feature names) or query name. Once defined, the category structure appears in treeviews across the product by the commands, for example Attribute Queries and , and controls to 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.


261


In creating categories under the Categories root node or subfolder, you use Create Category to provide a unique name and an optional description, both of which you can later change. You can delete a selected category, which also deletes all subfolders and their contents by clicking Delete Category on the Categories dialog box or by pressing the Delete key. To add one or more sets of features (feature classes/queries) under a category, you select a category and then use Add Features to make selections from all the features and queries in the GeoWorkspace under the Queries node and the name of each connection in the GeoWorkspace as a separate node at the first level, as displayed on the Add Features dialog box. All connection nodes contain the feature classes available in that connection. These are the physical connection, feature class, and query names, not the logical names as categorized. You can add multiple items to a category by checking multiple item check boxes or the Queries node and/or the connection node on the Add Features dialog box. You can remove features or queries from a category by selecting the item then clicking Remove Features on the Categories dialog box or by pressing the Delete key.

Once you have added feature classes and queries to a category, you can review and edit their properties from the Categories dialog box. Selecting a feature class or query and then clicking Attributes displays the Attributes of 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 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

262


Working with Features 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/-defined, categorized feature class and query names and descriptions. Changing these names and descriptions does not change the original, read-only values. You can also view the read-only feature class and query category names. These names show the complete category hierarchy using the dot convention. For example, a category C1.Sub_C1_1 indicates, that the feature class belongs to sub-category Sub_C1_1 whose parent category is C1.

Feature Class Properties Query Properties After you edit the properties, the command validates the new name for uniqueness at the same level of hierarchy in the treeview, and the name and description of the categorized feature class/query are updated.

To create a category and add features/queries: 1. Select Warehouse > Categories.


263

Working with Features 2. Click New Category.

3. Type the appropriate category Name. 4. Optional: Type a category Description. 5. Click OK to create the category.

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.

264


Working with Features 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.

9. Click OK to return to the Categories dialog box.

To edit feature class and query properties: 1. Select Warehouse > Categories. 2. Select the appropriate feature class or query.


265

Working with Features 3. Click Properties.

4. Edit the Name and/or Description fields; then click OK.

To manage feature class and query attributes: 1. Select Warehouse > Categories. 2. Select the appropriate feature class or query. 3. Click Attributes.

4. Check or uncheck the appropriate Attributes check box(es) for the selected feature class or query. 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. Graphic attributes cannot be renamed.

266


Working with Features 7. Type the New name; then click OK.

8. Click OK on the Attributes of dialog box.


267


268


SECTION 9

Working with Catalogs The Catalogs commands form a bridge between spatial data and the standard geospatial catalog record(s) that describe that data. These commands the integration of metadata search, edit, and query functionality with other GeoMedia functions, and they also provide complete spatial metadata functionality within GeoMedia Professional. With these commands, you can connect to geospatial catalogs, query for interesting catalog records (metadata items), and open associated GDO connections (if the record is already associated to a feature class). See “Catalog Features,” “What is Geospatial Metadata?,” and “Glossary of Catalog Terminology” in this section.

In summary, the Catalogs commands let you catalog and open associated feature classes and perform the following additional tasks in manipulating catalogs:  Import metadata from other exchange formats.  Associate a feature class to a metadata record.  Update spatially related metadata elements from the associated feature class.  Search catalogs for feature data and image files.  Export to standard exchange formats.  Generate catalog record reports. 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.


269

Working with Catalogs 2. The second set of modules has spatial data as input from warehouses, and it 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 -selected metadata records or as a result set from a query, and it lets you open associated connections in GeoMedia. These modules, the Catalogs commands, thus form a bridge between spatial data sets and their associated metadata sets. The Catalogs commands are the following: 

New Catalog



Export Catalog Records



New Catalog Connection



Associate Catalog Records



Catalog Connections



Catalog Explorer



Import Catalog Records

Catalog Features Standards-compliant—GeoMedia Catalog makes it easy for anyone, regardless of prior knowledge of the Federal Geographic Data Committee (FGDC) standard, to create, manage, and publish FGDC-compliant metadata. Catalog also s import and publication of metadata records that conform to the ISO-19139 technical specification. Biological Data Profile—Create standardized metadata for your biological datasets following the FGDC‘s Biological Data Profile. Data Layer Association—Catalog ties metadata to data by allowing you to associate a metadata record with the GeoMedia feature class or image file that it describes. Metadata Capture—Once you have associated a catalog record with a dataset, you can extract metadata elements like bounding coordinates and attributes, directly from the dataset into the metadata record. Catalog Explorer—Bridges the gap between spatial data and metadata catalogs to provide an unprecedented level of access to and control over your GIS data library. With the Catalog Explorer, you can quickly locate and preview any dataset in your GIS data library, and you can automatically load search results into a GeoMedia map window. Browse Graphics—Include images of datasets in your Catalog reports. Online Help with Real-world Metadata Samples—Context-sensitive online Help provides FGDC definitions and real-world metadata samples. Metadata Templates—Load one record with your organization's core metadata, save it, and use it to create multiple metadata records, and thus instantly reduce data-entry time. Import and Export—Load any metadata record that is FGDC compliant – in ASCII text or XML format, or in GeoMedia Catalog Exchange format(s) or ISO-19139 XML format – into GeoMedia Catalog. Exchange your catalog records with others as ASCII text, in GeoMedia Catalog Exchange format, or in XML (FGDC or ISO-19139) format. Metadata publishing—Output attractive, Web-ready metadata reports to distribute or to put on your Web site. Create and use your own enterprise style sheets to make published XML files look just as you would like them to.

270


Working with Catalogs

What Is Geospatial Metadata? Geospatial Metadata is data that describes geospatial data. Geospatial metadata tells you the who, what, and when of a geospatial dataset. Who created it? For what purpose? When? Geospatial metadata tells you what a dataset cannot show you—data quality, history, and availability. Through metadata, you can answer the following questions to determine whether a geospatial dataset suits your needs: 

Where did a dataset originate?



What geographic area does it cover?



What steps were followed to create it?



How do I obtain the data?



What attributes does it contain?



Will it cost me anything?



How is the data projected?



Whom do I for more information?

Geospatial metadata has been compared to the nutrition label on a food package. Without this label, you cannot be sure whether the food you are eating is good for you. Without metadata, you do not know if the data you are considering using is good for your intended use. See the “GeoSpatial Metadata Profile: FGDC Dataset” document (FGDCDatasetMetadataProfile.pdf in \Program Files\GeoMedia Professional or \GeoMedia).

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


271


What Are FGDC Metadata Standards? The FGDC is the Federal Geographic Data Committee—the U.S. federal government committee responsible for creating and maintaining widely adopted standards for metadata. FGDC geospatial metadata standards have been adopted by organizations that author metadata within the U.S. and by many enterprises outside the U.S. as well. GeoMedia Catalog commands both the FGDC Content Standard for Digital Geospatial Metadata, commonly called the FGDC standard, and the Biological Data Profile of the CSDGM, which includes an extended set of specialized metadata content elements. The FGDC standard is like a style guide for metadata. It defines what information belongs in a metadata record and the order in which it is presented. The purpose of the FGDC standard is to provide a common definition for geospatial metadata to the GIS community. Through the use of a common standard, it becomes easier for those within and among different organizations to share data through metadata. The FGDC standard organizes a metadata record into the following seven main sections: 1. Identification Information: Basic information about the dataset. Where did the data originate? How current is it? For what purpose was it created? What geographic area does it cover? 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 ed? 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?

272


Working with Catalogs In addition, the FGDC standard defines three ing sections, which are not used alone, but rather are used within the seven main sections. The ing 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. 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. Under the FGDC standard, there is a one-to-one relationship between a metadata record and the GeoMedia feature class or image file that it describes. In other words, you should have one metadata record per dataset.

What Are ISO Metadata Standards? In 2003 the international community adopted the ISO-19115 Geospatial Metadata standard. The objective of ISO-19115 is to provide a clear procedure for the description of digital geographic datasets so that s can determine whether the data in a holding will be of use to them and how to access the data. Like the FGDC metadata standard, the ISO-19115 model consists of multiple packages of geospatial metadata content elements.


273

Working with Catalogs ISO has also produced the ISO-19139 technical specification, an XML schema for metadata implementation. ISO-19139 is designed to provide a common specification for describing, validating, and exchanging metadata about geographic datasets. It is intended to promote interoperability, and to exploit ISO 19115‘s advantages in a concrete implementation specification. GeoMedia‘s Catalog commands include for importing and exporting metadata records in an XML format that conforms to the ISO-19139 technical specification.

Updating Metadata Databases for GeoMedia 6.0 or Higher The following workflow allows s of the current software to update their databases to the new format. 1. Open GeoMedia SMMS version 5.x before uninstalling the legacy product and before installing GeoMedia Professional 6.0 or a higher version. 2. Export all records to SEF format, and make a secure copy. 3. Uninstall GeoMedia SMMS version 5.x and GeoMedia Professional version 5.x, and then install GeoMedia Professional 6.0 or a higher version. 4. Create one or more new catalogs. 5. Import SEF records exported from GeoMedia SMMS version 5.x. See the “Using Oracle Connections” and “Using SQL Server Connections” appendices for more information.

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

274


Working with Catalogs To create a new catalog: 1. Select Tools > Catalogs > New Catalog.

2. Select the appropriate catalog template; then click Open.

3. Type the appropriate File name; then click Save.

The template is validated, and if valid, the catalog is created. See the “Using Oracle Connections” and “Using SQL Server Connections” appendices, which discuss how to create Oracle and SQL Server Catalog data bases.


275


Creating a New Catalog Connection New Catalog Connection lets you connect to multiple geospatial catalogs that are compatible with GeoMedia Professional. This connection is then available for use with other catalog commands. You can open a cata read-write, in read-only, or in closed states. You create a catalog with the New Catalog command in GeoMedia Professional or GeoMedia. This command lets you create a new Access catalog compatible with Access 2K. You can make the following two types of connections:  Access database—Catalog is a Microsoft Access database (default), with the default connection name Access Catalog Connection , for example, Access Catalog Connection 1.  ODBC database—Catalog is located in a SQL Server or Oracle database, with the default connection name ODBC Catalog Connection , for example, ODBC Catalog Connection 1. For Access, you select the location of the Microsoft Access database file (.mdb) to which you want to establish a connection. For ODBC, you select the data source name (DSN) of the catalog to which you want to establish a connection. You then provide additional parameters for the SQL or Oracle database. The command makes the connection to the catalog with maximum permissions available to you. Initially the command tries the connection in the read-write state. If this fails it tries to open the connection in the read-only state. If a connection fails, it is added to the list of the catalog connections, but its state is set to closed. If a connection to the same database already exists, a message is displayed telling you to use the existing connection. In this case, the connection is not made. 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.

To create a new catalog connection: 1. Select Tools > Catalogs > New Catalog Connection. 2. Select Access database as the Connection type.

OR

276


Working with Catalogs Select ODBC database as the Connection type.

3. Change the default connection Name if appropriate. 4. For Access, type the complete path of the .mdb file, or select the Database file name through Browse. OR For ODBC, select the Data source name from the drop-down list. 5. Click OK.

For Access, the connection is made. OR

For ODBC, type the name and in the SQL or Oracle dialog boxes that are displayed, and then the connection is made.

Managing Catalog Connections Catalog Connections lets you manage the connection information of catalogs in a manner similar to the Warehouse > Connections command of GeoMedia Professional. This command lets you perform the following:  Make a new catalog connection.  Review a list of all available catalog connections in a GeoWorkspace.  Change the state of a catalog connection (open read-write, open read-only, or closed).  Edit the catalog connection parameters of an existing connection.  Delete an existing open or closed catalog connection. All catalog connections present in the GeoWorkspace are displayed in the connection grid on the Catalog Connections dialog box. The rows in the grid are sorted alphabetically based on the Name column. You can resize this grid as appropriate. The connection grid has the following read-only columns: Name—Catalog connection names, with an icon at the start of the cell indicating the state:

Type—Catalog connection type, Access or ODBC. Catalog—Location of the database .mdb file for an Access database or the data source name for an Oracle or SQL Server database. You can edit the location of the catalog using the Properties but not directly from the cell of the grid.


277

Working with Catalogs To create a new connection: 1. Select Tools > Catalogs > Catalog Connections.

2. Click New. 3. Select Access database as the Connection type.

OR Select ODBC database as the Connection type.

4. Change the default connection Name if appropriate. 5. For Access, type the complete path of the .mdb file, or select the Database file name through Browse. OR For ODBC, type the complete path of the Data source name, or select it from the drop-down list. 6. Click OK.

For Access, the connection is made. OR

278


Working with Catalogs For ODBC, type the name and in the Oracle or SQL Server dialog boxes that are displayed, and then the connection is made. To open or close connections: 1. Select Tools > Catalogs > Catalog Connections. 2. Select the row of the connection that you want to open or close. 3. Click Open Connection or Close Connection as appropriate.

To edit a catalog connection: 1. 2. 3. 4.

Select Tools > Catalogs > Catalog Connections. Select the row of the connection that you want to edit. Click Close Connection if the connection is open. Click Properties.

5. Change the location of the .mdb file for an Access database or the data source name for an Oracle or SQL Server database.

Importing Catalog Records Import Catalog Records lets you import catalog records from multiple sources into a read-write catalog. Thus, this command is a timesaving tool that allows the easy integration, sharing, and storage of data. To use this command, at least one read-write catalog connection must exist in the GeoWorkspace. When you select a catalog, a connection is made to the catalog if it is not already open, that is, the catalog connection is opened on-demand by the command but not during the GeoWorkspace load. You must supply a to establish a connection to the catalog if it is required. Imported records can be from the following exchange formats: GCE (GeoMedia Catalog Exchange), TXT (FGDC), and XML (FGDC or ISO-19139). You can import multiple files of the same format in a single import operation. In addition, you can apply a filter on the list of selected files. Based on the selected import format, the filter is the selected format or all files, as follows: Selected Format GCE

Filter GeoMedia Catalog Exchange Files (.gce) SMMS Exchange Format Files (.sef) All Files

TXT (FGDC)

FGDC Formatted Text files (.txt) All Files


279

Working with Catalogs Selected Format XML (FGDC)

Filter FGDC standard or ISO-19139 XML Documents (.xml) All Files

XML files can be used by different applications when they conform to a published Document Type Declaration (DTD) file or XML schema, which defines tag names and proper sequence, or to an XML schema. When importing FGDC metadata generated by other applications, Catalog anticipates that those files will use the standard FGDC metadata DTD file: FGDC-STD-001-1998 (Version 2) – link http://www.fgdc.gov/metadata/fgdc-std-001-1998.dtd. Fo. For exporting and importing ISO metadata records generated by other applications, Catalog uses the standard ISO-19139 schema – link http://www.isotc211.org/schemas/2005/. When exporting catalog records in (FGDC) XML format, Catalog uses the same DTD file, enhanced with elements included in the GM Catalog profile, that is, internal GM Catalogue metadata elements. Catalog s can process any FGDC XML metadata file through mp and can generate an output XML file that is completely compliant, along with helpful information about metadata fields that may be missing or incorrect. Other applications may generate XML files which use variants of this XML format. Therefore, Catalog s 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 through the USGS Web site at the link http://geology.usgs.gov/tools/metadata/. 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. When importing ISO-19139 XML metadata files, Catalog creates one record for each imported file, and generates a primary key consisting of a combination of the UUID within that file, or the Citation.title. 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.

280


Working with Catalogs To import catalog records: 1. Select Tools > Catalogs > Import Catalog Records.

2. Type the location from where the import files are to be read, or use Browse to select the location. 3. Select the appropriate file(s) from the Available files list. 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 in this process in the case of ODBC catalog. If the connection cannot be opened in Read-Write mode, a message is displayed because the import cannot be done on the Read-Only/Closed connection.

Hints about Importing Metadata 

The Catalog database structure will recognize s, citations, and other ―re-usable‖ components of imported metadata records if they have the same names as those s, citations, and so on, that are already in the Catalog database. Catalog will not update a , citation, or other component of existing metadata records when new (records) contain the same ―key‖ information.


281

Working with Catalogs 





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 an FGDC-formatted file, you should consult Catalog Help regarding the use of the mp utility to validate the file as part of your preparation for importing data. The import process can be aborted pressing ESC.

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

The Difference between Exporting and Publishing The Export Catalog Records command produces two kinds of metadata files. While the results may seem similar, the intent of the two groups of file types is different, as follows:  Catalog records that are ―exported‖ are intended for exchange with other Catalog s, 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 GeoMedia Catalog s. TXT files can be used for either, and XML files may be created for file exchange or – when a style sheet reference is included – for viewing. To use the Export Catalog Records command, at least one catalog must exist in the GeoWorkspace. When you select a catalog, a connection is made to the catalog if it is not already open, that is, the catalog connection is opened on-demand by the command but not during the GeoWorkspace load. You must supply a 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).

282


Working with Catalogs Each format lets you select different parameters on the Advanced tab, as follows: Export Format:

HTML

TXT (FGDC)

GCE

XML (FGDC)

XML (ISO)

Defined

√

√

-

-

-

Identification

√

√

-

-

-

Data Quality

√

√

-

-

-

Spatial Data Organization

√

√

-

-

-

Entity and Attributes

√

√

-

-

-

Distribution

√

√

-

-

-

Metadata Reference

√

√

-

-

-

Rollup empty fields

√

√

-

-

-

Include biological profile

√

√

√

√

-

Include map display

√

-

-

-

-

Sections to include:

Options:

√ √ √ Publish using style sheet Sections to include—Lets you select which FGDC metadata sections to export. Options:  Rollup empty fields—Lets you exclude all the empty metadata elements.  Include biological profile—Lets you include the metadata content belonging to biological profiles.  Include map display—Lets you include a map display of the record. This option is not applicable if the selected record is nongraphic. Publish using style sheet, displayed only for the XML (FGDC) and XML (ISO) formats—Lets you attach a style sheet to the exported data. You can type the style sheet path or browse to select the style sheet. A style sheet customizes the display of your catalog content. It is attached to the exported XML file to view the XML data in a browser. For XML(ISO) only, the core elements are published using a style sheet. Four style sheets are delivered in the \Program Files\GeoMedia Professional\stylesheets\catalogs folder: FGDC_classic.xsl, FGDC_FAQ.xsl, ViewDetails.xsl, and ISO_Stylesheet1.xsl. 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


283

Working with Catalogs file naming in Windows, these characters are replaced by an underscore ( _ ) in naming the log file. The log files are output to the export folder.

To export catalog records: 1. Select Tools > Catalogs > Export Catalog Records.

2. 3. 4. 5.

On the General tab, select the appropriate Catalog connection from the drop-down list. Select the appropriate open catalog record(s) from the Records list. Select the appropriate Export format option. Type the appropriate location where the export files are to be saved in the Export folder field, or use Browse to select it. 6. Select the Advanced tab; then set the available parameters appropriately.

284


Working with Catalogs (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 selection, Catalog will publish all XML (ISO) metadata records with a link to this style sheet. Some s 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 location—instead, type or paste in the full URL for the style sheet, such as http://www.gisdataserver.org/metadata/my_style.xls.


285

Working with Catalogs 7. Click Apply.

The status of the export for the selected records is displayed in the status bar, the selected catalog records are exported, and the files are stored in the destination folder.

Select Text Styles and Graphic File for XML Display An XSL style sheet is a file that describes how to display an XML document of a given type, and an accomplished XSL editor can control many aspects of the display of the metadata content contained in an Catalog XML record. You can control the font, colors, and size of text displayed in your XML metadata reports by editing a custom style sheet. Each of the XSL (style sheet) files supplied with catalogs is located in the \StyleSheets\Catalogs folder, and contains identical code that defines text font, color, and size used when that style sheet is used. XSL editors can use Notepad or another tool to edit the class definitions that are encoded in the beginning of the style sheet. The style sheet is initially delivered with following classes: CLASS

RENDERS

.title

Title of the report

.contents

List of sections

.sectionname

Hyper linked section names

.tag

Metadata element headings

.text

Element content of type text

.biotag

Biological element headings

.biotext

Text of biological elements

XSL editors can also eliminate the GeoMedia graphic displayed at the top-left corner of XML metadata reports, or replace it with the graphic identity of the enterprise graphic, by editing any of the style sheets delivered with GeoMedia Catalog. The four XSL files supplied with Catalog use the following graphic:  \StyleSheets\tech_geomedia.gif as the graphic file that displays by default. XSL editors can create a graphic file of similar size, located in any convenient pathname.

Associating Catalog Records Associate Catalog Records lets you link a catalog record to the dataset, which is the GeoMedia feature class or image that it describes. This allows you to do the following:  Capture certain metadata elements automatically.  Provide a visual view of your data.  Export browse graphics on the fly when generating an HTML report. To use this command, at least one catalog connection must exist in the GeoWorkspace. When you select a catalog connection, the catalog will be opened if it is not already open, that is, the catalog connection is opened on-demand by the command but not during the GeoWorkspace load. You must supply a to establish a connection to the catalog if it is required.

286


Working with Catalogs 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. ed image file formats are the same as those of the GeoMedia raster system that are georeferenced. You can associate a dataset with a catalog record as a foreground layer or as a background layer. The first dataset associated is called the foreground layer. The catalog record can be associated to a second dataset called the background layer, which helps provide a frame-of-reference for the associated dataset. For example, a dataset that displays rivers in a state is more useful if a background layer showing the state is displayed with it. Therefore, the background layer must thus have the same projection as the foreground layer. This command associates a dataset (foreground or background) to a catalog record and captures spatial-related metadata from the associated (foreground) dataset. Each catalog record can point to zero, one, or two GeoMedia feature classes, which are then used in map displays of the spatial data described by the catalog record. Associate Catalog Records also displays the available catalog record titles from the connected catalogs before making an association. Catalog record titles are displayed along with icons to indicate whether or not the catalog record already has an association with a feature class as a foreground layer, as follows: —With an associated dataset in the foreground layer —Without an associated dataset in the foreground layer In addition, this command lets you create a new catalog record. You can create an entirely new catalog record, create a blank catalog record, or create one from an existing catalog record. If the latter, the new catalog record is created, and the content of the existing catalog record with any modified FGDC sections are copied into the new one. Once created, you can then associate a dataset to the new catalog record. You can also disassociate a dataset from a catalog record and re-associate a dataset with a catalog record. Disassociating a dataset breaks the link between the dataset and a catalog record, updating the relevant metadata record of the catalog. Once disassociated, the dataset can no longer be previewed. This command also captures spatially related metadata after associating a dataset (foreground) to a catalog record. The captured information is stored in related fields in the catalog record. This allows synchronizing the captured metadata stored in a catalog to reflect changes to the associated dataset in the foreground. Captured metadata elements are the following:  Bounding coordinates—The limits of coverage of a dataset expressed by latitude and longitude values. This compound metadata element is stored in the Identification/Spatial domain section.  Attribute name—The identity of all attributes associated with the feature class. This metadata element is stored in the Entity and Attributes section.  Point and vector object information—The type and number of vector or non-gridded-point spatial objects in the dataset. This compound metadata element is stored in the Spatial Data Organization section. Finally, this command lets you view the associations and complete metadata content for a selected catalog record. Thus, you can see the spatial data captured during a capture operation.


287

Working with Catalogs To associate a catalog record as a foreground or background layer: 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 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.

288


Working with Catalogs 6. For a feature class, select the appropriate connection and Feature class to which the catalog record needs to be associated; then click OK.

OR For an image file, select the appropriate connection and image file to which the catalog record needs to be associated; then click OK.

To create a new catalog record: 1. Select Tools > Catalogs > Associate Catalog Records.


289

Working with Catalogs 2. Click New Catalog Record.

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 -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.

The metadata elements of the catalog record are updated by capturing relevant information from the associated foreground layer. To view catalog details: 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 View Details.

290


Working with Catalogs A system-ed browser window is opened, and the metadata content is displayed as an XML file using the ViewDetails.xsl style sheet.

Exploring Catalogs Catalog Explorer provides a functional and practical means for you to manage your data and metadata. This command provides a powerful tool for quickly locating and previewing datasets in your GIS data library. You can browse catalog records from multiple catalogs and locate datasets according to metadata keywords, attributes, time period, or geographic area. To use this command, at least one catalog connection must exist in the GeoWorkspace. When you select a catalog connection, the catalog will be opened if it is not already open, that is, the catalog connection is opened on-demand by the command but not during the GeoWorkspace load. You must supply a 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 tree view, and view the important metadata content, as follows:  Title and the persons for the metadata and the dataset  Preview of the map if the catalog record is associated to a feature class  Basic description  Important spatial metadata content You can define specific criteria for searching within open catalogs, and you can clear and redefine a search. This search criteria for the selection of catalog records include the following:  Contains any or none of the listed keywords  Contains any of the listed attributes  Corresponds to the time period of content  Contains the warehouse type of the associated dataset  Contained in the bounding region you select After you have executed a search based on the search criteria entered, you can view the search results as a list of catalog records. You can then load the feature classes associated with the selected catalog record(s) into an active map window. You can also view a detailed display of a catalog record.


291


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

Catalog Record and Search Result Tree Views In this section, the Available catalog records field displays all the catalog connections in the GeoWorkspace in the collapsed mode. When you expand any catalog node, a connection is made to the catalog if it is not already open, that is, the catalog connection is opened on-demand by the command but not during the GeoWorkspace load. You must supply a to establish a connection to the catalog if it is required. A selected catalog is highlighted to indicate that it is the active catalog and that it can be expanded to view the catalog records. You can only select one catalog record at a time. When you select a catalog record, the metadata summary of an active record is displayed in the first four tabs to the right of the tree view. The icon to the left of each catalog record indicates whether or not the item is already associated with a feature class, as shown below:

292



—With associated dataset in the foreground. Both the dataset and metadata are available to preview.

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

The Search results tree view 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 tree view and in the Search results tree view is synchronized. Thus, if you select one catalog record in the Search results tree view, the same item is highlighted in the Available catalog records tree view 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 tree view, the corresponding item in the Search results tree view 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 tree view and the Search results tree view, and no metadata summary is displayed in the tabs.


293


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

294



Catalog Explorer Tabs The five Catalog Explorer tabs in the left section of the dialog box let you browse and search catalog records. These tabs are the following: Description, Identification, Spatial, Attributes, and Search. All the tabs except the Search tab are summary tabs. You define the search criteria on the Search tab and review the results on the summary tabs. The Search tab is always enabled, but the behavior of the summary tabs varies. The summary tabs are:  Disabled when you only select a catalog connection node.  Enabled when you select one catalog record having an association from the Available catalog records or Search results.  Enabled when you select one unbound record (having no foreground association) from the Available catalog records or Search results.  Enabled when multiple records are selected in Search results, and the content for the selected catalog record of the available records tree view is displayed.  Selecting a catalog record from the Available catalog records tree view, 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 that your warehouse-connection parameters are correct and try again.‖ Description tab—Displays the Abstract, Purpose, and Supplemental metadata elements. These elements are displayed in their respective read-only fields.


295

Working with Catalogs Identification tab—Displays important metadata elements of the Identification section: Dataset , Metadata , Theme keywords, Place keywords, keywords, Stratum keywords, Temporal keywords, Time period, Access constraints, Use constraints, Dataset credit, and Native dataset environment. Keywords may consist of one or more words and are separated by commas (,).

Spatial tab—Displays a map preview of the associated feature class of the selected catalog record. A catalog record can have two feature classes associated to it, one to display the foreground layer and one to display the background layer. The map control is disabled if either of the following two conditions exists:  The metadata has no associated feature class for the foreground layer.  The selection is on a catalog node in the Available catalog records tree view. To the left of the map is a toolbar that lets you display and browse the map content. Show Map—Display map or data, if available. Zoom In—Zoom in on features. Zoom Out—Zoom out from features. Pan—Pan map features. Full Extent—Display full extent (fit all) of the map.

296


Working with Catalogs 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.

The projection of the displayed map is always predefined as geographic, and the symbology is also predefined and hard coded.


297

Working with Catalogs Attributes tab—Displays all the Attribute labels and their Attribute definition for the entity named captured. FGDC metadata can contain multiple entities for the dataset it is explaining. An entity contains multiple attributes. Each attribute has a name, a value, and several associated properties. The attributes of the associated feature class are captured and placed under an entity named captured.

Search tab—Contains two subtabs, Text/Data Criteria and Spatial Criteria, that let you enter search criteria to search for metadata. You can search on the following criteria: 

Keywords



Time period



Attributes



Geographic area

The Text/Date Criteria tab contains the following frames: Keywords, Attributes, Not containing keywords (excluded), Associated dataset type, and Time period of content. The Keywords and Attributes frames let you enter a list of keywords or attributes. The search process finds the catalog records containing one of the keywords or attributes from the list. Clicking Add appends the new keyword or attribute to a list. The excluded frame finds the catalog records not containing the keywords from the list.

298


Working with Catalogs 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.

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.


299

Working with Catalogs 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:

.

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 tree view. 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.

300


Working with Catalogs To explore catalogs: 1. Select Tools > Catalogs > Catalog Explorer.

2. Select the appropriate catalog connection to display the tree view 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.


301


Sample Catalog Explorer Workflows A client has called to ask if you have any data for highways in the U.S. You plan on trying to do a GIS-based search for this data with no metadata. However, it is difficult to navigate through the data because there are over 50 features on the legend with names that are not descriptive. When you display a dataset in the map window, it is also difficult to know its quality. Therefore, you have decided to perform a metadata-based search using the Catalogs commands in the following workflow: 1. Start Catalog Explorer, which is your query and display tool for geospatial metadata catalogs. The GIS data stored in the USSampleData.mdb warehouse is described by metadata records that are stored in Catalog_Samples.mdb. 2. Next, use the Available catalog records tree view to expand the USSampleData connection. This results in a list of the catalog records being displayed. You can easily find datasets with this approach because the catalog record names are more descriptive than the feature class names in the legend. In addition, the summary tabs provide information about the dataset, such as abstract and purpose. 3. Select the record named Highway Interchanges -- USA_Sample_Data for GM6.0 to view the corresponding metadata elements. 4. To load the selected dataset into GeoMedia, use Load Feature Data.

Another client has called to ask if you have any U.S. data in your warehouses of worldwide feature classes. To perform a search on all of the feature classes described in the catalog, you select the Search tab and then the Spatial Criteria subtab. Define a region around the U.S. in the displayed map – zoom in, if you would like. Then click Search, which generates a search result set based on the bounding region. 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.

302


Working with Catalogs Notice that the feature classes appearing as Search Results is reduced; you have generated a search result set based on the spatial selection and on the keyword. 2. The client is happy you found the data, but now has asked you to provide a digital copy of the data in HTML format. To do this, use the Export Catalog Record command, selecting the catalog records included in your search results as the metadata to export. Then select the HTML export format (keeping the advanced defaults and including the map display), and then perform the export. 3. You were quickly able to query and to display for the client key information on U.S. geospatial datasets that are related to highways. Your client is really seeing the value of metadata management.

Glossary of Catalog Terminology The following is a list of useful when working with catalogs: Catalog: A database that serves as a repository of metadata records. Also termed a metadata database. Dataset: GeoMedia feature class or image file associated with a metadata record. The metadata record stores the connection and other information related to the feature class associated with a metadata record. According to the ISO-19115 Metadata standard: ―A dataset may be a smaller grouping of data which, though limited by some constraint such as spatial extent or feature type, is located physically within a larger dataset. Theoretically, a dataset may be as small as a single feature or feature attribute contained within a larger dataset. A hardcopy map or chart may be considered a dataset.‖ FGDC: U.S. Federal Geographic Data Committee, which s the ―Content Standard for Digital Geospatial Metadata.‖ See the link http://www.fgdc.gov/metadata. GCE: GeoMedia Catalog Exchange. A file format for the exchange (export and import) of metadata records among GeoMedia Catalog s. Geospatial Catalog: See Catalog. Geospatial Metadata: Data that describes the content, quality, condition, and other characteristics of geospatial data. ISO: International Organization for Standardization, which is the world's largest developer of standards. An ISO technical committee is responsible for the development of ISO-19115 and ISO-19139, which are international standards and technical specifications prescribing the content and expression of geospatial metadata. See the link http://www.isotc211.org. Metadata: Information about data. For the purposes of this document, see Geospatial Metadata. Metadata element: A data element is a logically primitive item of metadata. A compound metadata element is a group of logically related data elements and other compound elements. Metadata record: A single logical entity, which is a collection of related data (metadata elements) describing geospatial data. A key field (title) identifies each metadata record uniquely within a catalog. SEF: SMMS exchange format. A file format for the import of metadata generated from legacy Intergraph metadata products.


303


Software Delivery GeoMedia Catalog functions will be delivered as part of GeoMedia Professional by using the default delivery folder of C:\Program Files\GeoMedia Professional. These are referenced as ― ‖ in the remainder of this section. GeoMedia software components will be delivered to the folder \Program. GeoMedia Catalog functions require the delivery of database(s), style sheet(s), and other files that will be located in the structure detailed in the following table. Catalog Components Delivery Table Files/Folders

304

Description

Location

CatalogTemplate.mdb

Template access Catalog required for \Templates\Catalogs the New Catalog command.

Catalog_Samples.mdb

Sample Catalog required for the New :\Warehouses\Catalogs Catalog Connection command.

World.mdb

GeoMedia warehouse used in the Catalog Explorer command as the default search map.

Oracle Scripts

Template scripts required for creating \Program Oracle catalogs.

SQLServer Scripts

Template scripts required for creating \Program SQL Server catalogs.

FGDC_classic.xsl, FGDC_FAQ.xsl, ISO_Stylesheet1.xsl, View_Details.xsl

Style sheets used to View a Catalog \StyleSheets\Catalogs Record, and to publish record(s) using the Export Catalog Records command.

tech_geomedia.gif

Default graphic file displayed by XML \StyleSheets\Catalogs style sheets.

FGDC_to_ISO.xslt, FGDC Dataset Metadata Profile.pdf

\Program 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.

:\Warehouses


SECTION 10

ing 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 “SmartSnap” in the “Working with Features” section.

Performing Digitizer Setup Digitizer Setup allows you to configure GeoMedia Professional to receive input from a digitizing device for creating and editing features. Once you have created this configuration, the digitizer setup, you can save it for future use, and then edit, report on, and delete the saved setup. This is a representative workflow for setting up a digitizer: 1. Install the digitizer software, and attach the digitizer tablet and digitizer cursor. 2. Attach your paper map to the digitizer tablet. 3. Collect the appropriate control-point pairs. (A minimum of three pairs is required.) 4. Check the calculated error, and make any necessary corrections. 5. Add a name and an optional description to the new setup. 6. the new setup.

ed Digitizers GeoMedia Professional only s digitizer tablets that are Wintab32™ compliant. To find out if a WinTab-compliant driver is available for your digitizer, see the documentation that came with the tablet or the manufacturer. After installing the driver software, use the WinTab manager setup program to configure the buttons on your digitizer puck. One puck button should be configured to perform a left mouse click to digitize points and vertices; another button should be configured to perform a left double click to finish digitizing line or polygon features. You may also want to configure a button to perform a right click so you can access context menus. How this is configured depends on the digitizer you are using. For additional information on configuring the digitizer, visit the tablet vendor's site. To avoid the most common digitizer problems, that you install the latest available Wintab32 driver and perform the installation according to the tablet vendors instructions.


305

ing Data

Collecting Control-Point Pairs Setting up the digitizer involves creating control-point pairs (X and Y coordinate values) required to a digitizer device to a map view. A control point-pair is a point on a map for which an accurate easting, northing or geographic coordinate is known, and its corresponding X,Y location on a digitizer tablet. A minimum of three control-point pairs are required for registration. Control-point pairs allow the software to determine a mathematical transformation between the digitizer surface and the coordinate system in the map window and to help ensure more accurate digitizing. The New Digitizer Setup dialog box contains the X and Y coordinates of the digitizer control points (source) and the X and Y coordinates of the real-world location, map easting and northing, for the corresponding control points (target). You can use the vector snap and/or raster snap tools to snap to existing geometries when interactively placing control points in a map window.

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.  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,

306


ing Data 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. 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. 2. 3. 4. 5.

Secure your paper map to the digitizing surface of your digitizer. Select Tools > Digitizer Setup to display the Registrations dialog box. Click New to display the New Digitizer Setup dialog box. Click Edit Source to close the dialog box and to display placement prompts. Click an appropriate point on the digitizer to place digitizer control point 1.

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. 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.

10. 11. 12. 13.

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. Select the Type column in the grid to remove pairs with a high calculation error. Type an appropriate name and an optional description for the digitizer setup in the Name field on the New Digitizer Setup dialog box. Click to save and to apply the digitizer setup. that the setup was successful with the name appearing in the list on the Registrations dialog box.

To create a new digitizer setup by entering tablet and map control-point pairs: 1. 2. 3. 4.

Secure your paper map to the digitizing surface of your digitizer. Select Tools > Digitizer Setup. Click New on the Registrations dialog box. Click Add Points on the Digitizer Setup dialog box.

The dialog box is closed. 5. Click on an appropriate point on the digitizer to place digitizer control point 1. 6. Click to place the corresponding map control point 1 on the map. 7. Continue placing control-point pairs until you have entered them all; then press the digitizer cursor key assigned to the left double click action to complete source point placement.


307

ing Data The New Digitizer Setup dialog box is opened, with the X,Y coordinates of the placed digitizer control point displayed. 8. 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. 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 to save and to apply the digitizer setup. 12. that the setup was successful with the name appearing in the list on the Registrations dialog box.

To edit control points before applying setup: 1. Select Tools > Digitizer Setup. 2. Click New on the Registrations dialog box to create a new digitizer setup. Continue with Step 3. OR Select a digitizer setup from the list on the Registrations dialog box to edit an existing setup. Go to Step 4. 3. Collect control points by one of the four methods from the previously described new digitizer setup procedure. 4. Edit the control points by performing the following, as appropriate:  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 control-point target value). 5. Click to save and to apply the digitizer setup.

To perform a digitizer setup by applying an existing setup: 1. Select Tools > Digitizer Setup. 2. Select an existing digitizer setup from the list on the Registrations dialog box. 3. Click Edit to display the Edit Digitizer Setup dialog box; then retype the tablet control points, or use Edit Source, if the paper map has been moved on the digitizing tablet; then click . OR If you do not need to re- the tablet control points, click .

To report on a digitizer setup: 1. 2. 3. 4.

308

Select Tools > Digitizer Setup. Select an existing digitizer setup from the list on the Registrations dialog box. Click Report. Type a filename and location for the report file on the Save As dialog box; then click OK.


ing Data To delete a digitizer setup: 1. Select Tools > Digitizer Setup. 2. Select an existing digitizer setup from the list on the Registrations dialog box. 3. Click Delete.

Setting Digitizer Mode Setting the digitizer mode allows you to define the behavior of the digitizer cursor as screen mode or digitizer mode. In screen mode (with the Digitizer Mode item on the Tools menu unchecked, the default), the digitizer cursor has access to the entire monitor screen and behaves like a mouse cursor. In digitizer mode (with the Digitizer Mode menu item checked), the cursor has access to only open map windows and cannot access menus. You must be in digitizer mode to digitize from a paper map using a digitizer registration. When you move the digitizer on the digitizer tablet in this mode, the distance is translated to a real-world distance in the map window on the registration created with Digitizer Setup. You can only set the digitizer mode when you have a digitizer attached, and you can only have one mode active at a time. In digitizer mode, the cursor can move out of the map window if the digitizer tablet area is bigger than the window area. In this case, the cursor disappears from the screen. You can still place points with the digitizer, but they will not be visible at the current view extents of the windows. Before you can use your cursor in digitizer mode, you must have the following:  Digitizer installed on startup  Digitizer tablet attached  Digitizer setup ed  Active map view

To set digitizer mode to add features: 1. 2. 3. 4. 5. 6.

Secure your paper map to the digitizing surface of your digitizer. Start GeoMedia Professional. Use Digitizer Setup to your paper map to a map window. Select Tools > Digitizer Mode to change it to digitizer mode (checked). Select Insert > Feature with the digitizer puck, and select a feature to digitize. Digitize the selected feature(s).

Digitizer Button Mapping In general, if a digitizer button has been mapped to a mouse action outside of GeoMedia Professional (for example, by using the tablet manufacturer‘s own software), the mapping takes precedence, and the tracker tool ignores the button. Buttons 0-3 are mapped as specified through the setup software provided with your digitizer tablet. Buttons 4-15 are mapped to specific buttons or sequences of buttons by the tracker software. Buttons 4-9 are mapped to specific system buttons as specified in this section. Buttons 10-15 are mapped to specific key sequences as specified in this section. The following is the recommended button mapping to meet all GeoMedia Professional requirements:


309

ing Data Button Number

Recommended Wintab32 Mapping

0

Left Click

1

Left Double Click

2

Left Drag

3 (if present)

Right Click

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.

Buttons 3 and Higher With more than three buttons, you can do the following:  Allow more types of mouse events to be mapped using Wintab32.  Add other keys used in placement and editing (TAB, BACKSPACE, DELETE).  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. 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.

310

Button Number

Recommended Wintab32 Mapping

3

Exit to screen mode (Right click in screen mode)

4

Send ESC (To terminate command)

5

Send SHIFT keymask

6

Send CTRL keymask

7

Send TAB

8

Send <- (Backspace)

9

Send DEL

10

Send CTRL+ALT+Z (Zoom In suggested)

11

Send CTRL+ALT+Y (Zoom Out suggested)

12

Send CTRL+ALT+X (Fit All suggested)

13

Send CTRL+ALT+W

14

Send CTRL+ALT+V

15

Send CTRL+ALT+U


ing Data

ing Images Image Registration allows you to a selected image by creating a new registration or applying an existing registration. Creating a new image registration involves ing 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- a selected image by editing the registration originally used to 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 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- it, and you must it manually with the 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. 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.

To an image by creating a new registration: 1. Insert an image into your GeoWorkspace. 2. Place the image you want to in a select set. 3. Select Tools > Image Registration.


311

ing Data 4. Click New.

5. Collect control-point pairs using the following available options:  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 to the image. OR Click Save to save the registration without ing the image.

To an image by applying an existing registration: 1. 2. 3. 4.

Select the image you want to . Select Tools > Image Registration. Select the appropriate registration from the list on the Registrations dialog box. Click .

To re- an image by editing its registration: 1. Select the image you want to re-. 2. Select Tools > Image Registration. 3. Select the registration originally used to the image from the list on the Registrations dialog box.

312


ing Data 4. Click Edit.

5. Make the required changes in the registration. 6. Click to re- the image.

To edit a saved image registration: 1. 2. 3. 4. 5.

Remove any images from the select set. Select Tools > Image Registration. Select the appropriate registration from the list on the Registrations dialog box. Click Edit. Make the required changes in the registration on the Edit Registration dialog box; then click Save.

To report on an image registration: 1. 2. 3. 4.

Select Tools > Image Registration. Select the appropriate registration from the list on the Registrations dialog box. Click Report. Type the appropriate folder and filename on the Save As dialog box; then click OK.

To delete an image registration: 1. Select Tools > Image Registration. 2. Select one or more registrations from the list on the Registrations dialog box. 3. Click Delete.

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 ed 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 GeoTIFF-formatted image files.


313

ing Data 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 GeoTIFF 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 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 ed by Output to GeoTIFF. See the “Coordinate System Information” appendix for a list of ed 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. the image with Image Registration to the correct geographic location. 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.

ing Vector Data Vector Registration allows source vector data to be transformed to match a set of already correctly ed target (base) features in a map. This tool is useful in situations where input features either do not have any projection information, such as a local coordinate system, or where discrepancies exist between the input data registration and the base data, such as a result of different accuracy of data collection. Thus, you can adjust (rotate, move, and scale) survey data to better fit with the surrounding parcel data in your master database. You can define a new vector registration or select an existing registration from a set of previously defined saved registrations. You can also edit, report on, and delete saved registrations. With Vector Registration, you can select a source feature class to be ed, selecting by feature name, and apply a transformation to its geometry. This tool s the Affine and Helmert transformation models, which require a minimum of three or two control-point pairs, respectively. Each pair must consist of one point from the source and one point from the target. This tool displays the residual value (the difference between the transformed source point and its corresponding target point) for each point pair whenever the number of control points meets or exceeds the minimum number for the transformation. Also displayed is an RMS (Root Mean

314


ing Data Square) value (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. Vector Registration produces two types of output, review and feature class, whose display style you can customize for optimum results. Review output allows you to view the data in an appropriate style to the that the registration is correct, and to make changes if it is not, before performing the actual transformation. Feature output allows the source data to be transformed directly into a feature that is stored in the target connection, which must be read-write. This is useful if the transformation has already been verified and there are many vector features to be ed. Certain conditions apply to storing the output in an existing feature class. For example, the source and target attribute lists must be compatible, that is, the source attributes must be a subset of the attributes of the target feature and have the same type definitions. Also, any unique key field cannot have duplicates in the target feature after the new features have been added. 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 ing 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 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. 3. 4. 5. 6.

You can further specify features with connection filters or any query conditions. Connect to the target warehouse/server as read-write. Open a target map view. Display various target features in the target map view. Select Tools > Vector Registration.


315

ing Data 7. Click New.

8. Click Add Points; then follow the prompts to 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. Select the correct source feature class from the Transform features in drop-down list. 12. 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.

316


ing Data 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.

To report on a vector registration: 1. 2. 3. 4. 5.

Connect to an appropriate warehouse. Select Tools > Vector Registration. Select the appropriate registration from the list on the Registrations dialog box. Click Report. Type the appropriate folder and filename on the Save As dialog box; then click OK.

To delete a vector registration: 1. 2. 3. 4.

Connect to an appropriate warehouse. Select Tools > Vector Registration. Select the appropriate registration from the list on the Registrations dialog box. Click Delete.


317

ing Data

318


SECTION 11

Editing Features and Geometries GeoMedia Professional provides various tools that allow you to edit features and feature geometry. With these tools, you can perform the following functions: Change feature attributes

Delete features

Update feature attributes

Edit geometry

Update feature attributes using text

Spin geometry

Change feature class

Rotate geometry

Copy features

Move geometry

Copy features parallel to other features

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” section.

Editing in a Map Window When digitizing or editing data in GeoMedia Professional, you must ensure that the GeoWorkspace coordinate system matches the coordinate system of the feature class being edited or digitized. Failure to do so can result in data that contains incorrect coordinates. GeoMedia Professional will compare the workspace coordinate system to the coordinate system of the feature you select for editing and will warn you if there is a mismatch with the following message (it will be up to you to rectify the mismatch): ―Coordinate System Mismatch Warning! The current GeoWorkspace coordinate system and the coordinate system of the feature being created/edited do not match and could cause data integrity problems. You should set the GeoWorkspace coordinate system to match the coordinate system of the feature being created/edited.‖

Changing Attribute Values of Features You can change the attribute values of features either in a map window or in a data window. In a data window, you use standard Windows editing tools and the Clipboard to cut, copy, and paste text in cells. You cannot, however, edit hidden cells or cells containing hypertext. In the map window, you use the Attributes tab of the Properties dialog box, displayed by selecting Edit > Select Set Properties.


319

Editing Features and Geometries Attributes Tab The Attributes tab lets you review and edit the attribute values of features. On this tab, all required fields are indicated by the value in the Name column appearing in bold, red type. All key fields are likewise indicated by the value in the Name column appearing in bold, red type (because key fields are also required fields) and by the value‘s being underlined.

Tooltips When you hover the cursor over a cell in the Name column, a tooltip displays the attribute description defined through the Feature Class Definition command. If no attribute description was defined, no tooltip appears. When you hover the cursor over a cell in the Value column, a tooltip displays the data type and the default value of the column. If there is no default value, the tooltip displays only the appropriate data type string from the table. If there is a default value, the data type string is followed by the string ― : Default = ― and then by the actual default value string supplied by the data server. If the default value string is a literal value of the correct data type for the attribute, it is formatted according to the display rules for the field (honoring the format and precision properties, regional settings as appropriate, custom Boolean wording, and so forth), as seen in the following example: Text (20) : Default = Alabama Memo : Default = This is a default value for a memo field. Integer : Default = 5 Double : Default = 123.456,789 Currency : Default = $ 1,200.50 Boolean : Default = Yes Date : Default = 01-May-2000 If the default value string is not a literal value of the correct data type for the attribute, it is displayed in its native form as provided by the data server. This may occur when, for example, the default value is an autonumber or is to be calculated through a database procedure, as in the following example: Integer : Default = AutoNumber Date : Default = TRUNC(SYSDATE)

To use the Properties dialog box: 1. Select one or more features as a select set. 2. Select Edit > Select Set Properties. 3. Optional: Resize the dialog as desired through standard Windows resize operations.

320


Editing Features and Geometries 4. Position the pointer over the appropriate item for your task to display the tooltip.

In this example, ID is a required field. The cursor is hovering over the word Alabama in the Value column, thus the tooltip shows the data type of the field, the size (because it is a text field), and the default value. To change attribute values of features in a map window or data window: 1. In the map window, select a single feature you want to change. OR In the data window, select the row of the feature you want to change. 2. Select Edit > Select Set Properties. 3. On the Attributes tab of the feature‘s Properties dialog box, edit the attribute values and click OK. You could also double click the select set, which amounts to triple clicking a feature, or right click a select set and select Properties from the right mouse menu.

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.


321

Editing Features and Geometries 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 "Working with Data Windows."

Updating Feature Attributes The Update Attributes command lets you update the attribute values for multiple features within a feature class automatically rather than one at a time. This command is a powerful tool for updating the database schema to optimize the attribute data. It is especially useful for cleaning, altering, and adjusting data brought in from other sources. You can use this command on a feature class, reference feature, categorized feature, query, or select set object. When entering constants for columns with a data type "date" assigned, you must enter the information in the form "Date(yyy,mm,dd)". For Boolean fields, you must enter 0 for False and 1 for True, or use one of the logical functions from the Expression dialog box. The following are some example uses of this command:  Changing constant values in the database.  Asg a new default value throughout the database.  Asg a value to empty fields throughout the database.  Trimming trailing spaces from text fields.  Compressing geometry from the MGE/DGN format into an optimal GeoMedia format. This command lets you update the attributes in several ways:  Typing a constant value (such as 5 or ‗Smith‘) or a combination of values into the Value field(s) of the Update Attributes dialog box.  Typing a simple mathematical expression into the Value field of the dialog box.  Right clicking in any Value field to open a right mouse menu with the options Length, Area, and Perimeter, then selecting one of these to append the corresponding fully qualified expression (the optional arguments in these cases are provided) to the value string. The constant name is displayed, for example, if Square Miles is the unit for processing areas, SquareMile is displayed in the field.  Creating a functional attribute expression in the Expression dialog box, accessed through Update Attributes. 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

322


Editing Features and Geometries 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 functional attribute expressions by the Functional Attributes, Aggregation, and Analytical Merge commands. Update Attributes is a database update tool that actually changes the original data. The other three commands produce queries to form additional data. Consequently, you must be careful when udate Attributes because it physically changes the data stored in the database and the original data cannot be restored. Update Attribute updates the database record only when the command is run so the attribute is static. For example, update an attribute called SALES_DATE using the NOW function. The resulting time value in the database remains constant until you run the command again.

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 “Analyzing GeoMedia Professional Data” for information on functional attributes.


323

Editing Features and Geometries To update feature attributes: 1. With a GeoWorkspace open with a connection to a read-write warehouse, select Edit > Attribute > Update Attributes.

2. Select an appropriate existing feature class, reference feature, categorized feature, query, or select set object from the Update features in treeview. 3. Select the appropriate attribute(s) from the Attributes to update list; then type the update value(s) and/or expressions into the corresponding Value field(s), or use the right mouse menu for standard functions to calculate area, length, or perimeter.

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.

324


Editing Features and Geometries 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.

5. Optional: Uncheck the Enable undo and logging check box. Undo will not be available after features are updated when this option is unchecked. 6. After forming expressions and/or entering values for all the features you want to update, click Apply to compute and to update the values. 7. Optional: Press ESC to stop updates.

Updating Feature Attributes Using Text Update Attributes Using Text allows you to update feature class attributes using spatially related text or label features. These attributes can be either character or numeric. You can use this command on features in feature classes, queries, categories, reference features , and select sets. The updating is performed by copying the text string stored in the geometry of the feature into the selected column in the output feature class or query. If the output feature class is an area feature class, the text from the text feature whose origin falls within the area is used to update the output feature class attribute. If the output feature class is a point, linear, or text feature class, the text of the closest text feature is used to update the output feature class attribute. The closest text feature is determined by the distance specified in the Options area of the dialog box. If the closest text feature contains geometry collection, the text from first geometry in the collection is used to update the feature class attribute. 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 data-collection workflow, the geometry and attributes are collected separately, and the conversion operator types text that represents the key for ing them together.


325

Editing Features and Geometries This command allows you to load text onto spatially related features so that you can use this as the key for ing to a database table. This command detects the following error conditions and writes them to a log file: Area Features  No text features found inside an area.  Multiple text features found inside an area.  Area feature has invalid or null geometry. Linear, Point, and Text Features  No text features found within the distance of a line feature.  Multiple text features found within distance of a line feature.  Linear feature has invalid or null geometry.  No text features found within distance of a point feature.  Multiple text features found within distance of a point feature.  Point feature has invalid or null geometry.  No text features found within distance of a text feature.  Multiple text features found within the distance of a text feature.  Text feature has invalid or null geometry.

To update feature attributes using text: 1. With a GeoWorkspace open with a connection to a read-write warehouse, select Edit > Attribute > Update Attributes Using Text.

2. Select an appropriate existing geometry feature class, query, reference feature, category, or select set object from the Update features in treeview. 3. Select an appropriate character or numeric attribute from the Attribute to update drop-down list. After selecting an attribute, hovering the cursor over the attribute name displays a tooltip indicating the type of field selected. 4. Select an appropriate label feature class or query (the text to use to update) from the Update text from drop-down list.

326


Editing Features and Geometries 5. When loading text to point, linear, or text features, type the appropriate search distance, and/or select the unit of measure from the drop-down list of the Distance field. This field is disabled for area features. 6. Change the default error filename if appropriate, and/or click Browse to select a different location. 7. Click Apply.

The attribute is updated for the feature class or query in the database, a message with the number of features in the feature class updated is displayed, and any errors are written to the error file.

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 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.

Defining the Attribute Copy Before you can copy attributes between features, you must establish the source and the target feature classes, reference features, categories, and queries, and which attribute fields will be copied from one to the other. You achieve this using the Copy Attributes Definition command. You then use the Copy Attributes command to perform the actual copy. The target feature class must be read-write, but the source can be read-write or read-only. Copy Attributes does not allow the adding of new fields in the case of a query‘s being selected as the target. Copy Attributes Definition selects the attributes available in the source feature class, reference feature, category, or query whose values are to be copied to a target feature class, reference feature, category, or query. This information is then used by the Copy Attributes command to perform the copy. You can select the target feature class from all currently open read-write connections or updateable queries to which the attributes are to be copied. You first select the source feature class from a currently open read-only or a read-write connection from which the attributes are to be copied to the target feature class. If any of the selected attributes do not already exist in the target feature class, the metadata for these attributes is added to the target feature class definition. Copy Attributes does not allow the adding of new fields in the case of a query‘s being selected as the target. Geometry fields are also available for selection.

Field Validation and Metadata Creation Often the attributes in the source and the target feature classes will be different in some way. Attributes may exist in one feature class and not the other, or the attribute metadata may be slightly different between the two feature classes. The attributes are displayed in the Attributes to copy list on the Copy Attributes Definition dialog box. These attribute fields can be divided into the following two cases:  Group 1—Attributes 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 2—Attributes 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


327

Editing Features and Geometries 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 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 with type gdbLongBinary and gdbSpatial with subtype gdbCoverage  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:  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

328


Editing Features and Geometries 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.

To select/unselect all attributes, click Select All or Unselect All.


329

Editing Features and Geometries If the selected attributes do not exist in the target feature class, the New Attributes dialog box is displayed to either create or not create field metadata in the target feature class.

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.  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.

330


Editing Features and Geometries The following are examples of area merge conditions:

If the features are not adjacent, merging the features creates a single feature with discontiguous geometry.

The following are examples of line merge conditions:

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 “Analyzing GeoMedia Data” 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 command‘s dockable control.

You can also use construction aids to construct the points for digitizing the split geometry.


331

Editing Features and Geometries See “Using Construction Aids” in the “Working with Features” section.

Split by Polyline Mode This mode (the default) lets you split a selected linear or contiguous areal geometry into two separate features by specifying a polyline about which the original geometry is to be divided. You split area features by digitizing an intersecting line across the selected feature. You can use existing geometry when digitizing an intersecting line. Splitting occurs along the intersection of the split line and the feature to be split. For areas, this is the portion of the line that intersects the face of an area.

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” sections for more information on these tabs.

Splitting Area Features The following cases are split feature conditions for area features: Case 1: The split line intersects the area boundary at two points.

Solution: The area is split into two features. Case 2: The split line crosses the area boundary at more than two points.

Solution: This is a value split. The area is split into three area features.

332


Editing Features and Geometries Case 3: A split line intersects two area boundaries at two points each.

Solution: The two areas are split into six features. Case 4: Given an area with a hole, the split line is snapped to the boundary only.

Solution. The hole is converted to an area boundary. Case 5: Given an area with a hole, the split line snaps to the boundary in one location.

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 area is split into four features.

Splitting Line Features The following cases are split feature conditions for line features: Case 1: The split point intersects a feature.

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.

Solution: The line is split into multiple lines at the intersection points.

Splitting and Maintaining Coincidence If the Maintain coincidence option on the Placement and Editing tab is selected, any features coincident to the split features will have vertices inserted at the snap points.


333

Editing Features and Geometries The following example is a split feature condition for maintaining coincidence in which the split line snaps into area and coincidence line geometry.

Line B is coincident with the portion of the boundary of Area D. Solution with coincidence on: Line B is split by a vertex only.

Solution with coincidence off: Line B is not split in any way; coincidence is broken.

Split by Polygon Mode This mode primarily lets you split either a heterogeneous or homogeneous geometry collection. You can, however, also use this mode for a single linear or areal geometry. When you digitize a split polygon for a split operation, the portions of the original geometry that fall inside the polygon are assigned to the original feature, and the portions of the original geometry that fall outside the split polygon are assigned to the new feature. The following example illustrates the use of the split polygon mode:

A

B

C

A—Original feature, containing a homogeneous geometry collection of four discontiguous area geometries. B—Original feature geometry with a split polygon shown, specifying the desired partitioning of the geometries. C—Result 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).

334


Editing Features and Geometries

Split by Point Mode You use this mode only when splitting a simple linear geometry feature. To use this mode, you move the cursor to a point along a linear feature to identify the location at which you want the split to occur; this point is then highlighted.

To complete the split you simply click to split the geometry at the highlighted point.

Split by Existing Features This mode lets you select one or more existing features to be used as the split geometry. You can select the split features by clicking on them, by a fence select, or by a combination of both. PickQuick makes feature selection easy in congested areas. The fence select honors the Inside or Overlap fence mode on the select toolbar. When the cursor is hovering over features, only point, linear and area features are highlighted, and only a highlighted feature can be selected. Likewise, a fence select ignores all the text features and the feature selected to be split. You can select more than one split feature by holding down CTRL or SHIFT during each click or each fence select. You can also deselect a feature by clicking on it again while holding CTRL or SHIFT. All features are deselected when you click in the map window where there is no feature. You can perform the split by double clicking or by selecting Perform Split from a right mouse menu. The following figure shows a fence select along with the right mouse menu.

To split features with simple geometries: 1. 2. 3. 4. 5.

Place a feature containing a simple linear or areal geometry in a select set. Select Edit > Feature > Split. Select the split by polyline mode on the dockable control. Place the first point of the line that will intersect the feature by clicking the left mouse button. Place the next point(s) of the intersecting line, or place the final point by double clicking the left mouse button.

If the Use existing geometry when digitizing option has been selected on the Placement and Editing tab of the Options dialog box, a portion of a bisecting feature that extends across the feature can be used to split the features. While digitizing the split line, snap to a bisecting feature at two points, and the portion of the bisection feature between them will be highlighted. If this option is not selected, a straight two-point line will be highlighted, ignoring the bisecting feature. 6. Optional: You can terminate the split by pressing ESC.


335

Editing Features and Geometries 7. If the Display Properties dialog box for new features option is selected on the Placement and Editing tab, type the attributes for each of the new features in the Properties dialog box as it is displayed for each feature (the attributes that appear in the Properties dialog box are the attributes of the original feature). 8. Click OK. Precision key-ins may be used at any time instead of clicking with the left mouse button to place the feature.

To split feature containing geometry collections: 1. Place a feature containing a geometry collection, having any combination of geometry types, in a select set. 2. Select Edit > Feature > Split. 3. Select the split by polygon mode on the control. 4. Digitize the split polygon. 5. Double click to complete the digitization of the split polygon and to perform the split operation.

To split a linear feature with the split by point mode: 1. 2. 3. 4. 5.

Place a feature containing a simple linear geometry in a select set. Select Edit > Feature > Split. Select the split by point mode on the dockable control. Move the cursor to the point on the feature at which you want to perform the split. Click to perform the split operation on the geometry at the highlighted point.

To split features with the by existing features mode: 1. 2. 3. 4. 5.

Place a feature in the select set. Select Edit > Feature > Split. Select the split by existing features mode on the dockable control. Select one or more features that would split the feature. Double click or right click and select Perform Split to perform the split.

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

336


Editing Features and Geometries 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 copy only the selected features or copy the selected cells during the command instance.

To copy features (object-action mode): 1. Select one or more features. 2. Select Edit > Feature > Copy. 3. Click to place a source point for the copy. OR Type the coordinate value of the source point in the Precision Coordinates dockable control and press ENTER.

The writable selected feature(s) appear in dynamics on the cursor. Any read-only features in the select set do not appear in dynamics. 4. Move the cursor to the appropriate destination. 5. Click to place the feature(s). OR Type a destination point and press ENTER.

If there are no required unique attribute values and the Display Properties dialog for new features option is turned off, the selected feature(s) are copied and again appear in dynamics. Go to Step 8.

If there are required unique attribute values and/or the Display Properties dialog for new features option is turned on, dynamics are turned off for all features, and the first read-write feature in the select set is highlighted. The Properties dialog box for the first read-write feature in the select set is displayed. Continue with Step 6. 6. Type the appropriate attributes on the Properties dialog box. Pressing Cancel or ESC when the Properties dialog box is open displays a message asking if you want to discard the current feature copy or all subsequent copies.

The feature is copied, and the Properties dialog box is displayed for the next feature. 7. Repeat Step 6 for each read-write feature in the select set.

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.

Copying Features Parallel to Other Features Copy Parallel allows you to copy a linear, area, or compound feature class; reference feature; category; or query and offset it to a specified distance from the original feature.


337

Editing Features and Geometries 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 box 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” sections 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. 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. 338


Editing Features and Geometries 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.

The feature is copied and changed to the specified feature class. 10. Click to select another feature to copy parallel. 11. When finished copying parallel, press ESC to end. See the “Working with Features” and “Working with Coordinate Systems” sections for more information on these tabs.

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. 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.

To delete a feature (object-action mode): 1. In a map window, create a select set containing the feature(s) you want to delete. OR In a data window, select the row(s) for the feature and then activate the map window by clicking the title bar. 2. Select Edit > Feature > Delete. OR Press CTRL+D. Through Tools > Options > Placement and Editing, you can specify whether the confirmation box is displayed before processing.

All views that were displaying the deleted features are updated.

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


339

Editing Features and Geometries 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” section.

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.

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.

340


Editing Features and Geometries 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.

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.

To insert, move, and delete vertices: 1. In a map window, create a select set containing the feature(s) you want to edit. OR In a data window, select the row for the feature and then activate the map window by clicking the title bar. 2. Select Edit > Geometry > Edit.

Vertex handles appear on all geometries of the selected feature(s) to indicate that the geometries can be edited. 3. To insert a vertex, click on the point of the geometry where you want to insert the vertex. 4. To move one vertex(es), press and hold the left mouse button on the vertex (CTRL+left mouse button to select multiple vertex(es)) you want to move, drag it to the desired location, and release the mouse button. 5. To delete the vertex(es), select the vertex(es) and press DELETE. OR


341

Editing Features and Geometries Select the vertex(es), right click to open the popup menu; then select Delete Vertex.

To edit the vertex height: 1. 2. 3. 4.

Select Edit > Geometry > Edit. Select the vertex(es) whose height you want to change. Right click to open the pop-up menu. Select Edit Height.

If a you selected a single vertex, the New height field displays the current height value. If you selected multiple vertices, the field is blank. The Current height field displays the current vertex height. 5. Type the new value in the New height field. 6. Click OK to update the coordinates of the selected vertex(es). See the “Validating and Fixing Data” section for tools to trim and to extend geometry and to insert intersections.

Moving a Vertex by Precision Keyin In addition to dragging a vertex to a new position, you can move a vertex by precisely defining where the vertex should be relocated by precision keyin to the Precision Coordinates dockable control. Such a keyin move honors all placement and editing options honored by a move with the mouse. For multiple vertexes, moving a vertex by keyin is based on the last point selected. The coordinate of the selected vertex defines the anchor point of the move operation. When you type a location to which to move the vertex, the last vertex selected is moved to the new location, and all other selected vertices are moved relative to their original locations. If snaps are turned on and the keyed-in location of the vertex is within the snap tolerance of another geometry, it automatically snaps to it, overriding the precision keyin value. If you do not want this to occur, you must turn off all snaps before moving the vertex.

To move a vertex by precision keyin: 1. In a map window, create a select set containing the feature you want to edit. Or, in a data window, select the row for the feature and then activate the map window by clicking the title bar. 2. Select Edit > Geometry > Edit. 3. Select a vertex.

342


Editing Features and Geometries 4. Using the Precision Coordinates control, type the coordinates of the new location to move the selected vertex; then press ENTER.

5. Repeat Steps 3 and 4 until the appropriate edits have been made.

Editing Coincident Geometry Edit allows you to edit (insert, move, and delete) coincident geometry when the Maintain coincidence option of the Placement and Editing tab is on. You can use the Locatable and Display On/Off options of the Legend Properties dialog box to prevent features of individual feature classes from interfering in coincidence for a given edit. For Edit, a vertex is coincident with another vertex if and only if they share the same (X, Y) position. To edit coincident geometry, you must first select the geometry with the Select Tool through the map window or the data window. When you move or delete a vertex, Edit searches to determine if a coincident vertex exists on any feature in the select set. If a coincident vertex exists, it is moved or deleted, too. When you insert a vertex, the tool searches to determine if a coincident line segment exists. If one or more coincident line segments exist, they are selected and vertices are inserted in them, too. This command also allows spinning one or more individual oriented point or text point geometries within a collection, including a composite text collection. For example, you could adjust the letter ―A‖ in ALABAMA by spinning it to the correct position.

To edit coincident geometry: 1. In a map window, select the feature you want with the Select Tool. OR In a data window, select the row for the feature and then activate the map window by clicking the title bar. 2. Select Edit > Geometry > Edit.

Handles are shown on all geometries of the selected feature to indicate that the geometries can be edited. All features coincident are highlighted by no handles are shown. 3. To insert a vertex, select the point of the geometry where you want to insert the vertex. OR 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.


343


Editing Geometry with a Snap-and-Break Workflow You can use a productive snap-and-break workflow with the snap-and-break capability of Edit.

To edit geometry with a snap-and-break workflow: 1. Select Tools > Options > Placement and Editing; then turn on Display Properties dialog for new features and Break linear features with the appropriate break option. 2. Select the features to be edited. 3. Select Edit > Geometry > Edit. 4. Select a vertex, and move it so that it snaps to another feature.

The features are split into two features when snapped to by the edited feature with break on, and the attributes are copied. 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.

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.

Deleting Geometry Using Edit Geometry Edit also allows you to delete an entire geometry or a range of vertices.

To delete an entire geometry: 1. Select the features to be edited.

344


Editing Features and Geometries 2. Select Edit > Geometry > Edit.

3. Select a vertex on the hole geometry.

4. Press CTRL+a.

5. Press DELETE.

To delete a range of vertices: 1. Select the features to be edited. 2. Select Edit > Geometry > Edit. 3. Select a vertex (1) on the geometry. 4. Press SHIFT and select a second vertex (2). 5. Press DELETE.

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


345

Editing Features and Geometries 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. You can enable or disable self snapping during placement by checking or unchecking Allow Snap to Same Feature on the Continue Geometry right mouse menu.

See “Inserting Features in a Map Window” in the “Working with Features” section for information on using placement modes and construction aids. 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.

To continue feature geometry with a snap-and-break workflow: 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. Select Options > Placement and Editing; then turn on Display Properties dialog for new features and Break linear features with, and the appropriate break option. 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.

346



Continue Geometry and Use Existing Geometry The Use Existing construction aid on the right mouse menu lets you digitize the next segment of a feature using existing geometry. This option is useful when two features share all or part of a boundary because you don‘t have to redigitize the entire boundary between features. You can click two points along the existing geometry, and all the vertices between those points are copied to the feature being placed. This ensures clean data without slivers or gaps. (You may optionally by the right mouse menu by pressing U on the keyboard to set this placement mode.) This temporary placement mode differs from the Use existing geometry when digitizing option on the Placement and Editing tab or the Options toolbar in two important ways:  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. The Use Existing construction aid is also available on the right mouse menu with the Insert Feature command.

To continue geometry with Use Existing geometry: 1. 2. 3. 4. 5.

Activate the map window that contains the compound feature you want to continue. Select a feature to be added to. Select Edit > Geometry > Continue. Place a point on a linear or area feature. Select the Use Existing construction aid from the right mouse menu.

If the previous vertex is snapped to a single feature, that feature is highlighted. Go to Step 7. Otherwise, the previous vertex is snapped to multiple features, so the PickQuick dialog box is displayed. 6. Select the feature whose geometry will be used.

The selected feature is highlighted. 7. Place the next point on the highlighted coincident feature.

The point is constrained to the coincident feature and the geometry from the first point to the second point is highlighted. 8. If the coincident geometry is an area, press TAB to switch to the path you want to use.

The other path from the second point to the first point is highlighted. 9. Click another point to accept the highlighted geometry. 10. Return to Step 4 or Step 5, or continue placing additional points.


347


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 s construction aids that return a point geometry and require no input geometry while identifying both the from point and the to 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 ing the cursor and the base point with respect to the current orientation of the feature.

348


Editing Features and Geometries The following figures show the result of the spin operation with the relative angle specification.

The geometry is oriented at 90 Resulting orientation of the geometry after being spun at a 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 ing 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 90 Resulting orientation of the geometry after being spun at an 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.

To spin a point symbol or text: 1. In a map window, select the point symbol or text you want to spin; or select the row for the point symbol or text in the data window, and then activate the map window by clicking the title bar. 2. Select Edit > Geometry > Spin.

An origin handle appears in the map window for each selected point symbol or text. 3. Select the appropriate spin option, Relative or Absolute. 4. Click the origin handle of the item to be spun.


349

Editing Features and Geometries As you position the cursor over the origin handle, the cursor changes to show the “active spin” cursor. After clicking on the origin handle, the cursor is changed back to the previous cursor. The active object displays a baseline and reference line from the origin handle.

5. Click to accept the angle. OR Type the appropriate value in the Angle field.

The display is updated once you establish the active angle.

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.

To interactively rotate geometry: 1. In a map window, select the feature(s) you want to rotate. OR Go to Step 2, and after selecting the command, select a feature to rotate. 2. Select Edit > Geometry > Rotate.

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.

350


Editing Features and Geometries 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 ing 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 Feature Geometry Redigitize Geometry allows you to delete any part of a linear or area feature geometry and to redigitize it as a modification to the original feature in object-action or action-object mode. In object-action mode, the command prompts you to place a start and end point for redigitizing, and you must place these points on the same geometry. For example, you cannot place a start point on an area geometry and an end point on a hole geometry. In action-object mode, you can start the command without an active select set. You can then repetitively select and redigitize individual features while the command remains active. In this mode, the click to identify a feature also identifies the start point of the segment to be redigitized, thus reducing the number of clicks required. 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


351

Editing Features and Geometries aid. You can enable or disable self snapping during placement by checking or unchecking Allow Snap to Same Feature on the Redigitize Geometry right mouse menu.

See “Inserting Features in a Map Window” in the “Working with Features” section 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 s 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.

To redigitize a line feature (object-action mode): 1. Select a line feature to redigitize. 2. Select Edit > Geometry > Redigitize. 3. Snap to a point on the line to identify the start point for redigitizing. 4. Hover over the end point for digitizing.

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.

To redigitize an area feature (object-action mode): 1. Select an area feature to redigitize. 2. Select Edit > Geometry > Redigitize. 3. Snap to a point on the area to identify the start point for redigitizing.

352


Editing Features and Geometries 4. Hover over the end point for redigitizing.

The snap glyph is displayed, and the geometry is highlighted between the start and end points. 5. Press the TAB key.

The area boundary is highlighted in the opposite direction. 6. 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 area feature is displayed in dynamics from the start point to the end point. 7. Click to place the next point.

8. Click the new point.

9. Double click to end.

To redigitize a feature with a break (object-action mode): 1. Turn on Break linear features and Display Properties dialog for new features on the Placement and Editing tab. 2. Select Edit > Geometry > Redigitize. 3. Snap to a point on the feature to identify the start point for redigitizing. 4. Place the end point.

The feature is displayed in dynamics from the start point to the end point.


353

Editing Features and Geometries 5. Place a point by snapping to another line.

The line feature snapped to is broken, and the Properties dialog box is opened. 6. Type the required attribute values for the feature snapped to; then click OK. 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.

Deleting Feature Geometry When you delete the geometry of a feature in a map window, the feature is no longer displayed in the map window. Deleting geometry, however, does not delete the feature. Attribute data still exists for the feature, which can be viewed in a data window. You can add geometry back at any time with the Continue tool. When you select multiple rows in a data window, this procedure deletes all the geometry and text for all selected rows, including those not displayed in the active view.

Partially Deleting Linear Features Partial Delete lets you partially delete a linear feature in object-action or action-object mode. In object-action mode, you first select a feature in a read-write connection, and then you enter start and end points while the cursor is within the locate tolerance of the selected feature. The portion of the feature delineated between the start and end points is dynamically highlighted as you move the cursor; then it is deleted. In action-object mode, you can start the command without an active select set. You can then repetitively select and perform partial delete on individual features while the command remains active. In this mode, the click to identify a feature also identifies the start point of the segment to be deleted, thus reducing the number of clicks required. This command s the partial deletion of lines, polylines, composite polylines, arcs, and linear geometry collections. For a geometry collection, the start and end points entered for partial deletion must reside on the same linear geometry object in the collection. You can specify a start point or an end point for partial deletion on either end point of a feature. You cannot completely delete the selected geometry by specifying the start and end points to be the two end points of the selected geometry. While using Partial Delete, the AutoPan setting is honored, and you can access the viewing commands. All vector snapping to the selected feature is always honored, even when the vector snapping options are not selected on the tool bar. The vector snapping to other (unselected) features is not honored, however. You can undo/redo the results of a partial deletion with the Undo/Redo commands. Also, pressing BACKSPACE reverts the state of the geometry placement back to the previous step.

To partially delete a linear feature (object-action mode): 1. 2. 3. 4. 5. 6.

Select a linear feature. Select Edit > Geometry > Partial Delete. Move the cursor to some location within the locate tolerance of the selected feature. Click to define the start point for deletion. Move the cursor to some other location within the locate tolerance of the selected feature. Click to define the end point for deletion.

The portion of the selected feature delineated by the start and end points is deleted, and the command is exited automatically. 354



Changing Feature Classes When you collect data using other software packages and import it into GeoMedia Professional, some of the features may have the wrong feature class. This is especially true for CAD data in which all the features were collected into a single file. Change Feature Class lets you select one or more features and change the feature class to another feature class. This command s converting point, line, and area features to a compatible destination feature class, and copying the values of the matching attribute fields, in addition to the geometry, while changing the feature class of the features from the select set. To change a feature class, you select the source feature(s) to be reclassified and then the target feature class. The software filters the set of available target feature classes depending on the geometry type of the feature in the select set. This command updates all open windows to reflect the change of feature class (The input features may change symbology, vanish, or appear.). Source features can be from either a read-write or read only warehouse or both, but the target feature class must be from a read-write warehouse only. You can delete the selected feature instance(s) from the read-write source by checking the Delete original feature check box (the default) on the Change Feature Class dialog box. The deletion takes place only when the change operation has completed. If this option is not checked, there is no deletion of the originating feature(s). When the select set contains features of the same geometry type, the Change Feature Class dialog box lists target feature classes of that geometry type only. However, in the case of point, line, and area geometry type, it also lists target feature classes of the type compound geometry. When the select set contains a combination of point, line and/or area features, the dialog box lists target feature classes having the compound geometry type only. If none of the read-write warehouse connections have compound feature classes, an appropriate error message is displayed. An error message is also displayed if the select set is not valid. A select set is considered to be not valid if it contains features of different geometry types (other than just point, line, and area) that cannot be changed to a single, target geometry type. 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. 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.

To change feature class: 1. In a map window, create a select set that contains the feature(s) that you want to reclassify. OR


355

Editing Features and Geometries In a data window, select the row(s) for the feature(s) that you want to reclassify and then activate the map window by clicking the title bar. 2. To display the Properties dialog box for each reclassified feature so that you can enter attribute values, select Tools > Options and do the following:  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.

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. 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. 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. 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” section.

356


SECTION 12

Validating and Fixing Data GeoMedia Professional provides tools that allow you to maintain data integrity by reviewing geometry information, validating geometry, and validating connectivity. In addition, this product provides tools to correct data by trimming and extending geometry to intersections, inserting intersections, fixing connectivity, and fixing geometry. These tools are the following: Geometry Information

Extend Two Lines to Intersection

Validate Geometry

Trim

Fix Geometry

Trim to Intersection

Validate Connectivity

Insert Intersections

Fix Connectivity

Construct Circular Fillet

Reverse Direction

Simplify Geometry

Extend

Smooth Geometry

Extend to Intersection This product also contains other editing tools for editing other conditions. There are two basic workflow scenarios for using these tools. In the first, you perform all of the data capture within GeoMedia Professional. Because the functionality of this product stresses getting the data right the first time, there should be a minimal number of conditions found that need to be corrected. In the second workflow, you import data that was captured outside of GeoMedia Professional, then validate its composition. In either workflow, you would typically perform data validation as a first step in using your data because clean data are required for accurate results of subsequent processing. These correction tools honor the settings on the Placement and Editing tab on the Tools > Options dialog box for coincidence, linear feature break, stream tolerance, display of the Properties attribution dialog box, and use of existing geometry when digitizing. You can also set coincidence, break, and attribution from the tool bar. See the “Working with Features” and the “Editing Features and Geometries” sections for information on other editing tools. See “Using the Placement and Editing Tab” in the “Working with Features” section.

Using Editing Tools with Data Validation Tools Validate Geometry and Validate Connectivity produce output queries of found conditions to a map window and/or data window. In a typical workflow, you would have both windows open and vertically tiled. You would also use Window > Map Window Properties to set the display so that you could zoom in on each found condition. In addition, you need to set the map legend so that the found anomalies are under the features because you edit the features, not the anomalies. You can also turn the locate off for the anomalies on the legend. 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


357

Validating and Fixing 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:  Delete it from the GeoWorkspace using the Queries command.  Remove it from all map window legends.  Remove it from all data windows. 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” section.

Displaying Geometry Information Geometry Information allows you to display and to edit information about the geometry of individual features in a warehouse. This command is a useful tool for understanding and resolving problems with a given feature that may have been uncovered by the validation or other commands in GeoMedia Professional or that may not be obvious from looking at the feature itself. For example, you can determine if two points that appear to be the same in the map window are in fact the same, which part of a polygon hole geometry falls outside its boundary, or which vertex needs to be changed to fix a loop error. This command is also useful because many GeoMedia Professional operations behave differently depending on the geometry type of a feature. For example, a two-point line can be broken but cannot have a vertex automatically inserted. To use Geometry Information, you must have at least one read-only or read-write warehouse connection, an active map window, and only one feature in the select set. This command lets you perform the following:  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.  Determine the order in which vertices are stored.  Display the coordinate values for individual vertices.  Display all arc parameters.  Change the order of geometries within a collection or the holes collection of a boundary geometry.  Reverse a polyline or composite polyline, or arc or line geometry. The polyline or composite polyline can be either a standalone geometry or a constituent geometry of a geometry collection.  Delete a geometry that is part of a geometry collection or the holes collection of a boundary geometry.  Delete a vertex within a polyline, composite polyline, polygon, boundary, or composite polygon. 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

358


Validating and Fixing Data 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.


359

Validating and Fixing Data ed Geometry Types Geometry Information s the following geometry types: Geometry Type Information

Displays

Arc Geometry

Start Point, Origin Point, End Point, Mid Point, Normal Vector, Radius, Sweep Angle, Arc Length, Chord Length

Boundary Geometry

Exterior Geometry, Geometry Collection of Holes

Composite Polygon Geometry

List of Geometries

Composite Polyline Geometry

List of Geometries

Geometry Collection

List of Geometries

Line Geometry

Start Point, End Point

Matrix

Four Column Vectors

Oriented Point Geometry

Origin Point, Orientation Vector

Point

x, y, z

Polygon Geometry

List of Points

Polyline Geometry

List of Points

Raster Geometry

Filename, Display Matrix, Raster Polygon

Rectangle Geometry

Origin Point, Height, Width, Rotational Vector, Normal Vector

Text Point Geometry

Text String and x, y, z

Vector

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. The editing menu contains the following commands: Delete—Deletes a geometry from a collection or a hole polygon from a boundary geometry. This command is enabled when the selected geometry is part of a geometry collection or part of the holes collection in a boundary geometry. If only one geometry remains in the collection after a delete action, the collection is converted to the corresponding geometry. If all the hole polygons in a boundary geometry are deleted, it is converted to a polygon or composite polygon geometry. This command also deletes a vertex from most geometry types. However, Delete is not enabled when you select a vertex in a composite geometry whose deletion would affect the connectivity of the constituent elements making up that composite geometry or select a vertex on an arc. Reverse—Changes the direction of the vertices making up the geometry. This command is enabled for all polylines, composite polylines, arcs, and lines. It is restricted to the single element already highlighted. Move to the top, Move up, Move down, Move to the bottom—Reorder the geometries within the geometry collection or holes collection. These commands are enabled when the selected geometry is part of a geometry collection or part of the holes collection of a boundary geometry.

360


Validating and Fixing Data The following table summarizes the editing functions:

Enabling Conditions Delete (geometry)

Constituent geometry of a ed geometry type is selected on the dialog box.

ed Geometry Types Geometry collection Boundary geometry holes collection

Processing

Special Rules

Constituent geometry is deleted.

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.

Standard text collection Nested text collection

Delete (vertex)

Reverse

Move

A vertex from a ed geometry type is selected on the dialog box, if standalone or part of a geometry collection

Polyline

One of the ed geometry types is selected on the dialog box, if standalone or part of a geometry collection.

Line

Constituent geometry of a ed geometry type is selected on the dialog box.

Geometry collection

Polygon Boundary Composite polyline Composite polygon

Arc Polyline

Vertex is If the selected vertex deleted from of a composite the geometry. polyline or composite polygon is on an arc, or is a vertex shared by consecutive the composite, this command is disabled. Order of the vertices is reversed.

N/A

Order of the constituent geometry within the collection is altered as specified.

N/A

Composite polyline

Boundary geometry holes collection Standard text collection Nested text collection


361

Validating and Fixing Data See “Reversing Direction” in this section. 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.

Changing Geometry Display With this command you can customize the geometry display through the Options dialog box accessed in this command by choosing among the following the following:  Whether to display the height value for point geometries.  Whether to display the coordinate values vertically or horizontally.  The color and the weight of the highlight display in map windows.  The format of the coordinate display (geographic or projection).

To display and to edit geometry information: 1. 2. 3. 4.

Select a feature in a map window or a data window. Select Tools > Geometry Information. Expand the geometry in the treeview. Select the appropriate geometry to display its values and to highlight it in the map window.

This dialog box is resizable. 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. You can also perform deletes by pressing the DELETE key.

362


Validating and Fixing Data 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. 8. Click OK to write the edited geometry to the database.

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.

Geometry Validation Error Conditions Validate Geometry can find the following error conditions: Error

Definition

Kickback and Duplicate Point

An area boundary or hole, or linear geometry that reverses direction temporarily so that it doubles back over itself and then proceeds in the original direction without creating a face. This includes conditions of repeating consecutive vertices.

Loop

The geometry of an area boundary or hole intersects itself.


363

Validating and Fixing Data Error

Definition

Kickback and Duplicate Point

An area boundary or hole, or linear geometry that reverses direction temporarily so that it doubles back over itself and then proceeds in the original direction without creating a face. This includes conditions of repeating consecutive vertices.

Unclosed Area

An area boundary or hole that does not close on itself, that is, the last vertex does not equal the first vertex.

Uncontained Hole

A hole that is not contained within its boundary.

Overlapping Holes

Holes that overlap within a boundary.

Invalid Geometry Type

Actual geometry stored in a GDO field that does not match the GDO type/subtype definition.

Empty Geometry Collection

Geometry collection contains zero geometries.

Too Few Vertices

Polygon geometries contain fewer than four vertices; polyline geometries contain fewer than two vertices.

Unknown Geometry Type

Binary format cannot be converted into a geometry object.

Invalid Coordinates

The absolute value of a coordinate or coordinates (x, y, or z) in the geometry is greater than infinity (1.0e+30).

To validate geometry: 1. Connect to a read-write warehouse.

364


Validating and Fixing Data 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. 4. , and change if appropriate, the default name anomalies assigned to the output record set in the Query name field. 5. Optional: Type a query description in the Description field. 6. 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. 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


365

Validating and Fixing Data 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.

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. If there are no duplicate points or kickbacks, an error message is displayed. 5. Click OK.

The message Fixing 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. 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.

366


Validating and Fixing Data

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: 

Undershoots

Overshoots



Node mismatches

Unbroken intersecting geometry



Non-coincident intersecting geometry

Nearly coincident geometry

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 section.


367


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. 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 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.

Unbroken Intersecting Geometry This condition occurs when features intersect one another without creating corresponding end point nodes at the intersection points. Only linear geometries can be broken, but the intersecting geometries can be either points, lines, or areas. Non-coincident Intersecting Geometry This condition occurs when features intersect one another without creating corresponding vertices at the intersecting points. Both linear and areal geometries can have vertices inserted. The intersection geometries can be points, lines, or areas. Nearly Coincident Geometry This condition occurs when an interior vertex of one geometry falls within the tolerance of either a vertex or an edge of another geometry. The geometry types affected are point (discontiguous), linear (single and discontiguous geometry), and area (single and discontiguous geometry, boundary, and holes).

368



Examples of Connectivity Conditions by Feature Class Line versus Line

Overshoot

(Intersection not broken, intersection not coincident. If all these switches are on, overshoot takes precedence.)

Undershoot

Node Mismatch

Node Mismatch – Undershoot

(If both switches are on, node mismatch takes precedence.)

Nearly Coincident

Nearly Coincident

Intersection Not Broken (This takes precedence over intersection not coincident.)

Intersection Not Coincident

Line versus Area

Overshoot

Undershoot


369


Node Mismatch

Nearly Coincident

Nearly Coincident

Intersection Not Broken

Line versus Point

Node Mismatch

Nearly Coincident

Intersection Not Broken (The line needs to be broken at the point.)

Intersections Not Coincident (The line needs a vertex at the point.)

Area versus Area

Nearly Coincident

Nearly Coincident

Intersections Not Coincident

(The area needs vertices at the intersection points.)

370


Validating and Fixing Data Area versus Line

Nearly Coincident

Nearly Coincident


(The area needs a vertex at the intersection.)

Area versus Point Area vertex nearly coincident with point


(The area needs a vertex.)

Point versus Point Node Mismatch between two points

Point versus Area Node Mismatch between point and vertex

Undershoot of point to a segment


371

Validating and Fixing Data Point versus Line

Node Mismatch

Node Mismatch

Undershoot

To validate connectivity: 1. Open a read-write warehouse. 2. Select Tools > Validate Connectivity.

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. , 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. 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.

372


Validating and Fixing Data 11. 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.

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



Breaking crossing lines



Extending undershoots



Inserting a vertex into crossing lines

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


373

Validating and Fixing Data the Break linear features options on the Placement and Editing tab of the Options dialog box (Tools > Options).

Examples of problems Fix Connectivity corrects: Trim Overshoots

Line A is trimmed back to Line B. Extend Undershoots

Line A is extended to Line B. Break Crossing Lines

Line A is broken into two segments, A and C, at the intersection of Line B. Insert Vertex into Crossing Lines

A vertex is inserted into Line A at the intersection with Line B.

Examples of problems Fix Connectivity cannot correct: Extend Undershoots

The extension of Line B is outside the tolerance.

The extension of Line B does not intersect Line A.

374



Order of Processing The order in which you fix connectivity problems is important. In general, you should trim overshoots first, then fix undershoots, and finally break crossing lines or insert a vertex into crossing lines. The following example shows where breaking crossing lines was performed before trimming overshoots:

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 connectivity: 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.

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. Depending on the types of problems, fixing one type at a time may reduce possible errors.


375

Validating and Fixing Data 6. Click OK.

The message Fixing 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. 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 control are determined by the distance units set on the Units and Formats tab of the GeoWorkspace Coordinate System dialog box. This command s 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 ed. 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.

3. Hover the cursor over the linear feature to be extended. 4. If only one feature is within the locate tolerance, click to select the highlighted feature on the end to be extended. If multiple features are within the locate tolerance, click to display the PickQuick dialog box; then choose the feature to be extended, clicking on the end to be extended. Continue with Step 5. OR Check the Lock check box on the dockable control.

The Distance field is enabled and locked at the current distance. Go to Step 7.

376


Validating and Fixing Data 5. Move the cursor on the screen.

The selected feature is dynamically extended as the cursor is moved, and the Distance field on the dockable control is dynamically updated. 6. Click to extend.

The feature is extended, and a vertex is placed at the point of extension. If the new vertex was snapped onto an existing feature (though an on-element snap only), coincidence and/or break processing are performed if those options are set. Go to Step 9. 7. Type the appropriate distance.

The selected feature is dynamically extended the distance specified on the control. 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 on-element 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.

Extending Geometry to Intersections Extend to Intersection allows you to extend linear features, one at a time, to the closest intersecting feature in a view. The vicinity of the cursor to the end points determines the extend direction, that is, the closest end point is extended. Selecting this tool clears any select set. As you move the cursor over the end segment of a linear feature, it appears in dynamics. This does not occur if the cursor hovers over internal segments. If the feature is editable, Extend to Intersection highlights and calculates the line segment that extends to the first intersecting feature in the current map view. You can then use a data point to accept the extension or move to another feature without accepting the extension. If there are multiple features, you can use PickQuick to select the feature to extend. Extend to Intersection honors the coincident settings, delayed attribute settings, and break settings on the Options dialog box. If the coincident setting is on, this tool adds vertices to all features on which the new extended end point falls. This tool modifies existing geometry, so it uses the height values of the existing geometry. The height value for the extend point will be a point extrapolated from the original geometry, not on the geometry that is being extended to.

Possible Extend Cases The following are the two possible extend cases handled by Extend to Intersection: Candidate feature to be extended = Case 1. Intersection: No closest feature found.

If you place the cursor on a linear feature that has no close features in both directions, the figure does not highlight.


377

Validating and Fixing Data Case 2. Polyline feature to be extended to linear feature.

These figures show the two possible extend cases.

To extend geometry to intersection: 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 > Extend to Intersection. 5. Move the cursor over a portion of the feature you want to extend.

The feature is highlighted with the extended line segment. 6. Click the highlighted feature to extend it to the nearest intersecting feature.

If the coincident setting is on, vertices are added to all features on which the new extended end point falls. If the Break within same feature class only option is on and the feature being extended to is the same feature class as the feature being extended, it is broken into two features. The first feature is discarded entirely, and you are prompted to fill in the attributes of both "new" features (first the left side, then the right). If the Break all feature classes option is on, all features on which the new extended end point falls are broken into two features. If the Display Properties dialog for new features option is on or if there are required attributes in the new feature(s) being created, its dialog box opens. The relevant map window, data window, and queries are updated, and the cursor waits for further input of features to be extended. 7. Double click to exit Extend to Intersection.

Extending Two Lines to an Intersection Extend Two Lines to Intersection lets you extend two linear features to their projected intersection point. If the intersection point lies on the end segment of one of the linear features, only one linear feature is extended, and the feature containing the intersection point is trimmed. You cannot use this command to trim two intersecting linear features to their intersection point.

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.

378


Validating and Fixing Data This command s 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 s the AutoPan, coincidence, and break settings. In order to make feature selection easier in congested areas, it also s 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.

To extend two lines to an intersection: 1. Select Edit > Geometry > Extend Two Lines to Intersection. 2. Hover the cursor over the two linear features. 3. If only one feature is within the locate tolerance, click to select the highlighted feature.

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.


379

Validating and Fixing Data 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 s 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 ed. 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.

3. Hover the cursor over the linear feature to be trimmed. 4. If only one feature is within the locate tolerance, click to select the highlighted feature on the end to be trimmed. If multiple features are within the locate tolerance, click to display the PickQuick dialog box; then choose the feature to be trimmed, clicking on the end to be trimmed. Continue with Step 5. OR Check the Lock check box on the dockable control.

The Distance field is enabled and locked at the current distance. Go to Step 7. 5. Move the cursor along the feature.

The selected feature is dynamically trimmed as the cursor is moved, the Distance field on the dockable control is dynamically updated, the vector snap option is honored, and the snap glyphs are displayed. 6. Click to trim.

The feature is trimmed, and a vertex is placed at the trim point. If the new vertex was snapped onto an existing feature (through an on-element snap only), coincidence and/or break processing are performed if those options are set. Go to Step 9. 7. Type the appropriate distance.

The selected feature is dynamically trimmed the distance specified on the control. 8. Click to trim.

The feature is trimmed the specified distance, and a vertex is placed at the trim point. If the new vertex was snapped onto an existing feature (through an on-element 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.

380



Trimming Geometry to Intersections Trim to Intersection allows you to trim overlapping linear features. In this process, the tool highlights the portion of the feature to be trimmed, trims the selected feature to the closest intersection from the end point that is closest to the cursor, and updates the modified feature in the warehouse. The intersecting feature can be a linear feature or an area boundary. This tool modifies existing geometry, so it uses the height values of the existing geometry. The height value for the trim point will be a point on the original geometry, not on the geometry that is being trimmed. You access Trim to Intersection from the Edit menu. Selecting this tool clears the select set of any selected items. You then move the cursor over a linear feature. If the feature is editable, Trim to Intersection highlights the portion of the feature to be trimmed, calculating this portion from the closest end point to the cursor to the first valid intersecting feature. If there are multiple features within the locate zone or the cursor, you can use PickQuick to select the feature to trim. If no intersection is found within the search range, which is bounded by what is displayed on the screen, Trim to Intersection does not process the selected feature. This does not apply to read-only features or features with locate turned off.

Possible Trim to Intersection Cases The following are the possible trimming cases handled by Trim to Intersection: Intersecting feature = Case 1. Intersection: Not found.

Candidate feature to be trimmed =

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.

(Break option off)

(Break option on)

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. Case 3. Intersection: One linear feature intersecting with an area boundary.

The segment to be trimmed when intersecting with an area boundary.


381

Validating and Fixing Data To trim geometry to Intersection: 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 > Trim to Intersection. 5. Move the cursor over a portion of the feature you want to trim. 6. Click the highlighted feature portion to accept the trim.

If the coincident setting is on, vertices are added to all features on which the new end point of the modified feature falls. If the Break same feature class only option is on and the feature intersecting the feature being trimmed is the same feature class, it is broken into two features. If the Break all feature classes option is on, all features on which the new end point of the modified feature falls are broken into two features. If the Display Properties dialog for new features option is on, its dialog box opens if a break occurs or if there are required attributes in the new feature(s) being created. The relevant map window, data window, and queries are updated, and the cursor waits for further input of features to be trimmed.

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 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:

382

Break all feature classes

Break same feature class only Action

Yes

Yes

Vertex is placed on all features at the intersection point.

No

Yes

All features are broken at the intersection point.


Validating and Fixing Data Break all feature classes

Break same feature class only Action

Yes

No

All features of the same feature class as the highlighted feature tolerance of the intersection point are broken. Vertex is placed on all features of a different feature class at the intersection point. 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.

Possible Intersection Cases The following are the possible intersection cases handled by Extend to Intersection: (The dots indicate the intersection point. The gray lines indicate the located features.)

Solutions For all the following cases, assume F1 to be the located feature. Case 1. Same feature class (linear).

Break same feature class: F1 and F2 are broken 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 2: Different 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.


383

Validating and Fixing Data 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. Break off: Vertex is inserted on F1 and F2 at the intersection.

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.

384



Constructing Circular Fillets Construct Circular Fillet lets you construct a circular fillet (arc) between two unparallel line segments. These two segments can be on the same feature instance or on different feature instances that could belong to the same feature class or to different feature classes.

You can also choose to trim the excess of both segments at their point of tangency with the fillet.

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. 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 s 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 s the following functionality:  PickQuick to ease feature selection in congested areas  Coincidence and break settings when you choose not to trim the excess  Access to viewing commands while this command is active  Properties settings  AutoPan


385

Validating and Fixing Data   

Undo/Redo commands Clicking in any open map window to select a segment and to determine and to place a fillet BACKSPACE to revert back to the previous geometry stage

To construct circular fillets: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13.

Select Edit > Geometry > Construct Circular Fillet. On the dockable control, uncheck the Trim excess check box if checked. Select a feature class for the fillet being constructed from the feature selection drop-down list. Click in the map window to select the first line segment for fillet construction. Click to select the second line segment for fillet construction. Move the cursor to dynamically construct the fillet between the selected two segments; then click to place the fillet as a separate feature instance into the feature class specified in Step 3. Select another two line segments by following Steps 4 and 5. Check the Lock check box. Type an appropriate radius value in Radius field to dynamically construct a fillet with the specified radius. Click to place the fillet as a separate feature instance into the feature class specified in Step 3. Check the Trim excess check box; then uncheck the Lock check box. Select another two line segments that belong to the same feature instance by following Steps 4 and 5. Move the cursor to dynamically construct the fillet between the selected two segments; then click to place the fillet.

The fillet is merged with the two selected segments that are trimmed at the point of their tangency with the fillet. No new feature instance is generated. 14. Select another two line segments that belong to the different feature instances that could belong to the same feature class or to different feature classes by following Steps 4 and 5. 15. Move the cursor to dynamically construct the fillet between the selected two segments; then click to place the fillet.

The fillet is placed as a new feature instance into the feature class specified on the control, and the two selected segments are trimmed at the point of their tangency with the 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

386


Validating and Fixing Data Geometry Information command before and after changing the line orientation to 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 the change in line orientation.

To reverse direction: 1. Select the appropriate linear feature(s). 2. Select Edit > Geometry > Reverse Direction.

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. 3. Optional: Select Tools > Geometry Information to that the order of the vertices has been reversed if you have not changed the line style to aid in visual verification.

Simplifying Geometry Simplify Geometry simplifies the geometry of linear, area, or compound features by eliminating insignificant vertices in the geometry. The command simplifies feature geometries through the execution of the Douglas-Poiker algorithm.

To simplify geometry: 1. Select Tools > Simplify Geometry.

2. Select the appropriate linear, area, or compound feature from the Simplify features in drop-down list. 3. Type or select the Distance and then the corresponding Units. 4. In the Output results as query field, accept the default, or type another name in the Query name field, and, optionally, type a description in the Description field. 5. To see the results in a map window, make sure that the check box to the left of Display results in map window is checked and that the appropriate Map window name is selected. 6. Optional: Click Style to define the display settings for the results in the map window.


387

Validating and Fixing Data 7. To see the results in a data window, make sure that the check box to the left of Display results in data window is checked and that the appropriate Data window name is selected. 8. When you have made the appropriate settings, click OK.

Smoothing Geometry The Smooth Geometry smooths the geometry of linear, area, or compound features. The command smooths feature geometries through the execution of a weighted-average algorithm, which is based on the following smoothing options: Look ahead-Determines how many vertices ahead of, and behind, the vertex that is to be smoothed are used in the smoothing of that vertex. This value should be a positive integer greater than or equal to 1. The default value is 3. Weight-Determines the weight given to the neighboring vertices during the averaging process. This value should be greater than or equal to 0 and less than or equal to 1. If the value is 0.0, there is no smoothing, and as the value increases, more smoothing occurs. The default value is 0.5. Densification tolerance/Units-Determines how many vertices are temporarily added along the geometry to compute the new location of the real vertices. The temporary vertices are deleted once the smoothing process is completed. If the value is zero, densification is not used. Zero is the default value. This value should be a positive number.. Units-Units of measure for the tolerance. The default unit is the UOM distance unit.

To smooth geometry: 1. Select Tools > Smooth Geometry.

2. In the Smooth features in drop-down list, select the appropriate linear, area, or compound feature. 3. Type the appropriate Look ahead/vertices value. 4. Type the Weight. 5. Type the appropriate Densification tolerance, and then select the corresponding Units. 6. In the Output results as query field, accept the default, or type another name in the Query name field, and, optionally, type a description in the Description field. 7. To see the results in a map window, make sure that the check box to the left of Display results in map window is checked and that the appropriate Map window name is selected. 8. Optional: Click Style to define the display settings for the results in the map window.

388


Validating and Fixing Data 9. To see the results in a data window, make sure that the check box to the left of Display results in data window is checked and that the appropriate Data window name is selected. 10. When you have made the appropriate settings, click OK.


389


390


SECTION 13

Analyzing GeoMedia Professional Data GeoMedia Professional provides various ways for you to analyze your data using queries. Broadly, a query is a request for information. Specifically, it is a request for the features that meet the conditions you define and/or a request for certain information about the features. The software gives you several ways to define these conditions. To find features that meet your conditions, you query feature classes in any open warehouse in the GeoWorkspace or query previously built queries. Queries are stored in the GeoWorkspace so that, if a warehouse changes, all queries are updated each time they are displayed. If a default spatial filter is defined for the warehouse connection at the time the query is defined, the query is limited to the geographic area defined by the spatial filter. Furthermore, spatial filters, feature classes, interact in three scenarios. First, if a feature class that has never been accessed in the GeoWorkspace, the feature class has never had a spatial filter created for it and so gets the default spatial filter. Second, if the feature class has already been accessed in the GeoWorkspace, it has its own spatial filter and so does not get the default spatial filter. Third, a query always has its own spatial filter. The software scans the query area for the features that meet your conditions and then displays the results geographically in a map window or in tabular format in a data window. An entry for the query result is added to the legend, and its display can be manipulated through the legend properties like any other legend entry. In fact, once built, a query can be treated just like a feature class.

Working with Filter Queries Filter queries are distinguished primarily by the fact that they return a subset of the features in a single feature class or query. You can build several types of filter queries although they have much in common:  An attribute-filter query allows you to limit the search to individual features whose attributes contain values that meet the conditions specified by an operator. An operator is a symbol or expression, such as = (equals) or > (is greater than), that represents the relationship between two values. For example, an attribute-filter query would return all parcels with an assessed value of $50,000 or more.  A spatial query allows you to limit the search to individual features whose geometry has a spatial relationship to features from another feature class or query. 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. 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.


391

Analyzing GeoMedia Professional Data 

To retrieve information from an MGSM warehouse, you build linear network queries. MGSM stores distributed attributes that are linearly referenced to network linear features such as roads, rivers, or pipelines. Linear network queries are a type of combined spatial and attribute query. For example, a linear network query would return all segments of a railroad that intersect accident sites.

Defining Attribute-Filter Queries In an attribute-filter query, you identify the features you want by defining an attribute filter. A filter consists of one or more expressions, each consisting of an attribute, an operator, and a value for the attribute. In a where statement, you can specify a specific value or a range of values for one attribute or a combination of attributes. For example, in an attribute-filter query to select all schools where enrollment is less than 400, schools is the feature class, enrollment is the attribute, less than (<) is the operator, and 400 is the value. The following operators are available for all attribute queries: =

Equals

>=

Greater than or equal to

<=

Less than or equal to

<>

Not equal to

>

Greater than

<

Less than

()

Parentheses for grouping expressions

and

Logical and between two expressions

or

Logical or between two expressions

Additional operators are available from the Operators drop-down list on the Filter dialog box. This list of operators is not inclusive of all available operators. The correct usage of an operator can vary depending on the warehouse connection type. For read-write connections (Access, MS SQL, and Oracle), the SQL statement is ed to the database for processing so the syntax varies according to the warehouse type. For read-only server connections, GeoMedia uses its own SQL parser, which is similar to that of Access. It is recommended that you consult data warehouse-specific resources for further information on proper syntax for SQL string construction. For example, the following query would find all parcels where the accessed value is greater than the average accessed value for all parcels: . . . where assessed_value > (select AVG (assessed_value) from parcels); You create compound expressions with the and or the or operator and group expressions with parentheses ( ). The and operator means that both statements must be true to produce a query result. For example, the following query would find all parcels where the owner is J. Smith and the assessed value is over $50,000: . . . where parcel_owner = 'J. Smith' and assessed_value > 50000; The or operator means that either statement can be true to produce a query result. For example, the following query would find all parcels where the owner is either J. Smith or M. Brown: . . . where parcel_owner = 'J. Smith' or parcel_owner = 'M. Brown'; Parentheses can be used to control the order in which an expression is evaluated. By default, all relational comparison operators (<, >, <>, =,<=, >=) are evaluated first, from left to right. The

392


Analyzing GeoMedia Professional Data logical and operator has a higher precedence than the logical or operator; so all and operations are performed first. You can use parentheses to change the order. For example, to find all roads with more than four lanes or divided roads that were paved before 1994, you would create the following filter: last_paved < 1994 and num_lanes > 4 or divided = 'yes'; Because of the precedence of the and operator, you would get all roads that are divided or all roads where the number of lanes is greater than four and paved before 1994. To get the correct results, you would use parentheses as follows: last_paved < 1994 and (num_lanes > 4 or divided = 'yes'); The software uses SQL for creating attribute-filter queries, but its point-and-click interface allows you to build a query without knowing SQL.

SQL Dialects Different connection types require different SQL dialects. For example, Access connections require pound sign (#) delimiters around date and time values, whereas MGSM connections require the keyword TIMESTAMP followed by single-quote (') delimiters. The software formats SQL statements into the appropriate dialect for each connection type except MGE and MGDM. The SQL dialect for MGE and MGDM connections depends on the ODBC driver. For date and time queries-and possibly others-you must manually edit the SQL text on the Filter dialog box to issue a successful query. In addition, the Filter dialog box performs the following:  Displays fields of date, currency, and Boolean data types in the attributes list when performing a query on a query.  Displays values for these fields when you click Show Values. These values are formatted according to the standard attribute formatting rules (that is, they appear as they appear in the data window, feature properties, and so forth. See table below).  When you select a value for such an attribute the list and add it to the Filter field, it is added with any necessary delimiters and with formatting compatible with the SQL dialect of the AttributeFilterPipe or the GDO server being queried (See table below).  When you type a value for such an attribute in the Values field above the list and add it to the Filter field, it is validated in standard 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 select from 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. Fields of type LongBinary, Spatial, Graphic, and GUID are not ed by the Filter dialog box.


393

Analyzing GeoMedia Professional Data Field Value Handling by Field Type for Entry, Presentation, and SQL Text, Memo

Byte, Integer, Boolean Long, Single, Double, Currency

Date

―Show Values‖ Display and Entry

Standard format (not hypertext)

-defined format (General Number, Fixed, Standard, Currency, or Percent)

-defined format -defined (Yes/No, etc., format (Date, custom) 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

-1 for TRUE, 0 for FALSE, not delimited

See note below.

If -defined format is ―Date‖, keyword DATE followed by date value expressed as YYYY-MM-DD, delimited by single quotes. If -defined format is ―Time‖, keyword TIME followed by time value expressed as HH:MM:SS, delimited by single quotes. If -defined format is ―Date/Time‖, keyword TIMESTAMP followed by date/time value expressed as YYYY-MM-DD HH:MM:SS, delimited by single quotes. Access GDO server SQL

See Attribute Filter Pipe

See Attribute Filter See Attribute Filter Pipe Pipe

See note below

If -defined format is ―Date‖, date value expressed as MM/DD/YYYY, delimited by pound signs. If -defined format is ―Time‖, time value expressed as HH:MM:SS, delimited by pound signs. If -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.

See Attribute Filter See Attribute Filter Pipe. Pipe.


ArcView GDO server SQL




MapInfo GDO server SQL




CAD GDO server See Attribute Filter SQL Pipe.



FRAMME GDO server SQL

See Attribute Filter Not ed Pipe.

See note below.


Date value expressed as MM/DD/YY, delimited by single quotes; time values are not ed. MGE GDO server SQL

See Attribute Filter Pipe

See Attribute Filter TBD - See note Pipe below.

See ODBC Tabular GDO server.

Differs according to ODBC driver in use. Approach to be taken is TBD.

394


Analyzing GeoMedia Professional Data Text, Memo

Byte, Integer, Boolean Long, Single, Double, Currency

Date

MGDM GDO server SQL


See Attribute Filter See MGE GDO Pipe. server.

See MGE GDO server.

MGSM GDO server SQL


See Attribute Filter Not ed Pipe.

See note below.

Keyword TIMESTAMP followed by date/time value expressed as YYYY-MM-DD:HH:MM:SS, delimited by single quotes. Oracle Relational GDO server SQL




Oracle Object See Attribute Filter GDO server SQL Pipe.



ODBC Tabular See Attribute Filter GDO server SQL Pipe.


See note below.

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 -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 -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 -defined format is ―Date/Time‖, the expression is defined by the keyword followed by date/time value expressed as YYYY-MM-DD HH:MM:SS, delimited by single quotes. SQL Server GDO See Attribute Filter server SQL Pipe.

See Attribute Filter See Attribute Filter See note below. Pipe. Pipe.

If -defined format is ―Date‖, the date value is expressed as YYYY-MM-DD, delimited by single quotes. If -defined format is ―Time‖, the time value is expressed as HH:MM:SS, delimited by single quotes. If -defined format is ―Date/Time‖, the date/time value is expressed as YYYY-MM-DD HH:MM:SS, delimited by single quotes.

To define and attribute filter query: 1. Select Analysis > Attribute Query.


395

Analyzing GeoMedia Professional Data 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.

5. Select an attribute from the selected feature class and click the down arrow below the Attributes box, or double click an attribute. MGE features use the MSLINK value as an identifier. Features in an MGE warehouse that have graphics but no attributes do not have an MSLINK value. When a query is performed on such features, the MGE data server assigns them MSLINK values that are numbered sequentially in the order that they are encountered-that is, sequentially within each category in map-table order. The first MSLINK number assigned is 16777217. When you view attributes in a data window or on the Filter dialog box, non-attributed features will have the MSLINK identifier assigned by the MGE data server, whereas attributed features will have an MSLINK, a MAPID, and other attributes. 6. Select an operator. If you select an operator from the drop-down list, you must click the down arrow to make it appear in the Filter box. 7. To see the list of values in the selected attribute, click Show Values.

If you checked Confirm show value operations on the Options dialog box, the confirmation message appears. 8. Type a value for the attribute in the Filter box, or select one from the list of values and click the down arrow, or double click an attribute. You can also type a value in the Values box. 9. that the SQL statement in the Filter box is correct; then click OK. For date and time queries—and possibly others—on MGE and MGDM connections, you may have to manually edit the SQL text on the Filter dialog box to issue a successful query. This is due to the varying SQL dialects of the various available ODBC drivers. 10. On the Attribute Query dialog box, accept or override the default query name, and optionally type a query description. 11. 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.

396


Analyzing GeoMedia Professional Data 13. that the Display query in data window box is checked, and change in the Data window name field, if appropriate, the data window in which to display the query results. OR To not display the query results in a data window, uncheck the Display query in data window box. 14. To display the query, click OK.

The query is displayed in accordance with the query options you set. See the ODBC documentation for instructions.

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

Available Spatial Operators The available spatial operators and example graphics of their results areas follows: Touch returns features that touch the defined features in any way-meeting, overlapping, containing, or being contained by. touch

with the Not qualifier

Contain returns features that surround defined features. Contained features can touch but not overlap the borders of the surrounding features. Points cannot contain other features. contain


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.


397

Analyzing GeoMedia Professional Data 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


Overlap returns features that overlap the defined features. overlap


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.

398


Analyzing GeoMedia Professional Data are within distance of


The spatial operators used by Spatial Query are different from the Oracle Spatial Cartridge specific operators used by the Native Query command when querying an Oracle warehouse.

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

To define a spatial or combined query: 1. Select Analysis > Spatial Query.

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. 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


399

Analyzing GeoMedia Professional Data 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. 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. 13. To display the query, click OK.

The query is displayed in accordance with the query options you set.

Defining Spatial Intersections Spatial Intersection allows you to perform a spatial overlay on two feature classes or queries to find the intersecting areas, or areas of coincidence. The spatial operators available for this command are touch, contain, are contained by, entirely contain, are entirely contained by, overlap, meet, and are spatially equal. After you choose the two sets of input features to intersect and the type of spatial operation to perform, this command outputs the results as a new query. The results include the geometry for the points, lines, and areas of spatial coincidence as well as the attributes for each pair of spatially intersecting features, that is, a spatial . The features can be point, line, area, or combinations of these feature types. You can output the resultant new spatial intersection to a map window and/or data window. Before Spatial Intersection After Spatial Intersection

In addition, you can set the style for the map window for optimum display results. One can think of this command as producing results that are the opposite of those produced by Spatial Difference as shown in the following two figures from the delivered Madison County, Alabama sample data set. 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.

400


Analyzing GeoMedia Professional Data Map features before using Spatial Intersection:

Spatial Intersection results with the touch operator showing the intersection of the Major Water Polygons features and the Parks features:

The following are two example workflows:  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.


401

Analyzing GeoMedia Professional Data To use spatial intersection: 1. Select Analysis > Spatial Intersection.

2. Select the first feature class from the top Features in drop-down list. 3. Optional: Click Filter to define an attribute filter for the selected feature class on the attribute filter dialog box. 4. Optional: Change the default spatial operator in the That drop-down list; then 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. 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. 11. 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. You may need to adjust the style for better viewing. See “Defining Spatial Queries” in this section for a description of the spatial operators. See “Defining Attribute-Filter Queries” in this section.

402


Analyzing GeoMedia Professional Data

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

The following cases are valid: From-feature

Subtract-feature

Result

area

area

area or nothing

line

area

line or nothing

line

line

line or nothing

point

area

point or nothing

point

line

point or nothing

point

point

point or nothing

The following cases are not allowed as input: From-feature

Subtract-feature

area

line

area

point

line

point

One can think of this command as producing results that are the opposite of those produced by Spatial Intersection. Or, one can think of a cookie-cutter process, with the results being the sheet of dough from which the cookies have been cut out, as shown in the following example from the delivered Madison County, Alabama, sample dataset:


403

Analyzing GeoMedia Professional Data 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.

See “Defining Spatial Queries” in this section.

To use spatial difference: 1. Select Analysis > Spatial Difference.

404


Analyzing GeoMedia Professional Data 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. 6. Optional: Change the default value in the Query name field. 7. Optional: Type a query description in the Description field. 8. that the Display difference in map window check box is selected, and change in the Map window name field, if appropriate, the default active map window in which to display the new spatial difference. OR To not display the new spatial difference in a map window, uncheck the Display difference in map window check box. 9. Optional: Click Style, and change the default style on the Select Style dialog box. 10. that the Display difference in data window box is checked, and change in the Data window name field, if appropriate, the default new data window in which to display the new spatial difference. OR To not display the nongraphic attributes of the new spatial difference in a data window, uncheck the Display difference in data window check box. 11. Click OK to generate and to display the new spatial difference in the specified map window and/or data window. You may need to adjust the style for better viewing. See “Defining Attribute-Filter Queries” in this section.

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

Defining Native Queries against an Oracle Warehouse When working with a connection to an Oracle database (with Spatial Cartridge), this command allows you to select the feature classes to query and an Oracle Spatial Cartridge spatial operator. The query is executed on the Oracle database, taking full advantage of the 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:


405

Analyzing GeoMedia Professional Data Touch-The boundaries intersect but the interiors do not.

Dist -The boundaries and interiors do not intersect.

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

Contains-The interior and boundary of one object are completely contained in the interior of the other. Inside-The opposite of Contains. A Inside B implies B Contains A. Covers-The interior of one object is completely contained in the interior of the other, and their boundaries intersect. Covered By-The opposite of Covers. A Covered By B implies B Covers A. Any Interact-The objects are non-dist. This is the default operator unless there is a valid session preference. 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.

406


Analyzing GeoMedia Professional Data To define an Oracle native query: 1. Select Analysis > Native Query.

2. From the Connection drop-down list, select an Oracle connection. 3. From the Select features in drop-down list, select the feature class on which to query. 4. Optional: Click Filter to define an attribute filter for the selected feature class on the attribute filter dialog box.

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. 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.


407

Analyzing GeoMedia Professional Data 12. 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. If you do not select either a map window or a data window, the query is only appended to the query folder. See “Defining Attribute-Filter Queries” in this section.

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

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

Offsetting to the Right or Left Offsets can be positioned to the right or left of the centerline by typing a positive number or a negative number, respectively, in the Offset field. If you use a fixed offset that is a positive number, the offset is to the right of the centerline when you are looking in the positive direction of

408


Analyzing GeoMedia Professional Data a highway (the direction of increasing distance). If you use a fixed offset that is a negative number, the offset is to the left of the centerline when you are looking in the positive direction of a highway (the direction of increasing distance). Scaled offsets are different because the offset display is depends on the value used in the database offset column (Scale attribute). If you use a scaled offset size that is positive and the offset value in the database is also positive, the offset is displayed on the right of the centerline. If your database offset value is negative, the offset is displayed to the left of the centerline. However, if you use a scaled offset size that is negative and the database offset value is positive, then the offset is displayed to the left of the centerline. If your database offset value is negative, the offset is displayed to the right of the centerline. The command retrieves the scale attribute value from the database and multiplies it by the scale factor to obtain the offset distance in the specified unit of measure. The scale factor is the server the command applies to the value of the scale attribute of the segment.

To define an MGSM native query: 1. Select Analysis > Native Query. 2. From the Connection drop-down list of the Native Query dialog box, select the MGSM connection that s native queries.

3. From the Select features in drop-down list, select the feature class on which to query. 4. Optional: Click Filter to define an attribute filter and/or an overlay filter for the selected feature class on the Filter dialog box. 5. Select the appropriate offset type(s), Fixed offset and/or Scaled offset. 6. Enter the appropriate corresponding offset parameters. 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. 9. 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.


409

Analyzing GeoMedia Professional Data 11. 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. If you do not select either a map window or a data window, the query is only appended to the query folder.

Defining Linear Network Queries If you are using an MGSM warehouse, you can define the search conditions for a linear network query by combining sets of segments in distributed attribute tables with overlay operators. The distributed attribute values that the query returns are displayed as point or linear segments along their respective network linear features. These new segments are created dynamically when you display the query. The following overlay operators are available:  The intersect operator searches for segments that overlap. For example, a query for accidents that intersect construction returns only segments containing accidents where there is also construction.



The difference operator searches for segments that differ. For example, a query for accidents that differ from construction returns only segments containing accidents where there is no construction.

You can also apply attribute filters and spatial queries to linear network queries. For example, you can build a query to find roads that intersect construction and touch wetlands where geese have nests. The linear network query finds roads that intersect construction.  The spatial query limits the search for roads that intersect construction to those that touch wetlands.  The attribute filter limits the search for roads that intersect construction to those where geese have nests. The procedures for creating a linear network query are the same as for any other query, except that you can include intersect and difference overlay operators.

To define a linear network query: 1. 2. 3. 4.

410

Select Analysis > Native Query. From the Select features in drop-down list, select a feature class or query. Click Filter. Select an attribute, and click the down arrow below the Attributes box.


Analyzing GeoMedia Professional Data 5. 6. 7. 8.

Select an operator and, if necessary, click the down arrow in the Operators box. To see the list of values in the selected attribute, click Show Values. Type or select a value, and click the down arrow below the Values box. Click Add Overlay to display the Add Overlay dialog box.

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. 9. Select an overlay operator from the drop-down list. 10. Select a distributed attribute table. 11. Click OK.

12. 13. 14. 15. 16.

On the overlay tab, select an attribute, and click the down arrow below the Attributes box. Select an operator and, if necessary, click the down arrow in the Operators box. To see the list of values, click Show Values. Type or select a value, and click the down arrow below the Values box. To add an additional overlay, click Add Overlay, and repeat Steps 9 - 15.

Clicking Remove Overlay removes the overlay displayed on the active tab, thereby removing that portion of the query statement. 17. Click OK. 18. On the Native Query dialog box, type a name and optional description for the query. 19. 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.


411


Displaying Queries In general, a query is displayed automatically when you build it. If you build a query without displaying it-to use in another query or for creating a thematic display, for example-there are many ways to display it later.

To display a query: Add the query to the legend. This displays queries in the active map window and ignores query option settings. When a data window is active, select Data > Change Contents, and select the query.

Open a new data window, selecting the query as the data you want to display.

Or, use the Analysis > Queries command to display a query. This command also lets you edit, delete, and unload queries. The icon beside each query name on the Queries dialog box indicates information about the query, including its status and geometry type (if available), as follows: Closed query AnySpatial Areas Image Line

Nongraphic Point Graphics Text Unknown, graphic type cannot be determined Invalid, query cannot be opened

Or, use the following procedure: 1. Select Analysis > Queries.

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.

412


Analyzing GeoMedia Professional Data 2. From the Queries dialog box, select the query you want to display, and click Display.

3. On the Display Query dialog box, select a window in which to display the query. 4. To display the query in a new window, type a name in the appropriate window name field. To display the query in an open window, select it by name from the drop-down list. 5. To change the style of a query display in a map window, click Style, define the style, and click OK on the Style dialog box. The style of the query depends on the feature class type returned by the query. 6. Click OK.

Editing Queries Once a query has been defined, you can change everything except the feature class or query on which it is built. If you change a query name, the new name is not changed in any existing legend-entry titles, data-view captions, or dependent query names. Editing a query that is used as input to other queries may affect the other queries. If a feature class or query that is used in a query changes, the dependent query is also affected:  Changes to the definition of a feature class or query can invalidate a dependent query. If the dependent query is an attribute-filter query, its display will be removed from the map window. Data windows associated with the feature class will not contain any data if the dependent query is rendered invalid by the change.  If you close the connection to a warehouse containing a feature class on which a query is dependent, the data will be removed from the display, but you will have to edit the legend to remove the entry.

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 or the Label dialog box. The Query Properties dialog box has a different appearance with queries generated from the following commands: Analyze Geometry, Attribute Filter, Geocode Addresses, Geocode Coordinates, , 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.


413

Analyzing GeoMedia Professional Data 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.

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.

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

414


Analyzing GeoMedia Professional Data For best results when using the Spatial Query command, you should create and apply filters to spatially constrain the search area. The spatial query alone does not spatially constrain the search area of the subject feature class. See “Defining Spatial Queries” in this section. The Spatial Filter command lets you perform the following:  Define filter geometry and perform spatial filtering at the GeoWorkspace level.  Select filter options.  Set the active filter to the map window.  Use and manage named spatial filters. Spatial Filter lets you perform all of these tasks though the Spatial Filter dockable control, which puts filtering at your fingertips.

This dockable control displays the name of the currently active spatial filter (if any) in a read-only field and contains command buttons for defining and managing spatial filters, as discussed in the following sections. This control is persistable. Thus, if you save a GeoWorkspace with the control hidden, when you next open this GeoWorkspace, the control is not displayed. To display the control again, you must select Warehouse > Spatial Filter, or select Spatial Filter from the right mouse menu.

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

Default Filter Name

Named Spatial Filter

Select Reference Features

Selected Reference Feature Filter

Select Set

Select Set Filter


415

Analyzing GeoMedia Professional Data Filter Type

Default Filter Name

Active Map Window Extent

Map Window Extent Filter

Rectangular Fence

Rectangular Fence Filter

Polygonal Fence

Polygonal Fence Filter

Circular Fence

Circular Fence Filter

Remove Filter

No Active Filter

By Placing a Fence You can define a spatial filter by simply following the standard digitizing prompts to place one of the following fence types in the active map window:  Rectangular Fence - (Rectangular Fence Filter)  Polygonal Fence - (Polygonal Fence Filter)  Circular Fence - (Circular Fence Filter)

By Selecting Reference Features You can use Select Reference Features (Selected Reference Feature Filter) to define a spatial filter by selecting one or more reference features by name from a feature class of area, compound, or raster geometry type whose geometry will be used as a spatial filter, using the following dialog box. Spatial filter reference features are designated through the Spatial Filter Reference Features command. See “Designating Spatial Filter Reference Features” later in this section.

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.

416


Analyzing GeoMedia Professional Data To create the final filter geometry, feature geometries that are not areas (for example, linear or point geometries from a compound feature class) are first discarded. Then if the number of selected feature instances is more than one, a single geometry is created by merging the remaining feature instances' geometries. In case the final geometry (single or merged) does not contain area geometries, the command displays an error message.

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

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

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

Defining Spatial Filter Workflows The following workflows show the procedures for defining spatial filters by the various methods discussed.

To define a spatial filter by selected reference features: 1. Select Warehouse > Spatial Filter.


417

Analyzing GeoMedia Professional Data 2. Click Select Reference Features on the dockable control.

3. Select the appropriate reference feature from the Select features from tree view.

4. Select the appropriate Feature name attribute from the drop-down list. 5. Click Show Values.

6. Select the appropriate attribute value(s) from the Features to use as spatial filter list; then click OK. The Features to use as spatial filter list s multiple selection.

The filter geometry is created, the dialog box is dismissed, and filtering is performed. Merged geometry of the selected features is displayed in the active map window. To define a spatial filter by select set: 1. Create a select set of the features needed for your workflow. 2. Select Warehouse > Spatial Filter. 3. Click Select Set on the dockable control.

Filter geometry is created from the select set, and filtering is performed. To define a spatial filter by active map window extent: 1. Adjust the map window so that it displays the data needed for your workflow

418


Analyzing GeoMedia Professional Data 2. Select Warehouse > Spatial Filter. 3. Click Active Map Window Extent on the dockable control.

Filter geometry is created from the active map window extent, and filtering is performed. To define a spatial filter by fence: 1. Select Warehouse > Spatial Filter. 2. Click Rectangular Fence on the dockable control; then draw a rectangular fence to define the filter area. OR Click Polygonal Fence on the dockable control; then draw a polygonal fence to define the filter area. OR Click Circular Fence on the dockable control; then draw a circular fence to define the filter area.

Filter geometry is created from the digitized fence, and filtering is performed.

Managing Spatial Filters After you have defined spatial filters, you can manage these filters by using the following commands accessed from the Spatial Filter dockable control: 

Spatial Filter Options



Fit Spatial Filter



Named Spatial Filters



Remove Filter

Spatial Filter Options When you first define a spatial filter, it takes the default filter options. However, you can easily change these to meet your specific workflow needs through the Spatial Filter Options. These options let you control the behavior of spatial filtering by setting the spatial operator, filter geometry, map window display and fit, and display style, using the following dialog box, which shows the default options:

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.


419

Analyzing GeoMedia Professional Data Entirely Inside-Lets you access only data that falls completely within the boundaries of your spatial filter geometry. No spatial filter applied Inside Entirely Inside

Coarse Overlap-Lets you access all data inside or overlapping the boundaries of your filter, but it may also return some additional features. The purpose of this operator is to allow the data server to quickly and efficiently return data according to its internal spatial indexing system, without doing individual geometry comparisons against the boundaries of your spatial filter geometry. This processing varies with server efficiency and data complexity. Overlap-Lets you access any feature that falls within or touches the boundaries of your spatial filter geometry.

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

420


Analyzing GeoMedia Professional Data 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- filtering method, and Coarse Overlap is always used as the first filter. The Coarse Overlap filter always provides the best performance in an Oracle environment. Spatial Filter Options also lets you choose to filter the geometry by using the minimum bounding rectangle (MBR) of the defined geometry, the Geometry extent (MBR), which is faster because filtering is not unnecessarily bogged down by very complex area definitions, or by using on the default actual defined geometry (Actual geometry), which is more precise. This command also gives you the option of fitting (auto fit) the filter with the MBR value of the active spatial filter, with a margin of 5% in the map window of your choice from all those in the GeoWorkspace (Automatically fit filter in check box, off by default). And you can optionally display the currently active spatial filter in the active map window at all times (Display filter on by default). Finally, you can change the area style used to display the active filter in the active map window through the Select Style dialog box.

To define spatial filter options: 1. Select Warehouse > Spatial Filter.

2. Click Spatial Filter Options on the dockable control.

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

Fit Spatial Filter Fit Spatial Filter lets you easily fit the active map window with the minimum bounding rectangle (MBR) value of the currently active filter, with a margin of 5%.

Remove Filter Remove Filter (No Active Filter) simply removes the existing active named spatial filter with a single click. The active filter can be a -named filter or a system-defined filter.


421


Named Spatial Filters Named Spatial Filters lets you choose an existing named spatial filter as the active filter, rename the active filter for later use, and delete previously named filters, using the following dialog box.

This dialog box displays the currently active spatial filter name in the Active filter field, in the same manner as the dockable control. This field is always enabled, locked, and grayed to indicate it is read-only. Also displayed are the names of all the GeoWorkspace spatial filters, except the active filter, in the Named filters list. The default spatial filter name is SpatialFilter , 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 -named spatial filter. Thus, only system-defined filters can be named and stored in the spatial filters collection. Also, you can never rename a named spatial filter. This adds the active spatial filter definition to the filter list with the name specified, and with the spatial operator currently defined for the command. The filter geometry added is either the actual active filter geometry or the MBR of the active filter geometry, according to the Filter by geometry extent setting from the Spatial Filter Options dialog box.

You can easily delete spatial filters by simply selecting one or more names from the list of named filters, and then clicking Delete. Deleting a spatial filter does not affect any existing legend entries, data windows, or queries.

To manage spatial filters: 1. Select Warehouse > Spatial Filter.

422


Analyzing GeoMedia Professional Data 2. Click Named Spatial Filters on the dockable control.

3. To apply an existing filter, select a name from the Named filters list; then click Apply. OR Double click a filter name.

Filtering is performed with the filter geometry and spatial operator of the selected filter. 4. To rename the active filter (not a named spatial filter), click Name.

5. Type the new name in the Name field; then click OK. 6. To delete a filter, select the name(s) from the Named filters list; then click Delete.

Designating Spatial Filter Reference Features Spatial Filter Reference Features lets you designate feature classes that will not be subject to spatial filtering. These spatial filter reference features provide you with a visual reference system for defining spatial filters. You can select a set of individual feature classes from any number of warehouse connections, rather than a single, entire connection. When a feature class is designated as containing spatial filter reference features, it plays that role in addition to its routine role as a spatially-filtered feature class. It is available in both filtered and unfiltered form. You can thus select the unfiltered form from the Reference Feature node for use with other commands, for example Add Legend Entries and Attribute Query. To designate spatial reference features, you first select a connection to display the corresponding feature classes from which you select those you want to designate. You cannot designate nongraphic feature classes or queries as spatial filter reference features. Spatial filtering is inherently performed through data servers, while queries inherit spatial filtering through the filtering of their input data. However, you can create queries from reference features, which yields essentially the same effect. It is easy to identify all feature classes within a connection as being spatial filter reference features. However, any feature classes subsequently added to the connection are not automatically considered to be reference features. In other words, it is the feature classes within the connection, not the connection itself, which are so designated. Once defined, the reference features appear in tree views across the product in the commands, for example Attribute Queries and , and controls to reference features. Reference features are thus displayed in the tree views 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.


423

Analyzing GeoMedia Professional Data After designating your reference features, you would typically define a corresponding spatial filter using the Select Reference Features command, as in the following workflow.

To designate spatial filter reference features: 1. Select Warehouse > Spatial Filter Reference Features.

2. Select the appropriate connection. 3. Check the appropriate Feature classes check box(es); then click OK.

All the selected feature classes are set as reference features. Any unselected feature classes that were previously reference features are reset as non-reference features. If a connection node is checked/unchecked, all the feature classes available in the connection are checked/unchecked. 4. Click Select Reference Features on the dockable control. 5. Select the States feature class from the Select Features from drop-down list. 6. Select STATE_NAME from the Feature name attribute drop-down list; then click Show Values.

424


Analyzing GeoMedia Professional Data 7. Select Alabama from as the feature to use as a spatial filter; then click OK to perform the filtering.

Querying Graphics-Only Features in MGE and MGSM The MGE and MGSM data servers expect valid map ID values in attribute tables, which means that the feature geometries actually exist in the design file identified by the map ID. This allows the data servers to limit queries for geometry to the identified design file. If a query on an MGE or MGSM warehouse includes graphics-only features (features that have no associated attribute table) or if map IDs are not valid, the query could take a very long time, depending on the number of design files that must be searched. This is because the server has to search all design files allowed by the spatial filter. See the “Creating Data Server .INI Files” topic in GeoMedia 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.

Working with Queued Edit The Queued Edit command on the Tools menu lets you sequentially review selected items for potential edit of the geometry and the non-graphical attributes of the located items. Each item is thus presented in sequence, so you do not have to perform time-consuming searches. Then as you review and/or fix each item, the queue is automatically updated. Furthermore, if you fix an item in the data window, the solution is automatically reflected in the map window and vice versa. You can use this command in two general workflows: as a review and edit tool for an operator performing an operational task, and as a tool for performing formal Quality Assurance/Quality Control tasks. The review items located by this command may or may not have geometry, and they can be of two kinds: standard review items available in the GeoWorkspace, that is, feature classes, categories, and queries; and items in a previously created queue. A queue is a special list of items selected for review, as generated by commands in GeoMedia Fusion (for example, a queue of geometric anomalies produced by the Advanced Geometric Validation >Advanced Validate Geometry


425

Analyzing GeoMedia Professional Data command), PixelQue, Map Editor, or other software, not by GeoMedia Professional. GeoMedia Professional currently does not have any commands that generate queues. However, the process of locating and stepping through selected items for review is similar for both standard review items and for queues. When working with queues, nevertheless, the Queued Edit command has additional capabilities, such as changing the status of queue items and creating subqueues. This section describes the use of this command with standard items and with queues. The active queue may be closed by various actions. These include placing a spatial filter in the GeoWorkspace, closing the connection containing the queue information, and changing the attribute filter query if you are looking at a query through Queued Edit. If this occurs, you need to re-open the queue to continue your workflow.

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

426



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

Using the Queued Edit Dockable Control Selecting Tools > Queued Edit opens the Queued Edit dockable control for selecting, navigating, and managing standard review items and queues. Some non-GeoMedia Professional commands automatically open this control when they create a queue. In the following example, the queue is designated as a dynamic queue by the yellow icon to the left of the queue name. A static queue is designated by a white icon.


427

Analyzing GeoMedia Professional Data 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 ed. After displaying the first item you can perform the following management tasks: 

Navigate through the subsequent items



Set options for viewing the items



Sort the items



Track the status of queue items



Delete queue items by status



Delete queues



Create subqueues



Show queue statistics



Access additional options and commands to manipulate the standard review items and queues

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

Reviewing and Updating the Status The Status Review/Update field displays the status for the current queue item - for static queues only, not for dynamic queues or standard review items. The status is generated by the process that created the queue. You can change the status of the active queue item (for example, from "Linked" to "Unlinked") by selecting a new value from the drop-down list. When you change the value, the status is updated in the queue, and the queue advances to the next item if you selected the Automatically advance when status changes check box on the Queuing Options dialog box General tab.

428


Analyzing GeoMedia Professional Data The Status Review/Update is disabled for queues generated by the GeoMedia Fusion Advanced Geometric Validation > Validate Geometry command.)

Using the Queued Edit Map Window The Queued Edit Map Window opens automatically when standard review items or a queue is selected on the Queued Edit control or upon queue navigation. As seen in the following example, this window contains two sections: the Queued Edit Map Window legend on the left and the map display on the right. This map displays the graphic attributes of the active review item. A legend entry is added to the Queued Edit Map Window legend for each item geometry, and the current item is initially displayed in a centered and fitted view in the Queued Edit Map Window.

The item graphics are displayed to the Queued Edit Map Window by placing each item geometry in the Queued Edit Map Window legend. On initial creation, there is one legend entry per geometry field identified, but you can add other feature classes or queries to this legend. You can also change the order of item legend entries and style, and the modified order and style is maintained upon a move next, move previous, move first, or move last action in the sequence. To customize the map, you can set options for defining an item locator and for viewing the map window display on the Queuing Options dialog box, which is accessed by clicking the Options button on the control.

Setting View Options The View tab on the Queuing Options dialog box lets you define the view options. When you zoom in, zoom out, or fit the view of an item in the Queued Edit Map Window, the view adjusts according to these view options.

The Zoom In/Out and Fit current queue item buttons on the dockable control let you control the map window view. They make use of the values on the View tab in the Zoom factor field and the


429

Analyzing GeoMedia Professional Data 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. 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. The features or the geometry that make up the queued item are not required to be in the legend of the other map windows for this to work as it does for a query. The following example illustrates the view before selecting the Honor setting from Map Window Properties during queue navigation check box.

The following example illustrates the view after selecting the check box during navigation, with the Fit and zoom out map window property set to 500%.

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

430



Using the Queued Edit Data Window The Queued Edit Data Window displays the nongraphic attributes of the active review items. It does not display geometry attributes or spatial attributes.

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

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

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


431

Analyzing GeoMedia Professional Data Show description box-Displays a description box on the control that contains an optional description for each queue item. This option is for queues only. Automatically advance when status changes-Advances the current queue item when you change the status of a queue using the Status Review/Update field on the Queued Edit control or the Queued Edit QuickStatus control. This field displays the current status value and lets you update the status of the active queue item. This option is for queues only. If the current queue item is deleted or removed from the queue, the next item becomes current. Add item to select set-Adds the graphic elements of the review items to a select set as you navigate through the items. This option is for standard review items and for queues. Clear Queuing Legend when queue closes-Clears all Queued Edit Map Window legend entries when you close a queue. This option is for standard review items and for queues. Show number of items in a queue-Displays the number of located queue items next to the corresponding name on the Queued Edit control. For dynamic queues from closed connections, the number displays as (0). This option is for queues only.

When this option is set, it may take longer for the queue name lists to display because a count of each queue is being made. Therefore, when queues contain many items, setting this option is not recommended.

Using Additional Commands Clicking the Additional Commands button on the control displays a menu with the following commands that let you manipulate queues according to your workflow. The Sort ascending/descending commands also work with standard review items.

Delete Queue, Create subqueue, and Show statistics are enabled when a GeoWorkspace is open, whether a queue is selected or not.

432


Analyzing GeoMedia Professional Data Delete queue-Deletes one or more queues/subqueues in one operation according to your selection on the Delete Queue dialog box. Deleting a queue also deletes its subqueues and all associated metadata. This command is for queues only.

Create subqueue-Creates a subqueue for any queue through the Create Subqueues dialog box. When you create a subqueue, it becomes the active queue. A subqueue is a -defined subset of a queue, that is, a view into a specific queue. You can create subqueues for queues but not for subqueues. The items in the subqueue remain in the parent queue. If you delete the parent queue, the subqueues are also deleted. Subqueues are the same type of queue as parent queues. That is, if the parent queue is dynamic, the subqueue is dynamic; if the parent queue is static, the subqueue is static. As with parent queues, dynamic subqueues are designated on the Queued Edit control by a yellow icon, static subqueues by a white icon. To create a subqueue, you first select the parent queue and then name the subqueue. You can create a subqueue based on one of two criteria: attribute filter (the default) or spatial filter. If an attribute filter, you select the Attribute filter option and then click Define, which displays the GeoMedia standard Attribute Filter dialog box for you to define an attribute query filter. If a spatial filter, you select the Spatial filter option and then select a filter from the corresponding drop-down list of spatial filters defined for the GeoWorkspace. This command is for queues only.

Show statistics-Displays information about a queue and its items on the Show Statistics dialog box. This information includes the name of the queue, the name of the process that created the queue, and the number of items in the queue. If the Status field is defined for the queue, the information includes the number of items with each defined status. If subqueues have been created, the information includes the number of subqueues, the names of the subqueues, and the number of items in the subqueues. You can also generate a queue report that displays in your default text editor. This command is for queues only.


433


Delete queue items by status-Deletes all the items in the active queue that have a particular status through the Delete Queue Items by Status dialog box. This command is for queues only.

Queued Edit QuickStatus-Displays the Queued Edit QuickStatus dockable control, which lets you quickly access and update the statuses of queue items by eliminating the need to scroll through the drop-down list of statuses in the Status Review/Update field on the Queued Edit control. This control is for use only with queues having a status defined. A tooltip displays the text associated with each status number, which is the same text displayed in the Status Review/Update field on the Queued Edit control. This command is for queues only.

If you want to use this control to change a series of statuses, select the Automatically advance when status changes option on the General tab of the Queuing Options dialog box before beginning this procedure. Sort ascending/descending-Sort the active review items or queue and the Queued Edit Data Window in ascending or descending order by attribute. This command is for standard review items and for queues.

Working with Searches A search locates a point of interest in the map window. You can do this with a text string to search the specified feature class, or with a query for features that have attribute values that match this string. You can create and perform searches though two related commands, Searches and Search. You use the Searches command to create, to change, and to manage

434


Analyzing GeoMedia Professional Data predefined searches. And, you use the Search command to perform these predefined searches or to create and directly perform ad hoc searches. Both types of searches locate the appropriate items and display them in the regular map window and the Search Data Window, allowing you to then perform operations on the results according to your workflow. This section discusses these two commands and how to create and to perform the different types of searches.

Creating and Managing Predefined Searches The Searches command lets you perform the following: 

Create predefined searches



Edit predefined search properties



View predefined searches and their descriptions



Delete predefined searches

Selecting View > Searches displays the Searches dialog box containing a list of all existing predefined searches in the active GeoWorkspace and, when one is selected, its corresponding description.

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.


435

Analyzing GeoMedia Professional Data 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.

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 s.

436


Analyzing GeoMedia Professional Data 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).

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.


437


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

To begin a search, you select one of the following:  A feature class, query, category member, or reference feature for an ad hoc search.  A predefined search, created through the Searches command, from the drop-down list, located in the Searches branch of the tree view. Depending on the search type selected, the dockable control takes one two forms, ad hoc or predefined.

Performing Ad Hoc Searches For an ad hoc search, the drop-down list, the key-in field, and the Options and Search buttons are enabled.

To create an ad hoc search, you select a feature or query (from the features, queries, categories, and reference features drop-down list) to search, type an appropriate text value, and then click Search to perform the search and to display the results, as in the following example. The Search command constructs an attribute query, executes it, and feeds the results into the Queued Edit control.

438


Analyzing GeoMedia Professional Data 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. It may be helpful when first using this command to practice using the input query you construct in the Analysis > Attribute Query command to ensure that it is correct and returns appropriate results. You can then use it to perform your ad hoc search.

Performing Predefined Searches For a predefined search, the dockable control appearance varies according to the type of search. If the search does not require attribute value input, that grid does not appear, as in the following example, with the Options and Search buttons enabled. To perform such a search, you only need to click Search to display the results.

If the search does require input, an attribute (prompt)/value grid is displayed and enabled along with the Options button. The Search button is enabled when you type a value for the displayed attribute. To perform such a search, you type the appropriate value and then click Search to display the results.

The number of rows in the grid is the same as the number of unique parameter values defined when the search was created with the Searches command. The Search command populates the left-hand column of the grid with parameter names extracted from the SQL of the predefined search. The right-hand column is for your data entry. The command substitutes the values entered for the SQL parameters, executes the query, and feeds the results into the Queued Edit system. If the search requires more than two substitutions, the grid has a vertical scroll bar, as in the following example.

Using the Queued Edit Control Whether your search is ad hoc or predefined, the search output is displayed as a queue using the Queued Edit control on the bottom of the Search dockable control in the map window and in the Search Data Window. You can use this control for navigating among multiple items returned by the search.


439

Analyzing GeoMedia Professional Data The Queued Edit control saves the map window name, Search Data Window, and the legend, so that if you delete the Search map window or data window, it can create the window again when you try to navigate the queue again. If you have deleted the map or data window and created a new one (with the same name as the original Search window), the Queued Edit control creates the window and adds ―1‖, or whatever number makes it unique to the name. You can define the extent of the map window using Queued Edit options and use the Spatial Filter Options to reset the spatial filter.

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

Setting Queuing Options You can set options for viewing the map window display and for defining an item locator through the two tabs on the Queuing Options dialog box, which is displayed by clicking the Options button on the control. The View tab lets you define the view options. When you zoom in/out or fit the view of an item in the map window the view adjusts according to the view options. The Locator tab lets you define the locator, which consists of two graphical elements, the locator box and the crosshairs.

See “Setting View Options” in the “Working with Queued Edit” section for more information on using this dialog box.

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

440



Working with s A query combines data from two feature classes or queries that have common attribute values. For example, a would return all attributes for parcels from the parcel feature class along with parcel ownership information from another feature class, based on a common parcel ID, even if the latter feature class is in another warehouse. The command lets you specify feature classes or queries to along with the attributes within those feature classes or queries to on, and the type of operation to perform. To create a 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. 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 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 or the inner portion of a left outer or right outer .

Defining s You can create the following types of s: Inner

Records are added to the only if the value from the left field matches the corresponding value in the right field. Records from either feature class that do not match are not included in the .

Left outer

All records from the left feature class are included in the , but only matching records from the right feature class are included. Records from the right feature class that do not match are not included.

Right outer

All records from the right feature class are included in the , but only matching records from the left feature class are included. Records from the left feature class that do not match are not included.

Full outer

All records from both feature classes are included in the .

In any of the outer s, fields in records with unmatched values have null values. Accordingly, 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. To display the in a map window, the software uses the geometry from the left feature class or query. So, when you create a 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 dialog box.


441

Analyzing GeoMedia Professional Data To create a : 1. Select Analysis > .

2. 3. 4. 5.

From the Left side of drop-down list, select the left feature class or query. From the Right side of drop-down list, select the right feature class or query. From the lists of available attributes, select the attributes on which to create a . Click the down arrow to add the attribute pair to the Selected attribute pairs list.

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 . 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).

See GeoMedia Professional Help for more information on using this dialog box. When you hover over an entry in either list, a tooltip is displayed indicating the name of the field. 8. Select the type of to perform.

442


Analyzing GeoMedia Professional Data 9. In the Query name field, type a name for the or accept the default name. 10. Optional: Type a description for the . 11. Select a window in which to display the . If you select a map window, you can also change the style of the . 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  Area features-area, perimeter, area/perimeter  Linear features-length, azimuth, bearing  Point features-geographic coordinate, projection coordinate, height 2  Compound features-area, length, perimeter, area/perimeter , length, azimuth, bearing, geographic coordinate, projection coordinate, height  Graphics text features-geographic coordinate, projection coordinate, height  Raster features-none In addition, you can use this tool as an analytical tool to find certain specified conditions. For example, you could use it to locate all the parcel areas of a certain size or to prepare a thematic map. You access Analyze Geometry from the Analysis menu. This tool takes a feature class or query as input and outputs the results as a new query containing all the fields from the input feature class, plus additional fields for each appropriate geometry statistic selected on the dialog box. You can display this resultant query in a map window and/or a data window. In addition, you can set the style for the map window for optimum display results. A query or data window sort can be performed to find small areas or short lines, which allows greater flexibility in the use of the tool. For example, you may want to find all features with large area or those with areas within a specific range. The default unit values are populated from the Units and Formats tab of the Coordinate System Properties dialog box, but you can change them. The distance and area units, however, are not displayed in the output query. See GeoMedia 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.


443

Analyzing GeoMedia Professional Data 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. After running Analyze Geometry, you can perform maintenance on the detected conditions. Any changes you make to the geometries of the features for which the statistics were calculated update the statistics automatically in any open map window and/or data window displaying the affected features. For example, if you wanted to delete small areas found by Analyze Geometry, you would do as follows: 1. Run Analyze Geometry to find the small areas. 2. Open a data window on the new query. 3. Sort the area column. 4. Select all rows with less than the appropriate area. 5. Delete the selected rows.

The data window and map windows are updated for the deletion.

Analysis Options You can choose from among the following analysis options for the statistics you need:  Area-Calculates the area of each feature with an area geometry and stores the value in a new field called Area. The area is calculated only for those features with an area geometry; any other geometries are ignored. If the input feature class or query is a linear geometry, this option is ignored.  Perimeter-Calculates the perimeter of discontiguous geometries, and holes are ed for in the area calculation each feature with an area geometry and stores the value in a new field called Perimeter. The perimeter is calculated only for those features with an area geometry; any other geometries are ignored. If the input feature class or query is a linear geometry, this option is ignored. 2  Area/Perimeter -Calculates the area/perimeter_2 ratio for each instance of the selected feature class or query with an area geometry. The value is stored in a new field in the output query set called AreaPerimeterRatio. If the input data contains compound feature classes, the statistic is calculated only for those features with an area geometry. The statistic is not calculated for dist area geometries. If the feature is a collection containing area and line or point geometries, the statistic is still calculated for the area geometry, while the other geometries are ignored. If the input data is a linear geometry, this option is ignored.  Length-Calculates the length of discontiguous geometries, and holes are ed for in the area calculation each feature with a linear geometry and stores the value in a new field called Length. The length is calculated only for those features with a linear geometry; any other geometries are ignored. If the input feature class or query is an area geometry, this option is ignored. Discontiguous geometries are ed for in the length calculation.  Azimuth-Calculates the azimuth for each feature with a linear geometry and stores the value in a new field called Azimuth. The azimuth is calculated only for compound and linear features.  Bearing-Calculates the bearing for each feature with a linear geometry and stores the value in a new field called Bearing. The bearing is calculated only for compound and linear features.  Geographic Coordinate-Outputs the geographic coordinate for each feature with a point or text geometry and stores the values in two new fields called GeographicFirstCoord and GeographicSecondCoord. The geographic coordinate is output only for compound, point, and text features.

444



Projection Coordinate-Outputs the projection coordinate for each feature with a point or text geometry and stores the values in two new fields called ProjectionFirstCoord and ProjectionSecondCord. The projection coordinate is output only for compound, point, and text features.  Height-Calculates the height for each feature with a point geometry and stores the values in a new field called Height. The height is calculated only for compound, point, and text features. The output feature class or query contains a new field for each selected analysis option that applies to the geometry type of the input feature class or query. The default headings of the new fields are those previously listed. If a column exists with one of these names, the new name is the same but with a ## symbol appended to the end of the name, where ## begins at 01 and is incremented until a unique name is found.

To analyze geometry: 1. Open a read-write warehouse. 2. Select Analysis > Analyze Geometry.

3. Select a feature class or query from the Features to analyze drop-down list. 4. Select the appropriate analysis statistics option(s) from the list in the Analysis options selection area.

5. 6. 7. 8.

9. 10.

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 -selected options are retained. Type an appropriate name in the Query name field. Optional: Type an appropriate query description in the Description field. Optional: Click Units and Formats, and change the values appropriately on the Units and Formats tab of the Coordinate System Properties dialog box. 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. Optional: Click Style, and change the default style on the Select Style dialog box. 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.


445

Analyzing GeoMedia Professional Data 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.

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.

446



Placing Buffer Zones around Features A buffer zone is a region around or within one or more features, generally used for spatial analysis or as input to spatial queries. When you use the Analysis > Buffer Zone command to place buffer zones, you are creating a query that is associated with an existing feature class. These buffer zones are inserted as area features. You can define and place buffer zones around point, linear, area, and compound feature classes (not graphics text, raster, or nongraphic features) or around the results of a query. Buffer zones work best when the coordinate systems of the GeoWorkspace and warehouse are matched and set to an equal area projection. This command outputs the buffer zones to a map window and/or data window. Buffer Zone is enabled when a map window is active and there is at least one open warehouse connection.

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 ed, including stacks, rings, and buffer zones in the interior of areas. The buffer zone distance can be of two kinds, constant or variable.

When using a constant distance, you set the distance value and unit. You must type the distances as follows:  Single-A simple number, for example: 10  Stacked-Numbers separated by semicolons (;), for example: 10;20;30  Ringed-Numbers separated by colons (:) and semicolons (;), for example: (start/end) 10:20;30:40 The default value for unit is from the Unit setting on the Units and Formats tab of the Define Coordinate System File dialog box. When using a variable distance, you select an attribute that contains distance values that may vary on a per-feature basis. Only attributes of type text, byte, integer, long, single, double, and currency are available for selection. These values must be in the ground units of the coordinates system of the data you are buffer zoning. If this is not the case, you can construct an expression using the Functional Attributes command, which performs any required unit conversion and formatting. See “Working with Functional Attributes” in this section.


447

Analyzing GeoMedia Professional Data You have the option of setting the type of end caps to place around the ends of linear or compound features, either rounded (default) or squared. You can also set the output of the touching buffer zones as merged or unmerged (default). Unmerged output contains one output buffer zone placed around or within each feature for each input feature-distance combination. Overlapping buffer zones are not merged. Diagram A below shows six unmerged buffer zone features. Merged output contains the originally resulting output buffer zones merged in such a manner that overlapping sets of buffer zone features are merged, but discontiguous buffer zones from a single input feature retain their grouping. Diagram B below shows four buffer zone features, one of which consists of three previously unmerged buffer zone features.

A

B

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.

448


Analyzing GeoMedia Professional Data The following diagrams show example buffer zones around different geometries and how they vary with both positive and negative distance:

Working with Functional Attributes The Functional Attributes command lets you create new query-based attributes. This command s the calculation of on-the-fly, dynamic attributes based on geometry measurement and/or attribute values for one database table at a time. The command returns all of the original attributes plus any new attributes defined on the Functional Attributes dialog box as a new query. You can use this command on read-only data as 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.


449

Analyzing GeoMedia Professional Data 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.

450


Analyzing GeoMedia Professional Data 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.

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 , and it does not have the Functional attribute name or Output type fields. See “Aggregating Data” and “Merging Feature Classes and Queries” in this section and “Updating Feature Attributes” in the “Editing Features and Geometries” section. To avoid possible confusion, 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 Attributes dialog box.

Functional Attribute Expressions Functional Attribute expressions are similar to the expressions used in Excel. They consist of operands and operators that are evaluated in order to get a resulting value. An expression can be just one operand or a combination of operands with one or more operators. You can use expressions in many ways, for example, as part of the data to retrieve in a query or as a search condition to look for data meeting a set of criteria. See the “Functional Attribute Information” topic in GeoMedia Professional Help for detailed information on the expression components.


451

Analyzing GeoMedia Professional Data 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. 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 e-mailing the GeoWorkspace, creating a GeoWorkspace template file, creating a GeoMedia WebMap Web site, and cutting and pasting expression strings.

Output Data Types The output data type of the functional attribute is displayed in the Output type read-only field only when the expression is currently valid, thus providing a valuable expression check. In addition to standard numeric and text data type outputs, some (Geometry) functions output geometry data types. Output geometry data types include the following: 

Area Geometry



Line Geometry



Compound Geometry



Point Geometry



Image Geometry



Text Geometry

Length You can review and/or edit of the length of the output functional attribute in the Length field when the output type is Text. The default value is 255, and you can edit this to any value from 1-255, inclusive.

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.

452



Operands Operands are manipulated by the operators in an expression. The operands can be the following: Identifiers-References to fields in which values vary for each record. Constants-Fixed values that are constant for each record. Functions-Operations that take inputs and return values. You can build an expression from combinations of these operands ed with operators. For example, an expression can be a calculation, such as: (price * 1.5) or (price + sales_tax). In an expression, you enclose character data values in single quotation marks ('). In the following expression, the character literal B% is used as the pattern for the LIKE clause: LastName LIKE 'B%'. In the following expression, the date value is enclosed in single quotation marks: OrderDate = 'Sep 28 2001'.

Operators Operators are symbols specifying an action performed on one or more operands, that is, how the operands are manipulated. The operator categories are the following: 

Arithmetic



Logical



Bitwise



String



Comparison



Unary

An expression can be built from several smaller expressions combined by operators. In these complex expressions, the operators are evaluated based on operator precedence. Operators with higher precedence are performed before operators with lower precedence. Operators with the same precedence are performed from left to right. The following are example expressions:  AssessedVal = Area* Value  TotalPop = sum(Pop)  If MeanIncome > 30,000 then sum(Pop)

Functions The Functional Attributes command provides the following types of functions to perform operations:  Scalar functions operate on a single value and then return a single value. 1:1 (1 record in, 1 record out) Example: Using the Functional Attributes command to calculate the X or Y coordinates of a point geometry feature class.  Aggregation functions operate on a collection of values but return a single, summarizing value. Many:1 (Many records in, 1 out) Example: Using the Analytical Merge command with CREATEPOLYGON to merge points to a polygon.  Expansion functions operate on a single value (usually a geometry value) and then return multiple values. 1:Many (1 record in, Many records out) Example: Using the Functional Attributes command to calculate SEGMENTS of lines.


453

Analyzing GeoMedia Professional Data 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: Date and Time

Miscellaneous

Geometry

Statistical

Logical

Text

Math & Trig

View

The categories on the Functional Attributes dialog box simply organize the functions by subject. If you select All Functions from the Categories list, all available functions are displayed for selection in the Functions list. If you select Most Commonly Used Functions, the Functions list contains only those functions that you have most recently and most frequently used. The default content consists of fourteen pre-selected functions; as you use this command, the list adjusts to include your own commonly used functions. Operators and Constants display a list of operators and constants, respectively. Attributes that can be used as input parameters for the functions are displayed in the Attributes list.

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

Constant

Meaning

0

Truemeas

Measurements are computed on the surface of the ellipsoid (taking the earth's curvature into ). Distances are also referred to as geodesic distances.

1

Projectgedmeas

Measurements are computed on the projection plane. These measurements are affected by projection distortions. UnitOfMeasure: The area unit in which the geometry is to be measured. This parameter is optional. If missing, the geometry is measured in square meters. Valid area measurement values can be selected from functions listed in the category Constants. Remarks: The return value depends on the geometry type. If the geometry is not defined (NULL value), the NULL value is returned. Return Type: gdbDouble

454


Analyzing GeoMedia Professional Data COMPRESS-Returns a compressed form of the given geometry. The geometry does not change visibly but is instead rewritten with efficient storage. It is sometimes used with certain data originating from CAD (that is, derived from complexed lines or polygons). The geometries are rewritten so they are easier to edit in GeoMedia 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: 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), a NULL value is returned. The act of compression involves three different activities: 1. Nested composites/collections are flattened. This eliminates geometry headers, eliminates recursive processing, and (for composites) sets the stage for further optimization in the next step. 2. Consecutive endpoint-matched lines/polylines within composites/collections are stitched together into a single polyline. This eliminates geometry headers and eliminates redundant vertices. In the case of composites, it is expected that consecutive geometries match endpoint-to-startpoint, in which case such geometries (if line/polyline) are stitched together with the redundant vertex eliminated. In the event that they do not match endpoint-to-startpoint, it is considered an invalid geometry. In this case there is no redundant vertex, and no compression occurs between the two geometries. In the case of collections, there is no expectation that consecutive linear geometries match endpoint-to-startpoint, but we know from experience that such circumstances do occur, and that when they occur, they are often meant to be treated as a single continuous linear geometry. For this reason, the same processing will occur in this step for collections as occurs for composites, as stated above.


455

Analyzing GeoMedia Professional Data 3. Single-member composites/collections are flattened and replaced with the single member primitive. This eliminates the parent geometry and simplifies future processing and editing of the geometries. Return Type: gdbSpatial CREATEPOLYLINE-Creates a polyline from an ordered series of points. This is an aggregating (that is, points stored in multiple records output to one linear record) or a scalar (that is, multiple points stored in 1 record output to 1 linear record) function. If the points for a single line are stored in multiple records, you should use CREATEPOLYLINE with the Analytical Merge command and, more rarely, the Aggregation command. If the points for a single line are stored in a single record (that is, a feature class or query that has multiple point geometry columns), you can use Analytical Merge, Functional Attributes, or Aggregation. Format: CREATEPOLYLINE(Geometry, OrderBy) or CREATEPOLYLINE(Geometry1, Geometry2, Geometry3, …) Geometry: The point geometry that represents vertices from which a polyline is created. OrderBy: The optional expression that is used for sorting the points. If it is missing, the order is determined by the recordset and pipe that is hosting this function, and in this case, the order of the vertices is not guaranteed. Geometry 1, 2, …: The point geometries that represent vertices from which the polyline is to be created. In the case of this format, the function becomes scalar. Remarks: The input geometry type must be type of gdbPoint. If the input field is a collection, each point of the collection will be handled separately in the order of the items in the collection. If 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 MERGE-Returns the merged geometry. Commonly used with the Analytical Merge command because this is an aggregating type function. Format: MERGE(Geometry) Geometry: The geometry for which you want to create merged geometry. Return Type: gdbSpatial PERIMETER-Returns the distance around the perimeter of the specified geometry. The following format is similar to the AREA function (see also the previous AREA function). Format: PERIMETER(Geometry, RefSpace, UnitOfMeasure) Geometry: The geometry for which you want to measure the perimeter. RefSpace: The active reference space used for performing measurements. This parameter is optional. If missing, Truemeas is used. For possible values see the AREA function. UnitOfMeasure: The linear unit in which the geometry is to be measured. This parameter is optional. If missing, the geometry is measured in meters. Valid linear units can be selected from the list of constants (found under the Constants category). If the geometry is not defined (NULL value), the NULL value is returned. Return Type: gdbDouble REVERSE-Returns the original geometry with reversed vertex order. This is a scalar function. Format: REVERSE(Geometry)

456


Analyzing GeoMedia Professional Data Geometry: The geometry that you want to reverse. It must be of the subtype gdbLinear, gdbAreal, or gdbAnySpatial. Remarks: If the geometry contains point geometry, the point is returned without any changes. If the geometry contains linear geometry, the reversed linear geometry is returned. If the geometry contains areal geometry, the reversed areal geometry is returned If the geometry contains a collection of geometry, the reversed collection of reversed geometry is returned. In other words, each individual geometry is reversed, and the items in the collection are also reordered, from last to first, so that the overall vertex sequence is retained. If the geometry is not defined (NULL value), the NULL value is returned. Return Type: The same as the original geometry type.

Constants A constant, also known as a literal or a scalar value, represents a specific data value that does not change during the calculation of an expression. The format of a constant depends on the data type of the value it represents. A full list of the available constants can be found under the Constants category.

To create and to display functional attributes: 1. Select Analysis > Functional Attributes.

2. Select a feature class or query as input from the Add functional attributes for drop-down list. 3. Click New to open the Functional Attribute dialog box to define at least one functional attribute. 4. Type an appropriate value in the Functional attribute name field. 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.


457


7. 8. 9. 10. 11. 12. 13.

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. Optional: Use the Expression field and Add button to create more functional attributes. Click Close to return to the Functional Attributes dialog box. Accept the default query name, or type an appropriate name in the Query name field. Optional: Type a query description in the Description field. 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. Optional: Click Style, and change the map window default style on the Select Style dialog box. Click OK.

To edit functional attributes: 1. 2. 3. 4.

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

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

458


Analyzing GeoMedia Professional Data Additional merge examples are the following:  Merge Parcels by Owner ID and/or Name and calculate the taxes owed.  Merge Pipe Segments by pressure_zone id, and return the total length of pipes and average pressure in each pressure zone.  Merge Streets by street_name and calculate the total length (sum of segments)  Merge Survey Points by Survey name to connect the stations with a line (connect the dots) using the CREATEPOLYLINE function. There are three possible queries, based on the merge criteria: attribute based, spatially based, or both. You specify the criteria through the following options on the Analytical Merge dialog box:  All-Merges all input features.  Touching-Merges features that touch.  By attribute-Merges features that share one or more selected equivalent attribute values.  By attribute and touching-Merges features that share one or more selected equivalent attribute values and that touch. If you select either of the two attribute-based criteria, the Attributes list is populated with the names of all displayable attributes of type Text, Byte, Integer, Long, Single, Double, Currency, Boolean, Memo, and Date (but not LongBinary, and GUID), from which you can select one or more attributes to be used for determining if features should be merged based on equivalence of attribute values. Attribute-based merging requires that the values of all attributes match, that is, there is no logical and between comparisons of the various attribute values. If you select attribute-based merging but do not select an attribute, it is as if attribute-based merging were not selected. Thus, the command behaves as if the All or Touching option (as appropriate) were selected. You must define at least one output functional attribute through the Functional Attributes dialog box. For all input features except nongraphic, the default attribute name is Geometry with the expression ―MERGE( )‖, where is the name of the primary geometry field of the input feature class or query. If the input features are nongraphic, no attribute name is displayed. You can also define additional output functional attributes and review and/or edit their properties through the Functional Attributes dialog box, and you can delete functional attributes through the Analytical Merge dialog box. See “Working with Functional Attributes” in this section for information on functional attributes. You can use Analytical Merge to operate on both input and output attributes. The attribute fields from the input are prefixed by Input in the Functional Attributes dialog box. When you create a functional attribute, the new attribute is prefixed by Output. This allows you to perform analytical operations on previously defined functional attributes with the same operation. For example, you can specify the following expressions in one run of the command: MergeGeometry = MERGE(Input.Geometry) AreaOfMergedGeometry = AREA(Output.MergeGeometry) SumOfAreas = SUM(AREA(Input.Geometry) The last two lines give you the same results if the geometries are only touching (not overlapping). If you have overlapped areas, you get different results, and, in this case, the SumOfAreas will be greater than AreaOfMergedGeometry.


459


Using the Right Mouse Menu In defining a functional attribute, you can use the buttons to the right of the Output functional attributes field, or you can use its right mouse menu. The menu contains shortcuts for creating common functional attribute definitions, as in the following example:

New—Opens a submenu with the following items:  Custom—Opens the Functional Attribute dialog box for creating new functional attributes, as does the New button.  Count(*)—Adds a new functional attribute with a default name of ―CountOf ‖, where is the name of the feature class or query input to the command. The expression for the functional attribute is ―COUNT(*)‖.  [Function] > [Attribute]—Adds a new functional attribute with a default name of ― Of ‖, where is the name of the function (AVERAGE, COUNT, FIRST, MAX, MEDIAN, MIN, SUM), and is the name of the attribute chosen. For example, to obtain the sum of the ―Population‖ attribute, the default functional attribute name would be ―SumOfPopulation‖. The expression for the functional attribute is ― ( )‖, for example, ―SUM(Population)‖.  [Function] > Multiple Attributes—Opens the Multiple Attributes dialog box for creating multiple new functional attributes as in the previous bulleted item, one per chosen attribute from the list of all attributes from the input feature class or query that is of a data type valid for the selected function. After checking appropriate attributes, clicking OK dismisses the dialog box and returns one new output functional attribute for each attribute chosen.

 

460

Properties—Opens the Functional Attribute dialog box for reviewing or editing functional attributes, as does the Properties button. Delete—Deletes selected functional attributes, as does the Delete button.


Analyzing GeoMedia Professional Data To perform analytical merge: 1. Select Analysis > Analytical Merge.

2. Select the feature class or query to merge from the Merge features in drop-down list. 3. Select the appropriate Merge criteria option. 4. If you select By attribute or By attribute and touching, select the appropriate Attributes check box(es).

5. Optional: Click New to define additional functional attributes on the Functional Attribute dialog box. 6. Optional: Change the default query name, and/or type a description in the Output merge as query fields. See the GeoMedia Professional Help for information on this dialog box. 7. that the Display merge 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 merge in map window check box. 8. Optional: Click Style, and change the default style on the Select Style dialog box. 9. 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.


461


Workflow for Dashed and Patterned Linear Features Applying a dashed line style or a patterned line style to linear features can often produce undesirable results if the linear network is segmented, as in the following example.

In the preceding example, the railroad pattern is uneven because of the segmented network; the pattern origin is redefined every time a new segment is encountered. This is easily overcome using the Analytical Merge command, as in the following example.

In the preceding example, the pattern spacing is consistent, as opposed to the first example, thereby producing the appropriate symbology, as specified on the Select Style dialog box. This is because the Analytical Merge command has merged the linear network, thus eliminating the problems associated with segmented displays. This workflow is also very useful for multiple-line displays used to show cased road (parallel line) symbology, especially at intersections.

Aggregating Data The Aggregation command lets you copy attributes from features, including graphic text feature classes and queries, in one feature class (the detail feature class) to related features in another feature class (the summary feature class) in the form of a dynamic query. This query is based on the spatial relation between two features and/or related table columns (similar to a ) between two features. The detail feature class attributes are aggregated into the summary feature class. Both summary and detail feature classes can be point, linear, area, compound, and nongraphic, but not graphics text or image. The output 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?

462


Analyzing GeoMedia Professional Data  

What is the total assessed value of parcels affected by a proposed road-widening project? How many houses are located within 300 feet of each road segment?

Aggregation Types There are three possible types of aggregation based on the merge criteria: attribute based, spatially based, or both. You specify the criteria through the tabs on the Aggregation dialog box. On these tabs, you also specify the resolution operator and the definition of output functional attributes to be computed from the summary features and the detail features.

Attribute Aggregation This type of aggregation uses matching attribute values to determine how the information in the detail table is aggregated into the summary table. For example, you could aggregate two tables, one with parcel geometry (PARCEL) and one with nongraphic information (PARCEL_INFO) that is related to the parcel features that have one common (identical) PARCEL_ID column. Using attribute aggregation would allow you to combine specific calculated information from the detail table (PARCEL_INFO) to the summary table (PARCEL), where appropriate, based on the comparison of the common attribute. To this , you could use functional attribution to add calculated information between the two sources. From the Attribute Aggregation tab, you can select one or more summary and detail attribute pairs from a list of all displayable attributes, to be used for determining if features should be aggregated based on the equivalence of attribute values. Values of all attributes must match, that is, there is a logical and between the comparisons of the various attribute values. When you have selected a summary feature class or query, you must select at least one attribute.

The selection button that lets you select an attribute pair is enabled only if the conversion between the data types of the selected attributes is possible. This conversion possibility is described in following table:


463

gdbBoolean gdbByte gdbInteger gdbLong gdbSingle gdbDouble gdbCurrency gdbDate gdbText

gdbText

gdbDate

gdbCurrency

gdbDouble

gdbSingle

gdbLong

gdbInteger

gdbByte

gdbBoolean


Y

N

N

N

N

N

N

N

N

N

Y

Y

Y

Y

Y

N

N

N

N

Y

Y

Y

Y

Y

N

N

N

N

Y

Y

Y

Y

Y

N

N

N

N

Y

Y

Y

Y

Y

N

N

N

N

Y

Y

Y

Y

Y

N

N

N

N

N

N

N

N

N

Y

N

N

N

N

N

N

N

N

N

Y

N

N

N

N

N

N

N

N

N

Y

Y = Selection button enabled.

N = Selection button disabled.

Spatial Aggregation When both summary and detail feature classes do not have a common (identical) database column and they are spatial feature classes, you can still perform aggregation through spatial criteria. For example, you could use spatial aggregation to find a site for a new restaurant based on traffic volume, population income, and distance from a particular intersection. For spatial aggregation, you need to check the Aggregate where summary features check box and to select an appropriate spatial operator on the Spatial Aggregation tab because this type of aggregation is based on spatial proximity. If you select the are within distance of operator, you also need to define the distance and distance unit. The operators are as follows:  accumulate nearest  are contained by  are entirely contained by  are nearest to  are spatially equal  are within distance of

    

contain entirely contain meet overlap touch

The accumulate nearest and are nearest to operators are specific to aggregation. accumulate nearest - This operator provides aggregation of the closest detail feature to each input summary feature. This operator allows you to find the nearest detail feature attribute for each summary feature. Each summary feature has exactly one detail feature assigned to it. Some detail features may not get assigned to a summary feature, while some detail features may be assigned to multiple summary features.

464


Analyzing GeoMedia Professional Data Even though each summary feature has one detail feature because of the nature of the Aggregation command, the FIRST function has to be used to get the appropriate nearest attribute(s) from the one detail feature. When this operator is used, the Resolution operator is ignored. Examples: Finds the single nearest super market (detail) for each house (summary). FIRST(input.attribute) Can be used to get the attribute from the nearest detail. FORMATMEAS(DISTANCE(Input.Geometry, FIRST(Detail.Geometry)), FormatType.Distance, Mile, 2) Can be used to get the distance of the nearest detail in miles with 2 decimal places. are nearest to - This operator provides aggregation of each detail to a single nearest input summary feature. Each detail feature is assigned to exactly one summary feature. Some summary features may not have any detail feature assigned, while some summary features may have multiple detail features assigned. When this operator is used, the Resolution operator is ignored. The detailed features to be aggregated are sorted in order from nearest to farthest. Examples: Assign every house (detail) to its nearest super market (summary). COUNT(*) Might be used to count the number of detail items (customers for example) that are mapped as the nearest to the summary feature (stores for example). In other words, the number of detail records the store serves, as the store is the closest to those particular customers than any other store. CONCATENATE(―,‖,Detail.Customer_Name) Might be used to obtain a comma-separated list of the nearest customer names to which the store serves as the closest store. FIRST(input.attribute) Could be used to return the attribute of the nearest customer to which the store serves as the closest store. Example of a complex expression: CONCATENATE(', ', CAST(Detail.ID, Text)+'('+FORMATMEAS(DISTANCE(Input.Geometry, Detail.Geometry), FormatType.Distance, Mile, 2)+'mi)') To get a comma-separated output such as "(ID of detail, distance from summary feature)" in ascending order of distance: 10(50.55mi), 11(71.57mi). See “Defining Spatial Queries” in this section for definitions of the other operators.

Attribute/Spatial Aggregation You can also perform a combination attribute and spatial aggregation when there is at least one common (identical) database column between the summary and detail features and when the geometries touch. You perform this aggregation by using input from both the Attribute Aggregation and Spatial Aggregation tabs.


465

Analyzing GeoMedia Professional Data 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. 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 . 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. and the detail features appear as Detail. . See "Working with Functional Attributes" in this section for more information on functional attributes.

Aggregation Examples The following are examples of using Aggregation with the USA and Madison County sample data sets that were delivered with this product. The example problems listed here are hypothetical, and there may be other valid workflow solutions to solve the problem. Problem 1: Need to transfer the state abbreviation from the state to the counties that are contained by the state. Solution:  Summary Feature: Counties  Detail Feature: States  Aggregation defined as Spatial  Aggregate where summary features are contained by detail features  Output Resolution Operator: All  Output Expression: FIRST(Detail.STAABBRV) Problem 2: Need the number of cities each state contains as an attribute of the state. Solution:  Summary Feature: States  Detail Feature: Cities  Aggregation defined as Spatial  Aggregate where summary features touch detail features  Output Resolution Operator: All

466


Analyzing GeoMedia Professional Data  Output Expression: COUNT(*) Problem 3: Need to calculate the number of people in each state who do not live in a city. Solution:  Summary Feature: States  Detail Feature: Cities  Aggregation defined as Spatial  Aggregate where summary features touch detail features  Output Resolution Operator: All  Output Expression: Input.POP-(SUM(Detail.POP)) The output expression can be thought of as State.Pop-(SUM(City.Pop)). Problem 4: Need to calculate the total number of miles of interstate in each county. Solution:  Must perform analysis on spatial intersection (Analysis > Spatial Intersection) of Counties with Interstates, that is, Interstates overlap Counties.  Summary Feature: Counties  Detail Feature: Spatial Intersection of Interstates and Counties  Aggregation defined as Spatial  Aggregate where summary features overlap detail features  Output Resolution Operator: All  Output Expression: SUM(LENGTH(Detail.IntersectionGeometry,TrueMeas,Mile)) The value of miles will be expressed using double precision, but the results could have been rounded using the expression. The following rounds the values to two significant digits: ROUND(SUM(LENGTH(Detail.IntersectionGeometry, TrueMeas, Mile)),2)

Using the Right Mouse Menu In defining a functional attribute, you can use the buttons to the right of the Output functional attributes field, or you can use its right mouse menu. The menu contains shortcuts for creating common functional attribute definitions as in the following example: New-Opens a submenu with the following items:  Custom-Opens the Functional Attribute dialog box for creating new functional attributes, as does the New button.  Count(*)-Adds a new functional attribute with a default name of ―CountOf ‖, where is the name of the feature class or query input to the command. The expression for the functional attribute is ―COUNT(*)‖.  [Function] > [Attribute]-Adds a new functional attribute with a default name of ― Of ‖, where is the name of the function (AVERAGE, COUNT, FIRST, MAX, MEDIAN, MIN, SUM), and is the name of the attribute chosen. For example, to obtain the sum of the ―Population‖ attribute, the default functional attribute name would be ―SumOfPopulation‖. The expression for the functional attribute is ― ( )‖, for example, ―SUM(Population)‖.


467


[Function] > Multiple Attributes-Opens the Multiple Attributes dialog box for creating multiple new functional attributes as in the previous bulleted item, one per chosen attribute from the list of all attributes from the input feature class or query that is of a data type valid for the selected function. After checking appropriate attributes, clicking OK dismisses the dialog box and returns one new output functional attribute for each attribute chosen.



Properties-Opens the Functional Attribute dialog box for reviewing or editing functional attributes, as does the Properties button. Delete-Deletes selected functional attributes, as does the Delete button.



To define aggregation: 1. Select Analysis > Aggregation.

2. Select a summary feature class or query from the Aggregate to summary features in drop-down list. 3. Select a detail feature class or query from the From detail features in drop-down list. 4. Optional: On the Spatial Aggregation tab for spatial aggregation, check the Aggregate where summary features check box; then select the appropriate spatial operator from the drop-down list. 5. Optional: On the Attribute Aggregation tab, select the attribute pair(s) from the Summary attributes and Detail attributes lists; then click the down arrow to add the attribute pair(s) to the Selected attribute pairs list. 6. Optional: On the Output tab, select an operator from the Resolution operator drop-down list.

468


Analyzing GeoMedia Professional Data 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. 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. that the Display aggregation in data window check box is checked, and change in the Data window name field, if appropriate, the data window in which to display the aggregation. OR To not display the nongraphic attributes of the aggregation in a data window, uncheck the Display aggregation in data window check box. 12. Click OK to generate the aggregation.

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

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

Differences between Aggregation and Analytical Merge The following are true for the Aggregation command:  Two feature classes are used per query record sets, summary feature and detail feature.  No summary record is left out of the resultant query. The following are true for the Analytical Merge command:  One feature class is used per query record.  The output attributes are limited to Geometry, ID, and -defined functions.


469


Each function takes multiple input, and outputs a single resultant value.

Generating Base Geometry Generate Base Geometry generates topological base geometry (edges, faces, and nodes) for point, linear, area, and compound feature classes; it decomposes these features into topological pieces. For example, you could input Area boundaries representing Counties and generate Edges that are lines (as opposed to areas). The following table shows the topological types enabled for selection, and the default selection, given the input feature type: Input feature type

Topological types selectable

Default selection

Point

Nodes

Nodes

Line

Edges, Nodes

Edges

Area

Edges, Nodes, Faces

Edges

Compound

Edges, Nodes, Faces

Edges

You can also select multiple output types when they are enabled. This command takes a feature class or query as input and outputs a read-only query that is appended to the query folder. The resultant query has a compound geometry type and contains the following two attribute fields:  OutputType (integer) - Indicates the output topological type; 1-Edge, 2-Face, 4-Node.  FeatureCount (integer) - Indicates the number of features that contribute to the given base geometry. Once you select a feature, a default query name, which you can override, is generated automatically. You also have the option to display the query in a map window and/or a data window.

470


Analyzing GeoMedia Professional Data To generate base geometry: 1. Select Tools > Generate Base Geometry.

2. Select the feature class from the Generate base geometry from drop-down list. 3. Check the appropriate Output types check box(es). 4. Accept or override the default query name (Base Geometry of ) in the Query name field, and type an optional Description. 5. To display the base geometry in a map window, 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, that the Display in data window check box is checked. 8. Accept the default, select, or type a Data window name. 9. Click OK to generate and to display the base geometry in the specified map and/or data window.

Workflow for Dashed and Patterned Area Boundaries Applying a dashed line style or a patterned line style to area boundaries can often produce undesirable results when the area boundaries are coincident, as in the following example.

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.


471


. In the preceding example, it is obvious that the coincident area boundaries are only being dashed once, as opposed to the first example. This is because the Generate Base Geometry command produces a query composed of compound geometries based on topological edges; there are no linear duplicates in the output query. Instead of placing duplicate geometries, a single geometry is placed and attributed with a feature count that identifies the number of base features encountered. The following example illustrates the result of running the Generate Base Geometry command on the States feature class in the sample data set.

In the preceding example, because there are no duplicate geometries, any dashed or patterned line styles applied will produce the appropriate symbology, as specified on the Style Properties dialog box. However, you may want to separate the linear instances based on their feature count, as seen in the following example.

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 s a single feature class or query as input. When trying to separate coincident boundaries

472


Analyzing GeoMedia Professional Data across feature classes, you can run the Generate Base Geometry command on the two feature classes, and then you can use the Spatial Difference command to subtract one boundary from another.

Selecting Attributes The Attribute Selection command lets you output a subset of input attribute fields from a feature class or query. In addition, you can change the names of the fields and reorder the fields. Thus, you can tailor your processing so that the results do not contain unnecessary attribute data. This command will be enabled if at least one open connection exists in the GeoWorkspace.

To select attributes: 1. Select Analysis > Attribute Selection.

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.

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.


473

Analyzing GeoMedia Professional Data 4. Optional: Click Rename to rename an attribute.

Double clicking on an entry in the Attributes list also opens this dialog box. 5. Optional: Change the default query name, and/or type a description in the Output attribute selection as query fields. 6. 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. 7. Optional: Click Style, and change the default style on the Select Style dialog box. 8. 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. 9. Click OK to generate the attribute selection query.

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

474



Combining Feature Classes and Queries The Union command lets you combine multiple feature classes, categories, reference features, or queries from different warehouses and with different schemas. You can thus use this command to combine different data sources into common views for analysis and integration. For example, you could use this command to combine different sets road features as in the following figure.

The functionality of this command parallels the union capability provided by SQL and most relational database management systems. A union provides the ability to record-wise append multiple tables/views (relations) in query results to create an output that is the logical union of the input. It can be thought of as appending together the records of many source inputs. In this sense, it is the record-wise equivalent to the column-wise concatenation provided by the command capability. The Union command performs a relational union of the chosen feature classes and queries. It does not perform a geometric union of features. You would use the Union command, for example, in the following scenario. You have feature classes of 100 different counties from 100 different database schemas, and you would like to merge (record-wise) all 100 different counties records, and output the results into one feature class. To do this, you would perform a union to create an output query and then use the Output To Feature Classes command to output the results into a database warehouse. The Union command requires that the corresponding attribute columns from the selected feature classes/queries should be of the same data type. This command raises the following error when there is a mismatch in the common attributes for the selected feature classes: “Unable to retrieve output query from union operation. The field's size does not match for field FIELD1.” You need to resolve the disparities in the attribute data-types as raised by the Union command. See “Working with s” in this section. Specifically, with this command you can perform the following:  Select multiple feature classes, categories, and reference features from multiple connections and queries.  Select the output schema mode.  Reorder records.  Select, rename, and reorder output attributes. You can select multiple feature classes, categories, and reference features across different connections and queries for output, but you must select at least two feature classes/queries to use this command.


475

Analyzing GeoMedia Professional Data The Advanced button on the Union dialog box lets you select the output schema mode. You can do this only after the selected features (any corresponding attribute mismatches should be resolved) have been determined to be correct for performing a union operation. The following three output schema modes are available:  Schema of the first selected feature class/query-The output attributes are determined by the first of the selected feature classes/queries.



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



Intersection of schemas from all selected feature classes/queries-The output attributes are determined by all the features. The attribute appears in the resultant query if it is in all the selected features classes/queries.

This command raises an error when there are conflicts arising due to geometry field mismatch. 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.

476


Analyzing GeoMedia Professional Data To combine feature classes and queries: 1. Select Analysis > Union.

2. Select the appropriate node(s) and/or feature check boxes in the Union features in list. 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.

4. Select the appropriate Attributes check box(es). 5. Reorder the attributes (use the arrow buttons and/or Select/Unselect All buttons) and/or Rename (click Rename and use the Rename Attribute box); then click OK on the Attributes of dialog box.


477

Analyzing GeoMedia Professional Data 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.

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 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. 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. 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.

478



Editing Union Queries through the Queries Command You can also edit union queries through the GeoMedia Professional Analyze > Queries command. To do this, you first select a union query from the list of queries displayed on the Queries dialog box and then click Properties. This displays the following form of the Queries Properties dialog box, which you complete with a workflow similar to that used with the Advanced dialog box and the Attributes of dialog box.


479


480


SECTION 14

Linear Referencing This section outlines the basic concepts behind the linear referencing capabilities contained in the LRS Precision Location and Dynamic Segmentation commands. This section also describes the major components of a Linear Referencing System (LRS) and provides table descriptions. Lastly, it discusses the LRS Precision Location and Dynamic Segmentation commands. The intent of these commands is to extend the accessibility of basic linear referencing capabilities within customers‘ organizations. The available GeoMedia Transportation Manager and GeoMedia Transportation Analyst products provide more full-featured linear referencing capabilities as well as robust routing capabilities.

What is Linear Referencing? Linear referencing is simply the tracking and analysis of data that is associated with locations along a linear network. Some road transportation examples include tracking the location of and condition of signage, the condition of pavement, and the location and severity of accident occurrences. One of the biggest uses of linear referencing is Asset Tracking. Asset Tracking primarily encomes the following four items: 

What, where, and when of the assets (for example, a pothole at kilometer post 41.7 along Route 66, reported th June 6 , 2008)



Asset conditions (for example, a stretch of pavement with rutting and cracking)



Incidents along the network (for example, a traffic accident)



Activities along the network (for example, construction projects)


481

Linear Referencing

LRS Terminology In order to understand the functioning of the Linear Referencing System, you should become familiar with its terminology, as follows: LRS (Linear Reference System)—The total set of data and procedures for determining specific points along a roadway. LRS Datum—The basic, linear geometry of an LRS with its key identifiers and measures. Event—Any feature, characteristic, or occurrence along a road (for example, accident, bridge, road condition). LRM (Linear Reference Method)—The technique used to specify where an event occurred along a road (an accident occurs at kilometer marker 4, stop sign at the intersection of Main Street and Elm). Traversal/Route—Set of segments in a certain order and direction. Milepoint/Kilometer Point/Log Mile—Distance measurement from the beginning of a route. Segment—Continuous section of roadway (that is, intersection to intersection). Marker—Start and endpoint of segments, often Intersections. Events are frequently measured as an offset of a marker.

Linear Referencing and Geospatial Technology The main impetus to merge linear referencing with geospatial technology can be summed up simply: it is often desirable to view location data on a map. It also opens up a lot of other analysis capabilities, such as summing up data within an area feature (for example, the kilometers of rail track that require maintenance within a given jurisdiction) or finding data within a proximity of linearly referenced data (for example, finding residences within a buffer zone of a construction project). Using the Dynamic Segmentation command is not the only way to merge linear referencing and geospatial technology, but it is certainly the easiest. This command enables you to create map features, including pavement conditions, accident data, and average daily traffic. This kind of information will help you plan improvements for deteriorating assets, will identify where your organization is spending its money, and will provide critical information clearly and accurately to all participants involved in your projects. This can increase the value of your data by turning it into business-critical, decision- information.

The preceding diagram shows a portion of road on the left and its geospatial representation on the right. The road has kilometer posts that indicate cumulative linear measures along the road. It also has a road name, Highway 6 in this example. A section of fencing along the road is also shown in both the left and right views. Based on the kilometer posts, it can be determined in the field that this stretch of fence runs along Highway 6 from kilometer measure 2.0 to 2.6.

482


Linear Referencing 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.

LRS Linear Features and Event Data As mentioned before, LRS Linear Features are the backbone of the LRS. But working with the linearly referenced tabular data, known as Event Data, is the whole reason for building the LRS in the first place. The following is a brief summary of the data structures of these two components. See the “LRS Data Structures” appendix for a detailed description. The LRS Linear Features represent the network itself. Each LRS Linear Feature table is a linear feature class that has the following fields:  ID—This is a long integer value that uniquely identifies each feature within the table.  LRSKeys1-4—This is one to four fields that together define the route that this feature belongs to.  StartMeasure—This is a numeric value that contains the measurement value for the beginning of this feature.  EndMeasure or Duration—This is a numeric value that contains either the measurement value for the end of this feature or the length measurement for this feature.  BeginMarker (optional)—This field stores a name for the beginning position of this feature. This is referred to as an internal marker.  EndMarker (optional)—This field stores a name for the end position of this feature. This is referred to as an internal marker.  ReversedGeometry (optional)—This Boolean (True/False) field declares whether the software should treat this linear feature as is it is (False) or as if its digitizing direction were reversed and its beginning were its end, and vice-versa (True). The Event Data represents the linearly referenced data. Note that Event Data can either be point data (occurring at just one spot on the linear network) or linear data (occurring at a span of distance along the linear network). Each Event Data table is (usually) a non-graphic table that has the following fields:  ID—This is a long integer value that uniquely identifies each record within the table.  LRSKeys1-4—This is one to four fields that together define the route that this record lies along.  Measurement data (pick one of the following options):  Measure Option—For point event data, this consists of one numeric Measure field that indicates the relative location of the point event record on the route defined by the LRS Key fields. For linear event data, this consists of two numeric fields: a StartMeasure


483

Linear Referencing field and an EndMeasure field. These define the relative location of the start and end points of the linear event record on the route defined by the LRS Key fields.  Marker Offset Option—For point event data, this consists of a Marker name field and a numeric Offset distance field. The point event data is located by first locating the marker and then by adding the offset distance to that location. For linear event data, there are two Marker fields and two Offset fields defining the start and end of the linear event record.  Coordinate Option—For point event data, this consists of two fields that, depending on the referenced Coordinate System File, may be either projected coordinates (for example, Northing & Easting) or geographic coordinates (Latitude & Longitude). For linear event data, there are four fields defining the coordinates for both the start and the end of the linear event record.  Duration Option—This is a slight variation on the Measurement Option and only applies to linear event data. It consists of a StartMeasure field and a Duration (or Length) field that together define the relative location of the record along its route.  Other Attributes (optional)—These are optional, but they are also the whole reason for doing linear referencing. For bridge events, these will store bridge data; for accident events, they will store accident data; and for pavement events, they will store pavement data.  Geometric length—2D (the default) or 3D. 3D makes three-dimensional geometric measurements be taken into consideration when performing linear referencing. Other optional components of the LRS are the External Markers. External Markers mark points along the network just like the Internal Markers discussed earlier, but these are not bound to just the beginning and end of LRS Linear Features. External Markers can occur anywhere along the LRS network and are functionally equivalent to point-event data using the Measure option. They are useful for modeling milestones and monuments that are commonly used to measure locations from. They can be used, along with Internal Markers, to locate event data using the Marker Offset option. Each External Marker table is (usually) a non-graphic table that has the following fields:  ID—This is a long integer value that uniquely identifies each record within the table.  LRSKeys1-4—This is one to four fields that together define the route that this record lies along.  Measure—This is a numeric field that indicates the relative location of the External Marker on the route defined by the LRS Key fields.  MarkerName—This field stores a name for this Marker. The GeoMedia Transportation Manager software, available separately, provides specialized tools for creating and validating an LRS Linear Feature class as well as tools for populating Event Data and External Marker tables. GeoMedia Transportation Manager is an add-on product to GeoMedia Professional.

Linear Referencing Commands This section briefly describes the major LRS Analysis tools provided in this software. Detailed instructions on how to use each of these commands is provided in the following sections of this document. LRS Precision Location – This command gets real-time LRS locations of your cursor location in the map window. With it you can also use key-ins of LRS locations to place points in the map window. You may use these points just for orientation, but you can also use them for placing vertices of new geometry. For more information, see "Working with the LRS Precision Location Command" in this section.

484


Linear Referencing Dynamic Segmentation – This command, which has already been referred, takes linearly referenced tabular data and creates a graphic query class from it that can be viewed in the map window. You can thus visualize your organization's inventory of assets more clearly than by simply reviewing tabular data. For more information, see "Working with the Dynamic Segmentation Command" in this section.

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

Measurement Reference Space is a Coordinate System setting that is copied from the GeoWorkspace to the underlying objects behind the scene by the respective command. It allows you to specify a measurement reference space to calculate the geometry measures. The command honors the reference space setting specified on the Units and Formats tab of the GeoWorkspace Coordinate System dialog box.

To perform precision location: 1. Open the GeoWorkspace connected to the data source containing the linear referenced network. 2. Select Tools > LRS Precision Location.

3. From the LRS features drop-down list, select the appropriate linear network feature class, reference feature, category, or query to be used for performing LRS Key-in or Readout.


485

Linear Referencing 4. Select the appropriate model from the LRS model drop-down list.

For more information on the different LRS Models ed, see the “LRS Data Structures” appendix. 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. Select a Geometric length option, 2D (the default) or 3D. Selecting 3D makes three-dimensional geometric measurements be taken into consideration when performing linear referencing. 9. 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. 10. 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. 11. Click OK after setting the appropriate values or Cancel to discard your changes. If, in Step 3, you picked an LRS model that uses external measure markers, continue with the following step. If not, skip to Step 17.

486


Linear Referencing 12. In the Marker features section of the LRS Precision Location dialog box, click Properties.

13. 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. 14. In the Name drop-down list, select the marker name for the Marker feature class. 15. In the Measure drop-down list, select the measure for the Marker feature class. 16. In the Marker unit drop-down list,, select the unit of measure for the Marker feature class. 17. Click OK after setting the appropriate values or Cancel to discard your changes.

You are returned to the LRS Precision Location dialog box. 18. 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. 19. Select the size of the LRS Keys Field and the Measures and Markers Field from the drop-down lists. 20. Select the Point style settings as follows:  Check Display point on mouse move to display a point on a mouse move.  Check Display point on mouse click to display a point on a mouse click.  Check Display point on key-in to display a point on key-in. The corresponding Style buttons display a default point style, which you can change by clicking the appropriate Style button. 21. 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. 22. 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. 23. Click OK.

The dialog box is dismissed, and the LRS Precision Location dockable control is displayed. 24. 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.


487

Linear Referencing 25. 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. 26. 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.

27. 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.

488


Linear Referencing 28. You can also use the LRS Precision Location control to supply data points to other GeoMedia commands. First enter whatever GeoMedia command you want (for example, Insert Feature). Next select the LRS Keyin button Precision Location control.

at the far right of the LRS

29. 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. 30. 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.

Working with the Dynamic Segmentation Command This section provides an overview of the Dynamic Segmentation command. Dynamic Segmentation is the process of generating geometry for events (event features) based on a Linear Referencing System (LRS).

Event features contain sufficient LRS information such that they can be dynamically segmented to produce geometry based on an LRS feature class. Typically, events do not contain geometry, so they cannot be displayed in a map window unless dynamic segmentation is performed. Events can be in a variety of formats, as described in the following discussion. The validation and correction of anomalies in the LRS should be performed before the Dynamic Segmentation command is used. This ensures that the proper analysis results are returned. Automated tools for LRS validation are available in the GeoMedia Transportation Manager product. The following capabilities are provided with the Dynamic Segmentation command:  Use any linear feature for dynamic segmentation that exposes a measure from any data connection that s graphic features.  Use a query of a linear feature for dynamic segmentation.  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.  Define up to four key fields for the LRS feature.


489

Linear Referencing     









Select an event table from any connection for dynamic segmentation. Use a query of an event table for dynamic segmentation. Use 2-D or 3-D Geometric length. Dynamically segment linear and point event data. of the following event referencing methods:  Measure  Projected XY coordinates  Longitude/Latitude  Marker Offset  Duration 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. of datum-based events. To define datum-based events, you select a Display LRM query as it has the required extensions to access LRS Metadata details. The Datum based option on the Dynamic Segmentation dialog box is enabled only if the selected LRS feature is a multi-level LRS Display LRM query. This option is disabled if the selected LRS feature is not a Display LRM query or if it is a single level LRS Display LRM query. The LRM based option is also enabled when the Datum base option is enabled. 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 asg a different offset distance value for each event so that events are not displayed on top of one another, thus differentiating overlapping event records. Whenever linear or point events overlap, the value of the Occurrence field is incremented for each successive linear event. This occurrence value can be used in conjunction with the offset display capability to show these events side by side to make the results clearer, as in the following examples:



Create dynamically segmented 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 ed through to the dynamically segmented events, and to reorder and/or to rename these attributes.  Choose to take the height (Z coordinates, 2-D or 3-D) into consideration when performing linear referencing, The results are output as a query to a map window and/or a data window. Measurement Reference Space is a Coordinate System setting that is copied from the GeoWorkspace to the underlying objects behind the scene by the respective command. It allows you to specify a measurement reference space to calculate the geometry measures. The command honors the reference space setting specified on the Units and Formats tab of the GeoWorkspace Coordinate System dialog box.

490


Linear Referencing To perform dynamic segmentation: 1. Open a GeoWorkspace; then connect to the warehouse containing the linear feature class to be used for dynamic segmentation. If the event feature class is in a different warehouse, make a connection to that warehouse also. 2. Select Analysis > Dynamic Segmentation.

3. Select the appropriate linear network feature class, reference feature, category, or query to be used for dynamic segmentation from the LRS features drop-down list. 4. Select the appropriate model from the LRS Model drop-down list. For more on the different LRS Models ed, see the “LRS Data Structures” appendix. 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. Select a Geometric length option, 2D (the default) or 3D. Selecting 3D makes three-dimensional geometric measurements be taken into consideration when performing linear referencing.


491

Linear Referencing 9. In the LRS definition fields drop-down lists, select the names of the Begin measure and End measure if you selected a Measure model type. If you selected a Duration model type, select the names of the Begin measure and Duration (length). If you selected an Internal Marker model type, select the names of the Begin marker and optional End marker. 10. 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. 11. Click OK after setting the appropriate values or Cancel to discard your changes. If, in Step 3, you picked an LRS model that uses external measure markers, continue with the following step. If not, skip to Step 18. 12. In the Marker features section of the dialog box, click Properties.

13. 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. 14. In the Name drop-down list, select the marker name for the Marker feature class. 15. In the Measure drop-down list, select the measure for the Marker feature class. 16. In the Unit drop-down list, select the unit of measure for the Marker feature class. 17. Click OK after setting the appropriate values or Cancel to discard your changes.

You are returned to the Dynamic Segmentation dialog box. 18. Select the appropriate Event feature option, LRM based or Datum based. 19. Select the connection and event feature class reference feature, category, or query to be dynamically segmented from the Event feature drop-down list. 20. Optional: Click Filter to filter event features by specifying a filter string on the Filter dialog box to select a subset of event features.

492


Linear Referencing 21. Click Event feature > Properties.

22. 23. 24. 25. 26.

27. 28.

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. Select the appropriate Event type option. Select the appropriate Event reference type option. 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. 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. 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). If your Event reference type is Coordinate, continue with the next step to set the coordinate system information for the selected events. If not, go to Step 33. 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.


493

Linear Referencing 29. 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. 30. Click OK after setting the appropriate values or Cancel to discard your changes.

You are returned to the Event Properties dialog box. 31. If your Event reference type is Coordinate, type a numeric value for the coordinate tolerance in the Coordinate tolerance field (the unit for this value is the one you set for the Distance on the Units and Formats tab of the GeoWorkspace Coordinate System dialog box). 32. Click OK after setting the appropriate values or Cancel to discard your changes.

You are returned to the Dynamic Segmentation dialog box. 33. Click Event feature > Attributes.

34. Select those attributes that you want reflected in the output query, using Select All and Unselect All to speed this process. 35. 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.). 36. Click OK after setting the appropriate values.

You are returned to the Dynamic Segmentation dialog box.

494


Linear Referencing 37. Optional: Click Advanced Display Settings.

38. 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. 39. 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. 40. 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. 41. Click OK after setting the appropriate values or Cancel to discard your changes and to return to the Dynamic Segmentation dialog box. 42. 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. 43. 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. 44. Optional: Click Style to define the display settings for the results in the map window. 45. 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. 46. When you have made the appropriate settings, click OK. 47. When the results are returned, you can tile the windows vertically.


495

Linear Referencing The workspace would then resemble the following:

48. 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.

49. Select the query generated by the Dynamic Segmentation command, and then click Properties.

50. 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.

496


SECTION 15

Working with Labels There are two different types of annotation in GeoMedia Professionall, text and labels. Text may be the result of data displayed from a warehouse, or text may be created and interactively placed with the Insert Text command. Labels may be the result of the batch labeling command Insert Label, which lets you create and insert labels as dynamic label queries or static text feature classes. The difference between the labeling tools and the Insert Text tool is that the labeling tools automatically place text using feature attribute values. Insert Text requires you to type in the text to be placed. GeoMedia also provides two other label-related commands. The Resolve Text Conflicts command lets you detect and resolve text overprints that occur in feature classes or queries. The Insert Leader Line command lets you place leader lines/leader terminators for label queries in the second part of a two-step workflow. In the first step, you use the Insert Label command to create labels as a query and select the Enable leader lines option to set up the leader line feature class and leader terminator query and to establish the underlying relationships between these feature classes/queries. In the second step, you use Insert Leader Line. Upon placement, the orientation of the leader terminator and the label alignment setting are calculated automatically. Additionally, this command lets you move labels and place multiple labels per feature if the Enable leader lines is selected. The Insert Interactive Label command allows you to select individual features and label them one at a time. See the “Inserting Text Features into a Feature Class” section in the “Working with Features” section. See “Resolving Text Conflicts” and “Inserting Leader Lines” later in this section.

Inserting Labels With the Insert Label command, you can create labels as a query or as a feature class, depending on how you want the labels to behave and what you want to do with them in the map window. In both cases, the attributes of the original feature (the additional columns) are copied to the label feature. However, in a query label the attributes are dynamically linked so that a change made in the original feature attributes is reflected in the linked label feature as well. In a feature class label, the attributes are static and not linked so that a change in the original feature attributes is not reflected in the feature class label. Each label creation method has its advantages. Labels as Query—You can create labels as a query in the GeoWorkspace if you want each label linked to the feature with which it is associated. As a query, the labels will be updated each time you edit the labeled features or open the GeoWorkspace. When, for example, a feature is deleted from the feature class, its label is deleted as well. Similarly, when a new feature is inserted into the feature class, the new feature is appropriately labeled. As a query, a label outputs as graphics text the values of the attributes you select 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.


497

Working with Labels If you plan to place leader lines/leader terminators for the labels, you must create labels as a query with the Enable leader lines option selected. If you do not, and subsequently want to place leader lines/leader terminators for the labels, you will not be able to. In this case, you would need to delete the labels and then insert them again as a query with the Enable leader lines selected. Labels as Feature Class—Labels created as a feature class do not have an active link to attribute values or geometry. You can edit the text in the labels, and you can insert the labels as features into a feature class in a read-write warehouse. In addition, like any other feature you can move, rotate, and delete labels that are output as a feature class. When you create labels as a feature class, you will not be able to place leader lines/leader terminators for the labels. You can only place leader lines/leader terminators for labels created as a query with the leader line option selected. Whether you output labels as a query or as a feature class, you can define their content, style, and layout for display in the map window. Among other things, you can display a frame around the text in a label, give it a solid or transparent background, and define it so its Paper (size is true at nominal map scale) (display scale dependent). By default, the text style is defined such that its View (size is true at any display scale) (display-scale independent). See the “Inserting Text Features into a Feature Class” section in the “Working with Features” section. See the “Working with Styles” and “Defining Map Window Display Properties” sections in the “Working with Map Windows” section.

Label Placement This command lets you set the label placement orientation, and alignment, offset, and whether to place single or duplicate labels. The available label placement orientation modes are as follows: Place at angle—Places the label at the angle specified in the degrees field. This mode is the default orientation mode, at 0 degrees. The valid range is –360 to 360 degrees. The angle unit and precision settings are based on the default settings defined on the Units and Formats tab of the GeoWorkspace Coordinate System dialog box. Orient to geometry—Places the label rotated in the direction of the geometry being labeled. The command displays the label with the rotation angle obtained from the geometry being labeled, using the style taken from the legend entry. If there is more than one legend entry, the style of the topmost entry is used. The following rules for label placement apply:  Point data—Orientation is based on the point rotation angle.  Linear data—Orientation is based on the angle of the line from begin point to end point.  Area data—Orientation is based on the angle of the longest edge of the area boundary. Labels are placed right side up and read as follows:  0, 180, 360 degrees—Text reads horizontal, left to right.  90, 270 degrees—Text reads vertical, bottom to top.  > 0 degrees, < 90 degrees—Text reads southwest to northeast.  > 90 degrees, < 180 degrees—Text reads northwest to southeast.  > 180 degrees, < 270 degrees—Text reads southwest to northeast.  > 270 degrees, < 0, < 360 degrees—Text reads northwest to southeast. Map window rotation at the time of placement is honored. If the orientation of the geometry is 30 degrees and the map window is rotated by 40 degrees, the labels is placed at 70 degrees from the horizontal.

498


Working with Labels The available label alignments are as follows: Top left

Top center

Top right

Center left

Center center

Center right

Bottom left

Bottom center

Bottom right

You can specify the horizontal and vertical offsets to define the distance each label is placed from its origin. For vertical offsets, positive values offset upward while negative values offset downward. Similarly, for horizontal offsets, positive values offset to the right while negative values offset to the left. The units are measured in ground units. Finally, you can specify that duplicate labels should not be placed. This temporarily merges contiguous multiple feature parts in a linear geometry collection to find the center point in order to place a single label.

To create a label: 1. Select Insert > Label.

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. 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.


499

Working with Labels

5. 6. 7. 8. 9.

10. 11. 12.

13. 14. 15.

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. 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. Select the appropriate label alignment from the Alignment drop-down list. Optional: To define the distance each label is placed from its origin, specify the horizontal and vertical offsets. Optional: To specify that duplicate labels should not be placed, check the Place single label along contiguous linear features check box. 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. Accept or override the default query name in the Query name field; then type an optional description in the Description field. Optional: To enable leader lines, check the Enable leader lines check box. 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. 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. Optional: Click Style to change the default text style. Click OK to generate and to display the labels.

Inserting Leader Lines The Insert Leader Line command lets you place leader lines/leader terminators for label queries in the second part of a two-step workflow. In the first step, you use the Insert Label command and select the Enable leader lines option to set up the leader line feature class and leader terminator query and to establish the underlying relationships between these feature classes/queries. In the second step, you use Insert Leader Line. Upon placement, the orientation of the leader terminator and the label alignment setting are calculated automatically. The Insert Leader Line command honors vector snaps, autopan, Undo, and precision key-ins. The following illustration shows the placement of leader lines:

500


Working with Labels A leader line is composed of a minimum of two vertices, a start point and an end point. The start point coincides with the coordinates used to define the placement of the leader terminator. It is the first point you digitize and is the point nearest the original label feature. The end point coincides with the coordinates of the last vertex digitized, and this point is used to define the placement of the new position of the label at the end of the leader line. The following illustrates the workflow for placing leader lines:

1. Select the label to start the leader line.

2. Place the first vertex to place the leader terminator, and the dynamic label appears.

3. Place the end of leader line at the new location of label.

4. Double click to remove the original label and to set the new label where specified.

Insert Leader Line performs the following tasks in placing a leader line: 1. Ensuring that the leader line feature class and leader terminator query associated with the label selected are displayed in the legend of the active map window. It is assumed that the label is already displayed because it must be selected.  The leader terminator query is displayed in the active map window. The position in the legend is right below the label selected.  The leader line feature class is displayed in the active map window. The position in the legend is right below its associated leader terminator query. 2. Digitizing the leader line geometry.  The leader line can have multiple interior vertices.  The start coordinates of the leader line are not fixed at the position of the originating label; they can be moved by using Edit > Geometry on the leader line.  The start point does not automatically move if the feature moves, except through coincidence. 3. Calculating the orientation of the leader terminator point geometry at the leader line start point.  Leader terminators are placed as oriented point geometries. The orientation is automatically calculated based on the angle of the leader line, from the second vertex to the start point. This accommodates the use of arrowhead terminators to ensure that the arrowheads align with the digitized leader lines. You should create arrowheads with the tip of the arrow at zero degrees and the origin at the center of the base of the arrowhead. A leader terminator symbol file (terminator.fsm) is delivered with the software.


501

Working with Labels 

Leader terminators are automatically displayed once the leader line geometry has been digitized; otherwise, they do not exist. 4. Moving the original label from the originating start point to the newly digitized end point.  The new position of the label is determined by the leader line end point, that is, to move the label once it has been placed, you must edit the leader line.  The alignment of the newly positioned label is determined on a per-instance basis to minimize the overlap between the label and the leader line. This is determined by the angle calculated between the next-to-last vertex before the end point and the end point as follows:

 

Degrees

Alignment

Degrees

Alignment

>337.5 to 22.5

Center left

>157.5 to 202.5

Center right

>22.5 to 67.5

Bottom left

>202.5 to 247.5

Top right

>67.5 to 112.5

Bottom center

>247.5 to 292.5

Top center

>112.5 to 145.5

Bottom right

>292.5 to 337.5

Top left

The originating label maintains its position and alignment until a leader line geometry has been digitized. The rotation of the newly positioned label is automatically set to zero degrees regardless of the current rotation angle of the original label (This varies based on the orientation method used during the original placement.).

To insert leader lines: 1. In a map window with the leader line feature class and leader terminator query set up through the Insert Label command, select the appropriate query label. 2. Select Insert > Leader Line. 3. Place the point nearest the labeled feature to begin digitizing the leader line.

As you move from the start point, a dynamic line segment is displayed, and the leader terminator is dynamically displayed, taking into the calculated orientation. The label position remains fixed until the second point is digitized. 4. Place any additional leader line vertices.

After the second point has been placed, the leader terminator is placed in dynamics using the calculated orientation. The label is displayed in dynamics at the cursor, using the alignment calculated on the segment. Pressing BACKSPACE removes the previously placed vertex, including the first point placed. Pressing ESCAPE before completing the leader line digitizing opens a dialog box to stating Do you want to discard the current feature?. Click Yes to return to the start point (Step 3). Click No to returns the previous digitizing state 5. Double click to end the leader line. OR Open the right mouse menu with the following options:  End feature—Ends the leader line.  Cancel feature—Same effect as pressing ESCAPE as described in the note in Step 4.

Dynamics are turned off, and the leader line is displayed from start point to end point. The dynamic label is turned off, and the label is moved from the start point to the end point using the appropriate calculated alignment setting. The rotation of the leader terminator is

502


Working with Labels calculated, and the newly rotated leader terminator is displayed. See “Inserting Labels” earlier in this section.

Moving Labels The Insert Leader Line command also lets you move labels you have already placed with the Insert Label command. The procedure is similar to that for placing a leader line except that before starting the command you turn off the leader lines and leader terminators in the legend. You then proceed as if you were placing leader lines and move the selected label to an appropriate new location in the map window.

To move existing labels: 1. In a map window, turn off the leader line feature class and leader terminator query in the legend. 2. Select the appropriate query label. 3. Select Insert > Leader Line. 4. Place a start point; then place as many vertices as necessary until the label is in the correct new location.

After the second point has been placed, the label is displayed in dynamics at the cursor, using the alignment calculated on the segment. 5. Double click to set the label in its new location.

The dynamic label is turned off, and the label is moved from the start point to the end point using the appropriate calculated alignment setting.

Inserting Interactive Labels The Interactive Label command allows you to place labels for individually selected features on a selected, predefined feature class. The label text is taken from the selected database value(s) for the selected feature. You use the Interactive Label dialog box to control content, layout, position, and text style. Available options include: feature class or query to be labeled, output feature class for the label, attribute(s) and layout to use, orientation, and alignment. In addition, you can override the current legend style definition for each label placed. After completing the setup, you can place multiple consecutive labels by selecting the feature to label and clicking the label location. At any time, you can return to the dialog box to change content, placement, style override options, or feature class to be labeled, by using a right mouse click in the map window. To use this command, there must be an active map window and at least one read-write connection.

Orientation The available label placement orientation modes are as follows: Place at angle—Places the label at the angle specified in the degrees field. This mode is the default orientation mode, at 0 degrees. The valid range is –360 to 360 degrees. The angle unit and precision settings are based on the 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 dynamically—Places 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.


503

Working with Labels Orient to geometry—Snapping 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 arc—Places a curved label where the curvature of the text string is defined by a -defined three-point arc. Place along existing geometry—Lets 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 ed 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:  Point data—Orientation is based on the point rotation angle.  Linear data—Orientation is based on the angle of the line from begin point to end point.  Area data—Orientation is based on the angle of the longest edge of the area boundary. Labels are placed right side up and read as follows:  0, 180, 360 degrees—Text reads horizontal, left to right.  90, 270 degrees—Text reads vertical, bottom to top.  > 0 degrees, < 90 degrees—Text reads southwest to northeast.  > 90 degrees, < 180 degrees—Text reads northwest to southeast.  > 180 degrees, < 270 degrees—Text reads southwest to northeast.  > 270 degrees, < 0, < 360 degrees—Text reads northwest to southeast. Map window rotation at the time of placement is honored. If the orientation of the geometry is 30 degrees and the map window is rotated by 40 degrees, the labels is placed at 70 degrees from the horizontal.

Alignment The available label alignments are as follows:

504

Top left

Top center

Top right

Center left

Center center

Center right

Bottom left

Bottom center

Bottom right


Working with Labels To create an interactive label: 1. Select Insert > Interactive Label.

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. 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 -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


505

Working with Labels 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. 13. Repeat Steps 2 - 12 for any other features to be labeled interactively. 14. If you want to make changes, click the right mouse button while in the map window to return to the Interactive Labels dialog box. Labeling is restricted to features of the feature class selected on the Interactive Labels dialog box. To label features from another feature class, you must enter the new information on the dialog box. 15. To exit Interactive Label, click the Select Tool, press the ESC key, or click Cancel.

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

506


Working with Labels Results from inserting labels:

Results from resolving text conflicts:

Results with conflicting queries turned off:

You could then use leader lines to move the conflicting queries.


507

Working with Labels

Workflow Options There are two different workflow options, depending on the input. The output capabilities of this command are two queries, but the input dictates the level of interactive editing and dynamic behavior of the modified input text: 1. Input is a query or read-only feature class—The command identifies non-conflicting text and conflicting text. The input query items cannot be moved or deleted, but the text string updates dynamically when changes are made to the originating feature‘s label attributes in the database. For example, if the input is a query, changing the State_Name attribute from al to AL in the original feature would cause the query to change, which in turn would cause the output conflict queries to change. If the input is a read-only feature class, you cannot edit the feature class, so the output conflicts query will not change. You will likely use this command to filter the overprints, displaying only the output non-conflicting query in the map window instead of the input query or read-only feature class. 2. Input is a read-write feature class—The command identifies non-conflicting text and conflicting text. The input feature class items can be moved or deleted, but the text string will not update dynamically when changes are made to the originating feature‘s label attributes in the database. For example, in the case where the State_Name_Labels text feature class was based on the States feature class, and the Resolve Text Conflicts command was run on the State_Name_Labels feature class, changing the attribute al to AL in States will have no effect on State_Name_Labels and thus no effect 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. The Resolve Text Conflicts command determines conflicts based on the processing scale and font size settings. To accurately display the result, set the Nominal Map Scale (Display Properties) equal to the Processing Scale, and make sure the View (size is true at any display scale) check box is unchecked on the Display Properties dialog box for both output queries.

To resolve text conflicts: 1. Select Tools > Resolve Text Conflicts.

508


Working with Labels 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. If you select -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.

6. 7. 8. 9. 10. 11. 12.

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. Select the attribute to use to filter the text conflict from the Attribute drop-down list. Select the appropriate Retain text with option. Optional: Select the Output non-conflicting text as query check box to output non-conflicting text as a query. Optional: Override the default query name, and/or type a description. Optional: Select the Output conflicting text as query check box to output conflicting text as a query. Optional: Override the default query name, and/or type a description. Click OK to generate and to optionally display the non-conflicting and conflicting text queries.


509

Working with Labels

510


SECTION 16

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. Pre-GeoMedia 6.1.5 geocoding models (U.S. only) are fully compatible with GeoMedia 6.1.5. However, GeoMedia 6.1.5 geocoding models cannot be used with GeoMedia 6.1.4 or earlier. The introduction of the address element description and address format description has changed the format of the geocoding model XML files, and they cannot be loaded with previous versions of the objects.

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

Looking at GeoMedia Address Geocoding: An Overview GeoMedia Address Geocoding provides two application commands to work with capturing and presenting certain specific data: Find Address and Geocode Addresses. Find Address is a view navigational tool that finds the location of an input address and displays it as a point centered in a map window. Geocode Addresses provides basic functionality for address geocoding by creating point geometries for a feature class or a query based on the input addresses or intersections. You can then display the results in a map window and/or data window. Address Geocoding also provides three istrative utilities that configure the data: Publish Address Geocoding Index, Define Parsing Rules, and Define Geocoding Model. The Publish Address Geocoding Index utility provides the ability to publish GDO data (feature


511

Geocoding classes) to an AGI for subsequent geocoding. The Define Parsing Rules utility helps you create a well-formed set of modified parsing rules files conforming to the requirements for address parsing. The Define Geocoding Model utility lets you create, view, and edit geocoding models. If you need assistance in using these utilities, Intergraph .

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. Reverse geocoding is not ed by the desktop GeoMedia Find Address and Geocode Addresses commands. Reverse geocoding is ed through geocoding web services. Address Geocoding provides tools to let you create AGI files from street centerline and rooftop (point) datasets accessible from GeoMedia by means of the GDO data servers.

Reference (Source) Data The geospatial data used for geocoding can comprise of two basic types: Street Centerlines—This type of dataset normally uses street centerlines with attributes that can be used for searching, as well as house number ranges. Centerline geocoding is where the underlying geospatial data consists mainly of a street network or other linear data that is attributed with left/right address ranges. The processing required in this case basically requires finding the correct street segment and then interpolating the position based on the address range attributes. Rooftop Data—This type of dataset uses point features that represent discrete addresses, although line, area, and text features can also be used to create the address geocoding index. Additionally, this type of dataset can be used where each valid address point (that is, a letter box, house, apartment, delivery point) has been previously determined and is represented by a point geometry. Rooftop geocoding is where the underlying geospatial data is represented by features of any geometry type that have identifying attributes. The processing required in this case is basically a parse and a search for a record whose attributes match the input. 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.

512


Geocoding 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.

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 for starting the Define Parsing Rules utility and the Define Geocoding Model utility.

Address Geocoding - Concepts Address Geocoding Terminology In order to understand the functioning of Address Geocoding, you should become familiar with its terminology, as follows: Address—Description of a place that can be used to determine the location of that place in world coordinates. An address in its most common form has a systematic structure involving building numbers, street names, municipalities, postal codes, and so forth. However, it may also be a much simpler description, for example, a city name, a postal code, or a parcel ID. An address, whether simple or complex, may be expressed as a single text string requiring highly sophisticated parsing or as a fully normalized set of atomic values for each element in the address structure. Address elements—Atomic units forming an address. Output elements of the parsing rules are used to represent address elements in the address definition. Address geocoding index (AGI)— Binary file (.agi), in a GeoMedia-proprietary format, highly optimized and indexed for rapid geocoding. It is created by the Publish Address Geocoding Index utility.


513

Geocoding Address geocoding profile—XML file (.agp) containing the complete profile of a publishing process. This file can be used to launch the Publish Address Geocoding Index utility, or as input from the command line in batch usage. Address matching—Process that takes a fully parsed input address and finds the best match in the index. Address parsing rules—Defined in files, these rules can be created either manually or through the Define Parsing Rules utility. They are used to transform a single input string to the address elements used in the matching operation. Address transformation (includes address parsing)—Process that decomposes the address into the matching attributes used (a) to build the index file, and (b) to match against the index during geocoding operations. Candidate list reference—The Find Address command matches a single input address against loaded reference data. The resultant candidate list reference contains all match candidates for the specified input address. They are indexed by numbers from 1 to the value of the count property. The match candidates are ordered by the match score, in descending order. The first match candidate has the highest match score. The match candidates are returned as dynamic points. Every match candidate has the following match result information: match score, matched address, and status. Find Address command—A View command that geocodes an address entered through dialog boxes, producing a dynamic point on the map display and panning to the location of that point. GDO warehouse—The source GeoMedia-accessible dataset that contains the features the geocoding index is derived from. Geocode Addresses command—An Analysis command that geocodes all of the features in an input (normally nongraphic) feature class or query containing address information, producing a query on output with point geometries. Geocoding—The process of identifying a geographic location. Geocoding dataset—A dataset used as reference to perform geocoding or reverse geocoding. The GeoMedia-delivered implementation of a geocoding dataset is the Address Geocoding Index (AGI) file. The term geocoding dataset is used as a generic term, as this design allows for third-party geocoding engines (and their data) to be used. Geocoding directory—An XML document that defines the reference dataset location and other characteristics for various geocoding engines. It consists of one or more defined geocoding datasets, each of which has a unique identifier for the applicable runtime engine and an associated connection string intended to link the object to its reference data source data. Geocoding engine interface—A COM (dispatch) interface definition that provides a generic interface by which any number of independent (Intergraph-developed or third-party) geocoding implementations may be written, using alternate data structures and/or underlying software/services, and which can be plugged into the GeoMedia geocoding system. Address Geocoding delivers an implementation of this interface specific to AGI files. Geocoding model—An XML document describing a geocoding model. A geocoding model (GCM) definition describes -recognizable address components (or fields) and their correlation to the various elements of an address, that is, a comprehensive description of address elements that make up a particular address structure. The relationship between the attributes of the source data used to create the index (AGI) file, and the internal address definition of the dataset is also defined in the GCM file. Additionally, various AddressTransformations are defined in the GCM. Index building—Processing the source data and building an Address Geocoding Index file. Part of processing of the index data also involves address transformation and standardization. The index is build with the Publish Address Geocoding Index utility.

514


Geocoding Location—A point on the earth, which may be expressed in world coordinates (textual or numeric) or as a point geometry. Matching—Comparing standardized address elements in a common structure (one may have been transformed) and selecting one or more successful or candidate matches. Matching index—Maximum eight-character text string composed of portions of selected address elements or their sound-like equivalents. It serves to improve geocoding performance by limiting the elements searched within the AGI file. The matching index is calculated for every address in a reference dataset and for every address to be matched. During matching, the address is compared with all reference addresses having the same value as the matching index. If the value of the matching index is the same for all reference addresses or varies too little, the address is compared with a large number of reference addresses and it significantly degrades the geocoding performance. An appropriate selection of matching index is, therefore, essential to achieving an optimum balance between geocoding performance and the matching rate. Parsing—Decomposing the textual representation of an address into constituent address elements according to various rules. Reverse geocoding—Taking a location (that is, a coordinate or a point) and generating an address for it. Rooftop dataset—Type of dataset using point locations that represent discrete addresses. This type of dataset can be used where each valid address point (that is, a letter box, house, apartment, delivery point) has been previously determined, and is represented in the AGI file by a point geometry. Source data—The original data used to build the geocoding dataset. It contains features such as street centerlines, which are used to convert between descriptions and locations. Squeeze factor—This property affects how house numbers are interpolated along a street centerline. It makes it possible to avoid placing results of geocoding to the very ends of the street centerlines. The property‘s value is used only while geocoding street addresses, that is, addresses with house number, on centerline reference data when interpolation along street centerline is performed to obtain the matched point. The property‘s value has no effect on geocoding upon rooftop reference data and geocoding intersections. It is only available in the Find Address command. Standardization—Evaluating and adjusting the parsed address elements according to addressing rule standards. Street centerlines dataset—Type of dataset using street centerlines with attributes that can be used for searching, as well as using house number ranges. Transformation—Transformation of an address with elements in one structure, for example, an address to be geocoded to a standardized address with elements in another structure, for example, a geocoding dataset.

Functional Overview There are three basic operations involved in Address Geocoding: 1. Index Building—Processing the source data and building an Address Geocoding Index file. Part of processing the index data also involves address transformation and standardization. 2. Address Transformation (includes address parsing)—Decomposing the address into the matching attributes used to build the index file. 3. Address Matching—Taking a fully parsed input attribute and finding the best match in the index.


515

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 ( input) and target (geocoding engine expectant) address formats.

Specifying the input for this command is a two-step process in which you first define parameters on the Find Address Options dialog box. You then provide additional address details and perform the actual find through the Find Address dialog box. The Find Address dialog box is displayed only if the geocoding directory has first been defined. If you try to start this command and no geocoding directory is known to the command (or a previously specified one does not exist), the Find Address Options dialog box is displayed first to let you define the geocoding directory. (Clicking Options on the Find Address dialog box also displays the Find Address Options dialog box.). The Find Address Options dialog box lets you specify the following parameters used in the geocoding process:  Geocoding directory—Selected geocoding directory file (XML) that has information for one or more geocoding datasets, by default in the GeoMedia Warehouses folder.  Geocoding dataset—Dataset name to geocode against, containing all the dataset names from the specified geocoding directory file. If there is more than one dataset, the additional item is added to the top of the drop-down list. You then have the option (Address element name) of specifying an address element whose corresponding value is used for determining the geocoding dataset (that is, the specified address element defines the geocoding dataset name to be used to find the address location). For example, you might use a regional name, such as the city name, when geocoding adjacent city street networks.  Address element name—Address element to be used to specify the name of the geocoding dataset to be used (if a geocoding directory contains a number of named geocoding datasets). This drop-down list is enabled only if the Geocoding dataset has been set to .



516

Input address format—Address format ed by the selected Geocoding dataset drop-down list. By default, the first input address format is selected. If is the selected dataset, this list is populated with all the input address formats listed in the geocoding folder. The input address format is displayed as the first line in the tooltip, along with the description of the selected input address format in subsequent lines. For example, the tooltip for ―Street Address : City : State : ZIP‖ input address format is: Street Address : City : State : ZIP


Geocoding Street Address: 288 Hemlock Ln City: Whittier State: NC ZIP: 28789  Minimum match score—Value (in the range 0-100) that determines if an address has been successfully matched. If a match operation obtains a match score of at least this value, the match status is displayed as Matched. If the match score obtained is less than this value, the match status contains descriptive text detailing the mismatch. The default value is 100.  Offset distance and unit—The default offset value is two meters for centerline geocoding. Offset is not used for intersection or rooftop geocoding. The units drop-down list contains all available linear units and is initially set to the default linear unit as specified by the GeoWorkspace Coordinate System command.  Squeeze factor—Value between 0% and 100% (default) to specify the squeeze factor, which moves the geocoded points away from the end points of the street centerline. This value determines how the house numbers are interpolated along the street centerline. This value is ignored for intersection addresses and for rooftop geocoding. This value specifies what part of a street centerline is used for the geocoded point‘s placement. If the street centerline‘s length is L, then all geocoded addresses are located along the middle part of the centerline of length * L. If the specified value is 100%, locations are interpolated along the whole centerline and, thus, can be close to its endpoints. If the property‘s value is 0, then all geocoded points on this centerline are located exactly in the middle of it.  Maximum number of candidates—Restricts the number of match results displayed in the Match results grid on the Find Address dialog box by the specified value in this field. The default value is 100, which returns the 100 highest match scores. The valid values are positive integers ranging from 1 to 1000.  Style—Point style geometry. The style can be set for optimum map window display of the geocoded address point geometry results through the GeoMedia Select Style and Style Properties dialog boxes, with the point style being enabled. The default style is the default point geometry style. The Find Address dialog box lets you specify the following parameters used in the geocoding process and lets you start the process and view the resulting match details:  Address element/Value grid—Contains the read-only Address element column listing the source address elements of the chosen Input address format. The number and name of the elements of this column are determined and populated at runtime by your selection of the Input address format on the Find Address Options dialog box. If an address element name is set as a required element, it is displayed in bold and red font. If the option is chosen for the geocoding dataset, the address element as specified by the Address element name list is also displayed in bold and red font. The descriptions of the address elements are displayed as tooltips.


517

Geocoding The read-write Value column contains fields for specifying values for each of the corresponding address elements.



   



518

Find—After all the parameters have been defined, clicking this button starts the Find Address geocoding operation. If an address match is returned, the first match result is selected in the grid and the corresponding point geometry is displayed in the map window, and the map window is 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 results grid. Clear—Clears the Match results and Address Element grids and puts the cursor back into the first row of the Value column of the Address Element grid. Options—Displays the Find Address Options dialog box, which lets you specify the geocoding directory and other parameters used in the address geocoding process. Standardized address—Displays the input address in the standardized format. The standardized address is displayed even if the geocoding operation results in zero results. Match results—Displays the following match status details returned from a geocoding operation: Score, Matched Address, and Status.

This grid is populated with all the matched results sorted by their match scores, in descending order. The results can be resorted based on other columns by clicking on the column headers. The number of rows in the grid is limited by the geocoding operation and the value specified for the Maximum number of candidates in the Options dialog box. You can select any row in the grid and the geocoded point for the selected row is automatically centered in the map window. If you select multiple rows, the geocoded points for the selected rows are fitted in the map window. Details—Displays the Find Address Details dialog box with the match score, match status, standardized address, and matched address details, of the selected match candidate in the


Geocoding grid. The standardized address and matched address are in the source address format, if reverse transformations are defined in the specified AGI file. This button is enabled when the Match results grid is populated and a single row is selected in the grid.



Center/Fit—Pans the map window such that the geocoded point of the selected candidate is displayed at the center. If multiple candidates are selected, the label of the button is changed from Center to Fit, which fits the points in the map window. 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, squeeze factor, maximum number of candidates, and the style of the point geometry using the GeoMedia Select Style and Style Properties dialog boxes.

Using the Find Address Command The following sample workflow gives you an introduction to finding an address. The objective is to find the location of the following address in Knox County, Tennessee:

1818 Lake Ave Knoxville, TN 37916


519

Geocoding 1. Start GeoMedia, and then create a new GeoWorkspace. 2. Create an Access warehouse connection to: C:\Warehouses\GMAGTrainingCenterlineStreetData.mdb. 3. Add a legend entry for the NCStreets and the TNStreets feature classes. 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. You do not need to connect to this warehouse for the purpose of geocoding; doing so helps you visualize the data and relative position in the current coordinate system for the GeoWorkspace. 4. Select View > 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.

8.

9. 10. 11.

520

This is one of the input address formats ed by the dataset being used; you may choose a different format to use to enter the address information. 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. Type 90% as the Squeeze factor. Type 100 as the Maximum number of candidates. Optional: Click Style to define the point display settings for the results in the map window.


Geocoding 12. Click OK to confirm the options selected and to display the Find Address dialog box.

The column of Address Element names match the input address format selected in Step 7. 13. In the Address Element/Value grid, type the following values: Street Address: 1818 Lake Ave City:

Knoxville

State:

TN

ZIP:

37916

14. 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. 15. Note the matched values in the Match details field. To show this information, you may need to resize the dialog box or to scroll the match details vertically. 16. 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


521

Geocoding

17.

18. 19. 20. 21.

the Minimum Match Score, the status message includes information about which fields contributed to the mismatch. 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. Change the name back to Knoxville, pan to a different area, and then click Find again to check out the centering. 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. Next, type 1818 Lake Ave, Knoxville, TN 37916 as the Value for Post address on the Find Address dialog box. Click Find. Notice the match information and the geocoded location. It should be the same as before. Also, notice how you used the same input address in two different forms. This feature gives you a great deal of flexibility in how you can enter an address to find.

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



522

Input address format—Address format ed by the selected Geocoding dataset drop-down list. By default, the first input address format is selected. If is the selected dataset, this list is populated with all the input address formats listed in the geocoding directory. By default, the first input address format is selected in the drop-down list box, but you can select any of the other input address formats. The input address format is displayed as the first line in a tooltip, along with the description of the selected input address format in


Geocoding subsequent lines. For example, the tooltip for ―Street Address : City : State : ZIP‖ input address format is: Street Address : City : State : ZIP



Street Address: 288 Hemlock Ln City: Whittier State: NC ZIP: 28789 Address attributes—Attributes that form the address elements of the displayed source address definition. These attributes are presented in a grid that lets you easily specify the mapping between the address elements of the source address definition and the address attributes from the input feature class/query. The description of the address element is displayed as tooltip on the first column.

The read-only Address element column is populated with the address elements from the specified input address format. The read-write Attribute name column has a drop-down list that is populated with all the attributes from the input feature class/query that are of type Text, Memo, Byte, Integer, or Long. If the suggested field names are present in the input feature class/query, the command populates the second column with those names. However, you can change the default values.





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 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. Output Attributes—All the available fields in the input feature class/query, along with the fields generated by the Geocode Addresses command (like GeometryField, MatchScoreField, MatchStatusField, StandardizedAddressField, and MatchedAddressField). Clicking Attributes displays this dialog box so that you can select, rename, and re-order the output attributes as necessary. Advanced Properties—Minimum match score plus the Offset distance and corresponding unit. Clicking Advanced displays this dialog box so that you can change these values as necessary. The minimum match score value (in the range 0-100) determines if an address is successfully geocoded. Records that have a match score less than this value have a null geometry value generated and so do not appear in the map window. The default value is 100. All input record match statistics can be viewed by displaying the geocode addresses query in a data window. The default offset value is two meters for centerline geocoding. Offset is not used for intersection or rooftop geocoding. The units drop-down list contains all available linear units


523

Geocoding and is initially set to the default linear unit as specified by the GeoWorkspace Coordinate System command. The Geocode Addresses command outputs the results as a new query set of the geocoded points. You can display these resultant points in a map window and/or the nongraphic attributes of the geocoded points in a data window. For map window optimum display results, you can define the output minimum match score, offset distance and unit, and the style of the point geometry using the GeoMedia Select Style and Style Properties dialog boxes.

Using the Geocode Addresses Command The following sample workflow gives you an introduction to bulk geocoding, a process whereby you can geocode many addresses at the same time. This workflow uses the familiar GeoMedia query workflow. 1. Start GeoMedia, and create a new GeoWorkspace. 2. Create an Access warehouse connection to: C:\Warehouses\GMAGTrainingCenterlineStreetData.mdb 3. Add a legend entry for the NCStreets and TNStreets feature classes. This is the data that was used to generate the geocoding dataset used in this workflow. You do not need to connect to this warehouse for the purpose of geocoding; doing so here helps you visualize the data. 4. Create an Access warehouse connection to: C:\Warehouses\GMAGExercisesAddress.mdb 5. Select Analysis > Geocode Addresses.

6. From the Geocode addresses in drop-down list, select the table BulkAddressList, which contains 61 rows, each having an address to be geocoded. 7. For the Geocoding directory file field, click Browse; then select: C:\Warehouses\GMAGTrainingCenterlineStreetData.xml. 8. From the Geocoding dataset drop-down list, select TN. 9. From the Input address format drop-down list, select Street Address : City : State : ZIP. This is one of the input address formats ed by the dataset being used; it matches the selected table containing the addresses to be geocoded. 10. For Address attributes, ensure that the Address element names match the correct field (Attribute name) names from the input data.

524


Geocoding The correct names are used automatically when the geocode configuration files contain enough information, such as in this exercise. 11. Optional: Click Attributes to change query properties, that is, some or all of the attributes of the query results.

12. 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.

13. Optional: Change the Query name and/or Description on the Geocode Addresses dialog box. 14. 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. 15. Optional: Click Style to define the display settings for the results in the map window. 16. 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. 17. When you have defined the appropriate settings, click OK to see the results.

The added columns in the data window show the match Score, match Status, StandardizedAddress, and MatchedAddress.


525

Geocoding 18. 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. 19. Select the GeoMedia command Analysis > Queries. 20. On the Queries dialog box, select the geocode addresses query; then click Properties. 21. On the Query Properties dialog box, click Advanced. 22. On the Advanced Properties dialog box, change the minimum match score from 100 to 50. 23. 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. The results are a query in GeoMedia, and thus this query can be edited in the usual manner. It can also be placed in part of a series of queries, as well as being persisted with the GeoWorkspace.

Geocoding Addresses with Multiple Datasets This sample workflow demonstrates a more advanced use of the Geocode Addresses command. You may have noticed the option on the Geocode Addresses dialog box to select the dataset to use based on an attribute of the input. For this example, you use the following geocoding directory that references multiple geocoding datasets: NC North Carolina Centerline TIGER/Line data GeoMedia.AGIGeocodingEngine c:\warehouses\GMAGTrainingCenterlineStreetData.agi TN Tennessee Centerline TIGER/Line data GeoMedia.AGIGeocodingEngine c:\warehouses\GMAGTrainingCenterlineStreetData.agi 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.

526


Geocoding 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. The content of this XML file is the example given at the beginning of this workflow. 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 ; 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. 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. Before clicking OK, you could have clicked Attributes and then have selected the contents of the output query, and also have renamed any of the attributes.

Defining Geocoding Models The geocoding model is stored in the geocoding model XML file. The delivered Define Geocoding Model utility is an interactive program for creating, editing, and viewing geocoding models. There are several predefined geocoding models delivered with the GeoMedia Address Geocoding system, and you can create more. The Define Geocoding Model utility lets you create or modify geocoding model files. The geocoding model contains the following: Base Address Definition This is an address format used to store the reference data in the Address Geocoding Index (AGI) file. During AGI publishing, all reference addresses are transformed to this format, standardized, and stored in the AGI file. During geocoding, all addresses are also transformed to this format and then matched field-by-field to the addresses from the AGI file. Preprocessing Options


527

Geocoding These are simple rules applied for all input strings during both index building and geocoding, before applying the address transformation. They are required to simplify the transformation rules. They can include, for example, upper/lowercasing the input string, converting accented characters to composite or precomposed form, and so forth. The default options are to uppercase the input string, replace all blanks with a standard ASCII space (with Unicode code 32), and then remove multiple spaces. Index Configuration This is information related to construction of the AGI file:  One or more Matching Index formulae. The Matching Index defines which addresses should be considered as similar and how they should be ordered internally within the index.  Suggested names of most probable reference data tables (feature classes).  Range address element declaration and the suggested field names for range elements in reference data (only for centerline geocoding models, see below).  Transformation rules to convert reference data to the base address format. Geocoding Configuration This is information related to address geocoding itself. It includes transformation rules used by the geocoding engine for addresses to be geocoded. The format of the geocoding model file is described in the XML schema file gmagcmod.xsd. Workflow for Creating a Geocoding Model 1. Define the geocoding model type (rooftop or centerline). 2. Define the base address definition. This should contain at least one address element for rooftop geocoding models and at least two address elements for centerline geocoding models. It can consist of at most 16 address elements. 3. Add at least one address transformation for reference data. Every address transformation consists of: a. Source address definition - All source address elements can optionally define one or more suggested field names that are used by the Publish Address Geocoding Index File utility and GeoMedia commands to pick up default values for address elements' input. b. A set of mappings - Every mapping is a rule that transforms one or more source address elements to some base address elements. It can use a single parsing rules file for this. 4. Add one or more address transformations for the addresses to be geocoded. 5. Optional: Define matching indices that can be used by the geocoding model. They will be shown to the of the Publish Address Geocoding Index File utility while building the AGI. 6. Optional: Define suggested reference data feature class names with the concurrent street attribute field name and suggested range elements names (for centerline geocoding models only). See the "Define Geocoding Model Utility Help" for complete information on using this utility.

Defining Parsing Rules Many data sources are human-generated as plain text, such as postal addresses and bibliography records. The data has the implicit schema consisting of a set of attributes, for example, postal addresses consist of elements like house number, street, and so forth. The text string itself is generated by concatenating values of different attributes without any explicit separator between them. The order of attributes is not fixed and not all of them are present in all instances.

528


Geocoding However, convenient usage of data in computing requires it to be organized as structured records. Therefore, an approach is needed to convert unstructured data into some appropriate consistent format automatically. This approach should be generic, allowing development of a flexible software solution applicable to different data schemas/data sets available. From a practical point of view, it is desirable to have configurable parser software such that for a given dataset it might be tuned (probably with some effort) to become able to reveal the implicit structure of the data. Then the parser can process raw text strings, recognize structural elements and optionally standardize them with little or no interaction. The address geocoding system provided with GeoMedia performs such parsing. The approach used exploits the theory of Hidden Markov Model (HMM). Hidden Markov models present a general approach that is widely used for recognition problems, for 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 delivered Define Parsing Rules utility is an interactive program for composing, editing, and testing these address parsing rules. There are several predefined sets of rules delivered with the utility, and you can create additional ones. See “Geocoding Models and Parsing Rules” in the “Additional Geocoding Information” appendix for the description of the parsing rules delivered with this software.

Overview The address parsing rules are described by a parsing rules file, which includes:  Definition of HMM states, that is tokens.  Standardization rules for every HMM state/token.  Pre-parsed samples that define typical order of the tokens.  Mapping from tokens to output entities and elements. Output elements of the parsing rules are used to represent address elements in the address definition. Every token describes some atomic attribute of the input data. In the U.S. Street addresses, for example, good candidates for the tokens are:  Street prefix (‗E‘ in ‗E Main Street‘)  Street name (‗Second‘ in ‗N Second Ave‘)  Street type (‗Road‘ in ‗Forrest Road‘)  Street suffix (‗NW‘ in ‗MLK Blvd NW‘) During parsing, all characters or words in the input string are assigned to tokens. For this, the characters or words that can be contained within every token should be defined. In the present implementation of the parsing rules, the definition can be done in five different ways, each corresponding to a different token type: 1. ‗Dictionary‘ token type—This element type is defined by enumeration of all values it can contain. 2. ‗Pattern‘ token type—The values of this element are defined by a single regular expression. A good example of the ‗pattern‘ token is the base U.S. ZIP, which always contains exactly five digits and can be described by the ―\d{5}‖ regular expression. 3. ‗External Rules‘ token type—The values of this token are defined by some other parsing rules. It is a convenient way to embed an existing set of parsing rules into the current parsing rules. 4. ‗Reference‘ token type—This token is exactly the same as some other token. It is possible, for example, to define the ‗Street suffix‘ token from the U.S. Street example as a reference to the ‗Street prefix‘ token. 5. ‗Characters‘ token type—This is the most generic notion. It should be used if none of the previous token types can fully describe the values that can be assigned to the token. This


529

Geocoding token definition takes values that are similar to the given samples. This type is the most suitable for the ‗Street name‘ element. Optionally, the system can perform standardization. The standardization is performed as defined in the parsing rules. Every token‘s value is replaced with its standard form. Then, these values are taken to form the standardized output entity(entities). The standard form is defined separately for every token, as follows: 1. ‗Dictionary‘ token type—All dictionary items are combined in groups, with every group consisting of some standard form value and its aliases. During standardization, all aliases are replaced with the standard form of the group. 2. ‗External Rules‘ token type—The standardization is performed by the embedded parsing rules. 3. ‗Reference‘ token type—The standardization is defined in the referenced token definition. 4. ‗Pattern‘ and ‗Characters‘ token types—Tokens of this type contain standardization rules. Every rule contains the following: what to replace (a substring or regular expression), a replacement (a substring or regular expression), and several flags that affect the standardization process. Besides the tokens themselves, their characteristic sequences should be defined. This is done by providing training samples. Every training sample is a manually parsed string along with the sequence of tokens that form this string. For the U.S. Streets address parsing rules with the elements discussed above, such training sequences can be the following: Address Sample

Token Sequence

1st Ave E

Street name

Street type

Street suffix

E Main Street

Street prefix

Street name

Street type

Broadway

Street name

-

-

Military Way

Street name

Street type

-

Every training sequence has a weight that shows how often such a sequence appears in the real addresses. The more the weight, the more common this sequence is in real life. As the HMM technique is a probabilistic one, the quality of parsing can significantly benefit from the proper weights. The Define Parsing Rules utility itself provides a way to estimate the weights of the sequences by parsing the large number of addresses and providing statistics for different sequences. 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‘). th  Introduce a special token to take values of the ‗numeric‘ street names, for example, ‗89 street‘ or ‗Fifth Blvd‘. Introducing such tokens results in better parsing, as it is possible to:  More precisely define the values of each token.  Define better standardization rules. For example, ‗12 street‘ should be standardized to ‗12TH ST‘, but ‘12 oaks blvd‘ should be standardized to ‗12 OAKS BLVD‘. The sample parsing rules file for U.S. street names delivered with the utility, for example, contains 30 tokens. Outputting all tokens values is usually overkill, so the parsing rules file also defines the output rules. The system returns the parsed string as output entities; each of them consists of several output elements. Each output entity has one or more associated tokens, called required tokens. If at least one of these tokens participates in the result of parsing a string (that is, a sequence of tokens

530


Geocoding 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 . 4. Optional: Perform testing of the parsing rules using appropriate data sources, and then analyze the results.


531

Geocoding

Geocoding Coordinates Geocode Coordinates creates point geometries for a feature class or query based on projected or geographic coordinate values stored in the attributes of the input tables of that input feature class or query. For example, you can use a data table containing latitude and longitude values to place points. This command outputs the results as a new query that is dynamic. Thus, you can display the resultant geocoded points in a map window and/or the attributes of the geocoded points in a data window, and if the source warehouse changes, the resultant points also change. For example, if new storm tracks or tract data is added to a text file with storm data, then the points update to reflect the current storms and storm positions. In addition, you can set the style for the map window for optimum display results.

Geocode Coordinates s:  2-D and 3-D coordinate attributes.  Geographic or projected coordinates in any GeoMedia Professional coordinate system.  Field types: text, integer, long, single, and double.  Coordinate units (for example: degrees, radians) and formats (for example: decimal degrees, d:m:s) of all types ed by GeoMedia Professional coordinate systems.  Definition of the coordinate system through the Coordinate System Properties dialog box.  Output of a status indicator for troubleshooting bad coordinate data. If the resultant coordinate values are suspect or problematic, you can review the resulting Geocode query in a data window to inspect a newly created column called GeoCode_Status. If for some reason a point could not be placed, this field records the problem. You can then sort on the column or run attribute queries to locate the problem coordinate records. See the “Working with Coordinate Systems" section.

532


Geocoding 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.

5. 6. 7. 8. 9.

10. 11.

12.

The names of the first and second coordinate fields vary dynamically with the selected coordinate system, units, and format. Select the attribute to be used for the second coordinate from the drop-down list. Optional: Select the attribute to be used for the height value from the drop-down list. Optional: Change the default value in the Query name field. Optional: Type a query description in the Description field. 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. Optional: Click Style, and change the default style on the Select Style dialog box. 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. Click OK to generate and to display the points in the specified map window and/or data window.


533

Geocoding

534


SECTION 17

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 ed 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. 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. 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).


535

Inserting Traverses 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.  Specifying points and line features from a map window.  Loading an ASCII file containing the coordinate geometry definition. 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 line-placement methods, distance/bearing, distance/azimuth, or distance/deflection. The default is distance/bearing. The name of the direction field changes with each method.

Deflection Angle Computation Selecting the distance/deflection method s deflection angles by setting the next traverse leg to be relative to the orientation of the previous leg. This allows placement of a traverse leg by angle and distance where the angle is relative to the previous traverse leg rather than the com direction. When you select the distance/deflection method and specify a distance (d) and an angle value ( ), this command creates a new traverse segment (d) in the direction resulting from the angular deviation ( ) relative to the previous traverse segment, as shown in the following figure:

Positive ( ) values indicate a clockwise, or right-turn, deflection angle relative to the direction of the previous segment (as in the previous figure). Negative ( ) values indicate a counterclockwise, or left-turn, deflection angle.

536


Inserting Traverses If the previous traverse segment is an arc, the deflection angle is computed relative to the chord of the arc, as shown in the following figure:

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.

Precision key-ins from outside the dialog box are not ed. 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

Chord Direction

Chord Length

Delta

4

Direction

Path

4 4

Delta End Point


4

4 4

4

4 4

Radius

Tangent Direction

4

4

4 4

4

4

4

537

Inserting Traverses

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 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

Resulting 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

538

Resulting line placement


Inserting Traverses

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).

Additional Command Features Insert Traverse allows you to close (Close Feature) the current area feature by inserting a Line from the current position to the point of beginning of the feature, not to the Start_Point. The point of beginning is the first point of the first Line, Point, or Arc traverse type. This allows you to have the software enter the closing boundary of the area feature being defined. This command also allows you to adjust (Adjust) the closure of the feature using a Com or Bowditch rule adjustment to distribute the small error that accumulates through precision input of direction, distance around the area feature. Through this adjustment, the error is distributed to each traverse leg based on its length in comparison to the total perimeter of the area feature. The perimeter value is the sum of all Line and Arc distances that make up the area feature; it does not contain any traverse-line distances leading up to the start of the Line/Arc components. You can only adjust the closure if the primary feature class of the feature to be adjusted is an area feature class. Any rows in the grid that are set to Lock will not be adjusted. You enter the Line or Arc definition information for each boundary from point of beginning, then from boundary to boundary, and back to the point of beginning. Consequently, the closure error should be very small. The total tolerance of the area feature is calculated on the absolute tolerance you type in the Tolerance field. You enter the tolerance value as a check on the incorrect closure of a feature. If the closing error exceeds the tolerance specified, the feature is not adjusted. It is important to note that the Adjust and Tolerance capabilities of Insert Traverse are built in to solely help prevent operator input errors, for example, inputting a bearing using the wrong direction notation or transposing the digits for a distance value, which would then be result in large Adjust error values. 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.


539

Inserting Traverses 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 . If set to Projected (planar), the distances for all subsequent traverse segments are computed as planar distances.

Insert Traverse Workflows Primary Workflow The primary workflow for Insert Traverse is the collection, closing, and adjustment of individual area features. The recommended method of storing this area information is to store the area as one feature (the primary feature, for example, parcel) and the individual boundaries as separate features (which is automatically performed if the component feature class is defined). This command allows you to select a feature class to place and to select the component feature class for each traverse leg. When you are placing an area feature as the primary feature, Close Feature and Adjust are enabled once you have defined enough legs to make them useful. At least two legs must be defined before Close Feature is enabled, and at least three legs must be defined before Adjust is enabled.

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.

To insert a traverse by typing plat data: 1. Create a read-write connection.

540


Inserting Traverses 2. With an active map window, select Insert > Traverse.

3. Select the Start_Point traverse type from the Traverse type drop-down list. 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. Point dimension method defaults to the coordinate readout control setting, that is Lat/Long or Projected coordinates.

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 the end and start points of the feature being digitized with a new line when the points are close together.

A line is shown ing the end point of the previous linear feature and the start point of the GeoMedia Professional 's Guide

541

Inserting Traverses 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 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. 12. Click Save to save the traverse definition as a .trv file.

To insert a traverse using the map window: 1. Create a read-write connection. 2. With an active map window, select Insert > Traverse. 3. Click Use Map.

The dialog box is dismissed. The prompt displayed and the required input vary with the traverse type. 4. If the traverse type is Point, select a single point in the map window by clicking a point in space or snapping to a vertex.

The dialog box opens with the coordinates of the point in the dimension frame. OR If the traverse type is Line, select two points in the map window by clicking two points in space, snapping to a vertex, or a combination of the two.

The dialog box opens with the distance and direction information for the line in the line frame. OR If the traverse type is Arc, select two points in the map window by clicking two points on an existing arc geometry, snapping to a vertex, or a combination of the two.

The dialog box opens with the distance and direction information for the line in the arc frame. 5. Click Add to Grid to populate the grid.

A new line is added to the grid with the same traverse type and component feature class as the previous line. 6. End the feature as in the previous workflow.

To insert a traverse using an imported file: 1. 2. 3. 4.

Create a read-write connection. With an active map window, select Insert > Traverse. Click Load. Select the appropriate .trv file to populate the grid in the Insert Traverse dialog box.

Only the first two fields of the grid are populated.

542


Inserting Traverses 5. Optional: Edit the appropriate values. 6. Complete the feature as in the first workflow.


543

Inserting Traverses

544


SECTION 18

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

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

Setting Layout Window Options The Layout tab on the Options dialog box (Tools > Options) lets you set various controls for the appearance of the layout window and the behavior of some of the graphics commands.


545

Working with Layout Windows

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 s up to seven-decimal precision and is used for precision key-in control in the drawing commands (Line, Circle, and so forth), the Measure Distance command, the Legend Properties command, and the grid subinterval spacing. The precision readout sets the number of significant figures to display the accuracy of the unit readout value. The precision setting does not alter the numbers that you type into the fields, only the display of the numbers in the field. Values ending in five are rounded up. For example, if the precision readout is 0.123 and you draw a line that is 2.1056 inches long, the line value length is rounded. The length value appears as 2.106 inches long. If you are using millimeters as your drawing sheet units, you can have the values display in the fields as 3.5 mm or 3.50 mm. When you set options on the Layout tab for the units in a document, the settings do not affect the dimensional values or sheet size for the document. The Grid and Nudge selection area lets you set options for using the Grid Display and Grid Snap capabilities as follows:  Grid display—Displays a grid for precision element placement. The grid lines themselves are not considered part of the document and do not print.  Grid snap—Aligns elements with the grid, which is an invisible set of lines in the document that helps you align elements. When you select this option, elements always align with the grid lines or the nearest intersection of the grid lines.  Subinterval spacing—Sets the spacing of the grid lines.  Subintervals per interval—Determines the number of index grid lines. The read-only unit is set by the layout window Page Setup command. The size of each grid cell is determined by the Subinterval spacing. The Subintervals per interval determines the number of minor grid lines to display between the major grid lines. If the grid spacing is set to 0.25 inches and the grid index is set to four inches, then the minor grid lines display as dashed gray lines at 0.25 inch intervals, and the major grid lines display as solid gray lines at 1.0 inch intervals, per the following formula: major grid line interval = grid spacing X grid index.

546



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 the “Defining the Layout Window Page Setup” section in the “Printing in GeoMedia Professional” section 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 the “Printing Layout Sheets from the Layout Window” section in the “Printing in GeoMedia Professional” section for more information.

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


547


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

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

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

GeoMedia Layout Sheets GeoMedia layout sheets are fully composed plot layout sheets stored as an external disk file outside the originating GeoWorkspace. They contain the layout graphics and map graphics. The status of the map graphics in the sheet, static mode or dynamic mode, is maintained during the export and import process. GeoMedia layout sheets are limited to a single layout, ing background and working sheets. The layout sheets should be imported into the originating GeoWorkspace, where they can then be updated, and plotted, which provides a useful mechanism for maintaining dynamic plot files outside the GeoWorkspace. A distinction is made between layout graphics and map graphics. Map graphics are those graphics that originated in the map window, and they include a map, legend, scale bar, and north arrow. Layout graphics are those graphics that originated in the layout window (Version 4.0 and above) or in SmartSketch, and they include SmartFrames, borders, titles, logos, and so forth. To importing .gls files, both interactively and in batch plotting, the Export Layout command assigns custom attributes to the GeoMedia layout sheet file that defines particular characteristics of the sheet being exported. When importing .gls files, all effort is made to

548


Working with Layout Windows 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 "Exporting Layout Sheets and Templates" in this section for information on this command. 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 \Program Files\GeoMedia Professional\Templates\Layouts.

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

Imagineer or SmartSketch Template and Drawing Files Similarly to importing a GeoMedia layout sheet or a GeoMedia layout template, you can copy the graphics from an external Imagineer or SmartSketch template file (.igt) or drawing file (.igr) and place them as a new layout sheet in the layout window. This option s legacy workflows in case you have invested a lot of time building Imagineer or SmartSketch plot layout drawings and templates. Unlike the import of a GeoMedia layout sheet or a GeoMedia layout template, the import of a .igt template file or a .igr drawing file brings all the sheets contained in the drawing or template, including multiple working sheets and background sheets. Some SmartSketch components are not ed 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.


549


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

To import a layout sheet or template: 1. Select Window > Show Layout Window. 2. Select Sheets > Import Layout.

3. Select GeoMedia Layout Sheets (*.gls) from the Files of type drop-down list; then select the appropriate .gls layout sheet file. OR Select GeoMedia Layout Templates (*.glt) from the Files of type drop-down list; then select the appropriate .glt template file.

550


Working with Layout Windows 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. 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.

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. If the sheet you are importing has the same name as an existing sheet, you have the option to overwrite the existing sheet or to import the sheet with a different name.

Exporting Layout Sheets and Templates Export Layout lets you export the active layout sheet in the layout window to any of the following external file types:  GeoMedia Layout Sheet (.gls)  GeoMedia Layout Template (.glt), the default for-first time use  Bitmap (.bmp)  JPEG File Interchange Format (.jpg)  TIFF Tagged Image File Format - TIFF (.tif)  Georeferenced TIFF - GeoTIFF (.tif) You can insert GeoMedia layout sheets and templates back into the layout window using the Import Layout command. Thus, you can create a layout sheet to reproduce the design of an existing plot.


551

Working with Layout Windows 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 udate Map Graphics. This workflow provides a useful mechanism for maintaining dynamic plot files outside of the GeoWorkspace. To importing .gls files, both interactively and in batch plotting, the Export Layout command assigns custom attributes to the GeoMedia layout sheet file that define particular characteristics of the sheet being exported. You can access these attributes by selecting a GeoMedia layout sheet in Windows Explorer, clicking the right mouse button, and then selecting the properties of the file. On the Custom tab, the attributes are listed as follows:  Name of the originating GeoWorkspace (drive:\folder\name)—When shared network drives are referenced, the attribute value reflects the Universal Naming Convention (UNC). This is required primarily for batch plotting workflows, but it is also necessary for interactive workflows to that the selected .gls file is being imported into the GeoWorkspace from which it was originally exported.  Attribute:  Name: GeoWorkspace  Type: Text  Value: C:\GeoWorkspaces\USSampleData.gws (for example)  SheetName of the exported file  Attribute:  Name: SheetName  Type: Text  Value: Illinois (for example) When importing .gls files, all effort is made to reproduce the originating map window of each map layout frame found in the .gls file. The Batch Plotting utility 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. For GeoTIFF, if the layout sheet has more than one map frame, you must first manually select a base map to be used for georeferencing the entire sheet. If the layout sheet has a single map frame, the GeoTIFF tags are obtained from the available map frame. If you start the command without selecting a map frame, in the case of multiple map frames, the command terminates after informing you that you must select a map frame.

552


Working with Layout Windows The export to GeoTIFF option does not exporting rotated map frames or map frames that refer to a rotated map view. In such cases, the exported file will have incorrect GeoTIFF tags. 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 ed include 72, 100, 200, 300, and 600 dpi. Before exporting a sheet, you can use Update Map Graphics to update the graphics with any changes in the map window, including the addition or removal of legend entries as well as any style modifications.

To export a layout sheet or template: 1. that you have the appropriate information in the active layout sheet or template. 2. For GeoTIFF only: Select the appropriate map frame to specify the appropriate coordinate system if more than one map frame exists. 3. Select Sheets > Export Layout.

4. 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, .tif, 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. 5. For .bmp and .tif files, select the appropriate File resolution on the Export Options dialog box; then click OK to write the active layout sheet to the specified name and to exit the command.


553

Working with Layout Windows For .jpg files, select the appropriate File resolution and JPEG Quality Factor on the JPEG Export Options dialog box; then click OK to write the active layout sheet to the specified name and to exit the command.

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

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

Renaming Layout Sheets Rename Sheet renames the active layout sheet. You can rename both working sheets and background sheets.

To rename a layout sheet: 1. Make the appropriate layout sheet active. 2. Select Sheets > Rename Sheet. OR Place the cursor over the layout sheet tab, right click, and select Rename from the right mouse menu.

3. Type the new name; then click OK.

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

554


Working with Layout Windows To delete layout sheets: 1. Make the appropriate layout sheet(s) active. 2. Select Sheets > Delete Sheet. OR Place the cursor over the layout sheet tab, right click, and select Delete from the right mouse menu.

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

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


555

Working with Layout Windows To view layout window properties: 1. With an active layout window displayed, select Window > Layout Window Properties.

2. Review the information for the listed layout sheets. 3. Change the Visible settings as appropriate by toggling the value to Yes (visible) or No (hidden). A minimum of one layout sheet must be visible at all times. 4. Optional: Double click on a row to open the Layout Window Page Setup dialog box, and then change the page setup on the Layout Window Page Setup dialog box.

Manipulating Layers The Layers command (Layout > Layer) displays the Layer toolbar, which lets you view and set the active layer, display or hide layers on the active layout sheet, and change the layer of an element.

The Layer field displays the active layer on the layout sheet. You can change the active layer by selecting an existing layer from a list of all the layers on the active sheet or by typing a new layer name to create a new layer. You can create as many layers on a layout sheet as you need, but you cannot give the same name to two layers on the same layout sheet. The layer definitions and display status can be defined independently for the working sheet and its attached background sheet. Change Layer lets you change the layer for all of the elements you select. Although you can assign an element to only one layer, you can change the layer to which an element is assigned. The dialog box of this command displays the current (source) layer for all the selected elements, and you can then select the (target) layer to which you want to change them from a list of all the layers for the active sheet. Layer Status lets you set the display criteria for the layers in the current layout sheet, displaying or hiding layers in a list of all available layers on the active layout sheet through the Layer Display dialog box. This dialog box also lets you set the display of layer groups.

To create a layer: 1. Select Layout > Layer. 2. Type the name of the new layer in the Layer field; then press TAB. You can also create a layer using the Layer Groups command.

556


Working with Layout Windows To change the layer of an element: 1. Select the appropriate element(s). 2. Select Layout > Layer. 3. Click Change Layer on the Layer toolbar.

4. Select the target layer from the Change all to list; then click OK.

To display or hide layers: 1. Select Layout > Layer. 2. Click Layer Status on the Layer toolbar.

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. 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.


557


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

You can also create a layer using the Layer Groups command. On the Layer Groups dialog box, type the name of a new layer in the Layers field and press ENTER. The name of the new layer is displayed at the bottom of the Layers table.

To create a layer group: 1. Select Layout > Layer Groups.

558


Working with Layout Windows 2. In the Groups field on the Layer Groups dialog box, type the name of the new group, and then press ENTER. 3. In the Layers table, in the Grouped column, click each check box to include the layers in the group.

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.

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

To delete a layer group: 1. Select Layout > Layer Groups. 2. In the Groups table of the Layer Groups dialog box, select the layer group you want to delete; then press DELETE.

To delete a layer: 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.


559

Working with Layout Windows 3. Click Groups.

4. 5. 6. 7.

560

Select a group from the Layer Groups list. Click On to display the layers in the selected layer group. Click Off to hide the layers in the selected group. Click Apply to apply the current display settings to the active sheet in the layout window and to leave the dialog box displayed. OR Click Close to apply the current display settings to the active sheet in the layout window and to dismiss the dialog box.


SECTION 19

Deg Map Layouts for Printing in the Layout Window Deg Map Layouts Overview After defining the page setup, you can begin placing graphics in the layout sheet. You can place two kinds of graphics, layout graphics and map graphics. Layout graphics are graphics such as borders, titles, company logos, and so forth. Map graphics consist of an extracted subset of the map window (a map) and ing marginalia (legend, north arrow, and scale bar). See the “Page Setup” section in the “Working with Layout Windows” section. The order of placement is up to you; there are no requirements to place map graphics before layout graphics, or vice versa. All marginalia placed in the layout are associated with the originating map. This means that the legend automatically reflects the graphic symbology used to define the map in the layout sheet. The north arrow automatically reflects the projection parameters and view rotation of the map in the layout sheet, and the scale bar automatically reflects the plot scale in the layout sheet. Placing marginalia is possible only if a map exists in the layout sheet. In addition, you can place multiple maps in a layout sheet when appropriate. To place layout graphics, you use the drawing commands available in the layout window. In of map graphics placement, there are two basic workflows: placing map graphics using layout frames, and placing map graphics without using layout frames. Each workflow is accomplished using different commands. Once the map graphics have been placed, there are several tools and commands available for modifying the size and position of the map graphics items and for placing a cartographic grid or reference grid on the map.

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

Defining Map Specifications in the Map Window The Display Properties command lets you define the following properties that affect the way in which the map graphics are displayed: display scale, nominal map scale, rotation angle, angular units, and legend entry display. You access this command in an active map window by selecting View > Display Properties.


561

Deg Map Layouts for Printing in the Layout Window See the “Defining Map Window Display Properties” section in the “Working with Map Windows” section for more information on this command.

Requirements for data display and presentation for analysis are generally quite different from those for output. In analysis, the display scale is constantly changing as you zoom in and out. Feature symbology settings are generally defined so they produce legible results at multiple display scales. In some cases, the data may be viewed in its raw geometric form as non-symbolized point, line, and area data. In output, the data presentation is typically defined to 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. 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 the “Working with Styles” section in the “Working with Map Windows” section 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, where unique legend settings can be applied independently of the settings used for analysis. Paper (size is true at nominal map scale)

View (size is true at any display scale)

When defining the symbology settings for output, the size of point, text, and patterned area fill features and the weight for the line and area boundary features should all be defined with the output plot scale in mind. Scale ranges are enforced as the data are transferred from the map

562


Deg Map Layouts for Printing in the Layout Window 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. 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. The rendering of map graphics takes into 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 the “Merging Feature Classes and Queries” and “Generating Base Geometry” sections in the “Analyzing GeoMedia Professional Data” section for more information.

Previewing the Map in the Map Window Once you have defined the display properties (as defined in the Display Properties dialog box), you can easily obtain a WYSIWYG preview of your map data in the map window by using the View > Zoom > to Nominal Map Scale command. This command adjusts the map view by zooming in or out to the defined nominal map scale, maintaining the view center of the window. The legend, north arrow, and scale bar are also adjusted if they are displayed. The nominal map scale is set on the Display Properties dialog box (View > Display Properties). See the “Defining Map Window Display Properties” section in the “Working with Map Windows” section for more information.


563

Deg Map Layouts for Printing in the Layout Window To zoom to nominal map scale: 1. 2. 3. 4.

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

Defining Marginalia Specifications in the Map Window Marginalia items in the layout window consist of the legend, north arrow, and scale bar. The symbology for the marginalia being transferred from the map window to the layout window is based on the current settings for each of the marginalia items. Whatever the active parameters are for these marginalia items in the map window, the same parameters are used to render these items in the layout window. In the case of the north arrow and scale bar, each corresponding Properties dialog box in the map window contains a Save as Default option. If this option is selected, the default settings, not the active settings, are used when placing the north arrow and scale bar into the layout window. This ensures consistency across layout sheets. If necessary, you can further customize the marginalia in the layout window itself through various layout window commands, as explained later in this section.  Legend-The symbology for each of the legend components is based on the settings defined on the Select Style, Legend Entry Properties, and Style Properties dialog boxes for each of the legend items. Legend definitions in the map window have an impact on what legend entries will be rendered in the layout window. If you do not want a particular legend item to appear in the layout window legend, you should use Hide Legend Entry (right mouse menu) in the map window legend. See the “Customizing the Legend“ section in the “Working with Map Windows” section. Legends are placed in the layout window with all default settings, regardless of the changes made to the map window legend properties (such as changes to the background color or the fonts of the title, subtitle, or heading).  North Arrow-To display the north arrow in the map window, you select View > North Arrow. On the shortcut menu (right mouse click) of the north arrow, you next select Properties. You can then define the size of the arrow by selecting a point size from the drop-down list or by typing the appropriate size. The drop-down list only goes to 96 points, but you can type larger values, such as 288 points (4 inches). The maximum size allowed is 32,767 points. You can also define the background color, position, symbol used, and azimuth of the north arrow . See the “Displaying the North Arrow“ section in the “Working with Map Windows” section. There is a large assortment of predefined north arrows and com 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 com 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. Scale Bar-To display the scale bar in the map window, you select View > Scale Bar. On the shortcut menu (right mouse click) of the scale bar, you then select Properties and make the appropriate changes. Use Define intervals on the Intervals and Units tab to define a fixed size scale bar. When this option is not selected, the size of the scale bar will be 20% of the width of the map window.

564


Deg Map Layouts for Printing in the Layout Window See the “Displaying the Scale Bar“ section in the “Working with Map Windows” section.

Basic Map Layout Workflows The flexibility of the Layout Window commands lets you tailor the actual workflow you use to your exact requirements. The following workflows illustrate the typical uses of these commands.

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

Placing Map Graphics in Layout Sheets Without Using Layout Frames This workflow is commonly used for producing a plot of data displayed in a map window, where the map and its associated marginalia must conform to pre-defined specifications. 1. Set up your map window with the specific data you want displayed at the appropriate zoom level, and define the appropriate marginalia settings. 2. Open the layout window, and using the Sheets > Import Layout command, import a layout template. 3. Optional: Use the assortment of drawing commands available in the layout window for placing title blocks, additional text, company logos, and so forth, to embellish the map.


565

Deg Map Layouts for Printing in the Layout Window 4. Select the Insert > Map command. Identify the appropriate map window, geographic extent, plot scale, and mode. See “Layout Graphics Components” in this section and GeoMedia Professional Help for more information on the drawing commands. 5. Select the previously placed map, and then select the Insert > Legend command, and identify the location for the placement of the legend in the layout sheet. 6. Select the previously placed map, and then select the Insert > North Arrow command, and identify the location for the placement of the north arrow in the layout sheet. 7. Select the previously placed map, and then select the Insert > Scale Bar command, and identify the location for the placement of the scale bar in the layout sheet. 8. Modify the size and position of the map graphics as necessary. 9. Optional: Place a cartographic grid using the Insert > Cartographic Grid command. 10. Optional: Place a reference grid and reference index using the Insert > Reference Grid and the Insert > Reference Index commands. 11. Select View > Zoom > to Actual Size to preview the map layout. 12. Plot the layout. OR Using the Sheets > Export Layout command, export the layout sheet to one of the available export formats.

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

Map Graphics Components You can insert maps or maps and their associated marginalia into layout sheets with the Insert Map and the Insert Graphics into Layout Frames commands, respectively. These commands let you insert maps and selected marginalia into the location you want on a layout sheet in the layout window. You can review the status of the placed map graphics using the Map Properties command. Insert Map inserts a single map into an empty layout sheet, without predefined layout frames. You can then place marginalia for the map with the individual commands for their respective placements: Insert Legend, Insert North Arrow, and Insert Scale Bar. The graphic size of the marginalia is determined by the current map window settings for each marginalia item. Insert Graphics into Layout Frames inserts a map and its associated marginalia in a single step into existing layout frames, which were previously placed in the layout sheet with the Insert Layout Frames command. This command places marginalia to fit into all drawn layout frames.

Map Specifications Map specifications for the Insert Map and Insert Graphics into Layout Frames commands are defined in of a map window, a geographic extent, a plot scale, and a static/dynamic mode setting.

566


Deg Map Layouts for Printing in the Layout Window 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 of the map window, which can be defined in a variety of ways. You can select the method for defining the geographic extent for the map from the following methods, and you can provide any additional necessary parameters:  Existing Shape-If the chosen feature is a geometry collection, this parameter uses an existing, -defined area geometry type or compound geometry type (containing an area definition) in the map window to identify the geographic extent. The area between the outside of the area feature and the layout frame limits is cropped. You can use the largest geometry or all the geometries in the collection.  Geographic Frame-Requires a -defined entry of the upper-left and lower-right corners of the quadrangle, defined using geographic coordinates (for example, d:m:s) to identify the geographic extent. This option is valid for projected or geographic coordinate systems defined in the GeoWorkspace coordinate system settings. The area between the outside of the quadrangle and the layout frame limits is cropped.  Map Window (the default method)-Uses the area currently displayed in the selected map window to identify the geographic extent. The map window display area is defined by the window extent when the map window is in the Restored state. This is because only one window can be maximized at a time, and when the active window is maximized, all other non-minimized windows revert to their Restored state. This behavior may give the perception that this selection is producing the wrong result. To illustrate this behavior, open a single map window (with data) and the layout window. Make the map window active, and maximize the window. Fit the map data to the window by selecting View > Fit All. Next, select Window > Tile Horizontally. The map window and layout window are now both currently being displayed in their Restored states. However, the displayed data extent in the Restored map window is half of the displayed data extent of the maximized map window. If the windows are in their maximized state, and the layout window is active, the map window will appear Restored in the background. If the map window active, it will appear maximized, and the layout window will be Restored in the background. Only one window can be maximized at a time, so to get around this behavior, minimize all windows except the map window you want, and select Window > Tile Horizontally. The map window will be made as large as possible within the application, displaying the Restored state.  Paper Size-Requires a -specified paper size. The units for the Height and Width values are based on the Distance unit defined on the Layout tab of the Options dialog box. The unit type (inches, centimeters, and so forth.) is displayed to the right of the fields. By default, the height and width are equivalent to the sheet size. The geographic extent varies based on the plot scale selected.  Polygon-Requires a -defined digitizing of a polygon to define the geographic extent. The area between the outside of the polygon and the layout frame limits is cropped.  Projected Frame-Requires a -defined diagonal entry of the upper-left and lower-right corners of the frame or rectangle, defined using projected coordinates to identify the


567

Deg Map Layouts for Printing in the Layout Window

 

geographic extent. This option is valid for projected coordinate or geographic systems defined in the GeoWorkspace coordinate system settings. Rectangle-Requires a -defined, two-point rectangle definition in the map window to define the geographic extent. Spatial Filter-Requires an existing, -selected spatial filter to define the geographic extent. The area between the outside of the spatial filter and the layout frame limits is cropped. If the spatial filter is defined by a select set containing a geometry collection, only the contents included inside the largest of the geometries will be considered to place the map.

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. -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 the “Defining Map Window Display Properties” section in the “Working with Map Windows” section for more information.



If the size of the map placed exceeds the size of the paper (defined on the Layout Window Page Setup dialog box), you must do one of two things. You can either increase the size of the paper on the Layout Window Page Setup dialog box, or you can crop the map placed so that it fits the paper. Fit to frame-This option is only available with the Insert Graphics into Layout Frames command. The plot scale is automatically calculated to perform a best-fit of the geographic extent into the existing layout frame. This option ensures that the map fits within the limits of the current layout design.

Static and Dynamic Modes The mode of the map graphics determines the relationship and behavior between the map graphics portrayed in the layout window and their originating map window. You can select from the following modes:  Static mode captures a snapshot in time, that is, what the data looked like when it was placed into the layout sheet. Any changes made in the originating map window are not automatically reflected in the layout window. With this mode, you must use the Update Map Graphics command to update the map. When Static mode is selected, the originating map window of the map graphics can be deleted without affecting the map layout.  Dynamic (the default) mode permits automatic updates, that is, certain types of modifications made in the map window are automatically reflected in the layout window, such as symbology changes or the addition or removal of feature classes. When Dynamic mode is selected, the originating map window of the map graphics is required to maintain the link with the map layout.

568


Deg Map Layouts for Printing in the Layout Window 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 “Modifying Maps” in this section for information. 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 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 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.


569

Deg Map Layouts for Printing in the Layout Window Scale Bar When placed using the Insert Scale Bar command, the scale bar is placed in the layout sheet using the parameters defined in the Scale Bar Properties dialog box of the originating map window. When placed into an existing layout frame using the Insert Graphics into Layout Frames command, the size of the scale bar varies based on the settings defined in the Scale Bar Properties dialog box of the originating map window. If the properties are defined as automatic (the Define intervals check box is unchecked on the Intervals and Units tab), the scale bar will be scaled so it fits within the extent of the layout frame's ―X‖ direction, (plus/minus one interval - to allow for round off). If the properties are defined as fixed (the Define intervals check box is checked), the scale bar will be sized according to the pre-defined interval setting. Placement of the scale bar into scale bar layout frames will be such that the center of the scale bar will be coincident with the center of the original layout frame, adjusting the layout frame to match the newly calculated size of the scale bar. Scale bars can be edited, moved, and scaled after placement, but they cannot be rotated. 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 “Modifying Map Graphics in Layout Sheets” in this section for information.

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

Looking at the Drawing Toolbox Most of the layout window graphics commands are found on or accessed through the Drawing toolbox, which is displayed by default at the bottom of the layout window. These commands let you place, edit, and symbolize layout graphics. In addition, this toolbox lets you define the active linear and fill styles and lets you apply those styles to elements in a select set. You can turn this toolbox on or off through View > Drawing Toolbox.

For various placement and editing commands, additional fields are displayed on the right side of an expanded Drawing toolbox. For example, when you select the Circle command, a Radius field is added.



570

Draw-Displays an assortment of menus of commands that operate on graphic elements in a select set, and provides additional commands to create symbols and to define the active symbol for placement.


Deg Map Layouts for Printing in the Layout Window       

Select Tool-Selects elements in the active layout sheet, and terminates any other active commands. This is the default active command in the layout window. Placement and Editing tools-Available from corresponding drop-down menus. These commands are also available on their corresponding toolbars. Text-Places one or more text boxes into which you can place text. Delete-Deletes the objects in a select set. Linear Controls-Define an active linear style by defining the color, width, pattern, terminators, end cap, and settings; and apply the style. Caps and Controls-Applies the active linear end cap and style to objects in a select set. Fill Controls-Apply a solid color fill to rectangles, circles, ellipses, and polygons.

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.

Draw Menu Commands Clicking Draw displays menus of the following commands for fine tuning layout window graphics (some commands are also available on their corresponding toolbars): See the corresponding topics in GeoMedia Professional Help for information on using these commands. Group Ungroup Order >

Bring to Front Send to Back Bring Forward Send Backward

Nudge >

Up - Up Arrow Down - Down Arrow Left - Left Arrow Right - Right Arrow

Align >

Left Center Right Top Middle Bottom

Distribute >

Horizontally Vertically


571

Deg Map Layouts for Printing in the Layout Window Group Ungroup Spin or Flip >

Spin Spin Left Spin Right Flip Horizontally Flip Vertically

Create Symbol Set Active Symbol See “Creating Symbols” later in this section.

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

Placement Menu

Editing Menu

See the corresponding topics in GeoMedia 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 commands are also available on layout window menus. See the corresponding topics in GeoMedia Professional Help for information on using these commands.

572



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.

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

Changing Graphic Element Properties Once graphic elements are placed in the layout window, you can easily display and change their properties by selecting an element and then by starting its corresponding Properties command from the right mouse menu. Graphic elements can be divided into four categories:  Linear (line, arc, curve, and polyline)  Symbol  Area (circle, ellipse, rectangle, and polygon)  Group The properties for each element can in turn be divided into general properties and geometry properties, which are set on the corresponding two tabs of the various Properties dialog boxes. For group elements, however, this dialog box does not have tabs. The General tab is the same within each category. The General tab for linear and area geometries contains an option to toggle between a Simple Style and a Map Window Style. Note that some dialog boxes (for example, legend, mapframe, object, and text) do not have the Simple/Map window style option. You can define simple line styles or select a map window style from the named styles of the GeoWorkspace. When choosing a named style, the remainder of the controls in the Style definition frame are disabled. Also in this case, the style definition is converted to a layout window style definition. Some aspects of a complex style definition may be lost during this process, and special handling is required for point style types used in pattern line styles.


573


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:

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 s. 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 s 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:

574


Deg Map Layouts for Printing in the Layout Window Element

Geometry Properties

Arcs

Center, start, and end coordinates; radius; start and sweep angle

Curves

All the nodes

Ellipses

Center point, primary and secondary axes, and rotation angle

Lines

Start and end coordinates, length, and angle

Polygons

All the vertices

Polylines

All the vertices

Rectangles

Four coordinates representing the four corners, height, width, and angle

Symbols

Origin coordinates, scale factor, and angle

The Properties command also lets you delete vertices or nodes of polyline, polygon, and curve elements. Groups are a special element type in that they are collections of elements from the other element types and group properties. Thus they are different from other graphic element properties. After changing the appropriate properties and clicking OK, the selected element is displayed on the specified layer with the specified sheet position, size, and angle. For linear types, the selected element is also displayed with the specified line color, style, width, and terminators. For area types, the selected element is also displayed with the specified line color, style, width, and fill color. If a group, the map frame name is updated appropriately. Changing Group Properties Only groups constructed using the Insert Layout Frames command are eligible for editing, specifically the map frame name used by the Batch Plotting utility. You can change the properties of a group through the Group Properties dialog box. You start this command by selecting the layout frame group and then Properties from the right mouse menu. The read-only properties listed are the following: number of items in the group, if the group is nested within another group, and if the group contains nested groups. The Batch Plotting-related map frame name is only enabled on valid layout frame groups.

See GeoMedia Professional Help for complete information on this dialog box.


575

Deg Map Layouts for Printing in the Layout Window 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. 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.

For all new text inserted, the layout window defaults to igTextSizeTypeTile. All old text that was placed at another standard is interpreted using this standard. Changing Text Properties After placing the text, you can later change its properties by selecting the text and then by selecting Properties from the right mouse menu to display the Text Properties dialog box, which has three tabs. See GeoMedia Professional Help for information on using this dialog box. The Text tab lets you change the font, text direction, text alignment, margins, and line spacing.

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.

576



Working with Linear Styles Various controls on the Drawing toolbox let you review, define, and apply an active linear style. This active style includes the color, width, pattern, terminator, end cap, and settings. When you open the layout window, the controls on the Drawing toolbox are initialized to reflect the properties of the active linear style, which is displayed on the Apply Linear Style button in the middle of the toolbox.

Clicking the Apply Linear Style button applies the linear style to the objects in the select set. This button also provides a preview for the linear style. The preview is updated when a change is made to the linear color, width, type, terminator, end cap, or 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. 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 section.


577

Deg Map Layouts for Printing in the Layout Window Styles Conversion The map window styles system and the layout window style system differ enough that the conversion from one to another is not complete. The following tables describe what converts, what partially converts, and what does not convert. Entries that do not convert have a note to describe what is done under that condition. Point styles are a special case. Because the layout window can only use .sym files for symbol styles, all non-sym symbols need to use a substitute .sym. The SymbolRendererName and Source property are used to parse the cell/symbol/filename. Then the software looks for a .sym matching the name of the symbol in the folder in which the source resides. If a suitable .sym is not found, the symbols folder is searched. If a matching .sym still is not found, a default symbol is used and an error message is displayed. For predefined symbols, a matching .sym is delivered. Font styles are simulated by creating a .sym containing a field. Style Properties - Simple Line Style Functional Capability

Convert?

Notes

Color

Yes

-

Translucency

Yes

-

Width

Yes

Line type

Yes

-

Dash-gap sequence

Yes

-

Dash-gap sequence proportional to width

No

Always uses igPhaseNormal.

Start cap

Partially

Square, round, triangle, and no cap are ed. The four Anchor types are converted as no cap with a corresponding terminator and scale based on line width.

End cap

Partially

The four Anchor types are converted with a corresponding terminator and scale based on line width. The actual cap is set to the same value as the start cap.

Dash cap

No

The dash cap cannot be defined independent of the start cap. The actual cap is set to the same value as the start cap.

Midline

Yes

-

Offset - left/right

Yes

Direction determined by positive/negative value

Offset distance

Yes

-

Advanced tab - ABS

No

Converted internally to mm.

Ignored

Style Properties - Pattern Line Style

578

Functional Capability

Convert?

Notes

Point style

Partially

Styles are converted by .sym. Font styles are emulated by .sym containing a field.


Deg Map Layouts for Printing in the Layout Window Functional Capability

Convert?

Notes

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 with angle

Yes

Using 'break on changes in direction'.

Position - Repeat with spacing

Yes

Adjust to produce even spacing

Yes

Gaps are set to stretchable.

Starting inset

No

This is problematic but may be added as a future enhancement. Ignored

Ending inset

No

Ignored

Offset - left/right

Yes

-

Offset distance

Yes

-

Advanced tab - ABS

No

-

Ignored.

Style Properties -Symbol Style Functional Capability

Convert?

Notes

Type

No

These attributes are used to find a suitable substitute .sym.

Source

No

-

Name

No

-

Size

Yes

Symbol is scaled when converted

Define override color

Yes

Accomplished on the Line Style dialog box.

Translucency

No

Ignored.

Rotation

Yes

Accomplished on the Line Pattern dialog box.

Alignment

No

Ignored.

Offset X distance

Yes

-

Offset Y distance

Yes

-

Display attribute value in symbol

No

Ignored.

Ignore map rotation

No

Ignored.

Ignore geometry rotation

Yes

Accomplished by Relative/Absolute orientation setting.

Always keep upright

Yes

Advanced tab - ABS

No


Ignored.

579

Deg Map Layouts for Printing in the Layout Window Style Properties - Font Style (simulated by a field in a symbol) Functional Capability

Convert?

Notes

Font

Partial

Strikeout is not ed.

Size

Yes

-

Character

Yes

-

Color

Yes

-

Translucency

Partial

Rotation

Yes

Alignment

Partial

Mapped.

Offset X distance

Partial

Simulated by symbol origin.

Offset Y distance

Partial

Simulated by symbol origin.

Display halo

No

-

Halo color

No

-

Halo size

No

-

Ignore map rotation

No

-

Ignore geometry rotation

Yes

Accomplished by Relative/Absolute orientation setting.

Always keep upright

No

-

Advanced tab - ABS

No

-

Only on border and fill. -

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

580



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

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

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


581

Deg Map Layouts for Printing in the Layout Window Defining End Cap and Styles Clicking the End cap and button applies the active linear end cap and style to objects in the select set. The end cap and settings can be applied to linear geometries (including area boundaries) but cannot be applied to rectangles, circles, ellipses, or polygons. You can change the active set of linear end cap and by clicking the corresponding arrow button, which displays the Select Caps and s dialog box for defining the start and end cap and mid-line types for the active style.

Start and end caps - Square Mid-line - Miter

Start cap - Triangle; End cap - Triangle Mid-line - Round

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

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

582



Looking at the Standard Toolbar There are two commands on the Standard toolbar to note for special use in the layout window.

Zoom to Actual Size-Displays the active layout sheet at a 1:1 paper scale. Hide Layout Window-Hides the layout window and shows the previously active window, either the map window or the data window. 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. 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. 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 uned workflow. Symbols that you create display the following default behaviors:  90-degree rotation angles.  Automatic alignment with a target element or object when the symbol is placed in a document.  No inherited size from their source definition; size is determined by the Styles dialog box, not the size the symbol was created with. 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.


583

Deg Map Layouts for Printing in the Layout Window To create a symbol: 1. 2. 3. 4.

Select a set of elements on the layout sheet. From the Drawing toolbox, select Draw > Create Symbol. Click a point on the layout sheet to define the origin of the symbol. On the Save As dialog box, select the directory, and then type an appropriate name.

When creating a symbol using different elements, press CTRL while choosing elements with the Select Tool.

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

To set an active symbol: 1. Open a layout window and make it active. 2. Select Draw > Set Active Symbol from the Drawing toolbox or from the Symbol toolbar.

584


Deg Map Layouts for Printing in the Layout Window 3. Click Browse.

4. Select an appropriate symbol file; then click Open. 5. Type a value greater than 0 in the Scale factor field of the Set Active Symbol dialog box; then click OK.

Placing a Symbol The Symbol command lets you place the active symbol interactively with a mouse click. The active symbol can be one you have defined with the Set Active Symbol command or the default symbol, Point.sym. The origin of the symbol being placed is attached to the cursor when you move the cursor, and the symbol is placed at the cursor location upon clicking. You can place multiple symbols until you exit the command. 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.

Changing Symbol Properties After placing a symbol, you can later change its properties by selecting the symbol and then by selecting Properties from the right mouse menu to display the Symbol Properties dialog box, which has two tabs. The General tab lets you define the layer and review the source file of the


585

Deg Map Layouts for Printing in the Layout Window selected symbol. The Geometry tab lets you move the symbol by changing the origin values, lets you change the symbol size by changing the scale factor, and lets you rotate the symbol by changing the angle. You can also set the mode to move, rather than edit by checking the check box. In the move mode, you can only change the position of the element, not its shape. In edit mode, you can change both. See GeoMedia Professional Help for information on using this dialog box.

Zooming to Actual Size Zoom to Actual Size lets you preview the plotted area at the paper size on the screen. This command lets you rescale the view in the active layout sheet to the actual size as if it were printed on paper, thus functioning similarly to the Print Preview command in Word®. Obviously, most plots exceed the size of the monitor, so you need to use the Pan command or horizontal and vertical scroll bars to move about in the layout window. You can access this command from the Standard tool bar or the View menu. Zoom to Actual Size is useful in the plotting workflow to let you see the layout at actual size before printing, that is, it lets you have a WYSIWYG view or plot preview of your layout window. This command affects the entire active sheet; the center of the sheet view is maintained, but the graphic contents are scaled. This command assumes that you have defined the logical dimensions for the layout sheet in the Page Setup command and that the appropriate extent of the data is displaying properly in the layout sheet. If graphics are falling outside the sheet limits, you should increase the size of the layout sheet. Zoom to Actual Size gives a 1:1 representation. However, this may not necessarily be completely accurate in the final output. Printers usually give the resolution in dots-per-inch (DPI), so it is easy to convert pixels to real inches. In contrast, video displays give the resolution only in pixels. Video displays are a certain number of pixels wide but are without any information about the real display-area dimensions. It is impossible for a program to determine the real output dimensions because there is no way for it to determine the real dimensions of the viewable area on a video display. When output is destined for a printer, an application can determine dots per real inch; however, for a video display, these numbers define a logical inch, which is almost never equal to a real inch.

586


Deg Map Layouts for Printing in the Layout Window Toggling Windows The Hide Layout Window command is enabled when the layout window is active and hides the layout window and shows the previously active window, either the map window or the data window. You can also switch between windows through commands on the Windows pull-down menu. The corresponding Show Layout Window command is enabled when either a map or data window is active. It creates the layout window (if necessary), displays it, and makes it the active window.

Setting SmartSnap As you move the pointer in the layout sheet, the software automatically updates values in the ribbon bar, giving you constant on the size and position of the element you are drawing. As you draw, the software also shows next to the pointer a temporary, dynamic display of the element you are drawing--this 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.

The Tools > SmartSnap Settings command lets you define which relationships are recognized by the software as you draw. On the SmartSnaps tab you can set these relationships and clear those you do not want so that the software does not place relationship handles. A relationship handle, or glyph, is a graphic used to represent a geometric relationship between elements, showing that the designated relationship is being maintained. You set these relationships by selecting the appropriate check boxes on the tab.

The Cursor tab lets you define the sizes of the Locate zone around the pointer in pixels. The locate zone is a circular area at the center of the crosshair cursor or at the end of the arrow cursor that specifies how close the cursor must be to an element you want to recognize or select. When using the placement and editing commands and the cursor is within this distance of a graphic element in the layout window, the element is snapped to if the appropriate snap has been turned on. The software recognizes relationships based on elements within the locate zone so that you do not have to move the cursor to an exact position. For example, if part of an element is within the locate zone, the software recognizes a Point On relationship. The size of the locate zone is indicated by a circle around the center of the pointer crosshair.


587


The Preview display shows the size of the locate zone.

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

To insert a new object: 1. Select Insert > Object.

2. Select the Create New option.

588


Deg Map Layouts for Printing in the Layout Window 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. The contents of the list depend on which applications installed on your computer linking and embedding. 4. To return to the layout window, do one of the following:  If the object was created in another application in a separate window, select Exit or Update on the File menu in that application. If a message appears asking if you want to update the document, click Yes.  If the software temporarily replaces some of the GeoMedia Professional or GeoMedia-based application menus and toolbars, click anywhere outside the embedded object.  When you return to GeoMedia Professional or to a GeoMedia-based application, a box the size of the object appears beside the pointer. You can click on the layout sheet to place the object that you edited or created.

To insert an existing object: 1. 2. 3. 4.

Select Insert > Object. Select the Create from File option. In the File field, type or select the name of the object you want to embed, and then click OK. When a box the size of the object appears beside the pointer, you can click on the layout sheet to place the object that you edited or created.

If you are working in the source software, you can embed an existing object with the Paste Special command on the Edit menu. In addition, you can embed an object by dragging and dropping a document from Windows Explorer into a layout sheet in the layout window. There are assorted tools and commands available that can be used to adjust the graphic display of an object after it has been placed in the layout sheet. See “Changing Object Properties” in this section for more information.


589


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

Creating a Map Title To begin, create and place a map title. Select the Text button on the Drawing toolbox, and use the rectangle method to place text.

Use a mouse down, mouse drag, mouse up sequence to define a rectangle. Next, select the appropriate text characteristics from the text Ribbon toolbar, and then type the map title text in the rectangle.

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. 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.

590



Now, select the previously placed frame, and then from the right mouse menu select Properties. On the Rectangle Properties dialog box, adjust the frame properties by changing the line width and color.

Inserting a Logo Next, insert the city logo into the layout sheet. A logo is an non-map graphic that is inserted as an object. Select Insert > Object from the layout window menu bar.

Ensure that the Create from File option is selected, and click Browse to find the logo file; then click OK. When a box the size of the object appears beside the pointer, position the logo, and then click on the layout sheet to place the logo.

To accurately align the logo with the north arrow above it, first create a select set containing both items. Then select Draw > Align > Center from the Drawing toolbox.


591

Deg Map Layouts for Printing in the Layout Window Inserting a Symbol Next, insert several layout window symbols (.sym files) to indicate a new recreation area in the map. Before inserting a non-default symbol, you must first set an active symbol with the Set Active Symbol command. Select Draw > Set Active Symbol from the Drawing toolbox.

Click Browse to locate an appropriate symbol.

Next, select the symbol file, and then click Open. On the Set Active Symbol dialog box, type a value greater than 0 in the Scale factor field, and then click OK. To place the symbol that was set, select the Symbol command from the Placement menu on the Drawing toolbox.

592


Deg Map Layouts for Printing in the Layout Window 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.

Placing a Reference Grid The next step in this workflow is to place a reference grid in the map, although this does not involve layout window graphic commands. The Insert Reference Grid command is used to place this grid. First, select the map layout frame in the layout sheet, and then Insert > Reference Grid from the layout window menus. See "Inserting References Grids and Indexes" later in this section for complete information on using this command.


593

Deg Map Layouts for Printing in the Layout Window Select and type the appropriate grid parameters, and then click OK to insert the grid.

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 redline, 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.

594


Deg Map Layouts for Printing in the Layout Window 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.

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.


595

Deg Map Layouts for Printing in the Layout Window Instead of clicking several points to draw a line, you can drag the pointer to draw a line.

Workflows for Placing Map Graphics Using Layout Frames Inserting Layout Frames Insert Layout Frames lets you design a map layout by placing layout frames for the required map and optional marginalia items into the layout sheet. Layout frames are containers that define the location you want in the map layout for the map, legend, north arrow, and scale bar. The layout frames placed for a set of map graphics are automatically associated with one another. Multiple maps and their corresponding marginalia items may be placed in a map layout, with each map having its own associated marginalia. This command lets you create templates and other plot layouts requiring map graphics to be placed in fixed locations on the layout sheet. You would typically use this command when you are starting from scratch and deg 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 deg 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 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

596


Deg Map Layouts for Printing in the Layout Window adjusted during the Insert Graphics into Layout Frames process, and therefore placement of marginalia layout frames should approximate the desired location of the marginalia item. Marginalia items can be scaled after placement, but they cannot be rotated.

To insert layout frames: 1. Select Insert > Layout Frames.

2. Select the appropriate marginalia check boxes. 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.


597

Deg Map Layouts for Printing in the Layout Window 5. Repeat the procedure of Step 4 until you have placed all the marginalia layout frames.

The newly inserted layout frame group is left in the select set.

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

598

Update Condition

What Is Updated

When the source map window name was changed on the command dialog box. The command only updates 5.2 legend frames; those placed before the 5.2 release are not processed.

A default legend control is placed. The upper-left corner of the legend frame is maintained.


Deg Map Layouts for Printing in the Layout Window Update Condition

What Is Updated

A change in the center point or rotation of the map. The command update north arrow frames only if the north arrow azimuth was defined by the map center. If it was -defined, it is not processed.

Only north arrow's angle is updated. The size, position, symbol file etc. will not be changed.

When there is a change in the map scale.

Only the scale of the scale bar is updated. Fill colors, font, caption, units, and so forth are not changed. The center point of the scale bar frame is maintained.

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" section for information on using PickQuick.

To insert graphics into layout frames: 1. that there is an active map window for the insert, that the marginalia properties have been properly defined, and that the layout frames have been placed using the Insert Layout Frames command. 2. Select the appropriate layout frame group or map layout frame in the layout window into which you want to insert the new map graphics.


599

Deg Map Layouts for Printing in the Layout Window 3. Select Insert Graphics into Layout Frames.

4. Select the appropriate map window from the Map window drop-down list. 5. Select the appropriate Geographic extent method, and select and/or type any corresponding required parameters. 6. Select the appropriate Plot scale method; then type the corresponding plot scale value. 7. Select the Static or Dynamic mode. 8. Click OK. OR Click Cancel to exit the command.

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. 9. If the geographic extent method selected is Map Window, Spatial Filter, Geographic Frame, or Projected Frame, there is no need for interaction in the map window. OR If the geographic extent method selected is not one of these four, continue with this step as follows, according to the selected method:  For the Rectangle method, identify the first point of the rectangle in the map window, move the cursor and attached rubber-banding rectangle to the opposing diagonal corner, and then place a second point to define the extent of the rectangle.  For the Polygon method, identify the first point of the polygon in the map window, move the cursor and attached rubber-banding polygon to another location, and then select a second point. Continue selecting points until the polygon has been defined; then double click to end.  For the Existing Shape method, select a shape in the map window to identify the extent that you want, and then identify the appropriate snap point. When 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.

600


Deg Map Layouts for Printing in the Layout Window See “Modifying Maps” in this section for information.

Workflows for Placing Map Graphics without Using Layout Frames Inserting Maps into Layout Sheets Insert Map places a single map into a layout sheet without using previously placed layout frames. With this command, you specify the map definition and then identify the location for placement of the map. The map definition consists of the originating map window, the geographic extent, the plot scale, and the static/dynamic status. The size of the map is calculated automatically based on the geographic extent and plot scale settings. As you drag your cursor across the layout sheet, an empty rectangle appears to identify the physical extent of the map being placed. After the map has been inserted, it remains in the 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 “Modifying Maps” in this section for information.

To insert a map into a layout sheet: (Applicable only if GeoMedia 3D is installed) You will need to toggle your 3D window to 2D in order to plot the contents. 1. that there is an active map window with map graphics for the insert. 2. Select Insert > Map.

3. Select the appropriate map window from the Map window drop-down list. 4. Select the appropriate Geographic extent method, and select and/or type any corresponding required parameters. 5. Type the appropriate plot scale value in the -defined field. 6. Select the Static or Dynamic mode. 7. Click OK. OR Click Close to exit the command.


601

Deg Map Layouts for Printing in the Layout Window 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. OR If the geographic extent method selected is not one of these four, continue with the steps as follows, according to the selected method:  For the Rectangle method, identify the first point of the rectangle in the map window, move the cursor and attached rubber-banding rectangle to the opposing diagonal corner, and then place a second point to define the extent of the rectangle.  For the Polygon method, identify the first point of the polygon in the map window, move the cursor and attached rubber-banding polygon to another location, and then select a second point. Continue selecting points until you have defined the polygon; then double click to end.  For the Paper Size method, move the cursor and attached fixed rectangle in the map window to the desired location; then place a point to identify the origin of the extent.  For the Existing Shape method, select a shape in the map window to identify the extent that you want; then identify the appropriate snap point.

You are prompted to place the origin of the map in the layout window.

When 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.

602


Deg Map Layouts for Printing in the Layout Window 9. Move the cursor and attached rectangle to the location where you want to place the map; then click the left mouse button.

The rectangle defines the maximum extent of the map frame before clipping occurs. After the map has been placed, it is populated with the graphics of the map, and clipping is performed if necessary. The map is left in the select set.

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

Inserting Layout Legends Insert Legend lets you insert a map legend from the map window into a layout sheet by using the legend of the map window referred to in the selected map frame. When you select this command, it displays the Insert Legend dialog box, through which you can insert the layout legend as is or review and customize it. When satisfied with the legend appearance, you place it by a single point. The legend is associated with the map, which allows for automatic updates of the layout legend when changes are made to the map content (such as the style of the legend entries). You can also create multiple legends for a single map frame. Furthermore, you can store the default settings for all the properties of a legend; and each time a legend is placed, the default settings are used regardless of the current map window settings. See the “Working with Map Windows” section for information on legends and using them in the map window.


603

Deg Map Layouts for Printing in the Layout Window 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 multi-select. The top node in the treeview contains the legend title. The next level in the treeview denotes columns with the text Column X (Y entries), where X is the column number, and Y is the number of entries in that column. The third level represents the legend entries and contains the key of the legend entries followed by the text of the feature name. In the case of range headings, the key is blank.

Customizing the Layout Legend The default layout legend properties are taken from the map window legend. You can customize these properties, which include multi-column legends, legend title and properties, prioritization of legend entry order, control of sizes and spacing, selection from multiple styles for legend keys, and control of thematic legend entries.

604


Deg Map Layouts for Printing in the Layout Window The flexibility of this command lets you customize the layout legend through various workflows using dialog boxes, right mouse menus, and drag-and-drop functionality. From the Insert Legend dialog box you can display the resizable Legend Properties dialog box by selecting the Legend name in the treeview and then either clicking Properties or selecting Prosperities from the right mouse menu. This dialog box and those displayed from it let you view and modify layout legend properties.

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

Customize the legend properties on the Legend Properties dialog box.

Rename Legend Title

Type a new legend title.

Add Column

Add an empty column below the legend title.

Distribute Entries Evenly

Distribute all displayed legend entries evenly across available columns.

Remove Column

Remove a column, transferring its contents to the previous column. (Press DELETE as a shortcut.)

Add Entries

Add legend entries on the Add Legend Entries dialog box.

Sort Entries Alphabetically

Perform an ascending alphabetic sort of all legend entries in the selected column.

Sort Entries by Geometry

Perform a geometric sort in the following order: text, point, line, compound, area.

Properties

Customize the entry properties on the corresponding Legend Entry Properties dialog box.

Column

Entries


605

Deg Map Layouts for Printing in the Layout Window Item

Command

Lets You

Rename Entry

Type a new feature name.

Add Entries

Add legend entries on the Add Layout Legend Entries dialog box.

Remove Entry

Remove the selected entry from the treeview, transferring it to the Add Legend Entries dialog box. (Press DELETE as a shortcut.) Selecting Properties on the legend entry right mouse menu displays a Legend Entry Properties dialog box, which lets you change the corresponding entry properties. The available parameters of this dialog box change with the entry type, which can be text, point, line, area, compound point, compound line, compound area, or thematic. The following example is for area:

See the corresponding GeoMedia 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-and-drop include legend columns and legend entries. You can move or copy them within a column or across columns, but you cannot move or copy the legend title node. You can also drag-and-drop nodes onto another node. The selected node is then moved below the destination node it was dropped upon. If you press CTRL when dragging the node, a copy of the selected node is dropped below the destination node. If you drop a column node onto the legend title node, the selected node and all its entries are dropped below the legend title node, becoming the first column in the treeview. If you drop a column node onto another column node, the selected node and all its entries are dropped below the destination column. If you drop a column node onto an entry node, the selected node and all its entries are dropped below the column where the destination entry node resides. As column nodes are shifted within the treeview, the software automatically renumbers the columns to reflect their new positions within the treeview. 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 “Modifying Legends” in this section for more information.

606


Deg Map Layouts for Printing in the Layout Window Looking at Legend Examples The following example shows the minimum column width based on the sum of the longest key width, the longest name width, and the width of the spacing between the two. The minimum column width defines the width of the column before the wrapping of the names occurs, as seen in the example on the left. The example on the right shows the column spacing between the two columns.

The following example shows the columns depicting the name position. The column on the left has the names to the right of the key; the column on the right has the names to the left of the key.


607

Deg Map Layouts for Printing in the Layout Window 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.

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.

608


Deg Map Layouts for Printing in the Layout Window You can also use right mouse menus and the Legend Entry Properties dialog box to customize individual legend entries. 5. To add a legend entry, click Add.

If the legend title node is selected, an empty column is added below this node, becoming the first column in the treeview. If a column or entry node is selected, the Add Legend Entries dialog box is displayed.

6. Select the appropriate Available entries. The names and the order in which the features are listed on the Available Legend Entries dialog box are based on the original map window. Check the Sort alphabetically check box to sort the entries. Thematic headings are sorted such that the thematic heading is considered in the sort, and its corresponding entries remain grouped and indented just below the heading within the sorted list. Thematic entries are not sorted within the group and always maintain their original order.

If a column node was selected, upon returning to the treeview, any entries selected are added below the column node, becoming the first entry(s) within the column. 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.


609


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

See GeoMedia Professional Help for complete information on this dialog box. 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 “Modifying North Arrows” in this section for more information.

To insert a north arrow: 1. Select the map frame in the layout window.

610


Deg Map Layouts for Printing in the Layout Window 2. Select Insert > North Arrow.

3. To change the North arrow file, browse to select a different one.

4. 5. 6. 7. 8.

To see graphics of all the north arrows and com roses, open the NorthArrows.pdf file, which is in the \GeoMedia Professional\Program folder. To review and customize the north arrow properties, click Properties. Set the north arrow properties appropriately on the North Arrow Properties dialog box. To save the defined north arrow as the default, click Save as Default. Click OK to close the North Arrow Properties dialog box. Click OK on the Insert North Arrow dialog box to insert the north arrow.

The dialog is dismissed, and a rectangle that represents the size of the north arrow is placed in dynamics. 9. Click on the layout sheet to define the location for the north arrow.

The lower-left corner of the north arrow is placed where you clicked.

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


611

Deg Map Layouts for Printing in the Layout Window The Style tab lets you define the display characteristics of the scale bar, including the type, color, and size.

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.

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). 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 “Modifying Scale Bars” in this section for more information.

To insert a scale bar: 1. Select the map frame in the layout window.

612


Deg Map Layouts for Printing in the Layout Window 2. Select Insert > Scale Bar.

3. Select the appropriate Type from the drop-down list. 4. To review and customize the scale bar properties, click Properties. 5. Set the scale bar properties appropriately on the three tabs of the Scale Bar Properties dialog box. 6. To save the defined scale bar as the default, click Save as Default. 7. Click OK to close the Scale Bar Properties dialog box. 8. Define the appropriate Unit and Unit label on the Insert Scale Bar dialog box. 9. Click OK to insert the scale bar.

The dialog box is dismissed, and a rectangle that represents the size of the scale bar is placed in dynamics. 10. Click on the layout sheet to define the location for the scale bar.

The lower-left corner of the scale bar is placed where you clicked.

Updating Map Graphics in Layout Sheets Update Map Graphics lets you manually update static maps in the layout window, regenerating the raster snapshot based on the current settings of the originating map window. To use this command, the originating map window must not have been deleted or 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


613

Deg Map Layouts for Printing in the Layout Window 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 of the map definition specified in the Insert Map or Insert Graphics into Layout Frames commands, the following conditions are applied during the update:  The originating map window selection is maintained.  The size, rotation, and origin of the current map frame are maintained regardless of the extraction method used during the original map placement.  The originating plot scale (-defined or Fit to Frame) setting is maintained.  After the map graphics are updated, any associated layout window marginalia are synchronized with the map graphics using the same rules that are followed when dynamic maps are updated automatically.

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

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

614



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

To change from dynamic to static mode: 1. Select the appropriate layout frame group. 2. Select Properties from the right mouse menu.

3. Select the Static mode from the Geometry and Content tab; then click OK.

The map becomes static and cannot be made dynamic again, and the contents of the Mode frame are disabled. The ability to have the height, width, and scale operate independently is also disabled.

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


615

Deg Map Layouts for Printing in the Layout Window file handles on the corners, whereas rectangle types (Map Window, Paper Size, and Rectangle) will have them on the corners and on the sides.

Boundary type

Rectangle type

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

Corner file handle

Side file handle

As you click the cursor and drag the mouse, the map frame is resized accordingly. Map frame scale enlargement has no limits. However, map frame scale reduction is limited such that the corner being reduced can never touch or 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 the file hand of its opposing side, leaving a minimum width/height map frame.

To scale map frames: 1. Select a valid map frame (all geographic extent methods).

All file handles appear as solid black squares. 2. the cursor over any one of the four corner file handles.

The cursor changes from the Select Tool arrow to a line with arrowheads on both ends. 3. While the cursor is changed, click and drag in the direction you want to rescale the map, making the map frame larger or smaller. 4. Release to complete the scaling definition.

The map is scaled accordingly, and a new scale bar is generated to reflect the new map scale. OR 1. Select the appropriate map frame group.

616


Deg Map Layouts for Printing in the Layout Window 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. To enlarge or reduce map frames: 1. Select a valid map frame (Map Window, Rectangle, or Paper Size geographic extent method).

All file handles appear as solid black squares. 2. the cursor over any one of the four side file handles.

The cursor changes from the Select Tool arrow to an open box. 3. While the cursor is changed, click and drag in the direction you want to resize the map, making the map frame larger or smaller. 4. Release to complete the resizing definition.

The map is resized accordingly on the side selected. OR 1. 2. 3. 4. 5.

Select the appropriate map frame group. Select Properties from the right mouse menu. Check the Modify width, height, and map scale independently check box. Type the appropriate height or width. Click OK.

The map is resized accordingly, maintaining the lower-left origin and map scale.


617


Zooming In/Out and Panning Maps within Map Frames Four map frame viewing commands let you zoom and pan on the contents of the map frame without changing the view settings of the layout sheet within the layout window. You can also zoom the contents of the map frame using the Map Properties command. Thus, you can fine-tune the map after it has been placed in the layout sheet. These commands are the following:  Map Zoom In  Map Zoom Out  Map Zoom Previous  Map Pan These command function in the same way other zoom and pan commands do, except that they only apply to the contents of the selected map frame. This means that if you fit the layout sheet within the layout window, you can zoom or pan within the map frame, altering the scale or position of map frame's contents, while the layout sheet remains fit within the layout window. Once a map frame has been selected, you can access these commands from the layout toolbar or from the right mouse menu. You can only zoom and pan on the map frames placed with rectangular (Map Window, Rectangle, and Paper Size) geographic extent methods. The Map Zoom In, the Map Zoom Out and the Map Zoom Previous commands have an effect on the scale bar if one is present when the commands are selected. If you perform a Map Zoom In, Map Zoom Out, or a Map Zoom Previous, the scale bar is re-generated to conform to the new map scale. Pan has two modes, dynamic and fast, which are set through the When panning map windows use 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 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.

To zoom in/out or pan maps within map frames: 1. Select an eligible map frame (Map Window, Rectangle, or Paper Size geographic extent method). 2. Select Map Zoom In, Map Zoom Out, Map Zoom Previous, or Map Pan from the Layout toolbar or right mouse menu. 3. Zoom or pan as necessary. 4. Press the right mouse button to exit the command.

The map is redrawn according to your actions. OR 1. 2. 3. 4. 5.

618

Select the appropriate map frame group. Select Properties from the right mouse menu. Check the Modify width, height, and map scale independently check box. Type the appropriate map scale. Click OK.


Deg Map Layouts for Printing in the Layout Window The map is scaled accordingly within the extent of the map frame, and a new scale bar is generated to reflect the new map scale.

Modifying Map Properties Layout Map Properties lets you review and modify the position, size, scale, rotation, and boundary style of a selected map in the layout window, and, as described earlier, change the static/dynamic mode. You start this command by selecting the map layout frame and then Properties from the right mouse menu. You can review and modify these map properties through the two tabs on the dialog box of this command. The Geometry and Content tab lets you modify information about the map and its position, size, and scale in the map in the layout window.

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 section. 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.


619

Deg Map Layouts for Printing in the Layout Window 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.

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. In this case, the boundary frame is the outline of the state of New Mexico.

620


Deg Map Layouts for Printing in the Layout Window To this placement, 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.

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


621

Deg Map Layouts for Printing in the Layout Window provide a quick and easy method for orienting North based on paper space independent of the workspace's geographic or projected space, which generally leads to improved layout and design.  Map frames must be in dynamic mode; you cannot rotate static maps.  Rotation angles are in degrees.  Rotation point is the center of the map frame. Rotation is measured counter clockwise from the x-axis. Upon clicking OK, the map is positioned at the correct coordinates on the sheet, the map size and scale are set appropriately, the boundary is displayed in the correct color, width, and style (if the boundary is to be displayed), the map is rotated, and the map and boundary are placed on the correct layer.

Modifying Legends The Layout Legend Properties command lets you view and modify information about a legend in the layout window, including the position, number of columns, title, font, key styles, layer, and boundary style of the legend frame. You start this command by selecting the legend frame and then selecting Properties from the right mouse menu. You can review and modify these legend properties through the two tabs on the dialog box of this command. The Legend tab lets you control what is displayed on the legend and how it is presented, such as the title, number of columns, fonts, key styles, and so forth. This tab functions the same as the Insert Legend dialog box. You can change these properties through the Legend Properties dialog box; the Legend Entry Properties dialog boxes; the right mouse menus of the legend title, columns, and entries in the treeview; and the drag-and-drop functionality as previously described in the ―customizing the legend‖ discussion. See “Inserting Layout Legends” earlier in this section for complete information on using the Legend tab.

622


Deg Map Layouts for Printing in the Layout Window The General tab lets you change the layer on which the legend is displayed and controls the display of the boundary around the legend, including color, width, and style. This tab also lets you position the lower-left corner of the layout frame geometry in the layout window by typing the X and Y coordinates in paper units.

Upon clicking OK, the updated legend is positioned at the specified origin, the legend size is calculated appropriately based upon the parameters entered, the boundary is displayed with the correct color, width, and style (if the boundary is to be displayed), and the legend and boundary are placed on the correct layer.

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

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


623

Deg Map Layouts for Printing in the Layout Window See the “Changing Display Characteristics of Map Objects” section in the "Working with Map Windows" section and GeoMedia Professional Help for information on using this dialog box.

Modifying North Arrows You can change the properties of the north arrow through the two tabs of the North Arrow Properties dialog box. Furthermore, you can store the default settings for all the properties of a north arrow. You start this command by selecting the north arrow frame and then Properties from the right mouse menu. The Style tab lets you change the file used, its size, and azimuth of the north arrow (drawn according to the north azimuth of the center of the associated map or the -defined direction in degrees).

See GeoMedia Professional Help for complete information on this dialog box. The unit for the Size is defined by the Style field on the Layout tab (Tools > Options).

624


Deg Map Layouts for Printing in the Layout Window 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.

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. The unit for the Width is defined by the Style field on the Layout tab (Tools > Options). The unit for the X and Y values is defined by the Distance field on the Layout tab.

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


625


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.

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.

626


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

See GeoMedia Professional Help for complete information on using this dialog box.

Inserting Cartographic Grids The Insert Cartographic Grid command lets you create and insert cartographic grids that can be comprised of any combination of a neatline, grid lines, ticks and crosses, their corresponding labels, and a border in the layout window. This command also lets you specify unit settings for Geographic, Projection, and paper parameters, but it does not map graphics from Geocentric coordinate systems. To use this command, you must first have placed map graphics in the active layout sheet with the Insert Map and Insert Graphics into Layout Frames commands, that is, you must have a populated map layout frame in the select set.


627

Deg Map Layouts for Printing in the Layout Window 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. 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 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.

628



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” section. 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.

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.


629


Corner Label Placement Corner labels are placed on the corners of the neatline, and show the coordinate values at the corners. You can place (or not place) corner labels by selecting or deselecting the check box. With this option selected, you can define the corner label orientation, font, and advanced label formatting. Corner labels are placed using a center justification so the label itself is centered on each corner. To minimize overprinting of labels, whenever an edge label overlaps a corner label, the edge label is not placed. For corner label orientation, the available label placement options are as follows: Parallel / Perpendicular (the default)-Parallel to the neatline on the top and bottom edges and perpendicular to the neatline on the left and right edges. All labels read horizontally. Parallel-Parallel to the neatline on all edges. Labels on the left read bottom to top, labels on the right read top to bottom, and labels on the top and bottom read left to right. Perpendicular-Perpendicular to the neatline on all edges. Labels on the left and right read left to right, and labels on the top and bottom read from bottom to top. You can define the font through the standard Microsoft Font dialog box to set the font, font style, font size, format, and script. You can also define advanced label formatting options through the Advanced Neatline Label Options dialog box. The style, format, and placement options on this dialog box vary for Geographic labels and for Projection labels. The following example is for Geographic labels: See GeoMedia Professional Help for information on using this dialog box.

630



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.

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” section. 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. 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


631

Deg Map Layouts for Printing in the Layout Window Projection is 0, and the default value for Geographic is 00:00:00 d:m:s. When 0 is defined for the skip interval, no grid line skipping occurs. You can also define intervals in paper units for the Projection grid type. When you choose this option, the grid and skip interval units and precision settings used on the dialog box are obtained from the current settings defined for the Distance unit on the Layout tab of the Options dialog box. During placement, the paper interval will be converted automatically to the appropriate ground interval based on the current map scale.

Grid Placement You can place (or not place) a grid by selecting or deselecting the check box. With this option selected, you can define the grid style (color, weight, and type). The default is dependent on the active setting for the neatline type defined on the Neatline tab. When the neatline type is Projection, the default is to place a grid. When the neatline type is Geographic, the default is to not place a grid. The default style setting matches the active settings for these items in the layout window. Grid lines are rotated appropriately on rotated map graphics.

Edge Label Placement You can place (or not place) edge labels by selecting or deselecting the check box. With this option selected, you can define the edge label orientation, font, and advanced label formatting options. The edge label placement default is dependent upon the active setting for the neatline type defined on the Neatline tab. When the neatline type is Projection, the default is to place edge labels. When the neatline type is Geographic, the default is to not place edge labels. Corner labels are placed using a center justification so the label itself is centered on each corner. To minimize overprinting of labels, whenever an edge label overlaps a corner label, the edge label is not placed. For edge label orientation, the available options for label placement are as follows: Parallel / Perpendicular (the default)-Parallel to the neatline on the top and bottom edges and perpendicular to the neatline on the left and right edges. All labels read horizontally. Parallel-Parallel to the neatline on all edges. Labels on the left read bottom to top, labels on the right read top to bottom, and labels on the top and bottom read left to right. Perpendicular-Perpendicular to the neatline on all edges. Labels on the left and right read left to right, and labels on the top and bottom read from bottom to top. You can define the font through the standard Microsoft Font dialog 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.

632



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

Tick and Cross Parameters The tick and cross parameters consist of the tick and cross coordinate system, tick and cross type, tick and cross intervals and of the skip intervals. You can define these parameters in Geographic or Projection coordinate space, with the default value matching the current GeoWorkspace coordinate system setting. 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” section. 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.


633

Deg Map Layouts for Printing in the Layout Window 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 dependent on the active setting for the neatline type defined on the Neatline tab. When the neatline type is Projection, the default is to not place ticks. When the neatline type is Geographic, the default is to place ticks. For the style, you can define the line color, weight, and type; the default setting matches the active settings for these items in the layout window. For the length, the unit and precision is based on the current settings defined for the Distance unit on the Layout tab on the Options dialog box. For the position, you can set the tick placement to be either inside the neatline (the default) or outside the neatline.

Cross Placement You can place (or not place) crosses by selecting or deselecting the check box. With this option selected, you can define the cross style and length. The default is dependent on the active setting for the neatline type defined on the Neatline tab. When the neatline type is Projection, the default is to not place crosses. When the neatline type is Geographic, the default is to place crosses. For the style, you can define the line color, weight, and type; the default setting matches the active settings for these items in the layout window. For the length, the unit and precision is based on the current units and precision settings defined for the Length readout on the Layout tab on the Options dialog box.

Edge Label Placement You can place (or not place) edge labels for ticks and cross by selecting or deselecting the check box. With this option, you can define the edge label orientation, font, and advanced formatting options. The edge label placement default is dependent on the active setting for the neatline type defined on the Neatline tab. When the neatline type is Projection, the default is to not place edge labels. When the neatline type is Geographic, the default is to place edge labels. For edge label orientation, the available options for label placement are as follows: Parallel / Perpendicular (the default)-Parallel to the neatline on the top and bottom edges and perpendicular to the neatline on the left and right edges. All labels read horizontally. Parallel-Parallel to the neatline on all edges. Labels on the left read bottom to top, labels on the right read top to bottom, and labels on the top and bottom read left to right.

634


Deg Map Layouts for Printing in the Layout Window Perpendicular-Perpendicular to the neatline on all edges. Labels on the left and right read left to right, and labels on the top and bottom read from bottom to top. You can define the font through the standard Microsoft Font dialog to set the font, font style, font size, format, and script. 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 cartographic grids: 1. 2. 3. 4.

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


635

Deg Map Layouts for Printing 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.

To define ticks and crosses: 1. Select the Ticks and Crosses tab. 2. Optional: Click Ticks and Crosses Coordinate System to define the ticks and crosses in a coordinate space other than the current GeoWorkspace coordinate system setting. 3. Select the Tick and crosses type as Geographic or Projection to define the ticks and crosses intervals. 4. Optional: Type changes in the Tick and cross intervals fields. 5. Optional: Type changes in the Skip intervals fields. 6. Optional: Check the Define intervals in paper units check box; then specify the Tick and cross intervals and Skip intervals in paper units. 7. Optional: Check the Place ticks check box; then specify the grid Style, Length, and Position settings. 8. Optional: Check the Place crosses check box; then specify the grid Style and Length settings. 9. Optional: Check the Place edge label check box; then specify the Orientation from the drop-down list. 10. Optional: Click Font to change the font values.

636


Deg Map Layouts for Printing in the Layout Window 11. Optional: Click Advanced to set the advanced label formatting options.

To define a border: 1. Select the Border tab. 2. Check the Place border around neatline check box. 3. Type the appropriate values settings for the Top margin, Bottom margin, Left margin, and Right margin fields. 4. Specify the Style settings.

To save a cartographic grid definition: 1. 2. 3. 4. 5.

Insert the appropriate map into the layout sheet. Select the map frame, and then select Insert > Cartographic Grid. Define the appropriate settings on the Neatline, Grid, Ticks and Crosses, and Border tabs. Click Save As. Browse for the appropriate folder, type a name for the Cartographic Grid Definition File (*.xml), and then click Save.

When saving a cartographic grid definition file, you are prompted to save the grid definition file (.csf) file if you have changed any of the coordinate systems. This action is required to ensure a valid grid definition file. If you cancel out of the Save Cartographic Grid Definition dialog box, it invalidates the grid definition file. This means that when you attempt to reuse the grid definition file, there will be no reference to the changed coordinate system. This is only required if you have changed one of the coordinate systems for the grid generation.

To load a saved cartographic grid definition: 1. 2. 3. 4.

Insert the appropriate map into the layout sheet. Select the map frame, and then select Insert > Cartographic Grid. Click Load. Browse for a Cartographic Grid Definition File (*.xml), and then click Open.

To modify cartographic grids: 1. 2. 3. 4.

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


637


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

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

638


Deg Map Layouts for Printing in the Layout Window To insert a reference grid: 1. 2. 3. 4.

Make a layout window active. Select an active sheet that contains a map frame. Select the map frame. Select Insert > Reference Grid.

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

The grid and labels are placed in the active layer, and the grid is left in the select set.

Inserting a Reference Index After you have placed a reference grid on the active layer of the layout window with the Insert Reference Grid command, the Insert Reference Index command lets you generate a corresponding reference index. To use this command, you must have generated a reference grid on a valid static or dynamic map in the select set. You can run this command multiple times for the same reference grid. This command lets you specify which point features and graphic text features to index. The available features to index are compiled from a list of features and queries that are present in the originating map window of the map being processed. For text features, the indexing is based on the graphic text string. In this scenario, the contents of the index correspond with the labels in the map. For point features, the indexing is based on an attribute of the point feature. In this


639

Deg Map Layouts for Printing in the Layout Window scenario, the contents of the index corresponds with text attributes of point data. So the map would contain school symbols, and the index would contain school names, for example. You can define a title to be placed at the top center of the index. To improve legibility and organization of the index, you can insert subheadings (123…; A, B, C …) inserted at the appropriate places in the index. If no items fall under a subheading, that heading is not used. The subheadings for numbers come first, followed by characters sorted alphabetically. Note that these additional subheadings increase the number of items in the index, which is calculated once the feature to index is selected, and can therefore affect the column and row calculation. Additionally, you can define font characteristics for the title, subheadings, and feature text. In placing columns or rows, you specify the number of columns and then the number of rows is calculated automatically (values are calculated using the number of features and the presence of subheadings). You also define the column width and the spacing between columns. The inter-column order is feature/grid. The alignment of the two parts of the column is seen in the following example:

The following example shows an index where duplicates were found:

This command lets you adjust the prefixes in two ways. You can ignore them when sorting, which, for example, places Rue de Orleans with the Os rather than the Rs. You also can specify a list of strings to be ignored or removed from the index, which, for example, places Rue de Orleans as Orleans. Note that choosing to ignore or remove prefixes when sorting can affect the number of items in the index. You can place an index by one point (using font and spacing information) or by two points (overriding font and spacing to fit the two points, forming a rectangle), or you can output the index to a text file, which may override some parameters.

To insert a reference index: 1. Make a layout window active. 2. Select an active sheet that contains at a dynamic map frame.

640


Deg Map Layouts for Printing in the Layout Window 3. 4. 5. 6.

Select a map frame. Create and insert a grid with the Insert Reference Grid command. Select the grid just placed. Select Insert > Reference Index.

7. 8. 9. 10. 11. 12. 13. 14.

Select the Features to index from the drop-down list. Select a corresponding Attribute from the drop-down list. Select the Title check box to display a title; then type in the title. Select the Alphabetic sub-heading check box to display the sub-headings. Specify the font of all text items - Title, Alphabetic sub-heading, and Feature text. Specify the Prefix options, typing any prefixes to be ignored and/or removed. Specify the Index format parameters. Select one of the following Index placement options:  Place by point (by a single point) - Continue with Step 15.  Place by rectangle (by two points) - Go to Step 17.  Output to file - Go to Step 20. 15. Click OK. 16. When prompted to Click to place the upper-left corner of the index, click the mouse to place the index.

A box the size of the index is displayed in dynamics. After the mouse click, the index is placed in the active layer at that location. 17. Click OK. 18. When prompted to Click to place the upper-left corner of the index, click the mouse to indicate the upper-left corner of the index.

A dynamic rectangle is displayed as the mouse is moved after the click. 19. When prompted to Click to place the lower-right corner of the index, click the mouse to indicate the upper-right corner of the index.

After the second click, the index is fit to that rectangle. 20. On the standard Open dialog box, select where the text file is to be placed; then click OK.

After the dialog box is dismissed, the file is written and the command is ended.


641


Inserting a Data Table The Insert Data Table command lets you display selected portions of a data window in the layout window in a customized style. To use this command, you must have first defined the data window area to be inserted. You can only place static data with this command.

You can select the data window portion you want to display by a single cell, a contiguous rectangle of cells, one or more rows (not necessarily contiguous), or one or more columns (not necessarily contiguous). You can customize the appearance of the data window insert by adjusting the title, column headers and widths, and cells. You have the option to display the title of the data window and the column headers. You can also change the title and its font and the font of the headers and cells through the standard Font dialog box. Additionally, you determine the column width by one of the following methods:  Based on data window (default)-Each column width is based on that column's width in the data window.  Based on longest text-Each column width is based on the longest string in that column.  -defined-All columns have the same -defined width. With the first and third options, column width might be too short, in which case the string is truncated. The width units are based on the distance units set on the Layout tab of the Tools > Options dialog box. You can further customize the data window display by using the Properties command to: 

Reorder columns



Hide/Show columns



Change column widths



Change data values



Re-sort data

To insert a data table: 1. 2. 3. 4. 5.

642

Open the appropriate data window. Format the data as you want it displayed. Highlight the data to be displayed. Activate the layout window Select Insert > Data Table.



. 6. Select the appropriate Data window from the drop-down list. 7. Check the Title check box to display a title; then optionally change the title text and font. 8. Check the Column headings check box to display headings; then optionally change the heading font. 9. Optional: Click Cells > Font to change the cell font. 10. Select appropriate Column widths option. If you select -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. A right mouse click lets you return (backup) to the dialog box without placing the data window grid.


643


644


SECTION 20

Printing in GeoMedia Professional Printing Overview Printing in GeoMedia Professional can be performed in any of its three windows: map window, data window, or layout window. Due to the difference in the types of data within each window and the difference in their respective environments, each window has a unique set of paper-related parameters that must be defined before printing. The map window and data window contain data on a sort of virtual canvas. The data of the map window are geographic, typically stored in ground units without any reference to a paper layout. Similarly, the data of the data window are tabular, without any reference to a paper layout. In contrast, the sheets in the layout window are specifically referenced to a paper layout. Although each window has its own subtleties due to its data type and environment, before printing, the paper layout parameters must be defined through the Page Setup of each window.

Defining the Map Window Page Setup The map window Page Setup contains the parameters necessary to transform the virtual canvas of the map window into paper space suitable for printing or plotting. The parameters are presented on the Map Window Page Setup dialog box on its four tabs: Size and Scale, Margins, Units, and Printer. Size and Scale—This tab contains the settings for defining the Paper Size, the paper Orientation, and the Print Scale. Once these parameters have been set, the results of these settings are displayed in the Print Range and Output sections.  Paper Size > Size—This drop-down list provides a list of all of the paper sizes ed by the printer specified on the Printer tab. Width and Height of the selected paper size are expressed in the units defined for paper units on the Units tab.  Orientation—Options include Portrait and Landscape.  Print Scale—This can be defined by selecting a predefined scale, by defining a custom scale, or by defining the output to fit a specific number of pages wide by pages tall. Print scale represents the relationship between paper units and ground units. This relationship can be expressed in the following ways:  Scale—Defined as a fractional equivalent, such as 1/25,000, commonly expressed as 1:25,000. This method states that one unit on the paper is equivalent to 25,000 units on the ground. The units are irrelevant as long as they are the same; one centimeter on the paper is equivalent to 25,000 centimeters on the ground, or one inch on the paper is equivalent to 25,000 inches on the ground.  Custom—Defined as a verbal description. This method states that some unit on the paper is equivalent to some unit on the ground, such as ―one inch equals one mile‖, or ―one inch to the mile.‖ The units on either side are typically different. ―One inch equals one mile‖ is simply another way of expressing 1:63,360 – that is, there are 63,360 inches in a mile. The left field defines paper units, and the right field defines ground units, as specified on the Units tab.  Fit to—Defined by stating that the geographic extent of the map window will be fit into a particular page definition. This method automatically calculates the fractional equivalent


645

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

646


Printing in GeoMedia Professional To define the map window page setup: 1. Select File > Page Setup.

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

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

To print a map window: 1. Configure the map, legend, north arrow, and scale bar so that they look the way you want them to print.


647

Printing in GeoMedia Professional 2. Select File > Print.

3. 4. 5. 6.

Select a printer from the Name drop-down list. Specify the Number of copies to print. If you want Draft Quality and your printer s that option, check that option. Click OK.

Printing to a File Printing to a file is similar to printing a hard copy, except it generates a printer file instead of routing the document directly to a printer. This provides a method for generating soft-copy files that can be stored on disk and printed or plotted as necessary without having to be in the application to resubmit the plots. The document is by default saved with printer formatting to a file with the .prn (printer driver) extension. The format of this reserved name file is device dependent, and it is derived from the printer driver of the printer selected in the Printer > Name field on the Print dialog box.

To print to a file: 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. To submit a .prn file, type at a DOS prompt:

648


Printing in GeoMedia Professional copy filename path_to_queue where filename = the name of the *.prn file, and where path_to_queue = the name of the printer and queue (for example, \\b17bpn\hp_101).

Defining the Data Window Page Setup The data window Page Setup contains the parameters necessary to transform the virtual canvas of the data window into paper space suitable for printing. The parameters are presented on the Data Window Page Setup dialog box on its four tabs: Size and Scale, Margins, Units, and Printer. Size and Scale—This tab contains the settings for defining the Paper Size, the paper Orientation, and the Print Scale. Once these parameters have been set, the results of these settings are displayed in the Print Range and Output sections.  Paper Size > Size—This drop-down list provides a list of all of the paper sizes ed by the printer specified on the Printer tab. Width and Height of the selected paper size are expressed in the units defined for paper units on the Units tab.  Orientation—Options include Portrait and Landscape.  Print Scale—This 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 Range—Reports the Width and Height of the tabular extent of the print in paper units, as specified on the Units tab.  Output—Reports assorted information pertaining to the paper output: Width, Height, Pages wide, and Pages tall. The width and height are reported in the units specified on the Units tab. Margins—This tab contains the settings for the position of the plot relative to the paper upon which it is printed. Options include specifying a fixed distance between the edge of the paper and the data on the Left, Right, Top, and Bottom. Margin settings will impact the overall size of the print, especially when the print requires multiple pages, as displayed in Pages wide and Pages tall in the Output section on the Size and Scale tab. Units—This tab contains the settings for defining the Paper Units that are expressed throughout the Data Window Page Setup dialog box. The Paper Unit selected is used when displaying the Width and Height of the selected Paper Size, the Print Range, and the Width and Height of the Output on the Size and Scale tab. It is also used for defining margins on the Margins tab. Printer—This tab contains a drop-down list of all of the available printing devices resident on the machine, including local and network printers. Once a printer has been selected, information regarding its status, the type of device, and where it is located is displayed. Each printer in the list has a set of default parameters that can be modified for the printing session by clicking Properties. The available Paper Sizes listed in the Size drop-down list on the Size and Scale tab are determined by the paper sizes ed by the printer selected on this tab.


649

Printing in GeoMedia Professional To define the data window page setup: 1. Select File > Page Setup.

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

Printing a Data Window You can print what is displayed in the data window, all rows or a range of rows.

To print a data window: 1. Configure the data window so that it looks the way you want it to print, hiding columns you do not want to print and showing those you do. 2. Select File > Print.

3. 4. 5. 6. 7.

650

Select a printer from the Name drop-down list. Identify the Print Range of the rows you want to print. Specify the Number of copies to print. If you want Draft Quality and your printer s that option, check that option. Click OK.


Printing in GeoMedia Professional Printing to file provides a method for generating soft-copy files that can be stored on disk and printed as necessary without having to be in the application to resubmit the prints. See the “Printing to a File” section for complete information.

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


651

Printing in GeoMedia Professional then selecting Save as Default causes the layout window to use the currently saved parameters when inserting the new sheets. The Save as Default parameters are used for the current working session, and they are persisted if you save the GeoWorkspace. Saving the GeoWorkspace saves the new parameters as the default page setup description.

To define the layout window page setup: 1. Select Window > Layout Window, and open the appropriate layout sheet. 2. Select File > Page Setup.

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. If this check box is unchecked, the sheet will not be displayed when you select OK. 5. Optional: Edit the description in the Description field. 6. Optional: Select an appropriate background sheet from the Background drop-down list.

The background sheet is displayed under the layout sheet, and its features cannot be selected unless the background sheet is active. OR Select none, which is displayed as a blank Background field. 7. Select the appropriate Paper Size from the drop-down list. OR Select Custom from the Size drop-down list, type in the appropriate Width and Height values, and then select the appropriate Units from the drop-down list. 8. Select the appropriate layout Orientation option. 9. Optional: Click Save as Default.

The current settings are saved as the default plot layout page setup. 10. Click OK.

652


Printing in GeoMedia Professional

Printing Layout Sheets from the Layout Window Printing layout sheets follows standard Windows printing procedures and interfaces; however, printing layout sheets is somewhat different from printing map windows and data windows. Print Layout Window options include defining the printer, print range, number of copies, print multiple sheets per page, and additional properties and settings. For the print range, you can choose the active layout sheet, all visible layout sheets, or selected visible layout sheets by using the logical numbers identified on the Layout Window Properties dialog box. For multiple sheets per page, you can perform plot nesting; choosing the finished paper size, where the selected sheets will be grouped together on a single plot. The parameters available in the Properties dialog box are determined by the printer driver used when creating the printer. Once you have chosen the appropriate options and parameters, you can print the layout sheet to a printer, a plotter, or a file. The Settings options let you edit scale and origin information, including margins and print magnification. The Print magnification pertains to all graphics on the layout sheets included in the print and is defined in of percentage. The default is 100% for full-size, 1:1 plots. You can make reductions and enlargements by changing the print magnification. A value of 50% produces a half-size drawing, and a value of 200% produces a double-size drawing. The Origin offset lets you specify additional margins and displays a preview of how the layout sheet fits on the paper form selected. Print magnifications have no cartographic intelligence. They are equivalent to enlargements or reductions performed by a photocopy machine. When print magnification is other than 100%, the scale bar is invalidated if it includes a fractional equivalent or ratio (for example, 1:24,000) or a description (for example, 1 inch = 1 mile). This situation can produce erroneous scale information in which the text no longer matches the scale bar. Consequently, if you use a print magnification other than 100%, the scale bars should omit any reference to fractional equivalents or descriptions. You can print a subset of a layout sheet by selecting the Print area option on the Print Layout Window dialog box. If you select this option, you are prompted to identify a rectangular area on the active layout sheet, and then the Print Area dialog box opens for the input of relevant parameters. You can combine multiple sheets into a single plot by selecting the Print multiple sheets per page on check box on the Print Layout Window dialog box, and then defining the finished paper size. This option is only enabled if more than one sheet is selected for printing, that is, if you select all-sheets mode, specify more than one sheet (for example, 1-4,5,10), or set the number of copies to more than one. 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:


653

Printing in GeoMedia Professional 

The Best setting processes the images at full resolution (every pixel up to the limit of the dpi of the device is sent to the printer). The Draft setting effectively reduces the resolution of the printer by a factor of 5 (but only for the images!).  The intermediate settings from Best to Draft cause GeoMedia Professional to generate sufficient raster resolution to match the printer resolution reduced by 1/2, 1/3, and 1/4, respectively (again, this only applies to any images in the plot). If the layout contains transparent or translucent features, or images with contrast and brightness adjustments, or bitmap-patterned area features, the Print Quality slider behaves quite differently. In these cases, GeoMedia Professional pre-processes the map graphics, generating a raster bitmap at a specific spatial and spectral resolution. This bitmap is then submitted to the device, along with the rest of the sheet content. At the Best setting, you create a 24-bit color bitmap of the map graphic at the full resolution reported by the plotting device. This will typically be a very large raster, and it may cause problems for some plotting configurations. The default (center) setting creates a 16-bit color bitmap at resolution equal to 50% of the plotter‘s reported value. The Draft setting reduces the target plot resolution to one-tenth the dpi reported by the device and creates the bitmap with only 8-bit color (256 total colors). Color Depth

Resolution % of Printer Default

Slider Setting

24-bit

100%

Best

16-bit

100%

16-bit

50%

8-bit

50%

(default)

Draft 8-bit 10% Both the Settings dialog box and the Print Area dialog box contain a color-coded preview area. This useful feature lets you easily view the relationship between the document print range, the printer paper size, and the actual printing area on the final plot before you actually print it. It also provides a preview of the graphics on the sheet for visual assistance.

To print a layout sheet: 1. Select the appropriate layout window as the active window.

654


Printing in GeoMedia Professional 2. Select File > Print.

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. 4. Optional: Click Properties to review and/or change the printer-specific properties. 5. Identify the Print Range that you want to print. Selecting the Print area option disables the Print multiple sheets per page on check box and the Settings button. 6. Specify the Number of copies to print. 7. Optional: Set the Print Quality slider appropriately. 8. Optional: Check the Print multiple sheets per page on check box; then select the Size from the drop-down list. This option is only available if more than one sheet has been selected for printing. 9. Optional: Check the Pure Black And White check box. 10. Optional: Click Settings to edit scale and origin information.


655

Printing in GeoMedia Professional 11. Type the appropriate Print magnification. 12. Select the Center check box to position the center of the print area to the center of the printer paper. Otherwise, the paper is positioned according to the X,Y settings, whose default is 0,0 (the upper left being the default origin). Center is disabled if you check the Print multiple sheets per page on check box. OR Type the appropriate X value to set a shift in the X direction from the origin and/or the Y value to set a shift in the Y direction from the origin. 13. Click OK.

The Settings dialog box is dismissed, and the Print Layout Window dialog box reappears. 14. After you have set all the parameters on the Print Layout Window dialog box, click OK.

If you are printing to a printer or plotter, the selected layout sheet or sheets are printed, and the command is exited. OR

If you selected Print area as the Print Range in Step 5, a set of crosshairs is displayed, and you are prompted to identify the area to print. 15. Identify the print area with a rectangle.

16. Type the appropriate Print magnification. 17. Select the Center check box to position the center of the print area to the center of the printer paper. Otherwise, the paper is positioned according to the X,Y settings, whose default is 0,0 (the upper left is the default origin). OR Type the appropriates X value to set a shift in the X direction from the origin and/or the Y value to set a shift in the Y direction from the origin. 18. Optional: Click XY Range to clear the previously defined print area; then define a new area to print by placing two data points. 19. Click OK.

If you are printing to a printer or plotter, the selected layout sheet or sheets are printed, and the command is exited. Printing to file provides a method for generating soft-copy files that can be stored on disk and printed or plotted as necessary without having to be in the application to resubmit the plots. See the “Printing to a File” section for complete information.

656



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 Professional” sections 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 s a graphical interface (Start > All Programs > GeoMedia Professional > Utilities > Batch Plotting) and a command line interface. See the Batch Plotting utility’s online Help for complete information.

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


657

Printing in GeoMedia Professional This type of problem that exists today between Windows printing and PostScript printer drivers is not uncommon in the computer business. Such problems are typically resolved over time by fixes and new releases of software, or by the evolution of language specifications. If not, you should not give up on using PostScript for printing from GeoMedia. You should try again periodically to see if some upgrade on your system may have solved the problem.

Outputting PDF from GeoMedia Professional GeoMedia Professional does not provide native authoring functionality to write PDF files. As with PostScript output, PDF output is generated from GeoMedia Professional through the Windows ® PRINT interface. In the case of PDF, Adobe (the originator of the PDF language) makes a ® business of selling a PDF driver for Windows systems. This PDF driver is known as the Acrobat Distiller and is delivered with the full version of Adobe Acrobat. Many computer s have installed the Acrobat Reader, typically at no cost through Internet or delivered with some PDF-format documents. But this does not include the authoring capability, only the ability to view existing PDF files. There are also several third-party PDF drivers available as alternatives to the Adobe product. But for the examples in this appendix, we will use the Adobe Acrobat product. When Adobe Acrobat is installed on a computer, a new printer driver is automatically installed on the computer. The printer is named Acrobat Distiller on the Windows Printers dialog box. When you print to the Acrobat Distiller driver from GeoMedia 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.

Setting Acrobat Distiller Parameters There are several parameters or properties that may be set to control PDF output from the Acrobat Distiller. The recommended choices depend on the ultimate purpose of the PDF document. These properties are set by starting Acrobat Distiller from the Windows Start menu. Acrobat is delivered with four sets of parameters pre-determined for compatibility with common applications. If you plan to publish a map using an offset printing press, the recommended Default Setting is Press Quality.

658


Printing in 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.


659


660


SECTION 21

Exporting Data to Other Systems GeoMedia Professional provides commands for exporting data to other GIS or CAD systems. You can export the following:  Feature data into shapefile (.shp) format.  Feature data into MapInfo Interchange Format (.mif /.mid).  Feature geometry and attribute linkage into MicroStation design file (.dgn) format.  Feature geometry and attribute data into AutoCAD .dwg or binary .dxf format or ASCII .dxf format.  Feature geometry and attribute data into GML format.  

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 a SQL Server database.

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 s 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 them. You can create a new shapefile or append to an existing one. When appending to an existing shapefile, the feature-class definition of the features being exported and the shapefile to which you are exporting data must be identical because a shapefile can contain only a single feature class. By default, this command appends to any existing shapefile(s) present in the output subfolder. If any error is found during appending, it is reported in the log file. When exporting a feature class with Oriented Point geometries, the orientation information is preserved by adding a numeric field to the output shapefile definition. This extra field is not added only when DWORD value AVExportPreserveRotation under the registry key ―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


661

Exporting Data to Other Systems 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” section. The warehouse configuration file (.ini) is also written in the output folder with ―COORDINATE SYSTEM‖, ―TEXT ENCODING‖, ―SERVE NUMERIC WIDTH AS INTEGER‖, ―SERVE NUMERIC WIDTH AS LONG‖, and ―SERVE NUMERIC WIDTH AS SINGLE‖ keywords as per the export settings. ―SERVE NUMERIC WIDTH AS INTEGER‖, ―SERVE NUMERIC WIDTH AS LONG‖, and ―SERVE NUMERIC WIDTH AS SINGLE‖ keywords are included based on the presence of DWORD values ―AVExportIntegerWidth‖, ―AVExportLongWidth‖, and ―AVExportSingleWidth‖ under the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Intergraph\Applications\, respectively. The name of the file is the same as the output folder name. When export is performed to a root folder, the name of exported file is Export.ini. You also have the option to export 3-D coordinate information or not; the default is to export 2-D coordinate information. Additionally, you can specify whether coded PickList values need to be exported as descriptions if PickList fields are present in the selected features. The default is to not export them. For each feature class/query, the following three output files are created during export:  / .shp  / .shx  / .dbf 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 formation is appended.

To export data to shapefile format: 1. Connect to the existing warehouse from which you want to export data. 2. Select Warehouse > Export to > Shapefile.

662


Exporting Data to Other Systems

3. Select the appropriate items from the Features to export treeview. Holding the cursor over an entry displays a tooltip describing the geometry type.

The default path of the file to contain the exported data is taken from the \Warehouses folder and displayed in the Export folder field. 4. Optional: Change the default path of the warehouse folder in the Export folder field. 5. Select the appropriate Output geometry type for the highlighted features option(s). These options are enabled only when a treeview entry is highlighted. For feature classes/queries of the compound geometry type, all the options in the frame are enabled (with Area as the default), and for other feature classes/queries, only the corresponding geometry type is enabled. 6. Check the appropriate Export options check box(es). 7. Select the appropriate format from the Text encoding drop-down list. 8. Click Apply to begin exporting.

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.


663

Exporting Data to Other Systems After completing the export process without any warnings or errors, the Export complete message is displayed. 9. Continue the export process until complete; then click Close to dismiss the Export to Shapefile dialog box.

Exporting to MapInfo Interchange Format Use the Export to MapInfo Interchange Format to export feature data (geometry and attributes) from any read-write or read-only warehouse connection into MapInfo Interchange Format files (.mif and .mid) that are compatible with MapInfo Professional 4.5. You can create a new MapInfo file, but you cannot append to or edit an existing one. The selected feature class will be written to the .mif (graphics) and .mid (database) files in the specified folder. Simple arcs are exported as arcs. However, arc geometry is stroked when present in compound features and exported. The following list describes characteristics of MapInfo that impact the exported files:  Geometry data is exported using the Geographic coordinates (base storage type Geographic in 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 must enter the correct coordinate system information in the .mif file before importing it into MapInfo. Export to MapInfo Interchange Format in such a case creates a GeoMedia .csf file containing the coordinate system information of the exported data with the same root name as the output .mif file, which you can use as a reference when creating the coordinate system entry in the .mif file. See MapInfo documentation for information on the .mif format and how to populate the coordinate system information.  MapInfo does not point-collection geometries (a single feature consisting of multiple-point geometry), so each point is exported as an individual feature. The attributes of the entire collection will be replicated for each exported point of the collection.  The MapInfo file format does not gdbmemo field types. Export to MapInfo Interchange Format exports these fields as normal character type, and they are truncated to 255 characters.  Hypertext is treated as normal character type and is truncated to 255 characters.  Export To MapInfo Interchange Format generates MIF and MID files that are compatible with MapInfo Professional 4.0. The following table defines the MapInfo geometry generated from each of the GeoMedia Professional geometry types:

664

GeoMedia Professional Geometry Type

MapInfo Geometry

Description

Point

Point

Point

Line

Line

Line

Arc

Arc

Arc


Exporting Data to Other Systems GeoMedia Professional Geometry Type

MapInfo Geometry

Description

Point

Point

Point

Polyline

Polyline

Polyline

Polygon

Polygon

Polygon

Composite Polyline

Multipolyline

A collection of linear features (polylines only). Arcs in composite polylines are stroked during export.

Composite Polygon

Polygon

Arcs in GeoMedia are stroked before export.

Boundary Geometry

Region/Multipolygon

Region object contains collection of polygons with or without corresponding holes.

Text Geometry

Text Geometry

Graphic Text

Point Collection

Individual Points

MapInfo does not collection of points.

Linear Feature Collection

Multipolyline

Previously defined. See Composite Polyline.

Areal Feature Collection

Region/Multipolygon

Previously defined. See Boundary Geometry.

Heterogeneous collection (point, line, and/or area together)

As individual features

MapInfo does not collection of heterogeneous type.

To export data to MapInfo Interchange Format: 1. Connect to the existing warehouse from which you want to export data. 2. Select Warehouse > Export to > MapInfo Interchange Format.

3. Select the feature class or query to be exported using the Features to export drop-down list. You can export only one feature class at a time.


665

Exporting Data to Other Systems 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. 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 of 1 decimal degree (using geodetic datum ―WGS84‖ with no shifts), enter 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. After using this command, you must use the Import command in MapInfo in order to use the output created from Export to MapInfo Interchange Format.

Exporting to Design File The Export to Design File command lets you export the primary geometry field of multiple feature classes/queries, including categories and reference features, and attribute-linkage data from any read-write or read-only warehouse connection into design file (.dgn) format, ® MicroStation Version 4 files. This format can be either MicroStation V7 or MicroStation V8. This command writes the selected feature classes/queries to the design files (new, append, or overwrite) that you specify. Writing to a new file requires a graphic seed file to write the required header information in the creation of the output design files, which provides the coordinate system for the output files. Appending causes the old files to be appended and new files to be freshly created. Overwriting causes the old files to be overwritten and the new files to be freshly created. With this command, you can only export from one warehouse at a time, or from queries in one run, and each warehouse in following runs. Append lets you output several runs to the same design file. See “Element Types” at the end of this section for a table of the IGDS element types generated from each of the GeoMedia Professional geometry types. 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. If the seed file does not contain a coordinate system, the input data is transformed to the GeoWorkspace coordinate system. In either case, an accompanying .csf file is generated in the same folder as the output file(s) that represents the coordinate system used during the transformation. When only one output file is produced, the name of the generated .csf file is the same as the name of the output file, but with a .csf extension. When multiple output files are produced, only one .csf file, named ExportDGN.csf, is generated. This command lets you export different sets of feature classes to different files in the same export session. You can use the feature class name or query name as the output design filename for the exported features, or export all features to a single design file. You can also assign the symbology (graphic and text properties) individually based on the geometry type to all the selected feature classes/queries; otherwise, the default values are taken.

666


Exporting Data to Other Systems You can have additional data in the seed file, which will be copied into the output file. In the case of MicroStation V7 format, GeoMedia‘s double precision floating-point 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, the MicroStation cell library filename (*.cel) has to be chosen, and for MicroStation V8 the cell library filename (.*dgn). 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-to-properties associations. You can select multiple feature classes/queries to add, in which case all the items are loaded into the grid. If you have already defined the graphic properties for the feature classes/queries, the selected items have those properties when added to the grid. Otherwise, the feature classes/queries are loaded with the default settings.

Integer fields for the feature or query can be used to define values for color, weight, style, and fill color of the output graphics. These are the Graphic properties fields with a pull-down list beside them. You can either type a value or select an integer column.


667

Exporting Data to Other Systems 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 -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 parcel, Access Connection 2 has to be selected. In this way you can generate a single settings file containing definitions for all feature classes and queries originating in multiple connections, and they all are available, regardless of which connection is selected; but only the pertinent ones for the selected connection are shown. When you load the contents of a settings file, they are applied to the feature classes in the selected connection/queries. If those feature classes/queries are selected to export, the graphic properties from these settings are applied to the selected feature classes/queries while exporting. For example, if you load a settings file containing settings for roads, rivers, and states, these feature classes are added to the grid, and when any of those feature classes are selected in the feature classes/queries list or the grid, the graphics properties reflect the loaded settings. If you select a different connection containing roads, rivers, and states, the graphics properties still reflect the loaded settings as the association is based on feature class or query name.

To export to a design file, saving the grid settings: 1. Connect to the existing warehouse from which you want to export data.

668


Exporting Data to Other Systems 2. Select Warehouse > Export to > Design File.

3. On the General tab, select the appropriate Export format option. 4. Select the appropriate Output file option. 5. For Use feature class or query name as output design file 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, type or select the filename in the Cell library name field.


669

Exporting Data to Other Systems 10. Select the Criteria tab; then select the appropriate items from the Select features to export treeview.

The Graphic properties controls are enabled based on the geometry type of the selected feature class/query. Selecting multiple feature classes/queries disables the edit controls. If the selected feature class is already added to the grid, the corresponding item in the grid is highlighted. 11. Select the appropriate Graphic properties. 12. Optional: Click Attributes; then check the Add linkage check box.

13. 14. 15. 16.

Check the Add linkage check box. Type the appropriate value in the Entity number field. Select the appropriate value from the Linkage type drop-down list. Select the appropriate value from the Occurrence number drop-down list; then click OK to save the linkage values for the selected feature class/query. 17. Click Add.

The selected feature class/query is added to the features to Features to export grid with the graphic properties assigned in Step 11, or if none were assigned, with the default values. 18. Optional: Select a feature class/query in the Features to export grid; then click Remove to remove it from the grid.

670


Exporting Data to Other Systems 19. Click Save As; then select or type the appropriate filename to save the settings to.

The contents of the grid are saved to a settings file (a -specified XML file). If an existing settings file is selected, you are prompted to overwrite or append and update. 20. Click Apply to start the export process.

All the feature classes/queries are exported from the Features to export grid, with the settings in the grid. If the Use feature class/query name as output design file name option is selected, all the feature classes from the grid are exported to their respective design files into the specified folder. If the design file already exists, and if the Append to existing output files check box is checked, the existing design files are appended. If unchecked, the existing files are deleted, and a new design file with the same name is created using the specified seed file. If a new filename was entered with the Output all features to a single design file option, the design file is created using the seed file specified and opened for export. When exporting to MicroStation V8 format, the input data 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. Pressing ESC aborts the export processing and results in exporting up to the current record and closing the output file.

To export to a design file without saving the grid settings: 1. 2. 3. 4.

Connect to the existing warehouse from which you want to export data. Select Warehouse > Export to > Design File. Set the appropriate items on General tab. On the Criteria tab, select the appropriate items from the Select features to export treeview.

The default Graphic properties are displayed. 5. Optional: Change the graphic properties. 6. Click Add.

The feature class/query is added to the Features to export grid with the specified properties. 7. Repeat Steps 3-7. You can select multiple items and add them to the grid together. In this case, they all get the default properties, if you have not edited any of those properties. 8. Click Apply to export the items in the grid.

To export to a design file, loading the grid settings: 1. 2. 3. 4. 5.

Connect to the existing warehouse from which you want to export data. Select Warehouse > Export to > Design File. Set the appropriate items on General tab. On the Criteria tab, select the appropriate items from the Select features to export treeview. Click Load; then select the appropriate settings filename to load.


671

Exporting Data to Other Systems 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. 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 ed 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. At this point you can edit the contents of the grid by selecting the feature class in the list box (or the grid) and modifying the properties. The modification is automatically reflected in the grid. You do not have to click Add again to update the grid. he grid reflects the current setting of the particular feature class.

Notes on Seed Files 



672

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 double-precision geometry coordinates will be copied (after rounding off) to the integer UORs of the resultant design file graphic elements. Therefore, it is important to set the GeoWorkspace Storage Space resolution (select View > GeoWorkspace Coordinate System, on the Storage Space tab under Advanced Parameters) so that no great loss of precision in the data will occur. For example, if a seed file with no type-56 element is used, and if the GeoWorkspace horizontal resolution is set to one meter, then the resultant design file graphic elements could have no finer precision than one meter. If this is unacceptable, you could select a horizontal resolution of one centimeter. In transforming the data from a GeoWorkspace to a design file, the command performs the following workflow in the absence of a type-56 element in the seed file:


Exporting Data to Other Systems 

 

Uses the type-9 element (design file header) of the seed file, which is always present irrespective of whether the type-56 element is present or not.  Gets Master Units (mu), Sub Units (su), and Positional Units (pu) from the type-9 element, and sets up storage parameters accordingly.  Sets the projection algorithm to undefined, which the legacy code calls rectangular grid. Sets the horizontal/vertical resolution based on the master unit (mu) of the seed file. Using this information, the command makes the required transformation equation to transform GeoWorkspace coordinates to the corresponding seed file. Because the projection is undefined or rectangular grid, no transformation actually takes place, but the conversion of coordinate values to their corresponding UOR equivalents occurs. This is actually a scaling activity resulting in less precise data, sometimes, because of the rounding off activity to make UORs. If you select a 3-D seed file, then the output will be 3-D. If you select a 2-D seed file, then the output will be 2-D. Eight seed files are delivered with the product in the \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).  seedgeo_v8.dgn is defined as a 2-D geographic coordinate system with a WGS84 geodetic datum (which matches the default GeoWorkspace coordinate system) for MicroStation V8.  seedzgeo.dgn is a 3-D version of the seedgeo.dgn file.  seedzgeo_v8.dgn is a 3-D version of the seedgeo_v8.dgn file for MicroStation V8.  seedprj.dgn is defined as a 2-D projected (Cylindrical Equirectangular) coordinate system with a WGS84 geodetic datum.  seedprj_v8.dgn is defined as a 2-D projected (Cylindrical Equirectangular) coordinate system with a WGS84 geodetic datum for MicroStation V8.  seedzprj.dgn is a 3-D version of the seedprj.dgn file.  Seedzprj_v8.dgn is a 3-D version of the seedpr_v8j.dgn file for MicroStation V8.

Element Types The following table defines the IGDS element types generated from each of the GeoMedia Professional geometry types: GeoMedia Professional Geometry Type

IGDS Element

Type Number

Point

Symbol / Degenerate line / Shared cell instance (only for MicroStation v7 format)

17 / 3 / 35

Text

Text

17

Line

Line

3

Linear

Linestring or complex linestring

4 or 12, 4, 4, …

Area

Shape or complex shape

6 or 14, 4, 4, …


673

Exporting Data to Other Systems GeoMedia Professional Geometry Type

IGDS Element

Type Number

Compound

One or more of the previously defined types 3, 4, 6, 12, 14 based on the content of the collection. The and/or 17 elements are assigned the same graphic group number in order to maintain their group identification.

Exporting to Oracle Object Model Use the Export to Oracle Object Model command to export data from any GeoMedia-ed data warehouse to an Oracle Object Model database for use with the GeoMedia product suite. This command is intended as a tool for bulk loading large amounts of data into a database schema by generating ASCII files that can be used by Oracle‘s SQL *Loader application as Oracle 8.1.6 compatible SQL*Loader files. This command is designed to create and load new tables or to append to existing tables without altering the original table structure or data. This command is not intended to be used as an update tool; you should use the Output to Feature Classes command to update existing records. You can select the data to be exported from a treeview of feature classes, categories, queries, and reference features under connections. If the export is from an existing Oracle , 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 Oracle‘s rules for table names. You can change this after export by directly editing the export files for the specific query. The Export 3D coordinates—This option allows you to choose whether or not to export 3-D coordinate information. If you do not choose this option, only 2-D coordinates are written to the database and the height information is discarded. This is beneficial for both performance reasons and if your data contains arcs because Oracle does not circular arcs in 3-D. Once data has been loaded to the feature class, you cannot change its dimensions without re-creating the table's geometry field. 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. 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 GeoMedia‘s GDOSYS metadata schema before importing data created by Export to Oracle Object Model. This can be done by 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:  _ _per.sql—Creates the table using defaults. For more control, you can create the table or edit the delivered script file.  _ .ctl—SQL*Loader control file for loading data.  _ .dat—SQL*Loader Data file.

674



_ .sqls—Post process script populates the Oracle metadata and GeoMedia‘s GDOSYS metadata tables.

For queries, the spatial index can be generated but not regular indices. 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.bat—Command file that controls the loading process. It will contain references for all the files created during the Export to Oracle Object Model process.  Export.log—Log 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 ed 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. You should 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*Loader‘s default capability. To solve the problem, you need to increase the READSIZE/BINDSIZE variable needs 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

To export data to Oracle Object Model: 1. Connect to the existing warehouse from which you want to export data.


675

Exporting Data to Other Systems 2. Select Warehouse > Export to > Oracle Object Model.

3. Select the appropriate items from the Features to export treeview. 4. 5. 6. 7. 8. 9.

Holding the cursor over an entry displays a tooltip with the geometry type of the entry. Optional: Set the appropriate Export options check box(es). Select the appropriate Export folder. Click Apply to export the data. Examine the output ASCII files, and modify them if necessary. Run the output script file. Use Oracle tools to create a spatial index on the tables.

Exporting to SQL Server Use the Export to SQL Server command to export data from a legacy data store to a SQL Server 2005 or later database for use with the GeoMedia product suite. This command is intended for bulk loading large amounts of data into a database by generating ASCII files that can be used by SQL Server‘s Bulk Loader application. This command is not intended to be used as an update tool. To use this command, you first select the data to be exported from a treeview of all feature classes/queries, including categories and reference features. You can select any mixture of feature classes, queries, categories, and reference features, across any number of connections. Exporting to SQL Server creates the following files based on the coordinate system of the GeoWorkspace:  Metadata.sql—creates eleven metadata tables.  Client: GFeatures, FieldLookup, AttributeProperties, and GeometryProperties.  GDO: GAliasTable, GCoordSystem, ModifiedTables, and ModificationLog.  SQL Server data server: GADOFieldMapping, GParameters, and GIndexColumns.  FeatureClassName_pre.sql (one for each feature class or query exported)—Creates the table using defaults. You can also create the table or edit the delivered script file for more control.  FeatureClassName.b (one for each feature class or query exported)—Data file for loading data.

676


Exporting Data to Other Systems    

FeatureClassName_post.sql (one for each feature class or query exported)—Populates the SQL Server metadata table and all GeoMedia metadata tables. FeatureClassName.dat—Contains the attribute and geometry data for use with the bulk load processor. Import.bat—Script file with all of the above files, which uses common defaults and can be edited for handling specific options. xport.log—Log 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 ed as a session preference. 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. You should review the export.log file at the completion of the export to determine if any errors occurred during the export process.

To export data to SQL Server: 1. Connect to the existing warehouse from which you want to export data. 2. Select Warehouse > Export to > SQL Server.

3. Select the appropriate items from the Features to export treeview. 4. 5. 6. 7. 8. 9.

Holding the cursor over an entry displays a tooltip with the geometry type of the entry. Select the appropriate Export folder. Select the appropriate Export to SQL Server version option. Click Apply to export the data. Examine the output ASCII files, and modify them if necessary. Run the output script file. Use Bulk Loader to create SQL Server tables and to load the geometry and attributes to the SQL Server database.


677


Exporting to AutoCAD Use the Export to AutoCAD command to export spatial data from any read-write or read-only warehouse connection into any of the AutoCAD Release Versions R14, 2000, 2004, 2007, and 2010 .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 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:  Export attributes—Exports attribute information in the input feature class as extended data to the corresponding entity in the output .dxf or .dwg file, or as block attributes and all the geometries (of any type) as BLOCKs in the output .dxf or .dwg file. The default is to not export the attribute information for each graphic object. In addition, you can export attribute information as database linkages. This option exports only the linkage information to the output drawing file, not the actual attribute data. Selecting this option enables the Linkage Details button to display the Linkage Details dialog box, which lets you set the values used to write the linkage information to the drawing file.

See the corresponding topic in GeoMedia Professional Help Topics for information on this dialog box.  Export 3D coordinates—Exports 3-D or 2-D features; the default is 2-D (unchecked). If you are exporting a point feature class/query or a compound feature class/query as block references, you have the option to specify the following:  Block AutoCAD drawing filename (.dwg or .dxf).

678



Block name from all the block names available in the specified block drawing file and the output file (in append mode), along with a special block name DWGFilename that indicates the entire block drawing file is to be exported as a single block definition. If the block drawing file already contains a block with the name DWGFilename, the block name listed refers to the block within the file, and not the entire drawing file.

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

To export data to AutoCAD: 1. Connect to the existing warehouse from which you want to export data. 2. Select Warehouse > Export to > AutoCAD.

3. Select the appropriate feature class/query from the Features to export drop-down list. 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 Output file type option. 6. Select the Output file version from the drop-down list: AutoCAD R14 (the default), AutoCAD 2000, AutoCAD 2004, or AutoCAD 2007.


679

Exporting Data to Other Systems 7. Select the Output file mode option.

8.

9.

10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20.

The Output file mode options are enabled only if the output file name is an existing file. 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. 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. Set the appropriate layer visibility check box(es): Layer on, Layer frozen, and/or Layer locked. 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. Select the Line type name from the drop-down list. Type the appropriate values in the Line width, Color, and Thickness fields. 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. Type the corresponding text font name (.shx) in the Text font name field. Type the appropriate values in the Text color and Text height fields. 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. Select or type the Block name; then type the Block scale. Optional: Check the Export 3D coordinates check box. Click Apply to export the data.

The features are exported and transformed to the GeoWorkspace coordinate system. An accompanying .csf file is generated in the same folder as the output file that represents the coordinate system used during the transformation. 21. Continue the export process until complete; then click Close to dismiss the Export to AutoCAD dialog box.

Exporting to GML Use the Export to GML command to export feature class geometry and its attribute data to GML (Geography Markup Language) format. The selected feature classes (including queries, categories, and reference features) are written to a GML Version 2.1.2, 3.0, 3.1.1 GML data file (.gml), and the corresponding XML Schema definition is written to the GML Version 3.2 base schema GML schema (.xsd) file. This command exports all ed 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.

680


Exporting Data to Other Systems 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 -defined coordinate system, depending on the two Target Coordinate System options on the command dialog box.  Use GeoWorkspace coordinate system—This option exports the data in the GeoWorkspace coordinate system. The default state of the this option to use the GeoWorkspace coordinate system as the target coordinate system depends on GRS and the GeoWorkspace coordinate system. This option is enabled and selected if GRS returns a valid EPSG code for the GeoWorkspace coordinate system, and the input data is then transformed to this coordinate system as the data is exported. If GRS does not return a valid EPSG code, this option is disabled, and you must use the second option.  Use the coordinate system file—This option transforms the input data from the GeoWorkspace coordinate system to the target coordinate system specified in the coordinate system file field. The coordinate system file must be an EPSG-named coordinate system file, that is, EPSGxxxxx.csf, where xxxxx can be any positive integer, and must be present in the \EPSG folder under the location where the host product is installed. GRS provides a valid EPSG code for this file, and the input data is then transformed to this coordinate system as the data is exported. This option is always enabled and is by default selected if GRS does not return a valid SPG code for the GeoWorkspace coordinate system. This command outputs one GML data file and one GML schema file per export operation. The default names are GMLData.gml and GMLData.xsd, respectively. The default location for both is the GeoMedia \Warehouses folder. You can, however, change these names and locations as needed. The GML data file and the GML schema file contain all the selected feature classes with names as follows: 

Feature Class: 



Query:



Categorized Item: Reference Feature:

You also set the following other parameters before exporting.  The appropriate GML version that is exported, by default, GML version 3.1.1.  The namespace and the prefix for the output GML data/schema file in the format: xmlns:<prefix>=’ . See the next section for more information on prefixes.  The location and name of the GML base schema file.  Whether or not the bounding box is output for every record in the output GML file.  Whether or not the sequence of fields output in the GML data/schema file is the same as that of the input feature class/query.  Whether or not the 3-D coordinates are exported in the GML data file.  Whether or not to swap the order of the coordinate values during the export process.

Using Prefixes When a recordset is exported in GML with default settings, the default namespace (or target namespace) for an application schema is taken as "xmlns:gmgml='http://www.intergraph.com/geomedia/gml'" and so the schema and data are encoded using the "gmgml", which refers to the target namespace. The following is an example excerpt taken from the output GML file exported using the default settings:


681

Exporting Data to Other Systems 34.665793 -86.776129 34.777847 -86.564569 STATE HWY 255 STATE HWY 255 1 34.777847 -86.672915 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.

682


Exporting Data to Other Systems 34.665793 -86.776129 34.777847 -86.564569 STATE HWY 255 STATE HWY 255 1 34.777847 -86.672915

To export data to GML: 1. Connect to the existing warehouse from which you want to export data. 2. Select Warehouse > Export to > GML.

3. Select the appropriate entries from the Features to export treeview. 4. Use the appropriate Target Coordinate System option. If Use GeoWorkspace coordinate system is enabled and selected, go to Step 6. OR If Use the coordinate system file is enabled and selected, continue with Step 5.


683


5. 6. 7. 8. 9. 10. 11. 12.

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. Type or select through Browse the location and name of an appropriate coordinate system file. In the GML data file field, select or type the appropriate path/location to which the exported GML data file is written. In the GML schema file field, select or type the appropriate path/location to which the exported GML schema file is written. Select the GML version to be output from the GML version drop-down list, if appropriate. Type the output namespace and prefix in the Output namespace and prefix field, if appropriate. In the GML base schema location field, select or type the appropriate location of the GML base schema file, if appropriate. Check the Bounding box per record and/or Preserve input field sequence and/or Export 3D coordinates checkboxes, if appropriate. 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.

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.

684


SECTION 22

Working with Libraries A library is a repository of sharable GeoWorkspace objects designed especially for the enterprise . With the library commands, you can easily and directly share the contents of your GeoWorkspace. You can create new libraries, connect to and manage libraries, and organize libraries. The library commands give you the ability to save the following object types: 

Catalog Connections



Searches



Categories



Spatial Filters



Legends



Styles



Queries



Warehouse Connections



Queues

Once you have saved these objects, any 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 for such an enterprise might create a corporate style library that all GIS s 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 can easily replace the Road style in the library, and s can then simply connect to the updated library and refresh the objects whose definitions have changed. Note that most of the sharable objects reference other objects. For example, a legend contains Legend Entries, each of which refers to one or more Style Definitions and Queries. The Queries can refer to other Queries and/or Feature Classes. Feature Classes in turn refer to Connections. And, of course, Style Folders contain Style Definitions, and Query Folders contain Queries. When you save one of these objects to a library, the system automatically saves all of the objects in the reference tree. Then when the object is copied to a GeoWorkspace, all of the required objects underneath it are also copied. This ensures that the copied object will be fully functional in the active GeoWorkspace. The library commands are the following: 

New Library



Library Connections



New Library Connection



Library Organizer

These commands are discussed in this section.

Creating a New Library The New Library command lets you create a new read-write library in an Access database file (.mdb) only. This command provides a simple way of creating a library schema layout in a new database while needing minimal input from you. You do not need a warehouse connection to create a library; however, you do need such a connection to carry out all library-related workflows.


685

Working with Libraries Creating a library is a two-step process. You first select and validate a library template, and then you use that template to actually create the new library. This command is similar to the Warehouses > New Warehouse command in GeoMedia Professional. See the “Working with Connections” section in the “Working with Warehouses” section. By default, this command creates the library from the provided library template LibraryTemplate.mdb located in the \GeoMedia Professional\Templates\Libraries folder. You can, however, choose a different template from those available in the product template folder. This template file acts as a seed for creating the library. To create the new library after selecting the template, you specify a name for the library or select an existing .mdb file in the default \GeoMedia Professional\GeoWorkspaces\Libraries folder or in any other location of your choice. The command then creates the library based on the selected template. If there is no coordinate system in the template, the command automatically configures the coordinate system of the library using the active coordinate system of the active GeoWorkspace. The principal use of the library coordinate system is to transform spatial filters into the GeoWorkspace coordinate system. The GCoordSystem table that may be present in the .mdb of the library is not used to store the coordinate system of the library. When the library is created, a connection is automatically opened for the new library. The name of the library connection is set as the library name itself. If a library connection exists with the same name, an incrementing digit is added to the end of the name.

To create a new library: 1. Select Tools > New Library.

686


Working with Libraries 2. Select the appropriate library template; then click Open.

3. Type the appropriate File name; then click Save.

The template is validated, and if valid, the library is created.

Creating a New Library Connection The New Library Connection command lets you connect to libraries that are compatible with GeoMedia Professional. This connection is then available for use with other library commands. You can open a library in read-write or in read-only states. 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 ed 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 ed by the software, a message tells you that that the library cannot be opened. You can make the following types of connections: 

Access



Access Read-Only



Oracle Object Model Read-Write



Oracle Object Model Read-Only



SQL Server Read-Write



SQL Server Read-Only

For Access, you select the location of the Microsoft Access database file (.mdb) to which you want to establish a connection. For Oracle and SQL Server, you select the mode of authentication, name, , and host string. For Oracle and MSSQL, which allow table and column level permissions, library connections are made with whatever database permissions are available to the 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


687

Working with Libraries server the connection will fail. To make a connection to a read-only Access library the read-only server must be used instead. When using Oracle, only the owner of the library can connect to the library, that is, the only ed workflow is a connection to the library schema by the library owner.

To create a new library connection: 1. Select Tools > New Library Connection. 2. Select Access or Access Read-Only as the Connection type; then:  Change the Connection name or keep the default,  

The comma ( , ) character is not allowed in the Connection name. Type an optional Connection description, and then Type the complete path of the .mdb Access Database file or select it by clicking Browse.

OR Select Oracle Object Model Read-Only/Read-Write as the Connection type; then:  Change the Connection name or keep the default,  Type an optional Connection description,  Select the Server and mode of authentication, and then:  Type the name, , and Host string.

OR Select SQL Server Read-Only/Read-Write as the Connection type; then:  Change the Connection name or keep the default,

688


Working with Libraries    

Type an optional Connection description, Select the Server and mode of authentication, Type the name and , and then Select the database.

3. Click OK to make the connection. Both SQL Server and Oracle require that the GeoMedia‘s standard metadata structure be present before establishing a library connection. For SQL Server, this metadata resides in the database. In Oracle, it is contained in the GDOSYS metadata schema. The specific tables required by the library commands are created automatically if the tables do not already exist.

Managing Library Connections The Library Connections command manages the connection information of a library connection in a manner similar to the Warehouse > Connections command of GeoMedia Professional. See the “Working with Connections” section in the "Working with Warehouses" section. The Library Connections command lets you do the following:  Make a new library connection.  Review a list of all available library connections in a GeoWorkspace.  Change the state of a library connection (open read-write, open read-only, or closed).  Edit the library connection parameters (properties) of an existing library connection for the data server involved.  Delete an existing open or closed library connection. 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 ed 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 ed 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:


689

Working with Libraries Name—Library connection names, with an icon at the start of the cell indicating the state:

Type—Library connection type. Library—Location of the library, that is, the database .mdb file for an Access database or the data source name for an Oracle Object Model or SQL Server database. You can edit the location of the library using Properties but not directly from the cell of the grid. By default, library connections are kept in a closed state. They are opened automatically when used by the Library Organizer command.

To open or close connections: 1. Select Tools > Library Connections.

2. Select the row selector of the row(s) whose open/close status you want to change.

Use Shift/Ctrl to select multiple rows; click the top left-corner grid button, to the left of the Name row, in order to select all rows. 3. Click the appropriate open, reopen, or close button.

To create a new connection: 1. Select Tools > Library Connections. 2. Click New. 3. Using the previously described procedure, select the Connection type; then enter the appropriate parameters. 4. Click OK to make the connection.

To view or edit library connection properties: 1. Select Tools > Library Connections.

690


Working with Libraries 2. On the Library Connections dialog box, select the row of the connection whose properties you want to view or edit; then click Properties.

3. Edit the server-specific properties appropriately. 4. Click OK.

Organizing Libraries The Library Organizer command lets you copy the following objects between the active GeoWorkspace and a library attached to it: Catalog Connections

Searches

Categories

Spatial Filters

Legends

Styles

Queries

Warehouse Connections

Queues 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. for queues also includes 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 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.


691

Working with Libraries The Select References button lets you check such common objects to easily refresh all common objects created from the library. 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 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. When Select References is used the Delete button is selected automatically so that the objects are overwritten and updated. Select References works only when the originating library is connected and the library connection name has not changed. You can also choose the behavior when an object with the same name as an object to be copied already exists. By default, copy works with the Overwrite option, which overwrites the existing object instances (except for connections), if any, in the target space. The Copy with new name option lets you append the existing instances in the target object space. If an object with the same name exists in the target object space, an incrementing digit is added to the end of the name so as not to conflict with the existing object. Finally, the read-only Description field displays the description of the currently highlighted object if it has a description. In copying to the library, it is possible that updating (that is, overwriting) an existing object instance in the library has an implication of version conflicts. While overwriting an object instance in the library, the command does the following:  If the object instance in the library is not updatable, then:  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 ed on the target system, this command displays overlay icons on the primary icons in both the Library contents and the GeoWorkspace contents treeviews based on the version compatibility status of the library objects, as follows:  If the compatibility status compatible or incomplete, no overlay symbol is displayed, indicating that the object is both loadable and updatable.  If the compatibility status is compatible backward or incomplete backward, the updatable overlay symbol ( ) is displayed, indicating that the object is both loadable and updatable and requires confirmation on update.  If the compatibility status is incompatible, the incompatible overlay symbol ( ) is displayed, indicating that the object is neither loadable nor updatable.

Compatibility Status The compatibility status of library objects determines whether the library is available for load and/or update. The status value and an explanation of each follows. Incompatible – Indicates that the object in the library is neither loadable nor updatable. This value is set if the object instance satisfies any of the following conditions:  The object instance stored in the library is unknown to the installed software.

692


Working with Libraries 

The version of the object instance stored in the library is greater than the version ed by the installed software.  The object instance stored in the library has a ―Required‖ relationship with a referenced object instance at any depth, and the referenced object instance is incompatible. Compatible – Indicates that the object in the library is both loadable and updatable. This value is set if the object instance satisfies all of the following conditions:  The version of the object instance stored in the library is the same as the version ed by the installed software.  There is no case in which the object instance stored in the library has a ―Required‖ relationship with a referenced object instance at any depth, and the referenced object instance is something other than compatible. Compatible Backward – Indicates that the object in the library is both loadable and updatable, but that an update will cause a version upgrade of the object within the library. This value is set if the object instance satisfies any of the following conditions:  The version of the object instance stored in the library is less than the version ed by the installed software.  The object instance stored in the library has at least one referenced object instance with a compatibility status of compatible backward. Incomplete – Indicates that the object in the library is both loadable and updatable, but that one or more referenced objects cannot be loaded or updated. This value is set when it satisfies all of the following conditions:  The version of the object instance stored in the library conforms to the rules of the compatible status.  The object instance stored in the library has a ―Member‖ or ―Optional‖ relationship with a referenced object instance at any depth, and the referenced object instance is incompatible. Incomplete Backward – Indicates that the object instance in the library is both loadable and updatable, but that one or more referenced objects cannot be loaded or updated, and that an update will cause a version upgrade of the object within the library. This value is set when it satisfies all of the following cases:  The version of the object instance stored in the library conforms to the rules of the compatible backward status.  The object instance stored in the library has a ―Member‖ or ―Optional‖ relationship with a referenced object instance at any depth, and the referenced object instance is incompatible. Object instances having any compatibility status other than incompatible are both loadable and updatable. However, any attempt to overwrite the library-resident object overwrites its content (including loss of for incomplete statuses), and upgrades its version.


693

Working with Libraries To organize libraries: 1. Select Tools > Library Organizer.

2. Select the appropriate Library connection from the drop-down list.

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

During the copy process, the status bar is updated. 5. Select one or more objects in the GeoWorkspace contents that already exist in the active library; then click the left-arrow button (<) to copy to the library.

During the copy process, the status bar is updated. All the selected objects are appended to the same position within the folders of active read-write library as it occupied in the GeoWorkspace with a decorated name. 6. Select the appropriate If an item exists with the same name option, Copy with new name or Overwrite. 7. Click Select References to select all the items common to the library and to the active GeoWorkspace. 8. Click the right-arrow button (>) to copy the selected items to the same position within the folders of active GeoWorkspace as they occupied in the library.

694


Working with Libraries 9. Edit the objects as necessary. 10. Click on left-arrow button (<) to copy the selected items back to the same position within the folders of the active read-write library as they occupied in the GeoWorkspace. 11. To delete, select one or more objects in the active library; then click Delete.

During the delete process, the status bar is updated. 12. To rename, select one object in the active library; then click Rename.

13. Type a new name not existing in the hosting collection of the library; then click OK. 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. Internally, the libraries use the | character. This character is reserved, do not use it in any GeoMedia object that you want to store in the library.


695

Working with Libraries

696


APPENDIX A

Technical and Information Intergraph provides several ways to access information and to , including self-help tools and phone .

Self-Help Tools Intergraph provides several electronic self-help tools to answer your questions 24 hours a day, 7 days a week. 1. Go to the SG&I page (http://.intergraph.com/). The first time you select this link, it displays the Intergraph page, and you need to select Security, Government & Infrastructure Division to display the SG&I page. When you select this link the next time, it will go directly to the SG&I page. If you later want to change the division, just click (Change Division) in the list at the upper left of the SG&I page. 2. Under Product , select the appropriate Intergraph product from the Products drop-down list; then click Go. 3. On the Customer page, enter your ID and ; then click . If you do not have a , click the link to request one. 4. On the product page, do one of the following:  Click Knowledge Base.  Scroll to the Product Versions table and click the icon for the document you want to read.  To read about new features, click Release Notes.  To read about updated features, click Issues Resolved. Release Notes and Issues Resolved may not be available for the initial release of a product because an initial release has all new features and no updated features. Patches, fixes, and minor releases may or may not have a Release Notes document, an Issues Resolved document, or a fixes list.

Phone Numbers For general Intergraph information, please call 1.800.791.3357 (U.S.) or 001.256.730.2000 (international). For worldwide , please your local Intergraph office (http://www.Intergraph.com/worldwide.aspx). For North American Phone , please call the appropriate number in the following table: Product Family

Phone Numbers

Additional Information

Utilities and Communication

1.877.463.1217

Monday – Friday 7:00 a.m. – 7:00 p.m., CST

FRAMME G/Technology InService


Critical problems after 7:00 p.m. CST, weekends or holidays

697

Technical and Information Product Family

Phone Numbers

Additional Information

Government/Transportation

1.800.661.8134


1.877.822.8921


Camera Systems Digital Cartographic Suite GeoMedia GIS Imaging GIPS/GIES ImageStation IntelliWhere MGE TerraShare Public Safety Business Intelligence I/CAD Map Production Products

Critical problems after 7:00 p.m. CST, weekends or holidays

Mobile Products Records Management Suite Security Video Analyst Federal & Third Party

1.800.633.7248

7:00 a.m. – 7:00 p.m., CST

Hardware

1.800.414.8991

Per-call and spare parts (7:45 a.m. - 4:00 p.m.). Per-call requires PO or credit card number.

Other Links 

698

To submit sales inquiries, general questions, and comments, please visit our Us Web page (http://www.intergraph.com//default.aspx).


APPENDIX B

Using Oracle Connections GeoMedia Professional provides an Oracle Object Model data server that facilitates connections to Oracle-based warehouses. This allows GeoMedia applications to access both Oracle simple data types and Oracle location-based data using the SDO_GEOMETRY data type. There are two variations of the Oracle Object Model Data Server, a read-only data server and a read-write data server. These are accessed through the New Connection command. This appendix applies to both variations.

Delivery and Connection Prerequisites GeoMedia Professional will automatically install the Object Model Data Server. Registration of this data server requires that Oracle client software (10.2 or later) be present on the system before installing GeoMedia Professional. If the Oracle client has not been installed, the Oracle connection types will not appear in the Connection types list on the New Connection dialog box in GeoMedia Professional. Oracle 10g is the earliest client version that is ed. If you are using Oracle 9i server, you will need to access it through the 10g client. If you have installed GeoMedia Professional before installing the Oracle client, you will need to re- GeoMedia Professional once the Oracle client has been loaded. The following command will re- GeoMedia Professional: :\Program Files\GeoMedia Professional\Program\RegGM.exe The Object Model Data Server requires the standard InterMedia Locator package in Oracle. The Oracle spatial package is not required (unless you are using GeoRaster capability) but is fully ed. Oracle Spatial is a superset of InterMedia Locator and adds commands for complex spatial analysis, LRS, and other advanced capabilities. The Object Model Data Server is fully compatible with both Spatial and Locator. Refer to the Oracle Spatial 's Guide and Reference documentation for information on storing spatial data in Oracle and on the difference between Locator and Spatial.

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 name, , and net service name. Net service names are created using Oracle‘s Net Configuration Assistant and reflect the database you are trying to connect to (the information is stored in the tnsnames.ora file. You can also connect using Oracle's EZConnect format; server:port/sid. For example, the connect string for the Oracle sid ORCL located on server DBSERVER would be DBSERVER:1521/ORCL. Read-only connections rely completely on Oracle‘s 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 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


699

Using Oracle Connections results with data access and performance, you should always configure GeoMedia‘s metadata. If GeoMedia‘s 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 for this schema must be called GDOSYS, and it can reside in any Oracle tablespace (20M expandable to 50M is usually sufficient). 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 “GeoMedia’s GDOSYS Metadata Schema” in this appendix.

Persistence By default, GeoMedia stores the Oracle connection in the GeoWorkspace. This is meant as a convenience and allows s to open existing GeoWorkspaces containing Oracle connections without having to re-enter connection s. However, this is a drawback to those s wanting higher levels of security. The option to turn off persistence is in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\GDO\Oracle Object Read-Only\1.0\Store HKEY_LOCAL_MACHINE\SOFTWARE\GDO\Oracle Object Read-Write\1.0\Store The default setting is 1, which means that connection s will be stored. To force the to enter a for each Oracle connection, change the (default) setting to 0. persistence is not an issue if you are using Windows domain authentication for your connections.

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= this sets the prefix Oracle will use for domain authenticated names. GeoMedia does not the default prefix OPS$. You will need to choose a prefix that does not contain the $ character. Any prefix will work, but the only special character allowed 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.

700


Using Oracle Connections Create you in Oracle using the OS_AUTHENT_PREFIX, and specify External Authentication for the . For example, if your domain is JSMITH, your Oracle name is DA_JSMITH. As with normal Oracle s, you need to assign the appropriate roles and privileges to this , typically connect and resource, but that is up to the Database (DBA). To connect in GeoMedia, set the connection option to Windows authentication, and enter the database service name. If your domain authenticated name 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/views and special characters will cause this to fail.

Object Model Data Server Requirements The Oracle object model data server has specific requirements and limitations. These are listed below:  Geometry is stored in a column of type SDO_GEOMETRY. Multiple geometry columns are allowed per feature class, but only one geometry field can be primary. GeoMedia will display all available geometry fields, but only the primary geometry will be editable. The primary geometry field can be changed through Database Utilities. Feature classes containing multiple geometries cannot be created using the GeoMedia Professional Feature Class Definition command.  Only one set of attribute data is allowed for any given geometry. The use of attribute tables in a -view relationship with a table containing geometry information allows you to get around this limitation. views limit editing capability and may require the use of instead of triggers.  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 _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 ed, but $ is generally reserved for system tables and should only be used when necessary. If you are planning to use Oracle‘s 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.  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 data type, 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


701

Using Oracle Connections





 



GeoMedia through the GDOSYS metadata table GINDEX_COLUMNS. In order to be editable, GeoMedia must furnish the key value, either through direct key-in or through autonumber assigned sequence. Any field assigned as a key for a view must be either integer or alphanumeric. For more information on the format and contents of this table, see “GINDEX_COLUMNS” in this appendix. The Oracle Object Model data server s 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. 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 . All Oracle DCL privileges are fully ed. Use the GRANT command in SQL to allow one to connect to another ‘s 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 that owns the table in the format OWNER.TABLENAME, for example, INGR.ROADS. The use of table and view synonyms is not ed at this time. Oracle spatial data that utilizes LRS geometry is ed in a read-only mode. You are allowed to view the associated geometry in GeoMedia Professional, but the measures are ignored. You must create and use Oracle views to 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 view‘s base table is. The column used here can 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.

Data Storage and Type Matching Geometry Storage Oracle Spatial/Locator uses a pre-defined database object type to store spatial data. The object type is defined in the database as MDSYS.SDO_GEOMETRY. The basic components of this data type are described as follows: GEOMETRY_COLUMN (SDO_GTYPE, SDO_SRID, SDO_POINT (X,Y,Z), SDO_ELEM_INFO(OFFSET,ETYPE,INTERPRETATION), SDO_ORDINATES(X,Y,Z)) For more detailed, up-to-date information, see the Oracle Spatial s 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

702









geodetic data, an SRID is required by Oracle. Consult the Oracle Spatial s 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 in this format. 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) If the points are three-dimensional, they are stored as: SDO_ORDINATE(X1,Y1,Z1,X2,Y2,Z2,X3,Y3,Z3,X4,Y4,Z4,X1,Y1,Z1}

Geometry Type Mapping The Oracle Object Model Data Server maps GeoMedia's geometry types into the SDO_GEOMETRY types, and vice versa. The following table identifies the mapping used when converting from Oracle geometry types to GeoMedia geometry types. The symbol ―d‖ indicates the dimension, d=2 for 2-D data and d=3 for 3-D data. The symbol "n" refers to the number of segments in the geometry definition. Oracle to GeoMedia Element Type Conversion Oracle Gtype

Oracle Etype

Oracle Interpretation

Oracle Meaning

GeoMedia Geometry Type

d001

0

6000

Application Defined

GeoMedia Point Rotation Matrix

d001

0

6001

Application Defined

GraphicText

d001

1

1

Point

SpatialPoint

d001

1

0

Point Orientation (10g Point Rotation Matrix or later) (deprecated)

d002

2

1

Linear – straight line segments only

SpatialLine

d002

2

2

Linear – arcs only

SpatialLine


703

Using Oracle Connections Oracle to GeoMedia Element Type Conversion Oracle Gtype

Oracle Etype


Oracle Meaning


d002

4

n>1

Linear – straight line segments and arcs

SpatialLine

d003

0

6002

Application Defined

Coverage (Raster)

d003

1003

1

Areal – straight line segments only

SpatialArea

2

Areal – arcs only

SpatialArea

3

Areal – rectangle

SpatialArea

4

Areal – circle

SpatialArea

n>1

Areal – straight line segments and arcs

SpatialArea

Heterogeneous Collection

SpatialAny

2003 d003

1003 2003

d003

1003 2003

d003

1003 2003

d003

4

d004 … d007

The following table identifies the mapping used when converting from GeoMedia‘s geometry types to Oracle geometry types (applies only to data changes through the read-write data server). GeoMedia to Oracle Element Type Conversion

704


Oracle Gtype

Oracle Etype


Oracle Meaning

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 Polyline d002

4

2

Linear – straight line segments and arcs

Boundary

d003

1003

-

Exterior Ring

Boundary

d003

2003

-

Interior Ring

Composite Polygon d003

1005

-

Composite Exterior Ring

Composite Polygon d003

2005

-

Composite Interior Ring


Using Oracle Connections GeoMedia to Oracle Element Type Conversion GeoMedia Geometry Type

Oracle Gtype

Oracle Etype


Oracle Meaning

Raster Polygon

d003

0

6002

Application Defined

In versions of Oracle prior to 10g, GeoMedia used its own format for oriented points. GeoMedia‘s oriented point format adds an application defined Etype of 0 and a custom 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 introduced a native oriented point storage format that is now the default point format used by GeoMedia. GeoMedia can read the older format but will convert data to the new format during any edit operations. 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:  Exterior polygon ring – ETYPE=1003 and ordinates must be specified in counterclockwise order.  Interior polygon ring – ETYPE=2003 and ordinates must be specified in clockwise order. 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:  1005: exterior polygon ring (ordinates must be specified in counterclockwise order).  2005: interior polygon ring (ordinates must be specified in clockwise order).  The INTERPRETATION value takes on a different meaning depending on whether or not the ETYPE is a compound element:  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 example, a line string may be made up of a sequence of connected straight-line segments or circular arcs. Several geometry types are not completely ed by GeoMedia. Both native SDO_POINT geometries and point clusters can be read and displayed, but GeoMedia will not write them. The same is true for arc-strings, native circles, and simple 2-point polygons.

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:


705

Using Oracle Connections SDO_GEOMETRY (3001, NULL, SDO_POINT(861906,-482832, 0),NULL,NULL) In this format, Oracle‘s SDO_POINT array did not store any information about the orientation of the point. For this reason, GeoMedia's handling of Oracle‘s native point format is strictly read-only. Before Oracle 10g, GeoMedia preserved 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 geometry‘s 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 -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 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 2-D 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 GeoMedia‘s 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: SDO_GEOMETRY (3001, NULL, NULL, SDO_ELEM_INFO_ARRAY (1,1,1,4,1,0), SDO_ORDINATE_ARRAY (861906,-482832,0, 0,0,1)) For 2-D points, only a 2-D matrix is required. Here is an example: SDO_GEOMETRY (2001, NULL, NULL, SDO_ELEM_INFO_ARRAY (1,1,1,3,1,0), SDO_ORDINATE_ARRAY (861906,-482832,0,1)) If GeoMedia detects 10g or later, it will automatically write oriented points using Oracle‘s 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 Oracle‘s _SDO_GEOM_METADATA, and a spatial index must be present.

Text and Labels Oracle currently does not have a native storage format for text. In order to make use of Oracle‘s existing format, GeoMedia stores text as a point feature with some additional information that contains text orientation, alignment, format, and the actual text decomposed into four-byte integers. An example of how GeoMedia stores the text Connecticut in a SDO_GEOMETRY object is shown below: SDO_GEOMETRY(3001,NULL,NULL, SDO_ELEM_INFO_ARRAY(1,0,6001,10,1,1), SDO_ORDINATE_ARRAY(0,1,0,0,65536, 11,1852731203,1769235301,7632227, 1919397.1,680897.264,0)) The geometry‘s 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

706


Using Oracle Connections -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 65536, -- Formatting 00000000 00000000 00000000 00000000 00000000 00000001 00000000 00000000 11, -- Number of characters including spaces 1852731203, -- 00000000 00000000 00000000 00000000 01101110 01101110 01101111 01000011 -NULL NULL NULL NULL 110 110 111 67 -n n o C 1769235301, -- 00000000 00000000 00000000 00000000 01101001 01110100 01100011 01100101 -NULL NULL NULL NULL 105 116 99 101 -i t c e 7632227, -- 000000000 00000000 00000000 00000000 000000000 01110100 01110101 01100011 -NULL NULL NULL NULL NULL 116 117 99 -t u c 1919397.1, 680897.264,0)) -Text location X,Y,Z (justification point) A text feature is treated just like a point feature, so entries are required in _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 s 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:


707

Using Oracle Connections 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)) In this example, the ELEM_INFO_ARRAY triplet (1,0,6002) contains a -defined ETYPE of 0 with an INTERPRETATION of 6002. This tells GeoMedia that the values it is reading correspond to a raster image. The second triplet (22,2003,1) represents the polygonal outline of the raster image. Only the OFFSET value, 22, may vary. 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 Oracle‘s spatial filtering capability. Because the raster image is treated a polygon, entries are required in the _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 as long as the standard raster metadata is assigned to the table containing the SDO_GEORASTER data type. 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.

Data Type Matching - Oracle to GeoMedia During a connection, the column data types used in Oracle are mapped to internal GeoMedia data types (known as GDO) by the Oracle Object Model data server. The following table identifies the mapping used when making the conversion. Any data type that is not listed in this table is considered uned and will be ignored by GeoMedia applications.

708

Oracle Data Type

GeoMedia Data Type

CHAR VARCHAR2

Text (<= 255)

DATE

Date

NUMBER

Double

NUMBER(p,s)

Long

Memo (> 255)

(p<10, s= 0)

Double

(s != 0)

Double Double

(p >= 10) (p=0, s=0)

INTEGER (p is null, s = 0)

Long

FLOAT

Double


Using Oracle Connections Oracle Data Type

GeoMedia Data Type

RAW

LongBinary

BLOB

LongBinary

CLOB NCLOB

Memo

SDO_GEOMETRY

Spatial

SDO_GEORASTER

Coverage

These default mappings may be overridden by GeoMedia client metadata tables. Uned column data types will be ignored by GeoMedia. There has been concern expressed over the fact that GeoMedia converts NUMBER(10) in Oracle to a DOUBLE in GDO rather than a LONG. This conversion is required because NUMBER(10) can store a value that will not fit into the LONG data type (+- 9999999999 versus +-2147483648). If you need to use an integer in Oracle, use the Oracle INTEGER data type and not NUMBER(10). An INTEGER type that is mapped to Autonumber in GeoMedia will require a sequence to be assigned. You can assign sequences to other NUMBER types, but they will not be treated as autonumber. Whether or not sequences are assigned through autonumber, they will still be used during data entry.

Data Type Matching – GeoMedia to Oracle The following table identifies the mapping used when converting from GeoMedia‘s GDO data types to Oracle data types (this applies only to metadata changes through the read-write data server). GeoMedia Data Type

Oracle Data Type

Boolean

NUMBER (1,0)

Byte

NUMBER (3,0)

Integer

INTEGER

Long

INTEGER

Single

FLOAT

Double

FLOAT

Currency

FLOAT

Date

DATE

Text

VARCHAR2

LongBinary

BLOB

Memo

CLOB

Guid

VARCHAR2

Spatial/Graphic (any type)

MDSYS.SDO_GEOMETRY


709


Native Geometry Metadata Each column of type SDO_GEOMETRY requires range and tolerance information for each dimension to be specified in a global table owned by MDSYS. Each spatial data has read-write access to this metadata table through a view called _SDO_GEOM_METADATA. For tables and views that the has select privileges on, ALL_SDO_GEOM_METADATA provides the information. The difference is that ALL_SDO_GEOM_METADATA is read-only. All DML operations related to Oracle‘s spatial metadata should be performed the _SDO_GEOM_METADATA view (never directly access MDSYS). All SDO_GEOMETRY columns that are in the schema must have appropriate values in the _SDO_GEOM_METADATA view. This is a requirement by both Oracle and GeoMedia. GeoMedia takes this one step further and requires views to also have entries here. Behind the scenes, GeoMedia writes metadata information to _SDO_GEOM_METADATA but reads the metadata through ALL_SDO_GEOM_METADATA. For this reason, GeoMedia can only create tables in the schema owned by the connected , but it can read metadata from any schema the connected has privileges to access. DBA's can work around this by granting insert privileges on MDSYS.SDO_GEOM_METADATA_TABLE to the affected . This will allow GeoMedia to create tables in schemas other than the connected . If you use the Output to Feature Classes command, _SDO_GEOM_METADATA is populated automatically using default values stored in the GDOSYS.GPARAMETERS table. If you use the Export to Oracle Object Model command, default values are provided in the _post.sql files. In all other cases, you will need to populate this view manually. You can set default values yourself using the following insert statements in SQL: INSERT INTO _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)), NULL); If your data is three dimensional, you need to include a dimension statement for the Z-value as follows: INSERT INTO _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 geodetic data using longitude and latitude coordinates, the metadata range must be +/- 180 and +/-90 similar to that shown below: INSERT INTO _SDO_GEOM_METADATA VALUES („TABLE_NAME','GEOMETRY_COLUMN', MDSYS.SDO_DIM_ARRAY ( MDSYS.SDO_DIM_ELEMENT('X',-180,180,0.05), MDSYS.SDO_DIM_ELEMENT('Y',-90,90,0.05)), NULL); Failure to assign the correct metadata range for geodetic data will lead to incorrect results for both spatial filters and spatial queries. The tolerance value used in the SDO_DIM_ARRAY is used by Oracle to determine when distinct coordinate values are to be considered equal and to associate a level of precision with spatial data. This value must be a positive number greater than zero.

710


Using Oracle Connections For non-geodetic data, the tolerance value is in the unit of storage associated with the data. For example, if the unit of measurement is meters, a tolerance value of 0.0001 indicates a tolerance of 1/10 millimeter. This is equivalent to GeoMedia's built-in spatial tolerance. For best results, Oracle's tolerance should be no less than half of GeoMedia's, or 0.00005 meters. Keep this in mind if your data is stored in feet because conversion will apply. For geodetic data (longitude, latitude), the tolerance value is always in meters (a tolerance of 1 would mean 1 meter). For most spatial operations, the tolerance value for geodetic data should never be smaller than 0.05 (5 centimeters), and in most cases, it should be larger. If a tolerance value less than 0.05 is specified, Oracle will automatically default it to 0.05 in those cases where a smaller tolerance is not allowed. Oracle uses the tolerance in its own internal calculations to determine the relationship between vertices; it has no effect on GeoMedia‘s own tolerance or on client side calculations. However, tolerance is important when using spatial analysis filters such as INSIDE, EQUAL, or COVEREDBY.

Oracle Coordinate Systems - SRID Oracle s a variety of coordinate systems that can be assigned to spatial data. These coordinate systems can be listed by means of the following query: SELECT CS_NAME, SRID FROM MDSYS.CS_SRS ; To use one of Oracle‘s coordinate systems, the SRID of the coordinate system must be loaded into both the _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 _SDO_GEOM_METADATA SET SRID=8307 WHERE TABLE_NAME=‟ROADS‟ AND COLUMN_NAME=‟GEOMETRY‟; -UPDATE ROADS A SET A.GEOMETRY.SDO_SRID=8307; 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 affected geometry column. GeoMedia Professional ignores the SRID value used by Oracle because it already has built-in for most coordinate systems. There is no direct mapping between Oracle‘s SRID‘s and GeoMedia‘s coordinate systems. You can use the SRID for compatibility with other applications, and GeoMedia automatically will 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 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 CS_NAME FORMAT A60; SELECT CS_NAME ,SRID FROM MDSYS.CS_SRS WHERE CS_NAME LIKE 'LONG%' AND (CS_NAME LIKE '%NAD%' OR CS_NAME LIKE '%WGS%'); The SRID to use in this example is 8307.


711


Utilizing Spatial Indexing Both GeoMedia and Oracle require spatial indexes to be present on all SDO_GEOMETRY-based columns present in the database. Oracle uses RTree indexing for spatial data. An RTree index approximates stored geometry by using a minimum bounding rectangle, or MBR, for each geometry. 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.

Creating Spatial Indexes Creating a spatial index is very similar in syntax to creating an index on a column of a simple data type. For tables created using GeoMedia‘s Feature Class Definition, the spatial index will be created for you. If you create your own tables, you need to create the spatial index manually using the example syntax shown below: CREATE INDEX ON (<sdo_geometry_col>) INDEXTYPE IS MDSYS.SPATIAL_INDEX; This is the syntax in its simplest form; there are many other parameters available depending on how you want the index to behave, including the ability to choose the index tablespace or to optimize the index creation. These are covered thoroughly in Oracle‘s documentation. For more detailed, up-to-date information, see the Oracle Spatial s 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 re-index 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 FORCE; Oracle allows geometries to contain up to four dimensions. The GeoMedia Object Model Data Server s 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. Spatial indexes can operate in all three dimensions, but GeoMedia will only work with 2-D spatial indexes.

Spatial Filtering Spatial filtering is critical when using large datasets. The more limitations placed on the amount of data ed 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- filter and the finer second- 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 ed 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):

712


Using Oracle Connections GeoMedia Filter Type

Oracle Filter Type

Coarse Overlap

MDSYS.SDO_FILTER

Overlap

MDSYS.SDO_RELATE Mask: ANYINTERACT

Entirely Inside

MDSYS.SDO_RELATE Mask: INSIDE

Inside

MDSYS.SDO_RELATE Mask: INSIDE+COVEREDBY+EQUAL

Coarse Overlap is the fastest performing filter because it uses Oracle‘s single 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 ed to Oracle‘s SDO_RELATE operator in a bind variable. SDO_RELATE uses a two- filter and produces results that are more accurate. 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 Oracle‘s 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:  Topology Engine – GeoMedia and Oracle use completely different topology algorithms.  Client versus Server – Spatial queries in GeoMedia operate completely on the client, while native queries run on the server. This is an advantage if the data is quite large and you want to leverage the server‘s power for the processing stage.  Distinct Results – GeoMedia‘s spatial queries use a DISTINCT operator that ensures that results are not redundant. For example, you have a warehouse consisting of a single County feature class that entirely contains three River feature classes. When GeoMedia performs a spatial query on all the counties that entirely contain rivers, the process returns one county. The same native spatial query would return three counties, one for each of the three rivers, even though it is the same county being returned each time. Both answers are correct. GeoMedia just returns what is required to display the result while Oracle returns the numeric result. 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.


713

Using Oracle Connections 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.

GeoMedia‘s GDOSYS Metadata Schema GeoMedia Professional uses a metadata schema called GDOSYS. For read-only connections, a GDOSYS schema is not required, but it is recommended (for coordinate systems). For read-write connections, the GDOSYS must exist in the Oracle database instance and must contain the set of required metadata tables. GeoMedia‘s Object Model Data Server uses GDOSYS.GALIASTABLE to determine if the GDOSYS schema is to be used. If GALIASTABLE is found during the initial connection, all tables and views in the schema will require appropriate entries in the GDOSYS metadata tables even if the schema is read-only.

Creating the GDOSYS Schema The GDOSYS metadata schema is created in your Oracle instance by a SQL script that is accessed via GeoMedia Professional‘s Database Utilities. To create GDOSYS, you need to connect to your database as the DBA using Database Utilities and run the Create Metadata Tables command. This only needs to be done once per Oracle instance. Make sure you use a net service (host) name when connecting even if the database instance is local. If you do not use the net service name, GDOSYS will not be created and no warning message will be issued. For best results, you should put GDOSYS in its own tablespace. You can also use Database Utilities to update GDOSYS to the current version. Connect as a DBA and select the Create Metadata Tables button. Because GDOSYS already exists, the process verifies the schema and updates it as necessary. The current GDOSYS is backward compatible to GeoMedia Professional 5.2; however, you must update GDOSYS with every new release of GeoMedia Professional. Oracle DBA‘s can use the CreateGDOSYS.sql script in the ..GeoMedia Professional/Scripts folder to manually create the GDOSYS schema. The script will need to be run from SQL*Plus while connected as a system DBA. The syntax of the create metadata script is: @CreateGDOSYS <_tablespace> where:  is the to use for the GDOSYS .  is the profile to use when creating the .  <_tablespace> is the tablespace where the schema will be created.  is the temporary tablespace to use. For example: @CreateGDOSYS GDOSYS DEFAULT S 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.

714



The Default GDOSYS Schema Definition Whether you use the scripts or Database Utilities to create the GDOSYS metadata schema, the following objects are created: GDOSYS Object

Type

ATTRIBUTEPROPERTIES

Table

FIELDLOOKUP

Table

GALIASTABLE

Table

GCOORDSYSTEM

Table

GEOMETRYPROPERTIES

Table

GEXCLUSIONS

Table

GFEATURES

View

GFEATURESBASE

Table

GFIELDMAPPING

Table

GINDEXCOLUMNS

Table

GPARAMETERS

Table

GPICKLISTS

Table

GQUEUE

View

GQUEUEBASE

Table

LIBRARYTABLES

Base

LIBRARYTABLESBASE

Table

MODIFIEDTABLES

Table

MODIFICATIONLOG

Table

GMODLOG

Sequence

GAUTONUMBERSEQUENCE

Sequence

FIELDLOOKUPINDEXID1

Sequence

DELETEMETADATAGMT

Trigger


715


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:

  

 



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. FIELDDESCRIPTION – A -provided description of the column. FIELDTYPE – Determines how GeoMedia applications interpret the data type used in the column definition (based on the data type matching table listed earlier). Available field type values are: 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 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 ‘s schema. These identifiers are then used by other metadata tables. The definition of the table is:



716

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 through GALIASTABLE. It is the only table required to be in GDOSYS. If a given sees the GDOSYS.GALIATABLE, that will require metadata for all tables that will be exposed as feature classes in GeoMedia. The definition of this table is:

 

TABLETYPE – GeoMedia‘s required name. TABLENAME – Actual metadata table name as stored. The table names in this field must be in the format OWNER.TABLE.

One mechanism for allowing different s 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 name so that each 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 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 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 -provided description of the coordinate system.  The other attribute fields in GCOORDSYSTEM are not editable and should not be modified in any way. Coordinate systems should be created through the GeoMedia Professional Define Coordinate System command. When a defined coordinates system is assigned to a feature class, the parameters that make up the coordinate system are inserted into the database table. Any feature class that uses the coordinate system is assigned the CSGUID for that coordinate system. Coordinate systems are defined on a per-feature-class basis. Each feature class can have its own coordinate system. The easiest way to assign a coordinate system to a feature class is by using the Database Utilities, which are available in the GeoMedia Professional program group.


717

Using Oracle Connections If you have incorrectly assigned a coordinate system to a feature class, you can also use the Database Utilities to correct the assigned coordinate system. See the section on “Database Utilities.” GDOSYS.GCOORDSYSTEM stores all of the coordinate systems used by all feature classes in all schemas in the Oracle instance. This allows any with the proper privileges to access and to display geometry data from any schema. Because all coordinate systems are available, you may find it useful to designate a default coordinate system for each schema to use. Default coordinate systems can be assigned using Database Utilities or the Feature Class Definition command. Only one default coordinate system is allowed per schema. The CSGUID of the default coordinate system is stored in the GDOSYS.GPARAMETERS table along with the schema name. It is a good practice to always set a default coordinate system. 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.

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:





 

 

718

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 (True) means the geometry column is the primary geometry. All other geometry columns in the feature class should be assigned 0 (False). Only one primary geometry field is allowed. 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. GCOORDSYSTEMGUID – This field contains the CSGUID from the GCOORDSYSTEM table. It tells the data server what coordinate system is assigned to the geometry. Each geometry column can be assigned a different coordinate system if required. FIELDDESCRIPTION – This field is a -provided description of the column. INDEXID – This key field links the information to the actual column defined in the FIELDLOOKUP table.



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 has privileges to see will be scanned for compatibility. The more schemas that are available to the connected , the longer the connection takes. This is one reason it is not recommended to connect as a 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:

 

OWNER – Schema name to exclude. EXTYPE – Specifies what type of exclusion to make. Setting EXTYPE to 'A' will exclude all views and tables from this schema. Setting the EXTYPE to 'V' will exclude only views, but will include tables.

GFEATURES and GFEATURESBASE GFEATURES is a view on GFEATURESBASE. The GFEATURESBASE metadata table stores the names of all tables and views available to GeoMedia applications as feature classes. GFEATURES is used to populate the Add Legend Entries dialog box in GeoMedia with those feature classes that are available to the connected . GFEATURESBASE is defined as:

 

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.  PRIMARYGEOMETRYFIELDNAME – This field is the name of the primary geometry column.  FEATUREDESCRIPTION – This field is a -provided description of the column. The definition of the GFEATURES view is as follows:


719

Using Oracle Connections SELECT * FROM GDOSYS.GFEATURESBASE WHERE EXISTS (SELECT 1 FROM ALL_OBJECTS WHERE OWNER=SUBSTR(FEATURENAME,1,INSTR(FEATURENAME,'.',1)-1) AND OBJECT_TYPE IN ('TABLE','VIEW') AND OBJECT_NAME=SUBSTR(FEATURENAME,INSTR(FEATURENAME,'.',1)+1)); This view only serves up the feature classes that the connected has privileges to select. All other feature classes are hidden. You can set up the GFEATURES view as you see fit; however, it must return the same columns as the GFEATURESBASE table. If you are using only one GeoMedia warehouse or want to expose all GeoMedia feature classes to all s, you do not need to use the view; simply rename GFEATURESBASE to GFEATURES. An alternate GFEATURES view definition is delivered in the …\GeoMedia Professional\Scripts folder (NewGFeaturesView.sql). This view definition can improve query performance for GFEATURES, particularly for the GeoMedia Transportation products. The new view is not required. A with DBA privileges is required to run the script.

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:

   

OWNER – This field is the owner of the table or feature class. TABLE_NAME – This field is the name of the table or feature class. COLUMN_NAME – This field is the column in the table that this information apples to. DATA_TYPE – This field is determines how GeoMedia interprets the data type used in the column definition. Field type values include: 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 See the “GeoMedia Type Mapping” section for more information on what data types to use here.

720


Using Oracle Connections 

  

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. SEQUENCE_NAME – This field is the name of the sequence assigned to 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:

OWNER – This field is the owner of the view. OBJECT_NAME – This field is the name of the view. INDEX_NAME – This field is the primary or unique key index name from the base table. The key must be included in the view definition and be key preserved.  INDEX_TYPE – This field is the type of the index, ‗P‘ for primary, ‗U‘ for Unique.  COLUMN_NAME – This field is the name of the column in the view that will use the index in INDEX_NAME. The index name is just a place holder and does not reflect an actual index.  COLUMN_POSITION – This field is the position of the key column as defined in the view. 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.   


721


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.

The default GPARAMETER values for the Oracle Object Model Data Servers are the following: GParameter

Type

Default GValue

Comments

SpatialIndexLevel

Long

1

Tessellation (Index) Level

NumberOfTiles

Long

1

Maximum Number of Tiles

MaxLevel

Long

1

Maximum Level (for Hybrid)

X_LowerBound

Double

-2147483648

X Minimum of MBR

X_UpperBound

Double

2147483647

X Maximum of MBR

X_Tolerance

Double

.00005

X1=X2 if |X1-X2| < X_Tolerance

Y_LowerBound

Double

-2147483648

Y Minimum of MBR

Y_UpperBound

Double

2147483647

Y Maximum of MBR

Y_Tolerance

Double

.00005

Y1=Y2 if |Y1-Y2| < Y_Tolerance

Z_LowerBound

Double

-2147483648

Z Minimum of MBR

Z_UpperBound

Double

2147483647

Z Maximum of MBR

Z_Tolerance

Double

.00005

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: <> .DEFAULTCOORDINATESYSTEM GVALUE:

722



GPICKLISTS The GPICKLISTS metadata table contains the Pick Lists assignments 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:

   



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 data type of the field in the Pick List table specified here must match the data type 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.

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 a 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 ed. It is up to the DBA to populate the PickList metadata table with the appropriate entries for the various schemas containing feature classes. The following is an example of using Pick Lists: GDOSYS.GPICKLISTS FEATURENAME

FIELDNAME

PICKLIST TABLENAME

VALUE FIELDNAME

DESCRIPTION FIELDNAME

FILTERCLAUSE

OWNER.BUILDINGS

NAME

OWNER.PL_BUILDING

CODE_VALUE

VAL_DESCRIPTION

BLD_TYPE = 'NAME'

OWNER.BUILDINGS

STATE

OWNER.PL_STATE

STATE_NAME

DESC

OWNER.BUILDINGS

TYPE

OWNER.PL_BUILDING

CODE_VALUE

VAL_DESCRIPTION


BLD_TYPE = 'TYPE'

723

Using Oracle Connections OWNER.PL_BUILDING CODE_VALUE

VAL_DESCRIPTION

BLD_TYPE

0

MOTEL

TYPE

1

MARRIOT

NAME

2

HOLIDAY INN

NAME

3

BED AND BREAKFAST

TYPE

4

DAYS INN

NAME

OWNER.PL_STATE STATE_NAME

DESC

ALABAMA

ALABAMA

ARKANSAS

ARKANSAS

COLORADO

COLORADO

TEXAS

TEXAS

FLORIDA

FLORIDA

GQUEUE and GQUEUEBASE GQUEUEBASE stores the static queue information used by the Queued Edit command in GeoMedia Professional. The GQUEUEBASE table stores information about all static queues used by the schemas in the database instance. The columns in GQUEUEBASE are populated through commands in GeoMedia and are used solely by the Queued Edit command. This table is not editable. The table definition is provided for information only.

The Queued Edit process accesses GQUEUEBASE through a view called GQUEUE that is defined as follows:

724


Using Oracle Connections 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 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 that needs to create static queues must have SELECT, INSERT, UPDATE and DELETE privileges on both GQUEUEBASE and GQUEUE. s who review static queues will require SELECT privilege on both GQUEUEBASE and GQUEUE.

LIBRARYTABLES and LIBRARYTABLESBASE LIBRARYTABLESBASE is similar to the GALIASTABLE and contains a list of the library table types and their associated table names in the format of owner.table. This table is not editable and the table definition is provided for information only.

The Library process accesses LIBRARYTABLESBASE through a view called LIBRARYTABLES that is defined as follows: CREATE OR REPLACE VIEW LIBRARYTABLES AS SELECT TABLETYPE, TABLENAME FROM GDOSYS.LIBRARYTABLESBASE WHERE EXISTS (SELECT 1 FROM all_objects WHERE owner = (SELECT FROM DUAL) AND owner||'.'||object_name = TABLENAME); This view ensures that the sees only the library tables in the schema they are directly connecting to.


725


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. 

726



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:

MODIFICATIONNUMBER – This field contains values from the GMODLOG sequence and is automatically incremented as edits are made  TYPE – This field tracks the type of edit made to the data. The types used are 1 for insert, 2 for update and 3 for delete.  MODIFIEDTABLEID – This field contains the OBJECT ID for the tables and views that will be tracked in the MODIFICATIONLOG table. The MODIFIEDTABLEID is the common link between MODIFICATIONLOG and MODIFIEDTABLES.  SESSIONID – This field Oracle session identifier.  MODIFIEDDATE – This contains the system date when the modification was made.  KEYFIELD1-KEYFIELD16 – KEYFIELD1 contains the primary key value for the row where the edit has occurred. If a multi-column primary key is used then the other KEYFIELDs will store the values for the other components of the primary key. 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 these tables: TRUNCATE TABLE GDOSYS.MODIFICATIONLOG; ........TRUNCATE TABLE GDOSYS.MODIFIEDTABLES; 


727

Using Oracle Connections 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'; EXECUTE IMMEDIATE 'TRUNCATE TABLE GDOSYS.MODIFIEDTABLES'; 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. For best results, run this in a nightly maintenance window. 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:  GMODLOG – Sequence for the MODIFICATIONNUMBER field in the MODIFICATIONLOG table.  GAUTONUMBERSEQUENCE – Sequence used to generate a unique identifier when generating sequences for autonumber fields through the Feature Class Definition command.  FIELDLOOKUPINDEXID1 – Sequence for the field INDEXID in the FIELDLOOKUP table.

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 _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 Oracle‘s 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;

728


Using Oracle Connections BEGIN SELECT COUNT(1) into v_EXIST FROM _SDO_GEOM_METADATA WHERE TABLE_NAME = sys.dictionary_obj_name; IF v_EXIST >0 THEN DELETE FROM _SDO_GEOM_METADATA WHERE TABLE_NAME = sys.dictionary_obj_name; END IF; END; /

Metadata Table Relationships The metadata tables in the GDOSYS schema are related to each other in specific ways. Direct relationships are listed as follows:  GCOORDSYSTEM.CSGUID = GFIELDMAPPING.CSGUID = GEOMETRYPROPERTIES.GCOORDSYSTEMGUID  GEOMETRYPROPERTIES.INDEXID = ATTRIBUTEPROPERTIES.INDEXID = FIELDLOOKUP.INDEXID  FIELDLOOKUP.FEATURENAME = GFEATURES.FEATURENAME  MODIFIEDTABLES.MODIFIEDTABLEID= MODIFICATIONLOG.MODIFIEDTABLEID The following are indirect and implied relationships:  The OWNER/TABLE_NAME in the GFIELDMAPPING table corresponds to the FEATURENAME column in the client metadata tables (FIELDLOOKUP and GFEATURES).  The COLUMN_NAME in the GFIELDMAPPING table corresponds to the FIELDNAME column in other metadata tables. 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.

Using Database Objects s and Privileges As a DBA, you have a lot of latitude in the creation of s in Oracle. What privileges you assign to the is dependent on what purpose the will serve. A typical is created using the following syntax: CREATE <> PROFILE "DEFAULT" IDENTIFIED BY DEFAULT TABLESPACE S TEMPORARY TABLESPACE TEMP UNLOCK; where <> is the name you want to create and is the for that . If this is the that will contain the spatial data, tables, views and other objects, you will need to assign specific privileges to give the that capability. The following privileges are just an example:


729

Using Oracle Connections GRANT UNLIMITED TABLESPACE TO <>; GRANT CONNECT TO <>; GRANT RESOURCE TO <>; GRANT CREATE TABLE TO <>; GRANT CREATE SEQUENCE TO <>; GRANT MERGE ANY VIEW TO <>;  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 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 must be granted explicitly. MERGE ANY VIEW allows the optimizer to improve query performance and is essential when dealing with spatial data. You can also handle this at the database level by setting the initialization parameter OPTIMIZER_SECURE_VIEW_MERGING to FALSE. Two main rules apply to creation:  Never create a in the SYSTEM Tablespace. Typically, a is created in the tablespace with temporary storage in TEMP. The actual tablespace used is up to the DBA.  Never assign the DBA role to a master or satellite if you plan to use it with GeoMedia. The DBA role can have serious performance implications for GeoMedia connections. Satellite s generally contain no database objects. They exist to allow a specific varying degrees of privilege on the master schema, which hold the database objects (tables, views, and so forth.). All s 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 and Schema – Schema objects can only be created by master .  – Has full control of master schema.  GRANT ALL on all database objects in GDOSYS.  GRANT ALL privileges on the master schema.  Viewing – Has read-only access to all objects.  SELECT on all GDOSYS objects.  SELECT on all master schema objects.  Editing – Has edit capability on some feature classes but not others and cannot remove or delete data. Cannot create objects.  Grant INSERT and UPDATE on GDOSYS‘s MODIFIEDTABLES AND MODIFICATIONLOG  Grant INSERT and UPDATE on GDOSYS‘s GQUEUE AND GQUEUEBASE so the can create and modify static queues in GeoMedia.  INSERT and UPDATE on all read-write tables and sequences in master schema. Add DELETE for the ability to delete data.

730



Tables Tables can be created using GeoMedia Professional‘s 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 data type. 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 SDO_GEOMETRY, GEOM2 SDO_GEOMETRY); 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 Oracle‘s ALTER table command: ALTER TABLE STATES ADD (GEOMETRY 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.


731


Views and -Views GeoMedia Professional makes no distinction between views and tables; it treats a view just like any other feature class. The Oracle Object Model data server handles read-write access to most types of views. Names of views are always expressed in uppercase. For views to be updatable in GeoMedia Professional, they must come from a table that is key-preserved. Only key-preserved tables can be updated through a view. One way to ensure this is true is to include a primary key as part of the view definition, which preserves the key‘s status in the view. In a -view, the primary key can come from either the left or the right side as long as it retains its key status. It cannot come from both sides of the and still be updatable. In addition, only the side of the containing the key will be updatable. To determine whether a view/-view is updatable or not, you can check the Oracle view _UPDATABLE_COLUMNS: SELECT * FROM _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 _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. Multi-column primary keys are allowed. 2. Update _SDO_GEOM_METADATA – All views that contain a column of type SDO_GEOMETRY need to have an entry in Oracle's spatial metadata view _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. For insert operations, GeoMedia must populate the primary key value itself; it cannot be populated through a trigger. To force this, assign the data type 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 -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 views. For more information, refer to Oracle's documentation on modifiable -views. If you need to have full edit capability on your views, you need to make use of ‗instead of’ triggers. The following is an example of a -view that has a relation between a graphic feature class (PARCEL_GEOM) and a non-graphic feature class (PARCEL_INFO):

732


Using Oracle Connections 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 -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. GeoMedia must be able to populate this pseudo key field in order to perform inserts. This can be done manually or by changing the data type of the key field to autonumber and using the sequence assigned to the base table. Use Database Utilities for sequence assignments. When you insert, 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 view‘s 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= ')='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.


733


Modification Logging GeoMedia Professional automatically records insert, update, and delete operations on features in the GDOSYS‘s 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 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 table‘s 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 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 IF :NEW.ID IS NULL THEN SELECT STATES_ID_SEQ.NextVal INTO :NEW.ID FROM dual; END IF; END; /

734


Using Oracle Connections 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 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 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 views. , 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 data type 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 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 s. 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. To use Database Utilities to create the GDOSYS schema, you will need to 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 as the who owns the schema if that 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.


735


Using an Existing Oracle Spatial Schema If you already have data in an Oracle schema that you want to utilize within the GeoMedia environment, you need to ensure the following:  The Oracle 10g Client software has been loaded, and a host has been configured using Oracle‘s Network Configuration Utility.  The database schema resides in Oracle 9.2 or later.  _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. For read-only connections, you will also need to ensure that:  The GeoWorkspace coordinate system used to view the data is in the same coordinate system as the data. For read-write connections, you will also need to ensure that:  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 _SDO_GEOM_METADATA has been populated with the correct values. Use the following SQL to see if there are existing entries: SELECT * FROM _SDO_GEOM_METADATA; If there are no entries, you will need to create them. The simplest way is to just insert the default range: INSERT INTO _SDO_GEOM_METADATA VALUES ('STATES','GEOMETRY', 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); INSERT INTO _SDO_GEOM_METADATA VALUES ('COUNTIES,'GEOMETRY', 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); COMMIT; 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;

736


Using Oracle Connections These feature classes are now ready for display in GeoMedia Professional through a read-only 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 ). 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. 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 asg 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.

Creating a New GeoMedia Warehouse in Oracle To create a new warehouse in Oracle for GeoMedia to use, you will first need to create the GDOSYS schema. This is outlined above in Steps 1-3 and requires DBA privileges on the database. After GDOSYS is created, your DBA needs to create a in Oracle that will hold the spatial object tables. Then use one of the following to load and use the data:  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 _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.


737

Using Oracle Connections 



738

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.


APPENDIX C

Using SQL Server Connections GeoMedia Professional provides a SQL Server data server that facilitates connections to Microsoft‘s Sequel Server (SQL Server) databases. This allows GeoMedia applications to use SQL Server databases as geospatial warehouses. The SQL Data Server is delivered in two variations – as a read-only data server and as a read-write data server. These are accessed through the New Connection command. This appendix applies to both variations.

Delivery and Connection Prerequisites SQL Server connections do not require client software. The SQL Server data server will be installed whether SQL Server is present or not. Connections can be made to SQL Server installations that are configured as case-sensitive or case-insensitive. Both Windows authentication and SQL Server authentication are ed for s. A SQL Server database must already exist and must have the required metadata tables before a SQL Server Read-Write or Read-Only connection can be made. The SQL Server data server is built on OLEDB and must have the latest version installed. This is automatically done for you if you are using Windows XP or later.

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 Professional‘s Export to SQL Server command) or by using GeoMedia Professional‘s Database Utilities. See the “GeoMedia Metadata Requirements” section of this appendix for a list of the required tables. To make a connection to SQL Server, provide a valid server name, and then a valid name and . Any databases the specified has privilege to see will appear in the drop down database list. SQL Server has two modes for validating s: Windows domain authentication and SQL Server authentication. If the SQL Server connection is set to use Windows authentication (the default), your domain will need to be added to SQL Server by a database 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. If you are using SQL Server authentication, you will need to have a valid SQL Server and as well as the appropriate privileges on the database you want to connect to.

Persistence When using SQL Server authentication, GeoMedia stores the SQL Server connection in the GeoWorkspace. This is meant as a convenience and allows s to open existing GeoWorkspaces containing SQL Server connections without having to re-enter connection s. However, this is a drawback to those s wanting higher levels of security. If you do not want the s to be persisted in the GeoWorkspace, you must use domain


739

Using SQL Server Connections authentication. Domain authenticated connections do not store any or information in the GeoWorkspace and have the added benefit of not prompting you to re-enter s.

Permissions In SQL Server warehouses, access to database objects is controlled by the object‘s 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 who created them. When creating database objects using GeoMedia Professional‘s Feature Class Definition command, the must be assigned the db_owner role. For database objects created outside of GeoMedia Professional, only a with the role db_owner will ensure that the resulting objects are owned by DBO. s that need read access should be assigned the db_datareader role. s 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.

SQL Server Warehouse Requirements Connections to SQL Server warehouses have several restrictions and requirements that must be adhered to. Violation of any of these requirements may lead to a connection failure or the inability to load data from the connection. Connection requirements and restrictions are listed below:  All SQL Server database objects must be owned by DBO. s 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.





 

 

740

Comparisons on data values will be case-sensitive, so caution is advised when identifier names are stored in the database. 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 Server‘s TIMESTAMP data type. This data type is not related to date/time functions and is not ed. A list of ed data types is presented in the SQL Server data model section. Data types that do not appear in the list are not ed. 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. Edit operations on -views will require the use of instead of triggers. 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.


Using SQL Server Connections

Data Storage and Type Matching Geometry Storage When you use the Feature Class Definition command to create a table that will contain spatial data in SQL Server, GeoMedia Professional creates the following five columns in which to store the geometry:  _XLO float(8)  _YLO float(8)  _XHI float(8)  _YHI float(8)  varbinary(max) or image(16) The 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 a different name from Geometry. In SQL Server 2000, the data type of the geometry column was image(16). This data type has been de-ed in SQL Server 2005, and the new preferred geometry data type is varbinary(max). Legacy datasets can still use image(16), but behind the scenes they are being interpreted as the new data type. 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 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 data type 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 Professional‘s 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


741

Using SQL Server Connections 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.

SQL Server to GeoMedia Data Type Matching In order to utilize data from SQL Server, GeoMedia‘s SQL Server data server converts SQL Server data types to GeoMedia data types. The following table shows how the SQL Server data types are mapped to the GeoMedia types. Any data types missing from this list are considered uned and are ignored. SQL Server Data Type

GeoMedia Data Type

binary image

LongBinary

bit

Boolean

char(size) varchar(size) nchar(size) nvarchar(size) ntext*

Text if size <= 255 Memo otherwise

datetime smalldatetime

Date

decimal(p,s) or numeric(p,s) p is precision s is scale

Integer if s = 0 and p < 6 Long if s = 0 and p >= 6 and p < 11 Double for all other cases.

float

Double

int

Long

money

Currency

real

Single

smallint

Integer

tinyint

Byte

uniqueidentifier

Guid

varbinary

LongBinary

*Memo only

GeoMedia to SQL Server Data Type Matching The following table identifies the mapping used when converting from GeoMedia‘s data types to SQL Server data types and whether specific metadata is required for the mapping:

742

GDO Field Type

SQL Field Type

Required Metadata

Boolean

bit

No

Byte

tinyint

No


Using SQL Server Connections GDO Field Type

SQL Field Type

Required Metadata

Integer

smallint

Yes for autonumber

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

GeoMedia Metadata Requirements GeoMedia applications require specific metadata tables to exist in the SQL Server database before a connection can occur. The metadata contains information about both the attribute and geometry tables stored in the database. The following table lists the required metadata tables/views. GeoMedia Metadata Objects

Type

AttributeProperties

Table

FieldLookup

Table

GAliasTable

Table

GCoordSystem

Table

GeometryProperties

Table

GFeatures

Table

GFieldMapping

Table

GIndexColumns

Table

GParameters

Table

GPickLists

Table

GQueue

Table

GTileIndexes

Table

ModifiedTables

View

ModificationLog

Table


743

Using SQL Server Connections 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 as the database owner (or ) 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. 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. IsFieldDisplayable – Determines whether a column is displayed in GeoMedia Professional. The default value is -1 for TRUE. Use 0 (FALSE) to hide the column. FieldType – Determines how GeoMedia interprets the data type used in the column definition. These are based on the conversion from SQL Server to GeoMedia data types. Typical field type values include: 1 – Boolean



 

744

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 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. FieldFormat – Determines the general format of the data being displayed. Format types include General Number, Date/Time, and Currency. FieldDescription – A -provided description of the column.



FieldLookup The FieldLookup metadata table provides a unique identifier (IndexID) for every column in every table (feature class) in the ‘s 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.  FeatureName – The table name.  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. 

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 hard-coded. 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 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 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.  Description – A -provided description of the coordinate system. This is optional.  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 systems should be created by means of the GeoMedia or GeoMedia Professional Define Coordinate System command. When a defined coordinates system is assigned to a feature class, the parameters that make up the coordinate system are inserted into the database table. Any feature class that uses the coordinate system is assigned the CSGUID for that coordinate system. Coordinate systems are defined on a per-feature-class basis. Each feature class can have its own coordinate system. Feature classes are assigned a coordinate system when they are created using the Feature Class Definition command. Outside of GeoMedia Professional, you will need to use the Database Utilities command, which is available in the GeoMedia


745

Using SQL Server Connections Professional program group. If you have incorrectly assigned a coordinate system to a feature class, you can also use the Database Utilities to correct the assigned coordinate system. See “Database Utilities” in this appendix. If you plan to use multiple coordinate systems in your SQL Server warehouse, you need to assign one coordinate system to use as a default. Default coordinate systems can be assigned using Database Utilities or Feature Class Definition. Only one default 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 s.

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:

 



 

746

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: 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. FieldDescription – A -provided description of the column.



GFeatures The GFeatures metadata table stores the table names of all 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

-1 – The feature class has no geometry field. PrimaryGeometryFieldName – The name of the primary geometry column. FeatureDescription – A -provided description of the column.

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:

   

TABLE_NAME – The name of the table. COLUMN_NAME – The column in the table that this information apples to. The TABLE_NAME/COLUMN_NAME combination makes up the primary key. DATA_TYPE – Determines how GeoMedia interprets the data type used in the column definition. Field type values include the following types (these are derived from the SQL Server to GeoMedia data type matching table): 1 – Boolean

8 – Date

2 – Byte

10 – Text

3 – Integer

11 – Binary


747




 

4 – Long

12 – Memo

5 – Currency

15 – GUID

6 – Single

32 – Spatial geometry

7 – Double 33 – Graphic geometry DATA_SUBTYPE – Used when the DATA_TYPE is 32 or 33; the subtype determines the graphic type: 1 – Line

2 – Area

3 – AnySpatial

4 – Coverage

5 – GraphicsText 10 – Point CSGUID – The coordinate system assigned to the primary geometry field. AUTOINCREMENT – A Boolean field indicating that the field is set to auto-increment. Use -1 from True.

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:

     

 

748

The primary key is a combination of the OBJECT_SCHEMA, OBJECT_NAME, INDEX_NAME, and COLUMN_NAME fields. OBJECT_SCHEMA – The owner of the view (the default is 'dbo'). OBJECT_NAME – The name of the view. 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 read-only. 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 ed. Only triggers can notification in this case.


Using SQL Server Connections 



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 ed. Only triggers can notification in this case. BASE_COLUMN_NAME – This field is the name of the corresponding field of the base table/view. This field is used for name aliasing. If this field is missing or contains NULL (empty string), name aliasing is not ed.

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.

This table contains two fields, GPARAMETER and GVALUE. Currently, the following values are used by default:

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:



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.


749

Using SQL Server Connections  

PickListTableName specifies a table in the schema containing the PickList values. ValueFieldName and DescriptionFieldName refer to the name of the fields in the table containing the PickList values.  The ValueFieldName specifies the field in the PickList table that contains the values to be stored in the database. The data type of the field in the PickList table specified here must match the data type of the attribute assigned in the FieldName.  The DescriptionFieldName specifies the field that contains PickList descriptions to be displayed in the pop-up menu on the Properties dialog box.  The values stored in ValueFieldName and DescriptionFieldName could be the same when the displayed values are the same as the stored values.  The FilterClause is optional and may contain a 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 ed. 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: GPickLists FEATURENAME

FIELDNAME

PICKLIST TABLENAME

VALUE FIELDNAME

DESCRIPTION FIELDNAME

FILTERCLAUSE

BUILDINGS

NAME

PL_BUILDING

CODE_VALUE

VAL_DESCRIPTION

BLD_TYPE = 'NAME'

BUILDINGS

STATE

PL_STATE

STATE_NAME

DESC

BUILDINGS

TYPE

PL_BUILDING

CODE_VALUE

VAL_DESCRIPTION

BLD_TYPE = 'TYPE'

PL_Building CodeValue

ValDescription

Bld_Type

0

MOTEL

TYPE

1

MARRIOT

NAME

2

HOLIDAY INN

NAME

3

BED AND BREAKFAST

TYPE

4

DAYS INN

NAME

PL_State

750

StateName

Desc

Alabama

ALABAMA

Arkansas

ARKANSAS

Colorado

COLORADO

Texas

TEXAS

Florida

FLORIDA


Using SQL Server Connections A separate application called PickList Manager is available from Intergraph Customer that can assist DBAs in configuring and using PickList tables. For more information, visit the link http://.intergraph.com/.

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 editable. The table definition is provided for information only.

ModifiedTables ModifiedTables is a view that provides the object id for each table/view. The view uses an inner 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.


751


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:

ModificationNumber – The auto-increment key filed for the table. Type – The type of edit that has occurred; 1 for insert, 2 for update, 3 for delete. ModifiedTableID - The column identifier from ModifiedTables. 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    

You could also set up a SQL Server job to do this automatically; just make sure it runs when there are no active GeoMedia sessions.

752


Using SQL Server Connections 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 modification logging 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:  Type is populated with the following constants: 1 - Insert, 2 – Update, or 3 – Delete.  ModifiedTableID is populated with the object ID of the object for which the entry is created. This field comes from the ModifiedTables view.  KeyValue1 to KeyValue10 are populated by converting the primary key value to nvarchar(255). If the primary key is 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 DECLARE @TableID INT if object_id('tempdb..#DisableModificationLog') is null SELECT @TableID=id FROM SYSOBJECTS WHERE name='States' BEGIN IF UPDATE([ID]) INSERT INTO ModificationLog([Type], [ModifiedTableID],KeyValue1) SELECT 2, convert(nvarchar(20),@TableID), convert(nvarchar(255), deleted.[ID]) FROM deleted INSERT INTO ModificationLog([Type], [ModifiedTableID],KeyValue1) SELECT 2, convert(nvarchar(20),@TableID), convert(nvarchar(255), inserted.[ID]) FROM inserted END GO


753


CREATE TRIGGER [dbo].[StatesGMTD] ON [dbo].[States] FOR DELETE 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 3, convert(nvarchar(20),@TableID), convert(nvarchar(255), deleted.[ID]) FROM deleted GO To make this work with views, you would need to add an entry to the base table trigger that handled the modification to the view as well. 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].[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' INSERT INTO ModificationLog([Type], [ModifiedTableID],KeyValue1) SELECT 1, convert(nvarchar(20),@ViewID), convert(nvarchar(255), inserted.[ID]) FROM inserted GO Then you need to create a dummy trigger using the view name so GeoMedia does not also write an entry to the ModificationLog: 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' GO Note that the trigger itself is still on the base table States; it is only the name of the trigger that refer to the view. 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 views, you will need to take into all the base tables and associated views. In the case of 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.

754



Working with SQL Server Importing Data The easiest way to get started using the SQL Data Server is by bulk importing data from another data source. GeoMedia Professional has two commands that will move data to SQL Server warehouses, Export to SQL Server and Output to Feature Classes. Export to SQL Server creates a set of files and an import.bat script that will load a SQL Server database from any data source that GeoMedia Professional is connected to. The process will use the coordinate system of the workspace for the output. The resulting export files use SQL Server‘s B command to load the data. For this reason, imports can only be run on a SQL Server istrative Client or on the system where SQL Server is installed. This method is very fast and is ideal for bulk loading large amounts of data (>100000 rows). Output to Feature Classes requires that metadata already exist in the target SQL Server database. To manually create the metadata, use GeoMedia Professional‘s Database Utilities and to the new database using a DBO like sa. When you click Insert Feature Class Metadata, Database Utilities will detect the absence of metadata tables and will prompt you to create them automatically. Once the metadata is created, you will be able to connect to the warehouse through GeoMedia Professional. Output to Feature Classes is very flexible and allows you to make modifications to the table/column definition, key definitions, and coordinate system assignments. The drawback is in performance, this command is considerable slower than Export to SQL Server. It is best used for smaller datasets (<100000 rows).

Feature Class Definition The Feature Class Definition command from within GeoMedia Professional works the same as it does with other read-write data servers. You can add tables and columns and edit existing tables and columns as long as the you are connected with has the correct permissions. Just , if a non-owner creates tables, they will only be accessible to the that created the tables. For best results, create tables while connected as the database or database owner. When it comes to editing tables, consider the following items:  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 Server‘s 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.


755


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- 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.

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 es. The first 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 filter is ed to the client and processed locally. This second 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.

756


Using SQL Server Connections For example: CREATE INDEX Parcel_SIDX ON [dbo].[Parcels] ([Geometry_XLO] desc , [Geometry _YLO] desc , [Geometry _XHI] desc , [Geometry _YHI] desc ) WITH DROP_EXISTING ON [PRIMARY]

Views and Views GeoMedia Professional makes no distinction between views and tables; it treats a view just like any other feature class. The SQL Server data server handles read-write access to most types of views. For views to be updatable in GeoMedia Professional, they must come from a table that is key-preserved. Only key-preserved tables can be updated through a view. One way to ensure this is true is to include a primary key as part of the view definition, which preserves the key‘s status in the view. In a -view, the primary key can come from either the left or the right side as long as it retains its key status. It cannot come from both sides of the and still be updatable. In addition, only the side of the containing the key will be updatable. For a view to be treated as a spatial feature class, you must make sure that the five required Geometry columns are part of the view definition. You will also need to use Database Utilities to add to the appropriate metadata for all of the views you create. This needs to occur for both spatial and non-spatial feature classes.

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:  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 such as sa or by any other 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.  To assign a default coordinate system to a new database or to re-assign coordinate systems for existing feature classes, use the Assign Coordinate System command. For existing feature classes, this command changes the coordinate system assignment without changing the data. Use discretion here; asg an incorrect coordinate system can cause problems when editing. Make sure the correct coordinate system is assigned.


757


758


APPENDIX D

Coordinate System Information This appendix contains information on the following items: 

Projection Algorithms



Ellipsoids



Datum Transformation Models



Units of Measure (UOM)



Standard Geodetic Datums



State Plane Zone Codes - NAD27 and Old Island Datums



Named Geodetic Datums



State Plane Zone Codes - NAD83 Datum



Vertical Datums



UTM Zones

Projection Algorithms Albers Equal Area ARC (Equal Arc-second Raster Chart/Map) Azimuthal Equidistant Bipolar Oblique Conic Conformal Bonne British National Grid Budapest Stereographic Cassini-Soldner Cylindrical Equirectangular Eckert IV EOV Equidistant Conic (Simple Conic) Gauss Conformal (South Africa) Gauss-Boaga (Italian zones) Gauss-Kruger (3-degree) Gauss-Kruger (6-degree) Gnomonic HR_HDKS Hungarian Oblique Cylindric HDR Hungarian Oblique Cylindric HER Hungarian Oblique Cylindric HKR Indonesian Polyhedric Japan Plane Rectangular (JGD2000) Japan Plane Rectangular (Tokyo) KKJ (Finnish zones) Krovak


Laborde Lambert Azimuthal Equal-Area Lambert Conformal Conic (1SP) Lambert Conformal Conic Local Space Rectangular Mercator Miller Cylindrical MK_TM Modified Polyconic (IMW Series) Mollweide New Brunswick Stereographic (ATS77) New Brunswick Stereographic (NAD83) New Zealand Map Grid New Zealand Transverse Mercator 2000 North Polar Stereographic Oblique Mercator Orthographic Polyconic RD (Amersfoort) Rectified Skew Orthomorphic Robinson RT 90 SI_TM Simple Cylindrical (Plate Carree) Sinusoidal South Polar Stereographic Spherical Mercator for Visualization

759

Coordinate System Information State Plane Coordinate System 1927 State Plane Coordinate System 1983 Stereographic SWEREF 99 Switzerland LV03 Switzerland LV95 Three-Step Stereographic

Transverse Mercator Undefined (Rectangular Grid) Universal Polar Stereographic Universal Transverse Mercator UTM with Easting Zone Prefix Van der Grinten

Datum Transformation Models Bursa-Wolf Canadian National Transformation (2.0) Complex Polynomial GEOID (NGS hybrid geoid) Molodensky (standard) Multiple Regression NADCON North American Datum 1927 to North American Datum 1983 (NGS Version 2.10) 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 -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

760


Coordinate System Information 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 -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: Geodetic Survey Division, Geomatics Canada Natural Resources Canada 615 Booth Street Ottawa, Ontario K1A0E9 CANADA Disclaimer by the Minister of Natural Resources (NRCan) for the Canadian National Transformation version 2.0 (NTv2) software: The NTv2, or any part thereof, is licensed on an "as is" basis and NRCan makes no guarantees, representations, or warranties respecting the NTv2, either expressed or implied, arising by law or otherwise, including but not limited to, effectiveness, completeness, accuracy or fitness for a particular purpose. NRCan shall not be liable in respect of any claim, demand, or action, irrespective of the nature of the cause of the claim, demand, or action alleging any loss, injury or damages, direct or indirect, which may result from Intergraph's, or Intergraph‘s clients‘, use or possession of the NTv2, or any part thereof. NRCan shall not be liable in any way for loss of profits or revenue, or any other consequential loss of any kind resulting from the Intergraph's, or Intergraph‘s clients‘, use or possession of the NTv2 or any part thereof. The Canadian National Transformation (version 2.0) has been adopted by the Intergovernmental Committee on Surveying and Mapping (ICSM) as the official high-accuracy transformation between the old Australian horizontal datums (AGD66 or AGD84, depending upon location) and the new official horizontal datum (GDA94). Grid files are published on the World Wide Web. The use of the Canadian National Transformation model for Australia has been included in the default entries in the autodt.ini configuration file. However, s 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, s will need to obtain the desired grid file from Land


761

Coordinate System Information 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: Area

Description

File Name

Alaska

Alaska, including Aleutian Islands

alaska

Alaska: St. George Island

Old island datum within Alaska

stgeorge

Alaska: St. Lawrence Island

Old island datum within Alaska

stlrnc

Alaska: St. Paul Island

O

stpaul

ld island datum within Alaska CONUS

Conterminous U.S. (lower 48 states)

conus

Hawaiian Islands

Old Hawaiian datum

hawaii

Puerto Rico and V.I.

Puerto Rico and Virgin Islands

prvi

Data used in the above files for NADCON datum transformations is selected on an area-by-area basis. For example, if you are performing a datum transformation within the U.S., data contained in the conus file is used in the transformation. However, the island datums of Alaska (St. Lawrence, St. George, and St. Paul) fall within the larger Alaska datum. When a point being transformed from NAD27 to NAD83 falls within multiple datums, the datum corresponding to the first file found in the list of file names in the …\cssruntm\cfg\nadcon\area.ini file is used. This is the default file list in area.ini: conus, prvi, stlrnc, stgeorge, stpaul, alaska, hawaii. To perform datum transformations for the three Alaska island datums using the Alaska datum instead of the island datums, the alaska entry must come before the island datum entries stlrnc, stgeorge, and stpaul. 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.

762


Coordinate System Information Grid files for going between NAD83 and HARN: Area

File Name

Alabama

alhpgn

American Samoa eastern islands

eshpgn

American Samoa western islands

wshpgn

Arkansas

arhpgn

Arizona

azhpgn

California above 37 deg. latitude

cnhpgn

California below 37 deg. latitude

cshpgn

Colorado

cohpgn

Florida

flhpgn

Georgia

gahpgn

Guam

guhpgn

Hawaii

hihpgn

Idaho – Montana east of –113 deg. longitude

emhpgn

Idaho – Montana west of –113 deg. longitude

wmhpgn

Illinois

ilhpgn

Kansas

kshpgn

Indiana

inhpgn

Iowa

iahpgn

Kentucky

kyhpgn

Louisiana

lahpgn

Maine

mehpgn

Maryland - Delaware

mdhpgn

Michigan (except Isle Royale)

mihpgn

Minnesota

mnhpgn

Mississippi

mshpgn

Missouri

mohpgn

Nebraska

nbhpgn

Nevada

nvhpgn

New England (CT, MA, NH, RI, VT)

nehpgn

New Jersey

njhpgn

New Mexico

nmhpgn


763

Coordinate System Information Area

File Name

New York

nyhpgn

North Carolina

nchpgn

North Dakota

ndhpgn

Ohio

ohhpgn

Oklahoma

okhpgn

Pennsylvania

pahpgn

Puerto Rico and Virgin Islands

pvhpgn

South Carolina

schpgn

South Dakota

sdhpgn

Tennessee

tnhpgn

Texas east of –100 deg. longitude

ethpgn

Texas west of –100 deg. longitude

wthpgn

Utah

uthpgn

Virginia

vahpgn

Washington - Oregon

wohpgn

West Virginia

wvhpgn

Wisconsin

wihpgn

Wyoming

wyhpgn

The area.ini file for NAD83 to HARN datum transformations is …\cssruntm\cfg\harn\area.ini. The default file list is alphabetical. Because many regions overlap, you may need to rearrange the list to ensure that the desired region is being used for your area. Note that the HARN files for American Samoa and Guam are an exception to the general application of the NAD83 to HARN datum transformation, in that these grid files transform directly from the old island datum (American Samoa 1962 or Guam 1963) to the NAD83 HARN datum (the original NAD83 datum was never applied to American Samoa or Guam). The accuracy of the transformations should be viewed with some caution. At the 67-percent confidence level, this method introduces approximately 0.15 meter uncertainty within the conterminous United States, 0.50 meter uncertainty within Alaska, 0.20 meter uncertainty within Hawaii, and 0.05 meter uncertainty within Puerto Rico and the Virgin Islands. In areas of sparse geodetic data coverage, NADCON may yield less accurate results, but seldom in excess of 1.0 meter. Transformations between NAD83 and States/Regions with High Accuracy Reference Networks (HARNs) introduce approximately 0.05 meter uncertainty. Transformations between old datums (NAD27, Old Hawaiian, Puerto Rico, and so forth) and HARN could combine uncertainties (for example, NAD27 to HARN equals 0.15m + 0.05m = 0.2m). In near offshore regions, results will be less accurate, but seldom in excess of 5.0 meters. Farther offshore NAD27 was undefined. Therefore, the NADCON computed transformations are extrapolations and no accuracy can be stated. NADCON cannot improve the accuracy of data. Stations that are originally third-order will not become first-order stations. NADCON is merely a tool for transforming coordinate values between datums.

764


Coordinate System Information This program is based exclusively upon data within the official National Geodetic Reference System (NGRS). Data originating from stations not part of this official reference may not be compatible. Be sure that the data to be transformed is actually referenced to the NGRS. Disclaimer published by the National Geodetic Survey in the public domain software package: The attendant software and any associated data were developed for use by the National Ocean Service under controlled conditions of software maintenance, input quality, processing configurations, and output data utilization. Any use of this software by other than the National Ocean Service would be under conditions not necessarily subject to such control. Therefore, the National Ocean Service makes no warranties, expressed or implied, concerning the accuracy, completeness, reliability, or suitability for any particular purpose of the information and data contained in or generated by this software or furnished in connection therewith. Furthermore, the National Ocean Service assumes no liability associated with the use of such software, information, and data, and assumes no responsibility to maintain them in any manner or means. Any exceptions to these conditions of release must be formally established through negotiated agreements with the National Ocean Service. Since this software and associated information and data were developed and compiled with U.S. Government funding, no proprietary rights may be attached to them, nor may they be sold to the U.S. Government as part of any procurement of ADP products or services.

Notes for the NGA Earth Gravity Model The NGA Earth Gravity Model (EGM96) model is a datum transformation model for the conversion of elevation (height) values between the EGM96 (orthometric) and Ellipsoid (geometric) vertical datums, based upon interpolation in a grid file using WGS84 geographic coordinates. This model uses algorithms found in the National Geospatial Intelligence Agency (NGA) public-domain "INTPT" executable. Comments in the source give original credit for the program to Professor Richard H. Rapp of The Ohio State University. The ASCII grid file published by NGA has been converted into a binary format and is delivered with the product in the …\cssruntm\cfg\EGMGeoid folder. The area.ini file in this folder references the binary grid file. NGA publishes the following disclaimer, which was worded when they were known as NIMA: 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.


765

Coordinate System Information

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

Notes for the USGG (NGS Gravimetric Geoid) Model The USGG (NGS gravimetric geoid) model is a datum transformation model for the conversion of elevation (height) values between the United States Gravimetric Geoid (orthometric) and Ellipsoid (geometric) vertical datums, based upon interpolation in a grid file using NAD83 geographic coordinates. This model uses algorithms found in the National Geodetic Survey (NGS) public-domain "intg" executable. You must obtain the desired .bin binary grid files from NGS (they are available from their website), place them in the …\cssruntm\cfg\ NGSUSGG folder, and edit the area.ini file found in that folder so that it contains the names of the binary grid files (with no path). NGS publishes .bin files for the conterminous USA, Alaska, Hawaii, Puerto Rico and U.S. Virgin Islands, American Samoa, and Guam and Northern Marian Islands. This software is compatible with .bin files published for the 1999 (G99SSS) and later epochs. Note that the disclaimer information found above for the NGS GEOID geoid undulation model applies to the NGS USGG geoid undulation model also.

766



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

Notes for the -Supplied Datum Transformation Model The -Supplied datum transformation model allows s to write a program to perform a datum transformation. The program must implement a simple, well-defined point transformation interface defined by GeoMedia. Please consult the Automation Help documentation for the DatumTransformation object for details.

Standard Geodetic Datums The definitions of these datums come primarily from the following two sources:  National Geospatial-Intelligence Agency (NGA) Technical Report 8350.2, Third Edition Amendment 2 (June 2004)  EPSG Geodetic Parameters Dataset, version 6.17 (July 2008) , published by the Surveying and Positioning Committee of the International Association of Oil and Gas Producers. Where conflicts between these two sources exist, both definitions are provided, and the names indicate the source. Adindan AFG (Afgooye) Agadez Ain el Abd 1970 American Samoa Datum 1962 Amersfoort


Ancienne Triangulation Francaise (ATF) Anna 1 Astro 1965 Antigua Island Astro 1943 Aratu Arc 1950 (EPSG Definition) Arc 1950 (NGA Definition)

767

Coordinate System Information Arc 1960 Ascension Island 1958 Astro Beacon "E" 1945 Astro DOS 71/4 Astro Tern Island (FRIG) 1961 Astronomical Station 1952 Australian Geodetic 1966 Australian Geodetic 1984 Average Terrestrial System 1977 (ATS77) Ayabelle Lighthouse Barbados Batavia Beduaram Beijing 1954 Bellevue (IGN) Bermuda 1957 Bern 1898 Bern 1938 Bissau Bogota Observatory Bukit Rimpah Campcupa Camp Area Astro Campo Inchauspe Canton Astro 1966 Cape (EPSG Definition) Cape (NGA Definition) Cape Canaveral Carthage (EPSG Definition) Carthage (NGA Definition) CH1903 CH1903+ Chatham Island Astro 1971 CHTRF95 Chua Astro Conakry 1905 Co-Ordiante System 1937 of Estonia Corrego Alegre Cote d‘lvoire D48 Dabola Datum 73

768

Datum Base SE (Porto Santo 1995) Dealu Piscului 1933 Dealu Piscului 1970 Deception Island (Antarctica) Deir ez Zor Deutsche Hauptdreiecksnetz (DHDN) Djakarta (Batavia) DOS 1968 Douala Easter Island 1967 EUREF-FIN European Terrestrial Reference System 1989 European 1950 European 1979 European 1987 Fahud Fort Thomas 1955 Gan 1970 Garoua Geocentric Datum of Australia (GDA94) Geocentric Datum of Malaysia (GDM2000) Geodetic Datum 1949 Graciosa Base SW 1948 Greek Greek Geodetic Reference System 1987 Guam 1963 Gunung Segara GUX 1 Astro Guyane Francaise Hartebeesthoek 94 HDKS (HR1901) Herat North Hermannskogel Hito XVIII 1963 Hjorsey 1955 Hong Kong 1963 Hong Kong 1980 Hungarian Datum 1972 (HD72) Hungarian Fasching 1909 Hungarian Stereo Datum 1863 Hu-Tzu-Shan


Coordinate System Information Indian Indian 1954 Indian 1960 Indian 1975 Indian (India and Nepal) Indian (Pakistan) 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) MAGNA-SIRGAS


Mahe 1971 Makassar Malongo 1987 Manoca Massawa Merchich (EPSG Definition) Merchich (NGA Definition) MGICS (equivalent to S-JTSK) Mhast Midway Astro 1961 Militar-Geographische Institut (MGI) Minna MK Monte Mario Montserrat Island Astro 1958 Nahrwan Naparima, BWI National Geodetic Network (NGN) New Zealand Geodetic Datum 2000 NGO 1948 Nord de Guerre North American 1927 North American 1983 North American 1983 – HARN Upgrade North Sahara 1959 (EPSG Definition) North Sahara 1959 (NGA Definition) Nouvelle Triangulation Francaise (NTF) NSWC 9Z-2 Observatorio Meteorologico 1939 Old Egyptian 1907 Old Hawaiian Oman Ordnance Survey of Great Britain 1936 OS (SN) 1980 OSGB 1970 (SN) Padang 1884 Palestine 1923 Pico de las Nieves Pitcairn Astro 1967 Point 58 Pointe Noire 1948 (EPSG Definition) Pointe Noire 1948 (NGA Definition)

769

Coordinate System Information Porto Santo 1936 Potsdam Provisional South Chilean 1963 Puerto Rico Pulkovo 1942 Pulkovo 1995 Qatar 1948 Qatar National Qornoq Reseau Geodesique Francais 1993 (RGF93) Reseau National Belge 1950 (Belge 1950) Reseau National Belge 1972 (Belge 1972) Reunion Rome 1940 S-42 (Pulkovo 1942) S-JTSK (equivalent to MGICS) Samboja Santo (DOS) 1965 Sao Braz Sapper Hill 1943 Schwarzeck Segora Selvagem Grande 1938 Serindung Sierra Leone 1960 SIRGAS 2000 South American 1956 South American 1969 South Asia Sudan Swedish RT38 Swedish RT90

770

SWEREF 99 Taiwan (TWD67) Taiwan (TWD97) Tananarive Observatory 1925 Timbalai (Sabah) Timbalai (Sarawak) Timbalai 1948 TM65 TM75 Tokyo Trinidad 1903 Tristan Astro 1968 Trucial Coast 1948 United States Standard -defined (non-standard) Viti Levu 1916 Voirol 1874 (NGA Definition) Voirol 1875 (EPSG Definition) Voirol 1960 (NGA Definition) Voirol 1960 (Obsolete EPSG Definition) Wake Island Astro 1952 Wake-Eniwetok 1960 WGS60 WGS66 WGS72 WGS 72 Transit Broadcast Ephemeris (WGS 72BE) WGS84 Yacare Yoff Zanderij



Named Geodetic Datums s may add named datums to the product using an ASCII configuration file. Each such named datum is based upon one of the standard geodetic datums listed above (the -defined datum is valid for this purpose). Named datums are defined in the …\cssruntm\cfg\NamedHDatum.ini file. See the comments in this file for further details. Datums defined in this file may be referenced from the autodt.ini configuration file. A named datum may be used with a coordinate system that presets the horizontal geodetic datum, provided that the base standard datum referenced by the named datum is the standard datum preset by the coordinate system.

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 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). The sections referred to are in the GeoMedia Object Reference Help. The following vertical datums are ed. The height type is orthometric for all cases, except where noted. Alicante Australian Height Datum 1971 Brazilian Vertical Datum (Imbituba) Cascais Canadian Vertical Reference 1928 Deutsches Haupthöhennetz 1992 (DHHN92) Earth Gravitational Model (EGM96) 1 Ellipsoid (geometric) European Vertical Reference Frame 2000 European Vertical Reference Frame 2007 International Great Lakes 1955 International Great Lakes 1985 Japanese Standard Leveling Datum 1949 National Geodetic Vertical Datum 1929

New Zealand (Vertical Datum) 2009 North American Vertical Datum 1988 Ordnance Newlyn Third Geodetic Leveling RH 00 RH 2000 RH 70 Tsingtao United European Leveling Network 1955 United European Leveling Network 1973 United European Leveling Network 73-81 United European Leveling Network 95-98 United States Gravimetric Geoid 2003 2 Unspecified -defined (non-standard)

1

Causes the height storage type of the containing CoordSystem to be geometric, referencing the ellipsoid of the horizontal geodetic datum. 2 Causes the height storage type to be unspecified.


771


Ellipsoids Ellipsoid

Earth Radius

Earth-Flattening Denominator

772

Airy 1830

6377563.396 m.

299.3249646

Australian National Spheroid

6378160 m.

298.25

Average Terrestrial System 1977

6378135 m.

298.257

Bessel 1841

6377397.155 m.

299.1528128

Bessel 1841 (Namibia)

6377483.865 m.

299.1528128

Clarke 1858 (EPSG Definition)

6378293.639246834 m.

294.2606763692611

Clarke 1866

6378206.4 m.

294.9786982139058

Clarke 1880 (Arc)

6378249.145 m.

293.4663077

Clarke 1880 (Benoit)

6378300.79 m.

293.4662345705142

Clarke 1880 (EPSG Definition)

6378249.138846127 m.

293.4663076556299

Clarke 1880 (IGN)

6378249.2 m.

293.4660212936294

Clarke 1880 (NGA Definition)

6378249.145 m.

293.465

Clarke 1880 (SGA 1922)

6378249.2 m.

293.46598

Danish

6377104.43 m.

300

Everest (Brunei and East Malaysia 1967) – also referenced as ―Everest 1830 (1967 Definition)‖

6377298.556 m.

300.8017

Everest (Pakistan)

6377309.613 m.

300.8017

Everest (Singapore and W. Malaysia 1948) - also referenced as ―Everest 1830 Modified‖

6377304.063 m.

300.8017

Everest (West Malaysia 1969)

6377295.664 m.

300.8017

Everest 1830 (1865 Indian Feet)

6377299.365595379 m.

300.8017255433728

Everest 1830 (1937 Adjustment)

6377276.345 m.

300.8017

Everest 1830 (1956 Definition)

6377301.243 m.

300.8017


6377301.243 m.

300.8017255433728


6377299.151 m.

300.8017255433728

Fischer 1960 (Mercury)

6378166 m.

298.3

Fischer 1968

6378150 m.

298.3

GEM 10C

6378137 m.

298.2572236


Coordinate System Information Ellipsoid

Earth Radius

Earth-Flattening Denominator

GRS 1967

6378160 m.

298.247167427

GRS 1967 (Rounded)

6378160 m.

298.25

GRS80

6378137 m.

298.257222101

Helmert 1906

6378200 m.

298.3

Hough

6378270 m.

297

Indonesian National 1974

6378160 m.

298.247

International 1924

6378388 m.

297

Krassovsky 1940

6378245 m.

298.3

Modified Airy - also referenced as ―Airy 6377340.189 m. Modified 1849‖

299.3249646

Modified Bessel

6377492.0176 m.

299.152812849997

Modified Fischer 1960 (South Asia)

6378155 m.

298.3

NWL 10D

6378135 m.

298.26

NWL 9D

6378145 m.

298.25

OSU86F

6378136.2 m.

298.2572236

OSU91A

6378136.3 m.

298.2572236

Plessis 1817

6376523 m.

308.64

South American 1969

6378160 m.

298.25

Struve

6378298.3 m.

294.73

Struve 1860

6378297 m.

294.73

Unit Sphere

1 m.

0

-defined (non-standard) War Office

6378300.583 m.

296

WGS60

6378165 m.

298.3

WGS66

6378145 m.

298.25

WGS72

6378135 m.

298.26

WGS84

6378137 m.

298.257223563


773


Units of Measure (UOM) Linear Units Alias

UOM

Conversion Factor

‘

feet

0.3048 (m/ft)

‖

inches

0.0254 (m/in)

chain

chain

20.1168 (m/chain)

cm

centimeters

0.01 (m/cm)

ft

feet

0.3048 (m/ft)

furlong

furlong

201.168 (m/furlong)

hundredth

hundredth

0.000254 (m/100th)

in

inches

0.0254 (m/in)

kft

kilofeet

304.80 (m/kft)

km

kilometers

1000.0 (m/km)

link

link

0.201168 (m/link)

m

meters

1.0

mi

miles

1609.344 (m/mi)

mm

millimeters

0.001 (m/mm)

nm

nanometer

0.000000001 (m/nm)

nmi

nautical miles

1852.0 (m/nmi)

pole

pole

5.0292 (m/pole)

pt

point

0.000352777777777778 (m/pt)

rod

rod

5.0292 (m/rod)

sf

survey feet

0.304800609601219 (m/sf)

si

survey inches

0.025400050800102 (m/si)

sk

survey kilofeet

304.800609601219 (m/sk)

svy_ft

survey feet

0.304800609601219 (m/sf)

svy_in

survey inches

0.025400050800102 (m/si)

svy_kft

survey kilofeet

304.800609601219 (m/svy_kft)

tenth

tenth

0.00254 (m/tenth)

thousandth

thousandth

0.0000254 (m/1000th)

yd

yard

0.9144 (m/yd)

774



Angular Units Alias

UOM

Conversion Factor

‘

minutes

0.000290888208665722 (rad/min)

‖

seconds

0.00000484813681109536 (rad/sec)

º

degrees

0.0174532925199433 (rad/deg)

dd.mmss

degrees minutes seconds

See individual units.

deg

degrees

0.0174532925199433 (rad/deg)

d:m

degrees:minutes


d:m:s

degrees:minutes:seconds


gr

grads

0.0157079632679490 (rad/gr)

min

minutes

0.000290888208665722 (rad/min)

rad

radians

1.0

rev

revolutions

6.28318530717959 (rad/rev)

sec

seconds

0.00000484813681109536 (rad/sec)

Alias

UOM

Conversion Factor

ac

acres

4046.8564224 (m^2/ac)

ares

ares

100.0 (m^2/are)

centare

centares

1.0 (m^2/centare)

chain^2

square chains

404.68564224 (m^2/chain^2)

cm^2

square centimeters

0.0001 (m^2/cm^2)

deciare

deciares

10.0 (m^2/deciare)

ft^2

square feet

0.09290304 (m^2/ft^2)

hectare

hectares

10000.0 (m^2/hectare)

in^2

square inches

0.00064516 (m^2/in^2)

km^2

square kilometers

1000000.0 (m^2/km^2)

link^2

square links

0.040468564224 (m^2/link^2)

m^2

square meters

1.0

mi^2

square miles

2589988.110336 (m^2/mi^2)

Area Units


775

Coordinate System Information Alias

UOM

Conversion Factor

mm^2

square millimeters

0.000001 (m^2/mm^2)

perch

perches

25.29285264 (m^2/perch)

rod^2

square rods

25.29285264 (m^2/rod^2)

yd^2

square yards

0.83612736 (m^2/yd^2)

State Plane Zone Codes—NAD27 and Old Island Datums Zone

Code

Projection

Alabama (E,W)

101, 102

Transverse Mercator

Alaska 1

5001

Oblique Mercator

Alaska (2-9)

5002-5009

Transverse Mercator

Alaska 10

5010

Lambert

Arizona (E,C,W)

201-203

Transverse Mercator

Arkansas (N,S)

301, 302

Lambert

California (I-VII)

401-407

Lambert

Colorado (N,C,S)

501-503

Lambert

Connecticut

600

Lambert

Delaware

700

Transverse Mercator

Florida (E,W)

901, 902

Transverse Mercator

Florida North

903

Lambert

Georgia (E,W)

1001, 1002

Transverse Mercator

Hawaii (I-V)

5101-5105

Transverse Mercator

Idaho (E,C,W)

1101-1103

Transverse Mercator

Illinois (E,W)

1201, 1202

Transverse Mercator

Indiana (E,W)

1301, 1302

Transverse Mercator

Iowa (N,S)

1401, 1402

Lambert

Kansas (N,S)

1501, 1502

Lambert

Kentucky (N,S)

1601-1602

Lambert

Louisiana (N,S)

1701, 1702

Lambert

Louisiana Offshore

1703

Lambert

Maine (E,W)

1801, 1802

Transverse Mercator

776


Coordinate System Information Zone

Code

Projection

Maryland

1900

Lambert

Mass, (Main, Isle)

2001, 2002

Lambert

Mich. (Old) (E,C,W)

2101-2103

Lambert

Mich. (N,C,S)

2111-2113

Lambert

Minnesota (N,C,S)

2201-2203

Lambert

Mississippi (E,W)

2301, 2302

Transverse Mercator

Missouri (E,C,W)

2401-2403

Transverse Mercator

Montana (N,C,S)

2501-2503

Lambert

Nebraska (N,S)

2601, 2602

Lambert

Nevada (E,C,W)

2701-2703

Transverse Mercator

New Hampshire

2800

Transverse Mercator

New Jersey

2900

Transverse Mercator

New Mexico (E,C,W)

3001-3003

Transverse Mercator

New York (E,C,W)

3101-3103

Transverse Mercator

N.Y. Long Island

3104

Lambert

North Carolina

3200

Lambert

North Dakota (N,S)

3301, 3302

Lambert

Ohio (N,S)

3401, 3402

Lambert

Oklahoma (N,S)

3501, 3502

Lambert

Oregon (N,S)

3601, 3602

Lambert

Pennsylvania (N,S)

3701, 3702

Lambert

Puerto Rico, Virg.I. 1

5201

Lambert

Puerto Rico, Virg.I. 2

5202

Lambert

Rhode Island

3800

Transverse Mercator

Samoa

5300

Lambert

South Carolina (N,S)

3901, 3902

Lambert

South Dakota (N,S)

4001, 4002

Lambert

Tennessee

4100

Lambert

Texas (N,NC,C,SC,S)

4201-4205

Lambert

Utah (N,C,S)

4301-4303

Lambert

Vermont

4400

Transverse Mercator

Virginia (N,S)

4501, 4502

Lambert


777


Code

Projection

Washington (N,S)

4601 4602

Lambert

West Virginia (N,S)

4701, 4702

Lambert

Wisconsin (N,C,S)

4801-4803

Lambert

Wyoming (E,EC,WC,W)

4901-4904

Transverse Mercator

State Plane Zone Codes—NAD83 Datum Zone

Code

Projection

Alabama (E,W)

101, 102

Transverse Mercator

Alaska 1

5001

Oblique Mercator

Alaska (2-9)

5002-5009

Transverse Mercator

Alaska 10

5010

Lambert

Arizona (E,C,W)

201-203

Transverse Mercator

Arkansas (N,S)

301, 302

Lambert

California (I-VI)

401-406

Lambert

Colorado (N,C,S)

501-503

Lambert

Connecticut

600

Lambert

Delaware

700

Transverse Mercator

Florida (E,W)

901, 902

Transverse Mercator

Florida North

903

Lambert

Georgia (E,W)

1001, 1002

Transverse Mercator

Hawaii (I-V)

5101-5105

Transverse Mercator

Idaho (E,C,W)

1101-1103

Transverse Mercator

Illinois (E,W)

1201, 1202

Transverse Mercator

Indiana (E,W)

1301, 1302

Transverse Mercator

Iowa (N,S)

1401, 1402

Lambert

Kansas (N,S)

1501, 1502

Lambert

Kentucky (Whole, N,S)

1600-1602

Lambert

Louisiana (N,S)

1701, 1702

Lambert

Louisiana Offshore

1703

Lambert

Maine (E,W)

1801, 1802

Transverse Mercator

Maryland

1900

Lambert

778



Code

Projection

Mass, (Main, Isle)

2001, 2002

Lambert

Michigan (N,C,S)

2111-2113

Lambert

Minnesota (N,C,S)

2201-2203

Lambert

Mississippi (E,W)

2301, 2302

Transverse Mercator

Missouri (E,C,W)

2401-2403

Transverse Mercator

Montana

2500

Lambert

Nebraska

2600

Lambert

Nevada (E,C,W)

2701-2703

Transverse Mercator

New Hampshire

2800

Transverse Mercator

New Jersey

2900

Transverse Mercator

New Mexico (E,C,W)

3001-3003

Transverse Mercator

New York (E,C,W)

3101-3103

Transverse Mercator

N.Y. Long Island

3104

Lambert

North Carolina

3200

Lambert

North Dakota (N,S)

3301, 3302

Lambert

Ohio (N,S)

3401, 3402

Lambert

Oklahoma (N,S)

3501, 3502

Lambert

Oregon (N,S)

3601, 3602

Lambert

Pennsylvania (N,S)

3701, 3702

Lambert

Puerto Rico, Virg.I.

5200

Lambert

Rhode Island

3800

Transverse Mercator

South Carolina

3900

Lambert

South Dakota (N,S)

4001, 4002

Lambert

Tennessee

4100

Lambert

Texas (N,NC,C,SC,S)

4201-4205

Lambert

Utah (N,C,S)

4301-4303

Lambert

Vermont

4400

Transverse Mercator

Virginia (N,S)

4501, 4502

Lambert

Washington (N,S)

4601 4602

Lambert

West Virginia (N,S)

4701, 4702

Lambert

Wisconsin (N,C,S)

4801-4803

Lambert

Wyoming (E,EC,WC,W)

4901-4904

Transverse Mercator


779


UTM Zones Zone

Meridian

Longitude Range

Zone

Meridian

Longitude Range

1

177W

180W-174W

32

9E

6E-12E

2

171W

174W-168W

33

15E

12E-18E

3

165W

168W-162W

34

21E

18E-24E

4

159W

162W-156W

35

27E

24E-30E

5

153W

156W-150W

36

33E

30E-36E

6

147W

150W-144W

37

39E

36E-42E

7

141W

144W-138W

38

45E

42E-48E

8

135W

138W-132W

39

51E

48E-54E

9

129W

132W-126W

40

57E

54E-60E

10

123W

126W-120W

41

63E

60E-66E

11

117W

120W-114W

42

69E

66E-72E

12

111W

114W-108W

43

75E

72E-78E

13

105W

108W-102W

44

81E

78E-84E

14

99W

102W-96W

45

87E

84E-90E

15

93W

96W-90W

46

93E

90E-96E

16

87W

90W-84W

47

99E

96E-102E

17

81W

84W-78W

48

105E

102E-108E

18

75W

78W-72W

49

111E

108E-114E

19

69W

72W-66W

50

117E

114E-120E

20

63W

66W-60W

51

123E

120E-126E

21

57W

60W-54W

52

129E

126E-132E

22

51W

54W-48W

53

135E

132E-138E

23

45W

48W-42W

54

141E

138E-144E

24

39W

42W-36W

55

147E

144E-150E

25

33W

36W-30W

56

153E

150E-156E

26

27W

30W-24W

57

159E

156E-162E

27

21W

24W-18W

58

165E

162E-168E

28

15W

18W-12W

59

171E

168E-174E

29

9W

12W-6W

60

177E

174E-180E

30

3W

6W-0

780



Meridian

Longitude Range

Zone

Meridian

Longitude Range

1

177W

180W-174W

32

9E

6E-12E

31

3E

0-6E

All values are expressed in full degrees east (E) or west (W) of Greenwich (0), Central Meridians, and Longitude Ranges.


781


782


APPENDIX E

Raster Information Raster Formats ed in GeoMedia ADRG Typical Extension: Directory structure, main file has a .img extension Compression Techniques: Uncompressed Bits per Pixel: 8 Number of Bands: 1 or 3 Tiling: Tiled only Placement Methods: Interactive or with internal georeferencing data (Geographic WGS84)

ASRP / USRP Typical Extension: Directory structure, main file has a .img extension. Compression Techniques: Uncompressed or RLE Bits per Pixel: 1, 4 or 8 (always returned to app as 8) Number of Bands: 1 Tiles: Tiled only Placement Methods: Interactive or with internal georeferencing data (Geographic WGS84)

Bitmap Typical Extension: .bmp Compression Techniques: Uncompressed or RLE Bits per Pixel: 1 or 8 Number of Bands: 1 or 3 Tiling: Untiled only Placement Methods: Interactive or with World File

CADRG / CIB Typical Extension: Directory format, main file has a .toc extension Compression Techniques: VQ Bits per Pixel: 8 Number of Bands: 1 (grey (CIB) or color indexed (CADRG)) Tiles: Tiled only Placement Methods: Interactive or with internal georeferencing data (Geographic WGS84)


783

Raster Information

CALS Typical Extension: .cal Compression Techniques: CCITTG4 Bits per Pixel: 1 Number of Bands: 1 Tiling: Tiled or Untiled Placement Methods: Interactive or with World File

ECW Typical Extension: .ecw Compression Techniques: Wavelet (ECW) Bits per Pixel: 8 Number of Bands: 1 or 3 Tiling: Tiled only Placement Methods: Interactive or Other with external coordinate system

ESRI Typical Extension: .bip, .bil Compression Techniques: Uncompressed Bits per Pixel: 8 Number of Bands: 1 Tiling: Untiled only Placement Methods: Interactive or with World File

Intergraph Typical Extension: .cot, .rle, cit, rgb Compression Techniques: Uncompressed, RLE, CCITTG4, PB, or JPEG Bits per Pixel: 1 or 8 Number of Bands: 1 or 3 Tiling: Tiled or Untiled Placement Methods: Interactive, with World File, with internal header data, or with internal GeoTie packets

JFIF Typical Extension: .jpg Compression Techniques: JPEG Bits per Pixel: 8 Number of Bands: 1 or 3 Tiling: Untiled only Placement Methods: Interactive or with World File

784


Raster Information

JPEG 2000 Typical Extension: .jp2 Compression Techniques: Wavelet (JPEG 2000) Bits per Pixel: 8 or 9-16 (reported as 16) Number of Bands: 1 or 3 Tiling: Tiled only Placement Methods: Interactive, with World File, or with internal georeferencing data

MrSID Typical Extension: .sid Compression Techniques: Wavelet (MrSID) Bits per Pixel: 8 Number of Bands: 1 or 3 Tiling: Tiled only Placement Methods: Interactive, with World File, or with internal well known text (WKTEXT)

NITF Typical Extension: .ntf Compression Techniques 8 bit: Uncompressed, VQ, JPEG, or JPEG 2000 9-16 bit: Uncompressed or JPEG 2000 Bits per Pixel: 8, 12, 9-16 (reported as 16) Number of Bands: 1 or 3 Tiling: Tiled or Untiled Placement Methods: Interactive or with internal georeferencing data (Geographic WGS84 or UTM) For 3-band images, only 8 bits per pixel is ed.

Oracle GeoRasters Typical Extension: N/A Compression Techniques: Any compression methods ed by Oracle Bits per Pixel: 8, 9-16 Number of Bands: 1 or 3 out of n. Tiling: Tiled or Untiled Placement Methods: None – GeoRaster feature classes must be created using Database Utilities. Compression is currently only ed with Oracle 10.2.


785

Raster Information

PNG Typical Extension: .png Compression Techniques: RLE or ZIP Bits per Pixel: 1 or 8 Number of Bands: 1 or 3 Tiling: Untiled only Placement Methods: Interactive or with World File

TIFF (and GeoTIFF) Typical Extension: .tif Compression Techniques: 1 bit: Uncompressed PB, or CCITTG4 8 bit: Uncompressed, JPEG, LZW, LZ77, or PB 12 bit: JPEG only 9-16 bit: Uncompressed, LZW, LZ77, or PB Bits per Pixel: 1, 8, 12, 9-16 (reported as 16) Number of Bands: 1, 3, or 4 Tiling: Tiled or Untiled Placement Methods: Interactive, with World File, or with internal GeoTIFF data For JPEG compressed 3-band TIFFs, only band interleaved is ed. For JPEG compressed 4-band TIFFs, only band separate is ed.

USGS DOQ Typical Extension: .doq Compression Techniques: Uncompressed Bits per Pixel: 8 Number of Bands: 1 Tiling: Untiled only Placement Methods: Interactive, with World File, or with internal georeferencing data

Compression Techniques

786

Format

Description

CCITTG4

Consultative Committee on International Telephone and Telegraph Group 4 format is standard for transmission and storage of bilevel facsimile images.

JPEG

t Photographic Experts Group format uses a block-by-block conversion to frequency space and stores a discrete cosine series representation of the frequency space.

LZW

Lempel-Ziv & Welch algorithm compresses binary, grayscale, or color data. This method was not used for a time because of patent and licensing issues.


Raster Information Format

Description

LZ77

1977 version of Lempel-Ziv compression. Commonly called the ―Deflate‖ algorithm. Similar to LZW in compression speed and size performance.

PB

Packbits algorithm compresses binary, grayscale, or color data. Packbits and Intergraph Type 29 are good for general-purpose raster data, continuous-tone imagery, and RLE data. For certain types of images, such as map images, significantly better disk compression is achieved with a different RLE format, such as Intergraph Type 9.

RLE

Run-Length Encoded. A run length is a unit that describes a series of contiguous pixels in a raster line that all have the same value. Run lengths are used to achieve data compression in binary scanned data and color run-length data. Long sequences of 0s, 1s, or identical color indexes are identified and recorded using less data than would otherwise be required to list the individual values of the series of pixels.

VQ

Vector quantization. Defined in MIL-STD-188-199.

Wavelet

An algorithm for grayscale and color data. Used by MrSID, ECW, and JPEG2000 format images.

ZIP

Similar to LZW, it was developed as a legal replacement for LZW.

Tiling Format

Description

Tiling

When raster data becomes large, it may be necessary to subdivide it into smaller sections that can be loaded into memory and manipulated individually. These sections are called tiles. A tiled raster file consists of the standard raster-file header, immediately followed by additional data specifying the tile information. Tiling does not make the raster file smaller, so it is not a compression technique. Rather, it breaks a raster file into manageable parts that the system can use more easily. Tiling a file often speeds up interactive display and editing operations. But tiling a run-length-encoded file can make the file much larger on the disk because any given run-length may be no longer than the relatively small tile dimension. Therefore, many short run-length entries may be required in place of a previous single, long entry.


787

Raster Information

File Types and Categories Listed for Inserting a Georeferenced Image File Types and Extensions TIFF

JFIF

MrSID

ECW

INGR

USGS DOQ

.tif, .tiff

.jpg, .jpeg

.sid

.ecw

.cot, .rgb, .cit

.doq, .key

Placement Mode -

-

-

-

√

-

√

-

-

-

-

-

√

-

-

-

√

-

USGS DOQ

-

-

-

-

-

√

World File

√

√

√

-

-

-

Other with Internal Coordinate System

-

-

-

-

-

-

Other with External Coordinate System

-

-

-

√

-

-

Intergraph Geo-Tie Information GeoTIFF Intergraph Header Matrix

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.

788


APPENDIX F

Layout Window Graphics Commands The Layout Window Graphics commands, or drawing commands, are enabled when you select Window > Show Layout Window to display the layout window. You access these commands from the various layout window toolbars and menus. This appendix simply lists these commands following their menu groupings. For ease of use, complete documentation for these commands consists of a context-sensitive online Help topic for each command, which you can access by pressing the F1 key. This appendix also lists the commands used for placing and manipulating map graphics in a layout window; these commands are described in the ―Deg Map Layouts for Printing in the Layout Window‖ section. See the “Working with Layout Windows”, “Deg Map Layouts for Printing in the Layout Window”, and “Printing in GeoMedia Professional” sections for information on layout windows.

Placing Graphics into a Layout Sheet Line Polyline Arc Curve Rectangle

Circle Ellipse Polygon Symbol

Editing Graphics in a Layout Sheet Move Spin Scale

Trim to Intersection Extend to Intersection

Aligning Graphics in a Layout Sheet Align Left Align Center Align Right

Align Top Align Middle Align Bottom

Distributing Graphics in a Layout Sheet Distribute Horizontally Distribute Vertically

Grouping Graphics in a Layout Sheet Group

Ungroup


789

Layout Window Graphics Commands

Ordering Graphics in a Layout Sheet Bring to Front Send to Back

Bring Forward Send Backward

Spinning or Flipping Graphics in a Layout Sheet Spin Spin Left Spin Right

Flip Horizontally Flip Vertically

Nudging Graphics in a Layout Sheet Up Down

Left Right

Working with Symbols in a Layout Sheet Create Symbol Set Active Symbol

Symbol (Place Active Symbol)

Inserting Objects into a Layout Sheet Insert > Object

Additional Layout Window Tools Text Apply Linear Style Line Width Line Terminators

Delete Line Color Line Pattern Fill

Edit Commands in the Layout Window Edit > Undo Redo Cut Copy Paste Paste Special

790

Select All Delete Links



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

Sheet Commands in the Layout Window Sheets > Insert Sheet Delete Sheet Rename Sheet

Import Layout Export Layout

Insert and Layout Commands in the Layout Window Insert > Layout Frames Graphics Into Layout Frames Map Legend North Arrow Scale Bar Data Table Cartographic Grid Reference Grid Reference Index Object

Layout > Layers Layer Groups Update Map Graphics

Tool Commands in the Layout Window Tools > Measure Distance SmartSnap Settings Options


791


Window Commands in the Layout Window Window > New Map Window New Data Window Hide Layout Window

792

Cascade Tile Horizontally Tile Vertically Layout Window Properties


APPENDIX G

Conversion Tables The following tables contain the multiplication factors for converting from the International System of Units (metric) to the United States Customary System and from the United States Customary System to the International System of Units (metric). These tables are useful with various GeoMedia functions, such as the Measure Distance and Scale Bar Properties commands and the Units and Formats tab of the Define Coordinate System File dialog box.

International System of Units to United States Customary System To Convert from

To

International System of Units

United States Customary System

Meters

Feet

3.280840

Meters

Yards

1.093613

Centimeters

Inches

0.3937008

Centimeters

Feet

0.03280840

Kilometers

Miles (U.S. statute)

0.6213711

Kilometers

Miles (international nautical)

0.5399568

Square meters

Square feet

Square meters

Square yards

1.195990

Square centimeters

Square inches

0.1550003

Square centimeters

Square feet

0.00107639

Square kilometers

Square miles (U.S. statute)

0.3861021

Hectares

Acres

2.471054

Hectares

Square miles

0.00386102


Multiply by

10.76391

793

Conversion Tables

United States Customary System to International System of Units

794

To Convert from

To

Multiply by

United States Customary System

International System of Units

Feet

Meters

0.3048

Yards

Meters

0.9144

Inches

Centimeters

2.54

Feet

Centimeters

Miles (U.S. statute)

Kilometers

1.609344

Miles (international nautical)

Kilometers

1.852

Square feet

Square meters

0.09290304

Square yards

Square meters

0.83612736

Square inches

Square centimeters

6.4516

Square feet

Square centimeters

Square miles (U.S. statute)

Square kilometers

2.589988

Acres

Hectares

0.4046856

Square miles

Hectares

30.48

929.0304

258.9988


APPENDIX H

Catalogs: Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers This appendix provides information on installing, setting up, and upgrading Oracle and MS-SQL Server for use with Catalogs. The dialog boxes and graphics in this appendix reflect the use of Oracle 10i and MS-SQL Server 2000; the interface may differ if you are using different versions of Oracle or MS-SQL Server. The OracleCatalogScripts and the SqlServerCatalogScripts folders are delivered in the product \Scripts folder. See the “Working with Catalogs” section for related information about creating new catalog connections and managing catalog connections.

Creating a Catalog Using Oracle Enterprises can tie multiple GeoMedia catalog s to a single database using Oracle. The following steps describe the procedure for installing the Oracle catalog, including creating the Oracle database and creating a new Catalog connection. The following shows a typical installation and configuration of an Oracle catalog. Your steps may vary depending on your organization's Oracle protocol. It is strongly recommended that this function be performed by a qualified Oracle database .

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: 1. Set up a service name. 2. Create an ODBC DSN. 3. Create a new Catalog connection.

Step One: Create an Oracle Catalog database. The first step is to create the Oracle catalog database where metadata records are stored and which will be used by GeoMedia Catalog functions. The following are required to perform this step:  Tablespace—At least one Oracle tablespace must exist for Catalog data and temporary data. The preferred setup is to have two separate tablespaces, one for data and another for temporary data. Scripts:  ora.sql—the master Oracle SQL script. Calls the following scripts in the order listed:  c.sql—Creates the Catalog schema owner ( name).


795

Catalogs: Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers    

ctable.sql—creates all tables in the Catalog schema owner ( name). cindex.sql—Creates all indexes. crel.sql—Creates foreign key relationships. cscd.sql—Creates triggers and sequences.

Other:  Oracle SQL*Plus and SQLNet installed on the client machine  Oracle database instance  System 1. Start SQL*Plus, and to the database as a with database permissions. 2. Run the ora.sql script, and type @some_path\ora.sql, where some_path is the path to the ora.sql file). Include the entire path, for example: SQL> @c:\ora.sql 3. Follow the SQL prompts to create the database. You will be prompted for the following:  Enter the name of the schema that will be created. This is the name of the Oracle schema that will be created when the script is run.  Enter the name of the default tablespace used by the schema. All objects created by the script will live in this tablespace. It must exist before the script is run.  Enter the name of the temporary tablespace used by the schema. This is the tablespace used for the schema's temporary segments. It must exist before the script is run.  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. The of the new Catalog database is the same as the 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 environment variable. This directory is typically found at <System Drive Letter>:\Documents and Settings\< Name>\Local Settings\Temp on Windows XP systems. Review this file for errors. With GeoMedia Catalog and Oracle, you may only to the database as the database owner. Read-only and read-write s are not ed.

Step Two: Set up a service name for the client. The next step is to set up a service name, or database alias, to identify and to attach the client to the Oracle database. The following steps demonstrate one of several available options for setting up a database alias. You may follow a different method, depending on your organization's Oracle protocol. Before performing this task, that the following are installed for the client:  Net Configuration Assistant  The most recent Oracle ODBC drivers. See the link (http://technet.oracle.com/). 1. Run Net Configuration Assistant. 2. Select the Local Net Service Name configuration 3. Select Add. 4. Click Next. 5. Select the proper Oracle version option. 6. Click Next.

796


Catalogs: Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers 7. Choose a networking protocol to connect to and communicate with the Oracle Catalog database. Your choice will depend on your organization's protocol. 8. Click Next. 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 connection test before completing the Oracle service configuration process. 12. Accept the Net Service name, or enter a new one. 13. Click Next. 14. Click Next. 15. When you are finished, click Next; then click Finish.

Step Three: Create ODBC DSN for the client. The final step before attaching the GeoMedia Catalog client to the Oracle Catalog database is to create an ODBC DSN. 1. Run Data Sources (ODBC) in the istrative Tools folder of your Control . 2. Choose DSN or System DSN, following your organization's Oracle protocol.

3. Click Add.


797

Catalogs: Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers 4. Select Oracle ODBC Driver.

5. Enter a Data Source Name name, a TNS Service Name, and a 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. It is recommended that you the ODBC connection by clicking the Test Connection button. Click OK when you are finished.

Step Four: Create a New Catalog Connection The final step is to create a new catalog connection. See the “Working with Catalogs” section for procedures for creating new catalog connections.

798


Catalogs: Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers

Server Database Upgrades Intergraph recommends the following workflow as a method to upgrade Oracle or MS-SQL Server software versions. 1. Select Tools > Catalogs > Export Catalog Records.

2. 3. 4. 5.

On the General tab, select the appropriate Catalog connection from the drop-down list. Click Select All, or select all records that are to be saved/backed up for the update process. Select the GCE Export format option. 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 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.


799

Catalogs: Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers 12. Select Tools > Catalogs > Import Catalog Records.

13. Type the location from where the import files are to be read, or use Browse to select the location. 14. Click Select All, or select the appropriate file(s) from the Available files list. A tooltip is attached to the filenames so that long filenames can be read easily. 15. Select the GCE Import format option. 16. Select the appropriate Target catalog from the drop-down list; then click OK.

The status of the import for the selected set of files is displayed in the status bar, the catalog records are imported from the selected source file(s) to the selected catalog, and an Import complete message is displayed.

Creating a Catalog Using the Microsoft MS-SQL Server Larger organizations can tie multiple GeoMedia Catalog s to a single database using MS-SQL Server. To create an MS-SQL database for use with the GeoMedia Catalog, you must have the MS-SQL Server Scripts that are provided by Intergraph. These scripts are in the MS-SQL folder of your GeoMedia distribution media. These instructions follow the basic steps associated with an MS-SQL Server Catastallation, 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 perform the installation.

800



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 . These scripts are in the Scripts\SqlCatalogScripts folder of GeoMedia and GeoMedia Professional. 3. Create s. 4. Set permissions. 5. Create an ODBC connection for clients. 6. Create a new Catalog connection.

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

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

The database is created and configured for use with GeoMedia. Now you are ready to create s.


801


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

To create a for MS-SQL: Here is a basic method for creating a for use with the MS-SQL Catalog database. You can follow these steps whether you are creating a read-write or read-only . The distinction between the two types will be made when you set the permissions. 1. Open the MS-SQL Enterprise Manager. First, you will define a to be used by GeoMedia Catalog s to access the MS-SQL Catalog database. 2. Expand the Security folder. 3. Right click the s icon. 4. Select New from the shortcut menu. 5. Type a name, such as catalog_, in the Name field on the SQL Server Properties dialog box. 6. Click the SQL Server Authentication option. 7. Optionally, type a to accompany the name. 8. Choose the MS-SQL Catalog database from the Database drop-down list. 9. Click the Database Access tab. 10. In the Permit column, click the check box next to the MS-SQL catalog database. 11. Click OK.

Step Four: Set permissions. Once you have created s, the next step is to set permissions to grant your s a level of access to Catalog data. You may grant a read-only access or data (read-write) access. It is recommended that an be granted the same permissions on all tables. An that is provided with different permissions on different tables may result in errors in GeoMedia.

To set read-write permissions for MS-SQL: 1. 2. 3. 4.

802

Expand the Databases folder in the MS-SQL Enterprise Manager. Expand the s icon. Right click the read-write for which you want to assign permissions. Select All Tasks | Manage Permissions from the shortcut menu.


Catalogs: Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers 5. In the Database Properties dialog box, in the Object column, starting with the table AT and ending with _Defined, choose the Select, Insert, Update, Delete, and DRI options for each table. 6. 7.

8. 9.

Ignore objects that have the owner Information Schema. Click Execute for the IsReadOnly, IsThesaurusKeyword, and ISWebPublish stored procedures. Finally, you must decide whether or not to provide read-write permission to two Catalog features which are generally reserved for istrative-level personnel: the Thesaurus/Keyword and Web Publish features of the GeoMedia Catalog.  The Thesaurus Keyword tool allows the to create and edit organizational keyword lists within the Catalog.  The Web Publish feature allows the 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 will have access to these features. If you want to change the permissions, do the following:  If you want to deny the read-write access to the Thesaurus Keyword tool, deselect the Insert, Update, and Delete permissions on the table ID_Thesaurus_Lookup.  If you want to deny the read-write access to the GeoMedia Catalog Web Publish feature, deselect the Insert, Update, and Delete permissions on the table ID_Web_Publish. Click Apply. Click OK.

To set read-only permissions for MS-SQL Catalog: 1. 2. 3. 4. 5.

Expand the Databases folder in the MS-SQL Server 7 Enterprise Manager. Expand the s icon. Right click the to whom you want to assign read-only permissions. Select All Tables > Manage Permissions from the shortcut menu. In the Database Properties dialog box, in the Object column, starting with the table AT and ending with _Defined, choose only the Select option for each table.

Ignore objects that have the owner Information Schema. 6. Click Execute for the ISReadOnly, ISThesaurusKeyword, and ISWebPublish stored procedures. 7. Click Apply when you are finished.


803


Step Five: Create an ODBC connection for GeoMedia Catalog s. The next step is to create an ODBC data source (DSN) to be used to connect GeoMedia Catalog s to the SQL database. The following steps show a typical Catalog ODBC connection. Your selections may vary according to your organization's SQL protocol. Follow these steps for each client: 1. Run Data Sources (ODBC) in the istrative Tools folder of your Control . 2. Choose either the DSN or the System DSN tab, following your organization's SQL protocol. 3. Click the Add button to create a new DSN. 4. Select SQL Server from the list of drivers. 5. Click Finish.

The Data Source Wizard launches. 6. Enter a data source name in the Name field. This name will be used by the GeoMedia Catalog as the DSN to connect to the MS-SQL Catalog database. 7. Optional: Enter a description of the data source in the Description field. 8. Enter the name of an MS-SQL Server on your network in the Server field. You can either select an existing server name from the list or enter a new name. If you select an existing server name, no further configuration is needed. 9. Click Next.

The second wizard screen opens, allowing you to select a method of authentication when a GeoMedia Catalog attaches to the MS-SQL Catalog database. 10. Choose the With SQL Server authentication using a ID and entered by the option, and enter a valid ID below. Leave the field blank. Reminder: These steps are intended to outline a typical configuration. Your MS-SQL protocol may differ. 11. Click Next. 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 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.

804



Step Six: Create a New Catalog Connection The final step is to create a new catalog connection. See the “Working with Catalogs” section for procedures for creating new catalog connections.


805


806


APPENDIX I

LRS Data Structures This appendix describes the Linear Referencing System (LRS) data structures that are directly ed.

Overview Data for Transportation Asset systems (using dynamic segmentation) generally falls into two categories: LRS data and Event data. LRS data describes the naming, measurement system, and geometry of the linear network. Event data describes attributes of the linear network, such as pavement conditions, roadway inventory data (for example, guardrails and signage), and accident occurrences. This software provides great flexibility in the structuring of both of these data types, as shown below: LRS Data Structure Options

Event Data Structure Options



Measure



Measure



Measure with Internal Markers



Marker Offset



Measure with External Measure Markers



Coordinate



Duration



Duration



Duration with Internal Markers



Duration with External Measure Markers

There are additional data structures associated with Multilevel LRS. These options are available if you also have GeoMedia Transportation installed. The details of these additional data structures are described in the ―LRS Data Structures‖ appendix of the Working with GeoMedia Transportation document.

Single-Level LRS Data Structures An LRS data structure is typically made up of a number of geometric segments that together define the entire LRS. All but the two External Marker options, described in the following subsections, consist only of a table describing those segments. The External Marker options have an additional table that describes marker points. Note that all of the field names used in the subsections to follow are representative only. You are free to name the fields as you please.


807

LRS Data Structures

Option 1 - Measure The segments in this option are defined by a set of up to four LRS keys to name the route, a start and an end measure value, and geometry.

BeginMeasure

EndMeasure Direction of Segment

LRS Feature Class Field

Sample

Description

PrimaryKey

US

The LRS key fields identify the "route" that this segment of the LRS belongs to. This identification can be done with anywhere from 1 to 4 fields within the LRS feature class. These fields are the same fields the event features will use to identify the "route". In the sample shown PrimaryKey identifies the roadway system, SecondaryKey contains the route number, TertiaryKey identifies whether the segment is part of a spur, and QuatenaryKey identifies whether this segment is part of an alternative route. All together the route name is "US6SA".

808

SecondaryKey

6

This is the 2nd key field that can be used to identify the "route" that this segment of the LRS belongs to. Its use is optional.

TertiaryKey

S

This is the 3rd key field that can be used to identify the "route" that this 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.

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).


LRS Data Structures LRS Feature Class Field

Sample

Description

RegionID

ORA

This text field contains an identifier as to which region a particular segment resides in. It is used to subdivide an LRS into more manageable subsets. Its use is optional. The ―ORA‖ in the sample shown is an ID code for ―Orange County‖.

Option 2 - Measure with Internal Measure Markers 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, a Begin Marker name, an optional End Marker Name, and geometry. The markers allow this structure to be used with event data using the Marker Offset option.

BeginMeasure

BeginMarker

EndMarker

EndMeasure

Direction of Segment


Sample

Description

PrimaryKey

US


SecondaryKey 6


TertiaryKey

S


QuatenaryKey A


BeginMeasure 12.3


EndMeasure


18.2


809


Sample

Description

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


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


Option 3 - Measure with External Markers 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. This option also requires markers that are defined by up to four LRS keys, a marker name, and a measure value. The markers allow this structure to be used with event data using the Marker Offset option.

BeginMeasure

Marker

EndMeasure

Marker

Direction of Segment


Sample

Description

PrimaryKey

US


SecondaryKey

810

6




Sample

Description

TertiaryKey

S


QuatenaryKey

A


BeginMeasure

12.3


EndMeasure

18.2


Geometry

blob


Geometry Reversed

True


RegionID

ORA


PrimaryKey

US


SecondaryKey

6


TertiaryKey

S


QuatenaryKey

A


MarkerName

M34

This is the identifying name of the marker.

MarkerMeasure

17.5

This is the measurement value at the marker.


811

LRS Data Structures

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

PrimaryKey

US


812

SecondaryKey 6


TertiaryKey

S


QuatenaryKey A


BeginMeasure 12.3


Duration

5.9

This is distance value from the beginning position to the ending position of this feature.

Geometry

blob


Geometry Reversed

True


RegionID

ORA



LRS Data Structures

Option 5 - Duration with Internal Markers 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, a Begin Marker name, an optional End Marker Name, and geometry. The markers allow this structure to be used with event data using the Marker Offset option.

BeginMeasure

BeginMarker

EndMarker



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 LRSkey4 identifies whether this segment is part of an alternative route. All together the route name is "US6SA".

SecondaryKey 6


TertiaryKey

S


QuatenaryKey A


BeginMeasure 12.3


Duration

5.9


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



813


Sample

Description

Geometry Reversed

True


RegionID

ORA


Option 6 - Duration with External Measure Markers 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. This option also requires markers that are defined by up to four LRS keys, a marker name, and a measure value. The markers allow this structure to be used with event data using the Marker Offset option.

BeginMeasure

Marker

Marker



Sample

Description

PrimaryKey

US


814

SecondaryKey 6


TertiaryKey

S


QuatenaryKey A




Sample

Description

BeginMeasure 12.3


Duration

5.9


Geometry

Blob


Geometry Reversed

True


RegionID

ORA

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‖.

Marker Feature Class Field

Sample

Description

PrimaryKey

US


SecondaryKey

6


TertiaryKey

S


QuatenaryKey

A


MarkerName

M34

This is the identifying name of the marker.

MarkerMeasure 17.5

This is the measurement value at the marker.


815

LRS Data Structures

Event Data Structures Note that these structures have no geometry. The whole purpose of the dynamic segmentation process is to combine the LRS data structure and the Event data structure to create a new geographic feature. Note that all of the field names used in the subsections to follow are representative only. You are free to name the fields as you please.

Option 1 - Measure The events in this option are defined by a set of up to four LRS keys to name the route, a start measurement, and for linear events only, an end measure value.

Event Feature Class Field

Sample

Description

PrimaryKey

US

The LRS key fields identify the "route" that this segment of the LRS belongs to. This identification can be done with anywhere from 1 to 4 fields within the LRS feature class. These fields are the same fields the event features will use to identify the "route". In the sample shown PrimaryKey identifies the roadway system, SecondaryKey contains the route number, TertiaryKey identifies whether the segment is part of a spur, and LRSkey4 identifies whether this segment is part of an alternative route. All together the route name is "US6SA".

816

SecondaryKey

6


TertiaryKey

S


QuatenaryKey

A


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.


LRS Data Structures

Option 2 - Marker Offset The events in this option are defined by a set of up to four LRS keys to name the route, a begin marker name and an offset value, and for linear events only, an end marker name and offset value.


Sample

Description

PrimaryKey

US


SecondaryKey

6


TertiaryKey

S


QuatenaryKey

A


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.


817

LRS Data Structures

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

PrimaryKey

US


818

SecondaryKey

6


TertiaryKey

S


QuatenaryKey

A


BeginX

2546234.2

This is the X or Longitude coordinate for the beginning position of this event. This field is required for both point and linear events.

BeginY

753124.4

This is the Y or Latitude coordinate for the beginning position of this event. This field is required for both point and linear events.

EndX

2584123

This is the X or Longitude coordinate for the ending position of this event. This field is used for linear events only.

EndY

745654.6

This is the Y or Latitude coordinate for the ending position of this event. This field is used for linear events only.


LRS Data Structures

Option 4 - Duration The events in this option are defined by a set of up to four LRS keys to name the route, a begin measure, and a duration (length) value. The Duration option applies to linear events only.


Sample

Description

PrimaryKey

US


SecondaryKey

6


TertiaryKey

S


QuatenaryKey

A


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.


819

LRS Data Structures

820


APPENDIX J

ed SVG Element Types Background GeoMedia Professional offers a means of ing symbols definitions from numerous formats through implementation of a common symbol-serving interface. This appendix describes the implementation of such an interface for the of symbols that are created in an SVG structure, which is XML based. This open format provides the with the ability to create new symbols and to convert existing symbols. These symbols can be used in GeoMedia within styles to render points, lines, and areas.

Discussion An SVG document is created according to the standard W3C SVG specifications, which allow for certain attributes and elements to make parametric behavior easier. The following are the major sections of an SVG document relevant to symbol usage:  XML version and encoding - A standard XML header. This header is not required. Whether the header is provided or not, UTF-8 encoding is always assumed.  Reference namespaces - Identify namespaces in use within the document. If GeoMedia-structured symbol parameters are to be used, the gmsvgsym namespace must be referenced. For more information, see the “Metadata Element” section of this appendix.  SVG - This root element for the document holds the sections for metadata (metadata), graphics definitions (symbol), and drawing objects (use).  Metadata - May include the GeoMedia SVG Symbol Metadata extension. For more information, see the “Metadata Element” section of this appendix.  Symbol - Contains symbols definitions. This section is used to segregate symbol definitions from actual drawing requests.  Use - Specifies actual use of a symbol definition at a particular coordinate location for visualization within an SVG viewer. This element is not required by GeoMedia's SVG interpreter, but it is required by SVG viewers. The symbol section contains the actual symbol definitions. Symbols may be composed of various SVG geometry elements. The following elements are ed by the GeoMedia SVG Symbol Server: 

svg



metadata



polygon



ellipse



symbol



line



rect



path



use



polyline



circle



text



g

The nature of these elements, the attributes of these elements, and the components of those attributes are discussed in the following discussion. Elements in the SVG file other than these are ignored.


821

ed SVG Element Types All distance and coordinate values, including those of fonts, are given in the unit of pixels, which are defined as being 1/96th of an inch. Because the XML is structured as UTF-8, the GeoMedia symbol interpreter will also handle Unicode symbols.

Versions and Variations SVG documents in SVG 1.1 format are ed.

ed 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 ed are as follows: Attribute

Value

Description

xmlns

"http://www.w3.org/2000/svg (http://www.w3.org/2000/svg)"

Defines the default namespace of the XML document.

xmlns:xlink

"http://www.w3.org/1999/xlink (http://www.w3.org/1999/xlink)"

Defines the xlink namespace and sets it to the xlink prefix. It is only required if someone uses the namespace.

xmlns:svg

"http://www.w3.org/2000/svg (http://www.w3.org/2000/svg)‖

Defines the namespace for SVG elements. This is not required if SVG namespace is the default.

xmlns:gmsvgsym

"http://www.intergraph.com/GeoMed Used to defined SVG metadata that ia/gmsvgsym" is specific to GeoMedia's use. This is not required if parametric behavior is not required by the symbol.

The following is an example of an svg element: <svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:gmsvgsym="http://www.intergraph.com/GeoMedia/gmsvgsym"> …

Symbol Element The <symbol> element is used to logically collect elements together to form a symbol. It is much like a element, with the exception that a symbol does not render. To use a symbol element

822


ed SVG Element Types 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

Value

Description

viewBox

X origin, y origin, width, and height.

This defines the bounding box of the view port and is in the default units. The cannot specify units for any of the four properties. The viewBox attribute is required.

id

String

The identifier for the element. Although not required by SVG, the GeoMedia symbol interpreter requires it to exist.

style

Font, stroke, and fill characteristics ed.

The attribute is not required. See the “Style Attribute” section for details.

Scaling or non-scaling of the pen based on size, can be specified using the ―gmscalepen‖ flag. Valid values are 0 and 1. Default value is 1.

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.

Varies

The attribute is not required. See the “Transform Attribute” section for details.

transform

The following is an example of a symbol element: <symbol id="RoadShield" viewBox="0 0 500 500" style="font-size:50;font-family:Arial"> …

Use Element The <use> element is used to define which symbols to actually use in an SVG display. The specifies a URI in an xlink:href attribute and specifies the x and y location where the item's (0,0) point should be moved to. This component is not used by the GeoMedia symbol interpreter, and if included as a part of the symbol definition, it will be ignored. The following is an example of a use element: <symbol id="RoadShield" viewBox="0 0 500 500" style="font-size:50;font-family:Arial"> … <use xlink:href="#RoadShield"/>


823

ed SVG Element Types

G Element The element gathers all of its child elements as a group and has an id attribute to give that group a unique name. Attribute

Value

Description

id

String

The identifier for the element. Not required.

style

Font, stroke, and fill characteristics ed.


transform

Varies


The following is an example of a group element: …

Metadata Element Metadata included in the SVG content is specified within the <metadata> element and allows symbol creators to define their own metadata for the symbol file. GeoMedia has introduced the following new namespace to address parametric behavior: xmlns:gmsvgsym=‖http://www.intergraph.com/GeoMedia/svgsym‖ The XML schema for this namespace defines a root element symbolParameters, which may contain zero or more individual symbol parameters for influencing the symbol content. For the symbol to be parametric:  Metadata should be defined as per the schema specified in the SVGSymbolMetadataXMLSchema.doc document.  Metadata should be placed before symbol definition(s) and optionally can go inside it. Each successive metadata definition overrides the previous one based on the scope.  Parametric criteria defined in metadata should match. That is, the ―replaceID‖ attribute value of the active (latest definition of) metadata should match with the ―ID‖ attribute value of the ―text‖ element in a symbol. If it matches, the symbol is treated as a parametric symbol; otherwise, it is not. For more information on the SVG Symbol Metadata XML Schema for GeoMedia, see the ―SVG Symbol Metadata XML Schema” section of this appendix.

824



Geometry Elements Line Element The following section defines the attributes of a line element. These are the only attributes ed, and all other attributes will be ignored. Attribute

Value

Description

x1

X start point

The x value for the start point of the line. No units can be given with the value.

y1

Y start point

The y value for the start point of the line. No units can be given with the value.

x2

X end point

The x value for the end point of the line. No units can be given with the value.

y2

Y end point

The y value for the end point of the line. No units can be given with the value.

id

String


style

Stroke characteristics ed.


transform

Varies


The following is an example of a line element:

Polyline and Polygon Elements The following section defines the attributes of polyline and polygon elements. The distinction between the polygon and polyline elements is that the polygon element is closed. These are the only attributes ed, and all other attributes will be ignored. Attribute

Value

Description

points

―x1,y1 x2,y2 … xn,yn‖

A set of white-space-separated coordinate pairs. No units can be given with the value.

id

String


style

Stroke and fill (polygon only) characteristics ed.


transform

Varies


The following are examples of polyline and polygon elements: <polyline id="Polyline1" points=”195,10 195,200” style="stroke-width:1; stroke-linecap:round; stroke:#e1e100; fill:none;"/>


825

ed SVG Element Types <polygon id="Polygon1" points=”150,0 150,200 300,100” style="stroke-width:1; stroke-linecap:round; stroke:#e1e100; fill:#ff0000;"/>

Rect Element The following section defines the attributes of a rect element. These are the only attributes ed, and all other attributes will be ignored. Attribute

Value

Description

x

x-upper-left

The horizontal coordinate of the upper-left point of the rectangle. No units can be given with the value. Note that if x is not given, it defaults to the viewBox x value.

y

y-upper-left

The vertical coordinate of the upper-left point of the rectangle. No units can be given with the value. Note that if y is not given, it defaults to the viewBox y value.

width

Width

The width of the rectangle, which must be a positive value. No units can be given with the value.

height

Height

The height of the rectangle, which must be a positive value. No units can be given with the value.

id

String


style

Stroke and fill characteristics ed.


transform

Varies


The following is an example of a rect element:

Circle Element The following section defines the attributes of a circle element. These are the only attributes ed, and all other attributes will be ignored.

826

Attribute

Value

Description

cx

X center

The horizontal coordinate of the center of the circle. No units can be given with the value.

cy

Y center

The vertical coordinate of the center of the circle. No units can be given with the value.

r

Radius

The radius of the circle, which must be positive. No units can be given with the value.

id

String


style

Stroke and fill

The attribute is not required. See the “Style Attribute”


ed SVG Element Types Attribute

transform

Value

Description

characteristics ed.

section for details.

Varies


The following is an example of a circle element:

Ellipse Element The following section defines the attributes of an ellipse element. These are the only attributes ed, and all other attributes will be ignored. Attribute

Value

Description

cx

X center

The horizontal coordinate of the center of the circle. No units can be given with the value.

cy

Y center

The vertical coordinate of the center of the circle. No units can be given with the value.

rx

X Radius

The radius of the ellipse along the x-axis, and the radius value must be positive. No units can be given with the value.

ry

Y Radius

The radius of the ellipse along the y-axis, and the radius value must be positive. No units can be given with the value.

id

String


style



transform

Varies


The following is an example of an ellipse element: <ellipse id="Ellipse1" cx=”150” cy=”150” rx=”100” ry=”50” style="stroke-width:2; stroke:#e1e100; fill:#ff00ff;"/>


827


Path Element The following section defines the attributes of a path element. These are the only attributes ed, and all other attributes will be ignored. Attribute

Value

Description

d

The set of flags and coordinates that describe the path being drawn. No units can be given with the value. See the “D Attribute” section for details

id

String


style



transform

Varies


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.

828

d Characteristics

Value

Description

M

x1,y1

Sets the current location to a value defined by the x1, y1 parameters. The ―M‖ characteristic is like a move to command.

m

dx1,dy1

Sets the current location to a value defined by the dx1 + the current x location, and dy1 + the current y location. The ―m‖ characteristic is like a move from the current location by the offset value.

L

x1,y1

Draws a line from the current point to x1, y1.

l

dx1,dy1

Draws a line from the current point to the pointed defined by the offset values of dx1, dy1.

A

rx ry x-axis-rotati on large-arc sweep x y

Draws an elliptical arc from the current point to x,y. The points are on an ellipse with x-radius rx and y-radius ry. The ellipse is rotated x-axis-rotation degrees. If the arc is less than 180 degrees, the large-arc is 0; if greater than 180 degrees, the large-arc is 1. If the arc is to be drawn in the positive direction, the sweep is 1; otherwise, it is 0.

a

rx ry x-axis-rotati on large-arc sweep dx dy

Draws an elliptical arc from the current point to the relative location defined by the offset dx,dy. The points are on an ellipse with x-radius rx and y-radius ry. The ellipse is rotated x-axis-rotation degrees. If the arc is less than 180 degrees, the large-arc is 0; if greater than 180 degrees, the large-arc is 1. If the arc is to be drawn in the positive direction, the sweep is 1; otherwise, it is 0.


ed SVG Element Types d Characteristics

Value

z

Description Closes the path by drawing a straight line where this subpath began.

The following is an example of a path element: <path id="Path1" d=”M6,199 L200,199 L200,5 L6,5z” style="stroke-width:2; stroke:#e1e100; fill:#ff0000;"/>

Text Element The following section defines the attributes of a text element. These are the only attributes ed, and all other attributes will be ignored. Attribute

Value

Description

x

x-upper-left

The horizontal coordinate of the upper-left point of the text. No units can be given with the value.

y

y-upper-left

The vertical coordinate of the upper-left point of the text. No units can be given with the value.

text-anchor

―start‖, ―middle‖, or ―end‖

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.

id

String


style

Font, stroke, and fill The attribute is not required. See the “Style Attribute” section for details. characteristics ed.

transform

Varies


The following is an example of a text element: Here is the text

Common Attributes Style Attribute SVG specifies the presentational aspects of graphic elements using inline styles. We set the value of the style attribute to a series of visual properties, and their values as described in the following sections. The format of a style attribute is ―stylecharacteristic1:value;stylecharacteristic2:value2;…‖. An example would be: style=‖stroke:#e1e100;stroke-width:1;stroke-opacity:0.5;‖. For more information refer to the W3C specification. Stroke Characteristics: Lines are considered to be strokes of a pen drawn to a canvas. The size, color, and style of the pen stroke are considered to be part of the line's presentation.


829

ed SVG Element Types Stroke Characteristics

Value

Description

stroke

Color of line

Specifies the color for a linear element. The color value ed is RGB-encoded using two hexadecimal digits per primary-color component, in the order Red, Green, Blue, prefixed with a hash (#) sign. For example, full red is encoded as ―#ff0000‖ (with no quotation marks). Note that this is the only format ed. The exception is the word ―none,‖ which implies an opacity value of 0.

stroke-width

Stroke width

Specifies the width of the rendered line. No units can be specified for this object.

stroke-dasharray

Dash gap sequence of line

Specifies a series of numbers that tell the length of dashes and gaps with which a line is to be drawn. Format is dash length, space, gap length, space, etc. No units can be given with the values, and the values are in quotes.

stroke-opacity

Stroke opacity

Controls the opacity of a linear element by giving stroke-opacity a value ranging from 0.0 to 1.0; 0.0 is entirely transparent, and 1.0 is entirely opaque.

stroke-line

―miter‖, ―bevel‖, Specifies the shape of the corners of a polygon or or ―round‖ series of lines. There are three types ed, which are listed in the value column.

stroke-linecap

―butt‖, ―round‖, or ―square‖

Specifies an end cap of a line. There are three types ed, which are listed in the value column.

Fill Characteristics: Specifies the way in which the interior of a shape is to be filled. Fill Characteristics

Value

Description

fill

Fill color

Specifies the fill color for closed symbols like boundaries and complex strings. The color value ed is RGB-encoded using two hexadecimal digits per primary-color component, in the order Red, Green, Blue, prefixed with a hash (#) sign. For example, full red is encoded as ―#ff0000‖ (with no quotation marks). Note that this is the only format ed. The exception is the word ―none,‖ which implies an opacity value of 0.

fill-rule

‖nonzero‖ or ―even-odd‖

The 'fill-rule' property indicates the algorithm that is to be used to determine what parts of the canvas are included inside the shape. For a simple, non-intersecting path, it is intuitively clear what region lies "inside"; however, for a more complex path, such as a path that intersects itself or where one subpath encloses another, the interpretation of "inside" is not so obvious. The 'fill-rule' property provides two options for how the

830


ed SVG Element Types Fill Characteristics

Value

Description

fill

Fill color

Specifies the fill color for closed symbols like boundaries and complex strings. The color value ed is RGB-encoded using two hexadecimal digits per primary-color component, in the order Red, Green, Blue, prefixed with a hash (#) sign. For example, full red is encoded as ―#ff0000‖ (with no quotation marks). Note that this is the only format ed. The exception is the word ―none,‖ which implies an opacity value of 0. inside of a shape is determined, nonzero and evenodd. nonzero: This rule determines the "insideness" of a point on the canvas by drawing a ray from that point to infinity in any direction and then examining the places where a segment of the shape crosses the ray. Starting with a count of zero, add one each time a path segment crosses the ray from left to right, and subtract one each time a path segment crosses the ray from right to left. After counting the crossings, if the result is zero, the point is outside the path; otherwise, it is inside. Evenodd: This rule determines the "insideness" of a point on the canvas by drawing a ray from that point to infinity in any direction and counting the number of path segments from the given shape that the ray crosses. If this number is odd, the point is inside; if even, the point is outside.

fill-opacity

Fill opacity

Controls the opacity of an area by giving fill-opacity a value ranging from 0.0 to 1.0; 0.0 is entirely transparent, and 1.0 is entirely opaque.

Font Characteristics: Specifies the way that text will be drawn. Font Characteristics

Value

Description

font-size

Size of font

The property is the size of the font. units (points) are assumed, and no other units are ed.

font-family

Family name

The generic family names are ―serif‖, ―sans-serif‖, and ―monospace‖. Also ed are the standard fonts available on the system.

font-style

―italic‖ or ―normal‖

There are two types of font styles that are ed, which are listed in the value field.

font-weight

―bold‖ and ―normal‖

There are two types of font weights that are ed, which are listed in the value field.


831

ed SVG Element Types Font Characteristics

Value

Description

text-decoration

―none‖, There are three types of text decorations that are ―underline‖, or ed, which are listed in the value field. ―line-through‖

Transform Attribute The value of the transform attribute is a , 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 Specifies a transformation in the form of a transformation matrix of six values. Matrix (a,b,c,d,e,f) is equivalent to ,d,e,f) applying the transformation matrix [a b c d e f].

translate

translate(< Specifies a translation by tx and ty. If is not provided, tx> [ ]) it is assumed to be 0.

scale

scale(<sx> Specifies a scale operation by sx and sy. If <sy> is not [<sy>]) provided, it is assumed to be equal to <sx>.

rotate

rotate( [ ])

skewX

―skewX(ske Specifies a skew transformation along the x-axis. w-angle)‖

skewY

―skewY(ske Specifies a skew transformation along the y-axis. w-angle)‖

Specifies a rotation by degrees about a given point. If optional parameters and are not supplied, the rotate is about the origin of the current coordinate system. The operation corresponds to the matrix [cos(a) sin(a) -sin(a) cos(a) 0 0]. If optional parameters and are supplied, the rotate is about the point ( , ). The operation represents the equivalent of the following specification: translate( , ) rotate( ) translate(- , - ).

All numeric values are real numbers. If a list of transforms is provided, the net effect is as if each transform had been specified separately in the order provided. For example, is functionally equivalent to:

832


ed SVG Element Types The transform attribute is applied to an element before processing any other coordinate or length values supplied for that element. In the element the x, y, width, and height values are processed after the current coordinate system has been scaled uniformly by a factor of 2 by the transform attribute. Attributes x, y, width, and height (and any other attributes or properties) are treated as values in the new coordinate system, not the previous coordinate system. Thus, the above 'rect' element is functionally equivalent to:

SVG Symbol Metadata XML Schema The SVG Symbol Metadata XML schema provides extensions to the SVG schema to the use of parametric characteristics within an SVG file. These elements are only understood by GeoMedia's SVG interpreter, but the format conforms with the SVG specification. As new releases come out, we expect additional elements to be added to the .xsd. With the original version of this schema released with GeoMedia Professional 6.0, only one parametric element is ed (textContent). There are several means of identifying an XML schema definition. For GeoMedia we have these design goals for schema definitions:  Short namespace prefixes so as not to burden the XML (and your vision), and for consistency with other prefixes.  Consistent names to ensure ease in correlation of schema file, namespace, and namespace prefix.  A form of designation specific to GeoMedia so that we can recognize our own constructs. To this end a single base schema name must be provided, which is no greater than six characters in length, and which uniquely identifies this XML schema within the GeoMedia product line. The length limit is imposed in order to ensure that the target name space prefix, which appears repeatedly in XML, is not unduly long. The base schema name has no meaning of its own, but it is used in automatically constructing the name of the schema file to be delivered with the product(s), the string for the target namespace, and the abbreviated prefix used for that target namespace. These values are given, and calculated, in this table: The schema identifier information used to identify the XML schema definition for GeoMedia is as follows: Identifier

Value

Base schema name

svgsym

Schema file name

gmsvgsym.xsd

Target namespace URI

http://ww.intergraph.com/GeoMedia/svgsym

Namespace prefix

gmsvgsym

The XML schema definition references the following external schema definition:


833

ed SVG Element Types Namespace Prefix

Target Namespace

xs

http://www.w3.org/2001/XMLSchema

Header Information The XML schema includes the following header information:  XML version and encoding  Target and reference namespaces  Version information 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 the link (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:

834



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: optional Default: 1.0 element symbolParameters/textContent Description: The textContent element defines a relationship between a style property object and a text element in the SVG file. The textContent element indicates to the GeoMedia symbol interpreter to update the contents of the text section of the text element with the string pulled from the style property. The replaceID holds the id of the text item to be replaced, with the string returned from the style property. The styleProp holds the name of the style property whose contents are used to update the string of the SVG text component. Parameters isRef: 0 Content: complex Attributes: Name: replaceID Type: xs:string Use: required Name: styleProp Type: xs:string Use: required element Toolbar/Button/ProgID Description: The ProgID of the command. Type: xs:string stimpeType VersionType Type: restriction of xs:string Used By: attribute symbolParameters/@version Facets: enumeration 1.0


835


XML Source The following is the XML source code for this schema definition: <xs:schema targetNamespace="http://www.intergraph.com/GeoMedia/svgsym" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:gmsvgsym="http://www.intergraph.com/GeoMedia/svgsym"> <xs:simpleType name="VersionType"> <xs:restriction base="xs:string"> <xs:enumeration value="1.0"/> <xs:element name="symbolParameters"> <xs:annotation> <xs:documentation>A set of parameters used to control the contents of SVG symbols via style properties <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:complexType> <xs:attribute name="replaceID" type="xs:string" use="required"/> <xs:attribute name="styleProp" type="xs:string" use="required"/> <xs:attribute name="version" type="gmsvgsym:VersionType" use="optional" default="1.0"/>

Example <svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:gmsvgsym="http://www.intergraph.com/GeoMedia/svgsym"> <metadata>

836


ed SVG Element Types <symbol id="Symbol_1" viewBox="0 0 400 388" style="stroke-line:round"> <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" /> DPW <use xlink:href="#Symbol_1" x="100" y="100"/>


837


838


APPENDIX K

Additional Geocoding Information This appendix contains information of the following geocoding items:  Address Geocoding - Concepts and Workflows  Geocoding Models and Parsing Rules  Intersection Geocoding  Sound Like Algorithms

Address Geocoding - Concepts and Workflows This section discusses various important concepts that s need to be familiar with when working with Address Geocoding.

Functional Overview The following diagram shows the basic operations involved with address geocoding when using the AGI geocoding engine:


839

Additional Geocoding Information

Architectural Overview To better depict the various processes involved with the architecture in more detail, these processes are described using separate sections and diagrams.

Address Parsing Rules The first thing that must be determined is what constitutes an address for a given geocoding action. An address is made up of a number of elements, and the geocoding system includes components that can recognize a textual input structure and determine the elements of the address. The parsing technique uses a state recognition algorithm based on the Hidden Markov Modelling (HMM). The Define Parsing Rules utility builds and tests the XML-formatted file that describes an address parsing rules in of an HMM. For higher-order address constructs, address parsing rules can reference other parsing rules.

Address Transformations The parsing rules file contains rules for transforming a single string into several fields. Often the address is defined by two or even more strings. The address transformation contains a set of Address Parsing Rules that provides a way to transform addresses from one (source) format to another (target) format. Both source and target formats can consist of multiple strings. The address transformations provide a way to transform addresses from different source formats to the same target format.

840



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 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.


841


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 addresses to be geocoded are encapsulated in the AGI file for later use.

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.

842


Additional Geocoding Information These transformation objects expose the address structure and provide a means of performing the transformation from the source element(s) to the target element(s).

An address transformation is a slight expansion to the concept of parsing in which a mapping between different address formats is expressed, for example: Reference Data

Example

Address Elements

Street Name

Main Street

Directional Prefix

Example

Street Name

Main

Street Type

Street

Street Type Suffix City

MILTONS

City

Miltons

State

Queensland

State

QLD

Postcode

4064

PostalCode

4064

Input

Example

Address Elements

Example

Street Address

1299 Main Street

House Number

1299

Directional Prefix Street Name

Main

Street Type

Street


MILTONS

City

Miltons

State

Queensland

State

QLD

Postcode

4064

PostalCode

4064


843

Additional Geocoding Information Input

Example

Address Elements

Example

Full Address

1299 Main Street MILTON QLD 4064

House Number

1299

Directional Prefix Street Name

Main

Street Type

Street


Milton

State

QLD

PostalCode

4064

Address Matching A private, low-level component known as GMAddressMatcher is used as the core geocoding technology used in GeoMedia. To allow for additional or third-party geocoding technologies to be used, a public interface (IGMGeocodingEngine) has been defined and is known as the Geocoding Engine interface. The geocoding engine provided with the GeoMedia product family is one such implementation of the interface, and is called the AGI Geocoding Engine. The AGI Geocoding Engine wraps the functionality provided by the GMAddressMatcher object.

844



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. Reverse geocoding is not ed by the desktop GeoMedia Find Address and Geocode Addresses commands.

Geocoding Directory Service The Geocoding Directory is used to allow a single name to be used to identify an instance of an address geocoding engine and its associated dataset. In the following example, an identifier of ―AL‖ has been supplied as the named identifier for a particular geocoding engine and geocoding dataset. The GeocodingDirectoryService (GDS) can then check the directory and expose the unique identifier (through the Type property) for the correct engine to instantiate and the initialization string for the engine. In the case of the AGIGeocodingEngine, the string is a path to the required AGI file. This approach allows for third-party engines to be plugged in. Such third-party engines must conform to the IGMGeocodingEngine interface as mentioned previously. The GeocodingDirectoryService also exposes address transformations that can be used for this geocoding dataset. The AGI file contains these named transformations and all the data required to instantiate the objects that perform the transformations. The transformations required for a particular dataset are exposed through various methods of the GDS.


845

Additional Geocoding Information Further metadata about the dataset, such as the BoundingBox, the Coordinate System, and which operations are ed are exposed as properties on the GeocodingDataset object that is returned from the GeocodingDirectoryService.

846



Component Interaction The following diagram depicts the geocoding subsystem as a whole:


847


Design Elements The overall design of the geocoding system, as represented by the components in the previous systems diagram, can be broken down into several distinct families:  Address Geocoding Index components—Generate datasets for geocoding and reverse geocoding.  Geocoding Model components—Generate rules for performing geocoding according to dataset address configuration, input data configuration, and locale-specific addressing rules.  Address Transformation components—Describe the schema of incoming or outgoing addresses, both the elements of the addresses and their storage normalization.  Geocoding components—Perform geocoding using input address elements already parsed and transformed into the format required for the dataset.  Reverse Geocoding components—Perform reverse geocoding using an input coordinates and address transformation rules. Within these families are found several different types of components:  Data components  Configuration components  Software components (services, pipes, commands, utilities, and web services)

Data Components The data components consist of the GDO warehouse and the Address Geocoding Index (AGI). GDO Warehouse The GDO warehouse is the source GeoMedia-accessible dataset that contains the features the geocoding index is derived from. Typically this would contain the street centerline data, but it could also contain data suitable for rooftop geocoding. This data is read and stored to an Address Geocoding Index (AGI) through the Publish Address Geocoding Index utility. Address Geocoding Index (AGI) The Address Geocoding Index (AGI) is a binary file, in a GeoMedia-proprietary format, optimized and indexed for rapid geocoding. It is created by the Publish Address Geocoding Index utility. This file is used by the AGIGeocodingEngine and the AddressTransformations object. The publishing utility also persists address transformations information internally to the AGI file. This ensures the AGI file is fully transportable, as it allows address transformations applicable to the data to be performed without having to maintain a link between the AGI file and other configuration files. This file can also be used for reverse geocoding operations.

Configuration Components The Configuration components consist of the Geocoding Model, Geocoding Dataset, Geocoding Directory, and the Address Parsing Rules. Geocoding Model The Geocoding Model is an XML document describing a geocoding model. A geocoding model (GCM) definition describes -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 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 interface.

848


Additional Geocoding Information 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 ed 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 s 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 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 ed by each of them. For GeoMedia‘s implementation of the GeocodingEngine, these datasets each consist of a single, portable file known as an AGI file. This GeocodingDirectoryService object allows client software to easily obtain information about the geocoding datasets contained in the directory, along with address format definitions. The GeocodingDirectoryService also specifies a number of address transformations available to transform input addresses conforming to various definitions into the required fields for address matching against a particular dataset. The Geocoding Directory consists of one or more defined geocoding datasets, each of which has a unique identifier for the applicable engine, and an associated connection string intended to link the object to its source data. This design is intended to allow a multi-row processing operation (that is, a pipe) to geocode each record against a different geocoding engine as necessary, based on an identifying field (database attribute or interface data entry control). For example, addresses in Alabama may be geocoded against an Alabama AGI, while those for Georgia would be geocoded against a Georgia AGI where the StateName field of the input recordset contained the identifying name for the applicable dataset. The Publish Address Geocoding Index utility can create a single-dataset directory, and also has the capability to alter an existing dataset entry in an existing multi- or single-dataset Geocoding Directory. A Geocoding Directory may also be created manually and/or edited using an appropriate text/XML editor.


849

Additional Geocoding Information 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. Address Parsing Rules The Address Parsing Rules are in an XML document conforming to the Parsing Rules XML Schema. The parsing rules are created either manually or through the Define Parsing Rules utility. They are used by the AddressTransformations object to instantiate AddressTransformation objects used to transform input address types to the correct field format used in matching operations. The AddressTransformation operations wrap a lower level private API that uses the Hidden Markov Modelling (HMM) technique for identifying patterns in unstructured text. This technique has been implemented and used successfully as a generic address parsing operation in the private API. This API requires the rules for such transformations to be initially stored in an XML document. An XML schema describing this file format forms part of the system. For the Intergraph implementation of the geocoding engine interface (AGIGeocodingEngine), the AGI files contain information that is extracted by the service layer to create the correct transformation objects.

Software Components – Services The software components consist of the Geocoding Engine interface, the Reverse Geocoding Engine interface, and the GeocodingDirectoryService. Geocoding Engine Interface This COM (dispatch) interface definition provides a generic interface by which any number of independent (Intergraph-developed or third-party) geocoding implementations may be written, using alternate data structures and/or underlying software/services, and which can be plugged into the GeoMedia geocoding system. This interface may be made available to individual partners with sufficient business justification. At this time only a single geocoding engine implementation is planned for delivery with GeoMedia, the AGIGeocodingEngine based on AGI files. GeocodingResults Interface The GeocodingEngine interface conveys its geocoding results through a GeocodePoints object. This object provides, for each input address, geocoding results such as the following: 

Point geometry



Match score





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 GeocodingDataset object and also the AddressTransformation object as a public API, and in turn its member objects. This component is public.

Software Components – Pipe The pipe consists of the GeocodePipe.

850


Additional Geocoding Information GeocodePipe This pipe geocodes addresses from a recordset, using the GeocodingEngine interface to generate locations from addresses, and adding fields for an output point geometry and other geocoding status information and match characteristics. It is of the base table/add fields pipe design family, and s notification and persistence. This component is public.

Software Components – Commands There are two commands, Geocode Addresses and Find Address. Geocode Addresses Command The Geocode Addresses command is an Analysis command that geocodes all of the features in an input (normally nongraphic) feature class or query containing address information, producing a query on output with point geometries. Find Address Command The Find Address command is a View command that geocodes an address hand-entered through a dockable control, producing a dynamic point on the map display and panning to the location of that point.

Software Components – Utilities There are two utilities, the Publish Address Geocoding Index utility and the Define Parsing Rules utility. Publish Address Geocoding Index Utility This standalone utility provides the ability to publish GDO data (single feature class) to an AGI for subsequent geocoding. It provides both a graphical interface, as well as a command-line interface for automated publishing. See the “Publish Address Geocoding Index Utility Help” for information on this utility. Define Parsing Rules Utility The Parsing Rules files needed for the address parsing components are generated by a graphical interface utility (Define Parsing Rules) to guide one in building such files. This utility helps one create a well-formed HMM (Hidden Markov Model) definition file conforming to the requirements of the private API for address parsing. The of the utility would generally be a system type of person. See the “Defining Parsing Rules” section of the "Geocoding" section for information on this utility.

Geocoding Models and Parsing Rules This section discusses and provides examples of geocoding models and parsing rules delivered with GeoMedia.


851


US Geocoding Models and Parsing Rules Geocoding Models US_Cities_gcm.xml A rooftop geocoding model for geocoding US cities. Reference Data address format(s):  Full city name (for example, Madison, AL) Full city name is parsed with the US_Cities.xml parsing rules. Geocoding address format(s):  City name with state name (for example, Madison, AL) City name with state name is parsed with the US_Cities.xml parsing rules.  City name + separate state name (for example, Madison + AL) Values are not parsed/standardized. Referenced Parsing Rules:  US_cities.xml

US_Post_gcm.xml A centerline geocoding model for US post addresses. Reference Data address format(s):  Street name + left/right City + left/right State + left/right ZIP (for example, E Main Street + Madison + AL + 12345) Can be used with GDT data.  Street name is parsed with the US_street.xml parsing rules. City is concatenated with State and then parsed with the US_Cities.xml parsing rules. The city and state names are defined separately for left and right sides of the street centerline. ZIP is parsed with US_ZIP.xml. ZIP is defined separately for left and right sides of the street centerline.  Prearranged street name + left/right City + left/right State + left/right ZIP (for example, E + Main + ST + Madison + AL + 12345) Can be used with GDT data (though not recommended as their data are structured in a different way than we expect).  Prearranged street name is not parsed/standardized. It is supposed to consist of: Street Prefix, Street Pretype, Street Name, Street Type and Street Suffix.  City is concatenated with State and then parsed with the US_Cities.xml parsing rules. The city and state names are defined separately for left and right sides of the street centerline.  ZIP is parsed with US_ZIP.xml. ZIP is defined separately for left and right sides of the street centerline.  Re-ed 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-ed 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.

852


Additional Geocoding Information City is concatenated with State and then parsed with the US_Cities.xml parsing rules. The city and state names are defined separately for left and right sides of the street centerline.  ZIP is parsed with US_ZIP.xml. ZIP is defined separately for left and right sides of the street centerline.  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. 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 (for example, 12 E Main St Madison AL, 12345) Post address is parsed with the US_Post.xml parsing rules. Intersections cannot be parsed.  Post address or intersections (for example, 12 E Main St Madison AL, 12345 or Main St & Shiny BLVD, Venice Ca, 12345) Post address or intersections is parsed with the US_Post_c.xml parsing rules. Intersections can have the following format: Street1 & Street2, City State Zip Where all elements besides Street1 and Street2 are optional; City, State, and Zip can be present in arbitrary order and, if present, are applied to both street addresses.  Street Address, City, State, ZIP (for example, 12 E Main St + Madison + AL + 12345) Street Address is parsed with the US_Streets.xml parsing rules.  City is concatenated with State and then parsed by the US_Cities.xml.  ZIP is parsed with the US_ZIP.xml parsing rules. Referenced 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. All other address elements are used ―as is‖. Geocoding address format(s):  House number + Street name + Crossing street name + City + ZIP


853

Additional Geocoding Information Both Street name and Crossing street name are parsed with the US_street.xml parsing rules. All other address elements are used ―as is‖. Referenced Parsing Rules:  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):  Full street address + ZIP (for example, E Main Street + 12345) Can be used with GDT and TeleAtlas data. Full street address is parsed with the US_street.xml parsing rules. It is also possible to define alternative street name. ZIP is parsed with US_ZIP.xml. ZIP is defined separately for left and right sides of the street centerline.  Prefix,Name,Type,Suffix + ZIP (for example, E + Main + ST + 12345) Can be used with MadisonCountyAL database delivered with GeoMedia. Prefix,Name,Type,Suffix are concatenated and then parsed with US_street.xml. ZIP is parsed with US_ZIP.xml. ZIP is defined separately for left and right sides of the street centerline.  Prefix + Pretype + Name + Type + Suffix + ZIP (for example, E + Main + ST + 12345) Can be used with GDT data (though not recommended as their data are structured in a different way than we expect). Prefix, Pretype, Name, Type and Suffix are taken "as is" and not standardized. ZIP is parsed with US_ZIP.xml. ZIP is defined separately for left and right sides of the street centerline. Geocoding address format(s):  Post address (for example, 12 E Main St, 12345) Post address is parsed with the US_Streets.xml parsing rules. Intersections cannot be parsed.  Post address or intersections (for example, 12 E Main St, 12345 or Main St & Shiny BLVD) Post address or intersections is parsed with the US_Streets_c.xml parsing rules. Intersections can have the following format: Street1 & Street2, Zip Where Zip is optional and, if present, is applied to both street addresses.  Street address + ZIP (for example, 12 E Main St + 12345) Street Address is parsed with the US_Streets.xml parsing rules. ZIP is parsed with the US_ZIP.xml parsing rules.  House number + Street name + Crossing street + ZIP (for example, 12 + E Main St + 12345 or Main St + Shiny BLVD) House number is not parsed/standardized. Street name is parsed with the US_Street.xml parsing rules. Crossing street is parsed with the US_Street.xml parsing rules.

854


Additional Geocoding Information 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. Referenced 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.  Madison Output record consists of two fields:  City name  State name

US_POBox.xml This file contains parsing rules for US PO box addresses. It is used by the US_Post.xml and US_Post_c.xml address parsing rules. Sample text recognized by the rules:  P O. BOX 34 Output record contains a single field:  PO BOX (PO BOX 34)

US_Post.xml This file contains parsing rules for US post addresses. It recognizes PO Boxes, Rural Routes, phone numbers, and secondary unit designators. Sample text recognized by the rules:  1000 AVENUE E  1000 AVENUE E SHERMAN, TX  1000 AVENUE E 76943  1000 AVENUE E SHERMAN, TX 76943  1400 S COMMERCIAL AVENUE, PO BOX 72, SHERMAN, TX 79501-0072  RR 1 BOX 82, SHERMAN, TX 76653  2530 UNIVERSITY BLVD SHERMAN TX 77005 713.522.2660  9077 FLAGSTONE #2118 MADISON AL 35758 Output record consists of nine fields:  House number  Street prefix  Street pretype


855

Additional Geocoding Information      

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 s intersections, recognized PO Boxes, Rural Routes, phone numbers, and secondary unit designators. Sample text recognized by the rules:  1000 AVENUE E  1000 AVENUE E SHERMAN, TX  1000 AVENUE E 76943  1000 AVENUE E SHERMAN, TX 76943  1400 S COMMERCIAL AVENUE, PO BOX 72, SHERMAN, TX 79501-0072  RR 1 BOX 82, SHERMAN, TX 76653  2530 UNIVERSITY BLVD SHERMAN TX 77005 713.522.2660  WALNUT & 6TH, PO BOX 39, SHERMAN, TX 79001-0039  CORNER OF WASHINGTON AVENUE AND MEMORIAL PARKWAY  9077 FLAGSTONE #2118 MADISON AL 35758 Output record consists of nine fields:  House number  Street prefix  Street pretype  Street name  Street type  Street suffix  City name  State name  ZIP If an intersection is recognized, the output contains two records (one for every crossing street). The intersection addresses can have the following format: Street1 & Street2, City State ZIP City, State, and ZIP can be present in arbitrary order. In this case, the 'House number' field in both output records is empty and ‗City name‘, ‗State name‘, and ‗ZIP‘ are the same for both records.

US_RR.xml This file contains parsing rules for US rural route and highway contract addresses. It is used by the US_Post.xml and US_Post_c.xml address parsing rules. Sample text recognized by the rules:  RURAL ROUTE 54 BOX 34  STAR ROUTE 3 BOX 1

856


Additional Geocoding Information Output record consists of three fields:  Box number (34)  RR identifier (RR)  RR number (54)

US_street.xml This file contains parsing rules for US street names. It is referenced from the US_Post.xml and US_Post_c.xml address parsing rules. Sample text recognized by the rules:  WASHINGTON COUNTY RD 354  US-45  AVE J N  1000TH ST  BOB WALLACE AVE SW Output record consists of five fields:  Street prefix  Street pretype  Street name  Street type  Street suffix

US_Streets.xml This file contains parsing rules for US street addresses. It recognized PO Boxes, Rural Routes, phone numbers, and secondary unit designators. It is identical to US_Post.xml but does not output the City and State names (if any).

US_Streets_c.xml This file contains parsing rules for US street addresses. It s 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 Output record consists of two fields:  ZIP or first part of ZIP+4 code Second part of ZIP+4 code


857


Files Referenced by Parsing Rules Numeric.csv List of numeric street names with aliases. It is referenced from US_street.xml.

US_Cities_sp1.csv A list of US cities that can confuse the parser, for example:  'EAST HAMPTON' ('East' can be erroneously reported as street suffix.)  'FORT WORTH' ('Fort' can be erroneously reported as street type.) It is referenced from US_Cities.xml.

US_secondary_units.csv List of secondary units designators in the US addresses ('FLOOR', 'ROOM', and so forth). It is referenced from US_Post.xml and US_Post_c.xml.

US_states.csv List of US state names. It is referenced from US_Cities.xml.

US_street_types.csv List of street types with aliases ('ST', 'FREEWAY', and so forth). It is referenced from US_street.xml.

Canadian Geocoding Models and Parsing Rules Geocoding Models CA_Post_gcm.xml A centerline geocoding model for Canadian post addresses. Reference Data address formats:  Street name + Alt street name + left/right City + left/right Postal code (for example, QUEENS QUAY WEST + TORONTO, ON + M7Y7S8) Street name is parsed with the CA_street.xml parsing rules. Alt street name is parsed with the CA_street.xml parsing rules. City is parsed with the CA_Cities.xml parsing rules. City names are defined separately for left and right sides of the street centerline. Postal code is parsed with CA_Postalcode.xml parsing rules. Postalcodes are defined separately for left and right sides of the street centerline.  Prefix + Name + Type + Suffix + left/right City + left/right Postal code (for example, QUEENS + QUAY + WEST + TORONTO, ON + M7Y7S8) Prefix, Name, Type, and Suffix are concatenated and parsed with the CA_street.xml parsing rules. City is parsed with the CA_Cities.xml parsing rules. City names are defined separately for left and right sides of the street centerline. Postal code is parsed with CA_Postalcode.xml parsing rules.

858


Additional Geocoding Information Postalcodes are defined separately for left and right sides of the street centerline. Prefix + Name + Type + Suffix + City ID + Province + left/right Postal code (for example, QUEENS + QUAY + WEST + 11345678 + ONTARIO + M7Y7S8) Prefix, Name, Type, and Suffix are concatenated and parsed with the CA_street.xml parsing rules. City ID is used "as is". Province is used "as is". Postal code is parsed with CA_Postalcode.xml parsing rules. Postalcodes are defined separately for left and right sides of the street centerline. Geocoding address formats:  Post address (for example, 3726 RUE JEAN TALON EST MONTREAL, QC H2A 1X9) Post address is parsed with the CA_Post.xml parsing rules. Intersections cannot be parsed.  Post address or intersections (for example, 3726 RUE JEAN TALON EST MONTREAL, QC H2A 1X9 or MAIN STREET & 1ST AVENUE, ONTARIO) Post address or intersections is parsed with the CA_Post_c.xml parsing rules. Intersections can have the following format: Street1 & Street2, City Province Postalcode, where all elements besides Street1 and Street2 are optional; City, Province, and Postalcode can be present in arbitrary order and (if present) are applied to both street addresses.  Street Address + City name + Postal code (for example, 3726 RUE JEAN TALON EST + MONTREAL, QC + H2A 1X9) Street Address is parsed with the CA_Post.xml parsing rules. City name, province name and postalcode (if any) are ignored. City name is parsed with the CA_Cities.xml parsing rules Postal code is parsed with the CA_Postalcode.xml parsing rules.  Street address + City ID + Province + Postal code (for example, 3726 RUE JEAN TALON EST + 1139822 + QC + H2A 1X9) Street Address is parsed with the CA_Post.xml parsing rules. City name, province name and postalcode (if any) are ignored. City ID is used "as is". Province is used "as is". Postal code is parsed with the CA_Postalcode.xml parsing rules.  House number + Street name + City name + Postal code (for example, 3726 + RUE JEAN TALON EST + MONTREAL, QC + H2A 1X9) House number is used "as is". Street name is parsed with the CA_street.xml parsing rules. City name is parsed with the CA_Cities.xml parsing rules Postal code is parsed with the CA_Postalcode.xml parsing rules. Referenced Parsing Rules:  CA_street.xml  CA_Cities.xml  CA_Postalcode.xml  CA_Post.xml  CA_Post_c.xml




859

Additional Geocoding Information CA_StreetsWithPostcode_gcm.xml A centerline geocoding model for Canadian street addresses (without city and province names). Reference Data address formats:  Street name + Alt street name + left/right Postal code (for example, QUEENS QUAY WEST + M7Y7S8) Street name is parsed with the CA_street.xml parsing rules Alt street name is parsed (if present) with the CA_street.xml parsing rules Postal code is parsed with CA_Postalcode.xml. Postal codes are defined separately for left and right sides of the street centerline.  Prefix + Name + Type + Suffix + left/right Postal code (for example, QUEENS + QUAY + WEST + M7Y7S8) Prefix, Name, Type, and Suffix are concatenated and parsed with the CA_street.xml parsing rules. Postal code is parsed with CA_Postalcode.xml parsing rules. Postalcodes are defined separately for left and right sides of the street centerline. Geocoding address formats:  Post address (for example, 3726 RUE JEAN TALON EST MONTREAL, QC H2A 1X9) Post address is parsed with the CA_Streets.xml parsing rules. Intersections cannot be parsed. Although the address can contain city and province names, they are not used on geocoding.  Post address or intersections (for example, 3726 RUE JEAN TALON EST MONTREAL, QC H2A 1X9 or MAIN STREET & 1ST AVENUE, ONTARIO) Post address or intersections is parsed with the CA_Streets_c.xml parsing rules. Intersections can have the following format: Street1 & Street2, City Province Postalcode, where all elements besides Street1 and Street2 are optional; City, Province, and Postalcode can be present in arbitrary order and (if present) are applied to both street addresses. City and Province are ignored on geocoding.  Street Address + Postal code (for example, 3726 RUE JEAN TALON EST + H2A 1X9) Street Address is parsed with the CA_Streets.xml parsing rules. City name, province name and postalcode (if any) are ignored. Postal code is parsed with the CA_Postalcode.xml parsing rules. Referenced Parsing Rules:  CA_street.xml  CA_Postalcode.xml  CA_Streets.xml  CA_Streets_c.xml

Parsing Rules CA_Cities.xml The file contains parsing rules for Canadian city name, which can be optionally postfixed with the province name. It is used by CA_Post_gcm.xml geocoding model and CA_Post.xml and CA_Post_c.xml parsing rules.

860


Additional Geocoding Information Sample text recognized by the rules:  MOUNT HOPE, ON.  Toronto Output entity consists of 2 elements:  City name  Province name

CA_POBox.xml The file contains parsing rules for Canadian PO box addresses. It is used by CA_Post.xml and CA_Post_c.xml parsing rules. Sample text recognized by the rules:  PO BOX 40  PO BOX 4001 STN A Output entity contains a single output element:  PO Box

CA_Post.xml The file contains parsing rules for Canadian post addresses. It recognized PO Boxes, Rural Routes and secondary unit designators. It is used by CA_Post_gcm.xml geocoding model. Sample text recognized by the rules:  100 MAIN STREET EAST  9149 AIRPORT ROAD, MOUNT HOPE  6790 KITIMAT ROAD, UNIT 4 MISSISSAUGA ON CANADA L5N 5L9  271 6TH CONCESSION ROAD, RR#1, MILLGROVE  42-302 48TH STREETSASKATOON SK S7K 6A4  PO BOX 34 A single output entity consists of 9 output elements:  House number  Street prefix  Street pretype  Street name  Street type  Street suffix  City name  Province name  Postal code

CA_Post_c.xml The file contains parsing rules for Canadian post addresses. It s intersections, recognized PO Boxes, Rural Routes and secondary unit designators. It is used by CA_Post_gcm.xml geocoding model. Sample text recognized by the rules:  100 MAIN STREET EAST  9149 AIRPORT ROAD, MOUNT HOPE  6790 KITIMAT ROAD, UNIT 4 MISSISSAUGA ON CANADA L5N 5L9


861

Additional Geocoding Information  271 6TH CONCESSION ROAD, RR#1, MILLGROVE  42-302 48TH STREETSASKATOON SK S7K 6A4  PO BOX 34  MAIN STREET & 1ST AVENUE, ONTARIO  CORNER OF RUE DE TURENNE AND RUE DE BRETAGNE Every output element consists of 9 output entities:  House number  Street prefix  Street pretype  Street name  Street type  Street suffix  City name  Province name  Postal code If an intersection is recognized, the output contains two elements (one for every crossing street). The intersection addresses can have the following format: Street1 & Street2, City Province Postalcode, City, Province, and Postal code can be present in arbitrary order. In this case the 'House number' output entity in both output elements is empty and 'City name', 'Province name' and 'Postal code' are the same. Intersecting streets can be separated with 'and', '&', 'AT', '@', 'ET', '/' or 'À'.

CA_RR.xml The file contains parsing rules for Canadian rural route addresses. It is used by CA_Post.xml and CA_Post_c.xml parsing rules. Sample text recognized by the rules:  RR 8 STN MAIN  RR #13 A single output element consists of 3 output entities:  Rural route box name or number  RR identifier (RR)  RR number

CA_street.xml The file contains parsing rules for Canadian street names. It is referenced from CA_Post_gcm.xml and CA_StreetsWithPostcode_gcm.xml geocoding models and CA_Post.xml and CA_Post_c.xml parsing rules. Sample text recognized by the rules:  CÔTE-DU-MILLE RUE  ROUTE 143 SUD  LA VÉRENDRYE OUEST BOULEVARD  AUTOROUTE DE LA GATINEAU A single output element consists of 5 output entities:  Street prefix  Street pretype

862


Additional Geocoding Information   

Street name Street type Street suffix

CA_Streets.xml The file contains parsing rules for Canadian street addresses. It is referenced from CA_StreetsWithPostcode_gcm.xml geocoding model. It is identical to CA_Post.xml but has no output the City and Province names in output (if any).

CA_Streets_c.xml The file contains parsing rules for Canadian street addresses. It is referenced from CA_StreetsWithPostcode_gcm.xml geocoding model. It is identical to CA_Post_c.xml but has no output the City and Province names in output (if any).

CA_Postalcode.xml The file contains parsing rules for Canadian postal codes. It is referenced from CA_Post_gcm.xml and CA_StreetsWithPostcode_gcm.xml geocoding models and CA_Post.xml and CA_Post_c.xml parsing rules. Sample text recognized by the rules:  K1R7S8  K1R 7S8 A single output element consists of a single entity:  Postal code

Files Referenced by the Parsing Rules CA_Cities_sp1.csv A list of Canadian cities that can confuse the parser. For example:  'ST. ALBERT' ('ST' can be erroneously reported as street type)  'NORTH PERTH' ('NORTH' can be erroneously reported as street suffix). It is referenced from CA_Cities.xml.

CA_territories.csv List of Canadian provinces and territories. It is referenced from CA_Cities.xml.

CA_street_types.csv List of street types with aliases ('ST', 'FREEWAY' etc). It is referenced from CA_street.xml.

CA_street_directions.csv List of street directions with aliases ('NE', 'NORTHEAST', 'NORD-EST', and so forth). It is referenced from CA_street.xml.

CA_street_pretypes.csv List of street pretypes with aliases ('HWY', 'HIGHWAY', and so forth). It is referenced from CA_street.xml.


863


Japanese Geocoding Models and Parsing Rules Geocoding Model JP_Post_gcm.xml A rooftop geocoding model for Japanese addresses. The preprocessing options are:  To upper case. This affects Latin letters that can appear in Banchi. Small hiragana/katakana letters are not affected.  To full-width.  To hiragana. This and above convert Katakana and Katakana half-width characters to Hiragana. Note that this also converts Latin letters and digits to their double width equivalents.  Fold compatibility zone characters. This converts double width Latin letters and digits (they reside in Unicode compatibility zone) to their standard representation.  Convert blanks to spaces.  Remove multiple spaces. These replace (multiple) blank characters with a single ASCII space character. Reference Data address format: 

Separate address elements: 郵便番号 + 都道府県 + 市区町村 + 大字・町丁目 + 街区符号・地番 + 号 (e.g. 〒150-2345 + 東京都 + 渋谷区 + 本町 2 丁目 + 4 + 7). The address format and the default source attribute names are taken from data published by MLIT (Ministry of Land, Infrastructure, Transport and Tourism). 郵便番号 is parsed with the JP_Postcode.xml parsing rules. Output is assigned to the Postcode base address element. 都道府県 is parsed with the JP_todoufuken.xml parsing rules. Output is assigned to the Todoufuken base address element. 市区町村 is parsed with the JP_shikuchouson.xml parsing rules. Output is assigned to the Shikuchouson base address element. 大字・町丁目 is parsed with the JP_azachome.xml and JP_azachome_s.xml parsing rules. Output is assigned to the Oaza and Chome base address elements. If the results of parsing are different, two addresses are stored in the reference data for a record. These two addresses differs only in Oaza base address element. 街区符号・地番 is parsed with the JP_banchi.xml parsing rules. Output is assigned to the Banchi base address element.

号 is parsed with the JP_go.xml parsing rules. Output is assigned to the Go base address element. Geocoding address format(s): 

Postal address: 住所全体 (e.g. 〒100-8799 東京都千代田区丸の内二丁目 7 番 2 号). The format is used by the Web service for free-formed addresses. 住所全体 is parsed with the JP_Post.xml parsing rules.



Separate address elements: 郵便番号 + 都道府県 + 市区町村 + 大字・町 + 丁目 + 街区符号・地番 + 号 (e.g. 〒100-8799 + 東京都 + 千代田区 + 丸の内 + 二丁目 + 7 番 + 2 号). 郵便番号 is parsed with the JP_Postcode.xml parsing rules.

864


Additional Geocoding Information 都道府県 is parsed with the JP_todoufuken.xml parsing rules. 市区町村 is parsed with the JP_shikuchouson.xml parsing rules. 大字・町 is used "as is". 丁目 is parsed with the JP_chome.xml parsing rules. 地番 is parsed with the JP_banchi.xml parsing rules. 号 is parsed with the JP_go.xml parsing rules. Referenced Parsing Rules:  JP_Post.xml  JP_Postcode.xml  JP_todoufuken.xml  JP_shikuchouson.xml  JP_azachome.xml  JP_azachome_s.xml  JP_chome.xml  JP_banchi.xml  JP_go.xml

Parsing Rules JP_Post.xml The file contains parsing rules for Japanese post addresses. It does not recognize Kyoto and Sapporo addresses based on street names and addresses that use Katakana instead of numbers for blocks. The rules are referenced from the JP_Post_gcm geocoding model. Sample text recognized by the rules: 

〒150-2345 東京都渋谷区本町 2 丁目 4-7 サニーマンション 203



〒１２５―００５３東京都葛飾区鎌倉２―２３－５



東京都葛飾区鎌倉２丁目２３番地５号



葛飾区鎌倉 2-23-5

The only output entity consists of 7 elements:  Postal code  Todoufuken  Shikuchouson  Aza  Chome  Banchi  Go

JP_Postcode.xml The file contains parsing rules for Japanese postal codes. It is used by JP_Post.xml parsing rules and referenced from the JP_Post_gcm geocoding model. Sample text recognized by the rules:  〒150-2345  150―2345 A single output entity contains a single output element:


865

Additional Geocoding Information 

Postal code: three-digit number, a hyphen, and a four-digit number. The 〒 prefix is removed if present; dash between numbers is replaced with a hyphen.

JP_todoufuken.xml The file contains parsing rules for Japanese prefecture names (todoufukens 都道府県). It uses the dictionary of 47 Japanese prefecture names. The file is referenced from the JP_Post.xml parsing rules and from JP_Post_gcm geocoding model. Sample text recognized by the rules: 

山口県

The only output entity consists of a single output element:  Todoufuken (Prefecture name)

JP_shikuchouson.xml The file contains parsing rules for Japanese municipality names. These are 市 (cities), 区 (wards), or 郡 (districts), followed by the 町 (town) or 村 (village). Parsing rules use the dictionary of all municipality names present in the MLIT data and also recognizes names that end with 市, 区, 町 or 村. Sample text recognized by the rules: 

庵原郡由比町

A single output entity consists of a single output element:  Shikuchouson (Municipality name)

JP_azachome.xml The file contains parsing rules for Japanese municipality subdivision names (wards 区, machi 町 , or aza 字) along with optional city district number (chome 丁目). It is referenced from JP_Post.xml parsing rules and from JP_Post_gcm geocoding model. Sample text recognized by the rules:  

おもちゃのまち一丁目柚木町三



山田

The chome number can be written with either kanji or ASCII numbers. Kanji numbers up to 49 are recognized and standardized to their ASCII equivalents. If the input string ends with kanji digit, the digit is assigned to a chome number. The 三 in the second example string is recognized as chome number 3. All exceptions must be specified explicitly in the JP_aza_ex.csv dictionary; see its description below for a bit more details. In rare cases the chome can contain some suffix after 丁目, for example, 西 or 下. Their full list is stored in the JP_postchome.csv. The suffix is preserved in output. A single output entity consists of 2 elements:  Municipality subdivision name.  City district number (without the 丁目 suffix)

866


Additional Geocoding Information JP_azachome_s.xml The file is identical to the JP_azachome.xml. The only difference is that if the name starts with 大字, the prefix is removed on standardization. It is used by the JP_Post_gcm geocoding model to produce alternative Japanese municipality subdivision name in reference data on publishing. A single output entity consists of 2 elements: 

Municipality subdivision name (without the 大字 prefix)



City district number (without the 丁目 suffix)

JP_chome.xml The file contains parsing rules for Japanese city district number (chome 丁目). It is referenced from JP_Post_gcm geocoding model. Sample text recognized by the rules:    

一丁目 19 19 丁目六丁目南

The chome number can be 1 to 49 written with either kanji or ASCII numbers. Kanji numbers are standardized to their ASCII equivalents. A single output entity contains a single output element: 

City district number (without the 丁目 suffix)

JP_banchi.xml The file contains parsing rules for Japanese city block numbers (banchi 番地). It is referenced from JP_Post.xml parsing rules and from JP_Post_gcm geocoding model. Sample text recognized by the rules:  6  五百五十八 

ろ



２３番地

12 い番地 A single output entity contains a single output element:  City block number The 番地 suffix (if any) is removed on output. JP_number_0-999999.xml parsing rules are used to recognize numbers.

JP_go.xml The file contains parsing rules for Japanese house numbers (go 号). It is referenced from JP_Post.xml parsing rules and from JP_Post_gcm geocoding model. Sample text recognized by the rules:   

十三号 45 33 号

A single output entity contains a single output element:


867


number (always numeric) The 号 suffix (if any) is removed on output. JP_number_0-999999.xml parsing rules are used to recognize numbers.

JP_number_0-999999.xml The file contains parsing rules for Japanese numbers. It is referenced from JP_banchi.xml and JP_go.xml parsing rules. It recognizes Kanji numbers up to 999 and replaces them with their ASCII forms on output. Formal numbers are also recognized by the parsing rules. Kanji numbers 1000 and more are not recognized by the parsing rules. Sample text recognized by the rules:  7654  13  十三  

壱拾参拾参

A single output entity contains a single output element:  ASCII number

Files Referenced by the Parsing Rules JP_aza_ex.csv The file contains list of Japanese municipality subdivision names (wards 区, machi 町 or aza 字) that ends with kanji number. It is referenced from JP_azachome.xml. If on parsing with JP_azachome parsing rules the name from the dictionary is encountered, it is treated as a municipality subdivision name. All other names that ends with kanji number are split into municipality subdivision name and city district number (chome 丁目).

JP_numbers_1-49.csv The file contains numbers 1 to 49 written in Kanji (both standard and formal), with double-width numbers and their ASCII equivalents. It is referenced from JP_azachome.xml and JP_chome.xml parsing rules.

JP_numbers_1-999.csv The file contains numbers 1 to 999 written in Kanji (both standard and formal), with double-width numbers and their ASCII equivalents. It is referenced from JP_Post.xml parsing rules.

JP_postchome.csv This is a list of suffixes that can appear after the 丁目 in Japanese city district numbers. The list is derived from the MLIT data. It is referenced from JP_azachome.xml, JP_azachome_s.xml, and JP_chome.xml parsing rules.

868


Additional Geocoding Information JP_shiku.csv The file contains a list of Japanese cities (市) and wards (区), which can start the address, for example 葛飾区鎌倉 2-23-5. That is, for the addresses in these city/wards, the prefecture name can be omitted in address. It is referenced from JP_Post.xml parsing rules.

JP_shikuchouson.csv This is a list of Japanese municipality names. They are 市 (cities), 区 (wards) or 郡 (districts), followed by the 町 (town) or 村 (village). It is referenced from JP_shikuchouson.xml parsing rules.

JP_todoufuken.csv This is a list of Japanese prefecture names. It is referenced from JP_todoufuken.xml parsing rules.

Spanish Geocoding Models and Parsing Rules There are two sets of files: one with names started with SPA, and another with names started with CAT. These are sets for Spanish and Catalan addresses, respectively. They behave identically except for one fact: the Spanish geocoding model standardizes addresses so that the street type has standard Spanish form (for example, CALLE), whereas Catalan geocoding model standardizes addresses so that the street type has standard Catalan form (for example, CARRER). The difference is in the street types dictionaries (SPA_street_types.csv and CAT_street_types.csv). All other files differ only in the names of referenced files. So in the tables below, the description is given for the corresponding Spanish/Catalan pair of files except for SPA_street_types.csv and CAT_street_types.csv. The parsing rules for postal codes (SPA_Postalcode.xml) and numeric street names (SPA_numeric.xml) are used by both Spanish and Catalan sets.

Geocoding Models SPA_Post_gcm.xml, CAT_Post_gcm.xml These are centerline geocoding models for Spanish / Catalan post addresses. Reference Data address format:  Street name + left/right Postal code + left/right City (for example, CARRER DE LES AGUDES + 08033 + BARCELONA). The default source attribute names are taken from NAVTEQ data. Street name is parsed with the SPA_street / CAT_street parsing rules. City is used "as is". City name is defined separately for left and right sides of the street centerline. Postal code is parsed with SPA_Postalcode parsing rules. Postal code is defined separately for left and right sides of the street centerline. Geocoding address format(s):  Postal address (for example, CARRER D'ALMASSORA 15, 08033, BARCELONA). The format is used by the Web service for free-formed addresses. Post address is parsed with the SPA_Post / CAT_Post parsing rules. Intersections cannot be parsed.


869


Street Address, Postal code, City (for example, CARRER DE LES AGUDES, 45 + 08033 + BARCELONA). Street Address is parsed with the SPA_Streets / CAT_Post parsing rules. Postal code is parsed with the SPA_Postalcode parsing rules. City is used "as is".  House number + Street name + Crossing street + Postal code + City (for example, 15 + CARRER DE LES AGUDES + 08033 + BARCELONA, or CARRER DEL COMTE D'URGELL + MALLORCA + 08036 + BARCELONA). House number is used "as is". Street name is parsed with the SPA_street / CAT_street parsing rules. Crossing street is parsed with the SPA_street / CAT_street parsing rules. If it is present, the address is considered to be an intersection and the value of House number is ignored. Postal code is parsed with the SPA_Postalcode parsing rules. City is used "as is".  House number + Street type + Street name + Postal code + City (for example, 15 + CARRER DE LES + AGUDES + 08033 + BARCELONA). House number is used "as is". Street type is parsed with the SPA_street_type / CAT_street_type parsing rules. Street name is parsed with the SPA_street / CAT_street parsing rules. Postal code is parsed with the SPA_Postalcode parsing rules. City is used "as is".  WebService street address (Building + Street + MunicipalitySubdivision + Municipality + CountrySecondarySubdivision + CountrySubdivision + PostalCode + Country) (for example, CARRER D'ALMASSORA 15 + BARCELONA + 08033 + ES). The format is used by the Web service for street addresses. Building is ignored. Street is parsed with the SPA_Streets / CAT_Streets parsing rules. MunicipalitySubdivision is ignored. Municipality is used "as is". CountrySecondarySubdivision is ignored. CountrySubdivision is ignored. PostalCode is parsed with the SPA_Postalcode parsing rules. Country is ignored.  WebService intersection address (IntersectingStreets + MunicipalitySubdivision + Municipality + CountrySecondarySubdivision + CountrySubdivision + PostalCode + Country) (for example, CARRER DE LES AGUDES & DE COSTABONA + BARCELONA + 08033 + ES). The format is used by the Web service for intersection addresses. IntersectingStreets is parsed with the SPA_Streets_c / CAT_Streets_c parsing rules. MunicipalitySubdivision is ignored. Municipality is used "as is". CountrySecondarySubdivision is ignored. CountrySubdivision is ignored. PostalCode is parsed with the SPA_Postalcode parsing rules. Country is ignored.

870


Additional Geocoding Information Referenced Parsing Rules:  SPA_Post.xml  SPA_Streets.xml  SPA_Streets_c.xml  SPA_street.xml  SPA_street_type.xml  SPA_number.xml  SPA_Postalcode.xml

Parsing Rules SPA_Post.xml, CAT_Post.xml The files contain parsing rules for Spanish post addresses. They do not recognize intersections. SPA_Post.xml is referenced from the SPA_Post_gcm geocoding model; CAT_Post.xml is referenced from the CAT_Post_gcm geocoding model. Sample text recognized by the rules:  CALLE MALLORCA 401, 08034, BARCELONA  ATGE VILARET 11, 08013, BARCELONA, ES  PLACA PORTAL DE LA PAU 4  CARRER DEL REVEREND PERRAMON 2, 08228  C/ ROIG, 24, APPT 3 The only output entity consists of 5 elements:  House number (this is a number, house names can be recognized but they are ignored on output)  Street type (Spanish standard form for SPA_Post.xml; Catalan for CAT_Post.xml parsing rules)  Street name  Postal code  City name

SPA_Streets.xml, CAT_Streets.xml The files contain parsing rules for Spanish street addresses. SPA_Streets.xml is referenced from the SPA_Post parsing rules and from the SPA_Post_gcm geocoding model. CAT_Streets.xml is referenced from the CAT_Post parsing rules and from the CAT_Post_gcm geocoding model. Sample text recognized by the rules:  C/ CISNES, S/N ED. PLATERO, PTL. 8  C/ NICARAGUA Nº 46  CALLE SAN BERNARDO 15 - 3° -C  C/ FRANCISCO DE SILVELA, 14, 4º The only output entity consists of 3 elements:  House number (this is a number, house names can be recognized but they are ignored on output)  Street type (Spanish standard form for SPA_Streets.xml; Catalan for CAT_Streets.xml parsing rules)  Street name


871

Additional Geocoding Information SPA_Streets_c.xml, CAT_Streets_c.xml The files contain parsing rules for Spanish street and intersection addresses. They are identical to the SPA_Streets.xml / CAT_Streets.xml parsing rules but also recognizes intersections. The parsing rules are referenced from the 'WebService intersection address' address transformation of the SPA_Post_gcm / CAT_Post_gcm geocoding model. Sample text recognized by the rules:  C/ CISNES, S/N ED. PLATERO, PTL. 8  C/ NICARAGUA Nº 46  CALLE SAN BERNARDO 15 - 3° -C  C/ FRANCISCO DE SILVELA, 14, 4º  EIG DE GRÀCIA AND CARRER DE PROVENÇA The output entity consists of 3 elements:  House number (this is a number, house names can be recognized but they are ignored on output)  Street type (Spanish standard form for SPA_Streets_c.xml; Catalan for CAT_Streets_c.xml parsing rules)  Street name If an intersection is recognized, the output contains two entities (one for every crossing street), and the House number output element is empty. Intersecting streets can be divided with 'And', 'At', 'Y', '@' and '&'.

SPA_street.xml, CAT_street.xml The files contain parsing rules for Spanish street names. SPA_street.xml is referenced from SPA_Post.xml and SPA_Streets_c.xml parsing rules and from SPA_Post_gcm geocoding model. CAT_street.xml is referenced from CAT_Post.xml and CAT_Streets_c.xml parsing rules and from CAT_Post_gcm geocoding model. Sample text recognized by the rules:  BAIXADA D'EN MERI  CARRER UNO  AUTOPISTA DE BARCELONA A MANRESA A single output entity consists of 2 elements:  Street type (Spanish standard form for SPA_street.xml; Catalan for CAT_streets.xml parsing rules)  Street name The 'De', 'De La', 'La', 'D'EN', and so forth prefixes between street type and street name are assigned to the end of the street type.

SPA_street_type.xml, CAT_street_type.xml The files contain parsing rules for Spanish street types. They are referenced from the Spanish / Catalan geocoding model from the "House number + Street type + Street name + Postal code + City" address transformation to standardize the street type. Sample text recognized by the rules:  CALLE  CARRER DE LES  PLAÇA D'

872


Additional Geocoding Information A single output entity contains a single output element:  Street type The standardization replaces the street type with the standard form. The standard form is defined in the CAT_street_types.csv for CAT_street_type.xml parsing rules and in the SPA_street_types.csv for the SPA_street_type.xml parsing rules.

SPA_number.xml The file contains parsing rules for numbers. It is used to handle numeric street names ('CARRER UNO', 'CARRER NÚMERO 2'). In addition to the numeric form, it recognizes the written Spanish and Catalan numerals from 1 to 30 and replaces them with their numeric equivalents. Sample text recognized by the rules:  Uno  VINT-I-NOU  VEINTINUEVE  108 A single output entity contains a single output element: number (always numeric) The file is referenced from SPA_street.xml and CAT_street.xml parsing rules.

SPA_Postalcode.xml The file contains parsing rules for Spanish postal codes. It is used by SPA_Post.xml and CAT_Post.xml parsing rules and referenced from the SPA_Post_gcm and CAT_Post_gcm geocoding model. Sample text recognized by the rules:  08033  8033  ES-52001 A single output entity contains a single output element:  5-digit postal code. A leading zero is added if necessary and the ES prefix is removed if present.

Dictionary Files Referenced by the Parsing Rules: SPA_numeric.csv Spanish and Catalan numbers from 1 to 30 with their numeric equivalents. It is referenced from SPA_number.xml parsing rules.

SPA_street_types.csv List of Spanish street types. Every street type contains standard Spanish form, possible abbreviations, and, optionally, Catalan spelling (for example, CALLE,CARRER,C/). The file is referenced from SPA_street.xml and SPA_street_type.xml parsing rules.

CAT_street_types.csv List of Spanish street types. It contains the same values as SPA_street_types.csv but has Catalan street types as a standard form (CARRER for CALLE, PLAÇA for PLAZA, and so forth). It is referenced from CAT_street.xml and CAT_street_type.xml parsing rules.


873

Additional Geocoding Information SPA_street_names.csv, CAT_street_names.csv List of "exceptional" Spanish street names. They are:  Names that ends with digits, for example, VINT-I-SIS DE GENER 1641. The number at the end of the street name could be erroneously treated as a house number by parsing rules.  Names that require custom standardization, for example, "VIOLANT D'HONGRIA, REINA D'ARAGÓ" with standard form "VIOLANT D'HONGRIA".  Names with characters that are not accepted by parsing rules, for example, EZEQUIEL VIGUÉS "DIDO" (quotes are not allowed in ordinary street names). CAT_street_names.csv is referenced from CAT_street.xml; SPA_street_names.csv is referenced from SPA_street.xml parsing rules.

SPA_street_prefix.csv List of particles that can appear between street type and street name, for example, 'De', 'La', 'De Les', and so forth. They are appended to street type in standardized addresses. It is referenced from SPA_street.xml, SPA_street_type.xml, CAT_street.xml, and CAT_street_type.xml parsing rules.

SPA_street_prefix_apo.csv List of particles that can appear between street type and street name and which are not separated with a space from street name, for example, L'. They are appended to street type in standardized addresses. It is referenced from SPA_street.xml, SPA_street_type.xml, CAT_street.xml, and CAT_street_type.xml parsing rules.

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 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 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.

874


Additional Geocoding Information 2. To define an input address format where the crossing street is provided as an independent input address element. The following are the examples from the delivered configuration files along with technical details: Automatic disambiguation of the intersection addresses from the ordinary addresses The parsing rules must be designed so that they can recognize intersections in the input string and report them by returning two output entities to the containing address transformation. The first output entity contains values for the primary street (first set of base address element's values), and the second for the crossing street (second set of base address element's values). The street separators in the intersection addresses are defined in the parsing rules. An example of such intersection detection is found in the US_Post geocoding model (US_Post_gcm.xml). The second address transformation (Post address of intersection) refers to the AddressParsingRules\US_Post_c.xml parsing rules, which are responsible for intersection detection. There is a dedicated dictionary token that accepts only street separators. Its name is 'CAND' and it accepts '&', 'AND', 'AT', and '@'. To adjust the parsing rules for another language, you have to modify at least the contents of the dictionary (for example, with Spanish addresses, the 'AND' dictionary entry must be replaced with 'Y'). This can be done by using the Define Parsing Rules utility or by direct editing of the XML file with parsing rules (US_Post_c.xml in case of US addresses) in any text editor. Intersection addresses do not have to be ed as a single string. For example, the Intersecting streets, City, State, ZIP source address format can be geocoded this way. If Intersecting streets is parsed into two output entities, the following two records will form the intersection:  Primary street, City, State, ZIP, and  Crossing street, City, State, ZIP. That is, if parsing rules produced only one output entity in intersection address, the returned values are copied to both the street and the crossing street address element sets. However, none of the delivered geocoding models has an input format ing 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 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


875

Additional Geocoding Information can be adopted to the local language. They can certainly be adopted for Spanish addresses, but cannot be adopted, for example, for Russian.

Sounds Like Algorithms Two Sounds Like algorithms are ed: the ‗Sounds Like (English)‘ Algorithm and the ‗Sounds Like (Spanish)‘ Algorithm.

‗Sounds Like (English)‘ Algorithm The Publish Address Geocoding Index utility uses the official Soundex algorithm (as described in this appendix as sound like) slightly modified so that it can process non-English letters and other characters. The algorithm is the following: 1. Retain the first letter of the word. 2. Remove all occurrences of the A, E, H, I, O, U, W, Y letters. 3. Map the rest of letters using the following ruleset: English Letters

Soundex Code

Code Used by the Utility

B, F, P, V

1

B

C, G, J, K, Q, S, X, Z

2

C

D, T

3

D

L

4

L

M, N

5

M

R

6

R

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:  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.

876



‗Sounds Like (Spanish)‘ Algorithm The 'Sounds LIke (Spanish)' algorithm is the following: 1. Before processing, all vocal accented characters are replaced with their non-accented forms (Ñ and Ç are preserved; Ç is later replaced with S). 2. The replacement rules at the beginning of a word are ('!' means negation): Input Characters

Phonetic Code

S(!vowel)

ES(!vowel)

PS

S

PN

N

3. The replacement rules at the end of a word are: Input Characters

Phonetic Code

RG

R

CH

K

Q

K

M

N

T

(T is removed)

4. Other replacement rules: Input Characters

Phonetic Code

NY

Ñ

NT(!vowel)

N(!vowel)

GE

JE

GI

JI

GUE

GE

GUI

GI

GN

N

LL

Y

H

(H removed if not part of CH)

CZ

CH

Z,X

S

TX

CH

Ç

S

V

B

CE

SE

CI

SI


877

Additional Geocoding Information Input Characters

Phonetic Code

CA

KA

CO

KO

CU

KU

CK

K

CQ

Z

CC

S

QUE

KE

QUI

KI

QUË

QUË

Q(vowel)

K(vowel)

W(vowel)

GU(vowel)

W(!vowel)

U(!vowel)

PH

F

OU

U

(vowel)P(N or D or B or T or S) (vowel)(N or D or B or T or S) (vowel)D(B or T or S)

(vowel)(B or T or S)

(vowel)B(D or T or S)

(vowel)(D or T or S)

(vowel)M(!vowel)

(vowel)N(!vowel)

(vowel)I(vowel)

(vowel)Y(vowel)

Y(!vowel)

I(!vowel)

5. All other characters are left intact. So although the name of the coder is similar to the English version, the algorithms are quite different. The code produced by the 'Sounds Like (Spanish) phonetic coder resembles the transcription rules for Spanish words rather than Soundex code. Here are a few examples:

878

Input string

Sounds Like (Spanish)

Sounds Like (English)

MARTINEZ

MARTINES

MRDMC

SMITH

ESMIT

SMD

LLUISOS

YUISOS

LCC

PI I MARGALL

PI I MARGAY

PMRCL

PETXINA

PECHINA

PDCM

SOR EULÄLIA D'ANZIZU

SOR EULALIA DANSISU

SRLLDMCC


Additional Geocoding Information Input string

Sounds Like (Spanish)

Sounds Like (English)

VUIT DE MARÇ

BUI DE MARS

VDMRC

QUATRE CAMINS

KUATRE KAMINS

QDRCMMC


879


880


APPENDIX L

File Types GeoMedia products introduce file types that must be ed with Windows. The following file types are exposed to the 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

AGI

Intergraph GeoMedia Address Geocoding Index No action

AGP

Intergraph GeoMedia Address Geocoding Profile

Publish Address Geocoding Index utility

CSC*

Intergraph GeoMedia CAD Server Cache File

No action

CSD*

Intergraph GeoMedia CAD Schema Definition File

Define CAD Server Schema File utility

CSF

Intergraph GeoMedia Coordinate System File

Define Coordinate System File utility

Intergraph GeoMedia Feature Symbol File

Define Symbol File utility

GBP**

Intergraph GeoMedia Batch Plotting File

Batch Plotting utility

GCE*

FSM &

Open Action

Intergraph GeoMedia Catalog Exchange File

No action

&

Intergraph GeoMedia Layout Sheet

No action

&

Intergraph GeoMedia Layout Template

GLS* GLT* GSD

Intergraph GeoMedia Style Definition File

Internet Explorer

&

Intergraph GeoMedia GeoWorkspace

&

Intergraph GeoMedia GeoWorkspace Template GeoMedia Professional

GWS GWT

No action 1

GeoMedia Professional

MDT*

Intergraph GeoMedia Access Warehouse Template

No action

SSP*

Intergraph GeoMedia SmartStore Profile

Publish to GeoMedia SmartStore Warehouse utility

SYM*

Intergraph GeoMedia Layout Symbol File

No action

TFD*

Intergraph GeoMedia Text Format Definition File Define Text File Server Format File utility

&

&

TRV*

Intergraph GeoMedia Traverse File


NotePad

881

File Types

882


Index A Accessing the Layout Window • 545 Adding Entries to the Legend • 126 Adding Hypertext to a Feature Class • 257 Adding Map Objects to the Legend • 126 Adding WMS Legend Entries • 139 Additional Command Features • 539 Additional Geocoding Information • 839 Address Geocoding - Concepts and Workflows • 839 Address Geocoding - Concepts • 513 Address Geocoding Terminology • 513 ADRG • 783 Aggregating Data • 462 Aggregation versus Analytical Merge • 469 Analysis Options • 444 Analyzing GeoMedia Professional Data • 391 Analyzing Geometry • 443 Architectural Overview • 840 Aspects of a GIS • 28 ASRP / USRP • 783 Associating Catalog Records • 286 Automatically Backing Up GeoWorkspaces • 36

B Background • 821 Basic Map Layout Workflows • 565 Benefits of GIS • 32 Bitmap • 783

C CADRG / CIB • 783 CALS • 784 Canadian Geocoding Models and Parsing Rules • 858 Catalog Features • 270 Catalogs Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers • 795 Changing Attribute Values of Features • 319 Changing Display Characteristics of Map Objects • 99 Changing Feature Classes • 355 Changing Map Window Properties • 94


Changing the Coordinate System of a New Access Warehouse Template • 72 Changing the Raster Image Display • 87 Circle Element • 826 Collecting Attributes • 247 Collecting Control-Point Pairs • 306 Collecting Data • 207 Combining Feature Classes and Queries • 475 Common Attributes • 829 Components of the Map Layout • 566 Compression Techniques • 786 Configuring for Datum Transformations • 49 Configuring PickLists with Access Warehouses • 73 Connecting to a CAD Warehouse • 59 Connecting to a FRAMME Warehouse • 60 Connecting to a GeoGraphics Warehouse • 60 Connecting to a GML Warehouse • 61 Connecting to a KML Warehouse • 62 Connecting to a MapInfo Warehouse • 62 Connecting to a SmartStore Server Warehouse • 65 Connecting to a SQL Server Warehouse • 65 Connecting to a Text File Server Warehouse • 65 Connecting to a WCS Warehouse • 66 Connecting to a WFS Server Warehouse • 66 Connecting to a WMS Warehouse • 67 Connecting to an Access Warehouse • 58 Connecting to an ArcInfo Warehouse • 58 Connecting to an ArcView Warehouse • 58 Connecting to an I/CAD MAP Warehouse • 61 Connecting to an MGE or MGDM Warehouse • 63 Connecting to an MGSM Warehouse • 63 Connecting to an ODBC Tabular Warehouse • 64 Connecting to an Oracle Object Model Warehouse • 64 Connections • 739 Connectivity Conditions • 368 Constructing Circular Fillets • 385 Continue Geometry and Use Existing Geometry • 347 Continuing Geometry • 345

883

Index Controlling the Data Window • 183 Controlling the Map Window • 93 Conversion Tables • 793 Converting Layout Legend to Raster Graphics • 623 Coordinate System Information • 759 Copying Attributes • 327, 328 Copying Features • 336 Copying Features Parallel to Other Features • 337 Creating a Catalog Using Oracle • 795 Creating a Catalog Using the Microsoft MS-SQL Server • 800 Creating a GeoWorkspace • 33 Creating a GeoWorkspace Template • 37 Creating a New Catalog • 274 Creating a New Catalog Connection • 276 Creating a New GeoMedia Warehouse in Oracle • 737 Creating a New Library • 685 Creating a New Library Connection • 687 Creating a Read-Write Access Warehouse • 56 Creating Additional Map Windows • 150 Creating an Access Warehouse Template • 71 Creating and Managing Named Styles • 104 Creating and Managing Predefined Searches • 435 Creating Coordinate-System Files from Design Files • 53 Creating Features with More than One Geometry Type • 245 Creating Image Footprints • 89 Creating Spatial Indexes • 712 Creating Symbols in Layout Windows to Use in Map Windows • 120 Creating the GDOSYS Schema • 714 Customizing the Legend • 143 Customizing the Legend Toolbar • 147 Customizing the Menus and Toolbars • 22

D D Attribute • 828 Data Storage and Type Matching • 702, 741 Data Type Matching – GeoMedia to Oracle • 709 Data Type Matching - Oracle to GeoMedia • 708 Database Utilities • 735, 757 Data-Capture Workflows • 24 Datum Transformation Models • 760 Default Values • 731, 756

884

Define Coordinate System File • 83 Defining a Border • 635 Defining a Coordinate System for a Feature Class • 44 Defining a Coordinate System for a GeoWorkspace • 42 Defining a Coordinate System for a Warehouse • 57 Defining a Neatline • 628 Defining a Traverse • 536 Defining Attribute-Filter Queries • 392 Defining Geocoding Models • 527 Defining Grids • 631 Defining s • 441 Defining Linear Network Queries • 410 Defining Map Specifications in the Map Window • 561 Defining Map Window Display Properties • 96 Defining Map Window ToolTips • 149 Defining Marginalia Specifications in the Map Window • 564 Defining Native Queries against an MGSM Warehouse • 408 Defining Native Queries against an Oracle Warehouse • 405 Defining Parsing Rules • 528 Defining Queries from Select Sets • 206 Defining Spatial Differences • 403 Defining Spatial Filters • 415 Defining Spatial Intersections • 400 Defining Spatial Queries • 397 Defining the Data Window Page Setup • 649 Defining the Layout Window Page Setup • 651 Defining the Map Window Page Setup • 645 Defining Ticks and Crosses • 633 Delaying Data Loading • 35 Deleting Feature Geometry • 354 Deleting Features • 339 Deleting Geometry Using Edit Geometry • 344 Deleting Layout Sheets • 554 Deleting Map Objects through the Legend • 150 Deleting Queries • 414 Delivery and Connection • 699, 739 Designating Spatial Filter Reference Features • 423 Deg Map Layouts for Printing in the Layout Window • 561 Deg Map Layouts Overview • 561 Digitizer Button Mapping • 309


Index Digitizing Discontiguous Features and Features with Holes • 244 Discussion • 821 Displaying Bing Maps • 168 Displaying CAD Files • 174 Displaying Data That Has No Coordinate System Specified • 50 Displaying External Maps • 166 Displaying Geometry Information • 358 Displaying Named Locations • 163 Displaying or Hiding the Legend • 125 Displaying Pictometry Maps • 169 Displaying Queries • 412 Displaying Selected Images • 91 Displaying the North Arrow • 150 Displaying the Scale Bar • 152 Docking the Legend • 123 Documentation for GeoMedia Professional • 18 Domain Authentication • 700

Exporting to MapInfo Interchange Format • 664 Exporting to Oracle Object Model • 674 Exporting to Shapefile • 661 Exporting to SQL Server • 676 Extending Geometry • 376 Extending Geometry to Intersections • 377 Extending Two Lines to an Intersection • 378

E

G Element • 824 General Data-Capture and Maintenance Workflow • 24 General Elements • 822 General Viewing and Analysis Workflow • 23 Generating Base Geometry • 470 Geocoding • 511 Geocoding Addresses with Multiple Datasets • 526 Geocoding and Finding Addresses • 511 Geocoding Coordinates • 532 Geocoding Models and Parsing Rules • 851 Geocoding Multiple Addresses • 522 GeoMedia Layout Sheets • 548 GeoMedia Layout Templates • 549 GeoMedia Metadata Requirements • 743 GeoMedia to SQL Server Data Type Matching • 742 GeoMedia‘s GDOSYS Metadata Schema • 714 Geometry Elements • 825 Geometry Storage • 702, 741 Geometry Type Mapping • 703 Geometry Validation Error Conditions • 363 Getting Around in the Software • 21 Getting Coordinate Readouts • 47 Getting Started • 21, 513 Getting WMS Feature Information • 177 GIS Applications • 32 GIS Concepts & Terminology • 29 Glossary of Catalog Terminology • 303

ECW • 784 Editing Attribute Selection Queries through the Queries Command • 474 Editing Cells in the Data Window • 186 Editing Coincident Geometry • 343 Editing Features and Geometries • 319 Editing Geometry with a Snap-and-Break Workflow • 344 Editing in a Map Window • 319 Editing Queries • 413 Editing Text • 252 Editing Union Queries through the Queries Command • 479 Element Descriptions • 835 Ellipse Element • 827 Ellipsoids • 772 E-Mailing a GeoWorkspace • 37 Enabling AFM Proxy Servers for GeoMedia PublicWorks Manager • 68 Error Reporting • 675 ESRI • 784 Event Data Structures • 816 Example • 836 Exploring Catalogs • 291 Exporting Catalog Records • 282 Exporting Data to Other Systems • 661 Exporting Layout Sheets and Templates • 551 Exporting to AutoCAD • 678 Exporting to Design File • 666 Exporting to GML • 680


F Feature Class Definition • 755 File Types • 881 File Types and Categories Listed for Inserting a Georeferenced Image • 788 Finding an Address • 516 Fixing Connectivity • 373 Fixing Geometry • 366 Functional Overview • 515, 839

G

885

Index

H Header Information • 834

I Images and Coordinate Systems • 82 Imagineer or SmartSketch Template and Drawing Files • 549 Importing Catalog Records • 279 Importing Data • 539, 755 Importing Layout Sheets and Layout Templates • 548 Insert Traverse Workflows • 540 Inserting a Data Table • 642 Inserting a Reference Grid • 638 Inserting a Reference Index • 639 Inserting Area Features Automatically • 248 Inserting Cartographic Grids • 627 Inserting Features in a Data Window • 259 Inserting Features in a Map Window • 219 Inserting Graphics into Layout Frames • 598 Inserting Images into Warehouses • 77 Inserting Interactive Labels • 503 Inserting Intersections • 382 Inserting Labels • 497 Inserting Layout Frames • 596 Inserting Layout Sheets • 548 Inserting Leader Lines • 500 Inserting Maps into Layout Sheets • 601 Inserting Marginalia into Layout Sheets • 603 Inserting Reference Grids and Indexes • 638 Inserting Text Features into a Feature Class • 250 Inserting Traverses • 535 Interactive Documents • 19 Intergraph • 784 International System of Units to United States Customary System • 793 Intersection Geocoding • 874

J Japanese Geocoding Models and Parsing Rules • 864 JFIF • 784 JPEG 2000 • 785

L Layout Graphics Components • 570 Layout Window Graphics Commands • 789 Layout Window Overview • 545 Line Element • 825 Linear Referencing • 481

886

Linear Referencing and Geospatial Technology • 482 Linear Referencing Commands • 484 Linking and Embedding a GeoWorkspace • 38 Linking Geometry Data to Coordinate Systems • 83 Looking at GeoMedia Address Geocoding An Overview • 511 Looking at GeoMedia Professional An Overview • 17 Looking at Legend Style Keys • 124 Looking at Style Classes • 115 Looking at Style Collections • 102 Looking at the Catalog Explorer Interface • 292 Looking at the Queued Edit Interface • 427 Looking at the Two Legend Tabs • 122 LRS Data Structures • 807 LRS Linear Features and Event Data • 483 LRS Terminology • 482

M Managing Catalog Connections • 277 Managing Categories • 260 Managing Library Connections • 689 Managing Named Locations • 165 Managing Spatial Filters • 419 Managing Warehouse Images • 83 Manipulating Features • 330 Manipulating Geometry • 339 Manipulating Layer Groups • 558 Manipulating Layers • 556 Manipulating Queries • 411 Map Graphics Components • 566 Map Window Considerations When Printing from the Layout Window • 561 Matching GeoWorkspace and Default Warehouse Coordinate Systems • 46 Measuring Angles • 157 Measuring Distances • 155 Merging Feature Classes and Queries • 458 Merging Features • 330 Metadata Element • 824 MicroStation Design Files • 83 MicroStation Layout Templates • 550 Modifying Legends • 622 Modifying Map Graphics in Layout Sheets • 614 Modifying Map Properties • 619 Modifying Map Window Legend Properties • 623


Index Modifying Maps • 614 Modifying North Arrows • 624 Modifying Scale Bars • 625 Moving a Vertex by Precision Keyin • 342 Moving Geometry • 348 Moving Labels • 503 MrSID • 785

N Named Geodetic Datums • 771 Naming Locations • 163 Native Geometry Metadata • 710 Native Queries • 713 NITF • 785

O Object Model Data Server Requirements • 701 Obtaining Symbols for Feature Class Displays • 114 Opening a GeoWorkspace • 34 Opening a New Data Window • 182 Option 1 - Measure • 808, 816 Option 2 - Marker Offset • 817 Option 2 - Measure with Internal Measure Markers • 809 Option 3 - Coordinates • 818 Option 3 - Measure with External Markers • 810 Option 4 - Duration • 812, 819 Option 5 - Duration with Internal Markers • 813 Option 6 - Duration with External Measure Markers • 814 Oracle Coordinate Systems - SRID • 711 Oracle GeoRasters • 785 Organizing Libraries • 691 Oriented Points • 705 Outputting Feature Data to Warehouses • 196 Outputting PDF from GeoMedia Professional • 658 Outputting to GeoTIFF • 313 Overview • 529, 807

P Page Setup • 547 Partially Deleting Linear Features • 354 Persistence • 700, 739 Path Element • 828 Performing Digitizer Setup • 305


Performing Searches • 437 Permissions • 740 Placement Modes • 222 Placing along Arc • 256 Placing along Existing Geometry • 256 Placing at Point • 255 Placing Buffer Zones around Features • 447 Placing Map Graphics in Layout Sheets Using Layout Frames • 565 Placing Map Graphics in Layout Sheets Without Using Layout Frames • 565 Plotting • 547, 657 PNG • 786 Polyline and Polygon Elements • 825 Possible Extend Cases • 377 Possible Intersection Cases • 383 Possible Trim to Intersection Cases • 381 Preparing to Connect • 57 Prerequisites • 699, 739 Primary Workflow • 540 Printing a Data Window • 650 Printing a Map Window • 647 Printing in GeoMedia Professional • 645 Printing Layout Sheets from the Layout Window • 653 Printing Overview • 645 Printing to a File • 648 Printing Transparent or Translucent Graphics • 657 Projection Algorithms • 759 Publishing Map Window Data • 176

Q Querying Graphics-Only Features in MGE and MGSM • 425 Quick Steps • 795, 801

R Raster Formats ed in GeoMedia • 783 Raster Images • 707 Raster Information • 783 Read-Only Connections • 699 Read-Write Connections • 700 Rect Element • 826 Redigitizing Feature Geometry • 351 Redigitizing Text • 255 ing Data • 305 ing Images • 311 ing Vector Data • 314 Removing Images from a View and Redisplaying Them • 86

887

Index Renaming Layout Sheets • 554 Resizing the Legend • 123 Resolving Text Conflicts • 506 Reversing Direction • 386 Rotating Geometry • 350

S Sample Catalog Explorer Workflows • 302 Saving, Closing, and Copying a GeoWorkspace • 36 Secondary Workflow • 540 Selecting and Manipulating Layout Sheets • 554 Selecting and Searching for Text • 254 Selecting Attributes • 473 Selecting Data • 538 Selecting Features in the Map Window • 203 Server Database Upgrades • 799 Setting Acrobat Distiller Parameters • 658 Setting Connection Status • 69 Setting Defaults for Feature Class Legend Entries • 142 Setting Digitizer Mode • 309 Setting Layout Window Options • 545 Setting Units and Formats • 48 Simplifying Geometry • 387 Single-Level LRS Data Structures • 807 Smoothing Geometry • 388 Software Delivery • 304 Sounds Like Algorithms • 876 Spanish Geocoding Models and Parsing Rules • 869 Spatial Filtering • 712, 756 Spinning Geometry • 348 Splitting Features • 331 SQL Dialects • 393 SQL Server to GeoMedia Data Type Matching • 742 SQL Server Warehouse Requirements • 740 Standard Geodetic Datums • 767 Start Here • 17 Starting the Layout Window • 547 State Plane Zone Codes—NAD27 and Old Island Datums • 776 State Plane Zone Codes—NAD83 Datum • 778 Step Five Create an ODBC connection for GeoMedia Catalog s. • 804 Step Four Create a New Catalog Connection • 798 Set permissions. • 802 Step One

888

Create a SQL database. • 801 Create an Oracle Catalog database. • 795 Step Six Create a New Catalog Connection • 805 Step Three Create ODBC DSN for the client. • 797 Create s. • 802 Step Two Run the MS-SQL Catalog scripts. • 801 Set up a service name for the client. • 796 Stream Digitizing Mode • 243 Style Attribute • 829 ed Digitizers • 305 ed SVG Element Types • 821 ed Types • 822 SVG Symbol Metadata XML Schema • 833 Symbol Element • 822

T Tables • 731 Taking a Snapshot of the Data Window • 187 Taking a Snapshot of the Map Window • 159 Technical and Information • 697 Text and Labels • 706 Text Element • 829 The Default GDOSYS Schema Definition • 715 The Product Workflows • 23 TIFF (and GeoTIFF) • 786 Tiling • 787 Tools for Collection of Attribute Information • 247 Tools for Speeding Up the Digitizing Workflow • 208 Transform Attribute • 832 Triggers • 733 Trimming Geometry • 379 Trimming Geometry to Intersections • 381 Types of Information • 28 Typing Data • 536

U Understanding Geometry Types • 189 Undo/Redo • 756 Undoing and Redoing Placement and Editing • 218 United States Customary System to International System of Units • 794 Units of Measure (UOM) • 774 Unloading Queries • 414 Updating Feature Attributes • 322 Updating Feature Attributes Using Text • 325


Index Updating Map Graphics in Layout Sheets • 613 Updating Metadata Databases for GeoMedia 6.0 or Higher • 274 US Geocoding Models and Parsing Rules • 852 Use Element • 823 s and Privileges • 729 USGS DOQ • 786 Using Additional Commands • 432 Using an Existing Oracle Spatial Schema • 736 Using Construction Aids • 228 Using Database Objects • 729 Using Editing Tools with Data Validation Tools • 357 Using Map Viewing Tools • 98 Using Oracle Connections • 699 Using Precision Keyins • 245 Using Queuing Options • 431 Using SQL Server Connections • 739 Using the Customize Command • 22 Using the Data View Tools • 184 Using the Find Address Command • 519 Using the Geocode Addresses Command • 524 Using the Legend Right Mouse Menu • 147 Using the Mouse in a Data Window • 183 Using the Mouse in a Map Window • 98 Using the Right Mouse Menu • 240, 460 Using the Save/Load Customized Settings Commands • 23 Utilizing Spatial Indexing • 712 UTM Zones • 780

V Validating and Fixing Data • 357 Validating Connectivity • 367 Validating Geometry • 363 Versions and Variations • 822 Vertical Datums • 771 Viewing and Editing Connection Properties • 70 Viewing Background and Working Sheets • 555 Viewing Changes in a Multi- Environment • 71 Viewing Layout Window Properties • 555 Views and Views • 757 Views and -Views • 732


W What Are FGDC Metadata Standards? • 272 What Are ISO Metadata Standards? • 273 What Can I Do with a GIS? • 28 What is a GIS? • 28 What Is Geospatial Metadata? • 271 What is Linear Referencing? • 481 What You Need to Know to Work • 18 What's New • 20 Why Have Metadata? • 271 Workflow for Dashed and Patterned Area Boundaries • 471 Workflow for Dashed and Patterned Linear Features • 462 Workflows for Placing Map Graphics Using Layout Frames • 596 Workflows for Placing Map Graphics without Using Layout Frames • 601 Workflows for Using Bing Maps and Pictometry Maps • 172 Working with Catalogs • 269 Working with Categories • 260 Working with Connections • 68 Working with Coordinate Systems • 39 Working with Data Windows • 181 Working with Feature Classes • 190 Working with Features • 189 Working with Filter Queries • 391 Working with Functional Attributes • 449 Working with GeoWorkspaces • 33 Working with Images • 77 Working with s • 441 Working with Labels • 497 Working with Layout Windows • 545 Working with Legends • 121 Working with Libraries • 685 Working with Map Locations • 162 Working with Map Windows • 93 Working with Native Queries • 405 Working with Queued Edit • 425 Working with Searches • 434 Working with Spatial Filters • 414 Working with SQL Server • 755 Working with Styles • 102 Working with the Dynamic Segmentation Command • 489 Working with the LRS Precision Location Command • 485 Working with the Overview Window • 159 Working with Warehouses • 55

889

Index

X XML Source • 836

890


Additional information on Intergraph and Services is available on the Internet. Use a Web browser to connect to Intergraph Online (http://www.intergraph.com). For general Intergraph information, call 1-800-791-3357 (U.S. and Canada) or 001-256-730-2000 (international).

Geo Media Professional Guide 3g4q3b

Overview 3e4r5l

More details w3441

Related Documents 3m3m1z

Geo Media Professional Guide 3g4q3b

Installing Geo Media Professional 1f4gx

Asset Geo Reference Guide 6j325j

Geo 5 Guide En 1l5321

Cisco Configuration Professional Guide 6j6070

Micropay Professional Pye Guide 2a5b5k

More Documents from "nori" 4z1437

Geo Media Professional Guide 3g4q3b

Tmo Sm-t377t Tab-e Sp 5y512r

Discapacidad Visual b5i2c

Ifu_647g403_3r80-final.pdf 4g5o4j

6l6m1j

4. Casumpang V. Cortejo 6c4o5y