CODEWITHSUNDEEP
javascript
Tahmina Khanam Urmi
Tahmina Khanam Urmi

Reputation: 21

Accessing location using Javascript

I run the code shown below from different places but this results in same latitude and longitude value at different places. 

 <html>
        <head>
            <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
            <title></title>
        </head>
        <body onload="getLocation()">
        <p id="demo"> </p>
    <script>
    var x= document.getElementById("demo");
    function getLocation() {
        if (navigator.geolocation) {
            navigator.geolocation.getCurrentPosition(showPosition);
        } else { 
           x.innerHTML = "Geolocation is not supported by this browser.";
        }
    }
    function showPosition(position) {
    x.innerHTML= position.coords.latitude;
    x.innerHTML= position.coords.longitude;
    var lat=position.coords.latitude;
    var lon=position.coords.longitude;
    }
    </script>
    **strong text**</body>
    </html>

Any help would be appreciated.

Upvotes: 0

Views: 74

Answers (1)

Travis Clark
Travis Clark

Reputation: 61

In short, the problem isn't with your code, but most likely with your device. I can tell you're using the demo code from the W3Schools article on the geolocation API. That code seems to work fine for me, at least as much as I would expect.

Geolocation isn't terribly precise in all cases. According to MDN, the method use to determine location will be the most accurate available for your device at that time. If you're testing on a desktop browser, the results might be no more accurate than to the nearest city, and in some cases even more inaccurate than that (My home in Michigan registers as the middle of New York state, for some weird reason). If you test on a 3g or 4g phone, you might get better results, down to the nearest broadcast area. If you test on a phone with GPS, you might get highly accurate data, where you'll notice a difference if you move even a few feet or so. I say 'might' for these cases, because location data is a huge privacy concern area, and there's a lot of things that might interfere with geolocation to protect a user's privacy.

If you're seeing the same result from relativly small moves, this would easily be the cause. If you've travelled a few hundred miles to run your code elsewhere, then I would have to admit that there's something

Upvotes: 1

Related Questions