Ontologia

Ruisseau

Big Muddy Creek

Crosses 4 administrative regions : Hoke, Moore, Richmond, Scotland

ruisseau

Total length

526km

Max discharge

0,6m³/s

Max Strahler

1

Segments matched

1

River geography4 admin regions · 0 communes

Parent watershed

hybas-70806722102040 km²

4 administrative regions crossed (GADM L2)

  • Scotland
    North Carolina · United States
    8.7 km
    in this dpt
  • Hoke
    North Carolina · United States
    0.9 km
    in this dpt
  • Richmond
    North Carolina · United States
    0.0 km
    in this dpt
  • Moore
    North Carolina · United States
    0.0 km
    in this dpt

1 intersecting protected areas

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

Species present

637 distinct species · 4 588 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 37 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 Muddy Creek : 27 espèces reliées par 78 interactions GloBI sur 4 types (connectance 10.0%, filtre Serrano α=0.2). 13 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
40
Interactions affichées
78
Connectance
0.100
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

526km

Max discharge

0,6m³/s

Max Strahler

1

Segments matched

1

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