Worldwide routable Garmin maps: URL REMOVED

Thanks, ligfietser.

So I think the website and map generation scripts work well enough for people to test the functionality and see if it works for them. So, i’ll put the new website online. Feedback is appreciated…

I’m curious if this functionality will drive other people to create suitable TYP files for different target usergroups which could be added to that drop-down box as well. Yes, this is a call for other TYP files :wink:

Note to users: uninstall the previously installed OSM world routable Garmin maps from this site and remove the osm_world_routable directory from c:/garmin/maps (or where you installed the maps previously). Otherwise the typ file will not be loaded.

Tried ctrl+g twice and still nothing.

I posted the problem on another forum. ADVrider.com and someone on there said “Garmin has changed their map rendering and these map sets may not have been updated in a while on Lambertus’ site. Or, they need to update their compilers. I have pulled other maps recently and they work fine so I expect it is the NZ maps that are the issue.”

Yes, they do that with about every update for MapSource. Personally I’m still using 6.13.7 and I don’t test against every version of MapSource or various GPS devices, just following the “release early and often” rule.

Nope, these maps are more up to date then most other (non-OSM) map providers.

Possibly, but I don’t recall reading about any changes made to fix MapSource handling on the Mkgmap mailinglist. I’m using a very recent Mkgmap compiler, so if the problem is Mkgmap then there is nothing I can do.

I think this shows the crux of the problem, but I don’t know how to find out what’s wrong.

One thing I have noticed is that the default directory has changed. This was something like osm world routable and now the default dir is “C:\Garmin\Maps\OSM map”. It has to do with the changes in the nsis scripting of mkgmap. I havent updated the map since a few months and now I see that the mapsource installer didn’t uninstall the previous one because of the changes in the installer.

So maybe in the NZ case there are some leftovers of the old version which needs to be uninstalled first?

Yes, I was just about to comment on this. The NSIS install script from the latest Mkgmap does not use the parameters provided to Mkgmap and thus NSIS always uses “OSM Map” as map name (which I think is a bug). It is therefore more important then ever to remove old maps first before installing the new one and make sure the the registry key “HKEY_LOCAL_MACHINE\SOFTWARE\Garmin\MapSource\Families\OSM world routable” is also removed.

OSM Map is the standard name if you dont specify one in your settings. It comes from the Family name (in the older installer series-name was used). If you tweek the nsis installer you can also let the installer remove osm world routable if it is already installed.

Edit: maybe you should check this and use your old ‘osm world routable’ dir name, because if someone makes a mkgmap custom map, it will be installed in the same directory ‘osm map’ and this can lead to map conflicts too

Thanks for explaining this. To be frank I think its weird…

Imagine you have a range of maps in your portfolio:
Lambertus
– world routable
– world topo
– world seamap
– Netherlands small tiles

Then “lambertus” would be the family name right? And the usual way to differentiate between the range of maps is to use different product id’s right? Or should every map have it’s own family id/name and each new version of that map a different product id?

Edit: oh, hmm, there’s also the series name…

The way Garmin organises its maps is not so logical as we would like :-/
If you give every new update another PID it will be a mess in the windows register and on your disk with old map remains. Better leave it with the default 2000/3 combination.

Yes with the series-name you can add the datestamp of the maps now. This will only show up in Mapsource and not in the register or in the default dir name (thats the family-name if I’m correct?). Maybe you could also add the country extract name to the series-name?

No… really??</> :wink:

Yes, that seems wise …

Ok, I’ll see if that can be added easilly.

Afaik: yes.

Possibly, but that won’t allow you to install more then one country at the same time. So I was thinking about defining a unique family/product id for each country…

Does anyone know where I can find or have the directions for loading multiple maps that were on the site before JaVaWa GMTK came out. I have tried to use the program but my Dutch is a little rusty and the google translation is just slightly less confusing. I’m thinking someone has probably asked this before so i apologize. I did a forum search but could not find and answer. Thank you for your help.

