Skip to content

0.9.3

Choose a tag to compare

@Praddy-GByte Praddy-GByte released this 19 Oct 23:31
· 7 commits to main since this release

The answer now carries the accuracy that was measured at its own size

The accuracy published with basinkit is a median per size band, and those medians span two orders of magnitude: 0.3% above 100,000 km2, 1.3% from 10,000 to 100,000, 1.7% from 2,000 to 10,000 — and 30% between 100 and 500, 181% below 100. Both halves have been in the README since the validation was run. Only the first half ever reached the output.

Someone clicking a 135 km2 headwater in QGIS got an area, a boundary and a consistency check, and nothing that said the figure behind the software was measured on basins two orders of magnitude away from theirs. The number was not wrong. It was being quoted about a case it had never been measured on, and the software was the one quoting it.

Basin.validation_envelope() answers the narrower question instead: of the basins that were measured, which ones does this one resemble, and what was the error there. It returns inside, edge or outside, with the band’s own median error and its within-5% and within-20% counts. Reading the area is all it costs, so it downloads nothing.

Given a dem_suitability() result it compares the terrain descriptors too. Those are not new measurements: the five suitability tests are the five numbers recorded beside the area error for 133 of the validation gauges, so each is compared against the range it covered there — the middle 90% separately from the full span, because a value at the 99th percentile was measured by almost nothing and should not read as covered.

Two of those comparisons carry a finding of their own. Within every size band, the fifth of basins whose depression filling was heaviest carried two to three times the median area error of the rest, on three to ten basins per band, which is a direction and not a coefficient. And every basin in the terrain study was fully covered, so a basin with a void in it is outside the set by definition rather than merely unusual.

Aridity, flow regulation and karst are named as uncharacterised rather than quietly omitted. None was recorded in the validation, so no figure here was measured on any of them, and the output says which tool measures each one.

Where it surfaces: Delineate basin prints the band and writes validated and band_err_pct into the output layer’s attribute table, so it survives the dialog closing. Elevation data suitability writes validation_envelope.csv. The report’s uncertainty section states the row instead of pointing at the documentation, and the full-run manifest carries the envelope. The ArcGIS run stays at 70 analyses.

A provenance record that does not have to be believed

The acquisition record added in 0.9.2 said which product a layer came from and when. A repeat study six months later can do nothing with that: if the answer has moved, nothing separates a change of your own from the provider reissuing a tile under the same name and URL.

Every file the cache serves or fetches is now hashed, and each layer record carries the digests of the files that call actually read. The digest is computed once and kept in a sidecar, and HASH_DOWNLOADS turns it off where reproducibility is not the point — a source then reads as unverifiable, never as unchanged. cache.recheck() compares a recorded run against the cache now and answers unchanged, changed, absent or unverifiable.

Every figure in the envelope is recomputed from verify/benchmarks by tests/test_envelope.py, which fails if one drifts from the file it came from. Verified in QGIS 3.34.4 on a real 135 km2 DEM-routed basin.