Ontologia

Rivière

Córrego Palmito

⚠ 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 1 administrative regions : Brasília

rivière

Max discharge

22,6m³/s

Max Strahler

5

Segments matched

1

River geography1 admin regions · 0 communes

Parent watershed

hybas-60806329301171 km²

1 administrative regions crossed (GADM L2)

  • Brasília
    Distrito Federal · Brazil
    7.8 km
    in this dpt

1 intersecting protected areas

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

Species present

464 distinct species · 16 130 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 19 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 Córrego Palmito : 15 espèces reliées par 17 interactions GloBI sur 3 types (connectance 9.9%, filtre Serrano α=0.2). 4 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
19
Interactions affichées
17
Connectance
0.099
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.

42,8km

Max discharge

22,6m³/s

Max Strahler

5

Segments matched

1

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