Entur collects data for all Public Transport in Norway and makes this available both as open services for journey planning and open data. It is required by law that data for all “traditional” Public Transport is sent to Entur and this is fully implemented today. As the Public Transport system develops, new modes becomes a more important part of the Public Transport system and Entur will act as the national access point also for mobility data.
There is no legislation in place in Norway that require 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 a great number of different mobility operators and will require exchange of data through standard formats both to ensure common functionality and being able to scale across many parties. Entur expects all mobility feeds for both e-scooters, city bikes and car sharing services through General Bike Share Service v2.1 (GBFS)
https://github.com/NABSA/gbfs/blob/v2.1-RC2/gbfs.md
Expected data
The GBFS specification sets required fields in the different .JSON files. In addition to these required field, Entur will put additional requirements on certain data to provide useful and consistent data to end-users across multiple mobility operators.
Separation of data
Gathering data across many operators, separation of data is a key factor. To ensure uniqueness on all ID’s, data provided in the GFBS feeds should follow a strict ID structure after the same convention of all other public transport data in Norway.
IDs
All IDs exchanged with Entur should follow this convention:
<Codespace>:<ObjectType>:<Technical ID> eg. scooter from Lime "YLI:Scooter:PKDVWMOCKA2OZ"
Codespace:
Three Letter combination set by Entur for all data providers (Operator and/or Authorities) sending data to Entur. This Codespace definition stays unique for the specific operator and the full list of national defines codespaces are available her - List of current Codespaces
ObjectType:
ObjectType follow Transmodel to show what data object the id belong to
Technical ID:
ID set by the source system
This ID conventions primary purpose is to guarantee uniqueness for all ID’s in Enturs National Access point for public transport and mobility data. The full ID should in any implementation be handled as a String
Feeds
In addition, data for several geographic regions and / or for different vehicle types for the same codespace may be delivered in the same GBFS feed, or in separate feeds.
In either case, we require that data providers populate system_regions.json and vehicle_types.json to clarify which regions and vehicle types are covered by a specific feed.
If providers wish to combine feeds for dockless vehicles in multiple regions into a single feed, they should use the concept of “virtual station”, to associate vehicles with a specific region.
Minimum requirements
Entur will aim towards supporting the full scope of data exchanged through GBFS v2.1 and expect mobility operators to exchange as rich data as possible. However, Entur will expect a minimum amount of data to integrate any parties feed into the Enturs national mobility hub.
The following files with required fields will be expected as minimum requirements:
File | Comment |
|---|---|
gbfs.json | |
system_information.json | |
vehicle_types.json | |
station_information.json | Only for dock-based systems |
free_bike_status.json | |
system_regions.json | |
system_pricing_plans.json |
Authentication
Entur will offer authentication services for authenticating incoming feeds
https://developer.entur.org/pages-intro-authentication
Exchange of data
Entur will pull data data from all mobility providers. TODO - SKAL vi si noe om forventet frekvens?
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.
Data will be exposed through 3 different services:
Open GBFS-feeds for 3. parties to consume - TODO<link>
Open API for direct integration with consumer-clients - TODO<link>
Open JourneyPlanner API as integrated part of a TripPattern including mobilityservices - https://developer.entur.org/pages-journeyplanner-journeyplanner