Rust package to parse and analyze Rinex files
Use ::from_file to parse a RINEX file:
```rust let rinex = Rinex::from_file("data/amel0010.21g"); println!("{:#?}", rinex);
let rinex = Rinex::from_file("data/aopr0010.17o"); println!("{:#?}", rinex); ```
All "Comments" are currently discarded and not treated.
length
of a Rinex file returns the number of payload items:
RinexType::ObservationData
RinexType::NavigationMessage
rust
let rinex = Rinex::from_file("data/amel0010.21g");
println!("{}", rinex.len());
2.04 <= v <= 3.11 has been extensively tested and should work on most RINEX files.
Refer to /data to see the database against which this lib is automatically tested.
The Rinex Header
inner object contains all
general and high level information
rust
let rinex = Rinex::from_file("data/AMEL00NLD_R_20210010000_01D_MN.rnx");
let header = rinex.get_header();
println!("{:#?}", header);
assert_eq!(header.get_type(), RinexType::NavigationMessage);
assert_eq!(header.get_constellation(), constellation::Constellation::Mixed);
Other example
rust
let rinex = Rinex::from_file("data/dlf10010.21g");
let header = rinex.get_header();
println!("{:#?}", header);
assert_eq!(header.get_version().to_string(), "2.11");
assert_eq!(header.get_pgm(), "teqc 2019Feb25");
assert_eq!(header.run_by(), "Unknown");
TODO
Many RINEX file types exists, RinexType
(refer to API) describes some of them.
The payload of a RINEX file depends on the Rinex type.
For each supported type this library provides a convenient interface to
manipulate the file content.
NAV messages share NavigationFrame content in common.
The rest is GNSS constellation depedent (refer to data indexing section).
Three main constellations are currently supported
That means the lib will not build internal data against other unique GNSS constellation files.
TODO
This lib builds a dictionnary interface to interact, sort and retrieve RINEX files payloads. Some restrictions may apply to certains GNSS constellations, refer to specific paragraphs down below.
All known keys are referenced in the /keys folder.
For key and related data specifications, refer toe the related "DATA RECORD" description
in the RINEX
specifications
TODO
TODO
TODO
TODO