Table of contents

Search on the page

Bike Parking (bicycle parking spaces)

This data set will be replaced on 30 June 2026. New data set

#AutoTranslate

Brief Description

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

Latest news

2025-07-09 A new field appeared in the data, which 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 dataset will include bicycle and car parking spaces, and now occupancy forecast data as well.

Source: https://pixabay.com

Functional Description

The data feed consists of an approx. 900 KB file which is retrieved daily from an SBB database. The feed contains data for around 1,200 bicycle storage locations with names, geographical coordinates and some optional information.

Technical Description

The files are JSON files encoded in UTF-8. They are 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 spaces).

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 characteristics, including in particular:
    • “name“: the name of the bicycle park.
    • “stopPlaceUic”, “stopPlaceSloid”: external IDs (UIC and SLOID),
    • “source”: Notes on the source system and its internal IDs (e.g. ELM / SBB First & Last Mile 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 (null) or absent, and new properties can be added.

The code below shows an example with a single bicycle parking space for illustrative 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"
  }
}