Ontologia

Rivière· 62 segments

Apishapa River

Crosses 4 administrative regions : Crowley, Las Animas, Otero, Pueblo

rivière

Total length

235km

Max discharge

1,5m³/s

Max Strahler

4

Segments matched

62

River geography4 admin regions · 0 communes

Parent watershed

hybas-7080597580324 km²

4 administrative regions crossed (GADM L2)

  • Las Animas
    Colorado · United States
    226.2 km
    in this dpt
  • Otero
    Colorado · United States
    68.3 km
    in this dpt
  • Pueblo
    Colorado · United States
    63.1 km
    in this dpt
  • Crowley
    Colorado · United States
    0.3 km
    in this dpt

4 intersecting protected areas

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

Species present

33 distinct species · 107 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 16 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 Apishapa River : 15 espèces reliées par 17 interactions GloBI sur 2 types (connectance 12.5%, filtre Serrano α=0.2). 2 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
17
Interactions affichées
17
Connectance
0.125
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

235km

Max discharge

1,5m³/s

Max Strahler

4

Segments matched

62

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