Hi - how often the tiles used to generate the country maps (fast to download) are refreshed from OSM? I’m asking this since I updated some streets in OSM afew days ago, they are now available through OSM web interface and I’m wondering if I get my country map today I will get them!

Thanks

Perhaps this tool (MapRenamer) from the same author will help you out :slight_smile:

That would be very nice if the Garmin maps were updated that fast, but unfortunately that isn’t the case.

During the last year the maps have been updated approx. once or twice per month but I aim to do it every week and the new servers make that possible. Look at the date listed below the slippy map on the website to see if the map has been updated recently. That date reflects the date at which I started the update. I’m always using the planet dump for a new map version which is usually released on Wednesdays or Thursdays.

So if, for example, the date below the map lists the 14th of May then the data in the maps are from the planet dump released on May 12 or 13. In this particular case edits up to May 11 should be visible in the Garmin maps.

Regarding the New Zealand problem where the map only shows at certain zoom levels, I too have been frustrated by it since September of last year and I have tried many different downloads but with the same result. I have since been using the NZ OpenGPS Maps and while they have been working fine and will suffice for an upcoming bicycle tour that I am planning for the next NZ summer season, I would prefer to use OpenStreetMap as there is more detail available (minor ferries are missing in NZ OpenGPS).

A thought occurred to me that perhaps the problem is with the eastern edge of the tiles being right at the 180 degree east line. Could you try a build with the tile edge at 179 degrees east and see if that fixes the problem?

Thanks,

Peter

Hi again. I just did a test and downloaded the Russian tile that borders the 180 degree East longitude and it exhibits the same behavior as does New Zealand in that I can see the coastline at the 500 km scale but when I zoom in it disappears. However when I select a small piece of coastline and move my mouse over it, it shows the name “Coastline” and names of other details, but not the map itself.

I strongly suggest that it is an edge of the world problem. (Here ye find dragons and other manner of strange beasts!) Perhaps the solution would be to tile to 179 degrees 59 minutes, not 180 degrees.

Peter

Peter, I’ve confirmed the problem by just looking at the NZ Auckland tile. It’s quite possible that the 180 degree line is the problem, but how and where (i.e. Splitter or Mkgmap). I’ll gather some data to test with and write about this to the Mkgmap dev list.

Funny thing is that I can zoom in normally to 100 km, but one step further and the map disappears. Then, if I move the map to the left (i.e. scroll towards the 180 degree line) the map shows up again and when I zoom in again the map disappears again. This process can be repeated a few times more, but you end up looking at the empty ocean off the east-coast of the Northern Island in closeup.

Thanks for your report.

Edit: Ah, now I see. The problem also appears if you zoom in on the western part of the tile. You can keep zooming in as long as you keep a tile edge visible in the screen, but this doesn’t apply for the top or bottom tile edge; only the vertical tile edges. As soon as you scroll the left or right tile edge out the window the map disappears.

I have encountered a problem with a new version of a map for MAPSOURCE. In the original map there are areas where the lines of a border of region collide with the lines of roads. When you convert OSM into MAPSOURCE theese colided road disappear. As a result in last version of map there is a lack of roads, really miss half of all roads.
http://www.openstreetmap.org/?lat=-0.4005&lon=-78.54222&zoom=15&layers=M

That is unfortunate. I’m filtering all lower administrative borders from the OSM data (because they clutter the map) for a long time already. But when those lines are also used for roads… I’ll have to think about a solution…

Thanks for your work Lambertus. I have downloaded a custom map from the tiles covering my area (Canberra, Australia) and installed it via mapsource and then after removing that installation I tried using the version for direct copy to my Garmin directory on my device (Garmin Edge 800). Both times the map installed and appears on my device and is enabled but when I try to navigate with the device I get an error message telling me that there are no routable roads in my area. Could this be true? Any known issues with some Garmin devices such as Edge 800? Any suggestions?

thanks

I’ve downloaded and installed the Canberra tile in MapSource and I can route across Canberra just fine. Can you post the link to your custom map download?