The UNETRANS Essential Data Model CLEM 2001 Specialist Meeting August 6-7, 2001 Santa Barbara, CA Kevin M. Curtin Department of Geography, University of California, Santa Barbara and National Center for Geographic Information and Analysis (NCGIA)

Presentation Outline n Introduction to the UNETRANS Project –Goals and Objectives –Process used to meet these goals n Details of the UNETRANS Object Model –Analysis Diagram –Logical Groupings of Transportation Objects (Packages) –Detailed Object descriptions and relationships (Reference Network) –Employing the UML to Build a Geodatabase n Relationship of the UNETRANS model to Centerline Extraction –Networks –Multiple Representations –Centerline, Carriageway, Lane n Products, Publications, and Future directions

UNETRANS Goals and Objectives n ESRI has undergone a major software revision –Developing a set of Data Models for user groups –The UNETRANS Data Model is one of a suite of data models – – n Develop an Essential Data Model for Transportation GIS users –NOT a comprehensive model –Object Orientation plays a substantial role in this revision –Intended 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 transport –The model must not constrain any user – not a standard n Provide a Suite of Products –Analysis Diagram –Data Model Reference Document –Sample Data Sets –UML Model –Transportation Data Modeling Reference Book

Modeling Transportation Users View of Data n What is the essential data model? –Top-Down Approach »Initial Specialist Meeting – San Diego, CA »Review of Data Models n TOPS, TLOS, ESRI StreetMap, NCHRP (2) and (3) »European Consultation – Turin, Italy »Development of Draft UML Model »Stakeholders Meeting – Redlands, CA »Development of Data Model Reference Document and Sample Data set »Second Specialist Meeting – San Diego, CA –Bottom-Up Approach »Review of Transportation Literature n GDF n GeoNET (Dueker-Butler) n NCGIA publications 96-3 and 94-6 n NCHRP 20-27(2) reports #218 and #221 n NSDI Framework Transportation Feature Identification Standard n Pavement Management Model

Identifying the Essential Objects n Link n Local Link n Transport Edge n Arc n Linear Object n Network Feature n Line n Road n Street n Roadway n Rail Line / Track n Airport Runway n Aggregated Way n Lane n Road Element n HOV Lane n Anchor Section n Segment n Bridge n Tunnel n Node n Local Node n Intersection n Junction n Grade Separated Crossing n Brunnel n Traffic Square n Water Boundary Junction n Boundary Junction n Rail Start / End n Ferry Connection n Public Transport Junction n Rail Junction n Inspection Facility n Support Facility n Transfer Facility n Vehicle n Complex Vehicle n Fleet n Automobile n Pedestrian n Truck n Bus n Ferry n Bicycle n Emergency Vehicle n Traveler n Railcar n Cargo n Railway n Airline n Mobile Home

Identifying the Essential Transportation Functions n Data Maintenance n Attribute Update n Feature Replacement n Electronic Payment n Address Matching n Demand Modeling n Update Street Inventory n Create New Segment (Split / Join) n Sort Segments n Identify Candidate Segments n Retrieve Segment n Survey Pavement Conditions n Rank Potential Projects n Estimate Cost of Projects n Identify Project Collisions n Construction Project Planning n Project Compliance Monitoring n Project Progress Tracking n Final Project Approval n Policy Development n Strategic Plan Development n Document Management n Information Resource Management n Business Plan Development n Routing n Dynamic Routing n Route Guidance n Route Planning n Trip Planning n Traffic Management n Navigation n Automated Vehicle Operation n Collision Avoidance n Emergency Vehicle Management n Automated Collision Notification n Public Transport Management n Commercial Fleet Management n On-board Safety Monitoring n Traffic Control n Commercial Vehicle Administration n Automated Vehicle Identification n Incident Management n Travel Demand Management n Travel Demand Forecasting n Traffic Flow n Ride Matching n Positioning n Signaling n Space Management n Building and Grounds Management n Real Property Management n Capital Equipment Management n Human Resources Development n Plan and Standards Approval n Public Information Planning n Engineering Impact Evaluation n Alternate Impact Evaluation n Contract Management n Monitoring Work In Progress n Legal Services n Driver Regulation n Budgeting n Financial Services n Auditing n External Data Sharing n Revenue Forecasting n Weather Operation n Incident Response n Permit Issuing n Vehicle Regulation n Transportation System Law Enforcement

Modeling Transportation Users View of Data n What is the essential data model? –Top-Down Approach »Initial Specialist Meeting – San Diego, CA »Review of Data Models n TOPS, TLOS, ESRI StreetMap, NCHRP (2) and (3) »European Consultation – Turin, Italy »Development of Draft UML Model »Stakeholders Meeting – Redlands, CA »Development of Data Model Reference Document and Sample Data set »Second Specialist Meeting – San Diego, CA –Bottom-Up Approach »Review of Transportation Literature n GDF n GeoNET (Dueker-Butler) n NCGIA publications 96-3 and 94-6 n NCHRP 20-27(2) reports #218 and #221 n NSDI Framework Transportation Feature Identification Standard n Pavement Management Model –Reached a Consensus

Analysis Diagram - Packages

Package Definitions n Reference Network –A representation of physical, semi-permanent infrastructure features intended to facilitate a channeling or control of traffic n Street Names and Address Ranges –Attribute objects associated with one or many objects from the Reference Network n Location Referencing –Objects and procedures for associating transportation related n Routing –Primarily tabular related data needed to support transportation planning processes n Assets, Activities, Incidents –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. n Mobile Objects –An object representing any type of medium through which people or commodities are transported along the Reference Network.

Reference Network Package Details

Reference Network Details 2 n TransportEdge –Geometric and/or Logical network feature –Corresponds to arc, link, edge, segment, roadway, street… –May be a complex or a simple edge feature –Can be used for rendering or analysis or both –Subtypes can be created for any fundamentally unique Edge Type »Road »Rail »Waterways »Shipping Lanes »Bike Paths »Etc….

Reference Network Details 3 n TransportJunctions –Correspond to terms such as node, point, intersection… –The Object Model allows us a great deal more flexibility to handle a lot of difficult cases that come up at Junctions –Consider that many intersection in any given dataset can have identical properties. »All junctions with those properties can be of that TransportJunction Type »One need only record the type of junction rather than repeat all of the behavioral definitions for each intersection. »Even more complex junctions (brunnels) appear frequently enough to benefit from this structure

Other Packages - Relationships n TransportEdge - RoutesHaveEdges - TransportRoute n TransportEdge -LinearAlong - LinearAsset n TransportEdge - PointAlong - PointAsset n TransportEdge - Turn – TransportEdge n StreetName – StreetNameHasRoads – Road n Road – RoadHasAddressRanges – AddressRange

Other Packages – Domains n Coded Value Domains –Speed Class –Truck Type –Functional Class –Lane Type –Asset Condition –Boolean String –Boolean Integer –Census Feature Classification Code n Facilitates standardization and data sharing n Helps to discourage attribute error

What’s the UML Look Like?

Using the UML n Plan your Geodatabase –Use the Analysis Diagram as a template –Define your goals and data needs n In Visio modify the UML to meet your needs –OOAD –Add, delete, or modify objects –Add attribute definitions n Export from Visio to a Microsoft Repository n In ArcCatalog generate an empty schema from the Repository –Placeholders for your data n Load your data into the Geodatabase

Transportation Analysis and Planning

UNETRANS and Centerline Extraction n Networks –Topology is mandatory n Multiple Representations –Assets, Incidents, Activities –Reference Networks »Single Centerlines »Double Centerlines (Carriageways) »Lanes »CAD Generated Drawings

How to Proceed n Develop applications and use cases n Test the model’s ability to satisfy the needs of those applications n Continue to iterate through the modeling process in order to make improvements to the model based on the test results –Attributes n Publish the Results –Websites –Reference Document »Object Data Dictionary »UML Samples »Cross-references to existing standards and other data models –Transportation Data Modeling Book –CD with Sample Data Sets and Applications