I noticed in the past that bicyle routing was sometimes a bit weird, but I just assumed that things were not properly tagged. Recently, it seemed to get worse and worse, and spend some time investigating what was going on. I experimented with BaseCamp on OSX and a GPSmap 62s. And mkgmap r2643 What I'm seeing is that Garmin actually tries avoid anything that is marked with highway=cycleway. The rule for this is: highway=cycleway {add access = no; add bicycle = yes; add foot = yes} [0x07 road _class=0 road_speed=1 resolution 23] Now if I remove the 'access=no', then it just works. Experimenting a bit more, adding a 'add motorcar=no' causes it to misbehave again. Does anybody know what is going on?
On Mon, Jun 10, Philip Homburg wrote:
I noticed in the past that bicyle routing was sometimes a bit weird, but I just assumed that things were not properly tagged.
Recently, it seemed to get worse and worse, and spend some time investigating what was going on.
I experimented with BaseCamp on OSX and a GPSmap 62s. And mkgmap r2643 [...] Does anybody know what is going on?
Use MapSource and downgrade your 62s firmware to 3.90, and everything will start working again. GARMIN is dropping support for the old map format to have enough space in the firmware for their new activity routing for the new map format. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
Now if I remove the 'access=no', then it just works. Experimenting a bit more, adding a 'add motorcar=no' causes it to misbehave again.
Does anybody know what is going on?
Yep, you can search the archives for "active routing" and "Basecamp" In bicycle mode, everything is avoided which has either access=no or motorcar=no on it. Why? Because this seems to correspond with carpool avoidance* in the internal routing of Garmin. In the bicycle profile this is the default setting (you can turn it off if no profile is set, or use the car or motorcycle profile). In some gps units, one can (de)select carpool avoidance in the bicycle profile (new Etrex series?) in the Oregon 600 you cant, garmin has this hardcoded. So with the default style, the bike modus is crap in this unit. For my Openfietsmap bicycle maps, I dont use access=no & bicycle=yes but simply give all non cycleble roads a not routable line. But this means also that we can't use the default style for all kinds of vehicles anymore, unless you use Mapsource and older firmware or older GPS units. (* Please not that this doesn't have anything to do with carpool=no or mkgmap's carpool flag!)
In your letter dated Mon, 10 Jun 2013 22:41:02 +0200 (CEST) you wrote:
In bicycle mode, everything is avoided which has either access=no or motorcar= no on it. Why? Because this seems to correspond with carpool avoidance* in the internal routing of Garmin.
Cool. It looks like manually editing the 'carpool avoidance' bit into the cycling profile has an effect.
participants (3)
-
Minko -
Philip Homburg -
Thorsten Kukuk