Creating POIs on Movescount web page
-
@Prenj , I must say I didn’t even think of a possibility that someone might care about correct altitude there. What’s the difference when using just 0 or any other random value for POI altitude? Can you even see POI alt. from the watch?
And I really don’t think it use to be consistent, I went though all my past POIs and only 2 had altitude set to something else but 0m, all the rest looked like this:
.
Now MC just fails to fill it with a default “0” . Well, there is a slight chance that I’ve imported most of my existing POIs though some other means. I tend to clean this list from time to time, so I can’t see every single one I’ve had in MC.Had I ever missed that alt. value, I guess would have just added it manually from labeled contour lines from that same Mapbox terrain map, 1000m for the one above.
-
I think you have to specify altitude because if you use POI for navigating the watch has different functions i navigation modus as ETA, ETE and also how many meters up/down it is to you destination.
-
I think it is a bug connected with missing altitude in movescount. Maybe I am wrong
-
@zvonejan I have always punched the altitude manually and it works fine
-
@margusl said in Creating POIs on Movescount web page:
I just checked and the POI altitude is not visible in A3P and the watch ignores it when calculating distance to it. But, I checked all my POI-s and I only found one without altitude. Not sure why that one had 0.
Strange. I was under impression the altitude would be used to calculate with 3d distance, but that seems to work just in sport modes? Not sure why Movescount had this field in the first place and why was it obligatory to enter altitude if it’s not used at all then?! Maybe they planed to add the 3d distance for POI-s at some point? That would make sense for mountains… Or they just had this field so you could add POI from watch itself. That info would be meaningful to some people.Anyway, it should be an easy fix, but I’m getting increasingly annoyed by how slow Suunto is dealing with the problems with their software.
-
@Prenj , I believe it’s there mostly for POIs that are pulled from the watch - if I went through trouble of saving my location (at least 8 button presses without using a shortcut, just checked), I’d prefer to save it with current altitude.
-
@margusl said in Creating POIs on Movescount web page:
@Prenj , I believe it’s there mostly for POIs that are pulled from the watch - if I went through trouble of saving my location (at least 8 button presses without using a shortcut, just checked), I’d prefer to save it with current altitude.
Probably. The problem is that it doesn’t work (at least ATM). I added current location as POI in the watch and synced it with movescount. POI in movescount had altitude of 0. It would be logical that watch stores this info and syncs it back to movescount web, but it doesn’t, which brings us back to the first question - why is this field there in the first place and why is it obligatory?
-
@margusl I tried that with the Google map option and it did work. Now the Mapbox option is missing.
-
I have the same Problem. New POI’s can not be created on movescount. Why can one not create POI’s within the app?
-
Try adding an altitude to the POI on Movescount web page.
