Ontologia

Ruisseau· 14 segments

Emmer

Crosses 3 administrative regions : Hameln-Pyrmont, Höxter, Lippe

ruisseau

Total length

63km

Max discharge

6,4m³/s

Max Strahler

3

Segments matched

14

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080376960530 km²

3 administrative regions crossed (GADM L2)

  • Höxter
    Nordrhein-Westfalen · Germany
    17.9 km
    in this dpt
  • Hameln-Pyrmont
    Niedersachsen · Germany
    14.7 km
    in this dpt
  • Lippe
    Nordrhein-Westfalen · Germany
    5.2 km
    in this dpt

30 intersecting protected areas

21 more protected areas

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

Species present

772 distinct species · 3 173 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 34 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 Emmer : 23 espèces reliées par 113 interactions GloBI sur 6 types (connectance 17.0%, filtre Serrano α=0.2). 14 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
37
Interactions affichées
113
Connectance
0.170
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

63km

Max discharge

6,4m³/s

Max Strahler

3

Segments matched

14

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