Ontologia

Ruisseau· 15 segments

Thompson Creek

Crosses 3 administrative regions : Anson, Chesterfield, Marlboro

ruisseau

Total length

1 007km

Max discharge

11,3m³/s

Max Strahler

3

Segments matched

15

River geography3 admin regions · 0 communes

Parent watershed

hybas-7080667240911 km²

3 administrative regions crossed (GADM L2)

  • Chesterfield
    South Carolina · United States
    58.0 km
    in this dpt
  • Anson
    North Carolina · United States
    3.1 km
    in this dpt
  • Marlboro
    South Carolina · United States
    0.2 km
    in this dpt

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

Species present

259 distinct species · 2 055 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 44 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 Thompson Creek : 34 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 100 interactions GloBI sur 5 types (connectance 10.1%, filtre Serrano α=0.2). 11 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

1 007km

Max discharge

11,3m³/s

Max Strahler

3

Segments matched

15

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