Ontologia

Ruisseau· 2 segments

Butler Creek

Crosses 3 administrative regions : Columbia, Elbert, Richmond

ruisseau

Total length

460km

Max discharge

1,2m³/s

Max Strahler

1

Segments matched

2

River geography3 admin regions · 0 communes

Parent watershed

hybas-70806979001397 km²

3 administrative regions crossed (GADM L2)

  • Richmond
    Georgia · United States
    21.0 km
    in this dpt
  • Elbert
    Georgia · United States
    3.9 km
    in this dpt
  • Columbia
    Georgia · United States
    0.0 km
    in this dpt

10 intersecting protected areas

1 more protected areas

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

Species present

679 distinct species · 7 847 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 41 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 Butler Creek : 29 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 103 interactions GloBI sur 4 types (connectance 12.6%, filtre Serrano α=0.2). 12 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
41
Interactions affichées
103
Connectance
0.126
Patrimoniales
2
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

460km

Max discharge

1,2m³/s

Max Strahler

1

Segments matched

2

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