Home
Welcome to the RINEX Wiki 👋
This Wiki is a serie of tutorials to help you get started with our applications.
We will try to focus on real world and meaningful applications.
We focus on the applications (at a high level) and not the libraries.
If you're a developer who is familiar with some of these applications, you're probably more
interested by the official API (docrs), our contribution or developer guiderlines.
If you encounter any troubles reproducing one of the examples or would like to participate or provide other examples, you can
- Open a new Issue on Github.com
- Open a Discussion
- Leave a message on Discord
- GNSS and Navigation 🧭
- Timing and Time transfer 🕙 🕐
- Radio communications 📡
- Atmosphere analysis 🌧️
- Open Data 💹
We will focus on what RINEX and more broadly, GNSS processing demands. Especially how to navigate and study these datasets. We will also discuss SP3 and other high end products, that are typically used by the applications targetting the best accuracy.
This wiki is currently describes what our current RINEX-Cli (for the lack of a better name)
is capable of. The application is command line based, we do not have a GUI yet, it will be developped
once most features already work. Although, it is capable of generating visual reports (as HTML pages) and is typically
operated in conjunction of a web browser.
First designed to export the RINEX library, the tool then grew to emulate Teqc. Nowadays, the tools capabilities are broader than that, while not being the exact combination of all of these (too broad spectrum), the application regroups:
- like Teqc and Glab, the capacity to analyze and generate reports on GNSS datasets
- integrates a complete position solver with features similar to RTKLib, with the possiblity to generate CGGTTS (special) solutions (whick RTKLib does not have)
- like Teqc/Anubis, is oriented towards data quality verification and visualization
The current limitation of RINEX-Cli is that is does not support the analysis of differential contexts (typically RTK).
We support SBAS vehicles and may have some exotic operations like RINEX(A) - RINEX(B), that are differential by nature, or allow
differential positioning by nature. But complete analysis for a true differential context, made of one receiver and a secondary reference receiver,
is currently not supported.
This will no longer be true, once the position solver supports RTK, but it will require the capabilities to work with a real time receiver and have network communication capabilities.
Other limitations specified in the Git front page, apply to this toolbox as well.
This toolbox would not be possible without the incredible ecosystem that is available to Rust nowadays:
