Layer: BeaverDams (ID: 4)

Name: BeaverDams

Display Field: Date

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: The Wetland Conservancy and U.S. Fish and Wildlife Service provided .kml files with pin points showing dam locations. The latitude and longitude of the points are saved in the properties of the file. The latitude and longitude was used to add a point (Absolute X Y) in the ArcGIS shapefile layer. Similarly, the Tualatin River Keepers provided a screen shot of Google Earth with two pin points indicating dams. The exact latitude and longitude information could not be obtained from a screenshot, but the approximate location was determined based on landmarks and streets and the points were added to the ArcGIS shapefile layer. During meetings with USDA and Tigard Public Works, beaver dam locations were either marked on hardcopy maps or verbally explained using street names and parks. After the meeting, the maps and meeting notes were referenced and points of the beaver dams were created based on their descriptions. Also during these meetings, the source would state whether there was a known conflict and what the conflict was. This information was recorded in the Conflicts column of the attribute table.USGS had two field technicians walk specific stream reaches to record the GPS coordinates of beaver dams. The field technicians recorded the latitude and longitude information, as well as some other dam characteristic information, in an Excel spreadsheet. The coordinates from the spreadsheet were used to create points (Absolute X Y) within the ArcGIS layer. Clean Water Services provided the shapefiles for the 2013 and 2014 Rapid Bio Assessment that was conducted by Steve Task of Bio-Surveys, LLC in the Tualatin Basin. During the assessment, pools were surveyed for fish abundance and species. The technicians counted each beaver dam in their survey reaches, and the number of dams was noted. Ben Protzman (CWS) estimates that accuracy of the coordinates for the pools were +/- 30 meters when there was a thick canopy. The 2014 survey mapped 1009 pools, and 86 of them had beaver dams present. The attributes (along with the x and y coordinates) that contained beaver dams were selected and were added to the Beaver Dam Inventory attribute table. For these attributes, a GPS point represents the beginning of a stream reach. The number of beaver dams in that reach (and near that GPS coordinate) was noted in the attribute table. Therefore, one GPS point may represent up to 4 beaver dams.

Copyright Text:

Default Visibility: false

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 100000.0

Max Scale: 0.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:

Drawing Info:

Renderer:

Simple Renderer:

Symbol:

Label:

Description:

Transparency:

Labeling Info:

Advanced Query Capabilities:

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

OBJECTID_1 ( type: esriFieldTypeOID, alias: OBJECTID_1 )
Shape ( type: esriFieldTypeGeometry, alias: Shape )
OBJECTID ( type: esriFieldTypeInteger, alias: OBJECTID )
Date ( type: esriFieldTypeString, alias: Date, length: 50 )
Source ( type: esriFieldTypeString, alias: Source, length: 50 )
Method ( type: esriFieldTypeString, alias: Method, length: 50 )
DamQuantit ( type: esriFieldTypeString, alias: DamQuantit, length: 50 )
Easting ( type: esriFieldTypeInteger, alias: Easting )
Northing ( type: esriFieldTypeInteger, alias: Northing )
Notes ( type: esriFieldTypeString, alias: Notes, length: 254 )
Conflict ( type: esriFieldTypeString, alias: Conflict, length: 254 )

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

Iteminfo Thumbnail Metadata