Ontologia

Ruisseau· 15 segments

Verknė

Crosses 4 administrative regions : Alytaus, Birštono, Prienų, Trakų

ruisseau

Total length

84km

Max discharge

4,6m³/s

Max Strahler

3

Segments matched

15

River geography4 admin regions · 0 communes

Parent watershed

hybas-2080318720713 km²

4 administrative regions crossed (GADM L2)

  • Prienų
    Kauno · Lithuania
    30.2 km
    in this dpt
  • Trakų
    Vilniaus · Lithuania
    26.5 km
    in this dpt
  • Birštono
    Kauno · Lithuania
    0.8 km
    in this dpt
  • Alytaus
    Alytaus · Lithuania
    0.0 km
    in this dpt

11 intersecting protected areas

2 more protected areas

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

Species present

269 distinct species · 379 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 14 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 Verknė : 11 espèces reliées par 19 interactions GloBI sur 4 types (connectance 20.9%, filtre Serrano α=0.2). 3 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

84km

Max discharge

4,6m³/s

Max Strahler

3

Segments matched

15

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