Ontologia

Rivière· 2 segments

Планшица

Crosses 2 administrative regions : Samokov, Stolichna

rivière

Total length

14km

Max discharge

9,6m³/s

Max Strahler

4

Segments matched

2

River geography2 admin regions · 0 communes

Parent watershed

hybas-2080590540594 km²

2 administrative regions crossed (GADM L2)

  • Stolichna
    Grad Sofiya · Bulgaria
    13.0 km
    in this dpt
  • Samokov
    Sofia · Bulgaria
    1.7 km
    in this dpt

2 intersecting protected areas

  • Plana

    IUCN Not Reported

    Site of Community Importance (Habitats Directive)

  • Urvich

    IUCN III

    Natural Monument

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

Species present

70 distinct species · 185 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 Планшица : 31 espèces reliées par 80 interactions GloBI sur 5 types (connectance 13.4%, filtre Serrano α=0.2). 4 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

14km

Max discharge

9,6m³/s

Max Strahler

4

Segments matched

2

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