Ontologia

Ruisseau

Wiebelsbach

Crosses 3 administrative regions : Germersheim, Karlsruhe, Karlsruhe (Stadtkreis)

ruisseau

Total length

20km

Max discharge

1,2m³/s

Max Strahler

1

Segments matched

1

River geography3 admin regions · 0 communes

Parent watershed

hybas-20804478401980 km²

3 administrative regions crossed (GADM L2)

  • Germersheim
    Rheinland-Pfalz · Germany
    24.1 km
    in this dpt
  • Karlsruhe
    Baden-Württemberg · Germany
    0.0 km
    in this dpt
  • Karlsruhe (Stadtkreis)
    Baden-Württemberg · Germany
    0.0 km
    in this dpt

15 intersecting protected areas

6 more protected areas

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

Species present

1 820 distinct species · 7 209 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 Wiebelsbach : 32 espèces reliées par 111 interactions GloBI sur 6 types (connectance 12.9%, filtre Serrano α=0.2). 10 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
42
Interactions affichées
111
Connectance
0.129
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

20km

Max discharge

1,2m³/s

Max Strahler

1

Segments matched

1

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