Ruisseau· 11 segments
Outlet Creek
Crosses 2 administrative regions : Buena Vista, Pope
Total length
222km
Max discharge
2m³/s
Max Strahler
3
Segments matched
11
River geography2 admin regions · 0 communes
2 administrative regions crossed (GADM L2)
- PopeMinnesota · United States52.3 kmin this dpt
- Buena VistaIowa · United States15.0 kmin this dpt
14 intersecting protected areas
Martin County
IUCN VWaterfowl Production Area
Easement
Big Stone County
IUCN VWaterfowl Production Area
Pope County
IUCN VIWaterfowl Production Area
Pope County
IUCN VWaterfowl Production Area
National Wildlife Refuge
Permanent
IUCN VWetland Preserve
Pope County
IUCN VWaterfowl Production Area
Raccoon River Heritage
IUCN VWildlife Corridor
5 more protected areassorted by area
Pope County
IUCN VWaterfowl Production Area
Reserve Program
Star Lake
IUCN VState Wildlife Management Area
Strandness Prairie Fee
IUCN VPrivate Conservation Land
Lake
1 page = 1 named river (aggregation of 11 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
61 distinct species · 281 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 35 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 Outlet Creek : 28 espèces reliées par 70 interactions GloBI sur 4 types (connectance 11.8%, filtre Serrano α=0.2). 7 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
222km
Max discharge
2,0m³/s
Max Strahler
3
Segments matched
11
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.