Name: LWI Wetlands

Display Field: SITENAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: Local Wetlands Inventory development requires an LWI Wetlands dataset displaying all wetlands greater than or equal to one-half of an acre and all wetlands identified in DSL-approved wetland delineation reports to be identified and mapped as polygons with a goal accuracy of +/- 5 meters (under 2009 LWI rules).LWIs developed prior to 2001 did not require mapping of wetlands less than one half acre in size. Beginning in 2001 mapping of “Probable Wetland" or “PW” is required and means an area noted during the LWI development that appeared to meet wetland criteria but was less than one half of an acre in size or was small and of undetermined size. Therefore, there may be unmapped wetlands within the study areas of all LWIs, particularly older inventories.LWI wetland polygons are associated with wetland functional assessment results and wetland summary sheets, found within the LWI report. Wetland polygons include required attributes including unique wetland identification label, Cowardin classification code(s) and modifiers, HGM classification, approximate wetland size, Locally Significant Wetland status determination, whether the wetland investigation was onsite, offsite, or visually confirmed, and DSL's wetland delineation report file number, if any.The LWI Wetlands dataset is part of the LWI_Subset pulled from the LWI_Statewide dataset. The LWI_Subset dataset is used for the ORWAP and SFAM assessments map viewer.Upon approval by DSL the LWI must be used in lieu of the National Wetlands Inventory (NWI) and is incorporated into the Statewide Wetlands Inventory. The approved LWI must be used by cities and counties for notifying DSL of land use applications affecting mapped wetlands and other waters in the wetland land use notice (WLUN) process (ORS 215.418 and 227.350).New LWIs are added to the LWI_Statewide dataset upon approval by DSL. The LWI_Statewide dataset is part of the Statewide Wetlands Inventory and supersedes the national inventory level mapping included in the SWI web map. View the SWI web map on the DSL SWI web page.Some local governments must inventory and include protections for resources listed in Oregon’s land use planning goals 5 (Natural Resources), 16 (Estuaries) and 17 (Coastal Shorelands). An LWI fulfills the wetlands inventory requirements for Goal 5 and Goal 17 (OAR 660-015, 660-016, and 660-023). DSL is responsible for the requirements and review of LWIs for Goal compliance and other natural resource planning efforts. In accordance with the DSL’s LWI standards, the approximate location and boundaries of all wetlands and waters are identified within a specified study area.Further information on the individual LWI development, results and citations can be found in the LWI report on the DSL LWI webpage. The original maps, individual GIS datasets, the DSL LWI GIS Data Description and template are also available for view and download on the DSL LWI web page.

Service Item Id: 77ea95fdf6064c1186e997695298f62c

Copyright Text: Local Wetlands Inventories received and approved by DSL dating from 1992 through 2019 were digitized and standardized by DSL, Institute for Natural Resources, and Oregon State University Libraries and Press. DSL combined the individual standardized LWI datasets into an LWI_Statewide dataset. New LWIs are added to the LWI_Statewide dataset upon approval by DSL. Individual LWIs are developed by consultants for local governments. Find full reports, citations, maps, and individual LWI GIS datasets on the DSL LWI web page. The digitizing and standardization of LWI GIS datasets approved by the Oregon Department of State Lands prior to 2018 has been funded wholly or in part by the United States Environmental Protection Agency under assistance agreement number CD-01J37701-02 to the Oregon Department of State Lands. The contents of this LWI dataset do not necessarily reflect the views and policies of the Environmental Protection Agency, nor does mention of trade names or commercial products constitute endorsement or recommendation for use.

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 250000

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: true

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

XMin: 234382.57939632237
YMin: 146047.08727033436
XMax: 1942274.3185695559
YMax: 1641667.4540682435
Spatial Reference: 2992  (2992)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSFSDiagonalCross
Color: [197, 0, 255, 255]
Outline:
Style: esriSLSSolid
Color: [197, 0, 255, 255]
Width: 0
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
Label Placement: esriServerPolygonPlacementAlwaysHorizontal
Label Expression: [POLY_S_ID]
Use Coded Values: true
Symbol:
Color: [197, 0, 255, 255]
Background Color: N/A
Outline Color: N/A
Vertical Alignment: bottom
Horizontal Alignment: center
Right to Left: false
Angle: 0
XOffset: 0
YOffset: 0
Size: 10
Font Family: Arial
Font Style: normal
Font Weight: bold
Font Decoration: none

Min. Scale: 0.0
Max. Scale: 0.0

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: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• SITENAME ( type: esriFieldTypeString, alias: SITENAME, length: 100 )
• DATA_S_YR ( type: esriFieldTypeString, alias: DATA_S_YR, length: 100 )
• CREAT_YR ( type: esriFieldTypeString, alias: CREAT_YR, length: 100 )
• DATA_METH ( type: esriFieldTypeSmallInteger, alias: DATA_METH )
• DATA_ACCU ( type: esriFieldTypeSmallInteger, alias: DATA_ACCU )
• COWARDIN ( type: esriFieldTypeString, alias: COWARDIN, length: 20 )
• COWAR_S_YR ( type: esriFieldTypeString, alias: COWAR_S_YR, length: 100 )
• HGM ( type: esriFieldTypeString, alias: HGM, length: 10 )
• HGM_S_YR ( type: esriFieldTypeString, alias: HGM_S_YR, length: 100 )
• POLY_S_ID ( type: esriFieldTypeString, alias: POLY_S_ID, length: 100 )
• DATA_S_TYP ( type: esriFieldTypeSmallInteger, alias: DATA_S_TYP )
• HYD_BAR ( type: esriFieldTypeString, alias: HYD_BAR, length: 2 )
• HYD_DRA ( type: esriFieldTypeString, alias: HYD_DRA, length: 2 )
• HYD_FLO ( type: esriFieldTypeString, alias: HYD_FLO, length: 2 )
• WET_MGT ( type: esriFieldTypeSmallInteger, alias: WET_MGT )
• COV_TYP ( type: esriFieldTypeSmallInteger, alias: COV_TYP )
• VEG_SPEC ( type: esriFieldTypeString, alias: VEG_SPEC, length: 100 )
• VEG_COND ( type: esriFieldTypeSmallInteger, alias: VEG_COND )
• VEG_S_YR ( type: esriFieldTypeString, alias: VEG_S_YR, length: 100 )
• LSW ( type: esriFieldTypeString, alias: LSW, length: 2 )
• GOAL_5_17 ( type: esriFieldTypeString, alias: GOAL_5_17, length: 2 )
• SAC ( type: esriFieldTypeString, alias: SAC, length: 2 )
• DEVELOP ( type: esriFieldTypeString, alias: DEVELOP, length: 2 )
• DSL_WD ( type: esriFieldTypeString, alias: DSL_WD, length: 50 )
• DSL_FILE ( type: esriFieldTypeString, alias: DSL_FILE, length: 50 )
• MOSAIC ( type: esriFieldTypeString, alias: MOSAIC, length: 25 )
• Acres ( type: esriFieldTypeDouble, alias: Acres )
• FIELD_OBS_LWI ( type: esriFieldTypeString, alias: FIELD_OBS_LWI, length: 10 )
• OWMS_FIELD_OBS ( type: esriFieldTypeString, alias: OWMS_FIELD_OBS, length: 10 )
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )
• Shape.STLength() ( type: esriFieldTypeDouble, alias: Shape_Length )
• Shape.STArea() ( type: esriFieldTypeDouble, alias: Shape_Area )

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

  Iteminfo   Thumbnail   Metadata