Ruisseau
Elz-Kanal
Crosses 1 administrative regions : Neckar-Odenwald-Kreis
Total length
1km
Max discharge
1,6m³/s
Max Strahler
2
Segments matched
1
River geography1 admin regions · 0 communes
1 administrative regions crossed (GADM L2)
- Neckar-Odenwald-KreisBaden-Württemberg · Germany6.7 kmin this dpt
12 intersecting protected areas
Neckartal III
IUCN VLandscape Protection Area
Elzbachtal
IUCN VLandscape Protection Area
Neckartal und Wald Obrigheim
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Bauland Mosbach
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Landscape Protection Area
Landscape Protection Area
Henschelberg
IUCN VLandscape Protection Area
Nature Reserve
Nature Reserve
3 more protected areassorted by area
Henschelberg (3 Teilgebiete)
IUCN IVNature Reserve
Hasbachtal
IUCN VLandscape Protection Area
Hamberg
IUCN IVNature Reserve
1 page = 1 named river (aggregation of 1 HydroRIVERS v10 segment). Spatial join cached after first hit.
Species present
1 044 distinct species · 3 280 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 Elz-Kanal : 24 espèces reliées par 108 interactions GloBI sur 6 types (connectance 13.8%, filtre Serrano α=0.2). 16 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
1km
Max discharge
1,6m³/s
Max Strahler
2
Segments matched
1
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.