I see a strange behaviour lately: If I select a POI as the destination for a route, the calculated route will go to a completely unrelated coordinate on the map and will "jump" in a straight line to the destination. The calculated route is therefore completely unusable. The "wrong" coordinate the routing goes to was in one case at the border of a map tile, but thats not always the case. If I select a coordinate just beside the POI, routing is fine. Has anybody else seen this behaviour? It is triggered if you select a POI from the POI list on the GPS unit (Oregon 300 in my case). Regards Thilo
Thilo Hannemann wrote:
I see a strange behaviour lately: If I select a POI as the destination for a route, the calculated route will go to a completely unrelated coordinate on the map and will "jump" in a straight line to the destination. The calculated route is therefore completely unusable. The "wrong" coordinate the routing goes to was in one case at the border of a map tile, but thats not always the case.
If I select a coordinate just beside the POI, routing is fine.
Has anybody else seen this behaviour? It is triggered if you select a POI from the POI list on the GPS unit (Oregon 300 in my case).
Regards Thilo
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I see behavior like this with routes when I test the routing graph in MapSource. I created the map in gpsmapedit, and when I test the routes in this program they work correctly, but the same route after compiling with mkgmap will give strange routes, with straight-line jumps. If goes the wrong direction on a road for what looks like the correct distance, then jumps back to where it should have been and continues. Garvan
Hi Thilo, Could you please produce a concrete example of this behaviour? A small sample OSM file or area URL would be very useful to help investigate this. Cheers, Mark
Mark Burton wrote:
Hi Thilo,
Could you please produce a concrete example of this behaviour? A small sample OSM file or area URL would be very useful to help investigate this.
Cheers,
Mark _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I found an error in my map source, so I apologize for the previous post. I still don't understand the straight line jumps that resulted from my error, but at least it was a rubbish in - rubbish out case. If I can understand what conditions cause it, then I will file a bug report - if one is needed. Thanks Garvan
Hi Garvan,
I found an error in my map source, so I apologize for the previous post. I still don't understand the straight line jumps that resulted from my error, but at least it was a rubbish in - rubbish out case. If I can understand what conditions cause it, then I will file a bug report - if one is needed.
OK - thanks. You're using Polish format files as input to mkgmap? If so, you should be aware that more development time has gone into supporting the OSM file input so you may be running into issues that have been fixed for OSM files. In particular, the OSM reader removes short arcs which are known to break the routing. Cheers, Mark
Hi Mark, the problem is present in the map "Radkarte" that you can download from my wiki page http://wiki.openstreetmap.org/wiki/User:Radfahrer/Radkarte . But I will try to reproduce it with a small map, so that it is debuggable. It may take a while though, because I have only limited time this week. I wanted to hear if anybody else experienced this problem as well. I'm not sure whether it is related to the one that Garvan describes, because a) I'm using direct osm input (not MP) and 2) only the last part of the route is a straight jump, the route until then would be fine if the destination it goes to would be the right one. Regards Thilo Am 05.07.2009 um 17:32 schrieb Mark Burton:
Hi Thilo,
Could you please produce a concrete example of this behaviour? A small sample OSM file or area URL would be very useful to help investigate this.
Cheers,
Mark _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Mark, I've not forgotten about this bug, it is still biting me. The problem is that it I wasn't able to reproduce it with a small map. It seems to be related to the size of map. My maps are very POI ladden, so that might trigger it. By reducing the splitter tile size the frequency of occurence was reduced a lot. If I reduce the size of the map to anything suitable for debugging I don't see it. So I will monitor the behaviour with my regular map-builds and report any findings, but as I do about one run per day this will take its time. Regards Thilo
Hi Thilo,
I've not forgotten about this bug, it is still biting me. The problem is that it I wasn't able to reproduce it with a small map. It seems to be related to the size of map. My maps are very POI ladden, so that might trigger it. By reducing the splitter tile size the frequency of occurence was reduced a lot. If I reduce the size of the map to anything suitable for debugging I don't see it. So I will monitor the behaviour with my regular map-builds and report any findings, but as I do about one run per day this will take its time.
OK - whenever you have something to work from, I will look at it. Cheers, Mark
participants (3)
-
Garvan & maew -
Mark Burton -
Thilo Hannemann