Ontologia

Rivière· 38 segments

Abava

Crosses 4 administrative regions : Kuldiga, Talsi, Tukums, Ventspils

rivière

Total length

135km

Max discharge

22,7m³/s

Max Strahler

4

Segments matched

38

River geography4 admin regions · 0 communes

Parent watershed

hybas-20802758902169 km²

4 administrative regions crossed (GADM L2)

  • Tukums
    Riga · Latvia
    73.5 km
    in this dpt
  • Kuldiga
    Kurzeme · Latvia
    37.9 km
    in this dpt
  • Talsi
    Kurzeme · Latvia
    22.4 km
    in this dpt
  • Ventspils
    Kurzeme · Latvia
    11.6 km
    in this dpt

26 intersecting protected areas

17 more protected areas

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

Species present

212 distinct species · 576 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 36 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 Abava : 22 espèces reliées par 84 interactions GloBI sur 6 types (connectance 13.3%, filtre Serrano α=0.2). 14 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
36
Interactions affichées
84
Connectance
0.133
Patrimoniales
0
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

135km

Max discharge

22,7m³/s

Max Strahler

4

Segments matched

38

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