Ontologia

Ruisseau· 11 segments

Big Slough

Crosses 4 administrative regions : Pembina, Richland, Roberts, Wells

ruisseau

Total length

245km

Max discharge

0,5m³/s

Max Strahler

3

Segments matched

11

River geography4 admin regions · 0 communes

Parent watershed

hybas-7080391600875 km²

4 administrative regions crossed (GADM L2)

  • Roberts
    South Dakota · United States
    23.0 km
    in this dpt
  • Pembina
    North Dakota · United States
    17.4 km
    in this dpt
  • Wells
    North Dakota · United States
    7.7 km
    in this dpt
  • Richland
    North Dakota · United States
    4.6 km
    in this dpt

5 intersecting protected areas

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

Species present

56 distinct species · 1 163 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 26 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 Big Slough : 20 espèces reliées par 53 interactions GloBI sur 2 types (connectance 16.3%, filtre Serrano α=0.2). 6 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
26
Interactions affichées
53
Connectance
0.163
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

245km

Max discharge

0,5m³/s

Max Strahler

3

Segments matched

11

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