Ontologia

Ruisseau· 2 segments

Río Eslava

Crosses 3 administrative regions : La Magdalena Contreras, Tlalpan, Álvaro Obregón

Endorheicruisseau

Total length

6km

Max discharge

0,3m³/s

Max Strahler

1

Segments matched

2

River geography3 admin regions · 0 communes

Parent watershed

hybas-70800749901757 km²

3 administrative regions crossed (GADM L2)

  • La Magdalena Contreras
    Distrito Federal · México
    12.5 km
    in this dpt
  • Tlalpan
    Distrito Federal · México
    6.4 km
    in this dpt
  • Álvaro Obregón
    Distrito Federal · México
    2.1 km
    in this dpt

5 intersecting protected areas

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

Species present

1 730 distinct species · 96 491 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 41 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 Río Eslava : 32 espèces reliées par 64 interactions GloBI sur 5 types (connectance 7.8%, filtre Serrano α=0.2). 9 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
41
Interactions affichées
64
Connectance
0.078
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

6km

Max discharge

0,3m³/s

Max Strahler

1

Segments matched

2

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