dem_flow_direction — DEM `hydrology` op

• Data kinds: depth → labels

• Call: import fullseye as fs; fs.ledger.dem_flow_direction(dem, cell_size, nodata='error') (to call the implementation directly, import demops; demops.dem_flow_direction(dem, cell_size, nodata='error'); from the registry, opsdem.get("dem_flow_direction"))

• GPU: none (CPU reference implementation only)

Usage

D8 flow direction. O'Callaghan & Mark (1984).

The return value is an integer of (H, W), where 0-7 is the sequence of _D8 and -1 is the sequence of _D8. “No destination” (depression). Boundary cells of nodata="outlet" have 0-7 going out of bounds.

If nodata="outlet", then allow the flow to go to the missing cell (exit the system there). If it is barrier'', it will not lead to missing data. Missing cells themselves are always -1.

Detailed usage guide

• dem_terrain_analysis family guide

References (sample data, literature)

• Sample-data catalog (download URLs / licences) — 2-D uses skimage.data (BSD/public domain) plus synthetic images; 3-D lists download URLs for real data sources (Stanford, PDS, …).

• Operator provenance and references — the sources of the research/methods this op family came from.

• The canonical algorithm (author, year) and its uses are named in the family usage guide above.

Runnable examples (verified samples that actually call this op)

• dem_terrain_analysis_tour — py -3.11 examples/dem_terrain_analysis_tour.py

• poc_geodetic_height_frames — py -3.11 examples/poc_geodetic_height_frames.py

Ops the type connects to (they accept `labels` as input)

—

Same category (`hydrology`)

dem_fill_sinks · dem_flow_accumulation · dem_stream_network

*Provenance: demops.py — DEM operator registry. This per-op note is generated by tools/opdocs.py md (do not hand-edit).*

dem_flow_direction — DEM hydrology op