Participate in OSM – Tagging Guidelines

The VeloMap is based on . This means that you can and should help to improve the maps. You can think of openmtbmap as an equivalent to Wikipedia - but not as a general encyclopedia, but one for map data. Instead of writing on how you can work on the maps myself - I will include links to the most important wiki pages on If you don't know what Openstreetmap is about - you can read up on it here:

If you wan't to help improve the maps please read through the introduction here: Beginners_Guide Note that point 5 of the Beginneers_Guide is done here on for you. So you can improve the map by gathering data with your GPS, then uploading the GPX tracks, and then editing the openstreetmap data with JOSM or Potlatch. There is also a good overview here on the map_making_overview.


Important tags in OSM for the Velomap - or what should I map?

However to enable good autorouting there are some more tags not listed on this page that you should add:

  • You should use at least one of the following tags for pathes and tracks: Tracktype or Smoothness
  • Adding Surface is never bad, but for routing tracktype or smoothness would be enough: Surface
  • Also keys like sac_scale, mtb:scale, mtb:scale:uphill, trail_visibility and usability are evaluated. They will however only be used if none of the above is present.
  • In cities it is imortant to tag traffic_signals and a bit less important to tag Stop signs.
  • To make the routing understand that a road is really big, tag appropriate number of lanes. A primary road which is tagged Oneway=yes  & Lanes=2 can be considered to be not very nice for cycling.
  • Also if a road is part of the E-Road-Network and has  International_Reference set this is important to tag (so it can be avoided).
  • Of course both cycle routes and mtb routes (if the mtb route is on a paved road) can be valuable information and it is assumed that the way should be preferred.
  • Also cycleway=lane, cycleway:left=lane, cycleway:left=opposite_lane and all keys found here are of course used for autorouting and rendered on the map: Bicycle
  • I encourage to stopp the fuss about pathes, footways and cyclways by using the Designation
  • Very important for assessing whether a road is inside a city, or outside is to use source:maxspeed. Using this I can promote tertiary and secondary streets outside of cities, but degarde those high traffic inner city connector roads.

Soon and most importantly if you get bad routing even though the above keys are used, I will implement: Class:bicycle which you can use to promote or degrade any way. Just like car drivers know that based on street classification a primary is usually faster to drive than a tertiary street, with class:bicycle you can specify importance for cycling. Because it is simply impossible to tag everything objectively. So if the most popular tags and the ones above are already tagged, but the route is using suboptimal ways, use class:bicycle to specify the priority a road should have for cycling. For this map I will evaluate class:bicycle, class:bicycle:commute, class:bicycle:touring and most importantly class:bicycle:roadcycling




7 comments to Participate in OSM – Tagging Guidelines

  • Peter Rindfuss

    Hallo Felix,

    in der Velomap Germany gibt es südlich von Berlin ein kleines Stück Einbahnstraße, das weder in der Realität noch, soweit ich sehe, in OSM existiert. Das verhindert in Basecamp das Routing von Südwest nach Nordost auf dieser Straße (Mühlenstraße L77 an der Brücke).

    Was mag da das Problem sein?

    Viele Grüße, Peter

  • Bernhard Muenst

    Guten Tag,
    velomap_germany hat zwischen Echterdingen und dem Flughafen Stuttgart (N48° 41.176′ E9° 10.975′) einen Berg eingezeichnet, zumindest Höhenlinien 420, 440, 460 und 480 m. Den Berg gibt es nicht in echt und auch nicht in den Kartenebenen “CyclOSM” und “Radfahrerkarte” von Wie lässt sich dieser Fehler beheben?
    Viele Grüße Bernhard

    • extremecarver

      Wird sich nicht beheben lassen. Ganz ab und zu gibt es Fehler im DEM Ausgangsmaterial. Basen Württemberg hat leider keine LIDAR Daten veröffentlicht zur freien Benutzung. Ich nehme mal an ich nutze da ALOS World v3.2 – das ist meist das beste weltweite freie Modell und besser als viewfinderpanoramas 3″ bzw SRTM 1″. Ab und Zu gibts halt Fehler. Nur wenn die gesamte Kachel – sprich 48-49 E9-10 schlecht wäre könnte ich die austauschen. Danach sieht es mir aber nicht aus.

Leave a Reply