logo separator

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

From Martin Simon grenzdebil at gmail.com on Tue Jul 7 17:15:37 BST 2009

2009/7/7 Mark Burton <markb at ordern.com>:
> 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.

Wow, cool!

I was actually silently waiting for someone to implement that feature.. ;)

But what about using turn restrictions instead of manipulating the
nearest segments of  the ways?

The reason is: if my destination is on side "A" of the bollard on the
restricted segment, garmin would still send me via the bollard whe
it's shorter because it ignores all restrictions if the destination is
within a restricted zone, right?

Thank you for working on this! :)


More information about the mkgmap-dev mailing list