Name: i06_Bathy_NCRO_20180621_TomPaineSlough

Display Field: Feature_Class_Name

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: <DIV STYLE="text-align:Left;"><P STYLE="margin:0 0 11 0;"><SPAN><SPAN>May 2013 - performed by Kjeldsen, Sinnock &amp; Neudeck Inc. (KSN) at the request of Reclamation District 2058 to assess bed elevation change versus 2004 and 2005 DWR surveys. The KSN survey consisted one single-beam sonar along-axis profile that included direct GPS observation points through the non-navigable, weed-filled eastern reach of the slough (starting at about cross section 8). The nine cross sections were surveyed with direct GPS observations of limited data density due to the method used.</SPAN></SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN><SPAN>January 2018 – performed by DWR, North Central Region Office at the request of Bay Delta Office to assess channel elevations. This survey was intended to fully cover the target area with three along-axis profiles and the nine cross sections. All data was collected with sonar.</SPAN></SPAN></P><P STYLE="margin:0 0 11 0;"><SPAN><SPAN>The 2013 KSN dataset was very sparse in areas, with as much as 125 feet separating points along the profile, on average, and as few as five observations within the channel banks for cross sections. The 2018 DWR survey had much improved data density, but the comparison is necessarily limited by the availability of data from 2013. An estimate of bed elevation change in Tom Paine Slough along the centerline was made by subtracting 2013 elevation from calculated 2018 elevation for points that were within a 5-foot radius of one another according to an algorithm calculating the weighted average of nearest neighbor points (WANN). Change for the cross sections was analyzed separately. No attempt was made to produce an estimate of change for the whole of Tom Paine Slough because the data from 2013 only contained one centerline and the cross sections were too far apart to reasonably interpolate a surface. Change along the 2013 centerline was further broken down by 3,000 foot segments along the profile to examine change more locally. To prevent under-weighting areas with fewer qualifying data points, all statistics were calculated on an evenly-spaced dataset, with change in elevation interpolated to one foot intervals. Analysis of change along the centerline indicates a small, but significant, net deposition of sediment in Tom Paine Slough between 2013 and 2018. Sediment trends vary locally and are sensitive to differences in boat path 1, but suggest increasing deposition from west to east, with a short reach of scour near cross section 7. Since accuracy for two surveys was 0.24 ft and 0.16 ft for KSN and DWR, respectively, as much as 0.4 ft of difference could be explained by systematic survey error. However, this does not explain the increasing trend of deposition along Tom Paine Slough. The difference in data collection methods used by KSN — sonar for most of the slough, with direct GPS observation in weedy areas — could also be responsible for some of the increase seen towards the eastern end of the survey. There was a much higher mean elevation change for KSN points collected by direct observation (1.1 ft) compared to points collected by sonar (0.6 ft). Despite this, it is entirely possible that this observed difference between collection techniques was caused by an actual trend in deposition. It appears most likely that both are true: some of the increase in elevation towards the east is due to differing collection techniques, but most of it probably reflects an actual increase in elevation. Mean change in elevation and change in cross-sectional area was calculated for each individual cross section. Because the 2013 KSN cross sections were all conducted by labor intensive manual GPS observations, data points within the channel were sparse, but land elevations beyond the channel banks were included. The 2018 DWR survey was conducted by sonar within the navigable channel limits, and thus had much greater data density within the channel, but without land elevations beyond the banks.</SPAN></SPAN></P></DIV>

Copyright Text: California Department of Water Resources (DWR), North Central Region Office (NCRO).

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

XMin: -1.35158668509E7
YMin: 4547568.762400001
XMax: -1.35122758812E7
YMax: 4549060.5964
Spatial Reference: 102100  (3857)

Drawing Info:

Renderer:
Class Breaks Renderer:
Field: Z
Min. Value: -9.223372036854776E18
ClassBreakInfos:
• Class Maximum Value: 9223372036854775807
  Label: N/A
  Description: N/A
  Symbol:
  Style: esriSMSCircle
  Color: [130, 130, 130, 255]
  Size: 2.0
  Angle: 0.0
  XOffset: 0
  YOffset: 0
  Outline:
  [0, 0, 0, 255] Width: 0
Transparency: 0
Labeling Info:

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false
Supports Percentile Statistics: true
Supports Having Clause: true
Supports Count Distinct: true
Supports Time Relation: true
Supports Sql Format: false
Supports Query Analytic: true
Supports Query With Current User: true

HasZ: true

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• Y ( type: esriFieldTypeDouble, alias: Latitude )
• X ( type: esriFieldTypeDouble, alias: Longitude )
• Z ( type: esriFieldTypeDouble, alias: Elevation )
• Date_Data_Refers_To ( type: esriFieldTypeString, alias: Date Data Refers To, length: 255 )
• source ( type: esriFieldTypeString, alias: Source, length: 255 )
• comments ( type: esriFieldTypeString, alias: Comments, length: 255 )
• Last_Modified_Date ( type: esriFieldTypeString, alias: Last Modified Date, length: 255 )
• Modified_By ( type: esriFieldTypeString, alias: Modified By, length: 255 )
• Data_Format ( type: esriFieldTypeString, alias: Data Format, length: 255 )
• Data_Equipment_Type ( type: esriFieldTypeString, alias: Sonar, length: 255 )
• Date_Started ( type: esriFieldTypeString, alias: Date Field Work Started, length: 255 )
• Date_Complete ( type: esriFieldTypeString, alias: Date Field Work Complete, length: 255 )
• Feature_Class_Name ( type: esriFieldTypeString, alias: Feature Class Name, length: 255 )
• Survey_Report ( type: esriFieldTypeString, alias: Survey Report, length: 255 )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )

Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata