You are reading a single comment by @hippy and its replies.
Click here to read the full conversation.
-
Why use the Connect step? Can you not just drag the gpx to the NewFiles folder on it (or GPX if it's an etrex rather than an Edge unit)?
hippy-
I couldn’t say really. Was on my list of things to try and have done it now and on a quick check all the info reads as it does on Ride With GPS so hopefully that’s sorted it, thanks. Wasn’t bothered about the differing numbers across the different services as always assumed they pull their data from multiple data sources but was just more to show how massively out of place the route preview was compared to all of the others. This route sort of crosses over as the way in and out of London is pretty much the same so hopefully won’t have any issues there.
ric_a5
I've started to run into an issue with routes on my Edge Explore that I can't really work out. My usual steps are to plan a route on Ride With GPS, export the GPX and import that into Garmin Connect, then I'll use the app to get the route onto the unit.
I've never had an issue with this method but recently some routes have had odd numbers attached and the route has gone strange at some point on the ride.
First happened last month with a 200km route where at around the 160km mark that crossed over a road from earlier in the route it started to route me back up that road and along the route from that earlier point again. I stopped getting turn notifications because the garmin route thought I was on a different section, though the map and GPS were correct and still tracking properly, so luckily I was able to just follow to the line on the map for the rest of the route and I had it in my mind where it was going anyway so was ok to get on with it. I've looked at the route since and the elevation figures are way off on the unit route preview, with Garmin Connect saying it should be 1286m but the unit saying it will be 2804m which is obviously way off.
I did an ~80km route last weekend which didn't seem to have any issue and looking at the route preview the ascent matches up with what Garmin Connect says as well.
Then today I've uploaded another 200km route for tomorrow and the predicted ascent/descent is way off which makes me think the route issue might happen again. Ride With GPS says the route has 1,173m of elevation, Komoot says 930 and Garmin Connect Says 708m. The route preview on the Unit says 3643m though but also says its 204km which is correct distance wise.
Any ideas of a way to correct this. I don't actually care about the ascent/descent information, would just like to make sure the route is going to go off it again and make the last quarter of the ride stressful.