Rivière· 13 segments
Mokelumne River
Crosses 4 administrative regions : Amador, Calaveras, Sacramento, San Joaquin
Total length
128km
Max discharge
66,6m³/s
Max Strahler
5
Segments matched
13
River geography4 admin regions · 0 communes
4 administrative regions crossed (GADM L2)
- San JoaquinCalifornia · United States58.6 kmin this dpt
- SacramentoCalifornia · United States9.4 kmin this dpt
- AmadorCalifornia · United States7.7 kmin this dpt
- CalaverasCalifornia · United States5.1 kmin this dpt
9 intersecting protected areas
Cosumnes River
IUCN VPreserve
Staten Island
IUCN VPrivate Conservation
Cosumnes River
IUCN VEcological Reserve
Bean Ranch
IUCN VPrivate Conservation
Cosumnes Floodplain
IUCN Not AssignedMitigation Bank
Grizzly Slough
IUCN Not AssignedConservation Easement
Galeazzi Farm
IUCN Not AssignedConservation Easement
Lodi Lake Park and
IUCN VNature Area
Wilderness Area
1 page = 1 named river (aggregation of 13 HydroRIVERS v10 segments). Spatial join cached after first hit.
Species present
124 distinct species · 351 observations
Source: GBIF Occurrence snapshot 2026-05-01.
Ecological tissue
Sample of 43 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).
Indicateurs du tissu écologique
Tissu écologique de Mokelumne River : 30 espèces reliées par 134 interactions GloBI sur 4 types (connectance 14.8%, filtre Serrano α=0.2). 13 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).
Comparaison sur la connectance du réseau local complet vs distribution nationale (toutes les communes françaises).
Hydrology (HydroRIVERS v10)
Total length
128km
Max discharge
66,6m³/s
Max Strahler
5
Segments matched
13
HydroRIVERS v1.0 (Lehner et al. 2019) aggregated by name + main_riv → 1 entity = 1 named river.