Ontologia

Ruisseau

Lauterburerbaach

Crosses 2 administrative regions : Echternach, Eifelkreis Bitburg-Prüm

ruisseau

Total length

10km

Max discharge

0,3m³/s

Max Strahler

1

Segments matched

1

River geography2 admin regions · 0 communes

Parent watershed

hybas-2080434150291 km²

2 administrative regions crossed (GADM L2)

  • Echternach
    Grevenmacher · Luxembourg
    5.3 km
    in this dpt
  • Eifelkreis Bitburg-Prüm
    Rheinland-Pfalz · Germany
    0.0 km
    in this dpt

9 intersecting protected areas

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

Species present

2 653 distinct species · 26 104 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 33 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 Lauterburerbaach : 25 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) + 8 bulles famille, 52 interactions GloBI documentées sur 6 types (connectance 9.8%, filtre Serrano α=0.2). Les 8 bulles regroupent des espèces visuellement absorbées par famille (≥3 espèces visibles).

Espèces affichées
33
Interactions affichées
52
Connectance
0.099
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

10km

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.