Ontologia

Rivière· 3 segments

Arroyo de las Higueras

Crosses 3 administrative regions : Cáceres, Madrid, Toledo

rivière

Total length

17km

Max discharge

170,4m³/s

Max Strahler

6

Segments matched

3

River geography3 admin regions · 0 communes

Parent watershed

hybas-20806446202531 km²

3 administrative regions crossed (GADM L2)

  • Toledo
    Castilla-La Mancha · Spain
    25.7 km
    in this dpt
  • Cáceres
    Extremadura · Spain
    9.8 km
    in this dpt
  • Madrid
    Comunidad de Madrid · Spain
    0.3 km
    in this dpt

9 intersecting protected areas

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

Species present

216 distinct species · 1 334 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 43 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 Arroyo de las Higueras : 34 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 70 interactions GloBI sur 3 types (connectance 7.8%, filtre Serrano α=0.2). 9 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
43
Interactions affichées
70
Connectance
0.077
Patrimoniales
2
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

17km

Max discharge

170,4m³/s

Max Strahler

6

Segments matched

3

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