Using Utah’s LRS Thomas McMurtry InterPlan Bert Granberg AGRC 4/7/2011 Thomas McMurtry
What is an LRS <ul><li>Linear Referencing System </li></ul><ul><ul><li>Route Definition </li></ul></ul><ul><ul><ul><li>Sys...
Why LRS? <ul><li>Provides a Common Geometric Base </li></ul><ul><li>Simple geometry maintained in one place </li></ul><ul>...
Statewide Centerline Goals: <ul><li>Accessible, Valued Public Resource </li></ul><ul><li>Currency: </li></ul><ul><ul><li>S...
Statewide Centerline Goals: <ul><li>Accessible, Valued Public Resource </li></ul><ul><li>Currency: </li></ul><ul><ul><li>S...
Linear Referencing System <ul><li>How it gets built </li></ul><ul><ul><li>Statewide road, ramp & collector features: </li>...
Building Utah State Route 137
1. SELECT Participating Centerlines
2. ATTRIBUTE Road Features w/ RtName & RtPart_Nbr 0137P Part 1 0137P Part 2 0137P Part 3
3. MERGE Road Features Into Route Parts 0137P Part 1 0137P Part 2 0137P Part 3
4. CALIBRATE Route M Coordinates at Endpoints
2.314 8.801 5.  ADD INTERMEDIATE CALIBRATION Where Needed
6. MERGE Parts Into Single PolylineM Feature
6. MERGE Parts Into Single PolylineM Feature <ul><li>7. QA </li></ul><ul><li>8. DERIVE Additional Products: </li></ul><ul>...
<ul><li>Integrated Highway & Local Data </li></ul><ul><ul><li>Mileposts , </li></ul></ul><ul><ul><li>Exit Numbers , </li><...
P, N, & X <ul><li>‘ P’ositive direction routes exist for all highways, measures increase in  northbound or eastbound direc...
Agenda <ul><ul><li>Tools </li></ul></ul><ul><ul><li>Points </li></ul></ul><ul><ul><ul><li>Making a point route event </li>...
Tools <ul><li>Utah State Routes created by UDOT and AGRC </li></ul><ul><li>ArcToolbox includes LRS tools as defalt </li></...
4/7/2011 Thomas McMurtry
4/7/2011 Thomas McMurtry
Point Data <ul><li>Make Route Event Layer </li></ul><ul><ul><li>Working with tables </li></ul></ul><ul><ul><li>Adding Cras...
LRS Table <ul><li>Remember Route Identifier is the LABEL column </li></ul>4/7/2011 Thomas McMurtry
Crash Table <ul><li>Use “=concatenate” in excel to create a label column </li></ul>4/7/2011 Thomas McMurtry
Example 4/7/2011 Thomas McMurtry
4/7/2011 Thomas McMurtry
Point Data <ul><li>Locate Features along a route </li></ul><ul><ul><li>USTM Nodes </li></ul></ul><ul><ul><li>Intersection ...
Example 4/7/2011 Thomas McMurtry
Example <ul><li>Output Table </li></ul><ul><li>MEAS is the measure of the milepost along the route </li></ul>4/7/2011 Thom...
Example 4/7/2011 Thomas McMurtry
Final Product 4/7/2011 Thomas McMurtry
Segment Data <ul><li>Make Route Event Layer </li></ul><ul><li>Must have begin and end MP </li></ul><ul><li>UDOT segments <...
Example 4/7/2011 Thomas McMurtry
Example <ul><li>Used to calculated expected crash rates </li></ul><ul><li>Used for identifying top 5 % </li></ul><ul><li>U...
Segment Data <ul><li>Overlay Route Events  </li></ul><ul><ul><li>Combine multiple segment breaks </li></ul></ul>4/7/2011 T...
Example 4/7/2011 Thomas McMurtry
Example <ul><li>Creates a table with segments broken by all possible breaks  </li></ul>4/7/2011 Thomas McMurtry
Example <ul><li>Creates a table </li></ul>4/7/2011 Thomas McMurtry
Value of LRS Tools <ul><li>Save Time </li></ul><ul><li>Accurately map referenced data </li></ul><ul><li>Accurately referen...
Value of LRS Tools 4/7/2011 Thomas McMurtry
Lessons Learned <ul><li>There are some work arounds </li></ul><ul><ul><li>Requires database work </li></ul></ul><ul><li>I ...
Questions? <ul><li>Bert Granberg –  [email_address] </li></ul><ul><li>Thomas McMurtry –  [email_address] </li></ul>4/7/201...
Upcoming SlideShare
Loading in …5
×

