Skip to content

What is upstream of this pixel like?

Shape measures like perimeter or elongation normally have to be computed on demand: delineate the catchment of the point you care about, walk its boundary, then do the arithmetic. Here all sixteen are already computed and stored at the pixel, so getting them is a raster read. That is only possible because every pixel stores a depth-first interval, and both the catchment and its divide follow from those two numbers — which is what makes doing it at every pixel, rather than at a fixed list of outlets, affordable at all.

Global map(unavailable)Example basin (pixel-level)
Global map(unavailable)Not available in a browser: the sixteen values are stored at every land pixel with at least 10 km² upstream, far more than a web map can draw. The rasters are in the Zenodo archive. A browsable version arrives at reach level with FullRiver.
Example basin (pixel-level)Basin 8595: click a pixel and read the sixteen upstream attributes stored there
Show
Clicking

Attributes at the selected pixel

Click a pixel on the map. That pixel’s upstream catchment, the divide around it, and the two axes the shape metrics are built from are drawn, and the sixteen stored values are listed.
Basin 8595 pixels that carry the sixteen attributes
the upstream area those values describe
the divide around it
L∥, the axial length
L⊥ and the bounding box
L∥ = max ∥p − v∥, p ∈ ∂U(v)
Site under development — pages may change daily. The current data release is archived on Zenodo. Comments on the dataset are welcome in the open discussion at ESSD; anything else, [email protected]