@comfortably_numb said in Fix the elevation issue in Movescount:
I see the route in your screenshot is also missing the total ‘Ascent’ and ‘Descent’ data.
Of course - no one here is arguing that Movesount route view is not broken.
But for imported and older (pre-2020Q1) routes that’s just a piece of presentation and has been like that since Mapbox retired its Surface service about a year ago. Why have they decided not to calculate Movescount route asc / desc totals from data already included in the the route, I don’t know. Luckly it has no effect on how routes with already exiting elevation data are synced to the watch.
As your No.2 route / SAT15 clearly lacks elevation data, it must be come from somewhere else than Plotaroute.
You could also just export your routes from Movescount as GPX and check if elevation is set for routepoints (route created with Plotaroute, imported to Movescount):
<?xml version="1.0" encoding="utf-8"?>
<gpx version="1.1" creator="Movescount - http://www.movescount.com" ...>
<rte>
<name>ExpEst2020</name>
<rtept lat="57.8374105" lon="27.5755725">
<ele>69</ele>
</rtept>
<rtept lat="57.8373528" lon="27.5802755">
<ele>64</ele>
</rtept>
<rtept lat="57.8375673" lon="27.589674">
<ele>52</ele>
</rtept>
If <ele>elements are there, you’ll have your elevation plot on the watch as well.
In contrast, this is how routes created with Movescount itself (i.e. without elevation data) will look like:
<?xml version="1.0" encoding="utf-8"?>
<gpx version="1.1" creator="Movescount - http://www.movescount.com" ...>
<rte>
<name>Umbusi-Pikknurme</name>
<rtept lat="58.551599" lon="26.034306">
<ele>0</ele>
</rtept>
<rtept lat="58.569967" lon="26.019074" />
<rtept lat="58.570068" lon="26.019128" />
<rtept lat="58.570247" lon="26.019728" />
Don’t know about OS Maps, but I’d expect Strava to apply its own elevation model once a GPX route is uploaded, like it does with activities when imported from GPX files lacking elevation data.