Meteo Product Chain
How the ten meteo product notebooks (10_METEO/30_PRODUCTS) turn screened measurements into the finished variables, and which of them depend on each other.
The numbering carries dependency information: 02 and 03 read the product written by 01, 07 reads the products written by 02 and 04, and 10 reads 02 as a diagnostic reference. Everything else is independent and could run in any order.
The two soil products, 09 (SWC) and 10 (TS), differ from the tower products in one respect that the diagram makes visible: they have no external reference. No weather service measures this plot’s soil, so each is checked against the other depths of its own profile instead.
Reading the diagram
Blue products are gap-filled or reference-filled (SW_IN, TA, PPFD_IN, PREC, TS), green products ship as measured (RH, PA, LW_IN, SWC), and the orange product is computed from other products (VPD).
A few things the edges make explicit:
- Two notebooks do not read the database.
07 downloads nothing at all: it reads two finished product files and applies a formula. 10 reads the database indirectly, through the screened TS files that TS_FF1_SCREENED_30MIN_2004-2025 downloads once, so that the 34 channels are not re-queried every time a decision in 10 is revisited.
01 is the hub of the chain. Its gap-filled SW_IN_T1_47_1_gfXG is a driver in both the TA and the PPFD_IN gap-fill models, which is why the order 01 → 02 / 03 is real and not just a naming convention.
06 (LW_IN) has no reference of any kind. Lägern measures no longwave and there is no second longwave sensor on the tower, so its corrections rest on provenance rather than on an independent measurement.
08 (PREC) reads more references than any other notebook — three files, for two different jobs. The Ehrendingen (OED) record arrives as two products, daily up to September 2014 and 30MIN after, and the 30MIN half is what fills the gaps. The regional ensemble is a different tool: one nearby gauge can show that the tower changed in 2018, but only a dozen of them can show which side of that break is wrong, which is what the homogenisation factors rest on.
05 reads the MeteoSwiss pressure as a diagnostic only (dashed): it checks the tower record but never writes a value into it. The NABEL hut barometer it also downloads is likewise diagnostic and is not exported.
- The two soil products have no external reference.
09 (SWC) and 10 (TS) are checked against the other depths of their own profile. 10 additionally reads 02’s gap-filled air temperature as a diagnostic (dashed), which cannot validate any single depth but would catch a whole-profile error such as a wrong file, a wrong unit or a shifted year.
What 99 merges
Notebook 99 concatenates the value and flag columns of the individual products into one half-hourly table and re-checks the joined index. Its PRODUCTS list covers 01–09, 30 columns in all. 10 (TS) is not merged: its 35 columns are read from the TS product file directly.
TA, PREC and four of the five SWC depths enter the merge twice, because each exports two value columns: the measured series and the homogenised one. Each is listed as two entries so that both get their own overview figure, and the loader skips a column it has already taken, so a shared file cannot be merged in twice.
Three products may legitimately contain NaN in the merged file. 05 (PA) and 06 (LW_IN) export as measured and their sensors start in September 2005; PREC keeps the 2,224 half-hours before September 2014 that have no sub-daily reference to fill them from. The merge check carries a reason for each and asserts completeness for everything else.
Precipitation aggregates differently from the other products: rainfall sums, it does not average. Every entry in PRODUCTS therefore names its aggregation. A daily mean of 30-minute rainfall is approximately 0.05 mm and is not an interpretable quantity, whereas the daily total is.
Back to top