Ontologia

Ruisseau· 9 segments

Juniper Creek

Crosses 4 administrative regions : Bay, Calhoun, Marion, Talbot

ruisseau

Total length

577km

Max discharge

3,1m³/s

Max Strahler

2

Segments matched

9

River geography4 admin regions · 0 communes

Parent watershed

hybas-7080754520822 km²

4 administrative regions crossed (GADM L2)

  • Calhoun
    Florida · United States
    34.9 km
    in this dpt
  • Marion
    Georgia · United States
    10.1 km
    in this dpt
  • Bay
    Florida · United States
    4.2 km
    in this dpt
  • Talbot
    Georgia · United States
    0.4 km
    in this dpt

7 intersecting protected areas

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

Species present

127 distinct species · 750 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 Juniper Creek : 33 espèces reliées par 101 interactions GloBI sur 4 types (connectance 11.2%, filtre Serrano α=0.2). 10 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

577km

Max discharge

3,1m³/s

Max Strahler

2

Segments matched

9

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