Ontologia

Ruisseau· 3 segments

Абланица

Crosses 1 administrative regions : Velingrad

ruisseau

Total length

13km

Max discharge

2,2m³/s

Max Strahler

3

Segments matched

3

River geography1 admin regions · 0 communes

Parent watershed

hybas-20805991102229 km²

1 administrative regions crossed (GADM L2)

  • Velingrad
    Pazardzhik · Bulgaria
    11.4 km
    in this dpt

3 intersecting protected areas

  • Rodopi - Zapadni

    IUCN Not Reported

    Special Areas of Conservation (Habitats Directive)

  • Zapadni Rodopi

    IUCN Not Reported

    Special Protection Area (Birds Directive)

  • Chepino

    IUCN Not Assigned

    State Game Husbandries

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

Species present

91 distinct species · 132 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 35 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 Абланица : 30 espèces reliées par 51 interactions GloBI sur 4 types (connectance 8.6%, filtre Serrano α=0.2). 5 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
35
Interactions affichées
51
Connectance
0.086
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

13km

Max discharge

2,2m³/s

Max Strahler

3

Segments matched

3

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