Skip to end of banner
Go to start of banner

Mobility Data Collection - GBFS (WIP)

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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 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 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 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 uniqness 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.

All data 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

ObjectType:

ObjectType follow Transmodel to show what dataobject the id belong to

Technical ID:

ID set by the source system

This ID conventions primary purpose is to garantee uniqness for all ID’s in Enturs National Accesspoint for public transport and mobility data. The full ID should in any implementation be handled as a String

Minimum requirements

Entur will

  • No labels