...
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 useful and consisten consistent data to end-users across multiple mobility operators.
...
Gathering data across many operators, separation of data is a key factor is separation of data. To ensure this 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:
| Code Block |
|---|
<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
| Info |
|---|
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