Ontologia

Ruisseau· 9 segments

Chimney Creek

Crosses 3 administrative regions : Inyo, Kern, Tulare

Endorheicruisseau

Total length

235km

Max discharge

0,8m³/s

Max Strahler

3

Segments matched

9

River geography3 admin regions · 0 communes

Parent watershed

hybas-70806449302501 km²

3 administrative regions crossed (GADM L2)

  • Tulare
    California · United States
    28.9 km
    in this dpt
  • Kern
    California · United States
    11.3 km
    in this dpt
  • Inyo
    California · United States
    0.0 km
    in this dpt

10 intersecting protected areas

1 more protected areas

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

Species present

390 distinct species · 7 542 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 46 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 Chimney Creek : 30 espèces reliées par 89 interactions GloBI sur 4 types (connectance 7.9%, filtre Serrano α=0.2). 18 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
48
Interactions affichées
89
Connectance
0.079
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

0,8m³/s

Max Strahler

3

Segments matched

9

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