Ontologia

Ruisseau· 4 segments

Burlager-Langholter Tief

Crosses 3 administrative regions : Cloppenburg, Emsland, Leer

ruisseau

Total length

11km

Max discharge

2,6m³/s

Max Strahler

2

Segments matched

4

River geography3 admin regions · 0 communes

Parent watershed

hybas-20803465602212 km²

3 administrative regions crossed (GADM L2)

  • Leer
    Niedersachsen · Germany
    13.7 km
    in this dpt
  • Emsland
    Niedersachsen · Germany
    3.4 km
    in this dpt
  • Cloppenburg
    Niedersachsen · Germany
    0.0 km
    in this dpt

5 intersecting protected areas

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

Species present

513 distinct species · 1 427 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 Burlager-Langholter Tief : 22 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 173 interactions GloBI sur 6 types (connectance 22.2%, filtre Serrano α=0.2). 18 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

11km

Max discharge

2,6m³/s

Max Strahler

2

Segments matched

4

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