Ontologia

Ruisseau· 4 segments

Velika Trepča

Crosses 4 administrative regions : Glina, Gvozd, Pokupsko, Topusko

ruisseau

Total length

33km

Max discharge

2,2m³/s

Max Strahler

2

Segments matched

4

River geography4 admin regions · 0 communes

Parent watershed

hybas-20805423701503 km²

4 administrative regions crossed (GADM L2)

  • Gvozd
    Sisacko-Moslavacka · Croatia
    24.1 km
    in this dpt
  • Glina
    Sisacko-Moslavacka · Croatia
    2.1 km
    in this dpt
  • Pokupsko
    Grad Zagreb · Croatia
    0.0 km
    in this dpt
  • Topusko
    Sisacko-Moslavacka · Croatia
    0.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 4 HydroRIVERS v10 segments). Spatial join cached after first hit.

Species present

5 distinct species · 5 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 2 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 Velika Trepča : 2 espèces reliées par 1 interaction GloBI sur 1 type (connectance 100.0%, filtre Serrano α=0.2).

Espèces affichées
2
Interactions affichées
1
Connectance
1.000
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

33km

Max discharge

2,2m³/s

Max Strahler

2

Segments matched

4

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