Ontologia

Rivière

Osonoja

⚠ Partial coverage : only 1 named segment matched so far. The real rivière extends much further (Strahler order 6 indicates a major river). Cross-source ingest in progress — values below reflect only the matched segment.

Crosses 1 administrative regions : Kymenlaakso

rivière

Max discharge

221,6m³/s

Max Strahler

6

Segments matched

1

River geography1 admin regions · 0 communes

Parent watershed

hybas-2080222500280 km²

1 administrative regions crossed (GADM L2)

  • Kymenlaakso
    Southern Finland · Finland
    5.0 km
    in this dpt

7 intersecting protected areas

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

Species present

2 208 distinct species · 14 144 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 35 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 Osonoja : 22 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 116 interactions GloBI sur 5 types (connectance 18.4%, filtre Serrano α=0.2). 14 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
36
Interactions affichées
116
Connectance
0.184
Patrimoniales
2
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)

Matched len.

1,5km

Max discharge

221,6m³/s

Max Strahler

6

Segments matched

1

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