Rivière· 2 segments
Mērsraga kanāls
Crosses 2 administrative regions : Talsi, Tukums
Total length
6km
Max discharge
7,7m³/s
Max Strahler
4
Segments matched
2
River geography2 admin regions · 0 communes
2 administrative regions crossed (GADM L2)
9 intersecting protected areas
Rīgas līča rietumu piekraste
IUCN IVProtected Marine Area
Rigas lica rietumu piekraste
IUCN Not ReportedBaltic Sea Protected Area (HELCOM)
Rīgas līča rietumu piekraste
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Rīgas līča rietumu piekraste
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Lake Engure
IUCN IVWetland of International Importance (Ramsar Site)
Engures ezers
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Engures ezers
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Engures ezers
IUCN IINature Park
Mērsraga meži
IUCN IVNature Reserve
1 page = 1 named river (aggregation of 2 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
142 distinct species · 2 205 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 28 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 Mērsraga kanāls : 22 espèces reliées par 40 interactions GloBI sur 3 types (connectance 10.6%, 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
7,7m³/s
Max Strahler
4
Segments matched
2
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.