Ruisseau· 53 segments
South Fork Edisto River
Crosses 6 administrative regions : Aiken, Bamberg, Barnwell, Edgefield, Orangeburg +1
Total length
171km
Max discharge
27,2m³/s
Max Strahler
3
Segments matched
53
River geography6 admin regions · 0 communes
6 administrative regions crossed (GADM L2)
- AikenSouth Carolina · United States58.0 kmin this dpt
- OrangeburgSouth Carolina · United States38.1 kmin this dpt
- BambergSouth Carolina · United States33.4 kmin this dpt
- BarnwellSouth Carolina · United States18.8 kmin this dpt
- EdgefieldSouth Carolina · United States13.4 kmin this dpt
- SaludaSouth Carolina · United States0.7 kmin this dpt
9 intersecting protected areas
Reserve Program
Reserve Program
Wildlife Management Area
Aiken
IUCN IIIState Park
Reserve Program
Us-Sc-10-5
IUCN Not AssignedConservation Easement
Reserve Program
Conservation Easement
Conservation Easement
1 page = 1 named river (aggregation of 53 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
65 distinct species · 69 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 40 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).
Indicateurs du tissu écologique
Tissu écologique de South Fork Edisto River : 36 espèces reliées par 41 interactions GloBI sur 4 types (connectance 5.3%, filtre Serrano α=0.2). 4 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
171km
Max discharge
27,2m³/s
Max Strahler
3
Segments matched
53
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.