
Robert Vollmert wrote:
On Feb 19, 2009, at 17:09, Paul wrote:
I'm seeing very similar behaviour to this. Travelling North/South or South/North across a boundary seems to work fine but East/West or West/East fails. Picking North/South source/destinations I can route a considerable distance but there is a point where I can route to a town but not to the next town 5 miles further away. I have heard of a 13000 point limit on Garmin devices so this is possibly what I'm seeing here as the destinations are all on the same tile. From where I am then routing into Scotland is North/South boundary and Wales is on the same tile so this all works fine
This is with r911 or newer?
r911. I can try with the latest revision tomorrow.
If I use the individual England, Scotland, Wales files rather than the combined great_britain and combine then with mkgmap then routing into Wales (East/West junction so would fail anyway) or Scotland (North/South) simply fails. Is this possibly related to the way in which the individual country files are created from the raw data. I don't have to run splitter against Scotland or Wales but do against England
This is to be expected. Inter-tile routing only works if the tiles were created from one osm-file with one run of the splitter.
I expected so but thought I'd mention it Cheers Paul
Cheers Robert
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev