Ontologia

Ruisseau· 5 segments

Richland Creek

Crosses 3 administrative regions : Greenville, Saluda, Spartanburg

ruisseau

Total length

1 099km

Max discharge

4m³/s

Max Strahler

3

Segments matched

5

River geography3 admin regions · 0 communes

Parent watershed

hybas-7080679600873 km²

3 administrative regions crossed (GADM L2)

  • Saluda
    South Carolina · United States
    14.8 km
    in this dpt
  • Spartanburg
    South Carolina · United States
    4.7 km
    in this dpt
  • Greenville
    South Carolina · United States
    3.9 km
    in this dpt

3 intersecting protected areas

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

Species present

47 distinct species · 69 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 24 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 Richland Creek : 20 espèces reliées par 28 interactions GloBI sur 3 types (connectance 9.3%, filtre Serrano α=0.2). 5 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
25
Interactions affichées
28
Connectance
0.093
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

1 099km

Max discharge

4,0m³/s

Max Strahler

3

Segments matched

5

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