Ontologia

Ruisseau· 3 segments

Улудере

Crosses 3 administrative regions : Chernoochene, Mineralni Bani, Parvomay

ruisseau

Total length

7km

Max discharge

0,5m³/s

Max Strahler

2

Segments matched

3

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080604180968 km²

3 administrative regions crossed (GADM L2)

4 intersecting protected areas

  • Rodopi - Sredni

    IUCN Not Reported

    Special Areas of Conservation (Habitats Directive)

  • Zhenda

    IUCN Not Assigned

    State Game Husbandries

  • Boraka

    IUCN IV

    Managed Reserve

  • Dikilitash

    IUCN III

    Natural Monument

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

Species present

92 distinct species · 109 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 26 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 Улудере : 20 espèces reliées par 57 interactions GloBI sur 2 types (connectance 17.5%, filtre Serrano α=0.2). 6 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
26
Interactions affichées
57
Connectance
0.175
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

7km

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.