What is browser geolocation and how does it relate to geocoding?
Browser geolocation is a technology supported by almost all web browsers which enables users to share their location - in the form of geographic coordinates (longitude and latitude) - with a web service.
Geocoding, on the other hand is the process of turning coordinates into geographic information (address, placenames, etc) or vice versa.
The accuracy of the coordinates obtained from browser geolocation will depend on the underlying technology being used to determine the user’s location, which could be GPS, WiFi network, phone cell tower mapping, or IP address. If the user is on a mobile device with a GPS signal, the coordinates can be highly accurate. If however the user is using an ISP and the location is coming from an IP to location lookup the location may not be accurate at all. The browser location may also be misleading if the user is accessing a web service via a VPN or similar technologies.
Once you have used browser geolocation to obtain the user’s location in the form of coordinates, these coordinates can be reverse geocoded using the OpenCage geocoding API to be turned into geographic information like an address or a country, state/provice, time zone, etc.
Please see the code example below or the OpenCage API reference for details of how to do the geocoding.
Because a user’s location is private information, browser geolocation is only possible if the user explicitly grants permission to a web service via a browser prompt. You can see an example of how this can look on these screenshot taken from the OpenCage demo page.
First, the user is shown a button to start the browser geolocation process:
Then the browser (Firefox in this screenshot) prompts to ask the user if location info should be shared. Only if the user allows it does the browser get access to the user's location information.
It is not possible to perform browser geolocation without the user's active consent.
Technical details / Code Example