Why Use VeloMap maps for cycling?

  • High Contrast layout optimized for small size screen of Garmin GPS (1.8-4"). Clear differentiation between all street types. Separate low contrast Layout for tour planning on your PC/desktop.
  • Paved or Unpaved? Easy to spot road type. Bridges and tunnels shown. Cycle tracks and cycle lanes shown. Arrows for one way streets...... See the map legend for more.
  • Cycle relevant information like drinking water, city bike stations or bicycle shops searchable and shown prominently.
  • Cycle routes shown prominently BESIDES the streets differentiated by colour and size based on importance (other maps show cycle routes instead of streets so that you don't know what kind of street the route is on, bad for planning).
  • Navigation - Highly sophisticated Autorouting specialised for cycling. Don't cycle on big streets anymore because you got lost. The VeloMap focuses very strictly on road cycling, commuting and touring/trekking. Maps trying to focus for many purposes can never be as good.
  • Easy installation to Garmin Mapsource, Garmin Basecamp or Qlandkarte GT for on PC planning.
  • Good Documentation because everything you want and need to know for using the maps is found on VeloMap.org
  • Contourlines based on the best free (as in beer) data - viewfinderpanoramas.org - as separate download for most countries. Much higher quality in mountainous regions than the mostly used void filled SRTM3".
  • Map Incomplete? You can participate and Add missing to Openstreetmap. Every Week the maps become better and more complete! If you think anything "bicycle relevant" features are missing (but recorded and documented in OSM), drop a comment and I will try to add it.

 

New Here?:

Lots of information, don't get lost, Get Started!

 

Navigation - Find the shortest nice route -- or find the most cyclefriendly route.

Garmin offerst two seperate Autorouting modes supported by all GPS and Software. Shorter Distance will actually be shorter than on any other Garmin map I have tried (even though high traffic streets are avoided). Faster time finds nicer routes with even less traffic and makes some detours if needed. Autorouting using  Mapsource 6.16 or Basecamp v3 up to 200km trip distance without via-points. Around 100-150km with Oregon/Dakota/2010_Generation_etrex/GPSmaps. If you route over longer distances, cities are avoided except for cycleroutes crossing cities.  

Map Layout

Clean map layout 100% optimized for readability on GPS. Be assured that on the GPS maps therefore are very well readable. As for desktop use the layout has too much contrast, there is a second layout optimized for planning with Mapsource/Basecamp/Qlandkarte GT.

 

You can Improve the Maps!!

These maps are based on the freely available wikipedia like Openstreetmap Map Database. You should consider uploading your GPS tracks to openstreetmap and/or help out if you find errors or missing data.  There is a short introduction here listing the most relevant links to get you startet: Participate  

Who can make use of the maps?

The maps offered here are of course, currently primarily used by Garmin GPS users, but you don't need to have a Garmin GPS to use them. Qlandkarte GT an opensource and freely available Map Viewer can display them in all their pride, and also if not owning a Garmin GPS or buying maps from Garmin you can install the free Garmin Basecamp or Mapsource software and enjoy autorouting like you have not enjoyed before.  

Need a map for Mountainbiking or Hiking?

Head over to https://openmtbmap.org and get it. Whereas the Velomap showss non paved tracks and trails in very subtle colors, on the openmtbmap you can see difficulty gradings both for Up- and Downhill. Also mtb and hikingroutes are prominently shown.  

30.05.2021 – Huge Updates to OpenMTBMap and VeloMap Maps – New Contourlines and much more!

Some people may have noticed that there are 10m contourlines as separate maps on the download pages since about 4 weeks. During the process of generating them I noticed quite a few problems in steep areas that should not have been there. So began a long process of improving the contourlines. The problem was that the filters the map compiler runs against any lines were not suited  to contourlines. With the help of others mkgmap is now improved a lot in this regard - and kinda resulting from this also normal maps have improved a lot when zoomed out (thanks to Gerd on his never ending improvements to mkgmap). When zooming out - the further you zoom out now - the bigger the improvement.

For all countries and continent maps - except Asia full continent map (will come in 1-2 months - it is a huge work to create them) there are now 20m equidistance contourlines - and 10m equidistance contourlines. On all maps updated from 30. May 2021 you can select 10m or 20m contourlines. The 10m contourliens are now also integrated into the installer.  For Mac OSx they are integrated too  - and while for windows users the 10m contourlines have to be downloaded separately, for OSx most countries already bundle them in the gmapi Installer.  I had planned to integrate the 10m contourlines on 9 April 2021 for the 12 year anniversary of the OpenMTBMap website - but that work turned out to be way way bigger than anticipated - it is easy to create 2-3 maps, but creating 180 different countries/regions means everything is way more complicated and more bugs have a chance to appear somewhere in the process.

Less visible updates however also important. I have reworked the whole relations (MTB routes, Bicycle Routes, Hiking Routes) integration. Before it was kinda random if several routes were using the same way - which name was given to the way. Now this is ordered from most important to least important routes.  This previously had also caused problems that if say a regional route and a national route shared the same way - and the regional route was handled before the national - when zooming out the national route was not shown. This is now fixed. 

Complete overhaul of the windows installers - I spent about 80 hours optimizing the installer to be faster (yes still a bit slow - as they use lzma instead of lzma2 and do not support multithreaded unpacking of data) and correctly integrate the 10m and 20m contourlines. Also hope they are easier to understand now. There is still some work to be done - concerning if you install separate contourlines only map on both VeloMap and OpenMTBMap installer (with contourlines as separate download) - I will integrate a warning for this in the future.  It is now also possible to only install a separate contourlines only map without installing the map itself but obviously I do not recommend this.  Updating the installers I have often thought about just moving the windows maps to gmapi format - because I then would not need to fuss around with NSIS installers - but there are so many cool things that can be done with NSIS installers, plus the fact the windows format is IMHO still better than the gmapi format (except the windows registry) - that I recommend windows users to stick on using the classic map format. 

 

Old Contourlines based on Lidar Data:

vs the new 20m contourlines - based on the same data but with improved douglas peucker filtering. Notice how the lines are much better aligned to each other. there is no more one contourline crossing another because they were simplified at different locations. This effect will be everywhere - but because the actual distance difference is low - it will only be really visible in very steep areas like on this region. It is a little bit more exact now - but the main difference is that the rounding to the Garmin GPS device is more coordinated.

 

vs the new contourlines at 10m equidistance (and resolution 24 instead of 23 to be even more exact - one point is exact to around 2.8m at resolution 24 vs 5.4m at resolution 23 - this uses a lot more data however. I recommend to use 10m contourlines in hilly or flat areas - and 20m in real mountains like the Alps.

As the maps are updated over the next 24 hours - there will still be slight discrepancies and installers of maps with separate contourlines do not match the map. For OpenMTBMap this should happen much less often than for VeloMap maps (only for english language openmtbmap maps with separate contourlines). From Tuesday 01. June this should all be fixed. I will also still add some more gmapsupp.img contourline maps for continents or huge countries which are right now not online yet. As I need to create them manually with MapInstall this will still take a week or so. For Asia continent contourlines gmapsupp.img map is not possible - as it breaks the 4048 tiles limit. The windows 10m and 20m Asia contourlines map will still come in 2-3 weeks or so - there was a mistake on the first try an my server needs over 2 weeks computing nonstop to create them.

If there are no problems that I overlooked - I will update the Europe map in 4-5 days. The contourlines are ready for the Europe map - but I want to wait to see if I maybe missed some bug related to the installer that I simply did not notice. Creating the Europe map is always quite an effort - over 40 hours of compile time (due to 8 versions - 4x openmtbmap, 4x velomap).

 

Upcoming Improvements over the next few weeks: I started working on the zoom levels - but stopped this to focus on getting the contourlines updated. I will soon pick this up again and plan to move most ways/trails one zoom level down. Openstreetmap is more and more detailled and I feel it is needed to adapt this. I would prefer doing this only for Europa but I cannot maintain two styles differing in this regard at the same time. Most of my users use the maps in Europe and here it is simply better to have some features appearing later.  I already overworked the details when zoomed out further - and think there was a big improvement. The main problem is rivers - I spent hours trying to work around the inconsistencies in river mapping in OSM and making sure important rivers show in lower zoom levels. However the problem being here is that rivers are more and more mapped with relations - and many of those super relations for rivers like the Danube or other major rivers are broken or partly missing. It is better now than 2-3 months ago in my maps - but not perfect. Essentially it would be best to move away from OSM to another more consistent data source for the very far zoomed out regions - but I do not know how to do - nor which data source would be compatible.

 

Also I am working on a new layout - for people who prefer more of a classic hiking map look. I hope to finish it in 4-5 weeks. I still need some time testing it out in practice on my Edge, Oregon and etrex devices. I still feel there needs to be some adaptions for better contrast - typical paper maps are simply different. However I aim to make it easy to understand for people just used to topographic paper maps. My opinion is still that the color layout I am using right now is way better than the classic maps in readability and possibility to transmit information. All other OSM based maps contain way less information about the quality / usability of ways. But some people are just overwhelmed by it - so I will create that layout for them. 

 

Unrelated to this - I have overworked both OpenMTBMap and VeloMap websites - and included many tutorial videos. Many things were a bit outdated and I tried to correct most of them. Having so much content also means it takes a lot of time to keep it up to date. Most video tutorials are aimed at beginners - however the route planning videos for example may still contain a few tips and tricks also for regular users. I still feel that written tutorials are better than video tutorials - but because some people prefer seeing video tutorials I created video tutorials for nearly all common desktop related tasks with the OpenMTBMaps and VeloMaps. Somewhere on my roadmap are also videos using GPS devices - but they are more complicated to produce so still need some time. I will also still create a video comparing the different layouts and explaining a bit more about them. However that will have to wait until I have finished the classic topographic layout.

 

Personally I spent the last 6 months in Taiwan improving my Chinese and just came back 10 days ago to Europe. I plan to go to Taiwan next winter again - but lets see about coronavirus situation there (was the safest country in the world until 3 weeks ago - and while I am not afraid of catching the virus - also due to vaccination - I do not like lockdowns so will only go back if there is no risk of lockdowns anymore. I really hope the coronavirus related problems are over for Europe. This has also cost me many donators but luckily there are still enough people donating to OpenMTBMap or VeloMap to allow me to continue. I will soon for the first time since 2014 I think, increase the prices a bit. People using subscription will not be affected.

20.03.2021 – New Contour Lines for Europe and some countries

Todays (20.03.2021) Europa map comes with new contourlines - New Lidar based contourlines are also available for the following Countries: Switzerland, France, Iceland, Slovakia, Belgium. And in Germany for the state of Sachsen-Anhalt. So please make sure when updating the Europe map to redownload the new contourlines. Actually the country maps of France, Belgium and Iceland had new contourlines for some months. The country maps of Switzerland, Slovakia, Germany and Sachsen-Anhalt will from today/tomorrow onwards have the new contourlines too. Most of western Europe is now covered with LIDAR based altitude data - about half of central Europa, and very little of Eastern Europe. Outside of Europe it's mainly ALOS World data.

Some other recent updates to the maps have been:

Reworking of peak prominence. 

Fixing Marina to adapt to current tagging standards which contradict the old ones.

Also use mtb:imba if mtb:scale does not exist.

Various small fixes and changes.