Ruisseau· 2 segments
Moorkulturgraben
Crosses 2 administrative regions : Dahme-Spreewald, Spree-Neiße
Total length
4km
Max discharge
0,1m³/s
Max Strahler
1
Segments matched
2
River geography2 admin regions · 0 communes
2 administrative regions crossed (GADM L2)
- Spree-NeißeBrandenburg · Germany4.8 kmin this dpt
- Dahme-SpreewaldBrandenburg · Germany4.2 kmin this dpt
9 intersecting protected areas
Dahme-Heideseen
IUCN VLandscape Protection Area
Landscape Protection Area
Dahmetal bei Briesen
IUCN IVNature Reserve
Dahmetal bei Briesen
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Mahnigsee-Dahmetal
IUCN IVNature Reserve
Mahnigsee Dahmetal
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Glinziger Teich- und Wiesengebiet
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Nature Reserve
Landscape Protection Area
1 page = 1 named river (aggregation of 2 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
827 distinct species · 4 807 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 36 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 Moorkulturgraben : 26 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 77 interactions GloBI sur 3 types (connectance 12.2%, filtre Serrano α=0.2). 10 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
4km
Max discharge
0,1m³/s
Max Strahler
1
Segments matched
2
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.