Ontologia

Rivière

Ajankulunoja

⚠ 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 : Satakunta

rivière

Max discharge

206,9m³/s

Max Strahler

6

Segments matched

1

River geography1 admin regions · 0 communes

Parent watershed

hybas-20800293202601 km²

1 administrative regions crossed (GADM L2)

  • Satakunta
    Western Finland · Finland
    2.3 km
    in this dpt

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

Species present

1 258 distinct species · 15 039 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 38 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 Ajankulunoja : 28 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 132 interactions GloBI sur 5 types (connectance 17.8%, filtre Serrano α=0.2). 11 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
39
Interactions affichées
132
Connectance
0.178
Patrimoniales
1
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.

0,7km

Max discharge

206,9m³/s

Max Strahler

6

Segments matched

1

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