I have recently noticed a problem when following routes or tracks on my 800, with turn guidance turned on. Sometimes, the calculated route diverges from the gpx track and road, and makes a straight line to somewhere further on. The attached screenshot shows an example. I build my own maps, and noticed this problem with mkgmap-r2643. When I build a map with mkgmap-r2585 (the most recent older version I have), I do not see this problem. If someone can point me at any intermediate versions (I don't build mkgmap from source), then I can try and narrow down when the problem first occurs. Steve
Upon further investigation, I think this is caused by my use of routable types as non-routing overlays on roundabouts. When I stop using them, the problem goes away. Strange that this didn't cause a problem with earlier mkgmap builds. Steve On 19 June 2013 20:27, Steve Brophy <steve.brophy@gmail.com> wrote:
I have recently noticed a problem when following routes or tracks on my 800, with turn guidance turned on. Sometimes, the calculated route diverges from the gpx track and road, and makes a straight line to somewhere further on. The attached screenshot shows an example.
I build my own maps, and noticed this problem with mkgmap-r2643. When I build a map with mkgmap-r2585 (the most recent older version I have), I do not see this problem. If someone can point me at any intermediate versions (I don't build mkgmap from source), then I can try and narrow down when the problem first occurs.
Steve
Steve Brophy wrote
Upon further investigation, I think this is caused by my use of routable types as non-routing overlays on roundabouts. When I stop using them, the problem goes away.
ok, this is a known problem and --check-styles will help here. Steve Brophy wrote
Strange that this didn't cause a problem with earlier mkgmap builds.
Yes. Maybe the reason is that the newer releases of mkgmap are likely to produce fewer routing nodes. I see three ways to find out if you are still willing to test releases between r-2585 and r-2643: 1) You install the JDK and subversion and compile older releases on your own. This is really simple now. 2) I can try to guess which changes were important and compile a few jar files for you. 3) Steve could try to create something like a build on demand service which allows to select a specific release. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Routing-problem-on-Edge-800-tp5766106p5766137... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Thanks Gerd. Given that using routable types in this way is known to be a problem, I'll just stop using them. Steve On 20 June 2013 05:43, GerdP <gpetermann_muenchen@hotmail.com> wrote:
Steve Brophy wrote
Upon further investigation, I think this is caused by my use of routable types as non-routing overlays on roundabouts. When I stop using them, the problem goes away.
ok, this is a known problem and --check-styles will help here.
Steve Brophy wrote
Strange that this didn't cause a problem with earlier mkgmap builds.
Yes. Maybe the reason is that the newer releases of mkgmap are likely to produce fewer routing nodes. I see three ways to find out if you are still willing to test releases between r-2585 and r-2643: 1) You install the JDK and subversion and compile older releases on your own. This is really simple now. 2) I can try to guess which changes were important and compile a few jar files for you. 3) Steve could try to create something like a build on demand service which allows to select a specific release.
Gerd
-- View this message in context: http://gis.19327.n5.nabble.com/Routing-problem-on-Edge-800-tp5766106p5766137... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (2)
-
GerdP -
Steve Brophy