Your SlideShare is downloading. ×
Using Utah's Linear Referencing GIS Layer: SGID93.Transportation.UDOTRoutes_LRS
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

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

1,179
views

Published on

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

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,179
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
13
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Other examples may include local address point data
  • Transcript

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