Course Information

1. Framework Data Content -Transportation Related Topics NSDI Training Tracks: An initiative to define areas, topics, and materials for training within the NSDI. ISO 19100 Series: Suite of standards developed for geographic data and datasets. The most notable is ISO 19135 which pertains to metadata. ANSI Standards: Similar work to ISO, but standards directly apply to data created within the United States. Course Information The National Spatial Data Infrastructure (NSDI) Framework is a collaborative initiative to develop geographic datasets that are compatible based upon spatial location and content. The Framework approach allows data collected for variety of reasons and agencies to work together seamlessly; which can ultimately reduce project costs and increase interagency cooperation. The Framework Data Content Base Standards Suite dictates the requirements for Framework data. This course covers the fundamentals of the Framework Data Theme: Transportation as developed by the Framework Data Content Standard. It is designed for users who are both interested in an overview of the Framework Data Content Standard Transportation theme as well as designers and developers implementing Framework data, and associated tools. Prerequisites • General Understanding of GIS, Geospatial Data and Metadata • Familiarity with the FGDC and NSDI • Basic knowledge of Geographic Data Standards (specifically ISO 19100 series) • Completion of Framework Data Content Base Standard Course

2. Navigating Through the Course Explanation of Navigation Buttons

3. Learning Objectives Understand Transportation Data Comprehend basics of transportation framework standard Understand how to implement the standard Course modules • Understanding Transportation • Transportation Base (Part 7) of the Framework Data Content Standard • Implementing the Transportation Base • Course Review and Comprehensive Self-Test Estimated Time Estimated time for the entire course is 150 minutes.

4. Module 1: Understanding Transportation Time Requirement Topics • What is Transportation Data • Types of Transportation Data • Transportation in Action • Module Exercise and Summary Estimated time for this module is 30 minutes Key Terms Transportation Framework NSDI/FGDC First Topic What is Transportation Data

5. What is Transportation Data Related scientific field Network Analysis: A transport network, or transportation network in American English, is typically a network roads, streets, pipes, aqueducts, power lines, or nearly any structure which permits either vehicular movement or flow of some commodity. A transport network is used for transport network analysis to determine the flow of vehicles (or people) through it within the field of transport engineering, typically using graph theory. It may combine different modes of transport, for example, walking and car to model multi-modal journeys. Transportation can be defined as the movement of people and goods from one place to another. Thus Transportation data, and geospatial Transportation data are representations of the means in which transportation can occur. For example a state highway map is an example of transportation data. next Topic Types of Transportation Data

6. Types of Transportation Data • There are probably hundreds of different types and ways to represent Transportation Data. However for the purposes of Framework Data and the Framework Data Content Standard there are five main types of Transportation data. • Part 7, Transportation • Part 7a, Air • Part 7b, Rail • Part 7c, Road • Part 7d, Transit • Part 7e, Inland Waterways next Topic Transportation Data in Action

7. Transportation in action Example In General terms the diagrams above represent one way we can represent real transportation (road) features and use them for analysis in GIS and other tools. The purpose of this Transportation Framework Standard is to provide a process by which data is standardized and categorized to ensure a level of consistency and interoperability. next Topic Transportation Exercise

8. Transportation Base Module 1 exercise Wyoming Road Conditions map The Wyoming Road Conditions website allows a user to locate, and access weather information about a given road or set of roads. Transportation Data in action Transportation data is being applied and used in real world projects by many different agencies. These agencies use transportation data for a variety of reasons. Now that you have some basic transportation knowledge let’s see some a transportation data set in action. Step 1) Open an Internet Browser and proceed to: http://map.wyoroad.info/ Step 2) Select either a town or highway of your choice Step 3) Click Go Step 4) Explore the information that is available and how it tied to the transportation data Step 5) Close all Internet windows and proceed with the course next Topic Module Summary

9. Module Summary Understanding Transportation • Transportation data is data that describes how people and goods move across a landscape • 5 categories of transportation data makeup the transportation framework • Many different transportation features can be collected and mapped next Topic Module 2: Transportation Base (Part 7) of the Framework Data Content Standard

10. Module 2: Transportation Base (Part 7)of the Framework Data Content Standard Time Requirement Topics Estimated time for this module is 20 minutes • What is the Transportation Standard • Purpose for Standard • Goals of the Standard • Capacities of the Standard • Standard Related Contact Information • Module Exercise and Summary Key Terms Transportation Framework Standard Framework

