11
22
3- ###########################
3+ ########################
44Time Series Repositories
5- ###########################
5+ ########################
66
77This page describes the design of the repository system for developers and advanced
88users who need to build inventory tools, implement downloaders, or integrate with
@@ -25,7 +25,7 @@ These form a strict, deterministic pipeline::
2525
2626
2727Repository Configuration
28- =========================
28+ ========================
2929
3030A repo configuration defines how a directory of files is interpreted as structured data.
3131
@@ -70,7 +70,7 @@ Key terminology
7070
7171
7272Source Priority Configuration
73- ------------------------------
73+ -----------------------------
7474
7575The ``source_priority `` block in ``dstore_config.yaml `` specifies preferred data
7676sources per agency-managed station group:
@@ -93,7 +93,7 @@ For example, EBMUD station data is resolved by preferring USGS, then EBMUD, then
9393
9494
9595Filename Templates and Interpretation
96- ======================================
96+ =====================================
9797
9898Filename templates define the bidirectional mapping between metadata and filenames.
9999
@@ -120,7 +120,7 @@ Design rules:
120120
121121
122122Registry (station_dbase.csv)
123- =============================
123+ ============================
124124
125125The registry provides authoritative metadata that enriches filename-derived fields.
126126
@@ -138,7 +138,7 @@ Inventory System
138138Inventory converts repository files into structured summaries.
139139
140140File inventory (``repo_file_inventory ``)
141- -----------------------------------------
141+ ----------------------------------------
142142
143143Groups by ``file_pattern ``. Represents:
144144
@@ -147,7 +147,7 @@ Groups by ``file_pattern``. Represents:
147147* Provider-specific datasets
148148
149149Data inventory (``repo_data_inventory ``)
150- -----------------------------------------
150+ ----------------------------------------
151151
152152Groups by ``series_id ``. Represents:
153153
@@ -167,7 +167,7 @@ A ``series_id`` is constructed from metadata::
167167
168168
169169Populating the Repository
170- ==========================
170+ =========================
171171
172172The :doc: `commands ` page documents the full CLI workflow. A summary::
173173
@@ -225,7 +225,7 @@ Guarantees: stable formatting, idempotent round-trip, canonical YAML header.
225225
226226
227227End-to-End Flow
228- ================
228+ ===============
229229
230230Read path::
231231
@@ -241,7 +241,7 @@ Write path::
241241
242242
243243Design Principles
244- ==================
244+ =================
245245
246246Fail fast
247247 Bad filenames → error. Bad config → error. No implicit recovery.
@@ -265,7 +265,7 @@ Separation of concerns
265265
266266
267267Architectural Evolution Notes
268- ==============================
268+ =============================
269269
270270The repository system was refactored from an implicit agency-based model to a fully
271271config-driven provider model. Key terminology changes:
@@ -284,5 +284,4 @@ Configs **must** define ``site_key``, ``provider_key``, and
284284``provider_resolution_mode ``. Misconfigured repos fail immediately — there is
285285no fallback behavior.
286286
287- The legacy ``parse.style = legacy `` option remains for backward compatibility.
288-
287+ The legacy ``parse.style = legacy `` option remains for backward compatibility.
0 commit comments