Hi Thorsten, Steve saw similar problems regarding tile boundaries. He used an older version of MapSource (6.10.?) and maybe tiles that were not split properly. His problems were gone after updating to MapSource 6.16.3 and using a new split. Gerd
Date: Sun, 9 Mar 2014 09:26:55 +0100 From: kukuk@suse.de To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] new branch NOD127
Hi,
On Thu, Mar 06, Gerd Petermann wrote:
Hi all,
I've created a new branch NOD127 : http://www.mkgmap.org.uk/download/mkgmap-NOD127-r3086.zip
This is used to test the latest findings regarding the NOD file format. Most of it is understood now, thanks to Steve and his display tool :-)
I made quite some tests the last two days with it.
In principle the result is much better then with trunk, but sometimes I see really bad choices, like leaving a highway and using a primary/secondary street only to go back to the highway a little bit later. Or using highways which are much longer then the direct highway. What I found out: this happens always if the direct route would cross a tile border. And I'm not sure if this is really only a problem of the branch, because I can now see similar problems on trunk, too :(
I have two styles: "streets", which contains only bigger routes and very few POIs, thus has really big tiles. Here the routing is very good. The second style, "basemap", contains all streets and a huge amount of POIs, thus small tiles. Here I suddenly see similar problems. So looks like at some point we introduced a problem with routing via tile borders, at least with MapSource. I'm currently trying to find out when this got worse.
Thorsten
-- Thorsten Kukuk, Senior Architect SLES & Common Code Base SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev