Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expecting a great number of different mobility operators, Entur will require that the exchange of data happen happens through standard formats to ensure common and predictable functionality and being able to scale across many parties.

Entur expects all mobility feeds for e-scooters, city bikes and car sharing services to be shared through General Bike Share Service Feed Specification v2.2 (GBFS)

https://github.com/NABSA/gbfs/blob/v2.2/gbfs.md

Expected data

The GBFS specification standard defines required fields in the JSON files. In addition to these required fields, Entur will have additional requirements on certain data in order to provide useful and consistent data to end-users across multiple mobility operators.

...

The following ObjectTypes should be used:

Feed

Field

ObjectType

vehicle_types.json

vehicle_type_id

VehicleType

station_information.json

station_id

Station

free_bike_status.json

bike_id

Vehicle

system_regions.json

region_id

Region

system_pricing_plans.json

plan_id

PricingPlan

system_alerts.json

alert_id

Alert

Technical ID:

The technical ID has no specific requirements other than that it has to be unique within the dataset. It is commonly the ID from the source data.

...

The following files with their required fields are the minimum requirements:

File

Comment

gbfs.json

system_information.json

vehicle_types.json

station_information.json

Only for dock-based systems

station_status.json

Only for dock-based systems

free_bike_status.json

Optional for dock-based system

system_pricing_plans.json

Exchange of data

Entur will pull data from all providers at a minimum of 60 seconds interval.

...

Change history

Change History