Ontologia

Ruisseau· 4 segments

Rio Piraquê-Açu

Crosses 3 administrative regions : Aracruz, Ibiraçu, João Neiva

ruisseau

Total length

87km

Max discharge

3,8m³/s

Max Strahler

3

Segments matched

4

River geography3 admin regions · 0 communes

Parent watershed

hybas-6080013490390 km²

3 administrative regions crossed (GADM L2)

  • Aracruz
    Espírito Santo · Brazil
    34.8 km
    in this dpt
  • João Neiva
    Espírito Santo · Brazil
    10.7 km
    in this dpt
  • Ibiraçu
    Espírito Santo · Brazil
    1.6 km
    in this dpt

6 intersecting protected areas

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

Species present

473 distinct species · 1 646 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 Piraquê-Açu : 26 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 27 interactions GloBI sur 2 types (connectance 5.8%, filtre Serrano α=0.2). 5 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

87km

Max discharge

3,8m³/s

Max Strahler

3

Segments matched

4

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