Ontologia

Rivière· 7 segments

Ralston Creek

Crosses 4 administrative regions : Adams, Gilpin, Jefferson, Johnson

rivière

Total length

69km

Max discharge

70,5m³/s

Max Strahler

5

Segments matched

7

River geography4 admin regions · 0 communes

Parent watershed

hybas-70805453401472 km²

4 administrative regions crossed (GADM L2)

  • Jefferson
    Colorado · United States
    36.7 km
    in this dpt
  • Gilpin
    Colorado · United States
    7.4 km
    in this dpt
  • Adams
    Colorado · United States
    4.8 km
    in this dpt
  • Johnson
    Iowa · United States
    3.1 km
    in this dpt

30 intersecting protected areas

21 more protected areas

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

Species present

32 distinct species · 256 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 18 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 Ralston Creek : 13 espèces reliées par 35 interactions GloBI sur 2 types (connectance 22.9%, filtre Serrano α=0.2). 5 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
18
Interactions affichées
35
Connectance
0.229
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

69km

Max discharge

70,5m³/s

Max Strahler

5

Segments matched

7

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