Ontologia

Ruisseau· 6 segments

Plenty River

Crosses 4 administrative regions : Banyule, Manningham, Nillumbik, Whittlesea

ruisseau

Total length

345km

Max discharge

2,6m³/s

Max Strahler

3

Segments matched

6

River geography4 admin regions · 0 communes

Parent watershed

hybas-5080611670349 km²

4 administrative regions crossed (GADM L2)

  • Whittlesea
    Victoria · Australia
    27.5 km
    in this dpt
  • Banyule
    Victoria · Australia
    7.6 km
    in this dpt
  • Nillumbik
    Victoria · Australia
    5.7 km
    in this dpt
  • Manningham
    Victoria · Australia
    0.0 km
    in this dpt

3 intersecting protected areas

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

Species present

1 898 distinct species · 160 145 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 37 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 Plenty River : 29 espèces reliées par 74 interactions GloBI sur 5 types (connectance 10.0%, filtre Serrano α=0.2). 10 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
39
Interactions affichées
74
Connectance
0.100
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

345km

Max discharge

2,6m³/s

Max Strahler

3

Segments matched

6

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