Ruisseau· 8 segments
Piasecznica
Crosses 3 administrative regions : Ostrołęka, Tomaszów Mazowiecki, Łódzki Wschodni
Total length
47km
Max discharge
1,2m³/s
Max Strahler
3
Segments matched
8
River geography3 admin regions · 0 communes
3 administrative regions crossed (GADM L2)
- OstrołękaMazowieckie · Poland37.6 kmin this dpt
- Tomaszów MazowieckiŁódzkie · Poland23.8 kmin this dpt
- Łódzki WschodniŁódzkie · Poland9.6 kmin this dpt
6 intersecting protected areas
Doliny Omulwi i Płodownicy
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Bory Chrobotkowe Karaska
IUCN Not ReportedSite of Community Importance (Habitats Directive)
Bory bagienne i torfowiska Karaska
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Łąki Ciebłowickie
IUCN Not ReportedSite of Community Importance (Habitats Directive)
Torfowisko Karaska
IUCN IVNature Reserve
Podgórze
IUCN IVNature Reserve
1 page = 1 named river (aggregation of 8 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
217 distinct species · 437 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 39 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).
Indicateurs du tissu écologique
Tissu écologique de Piasecznica : 31 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 81 interactions GloBI sur 5 types (connectance 10.9%, filtre Serrano α=0.2). 8 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
47km
Max discharge
1,2m³/s
Max Strahler
3
Segments matched
8
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.