Skip to content

Update README.md #208

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.

Sign up for GitHub

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

Open
jtec wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update README.md #208

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -159,9 +159,9 @@ RINEX file with us.

When processing your own GNSS data, your receiver may provide you both the RINEX OBS and NAV files. If you want to
specifically use your own RINEX NAV file, it shall be in the same folder as your OBS file and follow the RINEX 3 file
naming convention. This can be achieved by passing your RINEX NAV file in `gfzrnx`:
naming convention. This can be achieved by processing your RINEX NAV file with `gfzrnx`:

`gfzrnx_217.exe -finp <RINEX_OBS_filepath> -fout ::RX3::` (on Windows, use the adequate
`gfzrnx_217.exe -finp <RINEX_NAV_filepath> -fout ::RX3::` (on Windows, use the adequate
`gfzrnx` binary for your platform)

## Acronyms
Expand Down