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 (62)
Topic: Problems
Sort
Jason (China)
Reply
Permalink
Flag
0
0
Can you add a 'highway=scramble' tag to the map and render it with an appropriate style?
Admin:
I don't see any description for highway=scramble at OSM wiki. What is it?
ReplyPermalinkFlag0025th December 2024 1:47pm
Hello admin, love your work and just registered for this website.
I have one thing to share with you and everyone who see this comment: Although I can see everyone on the internet says Garmin GPS device only accept SDHC 32GB storage card, among my test, SDXC 512GB card works fine on my GPSMAP76. The only thing you need to do is using a 3rd party software to format card into FAT32 (windows can't do this with large capacity cards).
With this been said, plus these cards are very cheap ... Read More
Admin:
I'll add it to my TODO list, but note it's not easy to implement it, as base map and DEM tiles do not cover the same areas, and it would require remaking contour lines/DEM tiles, which is a lot of work for big maps, like the one you ask for. Additionally, I'll do it first with base maps, so it will take a while before I can prepare DEM maps divided as you want.
25th November 2024 7:32am
Page 1 of 13