Ontologia

Rivière· 5 segments

Tržiška Bistrica

Crosses 4 administrative regions : Kranj, Naklo, Radovljica, Tržič

rivière

Total length

18km

Max discharge

33m³/s

Max Strahler

5

Segments matched

5

River geography4 admin regions · 0 communes

Parent watershed

hybas-2080525670420 km²

4 administrative regions crossed (GADM L2)

  • Tržič
    Gorenjska · Slovenia
    15.7 km
    in this dpt
  • Naklo
    Gorenjska · Slovenia
    6.3 km
    in this dpt
  • Kranj
    Gorenjska · Slovenia
    0.0 km
    in this dpt
  • Radovljica
    Gorenjska · Slovenia
    0.0 km
    in this dpt

14 intersecting protected areas

5 more protected areas

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

Species present

330 distinct species · 578 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 47 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 Tržiška Bistrica : 41 espèces reliées par 82 interactions GloBI sur 5 types (connectance 7.6%, filtre Serrano α=0.2). 6 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
47
Interactions affichées
82
Connectance
0.076
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

18km

Max discharge

33,0m³/s

Max Strahler

5

Segments matched

5

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