Ontologia

Rivière

Bergdøla

⚠ Partial coverage : only 1 named segment matched so far. The real rivière extends much further (Strahler order 6 indicates a major river). Cross-source ingest in progress — values below reflect only the matched segment.

Crosses 2 administrative regions : Ringebu, Øyer

rivière

Max discharge

201,1m³/s

Max Strahler

6

Segments matched

1

River geography2 admin regions · 0 communes

Parent watershed

hybas-20802174201908 km²

2 administrative regions crossed (GADM L2)

  • Øyer
    Oppland · Norway
    5.2 km
    in this dpt
  • Ringebu
    Oppland · Norway
    4.9 km
    in this dpt

4 intersecting protected areas

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

Species present

2 236 distinct species · 9 939 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 Bergdøla : 6 espèces reliées par 9 interactions GloBI sur 1 type (connectance 20.0%, filtre Serrano α=0.2). 4 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

Matched len.

4,1km

Max discharge

201,1m³/s

Max Strahler

6

Segments matched

1

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