Extended San Joaquin River Model - PowerPoint PPT Presentation

About This Presentation
Title:

Extended San Joaquin River Model

Description:

Extended San Joaquin River Model – PowerPoint PPT presentation

Number of Views:33
Avg rating:3.0/5.0
Slides: 28
Provided by: khhucke
Learn more at: http://www.sjrdotmdl.org
Category:
Tags: extended | joaquin | model | paar | river | san

less

Transcript and Presenter's Notes

Title: Extended San Joaquin River Model


1
Extended San Joaquin River Model
  • Kate Huckelbridge
  • Nigel Quinn
  • 2/21/06

2
Objectives
  • Extend existing SJR model network to include
  • Stanislaus River (SJR to Goodwin dam)
  • Tuolumne River (SJR to LaGrange dam)
  • Merced River (SJR to Crocker-Huffman dam)
  • Salt Slough (SJR to gauging station at Hwy 165)
  • Mud Slough (SJR to gauging station near Gustine)

3
Objectives (cont.)
  • Incorporate flow and salinity information into
    extended SJR model for
  • East side irrigation districts discharging to
    east side tributaries
  • West side creeks and drains (based on data
    collection efforts)

4
East Side Tributaries
5
General Process
  • Original Plan
  • Convert cross-sectional data into DSM2 format
  • Update DSM2 input files to incorporate geometry,
    flow and EC data for east side tributaries
  • Run and calibrate model
  • Problems with DSM2 approach
  • Difficulty in making code changes
  • Lack of model documentation
  • Difficulty with consistent model execution
  • New Plan
  • Convert cross-sectional data into WARMF format
  • Original format different for different data
    sources (i.e., USACE in station/elevation format)
  • WARMF format stage/width
  • Turn files over to Systech for incorporation into
    SJR model

6
Stanislaus River
  • Geometry
  • USACE Comprehensive Study (RM 1-14)
  • 36 cross sections converted to 6 representative
    cross-sections
  • Channel segment length averages 1.9 river miles
  • Still Need Data for RM 14 RM 56 (Goodwin Dam)
  • Flow/EC
  • Gauge data already incorporated
  • Discharge data from MID
  • Daily and monthly average data for 2000 2005
    for Lateral 6, Main Canal, Main Drain (via Miller
    Lake), Main Canal at Spenker

7
Tuolumne River
  • Geometry
  • USACE comprehensive Study (RM 1 RM 24)
  • 92 cross sections converted to 17 representative
    cross-sections
  • Channel segment length averages 1.3 river miles
  • RMA/TriDam HEC-RAS study (still awaiting data)
  • Still need data for RM 24 RM 52 (LaGrange Dam)
  • Flow/EC
  • Gauge data already incorporated
  • Discharge data from MID, TID
  • MID Daily and monthly average data for 2000
    2005 for Lateral 2 _at_ Santa Fe, Lateral 2, Lateral
    5, Main Waterford Canal
  • TID Daily data for 2000 2004 for Faith Home
    Spill

8
Merced River
  • Geometry
  • USACE comprehensive Study (RM 1 RM 17)
  • 56 cross sections converted to 11 representative
    cross-sections
  • Channel segment length averages 1.8 river miles
  • RMA/TriDam HEC-RAS study (RM 1- RM 52
    (Crocker-Huffman Dam))
  • Awaiting thalweg data for conversion to WARMF
    format
  • RM 21 RM 36.4 based on data from 1968
  • Still need data for RM 21 RM 36.4
  • Flow/EC
  • Gauge data already incorporated
  • Discharges from TID, Merced Irrigation District
  • TID Daily data for 2000 2004 for Highline and
    Lower Stevenson spills
  • Merced Merced flows below Crocker-Huffman Dam
    average flows during irrigation season for spills
    near Cressy

9
San Joaquin River
  • TID daily data from 2000 to 2004 (replaces
    monthly data currently in DSM2)
  • MID - daily data from 2000 to 2004 (replaces
    monthly data currently in DSM2)

10
Mud Slough
  • Geometry
  • Summers Engineering surveys (RM 1 RM 5.5)
  • 25 cross-sections converted to 4 representative
    cross-sections
  • Channel segment length averages 1.4 river miles
  • Flow/EC
  • Gauge data already incorporated

11
Salt Slough
  • Geometry
  • LBNL bathymetry surveys (RM 1 RM 6.4)
  • 5 representative cross-sections
  • Channel segment length averages 1.3 river miles
  • Flow/EC
  • Gauge data already incorporated

12
Salt Slough Surveys
13
Salt Slough Surveys
14
West Side Flows
15
General Process
  • Obtain flow and EC data from data collection team
  • Only 2005 data (January November) available
    (December values calculated as an average of
    January and November values)
  • Develop monthly relationships based on 15-minute
    data
  • Compare data with current DSM2 inputs

16
West Side Data
  • Del Puerto Creek
  • Hospital Creek
  • Ingram Creek
  • Moran Drain
  • Marshall Drain
  • Spanish Drain
  • Westley Wasteway
  • New Jerusalem
  • Ramona Lake

17
West Side Flows for 2005
18
West Side EC for 2005
19
Del Puerto Creek Flow
  • 2005 Data quality fair
  • 2005 flows capped at 200cfs (to remove erroneous
    data)
  • Seasonal peaks differ in time and magnitude from
    DSM2 data (USGS)

20
Del Puerto Creek EC
  • 2005 Data quality good
  • DSM2 assumed same EC as Orestimba Creek
  • Relatively good agreement with DSM2 data

21
Hospital and Ingram Creek Flow
  • 2005 Data quality very good
  • Flow data for Ingram Creek prior to June 15
    determined based on flow relationship with
    Hospital Creek
  • DSM2 combined flow for Hospital and Ingram Creek
  • DSM2 calculated flows based on relationship with
    Del Puerto Creek
  • Average monthly values much lower than DSM2
    except for July-September
  • Timing of Peaks is off

22
Hospital and Ingram Creek EC
  • 2005 Data quality very good
  • DSM2 assumed same EC as Orestimba Creek
  • EC monthly averages for Hospital Creek are lower
    than DSM2
  • EC monthly averages for Ingram Creek are higher
    than DSM2

23
Marshall, Moran and Spanish Drains
  • Not included in original SJR model
  • Flow Data for Spanish Drain not yet available

24
Ramona Lake
  • Flow data not yet available

25
Westley Wasteway
  • Negative flows in 2005 field data were assumed to
    be zero
  • DSM2 assumed a constant flow (2 cfs) and EC (1000
    uS/cm) for Westley

26
New Jerusalem
  • EC data between 11/26 and 12/31 was discarded
    (mostly zero values)
  • Flow data not yet available

27
Next Steps
  • Transfer data to Systech
  • Continue assessing data quality
  • Improve model calibration, focusing on east and
    west side drainage, river diversions and
    groundwater accretions
  • Address channel geometry data gaps for
    Stanislaus, Tuolumne and Merced Rivers
Write a Comment
User Comments (0)
About PowerShow.com