1. 15 yrs ago GIS own specialty, no real integration with TE 10 yrs ago just for mapping purposes, end result graphics LRS = mainframe large DOT, no GUI (please contradict) 5 years ago just making into true RDBMS (no more clunky SQL connect navigator Tabular data in RDBMS = ref integ, speed, no spatial unless suited for task (too many people use spatial bc they can … working arcmap

2. Presentation to the ESRI Transportation Special Interest Group February 19 th, 2008 Linear Referencing Systems: Focus on County-level Usage

3. Presented by Gerry Kelly – Morning session GIS-T overview: The evolution of GIS-T at the county level The Chester County GIS-T GIS-T Geodatabase Linear referencing GIS-T applications Presentation to the ESRI Transportation Special Interest Group February 19 th, 2008 Linear Referencing Systems: Focus on County-level Usage

4. GIS Transportation Planning/ Engineering Traditional Database Computer Applications The evolution of GIS-T: 15 years ago … GIS own specialty, no real integration with TE

5. GIS Transportation Planning/ Engineering Traditional Database Computer Applications The evolution of GIS-T: 10 years ago …

6. GIS Transportation Planning/ Engineering Traditional Database Computer Applications The evolution of GIS-T: 5 years ago … Internet GIS(-T)

7. GIS Traditional Database Computer Applications The evolution of GIS-T: Now … Many related applications and datasets Web applications = GIS-T that people dont know is GIS-T Transportation Planning/ Engineering

8. The Chester County GIS-T Presented by Gerry Kelly Feb. 19, 2008

10. PennDOT Data ChesCo GIS Street Centerline Significant & consistent transportation-related data Largely limited to State Rd system (about one-third Countys approx. 4500 road-miles) Based on PennDOTs linear referencing system (LRS) PennDOT Street Centerline Overview the Chester County GIS-T Geodatabase ChesCo Other Data (non-GIS, or GIS from other depts) Only centerline for State roads has meaningful data, usable LRS and is reasonably current and accurate. Municipal and other-agency data Other ChesCo GIS Data Multi-modal GIS-T TRANSPORTATION_NETWORK + a lot of work = The data: What went in the GDB, Whered it come from?

11. Thirty+ feature classes More than 225 related attribute and/or feature class tables More than 200 coded-value domains/look-up tables Meta data for spatial datasets within ArcCatalog Other metadata in Oracle (same database as GDB) Overview the Chester County GIS-T Geodatabase The final product …

12. GIS-T Surface Transportation Reference Network: The platform for the GIS-T Initially based on the ESRI/UNETRANS GIS-T model Consists of: Two feature classes (derived from a geometric network) o TRANSPORTATION_CENTERLINE (was SURFACE_TRAN_EDGE) o TRANSPORTATION_JUNCTIONS (was SURFACE_TRAN_JUNCTION) Oracle Tables directly related to one of the above feature classes Oracle Tables that constrain values for IDs, segment names, route assignment etc.

13. GIS-T Surface Transportation Reference Network: General Characteristics Serves as platform for almost all other GIS-T data Either as the 1) spatial reference for events linearly referenced to the transportation network or 2) the network-related tables that tie together the bulk of the GIS-T GDB attribute data. Unlike in the UNETRANS/ESRI GIS-T model, the network includes only a single feature class of all lines that represent the centerline of segments upon which travel can or does occur – regardless of transportation mode ( TRANSPORTATION_CENTERLINE feature class). o This approach provides sufficient flexibility to model a truly multi- modal system. (While the vast majority of transportation elements occur along and are referenced to the street network, it is just as important have the ability to seamlessly reference such items to a segment of any travel mode)

14. GIS-T Surface Transportation Reference Network: The GIS-T Centerline Whats different from the base ChesCo centerline? Accommodates all linear features that serve, have served or could serve surface transportation, regardless of travel mode. Segments are assigned to routes Segment and route IDs in accordance with regional standard for unique ID of by data-owner, area, travel mode, etc. oSecondary IDs relate back to County CL data and PennDOT segment data. Supports the PennDOT linear-referencing system (LRS) Ramps added as necessary M values applied for non-PennDOT segments to maintain Local LRS Feature dataset topological rules applied.

