TransXML: XML Schemas for Exchange of Transportation Data (2007) / Chapter Skim
Currently Skimming:
Pages 12-20
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 12... ...
LandXML includes specifications for raw and reduced surveying data, surface data, parcel data, and a 3D road model. LandXML also includes a standard format for official electronic design submission.
|
From page 13... ...
Includes standard format for official electronic design submission. Most recent version incorporates mechanisms for interoperability with the Federal Highway Administration (FHWA)
|
From page 14... ...
aecXML AASHTOWare Trns•port XML Schema exists for construction contracts, project cost estimates, and daily work reports. Trns•port includes a broader construction management data model from which additional schema could be generated.
|
From page 15... ...
http://www4.nas.edu/trb/ crp.nsf/All+Projects/ NCHRP+20-07#149 The data model provided in the appendix of this report starts with the AASHTO Virtis/Opis data model and adds on specific classes related to fabrication and construction of steel bridges. National Cooperative Highway Research Program (NCHRP)
|
From page 16... ...
XML tags for crash records information. University of Florida Transportation Research Center Detailed evaluation Detailed evaluation FARS ftp://ftp.nhtsa.dot.gov/ FARS/FARS-DOC National fatal accident reporting system – coding manual published with all data elements.
|
From page 17... ...
http://www.fhwa.dot.gov/ohi m/hpmsmanl/hpms.htm Standard reporting format for highway performance information – reported annually by all state DOTs to FHWA. FHWA NCHRP 20-57 http://www4.nationalacademi es.org/trb/crp.nsf/All+Project s/NCHRP+20-57 This project developed generic tools to support asset management, along with a draft XML schema for the transportation asset performance tradeoff domain.
|
From page 18... ...
, the Model Minimum Uniform Crash Criteria (MMUCC) , and standard reporting formats defined by NHTSA for the Fatal Accident Reporting System (FARS)
|
From page 19... ...
3.2 Screening and Evaluation of Schema and Standards The XML schema and data standards reviewed in Section 3.1 were screened to determine which should be evaluated in detail for potential incorporation in TransXML. The screening criteria applied were as follows: • Relevant to the surface transportation business focus areas of bridge structures, safety, survey/design, and construction/ materials; • Beneficial to address a real business need and support data exchange across disparate applications for transportation planning, design, construction, maintenance and operations; and • Nonproprietary namely, in the public domain.
|
From page 20... ...
• Extensible -- Reusable elements; • Technically sound -- Well-formed, well-structured, simple/ clean design, use of elements as opposed to attributes; • Practical -- As demonstrated by the level of existing use, level of support from users and vendors, documentation, existence of sample schema and programs using those schema, ease of creating instance documents, ease of parsing; and • Compatible -- With related data and XML standards that have been adopted by the user community -- e.g., a schema with a crash type element should use compatible coding with existing ANSI standards for traffic data records. The detailed evaluations of the schema/standards are included in Appendix A
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.