Ontologia

Ruisseau

Svēpaine

Crosses 1 administrative regions : Dobele

ruisseau

Total length

28km

Max discharge

0,2m³/s

Max Strahler

1

Segments matched

1

River geography1 admin regions · 0 communes

Parent watershed

hybas-20802824602306 km²

1 administrative regions crossed (GADM L2)

  • Dobele
    Zemgale · Latvia
    7.9 km
    in this dpt

3 intersecting protected areas

  • Nature Reserve

  • Ukru gārša

    IUCN Not Reported

    Special Protection Area (Birds Directive)

  • Ukru gārša

    IUCN Not Reported

    Special Areas of Conservation (Habitats Directive)

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

Species present

96 distinct species · 129 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 23 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 Svēpaine : 18 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 20 interactions GloBI sur 4 types (connectance 7.9%, filtre Serrano α=0.2). 5 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
23
Interactions affichées
20
Connectance
0.079
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

28km

Max discharge

0,2m³/s

Max Strahler

1

Segments matched

1

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