Ontologia

Ruisseau· 3 segments

Leutra

Crosses 2 administrative regions : Jena, Weimarer Land

ruisseau

Total length

22km

Max discharge

0,2m³/s

Max Strahler

2

Segments matched

3

River geography2 admin regions · 0 communes

Parent watershed

hybas-2080402200361 km²

2 administrative regions crossed (GADM L2)

  • Jena
    Thüringen · Germany
    6.6 km
    in this dpt
  • Weimarer Land
    Thüringen · Germany
    0.0 km
    in this dpt

11 intersecting protected areas

2 more protected areas

  • Oberaue

    IUCN V

    Landscape Protection Area

  • Kirche Cospeda

    IUCN Not Reported

    Special Areas of Conservation (Habitats Directive)

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

Species present

3 404 distinct species · 58 774 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 38 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 Leutra : 27 espèces reliées par 93 interactions GloBI sur 5 types (connectance 12.6%, filtre Serrano α=0.2). 12 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
39
Interactions affichées
93
Connectance
0.126
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

22km

Max discharge

0,2m³/s

Max Strahler

2

Segments matched

3

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