Ontologia

Ruisseau· 3 segments

Gvellikbäcken

Crosses 1 administrative regions : Arvidsjaur

ruisseau

Total length

6km

Max discharge

0,5m³/s

Max Strahler

2

Segments matched

3

River geography1 admin regions · 0 communes

Parent watershed

hybas-2080152810534 km²

1 administrative regions crossed (GADM L2)

4 intersecting protected areas

  • Ledfat

    IUCN IV

    Nature conservation agreement

  • A576829

    IUCN Not Applicable

    Voluntary set-aside areas

  • A547359

    IUCN Not Applicable

    Voluntary set-aside areas

  • A549350

    IUCN Not Applicable

    Voluntary set-aside areas

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

Species present

128 distinct species · 150 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 37 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 Gvellikbäcken : 25 espèces reliées par 56 interactions GloBI sur 5 types (connectance 8.4%, filtre Serrano α=0.2). 12 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
37
Interactions affichées
56
Connectance
0.084
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

6km

Max discharge

0,5m³/s

Max Strahler

2

Segments matched

3

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