Ontologia

Fleuve· 5 segments

Łacha

Crosses 4 administrative regions : Aleksandrów, Kozienice, Ryki, Toruń

fleuve

Total length

56km

Max discharge

990,5m³/s

Max Strahler

7

Segments matched

5

River geography4 admin regions · 0 communes

Parent watershed

hybas-2080353640169 km²

4 administrative regions crossed (GADM L2)

  • Aleksandrów
    Kujawsko-Pomorskie · Poland
    7.6 km
    in this dpt
  • Kozienice
    Mazowieckie · Poland
    2.5 km
    in this dpt
  • Toruń
    Kujawsko-Pomorskie · Poland
    0.2 km
    in this dpt
  • Ryki
    Lubelskie · Poland
    0.0 km
    in this dpt

6 intersecting protected areas

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

Species present

136 distinct species · 933 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 31 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 Łacha : 25 espèces reliées par 63 interactions GloBI sur 3 types (connectance 13.5%, filtre Serrano α=0.2). 6 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
31
Interactions affichées
63
Connectance
0.136
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

56km

Max discharge

990,5m³/s

Max Strahler

7

Segments matched

5

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