Name: Revetment - RM 243 to 80

Display Field: STREAMNAME

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: All Data was collected in the Upper Sacramento River and Lower Sacramento River Conservation Planning Areas (CPA)Operations and modifications:Sacramento River River Mile 243-144, Red Bluff to ColusaField data were collected by a team of two people by jet boat in the fall of 2013. Previous revetment data collected by DWR Northern Region were updated. Data collection consisted of updating previous mapped revetment. No changes were made to the mapping or geodatabase if the length of revetment did not change. New revetment, missing revetment, or where the active channel moved away from or moved to revetted or natural banks were updated. Update methods were consistent with previous methods as the bank type changed either from revetment type or to natural, the length of the change had to be >10 meters to be mapped as line on NAIP 2013 photography. For example, if a bank was continuously rocked with the same type of revetment for 300m, but there was a small section <10 meters of rubble in the middle of the rocked section, the entire section would be mapped as rock. However, if the rubble section in the middle was >10 in length, then 3 seperate sections were mapped (rock, rubble, then rock). Basically we used a 10m minimum mapping unit for features UNLESS a small section of revetment was on a natural bank.Sacramento River Mile 144-80, Colusa to VeronaField data were collected by a team of two people by jet boat in the spring of 2014. Previous revetment data collected by USACE (Sacramento Bank Protection Project, 2007) were updated. Data collection consisted of updating previous mapped revetment. No changes were made to the mapping or geodatabase if the length of revetment did not change. New revetment, missing revetment, or where the active channel moved away from or moved to revetted or natural banks were updated. Update methods were consistent with previous methods as the bank type changed either from revetment type or to natural, the length of the change had to be >10 meters to be mapped as line on NAIP 2013 photography. For example, if a bank was continuously rocked with the same type of revetment for 300m, but there was a small section <10 meters of rubble in the middle of the rocked section, the entire section would be mapped as rock. However, if the rubble section in the middle was >10 in length, then 3 seperate sections were mapped (rock, rubble, then rock). Basically we used a 10m minimum mapping unit for features UNLESS a small section of revetment was on a natural bank.All of the updated revetment data was then overlayed with our 2009 channel (derived from the Parent Data ds292 and ds273) where it did always not land exactly on the channel lines. This is due to various reasons including accuracy of the GPS unit and mapping technique, river channel movement and stage differences. Breaks in the 2009 lines were made using the revetment line locations and notes as a guide.Original revetment data are not included and will be held by Adam Henderson, DWR-NRO/FESSRO.Sacramento River Field Data Collection and Data Development Team:Adam Henderson, Senior Environmental Scientist (Specialist), DWR FESSROAlison Groom, Research Analyst II, DWR NROParent channel data data can be found here as of 11/17/14http://www.dfg.ca.gov/biogeodata/gis/veg.asp

Copyright Text:

Default Visibility: false

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.3604681476E7
YMin: 4687234.647399999
XMax: -1.35395022949E7
YMax: 4888725.991300002
Spatial Reference: 102113  (3785)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSLSSolid
Color: [0, 0, 0, 255]
Width: 1
Label: N/A
Description: N/A
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

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• OBJECTID_1 ( type: esriFieldTypeOID, alias: OBJECTID_1 )
• OBJECTID ( type: esriFieldTypeInteger, alias: OBJECTID )
• BANK_TYPE ( type: esriFieldTypeString, alias: BANK_TYPE, length: 50 )
• STREAMNAME ( type: esriFieldTypeString, alias: STREAMNAME, length: 50 )
• BANK_TYPE3 ( type: esriFieldTypeString, alias: BANK_TYPE3, length: 25 )
• Shape_Leng ( type: esriFieldTypeDouble, alias: Shape_Leng )
• CPA ( type: esriFieldTypeString, alias: CPA, length: 50 )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• Shape_Length ( type: esriFieldTypeDouble, alias: Shape_Length )

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

  Iteminfo   Thumbnail   Metadata