Ontologia

Rivière· 49 segments

Elandsrivier

Crosses 4 administrative regions : City of Tshwane, Nkangala, Sekhukhune, Waterberg

rivière

Total length

348km

Max discharge

3,3m³/s

Max Strahler

5

Segments matched

49

River geography4 admin regions · 0 communes

Parent watershed

hybas-10815903701320 km²

4 administrative regions crossed (GADM L2)

  • City of Tshwane
    Gauteng · South Africa
    117.1 km
    in this dpt
  • Waterberg
    Limpopo · South Africa
    66.9 km
    in this dpt
  • Sekhukhune
    Limpopo · South Africa
    16.8 km
    in this dpt
  • Nkangala
    Mpumalanga · South Africa
    15.4 km
    in this dpt

11 intersecting protected areas

2 more protected areas

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

Species present

349 distinct species · 8 969 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 14 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 Elandsrivier : 14 espèces reliées par 8 interactions GloBI sur 3 types (connectance 8.8%, filtre Serrano α=0.2).

Espèces affichées
14
Interactions affichées
8
Connectance
0.088
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

348km

Max discharge

3,3m³/s

Max Strahler

5

Segments matched

49

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