mapintelligenceagency/gbfsQL: Wraps any number of GBFS feeds into an easily consumable GraphQL API. Merges relevant feeds and supports real-time updates for clients via Websockets/GraphQL Subscriptions.

OneBusAway: A Java app that consumes GTFS and GTFS-Realtime (along with other formats) and turns them into an easy to use REST API.

OpenTripPlanner: An open source platform for multi-modal and multi-agency journey planning, as well as returning information about a multi-modal graph (using data sources such as GTFS and OpenStreetMap).

pyBikes: Software powering CityBikes for worldwide bikeshare system info.

GBFS/Open Data Viewer: Visualize micromobility and other open data.

GBFS-Viewer: View micromobility data in your browser.

Alliance for Parking Data Standards (APDS): Formed by the International Parking Institute, the British Parking Association, and the European Parking Association, 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.

City Data Standard - Mobility: An open data standard for data exchange between cities and shared mobility operators.

Data Standards and Guidance for Transportation Planning and Traffic Operations: Standards and/or guidance to be used and adopted by the transportation community collecting, managing, an sharing status and real-time data for transportation planning and operations.

Dyno-Demand: A GTFS-based travel demand data format focusing on individual passenger demand suitable for dynamic network modelling developed by San Francisco County Transportation Authority, LMZ LLC, and Urban Labs LLC.

Dyno-Path: (Under development) Data from individual passenger trajectories.

General Transit Feed Specification: A GTFS feed is a group of text files that contains infrequently changing transit data, like stops, routes, trips, and other schedule data. Transit agencies typically update their GTFS feed every few months.

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 comprises of MTLFS and defined the field 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.

Mobility Data Specification: A project of the Open Mobility Foundation (OMF), MDS is a set of open source APIs focused on dockless shared mobility. Inspired by projects like GTFS and GBFS, the goals of MDS are to provide a standardized way for municipalities or other regulatory agencies to regulate operators and enforce policy, and ingest, compare and analyze data from mobility service providers, and to give municipalities the ability to express regulation in machine-readable formats.

NeTex: A general purpose XML format designed for the exchange of complex static transport data among distributed systems managed by the CEN standards process.

SAE Shared Mobility: Working on a data standard for carshare and transportation network companies/rideshare.

Transactional Data Specifications for Transportation Planning and Traffic Operations: Technical specifications for transactional data for entities involved in the provision of demand-responsive transportation.

Transit ITS Data Exchange Specification (TIDES) Project: A proposed effort to create standard data structures, APIs, and data management tools for historical transit ITS data including AVL, APC, and AFC Data.