Ontologia

Rivière· 16 segments

Lielupe

Crosses 4 administrative regions : Bauska, Jelgava, Riga, Tukums

rivière

Total length

117km

Max discharge

127,7m³/s

Max Strahler

6

Segments matched

16

River geography4 admin regions · 0 communes

Parent watershed

hybas-20802829802281 km²

4 administrative regions crossed (GADM L2)

  • Jelgava
    Zemgale · Latvia
    56.8 km
    in this dpt
  • Bauska
    Zemgale · Latvia
    8.7 km
    in this dpt
  • Riga
    Riga · Latvia
    2.1 km
    in this dpt
  • Tukums
    Riga · Latvia
    0.0 km
    in this dpt

18 intersecting protected areas

9 more protected areas

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

Species present

127 distinct species · 165 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 34 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 Lielupe : 28 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 66 interactions GloBI sur 3 types (connectance 11.8%, filtre Serrano α=0.2). 6 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
34
Interactions affichées
66
Connectance
0.118
Patrimoniales
2
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

117km

Max discharge

127,7m³/s

Max Strahler

6

Segments matched

16

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