@david26 said in Suunto 5 new user experience:
@david26 said in Suunto 5 new user experience:
Lukasz
Well, it did show something. The Runalyze import shows what appear to be correct ascent/descent values. The problem is therefore not with the watch itself but with the processing of the information to create the .fit file, which matches the sneaking suspicion I had. A Suunto background processing (it appears that the numbers are crunched outside the application itself) glitch.
Thanks again, Lukasz.
You are incorrect here. A GPS-based altimeter will not be all that accurate and Runalyze corrects elevation data (you can pick the elevation model you want) so you are observing corrected data as you do in Strava. It would be a lot less confrontational if you asked questions instead of always assuming the product and its implementation are substandard. The watch you have does not have a barometer and the altitude values it provides will be estimates at best. The watch will work better on longer, sustained climbs and poorly on small differences, especially rolling hills.