...
Minimum requirements
Entur will support
Authentication
Exchange of data
...
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