Tools & Services
There are a multitude of tools and services available to help with the creation, implementation, and consumption of GBFS. Below is an extensive, although by no means exhaustive, list of tools and services.
Third Party GBFS URL Directories
Bike Share Research: BSR aims to facilitate the curation of bikeshare service data through collaborative and open data platforms while making it API accessible.
Archived Bikeshare Data
Open Mobility Foundation Mobility Data Management State of Practice - Public Data Sharing: A list of public mobility data sets, and information about approaches to anonymization published by cities.
Proprietary (non-standard) Vendor APIs
Software for Creating APIs
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.
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).
Bikeshare Map: Status of all worldwide bikeshare stations.
CityMapper Webapp: Webapp with trip planner and route status for over 30 cities.
OpenTripPlanner Client GWT: A Google Web Toolkit-based web interface for OpenTripPlanner.
1-Click: A virtual “trip aggregator” that assembles information on a wide variety of available modes: public transit, private, rail, rideshare, carpool, volunteer, paratransit, and walking and baking. Open-source on GitHub.
Native Apps (open source)
Native Apps (closed source)
BikeshareClient: dotnet client for GBFS written in C#. Enables dotnet developers to create apps and services using data from GBFS Bikeshare systems.
GBFS Analysis Tools
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-json-schema: JSON schemas for all existing versions of GBFS (including up to v2.2 and v3.0RC
Other Multimodal Data Formats
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.
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.
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.
SAE Shared and Digital Mobility Committee: 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.