Using Utah's Linear Referencing GIS Layer: SGID93.Transportation.UDOTRoutes_LRS

1,591 views

Published on

Slides from UGIC 2011 conference in Logan (April 2011).

First half of slides (Bert Granberg AGRC) discuss what, why and how of the LRS dataset created by AGRC and UDOT to represent state and federal routes in Utah in a polylineM format.

Second half (Thomas McMurtry, Interplan) shows use cases where tabular data on traffic volume, accidents, projects, etc was linked to the GIS representation of the LRS for map display and query

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,591
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
19
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Other examples may include local address point data
  • Using Utah's Linear Referencing GIS Layer: SGID93.Transportation.UDOTRoutes_LRS

    1. 1. Using Utah’s LRS Thomas McMurtry InterPlan Bert Granberg AGRC 4/7/2011 Thomas McMurtry
    2. 2. What is an LRS <ul><li>Linear Referencing System </li></ul><ul><ul><li>Route Definition </li></ul></ul><ul><ul><ul><li>System Standards </li></ul></ul></ul><ul><ul><ul><li>Route Names, IDs </li></ul></ul></ul><ul><ul><ul><li>Ordered Road Segments </li></ul></ul></ul><ul><ul><ul><li>Calibration Points {Start, Intermediate(s), End} </li></ul></ul></ul><ul><ul><li>Physical monuments (mileposts, exit nbrs) </li></ul></ul><ul><ul><li>Linear Diagrams (1D) </li></ul></ul><ul><ul><li>Digital Geographic Base Reference (2D & 3D) </li></ul></ul><ul><ul><ul><li>PolylineM Feature Class (x,y,m(easure) coordinates) </li></ul></ul></ul>
    3. 3. Why LRS? <ul><li>Provides a Common Geometric Base </li></ul><ul><li>Simple geometry maintained in one place </li></ul><ul><li>Events (as table rows, but references RT_ID + MP) </li></ul><ul><ul><li>Point: Overhead sign 0015P 306.381 </li></ul></ul><ul><ul><li>Line: Asphalt pavement overlay, 0210P 7.982 to 12.119 (lane 1) </li></ul></ul><ul><ul><li>Think about lanes on I-15 </li></ul></ul><ul><li>Analytical Advantages </li></ul><ul><ul><li>Many ‘spatial’ operations are done in 1 dimension </li></ul></ul>
    4. 4. Statewide Centerline Goals: <ul><li>Accessible, Valued Public Resource </li></ul><ul><li>Currency: </li></ul><ul><ul><li>Statewide roads published update every 2 months </li></ul></ul><ul><li>Functionality: </li></ul><ul><li>Cartographic Base Map Support </li></ul><ul><li>Inventory (funding, jurisdiction, surface, etc) </li></ul><ul><li>Address Matching </li></ul><ul><ul><li>Street Address & Route/Milepost </li></ul></ul><ul><li>Routing Solutions </li></ul>
    5. 5. Statewide Centerline Goals: <ul><li>Accessible, Valued Public Resource </li></ul><ul><li>Currency: </li></ul><ul><ul><li>Statewide roads published update every 2 months </li></ul></ul><ul><li>Functionality: </li></ul><ul><li>Cartographic Base Map Support </li></ul><ul><li>Inventory (funding, jurisdiction, surface, etc) </li></ul><ul><li>Address Matching </li></ul><ul><ul><li>Street Address & Route/Milepost </li></ul></ul><ul><li>Routing Solutions </li></ul><ul><li>Linear Referencing Base </li></ul><ul><ul><li>Adds Complexity but makes Enterprise Sense!!! </li></ul></ul>
    6. 6. Linear Referencing System <ul><li>How it gets built </li></ul><ul><ul><li>Statewide road, ramp & collector features: </li></ul></ul><ul><ul><ul><li>Connectivity, Alignment, Geometric Depiction </li></ul></ul></ul><ul><ul><ul><li>DOT_RTNAME  Route ID </li></ul></ul></ul><ul><ul><ul><li>DOT_RTPART  Part Number, for multipart routes </li></ul></ul></ul><ul><ul><li>Merge road features  route features </li></ul></ul><ul><ul><li>Calibration points </li></ul></ul><ul><ul><ul><li>All part end points </li></ul></ul></ul><ul><ul><ul><li>Intermediate points, about every 5-10 miles </li></ul></ul></ul>
    7. 7. Building Utah State Route 137
    8. 8. 1. SELECT Participating Centerlines
    9. 9. 2. ATTRIBUTE Road Features w/ RtName & RtPart_Nbr 0137P Part 1 0137P Part 2 0137P Part 3
    10. 10. 3. MERGE Road Features Into Route Parts 0137P Part 1 0137P Part 2 0137P Part 3
    11. 11. 4. CALIBRATE Route M Coordinates at Endpoints
    12. 12. 2.314 8.801 5. ADD INTERMEDIATE CALIBRATION Where Needed
    13. 13. 6. MERGE Parts Into Single PolylineM Feature
    14. 14. 6. MERGE Parts Into Single PolylineM Feature <ul><li>7. QA </li></ul><ul><li>8. DERIVE Additional Products: </li></ul><ul><ul><li>Milepost Points (events!) </li></ul></ul><ul><ul><li>Milepost Ranges on Road Features </li></ul></ul>
    15. 15. <ul><li>Integrated Highway & Local Data </li></ul><ul><ul><li>Mileposts , </li></ul></ul><ul><ul><li>Exit Numbers , </li></ul></ul><ul><ul><li>Ramp IDS ( not shown ) </li></ul></ul><ul><ul><ul><li> Happier Response Community </li></ul></ul></ul>
    16. 16. P, N, & X <ul><li>‘ P’ositive direction routes exist for all highways, measures increase in northbound or eastbound direction. </li></ul><ul><li>‘ N’egative exist only for divided highway sections and depict the southbound or westbound directions </li></ul><ul><ul><li>Measures for Interstate N routes are in DRIVEN, not mileposted direction, as this is how UDOT inventories features on these routes </li></ul></ul><ul><ul><li>For interstates, X route measures are according to physical mileposts in the negative direction (this is how they are common referenced outside of UDOT) </li></ul></ul>4/7/2011 Thomas McMurtry “ P” Northbound Mileposts 0 - 400 “ N” Southbound Mileposts 0 - 400 “ X” Southbound Mileposts 400 - 0
    17. 17. Agenda <ul><ul><li>Tools </li></ul></ul><ul><ul><li>Points </li></ul></ul><ul><ul><ul><li>Making a point route event </li></ul></ul></ul><ul><ul><ul><li>Locating features along a route </li></ul></ul></ul><ul><ul><li>Segments </li></ul></ul><ul><ul><ul><li>Making a segment route event </li></ul></ul></ul><ul><ul><ul><li>Overlay multiple route events </li></ul></ul></ul>4/7/2011 Thomas McMurtry
    18. 18. Tools <ul><li>Utah State Routes created by UDOT and AGRC </li></ul><ul><li>ArcToolbox includes LRS tools as defalt </li></ul><ul><li>Make sure that the routes functions are available </li></ul><ul><li>P, N, & X </li></ul>4/7/2011 Thomas McMurtry
    19. 19. 4/7/2011 Thomas McMurtry
    20. 20. 4/7/2011 Thomas McMurtry
    21. 21. Point Data <ul><li>Make Route Event Layer </li></ul><ul><ul><li>Working with tables </li></ul></ul><ul><ul><li>Adding Crash Locations </li></ul></ul>4/7/2011 Thomas McMurtry
    22. 22. LRS Table <ul><li>Remember Route Identifier is the LABEL column </li></ul>4/7/2011 Thomas McMurtry
    23. 23. Crash Table <ul><li>Use “=concatenate” in excel to create a label column </li></ul>4/7/2011 Thomas McMurtry
    24. 24. Example 4/7/2011 Thomas McMurtry
    25. 25. 4/7/2011 Thomas McMurtry
    26. 26. Point Data <ul><li>Locate Features along a route </li></ul><ul><ul><li>USTM Nodes </li></ul></ul><ul><ul><li>Intersection MPs </li></ul></ul>4/7/2011 Thomas McMurtry
    27. 27. Example 4/7/2011 Thomas McMurtry
    28. 28. Example <ul><li>Output Table </li></ul><ul><li>MEAS is the measure of the milepost along the route </li></ul>4/7/2011 Thomas McMurtry
    29. 29. Example 4/7/2011 Thomas McMurtry
    30. 30. Final Product 4/7/2011 Thomas McMurtry
    31. 31. Segment Data <ul><li>Make Route Event Layer </li></ul><ul><li>Must have begin and end MP </li></ul><ul><li>UDOT segments </li></ul><ul><ul><li>Crash Segments </li></ul></ul><ul><ul><li>Traffic Volume Segments </li></ul></ul><ul><ul><li>Travel Model Segments </li></ul></ul><ul><ul><li>Maintenance Segments </li></ul></ul>4/7/2011 Thomas McMurtry
    32. 32. Example 4/7/2011 Thomas McMurtry
    33. 33. Example <ul><li>Used to calculated expected crash rates </li></ul><ul><li>Used for identifying top 5 % </li></ul><ul><li>Used for prioritization </li></ul>4/7/2011 Thomas McMurtry
    34. 34. Segment Data <ul><li>Overlay Route Events </li></ul><ul><ul><li>Combine multiple segment breaks </li></ul></ul>4/7/2011 Thomas McMurtry
    35. 35. Example 4/7/2011 Thomas McMurtry
    36. 36. Example <ul><li>Creates a table with segments broken by all possible breaks </li></ul>4/7/2011 Thomas McMurtry
    37. 37. Example <ul><li>Creates a table </li></ul>4/7/2011 Thomas McMurtry
    38. 38. Value of LRS Tools <ul><li>Save Time </li></ul><ul><li>Accurately map referenced data </li></ul><ul><li>Accurately reference mapped data </li></ul><ul><li>Link data from multiple sources to one data point </li></ul><ul><li>Create new valuable products </li></ul><ul><li>Only State Routes </li></ul>4/7/2011 Thomas McMurtry
    39. 39. Value of LRS Tools 4/7/2011 Thomas McMurtry
    40. 40. Lessons Learned <ul><li>There are some work arounds </li></ul><ul><ul><li>Requires database work </li></ul></ul><ul><li>I typically don’t get the results I want on the first try </li></ul><ul><li>Some need to verify Mileposts </li></ul><ul><li>Break large data sets up </li></ul>4/7/2011 Thomas McMurtry
    41. 41. Questions? <ul><li>Bert Granberg – [email_address] </li></ul><ul><li>Thomas McMurtry – [email_address] </li></ul>4/7/2011 Thomas McMurtry Thank You

    ×