Bug - mkgmap distance to insert additional points on straight lines too long
Well the title says most of it. AFAIK there is some setting in mkgmap, that splits up ways, or adds additional points to ways that are fully straight. I tested around and to me it seems that it needs to be less than 800m as this might solve some long distance routing probs, and routing probs over tile borders. Currently it's much longer. Can this be adjusted in sourcecode easily? -- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
To Specify it a bit more: Affected are currently only GPS devices which support active routing (this new profile based stuff which we don't know how it is encoded), and Basecamp v 3.3 upwards (including Basecamp v4 beta). Using older GPS Firmware or Mapsource this problem is not present. I'm still trying to debug it however. Strangely GPSMapedit reports several polylines as type=0x5 instead of 0x05, or 0x6 instead of 0x06 - but no such types are present in my style... On 13.08.2012 18:42, Felix Hartmann wrote:
Well the title says most of it. AFAIK there is some setting in mkgmap, that splits up ways, or adds additional points to ways that are fully straight.
I tested around and to me it seems that it needs to be less than 800m as this might solve some long distance routing probs, and routing probs over tile borders. Currently it's much longer. Can this be adjusted in sourcecode easily?
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
On 13/08/12 17:42, Felix Hartmann wrote:
Well the title says most of it. AFAIK there is some setting in mkgmap, that splits up ways, or adds additional points to ways that are fully straight.
I can't find such a thing after a quick look, but it should be easy to add if there isn't one. I'll take a look at it later today. ..Steve
well I found the main problem. As soon as I inserted a single 0x00 type of line, or made 0x14, 0x15 or 0x1a (!!!!!) routable, then the autorouting for the whole map got some weak spots - amongst them the problem with lines over 800m without any point not usable for routing anymore, or any routable line connected to a line with any additional attribute (like unpaved, or motorcar=no) also being blocked for routing (only within one tile). I still think however, that it showed that we shouldn't allow lines without a node for over 800m. I would love to see if there is any improvement to long distance autorouting, by making sure that the map doesn't contain any routable lines fully straight without points. I don't think those are often present, but ferries would often be longer than 800m without any node. Also if I knew where I could change the maximum nodes, that a single routable line contains, there could be affections on routing. On 14.08.2012 13:59, Steve Ratcliffe wrote:
On 13/08/12 17:42, Felix Hartmann wrote:
Well the title says most of it. AFAIK there is some setting in mkgmap, that splits up ways, or adds additional points to ways that are fully straight. I can't find such a thing after a quick look, but it should be easy to add if there isn't one.
I'll take a look at it later today.
..Steve _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
I don't understand this issue, I can route from Hoek van Holland, NL to Harwich without any problems, even in BC 3.3.3. It contains a straight ferry line with some nodes more than 800 m apart. http://www.openstreetmap.org/browse/way/121724962
As I observed later, it only happened to play havoc, once some lines, that basecamp didn't expect to be routable, contained routing information (while Mapsource 6.13 to 6.16 or Basecamp v2 didn't mind at all) - then once straight lines with a connection to a non supposed object, started to crash, while most things still worked without problems. I therefore would like to eliminate lines without nodes for distances over ~800m, because I assume, that Basecamp expects nodes. I think this could for example improver routing over several tiles - which mkgmap created maps still don't properly do (the routing algos try never to go back into a tile, it left if possible - you can notice this if you make artificially small tiles, and than observe pretty different routes). I would hope, that this could improve intertilerouting therefore. On 15.08.2012 10:20, Minko wrote:
I don't understand this issue, I can route from Hoek van Holland, NL to Harwich without any problems, even in BC 3.3.3. It contains a straight ferry line with some nodes more than 800 m apart. http://www.openstreetmap.org/browse/way/121724962
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
Hi
all) - then once straight lines with a connection to a non supposed object, started to crash, while most things still worked without problems. I therefore would like to eliminate lines without nodes for distances over ~800m, because I assume, that Basecamp expects nodes. I
I'll also look into the situation when a non-routable line connects to a reputable one. Of course it should'nt connect but the cod may not make the distinction. Although adding nodes so that none are more than 800m apart is not too difficult there are other bits of code that removes nodes. So I'm going to trace through exactly what happens in what order. ..Steve
[Sorry about the last reply, I was using an unfamiliar mail app which lost all my text before sending.] There may be a bug with connecting to a non routeable line as I am not sure that the code distinguishes between roads and other lines when adding routing nodes.
actually, I found out some more ways to trigger Basecamp running havoc. .e.g setting a road with road_type=0 road_speed=7 0x13 resolution=21 and Basecamp or my etrex 30 run fully havoc on straight lines over 800m, which are connected (with max 2 links) to such a road. On 14.08.2012 13:59, Steve Ratcliffe wrote:
On 13/08/12 17:42, Felix Hartmann wrote:
Well the title says most of it. AFAIK there is some setting in mkgmap, that splits up ways, or adds additional points to ways that are fully straight. I can't find such a thing after a quick look, but it should be easy to add if there isn't one.
I'll take a look at it later today.
..Steve _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
participants (3)
-
Felix Hartmann -
Minko -
Steve Ratcliffe