Names follow the SUEWS YAML specification; click one for its definition in the configuration reference.
state_limit | 2000 |
Where: Pre-migration Water State row 42240000
Stores Helsinki origin, StateLimit 2000, WaterDepth 2000 and Ref 90240015.
Where: First archived SUEWS_Water code-1000 row
First introduces the code-1000 row with StateLimit 2000; the change was reverted and the same row was restored in commit d3659012860cb22f8c778e953e474d532cc08ae3.
Where: SUEWS v2017a labelled code-1000 row
Adds WaterDepth 2000 to the row and explicitly labels it Helsinki, Järvi et al. (2014).
Where: SUEWS input option StateLimit
Defines StateLimit as the maximum water-surface state in millimetres, with WaterDepth required not to exceed it; large bodies use large limits and shallow fountains use small limits.
Where: Open-water state limiting in suews_phys_waterdist.f95
Excess water above StateLimit becomes runoff and the water state is capped at the configured limit.
Where: Table 4, SUEWS parameter values, p. 1701
The Water column and overall-area table do not publish StateLimit or WaterDepth 2000 mm.
| Name | supported Archived Helsinki 2 m water-state configuration identifies the retained release row and its model role without presenting Järvi et al. (2014) as the publication of the 2 m limit. issue #189 |
|---|---|
| Target | supported SUEWS defines StateLimit as the upper limit of the open-water surface state, matching the land_cover.water water-state target. |
| Values | supported The legacy database, the first archived SUEWS input row and the labelled v2017a row all retain StateLimit 2000 mm; v2017a also carries WaterDepth 2000 mm. Model documentation confirms these are a 2 m upper state limit and configured water depth, not a sentinel or a published measurement. |
| Source | supported Unreferenced is correct because no publication states or derives the 2 m configuration. Järvi et al. (2014) Table 4 contains no water state limit; source_legacy_ref 90240015 preserves the historical application-paper link without exporting it as parameter provenance. issue #189 |
| Place | supported Helsinki is the explicit identity of the archived release configuration. It records where the row was intended for use, not where a physical 2 m water body was measured. |
| Representativeness | supported City limits the catalogue entry to its labelled Helsinki application scope. It does not claim that every Helsinki water body is 2 m deep or that the setting transfers beyond Helsinki. |
| Method | supported Assumed records a model-configuration choice for an upper state limit and initial water depth; the archive and documentation provide no measurement, fit or calculation for the selected 2000 mm. issue #189 |
| Identity | supported Legacy ID 42240000 and the exact code-1000 release lineage establish a distinct archived Helsinki configuration. The stable path and origin remain unchanged. |
The 2000 mm pair is fully traceable as an archived SUEWS configuration but not as a published Järvi parameter. Git history first introduces code 1000 with StateLimit 2000, later restores it after a revert, and the v2017a table adds WaterDepth 2000 and the Helsinki/Järvi label. SUEWS documentation and source code establish the quantity as an upper open-water state and configured depth. The database therefore retains the exact row as an assumed Helsinki application configuration, uses unreferenced to avoid false publication attribution, and preserves legacy source ID 90240015 only as lineage. No value, stable path, origin, legacy ID or legacy WaterDepth is changed.
WaterDepth | 2000 |
Paste under land_cover.water in a SUEWS YAML configuration; every value carries its citation.
state_limit:
value: 2000
ref:
ID: unreferenced
DOI: null
desc: helsinki, city
Raises a prefilled sign-off issue. CI accepts it only when the issue author is in the verifier registry and the evidence revision is still current.
Review procedureland_cover.water · docs