Ontologia

Ruisseau

Bad Creek

Crosses 4 administrative regions : Jackson, Macon, Oconee, Rabun

ruisseau

Total length

110km

Max discharge

0,1m³/s

Max Strahler

1

Segments matched

1

River geography4 admin regions · 0 communes

Parent watershed

hybas-70806723702513 km²

4 administrative regions crossed (GADM L2)

  • Oconee
    South Carolina · United States
    0.4 km
    in this dpt
  • Rabun
    Georgia · United States
    0.2 km
    in this dpt
  • Jackson
    North Carolina · United States
    0.0 km
    in this dpt
  • Macon
    North Carolina · United States
    0.0 km
    in this dpt

4 intersecting protected areas

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

Species present

969 distinct species · 3 362 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 42 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 Bad Creek : 34 espèces reliées par 53 interactions GloBI sur 3 types (connectance 5.9%, filtre Serrano α=0.2). 9 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

110km

Max discharge

0,1m³/s

Max Strahler

1

Segments matched

1

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