Ontologia

Ruisseau· 2 segments

Gailbach

Crosses 3 administrative regions : Kusel, Moselle, Saarpfalz-Kreis

ruisseau

Total length

25km

Max discharge

0,8m³/s

Max Strahler

2

Segments matched

2

River geography3 admin regions · 1 communes

Parent watershed

hybas-2080438400704 km²

3 administrative regions crossed (GADM L2)

  • Kusel
    Rheinland-Pfalz · Germany
    7.0 km
    in this dpt
  • Saarpfalz-Kreis
    Saarland · Germany
    1.8 km
    in this dpt
  • Moselle
    Grand Est · France
    0.0 km
    in this dpt
1 communes (L5)

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

451 distinct species · 1 883 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 31 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 Gailbach : 22 espèces reliées par 77 interactions GloBI sur 6 types (connectance 15.5%, filtre Serrano α=0.2). 10 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
32
Interactions affichées
77
Connectance
0.155
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,8m³/s

Max Strahler

2

Segments matched

2

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