logo separator

R: [mkgmap-dev] [PATCH v1] - beware of the bollards!

From Marco Certelli marco_certelli at yahoo.it on Tue Jul 7 15:00:45 BST 2009

--- Mar 7/7/09, Mark Burton <markb at ordern.com> ha scritto:

> Da: Mark Burton <markb at ordern.com>
> Oggetto: [mkgmap-dev] [PATCH v1] - beware of the bollards!
> A: mkgmap-dev at lists.mkgmap.org.uk
> Data: Martedì 7 luglio 2009, 15:30
> Fed up of being routed in your car down city streets only
> to find the
> way is blocked by a bollard? Well, if so, this is the patch
> for you.
> If a way has a bollard on a point, the segments of the way
> that
> connect to the bollard have access restrictions placed on
> them. By
> default, a bollard implies: access=no, foot=yes,
> bicycle=yes.
> Testing using mapsource shows that it generally works as
> expected
> although if the destination cannot be reached by any other
> route, it
> routes straight through the bollard rather than failing! If
> the
> destination can be reached by some other route, even if the
> route is
> really long, it will avoid the bollard.
> I have chosen Garmin code 0x660f (pillar) for the bollard.
> On my etrex
> it appears as a small dot in the way.
> As usual, all feedback is welcome.


I read on wiki that cycle_barrier has no "default" access rule. I think you should be more conservative and, in absence of explicit tags, let bicycles passing through (wiki says that cycle_barrier should only imply motor_vehicle=no)


> Cheers,
> Mark
> -----Segue allegato-----
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev


More information about the mkgmap-dev mailing list