You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 15, 2024. It is now read-only.
I written a little app that writes a GPX file contains a track composed with returned locations.
The app is based on the app described in https://github.com/jfversluis/XFBackgroundLocationSample.
The coordinates are not very precise, there are jumps in places where they shouldn't be.
The test.gpx file is the file saved after the test and the test.jpg image illustrates the track on a map (the red path is the real one, the blue one is the recorded one).
How can this behavior be improved?
Unfortunately, this is not acceptable in a track recording app.
Steps to Reproduce
I've attached the app.
Give permissions to the app:
App - Location => Allow all the time
App - Location => Use precise location
App - Battery => Unrestricted
Battery => Power saving off
After launch tap on Start/stop button, walk a couple of blocks and tap the button again.
Go in Documents directory. You can find a file named test.gpx.
Open the gpx file in a map application/web site and look at the track and compare it with the traveled track.
Expected Behavior
The recorded track and the track traveled should be similar
Actual Behavior
The recorded track contains many inaccurate points
Version with issue: Xamarin.Essentials 1.7.3
Platform Target Frameworks:
Android: Target framework 12.1
Affected Devices: I've do the test with a Samsung A53 with Android version 12
I written a little app that writes a GPX file contains a track composed with returned locations.
The app is based on the app described in https://github.com/jfversluis/XFBackgroundLocationSample.
The coordinates are not very precise, there are jumps in places where they shouldn't be.
The test.gpx file is the file saved after the test and the test.jpg image illustrates the track on a map (the red path is the real one, the blue one is the recorded one).
How can this behavior be improved?
Unfortunately, this is not acceptable in a track recording app.
Steps to Reproduce
I've attached the app.
Expected Behavior
The recorded track and the track traveled should be similar
Actual Behavior
The recorded track contains many inaccurate points
Attachments
test.zip
XFBackgroundLocationSample-modified.zip
The text was updated successfully, but these errors were encountered: