Ontologia

Ruisseau· 5 segments

Pen Branch

Crosses 3 administrative regions : Aiken, Barnwell, Burke

ruisseau

Total length

38km

Max discharge

2m³/s

Max Strahler

2

Segments matched

5

River geography3 admin regions · 0 communes

Parent watershed

hybas-7080701340612 km²

3 administrative regions crossed (GADM L2)

  • Barnwell
    South Carolina · United States
    39.1 km
    in this dpt
  • Aiken
    South Carolina · United States
    5.1 km
    in this dpt
  • Burke
    Georgia · United States
    0.0 km
    in this dpt

1 intersecting protected areas

  • Yuchi

    IUCN V

    Wildlife Management Area

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

Species present

289 distinct species · 785 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

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

Espèces affichées
50
Interactions affichées
136
Connectance
0.111
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

38km

Max discharge

2,0m³/s

Max Strahler

2

Segments matched

5

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