Ontologia

Ruisseau

Estômbar

Crosses 3 administrative regions : Lagoa, Portimão, Silves

ruisseau

Total length

1km

Max discharge

0,2m³/s

Max Strahler

1

Segments matched

1

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080018550970 km²

3 administrative regions crossed (GADM L2)

  • Lagoa
    Faro · Portugal
    3.5 km
    in this dpt
  • Portimão
    Faro · Portugal
    0.0 km
    in this dpt
  • Silves
    Faro · Portugal
    0.0 km
    in this dpt

1 intersecting protected areas

  • Arade / Odelouca

    IUCN Not Reported

    Site of Community Importance (Habitats Directive)

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

Species present

1 696 distinct species · 49 506 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 28 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 Estômbar : 20 espèces reliées par 52 interactions GloBI sur 2 types (connectance 13.8%, filtre Serrano α=0.2). 8 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
28
Interactions affichées
52
Connectance
0.138
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)

Total length

1km

Max discharge

0,2m³/s

Max Strahler

1

Segments matched

1

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