15. GIS-T Surface Transportation Reference Network: The GIS-T Centerline Segment Types The LU_TRANSPORT_EDGE_TYPE table presently permits five subtypes of segments: Street Rail (including inactive and/or abandoned if track still exists) Non-motorized path (bicycle/multi-use paths, trails, off-street sidewalks) Inactive corridor (utility rights-of-way, abandoned, greenways without formal paths …) Waterway routes (only recreational in Chester County)

16. Example of Topology applied (by subtype for streets) GIS-T Surface Transportation Reference Network: Topology of the GIS-T Network Essentially means that segments can only touch exactly at endpoints Additional topological rules guarantee that every segment endpoint is covered by a network junction point (and junction points cannot be coincident or exist elsewhere than the endpoints) to ensure: Network connectivity Topologically accurate base for LRS

17. GIS-T Surface Transportation Reference Network: The GIS-T Centerline Navigable waterway (miles from confluence of Brandywine Creek branches) Rail PennDOT street (NHS) Non NHS local street Trail Inactive corridor

18. GIS-T Surface Transportation Reference Network: The GIS-T Centerline Example of network connectivity for various travel modes: Note: No connection

19. High-resolution ortho- photos for spatial accuracy, topology, GIS-T Surface Transportation Reference Network: The GIS-T Centerline Examples of centerline accuracy for the non-street segments: Consistency with land parcel layer Non-motorized travel, schools – missing connections

20. [State FIPs Code]_[County Code]_[Municipality Code]_[Route ID]_[Segment ID]_[Mode Code]_[Data Agency Code] 42 for PA 15 for Chester County (from DOT) Format for Unique Identification of Segments From Route- naming Agency For Example: Segment 0030 of PennDOT Route 3063 in the PennDOT centerline file is uniquely identified as 42_15_3063_X_0030_ST_PD If applicable, otherwise X From Segment- naming Agency Whereas a corresponding segment from the Chester County centerline may have a unique ID of 2615 within the file, that translates into a global unique ID of 42_15_3063_X_2615_ST_CC GIS-T Surface Transportation Reference Network: The GIS-T Centerline Relating the centerline to other data:

21. Activities Administration Air Travel/Transport Analysis and Planning Assets Auxiliary Transportation Infrastructure Bridge and Tunnel Drainage Incidents Intersection Lighting Maintenance Metadata Parking PennDOT Supplemental Projects Rail Safety School Transportation Toll Road Traffic Operation Traffic Regulation Traffic Signal Transit Transportation ancillary Transportation Communication Transportation Electrical Transportation Infrastructure Transportation Network Geometry Transportation Reference Network Utilities Waterway Transportation Geodatabase Datasets:

22. Relationships Among Features and Tables Streetlights, Traffic Signals and Related !

24. Chester County LRS (Linear Referencing System (s) )

25. Multiple LRS options Supported by single underlying geometry SingleTransportation Centerline Feature Class PennDOT LRS AppliedLocal LRS AppliedOther LRS Applied Rail station, mile marker, other agency measures, etc: All Linearly-referenced data transformable among LRSs via common underlying geometry/ArcToolbox Hybrid LRS Applied? 1)Fully-segmented, all inclusive FC (allows segment-specific event reference) 2)FC dissolved by applicable route IDs after definition query is applied to extract only relevant segments (provides better performance) OR

26. Multiple LRS options Supported by single underlying geometry SingleTransportation Centerline Feature Class PennDOT LRS AppliedLocal LRS Applied PennDOT measures by NLF Local measures by local Route ID

27. Example of application of M-Values to Route West Bradfords Vermont Lane Route: Two segments – approx. 505 Route runs EB, but Westernmost segment runs WB

