Ontologia

Ruisseau· 3 segments

Močilnik

Crosses 3 administrative regions : Divaca, Postojna, Vipava

ruisseau

Total length

17km

Max discharge

0,8m³/s

Max Strahler

1

Segments matched

3

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080532250592 km²

3 administrative regions crossed (GADM L2)

  • Vipava
    Goriška · Slovenia
    7.8 km
    in this dpt
  • Divaca
    Obalno-kraška · Slovenia
    1.0 km
    in this dpt
  • Postojna
    Notranjsko-kraška · Slovenia
    0.0 km
    in this dpt

11 intersecting protected areas

2 more protected areas

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

Species present

400 distinct species · 1 195 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 43 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 Močilnik : 29 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 116 interactions GloBI sur 6 types (connectance 12.3%, filtre Serrano α=0.2). 15 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
44
Interactions affichées
116
Connectance
0.123
Patrimoniales
1
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

17km

Max discharge

0,8m³/s

Max Strahler

1

Segments matched

3

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