Content deleted Content added
m Task 70: Update syntaxhighlight tags - remove use of deprecated <source> tags |
m date format audit, minor formatting |
||
Line 1:
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.<ref>{{cite web |url=https://www.w3.org/TR/geolocation-API/ |title=Geolocation API Specification: W3C Recommendation 24 October 2013 |first=Andrei (editor, Google Inc.) |last=Popescu |publisher=W3C |accessdate=4 February 2016}}</ref> 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 Server]]s, 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]]/[[CDMA2000|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]] [[plug-in (computing)|plugin]], but this was discontinued in 2010 and the server-side API it depended on stopped responding in 2012.<ref>{{cite web |url=https://code.google.com/apis/gears/api_geolocation.html |title=Geolocation API: Gears API: Google Code |date=9 July 2009}}</ref><ref>[https://code.google.com/p/gears/wiki/GeolocationAPI 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
The Geolocation API is ideally suited to web applications for mobile devices such as [[personal digital assistant]]s (PDA) and [[smartphone]]s. On desktop computers, the W3C Geolocation API works in [[Firefox]] since version 3.5, [[Google Chrome]],<ref>{{cite web |url=http://chrome.blogspot.com/2010/05/new-chrome-stable-release-welcome-mac.html |title=A new Chrome stable release: Welcome, Mac and Linux! |date=25 May 2010}}</ref> [[Opera (web browser)|Opera]] 10.6,<ref>{{cite web |url=http://my.opera.com/desktopteam/blog/2010/07/01/opera-10-60-goes-final |title=Opera 10.60 goes final |first=Huib |last=Kleinhout |date=1 July 2010 |work=[[My Opera]] |publisher=[[Opera Software]] |accessdate=2 July 2010}}</ref> [[Internet Explorer]] 9.0,<ref>{{cite web|title=W3C Geolocation API in IE9|url=http://blogs.msdn.com/b/ie/archive/2011/02/17/w3c-geolocation-api-in-ie9.aspx}}</ref> and Safari 5. On mobile devices, it works on [[Android (operating system)|Android]] (firmware 2.0+), [[iOS (Apple)|iOS]], [[Windows Phone]] and [[Maemo]]. The W3C Geolocation API is also supported by Opera Mobile 10.1
[[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 (operating system)|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.
Line 64 ⟶ 65:
* [http://www.w3.org/TR/geolocation-API/ W3C Geolocation API Specification]
* [https://whereaminow.co W3C Geolocation API Usage]
{{W3C standards}}
{{Web interfaces}}
▲{{Use dmy dates|date=March 2011}}
[[Category:Application programming interfaces]]
| |||