Ontologia

Ruisseau· 26 segments

Pipestone Creek

Crosses 4 administrative regions : Minnehaha, Moody, Pipestone, Rock

ruisseau

Total length

758km

Max discharge

2,7m³/s

Max Strahler

3

Segments matched

26

River geography4 admin regions · 0 communes

Parent watershed

hybas-70804522901668 km²

4 administrative regions crossed (GADM L2)

  • Pipestone
    Minnesota · United States
    50.9 km
    in this dpt
  • Minnehaha
    South Dakota · United States
    37.2 km
    in this dpt
  • Moody
    South Dakota · United States
    35.5 km
    in this dpt
  • Rock
    Minnesota · United States
    0.8 km
    in this dpt

4 intersecting protected areas

1 page = 1 named river (aggregation of 26 HydroRIVERS v10 segments). Spatial join cached after first hit.

Species present

21 distinct species · 29 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 12 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).

RègnesAnimalPlanteChampignonBacterie
RelationsPredationParasitismeSymbiosePollinisation
StatutEn dangerVulnérableProtégéeEndémique

Indicateurs du tissu écologique

Tissu écologique de Pipestone Creek : 11 espèces reliées par 11 interactions GloBI sur 3 types (connectance 16.7%, filtre Serrano α=0.2). 1 bulle taxonomique (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
12
Interactions affichées
11
Connectance
0.167
Patrimoniales
0
Plus dense que (national)0 %(top 100%)

Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).

Hydrology (HydroRIVERS v10)

Total length

758km

Max discharge

2,7m³/s

Max Strahler

3

Segments matched

26

HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.