Ontologia

Ruisseau· 3 segments

Arroyo de la Nava

Crosses 3 administrative regions : Badajoz, Barrancos, Toledo

ruisseau

Total length

124km

Max discharge

0,5m³/s

Max Strahler

2

Segments matched

3

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080653370443 km²

3 administrative regions crossed (GADM L2)

  • Toledo
    Castilla-La Mancha · Spain
    31.6 km
    in this dpt
  • Badajoz
    Extremadura · Spain
    2.2 km
    in this dpt
  • Barrancos
    Beja · Portugal
    0.0 km
    in this dpt

5 intersecting protected areas

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

Species present

353 distinct species · 6 813 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 30 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 la Nava : 22 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 50 interactions GloBI sur 2 types (connectance 10.1%, filtre Serrano α=0.2). 10 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

124km

Max discharge

0,5m³/s

Max Strahler

2

Segments matched

3

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