Ontologia

Rivière· 37 segments

Sepulga River

Crosses 4 administrative regions : Butler, Conecuh, Covington, Escambia

rivière

Total length

100km

Max discharge

109,2m³/s

Max Strahler

5

Segments matched

37

River geography4 admin regions · 0 communes

Parent watershed

hybas-70807381002707 km²

4 administrative regions crossed (GADM L2)

  • Conecuh
    Alabama · United States
    103.3 km
    in this dpt
  • Escambia
    Alabama · United States
    18.2 km
    in this dpt
  • Butler
    Alabama · United States
    4.5 km
    in this dpt
  • Covington
    Alabama · United States
    4.3 km
    in this dpt

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

Species present

55 distinct species · 66 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 28 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 Sepulga River : 26 espèces reliées par 23 interactions GloBI sur 4 types (connectance 6.1%, filtre Serrano α=0.2). 2 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

100km

Max discharge

109,2m³/s

Max Strahler

5

Segments matched

37

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