15 yrs ago GIS own specialty, no real integration with TE10 yrs ago just for mapping purposes, end result graphicsLRS = 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
Presentation to the ESRI Transportation Special Interest
GroupFebruary 19th, 2008
Linear Referencing Systems: Focus on County-level Usage
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 GroupFebruary 19th, 2008
Linear Referencing Systems: Focus on County-level Usage
GIS
TransportationPlanning/
Engineering
TraditionalDatabase
Computer Application
s
The evolution of GIS-T: 15 years ago …
GIS own specialty, no real integration with TE
GIS
TransportationPlanning/
Engineering
TraditionalDatabase
Computer Application
s
The evolution of GIS-T: 10 years ago …
GIS
TransportationPlanning/
Engineering
TraditionalDatabase
Computer Applications
The evolution of GIS-T: 5 years ago …
Internet GIS(-T)
Internet GIS(-T)
GIS
TraditionalDatabase
Computer Applications
The evolution of GIS-T: Now …
Many related applications and datasetsWeb applications = GIS-T that people don’t know is GIS-T
TransportationPlanning/
Engineering
The Chester County GIS-T
Presented by Gerry Kelly Feb. 19, 2008
PennDOT Data
ChesCoGIS Street Centerline
Significant & consistent transportation-related data Largely limited to State Rd system (about one-third County’s approx. 4500 road-miles) Based on PennDOT’s linear referencing system (LRS)PennDOT
Street Centerline
Overview the Chester County GIS-T Geodatabase
ChesCoOther 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 ChesCoGIS Data
Multi-modal GIS-T TRANSPORTATION_NETWO
RK
+ a lot of work =
The data: What went in the GDB, Where’d it come from?
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 …
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.
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)
GIS-T Surface Transportation Reference Network:
The GIS-T Centerline
What’s 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.
o Secondary 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.
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)
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 endpointsAdditional 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
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
GIS-T Surface Transportation Reference Network:
The GIS-T Centerline
Example of network connectivity for various travel modes:
Note: No connection
High-resolution ortho-photos for spatial
accuracy, topology,
GIS-T Surface Transportation Reference Network: The GIS-T CenterlineExamples of centerline accuracy for the non-street segments:
Consistency with land parcel layer
Non-motorized travel, schools – missing connections
[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 CenterlineRelating the centerline to other data:
ActivitiesAdministrationAir Travel/TransportAnalysis and PlanningAssetsAuxiliary Transportation InfrastructureBridge and TunnelDrainageIncidentsIntersectionLightingMaintenanceMetadataParkingPennDOT SupplementalProjects
RailSafetySchool TransportationToll RoadTraffic OperationTraffic RegulationTraffic Signal TransitTransportation ancillaryTransportation CommunicationTransportation ElectricalTransportation InfrastructureTransportation Network GeometryTransportation Reference NetworkUtilitiesWaterway
Transportation Geodatabase Datasets:
Relationships Among Features and Tables
Streetlights, Traffic Signals and Related
!
Gas_Company_Data
PK Gas_Company_ID
NameDescriptioncomment1comment2
Gas_Pipe_Segment
PK,FK1 Gas_Pipe_ID
FK2,I1 Gas_System_IDcomment1comment2Overhead_or_Underground
Gas_System_Data
PK Gas_System_ID
FK1,I1 Gas_Company_IDNameDescriptioncomment1comment2
TBL_Gas_Companies_Polygon_FC
PK Companies_Representation_ID
FK1,I2,I1 Gas_Company_IDPhysical_Boundary_y_nServed_Area_y_nPotential_Area_y_nJurisdictional_Boundary_n_y
TBL_Gas_Systems_Polygon_FC
PK System_Representation_ID
FK1,I2,I1 Gas_System_IDPhysical_Boundary_y_nServed_Area_y_nPotential_Area_y_n
TBL_Sewer_Authority_Polygon_FC
PK Authority_Representation_ID
FK1,I2,I1 Sewer_Authority_IDPhysical_Boundary_y_nServed_Area_y_nPotential_Area_y_nJurisdictional_Boundary_n_y
TBL_Sewer_Systems_Polygon_FC
PK System_Representation_ID
FK1,I2,I1 Sewer_System_IDPhysical_Boundary_y_nServed_Area_y_nPotential_Area_y_n
Sewer_Authority_Data
PK Sewer_Authority_ID
I1 NameDescriptioncomment1comment2
Sewer_Pipe_Segment
PK,FK1 Sewer_Pipe_ID
FK2,I1 Sewer_System_IDcomment1comment2Overhead_or_Underground
Sewer_System_Data
PK Sewer_System_ID
FK1,I2,I1 Sewer_Authority_IDNameDescriptioncomment1comment2
Pipeline_Data
PK,FK1 Pipeline_ID
Material_Transportedcomment1comment2Overhead_or_Underground
Asset_Line_Data
PK AssetID
FK2,I2 OwnerDesignDateConstructionDateInServiceDateOutOfServiceDateConditionLifecycleStatusSubtypeFieldJunction_IDLocation_Data_SourceLocation_DescriptionVertical_Level
FK1,I1 Enclosed_Area_IDOther_Asset_Description
FK4,I4 Shared_ByFK3,I3 Maintained_By_Agency
Maintained_By_ContractorLast_Inspection_DateScheduled_Replace_DateScheduled_Remove_DateScheduled_Modify_DateLast_Modify_DateSchedule_Maintenance_DateLast_Maintenance_DateLocal_IDResponsible_partyInput_ByInput_Date
Asset_Line_LRS
PK,FK1 AssetID
FK2,I1 Transport_Route_IDFromMeasureToMeasureLateral_OffsetAssets_Lateral_Offset_Reference
TBL_Asset_Line_NonLRS
PK,FK1 AssetID
FK2,I2,I1 Transport_Route_ID
Drainage_Pipes_and_Culverts
PK,FK1 Pipe_Or_Culvert_ID
Pipe_Or_CulvertOverhead_or_Undergroundcomment1comment2
Drainage_Inlet
PK,FK1 Drainage_Inlet_ID
FK2,I1 Pipe_or_Culvert_IDFK4,I3 Sewer_Pipe_Segment_IDFK5,I4 Sewer_System_IDFK3,I2 Sewer_Authority_ID
comment1comment2
TBL_Asset_Polygon
PK,FK1 Asset_ID
Asset_Polygon_Data
PK Asset_ID
Parcel_IDParcel_Note
FK1,I1 OwnerFK3,I3 Shared_By
DesignDateConstructionDateInServiceDateOutOfServiceDateConditionLifecycleStatusSubtypeFieldLocation_Data_SourceLocation_Description
FK2,I2 Maintained_By_AgencyMaintained_By_ContractorLast_Inspection_DateScheduled_Replace_DateScheduled_Remove_DateScheduled_Modify_DateLast_Modify_DateSchedule_Maintenance_DateLast_Maintenance_DateLocal_IDFacility_Phone_NumbersResponsible_partyInput_ByInput_Date
Wire_and_Cable_Segments
PK,FK1 Wire_ID
Unknown_Type_y_nElectric_y_nCATV_y_nTelephone_y_nOther_Communcation_y_nOther_Communcation_Describecomment1comment2Overhead_or_UndergroundHeight_Overhead
Water_Pipe_Segment
PK,FK1 Water_Pipe_ID
FK2,I1 Water_System_IDcomment1comment2Overhead_or_Underground
Water_Provider_Data
PK Water_Provider_ID
NameDescriptioncomment1comment2
Water_System_Data
PK Water_System_ID
FK1,I1 Water_Provider_IDNameDescriptioncomment1comment2
TBL_Water_Providers_Polygon_FC
PK Provider_Representation_ID
FK1,I2,I1 Water_Provider_IDPhysical_Boundary_y_nServed_Area_y_nPotential_Area_y_nJurisdictional_Boundary_n_y
TBL_Water_Systems_Polygon_FC
PK System_Representation_ID
FK1,I1,I2 Water_System_IDPhysical_Boundary_y_nServed_Area_y_nPotential_Area_y_n
Electrical_Circuit_Data
PK Circuit_ID
NameService_Point_IDDescriptionComments
Electrical_Circuit_Segments
PK,FK1 Circuit_Segment_ID
FK2,I1 Circuit_IDOverhead_or_UndergroundDescriptionComments
Electrical_Service_Points
PK,FK1 Service_Point_ID
FK2,I1 Electrical_Circuit_IDLocation_DescriptionCommentsOverhead_or_Underground
Asset_Point_Data
PK,I5 AssetID
FK1,I1,I4 Asset_Support_IDFK8,I10 Owner
DesignDateConstructionDateInServiceDateOutOfServiceDateConditionLifecycleStatusSubtypeField
FK4,I6 Transport_Edge_IDFK3,FK5,I7 Junction_ID
Location_Data_SourceLocation_DescriptionVertical_Level
FK2,I2,I3 Enclosed_Area_IDOther_Asset_Description
FK6,I8 Shared_ByFK7,I9 Maintained_By_Agency
Maintained_By_ContractorLast_Inspection_DateScheduled_Replace_DateScheduled_Remove_DateScheduled_Modify_DateLast_Modify_DateSchedule_Maintenance_DateLast_Maintenance_DateLocal_IDResponsible_partyInput_ByInput_Date
Asset_Point_LRS
PK,FK1,I1 AssetID
FK2,I2 Transport_Edge_IDPointMeasureLateral_Offset
TBL_Asset_Point_NonLRS
PK,FK1 AssetID
FK2,I2,I1 Transport_Edge_ID
See Asset Dataset Diagrams for Asset tablerelationships with the reference network.
See Asset Dataset Diagrams for Asset tablerelationships with the reference network.
See Asset Dataset Diagrams forAsset table relationships withthe reference network.
Communication_Circuit_Data
PK Circuit_ID
NameService_Point_IDDescriptionComments
Communication_Circuit_Segments
PK,FK2 Circuit_Segment_ID
FK1,I1 Circuit_IDDescriptionCommentsOverhead_or_Underground
Communication_Service_Points
PK,FK1 Service_Point_ID
FK2,I1 Communication_Circuit_IDLocation_DescriptionCommentsOverhead_or_Underground
Utilities DatasetWater Sewer Gas
Drainage
Electrical(Related to the
Transportation System)
Communications(Related to the
Transportation System)
Uncategorized Electrical and
Communication wire and cable (i.e. wire/cable
that may lie along or near the transportation system, butis not otherwise related to transportation)
The records of these tables correspondwith polygonal features in ArcSDE-managed feature classes as indicated.Referential integrity is enforced bydatabase triggers. See documentation.
Feature classWater_Providers_Polygon_FCWater_Provider_ID (1:1 related field)
Feature classSewer_Systems_Polygon_FCSewer_Systems_ID (1:1 related field)
Feature classWater_Systems_Polygon_FCWater_Systems_ID (1:1 related field)
Feature classSewer_Authority_Polygon_FCSewer_Authority_ID (1:1 related field)
Feature classGas_Companies_Polygon_FCGas_Companies_ID (1:1 related field)
Feature classGas_Systems_Polygon_FCGas_Systems_ID (1:1 related field)
G SChester County LRS
(Linear Referencing System(s))
Multiple LRS optionsSupported 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
Hybrid LRS Applied?
1) Fully-segmented, all inclusive FC (allows segment-specific event reference)
2) FC “dissolved” by applicable route ID’s after definition query is applied to extract only relevant segments (provides better performance)
OR
Multiple LRS optionsSupported by single underlying geometry
Single “Transportation
Centerline” Feature Class
PennDOT LRS Applied Local LRS Applied
PennDOT measures by NLF
Local measures by local Route ID
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
ActivitiesAdministrationAir Travel/TransportAnalysis and PlanningAssetsAuxiliary Transportation InfrastructureBridge and TunnelDrainageIncidentsIntersectionLightingMaintenanceMetadataParkingPennDOT SupplementalProjects
RailSafetySchool TransportationToll RoadTraffic OperationTraffic RegulationTraffic Signal TransitTransportation ancillaryTransportation CommunicationTransportation ElectricalTransportation InfrastructureTransportation Network GeometryTransportation Reference NetworkUtilitiesWaterway
LRS vs. xy features … who’s to know?
G SApplications
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 GDB’s.
ESRI’s ArcObjects supports VB form development that allows customized spatial functionality.
GIS-T Surface Transportation Reference Network: GIS-T ApplicationsExample: General approach to GIS-T application development
ArcObjects and VBA link spatial and non-spatial functionality
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
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
GIS-T Bridge Application: Example of quick display of basic bridge info
Integration of Signal Data into the GIS-T1) 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
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 interestResident’s locationsStreets and intersections
• 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)
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 …
Prohibited Turn
Routable Network Examples: Spatial & Attributes
The Turns Feature Class
One-way segmentsGrade separated intersections
Routable Network Examples: Routing Hierarchy
Routable Network Examples:
US 30/Bondsville Rd Interchange:Arrows depict digitized direction
Sample of edits required for routable network
Bon
dsvi
lle R
d
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
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.
G S