Ontologia

Ruisseau· 3 segments

Peppers Creek

Crosses 3 administrative regions : Bathurst, Cooma-Monaro, Oberon

ruisseau

Total length

39km

Max discharge

0,7m³/s

Max Strahler

2

Segments matched

3

River geography3 admin regions · 0 communes

Parent watershed

hybas-50805848101104 km²

3 administrative regions crossed (GADM L2)

  • Bathurst
    New South Wales · Australia
    14.6 km
    in this dpt
  • Cooma-Monaro
    New South Wales · Australia
    14.1 km
    in this dpt
  • Oberon
    New South Wales · Australia
    0.0 km
    in this dpt

1 intersecting protected areas

  • Deua

    IUCN Ib

    National Park

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

Species present

236 distinct species · 6 776 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 34 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 Peppers Creek : 26 espèces reliées par 65 interactions GloBI sur 5 types (connectance 11.6%, filtre Serrano α=0.2). 8 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
34
Interactions affichées
65
Connectance
0.116
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

39km

Max discharge

0,7m³/s

Max Strahler

2

Segments matched

3

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