An Overview of the Chester County Local Linear Referencing System (LRS)

1. An Overview of the Chester County Local Linear Referencing System (LRS)

2. What is an LRS? • Most generally, a linear referencing system comprises: • Selected linear features of an agency’s centerline aggregated into routes that represent distinct paths where travel can, does or will occur. • For the regional GIS-T the focus is existing street centerline • Measure values (in feet for the PA regional GIS-T) applied along these routes – consistently ascending from one end to the other and no redundancy. • Linear or point representations of Spatial and/or Attribute data related to these routes and measures; referenced by event tables.

3. Evaluation and Preparation of the pre-local LRS Centerline File Chester County non-local LRS transportation centerline (TCL): • “Native” County Centerline (CL) consists of street (and limited trail) segmented and attributed according to requirements of emergency services and addressing. Spatially accurate with a few known exceptions. • Digitized direction of segments runs with increasing addresses (or travel direction on dual-centerline freeway) Ramps generally not part of native ChesCo CL: added to TCL • TCL maintained as network – with Junctions feature class (FC) – in feature dataset. • Native ChesCo CL – and now TCL – verified as 100% topologically correct (according to rules elsewhere described).

4. Pre-local LRS File Evaluation and Preparation (cont.) Chester County non-local LRS TCL Example # 1: PennDOT LRS supported on spatially accurate ChesCo CL, TCL includes all public roads and ties to County data.

5. Step 2: Assignment of segments to routes cont Example of correct route definition (route color by local route ID)

6. Step 2: Assignment of segments to routes cont Example of correct route definition (muni-line roads) In contrast to the muni-line road illustrated on the previous slide, Berwyn Paoli Rd must change route ID because Tredyffrin has the higher PennDOT code.

7. Step 2: Assignment of segments to routes cont Example of correct route definition: reasons for breaking routes Same name & muni, but not continuous Directional Prefix change

8. Step 2: Assignment of segments to routes cont Subjective Route Definition Choice When same-name/same muni streets intersect • Six segments named Esprit TC • No more than four can be strung together to form a route • Several options for route definition • Best (?) solution leaves two single standalone segment routes (other “correct” options are possible) Option 5 Option 4 • There is no need to waste time analyzing the comparative merits of one route definition over another. Just make sure your method produces a result that is acceptable by the route-definition rules. Option 1 (selected) Option 3 Option 2

9. Step 2: Assignment of segments to routes cont Examples of route definition and Route Names/ID’s

10. Step 2: Assignment of segments to routes cont Example of route definition and measure for routes that begin and/or end with a loop segment.

11. Route-data Table(s), ID’s and Attributes • A master route table(s) for all routes (local, PennDOT …) • Ensures that all route ID’s are unique and valid; • Maintains referential integrity with regard to segments’ route attributes; • Lets you join centerline segments to their route data. The Transportation Centerline feature class table includes fields for all possible route ID’s

12. Step 2: Assignment of segments to routes: suggested procedure Example of application of M-Values to Route • West Bradford’s Vermont Lane Route: • Two segments – approx. 505’ • Route runs EB, but Westernmost segment runs WB

13. Multiple LRS options Supported by single underlying geometry Single “Transportation Centerline” Feature Class PennDOT LRS Applied Local LRS Applied Other LRS Applied • Rail station, mile marker, other agency measures, etc: • All Linearly-referenced data transformable among LRS’s via common underlying geometry/ArcToolbox • Fully-segmented, all inclusive FC (allows segment-specific event reference) OR • FC “dissolved” by applicable route ID’s after definition query is applied to extract only relevant segments (provides better performance) Hybrid LRS Applied?

14. Multiple LRS options Supported by single underlying geometry Single “Transportation Centerline” Feature Class PennDOT LRS Applied Local LRS Applied Local measures by local Route ID PennDOT measures by NLF

15. Local vs. PennDOT LRS on Same Centerline • Routes Start in same place and run in same direction • M-values on both LRS’s are close through West Chester • New Local Route 52_0036 begins at municipal line, where as PennDOT NLF 2907 continues

16. Local vs. PennDOT LRS ramps and divided highway

19. Local Routes:Not just for streets • Rail (active, inactive, abandoned…) • Non-motorized path (trail, multi-use path, etc) • Waterway (navigable/for recreation) • Inactive corridors (utility ROW’s, muni easements, railbanking …)

20. Using the local LRS Example of route event source

22. Using the local LRS Example of route event generation with custom application