Hi WanMil,
> > The problem probably only occurs with ways close to the tile
> > boundary that are clipped. I don't know if we can save a route
> > restriction when the to-node or from-node lies outside of the boundary.
>
> Would it solve the problem if the boundary nodes are added earlier just
> before the RestrictionRelation.addRestriction(MapCollector) is called?
The boundary nodes are added for all ways before style processing, even for
all non-routable ways and shapes.
This wastes a few cpu cycles, but I don't see a problem or a solution here.
Gerd
As far as I understand the to-node and the from-node are calculated by
mkgmap. So I don't understand why there is a problem if the boundary
nodes are available. Can you explain a bit more in detail?
WanMil
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
