Ruisseau· 2 segments
Schwippe
Crosses 1 administrative regions : Böblingen
Total length
16km
Max discharge
1m³/s
Max Strahler
2
Segments matched
2
River geography1 admin regions · 0 communes
1 administrative regions crossed (GADM L2)
- BöblingenBaden-Württemberg · Germany13.4 kmin this dpt
10 intersecting protected areas
Glemswald
IUCN VLandscape Protection Area
Glemswald und Stuttgarter Bucht
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Landscape Protection Area
Aidlingen
IUCN VLandscape Protection Area
Gäulandschaft an der Würm
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Grafenau
IUCN VLandscape Protection Area
Sindelfingen
IUCN VLandscape Protection Area
Böblingen
IUCN VLandscape Protection Area
Hacksberg und Steckental
IUCN IVNature Reserve
1 more protected areassorted by area
Kasparsbrunnen-Ried-Binn
IUCN IVNature Reserve
1 page = 1 named river (aggregation of 2 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
1 300 distinct species · 5 510 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 34 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 Schwippe : 20 espèces reliées par 111 interactions GloBI sur 5 types (connectance 17.6%, 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
16km
Max discharge
1,0m³/s
Max Strahler
2
Segments matched
2
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.