Ontologia

Rivière· 17 segments

Río Chanza / Rio Chança

Crosses 3 administrative regions : Huelva, Mértola, Serpa

rivière

Total length

66km

Max discharge

15,2m³/s

Max Strahler

4

Segments matched

17

River geography3 admin regions · 0 communes

Parent watershed

hybas-20806957802137 km²

3 administrative regions crossed (GADM L2)

  • Serpa
    Beja · Portugal
    21.9 km
    in this dpt
  • Huelva
    Andalucía · Spain
    21.9 km
    in this dpt
  • Mértola
    Beja · Portugal
    12.5 km
    in this dpt

8 intersecting protected areas

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

Species present

186 distinct species · 1 433 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 44 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 Chanza / Rio Chança : 34 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 79 interactions GloBI sur 4 types (connectance 8.4%, filtre Serrano α=0.2). 10 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
44
Interactions affichées
79
Connectance
0.084
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

66km

Max discharge

15,2m³/s

Max Strahler

4

Segments matched

17

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