search

barbeau / gpstest

The #1 open-source Android GNSS/GPS test program
Apache License 2.0
1.78k stars 364 forks source link

Accuracy: Show +/- bias for vertical (altitude) error #548

Open barbeau opened 3 years ago

barbeau commented 3 years ago

Is your feature request related to a problem? Please describe. Mentioned in https://github.com/barbeau/gpstest/issues/529#issuecomment-925287123.

Currently the vertical error graph uses the absolute value of difference between actual and observed altitude (height above WGS84 ellipsoid) values, so you can't tell directional bias.

Describe the solution you'd like It would be nice to show +/- values somehow. One option would be to include a preference to make the graph show +/- values, another would be to show a separate graph.

From https://github.com/barbeau/gpstest/issues/529#issuecomment-925287123:

Coming up with a value to enter was still a bit of a problem, until I realized that by setting the altitude to zero instead of leaving it blank, the "error" now becomes an "calculated altitude," and if I know the actual/recorded altitude, I can simply compare them. The outcome is more useful than the original intent, since for "error," the app returns the absolute value, and for my usage, high or low is of interest. For horizontal error, the error traceline tells me if there is a directional bias. For vertical error, I didn't get a clue as to directional bias. If other use cases would have interest in actual error, perhaps you could put a box below the map with a graph like the elevation graph on some tracking displays. Not a priority for me, but I would enjoy it.

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. Please comment here if it is still valid so that we can reprioritize. Thank you!

stale[bot] commented 1 year ago

Closing this. Please reopen if you believe it should be addressed. Thank you for your contribution.

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. Please comment here if it is still valid so that we can reprioritize. Thank you!

barbeau commented 1 year ago

Not stale

stale[bot] commented 7 months ago

This issue has been automatically marked as stale because it has not had recent activity. Please comment here if it is still valid so that we can reprioritize. Thank you!

barbeau commented 7 months ago

Not stale