Ontologia

Rivière· 39 segments

Patsaliga Creek

Crosses 3 administrative regions : Butler, Covington, Crenshaw

rivière

Total length

93km

Max discharge

54,9m³/s

Max Strahler

4

Segments matched

39

River geography3 admin regions · 0 communes

Parent watershed

hybas-70807349101527 km²

3 administrative regions crossed (GADM L2)

  • Crenshaw
    Alabama · United States
    74.7 km
    in this dpt
  • Covington
    Alabama · United States
    44.1 km
    in this dpt
  • Butler
    Alabama · United States
    2.0 km
    in this dpt

1 intersecting protected areas

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

Species present

121 distinct species · 157 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 39 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 Patsaliga Creek : 32 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 47 interactions GloBI sur 4 types (connectance 6.3%, filtre Serrano α=0.2). 7 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
39
Interactions affichées
47
Connectance
0.063
Patrimoniales
1
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

93km

Max discharge

54,9m³/s

Max Strahler

4

Segments matched

39

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