Ontologia

Rivière· 17 segments

Big Satilla Creek

Crosses 5 administrative regions : Appling, Bacon, Jeff Davis, Pierce, Wayne

rivière

Total length

79km

Max discharge

18,6m³/s

Max Strahler

4

Segments matched

17

River geography5 admin regions · 0 communes

Parent watershed

hybas-70807363602054 km²

5 administrative regions crossed (GADM L2)

  • Appling
    Georgia · United States
    42.8 km
    in this dpt
  • Jeff Davis
    Georgia · United States
    19.7 km
    in this dpt
  • Bacon
    Georgia · United States
    11.8 km
    in this dpt
  • Pierce
    Georgia · United States
    8.6 km
    in this dpt
  • Wayne
    Georgia · United States
    4.7 km
    in this dpt

1 intersecting protected areas

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

Species present

30 distinct species · 31 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 23 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 Big Satilla Creek : 23 espèces reliées par 18 interactions GloBI sur 4 types (connectance 7.1%, filtre Serrano α=0.2).

Espèces affichées
23
Interactions affichées
18
Connectance
0.071
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

79km

Max discharge

18,6m³/s

Max Strahler

4

Segments matched

17

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