Ontologia

Ruisseau· 5 segments

Zalesianka

Crosses 4 administrative regions : Lublin, Opole Lubelskie, Puławy, Ryki

ruisseau

Total length

22km

Max discharge

0,5m³/s

Max Strahler

2

Segments matched

5

River geography4 admin regions · 0 communes

Parent watershed

hybas-20803905201145 km²

4 administrative regions crossed (GADM L2)

  • Ryki
    Lubelskie · Poland
    15.8 km
    in this dpt
  • Lublin
    Lubelskie · Poland
    2.7 km
    in this dpt
  • Opole Lubelskie
    Lubelskie · Poland
    0.0 km
    in this dpt
  • Puławy
    Lubelskie · Poland
    0.0 km
    in this dpt

4 intersecting protected areas

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

Species present

128 distinct species · 189 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 44 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 Zalesianka : 34 espèces reliées par 109 interactions GloBI sur 6 types (connectance 11.5%, filtre Serrano α=0.2). 10 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
44
Interactions affichées
109
Connectance
0.115
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

22km

Max discharge

0,5m³/s

Max Strahler

2

Segments matched

5

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