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

2009-07-08 Thread Mark Burton
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

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

2009-07-08 Thread Mark Burton
> 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. Sorry, my comment is incorrect. It only stops routing across the POI when the start point is in the restricted area not when both the st

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

2009-07-17 Thread Mark Burton
Howdy folks, Shall I commit this stuff or does it need more work? To recap, it stops routing across a bollard (or other POI that has access restrictions). It works OK except in the case where the start and end positions are close to the bollard. As previously discussed, that is probably not fixa

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

2009-07-20 Thread Clinton Gladstone
On Fri, Jul 17, 2009 at 10:32 PM, Mark Burton wrote: > Shall I commit this stuff or does it need more work? I have not yet had time to test this, but would it be an idea to optionally enable or disable this behaviour? I know that mkgmap is slowly growing an unmanageable number of command line opt

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

2009-07-20 Thread Mark Burton
Hi Clinton, > I have not yet had time to test this, but would it be an idea to > optionally enable or disable this behaviour? I know that mkgmap is > slowly growing an unmanageable number of command line options, but > this still might help if we discover unwanted side effects. I can do that. My

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

2009-07-20 Thread Torsten Leistikow
Clinton Gladstone schrieb: > In particular, I wonder how this would affect special cycling maps > which use (or abuse) automobile routing for bicycles. This shouldn't be a problem, since the bollard implementation is based on the access values. And such a map has to deal with the access tags in ge

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

2009-07-20 Thread Felix Hartmann
2009/7/20 Torsten Leistikow > Clinton Gladstone schrieb: > > In particular, I wonder how this would affect special cycling maps > > which use (or abuse) automobile routing for bicycles. > > This shouldn't be a problem, since the bollard implementation is based > on the access values. And such a m

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

2009-07-20 Thread Torsten Leistikow
Felix Hartmann schrieb: > Well but one allways has to remap these values to motorcar=yes for > special purpose maps, as only car/motorcycle provides proper routing. Yes, but you have to do such a change for all highway types anyway (bicycle=* -> motorcar=*, motorcar=* -> bicycle=*). So there is no

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

2009-07-20 Thread Mark Burton
Hi Felix, > Well but one allways has to remap these values to motorcar=yes for special > purpose maps, as only car/motorcycle provides proper routing. Never understood that need to route as a car, but I am happy to cater for such a foible. > I have not > really read through the patch as it does

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

2009-07-20 Thread Felix Hartmann
2009/7/20 Mark Burton > > Hi Felix, > > > Well but one allways has to remap these values to motorcar=yes for > special > > purpose maps, as only car/motorcycle provides proper routing. > > Never understood that need to route as a car, but I am happy to cater > for such a foible. > bicycle does r