11. Next Topic Purpose for the Standard What is the Transportation Base standard • The Transportation Base Framework Data Content Standard: • One of the seven themes defined as Framework data • All the elements that apply to all Transportation Framework Data • Establishes a baseline for Transportation data collection and creation • Builds on the Framework Data Content Base Standard. • Only when a dataset meets both the requirements set forth in a thematic standard part(s) and the Framework Base Standard can it be considered Framework data.

12. Next Topic Goals of the Standard Purpose for the Standard Quick Facts Each standard part was developed and edited by thematic experts Certain themes have additional pieces to address sub components. For example Transportation has five additional parts to address different elements (i.e. roads, airports, etc.) The Geographic Information Framework Data Content Standard, Part 7: Transportation Base defines the data model for describing transportation systems components of transportation systems for five modes that compose the Transportation theme of the NSDI. The primary purpose of this part of the standard is to support the exchange of transportation data related to transportation systems. It is the intent of the Transportation Base part to set a common baseline that will ensure the widest utility of transportation data for the user and producer communities through enhanced data sharing and the reduction of redundant data production. At a high level, the transportation system described in this part of the Framework Data Content Standard is made up of transportation features, which can have geographic locations and characteristics. These transportation features can be interconnected in various ways and across several modes to represent transportation networks for path finding/routing applications.. It is expected that the content in the part will support the development of specialized networks for routing applications, but this level of information is not a requirement of the data standard. This part of the standard can be implemented using a variety of software packages and is designed to accommodate data encoded without geometry as well as to support the exchange of data encoded in a variety of geographic information systems. The part accommodates assets associated with the transportation system that are typically used for navigation, safety, and measurement. The Transportation Base part integrates the five modes of transportation systems: air, rail, road, transit, and water.

13. Next Topic Capacities of the Standard Goals for the Transportation Base Standard • The goal of the transportation base part of the Framework Data Content Standard is to provide common definitions and syntax to enable collaborative development, use, and exchange of Transportation data. • It is the intent of the part to set a common baseline of information content for exchange within the hydrographic community that will enhance data sharing and applications development when used with standards-based Web services or file transfer. • This part supports the mapping and conversion of native data in any format into a common representation for exchange over the Web or as files. Encoding of transportation data for transfer, based on the models in this part, is described in the Framework Data Content Base Standard. • The audience of this part of the standard includes Transportation data users, maintainers, and distributors. Specific guidance on the implementation of this part for specific user communities will be made through the sub-standard parts, external guidance or policy documents.

14. Capacities for the Transportation Standard More Information The FGDC is the responsible organization for coordinating work on all parts of the Geographic Information Framework Data Content Standard. The United States Department of Transportation (USDOT), working with the FGDC, is the responsible organization for coordinating work on the Geographic Information Framework Data Content Standard, Part 7: Transportation Base and subparts (Parts 7a, 7b, 7c, and 7d, excluding 7e) and is directly responsible for development and maintenance of the transportation parts (excluding 7e) of the Framework Data Content Standard. • The development of this part of the Framework Data Content Standard will greatly assist in mitigating the following issues: • Duplication of data and application development • Complications exchanging Transportation data and information • Difficulties integrating data • Poor framework/support for analytic activities • Difficulties managing multiple representations of features next Topic Contact Info

15. Who to Contact for Questions about the Transportation Base Standard Part Standard Coordination The FGDC is the responsible organization for coordinating work on all parts of the Geographic Information Framework Data Content Standard. The development and maintenance authority for Part 6: Transportation is held jointly by the U.S. Geological Survey and U.S. Environmental Protection Agency. The FGDC shall be the sole organization responsible for direct coordination with the InterNational Committee for Information Technology Standards (INCITS) concerning any maintenance or any other requirements mandated by INCITS or ANSI. Federal Geographic Data Committee Secretariat c/o U.S. Geological Survey 590 National Center Reston, Virginia 20192 USA Telephone: (703) 648-5514 Facsimile: (703) 648-5755 Internet (electronic mail): gdc@fgdc.gov WWW Home Page: http://www.fgdc.gov next Topic Module 2 Exercise

16. Transportation Module exercise Instructions: The following Quiz will test the knowledge you should have gained in Module 2. There are 3 True or False Questions. Good Luck! Proceed To Quiz

17. True or False: The transportation base part identifies and defines terminology, encoding schema, and the data components required for describing hydrographic features, along with the metadata needed for the transportation data exchange A) True B) False Correct - Click anywhere to continue Incorrect - Click anywhere to continue Your answer: You answered this correctly! You did not answer this question completely You must answer the question before continuing The correct answer is: Submit Clear

18. True or False: One goal of the standard is to set a standard that will allow the transportation community that will reduce the need for data sharing and allow users to create their own data without the need to share with others. A) True B) False Correct - Click anywhere to continue Incorrect - Click anywhere to continue Your answer: You answered this correctly! You did not answer this question completely You must answer the question before continuing The correct answer is: Submit Clear

19. True or False: The Federal Geographic Committee and NSDI are NOT involved with these standards in anyway. A) True B) False Correct - Click anywhere to continue Incorrect - Click anywhere to continue Your answer: You answered this correctly! You did not answer this question completely You must answer the question before continuing The correct answer is: Submit Clear

20. Module 2 Quiz next Topic Module Summary

21. Module summary • The goal of the Transportation Base part of the Framework Data Content Standard is to provide common definitions and syntax to enable collaborative development, use, and exchange of Transportation data. • Establish the content requirements for the collection and interchange of Transportation features • The Transportation Base part integrates the five modes of transportation systems: air, rail, road, transit, and water. next Topic Module 3: Transportation Base Requirements

22. Module 3:Transportation Requirements Time Requirement Topics Estimated time for this module is 60 minutes • Framework Data Content Transportation Base Standard Requirements • Encoding and Implementing the Standard • Module Summary Key Terms UML Coding Elements Feature Relationships First Topic Transportation Standard Requirements

23. Framework Data Standard Transportation Requirements In this module you will learn about the three different requirements for Framework Transportation data, as specified in the standard. Each requirement is addressed as a separate topic, however more attention may be given to certain requirements as they are the most crucial requirements for creating Framework quality Transportation data. Many of the requirements are specific UML features. For these requirements the a brief description of the component will be included. Please see the UML chart and associated tables, included as an appendix for more specifics. Additionally encoding and implementation will be covered briefly. next Topic Transportation Requirements Continued

24. Framework Data Standard Transportation Requirements The diagram to the right is the UML flow chart for the Framework Transportation Standard. This diagram shows the components and relationships that comprise the Framework Transportation Standard. UML is designed to show these relationships in a generic manner without specifying a coding language or specific software needed to complete the task. For more information about UML visit http://www.uml.org next Topic Transportation Requirements Continued

25. Framework Data Standard Transportation Requirements The following list is a list of the four main UML object specified in the Transportation standard. Each one corresponds to a box on the UML diagram. For more detailed information please see the Appendices which have a copy of the compete standard including tables outlining the specifics of each UML object. 1 Transportation base model Transportation entities are represented as TranFeatures. The transportation network is represented by TranSegs, TranPoints, and TranPaths. TranFeatures can have attributes. For linear TranSegs and TranPaths, if the values for these attributes can change along the length of the feature, the attributes are represented by AttributeEvents. FeatureEvents allow Features to be linearly located along TranSegs and/or TranPaths. 2 Transportation feature model Many transportation features have certain characteristics in common, such as linear geometries, a connective nature, and a system for indexing these real world features. In this part of the standard, rail, road, and transit modes share a common model for representation shown in Figure 2. TranFeature is simply an extension of Feature that includes any and all transportation features. TranFeature has three feature subclasses: TranPath, TranSeg, and TranPoint to represent the Transportation Segmentation Model. These three feature subclasses have analogues in the rail, road, transit, and waterway modes of transportation. All other transportation related real world entities are represented as instances of transportation features. 3 TranPoint TranPoints provide the topological connection between TranSegs. Each TranSeg must have exactly one start TranPoint and one end TranPoint. If a roadway transportation network is segmented at all roadway intersections, each TranSeg represents the physical roadway between two intersections and the TranPoints correspond to intersection locations. If instead, the transportation network is segmented into exactly five-mile long TranSegs, there may not be a physical entity where the resultant TranPoints occur. An intersection shall be represented as a Transportation Feature rather than a TranPoint. This allows flexibility in defining its geometry as being a point, an area, or both. 4 Transportation event model Events are the mechanism by which attributes or entities can be linearly located along either a TranSeg or a TranPath linear feature. As can be seen in Figure 6, Transportation Events can be either AttributeEvents or FeatureEvents. next Topic Transportation Requirements Continued

