You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been glancing at the googlelocation reference, but I have been unable to find any Google documentation on the Browser Location API. I'm wondering if that has potentially been deprecated, and, if so, maybe the documentation here should be updated?
Utilizing the API endpoint as defined in "googlelocation.agent.nut" does return location data, but I wonder if the reference should be updated to the Geolocation API.
It should be noted that the response body from the Geolocation API looks similar to that of the Browser Location API (contains a 'location' object with 'lat' and 'lng' as well as 'accuracy' data). Maybe it's simply been renamed...
The text was updated successfully, but these errors were encountered:
Thanks for catching this. Not sure when they fully deprecated the Browser Location API, but it must have been in the last couple of months. I've added a task to our backlog to take a look at implementing a proper library for the Google Geolocation API.
I've been glancing at the googlelocation reference, but I have been unable to find any Google documentation on the Browser Location API. I'm wondering if that has potentially been deprecated, and, if so, maybe the documentation here should be updated?
Utilizing the API endpoint as defined in "googlelocation.agent.nut" does return location data, but I wonder if the reference should be updated to the Geolocation API.
It should be noted that the response body from the Geolocation API looks similar to that of the Browser Location API (contains a 'location' object with 'lat' and 'lng' as well as 'accuracy' data). Maybe it's simply been renamed...
The text was updated successfully, but these errors were encountered: