Ontologia

Rivière· 17 segments

Burnt River

Crosses 3 administrative regions : Haliburton, Kawartha Lakes, Peterborough

rivière

Total length

428km

Max discharge

19,4m³/s

Max Strahler

4

Segments matched

17

River geography3 admin regions · 0 communes

Parent watershed

hybas-70804252001481 km²

3 administrative regions crossed (GADM L2)

  • Haliburton
    Ontario · Canada
    52.6 km
    in this dpt
  • Kawartha Lakes
    Ontario · Canada
    42.8 km
    in this dpt
  • Peterborough
    Ontario · Canada
    0.0 km
    in this dpt

2 intersecting protected areas

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

Species present

236 distinct species · 1 054 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 46 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 Burnt River : 37 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 102 interactions GloBI sur 5 types (connectance 9.0%, filtre Serrano α=0.2). 11 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
48
Interactions affichées
102
Connectance
0.090
Patrimoniales
2
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

428km

Max discharge

19,4m³/s

Max Strahler

4

Segments matched

17

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