Other multimodal data formats

• Alliance for Parking Data Standards (APDS) - Formed by the International Parking Institute (IPI), the British Parking Association (BPA), and the European Parking Association (EPA), APDS is a not-for-profit organization with the mission to develop, promote, manage, and maintain a uniform global standard that will allow organizations to share parking data across platforms worldwide. APDS Version 1.0 documents are here.
• CurbLR - A specification for curb regulations.
• Dyno-Demand - A GTFS-based travel demand data format focusing on individual passenger demand suitable for dynamic network modeling developed by San Francisco County Transportation Authority, LMZ LLC, and UrbanLabs LLC.
• Dyno-Path - (Under development - see this post) Data for individual passenger trajectories.
• General Bikeshare Feed Specification (GBFS) - Open data standard for real-time bikeshare information developed by members of the North American Bikeshare Association (NABSA).
  • gbfs-validator - 3rd party tool to validate GBFS feeds.
  • gbfs R package - Functions to interface with GBFS feeds in R, allowing users to save and accumulate tidy .rds datasets for specified cities/bikeshare programs.
  • GBFS Documentation Platform - Documentation platform for the General Bikeshare Feed Specification, maintained by MobilityData. View the GBFS specification, change proposals, policy guides, and technical tools.
• GTFS-flex - A data format that models flexible public transportation services as an extension to GTFS.
• GTFS-plus - A GTFS-based transit network format for vehicle and capacity data suitable for dynamic transit modeling developed by Puget Sound Regional Council, UrbanLabs LLC, LMZ LLC, and San Francisco County Transportation Authority.
• GTFS-ride - An open, fixed-route transit ridership data standard developed through a partnership between the Oregon Department of Transportation and Oregon State University.
• GTFS-stat - An extension to a GTFS transit network with additional files that contain performance data developed by UrbanLabs LLC and San Francisco County Transportation Authority.
• General Modeling Network Specification (GMNS) - A format for sharing routable road network files designed to be used in multi-modal static and dynamic transportation planning and operations models. Volpe/FHWA partnership with Zephyr Foundation.
• General Travel Network Specification - A planned data specification for sharing travel demand model networks.
• Managed and Tolled Lanes Feed Specification (MTLFS) - Proposal for a schema that comprise the Managed and Tolled Lanes Tolling Feed Specification (MTLFS) and defines the fields used in all of those files developed by Santa Clara Valley Transportation Authority.
• Mobility as a Service API - A set of open documents and test suite that defines a MaaS-compatible API (e.g., a MaaS Transport Service Provider Booking API).
• Mobility Data Specification (MDS) - A format to implement realtime data sharing, measurement and regulation for municipalities and mobility as a service providers. It is meant to ensure that governments have the ability to enforce, evaluate and manage providers. Maintained by the Open Mobility Foundation.
• NCHRP 08-119 Developing Data Standards and Guidance for Transportation Planning and Traffic Operations - Phase 1 (Anticipated) - The objective of this research is to develop standards and/or guidance to be used and adopted by the transportation community in collecting, managing, and sharing static and real-time data for transportation planning and operations.
• NeTex - A general purpose XML format designed for the exchange of complex static transport data among distributed systems managed by the CEN standards process.
• OMX: The Open Matrix data file format - A structured collection of two-dimensional array objects and associated metadata, for possible use in the transportation modeling industry.
• Open Sales and Distribution Model (OSDM) - Aims to substantially simplify the booking process for customers of rail trips and to lower complexity and distribution costs for distributors and railway carriers. Contains a specification of an offline model and on-line API. Maintained by the International Union of Railways (UIC).
• SAE Shared and Digital Mobility Committee - Appears to be working on a data standard for car share and transportation network companies (TNCs) / rideshare.
• shared-row - A specification for right-of-way (ROW) for a SharedStreets Reference.
• TCRP G-16 Development of Transactional Data Specifications for Demand-Responsive Transportation (In progress) - The objective of this research is to develop technical specifications for transactional data for entities involved in the provision of demand-responsive transportation. Expected completion date is late 2018.
• TIDES project - Transit ITS Data Exchange Specification (TIDES) is a proposed effort to create standard data structures, APIs, and data management tools for historical transit ITS data including AVL, APC and AFC Data.
• Cal-ITP Operational Data Standard (ODS) - Intended to address the lack of a standard format for representing transit schedules used by drivers, dispatchers, and planners to carry out transit operations.
• Transport Operator Mobility-as-a-service Provider (TOMP)-API - Working group in the Netherlands with a goal to develop an API for use by Transport Operators and Mobility-as-a-service Providers for operator discovery, trip planning, end user interaction, booking, and payment.