Ontologia

Rivière· 26 segments

North Fork Mokelumne River

Crosses 3 administrative regions : Alpine, Amador, Calaveras

rivière

Total length

103km

Max discharge

25,2m³/s

Max Strahler

4

Segments matched

26

River geography3 admin regions · 0 communes

Parent watershed

hybas-7080580010967 km²

3 administrative regions crossed (GADM L2)

  • Amador
    California · United States
    71.8 km
    in this dpt
  • Calaveras
    California · United States
    46.4 km
    in this dpt
  • Alpine
    California · United States
    37.7 km
    in this dpt

3 intersecting protected areas

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

Species present

65 distinct species · 107 observations

Source: GBIF Occurrence snapshot 2026-05-01.

Ecological tissue

Sample of 21 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 North Fork Mokelumne River : 18 espèces reliées par 19 interactions GloBI sur 3 types (connectance 9.0%, filtre Serrano α=0.2). 3 bulles taxonomiques (cascade genre/famille GloBI, ≥3 espèces).

Espèces affichées
21
Interactions affichées
19
Connectance
0.090
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

103km

Max discharge

25,2m³/s

Max Strahler

4

Segments matched

26

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