Ontologia

Rivière· 50 segments

Río Alberche

Crosses 3 administrative regions : Madrid, Toledo, Ávila

rivière

Total length

199km

Max discharge

19,1m³/s

Max Strahler

4

Segments matched

50

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080641950714 km²

3 administrative regions crossed (GADM L2)

  • Ávila
    Castilla y León · Spain
    83.2 km
    in this dpt
  • Toledo
    Castilla-La Mancha · Spain
    81.9 km
    in this dpt
  • Madrid
    Comunidad de Madrid · Spain
    33.0 km
    in this dpt

15 intersecting protected areas

6 more protected areas

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

Species present

398 distinct species · 1 323 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 49 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 Río Alberche : 38 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 99 interactions GloBI sur 6 types (connectance 8.4%, filtre Serrano α=0.2). 11 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
49
Interactions affichées
99
Connectance
0.084
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

199km

Max discharge

19,1m³/s

Max Strahler

4

Segments matched

50

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