Ontologia

Rivière· 15 segments

Nidelva

Crosses 3 administrative regions : Klæbu, Melhus, Trondheim

rivière

Total length

113km

Max discharge

84,5m³/s

Max Strahler

5

Segments matched

15

River geography3 admin regions · 0 communes

Parent watershed

hybas-2080036360786 km²

3 administrative regions crossed (GADM L2)

  • Klæbu
    Sør-Trøndelag · Norway
    21.2 km
    in this dpt
  • Trondheim
    Sør-Trøndelag · Norway
    10.3 km
    in this dpt
  • Melhus
    Sør-Trøndelag · Norway
    0.0 km
    in this dpt

2 intersecting protected areas

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

Species present

1 789 distinct species · 25 396 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

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

Espèces affichées
38
Interactions affichées
93
Connectance
0.132
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

113km

Max discharge

84,5m³/s

Max Strahler

5

Segments matched

15

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