Ontologia

Ruisseau· 4 segments

Tarnawka

Crosses 4 administrative regions : Bochnia, Limanowa, Przeworsk, Łańcut

ruisseau

Total length

67km

Max discharge

0,9m³/s

Max Strahler

3

Segments matched

4

River geography4 admin regions · 0 communes

Parent watershed

hybas-20804262601536 km²

4 administrative regions crossed (GADM L2)

  • Bochnia
    Małopolskie · Poland
    6.6 km
    in this dpt
  • Przeworsk
    Podkarpackie · Poland
    3.2 km
    in this dpt
  • Limanowa
    Małopolskie · Poland
    0.7 km
    in this dpt
  • Łańcut
    Podkarpackie · Poland
    0.0 km
    in this dpt

5 intersecting protected areas

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

Species present

207 distinct species · 1 531 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 40 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 Tarnawka : 34 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 87 interactions GloBI sur 5 types (connectance 11.2%, filtre Serrano α=0.2). 6 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
40
Interactions affichées
87
Connectance
0.112
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

67km

Max discharge

0,9m³/s

Max Strahler

3

Segments matched

4

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