W3C Geolocation API: Difference between revisions

Content deleted Content added
Location sources: fix typo from prev edit
"Geolocation API" is natively English. Features: Merge tiny section into lead. Citation needed. Location sources: Tag {{Unreferenced section}}. See also: Alphabetize per MOS:SEEALSO.
Line 3:
| title = Geolocation API
| long_name =
| native_name = Geolocation API
| native_name_lang = en
| image =
| caption =
Line 30 ⟶ 28:
 
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 name="geolocation-spec">{{cite web|url=https://www.w3.org/TR/geolocation-API/|title=Geolocation API Specification 2nd Edition|first=Andrei (editor, Google Inc.)|last=Popescu|website=W3C|publisher=Geolocation Working Group|date=2016-11-08|access-date=2021-04-21}}</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.
 
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.{{Citation needed|date=January 2022}}
 
== Deployment in web browsers ==
Line 37:
 
[[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.
 
==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==
{{Unreferenced section|date=January 2022}}
 
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.
 
Line 83 ⟶ 82:
 
==See also==
*[[Location-based service]]s
*[[Local search (Internet)]]
*[[Location-based service]]s
 
==References==
{{reflistReflist}}
 
==External links==
Line 96 ⟶ 95:
 
[[Category:Application programming interfaces]]
[[Category:Internet geolocation]]
[[Category:HTML5]]
[[Category:WebInternet standardsgeolocation]]
[[Category:Location-based software]]
[[Category:InternetWeb geolocationstandards]]