28. Activities Administration Air Travel/Transport Analysis and Planning Assets Auxiliary Transportation Infrastructure Bridge and Tunnel Drainage Incidents Intersection Lighting Maintenance Metadata Parking PennDOT Supplemental Projects Rail Safety School Transportation Toll Road Traffic Operation Traffic Regulation Traffic Signal Transit Transportation ancillary Transportation Communication Transportation Electrical Transportation Infrastructure Transportation Network Geometry Transportation Reference Network Utilities Waterway LRS vs. xy features … whos to know?

29. Applications

30. GIS-T Application forms allow access to the ArcSDE portion and/or the native–Oracle portion of the hybrid database, as well as special-purpose personal GDBs. ESRIs ArcObjects supports VB form development that allows customized spatial functionality. GIS-T Surface Transportation Reference Network: GIS-T Applications Example: General approach to GIS-T application development ArcObjects and VBA link spatial and non-spatial functionality

33. Same bridge by PennDOT data: LAT/LONG point 300 away from accurate line event. LAT/LONG point only … location accurate Integration of Bridge Data into the GIS-T 1)Translate PennDOT locations into accurate bridge centerpoints on GIS-T reference network. 2)Incorporate State and County data into the GIS-T database

34. GIS-T Bridge Application: Integration with Other GIS-T tools 1)General-purpose access to, and editing of all GIS-T data 2)Navigation of and info for transportation reference network 3)Bridge-specific tasks 4)Signal-specific tasks 5)Management of GIS-T pictures 6)Generalized functionality based on work done for the Bridges and Signals 7)ArcMap, ArcSDE enhancement GIS-T custom toolbar provides tools for

35. GIS-T Bridge Application: Example of quick display of basic bridge info

38. Integration of Signal Data into the GIS-T 1) cleanup and attribution of signal shapefile Redundant signal point locations Inaccurate Placement No Attribute Data Before Unique signal point locations Accurate Placement Basic Attribute Data After 2) Signal data consistent with GIS-T network, LRS and data structure

40. GIS EPZ (Emergency Planning Zone) Analysis application EPZ population, demographics Employment and school/daycare Employment by place of work Special facilities – such as schools and hospitals Other places of interest Residents locations Streets and intersections

41. Network connectivity : 100% network connectivity in the County and logical routes for travel just outside the county. Grade separated intersections : Elevation data for the beginning and end of each segment are used to reflect connectivity, or lack there of Oneway streets : (attributed by travel direction versus digitized direction) Impedance (based on Travel Speeds): These speeds may reflect free-flow conditions, or travel speeds that reflect congestion by time-of-day, location, direction, etc. Turning costs and restrictions : A Turn feature class defines prohibited turning movements and, potentially, turns that take a lot of time. Route Hierarchy : Classifying roads to favor major roads to produce simpler more intuitive real-world routes ChesCo Routable Network & Network Dataset … Future enhancements could include attribution for specific motor vehicle type and purpose (i.e. emergency vehicles, hazardous materials, school busses, bicycle, pedestrian routing, multi-modal trips, etc)

42. With ArcGIS Network Analyst or TransCAD, you can conduct Drive-time analysis Point-to-point routing Route directions Service area definition (incl. walk-to-school zones, etc.) Shortest path Optimum route Closest facility Origin-destination analysis Using the Network Dataset …

43. Prohibited Turn Routable Network Examples: Spatial & Attributes The Turns Feature Class One-way segments Grade separated intersections

44. Routable Network Examples: Routing Hierarchy

45. Routable Network Examples:

46. US 30/Bondsville Rd Interchange : Arrows depict digitized direction Sample of edits required for routable network Bondsville Rd US 30 (not needed for routable network, but also evaluate whether the short segments are valid/required) Replace with one node Split Bondsville Segment, relocate node Record Segment as one-way in the digitized direction (F) Record Segment as one-way in reverse of digitized direction (R) Record Segment as two-way (T) 1 2 3 2 2 2 2 3 3 3 3 1 1 1 1 1 1 3 1 1 Flag as Grade- Separated Replace with one node Edit for connectivity at single node Note: The one-way data for the segments should ensure proper routing in this case. However, turning restrictions (regulatory or geometric) will often have to be explicitly defined for a given intersection.