...
There is no legislation in place in Norway that requires mobility operators to provide this data to Entur, however, it is expected this will be a requirement in the future and we will start to collect this data on a voluntary basis. This document will describe requirements Entur will put on mobility operators for integrating their services in Enturs national platform.
Standard
Expecting a great number of different mobility operators, Entur will require that the exchange of data 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 Feed Specification v2.2 (GBFS), version 2.2 or version 2.3.
https://github.com/NABSA/gbfs/blob/v2.2/gbfs.md
https://github.com/NABSA/gbfs/blob/v2.3/gbfs.md
Expected data
The GBFS 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.
Separation of data
When gathering data across many operators separation of data is a key factor for success. To ensure uniqueness on all ID’s, data provided in the GFBS feeds need to follow a set ID structure adhering to the same convention as all other public transport data in Norway.
IDs
All IDs exchanged with Entur must follow the convention of Codespace + ObjectType + Technical ID combined into a single String separated by :.
...
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.
Feeds
Data for several geographic regions (i.e. cities) should be delivered in separate feeds.
Data for different vehicle types may be delivered in the same GBFS feed. Data providers should always specify which vehicle types are supported by the system in vehicle_types.json.
Language
Feeds should be provided with a Norwegian language code (no, nb or nn) in the discovery file (gbfs.json) and system information file (system_information.json), and all human-readable strings should be in Norwegian.
Minimum requirements
Entur aims to support the full scope of data exchanged through GBFS v2.23 and expects mobility operators to exchange the richest data possible. However, Entur will require a minimum amount of data in order to integrate feeds into the national mobility access point.
...
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.
Use and redistribution of data
All data exchanged with Entur will be distributed as open data under the NLOD-license. Read more about this on developer.entur.org.
...
Open GBFS-feeds for third parties to consume - https://api.entur.io/mobility/v2/gbfs/
Open API for direct integration with consumer-clients - https://api.entur.io/mobility/v2/graphql/
Open JourneyPlanner API for journey planning including mobility services - https://developer.entur.org/pages-journeyplanner-journeyplanner
Change history
| Change History |
|---|