Ruisseau· 13 segments
Körös-éri-főcsatorna
Crosses 5 administrative regions : Jánoshalm, Kanjiža, Kiskunhalas, Mórahalm, Subotica
Total length
49km
Max discharge
0,8m³/s
Max Strahler
2
Segments matched
13
River geography5 admin regions · 0 communes
5 administrative regions crossed (GADM L2)
- KiskunhalasBács-Kiskun · Hungary54.3 kmin this dpt
- SuboticaSeverno-Bački · Serbia14.6 kmin this dpt
- MórahalmCsongrád · Hungary9.8 kmin this dpt
- JánoshalmBács-Kiskun · Hungary0.0 kmin this dpt
- KanjižaSeverno-Banatski · Serbia0.0 kmin this dpt
6 intersecting protected areas
Suboticka pescara
IUCN IVLandscape of Outstanding Qualities
SUBOTICKA PESCARA
IUCN Not ReportedEmerald Network
Déli-Homokhátság
IUCN Not ReportedSpecial Areas of Conservation (Habitats Directive)
Landscape Protection Area
LUDASKO JEZERO
IUCN Not ReportedEmerald Network
Ludasko jezero
IUCN IVNature Reserve
1 page = 1 named river (aggregation of 13 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
101 distinct species · 145 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 46 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).
Indicateurs du tissu écologique
Tissu écologique de Körös-éri-főcsatorna : 44 espèces reliées par 42 interactions GloBI sur 5 types (connectance 4.1%, filtre Serrano α=0.2). 2 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
49km
Max discharge
0,8m³/s
Max Strahler
2
Segments matched
13
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.