Ontologia

Ruisseau· 4 segments

Dreisam

Crosses 3 administrative regions : Breisgau-Hochschwarzwald, Emmendingen, Freiburg im Breisgau

ruisseau

Total length

30km

Max discharge

6,4m³/s

Max Strahler

3

Segments matched

4

River geography3 admin regions · 0 communes

Parent watershed

hybas-20804727101258 km²

3 administrative regions crossed (GADM L2)

  • Breisgau-Hochschwarzwald
    Baden-Württemberg · Germany
    8.7 km
    in this dpt
  • Freiburg im Breisgau
    Baden-Württemberg · Germany
    8.2 km
    in this dpt
  • Emmendingen
    Baden-Württemberg · Germany
    0.3 km
    in this dpt

19 intersecting protected areas

10 more protected areas

1 page = 1 named river (aggregation of 4 HydroRIVERS v10 segments). Spatial join cached after first hit.

Species present

2 541 distinct species · 42 661 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 35 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).

RègnesAnimalPlanteChampignonBacterie
RelationsPredationParasitismeSymbiosePollinisation
StatutEn dangerVulnérableProtégéeEndémique

Indicateurs du tissu écologique

Tissu écologique de Dreisam : 23 espèces reliées par 93 interactions GloBI sur 5 types (connectance 15.6%, filtre Serrano α=0.2). 12 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
35
Interactions affichées
93
Connectance
0.156
Patrimoniales
0
Plus dense que (national)0 %(top 100%)

Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).

Hydrology (HydroRIVERS v10)

Total length

30km

Max discharge

6,4m³/s

Max Strahler

3

Segments matched

4

HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.