Ruisseau
Oosteindervaart
Crosses 4 administrative regions : Bloemendaal, Haarlemmermeer, Heemstede, Hillegom
Total length
2km
Max discharge
0,3m³/s
Max Strahler
1
Segments matched
1
River geography4 admin regions · 0 communes
4 administrative regions crossed (GADM L2)
- HillegomZuid-Holland · Netherlands2.6 kmin this dpt
- BloemendaalNoord-Holland · Netherlands1.7 kmin this dpt
- HaarlemmermeerNoord-Holland · Netherlands0.0 kmin this dpt
- HeemstedeNoord-Holland · Netherlands0.0 kmin this dpt
4 intersecting protected areas
NNN-NH
IUCN Not AssignedNature Reserves owned by professional nature management organizations
NNN-ZH
IUCN Not AssignedNature Reserves owned by professional nature management organizations
Kennemerland-Zuid
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Kennemerland-Zuid
IUCN IVNature Conservation Act
1 page = 1 named river (aggregation of 1 HydroRIVERS v10 segment). Spatial join cached after first hit.
Species present
4 046 distinct species · 83 748 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 35 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).
Indicateurs du tissu écologique
Tissu écologique de Oosteindervaart : 24 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 127 interactions GloBI sur 6 types (connectance 21.3%, filtre Serrano α=0.2). 11 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
2km
Max discharge
0,3m³/s
Max Strahler
1
Segments matched
1
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.