Ontologia

Fleuve· 8 segments

Bear Den Creek

Crosses 4 administrative regions : Dunn, McKenzie, Mountrail, Stone

fleuve

Total length

30km

Max discharge

771,8m³/s

Max Strahler

8

Segments matched

8

River geography4 admin regions · 0 communes

Parent watershed

hybas-70803374101035 km²

4 administrative regions crossed (GADM L2)

  • McKenzie
    North Dakota · United States
    17.0 km
    in this dpt
  • Mountrail
    North Dakota · United States
    3.1 km
    in this dpt
  • Stone
    Missouri · United States
    2.0 km
    in this dpt
  • Dunn
    North Dakota · United States
    1.6 km
    in this dpt

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

Species present

84 distinct species · 314 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 29 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 Bear Den Creek : 22 espèces reliées par 60 interactions GloBI sur 3 types (connectance 13.8%, filtre Serrano α=0.2). 8 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
30
Interactions affichées
60
Connectance
0.138
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

30km

Max discharge

771,8m³/s

Max Strahler

8

Segments matched

8

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