breautek edited a comment on issue #219: URL: https://github.com/apache/cordova-plugin-geolocation/issues/219#issuecomment-748089940
There are several environmental reasons outside of the developer's control that may cause poor `accuracy` readings. Things that tend to cause poor accuracy readings includes being in an office building or any other large building with thick materials, being surrounded by mountains or just poor weather. The "perfect" environment for GPS is being in an open field with clear open skies. Most modern phones can get up to 3 to 5 meters in accuracy; that is, the phone is 95% confident that the actual GPS point is within a 3-5 meters radius of the given location. I've written a [blog post](https://breautek.com/2020/08/25/geolocation-accuracy/) that goes into more detail but to summarise, you can do the following things to help ensure you have good accuracy reading: 1. Enable `enableHighAccuracy` option (Which I see you've already done). 2. Most devices has Location Accuracy settings on the device itself, which includes enabling A-GPS features like using Wifi / Bluetooth. Enable these settings. Unfortunately this is something you can't programmatically control. You can however use the [diagnostics](https://github.com/dpa99c/cordova-diagnostic-plugin#getlocationmode) plugin to check the current values of these settings and give proper feedback to your users if this is critical for your app. 3. Consider trying to test your app outside if you're in an office building. I also receive poor accuracy in my office building, which is an old think concrete building. Therefore if I'm trying to test a "good accuracy" path, I physically need to take the phone outside. 4. Also consider dropping or reducing the `maximumAge` option. This is an acceptable cache option, which means you're accepting a GPS point up to 3 seconds old. 5. Lastly, this is mostly for android devices - remember that GPS receivers are not standardised by Google. Device manufacturers have the freedom to put whatever GPS receiver they wish if any at all. Cheap budget phones tend to have cheap hardware and a higher tendency to produce poor accuracy readings. I'm closing this as a "not a bug" issue. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
