General requirements

A partner must provide us with one and only one feed set, and it must conform to GBFS V2.2 for either docked or dockless systems. The set must include only one of each file. For example, it must contain only one station_information.json. Because of the file limit, the following constraints exist for a given feed set:

  • The feed set is limited to a single set of GBFS files that have the fields defined in the local language of the city it covers, where appropriate. For example, if a feed covers both the United Kingdom and Germany, stations[].name must contain the station name in English for stations located in the United Kingdom and in German for the stations located in Germany.
  • The feed set must be global. The official GBFS lets a provider "shard" their feeds, but Google doesn't currently support this feature. An example of "sharding" is when a provider has more than one free_bike_status.json for a given region.

Structured data type definitions

To successfully build your feed, you must adhere to the applicable set of structured data type definitions that we provide. In the GBFS definitions, all the files in GBFS V2.2 are listed with indications of which systems they're applicable for in the header with the following permutations:

  • Docked system
  • Dockless system
  • Docked and dockless system

For example, if the provider uses a dockless system, you must only provide files that are indicated for Dockless system or Dockless and docked systems to describe the system. For more information, refer to Supported micromobility systems.

Each section in the GBFS definitions provides the structured data type definitions that you need to successfully build a complete feed. It includes the definitions and instructions specific to the provider-type for the feed.