Stronger Intertile Routing Problems with Basecamp 4.2.1?
Well, I like some other people have noted that Basecamp 4.2.1 doesn't autoroute very well. I tried through many examples, and what I found out was that intertile routing seems to be the major problem. As soon as the route leaves one tile more than two times - to go back into it, seems to crash the routing - if it is the preferred way. Anyone else finds another solution? (hope this image passes the size limit of the mailing list..) -- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
Hi Felix, I cant reproduce those crashes, how do you make that route? First in Mapsource and then copy it to Basecamp (because I cant see those tileborders in BC)?
Well, I like some other people have noted that Basecamp 4.2.1 doesn't autoroute very well. I tried through many examples, and what I found out was that intertile routing seems to be the major problem. As soon as the route leaves one tile more than two times - to go back into it, seems to crash the routing - if it is the preferred way. Anyone else finds another solution?
(hope this image passes the size limit of the mailing list..)
Sorry for taking so long to reply. Actually the route screenshot is only from Mapsource. In Basecamp routing this small distance actually calculates forever/crashes. Yes in Basecamp there is no way to check for tileboarders. I did notice that most routes calculated just fine, be it Mapsource or Basecamp 4.2.1 Those that created problems on short or "easy" distances - were all somehow related to tileborders. That's how I noticed the problem. On 03.07.2013 07:54, Minko wrote:
Hi Felix, I cant reproduce those crashes, how do you make that route? First in Mapsource and then copy it to Basecamp (because I cant see those tileborders in BC)?
Well, I like some other people have noted that Basecamp 4.2.1 doesn't autoroute very well. I tried through many examples, and what I found out was that intertile routing seems to be the major problem. As soon as the route leaves one tile more than two times - to go back into it, seems to crash the routing - if it is the preferred way. Anyone else finds another solution?
(hope this image passes the size limit of the mailing list..)
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
Felix Hartmann <extremecarver@gmail.com> wrote:
Well, I like some other people have noted that Basecamp 4.2.1 doesn't autoroute very well. I tried through many examples, and what I found out was that intertile routing seems to be the major problem. As soon as the route leaves one tile more than two times - to go back into it, seems to crash the routing - if it is the preferred way. Anyone else finds another solution?
I found also some strange behaviour with Basecamp 4.2.1 on OS X. http://picpaste.de/Bildschirmfoto_2013-07-04_um_00.00.37-hag375X7.png Dont know if the problem is a tile border, but the routing has some serious bugs. Regards Johannes
I sent the attached mail a couple of weeks ago. Reducing --max-nodes seems to make a difference; I tested another route this morning in Basecamp after creating it in Mapsource and it worked fine (both latest versions); and I have tested on my Dakota 20. My guess is Garmin software uses fixed length buffers, so if there is too much information in the tiles it sorts it on size order and disposes of the smaller bits of information. I'm not saying it's perfect; but it helped me. If someone who is experiencing routing across tile boundary problems tries with a --max-nodes=750000 and confirms this fixes the problem then we could have a work around. Regards, Geoff. -----Original Message----- From: Johannes Formann Sent: Wednesday, July 03, 2013 11:12 PM To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Stronger Intertile Routing Problems with Basecamp4.2.1? Felix Hartmann <extremecarver@gmail.com> wrote:
Well, I like some other people have noted that Basecamp 4.2.1 doesn't autoroute very well. I tried through many examples, and what I found out was that intertile routing seems to be the major problem. As soon as the route leaves one tile more than two times - to go back into it, seems to crash the routing - if it is the preferred way. Anyone else finds another solution?
I found also some strange behaviour with Basecamp 4.2.1 on OS X. http://picpaste.de/Bildschirmfoto_2013-07-04_um_00.00.37-hag375X7.png Dont know if the problem is a tile border, but the routing has some serious bugs. Regards Johannes _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hello, I tried reducing the max-nodes but that did not change the problem. After a short investigation a possible reason are large differences in the road_type and road_speed. Anyone observed a similar behaviour? Regards Johannes
Am 06.07.2013 12:43, schrieb Johannes Formann:
After a short investigation a possible reason are large differences in the road_type and road_speed.
Anyone observed a similar behaviour? I think Felix reported this problem some time ago, but this shouldn't have anything to do with the new problem. I've also problems if road_speed stays same.
@Geoff: While changing max-nodes splitter will create different tile-boundaries, so problematic location will move. Is this the thing which "solves" the problem for you? Henning
Hi Henning, I recompiled my maps this morning changing --max-nodes back to 1500000, but could not find a inter-tile routing problem; so I think it must have been something else that broke my routing before. It was probably using routable overlays for trunk roads and primary roads at higher zoom levels which I corrected recently after I realised I could not route down these roads anymore. I did notice on recalculating the route created in Mapsource that Basecamp produced a slightly different route, which ended up being a little shorter than that produced in Mapsource. The differences were not where it crossed a tile boundary though. Sorry I can't help further. Geoff. -----Original Message----- From: Henning Scholland Sent: Sunday, July 07, 2013 12:06 PM To: Development list for mkgmap Subject: Re: [mkgmap-dev] Stronger Intertile Routing Problems withBasecamp4.2.1? Am 06.07.2013 12:43, schrieb Johannes Formann:
After a short investigation a possible reason are large differences in the road_type and road_speed.
Anyone observed a similar behaviour? I think Felix reported this problem some time ago, but this shouldn't have anything to do with the new problem. I've also problems if road_speed stays same.
@Geoff: While changing max-nodes splitter will create different tile-boundaries, so problematic location will move. Is this the thing which "solves" the problem for you? Henning _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
yes - I noticed that big changes in road_type (meaning more than 1) so eg from 4 to 2 are less likely to be routed than 4 to 3. I tried that out by creating identical left/right options - then testing which one is choosen. 4 to 1 or 4 to 0 had actually quite big penalties. This only mattered on Basecamp 4.1 or higher, new generation GPS with up to date firmware. Mapsource or older Basecamp or older GPS firmware was not really affected strangely. Road_speed I dunno - I would guess there are just the usual probs (doens't like to do sharp turns on higher road_speeds). On 07.07.2013 13:06, Henning Scholland wrote:
Am 06.07.2013 12:43, schrieb Johannes Formann:
After a short investigation a possible reason are large differences in the road_type and road_speed.
Anyone observed a similar behaviour? I think Felix reported this problem some time ago, but this shouldn't have anything to do with the new problem. I've also problems if road_speed stays same.
@Geoff: While changing max-nodes splitter will create different tile-boundaries, so problematic location will move. Is this the thing which "solves" the problem for you?
Henning
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
Oh and I forgot to say, I know for certain it's the tile boundaries - because identical map with different split tiles, calculates the route just fine. Too bad we don't have differently split tiles on identical original garmin non NT maps, to see if there are problems too! On 09.07.2013 20:36, Felix Hartmann wrote:
yes - I noticed that big changes in road_type (meaning more than 1) so eg from 4 to 2 are less likely to be routed than 4 to 3. I tried that out by creating identical left/right options - then testing which one is choosen. 4 to 1 or 4 to 0 had actually quite big penalties. This only mattered on Basecamp 4.1 or higher, new generation GPS with up to date firmware. Mapsource or older Basecamp or older GPS firmware was not really affected strangely.
Road_speed I dunno - I would guess there are just the usual probs (doens't like to do sharp turns on higher road_speeds). On 07.07.2013 13:06, Henning Scholland wrote:
Am 06.07.2013 12:43, schrieb Johannes Formann:
After a short investigation a possible reason are large differences in the road_type and road_speed.
Anyone observed a similar behaviour? I think Felix reported this problem some time ago, but this shouldn't have anything to do with the new problem. I've also problems if road_speed stays same.
@Geoff: While changing max-nodes splitter will create different tile-boundaries, so problematic location will move. Is this the thing which "solves" the problem for you?
Henning
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
Hi, I think that last version of BaseCamp uses nearly exclusively class 4 roads for long routes in car mode. This is similar change like Garmni did for routing in nuvi models form 2012. Falager from Garmin has confirmed here: https://forums.garmin.com/showthread.php?43441-Bad-quality-of-routing-in-Bas... If class 4 network is not continuous, then routing will fail. I have made some maps for Poland, that should work in BaseCamp. The main changes to default style is that I added motorway_links, trunk_links and trunk roundabouts to class 4. For Poland I had to add selected primary and primary_links too, but this is specific the country without continuous network of highways. I haven't noticed any problems with tiling. My map is here, you can test it: http://www.gmaptool.eu/en/content/poland-osm-auto -- Best regards, popej
Am 11.07.2013 13:14, schrieb Andrzej Popowski:
If class 4 network is not continuous, then routing will fail. I have made some maps for Poland, that should work in BaseCamp. The main changes to default style is that I added motorway_links, trunk_links and trunk roundabouts to class 4.
Thanks for this info. Good to know. I was just about changing in my style motorway_link from class 4 to 3 because the device often routes me over the parallel link ways in motorway-junctions. Chris
participants (7)
-
Andrzej Popowski -
chris66 -
Felix Hartmann -
Geoff Sherlock -
Henning Scholland -
Johannes Formann -
Minko