Table of contents

Search on the page

Bike Parking (bicycle parking spaces)

#AutoTranslate

Brief description

‘Bike Parking’ is a data set in GeoJSON format with around 1,200 bicycle parking spaces at railway stations in Switzerland.

Latest news

2025-07-09 A new field has appeared in the data but should be ignored at the moment: ‘properties_publicAccess’: ‘False’

2025-07-09 Outlook: In the coming weeks/months, we will release a new major version of the data. The new data set will include bicycle and car parking spaces, as well as occupancy forecast data.

Source: https://pixabay.com

Functional Description

The data feed consists of a approx. 900 kB file which is accessed daily from an SBB database. The feed contains data on around 1,200 bicycle parking locations with names, geographical coordinates and some optional information.

Technical description

The files are JSON files encoded in UTF-8 and based on the GeoJSON standard (see https://de.wikipedia.org/wiki/GeoJSON).

The data structure is a GeoJSON ‘FeatureCollection,’ which contains a list (array [ ]) of ‘features’ (the bicycle parking).

Each feature (bicycle parking) mainly contains the following fields:

  • id‘: technical key,
  • type‘: ‘Feature’ (required by the GeoJSON standard, as a definition of the type used),
  • geometry’ a GeoJSON data structure for a point with the WGS-84 coordinates,
  • properties‘: other properties, including in particular:
    • “name“: the name of the bicycle parking facility.
    • “stopPlaceUic”, “stopPlaceSloid”: external IDs (UIC and SLOID),
    • “source”: Notes to the source system and its internal IDs (e.g. ELM / SBB’s Erste & Letzte Meile team)
    • “category”: “parking”; “subCategory”: “bike_parking”: currently constant fields.

In the future, we expect that the fields “id”, “type”, “geometry”, “name” remain unchanged, while other properties can be empty (zero) or non-existent, and new properties can be added.

The following code shows an example with a single bicycle parking space for illustration purposes. Ultimately, the data feed itself should be considered for the actual structure and properties.

{
 "type": "FeatureCollection",
 "bbox": [
   8.9022774,
   47.4885437,
   8.9022774,
   47.4885437
 ],
 "features": [{
   "type": "Feature",
   "id": "9a074e29-a611-473d-84ac-4f92ed3bfe34",
   "geometry": {
    "type": "Point",
    "coordinates": [
     8.9022774,
     47.4885437
    ]
   },
   "properties": {
    "name": "Veloparking Aadorf",
    "stopPlaceUic": 8506013,
    "stopPlaceSloid": null,
    "source": {
     "name": "elm",
     "id": "719"
    },
    "category": "parking",
    "subCategory": "bike_parking"
  }
}