Ontologia

Ruisseau· 3 segments

Tuszymka

Crosses 4 administrative regions : Dębica, Kolbuszowa, Mielec, Ropczyce-Sędziszów

ruisseau

Total length

35km

Max discharge

0,8m³/s

Max Strahler

2

Segments matched

3

River geography4 admin regions · 0 communes

Parent watershed

hybas-2080424300217 km²

4 administrative regions crossed (GADM L2)

  • Ropczyce-Sędziszów
    Podkarpackie · Poland
    27.8 km
    in this dpt
  • Mielec
    Podkarpackie · Poland
    4.4 km
    in this dpt
  • Kolbuszowa
    Podkarpackie · Poland
    1.6 km
    in this dpt
  • Dębica
    Podkarpackie · Poland
    0.0 km
    in this dpt

4 intersecting protected areas

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

Species present

196 distinct species · 446 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 28 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 Tuszymka : 14 espèces reliées par 122 interactions GloBI sur 6 types (connectance 26.2%, filtre Serrano α=0.2). 17 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
31
Interactions affichées
122
Connectance
0.262
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

35km

Max discharge

0,8m³/s

Max Strahler

2

Segments matched

3

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