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

Tue Jul 7 16:33:03 BST 2009

Hi Dermot,

> Yes but...
> 
> 2009/7/7 Mark Burton <markb at ordern.com>:
> 
> > My testing indicates the later. If there is no other route, mapsource
> > at least, ignores the restriction.
> 
> Consider a case where you have a very simple configuration which I
> shall try to draw in ASCII:
> 
> 
> 
> |
> |
> |
> +---------------x-------------o-----------
> |
> |
> |
> 
> 
> Let "o" be the bollard and x your destination. For badness, let's also
> assume that there is only a single way segment between o and the
> junction at "+".
> 
> So now the entire piece of road from junction to x is access=no. Do
> you think the restriction will be ignored in this case?

Yes, mapsource ignores the restriction.

> (maybe this won't matter in the real world, I'm just saying it now in
> case it could be. I suppose the harder and more correct solution would
> be to carve off 5m either side of the bollard into separate restricted
> segments)

I had already considered doing that but it's not worth it unless
the real GPS units behave differently from mapsource.

Cheers,

Mark