Ontologia

Ruisseau· 2 segments

Hotnjica

Crosses 3 administrative regions : Lekenik, Petrinja, Pokupsko

ruisseau

Total length

25km

Max discharge

0,6m³/s

Max Strahler

2

Segments matched

2

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080541110502 km²

3 administrative regions crossed (GADM L2)

  • Lekenik
    Sisacko-Moslavacka · Croatia
    11.5 km
    in this dpt
  • Pokupsko
    Grad Zagreb · Croatia
    1.4 km
    in this dpt
  • Petrinja
    Sisacko-Moslavacka · Croatia
    1.0 km
    in this dpt

1 intersecting protected areas

  • Kupa

    IUCN Not Reported

    Site of Community Importance (Habitats Directive)

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

Species present

42 distinct species · 46 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 20 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 Hotnjica : 18 espèces reliées par 19 interactions GloBI sur 3 types (connectance 10.0%, filtre Serrano α=0.2). 2 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
20
Interactions affichées
19
Connectance
0.100
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

25km

Max discharge

0,6m³/s

Max Strahler

2

Segments matched

2

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