@John-S-Parry said:
@Marinus-van-Deudekom said:
This whole topic is about getting routes into Garmin devices. Garmin uses Here as road map. Its a known and multiple proved fact that routes created with OSM or TomTom cause problems on those Garmin devices.
Im certainly not stating that the Here map is perfect. Far from that BUT it's the map Garmin uses.
If you want to use OSM be my guest.
By the way my Garmin devices are all sold
Im a MRA RouteXpert so yes I'm promoting MRA. Is it perfect no but pretty damn near close and as far as I'm concerned the number 1 app to navigate with.
If "it's a known and multiple proved fact that routes created with OSM or TomTom cause problems on those Garmin devices", where is the documentation? Proven facts are usually outlined somewhere for public consumption. This is the second time you've made this assertion, but again provide no context to what "causes problems" means. We all want to learn, but simply throwing out assertions that fly in the face of what others have actually experienced is not helpful.
But I'll take a stab at what you're trying to communicate. If in Routeplanner you create a route using OSM or TomTom, and in that route you minimize the use of shaping points and instead allow OSM/TomTom to make route calculation decisions for you, problems may in fact occur on a Garmin. You're then allowing Garmin, which has different route calculation algorithms, to possibly choose different paths between Via Points. I'd argue that the problem is more with the route creator than with OSM/TomTom. If you're actually talking about something else, please bring some substance that would be helpful.
Interesting discussion so far. With regard to the point above I'd have to concur with @marinus-van-deudekom. If you use the OSM or Tom tom mapping on a Garmin Device using Here mapping you may get unexpected results. This is because the road lines are projected in slightly different ways depending on the map set.
[image: 1786089978996-85d578b5-6092-4eb8-8f65-83cf4ca3d8c4-image.jpeg].
This is not a good example, but you can see that the map road lines don't quite line up. This is a google maps underlay with Here (black), TomTom red, and OSM blue road lines. The divergence is not bad in this example but I have encountered bits of road where the divergence is 10-15M. This can cause a problem particularly if a waypoint is inadvertently placed on the opposite carriageway because of map differences, or occasionally the route might direct you down a track you don't want to be on as OSM and Here categorise what constitutes a "Road" slightly differently :D. or you might have the occasional turn up a sideroad that is unintended. These issues are not serious but could be irritating. Long story short you will get better results if you use the map set that matches the maps on your device.
When I used my Garmin devices for navigation I often used OSM maps to keep old discontinued units for which Garmin no longer produce mapping up to date, and to make maps for places like Canada and the US, for which I had no mapping.
A write up I did explaining this can be found here.
https://www.ukgser.com/community/threads/using-open-street-maps-on-old-and-new-garmin-devices.439311/
Finally I notices a post on FrankB's excellent trip planner tool. This is indeed good but its use is dependant on having access to a computer to turn the routes on a Zumo XT to saved routes. There is another way to do this on the device itself. I take no credit for this Oop North John on the Zumo website discovered this. Basically if you have an imported route and you want to make it into a saved route to avoid potential RUT issues do this.
Send the calculated route to the XT
Open it up in the Trip Planner
Select Go!
Select the next via / way point, then Start
Then go back into Trip Planner
Select Saved trips
Select My Active Route and Save it. Unfortunately the original name is lost, but c'est la vie
Then select the trip you just saved in the Saved Trips area
Again interesting thread which hopefully we will all learn from. That said if MyRoute app POI track handling was more functional I'd have no use for my Garmin devices at all.
716410.9k
08115
0331.2k
0463
0210
023489
33114
05271
