Ontologia

Rivière· 8 segments

Red Oak Creek

Crosses 2 administrative regions : Meriwether, Pike

rivière

Total length

107km

Max discharge

31,7m³/s

Max Strahler

4

Segments matched

8

River geography2 admin regions · 0 communes

Parent watershed

hybas-70807068202234 km²

2 administrative regions crossed (GADM L2)

  • Meriwether
    Georgia · United States
    26.9 km
    in this dpt
  • Pike
    Georgia · United States
    1.1 km
    in this dpt

2 intersecting protected areas

  • 2013010

    IUCN Not Assigned

    Conservation Easement

  • 2015014

    IUCN Not Assigned

    Conservation Easement

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

Species present

35 distinct species · 46 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 16 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 Red Oak Creek : 14 espèces reliées par 14 interactions GloBI sur 2 types (connectance 11.7%, filtre Serrano α=0.2). 2 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
16
Interactions affichées
14
Connectance
0.117
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

107km

Max discharge

31,7m³/s

Max Strahler

4

Segments matched

8

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