Maps for Garmin based on OpenStreetMap
Known issues
Garmin maps format is not public, so map generation process (done with mkgmap) is based in reverse engineering. As format has not been completely deciphered yet, there's still a number of problems affecting the maps. They have the advantage that data on them are most probably more up to date than commercial ones, although in some areas coverage is lower. Another great advantage is that anyone can complete or correct missing or wrong data. Below there is a list of known issues regarding the use of the maps.
- Address search: in order to find a given street using 'Search by address' option of the GPS it is necessary to type the name of the street exactly as it is on the map, e.g. 'Calle de los Derechos Humanos' (Human Rights Street). It may be a problem for languages like Spanish or French, in which the name of the way is preceded by the type of way: Avenida de América, Paseo de la Castellana, etc. as it will be difficult to know how the name of a street is in the map: it may be Calle Derechos Humanos, C/ de los Derechos Humanos, Avenida América, etc.
To avoid this, some changes are introduced that let you omit the type of way and also particles before the main part of the name. For the examples above, typing “Derechos Humanos”, “América” or “Castellana” will be enough. Some irrelevant words common at the end of street names, like Avenue, Street, Road (English), Strasse, Weg (German), kalea, bidea (Basque), etc. are also removed. - Roundabouts exit number: if a way entering a roundabout shares a node with an exiting way, that exit is not taken into account for the 'Take exit # to the right' instruction, although on screen it is correctly displayed. In fact, it is caused by errors in the data used to generate the map, and must be fixed on OpenStreetMap data.
- Advanced functions: some advanced functions, such as lane indication, on screen speed limit display, crossing search, etc. don't work.
- Topographic maps on MapSource: contour lines behavior in MapSource is quite variable, some times they are displayed and some times they are not, without a known motive, just showing the number that indicates the height but not the line. However, although they are not seen, they are there and can be used, for example, to calculate a route profile (Edit menu->Route Properties->Show Profile...). On BaseCamp and QLandkarte GT this problem doesn't occur.
If you detect any other problem in the maps, other than those due to errors or lacks in OpenStreetMap data, please use the comments at the en of this page to report it.
You can leave your comments on this page below:
Comments (63)
Topic: Problems
Sort
Ivars Brencis (Christchurch, New Zealand)
Hi!
I noticed that those buildings on OSM that have the "house" tag on OSM are not saved into this map. The commercial buildings and others show on map but in places where there is residential house outlined on the OSM map, the garmin version shows blank space.
I noticed that those buildings on OSM that have the "house" tag on OSM are not saved into this map. The commercial buildings and others show on map but in places where there is residential house outlined on the OSM map, the garmin version shows blank space.
Admin:
Hi Ivars
That's intended. Most buildings without any special information (no name, no public use, etc) in residential areas are removed to keep the map clearer. I guess you are familiar with OSM, so you'll have noticed the high increase in buildings presence in the map. That was leading to maps really cluttered in some urban areas.
That's intended. Most buildings without any special information (no name, no public use, etc) in residential areas are removed to keep the map clearer. I guess you are familiar with OSM, so you'll have noticed the high increase in buildings presence in the map. That was leading to maps really cluttered in some urban areas.
Reply
Permalink
Flag
1
025th January 2018 12:21pm
Ueli Streuli (Wil, Switzerland)
I tried to install Contourlines and OpenStreetmap Finland, but contourlines are not properly installed (Windows10). Basecamp doesn't start with the message that there was a Problem mith VP Finland , in mapsource contour lines are missing.
With other countries e.g. norway there is no such Problem.
Thanks for your help.
With other countries e.g. norway there is no such Problem.
Thanks for your help.
Admin:
You are right, thanks for reporting the problem. I'll fix it and update files.
21st January 2018 6:21pm
Hello
I've seen the problem on basecamp that causes a straight line to be shown instead of correct route calcultation. It look like newer versions of mkmap will correct this. Just for your info.
I've seen the problem on basecamp that causes a straight line to be shown instead of correct route calcultation. It look like newer versions of mkmap will correct this. Just for your info.
Admin:
Thanks for the info. What version (date) of map are you using? I'm currently using latest mkgmap to build maps, so there shouldn't be that problem.
11th April 2017 11:44pm
In the map for my area, a couple of streets appear as continuous, but they are not. They are actually separated by a wall, so you can't drive thru them. How do I fix that, or how do I report it to be fixed?
Admin:
You can zoom in to the affected area at OpenStreetMap web site, then click Share button at the right hand side bar of the page and send the link here. If you want to make further edits, I suggest you create an OSM account and edit data yourself.
29th December 2016 10:25pm
Page 10 of 13
I'm aware of such problem in some countries. I started to correct it, but updating contour lines requires a lot of time. I'll try to update Malaysia contour lines next.