26. Framework Data Standard Transportation Requirements Sub parts to requirement 3 – These subparts further explain the Transpoint element and its appropriate uses. Subpart 1 TranSeg TranSeg represents a linear section of the physical transportation network designed for, or the result of, human or vehicular movement. As shown in Figure 3, TranSeg extends TranFeature. Within this part of the standard, TranSeg may be defined in a variety of ways depending on mode and business application. It is left to the data creator to decide how to segment their transportation system in a manner that supports their organizational functions. A single TranSeg can represent an entire segment between two points, or, a separate TranSeg can be defined for each direction of travel. Defining how and where segments are defined is dictated by the need of the application and the dataset being exchanged. This has practical application within the Rail, Roads, and Transit parts as providers of those data may choose to represent only topology, without geometry, for rapid network tracing. The relationships between TranSeg and TranPoint in Figure 3 show that each TranSeg must have a startPoint and endPoint.. Subpart 2 TranPoint TranPoints provide the topological connection between TranSegs. Each TranSeg must have exactly one start TranPoint and one end TranPoint. If a roadway transportation network is segmented at all roadway intersections, each TranSeg represents the physical roadway between two intersections and the TranPoints correspond to intersection locations. If instead, the transportation network is segmented into exactly five-mile long TranSegs, there may not be a physical entity where the resultant TranPoints occur. An intersection shall be represented as a Transportation Feature rather than a TranPoint. This allows flexibility in defining its geometry as being a point, an area, or both. FeatureEvents can be used to define their location along and optionally offset from a TranSeg. Alternatively, Points C and D can be represented as AttributeEvents if they represent attributes instead of entities, such as the start of a bridge. TranPoint is a subtype of TranFeature. TranPoints can therefore have a geometry and topology attribute and may have one or more attributes that are associated with the location where the point occurs. Subpart 3 TranPath A TranSeg is used to represent a physical transportation real world entity and attributes about that entity. TranPath, as applied in the Rail, Roads, and Transit modal parts of the standard, can represent how the TranSegs are organized and used such as administrative routes like US 50, or bus or train routes. Because it is a path through the physical transportation system, a TranPath is defined by a list of the one or more, whole or partial, TranSegs it uses. next Topic Transportation Requirements Continued

27. Framework Data Standard Transportation Requirements Sub parts to requirement 4 – These subparts further explain the Transportation event model and its appropriate uses. LinearAttributeEvent LinearAttributeEvents provide the means of specifying the value and location of a single segment or path attribute that applies only to part of the segment or path. The value of the segment or path attribute is specified as the attributeValue, inherited from AttributeEvent. The location interval along which the value applies is specified by a start and end position along the segment or path, using linearly referenced position expressions. The name of the attribute is specified by the linearEventType attribute. For subtypes of LinearAttributeEvent, see subsequent, transportation mode-specific parts of this standard. PointAttributeEvent PointAttributeEvents (see Figure 7) provide the means of specifying the value and location of a single segment or path attribute that has a particular value only at a single point along the segment or path. The value of the segment or path attribute is specified as the attributeValue, inherited from AttributeEvent. The point location is specified by an atPosition along the segment or path, using a linearly referenced position expression. The name of the attribute is specified by the pointEventType attribute. For subtypes of PointAttributeEvent, see subsequent, transportation mode-specific parts of this standard. An example of a PointAttributeEvent is a stop sign along a road. “Sign” is the road attribute (pointEventType). A value of “stop” (attributeValue) specifies the type of sign. The sign is located at a position along the road segment. The position expression allows the sign to be located at a position laterally offset from the center of the road. If more information is needed about the sign, the sign shall instead be represented as a feature and then linearly located with a PointFeatureEvent. PointAttributeEvents can also be used to specify where something like a pedestrian cross walk crosses the segment or path. PointAttributeEvents have a linear location along a segment or path but have no explicit geospatial coordinate location of their own. This can be obtained from any geometry which may have been defined for the segment or path to which the PointAttributeEvent applies. Example An example of a LinearAttributeEvent is the speed limit of a road. “Speed limit” is the road attribute (linearEventType). A value of 55 MPH (attributeValue) might apply for only part of the road segment, delineated by start and end positions along the road segment. LinearAttributeEvents have no geometry of their own but instead inherit any geometry which may have been defined for the segment or path to which they apply. next Topic Transportation Requirements Continued

