Ontologia

Rivière· 64 segments

Tana - Deatnu - Teno

Crosses 3 administrative regions : Karasjok, Lapland, Tana

rivière

Total length

208km

Max discharge

196m³/s

Max Strahler

5

Segments matched

64

River geography3 admin regions · 0 communes

Parent watershed

hybas-20801161102594 km²

3 administrative regions crossed (GADM L2)

  • Tana
    Finnmark · Norway
    110.7 km
    in this dpt
  • Lapland
    Lapland · Finland
    107.0 km
    in this dpt
  • Karasjok
    Finnmark · Norway
    23.4 km
    in this dpt

11 intersecting protected areas

2 more protected areas

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

Species present

390 distinct species · 2 586 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 30 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 Tana - Deatnu - Teno : 22 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 55 interactions GloBI sur 5 types (connectance 11.8%, filtre Serrano α=0.2). 9 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
31
Interactions affichées
55
Connectance
0.118
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

208km

Max discharge

196,0m³/s

Max Strahler

5

Segments matched

64

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