Ontologia

Rivière

Arroio da Conserva

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

Crosses 2 administrative regions : Ipira, Piratuba

rivière

Max discharge

139,9m³/s

Max Strahler

5

Segments matched

1

River geography2 admin regions · 0 communes

Parent watershed

hybas-6080816670570 km²

2 administrative regions crossed (GADM L2)

  • Piratuba
    Santa Catarina · Brazil
    4.8 km
    in this dpt
  • Ipira
    Santa Catarina · Brazil
    4.3 km
    in this dpt

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

Species present

186 distinct species · 407 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 39 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 Arroio da Conserva : 31 espèces reliées par 39 interactions GloBI sur 6 types (connectance 5.3%, filtre Serrano α=0.2). 8 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
39
Interactions affichées
39
Connectance
0.053
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,3km

Max discharge

139,9m³/s

Max Strahler

5

Segments matched

1

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