Ruisseau· 2 segments
Moervaart
Crosses 1 administrative regions : Oost-Vlaanderen
Total length
23km
Max discharge
2m³/s
Max Strahler
3
Segments matched
2
River geography1 admin regions · 0 communes
1 administrative regions crossed (GADM L2)
- Oost-VlaanderenVlaanderen · Belgium4.8 kmin this dpt
6 intersecting protected areas
Bossen en heiden van zandig Vlaanderen: oostelijk deel
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
De Moervaartdepressie tot Durmevallei
IUCN Not AssignedFlemish Ecological Network (Flemish Region)
Het Heidebos
IUCN Not AssignedFlemish Ecological Network (Flemish Region)
NBP-OV-19-0158 type 4
IUCN IVNature management plan type 4 (Flemish Region)
NBP-OV-20-0228 type 4
IUCN IVNature management plan type 4 (Flemish Region)
NBP-OV-21-0004 type 4
IUCN IVNature management plan type 4 (Flemish Region)
1 page = 1 named river (aggregation of 2 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
1 603 distinct species · 100 551 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 Moervaart : 23 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 132 interactions GloBI sur 5 types (connectance 19.8%, filtre Serrano α=0.2). 14 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
23km
Max discharge
2,0m³/s
Max Strahler
3
Segments matched
2
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.