Routes not transferring properly between Google and BaseCamp
Former Member
I've used Google 'My Maps' to produce a route which I've exported into BaseCamp, then exported to my Garmin. I noticed some odd U-turns coming up in the directions and realised why - some of the points on Google aren't replicated properly in BaseCamp. See below for example - top image is Google and bottom image is Basecamp:
Why are points in Google not showing up properly in Basecamp?
Looking at your screenshots you appear to have sent a track rather than a route to Basecamp? If so a track is a track, Basecamp can only 'join the dots' sent by Google maps. If you then convert that to a route (which I guess you're then doing?) you may get some unexpected results, including u turns.
Now much of that is guesswork, perhaps you could give more of an idea about what you're doing and perhaps attach the relevant .gpx files?
I exported the routes from 'My Maps' on Google as a KMZ, then imported it into Basecamp and it appears as a track which I then convert to a route and send to the Garmin.
As can be seen above, the 'turns' on the Google map are translated into dots on the Basecamp track/route but they're not on the road - they're above the road. See image below for what I mean - I have coloured the corresponding points between the two maps.
PS. Could this thread please be moved to the Windows section for Basecamp? Thanks.
That's because the Google map and Basecamp map don't quite agree. Afraid that's the problem of trying to do what you're trying ...
Oh dear. :( I feared that could be the case. What's the best way around the problem? Reducing the number of viapoints when creating the route from the track seems to mostly remove the problem but surely there's a better way.
The reason I'm attempting this is because often I want to go on a particular route, and not the one Garmin wants to send me on if I just whack in a destination.
You'll just need to adjust the route once you've created it from the track or just navigate using the track ... you don't say which device you have, on some you can't follow a track.
I see and understand the issue but I truly don't see any "problem". The Basecamp route in the screenshot will only cause trouble for someone who is silly enough to think they have to follow the track off into the ditch rather than stay on the road. :)
If the Basecamp route was taking you onto other roads and far out of
your way, then I would say you have a problem.
Sorry, I didn't see any loops or u-turns in the posted screenshots. I guess you sort of have to imagine what the routing software will try to do with the associated directions when the original track is off the road.
So my next question is, Why make the initial route on Google Maps and then have to hammer it into shape in Basecamp? Why not just create the route in Basecamp in the first place?
[...]So my next question is, Why make the initial route on Google Maps and then have to hammer it into shape in Basecamp? Why not just create the route in Basecamp in the first place?[...]
Hi,
I also plan my routes in Google Maps first place. Google Maps has a lot more helpful options (like Satellite view, Street view, Terrain view, etc.) while at the same time the workflow to create and change a route is easier and more straight forward.
After having finished the Route in Google Maps, I don't import it into Basecamp but draw the route "by hand" in Basecamp.
