From some time, Garmin Connect is naming all trainings on the basis of localization. Problem is that, names are incorrect - instead of Warsaw I get Halinów (place 21 km from correct location). Is anyone is working on this ? Is there solution, to fix it ?
Yes, but I am running very often - so this is not solution for me. From my perspective if Garmin Connect Team want to add such enhancement, they should fix it and in period when it is not working correctly, should turn it off for the users - or give them possibility to turn it off - because I prefer to have a training without the name (as it was before), than incorrectly named training (as it causes a lot of confusion and unnecessary comments).
...so how can I update maps for garmin 310, to get positive results? I thought that Garmin Express is doing that, but I do not have any new updates on it. My actual version is 4.50
From some time, Garmin Connect is naming all trainings on the basis of localization. Problem is that, names are incorrect - instead of Warsaw I get Halinów (place 21 km from correct location). Is anyone is working on this ? Is there solution, to fix it ?
In my case I get auto naming from place ~300km away from actual. From support all I got is: -=- Unfortunately, it cannot be disabled. However, you can manually change the names as you would have done when the activities were named Untitled. Please accept our apologies for the inconvenience. -=- And no words about possible fixing of this issue. Of course I can change the names manually but still I don't accept it as a solution because it is clearly a bug that must be fixed. As I already wrote previously - suggestion to change names manually is similar to if android would now update all its OS to default setting 'change background to brigth yellow every midnight' and say - those of you who don't like it - you can change it back to what ever you want. Every day. :cool:
Folks complained about activities being named 'untitled'. Where it's now correct no one need take any further action. For the few where it's not there is really no difference, assuming you weren't happy with it being named 'untitled' and had to edit it, you still need to edit it, so I'm not sure why anyone should have an issue :confused:
It's improved for many, and not changed for others.
It's improved for many, and not changed for others.
Won't agree with second part of this statement - just from perception perspective - 'untitled' is also commonly used default name in many cases. Having it also in connect.garmin.com for workouts didn't make any big difference - untitled is untitled. But now instead of untitled I get 'Sklėriškių k. Running'. It's even more confusing because the title is from neighbouring country (!!) containing specific characters that I don't have in my native language. And that is something that attracts attention very much, every time when I'm connect.garmin.com.
I clearly get that for many this is working fine and they're happy about new feature. But what I don't get is that there are no words about admitting that there is a bug (at least for some of users) and that it will be fixed at some point. Instead all I get is - you can rename if you don't like it.
Having read through a few threads now it seems that this enhancement made by Garmin has only been completed for specific areas (eg not Ireland, not parts of Poland, etc...).
Can anyone at Garmin give any schedule as to when the rest of us will be able to benefit from this enhancement? We are meant to tracking our position via GPS after all... being out by 150 miles doesn't really instil confidence!
Agreed - just need more folks to complain - its a poorly thought through enhancement with insufficient testing. To say people are no worse off @SSUSAMB is not correct. At the very least activity naming should be switchable particularly if it does not work for many people. It does not work properly for me in an area about 30 Miles outside London in the UK which has to be one of the most accurately surveyed and mapped areas on the planet. Granted it's just an irritation but it just shows that the Garmin testing is poor and ideas are rushed through into the software without sufficient thought.
