1.5 KiB
1.5 KiB
Gaps: why measurements are missing
What serves to label a gap (No data) and to state its cause. Taken from docs/domaine/pieges-des-donnees.md (2026-11-04), which refers here; the rules for labeling a gap are in labeling/labeling-rules.md.
- A gap is not necessarily an outage. Acquisition, transmission, ingestion and display are distinct layers.
- At the end of a file, empty values can be just a synchronization delay (
last_sync): WILDSTRUBEL, and MISSISSIPPI on 09/10. - At the start of a file, empty values precede the first measurement: this is not an outage (VERMONT
Powerand temperatures, from 22/02 to 08/04). - Simultaneous gaps on several stations rather point to a common cause outside the station:
- on 22/07 at 14:00: FLORIDA, MISSISSIPPI, VERMONT and NORDEND;
- on 19/08 at 15:00: the same four stations;
- on 22/08 at 17:00: FLORIDA, MISSISSIPPI and NORDEND.
- A gap surrounded by a normal voltage is not an energy problem.
- At the end of a file, empty values can be just a synchronization delay (
- A power cut leaves a signature:
- the voltage is below the knee (~12.8 V) just before or just after the gap;
- the temperature drops during the gap, more than at the same hours on nights without a gap. On VERMONT, the difference ranges from 2.6 to 15 °C over 12 gaps. Alone, it does not settle: the common gap of 19/08 also comes back ~7 °C below the usual, and an outage that came back after sunrise shows no difference (
docs/temperature/domaine/point-de-depart.md).
- A
NaNorinfvalue in an export must be treated as an absence of measurement.