Ontologia

Rivière· 12 segments

Beaver Creek

Crosses 4 administrative regions : Calaveras, Lassen, Shasta, Tuolumne

rivière

Total length

7 489km

Max discharge

4m³/s

Max Strahler

5

Segments matched

12

River geography4 admin regions · 0 communes

Parent watershed

hybas-7080515720562 km²

4 administrative regions crossed (GADM L2)

  • Lassen
    California · United States
    48.4 km
    in this dpt
  • Tuolumne
    California · United States
    10.8 km
    in this dpt
  • Shasta
    California · United States
    6.5 km
    in this dpt
  • Calaveras
    California · United States
    0.1 km
    in this dpt

1 intersecting protected areas

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

Species present

170 distinct species · 882 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 55 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 Beaver Creek : 40 espèces reliées par 99 interactions GloBI sur 5 types (connectance 6.4%, filtre Serrano α=0.2). 16 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
56
Interactions affichées
99
Connectance
0.064
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

7 489km

Max discharge

4,0m³/s

Max Strahler

5

Segments matched

12

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