Ontologia

Ruisseau

Lambsbach

Crosses 3 administrative regions : Saarpfalz-Kreis, Südwestpfalz, Zweibrücken

ruisseau

Total length

15km

Max discharge

0,3m³/s

Max Strahler

1

Segments matched

1

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080451930738 km²

3 administrative regions crossed (GADM L2)

  • Saarpfalz-Kreis
    Saarland · Germany
    7.4 km
    in this dpt
  • Südwestpfalz
    Rheinland-Pfalz · Germany
    2.9 km
    in this dpt
  • Zweibrücken
    Rheinland-Pfalz · Germany
    0.0 km
    in this dpt

19 intersecting protected areas

10 more protected areas

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

Species present

1 354 distinct species · 2 986 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 40 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 Lambsbach : 27 espèces reliées par 120 interactions GloBI sur 5 types (connectance 15.4%, filtre Serrano α=0.2). 13 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
40
Interactions affichées
120
Connectance
0.154
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

15km

Max discharge

0,3m³/s

Max Strahler

1

Segments matched

1

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