Ruisseau· 2 segments
Peeda jõgi
Crosses 1 administrative regions : Kambja
Total length
21km
Max discharge
0,8m³/s
Max Strahler
3
Segments matched
2
River geography1 admin regions · 0 communes
1 administrative regions crossed (GADM L2)
- KambjaTartu · Estonia9.6 kmin this dpt
10 intersecting protected areas
Suure-Kambja mõisa park
IUCN VLimited management zone of protected landscape
Porijõgi/Reola jõgi
IUCN Not AssignedSpawning area
VEP nr.141092
IUCN Not AssignedWoodland key habitat
Peeda jõe
IUCN Not ReportedSite of Community Importance (Habitats Directive)
Peeda jõe - Idaoja hoiuala
IUCN VILimited-conservation area
Peeda jõgi
IUCN Not AssignedSpawning area
VEP nr.210199
IUCN Not AssignedWoodland key habitat
Idaoja
IUCN Not AssignedSpawning area
VEP nr.208746
IUCN Not AssignedWoodland key habitat
1 more protected areassorted by area
VEP nr.213162
IUCN Not AssignedWoodland key habitat
1 page = 1 named river (aggregation of 2 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
894 distinct species · 7 030 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 Peeda jõgi : 25 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 36 interactions GloBI sur 4 types (connectance 7.3%, filtre Serrano α=0.2). 7 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
21km
Max discharge
0,8m³/s
Max Strahler
3
Segments matched
2
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.