28. Framework Data Standard Transportation Requirements Sub parts to requirement 4 – These subparts further explain the Transportation event model element and its appropriate uses. LinearFeatureEvent A LinearFeatureEvent provides the means of specifying a linear location for a feature along a segment or path. All of the feature’s attributes, including optional geometry, are included with the feature. The LinearFeatureEvent is only attributed with the linear location of the feature along a segment or path, specified by a start and end position along the segment or path using linearly referenced position expressions (see Figure 7). There are no restrictions on the type of feature being located. The feature can be linear, like guardrail. Guardrail attributes, like date installed or manufacturer are kept with the guardrail feature. The guardrail feature may not have geometry of its own, but instead rely on the geometry of the locating segment or path. Features with area geometries, like a county, are also supported. In this case, the LinearFeatureEvent depicts what part of the segment or path is in the County. PointFeatureEvent A PointFeatureEvent provides the means of specifying a linear location for a feature along a segment or path. All of the feature’s attributes, including optional geometry, are included with the feature. The PointFeatureEvent is only attributed with the linear location of the feature along a segment or path, specified by a single atPosition along the segment or path using a linearly referenced position expression (see Figure 7). There are no restrictions on the type of feature being located. The feature can have a point footprint, like a stop sign. Sign attributes, like date installed or height are kept with the sign feature. The sign feature may not have geometry of its own, but instead rely on the geometry of the locating segment or path. Features with linear geometries, like a railroad, are also supported. In this case, the PointFeatureEvent depicts where the railroad crosses the segment or path. next Topic Transportation Requirements Continued

29. Encoding and implementation The Bigger Picture The Framework Standards do not have a specific application schema that can be implemented. Implementation of the Framework Standards in relation to data and tool creation occurs at the thematic level. Each thematic part complies with the Framework Base Standard. As such a road layer (for example) created in accordance with the Framework Transportation Roads part meets all Framework requirements. • The process of encoding is simply formatting or structuring data in a regulated manner. The Framework standards are encoded by applying the application schemas through the use of several different modeling and markup languages: • Unified Modeling Language (UML) • Extensible Markup Language (XML) • Geographic Markup Language (GML) • Specific knowledge of each language is important for data and tool designers; for more information see the Framework Base Standard Training Materials. next Topic Module Review

30. Module 3: Transportation Requirements Summary • Three different requirements, with multiple subparts are specified by the Framework Transportation Standard • This module covers the specifications on Transportation data should be built • Provides rigid requirements to ensure proper structure and documentation for Transportation data • UML diagrams and data dictionaries provide specifics for programmers and data creators to develop Transportation data that meets Framework specifications next Topic Module 4: Standard Implementation

31. Module 4: How To put The Standard into operation Time Requirement Topics Estimated time for this module is 20 minutes • Implementation Overview • Transportation Base Concept • Review Key Terms UML Transportation Applications First Topic Implementation Overview

32. Implementation Overview Now that you know more about the Transportation and how it applies to the overall objective of Framework; The goal of this module is to help you implement the Transportation Part of the Framework Standard. It is important that you realize that currently there are no tools to help you implement, or check your data to ensure it meets Framework Standard requirements. Remember these standards are new and tools to implement these standards will take time to develop. However, the slides in this module will give you an overview of the general process and requirements needed. Please refer to the Framework Standard Transportation Part for additional information and context. next Topic Design Requirements

33. Transportation Base Implementation Transportation Applications It is important to remember that different transportation based applications have specific data and information requirements. Thus the Transportation Framework part needs a complex data model to support these needs. The implementation of the Transportation Base standard is different from other standards since it is comprises the components that apply to all Transportation Data versus specifics of any one type of data. However like most spatial data, the main issue with the Transportation theme is how to represent real world features in a spatial system. Thus a data dictionary has been developed to help define the important elements needed to define Transportation Framework. next Topic Review

34. Module 4 Summary • The Transportation Base Framework Standard is broad standard that combines the components that are needed for all transportation data to make it interoperable. • Individual transportation applications and data have specific needs, however the model developed for the Transportation Framework model encompasses all of these needs and has sub-parts to address different transportation modes • Specific UML diagrams, code lists, and data dictionaries have been developed to document components necessary for Framework Transportation data. next Topic Module 5

35. Module 5: Course Review and Comprehensive Self-Test Topics • Review Exercise • Certificate of Completion next Topic Review Exercise

36. Transportation Exercise • 1. Visit the Virginia DOT transportation mapping service. • Explore the site and see how quality Transportation data can be implemented and integrated into an Internet Mapping Service to provide the consumer with valuable information. • http://www.virginiadot.org/travel/prOTIM.asp • Use an Internet search engine (i.e. Google, Yahoo) to search for a document titled “An Interoperable Transportation Framework Data Service”. • Review the document to see the techniques that George Mason University has used to develop a Transportation data distribution tool as part of an NSDI CAP grant. next Topic Course completion

37. Course Certificate Congratulations, you have successfully completed the Framework Transportation Standard Training! In order to print the certificate below you will need a copy of Adobe Acrobat Reader, http://www.adobe.com/products/acrobat/readstep2.html. After you open the certificate file, type your name and today’s date on the name/date line and print. Click here to receive course certificate