
Steve wrote:
I've never checked how the carpool bit works.
However it must have (or had) an effect in the past on at least some devices. Reported working here: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2011q3/012140.html
In fact there have been observations that it has unwanted side effects http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2011q3/012138.html http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2011q3/012147.html
The links are referring to observations I made in Basecamp. In Basecamp carpool avoidance is connected to motorcar=no and access=no tags. It doesn't seem to matter if there are tags with carpool=yes or carpool=no. Only the access and motorcar keys seem to trigger the carpool avoidance. On some devices this carpool avoidance is by default "on" and cant be switched off (for instance in the bicycle vehicle modus on my Oregon 600). In Basecamp this is the default rule: highway=cycleway is set to access=no & bicycle=yes -> access=no triggers carpool=yes -> cycleways are blocked for cyclists :( So it is not a question if real carpool lanes are interesting or not, it would be great if we could control this tag in the mkgmap styles to prevent those unwanted side effects. Minko