Managing a Multilevel Linear Referencing System. Phil Hardy Transportation Industry Consultant

Transcription

1 Managing a Multilevel Linear Referencing System Phil Hardy Transportation Industry Consultant

2 Agenda Design goals of Temporal, Multilevel LRS 4 big hairy problems Maintaining a Temporal, Multilevel LRS Maintaining the data model Temporality Conflation Session March 17 th,

3 Design goals of Temporal, Multilevel LRS

4 Linear Referencing Unifies a transportation agency s data Allows for cross discipline analysis Reduces a mountain of data into a form that facilitates decision making Session March 17th,

5 4 Big, Hairy Problems with Traditional LRSs Not all parties reference the network in the same way Session March 17 th,

6 4 Big, Hairy Problems Multiple Linear Referencing Methods State Border Route 50 Main St. 175 Main St km State Cumulative Address Range: 100 to 200 Street Address Orange County Los Angeles County Intersection with Elm Ave. Intersection with Spruce Ave. Route 50 Main St. 5.4 km County Cumulative Session March 17 th, m East Marker Offset

7 4 Big, Hairy Problems Multiple Linear Referencing Methods Traffic counts (Km Posts) Accidents (Intersection Referenced) Session March 17 th,

8 4 Big, Hairy Problems Multiple Linear Referencing Methods Refined results: high accident rate intersections Session March 17 th,

9 4 Big, Hairy Problems with Traditional LRSs Not all parties reference the network in the same way Not all parties use the same graphic representation of the network Session March 17 th,

10 4 Big, Hairy Problems Multiple Geometric Representations Different geometries for different uses LRS, Routing Demand Modeling Session March 17 th,

11 4 Big, Hairy Problems with Traditional LRSs Not all parties reference the network in the same way Not all parties use the same graphic representation of the network Roadway attributes can shift or even disappear over time Session March 17 th,

12 4 Big, Hairy Problems Attribute Stability Desired behavior Session March 17th,

13 4 Big, Hairy Problems with Traditional LRSs Not all parties reference the network in the same way Not all parties use the same graphic representation of the network Roadway attributes can shift or even disappear over time There s no good way to compare past and present attributes (temporality) Session March 17 th,

14 4 Big, Hairy Problems Temporality Need to compare the before with the after After network changes Session March 17th,

15 The Solution Multilevel, Temporal LRS Independent LRMs & Geometries tied to a bedrock, solid Linear Datum Events Linear Referencing Methods Linear Datum Geometry Session March 17 th,

16 Maintaining a Temporal, Multilevel LRS

17 Multilevel LRS Data Maintenance Design Challenges Need to make it: Simple Bulletproof Session March 17 th,

18 Multilevel LRS Data Maintenance Getting Started Convert Single-level LRS to Multilevel LRS LRM LRM Reference Datum Reference Linear Feature Class LRM Reference Datum Reference Linear Datum Geometry Reference Easy transition to Multilevel LRS Geometry Reference Geometry Session March 17 th,

19 Multilevel LRS Data Maintenance Intelligent LRM Feature Mimics a traditional LRS Knows where it came from Bulletproof Session March 17th,

20 Multilevel LRS Data Maintenance Intelligent Editing Commands Multilevel LRS-aware editing commands Insert LRM Segment Delete LRM Segment Redigitize LRM Segment Split LRM Segment Merge LRM Segments Interactive LRS Calibration LRS Calibration Interactive Multilevel LRS Conflation Multilevel LRS Conflation Multilevel LRS Validation Modeled after GeoMedia Pro Session March 17 th,

21 Multilevel LRS Data Maintenance Intelligent Editing Commands Add, Delete, Split, Merge, & Digitize Commands understand MLRS LRM changes on LRM layer Geometry changes on Geometry layer Commands understands measures Changes don t affect data location stability Session March 17th,

22 Multilevel LRS Data Maintenance Maintaining a Temporal LRS GeoMedia Transaction Manager (GTM) LRS! Temporal GIS! Open Editing Session Edit as normal Commit Changes & Close Curve Realignment 07/07/03 Modified Session March 17th,

23 GM Transportation Manager & GM Transaction Manager Temporality, Maintenance, and Stability Our simulation - Before Dangerous Curve Linear Event (Pavement Condition) Point Events (Accidents) LRS Segments Session March 17th,

24 GM Transportation Manager & GM Transaction Manager Temporality, Maintenance, and Stability Modeling a realignment that went into effect on 7/7/03 Open a GTM editing session Set Valid Time dates Oracle Object LTT R-W Curve Realignment 07/07/03 Modified Dockable control Session March 17th,

25 GM Transportation Manager & GM Transaction Manager Temporality, Maintenance, and Stability Take out the curve with the Redigitize LRM Segment command Session March 17th,

26 GM Transportation Manager & GM Transaction Manager Temporality, Maintenance, and Stability Readjust measures with the Interactive LRS Calibration command Session March 17th,

27 GM Transportation Manager & GM Transaction Manager Temporality, Maintenance, and Stability Readjust measures with the Interactive LRS Calibration command Session March 17th,

28 GM Transportation Manager & GM Transaction Manager Temporality, Maintenance, and Stability When edits are complete, use GTM to commit changes and close editing session Session March 17th,

29 GM Transportation Manager & GM Transaction Manager Temporality, Maintenance, and Stability Turn Event data back on 1. Event data doesn t shift. 2. No off road Events show up 3. No editing of Event tables was required Session March 17th,

30 GM Transportation Manager & GM Transaction Manager Temporality, Maintenance, and Stability Use GTM to look at the past before our realignment 07/07/03 Oracle Object LTT R-W None 07/07/03 Modified Session March 17th,

31 GM Transportation Manager & GM Transaction Manager Temporality, Maintenance, and Stability Use GTM to look at the past before our realignment 01/01/03 Oracle Object LTT R-W None 01/01/03 Modified Event data is displayed as it was prior to the realignment Session March 17th,

32 One More Big, Hairy Problem Session March 17th,

33 Multilevel LRS Data Maintenance LRS Conflation Different Segmentation Dual vs. Single Centerline Dual vs. Single Repercussions Keystone Ave. Use it to replace existing data with better data Use it to add LRMs Use it to add Geometric representations Use it to add to existing data Or should these points correlate? 80 Session March 17th, Significant location differences One Two

34 GM Fusion Linking Methodology Valence v = 2 v = 1 v = 3 v = 4 Session March 17th,

35 GM Fusion Linking Methodology Handles variations in segmentation New data Link 1 Link 2 Link 3 Link Existing LRS Session March 17th,

36 LRS Conflation Event data location stability Session March 17th,

37 Taming big hairy problems! Session March 17th,

38 Philip H. Hardy Transportation Industry Consultant Security, Government & Infrastructure Tel. +1 (949) Fax +1 (949) Intergraph Corporation Mill Pond Mission Viejo, CA Session March 17th,