Ontologia

Ruisseau· 3 segments

Raccoon Creek

Crosses 4 administrative regions : Placer, Siskiyou, Sutter, Yolo

ruisseau

Total length

742km

Max discharge

3,8m³/s

Max Strahler

3

Segments matched

3

River geography4 admin regions · 0 communes

Parent watershed

hybas-7080570400678 km²

4 administrative regions crossed (GADM L2)

  • Sutter
    California · United States
    28.9 km
    in this dpt
  • Placer
    California · United States
    27.2 km
    in this dpt
  • Siskiyou
    California · United States
    3.5 km
    in this dpt
  • Yolo
    California · United States
    0.0 km
    in this dpt

5 intersecting protected areas

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

Species present

125 distinct species · 2 079 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 33 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 Raccoon Creek : 21 espèces reliées par 107 interactions GloBI sur 4 types (connectance 18.0%, filtre Serrano α=0.2). 14 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

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

742km

Max discharge

3,8m³/s

Max Strahler

3

Segments matched

3

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