Ontologia

Ruisseau· 4 segments

Sinjiri River

Crosses 2 administrative regions : Luangwa, Mbire

ruisseau

Total length

8km

Max discharge

1,1m³/s

Max Strahler

3

Segments matched

4

River geography2 admin regions · 0 communes

Parent watershed

hybas-10814316802031 km²

2 administrative regions crossed (GADM L2)

  • Mbire
    Mashonaland Central · Zimbabwe
    10.4 km
    in this dpt
  • Luangwa
    Lusaka · Zambia
    0.0 km
    in this dpt

2 intersecting protected areas

  • Rufunsa

    IUCN VI

    Game Management Area

  • Chapoto

    IUCN Not Reported

    Wildlife Management Area

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

Species present

245 distinct species · 664 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 30 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 Sinjiri River : 26 espèces reliées par 24 interactions GloBI sur 2 types (connectance 5.5%, filtre Serrano α=0.2). 4 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
30
Interactions affichées
24
Connectance
0.055
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

8km

Max discharge

1,1m³/s

Max Strahler

3

Segments matched

4

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