Ontologia

Ruisseau

Deggenhauser Aach

Crosses 2 administrative regions : Bodenseekreis, Sigmaringen

ruisseau

Total length

25km

Max discharge

0,7m³/s

Max Strahler

1

Segments matched

1

River geography2 admin regions · 0 communes

Parent watershed

hybas-2080490680706 km²

2 administrative regions crossed (GADM L2)

  • Bodenseekreis
    Baden-Württemberg · Germany
    11.6 km
    in this dpt
  • Sigmaringen
    Baden-Württemberg · Germany
    0.0 km
    in this dpt

1 intersecting protected areas

  • Deggenhauser Tal

    IUCN Not Reported

    Special Areas of Conservation (Habitats Directive)

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

Species present

859 distinct species · 1 752 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 25 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 Deggenhauser Aach : 14 espèces reliées par 109 interactions GloBI sur 6 types (connectance 26.8%, filtre Serrano α=0.2). 15 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
29
Interactions affichées
109
Connectance
0.269
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

25km

Max discharge

0,7m³/s

Max Strahler

1

Segments matched

1

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