Ontologia

Ruisseau· 2 segments

Mosbach

Crosses 3 administrative regions : Mainz, Rhein-Sieg-Kreis, Wiesbaden

ruisseau

Total length

20km

Max discharge

16,7m³/s

Max Strahler

3

Segments matched

2

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080410660326 km²

3 administrative regions crossed (GADM L2)

  • Rhein-Sieg-Kreis
    Nordrhein-Westfalen · Germany
    8.4 km
    in this dpt
  • Wiesbaden
    Hessen · Germany
    3.9 km
    in this dpt
  • Mainz
    Rheinland-Pfalz · Germany
    0.0 km
    in this dpt

28 intersecting protected areas

19 more protected areas

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

Species present

556 distinct species · 1 531 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 44 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 Mosbach : 31 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 102 interactions GloBI sur 7 types (connectance 10.3%, filtre Serrano α=0.2). 14 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
45
Interactions affichées
102
Connectance
0.103
Patrimoniales
1
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

20km

Max discharge

16,7m³/s

Max Strahler

3

Segments matched

2

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