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

Version 1 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 usefull and consisten data to end-users across multiple mobility operators.

Separation of data

Gathering data across many operators a key factor is separation of data. To ensure this ID’s provided in the GFBS feeds should follow a strict structure

  • No labels