The UNETRANS Essential Data ModelThe UNETRANS Essential Data Model

CLEM 2001 Specialist MeetingCLEM 2001 Specialist Meeting

August 6-7, 2001August 6-7, 2001

Santa Barbara, CASanta Barbara, CA

Kevin M. CurtinKevin M. CurtinDepartment of Geography, University of California, Santa BarbaraDepartment of Geography, University of California, Santa Barbara

andand

National Center for Geographic Information and Analysis (NCGIA)National Center for Geographic Information and Analysis (NCGIA)

curtin@ncgia.ucsb.educurtin@ncgia.ucsb.edu

Presentation OutlinePresentation Outline

Introduction to the UNETRANS ProjectIntroduction to the UNETRANS Project– Goals and ObjectivesGoals and Objectives

– Process used to meet these goalsProcess used to meet these goals

Details of the UNETRANS Object ModelDetails of the UNETRANS Object Model– Analysis DiagramAnalysis Diagram

– Logical Groupings of Transportation Objects (Packages)Logical Groupings of Transportation Objects (Packages)

– Detailed Object descriptions and relationships (Reference Network)Detailed Object descriptions and relationships (Reference Network)

– Employing the UML to Build a GeodatabaseEmploying the UML to Build a Geodatabase

Relationship of the UNETRANS model to Centerline ExtractionRelationship of the UNETRANS model to Centerline Extraction– NetworksNetworks

– Multiple RepresentationsMultiple Representations

– Centerline, Carriageway, LaneCenterline, Carriageway, Lane

Products, Publications, and Future directionsProducts, Publications, and Future directions

UNETRANS Goals and ObjectivesUNETRANS Goals and Objectives

ESRI has undergone a major software revisionESRI has undergone a major software revision– Developing a set of Data Models for user groupsDeveloping a set of Data Models for user groups– The UNETRANS Data Model is one of a suite of data modelsThe UNETRANS Data Model is one of a suite of data models– http://www.http://www.ncgiancgia.ucsb.edu/vital/unetrans.ucsb.edu/vital/unetrans– http://http://arconlinearconline.esri.com/.esri.com/arconlinearconline//datamodelsdatamodels..cfmcfm

Develop an Essential Data Model for Transportation GIS usersDevelop an Essential Data Model for Transportation GIS users– NOT a comprehensive modelNOT a comprehensive model– Object Orientation plays a substantial role in this revisionObject Orientation plays a substantial role in this revision– Intended as a starting point for users to design their own specific data modelsIntended as a starting point for users to design their own specific data models– Focus on Road and Rail transport with hooks for water and air transportFocus on Road and Rail transport with hooks for water and air transport– The model must not constrain any user – not a standardThe model must not constrain any user – not a standard

Provide a Suite of ProductsProvide a Suite of Products– Analysis DiagramAnalysis Diagram– Data Model Reference DocumentData Model Reference Document– Sample Data SetsSample Data Sets– UML ModelUML Model– Transportation Data Modeling Reference BookTransportation Data Modeling Reference Book

Modeling Transportation Users View of DataModeling Transportation Users View of Data

What is the essential data model?What is the essential data model?– Top-Down ApproachTop-Down Approach

» Initial Specialist Meeting – San Diego, CAInitial Specialist Meeting – San Diego, CA

» Review of Data ModelsReview of Data Models TOPS, TLOS, ESRI StreetMap, NCHRP 20-27 (2) and (3)TOPS, TLOS, ESRI StreetMap, NCHRP 20-27 (2) and (3)

» European Consultation – Turin, ItalyEuropean Consultation – Turin, Italy

» Development of Draft UML ModelDevelopment of Draft UML Model

» Stakeholders Meeting – Redlands, CAStakeholders Meeting – Redlands, CA

» Development of Data Model Reference Document and Sample Data setDevelopment of Data Model Reference Document and Sample Data set

» Second Specialist Meeting – San Diego, CASecond Specialist Meeting – San Diego, CA

– Bottom-Up ApproachBottom-Up Approach» Review of Transportation LiteratureReview of Transportation Literature

GDF GDF GeoNET (Dueker-Butler) GeoNET (Dueker-Butler) NCGIA publications 96-3 and 94-6 NCGIA publications 96-3 and 94-6 NCHRP 20-27(2) reports #218 and #221 NCHRP 20-27(2) reports #218 and #221 NSDI Framework Transportation Feature Identification Standard NSDI Framework Transportation Feature Identification Standard Pavement Management ModelPavement Management Model

