Severity: nit (registry is informational, not consumed programmatically)
Where: src/nhflodata/data/repository.yaml (~L197 and the extent fields).
Problem. The bodemlagen_pwn_regis_koppeltabel v1.1.0 entry lists its own version (1.1.0) as previous_version; and the extent fields mix two coordinate-order conventions and are stale for lakes_pwn, making the registry unreliable as documentation.
Suggested fix. Fix previous_version to 1.0.0, standardize extent on one documented convention (suggest nlmod's xmin,xmax,ymin,ymax), and regenerate stale extents from the actual files.
From a systematic review of modelscripts/09pwnmodel2/01_pwnmodel2.py and its dependency stack (nhflotools, nhflodata, nlmod), July 2026. Every finding was traced through the actual code and adversarially verified before filing.
Severity: nit (registry is informational, not consumed programmatically)
Where:
src/nhflodata/data/repository.yaml(~L197 and theextentfields).Problem. The
bodemlagen_pwn_regis_koppeltabelv1.1.0 entry lists its own version (1.1.0) asprevious_version; and theextentfields mix two coordinate-order conventions and are stale forlakes_pwn, making the registry unreliable as documentation.Suggested fix. Fix
previous_versionto1.0.0, standardizeextenton one documented convention (suggest nlmod'sxmin,xmax,ymin,ymax), and regenerate stale extents from the actual files.From a systematic review of
modelscripts/09pwnmodel2/01_pwnmodel2.pyand its dependency stack (nhflotools, nhflodata, nlmod), July 2026. Every finding was traced through the actual code and adversarially verified before filing.