Ontologia

Ruisseau· 2 segments

Uru oja

Crosses 4 administrative regions : Kaisama, Kehtna, Tori, Vändra

ruisseau

Total length

38km

Max discharge

0,8m³/s

Max Strahler

2

Segments matched

2

River geography4 admin regions · 0 communes

Parent watershed

hybas-2080257830590 km²

4 administrative regions crossed (GADM L2)

  • Vändra
    Pärnu · Estonia
    11.0 km
    in this dpt
  • Kaisama
    Pärnu · Estonia
    5.1 km
    in this dpt
  • Kehtna
    Rapla · Estonia
    3.0 km
    in this dpt
  • Tori
    Pärnu · Estonia
    0.0 km
    in this dpt

30 intersecting protected areas

21 more protected areas

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

Species present

379 distinct species · 729 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 42 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 Uru oja : 31 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 106 interactions GloBI sur 7 types (connectance 11.7%, filtre Serrano α=0.2). 12 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
43
Interactions affichées
106
Connectance
0.117
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

38km

Max discharge

0,8m³/s

Max Strahler

2

Segments matched

2

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