Rivière
Gosebach
⚠ Partial coverage : only 1 named segment matched so far. The real rivière extends much further (Strahler order 6 indicates a major river). Cross-source ingest in progress — values below reflect only the matched segment.
Crosses 1 administrative regions : Meißen
Max discharge
336m³/s
Max Strahler
6
Segments matched
1
River geography1 admin regions · 0 communes
1 administrative regions crossed (GADM L2)
- MeißenSachsen · Germany5.3 kmin this dpt
6 intersecting protected areas
Landscape Protection Area
Elbtal zwischen Schöna und Mühlberg
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Elbtal zwischen Schöna und Mühlberg
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Seußlitzer Elbhügelland und Golk
IUCN Not ReportedSpecial Protection Area (Birds Directive)
Nature Reserve
Seußlitzer Gründe
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
1 page = 1 named river (aggregation of 1 HydroRIVERS v10 segment). Spatial join cached after first hit.
Species present
1 662 distinct species · 4 696 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 Gosebach : 25 espèces reliées par 141 interactions GloBI sur 5 types (connectance 19.0%, filtre Serrano α=0.2). 14 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)
Matched len.
16,8km
Max discharge
336,0m³/s
Max Strahler
6
Segments matched
1
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.