Ontologia

Ruisseau· 11 segments

Омуровска река

Crosses 4 administrative regions : Bratya Daskalovi, Brezovo, Parvomay, Sadovo

ruisseau

Total length

58km

Max discharge

1,7m³/s

Max Strahler

3

Segments matched

11

River geography4 admin regions · 0 communes

Parent watershed

hybas-2080600370328 km²

4 administrative regions crossed (GADM L2)

  • Bratya Daskalovi
    Stara Zagora · Bulgaria
    48.0 km
    in this dpt
  • Parvomay
    Plovdiv · Bulgaria
    2.9 km
    in this dpt
  • Brezovo
    Plovdiv · Bulgaria
    0.0 km
    in this dpt
  • Sadovo
    Plovdiv · Bulgaria
    0.0 km
    in this dpt

6 intersecting protected areas

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

Species present

15 distinct species · 19 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 5 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 Омуровска река : 4 espèces reliées par 4 interactions GloBI sur 2 types (connectance 40.0%, filtre Serrano α=0.2). 1 bulle taxonomique (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
5
Interactions affichées
4
Connectance
0.400
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

58km

Max discharge

1,7m³/s

Max Strahler

3

Segments matched

11

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