Ontologia

Ruisseau· 9 segments

Rems

Crosses 3 administrative regions : Ludwigsburg, Ostalbkreis, Rems-Murr-Kreis

ruisseau

Total length

78km

Max discharge

7,2m³/s

Max Strahler

3

Segments matched

9

River geography3 admin regions · 0 communes

Parent watershed

hybas-20804547201643 km²

3 administrative regions crossed (GADM L2)

  • Rems-Murr-Kreis
    Baden-Württemberg · Germany
    22.0 km
    in this dpt
  • Ostalbkreis
    Baden-Württemberg · Germany
    20.5 km
    in this dpt
  • Ludwigsburg
    Baden-Württemberg · Germany
    2.4 km
    in this dpt

23 intersecting protected areas

14 more protected areas

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

Species present

1 158 distinct species · 3 962 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

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

Espèces affichées
43
Interactions affichées
125
Connectance
0.138
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

78km

Max discharge

7,2m³/s

Max Strahler

3

Segments matched

9

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