Ontologia

Ruisseau· 14 segments

Coyote Creek

Crosses 3 administrative regions : Archuleta, Kane, Rio Arriba

ruisseau

Total length

808km

Max discharge

0,9m³/s

Max Strahler

3

Segments matched

14

River geography3 admin regions · 0 communes

Parent watershed

hybas-70806134801198 km²

3 administrative regions crossed (GADM L2)

  • Kane
    Utah · United States
    35.0 km
    in this dpt
  • Archuleta
    Colorado · United States
    17.2 km
    in this dpt
  • Rio Arriba
    New Mexico · United States
    0.6 km
    in this dpt

2 intersecting protected areas

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

Species present

23 distinct species · 61 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 13 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 Coyote Creek : 12 espèces dont 1 patrimoniale (LR IUCN CR/EN/VU) reliées par 8 interactions GloBI sur 3 types (connectance 10.3%, filtre Serrano α=0.2). 1 bulle taxonomique (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
13
Interactions affichées
8
Connectance
0.103
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

808km

Max discharge

0,9m³/s

Max Strahler

3

Segments matched

14

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