Ruisseau· 8 segments
Ringvaart van de Haarlemmermeerpolder
Crosses 9 administrative regions : Aalsmeer, Amstelveen, Amsterdam, Bloemendaal, Haarlemmermeer +4
Total length
60km
Max discharge
3,6m³/s
Max Strahler
3
Segments matched
8
River geography9 admin regions · 0 communes
9 administrative regions crossed (GADM L2)
- HaarlemmermeerNoord-Holland · Netherlands17.8 kmin this dpt
- HillegomZuid-Holland · Netherlands3.9 kmin this dpt
- AalsmeerNoord-Holland · Netherlands3.8 kmin this dpt
- LisseZuid-Holland · Netherlands3.0 kmin this dpt
- Kaag en BraassemZuid-Holland · Netherlands1.6 kmin this dpt
- TeylingenZuid-Holland · Netherlands0.7 kmin this dpt
- AmsterdamNoord-Holland · Netherlands0.5 kmin this dpt
- BloemendaalNoord-Holland · Netherlands0.0 kmin this dpt
- AmstelveenNoord-Holland · Netherlands0.0 kmin this dpt
2 intersecting protected areas
1 page = 1 named river (aggregation of 8 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
2 955 distinct species · 62 215 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 36 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 Ringvaart van de Haarlemmermeerpolder : 27 espèces reliées par 121 interactions GloBI sur 6 types (connectance 18.2%, filtre Serrano α=0.2). 10 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
60km
Max discharge
3,6m³/s
Max Strahler
3
Segments matched
8
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.