Ontologia

Ruisseau· 2 segments

Старий Ботар

Crosses 2 administrative regions : Fehérgyarmat, Vynohradivs'kyi

ruisseau

Total length

16km

Max discharge

3,4m³/s

Max Strahler

2

Segments matched

2

River geography2 admin regions · 0 communes

Parent watershed

hybas-2080479240362 km²

2 administrative regions crossed (GADM L2)

4 intersecting protected areas

  • Szatmár-Bereg

    IUCN Not Reported

    Special Protection Area (Birds Directive)

  • Felső-Tisza

    IUCN Not Reported

    Special Areas of Conservation (Habitats Directive)

  • Botar

    IUCN Not Reported

    Emerald Network

  • Botar

    IUCN Not Reported

    Zakaznyk

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

Species present

92 distinct species · 133 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 44 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 Старий Ботар : 37 espèces reliées par 78 interactions GloBI sur 5 types (connectance 8.2%, filtre Serrano α=0.2). 7 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
44
Interactions affichées
78
Connectance
0.083
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

16km

Max discharge

3,4m³/s

Max Strahler

2

Segments matched

2

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