Name: Oak Quest Tree Inventory

Display Field: Name

Type: Feature Layer

Geometry Type: esriGeometryPoint

Description: <DIV STYLE="text-align:Left;"><DIV><DIV><P STYLE="margin:0 0 0 0;"><SPAN><SPAN>This point data set represents both where Oregon White Oak has been detected as well as where there is no significant oak presently detected. We placed points where we were confident the tree canopy was Oregon white oak. The points do not necessarily represent individual oak trees. We were conservative because we didn’t want to portray false positives, therefore we likely omitted some small oaks, mixed forest oaks where oak was mostly overtopped by conifers, and some individual trees that we were not certain were oak.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN /><SPAN /></P><P STYLE="font-style:italic;font-weight:bold;margin:7 0 7 0;"><SPAN><SPAN>Extent</SPAN></SPAN></P><P STYLE="margin:7 0 7 0;"><SPAN><SPAN>This release, OakQuest 2020, of The Intertwine Alliance's OakQuest data incorporates new data from southwestern Washington and previous releases from 2016-18 plus minor edits to previous data releases. With this 2019 release, we consider the whole of the Oregon and Washington portions of the RCS planning area within which Oregon white oak was historically prominent, complete. The oak data show concentrations of oak as well as areas where oak is likely very sparse or absent. </SPAN></SPAN></P><P STYLE="margin:7 0 7 0;"><SPAN><SPAN>This “full coverage” area of 1,790 sq. miles of northwestern Oregon and 375 sq. miles of southwestern Washington shows portions of the landscape where oak was mapped using a combination of aerial photo interpretation and limited field work. This “full coverage” area documents the search area within which oak were identified with high confidence and/or determined absent with moderate to high confidence. Across this full coverage area we have high confidence that oak is present where mapped and we believe that few or no significant stands of oak were missed. The additional 699 sq. miles within the RCS boundary beyond the full coverage areas has been spot-checked for oak but not searched thoroughly due to habitat conditions deemed not conducive to oak, e.g. areas above approximately 1,000 ft. elevation. Clark County partners may decide to expand their mapping extent in the future if it is determined that some unmapped areas may contain oak; although not likely necessary, if needed such adjustments can be made on the Oregon side as well in future data releases.</SPAN></SPAN></P><P STYLE="font-style:italic;font-weight:bold;margin:7 0 7 0;"><SPAN><SPAN>Methods</SPAN></SPAN></P><P STYLE="margin:7 0 7 0;"><SPAN><SPAN>Version I of the OakQuest data was developed from field observations and inspection of high-resolution aerial photography in GIS, as well as other records checked and compiled from existing regional tree inventories in 2014 which included available street, heritage, and other regional tree inventories. During July-Oct 2014 and August-November 2015, community volunteers and natural resource professionals collected field observations of oak and other tree species using a custom smart phone app. Data collected in the field were later spatially adjusted and error-checked within ArcGIS. During inspection of oak field observations with aerial photos in ArcGIS, Metro staff developed an eye for spotting Oregon white oak and additional oak trees visible in high-resolution aerial photography were digitized. Data were converted to a common projected coordinate system and observations were coded by source and category of origin. </SPAN></SPAN></P><P STYLE="margin:7 0 7 0;"><SPAN><SPAN>Data release versions II and III included additional full coverage areas beyond Version I, including urban and rural areas, for approximately 824 sq. miles and 766 sq. miles of the Oregon portion of the Intertwine Alliance RCS planning area, respectively. For portions of the region where high-resolution Metro or NAIP aerial photography was available, we used heads-up digitizing of points representing Oregon white oak tree canopy centers in ArcGIS. In outlying rural areas where Metro or NAIP aerial photos were not available, we used heads-up digitizing of oak tree canopy centers over Google and Bing aerial photography in Quantum GIS.</SPAN></SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN /><SPAN /></P></DIV></DIV></DIV>

