Ontologia

Ruisseau· 2 segments

Torrente Lodrone

Crosses 1 administrative regions : Trento

ruisseau

Total length

2km

Max discharge

0,7m³/s

Max Strahler

2

Segments matched

2

River geography1 admin regions · 0 communes

Parent watershed

hybas-20805423601358 km²

1 administrative regions crossed (GADM L2)

  • Trento
    Trentino-Alto Adige · Italy
    4.3 km
    in this dpt

2 intersecting protected areas

  • Monte Zugna

    IUCN Not Reported

    Special Areas of Conservation (Habitats Directive)

  • Talpina - Brentonico

    IUCN Not Reported

    Special Areas of Conservation (Habitats Directive)

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

Species present

636 distinct species · 1 941 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 42 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 Torrente Lodrone : 31 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 103 interactions GloBI sur 7 types (connectance 12.0%, filtre Serrano α=0.2). 11 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
42
Interactions affichées
103
Connectance
0.120
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

2km

Max discharge

0,7m³/s

Max Strahler

2

Segments matched

2

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