Rivière· 5 segments
Heron Lake Outlet
Crosses 2 administrative regions : Cottonwood, Jackson
Total length
27km
Max discharge
6,5m³/s
Max Strahler
4
Segments matched
5
River geography2 admin regions · 0 communes
2 administrative regions crossed (GADM L2)
- JacksonMinnesota · United States23.2 kmin this dpt
- CottonwoodMinnesota · United States4.9 kmin this dpt
12 intersecting protected areas
Martin County
IUCN VWaterfowl Production Area
Easement
Reserve Program
Pope County
IUCN VWaterfowl Production Area
Permanent
IUCN VWetland Preserve
Reserve Program
Jackson County
IUCN VWaterfowl Production Area
Heron Lake
IUCN VState Wildlife Management Area
Jackson County
IUCN VWaterfowl Production Area
3 more protected areassorted by area
Valleau
IUCN VState Wildlife Management Area
Heron Meadows
IUCN VState Wildlife Management Area
Pats Pasture
IUCN VState Wildlife Management Area
1 page = 1 named river (aggregation of 5 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
430 distinct species · 3 784 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 28 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 Heron Lake Outlet : 20 espèces reliées par 81 interactions GloBI sur 4 types (connectance 21.4%, filtre Serrano α=0.2). 8 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
27km
Max discharge
6,5m³/s
Max Strahler
4
Segments matched
5
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.