Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: HDOP threshold setting #382

Open
W-Geronius opened this issue Nov 3, 2024 · 2 comments
Open

Suggestion: HDOP threshold setting #382

W-Geronius opened this issue Nov 3, 2024 · 2 comments

Comments

@W-Geronius
Copy link
Contributor

Some GPS receivers report a 3D fix despite very poor DOP values. It might be better not to rely too closely on these positional data.
What about a HDOP threshold to invalidate a poor fix? Acceptable ranges may be documented as in http://www.noomio.com.au/wiki/faqs/gnss-setting-threshold-for-acceptable-accuracy/

Example:
sensor ATGM336H as included in OBP60 V2 reported a fix at HDOP > 25.0, resulting in position jumps within several hundreds of meters.

@wellenvogel
Copy link
Owner

This functionality heavily depends on the available NMEA0183 data.
Some records like RMC do not report HDOP.
So it at least requires GSA.
And it could be difficult to decide if a HDOP reported by GSA is relevant for a position reported by RMC.

@W-Geronius
Copy link
Contributor Author

Sure, no DOP when GSA is missing - in that case, as well as when RMC talkerid differs from GSA talkerid, no threshold can be applied

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants