Ontologia

Rivière· 12 segments

Arroyo Grande

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

rivière

Total length

1 573km

Max discharge

12,3m³/s

Max Strahler

4

Segments matched

12

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080642070216 km²

3 administrative regions crossed (GADM L2)

  • Toledo
    Castilla-La Mancha · Spain
    35.7 km
    in this dpt
  • Cáceres
    Extremadura · Spain
    19.6 km
    in this dpt
  • Madrid
    Comunidad de Madrid · Spain
    4.1 km
    in this dpt

9 intersecting protected areas

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

Species present

155 distinct species · 342 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 29 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 Grande : 20 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 49 interactions GloBI sur 2 types (connectance 11.3%, filtre Serrano α=0.2). 10 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

1 573km

Max discharge

12,3m³/s

Max Strahler

4

Segments matched

12

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