working with gm transp manager

Working with GeoMedia® Transportation Manager

Working with GeoMedia Transportation Manager

DJA084590 (6.0.3)

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

What do you think about Working with GeoMedia Transportation Manager? DJA084590

We would like your opinion of this document. Please help us improve our documentation by completing this questionnaire. Write your comments or circle your responses to the questions. Circle all responses that apply, and include additional pages of comments if you wish. When you have completed the questionnaire, fold and mail it to Intergraph. Postage is prepaid. Thank you for taking the time to let us know what you think. 1. How much of this document have you worked through? 1. 1 - 2 - 3 - 4 - 5 (1=entire document, 2=most of it, 3=about half, 4=about one-third, 5=one-fourth or less) 2. How easy was this document to read and understand? 2. 1 - 2 - 3 - 4 - 5 (1=difficult . . . 5=easy) 3. How easy was it to find specific information in this document? 3. 1 - 2 - 3 - 4 - 5 (1=difficult . . . 5=easy) 4. What was your primary intent in using this document? 4. 1 - 2 - 3 - 4 - 5 (1=orientation . . . 5=thorough understanding) 5. How well did this document satisfy this intent? 5. 1 - 2 - 3 - 4 - 5 (1=poorly . . . 5=very well) 6. Have you used Intergraph software before? (1=yes, 2=no) 6. 1 - 2 7. What percentage of your work time is spent using Intergraph software? 7. 1 - 2 - 3 - 4 - 5 (1=10% or less, 2=25%, 3=50%, 4=75%, 5=90% or more) 8. How would you rate your level of software use? 8. 1 - 2 - 3 - 4 - 5 (1=demanding . . . 5=casual) 9. Did this document help you learn to use the software in a satisfactory way? 9. 1 - 2 (1=yes, 2=no) 10. How would you rate this document overall? (1=poor . . . 5=excellent) 10. 1 - 2 - 3 - 4 - 5 11. Have you used Intergraph documentation before? (1=yes, 2=no) 11. 1 - 2 12. Please describe and note page numbers of any errors or inconsistencies in this document.

13. How would you improve this document?

Name Date

Organization Phone

Address

City State Zip Code

Thanks again for your time and effort.

--------------------------------------------------------------------------------------------------

BUSINESS REPLY MAIL FIRST CLASS MAIL PERMIT NO. 9079 HUNTSVILLE, AL

POSTAGE WILL BE PAID BY ADDRESSEE

Security, Government & Infrastructure (SG&I) Division Manager, Technical Documentation Mail Stop IW17B2 P.O. Box 6695 Huntsville, AL 35824-6695

--------------------------------------------------------------------------------------------------

i

Table of Contents

Start Here ................................................................................................................................... 1-1 What’s New in Transportation Manager 6.0.3....................................................................... 1-1 Overview of the Document .................................................................................................... 1-2 Documents Delivered............................................................................................................. 1-3 Document Conventions.......................................................................................................... 1-4

Introduction to Linear Referencing ......................................................................................... 2-1 What is Linear Referencing?.................................................................................................. 2-1 Linear Referencing and GeoSpatial Technology ................................................................... 2-2 LRS Linear Features and Event Data..................................................................................... 2-3 Multilevel Linear Referencing Systems (MLRS) .................................................................. 2-5 Linear Referencing Analysis................................................................................................ 2-14 Linear Referencing System Maintenance ............................................................................ 2-16

Introduction to Working with Multilevel LRSs...................................................................... 3-1 LRS Analysis Using a Multilevel LRS .................................................................................. 3-1 Maintaining a Multilevel LRS ............................................................................................... 3-8

Working with the LRS Metadata Definition Command........................................................ 4-1 The LRS Metadata Definition Command Workflow to Create New Metadata Definitions .. 4-4 The LRS Metadata Definition Command Workflow to Modify an Existing LRS Definition4-9

Working with the Interactive LRS Calibration Command ................................................... 5-1 The Interactive LRS Calibration Command Workflow ......................................................... 5-2

Working with the LRS Calibration Command....................................................................... 6-1 The LRS Calibration Command Workflow ........................................................................... 6-2

Working with the LRS Validation Command ........................................................................ 7-1 The LRS Validation Command Workflow ............................................................................ 7-2

Working with the Reformat Linear Collections Command .................................................. 8-1 The Reformat Linear Collections Command Workflow........................................................ 8-2

Working with the Create Intersection Markers Command .................................................. 9-1 The Create Intersection Markers Command Workflow......................................................... 9-4

Working with the Insert LRM Segment Command............................................................. 10-1 The Insert LRM Segment Command Workflow.................................................................. 10-1


ii

Working with the Split LRM Segment Command ................................................................ 11-1 The Split LRM Segment Command Workflow ................................................................... 11-2

Working with the Redigitize LRM Segment Command ...................................................... 12-1 The Redigitize LRM Segment Command Workflow .......................................................... 12-3

Working with the Merge LRM Segments Command........................................................... 13-1 The Merge LRM Segments Command Workflow............................................................... 13-2

Working with the Delete LRM Segment Command............................................................. 14-1 The Delete LRM Segment Command Workflow ................................................................ 14-1

Working with the Output Linear Datum Command ........................................................... 15-1 The Output Linear Datum Command Workflow ................................................................. 15-3

Working with the Interactive Multilevel LRS Conflation Command ................................ 16-1 The Interactive Multilevel LRS Conflation Command Workflow ...................................... 16-3

Working with the Multilevel LRS Conflation Command.................................................... 17-1 The Multilevel LRS Conflation Command Workflow ........................................................ 17-3

Working with the Multilevel LRS Validation Command .................................................... 18-1 Data Integrity Rules ............................................................................................................. 18-1 Geometry Rules.................................................................................................................... 18-2 LRM Rules........................................................................................................................... 18-4 Schema ................................................................................................................................. 18-6 The Multilevel LRS Validation Command Workflow......................................................... 18-7

Working with the Display LRM Command.......................................................................... 19-1 The Display LRM Dialog Box............................................................................................. 19-1 The Display LRM Command Workflow ............................................................................. 19-3

Working with the LRS Event Overlay Command................................................................ 20-1 The LRS Event Overlay Command Workflow.................................................................. 20-11

Working with the Resolve LRS Event Overlaps Command................................................ 21-1 The Resolve LRS Event Overlaps Command Workflow..................................................... 21-2

Working with the LRS Event Conversion Command.......................................................... 22-1 The LRS Event Conversion Command Workflow .............................................................. 22-1

Working with the Convert Intersection Referenced Events Command ............................. 23-1 The Convert Intersection Referenced Events Command Workflow.................................... 23-1

Table of Contents

iii

Working with the LRS Event Generation Command .......................................................... 24-1 The LRS Event Generation Command Workflow ............................................................... 24-2

Working with the Create Intersections and Midblocks Command .................................... 25-1 The Create Intersections and Midblocks Command Workflow........................................... 25-3

Working with the Insert LRS Event Command ................................................................... 26-1 The Insert LRS Event Command Workflow........................................................................ 26-1

Working with the LRS Keys for Coordinate Events Command ......................................... 27-1 The LRS Keys for Coordinate Events Command Workflow............................................... 27-1

Working with the Routes and Sections to LRS Command.................................................. 28-1 The Routes and Sections to LRS Command Workflow....................................................... 28-1

Working with the LRS Event Transform Command........................................................... 29-1 The LRS Event Transform Command Workflow................................................................ 29-1

Working with the LRS and Marker Properties Dialog Boxes............................................. 30-1 The LRS Properties Dialog Box Workflow for an LRS Feature Class................................ 30-1 The Marker Properties Dialog Box Workflow for a Marker Feature Class ......................... 30-2

Working with the Event Properties Dialog Box.................................................................... 31-1 The LRM-based Event Properties Dialog Box Workflow ................................................... 31-1 The Datum-based Event Properties Dialog Box Workflow................................................. 31-3

Working with the Coordinate System Dialog Box................................................................ 32-1 The Coordinate System Dialog Box Workflow ................................................................... 32-1

Working with the LRS Data Preparation Workflows.......................................................... 33-1 Reformat Linear Collections ................................................................................................ 33-1 Validate and Fix Geometry .................................................................................................. 33-2 Validate and Fix Connectivity ............................................................................................. 33-3 Calibrate the LRS................................................................................................................. 33-5 Validate the LRS.................................................................................................................. 33-5 Fix the LRS .......................................................................................................................... 33-6 Index the LRS ...................................................................................................................... 33-6

Working with Intersection Preparation Workflows............................................................. 34-1 Intersection Preparation for Single Level LRSs................................................................... 34-1 Intersection Preparation for Multilevel LRSs ...................................................................... 34-8


iv

Working with the Single Level to Multilevel LRS Conversion Workflow ......................... 35-1

Data Model Design .............................................................................................................. 35-1 Source Data Preparation....................................................................................................... 35-3 Data Conversion................................................................................................................... 35-4 Final Touches ....................................................................................................................... 35-4

Working with the LRS Annotation Workflows .................................................................... 36-1 Annotate Digitizing Direction.............................................................................................. 36-1 Annotate Begin and End Measurements .............................................................................. 36-3 Annotate Even Measures Along the LRS ............................................................................ 36-8

Working with the LRS Analysis Workflows ......................................................................... 37-1 Aggregate Point Event Data onto Linear Segments............................................................. 37-1 Aggregate Point Event Data onto Intersections ................................................................... 37-7 Aggregate Linear Event Data within Boundaries .............................................................. 37-12 Aggregate Segment Event Data onto Linear Segments by Proportion .............................. 37-18

Introduction to Routing .......................................................................................................... 38-1 What is a Routing Network? ................................................................................................ 38-1 Edge-Node Connectivity...................................................................................................... 38-2 Impedance ............................................................................................................................ 38-4 Turn Tables .......................................................................................................................... 38-4 Restrictors ............................................................................................................................ 38-6 Stops..................................................................................................................................... 38-8 Routing Analysis.................................................................................................................. 38-9 Routing Maintenance ......................................................................................................... 38-10

Working with the Build Network Command........................................................................ 39-1 The Build Network Command Workflow............................................................................ 39-1

Working with the Stop Manager Command......................................................................... 40-1 The Stop Manager Workflows ............................................................................................. 40-1

Working with the Turn Editor Command ............................................................................ 41-1 The Turn Editor Workflow .................................................................................................. 41-1

Working with the Restrictor Editor Command.................................................................... 42-1 The Restrictor Editor Workflow .......................................................................................... 42-1

Working with the OneWay Editor Command...................................................................... 43-1 The OneWay Editor Workflow............................................................................................ 43-1

Working with the Blockage Editor Command...................................................................... 44-1 The Blockage Editor Workflow ........................................................................................... 44-1

Table of Contents

v

Working with the Display OneWays Command................................................................... 45-1 The Display OneWays Workflow........................................................................................ 45-1

Working with the Display Blockages Command .................................................................. 46-1 The Display Blockages Workflow ....................................................................................... 46-2

Working with the Easy Path Command................................................................................ 47-1 The Easy Path Workflow ..................................................................................................... 47-2

Working with the Best Path Command................................................................................. 48-1 The Best Path Workflow...................................................................................................... 48-2

Working with the Find Closest Stops Command.................................................................. 49-1 The Find Closest Stops Workflow ....................................................................................... 49-2

Working with the Network Coverage Command ................................................................. 50-1 The Network Coverage Command Workflow ..................................................................... 50-2

Working with the Generate Path Directions Command...................................................... 51-1 The Generate Path Directions Command Workflow ........................................................... 51-1

Working with the Configure Network Dialog Box ............................................................... 52-1 The Configure Network Dialog Box Workflow .................................................................. 52-1

Working with the Stop Properties Control ........................................................................... 53-1 The Stop Properties Control Workflow ............................................................................... 53-1

Working with the Routing Data Maintenance Workflows .................................................. 54-1 The Dynamic Routing Data Maintenance Workflow .......................................................... 54-1 Manual Routing Data Maintenance – The Initial Network Creation Workflow.................. 54-2 Manual Routing Data Maintenance – The Network Update Workflow .............................. 54-3 The Routing Network Validation Workflow ..................................................................... 54-10

Working with the LRS-based Routing Restrictions Workflow........................................... 55-1

A. How to Reach Intergraph.................................................................................................... A-1 Electronic Self-Help Support ................................................................................................ A-1

B. GeoMedia Transportation LRS Data Structures...............................................................B-1 Overview................................................................................................................................B-1 Single Level LRS Data Structures .........................................................................................B-2 Additional Multilevel LRS Data Structures .........................................................................B-13 Event Data Structures...........................................................................................................B-14


vi

Additional Multilevel LRS Event Structures .......................................................................B-19 Multilevel LRS Supporting Tables ......................................................................................B-21 GeoTrans Transportation Data Model….............................……………………………….B-24

C. Working With Oracle LRS and ArcView Data ................................................................ C-1 Working with Oracle LRS Data .............................................................................................C-1 Working with ArcView Data .................................................................................................C-1

Index .......................................................................................................................................... IN-1

1-1

Start Here

What’s New in Transportation Manager 6.0.3 The major new feature of GeoMedia Transportation Manager 6.0.3 is the option to create and use Multilevel LRSs. This is important functionality that addresses many common problems facing transportation agencies, including:

• Handling multiple linear referencing methods – This allows Event data collected using a wide variety of route measurement and naming schemes to be used together when analyzing a transportation system.

• Handling multiple network representations – This harmonizes the use of multiple network representations that perhaps originate from other transportation agencies at different levels of government. You can choose to analyze your Event data using any of the available network representations.

• Securing Event data location stability – One of the dangers of a linear referencing system is that as the network changes (for example, road name changes, realignments, and recalibrations), the location of Event data can be incorrectly changed. Intergraph’s Multilevel LRS can prevent this from happening.

• Preserving the history of the network – When used with GeoMedia Transaction Manager, Intergraph’s Multilevel LRS provides the ability to create, maintain, and analyze a temporal history of a linear referencing system and the Event data associated with it. This is a powerful tool for analyzing the effectiveness of maintenance and corrective actions executed by the agency.

Of course GeoMedia Transportation Manager also has the tools to create and maintain a Multilevel LRS. Beyond the introduction of Multilevel LRS support, this release also provides important new functionality in the following areas:

• LRS Conflation – Conflation, the selective copying of data from one source to another, is especially tricky for transportation networks due to the fact that no two representations of the same network are modeled or segmented in the same way. The conflation tools in this release overcome those obstacles. Furthermore, when used in conjunction with the tools in the GeoMedia Fusion product, GeoMedia Transportation Manager can perform conflation for an entire data set in a very automated manner.

• LRS Definitions – With this release, the LRS Property settings can be stored centrally in your enterprise database where they can be set once and be available to all users.

• Region IDs – We have introduced the concept of Region IDs, which allows you to subdivide your network into logical units. This often improves performance when the entire network is not needed for a particular analysis.


1-2

• Intersection-referenced Events – We now support Event data that is located by its distance and direction from intersections. This even includes the capability to resolve ambiguous locations associated with roads that cross more than once.

• Aggregation – Often transportation agencies like to analyze their network at intersections and the “midblocks” between intersections. This release provides a tool to make these analyses easier, more accurate, and the end results more useful.

• Routing improvements – This release has two improvements to our routing tools. One is the option to enforce turn restrictions at intermediate stops, which is important for applications such as large vehicle routing. Another improvement is the ability to edit the restrictors used by an existing path query via the Query Properties dialog box, which facilitates what if analyses.

Overview of the Document This document contains information on using GeoMedia Transportation Manager for linear data analysis and routing analysis. The structure of this document is as follows:

• There are two major divisions: Chapters 2-37 pertain to Linear Referencing Systems (LRS), and Chapters 38-55 pertain to Network Routing.

• Chapter 2 provides an introduction to the basic concepts behind linear referencing, and Chapter 3 provides a good overview of how to work with Multilevel LRSs.

• Chapters 4-18 provide step-by-step instructions on how to use each of the LRS (Linear Referencing System) Maintenance commands.

• Chapters 19-29 provide step-by-step instructions on how to use each of the LRS Analysis commands.

• Chapters 30-32 provide step-by-step instructions on how to use four of the elements common to many of the LRS commands included in this product: the LRS Properties dialog box, the Markers Properties dialog box, the Event Properties dialog box, and the Coordinate System dialog box.

• Chapters 33-37 provide instruction on common workflows used in the preparation and analysis of linear data.

• Chapter 38 provides an introduction to the basic concepts behind network routing.

• Chapters 39-46 provide step-by-step instructions on how to use each of the Routing Maintenance commands.

• Chapters 47-51 provide step-by-step instructions on how to use each of the Routing Analysis commands.

• Chapters 52-53 provide step-by-step instructions on how to use two of the elements common to many of the Routing commands included in this product: the Configure Network dialog box and the Stop Properties control.

Start Here

1-3

• Chapters 54-55 provide instruction on common workflows used in Routing maintenance and analyses.

• Appendix B provides details of the LRS data structures supported by the GeoMedia Transportation product line.

• Appendix C provides instruction for using Oracle LRS or ArcView data with the GeoMedia Transportation product line.

Each section of this document takes you through a systematic process to use the software commands.

Documents Delivered The following online documents are delivered with GeoMedia Transportation Manager:

Document Number Description


DJA0845Online only

An overview of the workflows and commands for performing most software tasks. Available online in .pdf format at Start > All Programs > GeoMedia Transportation Manager > User Documentation > Working with GeoMedia Transportation Manager.

Installing GeoMedia Transportation Manager

DJA0853 Online only

Instructions for installing the product. Available online in .pdf format at Start > All Programs > GeoMedia Transportation Manager > User Documentation > Installing GeoMedia Transportation Manager.

GeoMedia Transportation Manager Object Reference

Online only Programmer's guide for objects, methods, and properties. Available from the \Program Files\GeoMedia\Help folder or at Start > All Programs > GeoMedia Transportation Manager > Developer Documentation > GeoMedia Transportation Manager Object Reference.

GeoMedia Transportation Object Diagrams

Online only Object diagrams for programmers. Available online in .pdf format at Start > All Programs > GeoMedia Transportation Manager > Developer Documentation > GeoMedia Transportation Object Diagrams.

GeoMedia Transportation Workflow Diagrams

Online only Workflow diagrams for programmers. Available online in .pdf format at Start > All Programs > GeoMedia Transportation Manager > Developer Documentation > GeoMedia Transportation Workflow Diagrams.

Visit our web site at http://support.intergraph.com/Documentation.asp for the latest version of these documents.

http://support.intergraph.com/Documentation.asp


1-4

Document Conventions

Typeface Conventions Used in the Documents ALL CAPS Keyboard keys.

If keys are separated by a comma, press them in sequence. For example: ALT, F5. If they are joined by a plus sign, press them at the same time. For example: CTRL+z.

Bold unserifed type

An item in the graphical interface, such as the title of a dialog box or a tool. Paths through menus use right angle brackets between items you select. For example: Select File > Open to load a new file.

Courier type

Information you type. For example: Type original.dat to load the ASCII file.

Italic type A document title, the first occurrence of a new or special term, folder and filenames, or information about what the software is doing.

Introduction to Linear Referencing The purpose of this chapter is to outline the basic concepts behind the linear referencing capabilities of GeoMedia Transportation Manager. Both single-level and Multilevel linear referencing systems (LRSs) are described in some detail. Lastly, the various LRS analysis and maintenance tools are described.

What is Linear Referencing? Linear Referencing is simply the tracking and analysis of data that is associated with locations along a linear network. Some road transportation examples include tracking the location of and condition of signage, the condition of pavement, and the location and severity of accident occurrences. The biggest uses of linear referencing are Asset Tracking and Asset Analysis.

Asset Tracking primarily encompasses the following four items:

2-1

• What, where, and when of the assets (for example, a pothole at kilometer post 41.7 along Route 66, reported June 6th, 2002)

• Asset conditions (for example, a stretch of pavement with rutting and cracking)

• Incidents along the network (for example, a traffic accident)

• Activities along the network (for example, construction projects)

Asset Analysis includes such activities as “hot-spotting” (finding areas with an unusual density of a given type of problem) and cross-discipline analysis (for example, cross analyzing areas that have both run-off-the-road accidents and no guardrails). This type of analysis can be important for any number of areas, including the following:

• Protecting the public (for example, finding areas of high-density accidents and finding the common contributing factor)

• Optimizing usage of assets (for example, locating areas with both high volume and low number of lanes in order to identify areas of congestion)

• Optimizing budget usage (for example, locating the areas with the most traffic and the worst pavement conditions to be first priority for resurfacing)


Linear Referencing and GeoSpatial Technology The main impetus to merge linear referencing with geospatial technology can be summed up simply: it is often desirable to view location data on a map. It also opens up a lot of other analysis capabilities, such as summing up data within an area feature (for example, the kilometers of rail track that require maintenance within a given jurisdiction) or finding data within a proximity of linearly referenced data (for example, finding residences within a buffer zone of a construction project).

Using GeoMedia Transportation Manager is not the only way to merge linear referencing and geospatial technology, but it is certainly the easiest. GeoMedia Transportation Manager enables you to create map features, including pavement conditions, accident data, and average daily traffic. This kind of information will help you plan improvements for deteriorating assets, will identify where your organization is spending its money, and will provide critical information clearly and accurately to all participants involved in your projects. GeoMedia Transportation Manager increases the value of your data by turning it into business-critical, decision-support information.

1.8

0.9

3.2

4.1

1.8

0.9

3.2

4.1

1.8

0.9

3.2

4.1

2

3

Hwy 62

3

2

3

Hwy 6Hwy 6

The preceding diagram shows a portion of road on the left and its geospatial representation on the right. The road has kilometer posts that indicate cumulative linear measures along the road. It also has a road name, Highway 6 in this example. A section of fencing along the road is also shown in both the left and right views. Based on the kilometer posts, it can be determined in the field that this stretch of fence runs along Highway 6 from kilometer measure 2.0 to 2.6.

On the geospatial side, we have three linear features, known as LRS Linear Features, that will all have a road name and begin and end measure attribution. These LRS Linear Features are the backbone of the LRS and are used in automating the mapping of linearly referenced data, such as this stretch of fencing, onto our map view.

2-2

Introduction to Linear Referencing

2-3

Of course, this mapping of linearly referenced data does not have to be automated. Without GeoMedia Transportation Manager, 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 GeoMedia Transportation Manager, all of these items can be mapped with a single command.

The methodology used by GeoMedia Transportation Manager 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 measurement attributes stored on those features.

LRS Linear Features and Event Data As mentioned before, LRS Linear Features are the backbone of the LRS. But working with the linearly referenced tabular data, known as Event Data, is the whole reason for building the LRS in the first place. Although the data structures of these two components are described in detail in Appendix B: GeoMedia Transportation LRS Data Structures, we will provide a brief summary here of what is known as traditional, or single-level, LRS. We will address Multilevel LRS (MLRS) in the next section.

The LRS Linear Features represent the network itself. Each LRS Linear Feature table is a linear feature class that has the following fields:

• ID – This is a long integer value that uniquely identifies each feature within the table.

• LRSKeys1-4 – This is one to four fields that together define the “route” that this feature belongs to.

• StartMeasure – This is a numeric value that contains the measurement value for the beginning of this feature.

• EndMeasure or Duration – This is a numeric value that contains either the measurement value for the end of this feature or the length measurement for this feature.

• BeginMarker (optional) – This field stores a name for the beginning position of this feature. This is referred to as an internal marker.

• EndMarker (optional) – This field stores a name for the end position of this feature. This is referred to as an internal marker.

• ReversedGeometry (optional) – This Boolean (True/False) field declares whether the GeoMedia Transportation Manager software should treat this linear feature as if (False) or as if its digitizing direction were reversed and its beginning were its end, and vice-versa (True).


2-4

The Event Data represents the linearly referenced data. Note that Event Data can either be point data (occurring at just one spot on the linear network) or linear data (occurring at a span of distance along the linear network). Each Event Data table is (usually) a non-graphic table that has the following fields:

• ID – This is a long integer value that uniquely identifies each record within the table.

• LRSKeys1-4 – This is one to four fields that together define the “route” that this record lies along.

• Measurement data (pick one of the following options)

- Measure Option – For point event data, this consists of one numeric Measure field that indicates the relative location of the point event record on the “route” defined by the LRS Key fields. For linear event data, this consists of two numeric fields: a StartMeasure field and an EndMeasure field. These define the relative location of the start and end points of the linear event record on the “route” defined by the LRS Key fields.

- Marker Offset Option – For point event data, this consists of a Marker name field and a numeric Offset distance field. The point event data is located by first locating the marker and then by adding the offset distance to that location. For linear event data, there are two Marker fields and two Offset fields defining the start and end of the linear event record.

- Coordinate Option – For point event data, this consists of two fields which, depending on the referenced Coordinate System File, may by either projected coordinates (for example, Northing & Easting) or geographic coordinates (Latitude & Longitude). For linear event data, there are four fields defining the coordinates for both the start and the end of the linear event record.

- Duration Option – This is a slight variation on the Measurement Option and only applies to linear event data. It consists of a StartMeasure field and a Duration (or Length) field that together define the relative location of the record along its “route.”

• Other Attributes (optional) – These are optional, but they are also the whole reason for doing linear referencing. For bridge events, these will store bridge data; for accident events, they will store accident data; and for pavement events, they will store pavement data.

Optional components of the LRS that we have not discussed as yet 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.


2-5

Each External Marker table is (usually) a non-graphic table that has the following fields:

• ID – This is a long integer value that uniquely identifies each record within the table.

• LRSKeys1-4 – This is one to four fields that together define the “route” that this record lies along.

• Measure – This is a numeric field that indicates the relative location of the External Marker on the “route” defined by the LRS Key fields.

• MarkerName – This field stores a name for this Marker.

Detailed information on how to create a LRS Linear Feature class is provided in the “LRS Data Preparation Workflows” chapter. Information on at least one way to populate Event Data and External Marker tables is provided in the “Working with the Insert LRS Event Command” chapter.

Multilevel Linear Referencing Systems (MLRS) GeoMedia Transportation Manager and GeoMedia Transportation Analyst now support Multilevel LRSs (MLRS) as well as the traditional, single-level LRSs. Multilevel LRS has been a topic of discussion since at least the early 1990s and the original NCHRP (National Cooperative Highway Research Program) 20-27 study. The Multilevel LRS model that Intergraph uses is known as the GeoTrans model and is derivative of the NCHRP 20-27 model.

Since the inception of the concept of Multilevel LRS, there have been numerous implementations and attempted implementations. The reason for the interest is very understandable. This kind of model addresses a variety of problems that are common to almost all transportation agencies, which raises the question as to why this kind of model is not more common. First, let’s summarize some of the problems a Multilevel LRS solves, and then we will explore why these models are not in use everywhere.

Multiple Linear Referencing Methods Perhaps the key issue addressed by Multilevel LRSs is the need to support multiple Linear Referencing Methods (LRMs). Most transportation agencies have various sub departments and external sources that collect data about their transportation network using a variety of different measurement methods and sometimes different road- or rail-naming conventions. A few example LRMs are shown here:


Sta

te B

orde

r

Cou

nty

Bor

der

Route 50

87.60 mi

State Cumulative

Sta

te B

orde

r

Cou

nty

Bor

der

Route 50

87.60 mi

Sta

te B

orde

r

Cou

nty

Bor

der

Route 50

87.60 mi

State Cumulative

Sta

te B

orde

r

Cou

nty

Bor

der

Route 50

5.4 mi

County Cumulative

Sta

te B

orde

r

Cou

nty

Bor

der

Route 50

5.4 mi

Sta

te B

orde

r

Cou

nty

Bor

der

Route 50

5.4 mi

County Cumulative

175

Mai

n S

t.

Main St.

Address Range:100 to 200

Street Address

175

Mai

n S

t.

Main St.


175

Mai

n S

t.

Main St.


Street Address

Inte

rsec

tion

with

Elm

Ave

.

Main St.

200 ft East

Inte

rsec

tion

with

Spr

uce

Ave

.

Marker Offset

Inte

rsec

tion

with

Elm

Ave

.

Main St.

200 ft East

Inte

rsec

tion

with

Spr

uce

Ave

.

Marker Offset Support of these different LRMs is key to being able to compile the data collected by these different methods for analysis. For example, if accidents are located by GPS and guardrail inventory is located by milepost, then you would need to be able to use these different LRMs together in order to locate an accident in which a car runs off the road where there is no guardrail.

Multiple Geometric Representations Another issue that can be addressed by Multilevel LRSs is the need that many transportation agencies have to support more than one geometric representation of their network. One case for this is where different levels of generalization are used for different map products. Agencies would like to be able to use the same event data (also known as distributed attribute data) against different geometric representations, depending on whether they are doing large-scale or small-scale analysis.

2-6


A second common use case for multiple geometric representations is where some of the data comes from a regional agency and some of it comes from one or more local agencies. There may be considerable overlap of the data coverage, but there may also be many roads covered by the local data that are not covered by the regional data. For some analyses, the user will want to see all of the local roads; but for others, he or she will only want to use the major roads.

Without a Multilevel LRS, users have to duplicate 100% of their LRS data maintenance efforts for each geometric representation that they want. And even then, they are not assured that each LRS is in sync with the other and will give similar analysis results. Agencies want to be able to easily switch back and forth between geometric representations without worrying if this will affect the validity of their analysis. This is possible with Multilevel LRSs.

2-7


Event Location Stability One of the toughest challenges facing managers of transportation information is how to handle the effects of changes that are made in the transportation network over time. These changes include road-name changes, realignments, recalibrations, and so on. To illustrate these effects, we have an example of a small piece of a network with some point and linear event data associated with it. We will say that the point events represent accident locations along a road and that the linear event represents pavement conditions. This is our “before” picture:

0 5 13 187 11

Before network changes

0 5 13 187 11

Before network changes

Now let’s see what happens to our data when our road gets realigned and recalibrated. Because dynamic segmentation is an interpolation based on the road names, measures, and geometry, all of these changes can cause our linearly referenced event data to shift locations with a traditional LRS. In this case, these errors show accident data where accidents never happened, and they show pavement conditions for a now-abandoned piece of roadway as if the data relates to a new stretch of road.

0 5 13 187 1112 1710

After network changes– with Single Level LRS

0 5 13 187 1112 1710

After network changes– with Single Level LRS

Now let’s look at this same example using the GeoTrans data model, which has some special features to address this particular problem. Here we see that our accidents and pavement conditions do not shift. Furthermore, these pavement conditions show up only on the segments of the road on which this data actually occurred – even with linear event data.

0 5 13 187 1112 1710

After network changes– with GeoTrans model

0 5 13 187 1112 1710

After network changes– with GeoTrans model

2-8


2-9

Data with incorrect locations is bad data and can lead to bad decisions. So, the desired effect is that we should see those events, and only those events, that pertain to the current version of the network. This should work for both point and linear events. GeoMedia Transportation Manager and the GeoTrans data model make this possible.

To take this further, many agencies would like to be able to look at the state of their networks for a specific time period and to see only those events that pertain to those networks as they existed at that specific time. When GeoMedia Transportation Manager is used in conjunction with GeoMedia Transaction Manager, this type of temporal analysis and temporal data management is made easy. This is discussed in more detail below and in the “Working with Multilevel LRSs” chapter.

Why do so few transportation agencies use MLRS? In the last few sections, we have seen a few of the important benefits (there are others) of using Multilevel LRS. So why are most transportation agencies still using traditional, single-level LRS?

Part of the reason is that implementations have been costly because of the lack of availability, until now, of an off-the-shelf solution. Implementations have had to be custom. The toughest part of these custom implementations has not been analysis, but rather it has been data maintenance. As we will see in the next section, the data in the GeoTrans model is spread over multiple, connected layers. Because of this, a single change affects multiple layers and the relationships between those layers. Because of this, it is understandable that the hardships associated with Multilevel LRSs have been too high a hurdle for most agencies to overcome.

GeoMedia Transportation Manager has overcome these obstacles by providing a tool that is available off-the-shelf that integrates the benefits of Multilevel LRS with the tools used to maintain and make use of it. So GeoMedia Transportation Manager, while also supporting traditional, single-level LRS, also has a complete set of tools for building, maintaining, and analyzing a Multilevel LRS. These tools are designed to take much of the complexity out of using this powerful model, while still giving all of the benefits. This will allow for better, more accurate, and more complete analyses of transportation data and will make the promise of Multilevel LRS a reality.

GeoTrans Data Model In this section, we review the development and structure of the GeoTrans data model that is the core of our MLRS solution. As mentioned before, the GeoTrans data model is derivative of the NCHRP 20-27 model. However, we have made some tweaks to improve event location stability and temporality and to allow for more flexible segmentation.

Before we get into the GeoTrans data model let’s start by looking at a logical representation of the traditional, single-level LRS. A single-level LRS consists of an LRS linear feature class with geometry, name, and measurement data. This LRS linear feature class is the foundation for linearly referencing any number of event tables. The LRS


Linear feature class and the event tables are “joined” via dynamic segmentation. This model works fine for a static network with just one LRM and just one geometric representation of the network and has been the state of the art for years.

LRS

Event1

Event2

EventN

Now, what do we do if we have a network that changes over time (road-name changes, realignments, and so on), if we have more than one LRM, or if we have more than one geometric representation of our network? The theory behind Multilevel LRS is to abstract out into separate entities those parts of the network that change independently. Towards that end, we have abstracted the route naming and measurement part into an LRM layer that can contain any number of LRMs. We have also abstracted the geometric representation part into a Geometry layer that can contain any number of physical representations of our network. We have tied both of these to a Linear Datum. The Linear Datum acts as a non-changing anchor that these other layers can tie to. A unique feature of the GeoTrans model is that the Linear Datum records can neither be edited nor deleted. They can only be added to when there are new roads or realignments. This permanence is, as we shall see, the key to Event Location Stability.

LRM1

LRM2

LRMN

LRM1

LRM2

LRMNLinear

ReferencingMethods

Linear Datum

EventData

Datum

Geom1

Geom2

GeomN

Geom1

Geom2

GeomN

Cartographic Representations

Event1/1

Event1/2

Event1/N

EventN/1

EventN/2

EventN/N

Event2/1

Event2/2

Event2/N

Event1/1

Event1/2

Event1/N

EventN/1

EventN/2

EventN/N

Event2/1

Event2/2

Event2/N

So from a practical stand point, how do we relate the individual LRMs and Geometries back to the Linear Datum? When we need a one-to-one or a one-to-many relationship in a database, we use a Join where one field in one table exactly matches a field in another table. However, if we do not want to force our model to have all geometries and LRMs segmented identically, then what we have is a many-to-many relationship. This is handled by having an intermediate table to store the relationship. The ability to have completely independent segmentation is a unique feature of the GeoTrans data model. We accomplish this by not using a standard many-to-many join, but rather by using dynamic segmentation to establish our relationships.

2-10


In the following diagram, we show the intermediate tables that store this many-to-many relationship. We call these cross reference tables (G-D xRef refers to Geometry to Datum cross reference, and L-D xRef refers to Datum to LRM cross reference). The diagram also shows the multilevel dynamic segmentation that relates each of these tables together. This complexity is handled for you by the software so that you get the benefits of the model without the extra trouble.

GeometryEndMeasBegMeasGeomID GeometryEndMeasBegMeasGeomID

DescriptionLengthDatumID DescriptionLengthDatumID

EndMeas Rev Geom

LRM Key(s)BegMeasLRMID EndMeas Rev

GeomLRM

Key(s)BegMeasLRMID

IDDatum

BegMeas EndMeasGeometry

EndMeasBegMeasID IDDatum

BegMeas EndMeasGeometry

EndMeasBegMeasID

IDLRM

BegMeas EndMeasDatum

EndMeasBegMeasID IDLRM

BegMeas EndMeasDatum

EndMeasBegMeasID

Geometry

G-D xRef

Linear Datum

L-D xRef

LRM

LRM Key(s) AttributesEndMeasBegMeasLRM Key(s) AttributesEndMeasBegMeasEvent

Another key part of the model pertains to our Event Location Stability methodology. By way of contrast, we will describe two common alternative methods that some have used to accomplish this same thing.

The first alternative method is sometimes referred to as Permanent Event Geometry, which simply means storing geometry created during dynamic segmentation permanently with the event data. The upside of this methodology is its simplicity. One downside is that it only works well if you have only one geometric representation and you never expect to update it with newly collected geometry. Another downside is that it does not handle temporality well. If a road gets realigned, this method will still show event data along the old alignment that no longer exists.

The second alternative method is sometimes referred to as Cascading Edits. This method develops database triggers that will change the measures of all event data associated with an LRS any time the LRS changes. The upside of this method is that the custom code it contains gives a lot of flexibility. However, it has several downsides. First, as in most transportation agencies, there could be a performance issue when a large number of tables are affected. Second, it assumes that all event tables are stored in the central database and thus are accessible to these triggers. Third, this problem is fairly difficult to implement for

2-11


2-12

events associated with the segment of the LRS that is actually changed. Lastly, it has the additional problem that once the measures are changed, they no longer are in the correct location in relation to the “old” version of the LRS. This creates an event location stability problem if you try to look at a temporal view of the data the way it once was. Thus this method is ill-suited for temporal analysis.

The method we have implemented in the GeoMedia Transportation products and the GeoTrans data model is called Event Registration. The downside of this method is that it requires users to do a one-time Event Registration step whenever they bring in new event data. The upside is that it has none of the downsides described above.

The Event Registration step is done with the LRS Event Transform command (see the “Working with the LRS Event Transform Command” chapter). One of the options of this command is to convert LRM-based names and measures on Event tables to Datum-based names and measures. Once this simple step is done, this event data can be used regardless of how the network changes over time. Road names can change, routes can be recalibrated, and realignments may occur – but the event data will still locate correctly.

The following figure shows the complete GeoTrans logical model. Note that this model shows some events as “LRM” Events and others as “Datum” Events. The Datum Events are those that have gone through Event Registration and thus will receive the benefit of Event Location Stability. Also shown on this diagram are the two types of external markers now supported by the GeoTrans data model. The ones labeled “LRM” Markers are the same as those used by traditional, single-level LRS. The ones labeled “Datum” Markers are LRM Markers that have gone through Event Registration and, therefore, have the same location stability as Datum Events.


‘LRM’Markers

Linear Datum

xRef1

xRef1

xRef2

xRef2

xRefN

xRefN

LRM1

LRM2

LRMN

Geom1

Geom2

GeomN

xRef1

xRef1

xRef2

xRef2

xRefN

xRefN

Event1/1

Event1/2

Event1/N

Event2/2

Event2/N

Event2/1

EventN/2

EventN/N

EventN/1

EventD/1

EventD/N

EventD/2

‘LRM’ Events

‘Datum’ Events

‘Datum’Markers

Another important consideration in the design of this model is support for temporality. Many agencies want to not only be able to analyze their transportation network as it is – but also how it was (for trend analysis) or how it might be (for design and planning purposes). When you use the GeoMedia Transportation products with GeoMedia Transaction Manager, you can automatically store historical versions of the network as it is being edited in order to represent the latest changes to your network. Likewise, you can model designs for future changes to the network without destroying the current representation. With events that have been registered, you can view both the network and linearly referenced event data correctly for any time for which you have data. (Please note that GeoMedia Transaction Manager is not required in order for you to use the GeoMedia Transportation products, but without it only current network analysis is possible.)

More details about the GeoTrans data model are discussed in Appendix B: GeoMedia Transportation LRS Data Structures.

2-13


2-14

Linear Referencing Analysis This section provides brief descriptions of the major LRS Analysis tools provided by GeoMedia Transportation Manager. Detailed instructions on how to use each of these commands is provided elsewhere.

Display LRM – This command creates an LRM query and works with either single-level or Multilevel LRSs. It works in conjunction with the LRS Metadata command, which is used to populate the choices the user has. For an MLRS, those choices are which LRM and Geometry to use. For single-level LRSs, the choice is only which single-level LRS to use. In both cases, the resultant query carries along metadata which simplifies the use of many of the other commands. When this query is used as the LRS Feature Class, the appropriate LRS Properties are automatically filled in. For more information see the “Working with the Display LRM Command” chapter.

Dynamic Segmentation – This command, which has already been referred to above, takes linearly referenced tabular data and creates a graphic query class from it that can be viewed in the map view. This lets you visualize your organization's inventory of assets more clearly than by simply reviewing tabular data. For more information see the “Linear Referencing” chapter in Working with GeoMedia or Working with GeoMedia Professional.

Note: The Dynamic Segmentation command is now located on the GeoMedia Professional menu bar under Analysis.

LRS Event Overlay – This command compares two different Event Data tables and calculates intersections, differences, or unions of the two tables and presents the results as a graphic query class that can be viewed in the map window. An example of this is to map all the locations with run-off-the road accidents and no guard rails. For more information see the “Working with the LRS Event Overlay Command” chapter.

Resolve LRS Event Overlaps – This command takes a single linear Event Data table and provides a very user-definable method for removing overlaps in the data. For example, in a table of pavement conditions you may have many overlapping records, but you may want to only see the most current pavement condition records. For more information see the “Working with the Resolve LRS Event Overlaps Command” chapter.

LRS Precision Location – This command allows you to get real-time LRS locations of your cursor location in the map view. It also allows you to use key-ins of LRS locations to place points in the map view. These points may just be used for orientation, but they also can be used for placing vertices of new geometry. For more information see the “Linear Referencing” chapter in Working with GeoMedia or Working with GeoMedia Professional.

Note: The LRS Precision Location command is now located on the GeoMedia Professional menu bar under Tools.


2-15

LRS Event Conversion – This command allows you to convert the measurement portion of your event data from one measurement option to another (these options were described earlier). This can allow you, among other things, to convert event data collected in a number of ways to a single measurement method for more consistent reporting. For more information see the “Working with the LRS Event Conversion Command” chapter.

Convert Intersection-referenced Events – This command takes intersection-referenced event data and converts it into marker-offset event data that is compatible with the GeoMedia Transportation products. It has a special tool for handling the ambiguity associated with intersection-referenced event data associated with roads that cross more than once. This command works in conjunction with the Create Intersection Markers command. For more information see the “Working with the Convert IntersectionReferenced Events Command” chapter.

LRS Event Generation – This command provides you with a number of ways to generate event data at various defined points along the LRS network. This comes in handy for both annotation and aggregation workflows. For more information see the “Working with the LRS Event Generation Command,” “LRS Annotation Workflows,” and “LRS Analysis Workflows” chapters.

LRS Keys for Coordinate Events – This command will take Event data that has coordinate data but no LRS Key data and add the LRS Key data to it. This will make this kind of Event Data, commonly collected using GPS instruments, usable with the other analysis commands, such as Dynamic Segmentation and LRS Event Overlay. For more information see the “Working with the LRS Keys for Coordinate Events Command” chapter.

Routes and Sections to LRS – This command takes the two component classes from an ArcRoute system (Routes and Sections) and creates a single query of an LRS class that is usable with the other commands within GeoMedia Transportation Manager. For more information see the “Working with the Routes and Sections to LRS Command” chapter.

Insert LRS Event – This command allows you to interactively create event data by clicking on the map view to define LRS key, begin measures, and (for linear events) end measures. This will allow you to create event data via “heads-up” digitizing. For more information see the “Working with the Insert LRS Event Command” chapter.

LRS Event Transform – This is an MLRS command that can transform an event feature class in any of the following ways:

• LRM-based to Datum-based Event feature class (Event Registration)

• Datum-based to selected LRM-based Event feature class in the same linear referencing system

• Source-LRM-based to target LRM in the same linear referencing system

For more information see the “Working with the LRS Event Transform Command” chapter.


2-16

Linear Referencing System Maintenance This section provides brief descriptions of the major LRS Maintenance tools provided by GeoMedia Transportation Manager. Detailed instructions on how to use each of these commands is provided elsewhere. A good overview of LRS maintenance is provided in the “LRS Data Preparation Workflows” chapter.

LRS Metadata Definition – This command provides the capability to define and modify LRS Metadata for either single-level or Multilevel LRSs. This allows a one time identification of the key tables and fields associated with the LRS so that others can make use of this definition without duplication of effort. This command works closely with the Display LRM command in order to simplify the use of the various LRS Analysis and Maintenance commands. For more information see the “Working with the LRS Metadata Definition Command” chapter.

Interactive LRS Calibration – This command can be used to name and calibrate (that is, populate measure values in) LRS features one route at a time. For more information see the “Working with the Interactive LRS Calibration Command” chapter.

LRS Calibration – This command can be used to calibrate (that is, populate measure values in) LRS features an entire feature class at a time. For more information see the “Working with the LRS Calibration Command” chapter.

LRS Validation – This command can be used to validate that a linear feature class is also a working LRS feature class that will provide accurate results. It queues up errors for easy correction. For more information see the “Working with the LRS Validation Command” chapter.

Reformat Linear Collections – This command can be used to repair some of the problems common to data sets containing geometry collections. It assures that components of geometry collections are in order and have correct and consistent digitizing directions. This helps assure an LRS that provides correct analysis results. For more information see the “Working with the Reformat Linear Collections Command” chapter.

Create Intersection Markers – This command creates an Intersection Markers feature class for an input LRS feature class. The Intersection Markers feature class will be a point feature class that represents all valid intersections in the input LRS feature class. This command is used in conjunction with the Convert Intersection-referenced Events command. For more information see the “Working with the Create Intersection Markers Command” chapter.

Create Intersections and Midblocks – This command creates two feature classes. The Intersection feature class covers the portions of the network within a user-specified distance of each valid intersection and has attribution identifying associated roads. The Midblock feature class shows that portion of the network in between these Intersection features and also includes identifying attribution. Both of these feature classes are very useful in aggregation workflows. For more information see the “Working with the Create Intersections and Midblocks Command” chapter.


2-17

Insert LRM Segment – This command is a special MLRS command to simplify the task of inserting new features into a Multilevel LRS dataset. For more information see the “Working with the Insert LRM Segment Command” chapter.

Split LRM Segment – This command is a special MLRS command to simplify the task of splitting features in a Multilevel LRS dataset. For more information see the “Working with the Split LRM Segment Command” chapter.

Redigitize LRM Segment – This command is a special MLRS command to simplify the task of redigitizing features or portions of features in a Multilevel LRS dataset. For more information see the “Working with the Redigitize LRM Segment Command” chapter.

Merge LRM Segments – This command is a special MLRS command to simplify the task of merging features in a Multilevel LRS dataset. For more information see the “Working with the Merge LRM Segments Command” chapter.

Delete LRM Segment – This command is a special MLRS command to simplify the task of deleting features in a Multilevel LRS dataset. For more information see the “Working with the Delete LRM Segment Command” chapter.

Output Linear Datum – This command provides the capability to display the linear datum graphically. It has special abilities to show the entire datum even if the entire datum is not represented in any one geometric definition. This command is primarily used by the two LRS Conflation commands. For more information see the “Working with the OutputLinear Datum Command” chapter.

Interactive Multilevel LRS Conflation – This command can be used to update an existing MLRS with new data from a separate linear feature class. In the Update mode of this command, the user identifies the related portions of both the new and existing data and which LRM and/or Geometry tables to update (while maintaining Linear datum definitions). In Insert mode, the user needs only to identify the pertinent potions of the new data and what LRM and/or Geometry tables to add to. For more information see the “Working with the Interactive Multilevel LRS Conflation Command” chapter.

Multilevel LRS Conflation – Like the Interactive Multilevel LRS Conflation command, this command can be used to update an existing MLRS with new data from a separate linear feature class. The difference is that instead of interactively identifying related portions of new andexisting data, this command makes use of the Links database, which can be populated using GeoMedia Fusion. Even without GeoMedia Fusion, this command is useful for converting single-level LRSs into MLRSs. For more information see the “Working with the MultilevelLRS Conflation Command” chapter.

Multilevel LRS Validation – This is an Oracle-only command used to validate the MLRSs. It works in conjunction with the LRS Validation command to find MLRS data errors. For more information see the “Working with the Multilevel LRS Validation Command” chapter.


2-18

3-1

Introduction to Working with Multilevel LRSs

This chapter provides general guidance for working with Multilevel LRSs. The focus is on how to make use of a Multilevel LRS after its initial creation. It covers using this kind of LRS for analysis as well as the maintenance of the LRS. Therefore, this chapter is broken into two major sections: LRS Analysis using a Multilevel LRS

• Maintaining a Multilevel LRS

Before reading this chapter, it is recommended that you first read the “Multilevel Linear Referencing Systems (MLRS)” section of the “Introduction to Linear Referencing” chapter for a basic description of the GeoTrans Multilevel LRS data model. Also recommended is the “Single Level to Multilevel LRS Conversion Workflow” chapter for help in initial creation and population of a Multilevel LRS.

LRS Analysis Using a Multilevel LRS In this section, topics pertaining to performing analysis with a Multilevel LRS are examined. The topics to be explored are as follows: • Intelligent LRS features • Region IDs • Event location stability • Multiple LRM Support • Temporal analysis

Intelligent LRS Features Perhaps the key concept in using Multilevel LRSs is the role of intelligent LRS features. These features are created using the Display LRM command (see the “Working with the Display LRM Command” chapter) in conjunction with the LRS Metadata Definition command (see the “Working with the LRS Metadata Definition command” chapter). The LRS Metadata Definition command defines the tables that make up a Multilevel LRS and which fields in those tables play which roles. The Display LRM command uses that metadata to display an intelligent LRS feature class using the user’s selected LRM/Geometry combination.

This intelligent LRS feature class can then be used in any command that asks for “LRS Features.” The benefit is that intelligent LRS feature classes have extra information tagged


to them so that all LRS Model information is automatically filled out when it is used in LRS analysis.

Use the Display LRM command to create an intelligent LRS feature class.

Use Display LRM’s intelligent feature class with any command that asks for LRS features.

LRS model and properties are automatically filled in.

3-2


Region IDs A second key concept is Region IDs. One of the options given in the LRS Metadata Definition command (see the “Working with the LRS Metadata Definition Command” chapter) is to define Region IDs. This is a way of subdividing your network into logical units. This is usually done using political boundaries. As shown in the previous example, the Display LRM command (see the “Working with the Display LRM Command” chapter) allows you the option to filter your output by these region IDs. This provides a convenient way to minimize the amount of data you are working with at any particular time and thus to improve performance.

Region IDs are made even more useful by the ability to edit the Region settings of an intelligent LRS feature. This is done as with any query using the Query Properties dialog box. This means the Display LRM query does not have to be re-created as you move around to work with one region to another. Also, due to the dynamic pipe architecture of the GeoMedia products, queries based on this intelligent LRS feature class will update to reflect the new region settings.

Region IDs can minimize the amount of data being used and can improve performance.

3-3


Region ID settings can be edited. Analyses based on the intelligent LRS feature will update.

Event Location Stability The GeoTrans Multilevel LRS data model is designed to provide for event location stability. This topic is introduced in the “Event Location Stability” section of the “Introduction to Linear Referencing” chapter. This is an optional capability.

The basic principle is that route names, measures, and even geometric representations are volatile in that they may change over time. Therefore we recommend that you convert your event data’s location information to a non-volatile format. We refer to this non-volatile format as a Datum based location reference.

LRM

LRM

LRM LRM

LRM

LRM

LinearDatum

LRM

LRM

LRM LRM

LRM

LRM

LinearDatum

LRMLRM

LRMLRM

LRMLRM LRMLRM

LRMLRM

LRMLRM

LinearDatumLinearDatum

The Linear Datum is the foundation of Intergraph’s MLRS.

3-4


This location format conversion is implemented via a method referred to as Event Registration using the LRS Event Transform command. Simply choose the LRM to Datum transform mode when using this command. For linear events, also choose any attributes that you want to be proportioned in case events need to be split.

The LRS Event Transform command is used to perform Event Registration.

This is a one-time process. The resultant converted event feature class should be saved as the permanent version of the event table. That’s it! Your data has been protected.

To simplify usage of this converted event data, the commands that use event data have been modified to use either LRM based or Datum based event data. If all of your data is converted to a Datum based location format, you can use all of your event data together. So, for instance, guardrail data originally collected with one LRM can be analyzed versus accident data originally calculated using another LRM using the LRS Event Overlay command.

Event data that has been registered can be used directly with all of GeoMedia

Transportation’s commands that use event data. 3-5


Multiple LRM Support Although Event registration to a Datum based location reference is the recommended way to work with event data collected using various LRMs, it is not the only way. The LRS Event Transform command can convert event data directly from one LRM to another. Simply choose the LRM to LRM transform mode when using this command. For linear events, also choose any attributes that you want to be proportioned in case events need to be split. But note that by using this method, the benefits of event location stability are not attained.

The LRS Event Transform command can convert event data between LRMs.

Temporal Analysis The GeoMedia Transportation products are designed to be able to be used either with or without GeoMedia Transaction Manager. One can reap almost all of the benefits of using a Multilevel LRS without using GeoMedia Transaction Manager, with one exception. That exception is temporal data capture and analysis. GeoMedia Transaction Manager gives you the ability to model your network as it changes over time and then to use it for analyses such as evaluating the cost/benefit of various roadway improvement strategies or performing trend analysis for congestion, safety, and so on.

This subsection addresses temporal analysis. Temporal data capture is covered later in this chapter. In depth coverage of setting up and using GeoMedia Transaction Manager is covered in the Working with GeoMedia Transaction Manager document. This is only meant as an overview.

3-6


Regarding temporal analysis, there are two tools for reviewing data that represents a given time or time period. The first tool uses a “Valid Time filter.” This can be set using the Set Valid Time Options button on the Transaction Manager Settings dockable control, shown below. Simply set the Valid Time filter date to the date you want to see, and all the features in that connection will display the portion of your data that represents that date.

You can set which date you wish to view via the Transaction Manager Settings control.

The second tool is the Temporal Query command. This tools lets you pick a specific date as did the Valid Time filter, but it also has the option to pick a time range. It has two other differences. First, the Temporal Query command works on one feature class at a time as opposed to an entire connection. Second it can be run multiple times. That means you might want to show your road network as it was between 1995 and 2000 in one color and between 2000 and 2005 in another.

The Temporal Query command can be used to see a given date or a time range

3-7


Maintaining a Multilevel LRS In this section, topics pertaining to maintaining a Multilevel LRS are examined. The topics to be explored are as follows:

• Temporality During Editing

• Intelligent Editing

• Interactive Multilevel LRS Conflation

• Bulk Multilevel LRS Conflation

• Calibration

• Validation

• Routing

• Production tables

Temporality During Editing This subsection covers how to use GeoMedia Transaction Manager to capture real-world history while you are editing. In-depth coverage of setting up and using GeoMedia Transaction Manager is covered in the Working with GeoMedia Transaction Manager document. This is only meant as an overview.

GeoMedia Transaction Manager is designed to do several things, two of which are very pertinent to editing transportation networks. The first is long-term transactions. That means that while you are editing, your revisions are invisible to the normal user up until the point you have accepted them and are ready to reveal them to the general user population. You also have the option to discard some or all of your revisions. This way any “mistakes" can be made and caught before affecting general system users.

The second pertinent capability of GeoMedia Transaction Manager is capturing temporal history. By default it captures transactional temporal history. This means you can see what your database looked like at any point in time. However, much more important to transportation users is the optional ability to capture real-world temporal history. This means you can see the database’s representation of the world as it existed at any point in time. It can also be used to capture future representations of the world.

Both of these capabilities are very easy to use. The basic workflow is as follows:

1. Create a Revision Set (start an editing session).

2. Edit as usual.

3. Commit or Discard your changes, and Retire your Revision Set.

3-8


GeoMedia Transaction Manager is used for the first and third steps. The second step is the topic of the rest of this chapter that follows this subsection. You can think of GeoMedia Transaction manager as bookends that come just before and just after your normal editing.

The first step, creating a revision set, is very easy. Just use the New option of the Revision Sets command. The New Revision Set dialog box, shown below, has several key parts.

The Name and Description entries can be whatever you want and are usually used to describe the types of edits you are making. The Options section tells GeoMedia Transaction Manager whether you are using Pessimistic or Optimistic transactions. A full description of these choices is in the Working with GeoMedia Transaction Manager document, but Pessimistic is the correct choice in most situations.

The Valid from date is the date that you want your edits to represent. So, for example, if you are editing your network to show a curve realignment that went into service on 7/7/2003 and will stay in service indefinitely, you would fill out the dialog box as shown below.

If you know the date your changes will go out of effect, then use an actual date for the Valid until date as opposed to Valid until Modified. Lastly, but very importantly, if your edits are to represent some real-world change, you would check Capture Valid Time for Updates and Deletes, as shown here. However, if your edits are just to correct data, then you would not check either of these. Note that Inserts are always stamped with the Valid from/Valid until dates, so make sure to set these dates appropriately regardless of which capture Valid Time options you choose.

The New Revision Set dialog sets the parameters for editing with GeoMedia Transaction

Manager.

3-9


3-10

The New Revision Set dialog box sets the initial parameters for editing with GeoMedia Transaction Manager. Some of these options can be changed during an editing session using the Transaction Manager Settings control described earlier in this chapter.

The third step comes after you have made and reviewed your edits. At this point GeoMedia Transaction Manager has a Commit command to accept your edits or a Discard command to undo them. Lastly, you can use the Retire option under the Revision Sets command to close your editing session. More details are available in the GeoMedia Transaction Manager documentation.

Intelligent Editing GeoMedia Transportation Manager comes with a set of commands for interactively editing a Multilevel LRS. These commands are especially designed for working with Multilevel LRS data. For instance they know that the road name and measure data goes on the LRM level, that the geometry goes on the Geometry level, and that all levels need to be linked together. These are the five commands:

• Insert LRM Segment

• Delete LRM Segment

• Redigitize LRM Segment

• Split LRM Segment

• Merge LRM Segments

For consistency, all of these commands are designed to work with queries created by the Display LRM command. This has the added advantage of automatically picking which LRM/Geometry combination you want to edit. For cases where you want to edit multiple LRMs and/or Geometries at the same time, use the Interactive Multilevel LRS Conflation command.

Besides the fact that these commands are all Multilevel LRS, they also have some other special features. For instance, the Insert, Split, and Merge commands automatically handle measure attribution, the Redigitize command knows only to create new Datum segments where there are changes to the geometry, and the Merge command knows only to merge segments belonging to the same route.

A special note on using the Redigitize command: if your goal is to correct geometry and not to represent a change to the actual road, then you should use the Interactive Multilevel LRS Conflation command instead.

Interactive Multilevel LRS Conflation The Interactive Multilevel LRS Conflation command is an extremely flexible and useful editing tool. It can be used to add new data, update existing data, or delete old data. It also gives you complete control over which LRMs and Geometries you wish to work with.


3-11

The Interactive Multilevel LRS Conflation command is an extremely flexible data

maintenance tool

As opposed to interactively editing in new data, this command takes data from a linear feature class and transfers it to your Multilevel LRS. Therefore, the first step is to have or create a linear feature class that represents the changed version of your network. This feature class is referred to as the input linear feature class. If you are transferring LRM data, it is good practice to run this linear feature class through the steps in the “LRS Data Preparation Workflows” chapter.

The second step is to have a linear feature class that represents your linear datum. This is key because the linear datum is the index to all LRMs and Geometries in your Multilevel LRS. You can create a linear datum feature class using the Output Linear Datum command. You will be conflating from the linear feature class in the first step to your Multilevel LRS represented by your linear datum feature class.

The last step is interactively associating portions of the input linear feature class with correlating portions of the linear datum feature class. Actually, this correlation is only done in the Update mode, where you select a portion from both the input linear feature class and the linear datum feature class. In the Add mode, you only need to select from the input linear feature class, and the software knows to create new datum segments. Likewise, in the Delete mode, you only need select from the linear datum feature class because it is only deleting existing portions of the Multilevel LRS.


3-12

Bulk Multilevel LRS Conflation The Multilevel LRS Conflation command can be used to perform a number of tasks. These include:

• To convert a single level LRS to a Multilevel LRS

• To replace existing data with better data – for instance, replacing old geometry data with better data, such as GPS, without affecting existing route name and measure data

• To add LRMs – for instance, extending an existing LRS with a street address LRM

• To add Geometric representations – for instance, extending an existing LRS by adding a geometric representation created by another agency

• To process data updates – for instance, to perform updates from a periodically updated data source to update changed data, to add new data, and, optionally, to delete portions of the network that are no longer in service

• To add to existing data – for instance, to add roads related to new development

• To delete existing data – for instance, to delete a whole region’s worth of data or a particular LRM or Geometry

The Multilevel LRS Conflation command can be used to perform a wide variety of LRS

maintenance tasks.

Although the Multilevel LRS Conflation command is very useful, it is also potentially very harmful. This is because it works on your entire LRS at one time. So, always, always save your data prior to using this command. If you are using GeoMedia Transaction Manager, it is wise to start a new Revision Set just for this purpose. That way if there are


any problems, you can merely discard the changes, and your data will be back to its prior state.

Like the interactive version, this command also gives you complete control over which LRMs and Geometries you wish to work with. Likewise, it also works with an input linear feature class and a linear datum feature class. However, for many of its modes, it also makes use of another feature class type. This is a link feature class, a table that is created and populated using the GeoMedia Fusion product. This feature class is used instead of interactively correlating the input linear feature class with the linear datum feature class. GeoMedia Fusion calculates these correlations in a bulk fashion and stores the results in this table, which is named GMFLinear_Linked by default.

To create the links feature class is a three-step process. The first two steps are done with GeoMedia Fusion, and the last step is done with GeoMedia Professional.

The first step is to use GeoMedia Fusion’s Manage Conflation Rules command. With this command you set the parameters used by GeoMedia Fusion to create links. You tell it what two feature classes to correlate (the input linear feature class and the linear datum feature class) and how closely the two feature classes match. The parameters are described in GeoMedia Fusion Help Topics, but it is important to note that for transportation networks you should pick the Intersection processing option. The Intersection Tolerance is the farthest apart you expect the representations of the same intersection to be between the two feature classes.

3-13


3-14

The first step to creating the Links feature class is to tell GeoMedia Fusion the parameters to

use.

The second step is to have GeoMedia Fusion populate the links feature class. This is easily done be using the Create Conflation Links command. Again this command is described in full in the GeoMedia Fusion Help Topics.

The last step is reviewing the links and deleting bad links. This is the most tedious step, but it is absolutely necessary. Any automated process like GeoMedia Fusion’s Create Links command is going to create a certain number of bad links. It takes human judgment to pick out the bad links. There are many ways to accomplish this task, but here are some suggested steps:

1. Display Legend Entries for both the input linear feature class and the linear datum feature class. Wide lines in pastel colors are suggested. Turn the Locatable option off.

2. Display Legend Entries for the GMFLinear_Linked feature class. Since this feature class has four geometries, it will show up as four entries. You will only need GMFLinear_Liked and Conn2LinkedGeometry of GMFLinear_Linked. Thinner lines in darker shades of the same colors used in the previous step is suggested. Turn the Locatable option on.


3. Display a data window of the GMFLinear_Linked feature class.

4. Set the Map Window Properties to something like Fit items in select set – Fit and zoom out 150%.

5. Select each link in the data window. The corresponding link will show up in the map window. Keep those that are good. Delete those that are not good. Pay special attention at intersections.

6. Double check to make sure that all the bad links are gone.

Review the links created by GeoMedia Fusion in GeoMedia Professional.

Now that you have a good links feature class, you can run the Multilevel LRS command. Again, remember to back up your data before running this command. Since you probably deleted some links during your review, you may not have full links coverage of your dataset. To remedy this, you can use the Interactive LRS Conflation command to conflate the remaining unlinked portions.

Calibration After editing using the tools previously described, it is most often necessary to recalibrate at least some portion of the edited route. The two calibration tools in GeoMedia Transportation Manager have been upgraded so that they can be used with either single level or Multilevel LRSs. To use these commands with a Multilevel LRM, choose a Display LRM query as the feature class to be calibrated. The two calibration tools are:

• Interactive LRS Calibration (this is the tool used most often after editing)

• LRS Calibration

With Multilevel LRSs, these commands know they need to update the measures in the LRM table and in the cross-reference table that links the LRM to the linear datum. This is why it is important to update measures using one of the calibration tools rather than editing

3-15


measures in a Properties dialog box or in a data window because the LRM can get out of sync with its cross-reference table.

The calibration tools also perform another function. They assure that the directionality of the route is consistent. With single level LRSs, this can be done by either reversing geometry directions or, if a Boolean field is specified for reverse geometry, by simply setting the value of this field. For Multilevel LRSs, only this second option is available. Therefore it is important to specify a reverse geometry field when defining the metadata for a Multilevel LRS.

Validation There are two validation commands in the GeoMedia Transportation Manager product. Both are useful for assuring a good LRS that will produce accurate analysis results. Those two commands are:

• LRS Validation

• Multilevel LRS Validation (the current version works with Oracle connections only)

The Multilevel LRS Validation command checks for errors in the LRS.

The suggested workflow for validating a Multilevel LRS is as follows:

1. Run the Multilevel LRS Validation command.

2. Clean up any LRM/Geometry problems found.

3. Re-run the Multilevel LRS Validation command, and fix problems (if necessary) until all problems have been resolved.

4. For each LRM/Geometry combination, create a Display LRM query.

3-16


5. Open a data window on each Display LRM query, and check the status field for error conditions.

6. Run the LRS Validation command on each Display LRM query.

7. Clean up the anomalies found by the LRS Validation command.

Routing Multilevel LRSs can be used in routing as well as linear referencing. The pertinent routing attribution is stored in the LRM layer. The attributes associated with a routing linear feature is described in the “Introduction to Routing” chapter. Methods for populating these fields are described in the “Routing Data Maintenance Workflows” chapter.

There are some advantages to performing routing with a Multilevel LRS. For instance, there are a number of commercially available datasets that are suitable for routing but not for linear referencing. The LRS Calibration command can be used to populate minimal LRS attribution on these data sets, and then they can be conflated onto the MLRS as a separate LRM. As discussed in “The LRS-based Routing Restrictions Workflow” chapter, often linear referenced data, such as bridge capacities and land widths, can be useful to model routing restrictions. Even if these events were recorded using another LRM, the LRS Event Transform command can be used to convert them to the routing LRM.

Production Tables The tables that make up Intergraph’s Multilevel LRS are normalized for the most part. This is quite useful for data integrity during maintenance but is not always the best for performance during analysis. With that in mind, many agencies opt to periodically create de-normalized, read-only, single level “Production tables” for the general user. They are usually read-only because they are only copies of the original data and should not be used for any data maintenance.

This creation of production tables pertains to both LRS and Event data. For LRS data the process is as follows:

1. If using GeoMedia Transaction Manager, pick the date you want to create production tables for using the Valid Time filter on the Transaction Manager Settings control.

2. Create Display LRM queries for each LRM/Geometry combination you want to expose to your users.

3. Use the Output to Feature Class command to save the Display LRM queries to tables.

4. Use the LRS Metadata Definition command to define each of these tables as a single level LRS.

3-17


5. Use your database indexing options to index LRS key, measure, and Region ID fields.

6. Use your database security options to allow only read-only access to these tables.

7. If desired, you can create Display LRM queries of these single level LRSs and save them in a Library using GeoMedia Professional. This way your users will have the easiest possible access to your LRS data.

The creation of production tables for Event data can be done as follows:

1. If you are using GeoMedia Transaction Manager, make sure that your Valid Time filter is set as it was for the creation of the LRS production tables.

2. For each LRM represented in your production LRS tables, use the LRS Event Transform command to convert your datum-based Event data to LRM-based Event data.

3. Use the Output to Feature Class command to save the transformed Event data to tables.

4. Use your database indexing options to index LRS key and measure fields.

5. Use your database security options to allow only read-only access to these tables.

3-18

4-1

Working with the LRS Metadata Definition Command

The LRS Metadata Definition command allows you to define, modify, delete, and review the LRS Metadata settings. The metadata settings are stored in the same warehouse where LRS data is stored. This command allows setting LRS metadata for the Datum, Geometry the corresponding Geometry to Datum cross reference, LRM and the corresponding LRM to Datum cross reference, Region ID, and External Marker feature classes. The LRS Metadata Definition command allows metadata definition for single as well as multilevel LRSs.

Note: The LRS Metadata tables are required in the specified connection for the LRS Metadata Definition command to work. For Oracle databases, the metadata tables need to be created up front by an administrator in the GDOSYS schema by executing CreateLRSMetadata.sql script. For other databases, the LRS Metadata Definition command will detect the absence of metadata tables and will create the necessary ones.

As illustrated in Figure 1, a single level referencing system (SLRS) consists of one table storing LRS information. By contrast, a multilevel linear referencing system (MLRS) consists of one Datum, 1 to n LRMs (and LDXRefs), 1 to n Geometries (and GDXRefs), and optionally, one Region ID table.

This command ensures the uniqueness of LRS metadata definition names. For example, LRM metadata definition names should be unique among all the LRMs defined in that MLRS. Similarly, the names should be unique for Geometries and cross reference definitions in that MLRS. Additionally, the LRS names also should be unique for that connection.

Optionally, a Region ID field can be defined for both MLRS and SLRS. In case the Region ID feature class is defined for an MLRS, the Region ID fields of Datum, LRM, Geometry, and cross reference feature classes are required to be defined. In case of a SLRS, Region ID field name is required in the LRM definition.

For an SLRS, only one LRM is required to be defined. An SLRS can be redefined to be an MLRS, but the reverse is not allowed.

This command also has the capability to create new feature classes for LRM, Geometry, Datum, the respective cross reference, External Marker, and Region ID tables.


Figure 1

In this diagram, in terms of table or feature classes for each MLRS, you will see the following:

• One Datum table

• One or more Geometry tables

• One or more LRM tables

In addition to the tables listed above, you should also see cross reference tables for the following:

• Connecting a Geometry to Datum

• Connecting an LRM to Datum

The following figure is an entity relationship diagram to represent the data model.

4-2


The diagram illustrates the following:

• A LRS can be of single level or multi level.

• There can be multiple MLRSs or SLRSs in the system.

• Each MLRS will have one datum.

• Each datum can have multiple LRMs and multiple geometries.

• Each LRM table has a corresponding XREF table.

• Each Geometry table has a corresponding XREF table.

• XREF tables are used to implement many-to-many dynamic segmentation joints. This relates whole or partial datum segments to whole or partial LRM/Geometry segments.

• A SLRS will be associated with a single LRM.

• The LRM table assigned to a SLRS will have attribution for LRM keys, LRM measures, and Geometry.

• LRM tables assigned to a MLRS will have attribution for LRM keys and LRM measures.

4-3


The LRS Metadata Definition Command Workflow to Create New Metadata Definitions

1. Select the LRS Metadata Definition command.

2. Select a read-write connection from the Connection drop-down list. 3. Click New to display the Create New LRS Metadata dialog box.

4. Enter a name for LRS metadata and select the level.

4-4


5. If the LRS definition is multilevel, define a measurement tolerance value. This tolerance value is accessed and used by several commands that process MLRS data.

6. Optional: On the Region ID tab, check Use Regions if you need to define Region ID information. Enter a name for Region ID definition. Select the RegionID feature class and the corresponding fields. If a valid Region ID feature class is not available, create a new Region ID feature class by clicking the Create New button.

The default settings for the new feature class appear in the tab fields.

Note: Skip to step 8 while defining SLRS.

7. On the Datum tab, enter a name for datum definition. Select the Datum feature class and the corresponding fields. If a valid datum feature class is not already available, click Create New to create a new datum feature class.

The default settings for the new feature class appear in the tab fields.

8. On the LRM tab, click New to define new LRM definition.

The LRM Definition dialog box is displayed.

4-5


9. Enter a name for LRM definition; then select the LRM feature class. If a LRM feature class is not already available, click Create New to create a new LRM feature class. If the LRS is single level, the created feature class includes a geometry field.

Note: For single level LRS, the coordinate system assigned to the new feature class is set to the default specified for the target warehouse. You must therefore ensure that a coordinate system is set as default in the warehouse prior to running this command.

If a default coordinate system is not set, the following warning message will be displayed before table creation: "There is no default coordinate system set for target warehouse. A random coordinate system will be applied to the created feature class."

10. Select the LRS model and corresponding fields. 11. Click OK to dismiss the LRM Definition dialog box. 12. Click Datum XRef.

The Define LRM to Datum Cross Reference dialog box is displayed.

4-6


13. Enter a name for the LDXRef definition. Select a LDXRef feature class, or if a LDXRef feature class is not available, click Create New to create one.

14. Select LRM and datum fields; then click OK.

15. If the LRS model for the defined LRM contains external markers, select the Ext Markers button on the LRM tab.

The Define External Markers dialog box is displayed.

4-7


16. Enter a name for External Marker definition; then select the External Markers feature class. Click Create New to create a Markers feature class if a valid external marker feature class is not available. Select the corresponding key fields, and then click OK.

You are returned to the Create New LRS Metadata dialog box.

17. On the Geometry tab, click New to display the Geometry Definition dialog box.

18. Enter the Geometry metadata name. Select a geometry feature class or create a new one class if one is not available. Select the corresponding fields; then click OK.

4-8


19. Click Datum XRef on the Geometry tab to display the Geometry to Datum Cross Reference dialog box.

20. Enter the GDXRef metadata name. Select a GDXRef feature class or create a new class if one is not available. Select the corresponding geometry and datum fields; then click OK.

21. Click OK on the Create New LRS Metadata dialog box. The newly created LRS name is added to the LRS list box.

The LRS Metadata Definition Command Workflow to Modify an Existing LRS Definition

1. Select the LRS Metadata Definition command. 2. Select a read-write connection from the Connection drop-down list. 3. Select an existing MLRS definition from the LRS list box. 4. Click Properties to modify the selected LRS. 5. On the General tab of the LRS Metadata Properties dialog box, modify the name of

the LRS. (Note that the Level property of the LRS cannot be changed from multi to single while modifying an existing LRS database.)

6. On the Region ID tab, modify the appropriate properties. 7. (For MLRS) On the Datum tab, modify the appropriate properties.

4-9


4-10

8. Highlight an LRM definition in the LRM list box. 9. Click Properties on the LRM tab; then modify the appropriate properties. 10. (For MLRS) Click Datum XRef on the LRM tab; then modify the appropriate

properties. 11. Click Ext Markers; then modify the appropriate properties. 12. Optionally, new LRM definitions can be added or existing LRM definitions can be

deleted as needed on this tab.

13. (For MLRS) Click Properties on the Geometry tab; then modify the appropriate properties.

14. (For MLRS) Click Datum XRef on the Geometry tab; then modify the appropriate properties.

15. Optionally, new Geometry definitions can be added or existing Geometry definitions can be deleted as needed on this tab.

16. Click OK.

The LRS Metadata Definition Command Workflow to Review an Existing LRS Definition

The LRS Metadata Definition command allows you to review a selected LRS definition in a simple text box without bringing up multiple dialog boxes. You can also share the metadata information by saving the definition as a text file.

1. Select the LRS Metadata Definition command. 2. Select a connection from the Connection drop-down list. 3. Select an existing LRS definition from the LRS list box. 4. Click Display to review the selected LRS.

5-1

Working with the Interactive LRS Calibration Command

The Interactive LRS Calibration command can be used to write key and measure values to a group of linear features making up a route. This is what is known as calibrating the LRS. The Interactive LRS Calibration command calibrates the LRS one route at a time. The LRS Calibration command calibrates an entire feature class at a time but assumes that the feature class already has valid LRS Key values (see the “Working with the LRS Calibration Command” chapter).

The Interactive LRS Calibration command is designed to handle several scenarios. If you have, for example, digitized raw linework representing a network of roads, then you can use the command to define routes through the network and to write key and measure values to the features making up the routes. By adding the key and measure values to the raw linework, the feature class becomes an LRS feature class. A second example is to use this command to re-calculate measures for a portion of a route. For example, construction eliminates a sharp bend in a portion of a route, so the features from the construction zone to the end of the route need to have their measures adjusted. Defining a route to be calibrated is done by selecting linear features at the beginning and end of the route (or a portion thereof) in the map window. The software makes use of a shortest path algorithm to automatically select, in the proper sequence, the features in between the two selected features. This allows an entire route to be selected, often with just two mouse clicks. This is particularly handy for routes that have some segments that are so small that they are hard to select manually and are easy to accidentally overlook. This method requires that the linear feature class to be calibrated must be displayed in a map window. If the feature class is not displayed, the command will add the feature class to the legend and display it. If the LRS is a Display LRM query, the measure values are written to both the LRM layer and to the LDXRef layer of the model. The LDXref layer is modified only if the Display LRM query was created for Multilevel LRS data.

The command can fill in NULL values or overwrite existing values. The fields for the keys and measures must exist in the feature class before running the command, that is, the command will not create new fields. The command cannot be used to create new features or split existing features.

It also automatically sets the direction of the features within a route to match the overall direction of the route. Depending on the setting in the LRS Properties dialog box, this will either be done by setting the digitizing direction of each feature or by setting the value of a Geometry Reversed field to True or False as needed. This second method is often useful when working with queries that might have geometry that is not editable.

The measurement calculations can be performed in three ways. The first is to use the geometry lengths as the basis for measurement calculations. The second is to use length


field values on the segments themselves (if the value is NULL for a given segment, the geometry length will be used). The third way is to override any calculated measures and to key in measure values manually.

An important capability of this command is that it allows some features to be treated as gaps within the route, and it allows you to either use or not use the length of the gap features when calculating measures for the features making up the route. The gap segments themselves are not edited. A common usage of this is where a minor road meets a major road and then continues on some distance down the major road, like Route 250 in the image below. If desired, the length of road along the major route can be added to the measure of the minor route when it starts up again on the other side of the major route.

The Interactive LRS Calibration Command Workflow

This section presents the procedural steps for using the Interactive LRS Calibration command.

1. Open a GeoWorkspace that contains one or more read/write connections.

5-2


Note: Due to the dynamic nature of queries in GeoMedia, it is recommended that this command be run in a GeoWorkspace with a minimal number of active queries that are based on your LRS network. That is because you may pay a substantial performance penalty when running these commands while waiting for these queries to update.

2. Select Transportation > LRS Maintenance > Interactive LRS Calibration.

The Interactive LRS Calibration dialog box is displayed.

3. Select an LRS model from the LRS Model drop-down list. For more information on the different LRS Models supported, see the “GeoMedia Transportation LRS Data Structures” appendix.

Note: The measure values calculated and written to each feature making up a route will be Begin and End measures for the LRS Measure model type, and Begin and Duration for the LRS Duration model type.

4. Select an LRS feature class or query from the LRS feature drop-down list.

Note: If a query is used, it must have writable LRS key and measure fields. It also must have either editable geometry or have a writable Geometry Reversed field. This last part is so that the command can correct the digitizing direction if necessary.

5-3


5. Click Properties to define metadata for the LRS feature class, including LRS key field names, begin and end measure field names, and measure units. If the selected LRS feature is a Display LRM query, the LRS Model and the Properties are restored based on the special extensions available from the query, and they are made read-only.

The LRS Properties dialog box is displayed.

Note: See the “Working with the LRS and Marker Properties Dialog Boxes” chapter for more information on this dialog box.

6. Optional: Click Use a field value for segment length to designate a field containing a length value, which will be used instead of geometry lengths in the calibration calculations.

7. If you checked Use a field value for segment length, select a Length field name and a Length field unit from the two drop-down lists.

8. Click OK.

9. Follow the on-screen prompts to define a route by selecting features in the map window. First you will be prompted to “locate the first segment of the route, right click to exit.” After you select the first segment, you will be prompted to “locate the next segment of the route, right click to exit.” Repeat this until you have selected all the segments necessary to outline the desired route. You need not select every segment because the shortest path algorithm will select the intermediate segments. As you select each subsequent segment, the intermediate segments will be added to the highlighted selection.

10. Select End route from the pop-up menu (right mouse click) to display the Interactive LRS Calibration Options dialog box.

This pop-up menu allows you to (1) select End route to indicate that the route definition is complete and to display the LRS Calibration Options dialog box, (2) to select Discard last selected segments to discard the most recently selected segments and to continue defining the route, (3) to select Restart route to discard the entire route and to start over, or (4) to Exit command.

When you select End route, the Interactive LRS Calibration Options dialog box is displayed.

5-4


11. Select the appropriate Route Key and Measure Options.

Fill in all route key and measure values (overwrite existing) is the default option, and it is the only option available if the key values for all features in the route are Null. Selecting this option will update the key and measure fields for all features in the route. Fill in route key and measure values only on segments that either have Null keys or match the Input Route Key Values treats segments with keys that both do not match the selected route and are not Null as gaps. This option is available when some features making up the route have existing key values and some features have Null key values. When you select this option, only the features that match the selected route or that have Null key values will be updated with new key values and measures.

Fill in measure values on segments that match the input route key values treats all other segments as gaps. This option is available when at least some of the features in the route have existing key values and there is more than one set of existing key values. Select this option only when updating the measures for one of the existing sets of key values.

12. Define the Route Key Values either by typing in or by clicking on one of the existing keyset values in the tree view control. The number of key fields defined in the LRS Properties dialog box determines the number of boxes enabled.

Existing key values are displayed in a tree view, with the primary key as the parent, the secondary key as the first child, and so on. The tree view is disabled if all key values

5-5


5-6

for all features in the route are Null. Clicking on a parent, or any children of a parent, writes the key values into the Primary, Secondary, and so on, text boxes in the Route Key Values portion of the dialog box.

13. Select the appropriate Route Measure Options.

Ignore gap measures in route measure calculations is the default option. In this case only segments that are not considered to be gaps are used when calculating measures for the features making up the route.

Use gap measures in route measure calculations uses the length of the all segments, including gaps, when calculating the measures. If measurement attributes are available on the gap segments, the lengths defined by these attributes will be used; otherwise, the geometric length of gap segments will be used.

14. Define the Route Measures for both the Begin and End of the selected portion of the route, or the Begin measure and Duration length in the case of a Duration model. The default value for the Begin field will be the begin measure attribute of the first segment selected. If that value is Null, the default Begin field value will be 0. The default End field value will equal the default Begin field value plus the sum of the geometric lengths of all segments to be calibrated. If the Use gap measures in route measure calculations option is used, the default End field value will equal that value plus the lengths of the gaps. The gap lengths will be defined by measurement attributes if available; otherwise, it will be based on geometric lengths. If the Selected LRS feature is a Display LRM Query, the measures are written to both the LRM layer and to the LDXRef layer of the model.

15. Click OK to write Key and Measure values to the appropriate fields and records of the feature class. This will also set the direction of all segments to match the direction of the route. If a Geometry Reversed field was selected in the LRS Properties dialog box, then this will be accomplished by setting the value of this field rather than reversing the geometry.

16. Follow the prompts to define another route, or click Exit command from the pop-up menu to exit the command.

6-1

Working with the LRS Calibration Command

The LRS Calibration command can be used to write measure values to a group of linear features making up a route. This is what is known as calibrating the LRS. Linear feature classes that contain LRS Key and measure values can be defined as a Linear Referencing System, and can be used in analysis processes such as dynamic segmentation.

The LRS Calibration command calibrates an entire feature class at a time and makes use of the assumption that the feature class already has valid LRS Key values that define which features are grouped together as routes. On the other hand, the Interactive LRS Calibration command calibrates the LRS one route at a time and does not require that the LRS Key values be filled in ahead of time (see the “Working with the Interactive LRS Calibration Command” chapter).

The LRS Calibration command is designed to handle the scenario where you have a network of streets that are named (via key values), but which lack measures. You can then use this command to calculate and write measure values and correctly set feature directions to all of the features making up the street network. Because this command works on both linear feature classes and queries, you can also use it to calibrate or recalibrate portions of a network defined by a query. If the LRS is a Display LRM query, the measure values are written to both the LRM layer and to the LDXRef layer of the model. The LDXref layer is modified only if the Display LRM query was created for Multilevel LRS data.

The measurement calculations can be performed in two ways. The first is to use the geometry lengths as the basis for measurement calculations. The second is to use length field values on the segments themselves (if the value is Null for a given segment, the geometry length will be used).

Another influence on the way measures are calculated is the way gaps are handled. These gaps occur between portions of a route that are geographically disconnected. This usually occurs when one route intersects another route, follows along the other route for some distance, and then separates again. You are given three choices as to how these gaps influence measure values. The first method is to use the map distance across the gap. The begin measure of the first segment after the gap is equal to the end measure of the last segment before the gap plus the straight line distance across the gap. The second method uses a constant, typed in, distance for all gaps. The third method is to find the shortest path along the network across the gap. This method assumes that other members of the selected feature class, but with different key values, define a continuous path across the gap. In this case, the shortest path distance across the gap is determined and is used to calculate the measures.


6-2

An important capability of this command is that it automatically sets the direction of the individual features within a route to match the overall direction of the route. Depending on the setting in the LRS Properties dialog box, this will either be done by setting the digitizing direction of each feature or by setting the value of a Geometry Reversed field to True or False as needed. This second method is often useful when working with queries that might have geometry that is not editable.

The overall direction of the route can be determined by either of two methods: the digitized direction of the segments making up the route or by the compass direction of the route. To determine the route direction by the digitized direction, the lengths of all segments digitized in one direction are added, the lengths of all segments digitized in the opposite direction are added, and the route direction will be determined to be in the direction of greatest length. To determine route direction by compass direction, an imaginary line is drawn between the two end points of the route. The trend of this line, in the local coordinate system, will be either east-west or north-south. On rare occasions, when the trend is exactly between north-south and east-west, then northeast and southwest are grouped as north-south trends, and northwest and southeast will be grouped as east-west trends. You can select a South to North or North to South option, and a West to East or East to West option. Based on the user selection and the trend of the line, route direction and the begin and end of the route can be determined.

The LRS Calibration Command Workflow This section presents the procedural steps for using the LRS Calibration command.


Note: Due to the dynamic nature of queries in GeoMedia, it is recommended that this command be run in a GeoWorkspace with a minimal number of active queries that are based on your LRS network. That is because you may pay a substantial performance penalty when running these commands while waiting for these queries to update.

2. Select Transportation > LRS Maintenance > LRS Calibration.

Working with the LRS Calibration Command

The LRS Calibration Command dialog box is displayed.

3. Select an LRS feature class or query from the LRS features drop-down list.

Note: If a query is used it must have writable measure fields. It also must have either editable geometry or have a writable Geometry Reversed field. This last part is so that the command can correct the digitizing direction if necessary.

4. Select an LRS model from the LRS model drop-down list. For more information on the different LRS Models supported, see the “GeoMedia Transportation LRS Data Structures” appendix.

Note: The measure values calculated and written to each feature making up a route will be Begin and End measures for the LRS Measure model type, and Begin and Duration for the LRS Duration model type.

5. Click Properties to define metadata for the LRS feature class, including LRS key field names, begin and end measure field names, and measure units.


Note: See the “Working with the LRS and Marker Properties Dialog Boxes” chapter for more information on this dialog box.

6. Click OK.

6-3


6-4

7. If desired, click Use a field value for segment length to designate a field on the input feature class or query containing a length value, which will be used instead of geometry lengths in the calibration calculations.

8. If you checked Use a field value for segment length, select a Length field name and a Length field unit from the two drop-down lists.

9. Select one of the Route Direction options. Select By digitized direction if the digitized directions of the segments making up the route are used as the criteria for determining the overall direction of the route. In the case of a route that has conflicting digitizing directions, the direction that constitutes the majority of the length of that route will be used. Select By Compass Direction to use general compass directions as the criteria for determining the overall direction of the route. The direction of the route will determine the direction in which measures will increase.

10. If you chose the By Compass Direction option, select South to North or North to South and select West to East or East to West to determine how the command will orient the routes and in which direction the measures of the routes will increase.

11. Select one of the options for processing measures across gaps. If you select Map Distance as Gap Distance, the calibration continues across the gap, with the begin measure equal to the end measure of the previous segment plus the straight-line distance across the gap. Select Constant Gap Distance to specify a constant distance to be used in all gap calculations (key in a value in the Value field). Select Shortest path across gap if the gap is spanned by features with different key values (different routes). The command will use a shortest path algorithm to calculate the length of the gap and will add that distance to the end measure of the last feature before the gap to calculate the begin measure of the first feature after the gap.

Note: The Shortest path across gap option gives the most accurate results, but at a cost of extra processing time.

12. Click OK to kick off the calibration process, or Cancel to exit the command. The calibration process can take a fair amount of time to process so a status bar is provided to keep you informed if its progress. All measure fields within the input feature class or query will be updated, and the direction of all individual features will be set to match the direction of the route it belongs to. If a Geometry Reversed field was selected in the LRS Properties dialog box, then this will be accomplished by setting the value of this field rather than reversing the geometry.

7-1

Working with the LRS Validation Command

This section provides an overview of the LRS Validation command, which identifies anomalies in the feature classes to be used as the linear referenced network. The LRS may be made up of a single linear feature class that contains all the information necessary for defining the LRS, or it may also contain a point feature class that is used as Nodes. Anomalies that are found by the LRS Validation command can be corrected using standard GeoMedia Professional placement and editing commands. Later in this chapter we present a general step-by-step workflow that you can apply to your data.

Note: You must use the Multilevel LRS Validation Command for validating Multilevel LRS data.

The LRS Validation command is a preparation step that should be used before linear analysis is performed with an LRS analysis command such as the Dynamic Segmentation command or the Event Overlay command. This ensures that the proper results are returned by these analysis functions. The tasks outlined in this chapter are part of an overall data preparation workflow, which is described in the “LRS Data Preparation Workflows” chapter. The following checks are performed by the LRS Validation command, depending on the LRS model type you select:

• Missing LRS keys—Looks for records in the input LRS feature class that are missing the necessary LRS keys. An LRS feature class is a feature class that contains linear geometry; fields that define the routes (LRS Keys); and fields with either begin and end measures, or begin measure and duration.

• Missing Begin or End measures—Looks for records in the input LRS feature class that are missing begin or end (duration) values. For duration models, zero or negative duration values are also flagged.

• Missing node IDs—For node models, looks for records in the input LRS feature class that are missing the begin or end node ID values.

• Begin distance >= End distance—Looks for records in the input LRS feature class that have a begin distance greater than or equal to the end distance.

• Overlapping distances—Looks for records that have the same LRS key values and that contain overlapping distances between the end measure of one record and the begin measure of the next record in the input LRS feature class.


7-2

• Linear Measure/Geometry ratio—Calculates a ratio of the user-defined linear measure (end distance minus begin distance) to the measured map distance (length) for each record of the LRS feature class. If the calculated ratio is outside the range of the minimum and maximum values entered on the dialog box, an anomaly will be created for that record.

• Geometry sequence/direction problems—Determines if the digitized direction is consistent for the records in the input LRS feature class and checks for sequencing problems and gaps between geometries in a collection. If the LRS Measure or Duration with Node model is selected, the correct digitized direction will be determined through the direction defined by the Begin Node to End Node as this relates to the actual location of the referenced nodes. In addition, nodes that are not at the ends of the LRS feature are flagged as anomalies.

• Gaps between geometries—Looks for gaps between geometries in the input feature classes based on a user-specified tolerance and for gaps between geometries in records that have the same LRS key values. While gaps between geometries of a route are valid, gaps less than the minimum tolerance are flagged as possible digitizing errors.

You can output the anomalies as a query to a map window and/or a data window for evaluation and correction.

The LRS Validation Command Workflow

This section presents the procedural steps for using the LRS Validation command.

1. Open the GeoWorkspace connected to the data source containing the linear referenced network.

2. Select Transportation > LRS Maintenance > LRS Validation.

The LRS Validation dialog box is displayed


3. Click the LRS features drop-down list; then select the appropriate LRS feature for

validation. If the Selected LRS feature is a Display LRM Query, then the LRS Model and the Properties are restored based on the special extensions available from the query and are made read-only.

4. Click the LRS model drop-down list; then select the correct LRS model. For more on the different LRS Models supported, see the “GeoMedia Transportation LRS Data Structures” appendix.

You are returned to the LRS Validation dialog box.

5. In the LRS Feature Class portion of the dialog box, click Properties.


7-3


6. In the LRS Key Fields portion, select Primary, Secondary, Tertiary, and Quaternary keys of the LRS feature class for as many keys as you use.

7. In the LRS Definition Fields box, select the field names of the Start Measure and End Measure from the drop-down lists.

8. If you selected one of the node model types, select the field names of the Begin Node and End Node from the drop-down lists.

9. In the LRS Unit box, select the field name of the unit for the LRS feature class.

10. Click OK after setting the appropriate values.

The LRS Validation dialog box is returned.

11. In the Node Feature Class portion of the dialog box, click Properties.

The Node Properties dialog box is displayed.

12. In the ID field, select the ID for the Node feature class from the drop-down list.


The LRS Validation dialog box is returned.

14. From the Options portion of the dialog box, select and/or deselect the appropriate validation checks to be performed.

7-4


7-5

15. In the Output results as query portion, type the Query name or accept the default.

The results are saved as a query that can be edited and redisplayed in the workspace.

16. If you want 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 on and that the appropriate map window name is selected.

The Map window name field is enabled. The anomalies will be added to the legend and map window of your choice. You can choose an existing map window or create a new one. It is typically best to select an existing map window. In addition, you edit the line styles in order that the anomalies will be visible in the map window.

Note: The query is output to the map window as not locatable. The original LRS model feature class should be edited to correct each anomaly.

17. Optional: Click Style to define the display settings for the results in the map window.

18. If you want 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 on and that the appropriate Data window name is selected.

The Data window name field is enabled. The anomalies will be added to a data window of your choice. You can choose an existing data window or create a new one. It is typically best to create a new one.

19. When you have set the appropriate values, click OK.

20. When the results are returned, you can tile the windows vertically.

The GeoWorkspace would then resemble the following:


21. Correct any anomalies by using the GeoMedia Professional placement and editing

commands on the LRS feature class and the Node/Marker feature class, if used.

As mistakes in the input feature classes are corrected, the associated anomalies will disappear from the map and data windows. Once all of the anomalies are corrected, the data window will be empty, and the legend entry in the map window for the anomaly query will empty.

If you perform any new feature additions or edits on the input feature classes while the query is still active, the new and/or edited features will be checked for anomalies. If anomalies are found, entries will appear in the anomaly query and in any data window or map window that contains the anomaly query.

Note: Selecting a record in the data window will highlight the corresponding entry in the map window so that you can see where the problem occurred. Use the Fit Select Set command, and Zoom In to the area containing the anomaly, or use the Map Window Properties command to set automatic view manipulation options as features are selected. The primary key value of the LRS feature that has the error is included in the data window for quick reference. Double click on the LRS features in the map window to determine which one is in error, or you may prefer to display a data window for the LRS feature class. The geometry and attributes of the LRS feature, along with the textual description of the problem, should allow you to quickly determine the appropriate fix to make. Remember that the anomaly is there just to show you what and where the error is. You do not edit the anomaly. You must edit the input LRS and/or Marker feature classes to correct the problem.

7-6


Remember, not all anomalies need to be edited. Some things are flagged as errors based on parameter settings and may indicate possible anomalies. The (distance/geometry length) ratio and gaps between geometries less than the tolerance are examples of anomalies flagged that you may determine to be valid conditions. Use the Query Properties dialog box in GeoMedia to change the validation parameters.

Note (continued): There is no single workflow for correcting anomalies. Try different options, settings, and workflows until you determine which is most productive for you and your data. However, it is recommended that you begin the corrections at the beginning measure of the LRS and work toward the end of the LRS. It is also recommended that you correct any gaps in the LRS before validating geometry sequences.

7-7


7-8

Working with the Reformat Linear Collections Command

The Reformat Linear Collections command allows you to repair some of the problems common to data sets containing geometry collections. A geometry collection is a grouping of multiple geometries that are associated with a single record in the dataset. If left unrepaired, these problems can cause GeoMedia Transportation Manager to provide incorrect results.

It is common for CAD or MGE/MGSM data as served to GeoMedia via data servers to contain linear collections that are out of order or have incorrect/inconsistent digitizing directions. The Reformat Linear Collections command processes one linear collection at a time from the selected feature class or query in order to correct the above mentioned problems.

The processing of linear collections rearranges the vertices contained in the geometry. Linear collections that are connected end to end will be converted to polylines; whereas linear collections that contain gaps will remain as collections. The updated geometry is then written back to the database.

1 3 2

Geometry Collection

Before

1

Polyline

After

1 3 211 33 22

Geometry Collection

Before

1

Polyline

After As the process continues, the progress bar and status bar are updated to indicate the number of records processed. At the end of command execution, a message box is displayed to show information that consists of the number of records processed, the total number of records, the number of linear collections processed, the total number of linear collections, and the name and location of the log file, if generated.

On the command dialog box, you can either specify the location and name of the log file or accept the defaults. A log file is generated only if errors were encountered. Each error message reported to the log file is appended by the primary key name and its value.

You can interrupt processing of the command at any time by pressing ESC. Also, you can undo the command results with the GeoMedia Professional Undo command.

Since the Reformat Linear Collections command processes one feature at a time, it does not keep track of the direction of routes that consist of multiple features. The command will rearrange the vertices of a feature to be in the correct sequence and to be going in the right direction, but that direction could be wrong with regard to other features making up

8-1


the route. Such features will be flagged as anomalies by the LRS Validation command as it compares direction within a route. You can use the Reverse Direction command under the Edit > Geometry menu from GeoMedia Professional to fix direction problems on the flagged features.

If the input geometry has kickbacks or duplicate points, the Reformat Linear Collections command may not be successful in correcting the out-of-order or digitizing problems. You can use the Validate Geometry and Fix Geometry commands under the Tools menu from GeoMedia Professional to fix the kickbacks and duplicate points before using Reformat Linear Collections. For more on a workflow for preparing LRS data, see the “LRS Data Preparation Workflows” chapter.

Note: This command is provided primarily for LRS data that is imported from MicroStation design files. It may convert some linear collections to polylines.

The Reformat Linear Collections Command Workflow

This section presents the procedural steps for using the Reformat Linear Collections command.


2. Select Transportation > LRS Maintenance > Reformat Linear Collections.

Note: You must have an open read/write connection to use this command.

The Reformat Linear Collections dialog box is displayed.

3. From the Reformat linear collections in drop-down list, select a linear feature class or query to use as input to the command.

8-2

Working with the Reformat Linear Collections Command

The Output Errors to box is enabled.

4. In the Output errors to box, accept the default, or type in or browse to change the default name or location of the log file generated to report the processing errors.

5. Click OK to update the linear geometries in the selected feature class.

8-3


8-4

Working with the Create Intersection Markers Command

The Create Intersection Markers command provides a GUI for allowing you to create an Intersection Markers feature class for an input LRS feature class. The Intersection Markers feature class will be a point feature class that represents all valid intersections in the input LRS feature class. These markers are used by the Convert Intersection-referenced Events command to resolve the location of intersection-referenced events. Figure 1 is a sample intersection:

154°

87°267°

Main St.

Elm St.

Main St.1

Elm St.1

MarkerName

1

1

Occurrence

False

False

Dupl_Int

45.6

12.3

Measure

154-1Main St.Elm St.113

26787Elm St.Main St.112

AzimuthMinusAzimuthPlusCrossStreetLRMkeyID

Main St.1

Elm St.1

MarkerName

1

1

Occurrence

False

False

Dupl_Int

45.6

12.3

Measure

154-1Main St.Elm St.113

26787Elm St.Main St.112

AzimuthMinusAzimuthPlusCrossStreetLRMkeyID

Accident occurred on Main St. at 0.5 miles East of the intersection with

Elm St.

Sample Event Table

E

Direction0.5Elm St.Main St.

OffsetCrossStreetLRMkeySample Event Table

E

Direction0.5Elm St.Main St.

OffsetCrossStreetLRMkey

Figure 1 A sample intersection

This command makes the selection of LRS feature classes or queries and their corresponding LRS properties available to the user. The command will create intersection markers for the entire LRS feature class or query at every valid intersection. A valid intersection is any place where the end points of 3 or more segments coincide. This allows you great control over where intersection markers are created. For instance, overpasses and underpasses should have unbroken segments if you don’t want them to be considered. For assistance on how to break segments at intersections, see the "Intersection Preparation Workflows" chapter.

Another area where the user has great control is the calculation of the direction of each leg of the intersection. The direction of each leg of the intersection is calculated as the azimuth between the intersection and a point on the leg that is a user-specified distance from the intersection. If the specified azimuth calculation distance is greater than the length from the

9-1


intersection to the end of a particular LRS segment attached to it, the latter is used for calculating Azimuth values.

If your LRS has multiple LRS keys specified, the various keys of the cross street are concatenated to populate the CrossStreet field. The command allows you to specify which character is used to separate the individual LRS keys. In a related mannery, a MarkerName field is populated by concatenating the CrossStreet and Occurrence fields, because CrossStreet alone will not ensure uniqueness due to multiple intersections that may occur between the same two streets.

It is worth noting that this command solves the following common complications:

• Intersections can have any number of legs. This command will accommodate the intersections with two or more legs.

• The same two roads can cross more than once. This command provides an automated method to distinguish between the various places where the two roads cross.

Please note that some data sets have forks where there are three or more legs with the same LRS Key set values. The roads highlighted in red in the example shown below in Figure 2 - Forked Roads all have the same LRS Key values. Forking is unsupported in the current LRS commands and would be unsupported here as well.

Figure 2 - Forked Roads

As output a new intersection marker table with the following schema is added to the output connection.

9-2


9-3

Schema of Intersection Marker feature class

Intersection Marker Table

Field Description Data type

ID This is an autonumber key field. It uniquely defines each Marker record.

gdbLong (AutoNumber)

LRS key(s)

This is the “Occurred On” street. This consists of one to four fields and needs to match the OccurredOn field(s) in the Intersection-referenced Event table.

gdbText (1 to 4 fields)

Measure This is the measure of the Occurred On street at the point of intersection. gdbDouble

CrossStreet

This is the name of the Cross Street of the intersection. It is the Marker Name as well. This can only be one field, so it will be a concatenation (separated by selected delimiter) if more than one LRS key field is used.

gdbText

AzimuthPlus

This is the azimuth of the “Occurred On” street going from the intersection in the direction of increasing measure. If the “Occurred On” street terminates at this intersection, so that there are no measures on the LRS feature higher than the measure at the intersection, then this value will be -1 (as is the case with Elm St. in Figure 3: Sample Intersection Marker)

gdbText

AzimuthMinus

This is the azimuth of the “Occurred On” street going from the intersection in the direction of decreasing measure. If the “Occurred On” street originates at this intersection, so that there are no measures on the LRS feature lower than the measure at the intersection, then this value will be -1.

gdbText

Dupl_Int

This is a Boolean field that indicates whether the 2 streets identified by LRS Keys and CrossStreet intersect more than once. If they do intersect more than once (True) this creates an ambiguous situation for events referenced to those 2 streets.

gdbBoolean

Occurrence

For each time these 2 streets cross, this number will increment. So, if there are 2 times that two particular streets cross, there will be one intersection marker with an Occurrence value of 1 and another with an Occurrence value of 2. If the value of Dupl_Int is False, then the value of Occurrence will always be 1.

gdbLong


9-4

Intersection Marker Table Field Description Data type

MarkerName

This field is the concatenation of the CrossStreet field with the Occurrence field. This is done so that duplicate intersection markers have unique Marker Names.

gdbText

The Create Intersection Markers Command Workflow

This section presents the procedural steps for using the Create Intersection Markers Command

1. Invoke the Create Intersection Markers command.

2. In the LRS definition box, select an LRS feature class/query from the drop-down list.

3. Select either LRS Measure or LRS Duration as the LRS model.

4. Click Properties, and select the LRS properties from the LRS Properties dialog box.

5. In the Options box, first select an LRS key separator from the drop-down list, or type in a separator string. A separator needs to be specified only if multiple LRS keys are chosen while specifying the LRS properties.

6. Enter a positive value for the Azimuth calculation distance, and select an appropriate unit.

7. In the Output intersection markers to box, select a connection from the drop-down list where you want the Intersection Markers feature class to be created.


9-5

8. In the Feature class name text box, type in a name for the new feature class to be created.

9. In the Description text box, optionally type in a description for the new feature class to be created.

10. Click OK to create the Intersection Marker feature class.


9-6

10-1

Working with the Insert LRM Segment Command

The Insert LRM Segment command allows you to insert new LRM features by digitizing linear segments in a map window in multilevel LRS datasets. The command uses a Display LRM Query as input to identify the target feature classes for storing new segments. The Display LRM command places a few special extensions on each query that is used by the downstream commands for extracting LRS metadata information.

When you select a Display LRM query on the command dialog box, its LRS metadata extensions are verified. If the metadata settings point to a Region ID table, the values from that table are displayed in the Select Region ID combo box for selection.

The command enters a modeless state when you dismiss the dialog box by clicking OK. You are allowed to make mouse clicks in the map window to digitize linear features. A popup menu is available with a right mouse click to aid in data capture. When the digitizing is complete, the Properties dialog box is displayed to capture LRS key, measure, and other attribute LRM information. The LRS measure values are pre-populated based on the geometry feature’s length, which can be overridden by you.

Inputs are validated when you click OK on the Properties dialog box. You can cancel the feature placement by clicking Cancel.

The Insert LRM Segment Command Workflow This section presents the procedural steps for using the Insert LRM Segment command.

1. With an open GeoWorkspace, one or more read-write connections, and an active map window, invoke the Display LRM command.

2. Select the LRS, LRM, and Geometry metadata definitions to generate a Display LRM query.

3. Invoke the Insert LRM Segment command.


4. Select the Display LRM query that was generated by the Display LRM command for a multilevel LRS.

5. Optionally, select a Region ID value to populate new segments that are inserted. This control is enabled only if a Region ID table was identified while defining the LRS metadata for the selected Display LRM query.

6. Click OK to enter the modeless state, which allows you to insert new features by digitizing new geometries in the map window. You can exit by pressing ESC during the modeless state.

7. Follow the status prompt: Click to place point, ESC to exit command.

8. Start clicking in the map window to digitize new features.

9. Follow the status prompt: Click to place next point, ESC to exit command.

10. Click in the map window to place the second point.

11. Follow the status prompt: Click to place next point, double click to end.

12. Either select End LRM Segment from the right-click menu, or double click to insert the digitized segment. This menu item is enabled when at least two points have been placed in the map window.

The Properties dialog box will be displayed.

10-2

Working with the Insert LRM Segment Command

10-3

Note: Selecting Remove Last Vertex will remove the last vertex from the feature being digitized. Selecting Cancel LRM Segment will clear the dynamics and reset the command.

13. Enter LRS Key and other attribute information in the Properties dialog box.

14. Click OK on the Properties dialog box to insert a new LRM segment, or click Cancel to cancel any database changes.

15. Click in the map window to digitize subsequent segments.

16. Press ESC to exit the command.

Note: UNDO/REDO of the changes made by this command is only supported for Oracle connections.


10-4

11-1

Working with the Split LRM Segment Command

The standard GeoMedia Split command is capable of splitting a linear feature into two features. However, the standard command operates only on the geometry portion without any knowledge of the attribution. The Split LRM Segment command was designed to split an LRM segment from a multilevel LRS dataset into two segments and to adjust the measure attributes appropriately. The command also updates the corresponding features in the LDXRef layer to maintain the integrity of the data model.

When the command is invoked, the Split LRM Segment dialog box is displayed with a list of multilevel Display LRM queries. An error message is displayed if there are no multilevel Display LRM queries available in the GeoWorkspace. The command enters the modeless state when the dialog box is dismissed on selecting a query and clicking OK.

The features that belong to the selected query are highlighted when the mouse cursor is placed within their locate zone. Clicking on the highlighted feature specifies the split location (point). You are allowed to change the split location to be more precise by modifying the LRM measure value on the Split Confirmation dialog box. The command uses the Measurement Tolerance value defined in the LRS Metadata command to make sure that the split does not result in a segment(s) less than the tolerance value.

The command uses extensions available on the selected Display LRM feature to extract the corresponding LRM and LDXRef record(s).

Processing of the LRM layer:

• The LRM feature corresponding to the selection is deleted.

• Two new LRM features are added to replace the deleted one.

• The LRS Key attribution on the new LRM features is copied from the deleted LRM feature.

• The end measure attribute on the first new LRM feature is the split location specified by the user.

• The begin measure attribute on the second new LRM feature is the split location specified by the user.

• The rest of the attributes (non-LRS for which we do not have metadata) are copied from the deleted LRM record.


Processing of the LDXRef layer:

• The LDXRef features corresponding to the selection are deleted.

• Depending on the datum coverage of the deleted LDXRef records, the command creates two or more new LDXRef features. If all of the old LDXRef records belong to the same Datum ID, then only two LDXRef features are created; otherwise more than two LDXRef features are created.

• Datum measure attributes are computed to reflect the split result.

• LRM measure attribute values are copied from the corresponding LRM feature.

The command allows splitting multiple features within the same session. The command supports vector snaps to specify a split location on one of the features that belong to the selected Display LRM query. If multiple features are located at the specified split location, the pick-quick dialog is displayed to allow you to select the correct feature to be split. You can exit the command by pressing ESC.

The Split LRM Segment Command Workflow This section presents the procedural steps for using the Split LRM Segment command.

1. Invoke the Split LRM Segment command.

2. Select a multilevel Display LRM Query on the Select a display LRM query drop-

down list. 3. Click OK to enter a modeless state. 4. Status message: Click to specify split location, ESC to exit command.

5. Place the mouse cursor within locate tolerance of the display LRM feature to be split.

The feature is highlighted if it can be located based on the selected vector snaps.

6. Click to specify the split location. 7. If needed, alter the split location by using the Split Location dialog box.

11-2

Working with the Split LRM Segment Command

Note: This text box control displays the split location in LRM Units. The value you key in is validated by clicking OK. The specified split location should be greater than LRM Begin + Measurement Tolerance and less than LRS End – Measurement Tolerance.

8. Click OK to accept the split location, or click Cancel to return to the map window.

9. Status message: Click to specify split location, ESC to exit command.

10. Continue splitting other features within the same display LRM query, or press ESC to

exit the command.


11-3


11-4

12-1

Working with the Redigitize LRM Segment Command

The standard GeoMedia Redigitize command is capable of redigitizing the selected feature. However, the standard command operates only on the geometry portion of the feature if the data is stored in a single read-write feature class. The Redigitize LRM Segment command was designed to reshape an LRM segment that belongs to a multilevel LRS dataset and adjust the measure attributes appropriately. The command also updates the corresponding features in other layers of the data model to maintain data integrity.

Note: The Redigitize LRM Segment command is designed to work for “New” mode, where you are trying to capture real-world change by assigning a new datum for the changed geometry. However, for “Correction” mode, where there is no real-world change but you have a better understanding of what the real-world geometry is, you should run the Interactive Multilevel LRS Conflation command. That command will allow you to conflate the changed geometry to the existing datum.

The command is enabled when a single feature is placed in the select set. The select set contents are validated for the following conditions:

• Feature must belong to a multilevel Display LRM query.

• Feature must have valid LRS metadata extensions available.

• LRS metadata extensions must point to valid metadata settings.

• The connection storing MLRS data must be read-write.

• Feature must be a valid linear geometry.

• Feature must have valid LRS Key and measure attribution.

If the input does not satisfy any of the above listed conditions, the command exits by displaying an appropriate error message.

The Redigitize operation is performed by the command in two steps with the help of the LRS Conflation service:

• The portion of the LRM segment identified by the user for reshaping will be deleted from MLRS data (partial delete).

• New features are added to MLRS data for storing the new shape digitized by the user (add new).


12-2

The command uses LRS metadata extensions available on the selected Display LRM feature to extract the corresponding LRM, LDXRef, Datum, GDXRef, and Geometry records.


• The original LRM feature corresponding to the selection is deleted. • New LRM features are added for unchanged portion(s) of the original LRM feature. • The LRS key attribution on the new LRM features is copied from the old LRM feature.

• The measure attribution on the new LRM features is modified to reflect the gap created by reshaping the middle portion.

• One new LRM feature is added for the reshaped portion of the original LRM feature.


• The LDXRef feature(s) corresponding to the selection are deleted. • New LDXRef features for unchanged portion(s)are created to link the new LRM

features to the Datum.

• One new LDXRef feature is added for the reshaped portion to link the LRM feature to the new Datum feature.

Processing of the Datum layer:

• A new datum feature is created for the reshaped portion.

Processing of the GDXRef layer:

• The GDXRef feature(s) corresponding to the selection are deleted. • New GDXRef features for unchanged portion(s) are created to link the new Geometry

features to the Datum.

• One new GDXRef feature is added for the reshaped portion to link the Geometry feature to the new Datum feature.

Processing of the Geometry layer:

• The original Geometry feature corresponding to the selection is deleted. • New Geometry features are added for unchanged portion(s) of the original LRM

feature.

Working with the Redigitize LRM Segment Command

• One new Geometry feature is added for reshaped portion of the original LRM feature.

The Redigitize LRM Segment Command Workflow This section presents the procedural steps for using the Redigitize LRM Segment command.

1. Invoke the Redigitize LRM Segment command. • The selected MLRS Display LRM feature is displayed in dynamics. • Status Message: Enter starting point for redigitizing.

2. Click on the geometry (Display LRM feature) to define the starting point. • The dynamics are shown between the first point clicked and the position of the

mouse cursor. • Status Message: Enter end point for redigitizing.

3. Click on the geometry again to define the end point. • The segment that needs to be redigitized is in dynamics. • Status Message: Click to place next point. Double click to end.

4. Click in the map window to define the new shape for the feature. • The dynamics are shown between the first point clicked (on the feature) and the

current position of the mouse cursor.

• Status Message: Click to place next point. Double click to end. 5. Continue to click in the map window to define the new shape for the feature.

• The dynamics are shown between the previous point clicked (in the map window) and the current position of the mouse cursor.

• Status Message: Click to place next point. Double click to end. 6. Double click.

• The inputs are processed, and the database is updated with changes.

12-3


12-4

• The dynamics are cleared. The command is terminated.


13-1

Working with the Merge LRM Segments Command

The standard GeoMedia Merge command is capable of merging multiple linear features into one feature. However, the standard command operates only on the geometry portion without any knowledge of the attribution. The Merge LRM Segments command allows you to merge two or more LRM segments from a multilevel LRS dataset and to adjust the measure attributes appropriately. The command also updates the corresponding features in the LDXRef layer to maintain the integrity of the data model.

The command is enabled when two or more features are placed in the select set. The select set contents are validated for the following conditions. If the input does not satisfy any of these conditions, the command exits by displaying an appropriate error message.

• Features must belong to the same Display LRM query.

• Features must have valid LRS metadata extensions available. • LRS metadata extensions must point to valid metadata settings. • Features must have valid linear geometry. • All features must belong to the same LRS Key set. • All features must belong to the same Region ID (if available). • All features must have valid (non-null) LRM Key and measure attribution. • All features must be contiguous without any gaps. • There should not be a break in the LRM measure values. • The connection storing LRM and LDXRef features must be read-write.

If validation succeeds, the command uses LRS metadata extensions available on the selected Display LRM features to extract the corresponding LRM and LDXRef records.


• The LRM features corresponding to the selection are deleted. • One new LRM feature is added to replace the deleted ones. • The LRS Key attribution on the new LRM feature is copied from the old LRM

features.

• The begin measure attribute on the new LRM feature is the minimum of all the begin measure values from the deleted LRM segments.


13-2

• The end measure attribute on the new LRM feature is the maximum of all the end measure values from the deleted LRM segments.

• The rest of the attributes (non-LRS for which we do not have metadata) are copied from the first selected LRM record.


• The LDXRef features corresponding to the selection are deleted. • Depending on the datum coverage of the deleted LDXRef records, the command

creates one or more new LDXRef features. If all of the old LDXRef records belong to the same Datum ID, only one LDXRef feature is created; otherwise multiple LDXRef features are created (one per Datum ID).

• All of the new LDXRef features will point to the newly created LRM feature. • Datum measure attributes are adjusted to reflect the merge result. • LRM measure attributes are adjusted to reflect the merge result.

The Merge LRM Segments Command Workflow This section presents the procedural steps for using the Merge LRM Segments Command.

1. With a read-write connection existing, select two or more Display LRM features in the map or data window that share the same LRS key set and Region ID.

2. Invoke the Merge LRM Segments command.

3. If the validation fails, an error message is displayed with an appropriate message.

4. If the validation succeeds, the selected features are merged into one feature.

5. The Status prompt while merging: Merging features…

6. The command exits after processing is complete.


14-1

Working with the Delete LRM Segment Command

The Delete LRM Segment command was designed to delete one or more LRM segments from a multi-level LRS dataset. In addition to deleting the selected features from the LRM table, the command also deletes the corresponding features in the LDXRef layer to maintain the integrity of the data model.

The command is enabled when one or more features are placed in the select set. The select set contents are validated for the following conditions. If the input does not satisfy any of these conditions, the command exits by displaying an appropriate error message.

• Features must belong to a Display LRM query.

• Features must have valid LRS metadata extensions available.

• LRS metadata extensions must point to valid metadata settings.

• Features must have valid linear geometry.

• The connection storing LRM and LDXRef features must be read-write.

If validation succeeds, the command uses extensions available on the selected Display LRM features to extract the corresponding LRM and LDXRef records.


• The LRM features corresponding to the selection are deleted.


• The LDXRef features corresponding to the selection are deleted.

The Delete LRM Segment Command Workflow This section presents the procedural steps for using the Delete LRM Segment Command.

1. With an active map window and a read-write connection, place one or more (multilevel) Display LRM query features in the select set.

2. Invoke the Delete LRM Segment command.

3. The Status prompt: Validating select set…

4. A message box is displayed to confirm the deletion.

5. Clicking Yes will delete the selected LRM features and the corresponding LDXRef features.


14-2

6. The Status prompt: Deleting selected features…

7. The command exits after processing.

8. Clicking No on message box will exit the command without deleting the selected features.


15-1

Working with the Output Linear Datum Command

An MLRS consists of one Linear Datum, one or more LRMs, one or more Geometry tables, and other required cross-reference tables. The Linear Datum layer does not have any geometry; instead the geometry is stored in the geometry layer made of one or more tables, which allows for multiple cartographic representations. The Output Linear Datum command provides a GUI for generating geometry for linear datum segments in a multilevel LRS by processing the data in Datum table, in one or more Geometry tables, and in the corresponding GDXRef tables. The main purpose of this command is to aid the two conflation commands that are used to associate new data to the existing linear datum.

The datum coverage is computed from one or more geometry sources selected as input to the command. The results are output to a static feature class in the target warehouse.

You are allowed to select a connection that contains the datum and geometry sources. Upon selecting the connection, LRS metadata is queried to display a list of available multilevel LRS definitions. When a particular multilevel LRS is selected, the corresponding geometry metadata definitions are listed. You can select one or more geometry sources from the list box. By default, the geometry sources are listed in the order returned by LRS Metadata service; you can change the order by selecting an item and moving it up, down, last, or first. The geometry sources are processed to generate geometry for each datum record. You can also generate datum coverage only for a particular region(s) by specifying the Region IDs.

For each unique Datum ID in the Datum table, the command sequentially searches its coverage across one or more selected geometry sources in the given order until it finds 100% coverage or until it runs out of sources. The static representation of the datum is outputted to a table in the target warehouse. The coordinate system for the output geometry is determined by the first geometry source selected in the list.

The output Datum recordset generated by the command includes the following fields:


15-2

Field Name Field Type Description

ID gdbLong Database Key, AutoNumber.

DatumID gdbLong ID value copied from the Datum table

DatumLength gdbDouble Length value copied from the Datum table.

RegionID gdbText Region ID value copied from the Datum table.

GeometryID gdbLong ID value of the Geometry

table record from which

output geometry was

extracted.

GeometrySource gdbText Name of the geometry table from which output geometry was extracted.

DatumStartMeasure gdbDouble Datum start measure value.

DatumEndMeasure gdbDouble Datum end measure value.

Geometry gdbSpatial, gdbLinear

Geometry generated.

Working with the Output Linear Datum Command

The Output Linear Datum Command Workflow This section presents the procedural steps for using the Output Linear Datum command.

1. With an open GeoWorkspace, one or more read-write connections, and an active map or data window, invoke the Output Linear Datum command.

2. In the Select multilevel LRS box, select the Connection that contains multilevel data

from the drop-down list.

3. In the Name field, select the multilevel LRS for which datum is to be generated.

4. Select the geometry sources for generating datum in the Select geometry source(s) box.

5. Alter the order of geometry sources by selecting an item and moving it up or down.

Note: the Select All control selects all the geometry definitions in the list, and the Unselect All control unselects all the geometry definitions in the list.

15-3


15-4

6. By default, the Filter by check box is off, which will generate the linear datum for the complete dataset. If you would like to limit the generation of linear datum to certain regions, select one or more Region IDs from the list.

7. In the Output linear datum to box, select a read-write Connection for outputting datum results.

8. Key in a valid name for the output feature class in the Feature class name box.

9. Key in an optional Description.

10. Display the results in a map window and/or in a data window by selecting the corresponding check box.

11. Click OK to process the inputs and output the linear datum.

OR

Click Cancel to dismiss the dialog without any processing.

16-1

Working with the Interactive Multilevel LRS Conflation Command

The Interactive Multilevel LRS Conflation command is developed to address the problem of updating an existing Linear Referencing System (LRS) with new data. The command allows you to interactively identify the portions of new or old data that need to be added, updated, or deleted from the existing LRS. When compared to the bulk version of the Conflation command, the interactive one gives you more control in creating associations between the old and the new representations of the data.

A Multilevel LRS (MLRS) consists of a Linear Datum, one or more LRMs, one or more Geometry tables, and other required cross-reference tables. One of the harder tasks involved in performing updates to an MLRS data model is figuring out these data set associations between the new data and the linear datum (old data). For one thing, the two data sets are very likely to have different segmentations, so the associations have to be done between parts of instances. Secondly, the same transportation network can be represented in very different ways, as shown in the following illustration:


8080

Keystone Ave.

New

Datum

New

Datum

Significant location

differences

Significant location

differences

Dual vs. Single Repercussions

Or should these points correlate?

Or should these points correlate?

Dual vs. Single

Centerline

Dual vs. Single

Centerline

The Interactive Multilevel LRS Conflation command lets you define these associations by making selections in a map window. The associations thus defined are used to identify linkages between the old data and the new data. These linkages are equivalent to Link features generated by the GeoMedia Fusion product and used in the Multilevel LRS Conflation command.

The command dialog box allows you to specify the mode, source connection for MLRS, input linear features (new-data), and linear datum features (existing data as generated by the Output Linear Datum command). When the command is invoked for the first time in a session, Update mode is selected as default, but it can be changed either on the main dialog box or from the right-click popup menu. On clicking OK on the main dialog box, the command will enter modeless state to allow selections in the map window.

To simplify the selection of linear features, the command makes use of network pipes for computing the best path between any two stops. The resultant path, which is optimized by distance, forms the input for processing. The stops and paths are displayed in dynamics as the selection progresses. Status prompts are displayed to guide you through the selection process. A right-click popup menu is provided to change mode, to delete the last stop, to delete all stops and to start over, to process inputs, or to exit the command. Shortcut keys are also allowed for each popup menu entry.

You can limit the Conflation edits to fewer portions of their MLRS data by using Region IDs. If a Region ID table was defined during the LRS Metadata step, the Region ID controls will be available on the MLRS Properties dialog box. The dialog box also allows you to define a constant or variable Region ID value for new and updated features.

16-2


The Interactive Multilevel LRS Conflation Command Workflow

This section presents the procedural steps for using the Interactive Multilevel LRS Conflation command.

1. With an open GeoWorkspace, one or more open read-write connections, and an active Map window, invoke the Interactive Multilevel LRS Conflation command.

2. Select one of three options for processing: Add, Update, or Delete.

3. Select a linear feature class or query as a source of new data for the conflation process from the Select input linear features drop-down list.

4. Select a connection where the Multilevel LRS data is stored from the Select multilevel LRS drop-down list.

5. Select a LRS metadata definition name from the Name drop-down list.

6. Click Properties to bring up MLRS Properties dialog box.

16-3


7. Check Filter by Region ID if the conflation process should be limited to certain portions of the MLRS data defined by the selected Region IDs.

8. Check Copy Region ID value from check box if the new records are to be populated with Region ID values. The GUI allows for selection of a constant Region ID value from the Region ID table or a variable value stored as an attribute in the Input (new data) features.

9. Check the LRMs that are to be conflated in the Select LRM definitions box.

10. For each LRM checked, click Mappings to display the mapping dialog box that defines the source attribution.

16-4


11. On the MLRS Properties dialog box, choose the definitions that are to be conflated on the Select Geometry definitions box.

12. Click OK to dismiss the MLRS Properties dialog box.

13. On the Interactive Multilevel LRS Conflation dialog box, use the Select linear datum features drop-down list to select the source of existing data.

14. Click Properties to bring up the Linear Datum Properties dialog box.

15. Select the Datum ID, Start measure, and End measure from the drop-down lists. The Measure unit shown in read-only mode is the Datum length unit specified on the LRS Metadata command.

16. Click OK to dismiss the Linear Datum Properties dialog box.

16-5


17. Click OK on the Interactive Multilevel LRS Conflation dialog box to start the modeless state, or click Cancel to exit.

18. Add mode:

a. Status message: ADD: Click on Input features to add stop, ESC to Exit command.

b. Click on the input features to define the starting point.

c. Status message: ADD: Click on Input features to add next stop.

d. Identify the ending point or intermediate points by clicking on the input features.

e. Status message: ADD: Click on Input features to add next stop, double click to process inputs.

f. Select Process Add from the right-click menu to add the selected features to the MLRS.

19. Update mode:

a. Status message: UPDATE: Click on Input features to add stop, ESC to Exit command.

b. Click on the input features to define the starting point.

c. Status message: UPDATE: Click on Input features to add next stop.

d. Identify the ending point or intermediate points by clicking on the linear datum features.

e. Status message: UPDATE: Click on Input features to add next stop, double click to process inputs and select linear datum features.

f. Select datum features from the right-click menu to reset the command for the next set of inputs.

g. Status message: UPDATE: Click on Linear Datum features to add stop, ESC to Exit command.

16-6


16-7

h. Click on the Linear datum features to define the starting point.

i. Status message: UPDATE: Click on Linear Datum features to add next stop.

j. Identify the ending point or intermediate points by clicking on the input features.

k. Status message: UPDATE: Click on Linear Datum features to add next stop, double click to process inputs.

l. Select Process Update from the right-click menu to update the selected portions of the MLRS with new features.

20. Delete mode:

a. Status message: DELETE: Click on Linear Datum features to add stop, ESC to Exit command.

b. Click on the Linear datum features to define the starting point.

c. Status message: DELETE: Click on Linear Datum features to add next stop.

d. Identify the ending point or intermediate points by clicking on the linear datum features.

e. Status message: DELETE: Click on Linear Datum features to add next stop, double click to process inputs.

f. Select Process Delete from the right-click menu to delete the selected portions of the MLRS.

21. Press ESC, or select Exit command from the right-click menu to exit the command.



16-8

17-1

Working with the Multilevel LRS Conflation Command

The Multilevel LRS Conflation command allows you to selectively update an existing Multilevel Linear Referencing System (MLRS) with new data. This capability has many uses, including:

• To convert a single level LRS to a Multilevel LRS (see the “Single Level to Multilevel LRS Conversion Workflow” chapter)

• To replace existing data with better data – for instance, replacing old geometry data with better data, such as GPS, without affecting existing route name and measure data

• To add LRMs – for instance, extending an existing LRS with a street address LRM

• To add Geometric representations – for instance, extending an existing LRS by adding a geometric representation created by another agency

• To process data updates – for instance, to perform updates from a periodically updated data source to update changed data, to add new data, and, optionally, to delete portions of the network that are no longer in service

• To add to existing data – for instance, to add roads related to new development

• To delete existing data – for instance, to delete a whole region’s worth of data or a particular LRM or Geometry

This LRS conflation command is designed to work with a Multilevel LRS (MLRS). Support of MLRS allows enhanced support of multiple Linear Reference Methods (LRMs), support for multiple cartographic representations, and, perhaps most importantly, MLRS provides better event stability, even over time. One of the keys to a MLRS providing these benefits is the presence of a stable Linear Datum that anchors the MLRS. Because of this, one of the key requirements of this command is to maintain the stability of the Linear Datum.

In order to maintain the Linear Datum, you need to know which parts of the new data correspond to each part of the existing MLRS. Then, when the old data is replaced with the new data, the new data can be associated to the same part of the Linear Datum, thus assuring stability. In this way, the command assures that any previous datum-referenced events from the old MLRS will still show up in the same relative location in the new MLRS.

One of the harder tasks involved in performing LRS conflation is figuring out these data-set associations. For one thing, the two data sets are very likely to have different segmentations, so the associations have to be done between parts of instances. Secondly,


the same transportation network can be represented in very different ways, as shown in the following illustration.

In this case, you can make use of a separate tool, such as GeoMedia Fusion, to perform the associations and to save them in a database. Then the associations are used to make the actual changes to the MLRS. GeoMedia Fusion is designed to automate the creation of these linkages as much as possible, but it also has tools for manually reviewing and editing these association links. The links define the association between the new (linear) dataset and the linear datum features that are generated by the Output Linear Datum command.

The Multilevel LRS Conflation command uses the linkages created by the GeoMedia Fusion product to know which parts of the new data correspond to each part of the existing MLRS.

It is recommended that you read the “Multilevel Linear Referencing Systems (MLRS)” section of the “Introduction to Linear Referencing” chapter for an overview of Multilevel LRSs. Also, information on how to perform analysis with, and data maintenance on, a Multilevel LRS is presented in the “Working with Multilevel LRSs” chapter.

The Multilevel LRS Conflation command offers you the following three options for data processing-

• Create new MLRS features from all input LRS features – Choose this option to convert a source linear feature class (single level LRS) into a Multilevel LRS.

17-2


17-3

• Update existing MLRS data by – Choose this option to use a source linear feature class to update existing MLRS data in one or more ways, as described below. This option uses linkages to determine how new data is associated to the existing MLRS data.

o Adding and/or Replacing MLRS features from linked portions of input features – Existing MLRS data is replaced by the new data while adding features that did not exist.

o Adding new MLRS features from unlinked portions of input LRS features – Selecting this option copies the new data which does not have a link to MLRS data.

o Deleting unlinked portions of MLRS features – Choose this option to delete all portions of the MLRS data that does not have a link to new data.

• Delete all MLRS features – Select this option to delete all features from selected MLRS tables. Use this setting with caution. Optionally, you can limit the deletion to certain portions of the dataset by using Region IDs.

Although the Multilevel LRS Conflation command is very useful, it is also potentially very harmful because it works on your entire LRS at one time. Therefore, always save your data prior to using this command. If you are using GeoMedia Transaction Manager, it is wise to start a new Revision Set just for this purpose. That way if there are any problems, you can merely discard the changes to return your data back to its prior state.

The Multilevel LRS Conflation Command Workflow 1. Open a GeoWorkspace that contains one or more readable-write connections. 2. Select Transportation > LRS Maintenance > Multilevel LRS Conflation.

The Multilevel LRS Conflation dialog box is displayed.


3. Select the Process options. You can choose one of the following options:

• Create new MLRS features from all input LRS features

• Update existing MLRS data. If this option is selected, you choose one or more sub-options.

− Adding and/or Replacing MLRS features from linked portions of input LRS features.

− Adding new MLRS features from unlinked portions of input LRS features.

− Deleting unlinked portions of MLRS features.

• Delete all MLRS features

4. Select the name of the conflation links features under the Select conflation link features drop-down list.

5. Select the Properties button to select the key fields.

The Link Feature Properties dialog box is displayed.

17-4


6. The Fusion product divides the link features into various link sets, one for each run.

You can select a link set name to identify the set of link features to be used for the conflation process. If a link set name is not selected, all link features will be used.

7. Select the key fields from the links feature class. These fields should match the selections made during the link generation step performed with the GeoMedia Fusion product. Click OK.

You are returned to the Multilevel LRS Conflation dialog box.

8. Select the name of the input linear feature class. This is the source of new data for the conflation process.

9. Select the Multilevel LRS to modify using the Connection and Name drop-down lists.

10. Click Properties under the Name drop-down list to define MLRS properties.

The MLRS Properties dialog box is displayed.

17-5


11. Choose the Filter by Region ID setting to limit the conflation process to selected

Regions. The Copy Region ID from setting allows two ways to copy Region ID information from Input linear features to MLRS data. If all of your data that you are processing at this time is from a single region, you can simply pick that region from the Region ID table list. However, the most common case is that the Region ID is contained in one of the fields in your source linear feature class. In that case, you can specify the name of that field by using Input feature attribute. The Region ID controls are available for selection only if Region ID settings were defined in the LRS Metadata creation step.

12. Select which LRMs and/or Geometries within the MLRS to work with. 13. For LRMs, source attribution should be defined by clicking Mappings.

The Input Feature To LRM Mappings dialog box is displayed.

17-6


14. Select the source fields to copy the values to the MLRS dataset. Optionally, if you

have other non-LRS fields which do not have metadata, select a source field and target field, and add them to the Selected attribute pairs list box.

15. Click OK to return to the MLRS Properties dialog box. 16. Click OK to return to the Multilevel LRS Conflation dialog box. 17. Select the name of the Linear Datum features. You can select key fields from the

Linear Datum feature class by clicking Properties.

The Linear Datum Properties dialog box is displayed. 18. Select the key fields, and click OK.

You are returned to the Multilevel LRS Conflation dialog box. 19. Click OK to conflate the data.


17-7


17-8

18-1

Working with the Multilevel LRS Validation Command

The Multilevel LRS Validation command provides a GUI to validate the Multilevel LRS model for Oracle read-write connections only. The anomalies found during the validation process are inserted into the selected LRSANOMALIES table.

Note: In Oracle Object read-write data servers, the LRSANOMALIES table has to be created by the database administrator by using the delivered SQL script (CreateLRSAnomalies.SQL).

The command will validate the data integrity rules of a Multilevel LRS model. Some of the checks ensure that measures are correct and that there are no orphaned records in any of the tables. When the command comes across an anomaly, its description and the details about the location are reported to the LRSANOMALIES table. Results from each run are grouped by the session ID value.

The Session ID value is generated by concatenating the Oracle User Name with the User-entered session name and the time stamp that was used when the validation process was started. A semicolon (‘;’) is used as the concatenating character. The Session ID format is as follows: USERNAME;SESSIONNAME;TIMESTAMP. An example Session ID is “GMTRANS_KV;LRM_Meas, Geom Validation;09-05-200613:44:31”.

Once the data layers have been verified and fixed (via standard GeoMedia tools), you can use the output from the Display LRM command as input to the LRS Validation command in order to find traditional errors, such as overlapping measures or digitizing/sequence problems.

Data Integrity RulesIn validating a Multilevel LRS model, the Multilevel LRS Validation command ensures that the following rules are not broken:

• All segments of the model must link to some portion of the Datum, but a portion of the Datum can exist without Geometries or LRMs.

• A geometry table and its associated cross-reference table are completely independent from any other geometry table and its associated cross-reference table.

• An LRM table and its associated cross-reference table are completely independent from any other LRM table and its cross-reference table.


18-2

• A geometry table and its associated cross-reference table are completely independent from an LRM table and its associated cross-reference table.

• This command does not validate across the Datum. • A datum record can have 0, 1, or more DatumToGeometryXRef records linked to

it.

• The geometry measure values in a DatumToGeometryXRef record can increase or decrease from begin to end. Decreasing measures indicate the geometry is reversed with respect to the datum.

• A datum record can have 0, 1, or more LRMToDatumXRef records linked to it. • The datum measure values in an LRMToDatumXRef record can increase or

decrease from begin to end. Decreasing measures indicate the LRM is reversed with respect to the datum.

Geometry Rules The following list of rules is used to test the validity of the geometry side of the model. The anomaly descriptions and Anomaly ID values associated with each anomaly are also shown below:

Anomaly Rule Reported Anomaly Description

Reported Anomaly ID

Any DatumToGeometryXRef record and its associated geometry records, that is not linked to a datum record, is invalid.

GDXRef record is not linked to a Geometry record.

101

Any Geometry record that is not linked to a DatumToGeometryXRef record is invalid.

Geometry record is not linked to a GDXRef record.

102

Any DatumToGeometryXRef record that is not linked to a Geometry record is invalid.

GDXRef record is not linked to a

Geometry record.

103

A Geometry record can be linked to one or more DatumToGeometryXRef records. The total length of the geometry measures (GeomEnd – GeomBeg) in the DatumToGeometryXRef records must equal the length (GeomEnd – GeomBeg) in the Geometry record.

Sum of measures with specified datum id in GDXRef table exceed the Geometry length.

104


18-3

Anomaly Rule Reported Anomaly Description

Reported Anomaly ID

When multiple DatumToGeometryXRef records are linked to one Geometry record, there cannot be gaps or overlaps of geometry measures in the DatumToGeometryXRef records

Geometry measures with specified unique ID are overlapping or having gaps in GDXRef table.

105

The total length of the datum measures (DatumEnd – DatumBeg) in the DatumToGeometryXRef records linked to a datum record, cannot exceed the length of the datum.

Sum of measures with specified datum ID in GDXRef table exceed the datum length.

106

The datum measure values in a DatumToGeometryXRef record must always increase from begin to end.

GDXRef record datum measures must always increase from begin to end.

107

All measure values must contain a valid value. NULL values for ID and measures are not allowed.

NULL is not a valid measure value.

108

Zero lengths are not allowed. Length should be greater than zero.

109

All Geometry records associated with the same Datum ID should have the same Region ID value.

Region ID associated with the Geometry segment does not correspond with that of the corresponding Datum segment.

110

All GDXRef records associated with the same Datum ID should have the same Region ID value.

Region ID associated with the GDXRef segment does not correspond with that of the corresponding Datum segment.

111


18-4

LRM Rules The following list of rules is used to test the validity of the LRM side of the model. The anomaly descriptions and the Anomaly ID values associated with each anomaly are shown below:

Anomaly rule Reported Anomaly

description Reported

Anomaly ID

Any LRMToDatumXRef record and its associated LRM records, that is not linked to a datum record, is invalid.

LDXRef record is not linked to a Datum record.

201

Any LRMToDatumXRef record that does not have an associated LRM record is invalid.

LDXRef record is not linked to a LRM record.

202

Any LRM record that is not linked to a LRMToDatumXRef record is invalid.

LRM record is not linked to a LDXRef record.

203

An LRM record can be linked to one or more LRMToDatumXRef records. The total sum of the LRM measures (LRMEnd – LRMBeg) in the LRMToDatumXRef records must equal the measure (EndMeasure – BegMeasure) in the LRM record.

Sum of measures with specified datum ID in LDXRef table exceed the LRM length.

204

When multiple LRMToDatumXRef records are linked to one LRM record, there cannot be gaps or overlaps of the measures in the LRMToDatumXRef. records

LRM measures with specified unique ID are overlapping or having gaps in LDXRef table.

205

The total length of the datum measures (DatumEnd – DatumBeg) in the LRMToDatumXRef records linked to a datum record, cannot exceed the length of the datum.

Sum of measures with specified Datum ID in LDXRef table exceed the datum length.

206


18-5

Anomaly rule Reported Anomaly

description Reported

Anomaly ID

The LRM measure values in an LRMToDatumXRef record must always increase from begin to end.

LDXRef record LRM measures must always increase from begin to end.

207

All measure values must contain a valid value. NULL values for ID and measures are not allowed.

NULL is not a valid measure value.

208

Zero lengths are not allowed. Length should be greater than zero.

209

All LRM records associated with the same Datum ID have the same Region ID value.

Region ID associated with the LRM segment does not correspond with that of the corresponding Datum segment

210

All LDXRef records associated with the same Datum ID should have the same Region ID value.

Region ID associated with the LDXRef segment does not correspond with that of the corresponding Datum segment

211


18-6

Schema The following is the schema for the LRS Anomalies table:

Field name Data type Field description

LRSANOMALYID gdbLong

(Autonumber)

Primary key field

ANOMALYSESSIONID gdbText The current Oracle user name, along with session name and date and time stamp, is reported as Session ID. The date and time stamp reports when the validation process was started. This value allows users to differentiate rows from one execution to another.

FEATURECLASSSNAME gdbText Name of the feature class in which anomaly was found.

UNIQUEIDVALUE gdbLong Primary key value of the anomaly record in the table reported in FeatureClassName field.

ANOMALYDESCRIPTION gdbText Description of the anomaly.

ANOMALYID gdbLong Anomaly ID value associated with the Anomaly description.

GMQESTATUS gdbLong Field to list status values when interacting with Queued edit sub-system.

GMQEDATE gdbText Field to store the edit data value when interacting with Queued edit sub-system.

GMQEREASON gdbText Field to store the edit reason value when interacting with Queued edit sub-system.


The Multilevel LRS Validation Command Workflow This section presents the procedural steps for using the Multilevel LRS Validation command. 1. Make sure that the LRSANOMALIES table is created by executing the delivered SQL

script in the oracle read-write connection before invoking the Multilevel LRS Validation command.

2. With an open GeoWorkspace, one or more open read-write connections (the command

only lists Oracle connections), and an active map or data window, invoke the Multilevel LRS Validation command.

3. Select the Oracle read-write connection from the Connection drop-down list. 4. Select the MLRS definition to be validated from the LRS Name drop-down list.

5. Optionally select the Filter by <Region ID Metadata name> check box, and choose

Region IDs of interest.

6. Select LRMs and Geometries, and click OK.

7. In the Anomaly session name field, key in a name for the current MLRS validation session.

8. In the Output LRS anomalies to drop-down list, select an LRS Anomalies table for

reporting MLRS validation results.

18-7


18-8

9. Open the LRSANOMALIES feature class in a data window, and note that new records corresponding to anomalies present are inserted into the table.

10. After running the command, clean up any LRM/Geometry problems found. 11. Re-run the Multilevel LRS Validation command, and fix problems (if necessary) until

all problems have been resolved.

12. For each LRM/Geometry combination, run the Display LRM command.

Note: This process is used to validate across the datum, and it will show LRM events that cannot be linked to geometry.

13. Display the Display LRM query results in a data window. 14. Check the status field for error conditions. 15. Run the Multilevel LRS Validation command using the output recordset from the

Display LRM command as input. 16. Clean up the anomalies found by the Multilevel LRS Validation command.

19-1

Working with the Display LRM Command

The Display LRM command provides a GUI to define and view an LRM query for a single-level or multilevel LRS (MLRS). For an MLRS, this command allows you to select an LRM table and a Geometry table and to display the output in a map/data window as a normal LRM query. For a single level LRS (SLRS), the LRM table is displayed in a map/data window as a normal LRM query. This command adds LRS Metadata extensions to each query generated. These metadata extensions are read and used by LRS Input control and other interactive editing commands, such as Insert, Split, Delete, Merge, and Redigitize that operate on an LRM segment.

In case of an MLRS, the command produces a query by extracting the geometry from the chosen geometry table. This query is added to the Queries subfolder of the document’s Query folder.

If the selected multilevel LRS has Region ID information associated with it, the LRM, Geometry, LRMDatumXRef, and GeometryDatumXRef tables are first queried to filter records based on Region ID values selected, and then the output query is generated.

You can also filter the LRM table by clicking the Filter command button and specifying a filter expression.

In the case of an SLRS, there is no dynamic segmentation involved, as the selected LRM table will already have geometry associated with it. The recordset is simply appended to the Queries subfolder of the document’s Query folder.

The Display LRM Dialog Box The Connection combo box will always be enabled. On invocation of the Display LRM dialog box, the combo box is populated with all open connection names in the current GeoWorkspace. By default, the first name in the list is selected.

When you select a name from the list of Connection names, the LRS name combo box is populated with all the defined LRSs in the selected connection. The LRS name combo box will be enabled only when a connection is selected. By default, nothing is selected unless there is only one LRS. In that case, the LRS name is selected by default.

When you select a multilevel LRS name from the list of LRS names, both the LRM name combo box and the Geometry name combo box are enabled. The combo boxes are populated with the respective LRM and Geometry names defined in the selected LRS. If a single-level LRS is selected, the LRM name combo box will have the LRM name selected by default, and the LRM name and Geometry name controls are disabled.


19-2

The LRM name combo box will be enabled only when a multilevel LRS name is selected. By default, nothing is selected unless there is only one LRM. In that case, the LRM name is selected by default.

The Filter command button is enabled when an LRM name is selected. On a click of the Filter button, the Filter dialog box is displayed with the fields of the LRM feature class. A filter expression can be specified by using the GUI options to build the filter or by key-in. On an OK click of the filter dialog, if the query storage control is enabled, the filter expression is added to query description.

The Attributes command button is enabled when an LRM name is selected. On a click of the Attributes button, the Schema Projection dialog box is displayed with the fields of the LRM feature class that corresponds to the selected LRM name. Any field can be selected/unselected or renamed except for those marked by an asterisk (*). In the case of an MLRS, the required fields are LRMID, LRMBeginMeasure, and LRMEndMeasure. In case of an SLRS, the required fields are LRMID, LRMBeginMeasure, LRMEndMeasure, and the primary geometry field. Also, if the LRS type of the LRM is internal markers, then the LRMBeginMarker and LRMEndMarker fields are also required.

The Geometry name combo box will be enabled only when a multilevel LRS name is selected as the LRS. By default, nothing is selected unless there is only one geometry. In that case, the geometry name is selected by default.

When an LRS that is an MLRS that has Region ID settings is selected in the LRS name combo box, the frame of the Region ID control containing the Filter by <Region ID Metadata Name> check box is enabled. By default, the check box is unchecked. If you check this check box, the list box and the Select All and Unselect All command buttons are enabled, and the Region ID and Region ID description values (from the Region ID feature class associated with the MLRS definition) are populated in the Region ID control’s list box. By default, all items in the list are unselected. You can click Select All and Unselect All to toggle selections, but you have to select a minimum of one Region ID value for a valid Region ID query.

For a multilevel LRS, the Output results as query control will be enabled when LRS name, LRM name, and Geometry name are selected. In the case of a single level LRS, the control is enabled on selection of LRS name after the automatic selection of LRM name. The default value for query name is LRM query for <LRM name>. In case of a multilevel LRS, the query description will be LRM query for <LRM name>(<LRM Feature class name>) on <Geometry name>(<Geometry Feature class name>). In case of a single level LRS, the query description will be LRM query for <LRM name>(<LRM Feature class name>). If an attribute filter is applied, the query would look like LRM query for <LRM name>(<LRM Feature class name> filtered on <filter>) on <Geometry name>(<Geometry Feature class name>) for an MLRS case and LRM query for <LRM name>(<LRM Feature class name> filtered on <filter>) for a SLRS case.

You have the option to modify the values in Name and Description text boxes.


19-3

For a multilevel LRS, the Display results in map window control will be enabled when LRS name, LRM name, and Geometry name are selected. In the case of a single level LRS, the control is enabled on selection of LRS name after the automatic selection of LRM name. By default, this check box is checked.

If you intend to change the map window name, you can key-in a new name or select a name from the Map window name combo box. To change the display style, click the Style button. Note that the enabling of the map window combo box and the Style button is controlled by the on/off status of the map window check box.

For a multilevel LRS, the Display results in data window control will be enabled when LRS name, LRM name, and Geometry name are selected. In the case of a single level LRS, the control is enabled on selection of LRS name after the automatic selection of LRM name. By default, the data window check box is unchecked.

If you intend to change the data window name, you can key-in a new name or select a name from the Display results in data window combo box. Note that the enabling of the data window combo box is controlled by the on/off status of the data window check box.

This OK button will be enabled when Connection, LRS definition, LRM name, and Geometry name (if applicable) are selected.

When you click OK with all combo box settings in place, the display LRM query is generated.

When you click Cancel, which will always be enabled, the command exits without any processing.

The Display LRM Command Workflow This section presents the procedural steps for using the Display LRM command.

1. Open a GeoWorkspace that contains one or more readable connections.

2. Invoke the Display LRM Command.


3. On the Display LRM dialog box, select a connection from the drop-down list in the Connection box, or use the connection selected by default.

4. In the LRS definition box, first select the LRS from the LRS name drop-down list. If the selected LRS is a single level LRM, the name will be selected automatically.

5. For a multilevel LRS, select a name from the LRM name drop-down list.

6. The Filter button is enabled on selecting an LRM name. Optionally click the button to define an attribute filter string to be applied to the LRM recordset.

7. The Attributes button is enabled on selecting an LRM name. Optionally click the button to select/unselect or rename output LRM attributes.

8. For a multilevel LRS, select a name from the Geometry name drop-down list.

9. If the selected LRS has Region ID settings, the Region ID control is enabled. Click the Filter by <Region ID Metadata Name> check box to populate the list with all the Region ID values defined for the LRS. You can use the Select All and Unselect All command buttons to toggle selections, but you have to select a minimum of one item to continue with the command processing.

10. The default query name and description are shown in the Output results as query frame. Accept the default, or key in a new query name and description.

19-4


11. To display the LRM query in a map window, toggle the Display results in map window check box to ON. Then accept the default, or select or key in a map window name.

12. To display the LRM query in a data window, toggle the Display results in data window check box to ON. Then accept the default, or select or key in a data window name.

13. Click OK to generate and display the LRM query in the specified map/data window. 14. To change the region(s) that the Display LRM query is displaying, use Analysis >

Queries > Select Display LRM Query > Properties, and select the region(s) of choice. Then click OK.

19-5


19-6

20-1

Working with the LRS Event Overlay Command

This section provides an overview of the LRS Event Overlay command. Event overlay is the process of overlaying two event sets, which could be tables or subsets of tables or queries, in order to find the intersection, union, or difference of the event records. The LRS Event Overlay command provides the capability to overlay two event feature classes.

This command is very useful for performing cross-discipline analysis to locate areas that may require attention. For example, you can locate areas where there is both heavy traffic and few lanes to identify possible congestions areas, or you could identify areas with run-off-the-road accidents and no guardrails.

There are three basic linear overlay operators supported: Intersection, Union, and Difference. There are also two versions of each of these three operators: normal and Without Overlaps. Lastly, this command works on both point and linear events in any combination (a total of four combinations). The three operators, with two versions each, working on four different event type combinations brings the total number of different behaviors you can get out of this one command to 24. Each one of these behaviors is explained in the next section.

Note: Versions 5.1a (05.01.01.06) and earlier did not have normal and Without Overlaps options. The Intersection, Difference, and Union options in those versions functioned in the same way as the Intersection Without Overlaps, Difference Without Overlaps, and the Union Without Overlaps options function in the current version.

You should perform the validation and correction of anomalies in the linear feature class before using the Event Overlay command. This ensures that the proper analysis results are returned

Behavior and Results The following is a description of the behavior and results from each of the LRS Event Overlay operators.

Event Intersection The Event Intersection overlay operators are designed to take two input event features and generate an output query that represents the intersection overlay of them. The output query will contain all the fields from the first input event feature and all the fields from the


second input event feature. New fields will be added that contain the measure fields of the output query.

The input events can be linear or point. If both the input events are linear, the result is linear; if both input events are points, the result is point. But, if one input event is linear and the other is point, the output event type is determined by the event type of the first event feature. If the first is linear, the output is linear; if the first is point, the output is point.

Event Intersection overlay operation when both events are linear is as follows:

A

BBAA

B#1

40.030.020.010.00.0

A/AA

B/AAA/BB

#2

Result

Event Intersection overlay operation (without overlaps) when both events are linear is as follows:

A

BBAA

B

B/AA

#1

40.030.020.010.00.0

A/BBA/BB

#2

Result

20-2


Event Intersection overlay operation when the first event is linear and the second is point is as follows:

A

AA

B#1

40.030.020.010.00.0

C

BB CC

EE

DD

#2

Result

D

B/AA

C/CC

A/BB

B/BBB/EE

Event Intersection overlay operation (without overlaps) when the first event is linear and the second is point is as follows:

A

AA

B#1

40.030.020.010.00.0

C

BB CC

EE

DD

#2

Result

D

B/EEA/BB

C/CC

20-3


Event Intersection overlay operation when the first event is point and the second is linear is as follows:

A

AA

B

#1

40.030.020.010.00.0

C

BB CC

EE

DD

AA/B BB/A CC/A

EE/B BB/B CC/C

#2

Result

Event Intersection overlay operation (without overlaps) when the first event is point and the second is linear is as follows:

A

AA

B

#1

40.030.020.010.00.0

C

BB CC

EE

DD

EE/B BB/B CC/A

#2

Result

Event Intersection overlay operation when both events are points is as follows:

AA

#1

40.030.020.010.00.0

BB CC

A B DC

D/CCC/BB

E

C/FF

#2

Result

EE FF

20-4


Event Intersection overlay operation (without overlaps) when both events are points is as follows:

AA

#1

40.030.020.010.00.0

BB CC

A B DC

D/CCC/BB

E

#2

Result

EE FF

Event Union The Event Union overlay operators are designed to take two input event features and generate an output query that represents the union overlay of the two. The output query will contain all the fields from the first input event feature and all the fields from the second input event feature. New fields will be added that contain the measure fields of the output query.

The input events can be linear or point. If both the input events are linear, the result is linear; if both input events are points, the result is point. But, if one input event is linear and the other is point, the output event type is determined by the event type of the first event feature. If the first is linear, the output is linear; if the first is point, the output is point.

Event Union overlay operation when both events are linear is as follows:

A

BBAA

B#1

40.030.020.010.00.0

A

A/AA

B/AAA/BB

BBB

#2

Result

20-5


Event Union overlay operation (without overlaps) when both events are linear is as follows:

A

BBAA

B#1

40.030.020.010.00.0

BB

B/AAA/BB

A/BBBB

#2

Result

Event Union overlay operation when the first event is linear and the second is point is as follows:

A

AA

B#1

40.030.020.010.00.0

C

BB CC

EE

DD

#2

Result

D

B/AA

C/CC

A/BB

B/BBB/EE

D

20-6


Event Union overlay operation (without overlaps) when the first event is linear and the second is point is as follows:

A

AA

B#1

40.030.020.010.00.0

C

BB CC

EE

DD

#2

Result

D

B/EEA

AD

C/CC

Event Union overlay operation when the first event is point and the second is linear is as follows:

A

AA

B

#1

40.030.020.010.00.0

C

BB CC

EE

DD

AA/B BB/A CC/A

EE/B BB/B CC/C

DD

#2

Result

Event Union overlay operation (without overlaps) when the first event is point and the second is linear is as follows:

A

AA

B

#1

40.030.020.010.00.0

C

BB CC

EE

DD

EE/B BB/B CC/A DD

#2

Result

20-7


Event Union overlay operation when both events are points is as follows:

AA

#1

40.030.020.010.00.0

BB CC

A B DC

AAA B D/CCC/BB

E

EE E C/FF

EE FF#2

Result

Event Union overlay operation (without overlaps) when both events are points is as follows:

AA

#1

40.030.020.010.00.0

BB CC

A B DC

AAA E D/CCC/BB

E

#2

Result

EE FF

Event Difference The Event Difference overlay operators take two input event features and generate an output query, which represents the difference of the overlay. The output is a query that contains all the fields from the first input event feature and the computed output Start Measure and the output End Measure fields. The values in the measure fields are the results of the difference overlay

The input event features can be linear or point. If both input features are linear, the result is linear; if both are points, the result is point. But, if one is linear and the other is point, the output event type is determined by the event type of the first input feature class. If the first is linear, the output is linear; if the first is point, the output is point.

20-8


Event Difference overlay operation when both events are linear is as follows:

A

BBAA

B#1

40.030.020.010.00.0

BA

#2

Result

Event Difference overlay operation (without overlaps) when both events are linear is as follows:

A

BBAA

B#1

40.030.020.010.00.0

BB

#2

Result

Event Difference overlay operation when the first event is linear and the second is point is as follows:

A

AA

B#1

40.030.020.010.00.0

C

BB CC

EE

DD

#2

Result

D

D

20-9


Event Difference overlay operation (without overlaps) when the first event is linear and the second is point is as follows:

A

AA

B#1

40.030.020.010.00.0

C

BB CC

EE

DD

#2

Result

D

AD

Event Difference overlay operation when the first event is point and the second is linear is as follows:

A

AA

B#2

40.030.020.010.00.0

C

BB CC

EE

DD

DD

#1

Result

Event Difference overlay operation (without overlaps) when the first event is point and the second is linear is as follows:

A

AA

B

#1

40.030.020.010.00.0

C

BB CC

EE

DD

DD

#2

Result

20-10


Event Difference overlay operation when both events are points is as follows:

AA

#1

40.030.020.010.00.0

BB CC

A B DC

A B

EE FF

E

E

#2

Result

Event Difference overlay operation (without overlaps) when both events are points is as follows:

AA

#1

40.030.020.010.00.0

BB CC

A B DC

A E

E

#2

Result

EE FF

The LRS Event Overlay Command Workflow

This section presents the procedural steps for using Event Overlay.

1. Open a GeoWorkspace; then connect to the warehouse containing the LRS feature class. If the event feature classes are in a different warehouse, connect to that warehouse also. It is possible that each of the event feature classes could be from different warehouses; if so, you need to make the appropriate connections.

2. Select Transportation > LRS Analysis > LRS Event Overlay.

The LRS Event Overlay dialog box is displayed.

20-11


3. Click the LRS Features drop-down list; then select the appropriate linear network feature to be used for Event Overlay analysis. If the selected LRS feature is a Display LRM Query, the LRS Model and the Properties are restored based on the special extensions available from the query and are made read-only.

4. Click the LRS Model drop-down list; then select the correct LRS model. For more on the different LRS Models supported, see the “GeoMedia Transportation LRS Data Structures” appendix.

5. Click the LRS Feature Class – Properties button.


20-12


20-13

Note: See the “Working with the LRS and Marker Properties Dialog Boxes” chapter for information on using this dialog box. If this is the first time this Properties dialog box is used, there will be no entries in any of the LRS Key Fields or LRS Definition Fields.


You are returned to the LRS Event Overlay dialog box.

7. If the LRS Model selected was LRS Measure with External Measure Markers or LRS Duration with External Measure Markers, select the Marker Features from the drop-down list.

Note: The Marker Features drop-down list and the Properties button will not be enabled unless the LRS model is one of the two listed in Step 8. If a Display LRM query defined with External Markers is selected as LRS Features, the Marker Features and the corresponding properties are defaulted and made read-only.

8. Click Properties in the Marker Features box.

The Marker Properties dialog box is displayed.

Note: See the “Working with the LRS and Marker Properties Dialog Boxes” chapter for information on using this dialog box.


You are returned to the LRS Event overlay dialog box.

10. Click the First event feature drop-down list; then select the event features to be used for event intersection analysis.

Note: The Datum based event feature option is available only when multilevel LRS based Display LRM query is selected as LRS Features.

11. Click the First event feature – Properties button.

The Event Properties dialog box is displayed.


Note: Based on the selected option, a properties dialog box is displayed for specifying LRM or Datum settings. See the “Working with the Event Properties Dialog Box” chapter for information on using this dialog box.



13. Click the First event feature class – Attributes button, and select the attributes to be included in the output recordset.

14. Click the Event Overlay Operator drop-down list; then select the appropriate overlay operator.

15. Click the Second event feature class drop-down list; then select the connection and the event table/query to be used for event intersection analysis.

16. Click the Second event feature– Properties button.

17. On the Event Properties dialog box, select the appropriate columns and click OK.


18. Click the Second event feature class – Attributes button, and select the attributes to be included in the output recordset.

19. If you want 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 on and that the appropriate Map window name is selected.

20. Optional: Click Style to define the display settings for the results in the map window.

21. If you want 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 on and that the appropriate Data window name is selected.

22. When you have made the appropriate settings, click OK.

23. When the results are returned, tile the windows.

20-14


The GeoWorkspace should resemble the following:

20-15


20-16

Working with the Resolve LRS Event Overlaps Command

The Resolve LRS Event Overlaps command provides the ability to resolve the overlaps that may exist within a Linear Event feature class. This ensures that there are no two linear events that cover the same portion of the network. This command gives you control over what criteria are used to define which of the overlapping events are chosen for output. What this command does is illustrated in the example below.

A

C

Inpu

t

50.030.020.010.00.0

Out

put

(MIN

exa

mpl

e)

40.0

B

AB

AB

C

LRSkey(s) BegMeas EndMeas ValueLRSkey 20 35 ALRSkey 5 25 BLRSkey 15 45 C

LRSkey(s) NewBegMeas NewEndMeas Min(Value)LRSkey 5 15 BLRSkey 15 20 BLRSkey 20 25 ALRSkey 25 35 ALRSkey 35 45 C

In the Input portion of this illustration you will see three different linear event records that overlap each other. For this example we used the MIN function (minimum) function to select those linear events that have the lowest Value attribute. The command makes use of the Functional Attributes capability of GeoMedia, which provides great flexibility to define what criteria are used in choosing which linear events are output.

This command is for linear events only. Identical functionality is available for point events using the Analytical Merge command. The result of this command is tabular data. To see the results in the map view you can use the Dynamic Segmentation command to add geometry to each recordset.

21-1


The Resolve LRS Event Overlaps Command Workflow

This section presents the procedural steps for using Resolve LRS Event Overlaps.


2. Select Transportation > LRS Analysis > Resolve LRS Event Overlaps.

The Resolve LRS Event Overlaps dialog box is displayed.

3. Select the LRS Features, LRS Model, the Marker Features, and the Event features from the drop-down lists; then select the Properties button for each. Note this command is for linear events only. If the selected LRS feature is a Display LRM Query, the LRS Model, LRS Properties, and the External Marker features and their Properties are restored based on the special extensions available from the query. They are also made read-only.

21-2


Note: See the “Working with the LRS and Marker Properties Dialog Boxes” chapter for information on the workflow for the LRS feature class and the LRS marker feature class; and see the “Working with the Event Properties Dialog Box” chapter for information on the workflow for the Event feature class.

4. Type in a query name and an optional description in the Output results as query fields.

5. In the Output functional attributes box, click New to specify any functional attributes, or click Properties to edit an exiting functional attribute. This will define how the overlaps in your linear feature class are resolved. In the example shown we are finding the most recent records by finding the maximum date. If there are two or more pavement condition readings for the same portion of the network, this will return only the most current record.

If you select New or Properties, the Functional Attribute dialog box will appear.

6. Click OK on the Functional Attribute dialog box to save your input or Cancel if you do not wish to save your work.

The Functional Attribute dialog box will be dismissed, and control will return to the Resolve LRS Event Overlaps dialog box.

21-3


7. In the Output functional attributes box, click New again to specify another functional attribute. This second functional attribute will bring along additional attributes that belong to the records selected via the functional attribute defined in Step 5. In the example shown, we are finding the most pavement condition readings that are on the most recent records.

If you select New or Properties, the Functional Attribute dialog box will appear.

Note: The LOOKUP functional attribute is very valuable to users of this command. In the example shown here the first parameter of the LOOKUP function is the same function as defined in Step 5, the second parameter is the field name that is narrowed by that functional attribute, and the third parameter is the field name we want to return.

8. Click OK on the Functional Attribute dialog box to save your input or Cancel if you do not wish to save your work.

The Functional Attribute dialog box will be dismissed, and control will return to the Resolve LRS Event Overlaps dialog box.

9. Repeat Steps 7 and 8 for each other attribute you wish to bring along from the records selected via the functional attribute defined in Step 5.

21-4


10. Optional: Select Display results in data window; then accept the default or select or type in a data window name.

11. Click OK to generate and display the results; or click Cancel to dismiss the dialog box.

The Data Window below shows the output of this command.

21-5


21-6

22-1

Working with the LRS Event Conversion Command

This section provides an overview of the LRS Event Conversion command, which provides the ability to convert events from one LRS Event Reference Type to another. For example, you can convert Coordinate events to Measure events, or vice versa. LRS Event Conversion allows the choice of the input recordset for the Linear Referencing System (LRS), the event, the marker features, and the properties of these recordsets; and it will convert the Event data format from the source to the Event data format specified by the Output Properties.

Multilevel LRS features are supported in addition to single-level LRS. To use multilevel LRS, a Display LRM query should be used as LRS feature. In this case, the LRS Model and LRS properties are set using LRS metadata extensions on the Display LRM query, and they are read-only. Datum based events are also supported. To define Datum based events, the LRS feature selected should be a multilevel Display LRM query.

The LRS Event Conversion Command Workflow

This section presents the procedural steps for using LRS Event Conversion.

1. Open a GeoWorkspace; then connect to the warehouse containing the LRS feature class. If the event feature classes are in a different warehouse, connect to that warehouse also. It is possible that each of the event feature classes could be from different warehouses; if so, you need to make the appropriate connections.

2. Select Transportation > LRS Analysis > LRS Event Conversion.

The Event Conversion dialog box is displayed.


3. Click the LRS Features drop-down list; then select the appropriate feature class to be used for LRS Event Conversion analysis. If the selected LRS feature is a Display LRM Query, the LRS Model and the Properties are restored based on the special extensions available from the query and are made read-only.

4. Click the LRS Model drop-down list; then select the correct LRS model. For more on the different LRS Models supported, see the “GeoMedia Transportation LRS Data Structures” appendix.

5. Click the LRS Features – Properties button.


Note: See the “Working with the LRS and Marker Properties Dialog Boxes” chapter for information on using this dialog box as well as the Marker Properties dialog box. If this is the first time this dialog box is used, there will be no entries in any of the LRS Key Fields or LRS Definition Fields.


You are returned to the Event Conversion dialog box.

22-2


22-3

7. If the LRS model is LRS Measure with External Measure Markers or LRS Duration with External Measure Markers, select the input marker feature class from the drop-down list in the Marker Feature Class box.

Note: The Marker Features drop-down list and the Properties button will not be enabled unless the LRS model is one of the two listed in Step 7. If a Display LRM query defined with External Markers is selected as LRS Features, the Marker Features and the corresponding properties are defaulted and made read-only.

8. Click Properties in the Marker Features box.


Note: See the “Working with the LRS and Marker Properties Dialog Boxes” chapter for information on using this dialog box.


You are returned to the LRS Event Conversion dialog box.

10. On the LRS Event Conversion dialog box, select the input event feature class from the drop-down list in the Event Feature box.

Note: The Datum based event feature option is available only when a multilevel LRS-based Display LRM query is selected as LRS Features.

11. Click the Event Feature – Properties button.


Note: Based on the selected option, a properties dialog box is displayed for specifying LRM or Datum settings. See the “Working with the Event Properties Dialog Box” chapter for information on using this dialog box.

12. If applicable, define the event coordinate system by clicking Browse or by clicking Define/Modify Coordinate System for LRM based events.

Note: See the “Working with the Coordinate System Dialog Box” chapter for information on the dialog boxes that appear.



You are returned to the LRS Event Conversion dialog box.

14. Click the Event Feature – Attributes button to select attributes from the input event feature that you want to have available in the output query.

The Event Attributes dialog box is displayed.

15. Select those attributes that you want reflected in the output recordset. Select All and Clear All buttons are provided to speed this process.


You are returned to the Event Conversion dialog box.

17. Select the output Event Reference Type from the choices in the Output Properties group box.

18. If the Coordinate type output property is selected, the coordinate system for the output must be defined by selecting a coordinate system file, by clicking Browse, or by clicking Define/Modify Coordinate System.

19. Accept the default, or choose another Query name field.

20. Optional: Assign a description in the Description field.

21. Check the Display Result in data window check box.

22. Accept the default, or type in a data window name.

22-4


22-5

23. Click OK to generate and display the Event Conversion results in the specified data window.


22-6

23-1

Working with the Convert Intersection Referenced Events Command

The Convert Intersection Referenced Events command allows you to convert intersection referenced events to the Marker Offset event reference type so that they can be used with other LRS commands in GeoMedia Transportation. With this command you can also resolve ambiguity for marker offset events referencing duplicate intersections. You can visually resolve the ambiguity of which intersection marker an event is actually associated with. You can assign one intersection marker for every point event, or you can assign two intersection markers for every linear event.

The command takes the following as input: LRS features, Intersection Marker features, and Intersection Referenced events. The output of the command is a new feature class. This new feature class will contain only non-ambiguous events, each of which is referenced to only one particular intersection marker.

If the Process ambiguous events check box is checked, and if there are any ambiguous events, the LRS and Intersection Markers are displayed in the map window. The LRS and Marker features are added to legend of the active map window if not already present.

The Convert Intersection Referenced Events Command Workflow

1. Open a GeoWorkspace; then connect to the warehouse containing the LRS feature class. If the event feature class is in a different warehouse, connect to that warehouse also. It is possible that each of the LRS and event feature classes could be from different warehouses. If so, make the appropriate connections.

2. Select the Transportation > LRS Analysis > Convert Intersection Referenced Events command.

The Convert Intersection Referenced Events dialog box is displayed.


3. Click the LRS features drop-down list; then select the appropriate feature class to be

used for Intersection Referenced Event Conversion. If the selected LRS feature is a Display LRM Query, the LRS Model and the Properties are restored based on the special extensions available from the query, and they are made read-only.

4. Click the LRS model drop-down list; then select the correct LRS model. For more information on the different LRS Models supported, see the “GeoMedia Transportation LRS Data Structures” appendix. This command supports only LRS Measure and LRS Duration models.

5. Click the LRS features – Properties button. The LRS Properties dialog box is displayed.

Note: See the “Working with the LRS and Marker Properties Dialog Boxes” chapter for information on using this dialog box. If this is the first time this dialog box is used, there will be no entries in any of the LRS Key Fields or LRS Definition Fields.


You are returned to the Convert Intersection Referenced Event dialog box.

7. Click the Intersection marker features drop-down list; then select the appropriate feature class to be used for Intersection Referenced Event Conversion. The Intersection Marker feature class can be created for the selected LRS (in Step 3) using the Create Intersection Events command.

23-2


Note: See the “Working with the Create Intersection Markers Command” chapter for information on creating an Intersection Marker feature class.

8. Click the Intersection marker features – Properties button. The Marker Properties dialog box is displayed.

The following steps describe the workflow to set the Intersection Marker properties.

a. In the Marker key fields boxes, select the Primary, Secondary, Tertiary, and Quaternary keys of the Marker feature class for as many keys as you want to use.

b. In the Marker fields boxes, select the Name and Measure fields of the Marker feature class.

c. In the Cross street field box, select the Cross Street field of the Marker feature class.

d. In the Intersection marker fields boxes select the Azimuth Plus, Azimuth Minus, Duplicate Intersection, and Occurrence fields of the Marker feature class.

e. In the Marker unit box, select the marker measure unit for the Marker feature class (the default is the unit set for the Distance on the Units and Formats tab of the GeoWorkspace Coordinate System dialog box).

f. Click OK after setting the appropriate values.

You are returned to the Convert Intersection Referenced Event dialog box. 23-3


23-4

.

10.

9 Click the Event features drop-down list; then select the appropriate intersection referenced event feature class to be converted to the Marker offset type.

Click the Event features – Properties button.


The following steps describe the workflow to set the Event properties.

the Primary, Secondary, Tertiary,

c. Direction lookup table box, select the Direction lookup feature class that

a. Select the Event type (point is the default).

b. In the Occurred on key fields boxes, select and Quaternary keys of the Event feature class for as many keys as you want to use.

In theyou want to use. This feature class contains azimuth and code value pairs. The following shows an example of a Direction Lookup table.


23-5

d. Click the Direction lookup table - Properties button.

The Direction Lookup Properties dialog box appears.

e. In the Direction lookup fields box, select the code and azimuth fields from the Direction lookup feature class.

f. Click OK after setting the appropriate values.

You are returned to the Event Properties dialog box.

or End Primary, feature class for as many

h. the unit for the Event feature class (the default is tab of the

x.

ator to be applied while or used

j. es, select the Begin and/or End distance from

k.

11. In t x to indicate that

12. In t and description of the feature class iption text boxes, respectively.

13.

yed on the Process Ambiguous Events dialog box. The LRS and

g. In the Cross street key fields boxes, select Begin and /Secondary, Tertiary, and Quaternary keys of the Eventkeys as you want to use.

In the Measure unit box, selectthe unit you set for the Distance on the Units and FormatsGeoWorkspace Coordinate System dialog bo

i. In the Cross street key separator box, select the separconcatenating the cross street key fields. This would ideally be the separatin the cross street key of the intersection Marker feature class.

In the Measure fields boxintersection and the Begin and/or End direction from intersection fields of the Event feature class.

Click OK after setting the appropriate values.

You are returned to the Convert Intersection Referenced Events dialog box. he Options box, select the Process ambiguous events check bo

all ambiguous events are required to be resolved visually. Unselect the check box to skip the same.

he Output marker offset events to box, select the Connection in which the output feature class is to be created, and provide the nameto be created in the Feature class name and Descr

Upon clicking OK on the dialog box, all unambiguous events are converted and areoutput to the feature class specified. If there are any ambiguous events and if the Process ambiguous events check box is checked (the default setting), the ambiguousevents are displaIntersection marker feature classes are added to the map window if not already present to aid in visually resolving the ambiguous events.


14. On the Process Ambiguous Events dialog box, click the First, Previous, Next, and

Last buttons to traverse through all the ambiguous events. For each event, all the e

the

15. e just the viewing scale after selecting a zoom

16.

intersections referenced by it are displayed in the map window with the GeoWorkspachighlight color, and they are displayed in the Begin/End Marker list boxes. Uponclick of an occurrence value, the intersection marker corresponding to it is selected in the map window using the GeoWorkspace select color. If Fit all is selected (which is the default), all the intersection markers corresponding to the event are fit into the mapwindow and are highlighted except for the selected marker (other than None), which isin select color. If Fit selected is selected, the selected intersection marker (other than None) is centered and selected in the map window in the select color. You can assign an intersection to each of the ambiguous event records by clicking on an occurrence value in the Select intersection box.

In the View options box, to facilitate resolving the ambiguity visually, you can use thZoom Out and Zoom In buttons to adfactor appropriately.

Click OK to output all resolved events to the specified feature class.

23-6

Working with the LRS Event Generation Command

The LRS Event Generation command provides the ability to create either point or linear events for an existing LRS feature class. A variety of methods are available to control where the new events are located along the LRS. The output events from the command can be used in numerous workflows, including labeling and aggregation analysis. For more detail on some of these workflows, see the “LRS Annotation Workflows” and “LRS Analysis Workflows” chapters.

The command takes an input LRS recordset and generates point or linear events. Point events can be generated at various points along the LRS network, depending on the options selected. The placement options include placing the points at the begin, middle, and/or end of each LRS feature instance; at the begin, middle, and/or end of each LRS Keyset group (features that share the same LRS keys); or at a user-defined interval along the LRS Keyset group.

Begin

Middle

EndBegin

Middle

End

Middle

0

5

20

15

10

Point events at begin, middle, end of each

feature

Point events at begin, middle, end of each

route

Point events evenly spaced

along each route

Begin

End Linear events can be generated at various points along the LRS network, depending on the options selected. The placement options include linear events generated for each LRS Keyset group, or equal-length segments which are generated at a user-defined length along the LRS Keyset group.

24-1


Linear event for each route

Linear events of equal length

along each route

The command uses the LRSEventGenerationPipe to perform the functionality. The result of this pipe is tabular data. To see the results in the map view, you can use the Dynamic Segmentation command to add geometry to each recordset.

The LRS Event Generation Command Workflow This section presents the procedural steps for using the LRS Event Generation command.

1. Open a GeoWorkspace with readable connections.

2. Select Transportation > LRS Analysis > LRS Event Generation.

The LRS Event Generation dialog box is displayed.

24-2


3. On the LRS Features drop-down list, select the appropriate LRS feature to be used for generating new Events. If the selected LRS feature is a Display LRM Query, the LRS Model and the Properties are restored based on the special extensions available from the query and are made read-only.

4. On the LRS Model drop-down list, select the correct LRS model. For more on the different LRS Models supported, see the “GeoMedia Transportation LRS Data Structures” appendix.

5. Click the LRS Features – Properties button.


Note: See the “Working with the LRS and Marker Properties Dialog Boxes” chapter for information on using this dialog box. If this is the first time the dialog box is used, there will be no entries in any of the LRS Key Fields or LRS Definition Fields. Subsequent uses of the command will have the fields automatically set to what you selected the last time you ran the command.

6. Choose an option from the Event specifications box.

24-3


7. If the Point events at begin, middle, end of each feature or the Point events at begin, middle, end of each route option is selected, Choose one or all of the Begin, Middle, and End check boxes.

8. If the Point events evenly spaced along each route option is selected, type the measure interval between the point events and the unit.

9. If the Linear events of equal length along each route option is selected, key in the duration of equal length linear event and the unit.

10. Accept or override the default query name assigned in the Query name field, and assign an optional description using the Description field.

11. To display the output in a data window, check the Display events in data window check box; then accept the default Data window name, or select or key in a data window name.

12. Click OK to generate and to display the results in the specified data window.

13. After reviewing the result, you can change the event specifications settings by editing the query. Do this by first selecting Analysis > Queries from the GeoMedia Professional menu bar.

The Queries dialog box is displayed.

14. Select the query generated by the LRS Event Generation command, and then click Properties.

24-4


The Query Properties dialog box is displayed.

15. Edit the Query name, the Description, and the Event specifications settings as desired. When finished click OK. This will alter the results of the query according to your new input.

24-5


24-6

Working with the Create Intersections and Midblocks Command

The Create Intersections and Midblocks command allows you to create intersections and midblock features for a set of linear features. An intersection feature, in this case, is defined as a composite geometry feature that extends out a specified distance down each segment of a valid intersection. Midblock features are defined as linear features which form the spatial difference between the original linear features and the intersection features.

The purpose of this command is to create features that lend themselves to aggregation analysis. The features created by this command can be aggregated to using the Touch operator. In the case of intersections, this is more accurate than to create a point intersection and then aggregating using a Within Distance operator, because only data that lies on segments connected to the intersection will be counted. For directions on how to use this command in an aggregation workflow, see “The LRS Analysis Workflows” chapter.

IntersectionMidblock

Buffer Distance

25-1


The features created by this command lend themselves to aggregation in another way as well. The features are attributed with a Description field that makes any output report much more readable.

The command takes the following as input: linear features, a buffer distance, and a choice as to whether or not to merge the overlapping intersection buffers. The command will create intersection features for the entire linear feature class at every valid intersection. A valid intersection is any place where the end points of three or more segments coincide. This allows you great control over where intersection markers are created. For instance, overpasses and underpasses should have unbroken segments if you do not want them to be considered. For assistance on how to break segments at intersections, see the “Intersection Preparation Workflows” chapter.

The output of the command is two new feature classes, one for intersections and the other for midblocks. When you click OK, a new intersections feature class and a new midblocks feature class are created in the connections selected by you for each of them.

Schema of Intersections feature class

Intersections Feature Table Field Description Data type

ID This is an autonumber key field. It uniquely defines each Intersection record.

gdbLong (AutoNumber)

Street Names This is the concatenation of street names that are involved in the intersection separated by a user defined delimiter.

gdbText

Description This is description of the street names involved in the intersection gdbText

Geometry This field contains the intersection geometry gdbSpatial(Linear)

25-2


Schema of Midblocks feature class

Midblocks Feature Table Field Description Data type

ID This is an autonumber key field. It uniquely defines each midblock record. gdbLong (AutoNumber)

Street Name This is the street name the midblock is located on. gdbText

Description This is description of the streets between which the midblock segment lies. gdbText

Begin Street This is the street where the midblock segment begins. gdbText

End Street This is the street where the midblock segment ends. gdbText Geometry This field contains the midblock geometry gdbSpatial (Linear)

The Create Intersections and Midblocks Command Workflow

1. Open a GeoWorkspace; then connect to the warehouse containing the linear feature class. Also connect to a warehouse for the output Intersection and Midblocks feature classes if it is different from the one containing the linear feature class. Make sure that the connection for the output feature class is read-write.

2. Select the Transportation > LRS Analysis > Create Intersections and Midblocks command.

3. Select the input linear features.

25-3


4. Click Properties.

The Input Linear Feature Properties dialog box is displayed.

5. On the Input Linear Feature Properties dialog box, set at least one to a maximum of

four key attributes for the input linear features. If more than one key attribute is selected, the Street Name field in the Midblocks feature class is obtained by concatenating these fields using space as the delimiter. If only one key attribute is selected, the Street name field is populated with the values of the street name attribute chosen.

6. Select a Intersection key group delimiter by choosing one of the given options or by selecting Other and typing the desired delimiter in the adjacent text box. Then click OK. This delimiter is used to concatenate street names and to populate the Street Names field in the Intersections feature class. The default delimiter is a semicolon.

You are returned to the Create Intersections and Midblocks dialog box.

7. On the Create Intersections and Midblocks dialog box, type the Buffer distance. The default value is 1.

8. Select the units for the buffer distance. The default setting is the distance unit specified on the Unit and Formats tab in the GeoWorkspace Coordinate System dialog box.

9. To merge overlapping intersection buffers, check the Merge overlaps check box to select it.

Note: The StreetNames and description fields in the new Intersections feature class will be truncated to 255 characters if the length is longer than 255 characters due to the merge.

25-4


25-5

10. In the Connection drop-down list in the Output intersections box, select the connection to which the new intersections feature class will be output to.

11. Enter a Feature class name for the new intersections feature class.

12. Optionally, enter a description for the new intersections feature class.

13. In the Connection drop-down list in the Output midblocks box, select the connection to which the new midblocks feature class will be output.

14. Enter a Feature class name for the new midblocks feature class.

15. Optionally, enter a description for the new midblocks feature class.

16. Click OK to create the intersections and midblocks feature classes.


25-6

26-1

Working with the Insert LRS Event Command

The Insert LRS Event command allows you to interactively create event data by clicking on the map view to define LRS key, begin measures, and (for linear events) end measures. You will also be able to fill in non-location-related attribution. This is particularly useful in situations where map data exists (such as aerial photography) that can be interpreted to create event data (for example, the number of lanes or bridge locations).

The Insert LRS Event Command Workflow This section presents the procedural steps for using Insert LRS Event.


2. Optional: Display the LRS linear feature class along which you want to create event data. This step makes it easier to select points along the LRS.

3. Optional: If you have any map data that will help you discern where event data is located, display that data. This may come in many forms, such as aerial photography.

4. Optional: Create and display a dynamic segmentation query of the Event feature class you want to add records to. This step is helpful in that it provides visual feedback of the event data you will be creating. This would also aid in creating events without gaps or overlaps easily. For more information on this, see the “Linear Referencing” chapter in Working with GeoMedia or Working with GeoMedia Professional.

5. Select Transportation > LRS Analysis > Insert LRS Event.

The Insert LRS Event dialog box is displayed.


6. Click the LRS features drop-down list; then select the appropriate feature along with

event data is to be created. If the selected LRS feature is a Display LRM Query, the LRS Model and the Properties are restored based on the special extensions available from the query, and are made read-only.

7. Click the LRS model drop-down list; then select the correct LRS model. For more on the different LRS Models supported, see the “GeoMedia Transportation LRS Data Structures” appendix.

8. Click the LRS features drop-down list; then select the appropriate feature class along which event data is to be created.

9. Click the LRS model – Properties button to set the Key field and measure information.


Note: See the “Working with the LRS and Marker Properties Dialog Boxes” chapter for a detailed discussion of this dialog box.


You are returned to the Insert LRS Event dialog box.

26-2

Working with the Insert LRS Event Command

26-3

11. If the LRS model is LRS Measure with External Measure Markers or LRS Duration with External Measure Markers, select the input marker feature class from the drop-down list in the Marker Feature Class box.

Note: The Marker Feature Class drop-down list and the Properties button will not be enabled unless the LRS model is one of the two listed in Step 10. If a Display LRM query defined with External Markers is selected as LRS Features, the Marker Features and the corresponding properties are defaulted and are made read-only.

12. Click Properties in the Marker Feature Class box to set the Key field, marker name, and measure information.


Note: See the “Working with the LRS and Marker Properties Dialog Boxes” chapter for a detailed discussion of this dialog box.



14. On the Insert LRS Event dialog box, select the input event feature class from the drop-down list in the Event feature class box.

15. Click the Event feature class – Properties button.


Note: See the “Working with the Event Properties Dialog Box” chapter for a detailed discussion of this dialog box.



17. Click OK on the Insert LRS Event dialog box to dismiss this dialog box and to start creating event data.

18. Follow the prompts to collect event data locations by clicking in the map window. The first prompt is to “Click on a feature for begin distance, press ESC to exit.” If it is a point event, only one click is necessary. If it is a linear event, you will be prompted to give a second click with this prompt: “Click on the feature for end distance, press Backspace to undo previous click or ESC to exit.” Note that the second click will be ignored unless it is on an LRS linear feature that shares the same LRS Keys as the LRS linear feature identified by the first click. While selecting an event begin or end point,


the user can also snap to an existing linear feature. When there are multiple LRS features located within the tolerance zone of the cursor, you can select the required feature through the PickQuick dialog box. More information on the PickQuick dialog box is available in either the Working with GeoMedia or the Working with GeoMedia Professional documents.

If a dynamic segmentation query of the event feature class with the LRS is displayed, every inserted event appears in the map window. To place a contiguous event, you can snap to the end point of the previous event feature and thus avoid gaps or overlaps.

The Event Properties dialog box is displayed with the key and measure field values that reflect the position you clicked on the LRS on the map window.

19. Fill in other event data attributes, and click OK to dismiss the Select Set Properties

dialog box.

20. Repeat the two previous steps as often as desired to collect event data. To exit, press ESC.

26-4

27-1

Working with the LRS Keys for Coordinate Events Command

The LRS Keys For Coordinate Events command provides a way to linearly reference data whose only geographic reference is coordinates or latitude and longitude. The command searches in the vicinity of these coordinate locations and locates the nearest LRS linear feature within a given tolerance. The output of the command is the input data plus the LRS keys of the located LRS linear feature for each record. Since the other commands in the product can handle events data located by LRS keys and coordinates, this data is now ready to use with commands such as Dynamic Segmentation or Event Overlay. Coordinate events that are not within the given tolerance of any LRS feature are not given key values.

This command is particularly useful for event data collected with GPS because this data often does not identify the LRS keys of the road that the data is associated with. It is also useful for GIS point features that you want to linearly reference. In this case, use the GeoMedia Professional Analyze Geometry command to add coordinate attributes to the recordset. From there the LRS Keys For Coordinate Events command can add LRS keys, and the data is ready to use in a linear referencing environment.

The LRS Keys for Coordinate Events Command Workflow

This section presents the procedural steps for using the LRS Keys For Coordinate Events command.


2. Select the Transportation > LRS Analysis > LRS Keys For Coordinate Events.

The LRS Keys For Coordinate Events dialog box is displayed.


3. Select a feature or query from the LRS Feature drop-down list.

4. Click Properties in the LRS Feature box.

The LRS Keys Properties dialog box is displayed.

27-2


5. On the LRS Keys Properties dialog box, accept the defaults, or choose other Primary, Secondary, Tertiary, and Quaternary Keys for the LRS recordset from the appropriate drop-down lists.

6. Click OK to exit this dialog box.

7. On the LRS Keys For Coordinate Events dialog box, select an event feature from the Event Feature drop-down list.

8. Click Properties in the Event Feature box.

The Coordinate Event Properties dialog box is displayed.

9. On the Coordinate Event Properties dialog box, select either Point or Linear as the Event Type.

10. In the Coordinate Fields box, accept the defaults, or choose other properties for each drop-down list.

27-3


11. Accept the default, or define another event coordinate system by clicking Browse or by clicking Define/Modify Coordinate System. For more on this see the “Working with the Coordinate System Dialog Box” chapter.

Note: 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 brings up the GeoWorkspace Coordinate System dialog box. From there select the Save As button and assign it a filename and location.

12. Click OK to exit the Coordinate Event Properties dialog box.

13. In the Coordinate Tolerance box on the LRS Keys For Coordinate Events dialog box, accept the default, or key in another number for the coordinate tolerance in the Tolerance textbox.

14. Accept the default, or choose another unit for the coordinate tolerance from the Unit drop-down list.

15. In the Output Query box, accept the default, or choose another query name in the Query Name field; then assign an optional description in the Description field.

16. Check the Display results in data window check box to display the new results in a data window. Then accept the default, or select or key in a Data window name.

17. Click OK to generate and to display the results in the specified data window.

18. After reviewing the result, you can change the tolerance by editing the query. Do this by first selecting Analysis > Queries from the GeoMedia Professional menu bar.


27-4


19. Select the query generated by the LRS Keys for Coordinate Events command, and then click Properties.


20. Edit the Query name, the Description, the Tolerance, and the Unit as desired. When finished click OK. This will alter the results of the query according to your new input.

27-5


27-6

28-1

Working with the Routes and Sections to LRS Command

This section provides an overview of the Routes and Sections To LRS command. This command is used to create an LRS query recordset that can be used by other transportation processes. It combines elements from ARC/INFO® Routes and Sections feature classes because neither class has all of the fields necessary for an LRS model. The output of this command is a query containing an LRS Linear feature class. This query can be used as input to any of the GeoMedia Transportation Manager commands that need an LRS linear feature class (for example, Dynamic Segmentation or LRS Event Overlay). If desired, the Warehouse > Output to Feature Class command can be used to permanently store the resultant LRS Linear feature class. This will facilitate validation and editing of the LRS feature class.

An ARC/INFO Route System, as served up by the ARC/INFO data server, is essentially two tables: the Routes table and the Section table. The Routes table is derived from the Section table by the following:

1. Finding all sections that make a route,

2. Finding the vertices that make up each section of the route,

3. Creating polyline geometries from the vertices, and

4. Creating a geometry collection of the section polylines to form the geometry for one row in the Routes table.

The Routes and Sections To LRS command builds a recordset (query) that contains all fields from the Routes table except for geometry, adds the Begin and End measure fields from the Section table, and adds a new geometry field where the geometry collection is unbundled back to individual polylines. This recordset, a combination of both the Routes and Section tables, can then be used by other GeoMedia Transportation Manager commands.

The Routes and Sections to LRS Command Workflow

This section presents the procedural steps for using the Routes and Sections To LRS command.


2. Select Transportation > LRA Analysis > Routes and Sections To LRS.


The Routes and Sections To LRS dialog box appears.

3. From the Feature class drop-down list in the Routes box, select a Routes feature class

to represent the Routes table.

4. From the Link field name drop-down list in the Routes box, select the Routes link field name, whose values link the Routes table to the Sections table.

5. From the Feature class drop-down list in the Sections box, select a Section feature class to represent the Sections table.

6. From the Link field name drop-down list in the Sections box, select a Sections link field name, whose values link the Sections table to the routes table.

7. Select a name from the From measure field name drop-down list. The values of this field name represent the begin distance for the section.

8. Select a name from the To measure field name drop-down list. The values of this field name represent the end distance for the section.

9. In the Query name field, accept the default query name, or type in a new name.

10. Check the Display LRS in map window check box if the resulting query is to be displayed in a map window, or click the Display LRS in data window box if the resulting query is to be displayed in a data window.

Note: You can select an existing map or data window or enter a new map or data window name, and you can set the style of the output linework.

11. Click OK.

28-2

29-1

Working with the LRS Event Transform Command

This command provides a GUI for transforming an LRM based Event to a Datum based event, and vice-versa. Refer to the Event Data Transforms section in Advance LRS functionality documentation for more details on the requirements of Event data transformation. The command uses the LRSEventTransform Pipe for performing the transformation.

Three transformation modes are available on the GUI – LRM to Datum, Datum to LRM, and LRM to LRM. In case of LRM to LRM transformation, the GUI allows you to define Source LRM and Target LRM. The command allows computation of values for certain fields that are in proportion with the output segment length for linear events. Examples of such proportionate attributes are cost and length fields. You can also exclude any unwanted fields by unselecting them in the Event Attributes dialog box. The resultant output query is added to the queries folder and displayed in the data window based on your choice.

The LRS Event Transform Command Workflow This section presents the procedural steps for using the LRS Event Transform command.

1. Select the LRS Event Transform command.


2. On the LRS Event Transform dialog box, select the Transform mode in the Transform mode box.

3. In the LRS definition box, select the Connection name, the LRS name, and the Source LRM. If the transform mode is LRM to LRM, select the Target LRM. Then select the Event definition, and click Properties to fill in Event Key(s) and measure field information.

Note: For more information on the Event Properties dialog box, refer to the LRS Event Input control document.

4. For a linear Event feature class, select Proportionate attributes to specify attributes that depend on the output segment length, such as cost/length.

5. Accept or override the default query name assigned in the Query name textbox, and assign an optional description using the Description text box.

6. To display the output of the LRS Event Transform command in a data window, toggle the Display results in data window check box to ON. Then accept the default data window name, or select/ key in a data window name.

7. Click OK to generate and display the LRS Event Transform command results in the specified data window.

29-2

30-1

Working with the LRS and Marker Properties Dialog Boxes

This section provides an overview of the LRS Properties and Marker Properties dialog boxes, which provide a graphic user interface for entering LRS properties in GeoMedia Transportation Manager. For more on the subject of LRS properties and models, see the “GeoMedia Transportation LRS Data Structures” appendix

Use these two dialog boxes in the LRS Maintenance and Analysis commands to enter LRS properties. These dialog boxes provide a standard method for entering this information.

The following are two workflows, one for the LRS feature class and one for the Marker feature class.

The LRS Properties Dialog Box Workflow for an LRS Feature Class

This section presents the procedural steps for using the LRS Properties dialog box for an LRS feature class.

Note: If the selected LRS feature is a Display LRM Query, the LRS Properties are restored based on the special extensions available from the query, and they are made read-only.

1. In the LRS Feature Class portion of the dialog box, click Properties.



2. In the LRS Key Fields box, select Primary, Secondary, Tertiary, and Quaternary keys of the LRS feature class for as many keys as you use.

3. In the Geometry Reversed field, select the Boolean (true or false) field name that defines whether to use each linear feature’s digitizing direction 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). Use of this field is optional and, if not used, it is assumed that each linear feature’s digitizing direction is its direction of increasing measures.

4. In the LRS Definition Fields box, select the field names of the Start Measure and End Measure from the drop-down lists if you selected a Measure model type. If you selected a Duration model type, select the field names of the Start Measure and Duration (length) from the drop-down lists.

5. If you selected an Internal Marker model type, select the field names of the Begin Marker and End Marker (End Marker is optional) from the drop-down lists.

6. In the LRS Unit field, select the field name of the unit for the measures of this LRS feature class.

7. Click OK after setting the appropriate values or Cancel to discard your changes.

The Marker Properties Dialog Box Workflow for a Marker Feature Class

This section presents the procedural steps for using the Marker Properties dialog box for a Marker feature class. .

30-2

Working with the LRS and Marker Properties Dialog Boxes

Note: If the selected LRS feature is a Display LRM Query, the Marker Properties are restored based on the special extensions available from the query, and they are made read-only.

1. In the Marker Feature Class portion of the dialog box, click Properties.


If the selected LRS feature is a Display LRM Query that supports External Datum based markers, the Marker Properties dialog box’s appearance is somewhat different.

2. In the Key Fields box, select Primary, Secondary, Tertiary, and Quaternary keys of

the Marker feature class for as many keys as you use. For datum based markers, select the Datum ID field.

3. In the Name field, select the field name of the marker name for the Marker Feature class.

30-3


30-4

4. In the Measure field, select the field name of the measure for the Marker feature class.

5. In the Unit field, select the field name of the unit of measure for the Marker feature class.


31-1

Working with the Event Properties Dialog Box

This section provides an overview of the Event Properties dialog box, which provides support for setting and retrieving Event properties. For more on the subject of Event properties (and LRS models), see the “GeoMedia Transportation LRS Data Structures” appendix.

Use this dialog box in the LRS Maintenance and Analysis commands to input Event properties. This dialog box has two flavors and provides a standard method for entering LRM or Datum based Event information.

The LRM-based Event Properties Dialog Box Workflow

This section presents the procedural steps for using the LRM-based Event Properties dialog box.

1. Select the LRM-based option; then click Properties.



2. Select the Event Type (Point is the default).

3. Select the Event Reference Type (Measure is the default).

4. In the Key Fields box, select the Primary, Secondary, Tertiary, and Quaternary keys of the Event feature class for as many keys as you use.

5. In the Unit box, select the name of the unit for the Measure fields in 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).

6. In the Measure Fields box, select from the drop-down lists the available field names that are appropriate for your selection of the Event Type and the Event Reference Type.

7. If your Event Reference Type is Coordinate, type in a numeric value for the coordinate tolerance in the Coordinate Tolerance box (the unit for this value is the one you set for the Distance on the Units and Formats tab of the GeoWorkspace Coordinate System dialog box).

8. If your Event Reference Type is Coordinate, set the coordinate system information for the selected events in the Event Coordinate System box. The Define/Modify Coordinates System button brings up the Coordinate System dialog box. For more on this see the “Working with the Coordinate System Dialog Box” chapter.

31-2

Working with the Event Properties Dialog Box

Note: 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 brings up the GeoWorkspace Coordinate System dialog box. From there select the Save As button and assign it a filename and location.

The Datum-based Event Properties Dialog Box Workflow

This section presents the procedural steps for using the datum-based Event Properties dialog box.

1. Select the Datum based option; then click Properties.


2. Select the Event Type (Point is the default).

3. In the Datum Fields boxes, select the Datum ID, Start Measure, and End Measure fields.

4. In the Measure unit box, select the name of the unit for the datum measure fields in the event feature class.

31-3


31-4

Working with the Coordinate System Dialog Box

This section provides an overview of the Coordinate System dialog box, which provides support for setting and retrieving coordinate system properties.

Use this dialog box in the Event Input Control to input coordinate system properties. This dialog box provides a standard method for entering this information.

This control provides a graphic user interface for the following:

• Keying in or selecting .csf files

• Defining or modifying the coordinate system

• Setting or retrieving coordinate system properties

The Coordinate System Dialog Box Workflow This section presents the procedural steps for using the Coordinate System dialog box.

1. Click Browse in the Coordinate System box to locate an existing coordinate system file.

2. Select a coordinate system from the dialog box.

Note: The file type supported by this control is .csf.

OR

3. Click Define/Modify Coordinate System to define a new coordinate system file.

The Coordinate System Properties dialog box is displayed.

32-1


4. Select the Coordinate system type, and set or modify the coordinate system using this dialog box.

Note: See the GeoWorkspace Coordinate System Dialog Box topic in GeoMedia and/or GeoMedia Professional Help for more information.

On the Coordinate System dialog box, select the Projection Unit and the Projection Quadrant if the selected coordinate system type is Projection, or select the Geographic Unit and the Geographic Quadrant if the selected coordinate system type is Geographic.

32-2

33-1

Working with the LRS Data Preparation Workflows

This section provides recommendations for preparing an LRS feature class for use. Although the steps do not necessarily need to be taken in the exact order shown, this is the recommended order. These procedures make use of an assortment of commands from both the GeoMedia Transportation Manager product and from the core product, GeoMedia Professional.

The following data preparation steps are covered in this section:

• Reformat Linear Collections

• Validate and Fix Geometry

• Validate and Fix Connectivity

• Calibrate the LRS

• Validate the LRS

• Fix the LRS

• Index the LRS

This chapter specifically addresses single level LRSs. For information on Multilevel LRSs see the following chapters:

• “Introduction to Working with Multilevel LRSs”

• “Intersection Preparation Workflows”

• “Single Level to Multilevel LRS Conversion Workflow”

Reformat Linear Collections

In this section we will use the Reformat Linear Collections command to repair some of the problems common to datasets that make use of geometry collections. A geometry collection is a grouping of multiple geometries that are associated with just one record in the dataset. It sometimes happens that components of these collections can be out of order, or some of them may have incorrect digitizing directions. These errors can produce incorrect and erratic results in analysis. The Reformat Linear Collections command corrects these problems. For more information on the Reformat Linear Collections command, see the “Working with the Reformat Linear Collections Command” chapter. This workflow assumes that an LRS feature class exists.


1. Open a GeoWorkspace; then connect to the warehouse containing the linear feature class representing the transportation network.

2. Select the Reformat Linear Collections command.

3. Under the Reformat linear collections in drop-down, pick your LRS feature class, and click OK.

Validate and Fix Geometry

In this section you will identify geometry anomalies and correct them. These can produce incorrect and erratic results in analysis. The types of anomalies that can be found and corrected using this step are duplicate points, empty geometry collections, invalid geometries, and so on. This workflow assumes that there exists an LRS network.


2. From the GeoMedia Professional menu bar, select Tools > Validate Geometry.

3. Under the Validate geometry contained in drop-down, pick your LRS feature class, and click OK.

33-2


4. From the GeoMedia Professional menu bar, select Tools > Fix Geometry.

5. Set the check boxes to fix both Duplicate points and Kickbacks, and click OK.

Note: The step above will remove problems from the anomalies query set as they are fixed. Any remaining problems may need to be fixed manually, usually using the Edit Geometry command in GeoMedia Professional.

Validate and Fix Connectivity

In this section you will identify connectivity problems and correct them. These problems can produce incorrect and erratic results in analysis. The types of problems that can be found and corrected using this step are undershoots, overshoots, and so on. This workflow assumes that there exists an LRS feature class.


2. From the GeoMedia Professional menu bar, select Tools > Validate Connectivity.

3. Under both of the Features in drip-down lists, pick your LRS feature class, and click OK. Select the Undershoots, Overshoots, and Node Mismatches check boxes, and set the tolerance as desired. Then click OK.

33-3


4. From the GeoMedia Professional menu bar, select Tools > Fix Connectivity.

5. First, select the Trim overshoots check box, and click OK. Next, run it again, but select the Extend undershoots check box, and click OK.

Note: The step above will remove problems from the connectivity problems query set as they are fixed. Any remaining problems may need to be fixed manually, usually using the Edit Geometry command.

33-4


Calibrate the LRS

The next step is to add both LRS Key and measurement attribution to your LRS. This can be facilitated using either the Interactive LRS Calibration command or the LRS Calibration command. Instructions on how to use these command are shown in the “Working with the Interactive LRS Calibration Command” and “Working with the LRS Calibration Command” chapters.

Validate the LRS

The next step is to run the LRS Validation command, which can identify many of the LRS-specific errors that can occur. These errors can include mistakes in measurement attribution, incorrect sequencing of elements that make up a given route, errors in digitizing direction, and so on. Instructions on how to use this command are shown in the “Working with the LRS Validation Command” chapter.

33-5


Fix the LRS

There are a variety of errors that can be identified by the LRS Validation command, and there is no one command that corrects them all. Many of the errors that are identified by LRS Validation are errors in attribution, which of course can be corrected by using the Edit > Select Set Properties command in GeoMedia Professional to enter corrected attribution.

One of the other common errors is reversed digitizing direction (although the Calibration commands should prevent these). There is a command in GeoMedia Professional that can be used to correct these errors: the Edit > Geometry > Reverse Direction command. Simply select the LRS features you want to reverse, and then pick this command. This command works well in conjunction with the digitizing direction annotation workflow shown in the “LRS Annotation Workflows” chapter.

Index the LRS

For optimum performance, it is recommended that certain columns of your LRS be indexed. The LRS Key fields should be indexed as well as the Begin Measure attribute. If Internal Marker fields are used, these should be indexed as well. If an External Marker table is used, the Marker Name and Measure columns of that table should be indexed.

33-6

34-1

Working with Intersection Preparation Workflows

The purpose of this chapter is to provide workflows for breaking linework at intersections while still maintaining a valid LRS. In general it is recommended that linework at same-elevation intersections be broken, but to allow linework representing overpasses to cross without breaking. Although breaking linework at intersections is not necessary for most linear referencing analysis, there are several good reasons to do so.

The first reason is that two of the commands in GeoMedia Transportation are based on the assumption that linework is broken as described above. These twp commands are the Create Intersection Markers command (available in GeoMedia Transportation Manager only) and the Create Intersections and Midblocks command. These commands will only consider intersections with broken linework. The second reason is for routing networks. The routing analysis tools in GeoMedia Transportation will only allow turns at intersections with broken linework.

The methodology for breaking linework at intersections varies depending on whether the LRS in question is a single level or a Multilevel LRS. Because of that this chapter is broken into two sections, one for each kind of LRS.

Intersection Preparation for Single Level LRSs This subsection outlines how to prepare intersections in single level LRSs. Because it works on your entire LRS at one time, mistakes are potentially very time consuming. So, always, always save your data prior to using this procedure. If you are using GeoMedia Transaction Manager, it is wise to start a new Revision Set just for this purpose. That way if there are any problems you can merely discard the changes, and your data will be back to its prior state.

In the workflow below, work directly with the LRS feature class. Do not use a Display LRM query.

1. Assure that your LRS is valid. The “LRS Data Preparation Workflows” chapter has good tips on how to do this. Pay special attention to undershoots and overshoots identified by the Validate Connectivity command.

2. You may also want to use the Generate Base Geometry command in GeoMedia Professional to identify overlapping linework. Review the resultant data window, and locate linework where the FeatureCount attribute is greater than 1. Look at the original linework in these areas and make corrections as necessary.


3. Use the Feature Class Definition command to add the following three fields: ORIG_LENGTH, NEW_BEG_MEASURE, and NEW_END_MEASURE. The field names are not important, but these default names are shown for clarity. Later we will remove these fields.

4. Use the Updates Attributes command to populate the ORIG_LENGTH field. Use the

following expression, substituting the geometry name from your LRS and whatever units you use for your LRS measure data. LENGTH(Input.geometry, TrueMeas, Mile)

34-2


5. Use the Validate Connectivity command to check for unbroken intersecting Geometry. Use your LRS as both “Features in” entries.

6. Use the Fix Connectivity command to break crossing lines. Choose the query from

the previous step. Please note that this is a fairly intensive process and will likely take a while.

7. Use the Functional Attribute command to add the following four fields to our LRS.

In this example, the output query is called Original+.

34-3

− Add a NEW_LENGTH field that captures the length of the segment now that we have performed breaks at intersections. Use the following expression, substituting the geometry name from your LRS and whatever units you use for your LRS measure data.

LENGTH(Input.geometry, TrueMeas, Mile)


− Add a SPLIT boolean field that that identifies whether the segment in question was split. We recommend this be done by finding segments where the absolute difference between the two length fields is greater than approximately 0.00001. This is to avoid false positives from round-off error.

IF(ABS(Output.NEW_LENGTH - Input.ORIG_LENGTH) > 0.00001, TRUE(), FALSE())

− Add a CALIBRATION_LENGTH field that holds the proportion of the original measure length that each segment should have. Use the following expression, substituting the LRS measure fields (the original ones) from your LRS.

(Output.NEW_LENGTH / Input.ORIG_LENGTH) * (Input.END_MEASURE - Input.BEG_MEASURE)

− Add a CALIBRATION_KEY field that is a concatenation of the existing LRS Keys. This step is not necessary if you have two or fewer LRS Keys. Use the following expression, substituting the LRS key fields from your LRS.

CONCATENATE('|', Input.PRIMARY_KEY, Input.SECONDARY_KEY, Input.TERTIARY_KEY, INPUT_QUATERNARY_KEY)

8. Create an attribute query of the query from the previous step where the value of the SPLIT field is True. This shows only the segments that were split, and thus will give us a feature class that only has the records that need to be recalibrated. In this example, the new output query is called SplitOriginal+.

34-4


9. Run the LRS Calibration command on the query from the previous step using the

following settings. Please note that this is a fairly intensive process and will likely take a while.

− Use the query from the previous step as the LRS feature class.

− Under the LRS Properties dialog box, use the CALIBRATION_KEY field as the Primary key if you created that field in Step 7. Otherwise, use your LRS Keys for the Primary and Secondary keys (if you have two LRS Keys). In either case, for the next two keys, use your two original LRS measure fields. This will allow the program to calibrate each original set of segments that were split separately.

− Under the LRS Properties dialog box, use the two new LRS measure fields you created in Step 3.

− Use CALIBRATION_LENGTH field as the length source.

− Use the By digitized direction option for Route Direction.

− Use the Constant gap distance option for gaps with a Value of 0.

34-5


10. Use the Update Attributes command on the query from Step 8 to add the old LRS

begin measure value to both new LRS measures. The LRS Calibration command starts all routes at 0, and this step corrects for that. Use the following expressions, substituting your field names as appropriate. Please note that this is a fairly intensive process and will likely take a while.

− Set the NEW_BEG_MEASURE field equal to: Input.NEW_BEG_MEASURE + Input.BEG_MEASURE

− Set the NEW_END_MEASURE field equal to: Input.NEW_END_MEASURE + Input.BEG_MEASURE

34-6


11. This is a good time to do some quality control as you have both the new and old measures.

12. Use the Update Attributes command to copy the new LRS measures over old LRS measures. This way you can continue to use the same LRS measure fields you always have. Use the following expressions.

− Set the original LRS begin measure field equal to: Input.NEW_BEG_MEASURE

− Set the original LRS end measure field equal to: Input.NEW_END_MEASURE

At this point, the process of breaking linework at intersection is complete. As always with a process this extensive, it is a good idea to run more quality control. Also feel free to

34-7


34-8

delete the fields added in Step 3 and the queries created in Steps 7 and 8. And, of course, if major errors are found, you can always return to the backup you made at the beginning of this procedure.

Note that the above procedure breaks lineworks at all intersections, whether they are same-elevation intersections or overpasses. To merge back the linework at overpasses, just use the Merge Features command. Unfortunately, this command merely takes the attribution from the first selected feature. Therefore, you will need to adjust attributes, such as LRS measures, manually using the Properties dialog box. If you are preparing intersections in a single level LRS for the purpose of converting it to a Multilevel LRS, you may want to address the merging after the conversion and then use the Merge LRM Segments command.

Intersection Preparation for Multilevel LRSs This subsection outlines how to prepare intersections in Multilevel LRSs. The workflow for breaking linework at intersections for Multilevel LRSs is much less automated than the procedure for single level LRSs. Therefore, if you are trying to decide whether to perform this to a linear feature class before or after conflating it to a Multilevel LRS, it is highly recommended that you do it beforehand. Please note that this is a fairly intensive process and will likely take a while.

In the procedure below, work with a Display LRM query for the particular LRM/Geometry combination you are interested in.

1. Use the Validate Connectivity command to check for unbroken intersecting Geometry. Use your Display LRM query as both “Features in” entries. Make sure to display your results in both the map window and a data window.


2. Set your Map Window Properties so that when you select a record in the data window

created in the previous step, it is centered in your map window.

3. Arrange your windows similarly to what is shown in the following. Also set your

Intersection snap (vector) as the only active snap, and set your Display LRM query as the only locatable feature class in your map window. You may also want to check that the PickQuick options are set to your satisfaction.

34-9


4. Cycle through the anomalies in your data window, and use the Split LRM Segment

command to split the appropriate segments. Select the segment to split at the intersection, and use the PickQuick dialog box as necessary to make sure you are splitting the correct segment. Note you only want to split segments at same-elevation intersections, not at overpasses.

If you need to merge any segments that were accidentally split (or for any other reason), you can do this with the Merge LRM Segments command.

34-10

35-1

Working with the Single Level to Multilevel LRS Conversion Workflow

This section provides a workflow for converting a traditional single level LRS into a Multilevel LRS. This workflow is broken into the following steps, which are covered in this chapter:

• Data model design

• Source data preparation

• Data conversion

• Final touches

It is also recommended that you read the “Multilevel Linear Referencing Systems (MLRS)” section of the “Introduction to Linear Referencing” chapter for an overview of Multilevel LRSs. Also information on how to perform analysis with and data maintenance on a Multilevel LRS is presented in the “Working with Multilevel LRSs” chapter.

It should be noted that Intergraph offers services to assist organizations with tasks such as this.

Data Model Design There are a lot of options as to how you can build your Multilevel LRS. The questions below will help you decide which options are right for you.

1. Which Linear Referencing Methods (LRMs) are in use at your organization? An LRM is a combination of a route naming scheme and a route measurement scheme. One LRM might use a two-field naming scheme (one field for route type, another for route number) and a measurement scheme based on cumulative distance in kilometers from the start of each route. Another LRM might use a four-field naming scheme (street prefix, name, type, and suffix) and a measurement scheme based on street addresses.

One of the best ways to discover which LRMs are in use is to review the Event data used by various groups within the organization and also to review Event data that is provided to the organization from outside agencies.

2. Which geometric network representations are in use at your organization? Are there others you would like to use? Some organizations use different geometric representations with different levels of generalization for use with different map


35-2

products. Others like to incorporate geometric representations from other agencies. For instance, a national or regional transportation agency may want to use geometry from more local transportation agencies. This often is very useful in facilitating data sharing between various levels of government.

3. Does it make sense to use Region IDs to subdivide your data? If your linear network is relatively large, if there is some logical scheme for splitting up your data, and if you often perform work that is focused on a relatively small portion of the data, then it may well make sense to use region IDs.

4. Is there a concern regarding the integrity of event data in the light of changes to the transportation network? This is the event location stability issue discussed in more detail in the “Introduction to Linear Referencing” chapter.

5. Does your current LRS make use of internal or external markers? If external markers are used, is there any concern regarding the integrity of event data in the light of changes to the transportation network? This is very similar to the event location stability issue.

6. Is any of your event data based on distance and direction from intersections? What naming convention is used in this data to identify the streets involved?

7. Do you (or would you like to) perform analyses based on aggregating data to nearby intersections?

8. Do you want to perform routing analyses? For routing directions, do you have a preference of which LRM contains the most appropriate street names? Does one LRM have the most appropriate coverage for routing analyses?

9. What anomalies does your LRS data have? What anomalies do you expect to now have as part of the move to a Multilevel LRS? How does existing event data address these anomalies? Below are two examples of the types of anomalies referred to here:

o Shared roadbeds – One stretch of road that is referred to by two or more route names

o Single-Double centerlines – Instances where the same route is shown as a single centerline in one geometry table and as dual centerlines in another

10. Is temporality important to the type of analyses you do? Would like to be able to do trend analyses? Would you like to able to evaluate accident rate, congestion, and so on, before and after capital improvement projects?

11. Are there any specific requirements placed on your LRS to accommodate integration with other systems?

Based on your answers to the questions above, you can use the LRS Metadata Definition command to both create and set up the tables for your Multilevel LRS. One strategy is to use the Create New options of this command to create the tables you will need. Then, if you wish to make changes to these default tables, you can do so with the Feature Class Definition command. Lastly, you can update your LRS definition using the LRS


35-3

Metadata Definition command to address changes you made with the Feature Class Definition command, such as new field names, and so on.

Source Data Preparation There are two main tasks associated with source data preparation. The first is to identify the source data and the second is to clean and validate that data.

Here are some questions to help with identifying source data.

1. What linear feature classes are available to supply LRM and Geometry information?

2. Does existing Event data line up with LRS Keys and measures on at least one of the source linear feature classes?

3. What data exists for external markers? Is it point features and/or point event data? Does it include LRS Key information?

4. What data exists for Region data? Often geographic boundaries work well for this. Does the source have a code field and a description field?

5. If the LRS is also going to be used for routing, do you have source data for edge impedance, turning restrictions and impedances, and routing restrictions?

Here are some steps to help assure that your source data is clean and ready for data conversion.

1. Run all of your source linear feature classes through the steps outlined in the “LRS Data Preparation Workflows” chapter.

2. If there is any chance that the network may be used someday for routing, intersection-referenced event data, or intersection aggregation, then we recommend you run all of the source linear features through the steps outlined in the “Intersection Preparation Workflow” chapter.

3. If a particular source linear feature class is going to be used for routing, run through the steps in the “Manual Routing Data Maintenance – The Initial Network Creation Workflow” section of the “Routing data Maintenance Workflows” chapter.

4. If you plan on using Region IDs, your source linear feature classes will need to have Region ID attribution. If your source data does not have Region ID attribution, then there are several ways to populate such a field. One such way is as follows:

• Use the Feature Class Definition command to add a Region ID field to your source linear feature class

• Use the Aggregation command with you source linear feature class as the summary feature and your region area features as the detail feature. Have it output a calculated Region ID field.


35-4

• Use the Update Attributes command on the Aggregation query to copy the values from the calculated Region ID to the Region ID field added in the first step.

Data Conversion If you have more than one linear feature class, you will have to convert one first and then conflate the others to the resultant Multilevel LRS. There are no strict requirements regarding which linear feature class to convert and which ones to conflate. However, it makes sense to convert either the source linear feature class with the largest coverage or the one you were planning to use for routing.

The conversion step is performed using the Create new MLRS features from all input LRS features option of the Multilevel LRS Conflation command. Full details of this command are in the “Working with the Multilevel LRS Conflation command” chapter, but here are the basics:

• The inputs are the source linear feature class to be converted and the Multilevel LRS you defined during the Data Model Design step.

• If you are going to be using Region IDs, you need to specify how that data will be populated. If all of your data that you are processing at this time is from a single region, then you can just pick that region from the list. However, the most common case is that the Region ID is contained in one of the fields in your source linear feature class. In that case, you can specify the name of that field.

• You will be asked to pick which LRMs and/or Geometries you will populate. In this case, you should pick at least one of each. Some source linear feature classes actually contain the information for more than one LRM. In that case, feel free to pick those LRMs you wish to populate.

• You will be asked to define which fields from the source linear feature class will be used to define each key field in each selected LRM. Optionally, you can carry over other fields as well. If your source linear feature class has routing attributes, you should definitely carry those attributes over.

The conflation steps can be done in an interactive method, a bulk method, or a combination of both. Conflation is introduced in the “Working with Multilevel LRSs” chapter. The goal is to map new data to the linear datum established during the conversion step.

Final Touches Here are a few other tasks that you might want to take to complete your Multilevel LRS. Not all of these tasks will pertain to every implementation.

• Convert external markers


35-5

• Create Intersection Markers

• Register your Event data

The process for converting external markers will vary depending on the goals you have concerning location stability for your markers. If you had external markers that functioned fine with your single level LRS, they will still work fine with your Multilevel LRS. You just need to add them to your LRS definition by using the LRS Metadata Definition command. Make sure to set the LRS model for your LRM to Measure with External Measure Markers. If you want to have location stability for your markers, you just register your markers exactly the same way you register your events, as explained in the “Working with Multilevel LRSs” chapter. Once you have done this, you will need to add them to your LRS definition. Make sure to set the LRS model for your LRM to Measure with External Datum Markers.

If you will be using intersection-referenced events, you will need to create Intersection Markers. These are a special kind of external markers that contain extra information about intersection configurations. The steps for creating intersection markers are described in the “Working with the Create Intersection Markers command” chapter.

Lastly, if event data location stability is important to you, will need to perform a one-time registration step to each of your event data tables. This process is described in the “Working with Multilevel LRSs” chapter. It will also need to be done once to each new batch of event data.


35-6

36-1

Working with the LRS Annotation Workflows

This section provides step-by-step instructions on how to do a variety of LRS annotations. These procedures make use of an assortment of commands from both the GeoMedia Transportation Manager product and from the core product, GeoMedia Professional. The purpose of this section is to provide useful ways to add annotation that is useful in creating and maintaining a functional LRS.

The following workflows are covered in this section:

• Annotate digitizing direction

• Annotate begin and end measurements

• Annotate even measures along the LRS

Annotate Digitizing Direction

In a functioning LRS, all of the segments that make up a particular road (or pipe, and so on) need to all have the same digitizing direction. However, one cannot discern this digitizing direction just by looking at the features. The workflow in this subsection will annotate the features with an arrow that points in the digitizing direction. It is based on dynamic pipes so that if the digitizing direction is reversed, the arrow will automatically reverse as well. This workflow assumes that an LRS feature class exists.


2. From the GeoMedia Professional menu bar, select Transportation > LRS Event Generation.

3. Use the LRS Event Generation command as described in the “Working with the LRS Event Generation Command” chapter to create point events at the midpoint of each LRS feature.


4. From the GeoMedia Professional menu bar, select Analysis > Dynamic Segmentation.

5. Use the Dynamic Segmentation command as described in the “Linear Referencing” chapter in Working with GeoMedia or Working with Geomedia Professional to create a graphic feature class for the accident point events. Pick point symbology that will show directionality. In this example, we picked an arrow from the Wingdings font. Also make sure, under the Advanced Display Settings, to set the rotation to be aligned to the LRS.

36-2


6. When the results are returned, the GeoWorkspace will resemble the following:

Annotate Begin and End Measurements

In building and maintaining an LRS, it is often convenient to be able to see the measurement attributes at the beginning and end of each LRS feature. In the workflow in this subsection we will annotate the begin and end measures of each these features with distinct symbology. It is based on dynamic pipes, so if the measurement attribution is changed, the annotation will change as well. This workflow assumes that there exists an LRS feature class.


36-3



3. Use the LRS Event Generation command as described in the “Working with the LRS Event Generation Command” chapter to create point events at the beginning of each LRS feature.


5. Use the LRS Event Generation command as described in the “Working with the LRS Event Generation Command” chapter to create point events at the end of each LRS feature.

36-4



7. Use the Dynamic Segmentation command as described in the “Linear Referencing” chapter in Working with GeoMedia or Working with Geomedia Professional to create a graphic feature class for the begin measure point events. Make sure, under the Advanced Display Settings, to set the rotation to be aligned to the LRS.


9. Use the Dynamic Segmentation command as described in the “Linear Referencing” chapter in Working with GeoMedia or Working with Geomedia Professional to create a graphic feature class for the end measure point events. Make sure, under the Advanced Display Settings, to set the rotation to be aligned to the LRS.

36-5


10. From the GeoMedia Professional menu bar, select Insert > Label and choose settings similar to those shown here.

36-6



36-7



Annotate Even Measures Along the LRS

Another useful type of annotation used in LRS maintenance is marking evenly spaced measures along the LRS. In the workflow in this subsection, we will annotate these evenly spaced measures with both a symbol and a label. These symbols and labels are based on dynamic pipes, so if the measurement attribution is changed, the annotation will change as well. This workflow assumes that an LRS feature class exists.



3. Use the LRS Event Generation command as described in the “Working with the LRS Event Generation Command” chapter to create point events at evenly spaced measures along the LRS.

36-8



5. Use the Dynamic Segmentation command as described in the “Linear Referencing” chapter in Working with GeoMedia or Working with Geomedia Professional to create a graphic feature class for the evenly spaced point events. Make sure, under the Advanced Display Settings, to set the rotation to be aligned to the LRS.

36-9




36-10


36-11


36-12

37-1

Working with the LRS Analysis Workflows

This section provides step-by-step instructions on how to do a variety of LRS analyses. These procedures make use of an assortment of commands from both the GeoMedia Transportation Manager product and from the core product, GeoMedia Professional. The purpose of this section is to provide useful ways to turn an often overwhelming amount of linear referenced data into meaningful, readily usable information.

The following workflows are covered in this section:

• Aggregate point event data onto linear segments

• Aggregate point event data onto intersections

• Aggregate linear event data within boundaries

• Aggregate segment event data onto linear segments by proportion

Aggregate Point Event Data onto Linear Segments

This workflow makes use of source point event data to identify hot spots that may represent areas requiring special attention. In the example used, we are locating areas along a transportation network with an unusually high density of accidents. It is assumed that there exists both an LRS feature class and accident point-event data.

1. Open a GeoWorkspace; then connect to the warehouse containing the linear feature class representing the transportation network. If the event feature class is in a different warehouse, make a connection to that warehouse also.


3. Use the Dynamic Segmentation command as described in the “Linear Referencing” chapter in Working with GeoMedia or Working with Geomedia Professional to create a graphic feature class for the accident point events. For this analysis it is not necessary to display the results of the dynamic segmentation to the map window.


4. From the GeoMedia Professional menu bar, select Transportation > LRS Event

Generation.

5. Use the LRS Event Generation command as described in the “Working with the LRS Event Generation Command” chapter to create equal length linear events along each route.


7. Use the Dynamic Segmentation command as described in the “Linear Referencing” chapter in Working with GeoMedia or Working with Geomedia Professional to create a

37-2


graphic feature class for the equal length linear events. For this analysis it is not necessary to display the results of the dynamic segmentation to the map window.

8. From the GeoMedia Professional menu bar, select Analysis > Aggregation.

9. For the Aggregate to summary features in drop-down list, select the dynamically segmented equal length linear events. This feature class is referred to as the input class.

10. From the From detail features in drop-down list, select the dynamically segmented

Accident point events. This feature class is referred to as the detail class.

37-3


11. Under the Spatial Aggregation tab, pick the touch operator.

12. Under the Attribute Aggregation tab, pick the LRS Keys from each list. This will ensure, at intersections, that the accidents are counted towards the correct road.

13. Under the Output tab, set the Resolution Operator to First. This means, in our

example, that if an accident is located right at the split between two linear features, it will only be counted once and will be counted towards the first of these two linear features that is found in the warehouse.

37-4


14. Click the New button under the Output tab to bring up the Functional Attribute

dialog box. In the following picture we have created a count of the accidents.

15. After filling in the Functional Attribute dialog box and dismissing requests to create additional functional attributes, we are returned to the Aggregation dialog box. In this case we will not display the results in the map window. Click OK to process the aggregation.

37-5


16. From the GeoMedia Professional menu bar, select Analysis > Attribute Query. For the feature class, choose the results of the last step. For the Filter, choose something that locates the most egregious situations. In the example below we are picking 2-km segments that had five or more accidents in the year in question.

37-6



Aggregate Point Event Data onto Intersections

This workflow makes use of source point event data and aggregates the data onto a separate intersection feature class. This technique is especially useful to identify hot spots that may represent areas requiring special attention. The example we are using here is accidents near intersections. We are summing up the number of accidents that occur near each intersection. In this way we can identify intersections with particularly high accident rates. It is assumed that an LRS network and Accident point event data exist.

1. Open a GeoWorkspace; then connect to the warehouse containing the linear feature class representing the transportation network. If the Intersection feature class or Accident event feature classes are in different warehouses, make a connection to those warehouses also.

2. From the GeoMedia Professional menu bar, select Transportation > LRS Analysis > Create Intersections and Midblocks.

3. Use the Create Intersections and Midblocks command as described in the “Working with the Create Intersections and Midblocks Command” chapter to create Intersection and Midblock features.

37-7



5. Use the Dynamic Segmentation command as described in the “Linear Referencing” chapter in Working with GeoMedia or Working with Geomedia Professional to create a graphic feature class for the accident point events. For this analysis it is not necessary to display the results of the dynamic segmentation to the map window.


7. For the Aggregate to summary features in drop-down list, select the Intersection feature class. This feature class is referred to as the input class.

37-8


8. From the From detail features in drop-down list, select the dynamically segmented Accident point events. This feature class is referred to as the detail class.

9. Under the Spatial Aggregation tab, pick the touches operator.

10. Under the Output tab, set the Resolution operator to First. This means, in our example, that if an accident falls within the distance we set of more than one intersection, that it will only be counted once. For some analyses it might also make

37-9


sense to use the All resolution operator, in which case an accident of this type will be counted against all intersections it is close to.


dialog box. In the following picture we have created a count of the accidents:

2.


37-10


13. From the GeoMedia Professional menu bar, select Analysis > Attribute Query. For the feature class, choose the results of the last step. For the Filter, choose something that locates the most egregious situations. In the example below, we are picking intersections that had five or more accidents in the year in question.


37-11


Aggregate Linear Event Data within Boundaries

This workflow makes use of source linear event data and aggregates the data onto a separate area feature class. This technique is especially useful for creating summary reports. The example we are using here is Roadway Classification event data, and we are summing up the mileage of each classification within regional boundaries. It is assumed that there exists an LRS network, a Boundary area feature class, and Road Classification linear event data.

1. Open a GeoWorkspace; then connect to the warehouse containing the linear feature class representing the transportation network. If the Boundary feature class or Road Classification event feature classes are in different warehouses, make a connection to those warehouses also.


3. Use the Dynamic Segmentation command as described in the “Linear Referencing” chapter in Working with GeoMedia or Working with Geomedia Professional to create a graphic feature class for the Road Classification linear events. For this analysis it is not necessary to display the results of the dynamic segmentation to the map window.

37-12


4. From the GeoMedia Professional menu bar, select Analysis > Functional Attributes.

5. For the Add functional attributes for drop-down list, select the dynamic segmentation of the Road Classification events. This feature class is referred to as the input class.

6. Click the New button under the Output tab to bring up the Functional Attribute dialog

box. In the following picture, we have created a Ratio attribute that stores the ratio between the event length based on measurement attribution and the length based on the geometry. The formula shown below is: (Input.END_KM - Input.BEG_KM) / LENGTH(Input.Geometry1, TrueMeas, Kilometer)

37-13


7. After filling in the Functional Attribute dialog box and dismissing requests to create additional functional attributes, we are returned to the main Functional Attributes dialog box. In this case we will not display the results in the map window. Click OK to process the command.

8. From the GeoMedia Professional menu bar, select Analysis > Spatial Intersection. For the first feature class, pick the results of the previous step. For the second feature class, pick the area boundary feature class. Select the touch operator. Click OK to

37-14


process this command, which will split our roads where they cross area boundaries. This will make it easier to sum up the lengths within each boundary.


10. For the Aggregate to summary features in drop-down list, select the Boundary area feature class. This feature class is referred to as the input class.

11. From the From detail features in drop-down list, select the results of the Spatial

Intersection command. This feature class is referred to as the detail class.

12. Under the Spatial Aggregation tab, pick the contain operator because we are trying to

aggregate the roads that are contained within each area.

37-15


13. Under the Output tab, set the Resolution Operator to First. This is not terribly critical since the Spatial Intersection step has already ensured that each road segment can be easily assigned to one and only one area.


dialog box. In the following picture, we have calculated the total length of roads in the Primary Arterial class. The formula shown below is: SUM(IF(Detail.ROADWAY_CL='Primary Arterial', LENGTH(Detail.IntersectionGeometry, TrueMeas, Kilometer) * Detail.Ratio,0))

37-16


15. After filling out the Functional Attribute dialog box, fill out other similar functional attributes for each roadway classification. Afterwards, dismiss requests to create additional functional attributes, and we are returned to the Aggregation dialog box. In this case we will not display the results in the map window. Click OK to process the aggregation.

37-17


16. The resultant data window will summarize the length of roads in each classification in each region.

Aggregate Segment Event Data onto Linear Segments by Proportion

This workflow makes use of source linear event data and aggregates the data onto equal length segments. This technique is especially useful to identify hot spots that may represent areas requiring special attention. The example we are using here is construction project events. We are summing up the construction costs of all projects onto the underlying equal length segments. In this way we can identify areas in which construction costs have been particularly high.

It is understood that the source construction project event data might overlap several of the equal length segments and that the construction project events themselves may overlap each other. It is assumed that there exists both an LRS network and Construction Project linear event data.

1. Open a GeoWorkspace; then connect to the warehouse containing the linear feature class representing the transportation network. If the event feature classes are in a different warehouse, make a connection to that warehouse also.


3. Use the Dynamic Segmentation command as described in the “Linear Referencing” chapter in Working with GeoMedia or Working with Geomedia Professional to create a graphic feature class for the Construction Project linear events. For this analysis it is not necessary to display the results of the dynamic segmentation to the map window.

37-18



5. Use the LRS Event Generation command as described in the “Working with the LRS Event Generation Command” chapter to create equal length linear events along each route.


7. Use the Dynamic Segmentation command as described in the “Linear Referencing” chapter in Working with GeoMedia or Working with Geomedia Professional to create a

37-19


graphic feature class for the equal length linear events. For this analysis it is not necessary to display the results of the dynamic segmentation to the map window.


9. For the Aggregate to summary features in drop-down list, select the dynamically segmented equal length linear events. This feature class is referred to as the input class.

10. From the From detail features in drop-down list, select the dynamically segmented

Pavement Type linear events. This feature class is referred to as the detail class.

37-20


11. Under the Spatial Aggregation tab, pick the touch operator.

12. Under the Attribute Aggregation tab, pick the LRS Keys from each list. This will ensure, at intersections, that the accidents are counted towards the correct road.

13. Under the Output tab, set the Resolution Operator to All. This means, in our

example, that all construction project events will be counted to any equal length segments that they lie upon.

37-21



dialog box. In the following picture we have created an Aggregate Cost attribute. The formula shown does a number of things. The costs for each construction project event that lies along an equal length segment are multiplied by the length of the portion of the construction project event that coincides with the equal length segment and then are divided by the full length of the construction project event. This proportionally allocates the construction costs to each equal length segment that the construction project event crosses. Then these proportionally allocated costs are summed up for each equal length segment and rounded off. The formula from this functional attribute is: SUM((IF(Input.EndMeasure < Detail.End_Km, Input.EndMeasure, Detail.End_Km)- IF(Detail.Beg_Km > Input.BeginMeasure, Detail.Beg_Km, Input.BeginMeasure)) / (Detail.End_Km - Detail.Beg_Km) * Detail.Cost)

37-22



16. There are a number of ways to view the results of this aggregation. The picture below shows a thematic view of the aggregate construction costs we have calculated.

37-23


37-24

Introduction to Routing The purpose of this chapter is to outline the basic concepts behind the routing capabilities of GeoMedia Transportation Manager. Each of the major components of a routing network is described, and table descriptions are provided. Lastly, the various routing analysis and maintenance tools are described.

What is a Routing Network? A routing network is a system of connected linear features that can be used to support the simulated transportation of goods, services, or communications between locations on the network. A network can be thought of as an abstract model that is derived from a set of linear features and their relationships. Each network model is primarily composed of a set of geographic features called Edges and a set of implied features called Nodes.

Each Edge in a network represents one component of the transportation system that is being modeled. Streets, highways, shipping lanes, railway tracks, and even Ethernet cables between computer systems are all examples of Edges in a network. Nodes, on the other hand, are implied features that connect the end points of Edges together. A Node might have a real-world analog, such as a street intersection, a seaport, or a computer name, but often there is no real-world equivalent for a Node.

Nodes

Edges

This preceding figure of a street network illustrates the relationship between Edges and Nodes. Each Edge in the Streets feature class is connected to exactly two Nodes, and each Node is connected to one or more Edges. In this example, the Nodes are stored and

38-1


displayed as a point feature class. In your application, however, the Node locations might only be implied — and never created as a feature class that can be displayed in a map.

Edge-Node Connectivity The spatial relationship between Edges and Nodes defines the implicit connectivity of the network. Each Node in the network is given a unique identifier termed a NodeID. Similarly, each Edge in the network is given a unique identifier termed an EdgeID. Network connectivity is maintained by storing the relationship of each EdgeID and the two NodeIDs that connect to it. This relationship is often termed Edge-Node Connectivity and is the basis for all the routing analysis tools included in GeoMedia Transportation Manager.

12

3

4

56

FromNode Location

ToNode Location

Within GeoMedia, each Edge is defined as a series of points or vertices that define its shape. There is an implicit ordering of the vertices from the first vertex to the last vertex in the chain that gives each Edge a direction. The Edge in the preceding diagram is composed of six vertices. The Node that occurs at the first vertex in the chain is referred to as the FromNode, and the Node that occurs at the last vertex in the chain is referred to as the ToNode. The location of the FromNode is always coincident with the first vertex in the chain. Similarly, the location of the ToNode is always coincident with the last vertex in the chain. In this model, Edges always and only connect at a Node. When two Edges connect, they are said to be adjacent to one another and to have at least one Node in common and, therefore, at least one coincident vertex location.

38-2

Introduction to Routing

NodeID = 1003

NodeID = 1010

NodeID = 1005

NodeID = 1011

NodeID = 1004

Edg

eID

= 10

037

EdgeID = 10110

EdgeID = 10021

Edge

ID=

1003

8

1004100310110

1011100410038

1004101010037

1005100410021

ToNodeFromNodeEdgeID

1004100310110

1011100410038

1004101010037

1005100410021

ToNodeFromNodeEdgeID

Each Edge table is a linear feature class that has the following fields:

• EdgeID – This is a long integer value that uniquely identifies each Edge within the routing network.

• FromNodeID – This is a long integer value that identifies the Node at the beginning of this Edge.

• ToNodeID – This is a long integer value that identifies the Node at the end of this Edge.

• Length (recommended) – This is a numeric value that defines the length of this Edge. Alternately, Begin Measure and End Measure fields can be used, and the length will be calculated as the difference between the two values. As a last alternate, no length fields may be used at all, and the various routing analysis tools can calculate the length from the Edge’s geometry. This is considerably slower than the other two options.

• Cost(s) (optional) – This is a numeric value showing the impedance of navigating this Edge (more on impedance later). Some users use different cost fields to model different situations, such as rush hour vs. weekend travel. Also costs can be defined either symmetrically (the same for both travel directions) or asymmetrically (different for each travel direction). Asymmetrical Edge costs require two fields.

• OneWay (optional) – This is a long integer value that holds the code value that defines any one-way navigation restrictions for this Edge. For more on this, see the “Working with the OneWay Editor Command” and the “Working with Display OneWays Command” chapters.

• Blocked (optional) – This is a long integer value that holds the code value that defines any blockages for this Edge. For example, a street might be temporarily blocked due to construction, an accident, or some other reason. It may be blocked in one travel

38-3


38-4

direction or both. For more on this, see the “Working with the Blockage Editor Command” and the “Working with Display Blockages Command” chapters.

• Restrictor source field(s) (optional) – These are fields used in constructing Edge Restrictors. Restrictors are formulaic expressions that define whether a network component is navigable or not (more on Restrictors later).

Each Node table is a point feature class that has the following fields:

• NodeID – This is a long integer value that uniquely identifies each Node within the routing network.

• Cost (optional) – This is a numeric value showing the impedance of crossing this Node (more on impedance later).

• Blocked (optional) – This is a Boolean value (true or false) showing whether navigation across this Node is blocked or not.

• Restrictor source field(s) (optional) – These are fields used in constructing Node Restrictors. Restrictors are formulaic expressions that define whether a network component is navigable or not (more on Restrictors later).

The process of creating a routing network from a linear feature class, along with the required Edge-Node connectivity (also known as explicit topology), is done with the Build Network command (see the “Working with the Build Network Command” chapter).

Impedance Impedance measures the separation (time, cost, distance, etc.) of different places on a network. Impedances can be based on distance, cost, time, or any other numeric measure assigned to your network. Impedances can be stored on the various components of the routing network: Edges, Nodes, Turns, and Stops (more on Turns and Stops later). Finding Paths with minimum impedance is what routing analysis is all about. The routing analysis tools give two different choices for minimizing impedances. One is to Minimize Length, which simply means that it finds Paths with the minimum sum of Edge lengths. The other is to Minimize Cost, which finds Paths with the minimum sum of Cost values for Edges and, optionally, Nodes, Turns, and/or Stops. It is assumed that all Cost fields use the same units.

Turn Tables The routing network, defined by Edges and Nodes and the connectivity between them, can be further refined in a number of ways to better model reality. The first of these ways is with a Turn table. Each record in a Turn table is linked to a specific Edge-to-Edge movement at a Node in the network. Turn tables are commonly used to add delay to turning movements at street intersections or to prohibit certain turn options at a given intersection. For instance, it might take longer to make left turns than right turns at


intersections. These asymmetrical delays and prohibited turns are easily managed using Turn tables.

Turn tables are not required. Neither is it required to have a record in a Turn table for every turn option possible in your routing network. If a turn option is not included, the routing analysis tools assume that the turn is permissible and that no cost (e.g., a delay) is associated with that turn. In general it is best to omit records for all turn options that are not prohibited and for which there is no known delay because this will improve performance during routing analyses. On the other hand, if the Path results of your analysis seem unreasonably “jaggy,” it is likely because you are modeling no delay for turns.

One special case for which it is customary not to include turn records is for “two-edge nodes”. That is, a Node to which only two Edges are connected, making it impossible to make real turns (see the following illustration). The Build Network command explicitly lets you omit these turn options from the Turn table it generates.

2-Edge Nodes

U-turns are another special case. Even in cases where U-turns are permitted, you may want to exclude them from your analysis, especially if you are routing large vehicles. For this case you do not need to create prohibited U-turn records in your turn table. You can simply use the Disable U-turns option while doing your analysis.

Each Turn table is a non-graphic table that has the following fields:

• Signed FromEdgeID – This identifies the in-bound Edge. The sign says whether the direction of travel is with the digitizing direction (+) or in the reverse of the digitizing direction (-).

• Signed ToNodeEdgeID– This identifies the out-bound Edge. The sign says whether the direction of travel is with the digitizing direction (+) or in the reverse of the digitizing direction (-).

• Cost (optional) – This is a numeric value showing the impedance of this turn option (more on impedance later).

• Blocked (optional) – This is a Boolean value (true or false) showing whether this turn option is blocked to navigation or not.

38-5


• Restrictor source field(s) (optional) – These are fields used in constructing Turn Restrictors. Restrictors are formulaic expressions that define whether a network component is navigable or not (more on Restrictors later).

The following diagram shows a portion of a routing network and a sample Turn table that shows all of the possible turn options. You can calculate the number of possible turn options at each Node by squaring the number of Edges attached to the Node. So for a three-edge intersection there will be nine possible turn options, and for a four-edge intersection, there will be 16. It should be noted that this turn table could be simplified a bit just by making Edge 592 a one-way street (more on one-way streets later).

LeftFalse3-533-575Circle BackTrue4-592592U-turnTrue4592592StraightFalse1-564592U-turnTrue4-592-592Circle BackFalse1592-592StraightTrue1-564-592Veer leftTrue1-592564

U-turnTrue4-575575U-turnFalse4575-575RightFalse2564-575

Veer rightFalse1592564

U-turnFalse4564-564StraightFalse1-533-564RightFalse2575533

LeftFalse3575-564U-turnTrue4-564564

FalseFalseTrue

Blocked

144

Cost

Straight564533U-turn-533533U-turn533-533

DescriptionToEdgeIDFromEdgeID

LeftFalse3-533-575Circle BackTrue4-592592U-turnTrue4592592StraightFalse1-564592U-turnTrue4-592-592Circle BackFalse1592-592StraightTrue1-564-592Veer leftTrue1-592564

U-turnTrue4-575575U-turnFalse4575-575RightFalse2564-575

Veer rightFalse1592564

U-turnFalse4564-564StraightFalse1-533-564RightFalse2575533

LeftFalse3575-564U-turnTrue4-564564

FalseFalseTrue

Blocked

144

Cost

Straight564533U-turn-533533U-turn533-533

DescriptionToEdgeIDFromEdgeID

Edg

eID

= 53

3E

dgeI

D=

564

EdgeID = 575

EdgeID = 592

There are two tools provided for working with Turn tables. One is the Build Network command, which allows you to create all the Turn table records that you want with a single command with a great amount of flexibility (see the “Working with the Build Network Command” chapter). The second is the Turn Editor command, which allows you to interactively edit turns one intersection at a time (see the “Working with the Turn Editor Command” chapter).

Restrictors Restrictors are expressions defined for network components (Edges, Nodes, and Turns) that are used to constrain the network optimization algorithms. For example, routing a heavy truck over a road network requires each Edge in the path to have a maximum operating weight greater than the operating weight of the vehicle. Restrictors are necessary in logistics applications that involve managing specialized vehicles or in cases where physical or institutional constraints are imposed on the vehicle’s Path. Height, width, and weight limits are commonly used Restrictors for vehicles on a network. The routing

38-6


38-7

analysis tools in GeoMedia Transportation Manager can create Paths through the network where these Restrictors are used to constrain the resultant Paths.

Restrictors are modeled as a series of expressions that create Boolean (true/false) results. Each Restrictor models a particular constraint over the routing network. Examples of Edge Restrictors are as follows:

• Maximum Operating Weight > 80,000lbs

• Maximum Vertical Clearance > 13’6’’

The first Restrictor would restrict Paths in the network to those Edges that have a maximum operating weight greater than 80,000 lbs. The second Restrictor would restrict the Path to those Edges that have a maximum vertical clearance greater than 13 feet 6 inches. If both Restrictors were enabled, the Path would be restricted to those Edges that have both a maximum operating weight greater than 80,000 lbs. and a maximum vertical clearance greater than 13 feet 6 inches.

• Truck Route = True

The third example illustrates the case in which a single Restrictor could replace one or more Restrictors used in combination. If feasible truck Edges were known in advance and stored in the feature table as a Boolean variable, then the Paths created could be restricted to those Edges with a Truck Route value of True.

Note: GeoMedia Transportation Manager assumes that Edge Restrictors are symmetrically applied. This means that any Restrictor applied to an Edge feature in the network feature table will apply in both directions.

Although Edge Restrictors are the most common type of Restrictors, they can also be used on Nodes and/or Turns. Examples of Node and Turn Restrictors are as follows:

• 4-Way Stop = False (Node)

• Disallowed during rush hour = False (Turn)

• Turn name <> Left (Turn)

The first Restrictor would restrict Paths over the network from navigating through 4-way stops, which may be useful to avoid slow intersections. The second Restrictor is useful for creating Paths that eliminate turns that are usually legal but which are prohibited during rush hour. The third Restrictor would restrict the Path from taking turns designated as Left. This may be desirable for some vehicles such as snow plows.

Each Restrictor table is a non-graphic table that has the following fields:

• Name – This text field uniquely identifies this Restrictor within this table. It is recommended that it be as descriptive as possible as to what this Restrictor is for.


• Enabled – This Boolean (true/false) field is used to check off whether a Restrictor is to be used or not used during routing analysis.

• Expression – This text field holds a Functional Attribute formula that equates to a Boolean (true/false) value. Network components will only be considered for routing analysis resultant Paths if their expression equates to True. This expression usually has references to fields within the network component (Edge, Node, or Turn) for which it is being used to constrain.

Unlike the other methods shown so far to fine tune the routing network, Restrictors are not so much descriptors of the network as they are descriptors of how certain vehicles navigate that network. As they are usually vehicle-specific, they might be useful for one routing analysis and not for another. To accommodate this, GeoMedia Transportation Manager has made it easy to check off which Restrictors you wish to use for each analysis. For more on how to create, edit, enable, and disable Restrictor see the “Working with the Restrictor Editor Command” chapter.

Stops Network Stops are important locations on a network that will be used as part of an analysis. A Stop can represent any type of geographic phenomena; common examples of Stops are Customers, Distribution Centers, Fire Stations, and Crime scenes. The exact nature of what constitutes a Stop is defined in the context of your application and might be a point that is digitized from a map, a feature in a point feature class, or an input by a GPS or some other external mechanism.

Each point of interest must be turned into a Stop by snapping the input location to an Edge in the network and storing some information about where the snap point occurred. This process is illustrated in the following figure:

Edge

Edge

Input location for the Stop

Stop location is snapped to the Edge

38-8


38-9

Each Stop table is a point feature class that has the following fields:

• StopName – This text field is used to provide a descriptive name for each Stop and can be used in labeling and directions.

• StopSetName – This text field contains a group name for a set of Stops within a Stop table. This allows you to have a single Stop table that serves a number of purposes.

• Enabled – This is a Boolean (true/false) field that indicates whether this Stop is to be used in a routing analysis or not.

• StopEdgeID – This long integer field identifies which Edge within the routing network that this Stop lies along.

• StopEdgePosition – This numeric field indicates the relative position of the Stop along its Edge. A value of 0 means it as at the beginning of the Edge, and a value of 1 means it as at the end. Intermediate values between 0 and 1 describe intermediate locations along the Edge.

• ToleranceValue – This numeric field holds the snap distance used to convert the point geometry location of each record into an Edge location.

• ToleranceUnitID – This long integer field contains the code value that defines the units of the ToleranceValue field.

• StopOrder – This long integer field contains the sequential order of Stops within a Stop Set. This is used by the Best Path command if the Best Order option is not picked.

• Cost – This is a numeric value showing the impedance of this Stop. For example, a maintenance Stop to change a light bulb might have a cost of two minutes, while a maintenance Stop to fix an air conditioner might have a cost of 60 minutes.

GeoMedia Transportation Manager contains a specialized tool called the Stop Manager for taking locations you provide and assigning them to the network to create Stops. For more on how to create and manage Stops, see the “Working with the Stop Manager Command” chapter.

Routing Analysis There are five different routing analysis tools provided with GeoMedia Transportation Manager. Although their operation is described in detail elsewhere, a brief summary of all of them is provided here.


Best Path – This command gives the ability to find the best path for a vehicle that needs to make one or more stops. You may select whether Paths will be optimized so as to minimize distance traveled or to have the command minimize other “user costs,” such as time, money, or even safety. It also has an option to optimize the order of stops to further optimize the path. The time savings for maintenance, delivery, or other vehicles can result in significant cost savings, or in the case of emergency vehicles, even saved lives. For more information see the “Working with the Best Path Command” chapter.

Easy Path – This is a “quick and dirty” version of the Best Path command. The difference is that instead of using stored Stops in the analysis, you simply click on the map view, and the Paths are calculated as you click. For more information see the “Working with the Easy Path Command” chapter.

Find Closest Stops – This command finds the closest n destination Stops to a set of origin Stops. This is particularly useful for finding, for example, the two closest hospitals to each of a set of sports facilities. It is also useful in travel demand modeling workflows. Path optimization may be by distance or by user cost. For more information see the “Working with the Find Closest Stops Command” chapter.

Network Coverage – This command traces all paths that can be reached from a set of origin Stops within a given user cost or distance. This is useful, for example, in finding all the locations that can be reached from a fire station in a given amount of time and identifying areas where coverage is insufficient. You can define the number of bands of solutions using multiples of the given user cost or distance (e.g., three bands at 5 minutes would generate 5, 10, and 15 minute solutions). For more information see the “Working with the Network Coverage Command” chapter.

Generate Path Directions – This command will take the result of either the Best Path or the Find Closest Analysis command and will create directions to navigate between Stops. The format of the directions is user configurable. For more information see the “Working with the Generate Path Directions Command” chapter.

Routing Maintenance There are eight different routing maintenance tools provided with GeoMedia Transportation Manager. Although their operation is described in detail elsewhere, a brief summary of all of them is provided here. A good overview of Routing maintenance is provided in the “Routing Data Maintenance Workflows” chapter.

Build Network – This command gives the ability to create routing-ready Edge, Node, and Turn feature classes. The results of this command can be directly used with the routing analysis commands. For more information see the “Working with the Build Network Command” chapter.

38-10


38-11

Stop Manager – This command gives the ability to create and manage Stops. Stops are a special kind of point feature used by the routing analysis commands to define key points along their calculated paths. For more information see the “Working with the Stop Manager Command” chapter.

Turn Editor – This command gives the ability to interactively edit turn options. You can set costs associated with various turn options as well as being able to disallow turn options as desired. For more information see the “Working with the Turn Editor Command” chapter.

Restrictor Editor – This command gives the ability to define and edit restrictions for edges, nodes, and turns. Restrictions are very useful tools that work in conjunction with the various routing analysis commands to allow you to restrict which edges, nodes, and turns will be considered when calculating paths. For more information see the “Working with the Restrictor Editor Command” chapter.

OneWay Editor – This command gives the ability to interactively edit the one-way attributes of selected edges. This allows you to more accurately model the allowable navigation routes through a network. For more information see the “Working with the OneWay Editor Command” chapter.

Blockage Editor – This command gives the ability to interactively edit the blockage attributes of selected edges. This allows you to more accurately model the allowable navigation routes through a network. For more information see the “Working with the Blockage Editor Command” chapter.

Display OneWays – This command gives the ability to display the direction of permitted movement in the map view for all those features of the selected edge feature class that have a one-way attribute set. For more information see the “Working with the Display OneWays Command” chapter.

Display Blockages – This command gives the ability to display in the map view the direction of blockages for those edges of the selected edge feature class that have the Blockages attribute set. For more information see the “Working with the Display Blockages Command” chapter.


38-12

39-1

Working with the Build Network Command

The Build Network command allows you to create Edge, Node, and Turn queries for routing analysis. The results of this command can be directly used with the following routing analysis commands: Easy Path, Best Path, Find Closest Stops, and Network Coverage. For more information on building and maintaining a Routing network, see the “Routing Data Maintenance Workflows” chapter.

The minimum input is a linear feature class or query. Optionally, you can have a Point feature class or query as input for the Node output. This is useful when cost/blocked data already exists for these nodes. The output of Node and Turn queries is optional.

The output Edge queries will be identical to the input linear feature class except for the addition of network topology fields: an EdgeID field, a FromNode field, and a toNode field. The output Node query has point geometry and will have a NodeID field plus any selected fields from the input Node table if that option is chosen. The output Turn class will have a signed FromEdgeID field, a signed ToEdgeID field, a TurnName field, a TurnAngle field, a Cost Field, and a boolean Blocked field. A positive edge ID means the turn’s direction is same as the edge’s digitizing direction; a negative edge ID means the turn’s direction is reverse to the edge’s digitizing direction.

The Build Network Command Workflow

This section presents the procedural steps for using the Build Network command.


2. Select Transportation > Routing Maintenance > Build Network.

The Build Network dialog box is displayed.


3. On the Select linear feature class pull-down list, select a linear feature class or query from the list of all connections and queries. All fields from this feature class will be copied to the output query and will have extra network topology fields added to it so as to make it ready to use with the various routing analysis commands.

4. To generate nodes, click the Generate Nodes check box to enable the contents of the group box.

Note: Nodes are not required for routing analysis, but they are necessary if you want to assign costs to passing through nodes or if you want to block passage past selected nodes.

5. If you have an existing Node feature class or query that you want to copy attribution from, check the Copy attributes from check box. Then select the point feature class or query that you want to copy from in the pull-down list.

6. You can then click on the Attributes button to pick which Node attributes that you want to copy.

39-2


7. To generate turns, check the Generate Turns check box to enable the contents of the group box.

Note: Turns are not required for routing analysis, but are necessary if you want to assign costs to or block certain turn options. Generating turns like this is useful for making global turn assignments to represent standard conditions. To learn how to edit individual turns, see the “Working with the Turn Editor Command” chapter.

8. Click New to begin adding new turn types.

The Turn Type dialog box is displayed.

39-3


9. Select from the Name pull-down list one of the pre-defined turn types, or key in a name of your own choosing.

Note: When you pick one of the pre-defined names, the other fields of this dialog box are automatically filled in.

10. Key in a Begin Angle and an End Angle. The diagram in this dialog box will update to graphically show the range of turn angles that these two angles will encompass.

11. Set the Minimum Edges Per Node and the Maximum Edges Per Node. This allows you to exclude instances such as when only two edge segments are connected that represent just straight segments of road and not a turn opportunity.

12. Check or uncheck Blocked to give a default value for this turn type. If you check Blocked, then none of the generated turns will be allowed.

13. Key in a default Cost value (for example, the time to navigate a certain turn option).

14. Click Add.

15. Click Properties to modify a turn’s properties (except for the name) on the Turn Type dialog box.

16. Accept the default Output Edges as query name, or key in a new name (a description is optional). This field is enabled when a linear feature class is selected as input. It allows for storing resultant edges as a query in the GeoWorkspace. A default query name is assigned.

17. Accept the default Output Nodes as query name, or enter a new name (a description is optional). This field is enabled if you checked Generate Nodes. It allows for the storage of the resultant nodes as a query in the GeoWorkspace.

39-4


39-5

18. Accept the default Output Turns as query name, or enter a new name (a description is optional). This field is enabled if you checked Generate Turns. It allows for storing resultant turns as a query in the GeoWorkspace.

19. Click OK to process the inputs, or click Cancel to exit the command without processing.


39-6

40-1

Working with the Stop Manager Command

The Stop Manager command allows you to create and manage Stops. Stops are a special kind of point feature and are one of the fundamental components of network analysis. They are used by the Best Path, Find Closest Stops, and Network Coverage commands. Each of these commands uses Stops to define origin and/or destination points for the paths that they calculate along a linear network.

The Stop Manager command allows you to create or edit Stop feature classes. It also allows you to group Stops into Stop sets. This allows the logical organization of Stops and enables one Stop feature class to contain Stops used for many different purposes. New Stops can be added to the Stop Set from a feature class or a saved query, or by clicking on the map window.

The command also allows you to edit information about individual Stops. For instance, you can enable or disable individual Stops, you can reorder them, or you can edit their names or costs (for example, time spent at each Stop).

The Stop Manager Workflows There are two workflows for this command:

• Workflow for creating new stop feature classes

• Workflow for managing Stop sets

Workflow for creating new stop feature classes 1. Open a GeoWorkspace that contains one or more read/write connections.

2. Select Transportation > Routing Maintenance > Stop Manager.

The Stop Manager dialog box is displayed.


3. Click the New button in the Select stop feature class box to create a new Stop feature class.

The Create Stop Feature Class dialog box is displayed.

4. Select a read/write connection from the drop-down list, and specify a name (and optional description) for the new feature class.

5. Click OK to dismiss the Create Stop Feature Class dialog box.

Workflow for managing stop sets 1. Open a GeoWorkspace that contains one or more read/write connections.

2. Select Transportation > Routing Maintenance > Stop Manager.

The Stop Manager dialog box is displayed.

3. On the Stop Manager dialog box, select an existing Stop feature class from the drop-down list, which will show all point feature classes. However, not all point feature classes are Stop feature classes because they may not have all of the required fields. If you select a point feature class that is not a Stop feature class, you will get an error message instructing you to select a valid Stop feature class.

40-2


4. Select an edge feature class from the Select edge features drop-down list.

5. Click Properties to select the EdgeID field on the Edge Properties dialog box.

The Edge Properties dialog box is displayed.

6. Select an EdgeID field, and click OK to dismiss this dialog box and to return to the Stop Manager dialog box. If there are existing Stop sets in the Stop feature class, they will be presented in the Stop sets list box, as shown below.

7. From here you can select a Stop set and delete it by using the Delete button or edit it using the Stops sets Properties button. If you want to create a new Stop set, use the Stop sets New button.

Using either the Stop sets New or Properties button will cause the Stop Set Properties dialog box to be displayed.

Note: To view more stops in the grid, resize the height of the Stop Set Properties dialog box by dragging its border.

40-3


8. If the Stop Set Properties dialog box was reached by using the New Stop sets button on the Stop Manager dialog box, then the grid portion will be empty and the Stop set name field will be editable. In this case, fill in the desired name for the new Stop set. If you reached the Stop Set Properties dialog box by using the Stop set Properties button on the Stop Manager dialog box, then skip to the next step.

9. Click the Create Stops from Feature Class button to create Stops from an existing point feature class or query. If you do not want to do this, skip to Step 13.

The Create Stops From Feature Class dialog box will be displayed.

10. Select a point feature class or query from the Create stops from drop-down list. If you want to only use certain records from that class, you can use the Filter button to narrow the records used by using the standard GeoMedia query dialog box.

40-4


11. If you have any attribute data from the source feature class or query that you want to use to populate the Stop feature class fields, you can select them from the Select Attributes for drop-down lists. Note that all of these attribute field names are optional. Those fields that are not used will have Null or default values in the resultant Stop records.

12. Click OK to dismiss the Create Stops From Feature Class dialog box.

This will return you to the Stop Set Properties dialog box, where you will see your newly added Stops at the bottom of the list in the grid.

13. Click the Create Stops from Map button to add new Stops directly to the map. If you do not want to do this, skip to Step 19.

The Stop Set Properties dialog box will temporarily disappear, and a point feature will appear on your cursor when in the Map View.

40-5


14. Click in the Map View to place as many Stops as desired.

15. At any point in the process, you can bring up the following pop-up menu by right-clicking in the map window.

16. Select Discard last stop if you want to undo your last Stop click in the map window.

17. Select Discard all stops and restart if you want to clear all the Stops in the Stop set and restart.

18. When finished, you can either press ESC on your keyboard or select End stop creation from the right-click menu. The following dialog box will be displayed when ESC is pressed. Click Yes to return to the Stop Set Properties dialog box, or click No to place more Stops. If you click Yes, your newly added Stops can be seen at the bottom of the list in the grid. All attribute values for these new Stops will be Null or zero.

40-6


19. To edit an individual Stop, select it by clicking on the gray button to the left side of the row depicting that Stop. That row will be highlighted, and the buttons to the right of the grid will become enabled. Also, that feature will be highlighted in the Map View.

20. Once selected, there are a variety of edits that can be done to the Stop. The Name and Cost values can be edited by clicking and typing in a new value; the Stop can be deleted by clicking the Delete button ; the Stop can be moved up or down in the sequence by using the , , , and buttons; and the Stop can be enabled or disabled by clicking on the Enabled check box or by using the Enable All or Disable All buttons.

Note: The Delete button on this dialog will become disabled when there is only one stop left in the list box. If you choose to do so, an entire Stop set can be deleted using the Delete button on the Stop Manager dialog box.

The Cost value is used by the various routing analysis command if the Minimize Cost option is selected. The sequence of the stops within the grid is used by the Best Path command when the Best Order option is not used or if either the Start Fixed or the End Fixed option is used in that command. Stops that do not have their Enabled boxes checked will be ignored by the various routing analysis commands.

21. If you want to exit the Stop Set Properties dialog box without saving any of the changes you have made, click the Close button. Otherwise, first click Apply.

The Apply button makes use of the Snap Tolerance value to find the closest edge to each of the Stops in the list. This may take some time to calculate based on the size of the dataset. When completed, the Status, EdgeID, and Edge Position fields will be filled out in the grid.

The Status field will indicate the relative success of finding an Edge within the snap tolerance of each Stop. A blank field indicates success. The message “Stop located, multiple edges may be within tolerance” indicates success, but that more than one Edge was found within tolerance. The closest Edge is used in this case. The message “Not located, no edges within tolerance” indicates no Edge was located. Stops with this status will be ignored by any of the routing analysis commands.

The EdgeID and EdgePosition fields indicate which Edge a Stop was snapped to and the relative position (0 to 1) of that Stop along that Edge.

40-7


Note: The EdgeID and EdgePosition values calculated here are static values. That means that if your network changes, you may need to update these values to reflect those changes. You can update these values by revisiting the Stop Set Properties dialog box and by using the Apply button. It is possible to have the EdgeID and EdgePosition values calculated dynamically using the Output Stop Set as Query option (see Step 23 below). For example, if a network edge query is being used for network analysis, and stops have been assigned to edges prior to applying a spatial filter to the workspace or network edge query, the Stop Manager command needs to be run again to reassign the stops in a stop set.

22. Click Close to exit the Stop Set Properties dialog box and to return to the Stop Manager dialog box. If you have not first selected the Apply button, an informational message will appear, letting you know that if you exit the dialog box now, none of your changes will be saved.

23. To view your Stops, select the Output Query button. This brings up a standard output to query output dialog box. Fill out as desired, and click OK to execute the output or Cancel to cancel.

Note: The Output Stop Set as Query has another important feature. The EdgeID and EdgePosition values within this query are calculated dynamically. That means that if your network changes, these values will update automatically. This is especially useful when working with Spatial Filters. However, this dynamic behavior does inflict a performance penalty. Both static and dynamic methods for maintaining your routing network are discussed in the “Routing Data Maintenance Workflows” chapter.

24. Click Close to exit the Stop Manager dialog box and the Stop Manager command.

40-8

Working with the Turn Editor Command

The Turn Editor command allows you to interactively edit turn options. You define the intersection of interest by clicking in the map window; then you can set costs associated with various turn options as well as being able to disallow turn options as desired. As each intersection may have many turn options, graphical feedback is given in the map window to clearly indicate which turn option is being edited.

For a turn action not previously defined in the turn table, a new turn record will be created if you enter data for that turn. If a turn is not checked as prohibited and its cost is set to 0, the command will delete that turn record. When you click OK, the changes are written to the database. Clicking Cancel discards the changes.

The Turn Editor Workflow 1. Open a GeoWorkspace that contains one or more read/write connections.

Note: Due to the dynamic nature of queries in GeoMedia, it is recommended that this command be run in a workspace with a minimal number of active queries that are based on your routing network components. That is because you may pay a substantial performance penalty when running these commands while waiting for these queries to update.

41-1


2. Display the LRS linear feature class for which you wish to edit turns. Use the Legend to make sure it is locatable.

3. Select Transportation > Routing Maintenance > Turn Editor.

The Turn Editor - Definition dialog box is displayed.

4. Select a linear feature class for Edges from the Select feature class drop-down list.

5. Select an EdgeID from the Select EdgeID field drop-down list.

6. Click New in the Turns group box if you want to create a new Stop feature class. Otherwise, skip to Step 8.

The Create Turn Feature Class dialog box is displayed.

7. Select a read-write connection from the drop-down list, and specify a name (and optional description) for the new feature class.

41-2

Working with the Turn Editor Command

8. Click OK to dismiss the Create Turn Feature Class dialog box and return to the Turn Editor - Definition dialog box.

9. In the Turns box, select a Turn Table feature class from the Select feature class drop-down list. For more information on how to create this table see the “Working with the Build Network Command” chapter.

10. Select the FromEdgeID field from the Select FromEdgeID field drop-down list.

11. Select the ToEdgeID field from the Select ToEdgeID field drop-down list.

12. Select the Turn Cost field from the Select Turn Cost field drop-down list.

13. Select the Turn Blocked field from Select Turn Blocked field drop-down list.

14. Click OK to accept your Turn definition settings, or click Cancel to exit the command. In either case the Turn Editor – Definition dialog box is dismissed.

15. If you clicked OK, you will be prompted to “Click on an intersection where turns are to be edited. Press ESC to exit this command.” Click inside the map window on the intersection of edge features where there are turn options you want to edit.

If one or more edges are located, they are processed to display the Turn Editor dialog box.

If no edges are located, a message box is displayed prompting for another click.

Note: Located EdgeIDs are displayed along the row and the column of the grid. Turn cost and blocked values are displayed in the grid cells.

16. Click in a grid cell in this dialog box. Each cell represents a turn option. When you click in a cell, the software highlights the From Edge and the To Edge associated with that turn movement. The From Edge will be further identified by an arrow displayed on it. Once the turn option that you want to edit is identified, you can edit the cost associated with this turn option by typing it into the text box in the cell. You can also disallow the turn option by checking the Blocked check box.

41-3


Note: For one-way streets it is more efficient to mark these streets as one-way streets (see the “Working with the OneWay Editor Command” chapter) than to disallow turns that would be traveling in the wrong direction. It is not necessary to both mark the street as one-way and to disallow the turn.

17. Click OK to save the edits, or click Cancel to dismiss the dialog box.

The Turn Editor dialog box disappears, and you are once again prompted to identify another intersection.

18. Repeat Steps 15 through 17 to edit as many intersections as you need. Press ESC when the Turn Editor dialog box is not showing to exit the command.

41-4

42-1

Working with the Restrictor Editor Command

The Restrictor Editor command allows you to define and edit restrictions for edges, nodes, and turns. Restrictions are very useful tools that work in conjunction with the various routing analysis commands to allow you to solve specific routing problems. For example, if you are routing a very large vehicle, you may want to limit your routing analysis to consider only edges with at least a 30,000 pound weight rating and a height rating of at least 13 feet. If you are routing a vehicle during rush hour, you may want to avoid turns that are illegal during those hours. If you are doing emergency planning for a holiday, you may want to avoid certain intersections that are closed due to street fairs.

These restrictions are defined using the Functional Attribute capabilities of GeoMedia. The Functional Attribute interface allows you to easily define simple restrictions, but you also have the power to model very complex restrictions based on multiple fields with intricate equations. These Functional Attribute expressions need to resolve to a Boolean (True or False) value. Only edges, nodes, or turns whose expression evaluates as True will be considered to be in the Path results of any of the routing analysis commands. The various restrictions created with this command can be individually enabled or disabled and can be used in combination with each other. This gives you a great deal of flexibility to do analyses such as routing large vehicles during rush hour. For more information, see the discussion of the Functional Attributes command in Working with GeoMedia or Working with GeoMedia Professional.

The Restrictor Editor Workflow 1. Open a GeoWorkspace with at least one read/write connection to a warehouse.

2. Select Transportation > Routing Maintenance > Restrictor Editor.


3. Click New in the Select Restrictor feature class box to create a new Restrictor feature class on the Create Restrictor feature class dialog box. To use an existing Restrictor feature class, skip to Step 5.

4. Select an existing connection name from the Connection drop-down list, key in name of the restrictor feature class in the Feature class name field and, optionally, key in a Description. Then click OK to create the new feature class and to add columns with predefined names.

5. Select a feature class from the Select Restrictor feature class pull-down list.

6. On the Restrictor Editor dialog box, click New in the Restrictors box to define a new restrictor on the Functional Attribute dialog box.

42-2

Working with the Restrictor Editor Command

7. Accept or override the default name for the restrictor in the Functional attribute name field, and then build an expression that results in a Boolean value (True or False). If you create an expression that does not result in a Boolean value, the software will issue this error message: “The expression evaluates to an ineligible data type.” Only edges, nodes, or turns whose expression evaluates as True will be considered to be in the Path results of any of the routing analysis commands.

Note: For more information, see the discussion of the Functional Attributes command in Working with GeoMedia or Working with GeoMedia Professional.

8. Click Add to save the restrictor.

9. Select a restrictor in the list, and click Edit in order to edit the restrictor on the Functional Attribute dialog box.

10. Edit the restrictor name or expression, and click OK to save the changes.

11. On the Restrictor Editor dialog box, select a restrictor in the list, and click Delete to delete the restrictor.

12. Click on the check box next to each item in the list to enable or disable the restrictors.

13. Click OK to save the edits and to dismiss the dialog box, or click Cancel to dismiss the dialog box without saving the edits.

42-3


42-4

Note: Edits made with the Restrictor Editor command have no effect on pre-existing results from the Best Path, Find Closest Stops, or Network Coverage commands. To see the effects of changes to restrictions, you need to re-run any routing analyses.

43-1

Working with the OneWay Editor Command

The OneWay Editor command allows you to interactively edit the one-way attributes of selected edges. This allows you to more accurately model the allowable navigation routes through a network. By default, every edge in the network model is assumed to be bi-directional. A bi-directional edge is one that can be traversed in either the forward direction (that is, in the direction of digitization or FromNode to ToNode) or the reverse direction (that is, in the reverse direction of digitization or ToNode to FromNode). However, using this command, individual edges can also be set to one-way in either the forward direction or the reversed direction.

The command uses visual feedback in the map window to facilitate the editing of one-way restrictions. The selected edges will be symbolized in the map window based on their one-way attribution. As you edit the one-way restrictions, the symbology of the selected edges will change to match the current setting.

Underlying this visual feedback is the editing of an integer value of the One-way attribute of the Edge feature class. The supported integer values for this attribute, and their meanings, are listed below:

Value Meaning

0 or Null

No one-way restrictions to navigation

1 One-way navigation allowed in reverse digitizing direction

2 One-way navigation allowed in digitizing direction

The OneWay Editor Workflow 1. Open a GeoWorkspace that contains one or more read/write connections.


2. Select one or more edges in the map window that you wish to edit.


This will cause the OneWay Editor command to become enabled.

3. Select Transportation > Routing Maintenance > OneWay Editor.

The OneWay Editor dialog box will be displayed.

4. Select an Edge feature class from the Edit oneway restrictions in pull-down list. The list will be limited to only those linear feature classes in your select set.

5. Select a Oneway field from the Select oneway field drop-down list.

6. Click OK to dismiss the OneWay Editor dialog box and bring up the OneWay Options dialog box.

7. Choose one of the four OneWay options. Their effect will be indicated in the map window by arrows showing allowed travel flow. If there are no arrows, that indicates that travel is allowed in both directions.

8. Once you have set the OneWay restrictions, click OK to save these changes to the database, or click Cancel to discard these changes.

43-2

Working with the OneWay Editor Command

43-3

Note: Due to the interactive nature of the routing analysis tools, any active routing analysis queries will be updated if the Use OneWays option was chosen.


43-4

44-1

Working with the Blockage Editor Command

The Blockage Editor command allows you to interactively edit the blockage attributes of selected edges. This allows you to more accurately model the allowable navigation routes through a network. By default, every edge in the network model is assumed to be unblocked. An unblocked edge is one that can be traversed in either the forward direction (that is, in the direction of digitization or FromNode to ToNode) or the reverse direction (that is, in the reverse direction of digitization or ToNode to FromNode). However, using this command, individual edges can also be set to blocked in the forward direction, blocked in the reversed direction, or blocked in both directions.

The command uses visual feedback in the map window to facilitate the editing of blockage restrictions. The selected edges will be symbolized in the map window based on their blockage attribution. As you edit the blockage restrictions, the symbology of the selected edges will change to match the current setting.

Underlying this visual feedback is the editing of an integer value of the Blockage attribute of the Edge feature class. The supported integer values for this attribute, and their meanings, are listed below:

Value Meaning

0 or Null

No blockage to navigation

1 Navigation blocked in reverse digitizing direction

2 Navigation blocked in digitizing direction

3 Navigation blocked in both directions

The Blockage Editor Workflow 1. Open a GeoWorkspace that contains one or more read/write connections.



2. Select one or more edges in the map window that you wish to edit.

This will cause the Blockage Editor command to become enabled.

3. Select Transportation > Routing Maintenance > Blockage Editor.

The Blockage Editor dialog box will be displayed.

4. Select an Edge feature class from the Edit blockage restrictions in pull-down list. The list will be limited to only those linear feature classes in your select set.

5. Select a blockage field from the Select blockage field pull-down list.

6. Click OK to dismiss the Blockage Editor dialog box and bring up the Blockage Options dialog box.

7. Choose one of the five Blockage options. Their effect will be indicated in the map window by blocked arrows showing blocked travel flow. If there are no blocked arrows, that indicates that travel is unblocked in both directions.

8. Once you have set the Blockage restrictions as desired, click OK to save these changes to the database, or click Cancel to discard these changes.

44-2

Working with the Blockage Editor Command

44-3

Note: Due to the interactive nature of the routing analysis tools, any active routing analysis queries will be updated if the Use Blockages option was chosen.


44-4

Working with the Display OneWays Command

The Display OneWays command displays the direction of permitted movement in the map window for all those features of the selected edge feature class that have a one-way attribute set. The permitted direction of flow is indicated by arrows pointing in that direction. Edges without one-way restrictions have no arrows.

The command generates unique legend entry names that correspond to the arrow pattern for displaying the one-way in forward (that is, in the direction of digitization) and the reverse (that is, opposite to the direction of digitization) direction. The display of one-way can be switched off from the map view by deleting or making the display off for the corresponding legend entry(s).

The Display OneWays Workflow This section presents the procedural steps for using Display OneWays.


2. Select Transportation > Routing Maintenance > Display OneWays.

The Display OneWays dialog box is displayed.

45-1


3. Select the edge feature class from the Display OneWay restrictions in drop-down list.

4. Select the one-way field for the edge feature class in the Select OneWay field drop-down list.

5. Click OK to display the one-ways for the selected edge feature class in the map view.

The one way edges in the network will be added to your map window and legend that display the one-way conditions of those edges that have a one-way restriction set. If there are no one-way restrictions set in the entire selected edge feature class, an error message to this effect will be displayed.

45-2

Working with the Display Blockages Command

The Display Blockages command displays in the map window the direction of blockages for those edges of the selected edge feature class that have the Blockages attribute set. Blockages are flags used to restrict movement over the network. They are assumed to be more dynamic than one-way restrictions and can change quickly over time. If a blockage flag is not set, it is assumed that the edge feature is not blocked. An edge can be temporarily blocked due to construction, an accident, or some other reason. Blockages can limit travel in either or both directions. The blocked direction of flow is indicated by blocked arrows pointing in that direction. Edges without blockages have no blocked arrows.

The command generates unique legend entry names that correspond to the arrow pattern for displaying the blockages in forward (that is, in the direction of digitization), the reverse (that is, opposite to the direction of digitization), and both direction(s). The display of blockages can be switched off from the map view by deleting or making the display off for the corresponding legend entry(s).

46-1


The Display Blockages Workflow This section presents the procedural steps for using Display Blockages.


2. Select Transportation > Routing Maintenance > Display Blockages.

The Display Blockages dialog box is displayed.

3. Select the edge feature class from the Display blockages in drop-down list.

4. Select the blockage field for the edge feature class in the Select blockage field drop down list.

5. Click OK to display the blockages for the selected edge feature class in the map view.

The Blocked edges in the network will be added to your map window and legend that display the blockage conditions of those edges that have a blockage set. If there are no blockages set in the entire selected edge feature class, an error message to this effect will be displayed.

46-2

Working with the Easy Path Command

The Easy Path command provides a simple method to find the best path for a vehicle that needs to make one or more stops (one vehicle, many stops). Route optimization may be by distance or by user cost. This command allows you to define a best path by simply clicking on Network edges displayed in a map window.

The Configure Network dialog box allows you to specify the inputs that define the network for computing the best path. Properties can be set on the tabs of this dialog box for the Edge, Node, and Turn feature classes. If a resultant path is to be optimized by cost, a tab is available to set the Cost fields. Specifying restrictor features on the Restrictors tab for Edges, Nodes, and Turns can restrict the results.

The order in which stops are visited in the path result is determined by the order in which you create stops by clicking on the map. A pop-up menu is provided to allow various levels of undo and also to allow you to output the Stops and Path as queries and display them on the map.

47-1


The Easy Path Workflow This section presents the procedural steps for using Easy Path.


2. Select the Transportation > Routing Analysis > Easy Path.

The Easy Path dialog box appears.

3. Click Properties to select the inputs to define the network on the Configure Network

dialog box.

47-2

Working with the Easy Path Command

4. Set the properties for the Edges, Nodes, and Turns feature classes on the dialog box tabs. If a resultant path is to be optimized by cost, a tab is available to set the Costs inputs. In order to restrict the results, specify restrictor features on the Restrictors tab.

Note: See the “Working with the Configure Network Dialog Box” chapter for a detailed discussion of this dialog box.

5. Click OK.

The selected edge, node, and turn features are displayed on the Easy Path dialog box in the Edges, Nodes, and Turns text boxes.

6. On the Easy Path dialog box, select Distance or Cost in the Minimize by box to optimize the path.

7. Click OK.

8. Follow the First Stop and Next Stop prompts to define a path by placing stops on the network in the map window.

9. At any point in this process you can bring up the Easy Path pop-up menu by right-clicking in the map window.

10. Select Discard last stop if you want to undo your last Stop click in the map window. The path will revert to what it was before this last Stop.

11. Select Restart path if you want to undo all of your Stop clicks in the map window. The path will be erased altogether.

12. Select Output results from the pop-up menu to save the completed path and stops to the query folder, and, optionally, to add them to the legend for display in the map window.

The Easy Path Output dialog box appears.

47-3


13. Check Output Stops to define a name and description for the stops query.

14. Check Display Stops in map window to set the style and to display the stops in the map window.

15. Check Output path to define a name and description for the path query.

16. Check Display Path in map window set the style and to display the path in the map window.

17. Select Exit command from the pop-up menu to exit the command.

47-4

Working with the Best Path Command

The Best Path command will allow you to find an optimal Path through a given set of Stops on a network; for example, finding the best path for a vehicle that needs to make one or more stops. Path results can be optimized either by distance or by cost (for example, travel time). Route options and Order options specify the optimization criteria and the order in which stops are to be visited.

The Configure Network dialog box allows you to specify the inputs that define the network for computing the best path. Properties can be set on the tabs of this dialog box for the Edge, Node, and Turn feature classes. If a resultant path is to be optimized by cost, a tab is available to set the Cost fields. Specifying restrictor features on the Restrictors tab for Edges, Nodes, and Turns can restrict the results.

The output of the best path analysis will be a linear feature class showing the Path solution and, optionally, a point and text feature class used for Stop symbology. The results of the solution will be dynamic so that changes to stops, restrictions, blockages, and so on, are reflected in a change to the calculated paths.

48-1


The Best Path Workflow This section presents the procedural steps for using the Best Path command.


2. Select Transportation > Routing Analysis > Best Path.

3. In the Network box, click Properties to select the inputs to define the network on the Configure Network dialog box.

48-2


4. Set the properties for the Edges, Nodes, and Turns feature classes on the dialog box tabs. A tab is available to set the Costs inputs. In order to restrict the results of the Path pipe, specify restrictor features on the Restrictors tab.


5. Click OK.

6. Select a Stops feature class and Stop set or a Stop set query from the Stops portion of the Best Path dialog box.

Note: See the “Working with the Stop Properties Control” chapter for a detailed discussion on how to use this dialog box. For a discussion on the differences between Stop feature classes and Stop Set queries, see the “Working with the Stop Manager Command” chapter.

7. On the Best Path dialog box, optionally set the Order options to override the defaults. The four order options are Best Order, Start Fixed, End Fixed, and Return to Start.

• The Best Order option tells the software to disregard the assigned order of the Stops and to optimize the order of the Stops so as to minimize either cost or distance.

• The Start Fixed option slightly overrides the Best Order option to ensure that the first Stop in the path is the first Stop in the Stop Set.

48-3


48-4

• The End Fixed option slightly overrides the Best Order option to ensure that the last Stop in the path is the last Stop in the Stop Set.

• The Return to Start option means that the path created will both start and stop at the same Stop.

8. Optionally set the Route options to override the defaults. The seven route options are Minimize Distance/Cost, Use OneWays, Use Blockages, Use Restrictors, Disable U-turns, Honor turn restrictions at stops, and Include last-stop costs.

• The Minimize Distance/Cost option allows you to select whether the path created minimizes the length of the path or the “cost” of the path. The cost is the sum of the values in the fields designated in the Configure Network dialog box as cost fields for Edges and, optionally, Nodes and/or Turns. These cost fields can be used to store any numeric value, such as time, monetary expense, or safety indices.

• The Use OneWays, Use Blockages, and Use Restrictors options allow you to select whether to use or ignore the definitions set by you in the Configure Network dialog box for OneWays, Blockages, and Restrictors. When routing an emergency vehicle, for example, it might be useful to not Use OneWays; or when routing a regular-sized vehicle, it might be useful not to Use Restrictors developed to handle the limitations of 18-wheel vehicles.

• The Disable U-turns option allows you to globally disable U-turns when calculating paths. This is particularly useful when routing large vehicles that cannot easily make U-Turns.

• The Honor turn restrictions at stops option allows turn restrictions defined in the selected turn table to be honored at stops. If the Disable U turns option is selected along with Honor turn restrictions at stops, then U-turns are not allowed at stops. The Honor turn restrictions at stops option is available when the Best Order setting is not selected. By default, the turn restrictions are not honored at stops while computing the path result.

• The Include last-stop costs option tells the software whether to include the cost associated with the last stop in a path in the accumulated cost for that path. If this option is not picked, the accumulated cost will indicate the cost to get to the last path, but not any cost associated with that last stop.

9. Provide a Query name if you do not like the default, and, optionally provide a Description.

10. Choose whether to display the results in a map window, and choose the specific map window if different from the current one.

11. Click Properties in the Display results in map window group box to specify the Path Type and its symbology on the Output Style Properties dialog box. The two Type options are Individual Segments and Stop To Stop. An Individual Segments path


reflects each of the underlying edges. The Stop To Stop paths aggregate the individual segments into path segments that run from one stop to another.

To set the Path symbology, pick the Style button in the Path group. Optionally, you can display Stops by picking the Stops option and can set the Stops display options by using the Style and Label buttons in the Stops group.

12. Click OK.

13. On the Best Path dialog box, choose whether to Display the results in data window, and choose the specific data window from the drop-down list.

Note: The Query name, Description, Display results in map window and Display results in data window boxes are enabled only when valid input is given in the Configure Network dialog box and when a valid stop feature class has been selected.

14. Click OK to initiate the Best Path calculation

15. After reviewing the result, you can change the order and route options by editing the query. Do this by first selecting Analysis > Queries from the GeoMedia Professional menu bar.

48-5



16. Select the query generated by the Best Path command, and then click Edit.


48-6


.

17. Edit the Query name, the Description, the Order options, and the Route options. When finished click OK. This will alter the results of the query according to your new input.

18. If you selected Use Restrictors, click Edit to edit the restrictors linked with the analysis and to modify the restrictors independently on each query.

The Edit Restrictors dialog box is displayed.

48-7


19. In the Edit restrictors for drop-down list, select Edges, Nodes, or Turns if all three Edge/Node/Turn restrictors were defined in the analysis. (For example, if only Edge restrictors are set, then the drop-down list will have only Edges.

The selected restrictors are displayed in the associated list box.

20. Click Properties to display the Functional Attributes dialog box, which allows you to edit the name or expression of the restrictor. (Note: The expression must result in a Boolean value.)

OR

Click Delete to delete the restrictor and to permanently exclude it from analysis. 21. Click Close to dismiss the dialog box.

48-8

Working with the Find Closest Stops Command

The Find Closest Stops command allows you to find the closest N destination stops to a set of origin stops. This is useful for a number of tasks, including making assignments or for emergency pre-planning, such as finding the two closest hospitals to each sporting arena in a particular jurisdiction. Path results can be optimized either by distance or by cost (for example, travel time). Path solution options and Route options specify the optimization criteria and the number of paths to be created.

The Configure Network dialog box allows you to specify the inputs that define the network for computing the find closest stops solutions. Properties can be set on the tabs of this dialog box for the Edge, Node, and Turn feature classes. If a resultant path is to be optimized by cost, a tab is available to set the Cost fields. Specifying restrictor features on the Restrictors tab for Edges, Nodes, and Turns can restrict the results.

The output of the find-closest-stops analysis (also known as proximity analysis) will be a linear feature class showing the Path solution and, optionally, a point and text feature class used for Stop symbology. The results of the solution will be dynamic so that changes to stops, restrictions, blockages, and so on, are reflected in a change to the calculated paths, as shown in the following example:

49-1


The Find Closest Stops Workflow This section presents the procedural steps for using Find Closest Stops.


2. Select Transportation > Routing Analysis > Find Closest Stops.

The Find Closest Stops dialog box is displayed.

3. Click Properties in the Network box to select the inputs to define the network on the Configure Network dialog box.

49-2




5. Click OK.

The selected Edge, Node, and Turn features are displayed on the Find Closest Stops dialog box in the Edges, Nodes, and Turns fields.

6. Select a Stops feature class and Stop set or a Stop set query from the Origin stops portion of the dialog box.


7. Repeat Step 6 for the Destination stops. These stops define the set of end points that will be selected from in this analysis.

8. Select Closest destination stop (the default), All destination stops, or Number of destinations (enter the number of destination paths in the associated text box if this option is chosen) from the Path solution options group.

49-3


49-4

• The Closest destination stop option generates a path solution from each stop in the origin stop set to the single closest destination to each origin stop.

• The All destination stops option generates a path solution from each stop in the origin stop set to each and every stop in the destination stop set.

• The Number of Destinations option allows you to specify a number of destinations to generate a path solution from each stop in the origin stop set to the specified number of closest stops in the destination stop set. For example if you use a value of 2, it will find the Paths between each Origin Stop and the closest Destination Stop to each, as well as the Paths between each Origin Stop and the second closest Destination Stop.

9. Optionally set the Route options to override the defaults. The six route options are Minimize Distance/Cost, Use OneWays, Use Blockages, Use Restrictors, Disable U-turns, and Include last-stop costs.

10. The Minimize Distance/Cost option allows you to select whether the path created minimizes the length of the path or the “cost” of the path. The cost is the sum of the values in fields designated in the Configure Network dialog box as cost fields for Edges and, optionally, Nodes and/or Turns. These cost fields can be used to store any numeric value, such as time, monetary expense, or safety indices.

11. The Use OneWays, Use Blockages, and Use Restrictors options allow you to select whether to use or ignore the definitions set by the user in the Configure Network dialog box for OneWays, Blockages, and Restrictors. When routing an emergency vehicle, for example, it might be useful to not Use OneWays, or when routing a regular-sized vehicle, it might be useful not to Use Restrictors developed to handle the limitations of 18-wheel vehicles.

12. The Disable U-turns option allows you to globally disable U-turns when calculating paths. This is particularly useful when routing large vehicles that cannot easily make U-Turns. This option does not require that a turn table be defined.

13. The Include last-stop costs option tells the software whether to include the cost associated with the last stop in a path in the accumulated cost for that path. If this option is not picked, the accumulated cost will indicate the cost to get to the last path, but not any cost associated with that last stop.

14. Accept or override the default query name specified in the Query name field, and assign an optional description in the Description field.

15. To display the results in a map window, verify that the Display results in map window is checked. Then accept the default, or select or key in a map window name.

16. Click Properties in the Display results in map window group box to specify the Path Type and its symbology on the Output Style Properties dialog box. The two Type options are Individual Segments and Stop To Stop. An Individual Segments path


reflects each of the underlying edges. The Stop To Stop paths aggregate the individual segments into path segments that run from one stop to another.

17. To set the Path symbology, click Style in the Path group. Optionally, you can display and label Stops by clicking the Stops check box and can set the Stops display options by checking the Style and Label buttons in the Stops group.

18. To display the results in a data window, verify that the Display results in data window is checked. Then accept the default, or select or key in a data window name.

Note: The Query name, Description, Display results in map window and Display results in data window fields are enabled only when valid input is given in the Configure Network dialog box and when valid stop feature classes have been selected.

19. Click OK to initiate the Find Closest Stops calculation.

20. After reviewing the result, you can change the path solution and route options by editing the query. Do this by first selecting Analysis > Queries from the GeoMedia Professional menu bar.

49-5



21. Select the query generated by the Find Closest Stops command, and then click Edit.


22. Edit the Query name, the Description, the Path solution options, and the Route options. When finished click OK. This will alter the results of the query according to your new input.


49-6



24. In the Edit restrictors for drop-down list, select Edges, Nodes, or Turns if all three Edge/Node/Turn restrictors were defined in the analysis. (For example, if only Edge restrictors are set, then the drop-down list will have only Edges.)

The Selected restrictors are displayed in the associated list box.


OR


49-7


49-8

Working with the Network Coverage Command

The Network Coverage command allows you to find all paths that can be traversed from a set of origin Stops within a given user cost or distance. This is useful, for example, for planning what locations can be reached by emergency response teams in a given time from a given location. Path results can be optimized either by distance or by cost (for example, travel time). Coverage options and Route options specify the optimization criteria and the number of bands of solutions to be created (for example, 3 bands at 5 minutes would generate 5, 10, and 15 minute solutions).

The Configure Network dialog box allows you to specify the inputs that define the network for computing the network coverage solutions. Properties can be set on the tabs of this dialog box for the Edge, Node, and Turn feature classes. If a resultant path is to be optimized by cost, a tab is available to set the Cost fields. Specifying restrictor features on the Restrictors tab for Edges, Nodes, and Turns can restrict the results.

The output of the network coverage analysis will be a thematic linear feature class showing the Path solution and, optionally, a point and text feature class used for Stop symbology. The results of the solution will be dynamic so that changes to stops, restrictions, blockages, and so on, are reflected in a change to the calculated paths.

50-1


The Network Coverage Command Workflow This section presents the procedural steps for using the Network Coverage command.


2. Select Transportation > Routing Analysis > Network Coverage.

The Network Coverage dialog box is displayed.

3. Click Properties in the Network box to set the properties for the network on the Configure Network dialog box.



5. Click OK.

The Configure Network dialog box is dismissed.

6. Select a Stops feature class and Stop set or a Stop set query from the Stops portion of the dialog box.

50-2


50-3


7. Enter values for the Number of bands and Band interval. For instance if you select three bands with an interval of 500, a thematic feature class will be created showing paths up to 500 units from the origin, 1000 units from the origin, and 1500 units from the origin.

8. Select the unit of measure for your interval key-in from the Interval unit drop-down list if you are optimizing distance (see next step). If you are optimizing by cost, then you will be shown the cost units set in the Configure Network dialog box. All costs (Edge, Node, Turn, and Stop) are assumed to share these same units.

9. Optionally set the Route options to override the defaults. The five route options are Minimize Distance/Cost, Use OneWays, Use Blockages, Use Restrictors, and Disable U-turns.

• The Minimize Distance/Cost option allows you to select whether the path created minimizes the length of the path or the “cost” of the path. The cost is the sum of the values in fields designated in the Configure Network dialog box as cost fields for Edges and, optionally, Nodes, and/or Turns. These cost fields can be used to store any numeric value, such as time, monetary expense, safety indices, etc.

• The Use OneWays, Use Blockages, and Use Restrictors options allow the user to select whether to use or ignore the definitions set by the user in the Configure Network dialog box for OneWays, Blockages and Restrictors. When routing an emergency vehicle, for example, it might be useful to not Use OneWays, or when routing a regular-sized vehicle it might be useful not to Use Restrictors developed to handle the limitations of 18-wheel vehicles.

• The Disable U-turns option allows the user to globally disable U-turns when calculating paths. This is particularly useful when routing large vehicles that cannot easily make U-Turns. This option does not require a turn table to be defined.

10. Accept or override the default query name specified in the Query name field, and assign an optional description.

11. To display the results in a map window, check Display results in map window. Then, accept the default, or select or key-in a map window name. Click Properties to change the coverage and/or the stops style on the Output Style Properties dialog box.


12. To change the coverage styles, click Largest solution style and Smallest solution style. These set the styles for the first and last coverage band. Intermediate bands have a style that is interpolated between these two styles.

13. Check Stops if you want the origin Stops to be displayed and labeled. Click the Style and Label buttons to change the symbology options.

14. To display the results in a data window, check Display results data window. Then, accept the default, or select or key-in a map window name.

Note: The Query name, Description, Display results in map window and Display results in data window fields are enabled only when valid input is given in the Configure Network dialog box and when a valid stop feature class has been selected.

15. Click OK to initiate the Network Coverage calculation.

16. After reviewing the result, you can change the coverage and route options by editing the query. Do this by first selecting Analysis > Queries from the GeoMedia Professional menu bar.


50-4


17. Select the query generated by the Network Coverage command, and then click Edit.

The Edit Query dialog box is displayed.

50-5


18. Edit the Query name, the Description, the Coverage options, and the Route options. When finished click OK. This will alter the results of the query according to your new input.



50-6


20. In the Edit restrictors for drop-down list, select Edges, Nodes, or Turns if all three Edge/Node/Turn restrictors were defined in the analysis. (For example, if only Edge restrictors are set, then the drop-down list will have only Edges.

The Selected restrictors are displayed in the associated list box.


OR


50-7


50-8

Working with the Generate Path Directions Command

The Generate Path Directions command allows you to generate and display descriptive direction information for best path or find closest results. The command internally uses Direction Service to generate descriptive direction information. You should specify a feature class or query of best path or find closest result and a configuration file that is delivered with GeoMedia Transportation. The command also allows you to specify the feature class’ path descriptive fields, the accumulated length and its unit, and the accumulated cost and its unit from the stop and to stop fields. You can also specify the precision that is used to display accumulated length and accumulated cost.

The Generate Path Directions Command Workflow 1. Create a connection to a warehouse. 2. Select the Generate Path Directions command.

3. Select a feature class from the Generate Directions for combo box. 4. Click Properties. The Path Properties dialog box is displayed

51-1


.

• Select a primary descriptor field in the Primary combo box. • Optional: Select a Secondary/Tertiary/Quaternary descriptor field. • Select an Accumulated length field from the End Measure combo drop-down list. • Select an Accumulated length unit in the Unit drop-down list next to the

Accumulated length drop-down list.

• Select an Accumulated cost field in the Accumulated cost drop-down list. • Select an Accumulated cost unit in the Unit drop-down list next to the

Accumulated cost drop-down list.

• Select a From stop field in the From stop drop-down list. • Select a To stop field in the To stop drop-down list. • Click OK to process inputs. • Click Cancel to dismiss the dialog box.

5. Click Browse on the Path Connections dialog box, and then select a configuration file from the open file dialog box.

6. On the Path Connections dialog box, select a display precision in the Precision combo box.

7. Click OK to process the inputs, or click Cancel to exit the command without processing.

If you clicked OK, the Output Path Directions dialog box is displayed.

51-2

Working with the Generate Path Directions Command

8. Click Save As to save the directions as a text file, click Print to print the directions, or click Close to exit the command without saving/printing the directions.

51-3


51-4

Working with the Configure Network Dialog Box

This section provides an overview of the Configure Network dialog box, which provides a graphic user interface for entering Network properties in GeoMedia Transportation Manager. Use this dialog box in the Easy Path, Best Path, Find Closest Stops, and Network Coverage commands to input the Network properties. This dialog box provides a standard way for entering this information.

The Configure Network Dialog Box Workflow This section presents the procedural steps for using Configure Network dialog box.

1. Click the Edge tab.

The Edge Properties group is displayed.

2. In the Select edge features field, select an Edge feature class. This is the linear feature

class along which the networking analysis will be conducted.

52-1


52-2

3. In the EdgeID, FromNodeID, and ToNodeID field fields, select the names of the topology fields for this Edge class. For information on how to create and populate these fields, see the “Working with the Build Network Command” chapter.

4. Optional: In the OneWay field box, select the field name of the OneWay field. For information on how to populate this field see the “Working with the OneWay Editor Command” chapter.

5. Optional: In the Blockage field box, select the field name of the Blockage field. For information on how to populate this field, see the “Working with the Blockage Editor Command” chapter.

6. In the Length options group you have three choices:

• The first is to select Use Geometry and have the system calculate lengths based on geometry lengths of the Edges. This method has the slowest processing time due to the extra calculations involved.

• The second option is to choose Select length field and pick a single field containing length values.

• The third option is to choose Select measure fields and pick both a Start measure and an End measure field. The difference between the values in these two fields will define the length of the Edge.

7. If you picked either the Select length field or the Select measure fields option, then also pick the length unit of measure from the Length unit drop-down list. If you picked the Use Geometry option, then the distance units set for this workspace are displayed in a read-only field.

8. Click the Node tab.

The Node Properties group is displayed.


9. Optional: Select the Use nodes option. If this step is not chosen as an option, skip to

Step 13.

10. In the Select node features field, select a Node feature class. This is the point feature class that defines the intersections in our network.

11. In the NodeID field field, select the name of the NodeID field for this Node class. For information on how to create and populate this field see the “Working with the Build Network Command” chapter.

12. Optional: In the Blocked field box, select the name of the Blocked field. This contains true or false values as to whether each Node is blocked or not.

13. Click the Turns tab.

The Turn Properties group is displayed.

52-3


14. Optional: Select the Use turns option. If this step is not chosen as an option, skip to

Step 18.

15. In the Select turn features field, select a Turn feature class. This is the non-graphic feature class that defines the turn costs and restrictions within our network.

16. In the FromNodeID and ToNodeID field fields, select the names of the Edge fields for this Turn class. For information on how to create and populate these fields see the “Working with the Build Network Command” chapter.

17. Optional: In the Blocked field field, select the name of the Blocked field. This contains true or false values as to whether each Turn option is blocked or not. For information on how to edit these records, see the “Working with the Turn Editor Command” chapter.

18. Click the Costs tab.

The Cost Properties group is displayed.

52-4


19. Optional: Select the Use edge costs option. If this step is not chosen as an option, skip

to Step 22.

20. Pick Symmetrical if the edge costs are the same in both travel directions, and Asymmetrical if they are not.

21. If you chose Symmetrical, select the Edge Cost field name from the Edge Cost box. If you chose Asymmetrical, select both the Forward direction (digitizing direction) and Reverse direction field names from the Forward direction and Reverse direction fields.

22. Optional: Select the Use node cost option. If this step is not chosen as an option, skip to Step 24.

23. Select the Node cost field name from the Use node cost field.

24. Optional: Select the Use turn cost option. If this step is not chosen as an option, skip to Step 26.

25. Select the Turn cost field name from the Use turn cost field.

26. If you chose any of the costs options, then also fill out the units of measure for those costs in Unit for all costs field. All costs (Edge, Node, Turn, and Stop) are required to share these same units.

27. Click the Restrictors tab.

The Restrictor Properties group is displayed.

52-5


28. Optional: Select the Edges option. If this step is not chosen as an option, skip to Step

31.

29. In the Select restrictor features field, select an Edge Restrictor feature class. This is the non-graphic feature class that defines the conditions under which travel along certain edges may be restricted. For information on how to create and populate this table see the “Working with the Restrictor Editor Command” chapter.

30. The list box under the Select restrictor features field will show all of the restrictor records from this Edge Restrictor feature class. Check off those you wish to use for this analysis.

31. Optional: Select the Nodes option. If this step is not chosen as an option, skip to Step 34.

32. In the Select restrictor features field, select a Node Restrictor feature class. This is the non-graphic feature class that defines the conditions under which travel past certain nodes may be restricted. For information on how to create and populate this table see the “Working with the Restrictor Editor Command” chapter.

33. The list box under the Select restrictor features field will show all of the restrictor records from this Node Restrictor feature class. Check off those you wish to use for this analysis.

34. Optional: Select the Turns option. If this step is not chosen as an option, skip to Step 37.

35. In the Select restrictor features field, select a Turn Restrictor feature class. This is the non-graphic feature class that defines the conditions under which travel along certain

52-6


52-7

turn options may be restricted. For information on how to create and populate this table see the “Working with the Restrictor Editor Command” chapter.

36. The list box under the Select restrictor features field will show all of the restrictor records from this Turn Restrictor feature class. Check off those you wish to use for this analysis.



52-8

Working with the Stop Properties Control

This section provides an overview of the Stop Properties control, which provides a graphic user interface for entering Stop and Stop set properties in GeoMedia Transportation Manager. For more on the subject of Stops and Stop sets, see the “Working with the Stop Manager Command” chapter.

Use this control in the Best Path, Find Closest Stops, and Network Coverage commands to enter Stop and stop Set properties. This control provides a standard method for entering this information.

The Stop Properties Control Workflow This section presents the procedural steps for selecting Stops and Stop sets and setting their properties.

1. Select a Stops feature class or a Stop set query from the Select stop features drop-down list. This is the source of Stops to be used in this analysis.

If a Stop feature class was selected, the Select stop set drop-down menu will be populated with the Stops sets stored in the selected class. If a Stop set query was selected, the Select stop features Properties button, the Select stop set drop-down list, and the Select stop set Properties button will be disabled. That is because all of these options are preset with a Stop set query, and you can skip the rest of the steps in this chapter.

Note: For a discussion on the differences between Stop feature classes and Stop set queries, see the “Working with the Stop Manager Command” chapter.

53-1


2. Click the Select stop features Properties button to set the properties for the Stop feature classes.

The Stop Properties dialog box is displayed.

Note: Depending on which command you are using, some of the items in this dialog box may be disabled because they do not apply to that command.

3. Click OK to dismiss the Stop Properties dialog box.

4. Select a Stop set from the Select stop set drop-down list. This is the Stop set to be used in this analysis. Leave the Select stop set drop-down list blank if you want all Stops in the feature class to be used in the analysis.

5. In the Select Stop Set portion of the control, the Properties button will be enabled if a Stop set was selected in the previous step; click it to review the selected Stop set properties.

The Stop Set Properties dialog box is displayed.

Note: To view more Stops in the grid, resize the height of the Stop Set Properties dialog box by dragging its border.

53-2

Working with the Stop Properties Control

Note: The Enabled, Name, and Cost columns are shown on the Stop Set Properties dialog only if corresponding Stop feature class properties were defined in Step 2. For example, if the Enabled field is not specified, the Enabled column and the Enable All and Disable All buttons will not be shown. Similarly, if the Order field is not specified, the buttons used to move the Stops up or down will not be available. If the Stop feature class is non-editable, then all the columns are displayed with gray background.

6. To edit an individual Stop, select it by clicking on the gray button to the left side of the row depicting that Stop. That row will be highlighted, and the buttons to the right of the grid will become enabled. Also, that feature will be highlighted in the Map View.

7. Once selected, there are a variety of edits that can be done to the Stop. The Name and Cost values can be edited by clicking and typing in a new value; the Stop can be moved up or down in the sequence by using the , , , and buttons; and the Stop can be enabled or disabled by clicking on the Enabled check box or by using the Enable All or Disable All buttons.

The Cost value is used by the various routing analysis command if the Minimize Cost option is selected. The sequence of the Stops within the grid is used by the Best Path command when the Best Order option is not used or if either the Start Fixed or the End Fixed option is used in that command. Stops that do not have their Enabled box checked will be ignored by the various routing analysis commands.

8. If you want to exit the Stop Set Properties dialog box without saving any of the changes you have made, click the Close button. Otherwise, first click Apply.

The Apply button makes use of the Snap Tolerance value to find the closest edge to each of the Stops in the list. This may take some time to calculate based on the size of the dataset. When completed, the Status, EdgeID, and Edge Position fields will be filled out in the grid.

53-3


53-4

The Status field will indicate the relative success of finding an Edge within the snap tolerance of each Stop. A blank field indicates success. The message “Stop located, multiple edges may be within tolerance” indicates success, but that more than one Edge was found within tolerance. The closest Edge is used in this case. The message “Not located, no edges within tolerance” indicates no Edge was located. Stops with this status will be ignored by any of the routing analysis commands.

The EdgeID and EdgePosition fields indicate which Edge a Stop was snapped to and the relative position (0 to 1) of that Stop along that Edge.

Note: The EdgeID and EdgePosition values calculated here are static values. That means that if your network changes, you may need to update these values to reflect those changes. You can update these values by revisiting the Stop Set Properties dialog box and by using the Apply button. It is possible to have the EdgeID and EdgePosition values calculated dynamically using the Output Stop Set as Query option within the Stop Manager command (see the “Working with the Stop Manager Command” chapter.

9. Click Close to dismiss the Stop Set Properties dialog box. If you have not first selected the Apply button, an informational message will appear, letting you know that if you exit the dialog box now, none of your changes will be saved.

At the bottom of the control there are read-only fields that display the tolerance value and units set in the Stop Set Properties dialog box.

Note: You can edit these values only in the following two cases: a Stop set was not selected or EdgeID and EdgePos fields were not specified for the selected feature class.

54-1

Working with the Routing Data Maintenance Workflows

The purpose of this chapter is to outline the basic steps needed to build and maintain a routing network. Two approaches are presented. The first is a dynamic routing network approach based on queries that are automatically updated anytime the underlying linear geometry is changed. The second is a table-based approach that assumes the network components are stored as tables. The dynamic approach makes data maintenance very simple but has some limits on how much you can fine tune the network characteristics and is more memory intensive. The table-based approach allows you complete flexibility in fine tuning network characteristics but places a heavier burden on you to maintain the network when there are changes to network geometry. Lastly, some steps for validating your routing network are presented so as to ensure accurate routing analysis results.

The Dynamic Routing Data Maintenance Workflow This workflow uses the Build Network command to create dynamic queries that represent the three basic network components: Edges, Nodes, and Turns. Because these queries are dynamic, the network topology is automatically updated anytime the underlying linear feature class is changed. This is very helpful for dynamic data sets with geometry that changes fairly often. However, this method does not give you the flexibility to set individualized settings for turns or nodes after the initial network build (as the Node and Turn queries are not editable). So this methodology is excellent for a network that may have frequent geometry changes but whose turn characteristics are predictable.

1. Locate the source linear feature class for your network. This is the linear feature class that geometrically defines your network.

2. Add columns as desired to your source linear feature class for OneWays (long integer), Blockages (long integer), or Restrictor source fields using the Feature Class Definition command.

3. Locate, if available, the source Node attribute feature class for your network.

4. Use the Build Network command to create Edge, Node, and Turn queries. Set the options to create default turn costs and/or blockages. If you have a source Node attribute feature class, select the option to copy over any fields that you would like in your output Node query. For more information on this see the “Working with the Build Network Command” chapter.

5. Set OneWays and Blockage values as desired on individual Edges. This can be done using either the Edge query or the source linear feature class. For more information on


54-2

this see the “Working with the OneWay Editor Command” and “Working with the Blockage Editor Command” chapters.

6. Develop Restrictors for Edges, Nodes, and Turns as desired. For more information on this see the “Working with the Restrictor Editor Command” chapter.

7. Create Stops as needed for any routing analyses. Use the results of the Output Stop Set as Query option within the Stop Manager command when selecting Stops within any routing analysis command. It is important to use this query as opposed to the Stop table itself because the EdgeID and EdgePosition values for the stops are calculated dynamically within this query; whereas the EdgeID and EdgePosition values in the Stop table are static. For more information see the “Working with the Stop Manager Command” chapter.

The best part of this workflow is that now you are done. If you make changes to the geometry in your input linear feature class, your output network components will be automatically updated to reflect those changes with no interference needed on your part.

Manual Routing Data Maintenance – The Initial Network Creation Workflow

This is the first part of a two-part workflow for creating and maintaining a table-based routing network. This section is the one-time task of initial network creation. The next section covers the tasks needed to update the network to reflect changes in the network geometry that occur over time. Together these two workflows create an alternative to the Dynamic Routing Data Maintenance Workflow described previously. These two workflows require a little more work but offer more flexibility in defining your network.

1. Locate the source linear feature class for your network. This is the linear feature class that geometrically defines your network.

2. Locate, if available, the source Node attribute feature class for your network.

3. Use the Build Network command to create Edge, Node, and Turn queries. Set the options to create default turn costs and/or blockages. If you have a source Node attribute feature class, select the option to copy over any fields that you would like in your output Node query. For more information on this see the “Working with the Build Network Command” chapter.

4. Use the Output to Feature Class command to save your Edge, Node, and Turn query classes to tables in a read/write connection.

5. Delete the Edge, Node, and Turn queries that were created using the Build Network command.

6. Add columns as desired to your Edge class for Length (double), OneWays (long integer), Blockages (long integer), or Restrictor source fields using the Feature Class Definition command.


54-3

7. Set OneWays and Blockage values as desired on individual Edges. For more information on this see the “Working with the OneWay Editor Command” and “Working with the Blockage Editor Command” chapter.

8. Use the Update Attributes command to populate the Length field of the Edge feature class.

9. Add columns as desired to the Node and Turn feature classes for source Restrictor fields, and so on, using the Feature Class Definition command.

10. Set individual Node costs/blockages to suit using GeoMedia commands such as Select Set Properties or Data Window.

11. Use the Turn Editor to set individual Turn characteristics to suit. For more on this see the “Working with the Turn Editor Command” chapter.

12. Develop Restrictors for Edges, Nodes, and Turns as desired. For more information on this see the “Working with the Restrictor Editor Command” chapter.

13. Create Stops as needed for your routing analyses. For more information on this see the “Working with the Stop Manager Command” chapter.

Manual Routing Data Maintenance – The Network Update Workflow

This is the second part of the table-based routing network workflow. The first part created the initial network and made it ready for analysis. This part is what needs to be done anytime there are changes to the network geometry. This workflow updates the fields that define the network topology to ensure correct routing analysis results. There are several steps involved, but the basic approach can be summarized as follows:

- Use the Build Network command to calculate new EdgeID, FromNodeID, and ToNodeID values for the Edges and new NodeID values for the Nodes.

- Replace the old Node feature class with the newly calculated Node query.

- Use the Edge query created by the Build Network command, which contains both new and old EdgeID values, to update the old Turn table. Use the queries FromNodeID and ToNodeID values to ensure the correct directionality of the Edges in the Turn table.

- Update the EdgeID, FromNodeID, and ToNodeID values in your Edge feature class.

- Update any Stops you have using the Stop Manager command.

Because of the possibility of confusion in interpreting these steps, some key words have been italicized.

1. Use the Build Network command, with your existing Edge and Node feature classes as input, to create new Edge and Node query classes. This will create an Edge query class with both new and old network topology fields and will copy from your existing


Node feature class any data you might want to preserve such as costs, blockages, and restrictor source fields. Although your field names may vary, for purposes of this workflow we will say that the old Edge topology fields are named EdgeID, FromNodeID, and ToNodeID and that the new Edge topology fields are named EdgeID1, FromNodeID1, and ToNodeID1. For more information on this see the “Working with the Build Network Command” chapter.

54-4


First, let’s replace the Node table. . .

2. Use the Output to Feature Class command to save your Node query class to a new Node feature class. This is a replacement for the old Node feature class.

3. Delete the old Node feature class using the Feature Class Definition command.

Now, let’s update the Turn table…

4. Use the Feature Class Definition command to add three new fields to the existing Turn feature class: newFromEdgeID (long integer), newToEdgeID (long integer), and Status (text).

54-5


5. Use the ABS function of the Functional Attributes command on the existing Turn

feature class to create two new calculated fields: AbsFromEdgeID and AbsToEdgeID. These will be equal to the absolute values of the FromEdgeID and ToEdgeID fields, respectively. Call the output query from this command Turns2.

54-6


6. Use the Aggregation command using the Turns2 query class from the last step as the

summary class and the Edge query class as the detail class. Pick the Attribute Aggregation option, and select AbsFromEdgeID from Turns2 and the original EdgeID field from the Edge query class for the join fields. Set the Resolution operator to All. Create the following three functional attributes:

- FE_EdgeID = First(Detail.EdgeID1); this is the new Edge ID value for the From Edge.

- FE_FromNodeID = First(Detail.FromNodeID1); this is the new From Node ID value for the From Edge.

- FE_ToNodeID = First(Detail.ToNodeID1); this is the new To Node ID value for the From Edge.

Call the output query from this command Turns3.

54-7


7. Use the Aggregation command using the Turns3 query class from the last step as the

summary class and the Edge query class as the detail class. Pick the Attribute Aggregation option, and select AbsToEdgeID from Turns3 and the original EdgeID field from the Edge query class for the join fields. Set the Resolution operator to All. Create the following three functional attributes:

- TE_EdgeID = First(Detail.EdgeID1); this is the new Edge ID value for the To Edge.

- TE_FromNodeID = First(Detail.FromNodeID1); this is the new From Node ID value for the To Edge.

54-8


- TE_ToNodeID = First(Detail.ToNodeID1); this is the new To Node ID value for the To Edge.

Call the output query from this command Turns4.

8. Use the Update Attributes command on Turns4 to set the following attribute values. This process may take a while on a large network.

- newFromEdgeID = IF((FE_ToNodeID = TE_FromNodeID OR FE_ToNodeID = TE_ToNodeID) AND (FE_FromNodeID = TE_FromNodeID OR FE_FromNodeID = TE_ToNodeID), (FromEdgeID/AbsFromEdgeID) * FE_EdgeID, IF(FE_ToNodeID = TE_FromNodeID OR FE_ToNodeID = TE_ToNodeID, FE_EdgeID, -1 * FE_EdgeID))

- newToEdgeID = IF((FE_ToNodeID = TE_FromNodeID OR FE_ToNodeID = TE_ToNodeID) AND (FE_FromNodeID = TE_FromNodeID OR FE_FromNodeID = TE_ToNodeID), (ToEdgeID/AbsToEdgeID) * TE_EdgeID, IF(TE_FromNodeID = FE_FromNodeID OR TE_FromNodeID = FE_ToNodeID, TE_EdgeID, -1 * TE_EdgeID))

- Status = IF((FE_ToNodeID = TE_FromNodeID OR FE_ToNodeID = TE_ToNodeID) AND (FE_FromNodeID = TE_FromNodeID OR FE_FromNodeID = TE_ToNodeID), “Ambiguous direction”, “”)

This process derives the directionality of the Edges from the FromNodeID and ToNodeID attribution where possible. In ambiguous cases (such as Edges that begin and end at the same Node), it merely copies the directionality from the existing Turn table and marks these with a message in the Status field. This can be reviewed and edited as needed using the Turn Editor command. For more information on this see the “Working with the Turn Editor Command” chapter.

9. Delete queries Turns2, Turns3, and Turns4.

54-9


10. Use the Feature Class Definition command on the Turn feature class to delete original FromEdgeID and ToEdgeID fields and to rename the newFromEdgeID field to FromEdgeID and rename the newToEdgeID field to ToEdgeID.

Now let’s update the Edge table…

11. Use the Update Attributes command on the new Edge query class to set the old EdgeID, FromNodeID, and ToNodeID values equal to the new EdgeID1, FromNodeID1, and toNodeID1 values that were created by the Build Network command. Also you can update the Length field at the same time. This process may take a while on a large network.

12. Delete the Edge and Node query classes created by the Build Network command.

Finally, let’s update the Stop table…

13. Use the Stop Manager command to recalculate Stop locations. For more information on this see the “Working with the Stop Manager Command” chapter.

It is worth noting that automating the workflow just presented is currently planned for a future version of GeoMedia Transportation Manager.

The Routing Network Validation Workflow This last workflow in this chapter addresses checks that can be made to find common problems with routing networks. We will do three separate checks: Edge-Node connectivity, unwanted subnetworks, and unwanted disconnected Edges.

1. Check the Edge-Node connectivity using the LRS Validation command. Choose one of the two “With Nodes” options for the LRS Model, and only choose the Geometry sequence/direction problems check. For more information on this see the “Working with the LRS Validation command” chapter.

54-10


2. Review the results of the LRS Validation command. Note that some perfectly valid,

but questionable, situations (for example, cul-de-sacs that tie back in on themselves)

54-11


are located by this command so that you can use your own good judgment to decide if you want to correct them or not.

Next, let’s use the Network Coverage command to see if there are any unwanted subnetworks. Subnetworks are portions of the network that are, perhaps unintentionally, disconnected from the rest of the network. If this happens, the results of your routing analyses may not be accurate.

3. Use the Stop Manager command to create a one-Stop Stop Set. The one Stop in this Set can be anywhere in the network, but it probably makes good sense to pick a stop somewhere towards the middle of the network. For more on this see the “Working with the Stop Manager Command” chapter.

4. Use the Network Coverage command using your routing network and the new Stop

Set you just created. Use one band with a distance that you know to be sufficiently long to easily stretch from your Stop to any point on the network. Do not bother with Turns, OneWays, Blockages, or Restrictors. For more on this see the “Working with the Network Coverage Command” chapter.

54-12


5. Review the results visually to see if the results of the Network Coverage command

completely cover the entire routing network. For a more rigorous check, you can use the Spatial Difference command in GeoMedia to compare the results of the Network Coverage command with your routing network.

54-13


Lastly, let’s use the Aggregation and Attribute Query commands to see if there are any unwanted disconnected Edges. This can happen when there is an intersection to which, for example, four Edges are supposed to be connected, but one of them falls short of the intersection by a small amount. These situations are hard to detect visually, but they can cause errors in routing analysis results. The steps below locate all Nodes to which only one Edge is connected (sometimes called Terminal Nodes). These can be perfectly valid and are common around the perimeter of a routing network. However, by reviewing these one-Edge Nodes, you can catch the most common cases of unwanted disconnected Edges.

6. Use the Aggregation command to count how many Edges touch each Node.

54-14


7. Use the Attribute Query command to find all Nodes with one or fewer Edges

touching them.

8. Visually inspect these one-Edge Nodes to make sure no Edges are disconnected

unintentionally.

54-15


54-16

Working with the LRS-based Routing Restrictions Workflow

The purpose of this chapter is to outline the basic steps needed to develop routing restrictions from LRS-based data. The example we are going to use to illustrate this makes use of attribution on LRS bridge points to restrict routing analyses. In this case we will avoid any edge that contains a bridge with less than the desired maximum weight rating, as one might want to do when routing a heavily loaded vehicle. This example can be extended to any number of cases where the data that you want to base your routing restriction on exists on LRS-based Event data and not on the components of your routing network.

1. Use the Dynamic Segmentation command to place the Event data that contains the fields you want to base your routing restriction on. In this example, we have dynamically segmented bridges onto our network. For more information on this see the “Linear Referencing” chapter in Working with GeoMedia or Working with GeoMedia Professional.

2. Use the Aggregation command to transfer Event data attribution to our routing Edges. In this case we are going to transfer the lowest Maximum Weight rating of any bridge that lies along an Edge to that Edge. For the Spatial Aggregation operator we have picked touch, for the Attribute Aggregation operator we have picked our LRS Key, and for our Resolution operator we have picked First.

55-1


55-2


3. Use the Restrictor Editor to develop an Edge restriction that evaluates to True for Edges that you want to be included in your analysis and False for Edges you want to exclude. In this case we have included Edges with either no bridges or with bridges that have a 50,000 pound or greater Maximum Weight rating. Make sure to use the results of the Aggregation step as the query class to restrict. For more information on this see the “Working with the Restrictor Editor Command” chapter.

4. At this point you are ready to begin your routing analysis. For our example we will run an analysis using Best Path. It is important to pick the results of the Aggregation step for the Edge class, to choose the Restrictor created previously, and to pick the Use

55-3


Restrictors option. For more information on this see the “Working with the Best Path Command” chapter.

55-4


5. The following picture shows the results of our analysis. For clarity, bridges with less than 50,000 pound capacity are shown with an . Note that the Best Path result avoids Edges with these low capacity bridges. One of the more interesting things about this workflow is that if the MaxWeight attribution of one of these bridges is updated, the Best Path solution will automatically be updated to reflect that change.

55-5


55-6

A-1

A. How to Reach Intergraph

Electronic Self-Help Support Intergraph provides several electronic self-help support tools to answer your support questions 24 hours a day, seven days a week. Using any web browser, you can access Security, Government & Infrastructure User Support on the World Wide Web at http://support.intergraph.com.

The Knowledge Base and Technical Notes are available at http://support.intergraph.com/kb.asp.

For additional product information, please visit our product web site at http://www.intergraph.com/sgi/products/

http://support.intergraph.com/kb.asp

http://intergraph.com/products/default.asp

http://intergraph.com/products/default.asp

http://support.intergraph.com


A-2

B-1

B. GeoMedia Transportation Data Structures

This appendix describes the Linear Referencing System (LRS) data structures that are directly supported by the GeoMedia Transportation Suite of products as delivered (GeoMedia, GeoMedia Professional, GeoMedia Transportation Manager, GeoMedia Transportation Analyst, and GeoMedia WebMap Professional).

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. GeoMedia Transportation Manager provides great flexibility in the structuring of both of these data types, as shown below:

Single Level LRS Data Structure Options Event Data Structure Options

• Measure • Measure

• Measure with Internal Markers • Marker Offset

• Measure with External Measure Markers • Coordinate

• Duration • Duration

• Duration with Internal Markers

• Duration with External Measure Markers

Furthermore, GeoMedia Transportation also supports Multilevel LRS. This adds a few more choices and a few more supporting table types. It adds two more LRS options and one more Event Options:

Additional Multilevel LRS Options Additional Multilevel LRS Event Options

• Measure with External Datum Markers • Datum Measure

• Duration with External Datum Markers

Multilevel LRS also adds four supporting table types:

Multilevel LRS Supporting Tables

• Linear Datum – This is the table that holds the Multilevel LRS together. All segments are tied to this table.

• Geometry – These are the tables that hold the geometric representations for the Multilevel LRS.

• LRM to Datum Cross Reference – These are the tables that define the many-to-many relationship between LRM tables and the Linear Datum.


Multilevel LRS Supporting Tables

• Geometry to Datum Cross Reference – These are the tables that define the many to many relationship between Geometry tables and the Linear Datum.

For much more information on Multilevel LRS, see the “Introduction to Linear Referencing” chapter. Note that all of the field names used in the subsections to follow are representative only. You are free to name the fields as you please.

Single Level LRS Data Structures An LRS data structure is typically made up of a number of geometric segments that together define the entire LRS. All but the two External Marker options, described in the following subsections, consist only of a table describing those segments. The External Marker options have an additional table that describes marker points.

B-2

GeoMedia Transportation LRS Data Structures

Option 1 – Measure The segments in this option are defined by a set of up to four LRS keys to name the route, a start and an end measure value, and geometry.

EndMeasure

BeginMeasure

Direction of SegmentDirection of Segment

LRS Feature Class

Field

Sample Description

PrimaryKey US The LRS key fields identify the "route" that this segment of the LRS belongs to. This identification can be done with anywhere from 1 to 4 fields within the LRS feature class. These fields are the same fields the event features will use to identify the "route". In the sample shown PrimaryKey identifies the roadway system, SecondaryKey contains the route number, TertiaryKey identifies whether the segment is part of a spur, and QuatenaryKey identifies whether this segment is part of an alternative route. All together the route name is "US6SA".

SecondaryKey 6 This is the 2nd key field that can be used to identify the "route" that this segment of the LRS belongs to. Its use is optional.

TertiaryKey S This is the 3rd key field that can be used to identify the "route" that this segment of the LRS belongs to. Its use is optional.

QuatenaryKey A This is the 4th key field that can be used to identify the "route" that this segment of the LRS belongs to. Its use is optional.

BeginMeasure 12.3 This is the measurement value for the beginning position of this feature.

EndMeasure 18.2 This is the measurement value for the ending position of this feature.

Geometry blob This field contains the linear geometry that describes the linear segment geometrically.

Geometry Reversed

True This Boolean (True/False) field declares whether the software should treat this linear feature as is (False) or as if its digitizing direction were reversed and its beginning were its end and vice-versa (True). The default value should be set to False.

RegionID ORA This text field contains an identifier as to which region a particular segment resides in. It is used to subdivide an LRS into more manageable subsets. Its use is optional. The “ORA” in the sample shown is an ID code for “Orange County”.

B-3


Option 2 – Measure with Internal Markers The segments in this option are defined by a set of up to four LRS keys to name the route, a start and an end measure value, a Begin Marker name, an optional End Marker Name, and geometry. The markers allow this structure to be used with event data using the Marker Offset option.

EndMarker

BeginMarker EndMeasure

BeginMeasure


LRS Feature Class

Field Sample Description

PrimaryKey US The LRS key fields identify the "route" that this segment of the LRS belongs to. This identification can be done with anywhere from 1 to 4 fields within the LRS feature class. These fields are the same fields the event features will use to identify the "route". In the sample shown, PrimaryKey identifies the roadway system, SecondaryKey contains the route number, TertiaryKey identifies whether the segment is part of a spur, and QuatenaryKey identifies whether this segment is part of an alternative route. All together the route name is "US6SA".






BeginMarker M45 This field stores a name for the beginning position of this feature.

EndMarker M46 This field stores a name for the ending position of this feature. Its use is optional.


Geometry Reversed


B-4


LRS Feature Class



B-5


Option 3 – Measure with External Measure Markers The segments in this option are defined by a set of up to four LRS keys to name the route, a start and an end measure value, and geometry. This option also requires markers that are defined by up to four LRS keys, a marker name, and a measure value. The markers allow this structure to be used with event data using the Marker Offset option.

Marker

Marker EndMeasure

BeginMeasure


LRS Feature Class


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 external markers and 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".







Geometry Reversed



B-6


Marker Feature Class


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 LRS features used 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".




MarkerName M34 This is the identifying name of the marker.

MarkerMeasure 17.5 This is the measurement value at the marker.

B-7


Option 4 – Duration The segments in this option are defined by a set of up to four LRS keys to name the route, a start measure value, a duration (length) value, and geometry.


BeginMeasure

Duration

LRS Feature Class







Duration 5.9 This is distance value from the beginning position to the ending position of this feature.


Geometry Reversed



B-8


Option 5 – Duration with Internal Markers The segments in this option are defined by a set of up to four LRS keys to name the route, a start measure value, a duration (length) value, a Begin Marker name, an optional End Marker Name, and geometry. The markers allow this structure to be used with event data using the Marker Offset option.

BeginMeasure

Duration

EndMarker

BeginMarker


LRS Feature Class








BeginMarker M45 This field stores a name for the beginning position of this feature.

EndMarker M46 This field stores a name for the ending position of this feature. Its use is optional.


B-9


LRS Feature Class


Geometry Reversed

True This Boolean (True/False) field declares whether the software should treat this linear feature as if (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.


B-10


Option 6 – Duration with External Measure Markers The segments in this option are defined by a set of up to four LRS keys to name the route, a start measure value, a duration (length) value, and geometry. This option also requires markers that are defined by up to four LRS keys, a marker name, and a measure value. The markers allow this structure to be used with event data using the Marker Offset option.

BeginMeasure

Duration

Marker

Marker


LRS Feature Class


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 external markers and 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".






Geometry Blob This field contains the linear geometry that describes the linear segment geometrically.

Geometry Reversed

True This Boolean (True/False) field declares whether the software should treat this linear feature as if (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.

B-11


LRS Feature Class


RegionID ORA This text field contains an identifier as to which region a particular segment resides in. It is used to subdivide a LRS into more manageable subsets. Its use is optional. The “ORA” in the sample shown is an ID code for “Orange County”.



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 LRS features used 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".





MarkerMeasure 17.5 This is the measurement value at the marker.

B-12


Additional Multilevel LRS Data Structures In a Multilevel LRS, the six preceding options are six of the eight valid LRM options. The only difference is that with a Multilevel LRS, there is no Geometry field on an LRM table. These two additional LRM options come out of the option that Multilevel LRS gives you to define External Markers by a measure relative to the Linear Datum. These two options are identical to Option 3 – Measure with External Measure Markers, and Option 6 – Duration with External Measure Markers, except for the format of the External Marker table. The Linear Datum-based external Marker table has the following format:



DatumID 4567 The DatumID field identifies the linear datum segment that this marker lies upon.


MarkerMeasure 17.5 This is the linear datum-based measurement value at the marker.

Note that a Multilevel LRS may have multiple LRM tables, one for each LRM represented.

B-13


Event Data Structures Note that these structures have no geometry. The whole purpose of the dynamic segmentation process is to combine the LRS data structure and the Event data structure to create a new geographic feature. Note that all of the field names used in the subsections to follow are representative only. You are free to name the fields as you please.

B-14


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






BeginMeasure 14.4 This is the measurement value for the beginning position of this event. This field is required for both point and linear events.

EndMeasure 16.2 This is the measurement value for the ending position of this event. This field is used for linear events only.

B-15


Option 2 – Marker Offset The events in this option are defined by a set of up to four LRS keys to name the route, a begin marker name and an offset value, and for linear events only, an end marker name and offset value.

Event Feature Class






BeginMarker M34 This is the name of the marker from which the beginning point of the event is measured. This field is required for both point and linear events.

BeginOffset 0.6 This is distance value from the Begin Marker to the beginning position of this event. This field is required for both point and linear events.

EndMarker M35 This is the name of the marker from which the ending point of the event is measured. This field is used for linear events only.

EndOffset 0.4 This is distance value from the End Marker to the ending position of this event. This field is used for linear events only.

B-16


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






BeginX 2546234.2 This is the X or Longitude coordinate for the beginning position of this event. This field is required for both point and linear events.

BeginY 753124.4 This is the Y or Latitude coordinate for the beginning position of this event. This field is required for both point and linear events.

EndX 2584123 This is the X or Longitude coordinate for the ending position of this event. This field is used for linear events only.

EndY 745654.6 This is the Y or Latitude coordinate for the ending position of this event. This field is used for linear events only.

B-17


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






BeginMeasure 14.4 This is the measurement value for the beginning position of this event.

Duration 1.8 This is distance value from the beginning position to the ending position of this event. Note: the Duration option is for linear events only.

B-18


Additional Multilevel LRS Event Structures In a Multilevel LRS, there is an additional Event structure type: Datum Measure. Instead of using an identifying LRM segment and an LRM-based measurement value, this option uses a Datum segment and a datum-based measurement.

B-19


Option 5 – Datum 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


DatumID 4567 The DatumID field identifies the linear datum segment that this Event lies upon.

BeginMeasure 14.4 This is the linear datum-based measurement value for the beginning position of this event. This field is required for both point and linear events.

EndMeasure 16.2 This is the linear datum-based measurement value for the ending position of this event. This field is used for linear events only.

B-20


Multilevel LRS Supporting Tables In a Multilevel LRS, there are four supporting table types. These typically are built and maintained by the GeoMedia Transportation Manager software. Each of these tables are described below.

Linear Datum Table The Linear Datum table is where the base road naming and measurement system resides. Since the naming convention and the measurement system of this LRS Datum layer is not directly used by the average end-user, a computer generated DatumID is used for the segment “names”. This is the table that holds the Multilevel LRS together. All LRM and Geometry segments are tied to this table via cross reference tables. There is only one of Linear Datum table per Multilevel LRS. The software never deletes records from this table. It only makes additions.

Linear Datum Table


DatumID 4567 This autonumber or sequence field uniquely identifies a linear datum segment.

DatumLength 19.6 This is the length of the linear datum segment.


Geometry Tables These are the tables that hold the geometric representations for the Multilevel LRS. There will be one table for each geometrical representation within the Multilevel LRS.

Geometry Tables


GeometryID 1235 This autonumber or sequence field uniquely identifies a geometry segment.

BeginMeasure 0 This is the starting measure of a geometry segment. Typically the value of this field is 0.

EndMeasure 19.6 This is the ending measure of a geometry segment. Typically the value of this field is the geometric length of the segment.

RegionID ORA This text field contains an identifier as to which region a particular segment resides in. It is used to subdivide a LRS into more manageable subsets. Its use is optional. The “ORA” in the sample shown is an ID code for “Orange County”.

B-21


LRM to Datum Cross Reference Tables These are the tables that define the many-to-many relationship between LRM tables and the Linear Datum. There will be one of these tables for each LRM used in the Multilevel LRS.

LRM to Datum Cross Reference Tables


ID 7592 This autonumber or sequence field uniquely identifies a record in this table.

LRMID 98774 This is the unique identifier for the LRM segment being cross-referenced.

LRMBegin Measure

56.2 This the beginning measure for the portion of the LRM segment being cross referenced.

LRMEnd Measure

64.3 This the ending measure for the portion of the LRM segment being cross referenced.

DatumID 4567 This is the unique identifier for the Datum segment being cross-referenced.

DatumBegin Measure

2.3 This the beginning measure for the portion of the Datum segment being cross referenced.

DatumEnd Measure

10.5 This the ending measure for the portion of the Datum segment being cross referenced.


Geometry to Datum Cross Reference Tables These are the tables that define the many-to-many relationship between Geometry tables and the Linear Datum. There will be one of these tables for each geometric representation used in the Multilevel LRS.

Geometry to Datum Cross Reference Tables


ID 7592 This autonumber or sequence field uniquely identifies a record in this table.

GeometryID 98774 This is the unique identifier for the Geometry segment being cross-referenced.

Geometry BeginMeasure

46.2 This the beginning measure for the portion of the Geometry segment being cross referenced.

B-22


Geometry to Datum Cross Reference Tables


Geometry EndMeasure

54.3 This the ending measure for the portion of the Geometry segment being cross referenced.

DatumID 4567 This is the unique identifier for the Datum segment being cross referenced.

DatumBegin Measure

2.3 This the beginning measure for the portion of the Datum segment being cross referenced.

DatumEnd Measure

10.5 This the ending measure for the portion of the Datum segment being cross referenced.


B-23


GeoTrans Transportation Data Model

B-24

C-1

C. Working With Oracle LRS and ArcView Data

Working with Oracle LRS Data Some Oracle Spatial data has measure data stored within its geometry. This data can be exposed as measure fields by defining a view in Oracle. Below is an example view:

Create or replace view lrs_measure_test as SELECT mslink, SDO_LRS.FIND_MEASURE(a.gdo_geometry, m.diminfo, SDO_LRS.GEOM_SEGMENT_START_PT(a.gdo_geometry, m.diminfo)) LRS_MIN_MEASURE, SDO_LRS.FIND_MEASURE(a.gdo_geometry, m.diminfo, SDO_LRS.GEOM_SEGMENT_END_PT(a.gdo_geometry, m.diminfo)) LRS_MAX_MEASURE FROM interstates a, user_sdo_geom_metadata m WHERE m.table_name = 'INTERSTATES' AND m.column_name = 'GDO_GEOMETRY';

You can then use Database Utilities to define the view as a feature class and to assign a view key so that the OOM server can handle it. You can use these fields (LRS_MIN_MEASURE and LRS_MAX_MEASURE) along with the feature’s LRS key attribution in order to use Oracle LRS data as an LRS within GeoMedia Transportation.

Working with ArcView Data Some ArcView data has measure data stored within its geometry. Intergraph's ArcView data server makes those measures available as three fields with these default names: · MeasureMin - This is the lowest measure on a given feature. · MeasureMax - This is the highest measure on a given feature.


C-2

· Measure - This is the difference between MeasureMax and MeasureMin. You can use these fields along with the feature’s LRS key attribution in order to use ArcView data with measures as an LRS within GeoMedia Transportation.

IN - 1

Index

A Aggregating linear event data within

boundaries, 37-15 Aggregating point event data onto linear

segments, 37-1 Aggregating point event data onto points by

proximity, 37-7 Aggregating segment event data onto linear

segments by proportion, 37-20 Annotating begin and end measurements, 36-

3 Annotating digitizing direction, 36-1 Annotating even measures along the LRS,

36-8 arc, 38-4 Arc View

data, C-1 asymmetrical, 38-5

B Best Path Command, 48-1

workflow, 48-2 Blockage Editor Command, 44-1

workflow, 44-1 Build Network Command, 39-1

workflow, 39-1 Building a network, 39-1 Bulk multilevel LRS conflation, 3-12

C Calibrating interactive LRS, 5-1 Calibrating LRS, 6-1 Calibrating the LRS, 33-5 command

Best Path, 48-1 Blockage Editor, 44-1 Build Network, 39-1

Convert Intersection Referenced Events, 23-1

Create Intersection Markers, 9-1 Create Intersections and Midblocks, 25-1 Delete LRM Segment, 14-1 Display, 46-1 Display LRM, 19-1 Display OneWays, 45-1 Easy Path, 47-1 Find Closest Stops, 49-1 Generate Path Directions Command, 51-1 Insert LRM Segment, 10-1 Insert LRS Event, 26-1 Interactive LRS Calibration, 5-1 Interactive Multilevel LRS Conflation, 16-

1 LRS Calibration, 6-1 LRS Event Conversion, 22-1 LRS Event Generation, 24-1 LRS Event Overlay, 20-1 LRS Event Transform, 29-1 LRS Keys For Coordinate Events, 27-1 LRS Metadata Definition, 4-1 LRS Validation, 7-1 Merge LRM Segments, 13-1 Multilevel LRS Conflation, 17-1 Multilevel LRS Validation, 18-1 Network Coverage, 50-1 OneWay Editor, 43-1 Output Linear Datum, 15-1 Redigitize LRM Segment, 12-1 Reformat Linear Collections, 8-1 Resolve LRS Event Overlaps, 21-1 Restrictor Editor, 42-1 Routes And Sections To LRS, 28-1 Split LRM Segment, 11-1 Stop Manager, 40-1 Turn Editor, 41-1

Configure Network dialog box, 52-1


IN - 2

Configure Network Dialog Box workflow, 52-1

Configuring networks, 52-1 Conflating interactive multilevel LRSs, 16-1 Conflating multilevel LRSs, 17-1 control

Stop Properties, 53-1 conventions in GeoMedia documents, 1-4 Convert Intersection Referenced Events

Command, 23-1 workflow, 23-1

Converting intersection referenced events, 23-1

Converting LRS events, 22-1 Coordinate System Dialog Box, 32-1

workflow, 32-1 Covering networks, 50-1 Create Intersection Markers Command, 9-1

workflow, 9-4 Create Intersections and Midblocks

Command, 25-1 workflow, 25-3

Creating Intersection Markers, 9-1 Creating intersections and midblocks, 25-1

D Data conversion, 35-4 Data model design, 35-1 data structures

Event, B-15 LRS, B-3

Datum-based Event Properties Dialog Box workflow, 31-3

Defining LRS Metadata, 4-1 delay. See Impactors Delete LRM Segment Command, 14-1

workflow, 14-1 Deleting LRM segments, 14-1 dialog box

Configure Network, 52-1 Event Attributes, 29-1 Event Properties, 31-1 Marker Properties, 30-1

dialog box LRS Properties, 30-1

dialog box Coordinate System, 32-1

Display Blockages Command, 46-1 workflow, 46-2

Display LRM Command, 19-1 workflow, 19-3

Display LRM Dialog Box, 19-1 Display OneWay Command, 45-1 Display OneWays Command

workflow, 45-1 Displaying an LRM, 19-1 Displaying blockages, 46-1 Displaying one-ways, 45-1 document

conventions, 1-4 shipped with product, 1-3

E Easy Path Command, 47-1

workflow, 47-2 Edge-Node Connectivity, 38-2 Editing blockages, 44-1 Editing one-ways, 43-1 Editing restrictors, 42-1 Editing turns, 41-1 electronic self-help support, A-1 Event

data, B-1 data structures, B-14 data structures options, B-1

Duration, B-18 Marker Offset, B-16 XY, B-17

Event location stability, 3-5 Event Properties Dialog Box, 31-1

F Find Closest Stops Command, 49-1

workflow, 49-2 Finding the best path, 48-1 Finding the closest stops, 49-1 Finding the easy path, 47-1 Fixing the LRS, 33-6

Index

IN - 3

G Generate Path Directions Command, 51-1

workflow, 51-1 Generating LRS events, 24-1 Generating path directions, 51-1 GeoMedia

Technical Notes, A-1 GeoMedia Professional

Technical Notes, A-1 GeoMedia Transportation

LRS data structures, B-1 GeoMedia Transportation Automation

Programming Help, 1-4 GeoMedia Transportation Manager

documents shipped, 1-3 introduction, 1-2

GPS data, 27-1

H how to reach Intergraph, A-1

I Impedance, 38-4 Indexing the LRS, 33-6 Insert LRM Segment Command, 10-1

workflow, 10-1 Insert LRS Event Command, 26-1

workflow, 26-1 Inserting LRM segments, 10-1 Inserting LRS events, 26-1 Installing GeoMedia Transportation, 1-3 Intelligent editing, 3-12 Intelligent LRS features, 3-1 Interactive LRS Calibration Command, 5-1

workflow, 5-2 Interactive multilevel LRS conflation, 3-12 Interactive Multilevel LRS Conflation

Command workflow, 16-3

Intergraph how to reach, A-1 Knowledge Base, A-1 Support, A-1

Intersection Preparation for Multilevel LRSs, 34-8

Intersection Preparation for Single Level LRSs, 34-1

Intersection Preparation workflow, 34-1 introduction

GeoMedia Transportation Manager, 1-2 LRS, 1-2 Network Routing, 1-2 Routing, 38-1

edge-node connectivity, 38-2 impedance, 38-4 restrictors, 38-6 routing analysis, 38-9 routing maintenance, 38-10 routing network, 38-1 stops, 38-8 turn tables, 38-4

Introduction to Linear Referencing, 2-1 Linear Referencing Analysis, 2-15 Linear Referencing and GeoSpatial

Technology, 2-2 Linear Referencing System Maintenance,

2-17 LRS Linear Features and Event Data, 2-3

Introduction to Routing, 38-1 edge-node connectivity, 38-2 impedance, 38-4 restrictors, 38-7 routing analysis, 38-9 routing maintenance, 38-10 routing network, 38-1 stops, 38-8 turn tables, 38-4

K Keying LRS coordinate events, 27-1 Knowledge Base, A-1

L Linear Reference System Maintenance

introduction, 2-17 Linear Referencing

GeoSpatial Technology, 2-2


IN - 4

introduction, 2-1, 2-2 Linear Referencing Analysis, 2-14

introduction, 2-15 Linear Referencing and GeoSpatial

Technology, 2-2 Linear Referencing System Maintenance, 2-

17 Linear Referencing Systems, 1-2 logistics, 38-6 LRM Analysis

Working with the Insert LRM Segment Command, 10-1

LRM-based Event Properties Dialog Box workflow, 31-1

LRS, 1-2 coordinates, 27-1 data, B-1, C-1 data structures, B-3 data structures options

Duration, B-8 Duration with External Markers, B-11 Duration with Internal Markers, B-9 Measure, B-3 Measure with External Markers, B-6 Measure with Internal Markers, B-4

features, 16-1, 17-1, 24-1, 26-1, 29-1 Intersection Preparation, 34-1 introduction, 1-2 keys, 24-1, 27-1 linear features, 27-1 LRS data structures options, B-1 multilevel, 3-1 recordsets, 24-1 Single Level to Multilevel Conversion, 35-

1 validating workflow, 7-1

LRS Analysis using a multilevel LRS, 3-1 Working with the Insert LRS Event

Command, 26-1 Working with the Interactive Multilevel

LRS Conflation Command, 16-1 Working with the LRS Event Conversion

Command, 22-1

Working with the LRS Event Generation Command, 24-1

Working with the LRS Event Overlay Command, 20-1

Working with the LRS Event Transform Command, 29-1

Working with the LRS Keys for Coordinate Events Command, 27-1

Working with the Metadata Definition Command, 4-1

Working with the Multilevel LRS Conflation Command, 17-1

Working with the Resolve LRS Event Overlaps Command, 21-1

Working with the Routes And Sections to LRS Command, 28-1

LRS Analysis Workflows, 37-1 aggregate linear event data within

boundaries, 37-16 aggregate point event data onto linear

segments, 37-1 aggregate point event data onto points by

proximity, 37-7 LRS Analyst Workflows

aggregate segment event data onto linear segments by proportion, 37-21

LRS Annotation Workflows, 36-1 annotate begin and end measurements, 36-

3 annotate digitizing direction, 36-1 annotate even measures along the LRS,

36-8 LRS Calibration Command, 6-1

workflow, 6-2 LRS Data Preparation Workflows

calibrate the LRS, 33-5 fix the LRS, 33-6 index the LRS, 33-6 reformat linear collections, 33-1 validate and fix connectivity, 33-3 validate and fix geometry, 33-2 validate the LRS, 33-5

LRS Data Preparation Workflows, 33-1 LRS data structures

GeoMedia Transportation, B-1

Index

IN - 5

LRS Event Conversion Command, 22-1 workflow, 22-1

LRS Event Generation Command, 24-1 workflow, 24-2

LRS Event Overlay workflow, 20-11

LRS Event Overlay Command, 20-1 LRS Event Transform Command, 29-1

workflow, 29-1 LRS Keys For Coordinate Events Command,

27-1 workflow, 27-1

LRS Linear Features and Event Data, 2-3 introduction, 2-3

LRS Maintenance Working with the LRS Calibration

Command, 6-1 Working with the LRS Interactive

Calibration Command, 5-1 Working with the LRS Validation

Command, 7-1 Working with the Multilevel LRS

Validation Command, 18-1 Working with the Reformat Linear

Collections Command, 8-1 LRS Metadata Definition Command, 4-1 LRS Metadata Defintion Command

workflow, 4-4, 4-9, 4-10 LRS Properties Dialog Box, 30-1

workflow, 30-1, 53-2 LRS Validation

checks performed, 7-1 LRS Validation Command, 7-1

workflow, 7-2 LRS-based Routing Restrictions Workflow,

55-1

M Maintaining a multilevel LRS, 3-9 Managing stops, 40-1 Marker Properties Dialog Box, 30-1

workflow, 30-2, 30-3 Merge LRM Segments command

workflow, 13-2 Merge LRM Segments Command, 13-1

Merging LRM segments, 13-1 Multilevel LRS

analysis, 3-1 Intersectioin Preparation, 34-8

Multilevel LRS calibration, 3-17 Multilevel LRS Conflation Command

workflow, 17-3 Multilevel LRS Validation command

workflow, 18-7 Multilevel LRS Validation Command, 18-1 Multilevel LRSs, 3-1

bulk multilevel LRS conflation, 3-12 calibration, 3-15 event location stability, 3-4 intelligent editing, 3-10 intelligent LRS features, 3-1 interactive multilevel LRS conflation, 3-10maintaining a multilevel LRS, 3-8 multiple LRM support, 3-6 production tables, 3-17 region IDs, 3-3 Routing, 3-17 temporal analysis, 3-6 temporality during editing, 3-8 validation, 3-16

Multiple LRM support, 3-6

N Network, 50-1 Network Coverage Command

workflow, 50-2 Network Routing, 1-2

O OneWay Editor Command, 43-1

workflow, 43-1 optimization, 38-6 Oracle LRS data, C-1 Output Linear Datum Command, 15-1 Output Linear Datumcommand

workflow, 15-3 Outputting linear datum, 15-1 Overlaying LRS events, 20-1


IN - 6

P Production tables, 3-19

R Redigitize LRM Segment Command, 12-1

workflow, 12-3 Redigitizing LRM segments, 12-1 Reformat Linear Collections Command, 8-1

workflow, 8-2 Reformatting linear collections, 8-1, 33-1 Region IDs, 3-3 Resolve LRS Event Overlaps Command, 21-

1 workflow, 21-2

Resolving LRS event overlaps, 21-1 Restrictor Editor Command, 42-1

workflow, 42-1 Restrictors, 38-6, 38-7

examples, 38-7 operationalizing, 38-7

Route and section LRS, 28-1 Routes And Sections to LRS

capabilities, 28-1 Routes And Sections To LRS

workflow, 28-1 Routes And Sections to LRS Command, 28-1 Routing, 3-19

Working with the Configure Network Dialog Box, 52-1

Routing Analysis, 38-9 Working with the Best Path Command,

48-1 Working with the Easy Path Command,

47-1 Working with the Find Closest Stops

Command, 49-1 Working with the Network Coverage

Command, 50-1 Routing Data Maintenance Workflows, 54-1

Dynamic, 54-1 Manual – Initial Network Creation, 54-2 Manual – Network Update, 54-3 Routing Network Validation, 54-11

Routing Maintenance, 38-10

Working with the Blockage Editor Command, 44-1

Working with the Build Network Command, 39-1

Working with the Display Blockages Command, 46-1

Working with the Display OneWay Command, 45-1

Working with the OneWay Editor Command, 43-1

Working with the Restrictor Editor Command, 42-1

Working with the Stop Manager Command, 40-1

Working with the Turn Editor Command, 41-1

Routing Network, 38-1

S self-help support, A-1 Single Level LRS

Intersection Preparation, 34-1 intersection Preparation, 3-5

Single Level to Multilevel LRS Conversion workflow, 35-1

Source data preparation, 35-3 Split LRM Segment Command, 11-1

workflow, 11-2 Spliting LRM segments, 11-1 Start Here, 1-2 Stop Manager Command, 40-1

Creating new stop feature classes workflow, 40-1

Managing stop sets workflow, 40-2

workflow, 40-1 Stop Properties Control, 53-1

workflow, 53-1 Stops, 38-8 structures

GeoMedia Transportation data, B-1 support, Intergraph, A-1 symmetrical, 38-7

Index

IN - 7

T technical

notes, A-1 support, A-1

Temporal analysis, 3-8 Temporality during editing, 3-10 Transforming LRS events, 29-1 Transportation Asset system data, B-1 Turn Editor Command, 41-1

workflow, 41-1 Turn tables, 38-4 typeface conventions, 1-4

V Validate LRS

checks performed, 7-1 validating

LRS Workflow, 7-1 Validating and fixing connectivity, 33-3 Validating and fixing geometry, 33-2 Validating LRS, 7-1 Validating multilevel LRS, 18-1 Validating the LRS, 33-5 Validation commands

LRS Validation, 3-16 Multilevel LRS Validation, 3-16

W What’s New in Transportation Manager

6.0.3, 1-1 workflow

Best Path Command, 48-2 Blockage Editor Command, 44-1 Build Network Command, 39-1 Configure Network Dialog Box, 52-1 Convert Intersection Referenced Events

Command, 23-1 Coordinate System Dialog Box, 32-1 Create Intersection Markers Command, 9-

4 Create Intersections and Midblocks

Command, 25-3 Creating New Metadata Definitions, 4-4

Datum-based Event Properties Dialog Box, 31-3

Delete LRM Segment, 14-1 Display Blockages Command, 46-2 Display LRM Command, 19-3 Display OneWays Command, 45-1 Easy Path Command, 47-2 Find Closest Stops Command, 49-2 Generate Path Directions Command, 51-1 Insert LRM Segment Command, 10-1 Insert LRS Event Command, 26-1 Interactive LRS Calibration Command, 5-

2 Interactive Multilevel LRS Conflation

Command, 16-3 Intersection Preparation, 34-1 LRM-based Event Properties Dialog Box,

31-1 LRS Calibration Command, 6-2 LRS Event Conversion Command, 22-1 LRS Event Generation Command, 24-2 LRS Event Overlay Command, 20-11 LRS Event Transform Command, 29-1 LRS Keys For Coordinate Events

Command, 27-1 LRS Metadata Definition Command, 4-4,

4-9, 4-10 LRS Properties Dialog Box, 30-1 LRS Validation Command, 7-2 Marker Properties Dialog Box, 30-2, 30-3 Merge LRM Segments, 13-2 Modifying an Existing LRS Definition, 4-

9 Multilevel LRS Conflation Command, 17-

3 Multilevel LRS Validation command, 18-7 Network Coverage Command, 50-2 OneWay Editor Command, 43-1 Output Linear Datum Command, 15-3 Redigitize LRM Segment Command, 12-3 Reformat Linear Collections Command, 8-

2 Resolve LRS Event Overlaps Command,

21-2 Restrictor Editor Command, 42-1


IN - 8

Reviewing an Existing LRS Definition, 4-10

Routes And Sections To LRS, 28-1 Single Level to Multilevel LRS

Conversion, 35-1 Split LRM Segment, 11-2 Stop Manager Command, 40-1

Creating new stop feature classes, 40-1 Managing stop sets, 40-2

Stop Properties Control, 53-1 Turn Editor Command, 41-1

workflows LRS Analysis, 37-1 LRS Annotation, 36-1 LRS based Routing Restrictions, 55-1 LRS Data Preparation, 33-1 Routing Data Maintenance, 54-1

Working with GeoMedia Transportation, 1-3

Additional information on Intergraph Support and Services is available on the Internet. Use a web browser to connect to Intergraph Online at http:/intergraph.com.

For general Intergraph information, call 1-800-791-3357 (U.S. and Canada) or 00-1-256-730- 2000 (international).

Working with GeoMedia Transportation Manager 09/06

DJA084590

http://intergraph.com

working with gm transp manager

Technology

software product

reliability of software

trademarks intergraph

restricted computer

entire document

terms of use use

unpublished rights

product names