-
Notifications
You must be signed in to change notification settings - Fork 22
Meteo identification
RINEXCLI -i
and related options demonstrations.
Meteo Data is very similar to Observation Data, we expect a similar behavior.
When identification meteo data, you want to know:
- the physics being measured (temperature, pressure..)
- the time frame of the observations
- ideally: what sensors were in use
- ideally: the location of the sensors
The presence of data gaps in Observations will most likely inhibit further operations in those time frames.
We'll run the identification process on POTS00DEU
hosted in this repo.
The following applies as long as at least one Meteo file is present in the pool.
rinex-cli -i -f ./test_resources/MET/V2/POTS00DEU_R_20232540000_01D_05M_MM.rnx.gz
The time frame tells you that the observations are expressed in UTC as all METEO RINEX.
The sampling of 6 observations per hour is strictly steady, no gaps were detected.
Only the typical sensors are present: Tempearture, Pressure and Moisture sensors.
The altitude above sea of the station is given, which is useful when loading its data into models.
- Wiki
- RINEX Data
- Getting Started
- Filter Designer (Preprocessor)
- QC/Analysis mode
- File operations
- Post Processed Positioning (ppp)