Ontologia

Ruisseau· 11 segments

Boomley Creek

Crosses 2 administrative regions : Warrumbungle, Wellington

ruisseau

Total length

29km

Max discharge

0,1m³/s

Max Strahler

2

Segments matched

11

River geography2 admin regions · 0 communes

Parent watershed

hybas-5080566820504 km²

2 administrative regions crossed (GADM L2)

  • Warrumbungle
    New South Wales · Australia
    28.6 km
    in this dpt
  • Wellington
    New South Wales · Australia
    0.0 km
    in this dpt

1 intersecting protected areas

  • Goonoo

    IUCN II

    CCA Zone 3 State Conservation Area

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

Species present

208 distinct species · 574 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 40 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 Boomley Creek : 32 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 44 interactions GloBI sur 4 types (connectance 5.6%, filtre Serrano α=0.2). 8 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
40
Interactions affichées
44
Connectance
0.056
Patrimoniales
1
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

29km

Max discharge

0,1m³/s

Max Strahler

2

Segments matched

11

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