Ontologia

Ruisseau· 19 segments

Sandy Creek

Crosses 4 administrative regions : Franklin, Nash, Vance, Warren

ruisseau

Total length

8 225km

Max discharge

5,8m³/s

Max Strahler

3

Segments matched

19

River geography4 admin regions · 0 communes

Parent watershed

hybas-7080638390703 km²

4 administrative regions crossed (GADM L2)

  • Franklin
    North Carolina · United States
    32.9 km
    in this dpt
  • Nash
    North Carolina · United States
    18.4 km
    in this dpt
  • Vance
    North Carolina · United States
    11.9 km
    in this dpt
  • Warren
    North Carolina · United States
    4.3 km
    in this dpt

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

Species present

79 distinct species · 118 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).

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

Indicateurs du tissu écologique

Tissu écologique de Sandy Creek : 21 espèces reliées par 49 interactions GloBI sur 3 types (connectance 12.1%, filtre Serrano α=0.2). 8 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
29
Interactions affichées
49
Connectance
0.121
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

8 225km

Max discharge

5,8m³/s

Max Strahler

3

Segments matched

19

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