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

Parse DTM and display some info if it is non-standard #527

Closed
gdt opened this issue Jun 21, 2021 · 2 comments
Closed

Parse DTM and display some info if it is non-standard #527

gdt opened this issue Jun 21, 2021 · 2 comments

Comments

@gdt
Copy link

gdt commented Jun 21, 2021

We have observed receivers that operate in strange datums, when the user has not configured them to do so (.e.g. PZ-90 in the US). This is a receiver bug, not a GPSTest bug, and thus this is a feature request for GPSTest to help the user understand what their receiver is doing.

While a user can log data and go read NMEA, that requires effort. It would be great if GPSTest would observe DTM sentences and parse them, and if a non-standard configuration is observed, display something to the user. By non-standard, I mean anything other than "just WGS84, period, no offsets". What could be displayed might just be DTM in red, to give a clue that the raw NMEA should be looked at, or it could be more, like "DTM: PZ-90". (That's P90->PE90 from NMEA, and PZ-90 because that's what EPSG calls it.)

Perhaps, the red DTM could be clickable, and go to a screen with the full contents including transforming the minutes E/N shift into cm. But really, just seeing a '"your receiver is operating in a non-standard datum" warning would be a huge step forward.

@barbeau
Copy link
Owner

barbeau commented Jun 22, 2021

Thanks @gdt, this is a good idea. I've added to the future "Device info" screen that I have planned in #313 (comment), which will also show other common data issues. I'm going to close this issue as a duplicate now that I have this captured in #313 (comment).

@barbeau barbeau closed this as completed Jun 22, 2021
@Bug725
Copy link

Bug725 commented Jun 23, 2021 via email

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

No branches or pull requests

3 participants