Replies: 3 comments 8 replies
-
We store the horizontal accuracy as provided by Android. PS: Battery saver is tough as then we don't get any GPS data at all. |
Beta Was this translation helpful? Give feedback.
-
Ahhh. I was just going to start a discussion on exporting (some how) in a GPX file whether GPS was enabled for the track or not. But it seems that this horizontal accuracy would be the solution. This would also be usable for specifying the accuracy when uploading the data to Google Fit via the com.google.location.sample's Here's an interesting StackOverflow Q&A about expressing accuracy in GPX files with a wikipedia link for Dilution of precision. Other searches seem to indicate people using the |
Beta Was this translation helpful? Give feedback.
-
Seems not. Even tracks that don't enable GPS have accuracy set on their points. So a lack of accuracy cannot be used as a test for whether GPS was enabled or not. So it seems I am back to including some kind of element or attribute (whatever the XML nomenclature is for it) to indicate whether GPS was actually enabled for the track or not. The interesting thing is that in my GPX->Google Fit app, I made a WAG at a fixed 10m as the GPS accuracy of all of my |
Beta Was this translation helpful? Give feedback.
-
I'm finding that OpenTracks is the most transparent and currently maintained Android program for getting for GPX recordings for trail mapping, etc.
I wonder if open tracks could show information about the quality of the track - whether it detects energy saver mode interfering, when it had to discard location data because of low accuracy, etc, and save that as a log. It would help with troubleshooting poor-quality tracks. Is there already a way to get this information?
Beta Was this translation helpful? Give feedback.
All reactions