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

RINEX v2 ionosphere parameters support #236

Closed
fedosgad opened this issue Apr 24, 2024 · 4 comments · Fixed by #239
Closed

RINEX v2 ionosphere parameters support #236

fedosgad opened this issue Apr 24, 2024 · 4 comments · Fixed by #239

Comments

@fedosgad
Copy link
Contributor

In RINEX v2 files header records with labels ION ALPHA and ION BETA are allowed. They contain coefficients for ionospheric delay calculations for GPS system (GLONASS, which is also allowed in those RINEX versions, does not broadcast any ionosphere-related information and can be safely ignored). Those fields are checked for by header parser but not handled any further (there are TODO notices).

According to Navipedia and IS-GPS-200D (Figure 20-4), coefficients are used for Klobuchar model calculations. This model is already supported by library. IONOSPHERIC CORR field, which replaced ION ALPHA and ION BETA in RINEX v3, is handled by header parser which presents it as a separate IonMessage. I propose that ION ALPHA and ION BETA should be handled in a similar manner, adding a IonMessage wrapping KbModel to resulting Header.

I am willing to make a PR for this issue. It would be my first experience with Rust though, possibly requiring thorough code review (I have previous coding experience in other languages, so maybe it's not that bad). Current developers/maintainers, would you like me to make such a PR?

@gwbres
Copy link
Collaborator

gwbres commented Apr 25, 2024

@fedosgad,

first off, thank you very much for inquiring and yes any contribution is welcome.
This topic is important because the current state does not allow precise positioning using V < 3 RINEX (so GPS, Glonass and GAL possibly)

@fedosgad
Copy link
Contributor Author

Great!
I'll take to it then.

@fedosgad
Copy link
Contributor Author

Created #239

@gwbres gwbres linked a pull request Apr 26, 2024 that will close this issue
@gwbres
Copy link
Collaborator

gwbres commented Apr 26, 2024

Thank you for your contribution, this will be added to V0.16 that I'm publishing this week end

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

Successfully merging a pull request may close this issue.

2 participants