Ontologia

Rivière· 22 segments

Roaring Fork River

Crosses 3 administrative regions : Eagle, Garfield, Pitkin

rivière

Total length

111km

Max discharge

21,3m³/s

Max Strahler

4

Segments matched

22

River geography3 admin regions · 0 communes

Parent watershed

hybas-70805566201308 km²

3 administrative regions crossed (GADM L2)

  • Pitkin
    Colorado · United States
    48.4 km
    in this dpt
  • Garfield
    Colorado · United States
    29.2 km
    in this dpt
  • Eagle
    Colorado · United States
    11.2 km
    in this dpt

30 intersecting protected areas

21 more protected areas

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

Species present

276 distinct species · 6 576 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 36 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 Roaring Fork River : 23 espèces reliées par 114 interactions GloBI sur 5 types (connectance 18.1%, filtre Serrano α=0.2). 13 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
36
Interactions affichées
114
Connectance
0.181
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

111km

Max discharge

21,3m³/s

Max Strahler

4

Segments matched

22

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