Ontologia

Fleuve· 39 segments

Ondoto

Crosses 2 administrative regions : Curoca, Epupa

fleuve

Total length

81km

Max discharge

200,9m³/s

Max Strahler

7

Segments matched

39

River geography2 admin regions · 0 communes

Parent watershed

hybas-10814655301835 km²

2 administrative regions crossed (GADM L2)

  • Epupa
    Kunene · Namibia
    180.7 km
    in this dpt
  • Curoca
    Cunene · Angola
    0.0 km
    in this dpt

3 intersecting protected areas

  • Kunene River

    IUCN Not Reported

    Communal Conservancy

  • Ombombo

    IUCN Not Reported

    Communal Conservancy

  • Ombazu

    IUCN Not Reported

    Communal Conservancy

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

Species present

28 distinct species · 36 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 4 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 Ondoto : 3 espèces reliées par 3 interactions GloBI sur 1 type (connectance 50.0%, filtre Serrano α=0.2). 1 bulle taxonomique (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
4
Interactions affichées
3
Connectance
0.500
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

81km

Max discharge

200,9m³/s

Max Strahler

7

Segments matched

39

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