Ruisseau· 3 segments
Poppelsche Leij
Crosses 5 administrative regions : Alphen-Chaam, Antwerpen, Baarle-Nassau, Goirle, Tilburg
Total length
12km
Max discharge
1,8m³/s
Max Strahler
3
Segments matched
3
River geography5 admin regions · 0 communes
5 administrative regions crossed (GADM L2)
- GoirleNoord-Brabant · Netherlands9.0 kmin this dpt
- Alphen-ChaamNoord-Brabant · Netherlands1.6 kmin this dpt
- AntwerpenVlaanderen · Belgium0.1 kmin this dpt
- Baarle-NassauNoord-Brabant · Netherlands0.0 kmin this dpt
- TilburgNoord-Brabant · Netherlands0.0 kmin this dpt
4 intersecting protected areas
NNN-NB
IUCN Not AssignedNature Reserves owned by professional nature management organizations
NBP-AN-19-0143 type 2
IUCN VINature management plan type 2 (Flemish Region)
Regte Heide & Riels Laag
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Regte Heide & Riels Laag
IUCN IVNature Conservation Act
1 page = 1 named river (aggregation of 3 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
4 223 distinct species · 81 201 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 38 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 Poppelsche Leij : 24 espèces reliées par 106 interactions GloBI sur 6 types (connectance 14.3%, filtre Serrano α=0.2). 15 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
12km
Max discharge
1,8m³/s
Max Strahler
3
Segments matched
3
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.