Hello, I have spotted a routing issue with a mkgmap generated map. I was able to reproduce it in several versions: 1188, 1228 and 1265. The source file is the Cloudmade Michigan file (Sep 30), that I split using splitter. I can reproduce the issue either using the whole Michigan state (5 tiles) or just the tile where it happens. The tile were it happens has the following bounding box: 44.472656,-87.890625 to 47.548828,-83.144531 You can look at the following map: http://maps.cloudmade.com/?layers=&lat=46.115967&lng=-85.494747&zoom=13&dire... If I try to route from A to B, either on MapSource or on my etrex Vista, I get a line from A to D and a line from D to C If I try to route from A to C (or west of C), MapSource shows an error and the GPS can route but stille displays A-D-B lines. If you try either route (A to B or A to C) in Cloudmade, they work fine. I can provide the osm data (22 Mb gzipped) if needed. Thanks, N.
Hello Nakor,
I have spotted a routing issue with a mkgmap generated map. I was able to reproduce it in several versions: 1188, 1228 and 1265.
Are you generating the map directly from the OSM files or are you converting to Polish format and then generating the map from the Polish files? If the later, you need to limit the number of nodes contained in a single way by splitting the way every now and again. For OSM input files, we split the way every 16 nodes as that was found to be necessary for some maps. If you are generating the map from the OSM files, there must be some other problem we need to identify. Cheers, Mark
Mark, I build directly from the OSM files. I also tried to build the map with assertions enabled (r1265) and it built with no assertion showing up. Thanks, N.
Hi, I can confirm that there are routing issues with that map, don't know what the problem is at this time so I cannot give an ETA for a fix. I will work on it as time allows. Cheers, Mark
Hi Nakor, I haven't yet discovered why it appears to be impossible to cross certain longitudes. I will keep thinking about it and, hopefully, come up with a solution sometime. However, that map is riddled with non-connected ways so even if the bug is fixed, routing will still be very unreliable in that region until someone fixes all the duplicate nodes. Cheers, Mark
Hi mark,
I haven't yet discovered why it appears to be impossible to cross certain longitudes. I will keep thinking about it and, hopefully, come up with a solution sometime.
Sure. Thanks for looking into this.
However, that map is riddled with non-connected ways so even if the bug is fixed, routing will still be very unreliable in that region until someone fixes all the duplicate nodes.
This is WIP. As of now all Interstate, US and state routes should be OK which provides basic routing. But yes the TIGER data has a lot of duplicate nodes... Thanks, N.
However, that map is riddled with non-connected ways so even if the bug is fixed, routing will still be very unreliable in that region until someone fixes all the duplicate nodes.
This is WIP. As of now all Interstate, US and state routes should be OK which provides basic routing. But yes the TIGER data has a lot of duplicate nodes... I would like to know what's the effect of duplicate nodes on rutting. Some areas of Spain are full of them (I have already fixed more than 60.000 in the Northwest). Cheers Carlos
Hi Carlos,
I would like to know what's the effect of duplicate nodes on rutting. Some areas of Spain are full of them (I have already fixed more than 60.000 in the Northwest).
Duplicate nodes break routing because mkgmap makes no attempt to connect ways even if the coordinates of the duplicate nodes are the exactly the same. Cheers, Mark
*From* Nakor nakor.wp at gmail.com <mailto:mkgmap-dev%40lists.mkgmap.org.uk?Subject=Re:%20%5Bmkgmap-dev%5D%20Good%20news%20for%20Nakor%21&In-Reply-To=%3C4AEE522B.4050403%40gmail.com%3E> *on* /Mon Nov 2 03:29:47 GMT 2009/
/ />>/ Well, today's commit to limit the number of points in a way appears to />>/ have fixed that issue as well. />>/ />>/ />Good news indeed. I'll try this next time I update my maps and let you know.
I tried after cleaning up the area. The routing is now correct. Thanks, N.
On Tue, Oct 13, 2009 at 09:22:33AM +0200, Carlos Dávila wrote:
I would like to know what's the effect of duplicate nodes on rutting. Some areas of Spain are full of them (I have already fixed more than 60.000 in the Northwest).
I think that it was mentioned a few weeks ago when discussing the creation of bidirectional cycleways on oneway streets: Only ways that share nodes are connected. That is, routing will not work over duplicate nodes (unless both ways happen to be connected to one of the duplicate nodes, of course). It is not that hard to fix duplicate nodes. In JOSM, find them with the Validator plugin. Double-click a duplicate node warning in the validator error list and hit 3 to center the map at the nodes, so that you can check what to do. Then hit M to merge the nodes, unless it is something else (tunnel or bridge needed, for instance). Marko
Marko Mäkelä escribió:
On Tue, Oct 13, 2009 at 09:22:33AM +0200, Carlos Dávila wrote:
I would like to know what's the effect of duplicate nodes on rutting. Some areas of Spain are full of them (I have already fixed more than 60.000 in the Northwest).
I think that it was mentioned a few weeks ago when discussing the creation of bidirectional cycleways on oneway streets: Only ways that share nodes are connected. That is, routing will not work over duplicate nodes (unless both ways happen to be connected to one of the duplicate nodes, of course).
It is not that hard to fix duplicate nodes. In JOSM, find them with the Validator plugin. Double-click a duplicate node warning in the validator error list and hit 3 to center the map at the nodes, so that you can check what to do. Then hit M to merge the nodes, unless it is something else (tunnel or bridge needed, for instance). It's not so easy when josm finds thousands of duplicate nodes, even fixing them automatically with the validator and also if there's also duplicated ways. You have to fix first duplicated ways, but if some of them are members of any relations, things became more and more complicated. Carlos
It is not that hard to fix duplicate nodes. In JOSM, find them with the Validator plugin. Double-click a duplicate node warning in the validator error list and hit 3 to center the map at the nodes, so that you can check what to do. Then hit M to merge the nodes, unless it is something else (tunnel or bridge needed, for instance).
Validator plugin comes up with lots of false positives (like duplicated nodes one in a way and the other one in a city/county boundary) and is about useless for that purpose in the US. N.
On Tue, Oct 13, 2009 at 09:11:14AM -0400, Nakor wrote:
Validator plugin comes up with lots of false positives (like duplicated nodes one in a way and the other one in a city/county boundary) and is about useless for that purpose in the US.
I tried to silence one class of bogus validator warnings, but the patch was frowned upon: http://josm.openstreetmap.de/ticket/3669 Marko
participants (4)
-
Carlos Dávila -
Mark Burton -
Marko Mäkelä -
Nakor