Hello list, The following inter tile routing gives nice and unexpected results. areas.list: 63240001: 0x241000,0x25000 to 0x24d000,0x3b000 63240002: 0x24d000,0x25000 to 0x251000,0x34000 63240003: 0x24d000,0x34000 to 0x251000,0x3b000 63240004: 0x241000,0x3b000 to 0x24b000,0x42000 63240005: 0x241000,0x42000 to 0x24b000,0x53000 63240006: 0x24b000,0x3b000 to 0x251000,0x41000 63240007: 0x24b000,0x41000 to 0x251000,0x53000 63240008: 0x251000,0x25000 to 0x255000,0x39000 63240009: 0x251000,0x39000 to 0x255000,0x40000 63240010: 0x255000,0x25000 to 0x263000,0x40000 63240011: 0x251000,0x40000 to 0x259000,0x49000 63240012: 0x251000,0x49000 to 0x259000,0x53000 63240013: 0x259000,0x40000 to 0x263000,0x48000 63240014: 0x259000,0x48000 to 0x263000,0x53000 (You don't need all areas, but I don't know a trivial way to know which map part is which split). Then run: java -Xmx1600m -enableassertions -jar ../splitter/dist/splitter.jar --split-file=areas.list netherlands.osm java -enableassertions -Xmx1800m -jar ~/garmintest/mkgmap/dist/mkgmap.jar --country-name=Nederland --country-abbr=NL --latin1 --remove-short-arcs --lower-case --preserve-element-order --location-autofill=1 --gmapsupp --route --net --tdbfile -c template.args Then load the attached tdb-file in MapSource.exe. You'll notice three waypoints, A, B and C, all three on a different tile, A and B being adjacent and B and C also. Mapsource will route from A to B, from B to C and from A to B via C, but it will not route from A to C. I don't have my Garmin Nüvi at hand, so I can't test it there - if you want me to, I'll be able to do that in the evening if you want me to. Best regards, Valentijn
Valentijn Sessink schreef:
The following inter tile routing gives nice and unexpected results. areas.list:
You only need:
63240003: 0x24d000,0x34000 to 0x251000,0x3b000 63240008: 0x251000,0x25000 to 0x255000,0x39000 63240009: 0x251000,0x39000 to 0x255000,0x40000
Just found out: the trivial way to know which map part is which split is using the "Map" button in the tool bar. It has an icon that vaguely resembles a Cubism sort of Pac Man (what if... Picasso would have been a game developer?) Also: trying to route back (just put points D, E and F on the opposite lane of the A2 highway) shows the same problems: routing from D to E and E to F is OK, but D to F fails. V.
Hi Valentijn, What's really fascinating about your example is that mapsource will happily route from A to a point within the tile containing B passing right past point C. For example, route from A to the end of Plutoniumweg (damn it, why can't we have funky road names like that instead of the canonical Acacia Avenue!), but if you move the destination a little to the S so that it is in the lower tile, it fails to route - see attached gdb. It's almost as if having traversed B tile it then is happy to locate a destination in it but, for some reason, it's unhappy with a destination in C tile. I can't think at this time what would cause this to happen. It may be a limitation of the Garmin routing engine and it needs something extra from us to cope? Cheers, Mark
Mark, For me, routing to the Plutoniumweg doesn't work at all - but my Mapsource is older than yours, I could not read your Plutoniumweg.gdb (MapSource complains about the file being newer). "Utrecht, we have a problem" ;) I was thinking about trying to synchronize the vertical split line (i.e. have both maps split at 0x39000, just to make sure that's not the problem. Oh, btw: the reason I found this strange route is that a much longer inter-tile route, from my home in Zaandam to my parents in Houten, made a weird deviation half way (went off the A2 for no reason, somewhere above point A); also, a route to my wife's family in Culemborg could not be calculated at all. Just to be sure, I'll check my Nüvi this evening. Best regards, Valentijn Mark Burton schreef:
What's really fascinating about your example is that mapsource will happily route from A to a point within the tile containing B passing right past point C. For example, route from A to the end of Plutoniumweg (damn it, why can't we have funky road names like that instead of the canonical Acacia Avenue!), but if you move the destination a little to the S so that it is in the lower tile, it fails to route - see attached gdb. It's almost as if having traversed B tile it then is happy to locate a destination in it but, for some reason, it's unhappy with a destination in C tile. -- http://www.openoffice.nl/ Open Office - Linux Office Solutions Valentijn Sessink v.sessink@openoffice.nl +31(0)20-4214059
Hi,
For me, routing to the Plutoniumweg doesn't work at all - but my Mapsource is older than yours, I could not read your Plutoniumweg.gdb (MapSource complains about the file being newer).
I am using the latest version (as downloaded by the "check for software updates" option on the help menu).
"Utrecht, we have a problem" ;)
I was thinking about trying to synchronize the vertical split line (i.e. have both maps split at 0x39000, just to make sure that's not the problem.
Could be worth trying to see if it changes anything.
Oh, btw: the reason I found this strange route is that a much longer inter-tile route, from my home in Zaandam to my parents in Houten, made a weird deviation half way (went off the A2 for no reason, somewhere above point A); also, a route to my wife's family in Culemborg could not be calculated at all.
Yes, it's not specific to that particular piece of road. It must be a general problem with being unable to route across a tile in certain circumstances.
Just to be sure, I'll check my Nüvi this evening.
Please do, it would be useful to know if a real GPS has the same problem (my guess is that it will). Cheers, Mark
Hi Mark, Mark Burton schreef:
I am using the latest version (as downloaded by the "check for software updates" option on the help menu).
I can't run a later version, I use the version for older operating systems, as that is what runs nicely under Linux under Wine. I could not get the Splendid New version to work. Oh well, it says that "De MapSource versie 6.15.6.0 update is voor downloaden beschikbaar". But I'd really rather not try it, actually. I'll put the map in my Nüvi instead.
I was thinking about trying to synchronize the vertical split line (i.e. have both maps split at 0x39000, just to make sure that's not the problem. Could be worth trying to see if it changes anything.
Makes no difference (please note that 0003 is out of bounds but that doesn't matter as it is not used). 63240003: 0x24d000,0x34000 to 0x251000,0x39000 63240006: 0x24d000,0x39000 to 0x251000,0x41000 63240008: 0x251000,0x25000 to 0x255000,0x39000 63240009: 0x251000,0x39000 to 0x255000,0x40000 Same routing for A, B and C. V.
Mark Burton wrote:
<snip> I am using the latest version (as downloaded by the "check for software updates" option on the help menu).
<snip> Hi Mark, I tried the latest mapsource update, and I liked the rendering of the maps, but it was caching my maps so when I made updates, they were not immediately reflected in mapsource. It would still display the old map until I changed map to something else and back again a few times. This proved to be a problem in checking my changes, so I downgraded to 6.13.7, which is still available from garmin. If you know how to make the maps refresh with the latest versions this would be useful to share. Thanks Garvan
Hi Garvan,
I tried the latest mapsource update, and I liked the rendering of the maps, but it was caching my maps so when I made updates, they were not immediately reflected in mapsource. It would still display the old map until I changed map to something else and back again a few times. This proved to be a problem in checking my changes, so I downgraded to 6.13.7, which is still available from garmin.
Yes, the caching is a real pain.
If you know how to make the maps refresh with the latest versions this would be useful to share.
I don't know how to do that, it would be good to know. Cheers, Mark
Hi Mark, I'm not sure if this is good or bad news, but the Nuvi works!
Just to be sure, I'll check my Nüvi this evening. Please do, it would be useful to know if a real GPS has the same problem (my guess is that it will).
It also works out of the box, routing perfectly, when I route from home to my parents (MapSource didn't do that correctly) and to my wife's family (where MapSource did not route at all). So this seems a MapSource issue with the map, not a generic mapping issue. I could check/doublecheck the MapSource settings (i.e. check if there's any caching, remove and reload the TDB file again etc etc). Will do that, but as my Nuvi works, it's not high on the list. And now for something completely different: I think the mailing list noticed some time ago that bike routing is a wholly different thing on the Garmin, right? I'm still getting weird results when I let the Nuvi route by bicycle - simple routes will have the weirdest deviations, letting you drive 35 kilometers where the regular Garmin map has a 14 kilometer route. Now this regular map has no knowledge of bicycle paths, so sometimes the routing is wrong because of that. Anyway, I'm pretty confident now that the routing by car is pretty much as expected. I will keep using my Garmin for reference testing, however, and tell my experiences here on the mailing list. Back to the original topic: if you want me to do anything on the weird route, please tell me so. Thanks for your great work again! Best regards, Valentijn
participants (3)
-
Garvan & maew -
Mark Burton -
Valentijn Sessink