Rivière
Lievevrouweleibeek
⚠ Partial coverage : only 1 named segment matched so far. The real rivière extends much further (Strahler order 5 indicates a major river). Cross-source ingest in progress — values below reflect only the matched segment.
Crosses 1 administrative regions : Vlaams Brabant
Max discharge
40,9m³/s
Max Strahler
5
Segments matched
1
River geography1 admin regions · 0 communes
1 administrative regions crossed (GADM L2)
- Vlaams BrabantVlaanderen · Belgium2.2 kmin this dpt
4 intersecting protected areas
Demervallei
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
De Demervallei ten westen van Aarschot
IUCN Not AssignedFlemish Ecological Network (Flemish Region)
De Broekelei-Zegbroek-Tremelo
IUCN Not AssignedFlemish Ecological Network (Flemish Region)
NBP-VB-21-0315 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
1 886 distinct species · 65 412 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 43 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 Lievevrouweleibeek : 33 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 118 interactions GloBI sur 6 types (connectance 12.5%, 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)
Matched len.
0,6km
Max discharge
40,9m³/s
Max Strahler
5
Segments matched
1
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.