Ontologia

Ruisseau· 2 segments

Orderville Canyon

Crosses 3 administrative regions : Coconino, Kane, Washington

ruisseau

Total length

39km

Max discharge

0,2m³/s

Max Strahler

1

Segments matched

2

River geography3 admin regions · 0 communes

Parent watershed

hybas-70806155901711 km²

3 administrative regions crossed (GADM L2)

  • Coconino
    Arizona · United States
    23.8 km
    in this dpt
  • Kane
    Utah · United States
    14.8 km
    in this dpt
  • Washington
    Utah · United States
    3.8 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

217 distinct species · 633 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 45 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 Orderville Canyon : 26 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 148 interactions GloBI sur 5 types (connectance 12.6%, filtre Serrano α=0.2). 23 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
49
Interactions affichées
148
Connectance
0.126
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

39km

Max discharge

0,2m³/s

Max Strahler

1

Segments matched

2

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