Ontologia

Ruisseau· 2 segments

Blumenthaler Aue

Crosses 3 administrative regions : Bremen, Osterholz, Wesermarsch

ruisseau

Total length

15km

Max discharge

0,5m³/s

Max Strahler

2

Segments matched

2

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080345800267 km²

3 administrative regions crossed (GADM L2)

  • Osterholz
    Niedersachsen · Germany
    5.6 km
    in this dpt
  • Bremen
    Bremen · Germany
    2.1 km
    in this dpt
  • Wesermarsch
    Niedersachsen · Germany
    0.0 km
    in this dpt

6 intersecting protected areas

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

Species present

1 178 distinct species · 3 068 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 42 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 Blumenthaler Aue : 34 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 126 interactions GloBI sur 6 types (connectance 12.7%, filtre Serrano α=0.2). 11 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
45
Interactions affichées
126
Connectance
0.127
Patrimoniales
2
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

15km

Max discharge

0,5m³/s

Max Strahler

2

Segments matched

2

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