Ruisseau· 2 segments
Arula oja
Crosses 1 administrative regions : Puhajarve
Total length
6km
Max discharge
0,1m³/s
Max Strahler
1
Segments matched
2
River geography1 admin regions · 0 communes
1 administrative regions crossed (GADM L2)
- PuhajarveValga · Estonia2.3 kmin this dpt
9 intersecting protected areas
Otepää
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Otepää
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Otepää looduspark
IUCN Not AssignedProtected landscape (nature park)
Otepää LP, Otepää pv.
IUCN VLimited management zone of protected landscape
Limited management zone of protected landscape
Otepää LP, Kääriku skv.
IUCN VManaged conservation zone of protected landscape
Otepää LP, Välkjärve skv.
IUCN IbWilderness conservation zone of protected landscape
VEP nr.139094
IUCN Not AssignedWoodland key habitat
VEP nr.139091
IUCN Not AssignedWoodland key habitat
1 page = 1 named river (aggregation of 2 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
1 148 distinct species · 3 752 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 32 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).
Indicateurs du tissu écologique
Tissu écologique de Arula oja : 26 espèces reliées par 37 interactions GloBI sur 3 types (connectance 7.5%, filtre Serrano α=0.2). 6 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
6km
Max discharge
0,1m³/s
Max Strahler
1
Segments matched
2
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.