Ruisseau
Zuidervaartje
Crosses 1 administrative regions : West-Vlaanderen
Total length
16km
Max discharge
0,5m³/s
Max Strahler
1
Segments matched
1
River geography1 admin regions · 0 communes
1 administrative regions crossed (GADM L2)
- West-VlaanderenVlaanderen · Belgium8.2 kmin this dpt
8 intersecting protected areas
Special Areas of Conservation (Habitats Directive)
NBP-WV-23-0104 type 4
IUCN IVNature management plan type 4 (Flemish Region)
Het Vloethemveld, Sint-Andriesveld, Tillegem
IUCN Not AssignedFlemish Ecological Network (Flemish Region)
NBP-WV-18-0004
IUCN VINature management plan type 2 (Flemish Region)
NBP/WV/19/0123 type 3
IUCN IVNature management plan type 3 (Flemish Region)
UBBP-WV-13-0001 type 2
IUCN VINature management plan type 2 (Flemish Region)
NBP-WV-23-0104 type 2
IUCN VINature management plan type 2 (Flemish Region)
NBP-WV-21-0167 type 4
IUCN IVNature management plan type 4 (Flemish Region)
1 page = 1 named river (aggregation of 1 HydroRIVERS v10 segment). Spatial join cached after first hit.
Species present
2 592 distinct species · 66 250 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 Zuidervaartje : 22 espèces reliées par 126 interactions GloBI sur 5 types (connectance 17.9%, filtre Serrano α=0.2). 16 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
16km
Max discharge
0,5m³/s
Max Strahler
1
Segments matched
1
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.