Hi,

thanks for reporting! Without having had a detailed look at your test case it sounds like the same problem reported by Gerd: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2013q4/019532.html

I forgot to report that changing the order of nodes did not change the result in MapSource, so this is a different problem. Gerd

Hi Franco, did you check whether a tile boundary crosses the area? You can use option write-kml in splitter to create a kml file that you can load in JOSM when the opendata plugin is installed. Gerd franco_bez wrote

GerdP wrote

...

Hi, I forgot to report that changing the order of nodes did not change the result in MapSource, so this is a different problem.

Gerd The case is really strange.

When I build a DACH map - the routing is OK

When I try a data extract from JOSM with just this part of Kaufbeuren - the routing is OK

Anytime I build a BAYERN map - the routing is BAD.

So only the tile generated by splitter for the BAYERN map provokes the bad routing.

I suppose that the tile containing Kaufbeuren generated for the DACH map does not start at the same coordinates as the one generated for BAYERN.

This is the only difference I can imagine.

I uploaded the splitter-generated area information in the hope it might be helpful.

http://files.mkgmap.org.uk/download/167/bayern_areas.tgz

The tile in question is 65020003.

Ciao, Franco

-- View this message in context: http://gis.19327.n5.nabble.com/mergeroads-sometimes-breaks-routing-tp5791132... Sent from the Mkgmap Development mailing list archive at Nabble.com.

Hi Gerd, the KML files were generated while splitting, just forgot to put them in the archive. just in case they might be helpful http://files.mkgmap.org.uk/download/168/bayern.kml http://files.mkgmap.org.uk/download/169/dach.kml -- View this message in context: http://gis.19327.n5.nabble.com/mergeroads-sometimes-breaks-routing-tp5791132... Sent from the Mkgmap Development mailing list archive at Nabble.com.

Hi Franco, during the last days I found out that we probably don't write enough routing information. If I got that right, only "shorter distance" can work, but not "faster time". Garmin maps contain additional information how to get to a major road. It may well be that this lack of information makes routing worse when roads are merged. I am working on that in the high-prec-coord branch... Gerd

Date: Mon, 17 Feb 2014 00:18:06 -0800 From: franco.bez@web.de To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] mergeroads sometimes breaks routing

The problem still persists, just switched from a bayern map to dach map.

just yesterday I built a dach map with mkgmap-r2998 withe the strange routing.

I could provide a new tile if this helps.

-- View this message in context: http://gis.19327.n5.nabble.com/mergeroads-sometimes-breaks-routing-tp5791132... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

Hi Gerd and WanMil, the bug really is NOT related to mergeroads. I joined the "Beuthener Straße" and the "Allensteiner Straße" in OSM as they were split in several ways for no reason. Now the routing has changed, not for the better I'm affraid ;-) ( see screenshots ) But anyway now both mergeroads and no-mergeroads agree in how to route. I compressed the new tile with bzip2 so you have new sample data here: http://files.mkgmap.org.uk/download/163/65020003.osm.bz with mergeroads active: <http://gis.19327.n5.nabble.com/file/n5791269/mergeroads-9350.bmp> with --x-no-mergeroads: <http://gis.19327.n5.nabble.com/file/n5791269/no-mergeroads-17698.bmp> -- View this message in context: http://gis.19327.n5.nabble.com/mergeroads-sometimes-breaks-routing-tp5791132... Sent from the Mkgmap Development mailing list archive at Nabble.com.