Replies: 2 comments
-
|
Check this documentation, the PRIORITY_HIGH_ACCURACY setting. Use this constant when requesting location from MAUI. The example shows GeolocationAccuracy.Medium, but you can choose Best. A thank you note to CoPilot quick check-in. |
Beta Was this translation helpful? Give feedback.
-
|
I'll answer my own question here in case someone in the future has the same issue. In areas where satellite view is compromised (in a city amongst tall buildings) or inaccurate (when out on water with the device close to the water), the fused method is stupidly inaccurate, and your coordinates will jump from wi-fi hotspot location to mobile mast location. Even if kilometres away. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I have a new app that records location on a regular basis (every 10 seconds). This is used for safety management.
I recently had it used at an ocean paddling event where paddlers were up to a few hundred metres offshore with their phones in a backpack . The iOS devices recorded location perfectly using GPS. The Android devices, however, recorded almost all their locations as onshore, I assume as they paddled past various wi-fi hotspots and cellphone masts (you can clearly see many locations recorded as being on top of cell masts!). This is all very evident when you view a 'trail' of their route on a map. Out of hundreds of location records, maybe 2 would show in the correct spot out at sea.
When the users reached shore and drove on roads the Android devices mostly recorded accurately, with the occasional snap to a nearby wi-fi.
How do I force Android devices to only use GPS, but still as accurately as possible? In my test case it appears GPS was being ignored and preference was being given to cell towers kilometres away, which is ridiculous.
Beta Was this translation helpful? Give feedback.
All reactions