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

Wed Jul 8 09:27:41 BST 2009

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

> Da: Mark Burton <markb at ordern.com>
> Oggetto: [mkgmap-dev] [PATCH v3] - beware of the bollards!
> A: mkgmap-dev at lists.mkgmap.org.uk
> Data: Mercoledì 8 luglio 2009, 00:03
> 
> 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.
> 

Why either side? shoudn't be enough one side only for restrict the access to the whole way?

I hope you force the add of an extra node in the way only if another point within 25m does not exists already...

moreover, if a point exist in the way between 25m and 50m, you shoud add the new node by cutting the arc in 2 (otherwise you have a 25m arc on a side and a shorter arc on the other.

so, my proposal might be:
the first point from the barrier is at a distance
<25m: use the existing node
>25m & <50m: put a new node in the middle
>50m: add a node at 25m.

Marco.

> ------------
> 
> 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