Ontologia

Ruisseau· 2 segments

North Burn

Crosses 3 administrative regions : County Durham, Hartlepool, Stockton-on-Tees

ruisseau

Total length

20km

Max discharge

0,6m³/s

Max Strahler

2

Segments matched

2

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080053080255 km²

3 administrative regions crossed (GADM L2)

  • Hartlepool
    England · United Kingdom
    8.6 km
    in this dpt
  • Stockton-on-Tees
    England · United Kingdom
    2.3 km
    in this dpt
  • County Durham
    England · United Kingdom
    0.3 km
    in this dpt

7 intersecting protected areas

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

Species present

439 distinct species · 1 049 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 38 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 North Burn : 30 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 103 interactions GloBI sur 5 types (connectance 13.9%, filtre Serrano α=0.2). 9 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

20km

Max discharge

0,6m³/s

Max Strahler

2

Segments matched

2

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