Rivière· 11 segments
Coffee Creek
Crosses 11 administrative regions : Bureau, Clark, Cuming, Delaware, Dodge +6
Total length
371km
Max discharge
52,9m³/s
Max Strahler
5
Segments matched
11
River geography11 admin regions · 0 communes
11 administrative regions crossed (GADM L2)
- OklahomaOklahoma · United States13.1 kmin this dpt
- JohnsonKansas · United States8.2 kmin this dpt
- PutnamIllinois · United States5.3 kmin this dpt
- CumingNebraska · United States3.8 kmin this dpt
- LincolnWisconsin · United States3.2 kmin this dpt
- HutchinsonSouth Dakota · United States3.1 kmin this dpt
- DubuqueIowa · United States1.9 kmin this dpt
- ClarkArkansas · United States1.3 kmin this dpt
- DodgeNebraska · United States1.3 kmin this dpt
- DelawareIowa · United States0.0 kmin this dpt
- BureauIllinois · United States0.0 kmin this dpt
2 intersecting protected areas
Reserve Program
Reserve Program
1 page = 1 named river (aggregation of 11 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
176 distinct species · 710 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 44 species (selected proportionally per kingdom among those with at least one documented interaction here) to keep the graph readable. Hover for details, click to explore the full ecosystem of a species.
ℹ️ The territory contains many more species than displayed and all their documented interactions: the graph is intentionally the structural skeleton (top-N species by composite local score, edges filtered by Serrano 2009 disparity filter α=0.2).
Indicateurs du tissu écologique
Tissu écologique de Coffee Creek : 33 espèces reliées par 117 interactions GloBI sur 5 types (connectance 11.8%, filtre Serrano α=0.2). 12 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
371km
Max discharge
52,9m³/s
Max Strahler
5
Segments matched
11
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.