Ontologia

Ruisseau· 5 segments

Rio do Salto

Crosses 4 administrative regions : Anitápolis, Jaguaruna, Sangão, Treze de Maio

ruisseau

Total length

306km

Max discharge

3,1m³/s

Max Strahler

2

Segments matched

5

River geography4 admin regions · 0 communes

Parent watershed

hybas-6080830490282 km²

4 administrative regions crossed (GADM L2)

  • Treze de Maio
    Santa Catarina · Brazil
    12.1 km
    in this dpt
  • Jaguaruna
    Santa Catarina · Brazil
    6.2 km
    in this dpt
  • Anitápolis
    Santa Catarina · Brazil
    1.4 km
    in this dpt
  • Sangão
    Santa Catarina · Brazil
    0.0 km
    in this dpt

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

Species present

162 distinct species · 643 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 31 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 Rio do Salto : 28 espèces reliées par 27 interactions GloBI sur 3 types (connectance 5.8%, filtre Serrano α=0.2). 3 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

306km

Max discharge

3,1m³/s

Max Strahler

2

Segments matched

5

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