W3C Geolocation API

The W3C Geolocation API is an effort by the World Wide Web Consortium (W3C) to standardize an interface to retrieve the geographical location information for a client-side device.[1] It defines a set of objects, ECMAScript standard compliant, that executing in the client application give the client's device location through the consulting of Location Information Servers, which are transparent for the application programming interface (API). The most common sources of location information are IP address, Wi-Fi and Bluetooth MAC address, radio-frequency identification (RFID), Wi-Fi connection location, or device Global Positioning System (GPS) and GSM/CDMA cell IDs. The location is returned with a given accuracy depending on the best location information source available.

Deployment in web browsers

Web pages can use the Geolocation API directly if the web browser implements it. Historically, some browsers could gain support via the Google Gears plugin, but this was discontinued in 2010 and the server-side API it depended on stopped responding in 2012.[2][3]

The Geolocation API is ideally suited to web applications for mobile devices such as personal digital assistants (PDA) and smartphones. On desktop computers, the W3C Geolocation API works in Firefox since version 3.5, Google Chrome,[4] Opera 10.6,[5] Internet Explorer 9.0,[6] and Safari 5. On mobile devices, it works on Android (firmware 2.0+), iOS, Windows Phone and Maemo. The W3C Geolocation API is also supported by Opera Mobile 10.1 – available for Android and Symbian devices (S60 generations 3 & 5) since 24 November 2010.[7]

Google Gears provided geolocation support for older and non-compliant browsers, including Internet Explorer 7.0+ as a Gears plugin, and Google Chrome which implemented Gears natively. It also supported geolocation on mobile devices as a plugin for the Android browser (pre version 2.0) and Opera Mobile for Windows Mobile. However, the Google Gears Geolocation API is incompatible with the W3C Geolocation API and is no longer supported.

Features

The result of W3C Geolocation API will usually give 4 location properties, including latitude and longitude (coordinates), altitude (height), and [accuracy of the position gathered], which all depend on the location sources. In some queries, altitude may yield or return no value.

Location sources

The Geolocation API does not provide the location information. The location information is obtained by a device (such as a smartphone, PC or modem), which is then served by the API to be brought in browser. Usually geolocation will try to determine a device's position using one of these several methods.

GPS (Global Positioning System)
This happens for any device which has GPS capabilities. A smartphone with GPS capabilities and set to high accuracy mode will be likely to obtain the location data from this. GPS calculate location information from the satellite signal. It has the highest accuracy; in most Android smartphones, the accuracy can be up to 10 metres.
Mobile Network Location
Mobile phone tracking is used if a cellphone or wireless modem is used without a GPS chip built in.
WiFi Positioning System
If WiFi is used indoors, a Wi-Fi positioning system is the likeliest source. Some WiFi spots have location services capabilities.
IP Address Location
Location is detected based on nearest Public IP Address on a device (which can be a computer, the router it is connected to, or the ISP the router uses). The location depends on the IP information available, but in many cases where the IP is hidden behind Internet Service Provider NAT, the accuracy is only to the level of a city, region or even country.

Implementation

Though the implementation is not specified, W3C Geolocation API is built on extant technologies, and is heavily influenced by Google Gears Geolocation API. Example: Firefox's Geolocation implementation[8] uses Google's network location provider.[9]

Google Gears Geolocation works by sending a set of parameters that could give a hint as to where the user's physical location is to a network location provider server, which is by default the one provided by Google (code.l.google.com).[10] Some of the parameters are lists of sensed mobile cell towers and Wi-Fi networks, all with sensed signal strengths. These parameters are encapsulated into a JavaScript Object Notation (JSON) message and sent to the network location provider via HTTP POST. Based on these parameters, the network location provider can calculate the location. Common uses for this location information include enforcing access controls, localizing and customizing content, analyzing traffic, contextual advertising and preventing identity theft.[11]

Example code

Simple JavaScript code that checks if the browser has the Geolocation API implemented and then uses it to get the current position of the device. this code creates a function which can be called on HTML using <body onload="geoFindMe()">:

const geoFindMe = () => {
    if (navigator.geolocation) {
        navigator.geolocation.getCurrentPosition(success, error, geoOptions);
    } else {
        console.log("Geolocation services are not supported by your web browser.");
    }
}

const success = (position) => {
    const latitude = position.coords.latitude;
    const longitude = position.coords.longitude;
    const altitude = position.coords.altitude;
    const accuracy = position.coords.accuracy;
    console.log(`lat: ${latitude} long: ${longitude}`);
}

const error = (error) => {
    console.log(`Unable to retrieve your location due to ${error.code}: ${error.message}`);
}

const geoOptions = {
    enableHighAccuracy: true,
    maximumAge: 30000,
    timeout: 27000
};
gollark: Oh no. It begins.
gollark: ++remind 9d23h maybe just something where a `++` command in a reminder is executed as the right user? Somehow? Would need to build the context or whatever, probably.
gollark: ++remind 10d implement task scheduling mechanism, orbital laser strikes
gollark: ++remind 11d19h <@160279332454006795> POTATO GOOD
gollark: ++remind 11d21h <@160279332454006795> <@&435756585625714698> potato not²not²not²not² bad

See also

References
  1. Popescu, Andrei (editor, Google Inc.). "Geolocation API Specification: W3C Recommendation 24 October 2013". W3C. Retrieved 4 February 2016.
  2. "Geolocation API: Gears API: Google Code". 9 July 2009.
  3. GeolocationAPI - gears - Provides the geolocation of a device running a Gears-enabled web browser. - Improving Your Web Browser - Google Project Hosting. Code.google.com. Retrieved 2014-06-01.
  4. "A new Chrome stable release: Welcome, Mac and Linux!". 25 May 2010.
  5. Kleinhout, Huib (1 July 2010). "Opera 10.60 goes final". My Opera. Opera Software. Retrieved 2 July 2010.
  6. "W3C Geolocation API in IE9".
  7. Opera.com (25 November 2010). "Opera Mobile 10.1 for Nokia smartphones goes final".
  8. "Location-Aware Browsing". Mozilla Firefox. Mozilla.
  9. "Geolocation API Network Protocol: Gears API". Google Code. Retrieved 8 August 2011.
  10. "WebScanNotes.com: W3C Geolocation API". WebScanNotes.com.
  11. King, Kevin F. (8 June 2010). "Personal Jurisdiction, Internet Commerce, and Privacy: The Pervasive Legal Consequences of Modern Geolocation Technologies". SSRN 1622411. Missing or empty |url= (help)
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.