Identifying the Essential ObjectsIdentifying the Essential Objects

Link Link Local Link Local Link Transport EdgeTransport Edge Arc Arc Linear Object Linear Object Network Feature Network Feature LineLine Road Road Street Street RoadwayRoadway Rail Line / Track Rail Line / Track Airport Runway Airport Runway Aggregated Way Aggregated Way LaneLane Road ElementRoad Element HOV Lane HOV Lane Anchor Section Anchor Section Segment Segment

Bridge Bridge Tunnel Tunnel Node Node Local NodeLocal Node IntersectionIntersection JunctionJunction Grade Separated CrossingGrade Separated Crossing BrunnelBrunnel Traffic SquareTraffic Square Water Boundary JunctionWater Boundary Junction Boundary JunctionBoundary Junction Rail Start / EndRail Start / End Ferry Connection Ferry Connection Public Transport JunctionPublic Transport Junction Rail JunctionRail Junction Inspection FacilityInspection Facility Support FacilitySupport Facility Transfer FacilityTransfer Facility

VehicleVehicle Complex VehicleComplex Vehicle FleetFleet AutomobileAutomobile PedestrianPedestrian TruckTruck BusBus FerryFerry BicycleBicycle Emergency VehicleEmergency Vehicle TravelerTraveler RailcarRailcar CargoCargo Railway Railway AirlineAirline Mobile HomeMobile Home

Identifying the Essential Transportation FunctionsIdentifying the Essential Transportation Functions

Data Maintenance Data Maintenance Attribute UpdateAttribute Update Feature Replacement Feature Replacement Electronic Payment Electronic Payment Address Matching Address Matching Demand Modeling Demand Modeling Update Street InventoryUpdate Street Inventory Create New Segment (Split / Join)Create New Segment (Split / Join) Sort SegmentsSort Segments Identify Candidate SegmentsIdentify Candidate Segments Retrieve SegmentRetrieve Segment Survey Pavement ConditionsSurvey Pavement Conditions Rank Potential ProjectsRank Potential Projects Estimate Cost of ProjectsEstimate Cost of Projects Identify Project CollisionsIdentify Project Collisions Construction Project PlanningConstruction Project Planning Project Compliance MonitoringProject Compliance Monitoring Project Progress TrackingProject Progress Tracking Final Project ApprovalFinal Project Approval Policy Development Policy Development Strategic Plan DevelopmentStrategic Plan Development Document ManagementDocument Management Information Resource ManagementInformation Resource Management Business Plan DevelopmentBusiness Plan Development

RoutingRouting Dynamic Routing Dynamic Routing Route GuidanceRoute Guidance Route PlanningRoute Planning Trip PlanningTrip Planning Traffic ManagementTraffic Management NavigationNavigation Automated Vehicle Operation Automated Vehicle Operation Collision AvoidanceCollision Avoidance Emergency Vehicle Management Emergency Vehicle Management Automated Collision Notification Automated Collision Notification Public Transport Management Public Transport Management Commercial Fleet Management Commercial Fleet Management On-board Safety Monitoring On-board Safety Monitoring Traffic ControlTraffic Control Commercial Vehicle Commercial Vehicle

AdministrationAdministration Automated Vehicle IdentificationAutomated Vehicle Identification Incident ManagementIncident Management Travel Demand ManagementTravel Demand Management Travel Demand ForecastingTravel Demand Forecasting Traffic FlowTraffic Flow Ride MatchingRide Matching Positioning Positioning SignalingSignaling

Space ManagementSpace Management Building and Grounds Management Building and Grounds Management Real Property Management Real Property Management Capital Equipment Management Capital Equipment Management Human Resources Development Human Resources Development Plan and Standards Approval Plan and Standards Approval Public Information Planning Public Information Planning Engineering Impact Evaluation Engineering Impact Evaluation Alternate Impact Evaluation Alternate Impact Evaluation Contract ManagementContract Management Monitoring Work In ProgressMonitoring Work In Progress Legal ServicesLegal Services Driver RegulationDriver Regulation BudgetingBudgeting Financial ServicesFinancial Services AuditingAuditing External Data SharingExternal Data Sharing Revenue ForecastingRevenue Forecasting Weather Operation Weather Operation Incident ResponseIncident Response Permit IssuingPermit Issuing Vehicle RegulationVehicle Regulation Transportation System Law Transportation System Law

EnforcementEnforcement

Modeling Transportation Users View of DataModeling Transportation Users View of Data

What is the essential data model?What is the essential data model?– Top-Down ApproachTop-Down Approach

» Initial Specialist Meeting – San Diego, CAInitial Specialist Meeting – San Diego, CA» Review of Data ModelsReview of Data Models

TOPS, TLOS, ESRI StreetMap, NCHRP 20-27 (2) and (3)TOPS, TLOS, ESRI StreetMap, NCHRP 20-27 (2) and (3)

» European Consultation – Turin, ItalyEuropean Consultation – Turin, Italy» Development of Draft UML ModelDevelopment of Draft UML Model» Stakeholders Meeting – Redlands, CAStakeholders Meeting – Redlands, CA» Development of Data Model Reference Document and Sample Data setDevelopment of Data Model Reference Document and Sample Data set» Second Specialist Meeting – San Diego, CASecond Specialist Meeting – San Diego, CA

– Bottom-Up ApproachBottom-Up Approach» Review of Transportation LiteratureReview of Transportation Literature

GDF GDF GeoNET (Dueker-Butler) GeoNET (Dueker-Butler) NCGIA publications 96-3 and 94-6 NCGIA publications 96-3 and 94-6 NCHRP 20-27(2) reports #218 and #221 NCHRP 20-27(2) reports #218 and #221 NSDI Framework Transportation Feature Identification Standard NSDI Framework Transportation Feature Identification Standard Pavement Management ModelPavement Management Model

– Reached a ConsensusReached a Consensus

Analysis Diagram - PackagesAnalysis Diagram - Packages

Assets

LocationReferencing

Reference Network

IncidentsActivitiesMobileObjects

Routing

Street NamesAddressRanges

Package DefinitionsPackage Definitions

Reference NetworkReference Network– A representation of physical, semi-permanent infrastructure features intended to facilitate a A representation of physical, semi-permanent infrastructure features intended to facilitate a

channeling or control of trafficchanneling or control of traffic Street Names and Address RangesStreet Names and Address Ranges

– Attribute objects associated with one or many objects from the Reference NetworkAttribute objects associated with one or many objects from the Reference Network Location ReferencingLocation Referencing

– Objects and procedures for associating transportation relatedObjects and procedures for associating transportation related RoutingRouting

– Primarily tabular related data needed to support transportation planning processesPrimarily tabular related data needed to support transportation planning processes Assets, Activities, Incidents Assets, Activities, Incidents

– A representation of physical features, planned projects, and unplanned occurrences which are A representation of physical features, planned projects, and unplanned occurrences which are located in reference to Reference Network, but are not part of the network itself.located in reference to Reference Network, but are not part of the network itself.

Mobile ObjectsMobile Objects– An object representing any type of medium through which people or commodities are An object representing any type of medium through which people or commodities are

transported along the Reference Network.transported along the Reference Network.

Reference Network Package DetailsReference Network Package Details

TransportEdge

TransportEdgeIDFTSegmentIDSourceTransportModeDisplayClassSpeedClassCapacityDesignDateConstructionDateInServiceDateOutOfServiceDateUpdateTimestampLifecycleStatusDescriptionSubtypeField

RoadRailWaterEdge BicyclePath WalkingPath

TransportJunction

TransportJunctionIDFTReferencePointIDSourceDisplayClassCapacityImpedanceDesignDateConstructionDateInServiceDateOutOfServiceDateUpdateTimestampLifecycleStatusDescriptionSubtypeField

Brunnel

Intersection Station

DividedSurfaceCarriagewaysLanesSlope

TotalTracksSlopeGauge

TotalPathsSeparated

TotalPathsType

MinDepth

FunctionalClassOnewayMinWidthMinHeightMaxWeightVerticalLevelVehicleLengthRestrictionToFromImpedanceFromToImpedanceDetailedRoutingModes[n]

RoutableEdge

IntersectionIDControlType

TrainStationBusStation

PortCloverLeaf TransferPoint

StationIDAgency

Rotary

FourWayStop

<<Geometric Network>>ReferenceGN

ComplexEdgeFeature

SimpleJunctionFeature

FunctionalClasses for Roads

are:Carriageway

DividedHighwayRampOther

Reference Network Details 2Reference Network Details 2

TransportEdgeTransportEdge– Geometric and/or Logical network featureGeometric and/or Logical network feature– Corresponds to arc, link, edge, segment, roadway, street…Corresponds to arc, link, edge, segment, roadway, street…– May be a complex or a simple edge featureMay be a complex or a simple edge feature– Can be used for rendering or analysis or bothCan be used for rendering or analysis or both– Subtypes can be created for any fundamentally unique Edge TypeSubtypes can be created for any fundamentally unique Edge Type

