Ontologia

Ruisseau· 13 segments

Brasstown Creek

Crosses 4 administrative regions : Cherokee, Clay, Towns, Union

ruisseau

Total length

59km

Max discharge

6,4m³/s

Max Strahler

3

Segments matched

13

River geography4 admin regions · 0 communes

Parent watershed

hybas-70806579701088 km²

4 administrative regions crossed (GADM L2)

  • Clay
    North Carolina · United States
    14.9 km
    in this dpt
  • Towns
    Georgia · United States
    8.2 km
    in this dpt
  • Union
    Georgia · United States
    2.8 km
    in this dpt
  • Cherokee
    North Carolina · United States
    0.0 km
    in this dpt

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

Species present

262 distinct species · 2 501 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 42 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 Brasstown Creek : 33 espèces reliées par 81 interactions GloBI sur 4 types (connectance 9.0%, filtre Serrano α=0.2). 10 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
43
Interactions affichées
81
Connectance
0.090
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

59km

Max discharge

6,4m³/s

Max Strahler

3

Segments matched

13

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