It’s CITY CYCLING time – some of you may even be involved in your municipality – a good opportunity to have a look on the OpenStreetMap (OSM) cycling ways in our city Heidelberg.
Welcome to part 8 of our how to become ohsome blog post series. This time we will show you how to set up a more complex filter with several OR and AND combinations for the ohsome API to get the length of the mapped cycling ways in OSM. Like in part 4 of our series, we will again show you in a Jupyter Notebook how you can use Python to make this nice complex ohsome query and visualization in one go.
The idea is to analyse the mapped cycle ways in Heidelberg in OSM. Therefore we need to have a look on how cycling infrastructure is mapped in OSM. To set up the filter, we want to know which tags do we need to extract all the cycle lanes, ways and roads. There is more than one way to tag cycle ways, lanes or paths in OSM, described for example on this OSM wiki page. Instead of requesting every possible tag by itself, all combinations of tags that can be used to define a cycle way within OSM can be requested at once using our new filter parameter. This also prevents ways being counted twice, which might have several of these tags associated with them.
Our tag combination is based on Hochmair, Zielstra, and Neis’s paper Assessing the completeness of bicycle trails and designated lane features in OpenStreetMap for the United States and Europe. In their study they explored the cycling features in the United States and Europe. We take their filter combination and extend it with tags of the German cycling infrastructure mapping methods listed on the corresponding OSM wiki page. After a pre-query for each of the tag combinations we found out that for some of them no data was available for the region of Heidelberg, so we excluded them. As a result we got a filter that consists of 25 different tag combinations.
The final filter looks like following:
type:way and (
(cycleway=opposite and oneway:bicycle=no) or
(highway=track and bicycle=designated and motor_vehicle=no) or
(highway=path and bicycle=yes) or
(highway=path and (bicycle=designated or bicycle=official)) or
(highway=service and (bicycle=designated or motor_vehicle=no)) or
(highway=pedestrian and (bicycle=yes or bicycle=official)) or
(highway=footway and (bicycle=yes or bicycle=official)) or
(cycleway in (lane, opposite_lane, shared_busway, track, opposite_track)) or
(cycleway:left in (lane, shared_busway)) or
(cycleway:right in (lane, shared_busway)) or
(bicycle_road=yes and (motor_vehicle=no or bicycle=designated)) or
The official number given by the city of Heidelberg of cycle path network is about 480 kilometers, which is almost 3 times as many kilometers as there are in OSM. The difference may be due to the fact that there are some side roads that have an extra lane, others do not, or that sometimes a appropriate tag is really missing in OSM. In addition, in the explanation of the cycle road map for Heidelberg, the city’s network includes normal roads which have signposted cycle routes running through to neighbouring communities such as Leimen, Eppelheim, Dossenheim and Edingen.
We can also take a spatial look at the current expansion of the cycle path network. For this we use the same filter as above but in the data extraction endpoint of the ohsome API. A snippet of the request can be found here.
So if you are interested in the mapped cycling infrastructure in OSM in your city, just change the bounding box geojson in the code and find it out . The complete Jupyter Notebook with all the code and explanations can be found here.
Information on the ohsome OpenStreetMap History Data Analytics Platform and more examples of how to use the ohsome API can be found here: