0. XML Schema for Transportation Data Exchange
TransXML
XML Schema for Transportation Data Exchange
Overview

1. XML is a way to organize and define data
Data that used to look like this…
LAND RICHARD1120 N ST
PEDERSEN NEIL NCALVERT ST
KOBETSKY KEN NCAPITOL ST
Now look like this in XML…
<Person>
<SocialSecurityNumber> </SocialSecurityNumber>
<Name>
<LastName> LAND </LastName>
<FirstName> RICHARD </FirstName>
</Name>
<Address>
<StreetAddress> 1120 N STREET </StreetAddress>
<City> SACRAMENTO </City>
<State> CA </State>
<ZIPCode> </ZIPCode>
</Address>
<TelephoneNumber> </TelephoneNumber>
</Person>

2. The Basics about XML eXtensible Markup Language
It’s easy to interpret – you can “read” it
“Tags” (like <Person> or <TelephoneNumber>) can describe almost any kind of information
Each XML file is known as a “document”

3. XML 101 XML is: An XML “schema” is a data structure
A widely adopted way of exchanging information across web applications
Human-readable and self-documenting
Independent of individual applications/software
An XML “schema” is a data structure
A schema’s value depends on getting agreement across software vendors and agencies that produce and consume info regarding what pieces of data to include and how they should be defined

4. What is an XML Schema?
A set of rules describing the types of information that can (or must) appear in an XML document
For example: An accident report document…
Must contain the date, time, and location…
Must contain information on one or more vehicles…
Each vehicle must have a VIN, Make, Model, Plate #…
May have one driver (name, birth date, license #...)
May have one or more passengers (name, birth date…)
May contain information on one or more pedestrians…
[etc.]

5. Examples of XML in Transportation
LandXML – roadway design info
aecXML – construction pay items
AASHTO Trns*port construction management – data exchange between modules
AASHTO Virtis/Opis – XML import and export routine
AASHTO TSIMS (proposed)
JusticeXML – driver records, arrest warrants
Location Referencing Specification (SAE J2266)
ATIS – XML vocabulary for Traveler Information Exchange
GML – geographic markup language (object model & rules for developing XML schema)
TranXML/Logistics XML
TMML – Traffic Model Markup Language – data exchange across traffic modeling software packages
FMCSA – motor carrier profile, safety audit, driver/vehicle/carrier clearance

6. The History of “TransXML”
Initiated by AASHTO’s Technical Applications and Architecture (TA&A) Task Force
NCHRP Project created with a $500,000 budget
Driving Forces:
Growing support for data exchange standards within DOT community – given ITS experience, increase in web apps
Success of LandXML – sharing of road design info
AASHTOWare program interest in migrating to XML as the data exchange method in all products
Desire to coordinate/fill gaps in multiple fragmented XML efforts: construction, design, safety, GIS, ITS

7. TransXML Project Objectives
Develop broadly accepted public domain XML schemas for exchange of transportation data
Recommend an institutional framework for future schema development and dissemination
Initial focus was in four business areas:
Survey/Roadway Design
Transportation Construction/Materials
Highway Bridge Structures
Transportation Safety

8. Potential Benefits of TransXML
Status Quo
Future Vision
Proliferation of inconsistent, overlapping data standards
Time consuming to transfer data from one application to another
Duplicative data entry
Limited access to information across functional areas in an agency
Changes in technology limit access to archived legacy data
Coordinated, widely used core data standards
Open, non-proprietary data formats adopted
Automation of data transfer
Sharing of information across planning, design, construction and operations
Data archived in accessible, self-documenting format
LandXML:
XML standard for civil engineering and land survey data
Supported by 30+ applications including all major civil engineering packages, FHWA ISDHM
Demonstrated benefits
Faster & Easier data exchange across applications
Use of LandXML for control of GPS-guided excavation equipment
AASHTOWare:
Desire for Open Data Formats to Allow for Interoperability:
Construction Management
Bridge Rating & Design
Bridge Management
TSIMS
Research Community:
Recognition of XML’s emergence as major data exchange format
Multiple standards emerging
Investigate creation of coordinated mechanism for schema development

9. TransXML Current and Possible Future Scope
Current Focus Areas
Survey/
Design
Construction/
Materials
Bridge
Safety
Potential Future Focus Areas
Asset
Management
Maintenance
Management
Project
Development
Program
Development
Operations/ITS
Modeling/
Simulation
Geospatial
Data
Freight/
Logistics

10. TransXML Gaps and Opportunities Survey/Design – Current Schema
LandXML
Alignments
Coordinate Geometry Points
Grade Model
Surfaces – point, linear, triangle
Parcels
Roadways (IHSDM)
Survey Equipment and data
Geotechnical XML
Soil testing results
aecXML Infrastructure
Pay Items
Pay item prices for design estimates
Geographic Markup Language
Geometries (points, curves, surfaces, solids, composite)
Topologies
Location & Coordinate Reference Systems
Measurement Units
Metadata
Presentation Styles

11. The Goal of TransXML Survey/Design Example
Example: Imagine exchanging design info across all team members and having their individual software programs be able to instantly read and interpret all project data correctly
Geometric Design:
Alignment
Pavement section
Superelevation
Cross sections
Geometrics
Surveyor
Bridge
Hydraulics
Utilities
Right-of-Way
Traffic

12. Next Steps
Joint Technical Committee on Electronic Engineering Data has endorsed TransXML as the best way to standardize the transfer of data among softwares
4 subcommittees have also endorsed TransXML as the starting point for further work in standardizing data transfer:
Bridges and Structures
Construction
Design
Information Systems
The Joint Committee is looking for SCOH’s and the Board’s endorsement prior to moving forward with additional work in this area, as this is likely to be a long-term effort over the coming 5-10 years