Professional Documents
Culture Documents
User's Guide
Copyright Copyright 1998-2011 Intergraph Corporation. All Rights Reserved. Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license agreement; contains confidential and proprietary information of Intergraph and/or third parties which is protected by copyright law, trade secret law, and international treaty, and may not be provided or otherwise made available without proper authorization from Intergraph Corporation. Copyright for the Canadian National Transformation Version 2 Software: 1995. Her Majesty the Queen in Right of Canada, represented by the Minister of Natural Resources. Produced under license from Her Majesty the Queen in Right of Canada, represented by the Minister of Natural Resources. Software based on the National Transformation Version 2 developed by Geodetic Survey Division, Geomatics Canada. Copyright for Dynamap/2000 2002-2005 Tele Atlas North America, Inc. This product contains proprietary and confidential property of Tele Atlas North America, Inc. Unauthorized use, including copying for other than testing and standard backup procedures, of this product is expressly prohibited. Code for doing JPEG software compression and decompression is based in part on the work of the Independent JPEG Group, Copyright 1991-1998, Thomas G. Lane. Code for handling GeoTIFF files is based in part on LibTIFF and LibGeoTIFF, Copyright 1988-1997 Sam Leffler Copyright 1991-1997 Silicon Graphics, Inc. Copyright 1995 Niles D. Ritter Code for handling "Deflate" compression in GeoTIFF files is based on zlib, Copyright 1995-1996 Jean-loup Gailly and Mark Adler MrSID, MrSID Decompressor, and the MrSID logo are trademarks of LizardTech, Inc. used with permission. Portions of this computer program are copyright 1995-1998 LizardTech. All rights reserved. MrSID is protected by U.S. Patent No. 5,710,835. Foreign Patents Pending. Unauthorized use or duplication prohibited. Code for doing JPEG 2000 compression and decompression is based on Kakadu software, Copyright 2001-2008, David Taubman, UNSW Code for ECW decompression Copyright 1988-2002 Earth Resource Mapping Ltd Portions copyright Microsoft Corporation. All rights reserved. Portions copyright Blue Sky Software Corporation. All rights reserved. This product uses libpng version 1.2.12 - June 27, 2006 Copyright (c) 1998-2002 Glenn Randers-Pehrson Copyright (c) 1996-1997 Andreas Dilger Copyright (c) 1995-1996 Guy Eric Schalnat, Group 42, Inc. No warranty is expressed or implied by the holders of these copyrights. Please contact Intergraph with any problems with our implementation of this third party code. The copyright holders are not responsible for problems in our implementation. U.S. Government Restricted Rights Legend Use, duplication, or disclosure by the government is subject to restrictions as set forth below. For civilian agencies: This was developed at private expense and is "restricted computer software" submitted with restricted rights in accordance with subparagraphs (a) through (d) of the Commercial Computer Software - Restricted Rights clause at 52.227-19 of the Federal Acquisition Regulations ("FAR") and its successors, and is unpublished and all rights are reserved under the copyright laws of the United States. For units of the Department of Defense ("DoD"): This is "commercial computer software" as defined at DFARS 252.227-7014 and the rights of the Government are as specified at DFARS 227.7202-3. Unpublished - rights reserved under the copyright laws of the United States. Intergraph Corporation P.O. Box 240000 Huntsville, AL 35813 Terms of Use Use of this software product is subject to the End User License Agreement ("EULA") delivered with this software product unless the licensee has a valid signed license for this software product with Intergraph Corporation. If the licensee has a valid signed license for this software product with Intergraph Corporation, the valid signed license shall take precedence and govern the use of this software product. Subject to the terms contained within the applicable license agreement, Intergraph Corporation gives licensee permission to print a reasonable number of copies of the documentation as defined in the applicable license agreement and delivered with the software product for licensee's internal, non-commercial use. The documentation may not be printed for resale or redistribution. Warranties and Liabilities All warranties given by Intergraph Corporation about equipment or software are set forth in the EULA provided with the software or applicable license for the software product signed by Intergraph Corporation, and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or amendment of such warranties. Intergraph believes the information in this publication is accurate as of its publication date. The information and the software discussed in this document are subject to change without notice and are subject to applicable technical product descriptions. Intergraph Corporation is not responsible for any error that may appear in this document. The software discussed in this document is furnished under a license and may be used or copied only in accordance with the terms of this license. No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied by Intergraph or its affiliated companies. THE USER OF THE SOFTWARE IS EXPECTED TO MAKE THE FINAL EVALUATION AS TO THE USEFULNESS OF THE SOFTWARE IN HIS OWN ENVIRONMENT. Intergraph is not responsible for the accuracy of delivered data including, but not limited to, catalog, reference and symbol data. Users should verify for themselves that the data is accurate and suitable for their project work. Trademarks Intergraph, the Intergraph logo, and GeoMedia are registered trademarks of Intergraph Corporation. Microsoft and Windows are registered trademarks of Microsoft Corporation. Bing is a trademark of Microsoft Corporation. Google Maps is a trademark of Google Incorporated. Pictometry Intelligent Images is a registered trademark of Pictometry International Corporation. Other brands and product names are trademarks of their respective owners.
Contents
Start Here.................................................................................................................................................... 17 Looking at GeoMedia Professional: An Overview .............................................................................. 17 What You Need to Know to Work ......................................................................................................... 18 Documentation for GeoMedia Professional .......................................................................................... 18 Developer Documentation .............................................................................................................. 18 User Documentation ....................................................................................................................... 19 Utilities Documentation ................................................................................................................... 19 Interactive Documents .................................................................................................................... 19 What's New..................................................................................................................................... 20 Getting Started ...................................................................................................................................... 21 Getting Around in the Software ............................................................................................................. 21 Customizing the Menus and Toolbars .................................................................................................. 22 Using the Customize Command ..................................................................................................... 22 Using the Save/Load Customized Settings Commands ................................................................ 23 The Product Workflows ......................................................................................................................... 23 General Viewing and Analysis Workflow ........................................................................................ 23 General Data-Capture and Maintenance Workflow ....................................................................... 24 Data-Capture Workflows ................................................................................................................ 24 What is a GIS? ...................................................................................................................................... 28 What Can I Do with a GIS? ............................................................................................................ 28 Aspects of a GIS ............................................................................................................................. 28 Types of Information ....................................................................................................................... 28 GIS Concepts & Terminology ......................................................................................................... 29 GIS Applications ............................................................................................................................. 32 Benefits of GIS ............................................................................................................................... 32 Working with GeoWorkspaces ................................................................................................................. 33 Creating a GeoWorkspace .................................................................................................................... 33 Opening a GeoWorkspace .................................................................................................................... 34 Delaying Data Loading .......................................................................................................................... 35 Automatically Backing Up GeoWorkspaces ......................................................................................... 36 Saving, Closing, and Copying a GeoWorkspace .................................................................................. 36 E-Mailing a GeoWorkspace .................................................................................................................. 37 Creating a GeoWorkspace Template.................................................................................................... 37 Linking and Embedding a GeoWorkspace ........................................................................................... 38 Working with Coordinate Systems .......................................................................................................... 39 Defining a Coordinate System for a GeoWorkspace ............................................................................ 42 Defining a Coordinate System for a Feature Class .............................................................................. 44 Matching GeoWorkspace and Default Warehouse Coordinate Systems ............................................. 46 Getting Coordinate Readouts ............................................................................................................... 47 Setting Units and Formats .................................................................................................................... 48 Configuring for Datum Transformations ................................................................................................ 49 Displaying Data That Has No Coordinate System Specified ................................................................ 50 Creating Coordinate-System Files from Design Files ........................................................................... 53
Contents
Working with Warehouses........................................................................................................................ 55 Creating a Read-Write Access Warehouse .......................................................................................... 56 Defining a Coordinate System for a Warehouse .................................................................................. 57 Preparing to Connect ............................................................................................................................ 57 Connecting to an Access Warehouse ............................................................................................ 58 Connecting to an ArcInfo Warehouse ............................................................................................ 58 Connecting to an ArcView Warehouse........................................................................................... 58 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 an I/CAD MAP Warehouse ..................................................................................... 61 Connecting to a KML Warehouse .................................................................................................. 62 Connecting to a MapInfo Warehouse ............................................................................................. 62 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 Connecting to a SQL Server Warehouse ....................................................................................... 65 Connecting to a SmartStore 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 Working with Connections .................................................................................................................... 68 Enabling AFM Proxy Servers for GeoMedia PublicWorks Manager .............................................. 68 Setting Connection Status .............................................................................................................. 69 Viewing and Editing Connection Properties ................................................................................... 70 Viewing Changes in a Multi-User Environment .................................................................................... 71 Creating an Access Warehouse Template ........................................................................................... 71 Changing the Coordinate System of a New Access Warehouse Template ......................................... 72 Configuring PickLists with Access Warehouses ................................................................................... 73 Working with Images................................................................................................................................. 77 Inserting Images into Warehouses ....................................................................................................... 77 Using ERDAS IMG Files with Insert Georeferenced Images ......................................................... 79 Before Inserting Images ................................................................................................................. 79 Workflows for Inserting Interactive and Georeferenced Images .................................................... 79 Images and Coordinate Systems ................................................................................................... 82 Managing Warehouse Images .............................................................................................................. 83 Removing Images from a View and Redisplaying Them ............................................................... 86 Changing the Raster Image Display ..................................................................................................... 87 Creating Image Footprints .................................................................................................................... 89 Displaying Selected Images .................................................................................................................. 91 Working with Map Windows ..................................................................................................................... 93 Controlling the Map Window ................................................................................................................. 93 Changing Map Window Properties ................................................................................................. 94 Defining Map Window Display Properties ...................................................................................... 96 Using the Mouse in a Map Window ................................................................................................ 98 Using Map Viewing Tools ............................................................................................................... 98 Changing Display Characteristics of Map Objects ......................................................................... 99
Contents
Working with Styles ............................................................................................................................. 102 Looking at Style Collections ......................................................................................................... 102 Creating and Managing Named Styles ......................................................................................... 104 Obtaining Symbols for Feature Class Displays ............................................................................ 114 Looking at Style Classes .............................................................................................................. 115 Creating Symbols in Layout Windows to Use in Map Windows ................................................... 120 Working with Legends ......................................................................................................................... 121 Looking at the Two Legend Tabs ................................................................................................. 122 Docking the Legend ...................................................................................................................... 123 Resizing the Legend ..................................................................................................................... 123 Looking at Legend Style Keys ...................................................................................................... 124 Displaying or Hiding the Legend .................................................................................................. 125 Adding Map Objects to the Legend .............................................................................................. 126 Setting Defaults for Feature Class Legend Entries ...................................................................... 142 Customizing the Legend ............................................................................................................... 143 Customizing the Legend Toolbar ................................................................................................. 147 Using the Legend Right Mouse Menu .......................................................................................... 147 Defining Map Window ToolTips .................................................................................................... 149 Deleting Map Objects through the Legend ................................................................................... 150 Creating Additional Map Windows ...................................................................................................... 150 Displaying the North Arrow ........................................................................................................... 150 Displaying the Scale Bar .............................................................................................................. 152 Measuring Distances .................................................................................................................... 155 Measuring Angles ......................................................................................................................... 157 Taking a Snapshot of the Map Window........................................................................................ 159 Working with the Overview Window.................................................................................................... 159 Working with Map Locations ............................................................................................................... 162 Naming Locations ......................................................................................................................... 163 Displaying Named Locations ........................................................................................................ 163 Managing Named Locations ......................................................................................................... 165 Displaying External Maps ................................................................................................................... 166 Displaying Bing Maps ................................................................................................................... 168 Before Using the Command ......................................................................................................... 168 Using the Command ..................................................................................................................... 169 Displaying Pictometry Maps ......................................................................................................... 169 Before Using this Command ........................................................................................................ 169 Using the Command ..................................................................................................................... 170 Workflows for Using Bing Maps and Pictometry Maps ................................................................ 172 Displaying CAD Files .......................................................................................................................... 174 Publishing Map Window Data ............................................................................................................. 176 Configuring KML Publishing ......................................................................................................... 176 Publishing Map Window Data ...................................................................................................... 176 Getting WMS Feature Information ...................................................................................................... 177 Working with Data Windows .................................................................................................................. 181 Opening a New Data Window ............................................................................................................. 182 Controlling the Data Window .............................................................................................................. 183 Using the Mouse in a Data Window ............................................................................................. 183 Using the Data View Tools ........................................................................................................... 184 Editing Cells in the Data Window ................................................................................................. 186 Taking a Snapshot of the Data Window ............................................................................................. 187
Contents
Working with Features ............................................................................................................................ 189 Understanding Geometry Types ......................................................................................................... 189 Working with Feature Classes ............................................................................................................ 190 Outputting Feature Data to Warehouses ............................................................................................ 196 Selecting Features in the Map Window .............................................................................................. 203 Defining Queries from Select Sets ............................................................................................... 206 Collecting Data .................................................................................................................................... 207 Tools for Speeding Up the Digitizing Workflow ............................................................................ 208 Undoing and Redoing Placement and Editing ............................................................................. 218 Inserting Features in a Map Window .................................................................................................. 219 Placement Modes ......................................................................................................................... 222 Using Construction Aids ............................................................................................................... 228 Using the Right Mouse Menu ....................................................................................................... 240 Stream Digitizing Mode ................................................................................................................ 243 Digitizing Discontiguous Features and Features with Holes ........................................................ 244 Creating Features with More than One Geometry Type .............................................................. 245 Using Precision Keyins ................................................................................................................. 245 Tools for Collection of Attribute Information ........................................................................................ 247 Collecting Attributes ...................................................................................................................... 247 Inserting Area Features Automatically ................................................................................................ 248 Inserting Text Features into a Feature Class ...................................................................................... 250 Editing Text ......................................................................................................................................... 252 Selecting and Searching for Text ........................................................................................................ 254 Redigitizing Text.................................................................................................................................. 255 Placing at Point ............................................................................................................................. 255 Placing along Arc .......................................................................................................................... 256 Placing along Existing Geometry ................................................................................................. 256 Adding Hypertext to a Feature Class .................................................................................................. 257 Inserting Features in a Data Window .................................................................................................. 259 Working with Categories ..................................................................................................................... 260 Managing Categories ................................................................................................................... 260 Working with Catalogs ............................................................................................................................ 269 Catalog Features................................................................................................................................. 270 What Is Geospatial Metadata?............................................................................................................ 271 Why Have Metadata? ................................................................................................................... 271 What Are FGDC Metadata Standards? ........................................................................................ 272 What Are ISO Metadata Standards? ............................................................................................ 273 Updating Metadata Databases for GeoMedia 6.0 or Higher .............................................................. 274 Creating a New Catalog ...................................................................................................................... 274 Creating a New Catalog Connection................................................................................................... 276 Managing Catalog Connections .......................................................................................................... 277 Importing Catalog Records ................................................................................................................. 279 Exporting Catalog Records ................................................................................................................. 282 Associating Catalog Records .............................................................................................................. 286 Exploring Catalogs .............................................................................................................................. 291 Looking at the Catalog Explorer Interface .................................................................................... 292 Sample Catalog Explorer Workflows .................................................................................................. 302 Glossary of Catalog Terminology........................................................................................................ 303 Software Delivery ................................................................................................................................ 304
Contents
Registering Data ...................................................................................................................................... 305 Performing Digitizer Setup .................................................................................................................. 305 Supported Digitizers ..................................................................................................................... 305 Collecting Control-Point Pairs ...................................................................................................... 306 Setting Digitizer Mode ......................................................................................................................... 309 Digitizer Button Mapping .............................................................................................................. 309 Registering Images ............................................................................................................................. 311 Outputting to GeoTIFF ........................................................................................................................ 313 Registering Vector Data ...................................................................................................................... 314 Editing Features and Geometries .......................................................................................................... 319 Editing in a Map Window .................................................................................................................... 319 Changing Attribute Values of Features ............................................................................................... 319 Updating Feature Attributes ................................................................................................................ 322 Updating Feature Attributes Using Text .............................................................................................. 325 Copying Attributes ............................................................................................................................... 327 Copying Attributes ........................................................................................................................ 328 Manipulating Features ........................................................................................................................ 330 Merging Features ......................................................................................................................... 330 Splitting Features .......................................................................................................................... 331 Copying Features ......................................................................................................................... 336 Copying Features Parallel to Other Features ............................................................................... 337 Deleting Features ......................................................................................................................... 339 Manipulating Geometry ....................................................................................................................... 339 Moving a Vertex by Precision Keyin ............................................................................................. 342 Editing Coincident Geometry ........................................................................................................ 343 Editing Geometry with a Snap-and-Break Workflow .................................................................... 344 Deleting Geometry Using Edit Geometry ..................................................................................... 344 Continuing Geometry.................................................................................................................... 345 Continue Geometry and Use Existing Geometry ......................................................................... 347 Moving Geometry ......................................................................................................................... 348 Spinning Geometry ....................................................................................................................... 348 Rotating Geometry ....................................................................................................................... 350 Redigitizing Feature Geometry ..................................................................................................... 351 Deleting Feature Geometry .......................................................................................................... 354 Partially Deleting Linear Features ................................................................................................ 354 Changing Feature Classes ................................................................................................................. 355 Validating and Fixing Data...................................................................................................................... 357 Using Editing Tools with Data Validation Tools .................................................................................. 357 Displaying Geometry Information........................................................................................................ 358 Validating Geometry ........................................................................................................................... 363 Geometry Validation Error Conditions .......................................................................................... 363 Fixing Geometry .................................................................................................................................. 366 Validating Connectivity ........................................................................................................................ 367 Connectivity Conditions ................................................................................................................ 368 Fixing Connectivity .............................................................................................................................. 373 Order of Processing...................................................................................................................... 375 Infinite Loops ................................................................................................................................ 375 Extending Geometry ........................................................................................................................... 376 Extending Geometry to Intersections .................................................................................................. 377 Possible Extend Cases................................................................................................................. 377
Contents
Extending Two Lines to an Intersection .............................................................................................. 378 Trimming Geometry ............................................................................................................................ 379 Trimming Geometry to Intersections ................................................................................................... 381 Possible Trim to Intersection Cases ............................................................................................. 381 Inserting Intersections ......................................................................................................................... 382 Possible Intersection Cases ......................................................................................................... 383 Constructing Circular Fillets ................................................................................................................ 385 Reversing Direction ............................................................................................................................. 386 Simplifying Geometry .......................................................................................................................... 387 Smoothing Geometry .......................................................................................................................... 388 Analyzing GeoMedia Professional Data ................................................................................................ 391 Working with Filter Queries ................................................................................................................. 391 Defining Attribute-Filter Queries ................................................................................................... 392 Working with Native Queries............................................................................................................... 405 Defining Native Queries against an Oracle Warehouse ............................................................... 405 Defining Native Queries against an MGSM Warehouse .............................................................. 408 Defining Linear Network Queries ................................................................................................. 410 Manipulating Queries .......................................................................................................................... 411 Displaying Queries ....................................................................................................................... 412 Editing Queries ............................................................................................................................. 413 Deleting Queries ........................................................................................................................... 414 Unloading Queries ........................................................................................................................ 414 Working with Spatial Filters ................................................................................................................. 414 Defining Spatial Filters.................................................................................................................. 415 Managing Spatial Filters ............................................................................................................... 419 Designating Spatial Filter Reference Features ............................................................................ 423 Querying Graphics-Only Features in MGE and MGSM ...................................................................... 425 Working with Queued Edit .................................................................................................................. 425 Looking at the Queued Edit User Interface .................................................................................. 427 Using Queuing Options ................................................................................................................ 431 Using Additional Commands ........................................................................................................ 432 Working with Searches ....................................................................................................................... 434 Creating and Managing Predefined Searches ............................................................................. 435 Performing Searches .................................................................................................................... 437 Working with Joins .............................................................................................................................. 441 Defining Joins ............................................................................................................................... 441 Analyzing Geometry ............................................................................................................................ 443 Analysis Options ........................................................................................................................... 444 Placing Buffer Zones around Features ............................................................................................... 447 Working with Functional Attributes...................................................................................................... 449 Functional Attribute Expressions .................................................................................................. 451 Output Data Types ....................................................................................................................... 452 Length ........................................................................................................................................... 452 Format .......................................................................................................................................... 452 Precision ....................................................................................................................................... 452 Operands ...................................................................................................................................... 453 Operators ...................................................................................................................................... 453 Functions ...................................................................................................................................... 453 Common Geometry Functions ..................................................................................................... 454 Constants ..................................................................................................................................... 457 Merging Feature Classes and Queries ............................................................................................... 458 Using the Right Mouse Menu ....................................................................................................... 460
Contents
Workflow for Dashed and Patterned Linear Features .................................................................. 462 Aggregating Data ................................................................................................................................ 462 Aggregation versus Analytical Merge ........................................................................................... 469 Generating Base Geometry ................................................................................................................ 470 Workflow for Dashed and Patterned Area Boundaries ................................................................ 471 Selecting Attributes ............................................................................................................................. 473 Editing Attribute Selection Queries through the Queries Command ............................................ 474 Combining Feature Classes and Queries ........................................................................................... 475 Editing Union Queries through the Queries Command ................................................................ 479 Linear Referencing .................................................................................................................................. 481 What is Linear Referencing? ............................................................................................................... 481 LRS Terminology .......................................................................................................................... 482 Linear Referencing and Geospatial Technology................................................................................. 482 LRS Linear Features and Event Data ................................................................................................. 483 Linear Referencing Commands .......................................................................................................... 484 Working with the LRS Precision Location Command ................................................................... 485 Working with the Dynamic Segmentation Command ................................................................... 489 Working with Labels................................................................................................................................ 497 Inserting Labels ................................................................................................................................... 497 Inserting Leader Lines ........................................................................................................................ 500 Moving Labels .............................................................................................................................. 503 Inserting Interactive Labels ................................................................................................................. 503 Orientation .................................................................................................................................... 503 Resolving Text Conflicts ..................................................................................................................... 506 Workflow Options ......................................................................................................................... 508 Geocoding ................................................................................................................................................ 511 Geocoding and Finding Addresses ..................................................................................................... 511 Looking at GeoMedia Address Geocoding: An Overview .......................................................... 511 Getting Started ............................................................................................................................. 513 Address Geocoding - User Concepts ................................................................................................. 513 Address Geocoding Terminology ................................................................................................. 513 Functional Overview ..................................................................................................................... 515 Finding an Address ............................................................................................................................. 516 Using the Find Address Command .............................................................................................. 519 Geocoding Multiple Addresses ........................................................................................................... 522 Using the Geocode Addresses Command ................................................................................... 524 Geocoding Addresses with Multiple Datasets .............................................................................. 526 Defining Geocoding Models ................................................................................................................ 527 Defining Parsing Rules ....................................................................................................................... 528 Overview ....................................................................................................................................... 529 Geocoding Coordinates ...................................................................................................................... 532 Inserting Traverses ................................................................................................................................. 535 Defining a Traverse ............................................................................................................................. 536 Typing Data .................................................................................................................................. 536 Selecting Data .............................................................................................................................. 538 Importing Data .............................................................................................................................. 539 Additional Command Features ........................................................................................................... 539
Contents
Insert Traverse Workflows .................................................................................................................. 540 Primary Workflow ......................................................................................................................... 540 Secondary Workflow..................................................................................................................... 540 Working with Layout Windows .............................................................................................................. 545 Layout Window Overview ................................................................................................................... 545 Accessing the Layout Window ..................................................................................................... 545 Setting Layout Window Options ................................................................................................... 545 Page Setup ................................................................................................................................... 547 Plotting .......................................................................................................................................... 547 Starting the Layout Window ................................................................................................................ 547 Inserting Layout Sheets ...................................................................................................................... 548 Importing Layout Sheets and Layout Templates ................................................................................ 548 GeoMedia Layout Sheets ............................................................................................................. 548 GeoMedia Layout Templates ....................................................................................................... 549 Imagineer or SmartSketch Template and Drawing Files .............................................................. 549 MicroStation Layout Templates .................................................................................................... 550 Exporting Layout Sheets and Templates ............................................................................................ 551 Selecting and Manipulating Layout Sheets ......................................................................................... 554 Renaming Layout Sheets .................................................................................................................... 554 Deleting Layout Sheets ....................................................................................................................... 554 Viewing Background and Working Sheets .......................................................................................... 555 Viewing Layout Window Properties .................................................................................................... 555 Manipulating Layers ............................................................................................................................ 556 Manipulating Layer Groups .......................................................................................................... 558 Designing Map Layouts for Printing in the Layout Window ............................................................... 561 Designing Map Layouts Overview ...................................................................................................... 561 Map Window Considerations When Printing from the Layout Window .............................................. 561 Defining Map Specifications in the Map Window ......................................................................... 561 Defining Marginalia Specifications in the Map Window ................................................................ 564 Basic Map Layout Workflows .............................................................................................................. 565 Placing Map Graphics in Layout Sheets Using Layout Frames ................................................... 565 Placing Map Graphics in Layout Sheets Without Using Layout Frames ...................................... 565 Components of the Map Layout .......................................................................................................... 566 Map Graphics Components .......................................................................................................... 566 Layout Graphics Components ...................................................................................................... 570 Workflows for Placing Map Graphics Using Layout Frames .............................................................. 596 Inserting Layout Frames ............................................................................................................... 596 Inserting Graphics into Layout Frames ........................................................................................ 598 Workflows for Placing Map Graphics without Using Layout Frames .................................................. 601 Inserting Maps into Layout Sheets ............................................................................................... 601 Inserting Marginalia into Layout Sheets ....................................................................................... 603 Updating Map Graphics in Layout Sheets .......................................................................................... 613 Modifying Map Graphics in Layout Sheets ......................................................................................... 614 Modifying Maps ............................................................................................................................ 614 Modifying Map Properties ............................................................................................................. 619 Modifying Legends ....................................................................................................................... 622 Converting Layout Legend to Raster Graphics ............................................................................ 623 Modifying Map Window Legend Properties .................................................................................. 623 Modifying North Arrows ................................................................................................................ 624 Modifying Scale Bars .................................................................................................................... 625
10
Contents
Inserting Cartographic Grids ............................................................................................................... 627 Defining a Neatline ....................................................................................................................... 628 Defining Grids ............................................................................................................................... 631 Defining Ticks and Crosses .......................................................................................................... 633 Defining a Border .......................................................................................................................... 635 Inserting Reference Grids and Indexes .............................................................................................. 638 Inserting a Reference Grid ........................................................................................................... 638 Inserting a Reference Index ......................................................................................................... 639 Inserting a Data Table .................................................................................................................. 642 Printing in GeoMedia Professional ........................................................................................................ 645 Printing Overview ................................................................................................................................ 645 Defining the Map Window Page Setup ............................................................................................... 645 Printing a Map Window ....................................................................................................................... 647 Printing to a File .................................................................................................................................. 648 Defining the Data Window Page Setup .............................................................................................. 649 Printing a Data Window ...................................................................................................................... 650 Defining the Layout Window Page Setup ........................................................................................... 651 Printing Layout Sheets from the Layout Window ................................................................................ 653 Plotting ................................................................................................................................................ 657 Printing Transparent or Translucent Graphics .................................................................................... 657 Outputting PDF from GeoMedia Professional .................................................................................... 658 Setting Acrobat Distiller Parameters ............................................................................................ 658 Exporting Data to Other Systems .......................................................................................................... 661 Exporting to Shapefile ......................................................................................................................... 661 Exporting to MapInfo Interchange Format .......................................................................................... 664 Exporting to Design File ...................................................................................................................... 666 Notes on Seed Files ..................................................................................................................... 672 Element Types .............................................................................................................................. 673 Exporting to Oracle Object Model ....................................................................................................... 674 Error Reporting ............................................................................................................................. 675 Exporting to SQL Server ..................................................................................................................... 676 Exporting to AutoCAD ......................................................................................................................... 678 Exporting to GML ................................................................................................................................ 680 Using Prefixes .............................................................................................................................. 681 Working with Libraries ............................................................................................................................ 685 Creating a New Library ....................................................................................................................... 685 Creating a New Library Connection .................................................................................................... 687 Managing Library Connections ........................................................................................................... 689 Organizing Libraries ............................................................................................................................ 691 Compatibility Status ...................................................................................................................... 692 Technical Support and Information ....................................................................................................... 697 Self-Help Support Tools ............................................................................................................... 697 Phone Numbers............................................................................................................................ 697 Other Links ................................................................................................................................... 698
11
Contents
Using Oracle Connections...................................................................................................................... 699 Delivery and Connection ..................................................................................................................... 699 Prerequisites ................................................................................................................................. 699 Read-Only Connections ............................................................................................................... 699 Read-Write Connections .............................................................................................................. 700 Password Persistence .................................................................................................................. 700 Domain Authentication ................................................................................................................. 700 Object Model Data Server Requirements..................................................................................... 701 Data Storage and Type Matching ....................................................................................................... 702 Geometry Storage ........................................................................................................................ 702 Geometry Type Mapping .............................................................................................................. 703 Oriented Points ............................................................................................................................. 705 Text and Labels ............................................................................................................................ 706 Raster Images .............................................................................................................................. 707 Data Type Matching - Oracle to GeoMedia .................................................................................. 708 Data Type Matching GeoMedia to Oracle ................................................................................. 709 Native Geometry Metadata .......................................................................................................... 710 Oracle Coordinate Systems - SRID .............................................................................................. 711 Utilizing Spatial Indexing ..................................................................................................................... 712 Creating Spatial Indexes .............................................................................................................. 712 Spatial Filtering ............................................................................................................................. 712 Native Queries .............................................................................................................................. 713 GeoMedias GDOSYS Metadata Schema .......................................................................................... 714 Creating the GDOSYS Schema ................................................................................................... 714 The Default GDOSYS Schema Definition .................................................................................... 715 Using Database Objects ..................................................................................................................... 729 User Accounts and Privileges ...................................................................................................... 729 Tables ........................................................................................................................................... 731 Default Values .............................................................................................................................. 731 Views and Join-Views................................................................................................................... 732 Triggers ........................................................................................................................................ 733 Database Utilities ................................................................................................................................ 735 Using an Existing Oracle Spatial Schema .......................................................................................... 736 Creating a New GeoMedia Warehouse in Oracle ............................................................................... 737 Using SQL Server Connections ............................................................................................................. 739 Delivery and Connection ..................................................................................................................... 739 Prerequisites ................................................................................................................................. 739 Connections .................................................................................................................................. 739 Password Persistence .................................................................................................................. 739 Permissions .................................................................................................................................. 740 SQL Server Warehouse Requirements ........................................................................................ 740 Data Storage and Type Matching ....................................................................................................... 741 Geometry Storage ........................................................................................................................ 741 SQL Server to GeoMedia Data Type Matching ............................................................................ 742 GeoMedia to SQL Server Data Type Matching ............................................................................ 742 GeoMedia Metadata Requirements .................................................................................................... 743 Working with SQL Server .................................................................................................................... 755 Importing Data .............................................................................................................................. 755 Feature Class Definition ............................................................................................................... 755 Undo/Redo ................................................................................................................................... 756 Default Values .............................................................................................................................. 756
12
Contents
Spatial Filtering ............................................................................................................................. 756 Views and Join Views ................................................................................................................... 757 Database Utilities ................................................................................................................................ 757 Coordinate System Information ............................................................................................................. 759 Projection Algorithms .......................................................................................................................... 759 Datum Transformation Models ............................................................................................................ 760 Functional Categories of Datum Transformation Models ............................................................. 760 Notes for the Canadian National Transformation 2.0 Datum Transformation Model ................... 761 Notes for the NADCON NAD27 to NAD83 and NADCON NAD83 to HARN (NGS Version 2.10) Models.................................................................................................................... 762 Notes for the NGA Earth Gravity Model ....................................................................................... 765 Notes for the GEOID (NGS Hybrid Geoid) Model ........................................................................ 766 Notes for the USGG (NGS Gravimetric Geoid) Model ................................................................. 766 Notes for the VERTCON (NGS Version 2.10) Model ................................................................... 767 Notes for the User-Supplied Datum Transformation Model ......................................................... 767 Standard Geodetic Datums................................................................................................................. 767 Named Geodetic Datums.................................................................................................................... 771 Vertical Datums ................................................................................................................................... 771 Ellipsoids ............................................................................................................................................. 772 Units of Measure (UOM) ..................................................................................................................... 774 Linear Units .................................................................................................................................. 774 Angular Units ................................................................................................................................ 775 Area Units ..................................................................................................................................... 775 State Plane Zone CodesNAD27 and Old Island Datums ................................................................ 776 State Plane Zone CodesNAD83 Datum .......................................................................................... 778 UTM Zones ......................................................................................................................................... 780 Raster Information ................................................................................................................................... 783 Raster Formats Supported in GeoMedia ............................................................................................ 783 ADRG ........................................................................................................................................... 783 ASRP / USRP ............................................................................................................................... 783 Bitmap........................................................................................................................................... 783 CADRG / CIB ................................................................................................................................ 783 CALS ............................................................................................................................................ 784 ECW ............................................................................................................................................. 784 ESRI ............................................................................................................................................. 784 Intergraph ..................................................................................................................................... 784 JFIF............................................................................................................................................... 784 JPEG 2000 ................................................................................................................................... 785 MrSID............................................................................................................................................ 785 NITF .............................................................................................................................................. 785 Oracle GeoRasters ....................................................................................................................... 785 PNG .............................................................................................................................................. 786 TIFF (and GeoTIFF) ..................................................................................................................... 786 USGS DOQ .................................................................................................................................. 786 Compression Techniques ................................................................................................................... 786 Tiling .................................................................................................................................................... 787 File Types and Categories Listed for Inserting a Georeferenced Image ............................................ 788
13
Contents
Layout Window Graphics Commands ................................................................................................... 789 Placing Graphics into a Layout Sheet ................................................................................................. 789 Editing Graphics in a Layout Sheet..................................................................................................... 789 Aligning Graphics in a Layout Sheet ................................................................................................... 789 Distributing Graphics in a Layout Sheet ............................................................................................. 789 Grouping Graphics in a Layout Sheet ................................................................................................. 789 Ordering Graphics in a Layout Sheet ................................................................................................. 790 Spinning or Flipping Graphics in a Layout Sheet ................................................................................ 790 Nudging Graphics in a Layout Sheet .................................................................................................. 790 Working with Symbols in a Layout Sheet ........................................................................................... 790 Inserting Objects into a Layout Sheet ................................................................................................. 790 Additional Layout Window Tools ......................................................................................................... 790 Edit Commands in the Layout Window ............................................................................................... 790 View Commands in the Layout Window ............................................................................................. 791 Sheet Commands in the Layout Window ............................................................................................ 791 Insert and Layout Commands in the Layout Window ......................................................................... 791 Tool Commands in the Layout Window .............................................................................................. 791 Window Commands in the Layout Window ........................................................................................ 792 Conversion Tables .................................................................................................................................. 793 International System of Units to United States Customary System .................................................... 793 United States Customary System to International System of Units .................................................... 794 Catalogs: Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers .............................. 795 Creating a Catalog Using Oracle ........................................................................................................ 795 Quick Steps .................................................................................................................................. 795 Step One: Create an Oracle Catalog database. ........................................................................ 795 Step Two: Set up a service name for the client. ........................................................................ 796 Step Three: Create ODBC DSN for the client. ........................................................................... 797 Step Four: Create a New Catalog Connection ........................................................................... 798 Server Database Upgrades ................................................................................................................ 799 Creating a Catalog Using the Microsoft MS-SQL Server.................................................................... 800 Quick Steps .................................................................................................................................. 801 Step One: Create a SQL database. ........................................................................................... 801 Step Two: Run the MS-SQL Catalog scripts. ............................................................................. 801 Step Three: Create user accounts. ............................................................................................ 802 Step Four: Set user permissions. ............................................................................................... 802 Step Five: Create an ODBC connection for GeoMedia Catalog users. ..................................... 804 Step Six: Create a New Catalog Connection ............................................................................... 805 LRS Data Structures ................................................................................................................................ 807 Overview ............................................................................................................................................. 807 Single-Level LRS Data Structures ...................................................................................................... 807 Option 1 - Measure ....................................................................................................................... 808 Option 2 - Measure with Internal Measure Markers ..................................................................... 809 Option 3 - Measure with External Markers ................................................................................... 810 Option 4 - Duration ....................................................................................................................... 812 Option 5 - Duration with Internal Markers..................................................................................... 813 Option 6 - Duration with External Measure Markers .................................................................... 814 Event Data Structures ......................................................................................................................... 816 Option 1 - Measure ....................................................................................................................... 816
14
Contents
Option 2 - Marker Offset ............................................................................................................... 817 Option 3 - Coordinates ................................................................................................................. 818 Option 4 - Duration ....................................................................................................................... 819 Supported SVG Element Types ............................................................................................................. 821 Background ......................................................................................................................................... 821 Discussion ........................................................................................................................................... 821 Versions and Variations................................................................................................................ 822 Supported Types ................................................................................................................................. 822 General Elements ......................................................................................................................... 822 Symbol Element ........................................................................................................................... 822 Use Element ................................................................................................................................. 823 G Element ..................................................................................................................................... 824 Metadata Element ........................................................................................................................ 824 Geometry Elements ............................................................................................................................ 825 Line Element ................................................................................................................................. 825 Polyline and Polygon Elements .................................................................................................... 825 Rect Element ................................................................................................................................ 826 Circle Element .............................................................................................................................. 826 Ellipse Element ............................................................................................................................. 827 Path Element ................................................................................................................................ 828 D Attribute ..................................................................................................................................... 828 Text Element ................................................................................................................................ 829 Common Attributes ............................................................................................................................. 829 Style Attribute ............................................................................................................................... 829 Transform Attribute ....................................................................................................................... 832 SVG Symbol Metadata XML Schema ................................................................................................. 833 Header Information ....................................................................................................................... 834 Element Descriptions.................................................................................................................... 835 XML Source .................................................................................................................................. 836 Example .............................................................................................................................................. 836 Additional Geocoding Information ........................................................................................................ 839 Address Geocoding - Administrator Concepts and Workflows ........................................................... 839 Functional Overview ..................................................................................................................... 839 Architectural Overview.................................................................................................................. 840 Geocoding Models and Parsing Rules ............................................................................................... 851 US Geocoding Models and Parsing Rules ................................................................................... 852 Canadian Geocoding Models and Parsing Rules ........................................................................ 858 Japanese Geocoding Models and Parsing Rules ........................................................................ 864 Spanish Geocoding Models and Parsing Rules ........................................................................... 869 Intersection Geocoding ....................................................................................................................... 874 Sounds Like Algorithms ...................................................................................................................... 876 Sounds Like (English) Algorithm ................................................................................................. 876 Sounds Like (Spanish) Algorithm ............................................................................................... 877 File Types ................................................................................................................................................. 881 Index ......................................................................................................................................................... 883
15
Contents
16
SECTION 1
Start Here
Welcome to GeoMedia Professional-the next generation in geographic information systems (GIS). Based on Jupiter technology from Intergraph Corporation, this product is an enterprise GIS for the Windows XP, Windows Vista , Windows 7, or later operating systems. This product is the perfect tool for collecting GIS data, populating an enterprise database, and turning information into precise finished maps for distribution and presentation. As a viewing and analysis tool, this product allows you to combine geographic data from different sources, in different formats, and with different map projections, all into a single environment. Using this product, you can perform complex queries on spatial and attribute data from various sources, and produce numerous views of highly sophisticated maps in a single GeoWorkspace. Furthermore, this product gives you the capability of printing those map views on a single sheet and adding borders, marginalia, and other finishing touches. As a data capture and maintenance tool, this product allows you to capture and to edit data more easily, faster, and with more intelligence than other products. Its integrated vector and raster snaps allow you to capture vector data from raster images, automatically identifying snap points to ensure accurate heads-up digitizing. The software also provides table-top digitizing and vector transformation for data requiring geometry transformation. Using the software, you can capture clean, accurate data the first time, thus minimizing editing. Automatic vector breaking and coincident geometry digitizing allow you to avoid traditional data-capture problems. However, you can locate data-capture problems with automatic error detection and then correct them with intelligent feature placement and editing tools. Furthermore, you can quickly annotate the data with powerful labeling and text-placement tools. This product is also a software-development environment, and you can customize it with standard Windows-development tools such as Microsoft Visual Basic and Visual C++ .
17
Start Here
In this product, features are contained in feature classes, and the word feature refers to each instance of a feature within a feature class. Feature classes, images, query results, and thematic displays in the map window are collectively referred to as either features or map objects. Features are represented in the map window by geometry and in the data window by attributes. You can display any number of map and data windows simultaneously or separately. They are linked so that changes made in one window are automatically reflected in the other. You display features in a map window by adding entries to the legend. The legend is the control center for the map window. Through the legend, you populate the contents of the map window and control the display characteristics of the features, including their style and display priority. You can also perform tasks, such as capturing new data, performing maintenance on existing data, and inserting images or buffer zones. Furthermore, you can view data written to a read-write warehouse along with other data sets in a single GeoWorkspace. Results of your analyses can be customized in the map window, printed, and saved for future use, all without altering the original data.
Developer Documentation
Document GeoMedia Professional Command Wizard Help Description A CHM file that contains information about using the Command Wizard to create Visual Basic commands for the GeoMedia-based application and to edit or to delete Visual Basic or Visual C++ command-set information. Access through the Command Wizard. A DOC file that provides information about customizing the software and building your own applications with the GeoMedia engine. Access through Start > All Programs > GeoMedia Professional > Developer Documentation. A CHM file that contains the objects, methods, and properties in the softwares automation layer.
To access the documents, navigate to GeoMedia Professional > User Developer Documentation from the Start menu.
18
Start Here
User Documentation
Document Description GeoMedia Professional Installation A PDF file that contains instructions for installing the product. Guide GeoMedia Professional User's Guide GeoMedia Professional Help Learning GeoMedia Professional A PDF file that contains an overview of tasks. A CHM file that contains instructions for using tools and commands. Steps you through an example workflow that uses real data and covers the basic tasks.
To access the documents, navigate to GeoMedia Professional > User Documentation from the Start menu.
Utilities Documentation
Batch Plotting Database Utilities Define CAD Server Schema File Define Coordinate System File Define Symbol File Define Text File Server Format File Define Warehouse Configuration File Edit MGSM Parameter File Licensing Utility Publish Address Geocoding Index Publish to GeoMedia SmartStore Warehouse Utilities Documentation consists of online-only documentation for the following delivered utilities (Start > All Programs > GeoMedia Professional> Utilities): You can access this online documentation by: Selecting the utility document name in the GeoMedia Professional Help menu. Pressing F1 while the utility is active. Selecting online Help from the utility Help menu in the Batch Plotting, Define CAD Server Schema File, Define Text File Server Format File, and Publish to GeoMedia SmartStore Warehouse utilities.
Interactive Documents
This product provides an interactive tutorial to help you learn how to perform the basic tasks. If you are new to this product, you should work through GeoMedia Professional Training Guide first. Help is available online if you need step-by-step instructions, and other documents are available for programmers who want to customize the software.
19
Start Here
Help Topics
You can find information for advanced topics and procedures from the online Help. Included with the Help topics is a dictionary. If Help was not installed on your hard drive during setup, you must have the GeoMedia Professional CD in your CD-ROM drive or be connected to the network node containing the Help files. To display Help when GeoMedia Professional is active, select Help > GeoMedia Professional Help from the menu. To display Help when GeoMedia Professional is not active, select Start > All Programs > GeoMedia Professional > User Documentation > GeoMedia Professional Help. Help is context sensitive, which means that you can press F1 to display Help for the active window or dialog box. You can also click the Help button or press SHIFT+F1. When the cursor changes to a question mark, select a menu item, toolbar, or area of a window or dialog box.
Programming Guides
This product includes two online guides for developers who have experience with programming languages that use automated objects and who want to customize or build applications on this software. Building on the GeoMedia Professional Engine is an interactive user's guide developed in HTML. GeoMedia Professional Object Reference covers the objects, methods, and properties available through automation. You access these documents by selecting All Programs > GeoMedia Professional > Developer Documentation from the Start menu.
What's New
To read about new features, updated features, and system requirements for GeoMedia Professional 6.1.11, see the SG&I Support page. 1. Go to the SG&I Support page (http://support.intergraph.com/). The first time you select this link, it displays the Intergraph Support page, and you need to select Security, Government & Infrastructure Division to display the SG&I Support page. When you select this link the next time, it will go directly to the SG&I Support page. If
20
Start Here
you later want to change the division, just click (Change Support Division) in the list at the upper left of the SG&I Support page. 2. Under Product Support, select the appropriate Intergraph product from the Products drop-down list; then click Go. 3. On the Customer Log In page, enter your user ID and password; then click Log In. If you do not have a user login, click the link to request one. 4. On the GeoMedia Professional page, scroll down to the Product Versions table and click the download icon for the document you want to read. To read about new features, click Release Notes. To read about updated features, click Issues Resolved. To read about system requirements, click Certified Environments. Patches and fixes usually do not have Release Notes and Issues Resolved.
Getting Started
To start this product, select Start > All Programs > GeoMedia Professional > GeoMedia Professional. If the introductory GeoMedia Professional dialog box has been turned off, this dialog box appears.
This dialog box lets you create a new GeoWorkspace using a blank GeoWorkspace or a GeoWorkspace template or open an existing GeoWorkspace from a list of recently opened GeoWorkspaces. You can select one from the list, and click OK, or if the existing GeoWorkspace you want is not listed, you can select More Files, and click OK to find the GeoWorkspace yourself. To not open this dialog box when you start the software, check Don't show this dialog box again. To exit the software at any time, select File > Exit from the GeoMedia Professional menu. See the Working with GeoWorkspaces section for complete information on using GeoWorkspaces.
21
Start Here
menu items are dimmed when the tools they invoke are not available, and you can see what tool a button invokes by placing your cursor over the button. Common tools, such as File > Print, work essentially the same in this application as they do in any Windows application. Still, the GeoMedia Professional working environment does have some special characteristics: Within the software, you work in three types of windows, map windows, data windows, and the layout window. These windows are contained in a GeoWorkspace, which is roughly analogous to a workbook in Microsoft Excel. If you have a Microsoft IntelliMouse , you can use it to manipulate map, data, and layout windows faster and more efficiently. GeoMedia Professional offers several specialized toolbars that are available only under the appropriate circumstances. The Data toolbar, for example, is available only when the data window is active. Select View > Toolbars to specify which toolbars you want to display. Some right-mouse menus are available in this product. You display right-mouse menus by pressing the right mouse button. The tools on the menu vary with the location of your cursor. All controls in the product that perform the display and entry of either graphic text or attribute text support multi-language text (Unicode). The product's toolbars can be moved from their default locations and docked at other locations within the interface. Moving a toolbar over a map window converts the toolbar to a dockable control, and some tools provide a control rather than a dialog box interface. Further, clicking the right mouse button on the title bar of a control displays a menu that allows you to restore, move, minimize, maximize, or hide the control, while clicking the X icon dismisses the control. Clicking the right mouse button on a toolbar (or on the icons in a control) displays a menu that allows you to turn toolbars on and off, display the Status and Precision Coordinates toolbars, and customize toolbars. See the Working with Map Windows, Working with Data Windows, and "Working with Layout Windows" sections for information on these types of windows.
22
Start Here
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 Designing Map Layouts for Printing in the Layout Window 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 Registering 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. Register 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.
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.
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.
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.
5. 6.
Export the GIS features as 5. shapefiles. 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.
27
Start Here
1. Capture GIS features using GeoMedia Professional, and store them in Access or Oracle.
2. 3.
Export the GIS features as shapefiles. Use ArcView or ARC/INFO tools to merge the new and edited features into the legacy GIS .
2. 3.
Use MGE to import warehouse data into an MGE project. 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.
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 support 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.
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
Features can be represented in the GIS as points, lines, polylines, areas, arcs, text, and images.
30
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.
31
Start Here
GIS Applications
A GIS can be productively used in many endeavors, including the following: Agriculture Cartography Geology Education Facilities Management Asset Management Business Meteorology Tourism Archeology Military installation management Environmental Management
Utilities Management (water and sewer, electric, communication systems, cable, cell phone coverage areas, and so forth) Natural Resources and Resource Conservation Public Safety (emergency dispatch management) Disaster planning (hurricane evacuation, earthquake) Health Care Industry (disease outbreak studies, epidemics) Industrial (plants, pipelines, storage tanks, and so forth) Aeronautical (Airport GIS, airspace management) Marine Engineering (biology, soundings) State and local government - Land Information Systems (LIS): parcels, right-of-way, and so forth. Transportation Industry (highways, railroads, planning and analysis)
Benefits of GIS
Some of the benefits of using a GIS are the following: Reduces Operations and Maintenance Costs-As a productivity multiplier, a GIS enables less-skilled personnel to complete sophisticated analyses, as well as expanding the output of the technical staff. Improves Mission Effectiveness-A GIS provides command and management personnel with the opportunity to rapidly analyze multidisciplinary sets of data and to arrive at the best solution with complete supporting documentation. Provides Rapid Modeling Capabilities for Analyzing Alternative Strategies- A GIS provides the capability for command personnel to make the best and most cost-effective decisions in tight budget environments. Greatly Improved Communication Aids-Effective communication is essential for managing an infrastructure, whether it be a college campus, military installation, or a city. GIS visualization tools are fast and easy to use. Promotes Harmony-By providing a standard set of data and tools for modeling and analysis, major alternatives for a project can be consistently produced and analyzed. This 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
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
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 verify that your warehouse connection parameters are correct.
34
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.
36
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.
37
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. Verify that GeoWorkspace Template appears in the Save as type field. 12. Type a name for the template in the File name text box. The file extension must be .gwt. 13. Click Save.
38
SECTION 3
39
40
For the geographic base storage type, you also define the horizontal and vertical storage units, but the storage center options are longitude, latitude, and height. For the geocentric base storage type, you define the geocentric storage unit and the storage center options of X, Y, and Z. Horizontal storage unitFor the coordinate system of a data source, the horizontal storage unit defines what the distance between sequential integer X or Y coordinate values is when the base storage type is geographic or projection. For example, if the resolution is 0.001 ft., and then the X coordinate of a point changes from 1 to 2, the distance in the X direction of the change is 0.001 ft. This is very important for data sources that store coordinates as integers (MGE, MGDM, MGSM, and CAD with .dgn files) because for these data types, you cannot go between 1 and 2. Thus, the smallest distance that will resolve two values as being separate is 0.001 ft., which leads to the term resolution being applied to integer storage. In the context of IGDS/MGE, this concept was presented with the term UOR (Unit of Resolution), whereas GeoMedia Professional uses storage coordinates. Thus, when MGE tells you that you have 1000 UORs per ft., it is telling you exactly the same thing that GeoMedia Professional is telling you when it says you have a horizontal resolution of 0.001 ft. (1 ft./1000 UORs). GeoMedia Professional is just looking at the distance between two adjoining UORs, whereas MGE/MCSO presents the same concept as "how many UORs fill a common distance (such as 1 ft.)". The GeoMedia Professional way of presentation mimics common language, such as, "My data are at cm. resolution" (meaning the distance between UORs is 1 cm., whereas MGE would state this as "100 UORs per m." or "1 UOR per cm."). For CAD and MGE users, the horizontal resolution is expressing the very real limitations of the data. For example, you cannot draw a line and measure between two UORs. For other data sources that use floating point, these limitations do not exist (within reason). Much ArcInfo and MapInfo data are defined with a horizontal storage unit of 1 meter (or for geographic data, 1 degree). That just means that the data source chose to store the coordinates in those units. It is not necessary for floating point data to be stored as hundredths of a foot, for example, which would be wasted calculation; they just store it as feet (or meters, or 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
42
3. 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 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 user-defined (non-standard) geodetic datum, you can change the ellipsoid on the Geographic Space tab; and if you select a user-defined (non-standard) ellipsoid, you can change ellipsoid parameters as well. Optional: On the Geographic Space tab, select the vertical datum from the Vertical datum drop-down list.
4.
5. 6.
7.
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
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.
Changing the coordinate system type from Projection or Geographic to Geocentric resets the vertical datum to Ellipsoid (geometric). 10. Optional: On the General tab, type values in the coordinate system Name and Description fields. Both will be stored in the warehouse and can make it easier to determine what coordinate systems are assigned to specific feature classes. The Name entry will be used in the Coordinate system drop-down list on the New <feature class name> dialog box when you exit the Coordinate System Properties dialog box with OK. 11. Click OK on the Coordinate System Properties dialog box. 12. Optional: To create or change the default coordinate system for the warehouse, select the appropriate coordinate system from the Coordinate system drop-down list; then click the Set As Default button. You can assign only one default coordinate system per warehouse. 13. Click OK on the New <feature class name> dialog box.
45
The default warehouse coordinate system is assigned by clicking the Set As Default button on the New / Edit / Review <feature class name> dialog box within the Warehouse > Feature Class Definition command. If a default coordinate system has not been defined, the software will look for the first coordinate system having the Description property value Default. If no default is found that way, the first coordinate system found in the metadata table GCoordSystem will be used. The When making first connection option allows you to match the two coordinate systems by copying the definition of the default coordinate-system of the first warehouse connection made for the GeoWorkspace with the New Connection command to the current GeoWorkspace coordinate system. If you do not select this option, New Connection has no effect on the definition of the GeoWorkspace coordinate system. You can verify the new coordinate-system definition through View > GeoWorkspace Coordinate System. The When creating a new warehouse option allows you to match the two coordinate systems by copying the coordinate-system definition of the current GeoWorkspace to the default coordinate system of a new Access warehouse when it is created. If you do not select this option, the active template defines the default coordinate system of the new warehouse. This option does not affect Oracle or SQL Server connections. The optimum workflow in many situations is to first use New Connection to connect to your data, thus setting the GeoWorkspace coordinate system, and then to use New Warehouse to create any appropriate new Access warehouse(s). This sequence ensures that the new Access warehouse shares the same coordinate-system definition with the data source and the GeoWorkspace.
46
Related Effects
The software automatically updates the various aspects of the system that are affected by copying the default coordinate-system definition of the first connection to the GeoWorkspace coordinate system. Any transformation pathways to coordinate systems of connections that were previously created and then deleted will be updated. Any spatial filters that exist (either from the GeoWorkspace template or from running Spatial Filter definition commands) will be transformed into the new GeoWorkspace coordinate system. Coordinate-system information will be updated on all map views, resulting in recalculation of the display scale. If the north arrow and scale bar are displayed, they will be refreshed to account for the new coordinate system and display scale.
Copying the GeoWorkspace Coordinate-System Definition onto the Default Coordinate System of a New (Access) Warehouse
If you select the matching options, the software copies the definition of the coordinate system of the GeoWorkspace into the warehouse and marks it as the default coordinate system for the warehouse. This definition is written into the GCoordSystem table of the database. The software creates a new row if necessary. You can actually use the New Warehouse command in two slightly different ways to create 1) a new Access warehouse (.mdb the default), or 2) a new Access warehouse template (.mdt). Only when creating a new warehouse (.mdb) does the command establish a connection to the new warehouse. Because an open connection is required to update or to add a row to the GCoordSystem table of the warehouse, it is only when a new warehouse (not warehouse template) is created (and the preference is set) that the New Warehouse command copies the GeoWorkspace coordinate system to the warehouse and marks it as the default coordinate system. The impacts of copying the GeoWorkspace coordinate-system definition onto the coordinate system of a new (Access) warehouse affect the optimum workflow. The optimum workflow in many situations is to first use New Connection to connect to your data source, thus setting the GeoWorkspace coordinate system, and then to use New Warehouse to create any new warehouse(s). This ordering ensures that the new warehouse shares the same coordinate-system definition with the data source and GeoWorkspace.
This control displays the precision coordinates for the current cursor position in the map window. The current coordinate format drop-down list determines if the displayed 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
These are the options you can set on the Units and Formats tab: Type specifies the type of unit for which to set the default unit and precision. Each unit type used by the software is listed. When the software outputs values of the specified unit type, those values by default are displayed using the units and precision specified here. Some commands allow you to override these defaults. Unit sets the linear, areal, or angular unit of measure. The choices vary with the unit type. 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.
48
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.
49
When you make changes to the autodt.ini file, they do not affect any GeoMedia Professional or GeoMedia Professional object-based process that is currently running. This is because the coordinate transformation software only reads the file once at start-up time; so if the file is altered afterwards, the process does not know about the alteration until the next time the process is run. In addition, when you make changes to the autodt.ini file, they do not affect transformations that have already been persisted in a GeoMedia Professional GeoWorkspace. This is because the coordinate transformation software only uses the autodt.ini file to build new datum transformations. If, for example, you make a connection and the software at that time uses the autodt.ini file to include a datum transformation and you then save the GeoWorkspace, any subsequent change you make to the autodt.ini file does not affect that saved GeoWorkspace. This is because the datum transformation has already been created and saved within the GeoWorkspace. See the Coordinate System Information appendix for a list of datum-transformation models the software supports.
50
4. 5. 6. 7.
8.
9.
10. 11.
51
52
53
54
SECTION 4
You can output feature data in any GeoMedia Professional-supported format to a warehouse with the Output to Feature Classes command. You must have at least one read-write open connection to use this command. See the Outputting Feature Data to Warehouses section of the Working with Features 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 ARC/INFO ArcView shapefile MGE Data Manager (MGDM) MGE Segment Manager (MGSM) ODBC Tabular
55
Oracle Object Model SQL Server SmartStore Server Text File Server WCS (Web Coverage Service) WFS (Web Feature Server) WMS (WebMap Server)
GeoGraphics GML (Geography Markup Language) I/CAD MAP KML (Keyhole Markup Language) MapInfo 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).
56
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.
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
58
59
60
61
62
63
64
65
66
67
For all other cases, the connection is not proxied. While using the Connections command, verify if the connection type is AFM.GDatabase. In such case, instead of displaying the data server type as AFM, the underlying data server name is determined and populated.
68
Your choices of status are summarized in the following table: Command Button Initial Connection Status Final Connection Status If the data server is read-only: N/A No action - status remains unchanged. Open read-only N/A No action - status remains unchanged. Open read-only N/A Open read-only N/A Closed Closed No action - status remains unchanged. If the data server is read-write: No action - status remains unchanged. No action - status remains unchanged. Open read-write No action - status remains unchanged. No action - status remains unchanged. Open read-only Open read-write Open read-only N/A Closed Closed No action - status remains unchanged.
Open Connection
Open Read-Only
Reopen Connection
Close Connection
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
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.
70
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.
71
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
INGRPickLists GPickListTable The table referred to by the GAliasTable entry for INGRPickLists must contain the following fields: FeatureName, FieldName, PickListTableName, ValueFieldName, DescriptionFieldName, and FilterClause. Use the New Table command in Access to create the PickList metadata table using the following provided definitions (the table itself can be called anything as long as it is referenced in the GAliasTable): GPickListTable Column Name FeatureName FieldName PickListTableName ValueFieldName DescriptionFieldName FilterClause Datatype Varchar(255) Varchar(255) Varchar(255) Varchar(255) Varchar(255) Varchar(255)
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
GPickListTable FeatureName Buildings Buildings Buildings FieldName Name State Type PickListTableName PL_Building PL_State PL_Building ValueFieldName CodeValue StateName CodeValue
Bld_Type = 'TYPE'
PL_Building CodeValue 0 1 2 3 ValDescription MOTEL MARRIOT HOLIDAY INN BED AND BREAKFAST Bld_Type TYPE NAME NAME TYPE
74
75
76
SECTION 5
77
78
79
3. From the Warehouse drop-down list, select the read-write warehouse where you want to store the path to the image and other associated attributes. 4. From the Feature class drop-down list, select the feature class to add the image to, or type a new feature class name. Remember, all images in a single feature class must have a common coordinate system and projection. Only those image feature classes in which the coordinate system matches that of the GeoWorkspace will appear in the drop-down list. 5. Click OK to load the image into the specified warehouse and feature class.
The software prompts you to define a rectangle by two points in the active map window for the location of the image.
6. Place the cursor over the location for one corner, press and hold the mouse button, and then drag the cursor to the opposite corner.
The 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
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
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.
82
83
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
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.
85
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.
All files of the selected entries are validated and their associated icons are updated accordingly.
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
Translucency percentageThe 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. ContrastThe contrast of the image display on a scale of 100 to 100, applicable to all image types, including 8-bit color index imagery, however, not binary. BrightnessThe brightness of the image display on a scale of 100 to 100, applicable to all image types, including 8-bit color index imagery, however, not binary. Invert ImageIndicates whether the image display should be inverted (creates the effect of a negative) , applicable to all image types, including 8-bit color index imagery, however, not binary. Transparent colorA color within the image that is to be treated as transparent (not drawn). This is an actual color value (R,G,B), not a color index or pixel value. It is applicable to all image types except binary. Transparent pixel valuesA set of pixel values within the image that are to be treated as transparent (not drawn), applicable only to color index and grayscale images. These are color index or pixel values, not an actual color value (R,G,B). The pixel values are presented as comma (,) and a hyphen (-), separated values from 0-255. Binary foreground colorThe color with which the foreground pixels of a binary image are to be displayed, applicable only to binary images. Binary background colorThe color, if any, with which the background pixels of a binary image are to be displayed, applicable only to binary images. The background may be made transparent by not specifying a background color.
87
The changes are saved and reflected in the display of the image(s) in the associated map window.
OR
88
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.
89
2. Select an image feature class, query, category, or reference feature from the Create image footprints for drop-down list. 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.
3. 4. 5. 6. 7. 8. 9.
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
91
92
SECTION 6
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
94
The following diagram shows a the same feature selected in a data window and centered, fit, and zoomed out in the map window:
95
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
97
Using an IntelliMouse
If you have a Microsoft IntelliMouse, you can use it to manipulate the display in your map windows faster and more efficiently. Rolling the IntelliMouse wheel forward causes the view to zoom in at the current cursor location, and rolling the IntelliMouse wheel backward causes the view to zoom out at the current cursor location.
Zoom Out
Zoom Previous
Zoom to 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.
This command generates expected results only when the selected features are within the defined display scale range of the legend entry.
98
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 panel at the bottom of the GeoWorkspace window. To see the display scale change, select it on the Options dialog box, and zoom in or out in the map window.
99
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
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.
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
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
The preceding illustration shows the three distinct drawing orders available, from left to right: Order by feature, Order by style, and Select single index component. As with other style types, you can find and select a style collection on the Styles and Select Style dialog boxes, where you can edit the most commonly used style properties, with a focus on providing group editing of all members of the collection. In most cases, these collection controls provide limited editing capabilities because the collection may contain a mixture of different style types within that style class, and those style types may have different properties, as follows: Point Collection Style-Permits manipulation of the color and size of all point styles. Line Collection Style-Permits manipulation of the color and width of a simple line style. Fill Collection Style-Permits manipulation of the fill color and translucency percentage. Area Collection Style-Permits manipulation of the fill color and translucency percentage, and of the boundary color and width of the line style(s) associated with the area boundary. Compound Collection Style-Permits manipulation of the following: Fill color and translucency percentage. Boundary/line color and width of the line style(s) associated with the boundary/line. Point color and size of the point style(s). Text Collection Style-Permits the manipulation of the font, size, font style characteristics (bold, italic, underline), and color.
103
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
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.
105
See the corresponding GeoMedia Professional Help topics for complete information on these two dialog boxes.
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.
106
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 members 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
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
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
Clicking this button in any of the three states displays the Animation dialog box, which lets you define the animation frame sequence. Each member of the sequence is a frame with a designated style property value (or expression), as well as definition of the timing and nature of the transition to the next frame in the sequence. Note that you cannot define animation for the Locatable style property.
Clicking New or Properties on the Animation dialog box displays the Animation Property dialog box, which lets you define the properties for a specific animation frame. The options available vary with the selected style property. In addition, clicking the Animation icon on the Style Properties dialog box displays the Animate Style dialog box, which lets you set the animation properties (Animated and StartTime) of the root style for legend entries, except when the root style is a non-image style. This dialog box also lets you enable/disable the animation.
See the corresponding GeoMedia Professional Help topics for complete information on the animation user interface and its use.
110
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
112
See the "Adding a WMS Legend Entry" section for information on using this control.
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.
113
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
115
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.
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 encompasses a wide range of common Microsoft-supported formats mostly, but not exclusively, of a raster nature. The following style properties exist for a picture style:
116
JPEG File Exchange Format Image (*.jpg, *.jpe, *.jpeg). TIFF Document (*.tif, *.tiff). Windows Metafile Image (*.wmf).
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-supported font or picture, or a GeoMedia-supported symbol file format, for example a MicroStation cell file. You can define the following font style parameters: font, character, size, color, translucency percentage, halo, rotation, alignment, and offset. Symbol Style-This default point style class provides for the rendering of symbols at point locations. The term symbol indicates any of a number of data formats, produced by GeoMedia 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 supported: Predefined symbols-A set of simple, predefined symbols (circles and other shapes) are built into the symbol style. It is not necessary to select an external symbol path. Each predefined symbol has a name by which it is selected. The default symbol style is a small, filled, black circle. GeoMedia Feature Symbol Files (*.fsm)-This is a multi-symbol type. MicroStation Cell Files (*.cel)-This is a multi-symbol type. With this type, it is not necessary to convert cell files into .fsm format. AutoCAD Drawing Files (*.dwg)-This is a single-symbol type. The symbol name is automatically determined from the symbol file name. With this type, it is not necessary to convert drawing files into .fsm format. Scalable Vector Graphics (SVG) Files (*.svg)-This is an industry standard, multi-symbol type. These symbols may contain embedded text elements within the symbol that can be tied to attributes. This provides a parametric symbol capability in which the symbol text changes based on the attribute value for each feature instance, for example, Interstate Highway Shields.
117
No cap (the dash cap setting is used at the start and end instead) The anchor choices generate a cap that is proportionally larger than the width of the line, forming a knob at the start or end of the line. The display of the ends of each dash in the dash-gap sequence of a line may be set to any of the following: Round, Flat, or Triangle. The display of the joins that occur at each bend/vertex in a multi-vertex geometry may be set to any of the following: Round, Miter, or Bevel. Pattern Line Style-This line style class provides the ability to render a pattern of point styles along linear geometries, area boundaries, and area hatching. You can define the following simple line style parameters: point style, position of point style along line, insets, and offsets. The point style can be any user-defined style that is of the point style class. You may use the full range of point style types (picture style, font style, symbol style, or a collection of any combination of these) to draw the pattern. You can then adjust this property through the common properties interface. You can use any combination of five different positioning options on the Pattern Style tab of the Style Properties dialog box (Fix at start, Fix at end, Fix at center, Fix at vertex with angle, or Repeat with spacing of) for how the pattern elements described by the 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
119
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 members of compound geometries. As a composite style, the compound style has no style properties of its own for drawing. Rather, it provides a hierarchical style composition tree that includes the following style collections of: Points-Zero or more point style types to use in drawing the point geometries. Lines-Zero or more line style types to use in drawing the line geometries. Areas-Zero or more area style types to use in drawing the area geometries. Compound features also provide the ability to perform the following: Display no points, no lines, and/or no areas. Display any number of point styles, line styles, and areas styles. Guarantee, through style collections, that points are on top of lines, which are on top of areas.
120
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.
121
122
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.
123
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
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.
125
126
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.
127
128
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
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
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 supported for range thematics are: byte, short, long, float, currency, and double; the data types supported for unique value thematics are: text, memo, byte, short, long, float, and double. After selecting the attribute, you select the appropriate classification through the Classify button to populate the two grids with corresponding styles, values, labels, and counts. The styles are derived from the current settings of the Thematic styles frame. 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
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 joins, 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 assigning colors to area features, the result varies based on the definition of the Base style. If the base style of the area only contains a boundary definition, the boundary color will be modified. If the base style of the area contains a fill and boundary definition, only the fill color will be modified. If the base style of the area contains multiple fill definitions, the fill color of all definitions will be modified. The image drop-down list contains colored bands that represent a color scheme. The name for the color scheme is not displayed in the list but as a tooltip for the active color scheme. The ramp
133
When you select a color scheme, it is immediately applied to the styles in the top grid. The first item in the grid gets the first color in the color scheme. The second item gets the second color, and so on. If there are more items in the grid than color scheme colors, the process of assigning colors wraps back to the first color in the color scheme. Selecting a different color scheme does not re-apply the base style or size ramping to the top grid; only the colors are adjusted. The Assign sizes/widths options let you ramp the minimum/maximum size of a point style, text style, or a compound style that has a point style in it (that is, size applies to point and text styles only) or the minimum/maximum width of a linear style. Automatic size or width assignment happens when you click Classify or Base style. In each case, the active settings in the Thematic styles frame are applied. If you insert a new item, it gets assigned the base styles width. The size and width check boxes are not displayed at the same time. If the style is an area style, the check box and the minimum/maximum items are not displayed. If this option item is unchecked, automatic assignment of style information to the thematic classes ignores the size/width ramping and defaults to the width of the base style for all thematic classes. When selecting the minimum/maximum width, it is immediately applied to the styles in the top grid. The first item in the grid is assigned the minimum width value. The second item is assigned the next calculated width value, and so on. The act of assigning a minimum/maximum width does not re-apply the base style or active color scheme to the top grid. Only size ramping occurs. 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.
134
135
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
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
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
139
Right clicking on a treeview layer displays a right mouse menu from which you can select Show Capabilities to display the Capabilities of <Layer name> dialog box. This read-only dialog box contains the capabilities of the layer: the name, title, abstract, online resources URL, queryable, and time request supported.
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
141
See the Working with the Style Properties Dialog Box section for more information on using the Legend Entry Properties dialog box.
142
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.
143
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.
144
145
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.
147
Locatable Off
Add
Fit by Legend Entry Fits the contents of the selected legend entries to the map window. Legend Entry Properties Fit Legend Properties Opens the Legend Entry Properties dialog box to set the properties of the selected legend entry. Fits the legend to display all entries. Opens the Legend Properties dialog box to set the properties of the legend.
148
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
2. Type a title for the map window in the Window name field. 3. Select a legend for the map window. The legend can be one that has already been named (saved) in the GeoWorkspace, if one exists, or an empty legend. 4. Click OK.
You can click and drag the north arrow anywhere within the map window. The size of the north arrow remains constant regardless of how the scale is changed in the map window. If the azimuth is defined by the north arrow location, the north arrow is intelligent, that is, it updates dynamically when you move it or when you zoom or pan through the window. If the azimuth is user-defined, the north arrow does not update dynamically. The direction of the north arrow is determined in the following manner:
150
2. To change the north-arrow symbol, browse to select a different one. The product delivers .wmf files for north arrows and compass roses in the \GeoMedia Professional\Program folder, but you can also select another one if you have it. To see graphics of all the north arrows and compass roses, open the NorthArrows.pdf file, which is also in the \GeoMedia Professional\Program folder. 3. Select the size from the Size drop-down list, or type the appropriate value. The north arrow is not defined in ground units; it is printed at the position and size specified in the map window. 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
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 Designing Map Layouts for Printing in the Layout Window section for information on using scale bars in the layout window.
152
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
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
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
To measure distance/area:
1. Select Tools > Measure/Area Distance.
156
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 <Ctrl>+C accelerator key. This command is available for features from both read-write and read-only connections. The command also identifies both parallel and collinear lines. Measuring an angle with the Segment Mode requires you to define two line segment portions (of a linear or area feature) as input. If the identified lines do not intersect, an intersection point is
157
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 joining these two pairs of points are then extended to intersect at a vertex point. The angle between the two lines is shown dynamically. As you move the mouse, the measured angle value is displayed as a dynamic text at the midpoint of a dynamic arc showing the angle value. The command responds to mouse moves and calculates the appropriate angle measurements. As you hover the mouse beyond the calculated intersection point, the selected line segment portions are extended appropriately, and the corresponding supplementary/vertical angle measurement is shown in the dynamics.
If the intersection point is off the map window, the command attempts to show the dynamics (that is, angle value and arc). The command honors the auto pan option so that by placing the mouse on the boundary of the active map window, you can adjust the map window extent to see the dynamics and calculated intersection point.
158
159
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 user-specified background data content provides context for each map windows 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
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
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.
162
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.
163
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.
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
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.
165
166
The following example shows the two separate controls in one GeoMedia active map window:
167
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 Birds Eye View capability, you must agree to and abide by the Microsoft Bing Maps licensing and pricing terms. To review these licensing and pricing terms 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#. Birds Eye View is not available to Public Sector customers within the U.S. and Canada. You should visit the Microsoft End Users Terms of Agreement http://www.microsoft.com/maps/assets/docs/terms.aspx Web site to make sure that you understand the terms of use for Bing Maps.
168
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.
169
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.
170
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 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.
171
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 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.
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
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.
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 user-selected graphic.
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
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.
176
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>.<file extension for the selected canvas>. 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.
177
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
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
181
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.
182
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.
2. On the Data Window Properties dialog box, type a new title in the Data window name field. 3. Click OK.
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.
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.
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
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
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.
186
You can paste the snapshot into any application that supports OLE, such as Word, MSPaint, or an HTML Web page.
187
188
SECTION 8
189
Coordinate Systems
When creating a feature class through the Feature Class Definition command, you select a coordinate system to be assigned to the primary geometry field of the feature class from the list of available warehouse coordinate systems. Upon starting this command, a coordinate system is pre-selected on the General tab of New/Edit/Copy - <FeatureClass> dialog box. For a new feature class, this is the inherent default coordinate system. For an existing feature class being edited or reviewed, this is the coordinate system assigned to the primary geometry field.
190
Key Attributes
Each feature class created from scratch or by copying must contain a key attribute and a primary, unique index value on that key. You can define multiple key fields (up to ten) for a feature class on the Attributes tab of the New/Edit/Copy - <FeatureClass> dialog box. Note that there can only be one attribute with data type autonumber. You set the key definition for the current or selected attribute row by clicking the Set Primary Key button on this tab. This button appears when you select an attribute row. When the selected attribute is already a part of the primary key, the button name changes to Unset Primary Key. Ordering of the attributes in defining the primary compound key is determined by the order in which they are defined. As you define new keys, they are added at the next available index. When a key is undefined, that key is removed, and all key indices below it are adjusted
191
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 Gmodifications GmodifiedTables INGRSQLOperatorsTable INGRFeatures INGRGeometryProperties INGRAttributeProperties 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
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.
This dialog box is resizable for better viewing of long query names.
193
3. On the General tab of the New - <FeatureClass> dialog box, type a name for the feature class. The feature class name must be unique within a warehouse. 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
OR To define a new coordinate system and assign it to the feature class, click New; then define the coordinate system on the Coordinate Systems Properties dialog box. 7. Click the Attributes tab on the New - <FeatureClass> dialog box, which contains a grid with a row for each attribute definition.
8. To define a unique primary key for the feature class, click in a cell in the Key column or select the row; then click on the Set Primary Key button or press the space bar. You can define multiple rows as key columns as described earlier in this section. 9. In the Name column, type attribute names. Each of these must be unique for the feature class.
195
11. Select a data type, and define its parameters at the bottom of the Attributes tab, which varies with the data type selected. The AutoNumber data type has no parameters for you to define. 12. Optional: You can assign default values for attributes as long as the value is not a function. Functional defaults are not supported in Feature Class Definition. 13. Optional: Type a brief description of the attribute in the Description cell of each attribute. 14. Click OK. 15. Note the new feature class on the Feature Class Definition dialog box, and close the dialog box.
Editing an existing Oracle feature class definition is an Oracle administrative task and is, therefore, not allowed in the GeoMedia Professional Feature Class Definition tool.
196
197
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
199
Additional Options
Below the Output settings grid on the Advanced tab, you have the following two options: Select Source Attributes-Opens the Attributes of <feature name> dialog box that lets you select a subset of fields. You can use this option if only one record is selected in the grid. Target Coordinate System-Opens a dialog box of the same name that lets you perform the following: 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
Running Output To Feature Classes creates the log file gmotts.log in your \Warehouses folder, if the file does not already exist, and appends log information to the contents of an existing log file. The command always deletes the existing log file and creates a new one for each run of the command.
2. On the General tab, select the appropriate items from the Source features to output treeview. 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
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.
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.
202
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.
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
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.
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 supports keyboard navigation. You can use the arrow keys to navigate among the items, and the space bar to select\unselect items. You use the CTRL and SHIFT keys in the conventional way to select and unselect groups of items in multi-select mode. When you move the cursor over a numbered button representing a feature in the map view, a tooltip appears showing the name of the feature class or query of the highlighted item. If the Add connection prefix to feature names check box is selected on the General tab of the Options dialog box, the feature class name is prefixed with the connection name. If a map window tooltip has been defined for the legend entry associated with the highlighted item, the text for the map window tooltip is displayed. For more information on map window tooltips, see the Defining Map Window ToolTips section in Working with Map Windows.
Inside Fence selects all features that fall completely within the fence. Overlap Fence selects all features that fall inside and are overlapped by the fence. Rectangular Fence (the default) selects all features that fall completely inside the rectangular fence. Polygonal Fence selects all features that fall completely inside the polygonal fence.
This selects all map objects in the map window associated with highlighted legend entries, regardless of whether objects are fitted in the map window. Legend entries must have the
205
This selects all features in the data window, whether they are visible in the data window or not.
206
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. 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. Verify that the Display query in map window box is checked, and change in the Map window name field, if appropriate, the map window in which to display the query results. OR To not display the query results in a map window, click the Display query in map window box to remove the checkmark. Optional: Click Style, and change the default style on the Select Style dialog box. Verify that the Display query in data window check box is selected, and change in the Data window name field, if appropriate, the data window in which to display the query results. OR To not display the nongraphic attributes of the query results in a data window, select the Display query in data window check box to remove the checkmark. Click OK to generate and to display the query results in the specified data window and/or map window.
4. 5.
6. 7.
8.
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 supports 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 supports all of these workflows. This section describes the tools and capabilities available to address these workflows. It begins with a description of specialized productivity tools that are common to multiple placement and edit commands.
207
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
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
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
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
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
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.
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
215
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
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.
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
218
219
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
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.
221
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
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 user-specified angle, depending on cursor location, relative to the last segment placed by digitizing in this mode. If the previous geometry is an arc, the previous segment is considered to be that tangent to the arc at the arc end point. By default, this is the active rotation mode, and the active angle is zero degrees. When you select this mode, the Place Point at Angle dockable control appears for you to type the specific angle value. (Shortcut key SHIFT+A)
If there is no previous geometry, the point is placed at a user-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
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.
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.
224
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.
2. Choose a point feature class to insert. Place at angle: 1. Set the rotation mode to Place at angle.
225
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
For example, in the By Center Point mode, a dashed line is shown dynamically from the center first point to the cursor location to represent the radius, and a circle is shown dynamically as you move the mouse cursor for placement of the second point. Likewise, the By Diameter mode shows the circle dynamically after you define the first point of the diameter as you move the mouse cursor for placement of the second point. In By 3 Points mode, a dashed triangle whose vertices represent the three points on the edge of the circle is shown dynamically once two points have been defined, as in the following figure: The CTRL-Click key combination may be used at the last step of any circle placement workflow to enable the placement of geometry collections. For example, if you want to place two disjointed circles as a geometry collection using the By Diameter mode, you would click to specify the first point of the diameter of the first circle in the geometry collection, and then you would use CTRL-Click to specify the second point of the diameter of the first circle. At this stage, you would click to specify the first point of the diameter of the second circle in the geometry collection, and then you would click to specify the second point of the diameter of the second circle in the geometry collection, at which time the geometry collection would be placed. However, you cannot use CTRL-click to place a circle as a hole within another circle; the capability of generating a hole inside a circle is currently not supported. This command supports coincidence, break, and properties settings. In addition, you can access the viewing commands while the command is active. The AutoPan setting is also honored, as are vector and raster snaps when moving the mouse cursor. You can undo/redo the insert circle operation with the Undo/Redo commands. Pressing BACKSPACE reverts the placement state to the previous step.
6. 7. 8. 9. 10.
227
228
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 k ey Y)
229
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
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
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
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 comm and. (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
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
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.
235
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).
236
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.
The next vertex is drawn in dynamics at a 90o angle to the selected vertex.
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
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.
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 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 user-selected feature. You can then use the Options toolbar Use Existing Geometry When Digitizing option (or the Use existing geometry when digitizing option on the Placement and Editing tab of the Options dialog box) to quickly use all or part of the temporary feature to create a new feature. Offset mode remains on until you turn it off, at which point the temporary feature is deleted. While offset mode is on, all the SmartSnap tools and all the placement and editing options are available for use with the temporary feature.
238
5. Type the offset value in the dockable control. 6. Select the feature to offset from (Line A in the example).
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.
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.
239
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.
Figure 1
Figure 2
240
241
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.
242
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 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
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 user-specified distance along a feature. Place the next point at the user-specified distance and direction from a known location.
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
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.
GeoMedia Professional supports the placement of these features - called composite features by allowing you to switch between placement modes when you are digitizing individual features.
245
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
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.
Using this tool ensures that attribute information is always entered when new features are created.
247
248
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.
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 <Feature> Properties dialog box; then click OK. If Display Properties dialog for new features is off, all potential area features are highlighted in the highlight color.
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
3. Click the drop-down arrow to display the list of feature classes, queries, reference features, and categories in the read-write warehouses to which you are connected. 4. Click the feature class in which you want to create area features. 5. To include holes, select Include holes. 6. Pause the cursor over each closed region of linework.
For each closed region over which you pause, the new feature is highlighted.
7. Click to accept the feature.
If Display Properties dialog for new features is on, or if input is required for the selected feature class, specify the feature attributes on the <Feature> Properties dialog box; then click OK. If Display Properties dialog for new features is off, the feature is written to the database immediately after you click to accept. The following message is displayed: Writing area feature to database.
8. Continue until all area features have been created.
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
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
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.
252
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
You can type or select the text string you want to search for in the Text field. Note that the search is not based on a case-sensitive text string. Checking the Match entire text check box selects those graphic text features with their text having an exact match with the string value entered in the Text field. Checking the Use wildcards check box lets you use any of the listed special characters entered in the Text field as wildcards and perform pattern matching using both regular characters and wildcard characters as specified in the Text field. Regular characters must exactly match the characters specified in the character string. Wildcard characters, however, can be matched with arbitrary fragments of the character string based on the wildcard character used. This command supports the following GeoMedia-recognized wildcards only: % Any string of zero or more _ (underscore) Any single character
254
Redigitizing Text
Redigitize Text lets you redigitize a single text point geometry or curved text, that is, a composite text collection, while retaining its identity and attributes. Curved text is represented as an ordered collection of text point geometries in which each text point geometry represents a single character placed at a different location and possibly with a different orientation. Two text collection types exist: text placed along an arc where each character is a component of the collection, and text labeling multiple geometry in a collection such as the islands of Hawaii where each island name is a text component. This command lets you perform textual editing of such a curved text representation. For example, the textual editing may change the number of characters in the curved text as the result of the addition or deletion of text characters. Or it is possible that an individual text character has been moved or spun. The resulting geometry curvature of such curved text may either lose the display fidelity or may not properly undulate with the shape of the geometry for which it was initially placed. This command supports resolving these problems by letting you redefine geometry curvature and location using an existing geometry or a user-defined arc. Redigitize Text distributes each character in the text string so as to undulate along the geometry, orienting each character as required. This command honors the alignment of the input text string. However, for better display, the resulting text string is always center horizontal aligned by allowing all three vertical alignments (Top, Center, Bottom) when the resulting output is a composite text collection. For example an input text string with Top left or Top right alignment is converted to Top center after redigitizing. This command deals only with the location, curvature, and inter-character spacing of the selected text geometry, and it does not support redigitizing a multi-line text. You can 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
The following table describes the type of resultant text geometry for different types of input geometries: Input Single-unit text. (Single text point geometry) Output Composite text collection, or single-unit text Remarks 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.
256
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.
257
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.
258
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.
259
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
You can copy and move categories/sub-categories, feature classes, and queries to other categories by using drag-and-drop. You cannot, however, drop feature classes and queries on the root node Categories nor drag-and-drop this node. Drag-and-drop works similarly to Windows Explorer's folders treeview. While drag-and-drop is being done, if you press Ctrl, a copy is performed; otherwise, a move operation is performed. Tooltips on the treeview show the original feature class name (with or without the connection name, per the Options > General tab setting Add connection prefix to feature names) or query name. Once defined, the category structure appears in treeviews across the product by the commands, for example Attribute Queries and Join, and controls to support categories. Categories are thus displayed in the treeviews along with all the connections, queries, and reference features information, for example, in the New Data Window and Add Legend Features dialog boxes. If, however, categories have not been defined, no empty Categories node is displayed by other commands.
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 <feature name> dialog box, which lets you choose, reorder, and rename attributes for the selected feature class or query. Selecting a feature class or query in the Categories treeview and clicking Properties displays the Properties of <feature name> dialog box, which lets you review and change properties for both feature classes and queries. You can review the read-only original name and description (as
262
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.
263
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
8. Expand the appropriate feature class and/or query node(s); then check the appropriate feature class and/or query check boxes.
265
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
267
268
SECTION 9
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
Catalog Features
Standards-compliantGeoMedia Catalog makes it easy for anyone, regardless of prior knowledge of the Federal Geographic Data Committee (FGDC) standard, to create, manage, and publish FGDC-compliant metadata. Catalog also supports import and publication of metadata records that conform to the ISO-19139 technical specification. Biological Data ProfileCreate standardized metadata for your biological datasets following the FGDCs Biological Data Profile. Data Layer AssociationCatalog ties metadata to data by allowing you to associate a metadata record with the GeoMedia feature class or image file that it describes. Metadata CaptureOnce you have associated a catalog record with a dataset, you can extract metadata elements like bounding coordinates and attributes, directly from the dataset into the metadata record. Catalog ExplorerBridges the gap between spatial data and metadata catalogs to provide an unprecedented level of access to and control over your GIS data library. With the Catalog Explorer, you can quickly locate and preview any dataset in your GIS data library, and you can automatically load search results into a GeoMedia map window. Browse GraphicsInclude images of datasets in your Catalog reports. Online Help with Real-world Metadata SamplesContext-sensitive online Help provides FGDC definitions and real-world metadata samples. Metadata TemplatesLoad 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 ExportLoad 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 publishingOutput 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
Geospatial metadata has been compared to the nutrition label on a food package. Without this label, you cannot be sure whether the food you are eating is good for you. Without metadata, you do not know if the data you are considering using is good for your intended use. See the GeoSpatial Metadata Profile: FGDC Dataset document (FGDCDatasetMetadataProfile.pdf in <HOME>\Program Files\GeoMedia Professional or \GeoMedia).
271
272
273
274
275
OR
276
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 ODBC, type the username and password in the SQL or Oracle dialog boxes that are displayed, and then the connection is made.
TypeCatalog connection type, Access or ODBC. CatalogLocation 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
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.
278
5. Change the location of the .mdb file for an Access database or the data source name for an Oracle or SQL Server database.
279
280
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 password in this process in the case of ODBC catalog. If the connection cannot be opened in Read-Write mode, a message is displayed because the import cannot be done on the Read-Only/Closed connection.
281
282
Publish using style sheet Sections to includeLets you select which FGDC metadata sections to export. Options: Rollup empty fieldsLets you exclude all the empty metadata elements. Include biological profileLets you include the metadata content belonging to biological profiles. Include map displayLets you include a map display of the record. This option is not applicable if the selected record is nongraphic. Publish using style sheet, displayed only for the XML (FGDC) and XML (ISO) 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
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
(The following example is the Advanced tab for the XML (ISO) export format.)
If the style sheet you want to use is available on your network, browse to its location, and select the XSL file you want to use. Click Open and OK. Until you change this selection, Catalog will publish all XML (ISO) metadata records with a link to this style sheet. Some users map network drives to their machines with the possibility of remapping in the future. If this applies to you, you may want to use a UNC pathname, for example, \\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
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.
XSL editors can also eliminate the GeoMedia graphic displayed at the top-left corner of XML metadata reports, or replace it with the graphic identity of the enterprise graphic, by editing any of the style sheets delivered with GeoMedia Catalog. The four XSL files supplied with Catalog use the following graphic: <HOME>\StyleSheets\tech_geomedia.gif as the graphic file that displays by default. XSL editors can create a graphic file of similar size, located in any convenient pathname.
286
287
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
OR For an image file, select the appropriate connection and image file to which the catalog record needs to be associated; then click OK.
289
The width of the Catalog record field expands to fit the largest item in the list. 3. Type the Title of the new record. Go to Step 7. OR Type the Title of an existing record. Continue with Step 4. 4. Check the Create from check box. 5. Select the appropriate entry from the Catalog record drop-down list. 6. Check the appropriate Sections to include check boxes for the FGDC sections whose contents are to be copied from the existing catalog record into the new one. 7. Click OK.
The new catalog record is created with the user-specified title in the selected catalog, and the newly added catalog record is displayed in the Available catalog records treeview under the relevant catalog. To capture information:
1. Select Tools > Catalogs > Associate Catalog Records. 2. Select the appropriate catalog connection to display the treeview of Available catalog records. 3. Select the appropriate catalog record. 4. Click Capture.
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
Exploring Catalogs
Catalog Explorer provides a functional and practical means for you to manage your data and metadata. This command provides a powerful tool for quickly locating and previewing datasets in your GIS data library. You can browse catalog records from multiple catalogs and locate datasets according to metadata keywords, attributes, time period, or geographic area. To use this command, at least one catalog connection must exist in the GeoWorkspace. When you select a catalog connection, the catalog will be opened if it is not already open, that is, the catalog connection is opened on-demand by the command but not during the GeoWorkspace load. You must supply a password to establish a connection to the catalog if it is required. With this command, you can view a list of open catalogs and the catalog records that they contain. You can then select one of the catalog records in the Windows Explorer-style tree view, and view the important metadata content, as follows: Title and the contact persons for the metadata and the dataset Preview of the map if the catalog record is associated to a feature class Basic description Important spatial metadata content You can define specific criteria for searching within open catalogs, and you can clear and redefine a search. This search criteria for the selection of catalog records include the following: Contains any or none of the listed keywords Contains any of the listed attributes Corresponds to the time period of content 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
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
294
295
Spatial tabDisplays a map preview of the associated feature class of the selected catalog record. A catalog record can have two feature classes associated to it, one to display the foreground layer and one to display the background layer. The map control is disabled if either of the following two conditions exists: The metadata has no associated feature class for the foreground layer. 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 MapDisplay map or data, if available. Zoom InZoom in on features. Zoom OutZoom out from features. PanPan map features. Full ExtentDisplay full extent (fit all) of the map.
296
The projection of the displayed map is always predefined as geographic, and the symbology is also predefined and hard coded.
297
Search tabContains two subtabs, Text/Data Criteria and Spatial Criteria, that let you enter search criteria to search for metadata. You can search on the following criteria: Keywords Attributes Time period 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
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
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
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.
301
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
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 <HOME> in the remainder of this section. GeoMedia software components will be delivered to the folder <HOME>\Program. GeoMedia Catalog functions require the delivery of database(s), style sheet(s), and other files that will be located in the structure detailed in the following table. Catalog Components Delivery Table Files/Folders CatalogTemplate.mdb Catalog_Samples.mdb World.mdb Description Location
Template access Catalog required for <HOME>\Templates\Catalogs the New Catalog command. Sample Catalog required for the New <Drive>:\Warehouses\Catalogs Catalog Connection command. GeoMedia warehouse used in the Catalog Explorer command as the default search map. <Drive>:\Warehouses
Oracle Scripts
Template scripts required for creating <Home>\Program Oracle catalogs. Template scripts required for creating <Home>\Program SQL Server catalogs. Style sheets used to View a Catalog <HOME>\StyleSheets\Catalogs Record, and to publish record(s) using the Export Catalog Records command. Default graphic file displayed by XML <HOME>\StyleSheets\Catalogs style sheets. <HOME>\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.
SQLServer Scripts FGDC_classic.xsl, FGDC_FAQ.xsl, ISO_Stylesheet1.xsl, View_Details.xsl tech_geomedia.gif FGDC_to_ISO.xslt, FGDC Dataset Metadata Profile.pdf
304
SECTION 10
Registering Data
GeoMedia Professional provides you with easy-to-use tools to capture new data. These tools reduce the number of steps required to accomplish every task. With integrated vector and raster snaps, you can capture vector data from raster images with accurate heads-up digitizing. This product also allows table-top digitizing and vector transformation for existing vector data that requires geometry transformation to match your database. This chapter deals with tools that provide data registration: Digitizer Setup, Image Registration, Output to GeoTIFF, and Vector Registration. These tools follow a similar source-and-target data collection workflow with a similar graphic interface. See SmartSnap in the Working with Features section.
Supported Digitizers
GeoMedia Professional only supports 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 contact 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 support site. To avoid the most common digitizer problems, verify that you install the latest available Wintab32 driver and perform the installation according to the tablet vendors instructions.
305
Registering Data
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
Registering 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. 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 Register to save and to apply the digitizer setup. Verify 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.
307
Registering 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 Register to save and to apply the digitizer setup. 12. Verify that the setup was successful with the name appearing in the list on the Registrations dialog box.
308
Registering 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.
309
Registering Data
Button Number 0 1 2 3 (if present) Recommended Wintab32 Mapping Left Click Left Double Click Left Drag 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.
310
Registering Data
Registering Images
Image Registration allows you to register a selected image by creating a new registration or applying an existing registration. Creating a new image registration involves registering an image to its real-world coordinates, that is, transforming raster points to map control points. You can enter these points in any order and can collect them by placing data points or by precision keyins. This tool also allows you to re-register a selected image by editing the registration originally used to register the image. In the process of creating or editing image registration, you create or edit the control-point pairs. This tool is different from Digitizer Setup and Vector Registration in that it changes the display matrix of the image but does not change the data itself. In addition, this tool allows you to report on and to delete previously saved image registrations. Image Registration currently uses only the Affine transformation model. To create a new image registration, a single image must be in the select set before you select Image Registration. You must select an image to re-register it, and you must register it manually with the Register button; the tool does not do it automatically. After you collect all of your control points, you need to check their accuracy with the RMS (Root Mean Square) value on the New Digitizer Setup dialog box. The RMS value is a measure of the fit of the transformed source points as a whole for the whole set of control points whenever the number of control points meets or exceeds the minimum number for the transformation. If the RMS error is too high, you need to experiment with the Control/Check toggle of the Type column on the suspect pairs. A control-point pair of the type Control is used in the registration calculation and contributes to the overall RMS error value. A control-point pair of the type Check is saved, but not used in the registration or RMS value calculation. Once you have found the inaccurate control point, you can either modify or delete it. Click Edit Source or Edit Target to edit the respective control points by selecting a row and clicking on a new location for the control point. 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.
311
Registering 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 Register to register the image. OR Click Save to save the registration without registering the image.
312
Registering Data
4. Click Edit.
5. Make the required changes in the registration. 6. Click Register to re-register the image.
Outputting to GeoTIFF
Output to GeoTIFF takes a selected TIFF image and writes it out to a new GeoTIFF image file containing geographic header information. The selected TIFF image is assumed to display in the correct location. The image could have been inserted with Insert Interactive Image and registered with Image Registration, or it could have been placed using the Insert Georeferenced Images command. The output header information (also called GeoTIFF tags) in the GeoTIFF file allows the image to be inserted in another GeoWorkspace in the correct geographic location automatically with Insert Georeferenced Images or to be used in other software packages that accept GeoTIFF-formatted image files.
313
Registering 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 support GeoTIFF placement, it can use the world file. A world file is simply the six necessary components of an Affine matrix that define the mapping from pixel to world coordinates. Unlike the GeoTIFF tags, the world file does not include any coordinate system information. Output to GeoTIFF can write out to only certain projections and datums of coordinate systems. Insert Georeferenced Images can, however, read almost any data that is correctly defined within the GeoTIFF specifications. You can use GeoMedia and GeoMedia Professional to insert any GeoTIFF image with Insert Georeferenced Images. You can use GeoMedia Professional to output some TIFF images as GeoTIFF images as long as the coordinate system is one of those supported by Output to GeoTIFF. See the Coordinate System Information appendix for a list of s upported coordinate systems for writing GeoTIFF files.
To output to GeoTIFF:
1. To insert a TIFF image without any existing GeoTIFF tags, select either Insert > Interactive Image (Continue with Step 2.). OR Select Insert > Georeferenced Images (Go to Step 3.). 2. Register the image with Image Registration to the correct geographic location. 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.
314
Registering 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 verify 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 registered. 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 registering vector data: 1. Input the features to be transformed and the features for identifying the target transformation location. 2. Specify the transformation parameters. 3. Identify the source and destination control points. 4. Review the transformation, and make corrections if necessary. 5. Perform the actual transformation.
To create a new vector registration and to register source vector data for review and output feature:
1. Connect to an appropriate source warehouse. 2. Open a source map view, and display the source features you want to transform in the source map view. 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
Registering Data
7. Click New.
8. Click Add Points; then follow the prompts to register the source features against the target features by choosing corresponding control-point pairs. 9. Check the residual errors, and make corrections if necessary. 10. Click Transform.
11. Select the correct source feature class from the Transform features in drop-down list. 12. Verify that the Output as option is set to Review. 13. Optional: Click Style to open the Style Definition dialog box and customize your display; then click OK. 14. Select the appropriate map window from the Map window name drop-down list to display the source features and target features in a map view. 15. Click Apply on the Vector Transformation dialog box to review the transformation. 16. Visually check the placement of the transformed feature against the base feature display. 17. If the transformation is not acceptable, edit the transformation control points, repeat the process, and again check the results. OR If the transformation is acceptable, press ESC to return the Vector Transformation dialog box; then select the Feature class output option. 18. Select the appropriate connection from the Connection drop-down list.
316
Registering 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.
317
Registering Data
318
SECTION 11
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.
319
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)
320
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 features 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
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."
322
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 using Update 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 Byte Currency Date Double Integer Long Memo Single 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
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
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.
325
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
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.
327
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
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.
329
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
If the features are not adjacent, merging the features creates a single feature with discontiguous geometry.
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 commands dockable control.
You can also use construction aids to construct the points for digitizing the split geometry.
331
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.
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
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 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.
333
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.
AOriginal feature, containing a homogeneous geometry collection of four discontiguous area geometries. BOriginal feature geometry with a split polygon shown, specifying the desired partitioning of the geometries. CResult of the split operation. The shaded areas represent a geometry collection belonging to the new feature created by the split (portions of the original geometry that were external to the split polygon). The cross-hatched areas are the geometry collection now associated with the original feature (portions of original geometry that were internal to the split polygon).
334
To complete the split you simply click to split the geometry at the highlighted point.
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
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
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.
337
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 GeoMedia Professional User's Guide
The feature selection control is not populated with the feature class of the selected feature.
9. Click to place the feature.
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.
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
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 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.
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
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.
342
5. Repeat Steps 3 and 4 until the appropriate edits have been made.
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.
343
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.
344
4. Press CTRL+a.
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
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.
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
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 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 supports 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 joining the cursor and the base point with respect to the current orientation of the feature.
348
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 joining the cursor and the base point with respect to the positive X-axis or by exact key-in on the control. The following figures show the result of the spin with the absolute angle specification:
The geometry is oriented at 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.
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
5. Click to accept the angle. OR Type the appropriate value in the Angle field.
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.
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
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.
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
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 supports stream digitizing by holding down the left mouse button and dragging the mouse. This command, like Insert Feature and many other placement and editing commands, honors the settings on the Options dialog box (Tools > Options) for existing geometry, automatically breaking features, and maintaining coincidence. Redigitize Geometry uses the height value you specify for new points in the Default height value field of the Placement and Editing tab. Finally, you can digitize in stream mode by holding down the left mouse button.
The snap glyph is displayed, and the geometry is highlighted between the start and end points.
5. Place the end point. (a = highlight color, of what will be placed; b = select color)
The section of geometry between the start and end points is deleted, and the line feature is displayed in dynamics from the start point.
6. Place the next point. 7. Double click to end.
352
The snap glyph is displayed, and the geometry is highlighted between the start and end points.
5. Press the TAB key.
The section of geometry between the start and end points is deleted, and the area feature is displayed in dynamics from the start point to the end point.
7. Click to place the next point.
The feature is displayed in dynamics from the start point to the end point.
353
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.
The portion of the selected feature delineated by the start and end points is deleted, and the command is exited automatically. 354 GeoMedia Professional User's Guide
355
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
357
358
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
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: DeleteDeletes 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. ReverseChanges 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 bottomReorder 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
Enabling Conditions Delete (geometry) Constituent geometry of a supported geometry type is selected on the dialog box.
Supported Geometry Types Geometry collection Boundary geometry holes collection Standard text collection Nested text collection
Special Rules If the edited geometry may result in a conversion to a simpler geometry, single member collections and zero member holes collections (that is, boundary converted to polygon or composite polygon) are converted.
Delete (vertex)
A vertex from a supported geometry type is selected on the dialog box, if standalone or part of a geometry collection
Polyline Polygon Boundary Composite polyline Composite polygon Line Arc Polyline Composite polyline Geometry collection Boundary geometry holes collection Standard text collection Nested text collection
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 members the composite, this command is disabled. Order of the vertices is reversed. N/A
Reverse
One of the supported geometry types is selected on the dialog box, if standalone or part of a geometry collection. Constituent geometry of a supported geometry type is selected on the dialog box.
Move
N/A
361
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
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.
Loop
363
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
Overlapping Holes
Invalid Geometry Type Empty Geometry Collection Too Few Vertices Unknown Geometry Type Invalid Coordinates
Actual geometry stored in a GDO field that does not match the GDO type/subtype definition. Geometry collection contains zero geometries.
Polygon geometries contain fewer than four vertices; polyline geometries contain fewer than two vertices. Binary format cannot be converted into a geometry object.
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
3. Select the feature class or query for which to validate geometry from the Validate geometry contained in drop-down list. 4. Verify, and change if appropriate, the default name <Feature> anomalies assigned to the output record set in the Query name field. 5. Optional: Type a query description in the Description field. 6. Verify that the Display results in map window box is checked in the Map window name area, and change, if appropriate, the default active map window in which to display the results. OR To not display the results in a map window, click the Display results in map window box to remove the checkmark. 7. Optional: Click Style, and change the default style on the Select Style dialog box. 8. Verify that the Display results in data window box is checked in the Data window name area, and change, if appropriate, the default new data window in which to display the results. OR To not display the results in a data window, click the Display results in data window box to remove the checkmark. 9. Click OK to perform geometry validation.
Validation processing is performed in the selected feature class or query, and an output query is produced with the query name from the dialog box.
If the map window display check box was selected, the map window with the anomalies is displayed. If the data window display check box was selected, the data window with the
365
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 <query name> and a progress bar are displayed as the geometry problems are automatically fixed; then a message is displayed with statistics on the number of problems fixed per selected option.
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 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 Node mismatches Non-coincident intersecting geometry Overshoots Unbroken 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
Overshoot
(Intersection not broken, intersection not coincident. If all these switches are on, overshoot takes precedence.)
Undershoot
Node Mismatch
Nearly Coincident
Nearly Coincident
Intersection Not Broken (This takes precedence over intersection not coincident.)
Overshoot
Undershoot
369
Node Mismatch
Nearly Coincident
Nearly Coincident
Node Mismatch
Nearly Coincident
Nearly Coincident
Nearly Coincident
370
Nearly Coincident
Nearly Coincident
371
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. Verify, and change if necessary, the default query name for the output query in the Query name field. 8. Optional: Type a query description in the Description field. 9. Verify that the Display results in map window check box is checked in the Map window name field, and change, if appropriate, the map window in which to display the results. OR To not display the results in a map window, uncheck the Display results in map window check box. 10. Optional: Click Style, and change the default style on the Style Definition dialog box.
372
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 Extending undershoots Breaking crossing lines 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
Line A is broken into two segments, A and C, at the intersection of Line B. Insert Vertex into Crossing Lines
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
The message Fixing <query name> and a progress bar are displayed as the connectivity problems are automatically fixed; then a message is displayed with statistics on the number of problems fixed per selected option.
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 supports the extension of lines (converts to polyline), polylines, composite polylines, and arcs. When an arc is extended, the sweep angle of the arc is increased as the cursor is moved, up to the maximum sweep angle. Geometry collections are also supported. Extend honors the coincident settings, properties, and break settings on the Placement and Editing tab of the Options dialog box. It also honors auto pan and on-element snapping when extending, and you can undo/redo the results of an extend operation with the Undo/Redo commands.
To extend geometry:
1. Connect to a read-write warehouse. 2. Select Edit > Geometry > Extend.
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.
376
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.
If you place the cursor on a linear feature that has no close features in both directions, the figure does not highlight.
377
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.
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
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
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 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
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.
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.
381
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: Break all feature classes Yes No Break same feature class only Action Yes Yes Vertex is placed on all features at the intersection point. All features are broken at the intersection point.
382
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.
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
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.
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
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 supports the construction of a fillet between two line segments that can be lines, polylines, composite polylines, polygons, composite polygons, and geometry collections. In the cases of polygons or composite polygons, if you choose to trim the excess, and the two line segments that you select to construct the circular fillet cannot be trimmed in the context of polygons or composite polygons (for example, the two line segments are contained in different polygons), the fillet is inserted as a standalone feature, and the original selected feature(s) is not trimmed. The selected two segments can be on the same feature instance. In this case, if you choose to trim the excess, the constructed fillet merges with the selected trimmed segments into the same feature instance, and no new feature instance is generated. However, if you choose to not trim the excess, a new standalone feature instance is inserted for the constructed fillet. You can select the feature class for the new segment. In addition, this command supports the following functionality: 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
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
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 verify 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
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
389
390
SECTION 13
391
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 passed 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
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 support of formatted data entry (that is, as validated in the data window, feature properties, and so forth), and it is then added with any necessary delimiters and with formatting compatible with the SQL dialect of the AttributeFilterPipe or the GDO server being queried (See table below). When you type a value for such an attribute in the Filter field, it is interpreted as a literal and is not reformatted. When you 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 supported by the Filter dialog box.
393
User-defined format User-defined (Yes/No, etc., format (Date, custom) Time, Date/Time)
Standard format, delimit with single quotes, replace embedded single quotes with consecutive single quotes
If user-defined format is Date, keyword DATE followed by date value expressed as YYYY-MM-DD, delimited by single quotes. If user-defined format is Time, keyword TIME followed by time value expressed as HH:MM:SS, delimited by single quotes. If user-defined format is Date/Time, keyword TIMESTAMP 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 user-defined format is Date, date value expressed as MM/DD/YYYY, delimited by pound signs. If user-defined format is Time, time value expressed as HH:MM:SS, delimited by pound signs. If user-defined format is Date/Time, date/time value expressed as MM/DD/YYYY HH:MM:SS, delimited by pound signs. ArcInfo GDO server SQL ArcView GDO server SQL MapInfo GDO server SQL See Attribute Filter Pipe. See Attribute Filter Pipe. See Attribute Filter Pipe. See Attribute Filter See Attribute Filter Pipe. Pipe. See Attribute Filter See Attribute Filter Pipe. Pipe. See Attribute Filter See Attribute Filter Pipe. Pipe. See Attribute Filter See Attribute Filter Pipe. Pipe. See Attribute Filter Not supported Pipe. See Attribute Filter Pipe. See Attribute Filter Pipe. See Attribute Filter Pipe. See Attribute Filter Pipe. See note below.
CAD GDO server See Attribute Filter SQL Pipe. FRAMME GDO server SQL See Attribute Filter Pipe.
Date value expressed as MM/DD/YY, delimited by single quotes; time values are not supported. MGE GDO server SQL See Attribute Filter Pipe See Attribute Filter TBD - See note Pipe below. See ODBC Tabular GDO server.
394
Keyword TIMESTAMP followed by date/time value expressed as YYYY-MM-DD:HH:MM:SS, delimited by single quotes. Oracle Relational GDO server SQL See Attribute Filter Pipe. See Attribute Filter See Attribute Filter Pipe. Pipe. See Attribute Filter See Attribute Filter Pipe. Pipe. See Attribute Filter See Attribute Filter Pipe. Pipe. See Attribute Filter Pipe. See Attribute Filter Pipe. See note below.
Oracle Object See Attribute Filter GDO server SQL Pipe. ODBC Tabular See Attribute Filter GDO server SQL Pipe.
For an ODBC Tabular GDO server, the ODBC escape sequence is used. The entire escape sequence is enclosed in braces with an identifier for the type of expression (that is, keyword), followed by the expression: { type expression }. If user-defined format is Date, the expression is defined by the keyword d followed by date value expressed as YYYY-MM-DD, delimited by single quotes. If user-defined format is Time, the expression is defined by the keyword t followed by time value expressed as HH:MM:SS, delimited by single quotes. If user-defined format is Date/Time, the expression is defined by the keyword 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 user-defined format is Date, the date value is expressed as YYYY-MM-DD, delimited by single quotes. If user-defined format is Time, the time value is expressed as HH:MM:SS, delimited by single quotes. If user-defined format is Date/Time, the date/time value is expressed as YYYY-MM-DD HH:MM:SS, delimited by single quotes.
395
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. Verify that the SQL statement in the Filter box is correct; then click OK. For date and time queriesand possibly otherson MGE and MGDM connections, you may have to manually edit the SQL text on the Filter dialog box to issue a successful query. This is due to the varying SQL dialects of the various available ODBC drivers. 10. On the Attribute Query dialog box, accept or override the default query name, and optionally type a query description. 11. Verify that the Display query in map window check box is selected, and change in the Map window name field, if appropriate, the map window in which to display the query results. OR To not display the query results in a map window, uncheck the Display query in map window check box. 12. Optional: Click Style, and change the default style on the Select Style dialog box.
396
The query is displayed in accordance with the query options you set.
See the ODBC documentation for instructions.
Contain returns features that surround defined features. Contained features can touch but not overlap the borders of the surrounding features. Points cannot contain other features. contain with the Not qualifier
Are contained by returns features that fall completely within the defined features. Contained features can touch but not overlap the borders of the surrounding features.
397
Entirely contain returns features that surround defined features. Contained features cannot touch or overlap the borders of the surrounding features. Points cannot entirely contain other features. entirely contain with the Not qualifier
Are entirely contained by returns features that fall completely within the defined features. Contained features cannot touch or overlap the borders of the surrounding features. are entirely contained by with the Not qualifier
Overlap returns features that overlap the defined features. overlap with the Not qualifier
Meet returns features that fall next to the defined features, touching without overlapping. meet with the Not qualifier
Are spatially equal returns features that occupy the same space and location. Features must be of the same type to be spatially equal. are spatially equal with the Not qualifier
Are within distance of returns features having any part located within the specified distance of the defined features. If either the starting or ending point of a linear feature, for example, falls within the specified distance, it is returned.
398
The spatial operators used by Spatial Query are different from the Oracle Spatial Cartridge specific operators used by the Native Query command when querying an Oracle warehouse.
2. From the Select features in drop-down list, select a feature class or query. 3. Optional: To create a combined query, define an attribute filter for either or both feature classes or queries. Click Filter to display the Filter dialog box; then define the appropriate attribute filter. 4. Accept the default spatial operator for the that clause or override it by selecting another operator from the That drop-down list. 5. Accept or override the default not qualifier by checking or unchecking the Not check box. 6. If you selected the are within distance of operator in Step 5, type the zoning distance in the Distance field, and select the appropriate units from the Units drop-down list. 7. Select the second feature class or query from the Features in drop-down list. 8. Optional: Define an attribute filter as described in Step 4. 9. Accept or override the default query name, and optionally type a query description. 10. Verify that the Display query in map window check box is selected, and change in the Map window name field, if appropriate, the map window in which to display the query results. OR
399
The query is displayed in accordance with the query options you set.
In addition, you can set the style for the map window for optimum display results. One can think of this command as producing results that are the opposite of those produced by Spatial Difference as shown in the following two figures from the delivered Madison County, Alabama sample data set. 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
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
2. Select the first feature class from the top Features in drop-down list. 3. Optional: Click Filter to define an attribute filter for the selected feature class on the attribute filter dialog box. 4. Optional: Change the default spatial operator in the That drop-down list; then verify the operator in the illustration below the operator field. 5. Select the second feature class from the bottom Features in drop-down list. 6. Optional: Click Filter to define an attribute filter for the selected feature class on the attribute filter dialog box. 7. Optional: Change the default value in the Query name field. 8. Optional: Type a query description in the Description field. 9. Verify that the Display intersection in map window check box is selected, and change in the Map window name field, if appropriate, the default active map window in which to display the new spatial intersection. OR To not display the new spatial intersection in a map window, uncheck the Display intersection in map window check box. 10. Optional: Click Style, and change the default style on the Select Style dialog box. 11. Verify that the Display intersection in data window box is checked, and change in the Data window name field, if appropriate, the default new data window in which to display the new spatial intersection. OR To not display the nongraphic attributes of the new spatial intersection in a data window, uncheck the Display intersection in data window check box. 12. Click OK to generate and to display the new spatial intersection in the specified map window and/or data window. 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
The following cases are valid: From-feature area line line point point point Subtract-feature area area line area line point Result area or nothing line or nothing line or nothing point or nothing point or nothing point or nothing
The following cases are not allowed as input: From-feature area area line Subtract-feature line point point
One can think of this command as producing results that are the opposite of those produced by Spatial Intersection. Or, one can think of a cookie-cutter process, with the results being the sheet of dough from which the cookies have been cut out, as shown in the following example from the delivered Madison County, Alabama, sample dataset:
403
Spatial Difference results showing the difference of Major Water Polygons features and the Parks features. The difference is shaded gray.
404
405
Overlap Boundary Disjoint-The interior of one object intersects the boundary and interior of the other object, but the two do not intersect. This relation occurs, for example, when a line originates outside a polygon and ends inside that polygon. Overlap Boundary Intersect-The boundaries and interiors of the two objects intersect. Equal-The two objects have the same boundary and interior.
Contains-The interior and boundary of one object are completely contained in the interior of the other. Inside-The opposite of Contains. A Inside B implies B Contains A. Covers-The interior of one object is completely contained in the interior of the other, and their boundaries intersect. Covered By-The opposite of Covers. A Covered By B implies B Covers A. Any Interact-The objects are non-disjoint. 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
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. Verify that the Display query in map window check box is selected, and change in the Map window name field, if appropriate, the default active map window in which to display the query results. OR To not display the query results in a map window, select the Display query in map window check box to remove the checkmark. 11. Optional: Click Style, and change the default style on the Select Style dialog box.
407
408
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. Verify that the Display query in map window check box is selected, and change in the Map window name field, if appropriate, the default active map window in which to display the query results. OR To not display the query results in a map window, select the Display query in map window check box to remove the checkmark. 10. Optional: Click Style, and change the default style on the Select Style dialog box.
409
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.
410
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.
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 Or, use the following procedure: 1. Select Analysis > Queries. Nongraphic Point Graphics Text Unknown, graphic type cannot be determined Invalid, query cannot be opened
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
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 Join 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, Join, Label, Native Query, Spatial Difference, Spatial Intersection, and Spatial Query. This dialog box also varies if the query was created with Spatial Query in GeoMedia Professional version 4.0 and earlier or in GeoMedia Professional version 4.0 Service Pack 1. See GeoMedia Professional Help for more information. 3. Edit the items available for the specific selected query. For example you can edit the query name or description, or click Filter to edit the attribute filter for an attribute-filter query.
413
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.
414
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.
415
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)
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
417
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 supports multiple selection.
The filter geometry is created, the dialog box is dismissed, and filtering is performed. Merged geometry of the selected features is displayed in the active map window. To define a spatial filter by select set:
1. Create a select set of the features needed for your workflow. 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
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.
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
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
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.
Remove Filter
Remove Filter (No Active Filter) simply removes the existing active named spatial filter with a single click. The active filter can be a user-named filter or a system-defined filter.
421
This dialog box displays the currently active spatial filter name in the Active filter field, in the same manner as the dockable control. This field is always enabled, locked, and grayed to indicate it is read-only. Also displayed are the names of all the GeoWorkspace spatial filters, except the active filter, in the Named filters list. The default spatial filter name is SpatialFilter<n>, where n is a number determined at runtime to guarantee uniqueness. You can select a filter from this list to perform filtering with the geometry and spatial operator of the selected item by clicking Apply or double clicking on the item, and the filter definitions of the selected items are displayed on the active map window. The Filter by geometry extent and Spatial operator settings on the Spatial Filter Options dialog box are ignored. You can change the name of a filter by selecting it from the list, clicking Name, and then typing a new name on the Name dialog box. The Name button, however, is only enabled if there is an active spatial filter that is not a user-named spatial filter. Thus, only 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.
422
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.
423
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
425
426
427
Immediately after you make a selection, by default the first item of the sequence is displayed in the active Queued Edit Map Window and the active Queued Edit Data Window (if displayed). However, if the selected queue has previously been active during the session, the previously active item is remembered. After displaying the first item you can perform the following management tasks: Navigate through the subsequent items Sort the items Delete queue items by status Create subqueues Set options for viewing the items Track the status of queue items Delete queues Show queue statistics
Access additional options and commands to manipulate the standard review items and queues
428
The item graphics are displayed to the Queued Edit Map Window by placing each item geometry in the Queued Edit Map Window legend. On initial creation, there is one legend entry per geometry field identified, but you can add other feature classes or queries to this legend. You can also change the order of item legend entries and style, and the modified order and style is maintained upon a move next, move previous, move first, or move last action in the sequence. To customize the map, you can set options for defining an item locator and for viewing the map window display on the Queuing Options dialog box, which is accessed by clicking the Options button on the control.
The Zoom In/Out and Fit current queue item buttons on the dockable control let you control the map window view. They make use of the values on the View tab in the Zoom factor field and the
429
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%.
430
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.
431
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.
Delete Queue, Create subqueue, and Show statistics are enabled when a GeoWorkspace is open, whether a queue is selected or not.
432
Create subqueue-Creates a subqueue for any queue through the Create Subqueues dialog box. When you create a subqueue, it becomes the active queue. A subqueue is a user-defined subset of a queue, that is, a view into a specific queue. You can create subqueues for queues but not for subqueues. The items in the subqueue remain in the parent queue. If you delete the parent queue, the subqueues are also deleted. Subqueues are the same type of queue as parent queues. That is, if the parent queue is dynamic, the subqueue is dynamic; if the parent queue is static, the subqueue is static. As with parent queues, dynamic subqueues are designated on the Queued Edit control by a yellow icon, static subqueues by a white icon. To create a subqueue, you first select the parent queue and then name the subqueue. You can create a subqueue based on one of two criteria: attribute filter (the default) or spatial filter. If an attribute filter, you select the Attribute filter option and then click Define, which displays the GeoMedia standard Attribute Filter dialog box for you to define an attribute query filter. If a spatial filter, you select the Spatial filter option and then select a filter from the corresponding drop-down list of spatial filters defined for the GeoWorkspace. This command is for queues only.
Show statistics-Displays information about a queue and its items on the Show Statistics dialog box. This information includes the name of the queue, the name of the process that created the queue, and the number of items in the queue. If the Status field is defined for the queue, the information includes the number of items with each defined status. If subqueues have been created, the information includes the number of subqueues, the names of the subqueues, and the number of items in the subqueues. You can also generate a queue report that displays in your default text editor. This command is for queues only.
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.
434
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
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 users.
436
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
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.
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
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.
439
See Setting View Options in the Working with Queued Edit section for more information on using this dialog box.
440
Defining Joins
You can create the following types of joins: Inner join Records are added to the join only if the value from the left field matches the corresponding value in the right field. Records from either feature class that do not match are not included in the join. All records from the left feature class are included in the join, but only matching records from the right feature class are included. Records from the right feature class that do not match are not included. All records from the right feature class are included in the join, but only matching records from the left feature class are included. Records from the left feature class that do not match are not included. All records from both feature classes are included in the join.
In any of the outer joins, fields in records with unmatched values have null values. Accordingly, join attributes with null values cannot be matched to any record in the other feature class. If a record in one feature class contains a value that has a match in more than one record in the other feature class, the query will return multiple copies of the first record. To display the join in a map window, the software uses the geometry from the left feature class or query. So, when you create a join from two feature classes or queries that contain geometries, select the feature class or query whose geometry you want from the left side of the Join dialog box.
441
2. 3. 4. 5.
From the Left side of join drop-down list, select the left feature class or query. From the Right side of join drop-down list, select the right feature class or query. From the lists of available attributes, select the attributes on which to create a join. 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 join. 7. Optional: Click Attributes to rename (click Rename) and/or to reorder the attributes (using the arrow buttons and/or Select/Unselect All buttons to aid the selecting/unselecting process).
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 join to perform.
442
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
The data window and map windows are updated for the deletion.
Analysis Options
You can choose from among the following analysis options for the statistics you need: Area-Calculates the area of each feature with an area geometry and stores the value in a new field called Area. The area is calculated only for those features with an area geometry; any other geometries are ignored. If the input feature class or query is a linear geometry, this option is ignored. Perimeter-Calculates the perimeter of discontiguous geometries, and holes are accounted for in the area calculation each feature with an area geometry and stores the value in a new field called Perimeter. The perimeter is calculated only for those features with an area geometry; any other geometries are ignored. If the input feature class or query is a linear geometry, this option is ignored. 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 disjoint area geometries. If the feature is a collection containing area and line or point geometries, the statistic is still calculated for the area geometry, while the other geometries are ignored. If the input data is a linear geometry, this option is ignored. Length-Calculates the length of discontiguous geometries, and holes are accounted for in the area calculation each feature with a linear geometry and stores the value in a new field called Length. The length is calculated only for those features with a linear geometry; any other geometries are ignored. If the input feature class or query is an area geometry, this option is ignored. Discontiguous geometries are accounted for in the length calculation. 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
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. The Analysis options list is populated based on geometry of selected feature class or query. All available analysis options are off when a feature class or query is first selected. When the feature class or query is changed, all available analysis options are again turned off. However, if the geometry type of the new feature class or query matches that of the old feature class or query, the user-selected options are retained. 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. Verify that the Display results in map window check box is selected in the Map window name field, and change, if appropriate, the map window in which to display the results. OR To not display the results in a map window, uncheck the Display results in map window check box. Optional: Click Style, and change the default style on the Select Style dialog box. Verify that the Display results in data window box is selected in the Data window name field, and change, if appropriate, the data window in which to display the results.
5. 6. 7. 8.
9. 10.
445
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
You can specify the buffer zone distance (or the name of an attribute containing buffer zone distances) on a per-feature basis. Many variations of input distance values are supported, including stacks, rings, and buffer zones in the interior of areas. The buffer zone distance can be of two kinds, constant or variable.
When using a constant distance, you set the distance value and unit. You must type the distances as follows: Single-A simple number, for example: 10 Stacked-Numbers separated by semicolons (;), for example: 10;20;30 Ringed-Numbers separated by colons (:) and semicolons (;), for example: (start/end) 10:20;30:40 The default value for unit is from the Unit setting on the Units and Formats tab of the Define Coordinate System File dialog box. When using a variable distance, you select an attribute that contains distance values that may vary on a per-feature basis. Only attributes of type text, byte, integer, long, single, double, and currency are available for selection. These values must be in the ground units of the coordinates system of the data you are buffer zoning. If this is not the case, you can construct an expression using the Functional Attributes command, which performs any required unit conversion and formatting. See Working with Functional Attributes in this section.
447
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
449
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
See the GeoMedia Professional Help for information on this dialog box. You can also access the Functional Attribute dialog box to create, edit, review, and/or delete functional attributes through the Aggregation and Analytical Merge commands on the Analysis menu and the Update Attributes command on the Edit menu. The Analysis commands Functional Attributes, Aggregation, and Analytical Merge are types of queries for forming additional data with the Functional Attributes dialog box. The Edit command Update Attributes is different in that it is a database update tool for changing the original data and requires a read-write connection. When displayed through the Update Attributes command, the title of this dialog box is Expression for <attribute name>, and it does not have the Functional attribute name or Output type fields. See Aggregating Data and Merging Feature Classes and Queries in this section and Updating Feature Attributes in the Editing Features and Geometries sec tion. To avoid possible confusion, remember that there is a Functional Attributes command that, when selected, opens the Functional Attributes dialog box. However, from this dialog box, and from the other commands just discussed, you can access the Functional Attributes dialog box.
451
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.
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 joined with operators. For example, an expression can be a calculation, such as: (price * 1.5) or (price + sales_tax). In an expression, you enclose character data values in single quotation marks ('). In the following expression, the character literal B% is used as the pattern for the LIKE clause: LastName LIKE 'B%'. In the following expression, the date value is enclosed in single quotation marks: OrderDate = 'Sep 28 2001'.
Operators
Operators are symbols specifying an action performed on one or more operands, that is, how the operands are manipulated. The operator categories are the following: Arithmetic Bitwise Comparison Logical String 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
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.
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
Projectgedmeas
454
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
456
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.
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
458
459
NewOpens a submenu with the following items: CustomOpens the Functional Attribute dialog box for creating new functional attributes, as does the New button. Count(*)Adds a new functional attribute with a default name of CountOf<Feature>, where <Feature> is the name of the feature class or query input to the command. The expression for the functional attribute is COUNT(*). [Function] > [Attribute]Adds a new functional attribute with a default name of <Function>Of<Attribute>, where <Function> is the name of the function ( AVERAGE, COUNT, FIRST, MAX, MEDIAN, MIN, SUM), and <Attribute> is the name of the attribute chosen. For example, to obtain the sum of the Population attribute, the default functional attribute name would be SumOfPopulation. The expression for the functional attribute is <Function>(<Attribute>), for example, SUM(Population). [Function] > Multiple AttributesOpens the Multiple Attributes dialog box for creating multiple new functional attributes as in the previous bulleted item, one per chosen attribute from the list of all attributes from the input feature class or query that is of a data type valid for the selected function. After checking appropriate attributes, clicking OK dismisses the dialog box and returns one new output functional attribute for each attribute chosen.
PropertiesOpens the Functional Attribute dialog box for reviewing or editing functional attributes, as does the Properties button. DeleteDeletes selected functional attributes, as does the Delete button.
460
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. Verify 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. Verify that the Display merge in data window check box is checked, and change in the Data window name field, if appropriate, the data window in which to display the merge. OR To not display the nongraphic attributes of the merge in a data window, uncheck the Display query in data window check box. 10. Click OK to generate the merged features.
461
In the preceding example, the railroad pattern is uneven because of the segmented network; the pattern origin is redefined every time a new segment is encountered. This is easily overcome using the Analytical Merge command, as in the following example.
In the preceding example, the pattern spacing is consistent, as opposed to the first example, thereby producing the appropriate symbology, as specified on the Select Style dialog box. This is because the Analytical Merge command has merged the linear network, thus eliminating the problems associated with segmented displays. This workflow is also very useful for multiple-line displays used to show cased road (parallel line) symbology, especially at intersections.
Aggregating Data
The Aggregation command lets you copy attributes from features, including graphic text feature classes and queries, in one feature class (the detail feature class) to related features in another feature class (the summary feature class) in the form of a dynamic query. This query is based on the spatial relation between two features and/or related table columns (similar to a join) between two features. The detail feature class attributes are aggregated into the summary feature class. Both summary and detail feature classes can be point, linear, area, compound, and nongraphic, but not graphics text or image. The output 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
Aggregation Types
There are three possible types of aggregation based on the merge criteria: attribute based, spatially based, or both. You specify the criteria through the tabs on the Aggregation dialog box. On these tabs, you also specify the resolution operator and the definition of output functional attributes to be computed from the summary features and the detail features.
Attribute Aggregation
This type of aggregation uses matching attribute values to determine how the information in the detail table is aggregated into the summary table. For example, you could aggregate two tables, one with parcel geometry (PARCEL) and one with nongraphic information (PARCEL_INFO) that is related to the parcel features that have one common (identical) PARCEL_ID column. Using attribute aggregation would allow you to combine specific calculated information from the detail table (PARCEL_INFO) to the summary table (PARCEL), where appropriate, based on the comparison of the common attribute. To this join, you could use functional attribution to add calculated information between the two sources. From the Attribute Aggregation tab, you can select one or more summary and detail attribute pairs from a list of all displayable attributes, to be used for determining if features should be aggregated based on the equivalence of attribute values. Values of all attributes must match, that is, there is a logical and between the comparisons of the various attribute 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
gdbSingle
gdbLong
gdbByte
gdbDate N N N N N N N Y N N N N N N N N N Y
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
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
gdbText
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
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 join. You can use Aggregation to operate on both input and output attributes. This allows you to perform analytical operations on previously defined functional attributes with the same operation. The summary features appear in the Attributes field of this dialog box as Input.<attribute name> and the detail features appear as Detail.<attribute name>. See "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
467
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
469
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
2. Select the feature class from the Generate base geometry from drop-down list. 3. Check the appropriate Output types check box(es). 4. Accept or override the default query name (Base Geometry of <featurename>) in the Query name field, and type an optional Description. 5. To display the base geometry in a map window, verify that the Display in map window check box is checked. 6. Accept the default, select, or type a Map window name, and optionally the Style. 7. To display the base geometry in a data window, verify that the Display in data window check box is checked. 8. Accept the default, select, or type a Data window name. 9. Click OK to generate and to display the base geometry in the specified map and/or data window.
In the preceding example, adjacent area boundaries have the boundary line dashed twice where the coincidence is occurring. The end result is that the coincident boundary lines rarely appear as defined by their style definition. This can happen within a feature class, or across feature classes. This problem can be rectified using the Generate Base Geometry command, as in the following example.
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 supports a single feature class or query as input. When trying to separate coincident boundaries
472
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
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. Verify that the Display in map window check box is checked, and change in the Map window name field, if appropriate, the map window in which to display the merge. OR To not display the merge in a map window, uncheck the Display in map window check box. 7. Optional: Click Style, and change the default style on the Select Style dialog box. 8. Verify that the Display in data window check box is checked, and change in the Data window name field, if appropriate, the data window in which to display the merge. OR To not display the nongraphic attributes of the merge in a data window, uncheck the Display in data window check box. 9. Click OK to generate the attribute selection query.
474
The functionality of this command parallels the union capability provided by SQL and most relational database management systems. A union provides the ability to record-wise append multiple tables/views (relations) in query results to create an output that is the logical union of the input. It can be thought of as appending together the records of many source inputs. In this sense, it is the record-wise equivalent to the column-wise concatenation provided by the Join command capability. The Union command performs a relational union of the chosen feature classes and queries. It does not perform a geometric union of features. You would use the Union command, for example, in the following scenario. You have feature classes of 100 different counties from 100 different database schemas, and you would like to merge (record-wise) all 100 different counties records, and output the results into one feature class. To do this, you would perform a union to create an output query and then use the Output To Feature Classes command to output the results into a database warehouse. The Union command requires that the corresponding attribute columns from the selected feature classes/queries should be of the same data type. This command raises the following error when there is a mismatch in the common attributes for the selected feature classes: Unable to retrieve output query from union operation. The field's size does not match for field FIELD1. You need to resolve the disparities in the attribute data-types as raised by the Union command. See Working with Joins in this 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
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
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 <feature name> dialog box.
477
7. Select the appropriate Output schema mode, reorder the feature classes/queries as needed by using the arrow buttons, and then click OK. 8. Optional: Click Attributes, which is visible only in query edit workflows. Follow the workflow on the Attributes of <feature name> dialog box in Step 3. 9. Optional: Change the default query name, and/or type a description in the Output union as query fields. 10. Verify that the Display in map window check box is checked, and change in the Map window name field, if appropriate, the map window in which to display the merge. OR To not display the merge in a map window, uncheck the Display in map window check box. 11. Optional: Click Style, and change the default style on the Select Style dialog box. 12. Verify that the Display in data window check box is checked, and change in the Data window name field, if appropriate, the data window in which to display the merge. OR To not display the nongraphic attributes of the merge in a data window, uncheck the Display in data window check box. 13. Click OK to generate the attribute selection query.
478
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.
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 DatumThe basic, linear geometry of an LRS with its key identifiers and measures. EventAny feature, characteristic, or occurrence along a road (for example, accident, bridge, road condition). LRM (Linear Reference Method)The technique used to specify where an event occurred along a road (an accident occurs at kilometer marker 4, stop sign at the intersection of Main Street and Elm). Traversal/RouteSet of segments in a certain order and direction. Milepoint/Kilometer Point/Log MileDistance measurement from the beginning of a route. SegmentContinuous section of roadway (that is, intersection to intersection). MarkerStart and endpoint of segments, often Intersections. Events are frequently measured as an offset of a marker.
The preceding diagram shows a portion of road on the left and its geospatial representation on the right. The road has kilometer posts that indicate cumulative linear measures along 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.
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 OptionFor 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 OptionFor 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 OptionThis 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 length2D (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: IDThis is a long integer value that uniquely identifies each record within the table. LRSKeys1-4This is one to four fields that together define the route that this record lies along. MeasureThis is a numeric field that indicates the relative location of the External Marker on the route defined by the LRS Key fields. MarkerNameThis 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.
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.
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.
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 supported, 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.
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.
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 supports graphic features. Use a query of a linear feature for dynamic segmentation. Support for the LRS Measure, LRS Measure with Internal Markers, LRS Measure with External Measure Markers, LRS Duration, LRS Duration with Internal Markers, and LRS External Measure Markers models. 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. Support of the following event referencing methods: Measure Projected XY coordinates Longitude/Latitude Marker Offset Duration Support of single and multi-level LRS features. For a multilevel LRS, you use a Display LRM query as the LRS feature. The LRS model and LRS properties are set using extensions on the Display LRM query and are read only. Support of datum-based events. To define datum-based events, you select a Display LRM query as it has the required extensions to access LRS Metadata details. The Datum based option on the Dynamic Segmentation dialog box is enabled only if the selected LRS feature is a multi-level LRS Display LRM query. This option is disabled if the selected LRS feature is not a Display LRM query or if it is a single level LRS Display LRM query. The LRM based option is also enabled when the Datum base option is enabled. Create dynamically segmented events that are laterally offset from the source linear features. The lateral offset can be a distance defined by an entered constant, a variable distance based on a database attribute, or a combination of both. Resolve multiple events that occur at the same location by assigning a different offset distance value for each event so that events are not displayed on top of one another, thus differentiating overlapping event records. Whenever linear or point events overlap, the value of the Occurrence field is incremented for each successive linear event. This occurrence value can be used in conjunction with the offset display capability to show these events side by side to make the results clearer, as in the following examples:
Create dynamically segmented point events that are rotated. The rotation can be an angle defined by an entered constant, a variable rotation based on a database attribute, or a combination of both. Choose which of the event data attributes are passed through to the dynamically segmented events, and to reorder and/or to rename these attributes. Choose to take the height (Z coordinates, 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 supported, 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.
492
Linear Referencing
21. Click Event feature > Properties.
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.
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.
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
Inserting Labels
With the Insert Label command, you can create labels as a query or as a feature class, depending on how you want the labels to behave and what you want to do with them in the map window. In both cases, the attributes of the original feature (the additional columns) are copied to the label feature. However, in a query label the attributes are dynamically linked so that a change made in the original feature attributes is reflected in the linked label feature as well. In a feature class label, the attributes are static and not linked so that a change in the original feature attributes is not reflected in the feature class label. Each label creation method has its advantages. Labels as QueryYou can create labels as a query in the GeoWorkspace if you want each label linked to the feature with which it is associated. As a query, the labels will be updated each time you edit the labeled features or open the GeoWorkspace. When, for example, a feature is deleted from the feature class, its label is deleted as well. Similarly, 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
Label Placement
This command lets you set the label placement orientation, and alignment, offset, and whether to place single or duplicate labels. The available label placement orientation modes are as follows: Place at anglePlaces the label at the angle specified in the degrees field. This mode is the default orientation mode, at 0 degrees. The valid range is 360 to 360 degrees. The angle unit and precision settings are based on the default settings defined on the Units and Formats tab of the GeoWorkspace Coordinate System dialog box. Orient to geometryPlaces the label rotated in the direction of the geometry being labeled. The command displays the label with the rotation angle obtained from the geometry being labeled, using the style taken from the legend entry. If there is more than one legend entry, the style of the topmost entry is used. The following rules for label placement apply: Point dataOrientation is based on the point rotation angle. Linear dataOrientation is based on the angle of the line from begin point to end point. Area dataOrientation is based on the angle of the longest edge of the area boundary. Labels are placed right side up and read as follows: 0, 180, 360 degreesText reads horizontal, left to right. 90, 270 degreesText reads vertical, bottom to top. > 0 degrees, < 90 degreesText reads southwest to northeast. > 90 degrees, < 180 degreesText reads northwest to southeast. > 180 degrees, < 270 degreesText reads southwest to northeast. > 270 degrees, < 0, < 360 degreesText reads northwest to southeast. Map window rotation at the time of placement is honored. If the orientation of the geometry is 30 degrees and the map window is rotated by 40 degrees, the labels is placed at 70 degrees from the horizontal.
498
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
5. 6. 7. 8. 9.
500
2. Place the first vertex to place the leader terminator, and the dynamic label appears.
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
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.).
As you move from the start point, a dynamic line segment is displayed, and the leader terminator is dynamically displayed, taking into account the calculated orientation. The label position remains fixed until the second point is digitized.
4. Place any additional leader line vertices.
After the second point has been placed, the leader terminator is placed in dynamics using the calculated orientation. The label is displayed in dynamics at the cursor, using the alignment calculated on the segment.
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 featureEnds the leader line. Cancel featureSame 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
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.
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.
Orientation
The available label placement orientation modes are as follows: Place at anglePlaces the label at the angle specified in the degrees field. This mode is the default orientation mode, at 0 degrees. The valid range is 360 to 360 degrees. The angle unit and precision settings are based on the current settings defined for the Angle type in the default units and precision settings on the Units and Formats tab of the GeoWorkspace Coordinate System dialog box. Rotate dynamicallyPlaces the label, allowing you to specify rotation angle dynamically for each label instance. This mode labels by two clicks. The first click places the label; the second determines the label rotation. Rotation is dynamically displayed until the second click.
503
Alignment
The available label alignments are as follows: Top left Center left Bottom left Top center Center center Bottom center Top right Center right Bottom right
504
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 user-defined rotation angle, click to place the label. OR To place the label to rotate dynamically, click for the location for the label origin; then click for rotation and placement. OR To place the label to orient to geometry, click to identify the feature to be labeled at the location where the orientation should be calculated; then click to place the label. OR To place the label along an arc, digitize three points to define the curvature of the arc, in the order 1-2-3. Optionally, modify the inter-character spacing using the mouse wheel or
505
506
You could then use leader lines to move the conflicting queries.
507
Workflow Options
There are two different workflow options, depending on the input. The output capabilities of this command are two queries, but the input dictates the level of interactive editing and dynamic behavior of the modified input text: 1. Input is a query or read-only feature classThe command identifies 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 features label attributes in the database. For example, if the input is a query, changing the State_Name attribute from al to AL in the original feature would cause the query to change, which in turn would cause the output conflict queries to change. If the input is a read-only feature class, you cannot edit the feature class, so the output conflicts query will not change. You will likely use this command to filter the overprints, displaying only the output non-conflicting query in the map window instead of the input query or read-only feature class. 2. Input is a read-write feature classThe command identifies non-conflicting text and conflicting text. The input feature class items can be moved or deleted, but the text string will not update dynamically when changes are made to the originating features label attributes in the database. For example, in the case where the State_Name_Labels text feature class was based on the States feature class, and the Resolve Text Conflicts command was run on the State_Name_Labels feature class, changing the attribute al to AL in States will have no 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.
508
509
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.
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, contact Intergraph Support.
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 supported by the desktop GeoMedia Find Address and Geocode Addresses commands. Reverse geocoding is supported through geocoding web services. Address Geocoding provides tools to let you create AGI files from street centerline and rooftop (point) datasets accessible from GeoMedia by means of the GDO data servers.
Geocoding 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
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 Support for starting the Define Parsing Rules utility and the Define Geocoding Model utility.
513
Geocoding
Address geocoding profileXML 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 matchingProcess that takes a fully parsed input address and finds the best match in the index. Address parsing rulesDefined 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 referenceThe 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 warehouseThe source GeoMedia-accessible dataset that contains the features the geocoding index is derived from. Geocode Addresses commandAn Analysis command that geocodes all of the features in an input (normally nongraphic) feature class or query containing address information, producing a query on output with point geometries. GeocodingThe process of identifying a geographic location. Geocoding datasetA dataset used as reference to perform geocoding or reverse geocoding. The GeoMedia-delivered implementation of a geocoding dataset is the Address Geocoding Index (AGI) file. The term geocoding dataset is used as a generic term, as this design allows for third-party geocoding engines (and their data) to be used. Geocoding directoryAn XML document that defines the reference dataset location and other characteristics for various geocoding engines. It consists of one or more defined geocoding datasets, each of which has a unique identifier for the applicable runtime engine and an associated connection string intended to link the object to its reference data source data. Geocoding engine interfaceA COM (dispatch) interface definition that provides a generic interface by which any number of independent (Intergraph-developed or 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 modelAn XML document describing a geocoding model. A geocoding model (GCM) definition describes user-recognizable address components (or fields) and their correlation to the various elements of an address, that is, a comprehensive description of address elements that make up a particular address structure. The relationship between the attributes of the source data used to create the index (AGI) file, and the internal address definition of the dataset is also defined in the GCM file. Additionally, various AddressTransformations are defined in the GCM. Index buildingProcessing the source data and building an Address Geocoding Index file. Part of processing of the index data also involves address transformation and standardization. The index is build with the Publish Address Geocoding Index utility.
514
Geocoding
LocationA point on the earth, which may be expressed in world coordinates (textual or numeric) or as a point geometry. MatchingComparing standardized address elements in a common structure (one may have been transformed) and selecting one or more successful or candidate matches. Matching indexMaximum 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. ParsingDecomposing the textual representation of an address into constituent address elements according to various rules. Reverse geocodingTaking a location (that is, a coordinate or a point) and generating an address for it. Rooftop datasetType 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 dataThe 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 factorThis 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 propertys 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 propertys value has no effect on geocoding upon rooftop reference data and geocoding intersections. It is only available in the Find Address command. StandardizationEvaluating and adjusting the parsed address elements according to addressing rule standards. Street centerlines datasetType of dataset using street centerlines with attributes that can be used for searching, as well as using house number ranges. TransformationTransformation 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 BuildingProcessing the source data and building an Address Geocoding Index file. Part of processing the index data also involves address transformation and standardization. 2. Address Transformation (includes address parsing)Decomposing the address into the matching attributes used to build the index file. 3. Address MatchingTaking a fully parsed input attribute and finding the best match in the index.
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 (user input) and target (geocoding engine expectant) address formats.
Specifying the input for this command is a two-step process in which you first define parameters on the Find Address Options dialog box. You then provide additional address details and perform the actual find through the Find Address dialog box. The Find Address dialog box is displayed only if the geocoding directory has first been defined. If you try to start this command and no geocoding directory is known to the command (or a previously specified one does not exist), the Find Address Options dialog box is displayed first to let you define the geocoding directory. (Clicking Options on the Find Address dialog box also displays the Find Address Options dialog box.). The Find Address Options dialog box lets you specify the following parameters used in the geocoding process: Geocoding directorySelected geocoding directory file (XML) that has information for one or more geocoding datasets, by default in the GeoMedia Warehouses folder. Geocoding datasetDataset name to geocode against, containing all the dataset names from the specified geocoding directory file. If there is more than one dataset, the additional item <By address element> is added to the top of the drop-down list. You then have the option (Address element name) of specifying an address element whose corresponding value is used for determining the geocoding dataset (that is, the specified address element defines the geocoding dataset name to be used to find the address location). For example, you might use a regional name, such as the city name, when geocoding adjacent city street networks. Address element nameAddress element to be used to specify the name of the geocoding dataset to be used (if a geocoding directory contains a number of named geocoding datasets). This drop-down list is enabled only if the Geocoding dataset has been set to <By address element>.
Input address formatAddress format supported by the selected Geocoding dataset drop-down list. By default, the first input address format is selected. If <By address element> is the selected dataset, this list is populated with all the input address formats listed in the geocoding 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
516
Geocoding
Street Address: 288 Hemlock Ln City: Whittier State: NC ZIP: 28789 Minimum match scoreValue (in the range 0-100) that determines if an address has been successfully matched. If a match operation obtains a match score of at least this value, the match status is displayed as Matched. If the match score obtained is less than this value, the match status contains descriptive text detailing the mismatch. The default value is 100. Offset distance and unitThe default offset value is two meters for centerline geocoding. Offset is not used for intersection or rooftop geocoding. The units 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 factorValue 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 points placement. If the street centerlines length is L, then all geocoded addresses are located along the middle part of the centerline of length <value> * L. If the specified value is 100%, locations are interpolated along the whole centerline and, thus, can be close to its endpoints. If the propertys value is 0, then all geocoded points on this centerline are located exactly in the middle of it. Maximum number of candidatesRestricts 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. StylePoint style geometry. The style can be set for optimum map window display of the geocoded address point geometry results through the GeoMedia Select Style and Style Properties dialog boxes, with the point style being enabled. The default style is the default point geometry style. The Find Address dialog box lets you specify the following parameters used in the geocoding process and lets you start the process and view the resulting match details: Address element/Value gridContains the read-only Address element column listing the source address elements of the chosen Input address format. The number and name of the elements of this column are determined and populated at runtime by your selection of the Input address format on the Find Address Options dialog box. If an address element name is set as a required element, it is displayed in bold and red font. If the <By address element> option is chosen for the geocoding dataset, the address element as specified by the Address element name list is also displayed in bold and red font. The 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.
FindAfter 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. ClearClears 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. OptionsDisplays the Find Address Options dialog box, which lets you specify the geocoding directory and other parameters used in the address geocoding process. Standardized addressDisplays the input address in the standardized format. The standardized address is displayed even if the geocoding operation results in zero results. Match resultsDisplays 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. DetailsDisplays 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
518
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/FitPans 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.
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 verify 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. This is one of the input address formats supported by the dataset being used; you may choose a different format to use to enter the address information. 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.
8.
9. 10. 11.
520
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: State: ZIP: 14. Click Find. Knoxville TN 37916
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
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.
17.
Input address formatAddress format supported by the selected Geocoding dataset drop-down list. By default, the first input address format is selected. If <By address element> is the selected dataset, this list is populated with all the input address formats listed in the geocoding directory. 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
522
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 attributesAttributes that form the address elements of the displayed source address definition. These attributes are presented in a grid that lets you easily specify the mapping between the address elements of the source address definition and the address attributes from the input feature class/query. The 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 <By address element> is chosen as the geocoding dataset, the address element specified in the Address element name drop-down list also is displayed in bold and red font on the grid. The controls on the right-hand side are enabled only on a tab out from this control on the condition that you provide all the required fields. Output AttributesAll the available fields in the input feature class/query, along with the fields generated by the Geocode Addresses command (like GeometryField, MatchScoreField, MatchStatusField, StandardizedAddressField, and MatchedAddressField). Clicking Attributes displays this dialog box so that you can select, rename, and re-order the output attributes as necessary. Advanced PropertiesMinimum 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.
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 supported 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.
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 <By address element>; then select State from the Address element name drop-down list . 10. In the Address attributes grid, note that the address elements have a field mapped automatically for the attribute. This was defined through the Geocoding Model file used to build the Address Geocoding Index file (AGI). 11. Tab out of the grid control to enable the remainder of the Geocode Addresses data. 12. Verify that the check boxes to display the output to the map window and to the data window are checked and that the map window display style is appropriate. 13. Click OK to see the results. 14. Inspect the results, and note that there extra attributes added by the Geocode Addresses query. 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.
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 user 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.
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 user interaction. The address geocoding system provided with GeoMedia performs such parsing. The approach used exploits the theory of Hidden Markov Model (HMM). Hidden Markov models present a general approach that is widely used for recognition problems, for 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 typeThis element type is defined by enumeration of all values it can contain. 2. Pattern token typeThe values of this element are defined by a single regular expression. A good example of the pattern token is the base U.S. ZIP, which always contains exactly five digits and can be described by the \d{5} regular expression. 3. External Rules token typeThe values of this token are defined by some other parsing rules. It is a convenient way to embed an existing set of parsing rules into the current parsing rules. 4. Reference token typeThis token is exactly the same as some other token. It is possible, for example, to define the Street suffix token from the U.S. Street example as a reference to the Street prefix token. 5. Characters token typeThis is the most generic notion. It should be used if none of the previous token types can fully describe the values that can be assigned to the token. This
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 tokens value is replaced with its standard form. Then, these values are taken to form the standardized output entity(entities). The standard form is defined separately for every token, as follows: 1. Dictionary token typeAll dictionary items are combined in groups, with every group consisting of some standard form value and its aliases. During standardization, all aliases are replaced with the standard form of the group. 2. External Rules token typeThe standardization is performed by the embedded parsing rules. 3. Reference token typeThe standardization is defined in the referenced token definition. 4. Pattern and Characters token typesTokens of this type contain standardization rules. Every rule contains the following: what to replace (a substring or regular expression), a replacement (a substring or regular expression), and several flags that affect the standardization process. Besides the tokens themselves, their characteristic sequences should be defined. This is done by providing training samples. Every training sample is a manually parsed string along with the sequence of tokens that form this string. For the U.S. Streets address parsing rules with the elements discussed above, such training sequences can be the following: Address Sample 1st Ave E E Main Street Broadway Military Way Token Sequence Street name Street prefix Street name Street name Street type Street name Street type Street suffix 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 user. 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 supports: 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 supported 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. 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. Verify that the Display points in map window check box is selected, and change in the Map window name field, if appropriate, the default active map window in which to display the geocoded points. OR To not display the geocoded points in a map window, select the Display points in map window check box to remove the checkmark. Optional: Click Style, and change the default style on the Select Style dialog box. Verify that the Display points in data window box is checked, and change in the Data window name field, if appropriate, the default new data window in which to display the nongraphic attributes of the geocoded points. OR To not display the nongraphic attributes of the geocoded points in a data window, click the Display points in data window box to remove the checkmark. Click OK to generate and to display the points in the specified map window and/or data window.
5. 6. 7. 8. 9.
10. 11.
12.
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 registered survey/plat maps, parcel deeds, and title documents. An area feature generally consists of one primary feature class (for example, parcel) and various component feature classes (for example, the individual boundaries as separate feature classes). In addition to area features, you can precisely insert and maintain linear features. You select both primary and component feature classes from a list of all writable linear/compound features from all the open connections, reference features, and categories. When you select a compound geometry feature class as the primary feature class, this command creates an area geometry for the primary feature. When you select a compound geometry feature class as the component feature class, this command creates a linear geometry for each component feature. In addition, this command dynamically displays the feature geometry in the map window as you define the geometry. You have the option to add the traverse to the primary feature class or not through the Primary feature class check box on the Insert Traverse dialog box. When checked, it lists all writeable compound, area, and linear features, and lets you select the primary feature class for the traverse to be placed. When unchecked, the primary feature class is set to None, and the component feature class is populated by selecting a linear feature class. As a result, you can continue adding the line segments to the component feature class(es) and can optionally select the Primary feature class when required. Once defined, you can save the geometry definition data to a .trv file and/or insert the geometry into a read-write warehouse. The .trv files have many uses. You can save coordinate geometry input from many different input/editing sessions into a . trv file until the geometry for an entire region or area is captured. You can then Load and Apply this data to a read-write warehouse. This provides both an audit trail of the data and an ASCII archive. Also, you can use . trv files as templates in which the data are loaded and edited for the creation of subsequent geometry features. 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.
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 supported. To use point input, set the traverse type to Point and use the Longitude/Latitude or East/North fields to enter the point position.
Arc Dimensions
To define an arc, you must select one of the four arc-placement methods (arc, chord, delta, or end point) and enter the required (enabled) parameters.
The following table shows the four arc placement methods and their required input:
Arc Length Chord Direction Chord Length Delta Direction Path Radius Tangent Direction
4 4 4 4
4 4 4 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:
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:
538
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).
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 account. If set to Projected (planar), the distances for all subsequent traverse segments are computed as planar distances.
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.
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 join the end and start points of the feature being digitized with a new line when the points are close together.
A line is shown joining the end point of the previous linear feature and the start point of the GeoMedia Professional User'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 verify that the closure error is within your specified tolerance limit.
The Calculated traverse columns in the feature detail grid are populated with the corrected values of bearing and distances or coordinates of the Line/Point or Arc length features.
11. When finished, click Apply to insert the traverse geometry and to hide the dialog box during feature placement.
If Display Properties dialog for new features is on, or if input is required for the selected feature class, specify the feature attributes on the Properties dialog box; then click OK to exit and to again open the Insert Traverse dialog box.
12. Click Save to save the traverse definition as a .trv file.
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.
542
Inserting Traverses
5. Optional: Edit the appropriate values. 6. Complete the feature as in the first workflow.
543
Inserting Traverses
544
SECTION 18
545
Layout Tab
The Layout tab lets you set controls for the layout window graphics commands relating to the layout grid and length readout. This tab is displayed on top when the Options dialog box is opened in the layout window.
The Units selection area lets you set up the units for defining Distance and Style values in the layout sheet. The Style setting is used for defining line widths for the drawing commands (Line, Circle, and so forth), and for north arrow and scale bar style properties. The Distance setting supports up to seven-decimal precision and is used for precision key-in control in the drawing commands (Line, Circle, and so forth), the Measure Distance command, the Legend Properties command, and the grid subinterval spacing. The precision readout sets the number of significant figures to display the accuracy of the unit readout value. The precision setting does not alter the numbers that you type into the fields, only the display of the numbers in the field. Values ending in five are rounded up. For example, if the precision readout is 0.123 and you draw a line that is 2.1056 inches long, the line value length is rounded. The length value appears as 2.106 inches long. If you are using millimeters as your drawing sheet units, you can have the values display in the fields as 3.5 mm or 3.50 mm. 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 displayDisplays a grid for precision element placement. The grid lines themselves are not considered part of the document and do not print. Grid snapAligns elements with the grid, which is an invisible set of lines in the document that helps you align elements. When you select this option, elements always align with the grid lines or the nearest intersection of the grid lines. Subinterval spacingSets the spacing of the grid lines. Subintervals per intervalDetermines the number of index grid lines. The read-only unit is set by the layout window Page Setup command. The size of each grid cell is determined by the Subinterval spacing. The Subintervals per interval determines the number of minor grid lines to display between the major grid lines. If the grid spacing is set to 0.25 inches and the grid index is set to four inches, then the minor grid lines display as dashed gray lines at 0.25 inch intervals, and the major grid lines display as solid gray lines at 1.0 inch intervals, per the following formula: major grid line interval = grid spacing X grid index.
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.
547
548
549
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
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.
551
552
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 <file type> Export Options dialog box; then click OK to write the active layout sheet to the specified name and to exit the command.
553
554
555
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
4. Select the target layer from the Change all to list; then click OK.
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
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.
558
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 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
4. 5. 6. 7.
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.
560
SECTION 19
561
Requirements for data display and presentation for analysis are generally quite different from those for output. In analysis, the display scale is constantly changing as you zoom in and out. Feature symbology settings are generally defined so they produce legible results at multiple display scales. In some cases, the data may be viewed in its raw geometric form as non-symbolized point, line, and area data. In output, the data presentation is typically defined to support a particular plot scale. The symbology settings are defined so they produce the optimal results when they are applied at a fixed scale. The data are usually fully symbolized for cartographic display. Support for these two scenarios can be seen in several areas of the interface, beginning with the Display Properties dialog box, which provides the ability to specify how the feature is displayed. The View (size is true at any display scale) setting specifies that the symbology remains fixed, regardless of the display scale - a suitable option for analysis. When this setting is turned off, it specifies that the symbology is rendered at a specific scale. As you zoom in and out, the symbology of the feature increases or decreases relative to the change in the display scale - a suitable option for output. See 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)
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
563
564
565
Map Specifications
Map specifications for the Insert Map and Insert Graphics into Layout Frames commands are defined in terms of a map window, a geographic extent, a plot scale, and a static/dynamic mode setting.
566
Designing 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, user-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 user-defined entry of the upper-left and lower-right corners of the quadrangle, defined using geographic coordinates (for example, d:m:s) to identify the geographic extent. This option is valid for projected or geographic coordinate systems defined in the GeoWorkspace coordinate system settings. The area between the outside of the quadrangle and the layout frame limits is cropped. Map Window (the default method)-Uses the area currently displayed in the selected map window to identify the geographic extent. The map window display area is defined by the window extent when the map window is in the Restored state. This is because only one window can be maximized at a time, and when the active window is maximized, all other non-minimized windows revert to their Restored state. This behavior may give the perception that this selection is producing the wrong result. To illustrate this behavior, open a single map window (with data) and the layout window. Make the map window active, and maximize the window. Fit the map data to the window by selecting View > Fit All. Next, select Window > Tile Horizontally. The map window and layout window are now both currently being displayed in their Restored states. However, the displayed data extent in the Restored map window is half of the displayed data extent of the maximized map window. If the windows are in their maximized state, and the layout window is active, the map window will appear Restored in the background. If the map window active, it will appear maximized, and the layout window will be Restored in the background. Only one window can be maximized at a time, so to get around this behavior, minimize all windows except the map window you want, and select Window > Tile Horizontally. The map window will be made as large as possible within the application, displaying the Restored state. Paper Size-Requires a user-specified paper size. The units for the Height and Width values are based on the Distance unit defined on the Layout tab of the Options dialog box. The unit type (inches, centimeters, and so forth.) is displayed to the right of the fields. By default, the height and width are equivalent to the sheet size. The geographic extent varies based on the plot scale selected. Polygon-Requires a user-defined digitizing of a polygon to define the geographic extent. The area between the outside of the polygon and the layout frame limits is cropped. Projected Frame-Requires a user-defined diagonal entry of the upper-left and lower-right corners of the frame or rectangle, defined using projected coordinates to identify the
567
Plot Scale
The plot scale of the map defines the relationship between ground units and the paper units used when portraying the geographic extent on the paper. You can select the method for defining the plot scale using one of the following methods: When you start either command, the default plot scale is equal to the display scale defined in the map window on the Display Properties dialog box. User-defined -This option is available with the Insert Graphics into Layout Frames and Insert Map commands. The size of the resulting map is predetermined based on the combination of the geographic coverage selected and the plot scale defined. This is true for all geographic extent methods using the Insert Map command and for most geographic extent methods using the Insert Graphics into Layout Frames command. The one exception is the Map Window geographic extent method in the Insert Graphics into Layout Frames command. When this geographic extent method is used, the size of the resulting map will be based on the original layout frame, where the map will be placed in the layout frame at the specified scale, and then cropped to fit the original frame. See 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.
568
Marginalia Specifications
Marginalia items placed in the layout sheet are always associated with a map. The marginalia specifications for the Insert Graphics into Layout Frames, Insert Legend, Insert North Arrow, and Insert Scale Bar commands are defined in terms of a legend, north arrow, and scale bar. The display parameters used for rendering the marginalia in the layout sheet are based on the command used to place them and their respective properties defined in the map window.
Legend
When placed using the Insert Legend command, the legend is placed in the layout sheet using a fixed size based on a combination of the number of columns, the size of the legend 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
Designing 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.
For various placement and editing commands, additional fields are displayed on the right side of an expanded Drawing toolbox. For example, when you select the Circle command, a Radius field is added.
Draw-Displays an assortment of menus of commands that operate on graphic elements in a select set, and provides additional commands to create symbols and to define the active symbol for placement.
570
If the layout window Drawing toolbox and Ribbon toolbar are deleted, and the session is exited and saved, and then GeoMedia Professional is reopened, the toolbox and toolbar are displayed again in the new session.
Nudge >
Align >
Distribute >
571
Create Symbol Set Active Symbol See Creating Symbols later in this section.
Editing
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 joins. For area elements, they also include fill properties, that is, if it has solid fill and fill color. For symbols, they only include layer and symbol file. You can edit all the properties except the symbol file, which is read-only. All of the properties of a group are general in nature; no geometry properties are shown for a group. The geometry properties vary according to the different elements and can include coordinates, height, width, and rotation angle. For ease of editing, the command supports both move and edit modes. In move mode, you can only change the position of the element, not its shape. In edit mode, you can change both the shape and the position of the element. You can use either mode, or you can switch between them. The following table lists the elements and their geometry properties:
574
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
Designing 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
Clicking the Apply Linear Style button applies the linear style to the objects in the select set. This button also provides a preview for the linear style. The preview is updated when a change is made to the linear color, width, type, terminator, end cap, or join settings, or when a map window style is selected. You can define simple line styles or select a map window style from the named styles of the GeoWorkspace through the active style menu, which displays when you click the corresponding arrow button. This menu contains two options: Use Simple Style and Select Map Window Line Style. The first option enables all the controls on the toolbox and sets the active style to a Simple line style defined by those controls, that is, you can edit simple styles at the component (color, width, and so on) level using the toolbox. The second option displays the Select Style dialog box, which is restricted to linear styles in this context. When choosing a named style, the remainder of the toolbox buttons are disabled, so you cannot edit the style as with the first option. Also in this case, the style definition is converted to a layout window style definition. Some aspects of a complex style definition may be lost during this process, and special handling is required for point style types used in pattern line styles. These conversion issues are discussed in the following section. 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
End cap
Partially
Dash cap
No
Style Properties - Pattern Line Style Functional Capability Point style Convert? Partially Notes Styles are converted by .sym. Font styles are emulated by .sym containing a field.
578
Style Properties -Symbol Style Functional Capability Type Source Name Size Define override color Translucency Rotation Alignment Offset X distance Offset Y distance Display attribute value in symbol Ignore map rotation Ignore geometry rotation Always keep upright Advanced tab - ABS Convert? No No No Yes Yes No Yes No Yes Yes No No Yes Yes No Ignored. Ignored. Ignored. Accomplished by Relative/Absolute orientation setting. Notes These attributes are used to find a suitable substitute .sym. Symbol is scaled when converted Accomplished on the Line Style dialog box. Ignored. Accomplished on the Line Pattern dialog box. Ignored. -
579
580
581
Designing Map Layouts for Printing in the Layout Window Defining End Cap and Join Styles
Clicking the End cap and Join button applies the active linear end cap and join style to objects in the select set. The end cap and join settings can be applied to linear geometries (including area boundaries) but cannot be applied to rectangles, circles, ellipses, or polygons. You can change the active set of linear end cap and join by clicking the corresponding arrow button, which displays the Select Caps and Joins dialog box for defining the start and end cap and mid-line join types for the active style.
This dialog box lets you select the end cap and mid-line join styles from its two drop-down lists. The Start and end cap list contains for items: Round (the default), Square, Flat, and Triangle. The Mid-line join list contains three options: Round (the default), Miter, and Bevel). The cap and join settings should match for closed shapes, or the vertex where the begin and end points meet will look odd.
582
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 unsupported workflow. Symbols that you create display the following default behaviors: 90-degree rotation angles. Automatic alignment with a target element or object when the symbol is placed in a document. No inherited size from their source definition; size is determined by the Styles dialog box, not the size the symbol was created with. 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
When creating a symbol using different elements, press CTRL while choosing elements with the Select Tool.
584
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.
585
586
Designing 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 feedback on the size and position of the element you are drawing. As you draw, the software also shows next to the pointer a temporary, dynamic display of the element you are drawing--this feedback is called a relationship indicator. When the software recognizes a relationship, it displays a relationship indicator at the pointer. As you move the pointer, the software updates the indicator to show new relationships. If a relationship indicator appears by the pointer when you click to draw the element, the software applies that relationship to the element. The software can recognize one or two relationships at a time. When the software recognizes two relationships, it displays both relationship indicators at the cursor, as seen in the example on the right.
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
588
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 sectio n for more information.
589
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
Designing 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.
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
593
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
Designing 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
596
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
The newly inserted layout frame group is left in the select set.
598
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.
599
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
3. Select the appropriate map window from the Map window drop-down list. 4. Select the appropriate Geographic extent method, and select and/or type any corresponding required parameters. 5. Type the appropriate plot scale value in the User-defined field. 6. Select the Static or Dynamic mode. 7. Click OK. OR Click Close to exit the command.
601
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
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.
603
By default, the treeview is expanded, displaying one column with the entries in the order they appear in the map window legend. The hidden attribute is set according to the properties of the map window legend (show legend entry, collapse legend entry, and display by scale). By default, if an entry is hidden in the originating map window, it is not displayed on the treeview. If an entry is displayed in the treeview and its corresponding feature has its display turned off in the legend of the originating map window legend, the entry remains in the treeview. The treeview does not support multi-select. The top node in the treeview contains the legend title. The next level in the treeview denotes columns with the text Column X (Y entries), where X is the column number, and Y is the number of entries in that column. The third level represents the legend entries and contains the key of the legend entries followed by the text of the feature name. In the case of range headings, the key is blank.
604
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 Legend Command Properties Rename Legend Title Add Column Distribute Entries Evenly Column Remove Column Add Entries Sort Entries Alphabetically Sort Entries by Geometry Entries Properties Lets You Customize the legend properties on the Legend Properties dialog box. Type a new legend title. Add an empty column below the legend title. Distribute all displayed legend entries evenly across available columns. Remove a column, transferring its contents to the previous column. (Press DELETE as a shortcut.) Add legend entries on the Add Legend Entries dialog box. Perform an ascending alphabetic sort of all legend entries in the selected column. Perform a geometric sort in the following order: text, point, line, compound, area. Customize the entry properties on the corresponding Legend Entry Properties dialog box.
605
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
Designing 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
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
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.
609
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.
610
3. To change the North arrow file, browse to select a different one. To see graphics of all the north arrows and compass 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.
4. 5. 6. 7. 8.
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.
611
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.
612
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.
613
614
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.
615
Boundary type
Rectangle type
When you pass the cursor over the handles, the cursor changes from the Select Tool arrow to the appropriate glyph - a line with arrowheads at both ends for corner file handles to scale and an open box for side file handles to enlarge or to reduce.
As you click the cursor and drag the mouse, the map frame is resized accordingly. Map frame scale enlargement has no limits. However, map frame scale reduction is limited such that the corner being reduced can never touch or pass its opposing corner file handle, leaving a minimum width/height map frame. Enlarging or reducing operations are designed to fine tune the geographic extent of the map. You can increase the size of the map frame on all sides by 20% in each direction. Map frame size reduction is limited such that the side being reduced can never touch or pass the file hand of its opposing side, leaving a minimum width/height map frame.
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
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).
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, maintaining the lower-left origin and map scale.
617
618
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
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
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
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
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.
623
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
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.
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
Designing 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.
627
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
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
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.
632
633
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.
634
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.
635
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.
636
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.
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.
637
638
Designing 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.
639
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.
640
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.
After the dialog box is dismissed, the file is written and the command is ended.
641
You can select the data window portion you want to display by a single cell, a contiguous rectangle of cells, one or more rows (not necessarily contiguous), or one or more columns (not necessarily contiguous). You can customize the appearance of the data window insert by adjusting the title, column headers and widths, and cells. You have the option to display the title of the data window and the column headers. You can also change the title and its font and the font of the headers and cells through the standard Font dialog box. Additionally, you determine the column width by one of the following methods: Based on data window (default)-Each column width is based on that column's width in the data window. Based on longest text-Each column width is based on the longest string in that column. User-defined-All columns have the same user-defined width. 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 Change column widths Re-sort data Hide/Show columns Change data values
642
. 6. Select the appropriate Data window from the drop-down list. 7. Check the Title check box to display a title; then optionally change the title text and font. 8. Check the Column headings check box to display headings; then optionally change the heading font. 9. Optional: Click Cells > Font to change the cell font. 10. Select appropriate Column widths option. If you select User-defined, type a positive value for the column width in the key-in field. 11. Press OK; then click to place the data window grid. A right mouse click lets you return (backup) to the dialog box without placing the data window grid.
643
644
SECTION 20
645
646
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.
647
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 supports 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
649
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.
3. 4. 5. 6. 7.
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 supports that option, check that option. Click OK.
650
651
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
653
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.
654
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
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 supports a graphical user interface (Start > All Programs > GeoMedia Professional > Utilities > Batch Plotting) and a command line interface. See the Batch Plotting utilitys online Help for complete information.
657
658
659
660
SECTION 21
Exporting to Shapefile
Use the Export to Shapefile command to export feature data (geometry and attributes), including categories and reference features, from any read-write or read-only warehouse connection into shapefile format. You can select any mixture of feature classes, queries, categories, and reference features, across any number of connections. This command outputs dBase IV version 2.0 and ArcView version 3.0 compatible files. Export to Shapefile supports null geometry and arcs (converted to polylines). For compound feature class, the command exports only the geometries of the geometry type you select: point, line, area (the default), or all. If you specify that the compound features are to be exported to all three shape file types, three shape files are created in the output folder, one each for point, line, and area geometry types. The names of the output files are suffixed by the geometry type names. Arcs and composite polylines are converted to stroked polylines, and composite polygons are converted to polygons. This command also lets you export the rotation angle when you are exporting a feature class with oriented point geometry. Text feature classes cannot be exported because the shapefile format does not support them. You can create a new shapefile or append to an existing one. When appending to an existing shapefile, the feature-class definition of the features being exported and the shapefile to which you are exporting data must be identical because a shapefile can contain only a single feature class. By default, this command appends to any existing shapefile(s) present in the output subfolder. If any error is found during appending, it is reported in the log file. When exporting a feature class with Oriented Point geometries, the orientation information is preserved by adding a numeric field to the output shapefile definition. This extra field is not added only when DWORD value AVExportPreserveRotation under the registry key 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
662
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
664
Polygon Region/Multipolygon
Text Geometry Point Collection Linear Feature Collection Areal Feature Collection Heterogeneous collection (point, line, and/or area together)
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
If the filename already exists, you will be prompted to replace. If a new filename was entered, a new MapInfo file is created. The following message appears after export: Selected feature class exported.
7. If you select the GeoWorkspace coordinate system option and the GeoWorkspace coordinate system base storage type is not Geographic or the horizontal storage unit is not in terms of 1 decimal degree (using geodetic datum WGS84 with no shifts), enter 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.
666
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
668
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
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.
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
The contents of the grid are saved to a settings file (a user-specified XML file). If an existing settings file is selected, you are prompted to overwrite or append and update.
20. Click Apply to start the export process.
All the feature classes/queries are exported from the Features to export grid, with the settings in the grid. If the Use feature class/query name as output design file name option is selected, all the feature classes from the grid are exported to their respective design files into the specified folder. If the design file already exists, and if the Append to existing output files check box is checked, the existing design files are appended. If unchecked, the existing files are deleted, and a new design file with the same name is created using the specified seed file. If a new filename was entered with the Output all features to a single design file option, the design file is created using the seed file specified and opened for export. When exporting to MicroStation V8 format, the input data 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.
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.
671
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 remembered until the dialog box is dismissed. To save them permanently, click Save As so that the grid settings are saved. 8. Click Apply to export the items in the grid. 9. Select another connection.
The grid is cleared, and the matching feature classes from the new connection are added to the grid.
10. Select a feature class.
If the name matches a name in the loaded settings file, the graphic properties are populated from the loaded file. If not, the default properties are displayed.
11. Click Add.
The feature class/query, if not already added to the grid, is now added to the grid with the defined properties.
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.
672
Element Types
The following table defines the IGDS element types generated from each of the GeoMedia Professional geometry types: GeoMedia Professional Geometry Type Point Text Line Linear Area IGDS Element Symbol / Degenerate line / Shared cell instance (only for MicroStation v7 format) Text Line Linestring or complex linestring Shape or complex shape Type Number 17 / 3 / 35 17 3 4 or 12, 4, 4, 6 or 14, 4, 4,
673
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.
674
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.batCommand file that controls the loading process. It will contain references for all the files created during the Export to Oracle Object Model process. Export.logLog file that contains either the cause of failures if error conditions arise or the number of features successfully exported per selected feature class during the export process. By default, the data is exported to the \Warehouses folder. You can change this location on the dialog box, and this location is then remembered as a session preference.
Error Reporting
Error conditions are not reported to you while the Export to Oracle Object Model command is being run. This is to improve performance and to ensure uninterrupted exports of large sets of data. 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*Loaders 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
675
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 Administrator tools to create a spatial index on the tables.
676
By default, the data is exported to the \Warehouses folder. You can change this location on the dialog box, and this location is then remembered as a session preference. Error 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.
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 attributesExports 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 coordinatesExports 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
If the DWGFilename exceeds 26 characters in length, it is truncated to 26 characters. All the special characters within the DWGFilename that are not allowed for a block name (like the space character ) are replaced with an underscore character _.) Block scale factor, which can be any positive value. This scaling value, with the orientation of the point geometry, is applied on the specified block while exporting the point features. The default value is 1.0. In the export process, the input features are transformed to the GeoWorkspace coordinate system. Also, an accompanying .csf file is generated in the same folder as the output file that represents the coordinate system used during the transformation. The name of the generated .csf file is the same as the name of the output file, but with a .csf extension.
3. Select the appropriate feature class/query from the Features to export drop-down list. 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
8.
9.
10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20.
The features are exported and transformed to the GeoWorkspace coordinate system. An accompanying .csf file is generated in the same folder as the output file that represents the coordinate system used during the transformation.
21. Continue the export process until complete; then click Close to dismiss the Export to AutoCAD dialog box.
Exporting to GML
Use the Export to GML command to export feature class geometry and its attribute data to GML (Geography Markup Language) format. The selected feature classes (including queries, categories, and reference features) are written to a GML Version 2.1.2, 3.0, 3.1.1 GML data file (.gml), and the corresponding XML Schema definition is written to the GML Version 3.2 base schema GML schema (.xsd) file. This command exports all supported feature and geometry types with no data loss including but not limited to arcs, compound geometry, composite geometry, and graphics text. You should use this command as a tool for migrating data from any data store accessible by GeoMedia to a GML data file and a GML schema file. To use this command you select any mixture of feature classes, queries, categories, and reference features, across any number of connections. You also specify an appropriate target coordinate system file for the export process. The command transforms the input data to this coordinate system as the data is exported. In addition, you can swap, that is, reverse, the order of the coordinate values reversed during the export process.
680
You also set the following other parameters before exporting. The appropriate GML version that is exported, by default, GML version 3.1.1. The namespace and the prefix for the output GML data/schema file in the format: xmlns:<prefix>=<uri>. See the next section for more information on prefixes. The location and name of the GML base schema file. Whether or not the bounding box is output for every record in the output GML file. Whether or not the sequence of fields output in the GML data/schema file is the same as that of the input feature class/query. Whether or not the 3-D coordinates are exported in the GML data file. Whether or not to swap the order of the coordinate values during the export process.
Using Prefixes
When a recordset is exported in GML with default settings, the default namespace (or target namespace) for an application schema is taken as "xmlns:gmgml='http://www.intergraph.com/geomedia/gml'" and so the schema and data are encoded using the "gmgml", which refers to the target namespace. The following is an example excerpt taken from the output GML file exported using the default settings:
681
The following is the excerpt taken from output GML file created using the previous settings. In this case, the default namespace (or target namespace) for the schema is taken as "xmlns:test='http://www.test.com'", and the data and schema are encoded using "test", which refers to the target namespace. <?xml version="1.0" encoding="UTF-8"?>
682
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
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
Once you have saved these objects, any user can connect to the library and copy the appropriate objects into the active GeoWorkspace. For example, a large enterprise might have specific corporate standards for symbolizing each type of feature. Road features might be black with a dashed white centerline and rivers might be blue. The GIS administrator for such an enterprise might create a corporate style library that all GIS users would use to get copies of all of the official styles to be used in their GeoWorkspaces. But what if the official style for Road features changes? The GIS administrator can easily replace the Road style in the library, and users can then simply connect to the updated library and refresh the objects whose definitions have changed. Note that most of the sharable objects reference other objects. For example, a legend contains Legend Entries, each of which refers to one or more Style Definitions and Queries. The Queries can refer to other Queries and/or Feature Classes. Feature Classes in turn refer to Connections. And, of course, Style Folders contain Style Definitions, and Query Folders contain Queries. When you save one of these objects to a library, the system automatically saves all of the objects in the reference tree. Then when the object is copied to a GeoWorkspace, all of the required objects underneath it are also copied. This ensures that the copied object will be fully functional in the active GeoWorkspace. The library commands are the following: New Library New Library Connection Library Connections Library Organizer
685
686
For Access, you select the location of the Microsoft Access database file (. mdb) to which you want to establish a connection. For Oracle and SQL Server, you select the mode of authentication, username, password, and host string. For Oracle and MSSQL, which allow table and column level permissions, library connections are made with whatever database permissions are available to the user making the connection. When using the read-write servers, if the permissions are not available for read-write access, the connection will revert to a read-only state. If a connection to the same database already exists, a message is displayed telling you to use the existing connection. In this case, the connection is not made. When making a library connection to a read-only Access library using the read-write
687
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 User name, Password, 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
3. Click OK to make the connection. Both SQL Server and Oracle require that the GeoMedias 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.
689
TypeLibrary connection type. LibraryLocation 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.
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.
690
Organizing Libraries
The Library Organizer command lets you copy the following objects between the active GeoWorkspace and a library attached to it: Catalog Connections Categories Legends Queries Queues Support for queues is limited to dynamic queues, which are displayed in the dialog box treeviews on the Library Organizer dialog box. Static queues are thus not displayed in these treeviews. Support for queues also includes support for subqueues. Subqueue objects are not individually selectable but always move in and out of libraries with their parent queues; thus, child subqueues are not displayed in the treeviews. All of the objects that can be copied are displayed on the Library Organizer dialog box in two treeviews. The Library contents treeview on the left shows the objects that reside in the library. The GeoWorkspace contents treeview on the right shows objects that reside in the active GeoWorkspace. The icon next to each object indicates the type of the object. You can thus easily browse and directly manipulate any of these objects and then copy the selected objects from the active GeoWorkspace to a read-write library or from a library to the active GeoWorkspace. You can select an individual or multiple objects for copy from both treeviews. After selecting the objects you want to copy, you use the left or right arrow buttons to perform the copy operation. Clicking the right arrow copies the checked 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. Searches Spatial Filters Styles Warehouse Connections
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
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
693
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
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
696
APPENDIX A
Phone Numbers
For general Intergraph information, please call 1.800.791.3357 (U.S.) or 001.256.730.2000 (international). For worldwide support, please contact your local Intergraph office (http://www.Intergraph.com/worldwide.aspx). For North American Phone Support, please call the appropriate number in the following table: Product Family Utilities and Communication FRAMME G/Technology InService Phone Numbers 1.877.463.1217 Additional Information Monday Friday 7:00 a.m. 7:00 p.m., CST Critical problems after 7:00 p.m. CST, weekends or holidays
697
Other Links
To submit sales inquiries, general questions, and comments, please visit our Contact Us Web page (http://www.intergraph.com/contact/default.aspx).
698
APPENDIX B
Read-Only Connections
To make a read-only connection to an Oracle warehouse, you must provide a valid Oracle connection string, which usually consists of an Oracle username, password, and net service name. Net service names are created using Oracles Net Configuration Assistant and reflect the database you are trying to connect to (the information is stored in the tnsnames.ora file. 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 Oracles native data model; no specific GeoMedia metadata information is required. There will be limits on what GeoMedia can interpret from existing spatial data, but metadata itself is not a requirement 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
Read-Write Connections
A read-write connection to an Oracle warehouse requires the same connection parameters as the read-only connection. However, read-write connections also require a metadata schema to be present in the Oracle database instance. The user for this schema must be called GDOSYS, and it can reside 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 GeoMedias GDOSYS Metadata Schema in this appendix.
Password Persistence
By default, GeoMedia stores the Oracle connection password in the GeoWorkspace. This is meant as a convenience and allows users to open existing GeoWorkspaces containing Oracle connections without having to re-enter connection passwords. However, this is a drawback to those users wanting higher levels of security. The option to turn off password persistence is in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\GDO\Oracle Object Read-Only\1.0\Store Password HKEY_LOCAL_MACHINE\SOFTWARE\GDO\Oracle Object Read-Write\1.0\Store Password The default setting is 1, which means that connection passwords will be stored. To force the user to enter a password for each Oracle connection, change the (default) setting to 0. Password persistence is not an issue if you are using Windows domain authentication for your connections.
Domain Authentication
Connections to Oracle based schemas can utilize either Oracle authentication (the default mode) or Windows domain authentication. To use Windows domain authentication, you need to first set some Oracle configuration parameters. In the SPFILE or the initialization file, INIT.ORA, you need to set the following: REMOTE_OS_AUTHENT=TRUE this enables remote authentication in the instance. OS_AUTHENT_PREFIX=<auth_prefix> this sets the prefix Oracle will use for domain authenticated user names. GeoMedia does not support the default prefix OPS$. You will need to choose a prefix that does not contain the $ character. 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
701
702
Point Orientation (10g Point Rotation Matrix or later) (deprecated) Linear straight line segments only Linear arcs only SpatialLine SpatialLine
703
SpatialArea
The following table identifies the mapping used when converting from GeoMedias geometry types to Oracle geometry types (applies only to data changes through the read-write data server). GeoMedia to Oracle Element Type Conversion GeoMedia Geometry Type SpatialPoint Orientation Matrix Orientation Matrix GraphicText SpatialLine Spatial Line (Arc) d001 d002 d002 Oracle Gtype d001 Oracle Etype 1 0 1 0 2 2 4 1003 2003 1005 2005 Oracle Interpretation 1 6000 0 6001 1 2 2 Oracle Meaning Point Application-defined 10g Point Orientation Application-defined Polyline Linear arcs only Linear straight line segments and arcs Exterior Ring Interior Ring Composite Exterior Ring Composite Interior Ring
704
In versions of Oracle prior to 10g, GeoMedia used its own format for oriented points. GeoMedias 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 supported 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
706
Raster Images
GeoMedia Professional has its own format for the storage of raster images and it also supports Oracle Spatial's GeoRaster format. Oracle's GeoRaster format, SDO_GEORASTER, was introduced in 10g. It is a component of Oracle spatial; you cannot use it with Oracle Locator. When using its own format, GeoMedia Professional stores rasters similar to the way it stores text. GeoMedia stores the footprint or MBR of raster images as polygon features and includes some additional information about the display matrix and the full path to the image filename. The actual raster image is not stored in the database and is retrieved through its filename. An example is as follows:
707
708
These default mappings may be overridden by GeoMedia client metadata tables. Unsupported 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.
709
710
711
Spatial Filtering
Spatial filtering is critical when using large datasets. The more limitations placed on the amount of data passed to the client, the better the performance will be. When using the Oracle, all spatial filtering initiated within GeoMedia is actually processed on the database server. This includes both the coarse first-pass filter and the finer second-pass filter. Attempting to use a spatial filter without having the required spatial indexes will result in the following error: Recordset is invalid. MORE: ORA-13226: Interface not supported without a spatial index. The spatial filter operators in GeoMedia Professional are mapped to the Oracle spatial filters in the following way (listed in order of performance):
712
Coarse Overlap is the fastest performing filter because it uses Oracles single pass SDO_FILT ER function, but the results may exceed the boundary of the filter area. This is the best filter to use when performance is the only consideration. The other three filters are treated as standard spatial queries with the filter area being passed to Oracles SDO_RELATE operator in a bind variable. SDO_RELATE uses a two-pass filter and produces 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 Oracles SDO_RELATE function. This is very similar to the spatial filter command except that, in this case, two feature classes are used as input. There are three main differences between the spatial querying capability in GeoMedia and that used by Oracle: 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 servers power for the processing stage. Distinct Results GeoMedias 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
714
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 user-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 2 Byte 3 Integer 4 - Long 5 - Currency 6 - Single 8 Date 10 - Text 11 - Binary 12 - Memo 15 - GUID 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 users schema. These identifiers are then used by other metadata tables. The definition of the table is:
INDEXID This field stores the unique identifier for every column in every table/view. The INDEXID is used as a reference by other metadata tables such as ATTRIBUTEPROPERTIES
716
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 user sees the GDOSYS.GALIATABLE, that user will require metadata for all tables that will be exposed as feature classes in GeoMedia. The definition of this table is:
TABLETYPE GeoMedias 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 users to have different GALIASTABLES (and, therefore, different metadata systems) is to have GALIASTABLE actually be a parameterized view of another table, with the view definition based on the user name so that each user sees different contents in the view.
GCOORDSYSTEM
GCOORDSYSTEM stores coordinate system definitions. If this table is not present, no coordinate system transformation will occur, and the GeoWorkspace coordinate system will be used. This table is not typically user editable because of the large number of columns and types of parameters required to define a coordinate system. There are four columns worth noting: CSGUID A special value used to uniquely identify the coordinate system parameters. The CSGUID is what associates a geometry object to a GeoMedia coordinate system. The CSGUID is also used in GEOMETRYPROPERTIES and in GFIELDMAPPING to associate the coordinate system with the SDO_GEOMETRY field. CSGUIDTYPE An indicator for whether the coordinate system is permanent or not. This is really used by the GeoMedia API. In the database table, it should always be set to 2. NAME The name the user has assigned to this coordinate system. It is an optional parameter but should be used because it makes the coordinate system easier to identify, particularly in the Oracle environment. DESCRIPTION An optional user-provided description of the coordinate system. The other attribute fields in GCOORDSYSTEM are not user editable and should not be modified in any way. 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
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:
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 3 AnySpatial 2 Area 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 user-provided description of the column. INDEXID This key field links the information to the actual column defined in the FIELDLOOKUP table.
718
GEXCLUSIONS
The GEXCLUSIONS metadata table is specific to the Oracle Object Model Data Server and is used to exclude schemas from the initial connection scan. When establishing an Oracle connection, any schema that the connected user has privileges to see will be scanned for compatibility. The more schemas that are available to the connected user, the longer the connection takes. This is one reason it is not recommended to connect as a user with the DBA role. The values in GEXCLUSIONS do not hide schemas from GeoMedia; they are only used to exclude schemas from the initial connection scan. If the table does not exist, the data server will assume a hard-coded list of Oracle schemas to exclude. If the table does exist, only those schemas listed in the table will be excluded. The default list of schemas to exclude if the table is not present is as follows: CTXSYS, MDSYS, OLAPSYS, ORDSYS, OUTLN, SH, SYS, SYSTEM, WMSYS, WKPROXY, WKSYS, and XDB. The definition of this table is:
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.
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 3 AnySpatial 2 Area 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 user-provided description of the column. The definition of the GFEATURES view is as follows:
719
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 2 Byte 3 Integer 4 - Long 5 - Currency 6 - Single 8 Date 10 - Text 11 - Binary 12 - Memo 15 - GUID 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
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 SpatialIndexLevel NumberOfTiles MaxLevel X_LowerBound X_UpperBound X_Tolerance Y_LowerBound Y_UpperBound Y_Tolerance Z_LowerBound Z_UpperBound Z_Tolerance Type Long Long Long Double Double Double Double Double Double Double Double Double Default GValue 1 1 1 -2147483648 2147483647 .00005 -2147483648 2147483647 .00005 -2147483648 2147483647 .00005 Comments Tessellation (Index) Level Maximum Number of Tiles Maximum Level (for Hybrid) X Minimum of MBR X Maximum of MBR X1=X2 if |X1-X2| < X_Tolerance Y Minimum of MBR Y Maximum of MBR Y1=Y2 if |Y1-Y2| < Y_Tolerance Z Minimum of MBR Z Maximum of MBR Z1=Z2 if |Z1-Z2| < Z_Tolerance
Although GVALUE values are strings, the types listed above are what the string is converted to during processing. If this table does not exist or does not have an entry in GALIASTABLE, the data server cannot create geometry fields. If the table exists, has an entry in GALIASTABLE, and is populated with at least every parameter except for the Z entries, then the geometry fields can be created and indexed. If Z parameters are absent, 2-D geometries are created. If Z parameters are present, 3-D geometries are created. The default coordinate system assigned to a schema is also listed here. The format for default coordinate system entries is as follows: GPARAMETER: <USER>.DEFAULTCOORDINATESYSTEM GVALUE: <CSGUID>
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 supported. 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 OWNER.PL_BUILDING OWNER.PL_STATE OWNER.PL_BUILDING VALUE FIELDNAME CODE_VALUE STATE_NAME CODE_VALUE DESCRIPTION FIELDNAME VAL_DESCRIPTION DESC VAL_DESCRIPTION BLD_TYPE = 'TYPE' FILTERCLAUSE
BLD_TYPE = 'NAME'
723
The Queued Edit process accesses GQUEUEBASE through a view called GQUEUE that is defined as follows:
724
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 user FROM DUAL) AND owner||'.'||object_name = TABLENAME); This view ensures that the user 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
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 USER_SDO_GEOM_METADATA. This can cause a problem if you are creating a new table using the same name as one previously deleted. You must manually clear the entry from Oracles metadata or define a trigger in the affected schema that will handle this automatically. An example of this trigger is as follows: CREATE or REPLACE TRIGGER DROP_USGM_TRIG AFTER DROP ON SCHEMA DECLARE v_EXIST INTEGER;
728
729
730
Tables
Tables can be created using GeoMedia Professionals Feature Class Definition or using native Oracle commands. The benefit of using Feature Class Definition is that the maintenance of the metadata is handled transparently. However, data types assigned via Feature Class Definition have to be converted to native Oracle data types. This is not the case if you create tables directly in Oracle. Using SQL, you can create spatial tables just like standard tables; the difference is that you include a column using the spatial 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 Oracles 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
732
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 GDOSYSs MODIFICATIONLOG table. Changes to the schema made outside GeoMedia Professional are not recorded. To make external changes visible to GeoMedia Professional while in a session, you need to set up modification triggers. These triggers are assigned to table-based feature classes using the GeoMedia Professional Database Utilities. The trigger name will be <FEATURE_CLASS>GMT. For example, the trigger on STATES would be STATESGMT. A single trigger handles the insert, update, and delete operations. If GeoMedia Professional detects the presence of the modification log triggers, it will use them rather than its own internal logging. The use of triggers may improve performance in editing operations because modification logging is being done by the server. Views pose a different kind of problem because normal triggers cannot be assigned to views. When a view is edited, Oracle is actually editing the underlying base table. GeoMedia will automatically log modifications for the view, but will not show an update for the base table unless a modification log trigger is created on the base table. Another issue arises when both the view and the base table are displayed on the legend in GeoMedia. If a change is made to the view and a modification log trigger is active on the base table, updates to the view will also cause an update on the base table. The changes will be immediately visible in the map window. If the base table is updated, the view will also be updated at the database level. GeoMedia will not be aware of that change and will not show it in the map window unless the warehouse is closed and re-opened. There are two ways to avoid this issue: You can add entries for the view to the base tables modification log trigger. These can be quite complicated to set up and requires knowledge of PL/SQL. They can also lead to a redundant entry for the view in the MODIFICATIONLOG table because both GeoMedia and the trigger will add an entry for the view. The best solution here is to create another trigger on the base table that uses the name of the view. For example, the trigger for STATES_VIEW would be called STATES_VIEWGMT. The trigger would fire for the base table STATES but would update the MODIFCATIONLOG table for the view. The trigger itself would be nearly identical to the base table's trigger STATESGMT, which would also fire. To do this, make a copy of the trigger used for the base table, rename it to reflect the view's name, and then change the references to the base table in the body of the trigger to reference the view instead.
Sequences
Another important use of triggers is to automatically utilize the sequence when using an integer-based primary key. GeoMedia will use the sequence automatically if the metadata 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
INSTEAD OF Triggers
INSTEAD OF triggers are special types of trigger used to maintain views, specifically join views. These triggers are nothing more than a PL/SQL procedure that uses the columns of the view as the input parameters. Using this type of trigger allows you to edit join views by managing the insert, update, and delete operations for the underlying base tables. This is the only way to have full read write access to join views. Remember, for inserts to be successful, GeoMedia must populate the primary key automatically. If the 'instead of' trigger populates the primary key, the insert will fail. Using GeoMedia Professional's Database Utilities, change the 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 join view using GeoMedia Professional, the software will first attempt to write directly to the view. If an INSTEAD OF trigger is available, the trigger will process the insert, update, or delete operation. If a trigger is not available, Oracle will attempt to write directly to the underlying tables. This may return an error result from Oracle. If you are using triggers to populate required fields, make sure you turn off the Copy Attribute Values from Previous Feature option.
Database Utilities
The Database Utilities tool consists of several utilities for managing and updating GeoMedia metadata in Access, Oracle, and SQL Server databases. These utilities are delivered with GeoMedia Professional and GeoMedia Web Map. These are DBA utilities and should not be used by normal database users. See the Database Utilities online Help for complete information on these utilities. You can access Database Utilities from Start > Programs > GeoMedia Professional > Utilities > Database Utilities. To use Database Utilities to create the GDOSYS schema, you will need to log in to Oracle as a DBA or system/manager to create and to populate the necessary GeoMedia metadata. For operations involving a specific schema, you can log in as the user who owns the schema if that user has full privileges on the GDOSYS metadata schema. If the GDOSYS schema does not exist in your Oracle database, you will need to create it before any of the commands will work. Use the Create Metadata Tables button to create and populate the GDOSYS schema. You will need to be connected as DBA for this to work correctly. This command is useful in two ways: 1) It creates metadata tables for native databases, and 2) it checks and repairs sparse metadata or updates metadata for new releases. Once the GDOSYS schema is created, you will not be prompted to create it again.
735
736
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.
737
738
APPENDIX C
Connections
GeoMedia applications require specific metadata tables to exist in the SQL Server database before connection. This metadata is created during the bulk import of data (from GeoMedia Professionals Export to SQL Server command) or by using GeoMedia Professionals Database Utilities. See the GeoMedia Metadata Requirements section of this appendix for a list of the required tables. To make a connection to SQL Server, provide a valid server name, and then a valid username and password. Any databases the specified user has privilege to see will appear in the drop down database list. SQL Server has two modes for validating users: Windows domain authentication and SQL Server authentication. If the SQL Server connection is set to use Windows authentication (the default), your domain login account will need to be added to SQL Server by a database administrator and appropriate privileges will need to be granted on the databases you want to access. On connection, you will only need to supply the server name and the database name. If you are using SQL Server authentication, you will need to have a valid SQL Server user account and password as well as the appropriate privileges on the database you want to connect to.
Password Persistence
When using SQL Server authentication, GeoMedia stores the SQL Server connection password in the GeoWorkspace. This is meant as a convenience and allows users to open existing GeoWorkspaces containing SQL Server connections without having to re-enter connection passwords. However, this is a drawback to those users wanting higher levels of security. If you do not want the passwords to be persisted in the GeoWorkspace, you must use domain
739
Permissions
In SQL Server warehouses, access to database objects is controlled by the objects owner through the use of permissions. GeoMedia requires all objects in your SQL Server database to be owned by a Database Owner (DBO). Objects that are not owned by DBO will not be accessible or visible in GeoMedia except by the user who created them. When creating database objects using GeoMedia Professionals Feature Class Definition command, the user account must be assigned the db_owner role. For database objects created outside of GeoMedia Professional, only a user account with the role db_owner will ensure that the resulting objects are owned by DBO. Users that need read access should be assigned the db_datareader role. Users that need write access should be assigned the db_datawriter role. All other specific SQL Server privileges are honored as long as the DBO ownership criterion is met.
740
741
*Memo only Date Integer if s = 0 and p < 6 Long if s = 0 and p >= 6 and p < 11 Double for all other cases. Double Long Currency Single Integer Byte Guid LongBinary
742
743
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 2 Byte 3 Integer 4 Long 5 Currency 6 Single 8 Date 10 Text 11 Binary 12 Memo 15 GUID 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 user-provided description of the column.
744
FieldLookup
The FieldLookup metadata table provides a unique identifier (IndexID) for every column in every table (feature class) in the users schema. The table definition is shown below:
IndexID This key column contains a unique identifier for every column in every feature class in the schema. It is populated using an identity increment. 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 user editable because of the large number of columns and types of parameters required to define a coordinate system. It should never be populated manually. There are three columns worth noting: Name The name the user has assigned to this coordinate system. It is an optional parameter, but it should be used because it makes the coordinate system easier to identify, particularly in the Oracle environment. Description A user-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
GeometryProperties
The GeometryProperties metadata table stores the geometry type, primary geometry flag, and the coordinate system ID for geometry columns contained by feature classes. The common link between this table and FieldLookup is the IndexID column. This table determines the coordinate system that is assigned to each feature class. The table definition is shown below:
IndexID This key field links the information to the actual column defined in the FieldLookUp table. PrimaryGeometryFlag A feature class can contain multiple geometry fields, but only one field is allowed to be primary. The primary geometry field is the field that allows for editing. A value of -1 means the geometry column is the primary geometry. All other geometry columns in the feature class should be assigned 0. Only one primary geometry field is allowed. GeometryType This field determines how the data server maps the geometry: 1 Line 3 AnySpatial 2 Area 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 user-provided description of the column.
746
GFeatures
The GFeatures metadata table stores the table names of all user tables (feature classes). By manipulating the tables listed here, you can make feature classes visible or invisible in GeoMedia. The table definition is shown below:
FeatureName This key column contains the name of the table that will be exposed as a feature class in GeoMedia applications. GeometryType This field determines how the data server maps the geometry. 1 Line 3 AnySpatial 33 GraphicsText 2 Area 4 Coverage 10 Point
-1 The feature class has no geometry field. PrimaryGeometryFieldName The name of the primary geometry column. FeatureDescription A user-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 2 Byte 3 Integer 8 Date 10 Text 11 Binary
747
7 Double 33 Graphic geometry DATA_SUBTYPE Used when the DATA_TYPE is 32 or 33; the subtype determines the graphic type: 1 Line 3 AnySpatial 2 Area 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:
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 supported. Only triggers can support notification in this case.
748
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
BLD_TYPE = 'NAME'
PL_Building CodeValue 0 1 2 3 4 PL_State StateName Alabama Arkansas Colorado Texas Florida Desc ALABAMA ARKANSAS COLORADO TEXAS FLORIDA ValDescription MOTEL MARRIOT HOLIDAY INN BED AND BREAKFAST DAYS INN Bld_Type TYPE NAME NAME TYPE NAME
750
GQueue
The GQueue metadata table is used to store the static queues for the Queued Edit command. The columns in GQueue are populated through commands in GeoMedia Professional and are used solely by the Queued Edit command. This table is not user editable. The table definition is provided for information only.
ModifiedTables
ModifiedTables is a join view that provides the object id for each table/view. The view uses an inner join between the sysobjects table and the sysindexes table in conjunction with a union. Do not modify or change this view. The ModifiedTableID in this view provides the values for the ModifiedTableID used in the ModificationLog table. This value is used to identify the edited table in the ModificationLog table. You should never modify this view yourself.
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
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 join views, you will need to take into account all the base tables and associated views. In the case of join views, most editing would be handled through instead of triggers. In this case, you could embed the insert into the ModificationLog table directly using the instead of trigger as long as the trigger name adheres to the rules listed above.
754
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-join definitions. For example, a row of your data consists of an auto-increment field called ID that contains the value 10, and there are 300 total records in this table such that max(ID)=300. If you accidentally delete this row and use the Undo command to get it back, ID will now be assigned the next available number in the auto-increment sequence, in this case 301. In all cases, the next available autonumber value will be obtained on an undo/redo operation; the previous autonumber value will not be preserved. This is actually by design; it is how Microsoft intends the auto-increment field to be used. This only occurs when using undo/redo operations on data in Access or SQL Server databases.
Default Values
Default values can simplify data entry and supply values for columns that are either required or just need to have a specific entry. Default values are honored by GeoMedia but not directly. When inserting a new record with the option to display the Attribute Properties dialog box turned on, the default values are not shown in the dialog box even though they are available at the database level. They will be used when the insert occurs. If the fields are required, you will not see an error; instead, the insert will pick up the default values. However, if the option Copy Attribute Values from Previous Feature is enabled, you will no longer be able to use the default value. Instead, the value used in the previous insert will be used. If you delete the previous value used in a required field, the default value will still not be used, and you will get an error message. For best results with defaults, either turn off the Copy Attribute Values from Previous Feature option or do not make the fields required. Functional-based defaults will work, but again, you must turn off the Copy Attribute option. This same problem will occur if you are using triggers to populate required fields.
Spatial Filtering
Spatial filtering is done in two passes. The first pass is a coarse filter that operates as a query on the server. The SQL Data Server uses a where clause on the four range (MBR) columns that acts as a coarse filter, for example: SELECT * FROM Parcels WHERE Geometry _XLO>22000 AND Geometry _YLO>44000 AND Geometry _XHI<88000 AND Geometry _YHI<62000 With simple spatial filters like Active Map Window Extent or Rectangular Fence, the actual coordinates of the filter area are used in the where clause. With complex polygon filters, as with all spatial filters, the data server gets the MBR of the filter geometry to compare with the MBR of the feature geometry in the where clause. This provides a coarse filter. The results from the first pass filter is passed to the client and processed locally. This second pass filter provides the final result. Because spatial filters make heavy use of the Geometry_XLO, Geometry_XHI, Geometry_YLO, and Geometry_YHI columns in queries, you may be able to improve spatial filter performance by indexing these columns in each of your feature classes.
756
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 administrator login such as sa or by any other user who has been assigned the db_owner role. For new databases, you will need to select the Create Metadata Tables command before any other GeoMedia operation can take place. This only needs to be done once per database. For tables or views created in SQL Server, use the Insert Feature Class Metadata command to add the metadata required to see these as feature classes in GeoMedia. To alter metadata already entered for existing feature classes, use the Edit Feature Class Metadata command. To delete the metadata for an existing feature class, use the Delete Feature Class Metadata command. This is also used if you need to make any DDL modification to tables or views. In this case, you would need to first delete the current metadata and then re-insert it after performing the DDL operation. 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; assigning an incorrect coordinate system can cause problems when editing. Make sure the correct coordinate system is assigned.
757
758
APPENDIX D
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
760
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 Intergraphs 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 Intergraphs clients, use or possession of the NTv2 or any part thereof. The Canadian National Transformation (version 2.0) has been adopted by the Intergovernmental Committee on Surveying and Mapping (ICSM) as the official high-accuracy transformation between the old Australian horizontal datums (AGD66 or AGD84, depending upon location) and the new official horizontal datum (GDA94). Grid files are published on the World Wide Web. The use of the Canadian National Transformation model for Australia has been included in the default entries in the autodt.ini configuration file. However, users will need to obtain the desired grid file from the Australian authorities, place it in the \cfg\canada folder, and edit the \cssruntm\cfg\canada\area.ini file to reference the grid file by name. The Canadian National Transformation (version 2.0) has also been adopted by the Intergovernmental Committee on Surveying and Mapping (ICSM) and Land Information New Zealand (LINZ) as the official high-accuracy transformation between the old (New Zealand) Geodetic Datum 1949 and the new official datum, New Zealand Geodetic Datum 2000. Grid files are published by LINZ and are available on the World Wide Web. The use of the Canadian National Transformation model for New Zealand has been included in the default entries in the autodt.ini configuration file. However, users will need to obtain the desired grid file from Land
761
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 Alaska Alaska: St. George Island Alaska: St. Lawrence Island Alaska: St. Paul Island Description Alaska, including Aleutian Islands Old island datum within Alaska Old island datum within Alaska O ld island datum within Alaska CONUS Hawaiian Islands Puerto Rico and V.I. Conterminous U.S. (lower 48 states) Old Hawaiian datum Puerto Rico and Virgin Islands conus hawaii prvi File Name alaska stgeorge stlrnc stpaul
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
763
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
765
766
767
768
769
770
Vertical Datums
You can reference and transform data between different vertical datums including ellipsoid-geoid conversion. Vertical datums may reference the geoid (orthometric height), the ellipsoid (geometric height), or be undefined. Geoid undulation is handled as a vertical datum transformation. Vertical datum information is carried with the definition of a coordinate system, through the user interface (for more information see the GMDefCoordSystem control sections), the programmer interface (for more information see the GeogSpace and CoordSystem sections), and the storage system (for more information see the GeogSpace and GDO specification section). The sections referred to are in the GeoMedia Object Reference Help. The following vertical datums are supported. The height type is orthometric for all cases, except where noted. Alicante Australian Height Datum 1971 Brazilian Vertical Datum (Imbituba) Cascais Canadian Vertical Reference 1928 Deutsches Haupthhennetz 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
1
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 User-defined (non-standard)
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 Airy 1830 Australian National Spheroid Average Terrestrial System 1977 Bessel 1841 Bessel 1841 (Namibia) Clarke 1858 (EPSG Definition) Clarke 1866 Clarke 1880 (Arc) Clarke 1880 (Benoit) Clarke 1880 (EPSG Definition) Clarke 1880 (IGN) Clarke 1880 (NGA Definition) Clarke 1880 (SGA 1922) Danish Everest (Brunei and East Malaysia 1967) also referenced as Everest 1830 (1967 Definition) Everest (Pakistan) Everest (Singapore and W. Malaysia 1948) - also referenced as Everest 1830 Modified Everest (West Malaysia 1969) Everest 1830 (1865 Indian Feet) Everest 1830 (1937 Adjustment) Everest 1830 (1956 Definition) Everest 1830 (1962 Definition) Everest 1830 (1975 Definition) Fischer 1960 (Mercury) Fischer 1968 GEM 10C 6377563.396 m. 6378160 m. 6378135 m. 6377397.155 m. 6377483.865 m. 6378293.639246834 m. 6378206.4 m. 6378249.145 m. 6378300.79 m. 6378249.138846127 m. 6378249.2 m. 6378249.145 m. 6378249.2 m. 6377104.43 m. 6377298.556 m. 299.3249646 298.25 298.257 299.1528128 299.1528128 294.2606763692611 294.9786982139058 293.4663077 293.4662345705142 293.4663076556299 293.4660212936294 293.465 293.46598 300 300.8017
6377309.613 m. 6377304.063 m.
300.8017 300.8017
772
Modified Airy - also referenced as Airy 6377340.189 m. Modified 1849 Modified Bessel Modified Fischer 1960 (South Asia) NWL 10D NWL 9D OSU86F OSU91A Plessis 1817 South American 1969 Struve Struve 1860 Unit Sphere User-defined (non-standard) War Office WGS60 WGS66 WGS72 WGS84 6378300.583 m. 6378165 m. 6378145 m. 6378135 m. 6378137 m. 6377492.0176 m. 6378155 m. 6378135 m. 6378145 m. 6378136.2 m. 6378136.3 m. 6376523 m. 6378160 m. 6378298.3 m. 6378297 m. 1 m.
773
774
Angular Units
Alias dd.mmss deg d:m d:m:s gr min rad rev sec UOM minutes seconds degrees degrees minutes seconds degrees degrees:minutes degrees:minutes:seconds grads minutes radians revolutions seconds Conversion Factor 0.000290888208665722 (rad/min) 0.00000484813681109536 (rad/sec) 0.0174532925199433 (rad/deg) See individual units. 0.0174532925199433 (rad/deg) See individual units. See individual units. 0.0157079632679490 (rad/gr) 0.000290888208665722 (rad/min) 1.0 6.28318530717959 (rad/rev) 0.00000484813681109536 (rad/sec)
Area Units
Alias ac ares centare chain^2 cm^2 deciare ft^2 hectare in^2 km^2 link^2 m^2 mi^2 UOM acres ares centares square chains square centimeters deciares square feet hectares square inches square kilometers square links square meters square miles Conversion Factor 4046.8564224 (m^2/ac) 100.0 (m^2/are) 1.0 (m^2/centare) 404.68564224 (m^2/chain^2) 0.0001 (m^2/cm^2) 10.0 (m^2/deciare) 0.09290304 (m^2/ft^2) 10000.0 (m^2/hectare) 0.00064516 (m^2/in^2) 1000000.0 (m^2/km^2) 0.040468564224 (m^2/link^2) 1.0 2589988.110336 (m^2/mi^2)
775
776
777
778
779
UTM Zones
Zone 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 Meridian 177W 171W 165W 159W 153W 147W 141W 135W 129W 123W 117W 111W 105W 99W 93W 87W 81W 75W 69W 63W 57W 51W 45W 39W 33W 27W 21W 15W 9W 3W Longitude Range 180W-174W 174W-168W 168W-162W 162W-156W 156W-150W 150W-144W 144W-138W 138W-132W 132W-126W 126W-120W 120W-114W 114W-108W 108W-102W 102W-96W 96W-90W 90W-84W 84W-78W 78W-72W 72W-66W 66W-60W 60W-54W 54W-48W 48W-42W 42W-36W 36W-30W 30W-24W 24W-18W 18W-12W 12W-6W 6W-0 Zone 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 Meridian 9E 15E 21E 27E 33E 39E 45E 51E 57E 63E 69E 75E 81E 87E 93E 99E 105E 111E 117E 123E 129E 135E 141E 147E 153E 159E 165E 171E 177E Longitude Range 6E-12E 12E-18E 18E-24E 24E-30E 30E-36E 36E-42E 42E-48E 48E-54E 54E-60E 60E-66E 66E-72E 72E-78E 78E-84E 84E-90E 90E-96E 96E-102E 102E-108E 108E-114E 114E-120E 120E-126E 126E-132E 132E-138E 138E-144E 144E-150E 150E-156E 156E-162E 162E-168E 168E-174E 174E-180E
780
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 Supported 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 supported.
Oracle GeoRasters
Typical Extension: N/A Compression Techniques: Any compression methods supported 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 supported 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
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
Format CCITTG4 JPEG Description Consultative Committee on International Telephone and Telegraph Group 4 format is standard for transmission and storage of bilevel facsimile images. Joint Photographic Experts Group format uses a block-by-block conversion to frequency space and stores a discrete cosine series representation of the frequency space. Lempel-Ziv & Welch algorithm compresses binary, grayscale, or color data. This method was not used for a time because of patent and licensing issues.
LZW
786
Raster Information
Format LZ77 PB Description 1977 version of Lempel-Ziv compression. Commonly called the Deflate algorithm. Similar to LZW in compression speed and size performance. 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. 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. Vector quantization. Defined in MIL-STD-188-199. An algorithm for grayscale and color data. Used by MrSID, ECW, and JPEG2000 format images. Similar to LZW, it was developed as a legal replacement for LZW.
RLE
VQ Wavelet ZIP
Tiling
Format Tiling Description 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
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
789
790
791
792
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.
793
Conversion Tables
794
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 user 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.
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.
795
Catalogs: Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers
ctable.sqlcreates all tables in the Catalog schema owner (user name). cindex.sqlCreates all indexes. crel.sqlCreates foreign key relationships. cscd.sqlCreates triggers and sequences.
Other: Oracle SQL*Plus and SQLNet installed on the client machine Oracle database instance System password 1. Start SQL*Plus, and log in to the database as a user with database administrator permissions. 2. Run the ora.sql script, and type @some_path\ora.sql, where some_path is the path to the ora.sql file). Include the entire path, for example: SQL> @c:\ora.sql 3. Follow the SQL prompts to create the database. You will be prompted for the following: Enter the name of the schema that will be created. This is the name of the Oracle schema that will be created when the script is run. Enter the name of the default tablespace used by the schema . All objects created by the script will live in this tablespace. It must exist before the script is run. Enter the name of the temporary tablespace used by the schema. This is the tablespace used for the schema's temporary segments. It must exist before the script is run. 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 password of the new Catalog database is the same as the user name. 4. After the script has run, a log file will be generated. The log file is named SMMSOracle.logand is placed in your Temp folder as defined by the TEMP User environment variable. This directory is typically found at <System Drive Letter>:\Documents and Settings\<User Name>\Local Settings\Temp on Windows XP systems. Review this file for errors. With GeoMedia Catalog and Oracle, you may only log in to the database as the database owner. Read-only and read-write users are not supported.
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 user connection test before completing the Oracle service configuration process. 12. Accept the Net Service name, or enter a new one. 13. Click Next. 14. Click Next. 15. When you are finished, click Next; then click Finish.
3. Click Add.
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 User ID. Select the remaining settings, following your organization's Oracle protocol. If the Oracle 9i client is configured on the system, select the Workaround tab at the bottom of the ODBC Oracle Driver Configuration dialog box, and be certain to check the Set Metadata Id Default to SQL_True check box. It is recommended that you verify the ODBC connection by clicking the Test Connection button. Click OK when you are finished.
798
Catalogs: Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers
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.
2. 3. 4. 5.
The status of the export for the selected records is displayed in the status bar, the selected catalog records are exported, and the files are stored in the destination folder.
7. Use ODBC Data Source Administrator to remove the DSN you created by using the older version ODBC driver for Oracle or MS-SQL Server. 8. Uninstall the current version of your server database. 9. Install the new version of your server database. 10. Use either the Intergraph Oracle or the MS-SQL Server Catalog database scripts to create the required metadata database tables and related database configuration. 11. Create a new DSN using a compatible version of the Oracle or MS-SQL Server ODBC driver.
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.
800
Catalogs: Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers
Quick Steps
The following are the basic steps for installing an MS-SQL Server Catalog database: 1. Create a SQL database. 2. Run the MS-SQL Server Scripts as Administrator. These scripts are in the Scripts\SqlCatalogScripts folder of GeoMedia and GeoMedia Professional. 3. Create user accounts. 4. Set user permissions. 5. Create an ODBC connection for clients. 6. Create a new Catalog connection.
The database is created and configured for use with GeoMedia. Now you are ready to create users.
801
Catalogs: Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers
802
Catalogs: Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers
5. In the Database User Properties dialog box, in the Object column, starting with the table AT and ending with User_Defined, choose the Select, Insert, Update, Delete, and DRI options for each table. 6. 7. Ignore objects that have the owner Information Schema. Click Execute for the IsReadOnly, IsThesaurusKeywordAdmin, and ISWebPublishAdmin stored procedures. Finally, you must decide whether or not to provide read-write permission to two Catalog features which are generally reserved for administrative-level personnel: the Thesaurus/Keyword Admin and Web Publish features of the GeoMedia Catalog. The Thesaurus Keyword Admin tool allows the user to create and edit organizational keyword lists within the Catalog. The Web Publish feature allows the user to manually provide or block Web search access to Catalog records using Intergraph Catalog server applications in GeoMedia WebMap. As the permissions are set, the user will have access to these features. If you want to change the permissions, do the following: If you want to deny the user read-write access to the Thesaurus Keyword Admin tool, deselect the Insert, Update, and Delete permissions on the table ID_Thesaurus_Lookup. If you want to deny the user read-write access to the GeoMedia Catalog Web Publish feature, deselect the Insert, Update, and Delete permissions on the table ID_Web_Publish. Click Apply. Click OK.
8. 9.
Ignore objects that have the owner Information Schema. 6. Click Execute for the ISReadOnly, ISThesaurusKeywordAdmin, and ISWebPublishAdmin stored procedures. 7. Click Apply when you are finished.
803
Catalogs: Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers
The second wizard screen opens, allowing you to select a method of authentication when a GeoMedia Catalog user attaches to the MS-SQL Catalog database.
10. Choose the With SQL Server authentication using a login ID and password entered by the user option, and enter a valid Login ID below. Leave the Password field blank. Reminder: These steps are intended to outline a typical configuration. Your MS-SQL protocol may differ. 11. Click Next. 12. Click Change the default database to, and select the MS-SQL Catalog database from the drop-down list. 13. Click Next.
804
Catalogs: Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers
805
Catalogs: Installing, Setting Up, and Upgrading Oracle and MS-SQL Servers
806
APPENDIX I
Overview
Data for Transportation Asset systems (using dynamic segmentation) generally falls into two categories: LRS data and Event data. LRS data describes the naming, measurement system, and geometry of the linear network. Event data describes attributes of the linear network, such as pavement conditions, roadway inventory data (for example, guardrails and signage), and accident occurrences. This software provides great flexibility in the structuring of both of these data types, as shown below: LRS Data Structure Options Measure Measure with Internal Markers Measure with External Measure Markers Duration Duration with Internal Markers Duration with External Measure Markers Event Data Structure Options Measure Marker Offset Coordinate Duration
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 t he Working with GeoMedia Transportation document.
807
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
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".
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. 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. 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. This is the measurement value for the beginning position of this feature. This is the measurement value for the ending position of this feature. This field contains the linear geometry that describes the linear segment geometrically. 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).
808
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 t he sample shown is an ID code for Orange County.
BeginMeasure
EndMarker
BeginMarker
EndMeasure
Direction of Segment
LRS Feature Class Field PrimaryKey Sample US Description The LRS key fields identify the "route" that this segment of the LRS belongs to. This identification can be done with anywhere from 1 to 4 fields within the LRS feature class. These fields are the same fields the event features will use to identify the "route". In the sample shown PrimaryKey identifies the roadway system, SecondaryKey contains the route number, TertiaryKey identifies whether the segment is part of a spur, and QuatenaryKey identifies whether this segment is part of an alternative route. All together the route name is "US6SA". SecondaryKey 6 TertiaryKey S 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. 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. 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. This is the measurement value for the beginning position of this feature. This is the measurement value for the ending position of this feature.
809
RegionID
ORA
BeginMeasure
Marker
Marker
LRS Feature Class Field PrimaryKey Sample US Description The LRS key fields identify the "route" that this segment of the LRS belongs to. This identification can be done with anywhere from 1 to 4 fields within the LRS feature class. These fields are the same fields the event features will use to identify the "route". In the sample shown PrimaryKey identifies the roadway system, SecondaryKey contains the route number, TertiaryKey identifies whether the segment is part of a spur, and QuatenaryKey identifies whether this segment is part of an alternative route. All together the route name is "US6SA". SecondaryKey 6 This is the 2nd key field that can be used to identify the "route" that this segment of the LRS belongs to. Its use is optional.
810
RegionID
ORA
PrimaryKey
US
811
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
LRS Feature Class Field PrimaryKey Sample US Description The LRS key fields identify the "route" that this segment of the LRS belongs to. This identification can be done with anywhere from 1 to 4 fields within the LRS feature class. These fields are the same fields the event features will use to identify the "route". In the sample shown PrimaryKey identifies the roadway system, SecondaryKey contains the route number, TertiaryKey identifies whether the segment is part of a spur, and QuatenaryKey identifies whether this segment is part of an alternative route. All together the route name is "US6SA". SecondaryKey 6 TertiaryKey S 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. 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. 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. This is the measurement value for the beginning position of this feature. This is distance value from the beginning position to the ending position of this feature. This field contains the linear geometry that describes the linear segment geometrically. 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. 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.
QuatenaryKey A BeginMeasure 12.3 Duration Geometry Geometry Reversed 5.9 blob True
RegionID
ORA
812
BeginMeasure
EndMarker
BeginMarker
LRS Feature Class Field PrimaryKey Sample US Description The LRS key fields identify the "route" that this segment of the LRS belongs to. This identification can be done with anywhere from 1 to 4 fields within the LRS feature class. These fields are the same fields the event features will use to identify the "route". In the sample shown PrimaryKey identifies the roadway system, SecondaryKey contains the route number, TertiaryKey identifies whether the segment is part of a spur, and LRSkey4 identifies whether this segment is part of an alternative route. All together the route name is "US6SA". SecondaryKey 6 TertiaryKey S 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. 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. 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. This is the measurement value for the beginning position of this feature. This is distance value from the beginning position to the ending position of this feature. This field stores a name for the beginning position of this feature. This field stores a name for the ending position of this feature. Its use is optional. This field contains the linear geometry that describes the linear segment geometrically.
QuatenaryKey A BeginMeasure 12.3 Duration BeginMarker EndMarker Geometry 5.9 M45 M46 blob
813
RegionID
ORA
BeginMeasure
Marker
Marker
LRS Feature Class Field PrimaryKey Sample US Description The LRS key fields identify the "route" that this segment of the LRS belongs to. This identification can be done with anywhere from 1 to 4 fields within the LRS feature class. These fields are the same fields the event features will use to identify the "route". In the sample shown PrimaryKey identifies the roadway system, SecondaryKey contains the route number, TertiaryKey identifies whether the segment is part of a spur, and QuatenaryKey identifies whether this segment is part of an alternative route. All together the route name is "US6SA". SecondaryKey 6 TertiaryKey S 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. 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. 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.
QuatenaryKey A
814
RegionID
ORA
Marker Feature Class Field PrimaryKey Sample US Description The LRS key fields identify the "route" that this segment of the LRS belongs to. This identification can be done with anywhere from 1 to 4 fields within the LRS feature class. These fields are the same fields the event features will use to identify the "route". In the sample shown PrimaryKey identifies the roadway system, SecondaryKey contains the route number, TertiaryKey identifies whether the segment is part of a spur, and QuatenaryKey identifies whether this segment is part of an alternative route. All together the route name is "US6SA". SecondaryKey TertiaryKey QuatenaryKey MarkerName 6 S A M34 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. 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. 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. This is the identifying name of the marker. This is the measurement value at the marker.
MarkerMeasure 17.5
815
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 PrimaryKey Sample US Description The LRS key fields identify the "route" that this segment of the LRS belongs to. This identification can be done with anywhere from 1 to 4 fields within the LRS feature class. These fields are the same fields the event features will use to identify the "route". In the sample shown PrimaryKey identifies the roadway system, SecondaryKey contains the route number, TertiaryKey identifies whether the segment is part of a spur, and LRSkey4 identifies whether this segment is part of an alternative route. All together the route name is "US6SA". SecondaryKey TertiaryKey QuatenaryKey BeginMeasure EndMeasure 6 S A 14.4 16.2 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. 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. 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. This is the measurement value for the beginning position of this event. This field is required for both point and linear events. This is the measurement value for the ending position of this event. This field is used for linear events only.
816
Event Feature Class Field PrimaryKey Sample US Description The LRS key fields identify the "route" that this segment of the LRS belongs to. This identification can be done with anywhere from 1 to 4 fields within the LRS feature class. These fields are the same fields the event features will use to identify the "route". In the sample shown PrimaryKey identifies the roadway system, SecondaryKey contains the route number, TertiaryKey identifies whether the segment is part of a spur, and QuatenaryKey identifies whether this segment is part of an alternative route. All together the route name is "US6SA". SecondaryKey TertiaryKey QuatenaryKey BeginMarker 6 S A M34 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. 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. 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. 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. 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. 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. This is distance value from the End Marker to the ending position of this event. This field is used for linear events only.
BeginOffset
0.6
EndMarker EndOffset
M35 0.4
817
Option 3 - Coordinates
The events in this option are defined by a set of up to four LRS keys to name the route, a begin X/Y or Longitude/Latitude coordinate, and for linear events only, an end X/Y or Longitude/Latitude coordinate.
X,Y
Event Feature Class Field PrimaryKey Sample US Description The LRS key fields identify the "route" that this segment of the LRS belongs to. This identification can be done with anywhere from 1 to 4 fields within the LRS feature class. These fields are the same fields the event features will use to identify the "route". In the sample shown PrimaryKey identifies the roadway system, SecondaryKey contains the route number, TertiaryKey identifies whether the segment is part of a spur, and QuatenaryKey identifies whether this segment is part of an alternative route. All together the route name is "US6SA". SecondaryKey TertiaryKey QuatenaryKey BeginX BeginY EndX EndY 6 S A 2546234.2 753124.4 2584123 745654.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. 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. 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. This is the X or Longitude coordinate for the beginning position of this event. This field is required for both point and linear events. This is the Y or Latitude coordinate for the beginning position of this event. This field is required for both point and linear events. This is the X or Longitude coordinate for the ending position of this event. This field is used for linear events only. This is the Y or Latitude coordinate for the ending position of this event. This field is used for linear events only.
818
Option 4 - Duration
The events in this option are defined by a set of up to four LRS keys to name the route, a begin measure, and a duration (length) value. The Duration option applies to linear events only.
Event Feature Class Field PrimaryKey Sample US Description The LRS key fields identify the "route" that this segment of the LRS belongs to. This identification can be done with anywhere from 1 to 4 fields within the LRS feature class. These fields are the same fields the event features will use to identify the "route". In the sample shown PrimaryKey identifies the roadway system, SecondaryKey contains the route number, TertiaryKey identifies whether the segment is part of a spur, and QuatenaryKey identifies whether this segment is part of an alternative route. All together the route name is "US6SA". SecondaryKey TertiaryKey QuatenaryKey BeginMeasure Duration 6 S A 14.4 1.8 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. 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. 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. This is the measurement value for the beginning position of this event. 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
820
APPENDIX J
Discussion
An SVG document is created according to the standard W3C SVG specifications, which allow support for certain attributes and elements to make parametric behavior easier. The following are the major sections of an SVG document relevant to symbol usage: XML version and encoding - A standard XML header. This header is not required. Whether the header is provided or not, UTF-8 encoding is always assumed. Reference namespaces - Identify namespaces in use within the document. If GeoMedia-structured symbol parameters are to be used, the gmsvgsym namespace must be referenced. For more information, see the Metadata Element section of this appendix. SVG - This root element for the document holds the sections for metadata (metadata), graphics definitions (symbol), and drawing objects (use). Metadata - May include the GeoMedia SVG Symbol Metadata extension. For more information, see the Metadata Element section of this appendix. Symbol - Contains symbols definitions. This section is used to segregate symbol definitions from actual drawing requests. Use - Specifies actual use of a symbol definition at a particular coordinate location for visualization within an SVG viewer. This element is not required by GeoMedia's SVG interpreter, but it is required by SVG viewers. The symbol section contains the actual symbol definitions. Symbols may be composed of various SVG geometry elements. The following elements are supported by the GeoMedia SVG Symbol Server: svg symbol use g metadata line polyline polygon rect circle ellipse path text
The nature of these elements, the attributes of these elements, and the components of those attributes are discussed in the following discussion. Elements in the SVG file other than these are ignored.
821
Supported Types
Refer to the W3C SVG specifications for further details on each element.
General Elements
As a general rule, if elements contain other elements, the contained elements (components) inherit information defined on the container element (composite). One of the more common uses of this inheritance is with styles. A characteristic of a style can be inherited from the symbol, group, use, and like elements. As with any inheritance, inherited values from the composite can be overwritten by values set on the component.
SVG Element
The <svg> element is the root for the SVG-structured contents to follow. The attributes of the SVG element that will be supported are as follows: Attribute xmlns xmlns:xlink Value "http://www.w3.org/2000/svg (http://www.w3.org/2000/svg)" "http://www.w3.org/1999/xlink (http://www.w3.org/1999/xlink)" Description Defines the default namespace of the XML document. Defines the xlink namespace and sets it to the xlink prefix. It is only required if someone uses the namespace. Defines the namespace for SVG elements. This is not required if SVG namespace is the default.
xmlns:svg
"http://www.w3.org/2000/svg (http://www.w3.org/2000/svg)
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"> </svg>
Symbol Element
The <symbol> element is used to logically collect elements together to form a symbol. It is much like a <g> element, with the exception that a symbol does not render. To use a symbol element
822
id
String
style
Font, stroke, and fill characteristics supported. 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.
transform
Varies
The attribute is not required. See the Transform Attribute section for details.
The following is an example of a symbol element: <symbol id="RoadShield" viewBox="0 0 500 500" style="font-size:50;font-family:Arial"> </symbol>
Use Element
The <use> element is used to define which symbols to actually use in an SVG display. The user specifies a URI in an xlink:href attribute and specifies the x and y location where the item's (0,0) point should be moved to. This component is not used by the GeoMedia symbol interpreter, and if included as a part of the symbol definition, it will be ignored. The following is an example of a use element: <symbol id="RoadShield" viewBox="0 0 500 500" style="font-size:50;font-family:Arial"> </symbol> <use xlink:href="#RoadShield"/>
823
G Element
The <g> element gathers all of its child elements as a group and has an id attribute to give that group a unique name. Attribute id style transform Value String Font, stroke, and fill characteristics supported. Varies Description The identifier for the element. Not required. The attribute is not required. See the Style Attribute section for details. The attribute is not required. See the Transform Attribute section for details.
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 supported, and all other attributes will be ignored. Attribute x1 y1 x2 y2 id style transform Value X start point Y start point X end point Y end point String Stroke characteristics supported. Varies Description The x value for the start point of the line. No units can be given with the value. The y value for the start point of the line. No units can be given with the value. The x value for the end point of the line. No units can be given with the value. The y value for the end point of the line. No units can be given with the value. The identifier for the element. Not required. The attribute is not required. See the Style Attribute section for details. The attribute is not required. See the Transform Attribute section for details.
The following is an example of a line element: <line id="Line1" x1=100" y1=50 x2=320 y2=240 style="stroke -width:1; stroke-linecap:round; stroke:#e1e100; fill:none;"/>
id style transform
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
Rect Element
The following section defines the attributes of a rect element. These are the only attributes supported, and all other attributes will be ignored. Attribute x Value x-upper-left Description 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. 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. The width of the rectangle, which must be a positive value. No units can be given with the value. The height of the rectangle, which must be a positive value. No units can be given with the value. The identifier for the element. Not required. The attribute is not required. See the Style Attribute section for details. The attribute is not required. See the Transform Attribute section for details.
y-upper-left
transform
The following is an example of a rect element: <rect id="Rectangle1" x=20 y=20 width=100 height=50 style="stroke-width:2; stroke:#e1e100; fill:#ff00ff;"/>
Circle Element
The following section defines the attributes of a circle element. These are the only attributes supported, and all other attributes will be ignored. Attribute cx cy r id style Value X center Y center Radius String Stroke and fill Description The horizontal coordinate of the center of the circle. No units can be given with the value. The vertical coordinate of the center of the circle. No units can be given with the value. The radius of the circle, which must be positive. No units can be given with the value. The identifier for the element. Not required. The attribute is not required. See the Style Attribute
826
The following is an example of a circle element: <circle id="Circle1" cx=20 cy=20 r=10 style="stroke-width:2; stroke:#e1e100; fill:#ff00ff;"/>
Ellipse Element
The following section defines the attributes of an ellipse element. These are the only attributes supported, and all other attributes will be ignored. Attribute cx cy rx Value X center Y center X Radius Description The horizontal coordinate of the center of the circle. No units can be given with the value. The vertical coordinate of the center of the circle. No units can be given with the value. The radius of the ellipse along the x-axis, and the radius value must be positive. No units can be given with the value. The radius of the ellipse along the y-axis, and the radius value must be positive. No units can be given with the value. The identifier for the element. Not required. The attribute is not required. See the Style Attribute section for details. The attribute is not required. See the Transform Attribute section for details.
ry
Y Radius
id style
transform
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 supported, and all other attributes will be ignored. Attribute d Value Description The set of flags and coordinates that describe the path being drawn. No units can be given with the value. See the D Attribute section for details String Stroke and fill characteristics supported. Varies The identifier for the element. Not required. The attribute is not required. See the Style Attribute section for details. The attribute is not required. See the Transform Attribute section for details.
id style transform
D Attribute
The d attribute is used in the context of the path element. The following describes the format of the d attribute. If the characteristic is uppercase, the position values are absolute, but if the characteristic is lowercase, the position values are relative to the current point. d Characteristics M Value x1,y1 Description Sets the current location to a value defined by the x1, y1 parameters. The M characteristic is like a move to command. 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. Draws a line from the current point to x1, y1. Draws a line from the current point to the pointed defined by the offset values of dx1, dy1. 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. 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.
dx1,dy1
L l A
828
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 supported, and all other attributes will be ignored. Attribute x y text-anchor Value x-upper-left y-upper-left start, middle, or end String Description The horizontal coordinate of the upper-left point of the text. No units can be given with the value. The vertical coordinate of the upper-left point of the text. No units can be given with the value. The text-anchor attribute controls the horizontal location of the anchor point. This is a left, center, or right alignment for the text at the x and y origin. The identifier for the element. Not required.
id style
Font, stroke, and fill The attribute is not required. See the Style Attribute section for details. characteristics supported. Varies The attribute is not required. See the Transform Attribute section for details.
transform
The following is an example of a text element: <text id="Text1" x=20 y=20 style="font-size:10;font-family:Arial"> Here is the text </text>
Common Attributes
Style Attribute
SVG specifies the presentational aspects of graphic elements using inline styles. We set the value of the style attribute to a series of visual properties, and their values as described in the following sections. The format of a style attribute is stylecharacteristic1:value;stylecharacteristic2:value2; . An example would be: style=stroke:#e1e100;stroke-width:1;stroke-opacity:0.5;. For more information refer to the W3C specification. Stroke Characteristics: Lines are considered to be strokes of a pen drawn to a canvas. The size, color, and style of the pen stroke are considered to be part of the line's presentation.
829
stroke-width stroke-dasharray
stroke-opacity
Stroke opacity
stroke-linejoin
miter, bevel, Specifies the shape of the corners of a polygon or or round series of lines. There are three types supported, which are listed in the value column. butt, round, or square Specifies an end cap of a line. There are three types supported, which are listed in the value column.
stroke-linecap
Fill Characteristics: Specifies the way in which the interior of a shape is to be filled. Fill Characteristics fill Value Fill color Description Specifies the fill color for closed symbols like boundaries and complex strings. The color value supported is RGB-encoded using two hexadecimal digits per primary-color component, in the order Red, Green, Blue, prefixed with a hash (#) sign. For example, full red is encoded as #ff0000 (with no quotation marks). Note that this is the only format supported. The exception is the word none, which implies an opacity value of 0. 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
fill-rule
nonzero or even-odd
830
Font Characteristics: Specifies the way that text will be drawn. Font Characteristics font-size font-family Value Size of font Family name Description The property is the size of the font. User units (points) are assumed, and no other units are supported. The generic family names are serif, sans-serif, and monospace. Also supported are the standard fonts available on the system. There are two types of font styles that are supported, which are listed in the value field. There are two types of font weights that are supported, which are listed in the value field.
font-style font-weight
831
none, There are three types of text decorations that are underline, or supported, which are listed in the value field. line-through
Transform Attribute
The value of the transform attribute is a <transform-list>, which is defined as a list of transform definitions which are applied in the order provided. The individual transform definitions are separated by white space and/or a comma. The available types of transform definitions include the following: Transform Characteristics matrix Value Description
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(< Specifies a translation by tx and ty. If <ty> is not provided, tx> [<ty>]) it is assumed to be 0. 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(<rot ate-angle> [<cx> <cy>]) Specifies a rotation by <rotate-angle> degrees about a given point. If optional parameters <cx> and <cy> are not supplied, the rotate is about the origin of the current user coordinate system. The operation corresponds to the matrix [cos(a) sin(a) -sin(a) cos(a) 0 0]. If optional parameters <cx> and <cy> are supplied, the rotate is about the point (<cx>, <cy>). The operation represents the equivalent of the following specification: translate(<cx>, <cy>) rotate(<rotate-angle>) translate(-<cx>, -<cy>).
skewX skewY
skewX(ske Specifies a skew transformation along the x-axis. w-angle) skewY(ske Specifies a skew transformation along the y-axis. w-angle)
All numeric values are real numbers. If a list of transforms is provided, the net effect is as if each transform had been specified separately in the order provided. For example, <g transform="translate(-10,-20) scale(2) rotate(45) translate(5,10)"> <!-- graphics elements go here --> </g> is functionally equivalent to: <g transform="translate(-10,-20)"> <g transform="scale(2)"> <g transform="rotate(45)"> <g transform="translate(5,10)"> <!-- graphics elements go here -->
832
The XML schema definition references the following external schema definition:
833
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: <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="http://www.intergraph.com/GeoMedia/svgsym" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:gmsvgsym="http://www.intergraph.com/GeoMedia/svgsym"> <xs:simpleType name="VersionType"> <xs:restriction base="xs:string"> <xs:enumeration value="1.0"/> </xs:restriction> </xs:simpleType> <xs:element name="symbolParameters"> <xs:annotation> <xs:documentation>A set of parameters used to control the contents of SVG symbols via style properties</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="textContent" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>A symbol parameter that replaces the text content of a text element with the value of a style property</xs:documentation> </xs:annotation> <xs:complexType> <xs:attribute name="replaceID" type="xs:string" use="required"/> <xs:attribute name="styleProp" type="xs:string" use="required"/> </xs:complexType> </xs:element> </xs:sequence> <xs:attribute name="version" type="gmsvgsym:VersionType" use="optional" default="1.0"/> </xs:complexType> </xs:element> </xs:schema>
Example
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.0//EN" "http://www.w3.org/TR/SVG/DTD/svg10.dtd"> <svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:gmsvgsym="http://www.intergraph.com/GeoMedia/svgsym"> <!--Added the following metadata for text replacement in example Symbol_1--> <metadata> <gmsvgsym:symbolParameters gmsvgsym:version="1.0">
836
837
838
APPENDIX K
Functional Overview
The following diagram shows the basic operations involved with address geocoding when using the AGI geocoding engine:
839
Architectural Overview
To better depict the various processes involved with the architecture in more detail, these processes are described using separate sections and diagrams.
Address Transformations
The parsing rules file contains rules for transforming a single string into several fields. Often the address is defined by two or even more strings. The address transformation contains a set of Address Parsing Rules that provides a way to transform addresses from one (source) format to another (target) format. Both source and target formats can consist of multiple strings. The address transformations provide a way to transform addresses from different source formats to the same target format.
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 user 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
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 Street Name Example Main Street Address Elements Directional Prefix Street Name Street Type Street Type Suffix City State Postcode User Input Street Address MILTONS Queensland 4064 Example 1299 Main Street City State PostalCode Address Elements House Number Directional Prefix Street Name Street Type Street Type Suffix City State Postcode MILTONS Queensland 4064 City State PostalCode Miltons QLD 4064 Main Street Miltons QLD 4064 Example 1299 Main Street Example
843
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 supported by the desktop GeoMedia Find Address and Geocode Addresses commands.
845
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 componentsGenerate datasets for geocoding and reverse geocoding. Geocoding Model componentsGenerate rules for performing geocoding according to dataset address configuration, input data configuration, and locale-specific addressing rules. Address Transformation componentsDescribe the schema of incoming or outgoing addresses, both the elements of the addresses and their storage normalization. Geocoding componentsPerform geocoding using input address elements already parsed and transformed into the format required for the dataset. Reverse Geocoding componentsPerform 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 user-recognizable address components (or fields) and their correlation to the various elements of an address, that is, a comprehensive description of address elements that make up a particular address structure. This includes suggested field names that can be used by a graphical user interface to help one match up database fields to the address component fields. Fields may be represented by either database fields in a recordset or data entry/readout controls on a user interface.
848
849
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.
850
851
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-joined street name + left/right City + State + left/right ZIP (for example, E + Main + ST + Madison + AL + 12345). (This was used with Northeast Mississippi sample dataset by Mark on GSW.) Re-joined street name is supposed to consists of prefix, name, type, and suffix. These values are concatenated and parsed with the US_street.xml parsing rules.
852
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
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
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
US_Post_c.xml
This file contains parsing rules for US post addresses. It supports intersections, recognized PO Boxes, Rural Routes, phone numbers, and secondary unit designators. Sample text recognized by the rules: 1000 AVENUE E 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
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 supports intersections, recognized PO Boxes, Rural Routes, phone numbers, and secondary unit designators. It is identical to US_Post_c.xml but does not output the City and State names (if any).
US_ZIP.xml
This file contains parsing rules for US ZIP codes. It is used by the US_Post.xml and US_Post_c.xml address parsing rules. Sample text recognized by the rules: 12345-6789 12345 Output record consists of two fields: ZIP or first part of ZIP+4 code Second part of ZIP+4 code
857
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.
858
859
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
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 supports 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
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: CTE-DU-MILLE RUE ROUTE 143 SUD LA VRENDRYE OUEST BOULEVARD AUTOROUTE DE LA GATINEAU A single output element consists of 5 output entities: Street prefix Street pretype
862
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
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
864
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 1502345 A single output entity contains a single output element:
865
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
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
867
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
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
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.
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
870
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 PASSATGE 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
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 PLAA D'
872
SPA_number.xml
The file contains parsing rules for numbers. It is used to handle numeric street names ('CARRER UNO', 'CARRER NMERO 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.
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, PLAA for PLAZA, and so forth). It is referenced from CAT_street.xml and CAT_street_type.xml parsing rules.
873
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 pass pre-calculated intersection points to the AGI file along with centerline data. However, one could try to create a separate AGI file with pre-calculated intersection points based on a rooftop geocoding model (but it is not what we currently call intersection geocoding). Internally (at the matching stage, that is, at input to GMAddressMatcher after being processed by an AddresssTransformation), ordinary addresses are defined by a set of base address element values. The house number address element should be specified for proper location of the matched point along a street centerline. In contrast with ordinary addresses to be geocoded, an intersection address consists of two complete sets of base address elements for the primary street and the crossing street, respectively. The value of the house number address element can be specified in both the street and intersecting street, but it is not used in the location of the matched point. The geocoding system provides two basic ways to specify intersections at the user level: 1. To define an input address format where there is an input address field with special address parsing rules, automatically disambiguating it as an ordinary address or an intersection address.
874
875
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
3. The replacement rules at the end of a word are: Input Characters RG CH Q M T 4. Other replacement rules: Input Characters NY NT(!vowel) GE GI GUE GUI GN LL H CZ Z,X TX V CE CI Phonetic Code N(!vowel) JE JI GE GI N Y (H removed if not part of CH) CH S CH S B SE SI Phonetic Code R K K N (T is removed)
877
(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(D or T or S) (vowel)M(!vowel) (vowel)I(vowel) Y(!vowel) (vowel)(B or T or S) (vowel)(D or T or S) (vowel)N(!vowel) (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: Input string MARTINEZ SMITH LLUISOS PI I MARGALL PETXINA SOR EULLIA D'ANZIZU Sounds Like (Spanish) MARTINES ESMIT YUISOS PI I MARGAY PECHINA SOR EULALIA DANSISU Sounds Like (English) MRDMC SMD LCC PMRCL PDCM SRLLDMCC
878
879
880
APPENDIX L
File Types
GeoMedia products introduce file types that must be registered with Windows. The following file types are exposed to the user with GeoMedia Professional, and they must have an associated description, icon, and open action. The items with a single ampersand (&) are omitted from the GeoMedia Objects delivery. The items with a single asterisk (*) are omitted from the GeoMedia Viewer delivery. The items with a double asterisk (**) are omitted from both the GeoMedia Viewer and GeoMedia deliveries. The open action is normally the executable to be invoked for opening the file, when the file is opened from Windows, usually by double-click. Some file types are designated as No action, meaning that the file type has been designated as not to be opened directly through Windows. Extension AGI AGP CSC* CSD* CSF FSM GBP** GCE* GLS* GLT* GSD GWS GWT
& & & & &
Description
Open Action
Intergraph GeoMedia Address Geocoding Index No action Intergraph GeoMedia Address Geocoding Profile Intergraph GeoMedia CAD Server Cache File Intergraph GeoMedia CAD Schema Definition File Intergraph GeoMedia Coordinate System File Intergraph GeoMedia Feature Symbol File Intergraph GeoMedia Batch Plotting File Intergraph GeoMedia Catalog Exchange File Intergraph GeoMedia Layout Sheet Intergraph GeoMedia Layout Template Intergraph GeoMedia Style Definition File Intergraph GeoMedia GeoWorkspace
1
Publish Address Geocoding Index utility No action Define CAD Server Schema File utility Define Coordinate System File utility Define Symbol File utility Batch Plotting utility No action No action No action Internet Explorer GeoMedia Professional
Intergraph GeoMedia GeoWorkspace Template GeoMedia Professional Intergraph GeoMedia Access Warehouse Template Intergraph GeoMedia SmartStore Profile No action Publish to GeoMedia SmartStore Warehouse utility No action
Intergraph GeoMedia Text Format Definition File Define Text File Server Format File utility 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 - Administrator Concepts and Workflows 839 Address Geocoding - User 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 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
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
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 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 Joins 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 Designing Map Layouts for Printing in the Layout Window 561 Designing Map Layouts Overview 561 Digitizer Button Mapping 309
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
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
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
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 GeoMedias 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
E
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
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
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 User 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
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
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 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
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
Q
Querying Graphics-Only Features in MGE and MGSM 425 Quick Steps 795, 801
R
Raster Formats Supported 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 Registering Data 305 Registering Images 311 Registering Vector Data 314 Removing Images from a View and Redisplaying Them 86
P
Page Setup 547 Partially Deleting Linear Features 354 Password Persistence 700, 739 Path Element 828 Performing Digitizer Setup 305
887
Index
Renaming Layout Sheets 554 Resizing the Legend 123 Resolving Text Conflicts 506 Reversing Direction 386 Rotating Geometry 350 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 user accounts. 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 Supported Digitizers 305 Supported SVG Element Types 821 Supported Types 822 SVG Symbol Metadata XML Schema 833 Symbol Element 822
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 CodesNAD27 and Old Island Datums 776 State Plane Zone CodesNAD83 Datum 778 Step Five Create an ODBC connection for GeoMedia Catalog users. 804 Step Four Create a New Catalog Connection 798 Set user permissions. 802 Step One
T
Tables 731 Taking a Snapshot of the Data Window 187 Taking a Snapshot of the Map Window 159 Technical Support 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
888
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 User Accounts 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
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 Joins 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
V
Validating and Fixing Data 357 Validating Connectivit y 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-User Environment 71 Viewing Layout Window Properties 555 Views and Join Views 757 Views and Join-Views 732
889
Index
X
XML Source 836
890
Additional information on Intergraph Support 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).