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 expect 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 expect expects all mobility feeds for both e-scooters, city bikes and car sharing services through General Bike Share Service v2.1 (GBFS)

...

Gathering data across many operators, separation of data is a key factor. To ensure uniqness 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 data 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 dataproviders (Operator and/or Authorities) sending data to Entur. This Codespace definition stays uniq for the spesific operator and the full list of national defines codespaces are available her - List of current Codespaces

...

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 support