Ontologia

Ruisseau· 22 segments

Ashley River

Crosses 3 administrative regions : Berkeley, Charleston, Dorchester

ruisseau

Total length

93km

Max discharge

11,4m³/s

Max Strahler

3

Segments matched

22

River geography3 admin regions · 0 communes

Parent watershed

hybas-70800432702270 km²

3 administrative regions crossed (GADM L2)

  • Dorchester
    South Carolina · United States
    43.6 km
    in this dpt
  • Charleston
    South Carolina · United States
    28.3 km
    in this dpt
  • Berkeley
    South Carolina · United States
    20.5 km
    in this dpt

4 intersecting protected areas

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

Species present

570 distinct species · 39 618 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 38 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 Ashley River : 26 espèces reliées par 100 interactions GloBI sur 4 types (connectance 13.5%, filtre Serrano α=0.2). 13 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
39
Interactions affichées
100
Connectance
0.135
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

93km

Max discharge

11,4m³/s

Max Strahler

3

Segments matched

22

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