Ontologia

Rivière· 17 segments

Блатница

Crosses 3 administrative regions : Nova Zagora, Radnevo, Stara Zagora

rivière

Total length

32km

Max discharge

6,7m³/s

Max Strahler

4

Segments matched

17

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080597540652 km²

3 administrative regions crossed (GADM L2)

3 intersecting protected areas

  • Reka Blatnitsa

    IUCN Not Reported

    Site of Community Importance (Habitats Directive)

  • Reka Sazliyka

    IUCN Not Reported

    Site of Community Importance (Habitats Directive)

  • Protected Site

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

Species present

77 distinct species · 216 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 dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 43 interactions GloBI sur 3 types (connectance 11.4%, filtre Serrano α=0.2). 8 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
28
Interactions affichées
43
Connectance
0.114
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

32km

Max discharge

6,7m³/s

Max Strahler

4

Segments matched

17

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