TYP file yes, but style no…
Altough any help with improving the default style sheet is welcome, seems the guys on the mkgmap list are not so willing to change it.

If the OSM map is being created as opaque (i.e. no --transparent option) then the base map should be hidden. I think this may be a “feature” of the Zumo. I’ve not heard of the base map showing through the OSM layer on other Garmin devices (which, in most cases, let you disable the base map anyway).

A completely different question: when is the next update scheduled? The current data is from 4/11.

Thanks,
Peter.

I’m sorry. I appear to make that distinction mistake a lot…

Thanks for your ideas on this. Do you think it’s possible for the baselayer to have a higher priority then a standard OSM map?

An update is running now.

Not unless your mkgmap compile is really strange. I can’t imagine why the base map draw priority would be set high; in fact I suspect that the base map isn’t treated the same way as other maps by GPSr (at least on my GPSMap). For instance, if you try to route, the GPS will never route on the base map if another routing layer is available. I would have thought the firmware would ensure that the base map was always drawn below any other map, but that’s just a guess.

All I can add here is that on my Zumo the City Navigator NT map overlays the base map, but the OSM map doesn’t.

Beddhist, have you tried other OSM maps? There’s a list of alternative sources here: http://wiki.openstreetmap.org/wiki/OSM_Map_On_Garmin/Download
It would be good to know if the problem is general, or specific to Lambertus’ build.

OK, I just tried this one: http://debian.mcmillan.net.nz/nzosm/64010011-20101118-0503.img The same thing happens. I can see the relief shading from the basemap and h’way 1 not far from my home shows twice.

This one I installed differently: renamed the file to gmapsupp.img and copied it into the \Garmin dir on my Zumo. For Lambertus’ maps I used Mapsource to install.

Routing uses only the OSM map. I tested it, turned the OSM map off and recalc’ed. Then it used the basemap.

Regards,
Peer.

Hello All,

I have discovered another problem with garmin maps from openstreetmap. Under the “Point of Interest” → “Food”, if I select a restaurant, it displays the Category as “African” even though the restaurant is tagged as “cuisine=indian”. It works correctly for “chinese”. Again, the “Asian” category does not display any restaurant which are tagged as “cuisine=indian”. I have Garmin nuvi 1390T.

I wanted to load the screenshots of the same but do not know how to upload my images. Any help would be appreciated.

That’s interesting. “African” is not a known Garmin restaurant category. What GPS do you have?

The following assumes you are using a map created with mkgmap’s default style.

mkgmap takes OSM key-tag pairs and converts them into Garmin objects. The OSM cuisine=indian key-tag pair does not result in an Indian restaurant in the Garmin map because Garmin GPS units do not offer an Indian restaurant category. So any restaurants tagged like this are instead given the default Garmin restaurant code (0x2a13) which on my GPS at least fall under the “Other” restaurant category.

The OSM cuisine=chinese key-tag pair does have a corresponding Garmin category, hence why it works as you expected.

The only restaurants that will appear in your Asian category are those that have been tagged with cuisine=asian, as this is the only key-tag pair that mkgmap uses to generate Garmin objects in the Asian restaurant category.

You can see which key-tag pairs are being used by mkgmap to generate its maps here:
http://www.mkgmap.org.uk/svn/wsvn/mkgmap/resources/styles/default/points (scroll down to the section with amenity=restaurant & …

If you create your own style for mkgmap

If you create your own style and compile your own maps, you can assign any key-tag combination you like to any particular Garmin restaurant category. For instance, I assign the following key-tag pairs to the Garmin Asian restaurant category:
cuisine=asian | cuisine=japanese | cuisine=korean | cuisine=malaysian | cuisine=noodle | cuisine=thai | cuisine=vietnamese

Thus I get many more restaurants falling into that category for the maps that I make.

I have Garmin Nuvi 1390T.

I am using the osm india map downloaded from http://garmin.na1400.info/routable.php

Can you tell me how can I upload the screenshots to this forum to make the things more clear to the users.

I have never tried to upload images directly to this forum, but you could upload them to somewhere like imagebucket or flickr and post the links.

I forgot to add that I’m using the NZOpenGPS map here in NZ, compiled with cgpsmapper and I don’t have this problem. It’s only with mkgmap compiled maps.

hi,

I have another problem with my garmin with the OSM. When I select a railway station (which is a node on the railway track) from the list of POIs under Travel (or Transport) and ask it for routing, it says “Can’t calculate route”. However, when I select any other point near the railway station node, it is able to calculate the route. Is it because of some limitation with the OSM data.

Just noticed one more problem from the OSM routable map for Garmin (1390T).

Areas tagged as “building=apartments” or “building=yes” does not show-up on the OSM routable map on the garmin Nuvi 1390T.

That could be a good thing…

Unless the station is also connected to a road, or your Garmin allows a mixture of on and off-road routing, that’s probably why you can’t route to it.

It may be that they are the same colour as the background. If you hover over a building, do you get a different tool-tip?

That is “by design” in the last two updates. I’m trying to make the maps a little lighter (easier on the server, less download bandwidth needed, buildings are not needed for routing, etc.). I’ve also filtered “type=communication” in the latest update as I don’t think it adds to the map.

This is the pre-processing filter before the planet data is piped into the initial Splitter run:

osmosis/bin/osmosis --rx - --tf reject-ways building=* --tf reject-nodes type=communication --wx -

No, I do not get any tool-tip when i click (I mean touch) the building area.