» RoadRoad» RailRail» WaterwaysWaterways» Shipping LanesShipping Lanes» Bike PathsBike Paths» Etc….Etc….

Reference Network Details 3Reference Network Details 3

TransportJunctionsTransportJunctions– Correspond to terms such as node, Correspond to terms such as node,

point, intersection…point, intersection…

– The Object Model allows us a great The Object Model allows us a great deal more flexibility to handle a lot of deal more flexibility to handle a lot of difficult cases that come up at Junctionsdifficult cases that come up at Junctions

– Consider that many intersection in any Consider that many intersection in any given dataset can have identical given dataset can have identical properties.properties.

» All junctions with those properties can All junctions with those properties can be of that TransportJunction Typebe of that TransportJunction Type

» One need only record the type of One need only record the type of junction rather than repeat all of the junction rather than repeat all of the behavioral definitions for each behavioral definitions for each intersection.intersection.

» Even more complex junctions Even more complex junctions (brunnels) appear frequently enough to (brunnels) appear frequently enough to benefit from this structurebenefit from this structure

Other Packages - RelationshipsOther Packages - Relationships

TransportEdge - RoutesHaveEdges - TransportRoute TransportEdge - RoutesHaveEdges - TransportRoute TransportEdge -LinearAlong - LinearAsset TransportEdge -LinearAlong - LinearAsset TransportEdge - PointAlong - PointAsset TransportEdge - PointAlong - PointAsset TransportEdge - Turn – TransportEdgeTransportEdge - Turn – TransportEdge StreetName – StreetNameHasRoads – RoadStreetName – StreetNameHasRoads – Road Road – RoadHasAddressRanges – AddressRangeRoad – RoadHasAddressRanges – AddressRange

-Divided : BooleanInt = 0-Surface : esriFieldTypeInteger = 0-Slope : esriFieldTypeDouble = 0-TotalLanes : esriFieldTypeInteger = 2-CarriageWays : esriFieldTypeInteger = 1-StreetNameID : esriFieldTypeString-FunctionalClass : RoadFuncClasses = Carriageway

Reference Network::Road

-AddressRangeID : esriFieldTypeString-LowAddress : esriFieldTypeInteger-HighAddress : esriFieldTypeInteger-SideofStreet : esriFieldTypeString-SequenceNumber : esriFieldTypeInteger-FromMeasure : esriFieldTypeDouble = 0-ToMeasure : esriFieldTypeDouble = 100-SegmentID : esriFieldTypeString-CartoOffset1 : esriFieldTypeDouble = 5

Street Objects::AddressRange

-Road1

-AddressRange*

RoadHasAddressRanges

Other Packages – DomainsOther Packages – Domains

Coded Value DomainsCoded Value Domains– Speed ClassSpeed Class

– Truck TypeTruck Type

– Functional ClassFunctional Class

– Lane TypeLane Type

– Asset ConditionAsset Condition

– Boolean StringBoolean String

– Boolean IntegerBoolean Integer

– Census Feature Classification CodeCensus Feature Classification Code

Facilitates standardization and data sharingFacilitates standardization and data sharing Helps to discourage attribute errorHelps to discourage attribute error

+ThroughLane : esriFieldTypeInteger = 1+RightTurnLane : esriFieldTypeInteger = 2+LeftTurnLane : esriFieldTypeInteger = 3+CenterTurnLane : esriFieldTypeInteger = 4+HOVLane : esriFieldTypeInteger = 5+EmergencyVehicleLane : esriFieldTypeInteger = 6

«CodedValueDomain»LaneType

What’s the UML Look Like?What’s the UML Look Like?

-Divided = 0-Surface = 0-Slope = 0-TotalLanes = 2-CarriageWays = 1-StreetNameID-FunctionalClass = Carriageway

Road

-Separated = 1

BicyclePath

-Covered = 1

WalkingPath

-TotalTracks = 1-Gauge-FunctionalClass

Rail

-SubtypeField = 1

BusStation

-SubtypeField = 1

Brunnel

-SubtypeField = 5

CloverLeaf

-MinDepth

WaterEdge

Subtype

-NetworkType : esriNetworkType = esriNTUtilityNetwork

«GeometricNetwork»ReferenceGN

