Ontologia

Ruisseau· 16 segments

Long Cane Creek

Crosses 3 administrative regions : Abbeville, Greenwood, McCormick

ruisseau

Total length

121km

Max discharge

7,1m³/s

Max Strahler

3

Segments matched

16

River geography3 admin regions · 0 communes

Parent watershed

hybas-70806879602411 km²

3 administrative regions crossed (GADM L2)

  • Abbeville
    South Carolina · United States
    36.3 km
    in this dpt
  • McCormick
    South Carolina · United States
    16.9 km
    in this dpt
  • Greenwood
    South Carolina · United States
    4.7 km
    in this dpt

1 intersecting protected areas

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

Species present

160 distinct species · 326 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 53 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 Long Cane Creek : 39 espèces reliées par 114 interactions GloBI sur 5 types (connectance 8.3%, filtre Serrano α=0.2). 14 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
53
Interactions affichées
114
Connectance
0.083
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

121km

Max discharge

7,1m³/s

Max Strahler

3

Segments matched

16

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