Yes Klaus, I already wrote that in my first reply to your question. In the latest releases of Basecamp (since 3.2.1) all access rules are ignored. Some things still work, like oneway=yes. And the avoidance options. I reported this bug on the Garmin Forum but I doubt they will ever look on it, because OSM is not supported. See my (openfietsmap post at https://forums.garmin.com/showthread.php?t=21681&page=5 Garmin has started to update the firmware on the latest GPS units too so I'm afraid routing will break as soon as everybody has updated their firmware (haven't checked if it's the case on the latest firware though). I changed the routing in my cycling maps and removed all roads with bicycle=no to non-routable lines. It is a dirty workaround that is not working for someone who wants to choose another vehicle to route with. :-( ---------- "toc-rox" wrote: Further investigation has shown a significant difference (concerning routing) between MapSource (Windows, 6.16.3) and BaseCamp (Windows, OS X, 3.2.2). It seems that the access bits (e.g. access=no; bicycle=yes; ...) in BaseCamp are not working as expected. Could someone verify my observation? Thanks - Klaus

As the Garmin developer writes on the forum, they don't recognize it as a bug unless someone can show this behaviour affects also their official Garmin maps like Topo Germany. Maybe someone can test this? Klaus wrote:

And I hope that someone finds the reason for the new routing behavior.

I just noticed that even cars are routed on cycleways on OSM maps... This happens only in Basecamp, not in the latest Mapsource 6.16.3 nor on the GPS. Although they have never supported OSM tags, why is this changed? There must be some bug in the latest BC releases.

You can see this "phenomenon" also with CN-Maps ;) Am 28.08.2011 um 11:10 schrieb Minko:

I just noticed that even cars are routed on cycleways on OSM maps... This happens only in Basecamp, not in the latest Mapsource 6.16.3 nor on the GPS.

Although they have never supported OSM tags, why is this changed? There must be some bug in the latest BC releases. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

The last time my new garmin (Nüvi 1390) tried to route via pedestrian... Am 28.08.2011 um 12:13 schrieb Minko:

I don't agree, this is totally different, CN-maps never supported bike routing. Even in Mapsource and on the GPS cyclists are routed on major highways on CN maps. There are no cycleways on CN either so cars will never be routed on cycleways simply because they don't show them. This post is dealing with some new routing instructions of Garmin. Mapsource is quite compatible with the OSM access tags and routing will not be perfect but at least cars will stay out of cycleways and cyclists from major highways (not always, I must agree). In the latest Basecamp releases this is completely different.

Martin wrote: You can see this "phenomenon" also with CN-Maps ;) _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

this might be slightly off-topic, but still: why not avoid the whole problem altogether? i use a non-routable base map containing everything you see on the screen, on top of that 2 transparent routable maps, one for car, one for bicycle, switched on/off according to the vehicle used. this has at least 3 major advantages: * the whole access issue is handled by mkgmap - if you don't wanna ride a cycle along a motorway, don't render it in the 1st place * it let's you assign different road_speeds/road_classes for different vehicles - i want a good speed/class for primary highways if i drive a car, but on a cycle i'd prefer better class and speed for smaller roads * last but not least: the styles are a lot less complicated and easier to maintain Am 27.08.2011 19:32, schrieb toc-rox:

Further investigation has shown a significant difference (concerning routing) between MapSource (Windows, 6.16.3) and BaseCamp (Windows, OS X, 3.2.2). It seems that the access bits (e.g. access=no; bicycle=yes; ...) in BaseCamp are not working as expected.

Could someone verify my observation?

Thanks - Klaus

-- View this message in context: http://gis.638310.n2.nabble.com/Routing-Documentation-and-Best-Practice-tp67... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

On 08/28/2011 01:29 PM, Minko wrote:

Unfortunately Garmins mapbrowser don't support multi-layered maps.... :-( You have either a basemap that doesn't route, or an empty map with just roads. Not both, unless we stick to the discontinued Mapsource or we can find a trick.

You can make a special TDB file and overview map file for Mapsource with just one family ID and all your existing map tiles.

i think one could make 2 extra tdb files/overview maps for mapsource - 1 to bundle base/car, another to bundle base/cycle Am 28.08.2011 18:33, schrieb Minko:

Sounds interesting, but how will you do that? Can you give an example which I can download?

I don't see how you can tell mapsource which tile to take when you switch vehicle in the routing menu.

Ralf wrote:

...

You can make a special TDB file and overview map file for Mapsource with just one family ID and all your existing map tiles.

---

mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Ralf, I don't think it will work in Mapsource/Basecamp with two different routing layers in one map. For instance you have a car based routing map in Layer 1: family-name=Layer1 input-file: 10000001.osm.gz input-file: 10000002.osm.gz And a bicycle/foot routing map in Layer 2: family-name=Layer2 input-file: 10000003.osm.gz input-file: 10000004.osm.gz And below those maps Layer 3 with all the topographic data. If you combine this in Mapsource (or better, Basecamp because here lies the problem): tdbfile=yes family-id=1234 family-name=AllLayers input-file: 10000001.img input-file: 10000002.img input-file: 10000003.img input-file: 10000004.img How can you tell Basecamp which layer to choose if the bicycle profile is chosen? Routing has to be on 10000001 and 10000002.img but BC don't know this. It only works if you see two maps, one bike map and one car map. ---------- Ralf wrote: On 08/28/2011 06:33 PM, Minko wrote:

Sounds interesting, but how will you do that? Can you give an example which I can download?

Sure. I first run mkgmap on the OSM files to generate the IMGs and the gmapsupp.img. The config file looks somewhat like this: gmapsupp [more options ...] family-id=1234 family-name=Layer1 input-file: 10000001.osm.gz input-file: 10000002.osm.gz family-id=5678 family-name=Layer2 input-file: 10000003.osm.gz input-file: 10000004.osm.gz [possibly more input files ...] This produces the IMG files and a gmapsupp.img for the GPS unit which contains 2 layers which can be switched on and off in the unit. If you use a custom typ file you'll need two, one for each layer. Mapsource can't do this, so I need a different setup: tdbfile=yes family-id=1234 family-name=AllLayers input-file: 10000001.img input-file: 10000002.img input-file: 10000003.img input-file: 10000004.img This will make a TDB file and an overview map for mapsource in which both layers show up. For mapsource you need a typ file with all types in it. An example of such a map is my topo map of Germany, which contains an OSM layer and three SRTM layers: http://www.kleineisel.de/blogs/index.php/osmmap/ _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev