Ontologia

Ruisseau· 14 segments

Londža

Crosses 4 administrative regions : Kutjevo, Levanjska Varoš, Pleternica, Čaglin

ruisseau

Total length

32km

Max discharge

3,7m³/s

Max Strahler

3

Segments matched

14

River geography4 admin regions · 0 communes

Parent watershed

hybas-20805484801423 km²

4 administrative regions crossed (GADM L2)

  • Čaglin
    Požeško-Slavonska · Croatia
    28.3 km
    in this dpt
  • Pleternica
    Požeško-Slavonska · Croatia
    15.9 km
    in this dpt
  • Levanjska Varoš
    Osjecko-Baranjska · Croatia
    7.3 km
    in this dpt
  • Kutjevo
    Požeško-Slavonska · Croatia
    0.7 km
    in this dpt

6 intersecting protected areas

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

Species present

22 distinct species · 26 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 14 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 Londža : 14 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 10 interactions GloBI sur 3 types (connectance 11.0%, filtre Serrano α=0.2).

Espèces affichées
14
Interactions affichées
10
Connectance
0.110
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

32km

Max discharge

3,7m³/s

Max Strahler

3

Segments matched

14

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