Correct display of LocationName so where is the problem if not in the GCM app?

Hello, I contacted the GCM developer support about whether they are changing the strategy and the weather provider, specifically the location function (LocationName) and here is their response:

Hello, 
Our suggestion is to reference our support page in the link below in regards to sending forecast data to our wearable devices where it is then displayed on the watch in the default weather widget and default watch face weather data fields: 
Below is another link showing where the weather info displayed on activities within connect for activities recorded from our devices is displayed when synced one of our wearables devices:
If using a 3rd party developed watch face, widget, data field , or app from the iQ store...the source of weather info will vary depending on the content that was downloaded, and you must contact the developer of the content for more info on the source of the weather specific to their content. 
We off within the Garmin Connect mobile an option to use weather based on your current location or a fixed location. Weather info is then provided from location permissions offered from the smartphone the Connect app is being used on. 
At this time we do not have any public announcements on any plans of changing weather related features that are available through our Garmin Connect application. 
Let us know if further assistance is needed.

So I don't know if it's a FW issue or the error is somewhere else?

Does anyone have a way to fix the positioning error via garmin weather provider?

  • if you're talking about the change to observationLocationName in currentConditions, to me, it's s bug fix and not a bug.

    In the past it was the location of your phone, and not the location the data was actually observed.  Now, I see where the weather station is located (it's an airport a few miles away) and not the suburb I've having lunch in!

    This is the same thing you see with things like OpenWeatherMaps or WeatherUnderground.  They return the location (weather station) where the conditions are observed.  With OWM, Sometimes it's from a ranch a few miles west, and other times a town a few miles north east.  With WU, you also get the name of the weather station itself, and not just the location 

  • So if you see it as a fix and not a bug, then it's very interesting.

    However, regarding the fact that in the end "LocationName" is not meant to be a weather station, from where you get weather information to the device, but it is still not accurate.

    I want this function to work as before, that is, the "LocationName" was the city where you are mostly, of course I do not count the deviations of the places where you move.

    It just doesn't work correctly...

    Observation location name isn't showing the correct city.

  • Are you sure it's not the location of the weather station?  That's how Garmin Weather looks to me, and is the way it's done with other weather providers like OWM and WU.  observationLocationName to me means where the weather data as "observed" and not where your phone is.

  • You're trying to abuse the system. You're RECEIVING an object about the weather [at the weather station. I hope you see and understand why it can not be wherever you are...] so it's the only logical thing to get the location where the weather was measured inside that object.

    If you however want to display the location name of the watch's position then you should use a different api for that. I guess google has such apis, but many other providers also, that translate between coordinate to locality name.

  • I'm not trying to abuse the system - API (Weather.getCurrentConditions().observationLocationName)
    for location tracking city name.

    If it was fixed and the location after the new se
    shows as the name of the weather station that sends weather information to the device, so it should be mentioned somewhere that this is a fix.

    Now it is clear to me that if I want to display the location name of the city where I am, I have to use a different method, a different API..

  • you do try to "abuse": observationLocationName is in plain English telling you that it has the name of the location where the weather location was performed. Which is the weather station, not where your watch or phone is.

  • I think I'm not the only one who misunderstood this function.

    https://forums.garmin.com/apps-software/mobile-apps-web/f/garmin-connect-mobile-andriod/320001/observation-location-name-isn-t-showing-the-correct-city/1551240

    So, can someone advise me how to correctly write a function that will locate the city - the location where my phone is, i.e. where I am?

    Thank

  • So am I to understand that for this feature I already have to use an interface eg OWM where an API KEY is required?

    Can't it be solved in some other way via the Garmin API?

  • Yes: instead of displaying "Foo city" you could display the GPS coordinates. Less user friendly, but works even without internet ;)