Ruisseau· 2 segments
Kornerup Å
Crosses 2 administrative regions : Lejre, Roskilde
Total length
11km
Max discharge
1,6m³/s
Max Strahler
3
Segments matched
2
River geography2 admin regions · 0 communes
2 administrative regions crossed (GADM L2)
6 intersecting protected areas
Roskilde Fjord og Jaegerspris Nordskov
IUCN Not ReportedBaltic Sea Protected Area (HELCOM)
Roskilde Fjord
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Roskilde Fjord, Kattinge Vig og Kattinge Sø
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Lejre Kommune private
IUCN Not Assigned§3 protected habitats (all lakes, bogs, streams, heaths and meadows etc.)
Roskilde Kommune private
IUCN Not Assigned§3 protected habitats (all lakes, bogs, streams, heaths and meadows etc.)
Lejre Kommune public
IUCN IV§3 protected habitats (all lakes, bogs, streams, heaths and meadows etc.)
1 page = 1 named river (aggregation of 2 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
1 506 distinct species · 73 732 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 31 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 Kornerup Å : 21 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 91 interactions GloBI sur 6 types (connectance 17.2%, filtre Serrano α=0.2). 12 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
11km
Max discharge
1,6m³/s
Max Strahler
3
Segments matched
2
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.