Ontologia

Ruisseau· 7 segments

L'Eygues

Crosses 3 administrative regions : Drôme, Hautes-Alpes, Vaucluse

ruisseau

Total length

85km

Max discharge

10,5m³/s

Max Strahler

3

Segments matched

7

River geography3 admin regions · 28 communes

Parent watershed

hybas-20805686702022 km²

3 administrative regions crossed (GADM L2)

  • Drôme
    Auvergne-Rhône-Alpes · France
    18.8 km
    in this dpt
  • Vaucluse
    Provence-Alpes-Côte d'Azur · France
    12.9 km
    in this dpt
  • Hautes-Alpes
    Provence-Alpes-Côte d'Azur · France
    7.2 km
    in this dpt
28 communes (L5)

4 intersecting protected areas

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

Species present

1 078 distinct species · 6 773 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 32 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 L'Eygues : 27 espèces + 5 bulles famille, 68 interactions GloBI documentées sur 5 types (connectance 13.7%, filtre Serrano α=0.2). Les 5 bulles regroupent des espèces visuellement absorbées par famille (≥3 espèces visibles).

Espèces affichées
32
Interactions affichées
68
Connectance
0.137
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

85km

Max discharge

10,5m³/s

Max Strahler

3

Segments matched

7

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