Ontologia

Rivière

Regato de los Remoliños

⚠ Partial coverage : only 1 named segment matched so far. The real rivière extends much further (Strahler order 6 indicates a major river). Cross-source ingest in progress — values below reflect only the matched segment.

Crosses 1 administrative regions : Cáceres

rivière

Max discharge

236,9m³/s

Max Strahler

6

Segments matched

1

River geography1 admin regions · 0 communes

Parent watershed

hybas-2080650300254 km²

1 administrative regions crossed (GADM L2)

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

6 intersecting protected areas

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

Species present

502 distinct species · 4 437 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 41 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 Regato de los Remoliños : 30 espèces reliées par 94 interactions GloBI sur 5 types (connectance 10.9%, filtre Serrano α=0.2). 12 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
42
Interactions affichées
94
Connectance
0.109
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)

Matched len.

5,0km

Max discharge

236,9m³/s

Max Strahler

6

Segments matched

1

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