Ontologia

Ruisseau· 2 segments

Broekervaart

Crosses 3 administrative regions : Amsterdam, Landsmeer, Waterland

ruisseau

Total length

8km

Max discharge

1,5m³/s

Max Strahler

2

Segments matched

2

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080023220795 km²

3 administrative regions crossed (GADM L2)

  • Landsmeer
    Noord-Holland · Netherlands
    1.9 km
    in this dpt
  • Waterland
    Noord-Holland · Netherlands
    0.9 km
    in this dpt
  • Amsterdam
    Noord-Holland · Netherlands
    0.0 km
    in this dpt

4 intersecting protected areas

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

Species present

3 617 distinct species · 161 178 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

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

Espèces affichées
40
Interactions affichées
137
Connectance
0.176
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

1,5m³/s

Max Strahler

2

Segments matched

2

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