Ontologia

Fleuve· 3 segments

Reeser Altrhein

Crosses 3 administrative regions : Kleve, Wesel, Zevenaar

fleuve

Total length

5km

Max discharge

2 353,4m³/s

Max Strahler

7

Segments matched

3

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080382190329 km²

3 administrative regions crossed (GADM L2)

  • Kleve
    Nordrhein-Westfalen · Germany
    36.5 km
    in this dpt
  • Zevenaar
    Gelderland · Netherlands
    3.2 km
    in this dpt
  • Wesel
    Nordrhein-Westfalen · Germany
    0.9 km
    in this dpt

30 intersecting protected areas

21 more protected areas

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

Species present

1 220 distinct species · 8 766 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 42 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 Reeser Altrhein : 29 espèces dont 2 patrimoniales (LR IUCN CR/EN/VU) reliées par 122 interactions GloBI sur 6 types (connectance 13.5%, filtre Serrano α=0.2). 14 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
43
Interactions affichées
122
Connectance
0.135
Patrimoniales
2
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

5km

Max discharge

2 353,4m³/s

Max Strahler

7

Segments matched

3

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