Ontologia

Rivière· 2 segments

Savijõgi

Crosses 4 administrative regions : Haaslava, Luunja, Tartu, Ülenurme

rivière

Total length

2km

Max discharge

70,5m³/s

Max Strahler

5

Segments matched

2

River geography4 admin regions · 0 communes

Parent watershed

hybas-20802565602359 km²

4 administrative regions crossed (GADM L2)

  • Ülenurme
    Tartu · Estonia
    4.7 km
    in this dpt
  • Haaslava
    Tartu · Estonia
    2.2 km
    in this dpt
  • Luunja
    Tartu · Estonia
    0.6 km
    in this dpt
  • Tartu
    Tartu · Estonia
    0.0 km
    in this dpt

10 intersecting protected areas

1 more protected areas

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

Species present

2 434 distinct species · 60 392 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 27 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 Savijõgi : 19 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 46 interactions GloBI sur 3 types (connectance 13.1%, filtre Serrano α=0.2). 8 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
27
Interactions affichées
46
Connectance
0.131
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)

Total length

2km

Max discharge

70,5m³/s

Max Strahler

5

Segments matched

2

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