Service Item Id: b8b7e5ee59d140e6bc64cc4ce728878c

Copyright Text: Members of the Oak Prairie Work Group (OPWG; a project of The Intertwine Alliance) completed much of the digitizing and compilation of this data set. The original oak field observations were collected by over 200 community members during the 2014-15 OakQuest community science effort. Lori Hennings (Metro) and Ted Labbe (Urban Greenspaces Institute) digitized most of the remaining oak point locations in Oregon, with assistance from Carter Hoffman (independent contractor to UGI), Nesieka Breck (Metro/Siletz Tribal intern), as well as Janelle St. Pierre and Pat Welle (volunteers). In southwest Washington, interns Beth Lamb and Marissa Eckman mapped oak with support from the following people: Zorah Oppenheimer, Clark Conservation District (supervisor); Jeff Azerrad, George Fornes, Dave Howe and Chuck Stambaugh-Bowey (Washington Department of Fish and Wildlife), Ted Labbe and Lori Hennings. Tommy Albo (Metro) compiled the data and prepared it for release. Savahna Jackson and Sequoia Breck (Portland State University Indigenous Nations Studies, and Native American Youth and Family Center) helped organize and lead OakQuest community science volunteers during summers 2014 and 2015. Funding support was provided by Metro’s Nature in Neighborhoods, Metro Parks and Nature, U.S. Fish and Wildlife Service, Oregon Wildlife Heritage Foundation, Clackamas and Tualatin Soil and Water Conservation Districts, Oregon Department of Forestry/U.S. Forest Service, Clark County, Clark Public Utilities, and Washington Department of Fish and Wildlife.

Default Visibility: false

MaxRecordCount: 1000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 125000

Max Scale: 10

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.36786099122E7
YMin: 5681423.753700003
XMax: -1.3661497149500001E7
YMax: 5695946.115400001
Spatial Reference: 102100  (3857)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSMSCircle
Color: [121, 173, 43, 255]
Size: 5.0
Angle: 0.0
XOffset: 0
YOffset: 0
Outline:
[0, 0, 0, 255] Width: 0
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

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID_1 )
• Spp_Sci ( type: esriFieldTypeString, alias: Spp_Sci, length: 50 )
• Common_Nm ( type: esriFieldTypeString, alias: Common_Nm, length: 50 )
• Method ( type: esriFieldTypeString, alias: Method, length: 66 )
• source ( type: esriFieldTypeString, alias: source, length: 66 )
• Year ( type: esriFieldTypeString, alias: Year, length: 12 )
• Inventory ( type: esriFieldTypeString, alias: Inventory, length: 40 )
• Coverage ( type: esriFieldTypeString, alias: Coverage, length: 30 )
• collect_ve ( type: esriFieldTypeString, alias: collect_ve, length: 18 )
• Type ( type: esriFieldTypeString, alias: Type, length: 10 )
• Name ( type: esriFieldTypeString, alias: Name, length: 60 )
• INV_ ( type: esriFieldTypeString, alias: Inventory when collected(version), length: 50 )
• extent ( type: esriFieldTypeString, alias: extent, length: 50 )
• ID10_1 ( type: esriFieldTypeString, alias: ID10, length: 32 )
• ID2_56 ( type: esriFieldTypeString, alias: ID2_5, length: 32 )
• Unique_ID_ ( type: esriFieldTypeInteger, alias: Unique_ID_ )
• CITYNAME ( type: esriFieldTypeString, alias: CITYNAME, length: 30 )
• UGB_June18 ( type: esriFieldTypeString, alias: UGB_June18, length: 8 )
• Notes ( type: esriFieldTypeString, alias: Notes, length: 128 )
• Editor ( type: esriFieldTypeString, alias: Editor, length: 128 )
• SurveyType ( type: esriFieldTypeInteger, alias: SurveyType )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )

Supported Operations:   Query   Query Attachments   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata