Ontologia

Rivière· 8 segments

Варежка

Crosses 4 administrative regions : Danilovskiy rayon, Kamenskiy rayon, Lyubimskiy rayon, Pachelmskiy rayon

rivière

Total length

95km

Max discharge

5,5m³/s

Max Strahler

4

Segments matched

8

River geography4 admin regions · 0 communes

Parent watershed

hybas-20803379002365 km²

4 administrative regions crossed (GADM L2)

  • Kamenskiy rayon
    Penza · Russia
    25.6 km
    in this dpt
  • Pachelmskiy rayon
    Penza · Russia
    19.8 km
    in this dpt
  • Danilovskiy rayon
    Yaroslavl' · Russia
    4.1 km
    in this dpt
  • Lyubimskiy rayon
    Yaroslavl' · Russia
    0.1 km
    in this dpt

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

Species present

45 distinct species · 45 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 10 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 Варежка : 9 espèces reliées par 7 interactions GloBI sur 2 types (connectance 15.6%, filtre Serrano α=0.2). 1 bulle taxonomique (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
10
Interactions affichées
7
Connectance
0.156
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

95km

Max discharge

5,5m³/s

Max Strahler

4

Segments matched

8

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