Ontologia

Ruisseau· 2 segments

Dankácky potok

Crosses 2 administrative regions : Myjava, Senica

ruisseau

Total length

8km

Max discharge

0,7m³/s

Max Strahler

2

Segments matched

2

River geography2 admin regions · 0 communes

Parent watershed

hybas-2080464110795 km²

2 administrative regions crossed (GADM L2)

  • Senica
    Trnavský · Slovakia
    6.5 km
    in this dpt
  • Myjava
    Trenčiansky · Slovakia
    0.0 km
    in this dpt

2 intersecting protected areas

  • Rieka Myjava

    IUCN III

    Nature Monument / Private Nature Monument

  • Horný tok Myjavy

    IUCN Not Reported

    Special Areas of Conservation (Habitats Directive)

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

Species present

173 distinct species · 348 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 29 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 Dankácky potok : 21 espèces reliées par 69 interactions GloBI sur 6 types (connectance 15.9%, filtre Serrano α=0.2). 9 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
30
Interactions affichées
69
Connectance
0.159
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

8km

Max discharge

0,7m³/s

Max Strahler

2

Segments matched

2

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