KUON RINEX QC
Basic quality check for RINEX observations: epochs, completeness, per-constellation counts. Free, no account.
Processing runs on a <b>deterministic parser on the VPS (KUON basic-qc)</b>. <b>Basic statistics only</b> (epoch count, interval, completeness / gap %, per-constellation satellites and observation counts); <b>cycle-slip and multipath metrics are not included</b> (planned for a future advanced QC). To visualise the RINEX contents → RINEX Viewer. Your data is auto-deleted after 24 hours. No account required.
RINEX conversion ・ Hatanaka ・ all tools
What this checks
Four things, from the observation file itself: how many epochs are there, how many should there have been, where the gaps fall, and how many observations each satellite system contributed.
It answers one question before you spend hours on post-processing: is this session worth processing at all?
Completeness
Completeness is observed epochs divided by expected epochs. Expected comes from the interval and the span, so a one-second file over one hour expects 3,600.
Above 95 per cent is a clean session. Between 80 and 95 something interrupted it, and it is worth finding out what. Below 80 the result will be unreliable no matter which software you use.
Per-system counts
If one constellation is missing entirely, it was disabled in the receiver, not absent from the sky.
A system with far fewer observations than the others usually means its signals were not being tracked well: check the antenna and what it can receive.
What this does not tell you
This is a basic check. It counts what is present; it does not look for cycle slips or multipath.
A file can be 100 per cent complete and still give a poor position, because completeness says nothing about whether the measurements were clean.