Ward et al.'s Lookout Creek river corridor network, derived again from a terrain model and checked against their published geometry

Channels traced from a public 4 m terrain model at Ward et al.'s published 5 ha threshold give 689 links and a 5th-order Lookout Creek, against their 686 segments and 5th order. 90% of their published stream points lie within 30 m of a derived channel, and 99% and more on 3rd to 5th order streams.

How we did Close Matches except Exact New analysis 2 of 6 exact, 3 within tolerance, 1 explained all studies
Network size and order at the published 5 ha threshold · tolerance order exact; segment counts within 2%; basin within 3% (the paper rounds to 6,400 ha; the file's outlet area is 6,335.2 ha)
  • Segments (derived links)686 → 689 +3.0 (+0.4%)within tolerance
  • First-order segments344 → 346 +2.0 (+0.6%)within tolerance
  • Highest Strahler order5 → 5 0match
  • Basin above Ward et al.'s outlet≈ 6,400 ha → 6,264.2 ha −135.8 ha (−2.1%)within tolerance
Stream length · tolerance within 5%
  • Stream length (paper: about 242 km)242 km → 221.9 km −20.1 km (−8.3%)explained why
Published centreline, re-measured from Ward et al.'s StreamCenterline.csv (686 lines by segment number) · tolerance the paper says about 242 km, which rounds to the kilometre: within 0.5 km
  • Stream centreline length (paper: about 242 km)242 km → 242.0 km 0match
Published stream points with a derived channel nearby
  • Ward et al. points within 30 m of a derived channel89.9%new
  • Ward et al. points within 10 m83.6%new
  • Points on 3rd to 5th order streams within 30 m99.6%new
  • Derived channel cells within 30 m of a Ward et al. point92.6%new
  • Ward et al. points within 30 m of HF013-0290.9%new
689 linksfrom the DEM at the published 5 ha; Ward et al. publish 686 segments, 5th order in both
[23, 3]
89.9%of Ward et al.'s stream points lie within 30 m of a derived channel; 99% and more on orders 3 to 5
[33, 36]
92.6%of the derived channel cells lie within 30 m of a Ward et al. point
[58]
56 of 56steps replay identically in a fresh session

Numbers in brackets, like [14], are step numbers in this study's run.json: the NativeGIS call that returned the figure. NativeGIS 0.4.0, recorded 2026-10-31 22:12 UTC.

Map of the Lookout Creek basin over a hillshade, with Ward et al.'s published stream points in orange, the channels derived from the 4 m DEM at 5 ha in dark blue on top, published points more than 30 m from any derived channel in red, the basin outline in black and Ward et al.'s outlet as a black dot
Ward et al.'s published stream points (HydroShare, orange; red where more than 30 m from any derived channel) under the channels derived from the 4 m USGS 3DEP DEM where 5 ha or more drains (blue), inside the basin delineated above their outlet (black). Rendered as SVG by gis_render in the recorded run; click to zoom.

The lower basin, close up

A 4 by 3.5 km window at 1.7 m per pixel: Ward et al.'s points (orange, red beyond 30 m), the derived channels (blue) and HJ Andrews' HF013-02 (purple). The main stem and larger tributaries coincide; the red runs are small channels the two networks trace on different paths, and the tributary below the basin outline that drains past the outlet on the 3DEP DEM.

The lower basin: fire episodes outlined over 2023 high severity
The lower basin

Click or tap a map to open it full screen, then zoom and pan.

What was published

Ward et al. mapped the river corridor of the whole Lookout Creek network in the HJ Andrews Experimental Forest from "a 1 m digital terrain model based on airborne lidar collected in 2008", with a single-direction flow accumulation algorithm (Seibert and McGlynn, 2007) in a modified open-source topographic analysis toolbox. They "defined the stream network as any location draining more than 5 ha", split it into 686 river corridor segments between junctions, about 209 km of valley holding about 242 km of stream, and describe the basin as 5th order, draining about 6,400 ha. The geometry is published on HydroShare (CC BY 4.0): ValeyDetails.csv (the file's spelling) gives a cross-section about every 10 m of valley, 20,770 in all, each with its stream centreline point, upslope area, Strahler order and segment number. The segment counts below are read from that file.

Paper and data set (network geometry)Ward, A. S., Zarnetske, J. P., Baranov, V., et al. (2019). Co-located contemporaneous mapping of morphological, hydrological, chemical, and biological conditions in a 5th-order mountain stream network, Oregon, USA. Earth System Science Data 11, 1567–1581, doi:10.5194/essd-11-1567-2019. Network geometry: Ward, A. (2018), Ward et al., ESSD, 2019 - Network Geometry, HydroShare, doi:10.4211/hs.19024397586b42b0ae622b5a59b1d919. Used again in Ward et al. (2019), HESS 23, 5199, doi:10.5194/hess-23-5199-2019, and Ward et al. (2020), Frontiers in Water 2:7, doi:10.3389/frwa.2020.00007.

ESSD paper · HydroShare network geometry · HESS paper · Frontiers in Water paper

Published method. The threshold is published, so it is used as published: channels start where 5 ha or more drains, and nothing on this page is fitted to Ward et al.'s numbers. The terrain model is not the same: theirs is the 2008 1 m LiDAR DEM; this run uses a 4 m export of USGS 3DEP elevation (see Limits).

The data and where it came from

All of it is open: downloaded without an account or a form.

DataWhereLicence
Ward et al. network geometry, ValeyDetails.csv (the file's own spelling): 20,770 cross-sections with stream centreline X/Y/Z, upslope accumulated area, Strahler order and segment number, UTM zone 10N metresHydroShare resource 19024397586b42b0ae622b5a59b1d919, 10.4 MB CSV, no form or account (the link redirects to the file store)
https://doi.org/10.4211/hs.19024397586b42b0ae622b5a59b1d919
CC BY 4.0
Ward et al. stream centreline, StreamCenterline.csv: 205,322 points along the 1 m stream centreline with X/Y/Z, distance, upslope area, Strahler order and segment number, UTM zone 10N metres (its header ends with a trailing comma, which NativeGIS reads and reports)Same HydroShare resource, 27.7 MB CSV (sha256 c2b0932f…45b73d70), no form or account
https://www.hydroshare.org/resource/19024397586b42b0ae622b5a59b1d919/data/contents/StreamCenterline.csv
CC BY 4.0
USGS 3DEP elevation, exported as a 4 m DEM (32-bit float GeoTIFF, EPSG:26910) over the Lookout Creek basinUSGS National Map 3DEP elevation image service (exportImage), no form or account; the service can answer 502 or 504 under load, and a retry succeeds
https://elevation.nationalmap.gov/arcgis/rest/services/3DEPElevation/ImageServer
US federal data, public domain
HJ Andrews streams from the 2008 LiDAR DEM (HF013-02, lidar_stream.shp, 1,100 lines)HJ Andrews LTER, 356 kB zip, no form or account
https://andrewsforest.oregonstate.edu/sites/default/files/lter/data/studies/spatialdata/hf01302.zip
HJ Andrews data policy (CC BY, acknowledgement requested)

The input files the run read, pinned by checksum

File (relative to the data folder)Bytessha256
samples/dem3dep/ward_basin_26910_4m.tif32,379,9141e3fff6889ad6135…
samples/ward-hs/ValeyDetails.csv10,394,1926b47b82f95d12c98…
samples/hja-open/hf01302/x/lidar_stream.shp160,33270ac82b1e6bf3dc7…
samples/ward-hs/StreamCenterline.csv27,684,522c2b0932f8e6e1755…

Full checksums are in run.json. Replay refuses an input whose checksum differs.

Method

  1. Open the 4 m 3DEP DEM, Ward et al.'s ValeyDetails.csv as points (the stream centreline X and Y of each cross-section, EPSG:26910) and HJ Andrews HF013-02.
  2. From the published file alone: group the cross-sections by segment number and order to count segments by order, count cross-sections by order, and take the point with the largest upslope area as Ward et al.'s outlet (gis_process summarize, gis_query).
  3. Fill depressions (Priority-Flood), D8 flow direction, then the basin above Ward et al.'s outlet (watershed, moving the outlet to the nearest cell within 30 m that drains 100 ha). Keep the flow directions inside the basin only, and check the contributing area at the outlet (flowAccumulation).
  4. Derive channel links with Strahler order where 5 ha or more drains, the published threshold (streams), and count them by order.
  5. Distances: for every published stream point, the exact distance to the nearest derived link, simplified to 2 m (spatialJoin nearest), counted within 10 and 30 m and summarised by Ward et al.'s order and by the order of the nearest link. The converse: derived channel cells whose centre lies within 10 or 30 m of a published point (nearest-point interpolation with that search radius as a mask, then zonal counts). The same published points against HF013-02. Which published points fall outside the derived basin (spatialJoin intersects).
  6. Re-measure the published stream length: open StreamCenterline.csv as points and join them, in file order, into one line per value of "Segment number" (gis_process pointsToLines); the length is the sum of the lines.
  7. Render the maps as SVG over a hillshade of the same DEM; record the run and replay it in a fresh session.

The run made 56 NativeGIS calls: gis_open × 4, gis_process × 29, gis_query × 19, gis_render × 4.

Published numbers next to ours

Network size, order and basin

QuantityPublishedNativeGISSource
Area draining to Ward et al.'s outlet6,335.2 ha (largest UAA in the file)6,264.2 hawatershed on the 4 m DEM, outlet moved 2.4 m [11, 16, 18]
Basin, in the paperabout 6,400 ha6,264.2 ha[18]
Highest Strahler order55streams [23]
Segments (links)686689[3, 23]
Stream lengthabout 242 km221.9 kmD8 links joining 4 m cell centres [23]
Stream centreline, re-measuredabout 242 km241.97 kmWard et al.'s StreamCenterline.csv, 205,322 points joined into 686 lines by segment number [69, 70]
Valley lengthabout 209 km–no valley floor is derived here

Segments and length by order

Strahler orderWard et al. segmentsDerived linksWard et al. cross-sections (share)Derived length, km (share)
134434611,385 (54.8%)120.2 (54.2%)
21671545,318 (25.6%)57.3 (25.8%)
384922,089 (10.1%)23.3 (10.5%)
44545942 (4.5%)10.0 (4.5%)
546521,036 (5.0%)11.1 (5.0%)
All686 [3, 6]689 [23, 27]20,770 [9]221.9 [23]

Ward et al.'s segments run between junctions, as the derived links do, and carry their own Strahler order; NativeGIS counts them by grouping the cross-sections by segment number and order. Their cross-sections fall about every 10 m of valley, so each order's share of cross-sections is close to its share of valley length. The derived network's smallest channel heads drain 5 ha (3,124 cells of 16 m²); the published file's smallest upslope area is 5.0000 ha [6]. Units: metres and hectares in NAD83 / UTM zone 10N (EPSG:26910).

Where the channels are

What lies within the distanceCountShareSource
Ward et al. cross-section stream points within 10 m of a derived channel17,355 of 20,77083.6%[30, 32]
… within 30 m18,669 of 20,77089.9%[33]
Derived channel cells within 10 m of a Ward et al. point40,375 of 47,13585.7%[51, 44]
… within 30 m43,640 of 47,13592.6%[58]
Ward et al. points within 10 m of HJ Andrews HF013-0217,684 of 20,77085.1%[65, 67]
… within 30 m18,875 of 20,77090.9%[68]

Distances from each published stream point to the nearest derived link (simplified to 2 m, half a cell, which takes out the D8 stair-steps) are exact point-to-line distances (gis_process spatialJoin, nearest). The converse counts derived channel cells whose centre lies within 10 or 30 m of a published point; the points sit about 10 m apart along the valley, so between two points the 30 m test reaches at least 29.6 m.

Distance by order

Ward et al. orderPointsWithin 30 mMean distance (m)Largest (m)
111,38586.7%20.0865.9
25,31889.2%19.5651.3
32,08999.3%2.052.1
494299.9%1.832.1
51,03699.9%2.931.3

Distance to the nearest derived link, by the order Ward et al. give the segment [36, 39]. Of the points within 30 m, 84.8% lie nearest a derived link of the same Strahler order. 227 points (1.1%) lie outside the basin delineated on this DEM [59, 61, 63], 150 of them on one small tributary (segments 519 to 522) south-east of the outlet.

Why any numbers differ

Replay it yourself

The run file records every call, its arguments, the checksums of the files it read and the numbers it returned. Replaying it repeats every call in a fresh NativeGIS session and checks that each answer comes out the same.

Verified reproducible on 2026-10-31: 56/56 steps identical. The run file was replayed in a fresh NativeGIS session (0.4.0 (source 3692d6e)) against a folder holding nothing but the public downloads below, fetched with these exact commands.
  1. Make an empty data folder and fetch the inputs into it exactly as below (bash; the folder layout is the one the run file expects):
    cd /path/to/an/empty/folder
    mkdir -p samples/dem3dep && curl -fL -o samples/dem3dep/ward_basin_26910_4m.tif 'https://elevation.nationalmap.gov/arcgis/rest/services/3DEPElevation/ImageServer/exportImage?bbox=558700,4894200,571900,4903800&bboxSR=26910&imageSR=26910&size=3300,2400&format=tiff&pixelType=F32&noData=-9999&interpolation=RSP_BilinearInterpolation&compression=None&f=image'
    mkdir -p samples/ward-hs && curl -fL -o samples/ward-hs/ValeyDetails.csv https://www.hydroshare.org/resource/19024397586b42b0ae622b5a59b1d919/data/contents/ValeyDetails.csv
    mkdir -p samples/ward-hs && curl -fL -o samples/ward-hs/StreamCenterline.csv https://www.hydroshare.org/resource/19024397586b42b0ae622b5a59b1d919/data/contents/StreamCenterline.csv
    mkdir -p samples/hja-open/hf01302 && curl -fL -o samples/hja-open/hf01302/hf01302.zip https://andrewsforest.oregonstate.edu/sites/default/files/lter/data/studies/spatialdata/hf01302.zip && unzip -o samples/hja-open/hf01302/hf01302.zip -d samples/hja-open/hf01302/x
  2. Download run.json (157,583 bytes, sha256 f9d5efaa4e2bf2a5040de065d98bb7579875f2461a29c2990867cb46ce1c9bf7).
  3. Ask your assistant to replay it with NativeGIS, or call the tool directly:
gis_replay {"action": "replay",
            "file": "<absolute path to the run.json you downloaded>",
            "inputRoot": "<your data folder>",
            "outputRoot": "<a new, empty folder>"}

Paths in the run file are relative to the data folder (inputRoot), and outputs go under outputRoot, so nothing depends on where the original run lived.

Files

Limits

NativeGIS reproductions · every NativeGIS number on this page is read from the recorded run file it links to.