Ruisseau· 3 segments
Niitselysjoki
Crosses 2 administrative regions : Lapland, Loukhskiy rayon
Total length
14km
Max discharge
1m³/s
Max Strahler
2
Segments matched
3
River geography2 admin regions · 0 communes
2 administrative regions crossed (GADM L2)
- LaplandLapland · Finland13.4 kmin this dpt
- Loukhskiy rayonKarelia · Russia0.0 kmin this dpt
6 intersecting protected areas
Oulanka
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Oulanka
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Oulanka National Park
IUCN Not ReportedWetland of International Importance (Ramsar Site)
Oulangan kansallispuisto
IUCN IINational Park
Metsälain erityisen tärkeät elinympäristöt Lappi
IUCN Not AssignedForest habitats of special importance according to the Forest Act (OECM)
Metsätalouden ympäristötukikohteet Lappi
IUCN Not AssignedForestry environmental aid contracts (OECM)
1 page = 1 named river (aggregation of 3 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
289 distinct species · 1 137 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 28 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 Niitselysjoki : 19 espèces reliées par 57 interactions GloBI sur 4 types (connectance 15.1%, 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
14km
Max discharge
1,0m³/s
Max Strahler
2
Segments matched
3
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.