-TransportEdgeID : esriFieldTypeString-FTSegmentID : esriFieldTypeString-SourceID : esriFieldTypeString-TransportMode : esriFieldTypeInteger-DisplayClass : esriFieldTypeInteger-SpeedClass : UNETRANSSpeedClass-Capacity : esriFieldTypeInteger-DesignDate : esriFieldTypeDate-ConstructionDate : esriFieldTypeDate-InServiceDate : esriFieldTypeDate-OutOfServiceDate : esriFieldTypeDate-UpdateTimestamp : esriFieldTypeDate-LifecycleStatus : LifecycleStatus = Active-Description : esriFieldTypeString

TransportEdge

-TransportJunctionID : esriFieldTypeString-FTReferencePointID : esriFieldTypeString-SourceID : esriFieldTypeString-DisplayClass : esriFieldTypeInteger-Capacity : esriFieldTypeInteger-Impedance : esriFieldTypeInteger-DesignDate : esriFieldTypeDate-ConstructionDate : esriFieldTypeDate-InServiceDate : esriFieldTypeDate-OutOfServiceDate : esriFieldTypeDate-UpdateTimestamp : esriFieldTypeDate-LifeCycleStatus : LifecycleStatus = Active-Description : esriFieldTypeString-SymbolRotation : esriFieldTypeDouble = 0«SubtypeField» -SubtypeField : esriFieldTypeInteger

TransportJunction

ESRI Classes::SimpleJunctionFeature

ESRI Classes::ComplexEdgeFeature

-OneWay : BooleanInt = 0-MinWidth : esriFieldTypeDouble-MinHeight : esriFieldTypeDouble-MaxWeight : esriFieldTypeDouble-VerticalLevel : esriFieldTypeInteger-VehicleLengthRestriction : esriFieldTypeDouble-ToFromImpedance : esriFieldTypeDouble = 0-FromToImpedance : esriFieldTypeDouble = 0-DetailedRoutingModes : esriFieldTypeDouble

RouteableEdge

Reference Network

-IntersectionID : esriFieldTypeString-ControlType : esriFieldTypeInteger = 6

Intersection

-StationID : esriFieldTypeString-Agency : esriFieldTypeString

Station

-SubtypeField = 2

AllWayStop

-SubtypeField = 4

Rotary

Subtype

-SubtypeField = 2

TrainStation

-SubtypeField = 3

Port

-SubtypeField = 4

TransferPoint

-SubtypeField = 3

TwoWayStop

-SubtypeField = 6

Controlled

-SubtypeField = 7

UnControlled

Using the UMLUsing the UML

Plan your GeodatabasePlan your Geodatabase– Use the Analysis Diagram as a templateUse the Analysis Diagram as a template– Define your goals and data needsDefine your goals and data needs

In Visio modify the UML to meet In Visio modify the UML to meet your needsyour needs

– OOADOOAD– Add, delete, or modify objectsAdd, delete, or modify objects– Add attribute definitionsAdd attribute definitions

Export from Visio to a Microsoft Export from Visio to a Microsoft RepositoryRepository

In ArcCatalog generate an empty In ArcCatalog generate an empty schema from the Repositoryschema from the Repository

– Placeholders for your dataPlaceholders for your data Load your data into the Load your data into the

GeodatabaseGeodatabase

VISIOMicrosoftRepository

Transportation Analysis and PlanningTransportation Analysis and Planning

UNETRANS and Centerline ExtractionUNETRANS and Centerline Extraction

NetworksNetworks– Topology is mandatoryTopology is mandatory

Multiple RepresentationsMultiple Representations– Assets, Incidents, ActivitiesAssets, Incidents, Activities

– Reference NetworksReference Networks» Single CenterlinesSingle Centerlines

» Double Centerlines (Carriageways)Double Centerlines (Carriageways)

» LanesLanes

» CAD Generated DrawingsCAD Generated Drawings

How to ProceedHow to Proceed

Develop applications and use casesDevelop applications and use cases Test the model’s ability to satisfy the needs of those applicationsTest the model’s ability to satisfy the needs of those applications Continue to iterate through the modeling process in order to make Continue to iterate through the modeling process in order to make

improvements to the model based on the test resultsimprovements to the model based on the test results– AttributesAttributes

Publish the ResultsPublish the Results– WebsitesWebsites

– Reference DocumentReference Document» Object Data DictionaryObject Data Dictionary

» UML SamplesUML Samples

» Cross-references to existing standards and other data modelsCross-references to existing standards and other data models

– Transportation Data Modeling BookTransportation Data Modeling Book

– CD with Sample Data Sets and ApplicationsCD with Sample Data Sets and Applications