Entur collects data for all Public Transport in Norway and makes this available both as open services for journey planning and as open data. It is required by law that data for all “traditional” Public Transport public transport is sent to Entur and this is already fully implemented today. As the Public Transport Norwegian public transport eco-system develops, new modes becomes a more important part of the Public Transport system become increasingly important and Entur will act continue its role as the a national access point also for mobility datafor all modes of personal travel.
There is no legislation in place in Norway that require 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
Entur expects Expecting a great number of different mobility operators and Entur will require that the exchange of data happen through standard formats both 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 carsharing services to be shared through General Bike Share Service v2.1 (GBFS)
...
Expected data
The GBFS specification sets defines required fields in the different . JSON files. In addition to these required fieldfields, Entur will put have additional requirements on certain data in order to provide useful and consistent data to end-users across multiple mobility operators.
Separation of data
Gathering 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 should need to follow a strict set ID structure after adhering to the same convention as all other public transport data in Norway.
...
All IDs exchanged with Entur should must follow this convention:the convention of Codespace + ObjectType + Technical ID combined into a single String separated by :.
Example:
| Code Block |
|---|
<Codespace>:<ObjectType>:<Technical ID> eg. e-scooter from Lime "YLI:Scooter:PKDVWMOCKA2OZ" |
Codespace:Three
Letter combination A three-letter combination, or codespace, is defined by Entur for all providers (Operator and/or Authorities) sharing their dataeach data provider. This Codespace codespace definition stays remains unique for the each specific operator and the full list of national defined codespaces are available her - data provider and can be used to identify data after being merged into the national dataset.
...
ObjectType:
...
Technical ID:
ID set by the source system
| Info |
|---|
This The primary purpose of this ID conventions primary purpose is to guarantee uniqueness for all ID’s in Enturs National Access Point (NAP) for public transport and mobility data. The full ID should in any implementation always be handled as a |
ObjectType:
ObjectType follows Transmodel to show what data object the id belong to.
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.
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.
Minimum requirements
Entur will aim towards supporting aims to support the full scope of data exchanged through GBFS v2.1 and expect expects mobility operators to exchange as rich the richest data as possible. However, Entur will expect require a minimum amount of data in order to integrate any parties feed feeds into the Enturs national mobility hubaccess point.
The following files with their required fields will be expected as 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 data from all providers at a minimum of 60 seconds interval.
Use and redistribution of data
...
Data will be exposed through 3 different services:
Open GBFS-feeds for 3. third parties to consume - https://api.entur.io/mobility/v2/gbfs/
Open API for direct integration with consumer-clients - (Work work in progress)
Open JourneyPlanner API as an integrated part of a TripPattern including mobilityservices mobility services - https://developer.entur.org/pages-journeyplanner-journeyplanner (Work work in progress)