Ontologia

Rivière· 2 segments

Kanał Młynikowski

Crosses 4 administrative regions : Jarocin, Pleszew, Słupca, Września

rivière

Total length

16km

Max discharge

18m³/s

Max Strahler

5

Segments matched

2

River geography4 admin regions · 0 communes

Parent watershed

hybas-2080374390948 km²

4 administrative regions crossed (GADM L2)

  • Pleszew
    Wielkopolskie · Poland
    10.7 km
    in this dpt
  • Września
    Wielkopolskie · Poland
    6.1 km
    in this dpt
  • Jarocin
    Wielkopolskie · Poland
    0.0 km
    in this dpt
  • Słupca
    Wielkopolskie · Poland
    0.0 km
    in this dpt

5 intersecting protected areas

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

Species present

202 distinct species · 419 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 34 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 Kanał Młynikowski : 25 espèces reliées par 56 interactions GloBI sur 5 types (connectance 9.4%, filtre Serrano α=0.2). 10 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
35
Interactions affichées
56
Connectance
0.094
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

16km

Max discharge

18,0m³/s

Max Strahler

5

Segments matched

2

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