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

Tue Jul 7 16:39:42 BST 2009

Mark, may I suggest a totally different approach?

why not to use a couple of restriction relations?

a no_straight_on between the segment before (from) and after (to) the bollard node (via) and a second no_straight_on relation the way round.

Of course with the right "except": bicycle, foot, ...

You could also invent an "internal" relation restriction like "no_passage"

The issue here seems that the "except" key does not foresees "foot".

Would it be feasible?

Ciao.

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

> Da: Mark Burton <markb at ordern.com>
> Oggetto: [mkgmap-dev] [PATCH v2] - beware of the bollards!
> A: mkgmap-dev at lists.mkgmap.org.uk
> Data: Martedì 7 luglio 2009, 16:58
> 
> 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
> 
> -----Segue allegato-----
> 
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev