Ontologia

Ruisseau· 20 segments

Tallulah River

Crosses 3 administrative regions : Clay, Rabun, Towns

ruisseau

Total length

75km

Max discharge

11,8m³/s

Max Strahler

3

Segments matched

20

River geography3 admin regions · 0 communes

Parent watershed

hybas-70806723702513 km²

3 administrative regions crossed (GADM L2)

  • Rabun
    Georgia · United States
    45.7 km
    in this dpt
  • Towns
    Georgia · United States
    10.1 km
    in this dpt
  • Clay
    North Carolina · United States
    4.0 km
    in this dpt

2 intersecting protected areas

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

Species present

278 distinct species · 5 107 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 39 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 Tallulah River : 26 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 68 interactions GloBI sur 4 types (connectance 7.9%, filtre Serrano α=0.2). 16 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
42
Interactions affichées
68
Connectance
0.079
Patrimoniales
1
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

75km

Max discharge

11,8m³/s

Max Strahler

3

Segments matched

20

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