Ontologia

Rivière· 49 segments

Escalante River

Crosses 3 administrative regions : Garfield, Kane, San Juan

rivière

Total length

213km

Max discharge

2,7m³/s

Max Strahler

4

Segments matched

49

River geography3 admin regions · 0 communes

Parent watershed

hybas-7080598960114 km²

3 administrative regions crossed (GADM L2)

  • Garfield
    Utah · United States
    104.8 km
    in this dpt
  • Kane
    Utah · United States
    57.0 km
    in this dpt
  • San Juan
    Utah · United States
    0.5 km
    in this dpt

4 intersecting protected areas

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

Species present

144 distinct species · 750 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 Escalante River : 31 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 110 interactions GloBI sur 4 types (connectance 12.2%, filtre Serrano α=0.2). 12 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
43
Interactions affichées
110
Connectance
0.122
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

213km

Max discharge

2,7m³/s

Max Strahler

4

Segments matched

49

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