Ontologia

Ruisseau· 11 segments

Río Tozo

Crosses 1 administrative regions : Cáceres

ruisseau

Total length

80km

Max discharge

2,2m³/s

Max Strahler

3

Segments matched

11

River geography1 admin regions · 0 communes

Parent watershed

hybas-20806491303159 km²

1 administrative regions crossed (GADM L2)

  • Cáceres
    Extremadura · Spain
    66.1 km
    in this dpt

2 intersecting protected areas

  • Riberos del Almonte

    IUCN Not Reported

    Special Protection Area (Birds Directive)

  • Río Almonte

    IUCN Not Reported

    Special Areas of Conservation (Habitats Directive)

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

Species present

347 distinct species · 17 576 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 25 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 Tozo : 19 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 38 interactions GloBI sur 3 types (connectance 12.7%, filtre Serrano α=0.2). 6 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
25
Interactions affichées
38
Connectance
0.127
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

80km

Max discharge

2,2m³/s

Max Strahler

3

Segments matched

11

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