Movescount routing bug(s)

Prenj · 22 Apr 2020, 10:06

Those of you that are actively using Movescount to draw routes have probably noticed that Movescount lately had a problem with drawing routes (we were unable to add starting point). This has been fixed in the meantime, but it seems the whole new bug (or reduced functionality) has been introduced - no altitude profile for the routes (both ascent and descent values are zero).

It has been suggested by several forum users that there was similar problem in Suunto app (at least the starting point issue) and that has been fixed.

So is the altitude profile of routes gone forever, or is it just a bug? Has this been acknowledged by Suunto? Will it be fixed?

zvonejan · 22 Apr 2020, 10:18

Yes, I would also like to know is this is the way it is gonna be now. Route planning with heatmaps is no longer useful and that means,
that I have to make a drastic move at least half a year earlier that I planned

Brad_Olwin · 22 Apr 2020, 12:50

@Prenj @zvonejan I think there are some issues going on, my understanding is that MC will continue to be used for route planning. I do not think that this is a planned problem. Don’t forget that companies are challenged at this time because of COVID19.

zvonejan · 22 Apr 2020, 17:08

@Brad_Olwin

This is a very good news. Route planing on movescount is essential for me. Hope it comes back with all functionality.

Brad_Olwin · 22 Apr 2020, 17:15

I saw on another thread an answer on this. Suunto is aware and there were some map box changes that need to be dealt with. I don’t know when all will be back to normal but hopefully not too long.

Alessandro Provera · 19 May 2020, 13:25

is there any update on the elevation profile for route planning?

zvonejan · 19 May 2020, 14:22

@Alessandro-Provera

No, they do not care at all. I think they blame MapBox

Prenj · 19 May 2020, 14:57

At this point I’m not so sure this will ever be fixed. Suunto didn’t even bother to acknowledge the problem or to inform users of it . They just let us troubleshoot the whole thing on our own.

Just as they are pushing ads for their current watch models all the times, simple “We are having problems with our mapping services so the altitude data is unavailable in your routes. Our IT is working hard to fix the problem. Thank you for your patience.” would be nice, but it’s too much to ask for Suunto. Absolutely horrible communication with customers!

petmic · 20 May 2020, 04:19

@Prenj Yeah, fully agree with what you said. On the other hand, Suunto send me an email with a link to a questionnaire whether I would recommend Ambit3 to family or friends. They must be have been joking. I wonder, if someone really reads the answers from such questionnaires. Would make an interesting read to someone.

Prenj · 29 May 2020, 06:54

Still not even acknowledgment of this bug from Suunto. Total silence. Why would any company do such negative PR for itself. I just can’t comprehend this. Unbelievable.

petmic · 30 May 2020, 06:23

@Prenj I think they once said they are listening to the customers. It seems not to those on this forum

Prenj · 5 Jun 2020, 17:22

This is getting really ridiculous. 1,5 months and still not even public acknowledgement let alone fixing it. This is not some minor problem. It’s major issue! How the hell is this acceptable for any serious manufacturer??? Total disgrace! Is suunto in some kind of existential crisis? Going bankrupt or what? What is going on?

A Former User · 23 Oct 2020, 23:05

I know that this bug is not solved, but on my side I just use Komoot or ridewith gps to do the routes, send it to movescount, and then watch and on the watch the ascent/descent profile matches the one of komoot.
I know it is another site to register, another file to pass, adding entropy and possibility of failiure, but it is a “solution”, at least for my usage.
Hope to have helped