Ontologia

Rivière· 48 segments

Río Henares

Crosses 3 administrative regions : Guadalajara, Madrid, Soria

rivière

Total length

172km

Max discharge

14,5m³/s

Max Strahler

4

Segments matched

48

River geography3 admin regions · 0 communes

Parent watershed

hybas-20806349501476 km²

3 administrative regions crossed (GADM L2)

  • Guadalajara
    Castilla-La Mancha · Spain
    152.7 km
    in this dpt
  • Madrid
    Comunidad de Madrid · Spain
    27.7 km
    in this dpt
  • Soria
    Castilla y León · Spain
    0.1 km
    in this dpt

9 intersecting protected areas

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

Species present

354 distinct species · 1 297 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 Río Henares : 24 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 70 interactions GloBI sur 4 types (connectance 14.1%, filtre Serrano α=0.2). 8 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

172km

Max discharge

14,5m³/s

Max Strahler

4

Segments matched

48

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