Rivière· 84 segments
Rio Cabaçal
Crosses 12 administrative regions : Araputanga, Curvelândia, Cáceres, Lambari D'Oeste, Mirassol d'Oeste +7
Total length
358km
Max discharge
80,7m³/s
Max Strahler
5
Segments matched
84
River geography12 admin regions · 0 communes
12 administrative regions crossed (GADM L2)
- AraputangaMato Grosso · Brazil51.7 kmin this dpt
- Lambari D'OesteMato Grosso · Brazil50.3 kmin this dpt
- CáceresMato Grosso · Brazil43.2 kmin this dpt
- Reserva do CabaçalMato Grosso · Brazil42.5 kmin this dpt
- CurvelândiaMato Grosso · Brazil30.3 kmin this dpt
- VeríssimoMinas Gerais · Brazil25.3 kmin this dpt
- Rio BrancoMato Grosso · Brazil24.1 kmin this dpt
- São José dos Quatro MarcosMato Grosso · Brazil17.9 kmin this dpt
- Mirassol d'OesteMato Grosso · Brazil10.5 kmin this dpt
- UberabaMinas Gerais · Brazil9.6 kmin this dpt
- PrataMinas Gerais · Brazil7.5 kmin this dpt
- UberlândiaMinas Gerais · Brazil6.1 kmin this dpt
1 page = 1 named river (aggregation of 84 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
51 distinct species · 134 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 22 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).
Indicateurs du tissu écologique
Tissu écologique de Rio Cabaçal : 21 espèces reliées par 17 interactions GloBI sur 2 types (connectance 7.4%, filtre Serrano α=0.2). 1 bulle taxonomique (cascade genre/famille GloBI, ≥3 espèces).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
358km
Max discharge
80,7m³/s
Max Strahler
5
Segments matched
84
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.