Ontologia

Ruisseau· 6 segments

Mount Pleasant Creek

Crosses 3 administrative regions : Campaspe, Greater Bendigo, Tumut

ruisseau

Total length

131km

Max discharge

0,7m³/s

Max Strahler

3

Segments matched

6

River geography3 admin regions · 0 communes

Parent watershed

hybas-50806038903565 km²

3 administrative regions crossed (GADM L2)

  • Campaspe
    Victoria · Australia
    32.3 km
    in this dpt
  • Tumut
    New South Wales · Australia
    6.1 km
    in this dpt
  • Greater Bendigo
    Victoria · Australia
    1.4 km
    in this dpt

4 intersecting protected areas

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

Species present

200 distinct species · 965 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 32 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 Mount Pleasant Creek : 23 espèces dont 4 patrimoniales (LR IUCN CR/EN/VU) reliées par 43 interactions GloBI sur 4 types (connectance 8.7%, filtre Serrano α=0.2). 9 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
32
Interactions affichées
43
Connectance
0.087
Patrimoniales
4
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

131km

Max discharge

0,7m³/s

Max Strahler

3

Segments matched

6

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