Doc update

CONTRIBUTING.md

@@ -1,54 +1,52 @@
 CONTRIBUTING
 ============
 
-First of all: Hello and welcome on board!
+Hello and welcome on board :wave:
 
-Use `cargo fmt` prior submitting a pull request so the CI/CD does not fail on coding standards issues.
+Use the github portal to submit PR, all contributions are welcomed.  
+Don't forget to run a quick `cargo fmt` prior any submissions, so the CI/CD does not fail
+on coding style "issues".
 
 This crate and ecosystem is part of the Georust community.  
-You can contact us to ask questions on our Discord channel, 
-see the [community portal](https://github.com/georust/geo)
-
-lib architecture
-================
-
-For each supported RINEX types, we have one folder.  
-The folder bears the name of such RINEX type. In that folder,
-you can find a `record.rs` file where that particular files content is described. 
-It also contains its dedicated parsing methods.
-
-- src/lib.rs : main library, `Rinex` definitions
-- src/constellation/mod.rs : GNSS constellations definition
-  - src/constellation/augmentation.rs : SBAS related definitions 
-- src/sv.rs : Satellite vehicule definitions
-- src/observation/mod.rs : OBS RINEX entry point
-  - src/observation/record.rs : OBS RINEX specific record definitions
-- src/navigation/mod.rs : NAV RINEX entry point
-  - src/navigation/record.rs : NAV RINEX specific generic record definitions
-  - src/navigation/ephemeris.rs : Ephemeris frames definition, parsing method and related calculations, like Kepler solving
-  - src/navigation/ionmessage.rs : new ION frame definition and parsing methods
-  - src/navigation/eopmessage.rs : new EOP frame definition and parsing methods
-- src/meteo/mod.rs : Meteo RINEX entry point
-  - src/meteo/record.rs : specific record definitions, including parsing methods
-  - src/hatanaka/mod.rs : Compression / Decompression module 
-  - src/qc/mod.rs : Quality Check module
-  - src/qc/analysis/sv.rs : Satellite Vehicle general analysis
-  - src/qc/analysis/obs.rs : OBS RINEX specific analysis
+You can reach us on our Discord channel, 
+see our [community portal](https://github.com/georust/geo),
+to ask questions, request features..
+
+Crate architecture
+==================
+
+For each supported RINEX types, we have one folder named after that format.  
+`src/navigation` is one of those. 
+
+The module contains the record type definition. RINEX file contents vary a lot
+depending on which type of RINEX we're talking about.  
+For complex RINEX formats like Navigation Data, that module will contain all possible inner types.
+
+Other important structures :
+- `src/constellation.rs` defines GNSS constellations
+- `src/constellation/augmentation.rs` : preliminary SBAS support
+- `src/sv.rs` defines a Satellite vehicle, which is associated to a constellation
+  - src/hatanaka/mod.rs : the Hatanaka module contains the RINEX Compressor and Decompressor 
 
 NAV RINEX
 =========
 
-Abstraction for NAV files parsing is provided by the `navigation.json` descriptor.  
-This is how we describe all supported revisions and their data fields.  
+Orbit instantaneous parameters, broadcasted by GNSS vehicles, are presented in different
+forms depending on the RINEX revision and the GNSS constellation.
+
+To solve that problem, we use a dictionary, in the form of `src/db/NAV/orbits.json`,
+which describes all fields per RINEX revision and GNSS constellation.
+
+This file is processed at build time, by the build script and ends up as a static 
+pool we rely on when parsing a file. 
 
-Improving or updating NAV file parsing either means updating this database, 
-or improving the way we rely on it. This is handle
+The dictionary is powerful enough to describe all revision, the default Navigation Message
+is `LNAV`: Legacy NAV message, which can be omitted. Therefore, it is only declared 
+for modern Navigation messages.
 
 Introducing a new RINEX type
 ============================
 
-A good guideline would be to follow the src/meteo/mod.rs module, which is simple enough,
-yet follows the basic principles previously explained.  
+`src/meteo/mod.rs` is the easiest format and can serve as a guideline to follow.
 
-A more complex RINEX declination would be src/navigation, because the inner record entry
-can have 3 or 4 different variations.
+When introducing a new Navigation Data, the dictionary will most likely have to be updated (see previous paragraph).

README.md

@@ -11,25 +11,59 @@ RINEX
 
 Rust tool suites to parse, analyze and process [RINEX Data](https://en.wikipedia.org/wiki/RINEX).
 
+This RINEX toolsuite is part of the [GeoRust community](https://github.com/georust),
+and we aim towards advanced geodesic and ionospheric analysis.
+
+## Advantages :rocket: 
+
+- Fast
+- Open sources
+- Native Hatanaka decompression and compression
+- Seamless .gzip decompression with `flate2` compilation feature
+- RINEX V4 full support, that includes modern Navigation messages
+- Meteo RINEX full support
+- IONEX and Clock RINEX partial support, will be concluded soon
+- File merging, splitting and pre processing
+- Modern constellations like BeiDou, Galileo and IRNSS
+- Supported time scales are GPST, BDT, GST, UTC
+- Full support of Military codes : if you're working with such signals you can
+at least run a -qc analysis, and possibly the position solver once it is merged 
+- Supports high precision RINEX (scaled phase data with micro cycle precision)
+- RINEX post processing like SNR, DCB analysis, high precision Broadcast
+and SP3 ephemeris interpolation..
+- RINEX-qc : statistical analysis like "teqc", including on modern signals and SP3 high precision orbits
+- An SPP/PPP position solver is under develoment:
+checkout [this branch](https://github.com/georust/rinex/tree/solver) which
+is kept up to date until merged
+
+## Known weaknesses :warning:
+
+- QZNSST is represented as GPST at the moment
+- GLONASST and IRNSST are not supported : calculations (mostly orbits) will not be accurate 
+- Partial SBAS support : some features are not yet available
+- The command line tool does not accept BINEX or other proprietary formats
+- File production is not fully concluded to this day, some formats are still not correctly supported
+(mostly NAV).
+
+## Architecture 
+
 * [`rinex`](rinex/) is the core library 
 * [`rinex-cli`](rinex-cli/) is a command line application based on the core library.  
 It can be used to process RINEX files and perform operations similar to `teqc`.   
 The application is auto-generated for a few architectures, download it from the 
 [release portal](https://github.com/gwbres/rinex/releases)
 
-* [`rnx2crx`](rnx2crx/) is a RINEX compression program 
-* [`crx2rnx`](crx2rnx/) is a CRINEX decompression program (Compact RINEX to RINEX)
+* [`rnx2crx`](rnx2crx/) is a RINEX compressor (RINEX to Compact RINEX)
+* [`crx2rnx`](crx2rnx/) is a CRINEX decompresor (Compact RINEX to RINEX)
+* [`rinex-qc`](rinex-qc/) is a library dedicated to RINEX files analysis 
+* [`qc-traits`](qc-traits/) is a library dedicated to RINEX files analysis 
 * [`sinex`](sinex/) SNX dedicated core library
 
 * [`ublox-rnx`](ublox-rnx/) is an application that connects to a `Ublox`
 receiver and generates RINEX data quickly & easily.   
 It is the combination of the [ublox](https://github.com/lkolbly/ublox)
 and [rinex](rinex/) crates.
 
-By default, all timestamps are in UTC with leap seconds correctly managed.
-
-This RINEX toolsuite is part of the [GeoRust community](https://github.com/georust),
-and we aim towards advanced geodesic and ionospheric analysis.
 
 RINEX Standards
 ===============
@@ -63,11 +97,6 @@ File formats
 
 :heavy_minus_sign: No restrictions: file names do not have to follow naming conventions.  
 
-## Known weaknesses :warning:
-
-- Glonass Time Scale is not known to this day.
-We cannot parse and apply system time corrections from other time scales into the glonass time scale.
-
 Benchmarking
 ============
 
@@ -84,6 +113,14 @@ processing/esbc00dnkr2021/mask:obs |  438.73 ms |
 processing/esbc00dnkr2021/mask:sv | 341.42 ms | 
 processing/esbc00dnkr2021/smooth:hatch:l1c,l2c | 502.90 ms | 
 
+Special Thanks
+==============
+
+RINEX relies heavily on the great libraries written by C. Rabotin, [check out his work](https://github.com/nyx-space).  
+Some features would not exist without the invaluable help of J. Lesouple,
+check out his 
+[PhD manuscript (french)](http://perso.recherche.enac.fr/~julien.lesouple/fr/publication/thesis/THESIS.pdf?fbclid=IwAR3WlHm0eP7ygRzywbL07Ig-JawvsdCEdvz1umJJaRRXVO265J9cp931YyI)
+
 Contributions
 =============
 

rinex-cli/README.md

@@ -50,7 +50,7 @@ if you know how to operate the preprocessing toolkit
 ## Data analysis 
 
 This tool can perform several data analysis. Feasible operations
-are highly dependent on the context provided by the user.
+are highly dependent on the context provided by the user.  
 Refer to [this page](doc/file-combination.md) to understand
 what minimal context should be provided, for the analysis you want to perform.
 

rinex-cli/doc/file-combination.md

@@ -7,9 +7,9 @@ you want to perform.
 
 ## Meteo RINEX analysis
 
-To analyze a Meteo file, a primary file of this type should be passed
-to `--fp` (or `-f`). In this case, you get a visualization
-of all observations. An in depth statistical analysis is feasible with `--qc`.
+To analyze a Meteo file, a primary file of this type should be passed to `--fp` (or `-f`).   
+In this case, you get a visualization of all observations. 
+An in depth statistical analysis is feasible with `--qc`.
 
 It does not make sense to stack other RINEX files to such analysis.