Ontologia

Ruisseau

Westertocht

Crosses 2 administrative regions : Alkmaar, Castricum

ruisseau

Total length

8km

Max discharge

2,2m³/s

Max Strahler

2

Segments matched

1

River geography2 admin regions · 0 communes

Parent watershed

hybas-2080023220795 km²

2 administrative regions crossed (GADM L2)

  • Alkmaar
    Noord-Holland · Netherlands
    1.2 km
    in this dpt
  • Castricum
    Noord-Holland · Netherlands
    0.2 km
    in this dpt

1 intersecting protected areas

  • NNN-NH

    IUCN Not Assigned

    Nature Reserves owned by professional nature management organizations

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

Species present

3 135 distinct species · 67 489 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 45 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 Westertocht : 33 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 111 interactions GloBI sur 5 types (connectance 11.2%, filtre Serrano α=0.2). 12 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
45
Interactions affichées
111
Connectance
0.112
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

8km

Max discharge

2,2m³/s

Max Strahler

2

Segments matched

1

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