Ontologia

Ruisseau· 7 segments

Ärma jõgi

Crosses 4 administrative regions : Paistu, Saarepeedi, Tarvastu, Viiratsi

ruisseau

Total length

45km

Max discharge

3,1m³/s

Max Strahler

3

Segments matched

7

River geography4 admin regions · 0 communes

Parent watershed

hybas-2080258140756 km²

4 administrative regions crossed (GADM L2)

  • Tarvastu
    Viljandi · Estonia
    18.5 km
    in this dpt
  • Viiratsi
    Viljandi · Estonia
    11.6 km
    in this dpt
  • Paistu
    Viljandi · Estonia
    4.6 km
    in this dpt
  • Saarepeedi
    Viljandi · Estonia
    0.3 km
    in this dpt

18 intersecting protected areas

9 more protected areas

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

Species present

128 distinct species · 1 115 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 Ärma jõgi : 32 espèces reliées par 29 interactions GloBI sur 6 types (connectance 4.9%, filtre Serrano α=0.2). 3 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

45km

Max discharge

3,1m³/s

Max Strahler

3

Segments matched

7

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