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

Wed Jul 8 09:59:33 BST 2009

v4

forgot to make the POI a routing node - it is now - this stops routing
across the POI when the start and end points are within the restricted
area.

-------------

v3

now adds extra points either side of the POI to reduce length of
way that has restricted access. Currently points are 25m away from the
POI. It would be nice if they were really close (like 5m) but if you
try that, the map looks crap due to the limited coordinate resolution.
So, 25m is a compromise between visual appearance and minimising the
extent of the restricted zone.

------------

v2 - quick update based on instantaneous feedback from ML!

Now works for any POI that sets "access=no" (could use the more general
test of any of the access tags being set but let's see how this works
for now).

Default access rights now set in style file.

Any suggestions for a better code for cycle_barrier?

------------

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.

Cheers,

Mark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mb-barriers-v4.patch
Type: text/x-patch
Size: 8334 bytes
Desc: not available
Url : http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20090708/afaaab20/attachment.bin 