I am using the Geolocation functionality of Xamarin Essentials in my app as a foreground service running all the time and I have noticed on several devices that I sometimes (although rarely) get locations which are really far away from where they should actually be, looking like this:
Location history with incorrect location
For the location I set a timeout of 60 seconds and the best accuracy possible. The incorrect location on the screenshot has an Accuracy value of '8' but is much further away than 8 metres of the correct location. This raises the following questions:

1. The location has the mentioned attribute Accuracy which refers to "horizontal accuracy". There is also an attribute VerticalAccuracy but it is not clear whether this refers to an y-Axis if the coordinates are seen on a plain or if it means accuracy of the altitude?
2. What could be the reason for this single location to have such bad accuracy? All other points with similar accuracy values are actually very accurate. In this case it was the last location to be tracked but it also happens sometimes during longer tracking sessions.
3. Is there any way to prevent this? I was thinking about implementing some level of statistical function to collect multiple points and get an average of them but that does not fix the root of the problem.