Ontologia

Ruisseau· 4 segments

Río Arandilla

Crosses 1 administrative regions : Guadalajara

ruisseau

Total length

63km

Max discharge

2,4m³/s

Max Strahler

3

Segments matched

4

River geography1 admin regions · 0 communes

Parent watershed

hybas-20806276401301 km²

1 administrative regions crossed (GADM L2)

  • Guadalajara
    Castilla-La Mancha · Spain
    17.4 km
    in this dpt

3 intersecting protected areas

  • Alto Tajo

    IUCN Not Reported

    Special Protection Area (Birds Directive)

  • Alto Tajo

    IUCN Not Reported

    Special Areas of Conservation (Habitats Directive)

  • Alto Tajo

    IUCN VI

    Natural Park

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

Species present

610 distinct species · 1 068 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 35 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 Arandilla : 28 espèces reliées par 61 interactions GloBI sur 5 types (connectance 10.3%, filtre Serrano α=0.2). 7 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
35
Interactions affichées
61
Connectance
0.102
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

63km

Max discharge

2,4m³/s

Max Strahler

3

Segments matched

4

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