Ontologia

Ruisseau· 11 segments

Pivka

Crosses 3 administrative regions : Ilirska Bistrica, Pivka, Postojna

Endorheicruisseau

Total length

44km

Max discharge

3,6m³/s

Max Strahler

3

Segments matched

11

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080094400484 km²

3 administrative regions crossed (GADM L2)

  • Postojna
    Notranjsko-kraška · Slovenia
    13.3 km
    in this dpt
  • Pivka
    Notranjsko-kraška · Slovenia
    12.8 km
    in this dpt
  • Ilirska Bistrica
    Notranjsko-kraška · Slovenia
    5.3 km
    in this dpt

11 intersecting protected areas

2 more protected areas

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

Species present

580 distinct species · 2 176 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 38 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 Pivka : 25 espèces reliées par 120 interactions GloBI sur 6 types (connectance 14.6%, filtre Serrano α=0.2). 16 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
41
Interactions affichées
120
Connectance
0.146
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

44km

Max discharge

3,6m³/s

Max Strahler

3

Segments matched

11

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