View In:   ArcGIS Online Map Viewer

Name: LWI Probable Wetland points

Display Field: PW_ID

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: The Probable Wetland Points dataset displays “probable wetlands” as mapped in original DSL approved LWIs. "Probable Wetland" or “PW” 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. Wetlands that were less than one half of an acre may have been mapped as wetland polygons or as probable wetlands. LWIs developed prior to 2001 did not require mapping of wetlands less than one half acre in size. PWs were required as points beginning in 2001 and transitioned toward being represented as polygons starting around 2018. Probable wetlands are labeled as "PW” on the maps. A few LWIs represented delineated wetlands smaller than one-half acre in size as “DW” points (this does not comply with rule). No further characterization or assessment is required for PW wetlands in LWIs.All waters and wetlands, including PWs, mapped in a DSL approved LWI indicate that cities and counties shall submit a wetland land use notice to DSL for proposed land use activities affecting mapped wetlands and other waters (ORS 215.418 and 227.350).The LWI Probable Wetland Points dataset is part of the LWI_Statewide dataset that is created from the combined individual standardized LWI datasets and is part of the Statewide Wetlands Inventory (SWI). The LWI_Statewide dataset supersedes the national inventory level mapping included in the SWI within the LWI study areas.The LWI Probable Wetland Points dataset is one of five LWI layers contained in the LWI_Subset dataset pulled from the LWI_Statewide dataset. The LWI_Subset dataset is used for the ORWAP and SFAM assessments Map Viewer.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. Upon approval by DSL, the LWI must be used in lieu of the National Wetlands Inventory (NWI) and is incorporated into the SWI.New LWIs are added to the LWI_Statewide and the LWI_Subset datasets upon approval by DSL.Further information on the development and results of individual LWIs is contained in the LWI reports, original maps, and individual GIS datasets, available for view and download from the DSL LWI web page. The LWI GIS Data Description and template is available on the DSL LWI web page.

Service Item Id: 5ea5be6839d943cd8ad8b2be7eae456a

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

Can Scale Symbols: false

Use Standardized Queries: true

Supports ValidateSQL: true

Supports Calculate: true

Supports Datum Transformation: true

Extent:

XMin: 357345.8425196856
YMin: 149772.62762467563
XMax: 1752581.9255249351
YMax: 1503031.8192257285
Spatial Reference: 2992  (2992)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
Label Placement: esriServerPointLabelPlacementAboveRight
Label Expression: [PW_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: 8
Font Family: Arial
Font Style: normal
Font Weight: bold
Font Decoration: none

Min. Scale: 100000.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: true
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: false
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:

Fields:

• Site_Name ( type: esriFieldTypeString, alias: Site_Name, editable: true, nullable: true, length: 100, defaultValue: null, modelName: Site_Name )
• PW_ID ( type: esriFieldTypeString, alias: PW_ID, editable: true, nullable: true, length: 15, defaultValue: null, modelName: PW_ID )
• GlobalID ( type: esriFieldTypeGlobalID, alias: GlobalID, editable: false, nullable: false, length: 38, defaultValue: null, modelName: GlobalID )
• created_user ( type: esriFieldTypeString, alias: created_user, editable: false, nullable: true, length: 255, defaultValue: null, modelName: created_user )
• created_date ( type: esriFieldTypeDate, alias: created_date, editable: false, nullable: true, length: 8, defaultValue: null, modelName: created_date )
• last_edited_user ( type: esriFieldTypeString, alias: last_edited_user, editable: false, nullable: true, length: 255, defaultValue: null, modelName: last_edited_user )
• last_edited_date ( type: esriFieldTypeDate, alias: last_edited_date, editable: false, nullable: true, length: 8, defaultValue: null, modelName: last_edited_date )
• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID, editable: false, nullable: false, defaultValue: null, modelName: OBJECTID )

Templates:

• Name: Probable Wetland Points
  Description:
  Prototype:
  PW_ID: null
  Site_Name: null
  
  Drawing Tool: esriFeatureEditToolPoint

Capabilities: Query,Sync,Extract,ChangeTracking

Sync Can Return Changes: true

Is Data Versioned: false

Supports Rollback On Failure: true

Supports ApplyEdits With Global Ids: true

Edit Fields Info:

• Creation Date Field: created_date
• Creator Field: created_user
• Edit Date Field: last_edited_date
• Editor Field: last_edited_user

Supports Query With Historic Moment: true

Supports Coordinates Quantization: true

Child Resources:   Field Groups   Contingent Values

Supported Operations:   Query   Query Analytic   Validate SQL   Generate Renderer   Return Updates   Iteminfo   Thumbnail   Metadata   Update Metadata