Ontologia

Ruisseau

Diepenhoekse Veldenloop

Crosses 3 administrative regions : Cranendonck, Nederweert, Someren

ruisseau

Total length

1km

Max discharge

0,5m³/s

Max Strahler

1

Segments matched

1

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080386150892 km²

3 administrative regions crossed (GADM L2)

  • Someren
    Noord-Brabant · Netherlands
    9.0 km
    in this dpt
  • Nederweert
    Limburg · Netherlands
    0.3 km
    in this dpt
  • Cranendonck
    Noord-Brabant · Netherlands
    0.0 km
    in this dpt

4 intersecting protected areas

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

Species present

2 128 distinct species · 27 209 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 41 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 Diepenhoekse Veldenloop : 33 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 105 interactions GloBI sur 5 types (connectance 12.8%, filtre Serrano α=0.2). 8 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
41
Interactions affichées
105
Connectance
0.128
Patrimoniales
1
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

1km

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.