Ontologia

Rivière· 3 segments

Terrapin Creek

Crosses 4 administrative regions : Catawba, Iredell, Newberry, Saluda

rivière

Total length

150km

Max discharge

66m³/s

Max Strahler

5

Segments matched

3

River geography4 admin regions · 0 communes

Parent watershed

hybas-7080677810221 km²

4 administrative regions crossed (GADM L2)

  • Catawba
    North Carolina · United States
    4.6 km
    in this dpt
  • Saluda
    South Carolina · United States
    4.3 km
    in this dpt
  • Newberry
    South Carolina · United States
    2.6 km
    in this dpt
  • Iredell
    North Carolina · United States
    0.0 km
    in this dpt

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

Species present

130 distinct species · 535 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 40 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 Terrapin Creek : 32 espèces reliées par 74 interactions GloBI sur 4 types (connectance 9.0%, filtre Serrano α=0.2). 9 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
41
Interactions affichées
74
Connectance
0.090
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

150km

Max discharge

66,0m³/s

Max Strahler

5

Segments matched

3

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