Ruisseau· 3 segments
Kokonjoki
Crosses 2 administrative regions : Pirkanmaa, Tavastia Proper
Total length
12km
Max discharge
2,8m³/s
Max Strahler
3
Segments matched
3
River geography2 admin regions · 0 communes
2 administrative regions crossed (GADM L2)
- PirkanmaaWestern Finland · Finland15.0 kmin this dpt
- Tavastia ProperWestern Finland · Finland0.0 kmin this dpt
4 intersecting protected areas
Metsälain erityisen tärkeät elinympäristöt Pirkanmaa
IUCN Not AssignedForest habitats of special importance according to the Forest Act (OECM)
Metsätalouden ympäristötukikohteet Pirkanmaa
IUCN Not AssignedForestry environmental aid contracts (OECM)
Metsälain erityisen tärkeät elinympäristöt Kanta-Häme
IUCN Not AssignedForest habitats of special importance according to the Forest Act (OECM)
Kontunenän lehmuslehto
IUCN Not AssignedProtected Habitat Type
1 page = 1 named river (aggregation of 3 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
444 distinct species · 1 099 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 40 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 Kokonjoki : 31 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 85 interactions GloBI sur 6 types (connectance 10.9%, filtre Serrano α=0.2). 9 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
12km
Max discharge
2,8m³/s
Max Strahler
3
Segments matched
3
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.