Description: This theme contains PLS lines for the State of Oregon. This Pls theme includes donation claims lands. Attributes in this theme show Township Range and Section values.
Metadata
http://spatialdata.oregonexplorer.info/geoportal/rest/document?id={71C4C51D-5CB7-4DDF-84D9-3A65D4187D21}
Download
http://navigator.state.or.us/sdl/data/shapefile/k100/township_range.zip
Color: [0, 0, 0, 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: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Description: This theme contains PLS lines for the State of Oregon. This Pls theme includes donation claims lands. Attributes in this theme show Township Range and Section values.
Metadata
http://spatialdata.oregonexplorer.info/geoportal/rest/document?id={71C4C51D-5CB7-4DDF-84D9-3A65D4187D21}
Download
http://navigator.state.or.us/sdl/data/shapefile/k100/township_range.zip
Color: [0, 0, 0, 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: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Description: Land Management derived from BLM Ownership_poly: This theme portrays information representing fee land title and land manager of lands located in Oregon.
Metadata
http://spatialdata.oregonexplorer.info/geoportal/rest/document?id={9B644E0F-7A7D-4124-A50F-6B35C05626AE}
Download
http://www.odf.state.or.us/gis/data/Ownership/2015_LandManagementDraft.gdb.zip
Service Item Id: 42d3ecd3ee814a9e840f3832f64a1400
Copyright Text: Oregon Bureau of Land Management USDI edited by the Oregon Department of Forestry
Description: The Protected Areas Database of the United States (PAD-US) is a geodatabase, managed by USGS GAP, that illustrates and describes public land ownership, management and other conservation lands, including voluntarily provided privately protected areas. The State, Regional and LCC geodatabases contain two feature classes. The PADUS1_3_FeeEasement feature class and the national MPA feature class. Legitimate and other protected area overlaps exist in the full inventory, with Easements loaded on top of Fee. Parcel data within a protected area are dissolved in this file that powers the PAD-US Viewer. As overlaps exist, GAP creates separate analytical layers to summarize area statistics for "GAP Status Code" and "Owner Name". Contact the PAD-US Coordinator for more information. The lands included in PAD-US are assigned conservation measures that qualify their intent to manage lands for the preservation of biological diversity and to other natural, recreational and cultural uses; managed for these purposes through legal or other effective means. The geodatabase includes: 1) Geographic boundaries of public land ownership and voluntarily provided private conservation lands (e.g., Nature Conservancy Preserves); 2) The combination land owner, land manager, management designation or type, parcel name, GIS Acres and source of geographic information of each mapped land unit 3) GAP Status Code conservation measure of each parcel based on USGS National Gap Analysis Program (GAP) protection level categories which provide a measurement of management intent for long-term biodiversity conservation 4) IUCN category for a protected area's inclusion into UNEP-World Conservation Monitoring Centre's World Database for Protected Areas. IUCN protected areas are defined as, "A clearly defined geographical space, recognized, dedicated and managed, through legal or other effective means, to achieve the long-term conservation of nature with associated ecosystem services and cultural values" and are categorized following a classification scheme available through USGS GAP; 5) World Database of Protected Areas (WDPA) Site Codes linking the multiple parcels of a single protected area in PAD-US and connecting them to the Global Community. As legitimate and other overlaps exist in the combined inventory GAP creates separate analytical layers to obtain area statistics for "GAP Status Code" and "Owner Name". PAD-US version 1.3 Combined updates include: 1) State, local government and private protected area updates delivered September 2011 from PAD-US State Data Stewards: CO (Colorado State University), FL (Florida Natural Areas Inventory), ID (Idaho Fish and Game), MA (The Commonwealth's Office of Geographic Information Systems, MassGIS), MO (University of Missouri, MoRAP), MT (Montana Natural Heritage Program), NM (Natural Heritage New Mexico), OR (Oregon Natural Heritage Program), VA (Department of Conservation and Recreation, Virginia Natural Heritage Program). 2) Select local government (i.e. county, city) protected areas (3,632) across the country (to complement the current PAD-US inventory) aggregated by the Trust for Public Land (TPL) for their Conservation Almanac that tracks the conservation finance movement across the country. 3) A new Date of Establishment field that identifies the year an area was designated or otherwise protected, attributed for 86% of GAP Status Code 1 and 2 protected areas. Additional dates will be provided in future updates. 4) A national wilderness area update from wilderness.net 5) The Access field that describes public access to protected areas as defined by data stewards or categorical assignment by Primary Designation Type. . The new Access Source field documents local vs. categorical assignments. See the PAD-US Standard Manual for more information: gapanalysis.usgs.gov/padus 6) The transfer of conservation measures (i.e. GAP Status Codes, IUCN Categories) and documentation (i.e. GAP Code Source, GAP Code Date) from PAD-US version 1.2 or categorical assignments (see PAD-US Standard) when not provided by data stewards 7) Integration of non-sensitive National Conservation Easement Database (NCED) easements from August 2011, July 2012 with PAD-US version 1.2 easements. Duplicates were removed, unless 'Stacked' = Y and multiple easements exist. 8) Unique ID's transferred from NCED or requested for new easements. NCED and PAD-US are linked via Source UID in the PAD-US version 1.3 Easement feature class. 9) Official (member and eligible) MPAs from the NOAA MPA Inventory (March 2011, www.mpa.gov) translated into the PAD-US schema with conservation measures transferred from PAD-US version 1.2 or categorically assigned to new protected areas. Contact the PAD-US Coordinator for documentation of categorical GAP Status Code assignments for MPAs. 10) Identified MPA records that overlap existing protected areas in the PAD-US Fee feature class (i.e. PADUS Overlap field in MPA feature class). For example, many National Wildlife Refuges and National Parks are also MPAs and are represented in the PAD-US MPA and Fee feature classes.
Metadata http://spatialdata.oregonexplorer.info/geoportal/rest/document?id={1A95CDE7-7C27-46FF-9E02-785C8AAF6DB7}
Download
ftp://ftp.gis.oregon.gov/landuse/OR_stewardship.zip
Service Item Id: 42d3ecd3ee814a9e840f3832f64a1400
Copyright Text: ORBIC Stewardship Geodatabase. December 2013. Modified from: US Geological Survey, Gap Analysis Program (GAP). November 2012. Protected Areas Database of the United States (PADUS), version 1.4.
own_name
(
type: esriFieldTypeString, alias: Owner Name, length: 70
, Coded Values:
[0100: Tennessee Valley Authority (TVA)]
, [0110: Bureau of Land Management (BLM)]
, [0115: Bureau of Ocean Energy Management, Regulation and Enforcement (DOI)]
, ...54 more...
)
loc_own
(
type: esriFieldTypeString, alias: Local Owner, length: 100
)
status
(
type: esriFieldTypeString, alias: Status, length: 70
, Coded Values:
[Designated: Designated - Legally or administratively decreed]
, [Proposed: Proposed - local government level approval]
, [Other: Other - Site is recognized in a manner not otherwise classified]
, ...1 more...
)
state_nm
(
type: esriFieldTypeString, alias: State Name, length: 50
, Coded Values:
[10: Delaware]
, [11: District of Columbia]
, [12: Florida]
, ...58 more...
)
Description: The Protected Areas Database of the United States (PAD-US) is a geodatabase, managed by USGS GAP, that illustrates and describes public land ownership, management and other conservation lands, including voluntarily provided privately protected areas. The State, Regional and LCC geodatabases contain two feature classes. The PADUS1_3_FeeEasement feature class and the national MPA feature class. Legitimate and other protected area overlaps exist in the full inventory, with Easements loaded on top of Fee. Parcel data within a protected area are dissolved in this file that powers the PAD-US Viewer. As overlaps exist, GAP creates separate analytical layers to summarize area statistics for "GAP Status Code" and "Owner Name". Contact the PAD-US Coordinator for more information. The lands included in PAD-US are assigned conservation measures that qualify their intent to manage lands for the preservation of biological diversity and to other natural, recreational and cultural uses; managed for these purposes through legal or other effective means. The geodatabase includes: 1) Geographic boundaries of public land ownership and voluntarily provided private conservation lands (e.g., Nature Conservancy Preserves); 2) The combination land owner, land manager, management designation or type, parcel name, GIS Acres and source of geographic information of each mapped land unit 3) GAP Status Code conservation measure of each parcel based on USGS National Gap Analysis Program (GAP) protection level categories which provide a measurement of management intent for long-term biodiversity conservation 4) IUCN category for a protected area's inclusion into UNEP-World Conservation Monitoring Centre's World Database for Protected Areas. IUCN protected areas are defined as, "A clearly defined geographical space, recognized, dedicated and managed, through legal or other effective means, to achieve the long-term conservation of nature with associated ecosystem services and cultural values" and are categorized following a classification scheme available through USGS GAP; 5) World Database of Protected Areas (WDPA) Site Codes linking the multiple parcels of a single protected area in PAD-US and connecting them to the Global Community. As legitimate and other overlaps exist in the combined inventory GAP creates separate analytical layers to obtain area statistics for "GAP Status Code" and "Owner Name". PAD-US version 1.3 Combined updates include: 1) State, local government and private protected area updates delivered September 2011 from PAD-US State Data Stewards: CO (Colorado State University), FL (Florida Natural Areas Inventory), ID (Idaho Fish and Game), MA (The Commonwealth's Office of Geographic Information Systems, MassGIS), MO (University of Missouri, MoRAP), MT (Montana Natural Heritage Program), NM (Natural Heritage New Mexico), OR (Oregon Natural Heritage Program), VA (Department of Conservation and Recreation, Virginia Natural Heritage Program). 2) Select local government (i.e. county, city) protected areas (3,632) across the country (to complement the current PAD-US inventory) aggregated by the Trust for Public Land (TPL) for their Conservation Almanac that tracks the conservation finance movement across the country. 3) A new Date of Establishment field that identifies the year an area was designated or otherwise protected, attributed for 86% of GAP Status Code 1 and 2 protected areas. Additional dates will be provided in future updates. 4) A national wilderness area update from wilderness.net 5) The Access field that describes public access to protected areas as defined by data stewards or categorical assignment by Primary Designation Type. . The new Access Source field documents local vs. categorical assignments. See the PAD-US Standard Manual for more information: gapanalysis.usgs.gov/padus 6) The transfer of conservation measures (i.e. GAP Status Codes, IUCN Categories) and documentation (i.e. GAP Code Source, GAP Code Date) from PAD-US version 1.2 or categorical assignments (see PAD-US Standard) when not provided by data stewards 7) Integration of non-sensitive National Conservation Easement Database (NCED) easements from August 2011, July 2012 with PAD-US version 1.2 easements. Duplicates were removed, unless 'Stacked' = Y and multiple easements exist. 8) Unique ID's transferred from NCED or requested for new easements. NCED and PAD-US are linked via Source UID in the PAD-US version 1.3 Easement feature class. 9) Official (member and eligible) MPAs from the NOAA MPA Inventory (March 2011, www.mpa.gov) translated into the PAD-US schema with conservation measures transferred from PAD-US version 1.2 or categorically assigned to new protected areas. Contact the PAD-US Coordinator for documentation of categorical GAP Status Code assignments for MPAs. 10) Identified MPA records that overlap existing protected areas in the PAD-US Fee feature class (i.e. PADUS Overlap field in MPA feature class). For example, many National Wildlife Refuges and National Parks are also MPAs and are represented in the PAD-US MPA and Fee feature classes.
Metadata
http://spatialdata.oregonexplorer.info/geoportal/rest/document?id={1A95CDE7-7C27-46FF-9E02-785C8AAF6DB7}
Download
ftp://ftp.gis.oregon.gov/landuse/OR_stewardship.zip
Service Item Id: 42d3ecd3ee814a9e840f3832f64a1400
Copyright Text: ORBIC Stewardship Geodatabase. December 2013. Modified from: US Geological Survey, Gap Analysis Program (GAP). November 2012. Protected Areas Database of the United States (PADUS), version 1.4.
own_name
(
type: esriFieldTypeString, alias: Owner Name, length: 70
, Coded Values:
[0100: Tennessee Valley Authority (TVA)]
, [0110: Bureau of Land Management (BLM)]
, [0115: Bureau of Ocean Energy Management, Regulation and Enforcement (DOI)]
, ...54 more...
)
loc_own
(
type: esriFieldTypeString, alias: Local Owner, length: 100
)
status
(
type: esriFieldTypeString, alias: Status, length: 70
, Coded Values:
[Designated: Designated - Legally or administratively decreed]
, [Proposed: Proposed - local government level approval]
, [Other: Other - Site is recognized in a manner not otherwise classified]
, ...1 more...
)
state_nm
(
type: esriFieldTypeString, alias: State Name, length: 50
, Coded Values:
[10: Delaware]
, [11: District of Columbia]
, [12: Florida]
, ...58 more...
)
Description: The Protected Areas Database of the United States (PAD-US) is a geodatabase, managed by USGS GAP, that illustrates and describes public land ownership, management and other conservation lands, including voluntarily provided privately protected areas. The State, Regional and LCC geodatabases contain two feature classes. The PADUS1_3_FeeEasement feature class and the national MPA feature class. Legitimate and other protected area overlaps exist in the full inventory, with Easements loaded on top of Fee. Parcel data within a protected area are dissolved in this file that powers the PAD-US Viewer. As overlaps exist, GAP creates separate analytical layers to summarize area statistics for "GAP Status Code" and "Owner Name". Contact the PAD-US Coordinator for more information. The lands included in PAD-US are assigned conservation measures that qualify their intent to manage lands for the preservation of biological diversity and to other natural, recreational and cultural uses; managed for these purposes through legal or other effective means. The geodatabase includes: 1) Geographic boundaries of public land ownership and voluntarily provided private conservation lands (e.g., Nature Conservancy Preserves); 2) The combination land owner, land manager, management designation or type, parcel name, GIS Acres and source of geographic information of each mapped land unit 3) GAP Status Code conservation measure of each parcel based on USGS National Gap Analysis Program (GAP) protection level categories which provide a measurement of management intent for long-term biodiversity conservation 4) IUCN category for a protected area's inclusion into UNEP-World Conservation Monitoring Centre's World Database for Protected Areas. IUCN protected areas are defined as, "A clearly defined geographical space, recognized, dedicated and managed, through legal or other effective means, to achieve the long-term conservation of nature with associated ecosystem services and cultural values" and are categorized following a classification scheme available through USGS GAP; 5) World Database of Protected Areas (WDPA) Site Codes linking the multiple parcels of a single protected area in PAD-US and connecting them to the Global Community. As legitimate and other overlaps exist in the combined inventory GAP creates separate analytical layers to obtain area statistics for "GAP Status Code" and "Owner Name". PAD-US version 1.3 Combined updates include: 1) State, local government and private protected area updates delivered September 2011 from PAD-US State Data Stewards: CO (Colorado State University), FL (Florida Natural Areas Inventory), ID (Idaho Fish and Game), MA (The Commonwealth's Office of Geographic Information Systems, MassGIS), MO (University of Missouri, MoRAP), MT (Montana Natural Heritage Program), NM (Natural Heritage New Mexico), OR (Oregon Natural Heritage Program), VA (Department of Conservation and Recreation, Virginia Natural Heritage Program). 2) Select local government (i.e. county, city) protected areas (3,632) across the country (to complement the current PAD-US inventory) aggregated by the Trust for Public Land (TPL) for their Conservation Almanac that tracks the conservation finance movement across the country. 3) A new Date of Establishment field that identifies the year an area was designated or otherwise protected, attributed for 86% of GAP Status Code 1 and 2 protected areas. Additional dates will be provided in future updates. 4) A national wilderness area update from wilderness.net 5) The Access field that describes public access to protected areas as defined by data stewards or categorical assignment by Primary Designation Type. . The new Access Source field documents local vs. categorical assignments. See the PAD-US Standard Manual for more information: gapanalysis.usgs.gov/padus 6) The transfer of conservation measures (i.e. GAP Status Codes, IUCN Categories) and documentation (i.e. GAP Code Source, GAP Code Date) from PAD-US version 1.2 or categorical assignments (see PAD-US Standard) when not provided by data stewards 7) Integration of non-sensitive National Conservation Easement Database (NCED) easements from August 2011, July 2012 with PAD-US version 1.2 easements. Duplicates were removed, unless 'Stacked' = Y and multiple easements exist. 8) Unique ID's transferred from NCED or requested for new easements. NCED and PAD-US are linked via Source UID in the PAD-US version 1.3 Easement feature class. 9) Official (member and eligible) MPAs from the NOAA MPA Inventory (March 2011, www.mpa.gov) translated into the PAD-US schema with conservation measures transferred from PAD-US version 1.2 or categorically assigned to new protected areas. Contact the PAD-US Coordinator for documentation of categorical GAP Status Code assignments for MPAs. 10) Identified MPA records that overlap existing protected areas in the PAD-US Fee feature class (i.e. PADUS Overlap field in MPA feature class). For example, many National Wildlife Refuges and National Parks are also MPAs and are represented in the PAD-US MPA and Fee feature classes.
Service Item Id: 42d3ecd3ee814a9e840f3832f64a1400
Copyright Text: Oregon's Natural Areas Geodatabase. December 2020. Oregon Biodiversity Information Center and the Oregon Parks and Recreation Department. An update to the 2015 Oregon's Natural Areas Geodatabae, which is itself modified from the US Geological Survey, Gap Analysis Program (GAP). November 2012. Protected Areas Database of the United States (PADUS), version 1.4.
Description: The Protected Areas Database of the United States (PAD-US) is a geodatabase, managed by USGS GAP, that illustrates and describes public land ownership, management and other conservation lands, including voluntarily provided privately protected areas. The State, Regional and LCC geodatabases contain two feature classes. The PADUS1_3_FeeEasement feature class and the national MPA feature class. Legitimate and other protected area overlaps exist in the full inventory, with Easements loaded on top of Fee. Parcel data within a protected area are dissolved in this file that powers the PAD-US Viewer. As overlaps exist, GAP creates separate analytical layers to summarize area statistics for "GAP Status Code" and "Owner Name". Contact the PAD-US Coordinator for more information. The lands included in PAD-US are assigned conservation measures that qualify their intent to manage lands for the preservation of biological diversity and to other natural, recreational and cultural uses; managed for these purposes through legal or other effective means. The geodatabase includes: 1) Geographic boundaries of public land ownership and voluntarily provided private conservation lands (e.g., Nature Conservancy Preserves); 2) The combination land owner, land manager, management designation or type, parcel name, GIS Acres and source of geographic information of each mapped land unit 3) GAP Status Code conservation measure of each parcel based on USGS National Gap Analysis Program (GAP) protection level categories which provide a measurement of management intent for long-term biodiversity conservation 4) IUCN category for a protected area's inclusion into UNEP-World Conservation Monitoring Centre's World Database for Protected Areas. IUCN protected areas are defined as, "A clearly defined geographical space, recognized, dedicated and managed, through legal or other effective means, to achieve the long-term conservation of nature with associated ecosystem services and cultural values" and are categorized following a classification scheme available through USGS GAP; 5) World Database of Protected Areas (WDPA) Site Codes linking the multiple parcels of a single protected area in PAD-US and connecting them to the Global Community. As legitimate and other overlaps exist in the combined inventory GAP creates separate analytical layers to obtain area statistics for "GAP Status Code" and "Owner Name". PAD-US version 1.3 Combined updates include: 1) State, local government and private protected area updates delivered September 2011 from PAD-US State Data Stewards: CO (Colorado State University), FL (Florida Natural Areas Inventory), ID (Idaho Fish and Game), MA (The Commonwealth's Office of Geographic Information Systems, MassGIS), MO (University of Missouri, MoRAP), MT (Montana Natural Heritage Program), NM (Natural Heritage New Mexico), OR (Oregon Natural Heritage Program), VA (Department of Conservation and Recreation, Virginia Natural Heritage Program). 2) Select local government (i.e. county, city) protected areas (3,632) across the country (to complement the current PAD-US inventory) aggregated by the Trust for Public Land (TPL) for their Conservation Almanac that tracks the conservation finance movement across the country. 3) A new Date of Establishment field that identifies the year an area was designated or otherwise protected, attributed for 86% of GAP Status Code 1 and 2 protected areas. Additional dates will be provided in future updates. 4) A national wilderness area update from wilderness.net 5) The Access field that describes public access to protected areas as defined by data stewards or categorical assignment by Primary Designation Type. . The new Access Source field documents local vs. categorical assignments. See the PAD-US Standard Manual for more information: gapanalysis.usgs.gov/padus 6) The transfer of conservation measures (i.e. GAP Status Codes, IUCN Categories) and documentation (i.e. GAP Code Source, GAP Code Date) from PAD-US version 1.2 or categorical assignments (see PAD-US Standard) when not provided by data stewards 7) Integration of non-sensitive National Conservation Easement Database (NCED) easements from August 2011, July 2012 with PAD-US version 1.2 easements. Duplicates were removed, unless 'Stacked' = Y and multiple easements exist. 8) Unique ID's transferred from NCED or requested for new easements. NCED and PAD-US are linked via Source UID in the PAD-US version 1.3 Easement feature class. 9) Official (member and eligible) MPAs from the NOAA MPA Inventory (March 2011, www.mpa.gov) translated into the PAD-US schema with conservation measures transferred from PAD-US version 1.2 or categorically assigned to new protected areas. Contact the PAD-US Coordinator for documentation of categorical GAP Status Code assignments for MPAs. 10) Identified MPA records that overlap existing protected areas in the PAD-US Fee feature class (i.e. PADUS Overlap field in MPA feature class). For example, many National Wildlife Refuges and National Parks are also MPAs and are represented in the PAD-US MPA and Fee feature classes.
Metadata http://spatialdata.oregonexplorer.info/geoportal/rest/document?id=%7BD2E844F8-14C3-4B4F-97DC-2FFE0EAB7FD2%7D
Download ftp://ftp.gis.oregon.gov/adminbound/ORNaturalAreas.zip
Service Item Id: 42d3ecd3ee814a9e840f3832f64a1400
Copyright Text: Oregon's Natural Areas Geodatabase. October 2015. Oregon Biodiversity Information Center and the Oregon Parks and Recreation Department. An excerpt of the Oregon Stewardship Geodatabase (2015), which is itself modified from the US Geological Survey, Gap Analysis Program (GAP). November 2012. Protected Areas Database of the United States (PADUS), version 1.4.
Description: Geographic areas (census blocks) identified as "American Indian" by the US Census Bureau in the 2010 census.
Metadata
http://oe.oregonexplorer.info/metadata/tribal_areas_2010.htm
Download
http://oregonexplorer.info/ExternalContent/SpatialDataForDownload/bnd_or_tribal_areas_2010.zip
Description: Extent of Federal Lands (DOD, USFS, BLM, BOR, USFWS, NPS) intersecting the State of Oregon.
Metadata
http://oe.oregonexplorer.info/metadata/federal_lands.htm
Download
http://oregonexplorer.info/ExternalContent/SpatialDataForDownload/pln_or_federal_lands_2010.zip
Description: As part of assisting ODFW in the development of the State Comprehensive Wildlife Conservation Plan (CWCP) for Oregon, the Oregon Natural Heritage Program developed a GIS coverage showing the distribution of Protected Areas in Oregon. This GIS layer representing the stewardship/management of Oregon was compiled from multiple sources and scales.
Metadata
http://oe.oregonexplorer.info/metadata/majorpubliclands.htm
Download
http://oregonexplorer.info/ExternalContent/SpatialDataForDownload/pln_or_land_management_2005.zip
Description: Wilderness areas within Oregon
Metadata
http://oe.oregonexplorer.info/metadata/wilderness_orlam.htm
Download
http://oregonexplorer.info/ExternalContent/SpatialDataForDownload/loc_or_wilderness_areas_2010.zip
Color: [0, 0, 0, 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: Tahoma Font Style: normal Font Weight: normal Font Decoration: none
Description: This layer depicts land ownership allocations in the CLAMS area. The major ownerships have been broken into classes with specific forest management intentions.
Metadata
http://oe.oregonexplorer.info/metadata/ownership_CLAMS.htm
Download
http://oregonexplorer.info/ExternalContent/SpatialDataForDownload/NCE_ncst_own.zip
Description: As part of assisting ODFW in the development of the State Comprehensive Wildlife Conservation Plan (CWCP) for Oregon, the Oregon Natural Heritage Program developed a GIS coverage showing the distribution of Protected Areas in Oregon. This GIS layer representing the stewardship/management of Oregon was compiled from multiple sources and scales.
Metadata
http://oe.oregonexplorer.info/metadata/majorpubliclands.htm
Download
http://oregonexplorer.info/ExternalContent/SpatialDataForDownload/pln_or_publiclandownership.zip
Description: Interpreters used black-and-white digital orthophoto imagery with one-meter spatial resolution (acquired primarily in 1994, and available through the Oregon Geospatial Enterprise Office) to backdate the 2005 Development Zone land use polygons, producing a statewide land use polygon layer for 1994. The photo interpretation was conducted in 2006 for Eastern Oregon, and in 2010 for Western Oregon. Minor corrections were made to this layer during the 2014 Development Zone Project updates carried out in 2015-2016.Land Use Zone DefinitionsWildland Forest: Zone 1Polygon is >=640 acres.Polygon has <=4 developments per 640 acres.The developments are generally scattered across the polygon.The polygon is >80% forest land, and the remainder is agricultural or "other" land except for the developments.Wildland Range: Zone 2 (Eastern Oregon Only)Polygon is >=640 acres.Polygon has <=4 developments per 640 acres.The developments are generally scattered across the polygon.The polygon is <51% forestland.Agricultural lands are <20% of the polygon.The remainder is undeveloped rangeland.Alternately, the polgon is >=50% rangeland, agricultural lands are <20% of the polygon, and wildland forest makes up the remainder.Mixed Forest/Agriculture: Zone 5Polygon is >=640 acres.This zone contains forest, range, and "other" lands intermingled with agricultural land. It also includes lightly forested areas where livestock grazing is suspected as a regular use of the understory.Polygon has <9 developments per 640 acres.The developments are generally scattered across the polygon.Agricultural land comprises 20% to 80% of the polygon, and the remainder is forest or "other" land except for the developments. Forest land is >=50% of the remainder.Improved road patterns are generally 0.5mile or greater.Mixed Range/Agriculture: Zone 6 (Eastern Oregon Only)Polygon is >=640 acres.This zone contains rangeland and agricultural land.Polygon has <9 developments per 640 acres.The developments are generally scattered across the polygon.Agricultural land comprises 20% to 80% of the polygon.The undeveloped portion (i.e., non-agricultural land) is <51% forestland.Improved road patterns are generally 0.5 mile or greater.Intensive Agriculture: Zone 7Polygon is >=640 acres.Polygon has <9 developments per 640 acres.The developments are generally scattered across the polygon.Agricultural land occupies >80% of the polygon, and the remainder is forest or "other" lands except for the developments.Low-Density Residential: Zone 8Polygon can be any size, but must have >=9 developments within it.The average acreage per development is generally less than 80 acres.Improved road patterns are typically 0.25 mile or less.The residential lot size is generally greater than 1 acre.This zone can also be a polygon that meets urban qualifications, but is less than 40 acres in size.Urban: Zone 9Polygon is >=40 acres.This is a commercial, service, and residential subdivided area with city road patterns and closely spaced buildings.Single-home residential developments generally have lot sizes less than 1 acre.If the following are adjacent to, or within 0.25 mile of an urban zone, they must be included in the urban zone: golf courses, industrial parks, airports, maintained parks, mills or other industrial complexes, quarries, dams. However, if these are not within 0.25 mile of an urban zone and are >=40 acres, they are classified as a low-density residential area. If not within 0.25 mile of an urban zone and <40 acres, they are absorbed into the surrounding zone.Other: Zone 10Non-vegetated areas/large bodies of water >=640 acres.This zone contains only lava, sand, reservoirs, lakes, rivers, and mountain-top rock/snow.Development/Structure Count Notes"Developments" include individual buildings and/or clusters of buildings, which may or may not be related to the management of the land they are on.Each house/dwelling is considered a development, but a cluster of barns, storage sheds, garages, and other associated buildings is collectively considered as a single development.County tax parcel layers were used for reference, when available, in counting developments. There is generally zero or one development per parcel. If multiple structures are present within a single parcel, that parcel generally has one development counted regardless of the total number of structures.When interpreting developments for delineation of land use zones, "development" means developments not related to the usage of that zone. For example, when delineating an agricultural zone, farm houses do not count toward the number of developments per 640 acres. Zone Connectivity NotesIn areas where dominant land use is not clustered and easily defined, a number of different zones can be intermingled. In these instances, a maximum distance of 0.25 mi through other zones is used in zone delineation: in order to include a parcel or section of land in a zone, it must be within 0.25 mi of that zone."Stringers" are defined as any long, narrow section of a zone. Stringers must be less than 0.25 mi in length. A minimum width of 120 feet is required for all sections of a zone.Zones were drawn by county, therefore individual polygons may be under minimum acreage requirements if the zone continues across a county line.
Metadata
http://spatialdata.oregonexplorer.info/geoportal/rest/document?id=%7B66098644-28DB-4AFD-9D5A-202C090A6EB0%7D
Download
http://oe.oregonexplorer.info/ExternalContent/SpatialDataforDownload/OR_DZone_Polygons_2014.zip
Service Item Id: 42d3ecd3ee814a9e840f3832f64a1400
Copyright Text: U.S. Forest Service Pacific Northwest Research Station, Forest Inventory and Analysis (FIA) Program; Oregon Department of Forestry, Resources Planning Program; and Oregon State University Institute for Natural Resources.
Description: Interpreters used 2005 National Agricultural Imagery Program (NAIP) color digital orthophoto imagery with 1/2-meter spatial resolution to delineate land use zones, producing a statewide land use polygon layer for 2005. The photo interpretation was conducted in 2006. Minor corrections were made to this layer during the 2014 Development Zone Project updates carried out in 2015-2016.Land Use Zone DefinitionsWildland Forest: Zone 1Polygon is >=640 acres.Polygon has <=4 developments per 640 acres.The developments are generally scattered across the polygon.The polygon is >80% forest land, and the remainder is agricultural or "other" land except for the developments.Wildland Range: Zone 2 (Eastern Oregon Only)Polygon is >=640 acres.Polygon has <=4 developments per 640 acres.The developments are generally scattered across the polygon.The polygon is <51% forestland.Agricultural lands are <20% of the polygon.The remainder is undeveloped rangeland.Alternately, the polgon is >=50% rangeland, agricultural lands are <20% of the polygon, and wildland forest makes up the remainder.Mixed Forest/Agriculture: Zone 5Polygon is >=640 acres.This zone contains forest, range, and "other" lands intermingled with agricultural land. It also includes lightly forested areas where livestock grazing is suspected as a regular use of the understory.Polygon has <9 developments per 640 acres.The developments are generally scattered across the polygon.Agricultural land comprises 20% to 80% of the polygon, and the remainder is forest or "other" land except for the developments. Forest land is >=50% of the remainder.Improved road patterns are generally 0.5mile or greater.Mixed Range/Agriculture: Zone 6 (Eastern Oregon Only)Polygon is >=640 acres.This zone contains rangeland and agricultural land.Polygon has <9 developments per 640 acres.The developments are generally scattered across the polygon.Agricultural land comprises 20% to 80% of the polygon.The undeveloped portion (i.e., non-agricultural land) is <51% forestland.Improved road patterns are generally 0.5 mile or greater.Intensive Agriculture: Zone 7Polygon is >=640 acres.Polygon has <9 developments per 640 acres.The developments are generally scattered across the polygon.Agricultural land occupies >80% of the polygon, and the remainder is forest or "other" lands except for the developments.Low-Density Residential: Zone 8Polygon can be any size, but must have >=9 developments within it.The average acreage per development is generally less than 80 acres.Improved road patterns are typically 0.25 mile or less.The residential lot size is generally greater than 1 acre.This zone can also be a polygon that meets urban qualifications, but is less than 40 acres in size.Urban: Zone 9Polygon is >=40 acres.This is a commercial, service, and residential subdivided area with city road patterns and closely spaced buildings.Single-home residential developments generally have lot sizes less than 1 acre.If the following are adjacent to, or within 0.25 mile of an urban zone, they must be included in the urban zone: golf courses, industrial parks, airports, maintained parks, mills or other industrial complexes, quarries, dams. However, if these are not within 0.25 mile of an urban zone and are >=40 acres, they are classified as a low-density residential area. If not within 0.25 mile of an urban zone and <40 acres, they are absorbed into the surrounding zone.Other: Zone 10Non-vegetated areas/large bodies of water >=640 acres.This zone contains only lava, sand, reservoirs, lakes, rivers, and mountain-top rock/snow.Development/Structure Count Notes"Developments" include individual buildings and/or clusters of buildings, which may or may not be related to the management of the land they are on.Each house/dwelling is considered a development, but a cluster of barns, storage sheds, garages, and other associated buildings is collectively considered as a single development.County tax parcel layers were used for reference, when available, in counting developments. There is generally zero or one development per parcel. If multiple structures are present within a single parcel, that parcel generally has one development counted regardless of the total number of structures.When interpreting developments for delineation of land use zones, "development" means developments not related to the usage of that zone. For example, when delineating an agricultural zone, farm houses do not count toward the number of developments per 640 acres. Zone Connectivity NotesIn areas where dominant land use is not clustered and easily defined, a number of different zones can be intermingled. In these instances, a maximum distance of 0.25 mi through other zones is used in zone delineation: in order to include a parcel or section of land in a zone, it must be within 0.25 mi of that zone."Stringers" are defined as any long, narrow section of a zone. Stringers must be less than 0.25 mi in length. A minimum width of 120 feet is required for all sections of a zone.Zones were drawn by county, therefore individual polygons may be under minimum acreage requirements if the zone continues across a county line.
requirements if the zone continues across a county line.
Metadata
http://spatialdata.oregonexplorer.info/geoportal/rest/document?id=%7B66098644-28DB-4AFD-9D5A-202C090A6EB0%7D
Download
http://oe.oregonexplorer.info/ExternalContent/SpatialDataforDownload/OR_DZone_Polygons_2014.zip
Service Item Id: 42d3ecd3ee814a9e840f3832f64a1400
Copyright Text: U.S. Forest Service Pacific Northwest Research Station, Forest Inventory and Analysis (FIA) Program; Oregon Department of Forestry, Resources Planning Program; and Oregon State University Institute for Natural Resources.
Description: Interpreters used 2009 National Agricultural Imagery Program (NAIP) color digital orthophoto imagery with one-meter spatial resolution to update the 2005 Development Zone land use polygons, producing a statewide land use polygon layer for 2009. The photo interpretation was conducted in 2010. Minor corrections were made to this layer during the 2014 Development Zone Project updates carried out in 2015-2016.Land Use Zone DefinitionsWildland Forest: Zone 1Polygon is >=640 acres.Polygon has <=4 developments per 640 acres.The developments are generally scattered across the polygon.The polygon is >80% forest land, and the remainder is agricultural or "other" land except for the developments.Wildland Range: Zone 2 (Eastern Oregon Only)Polygon is >=640 acres.Polygon has <=4 developments per 640 acres.The developments are generally scattered across the polygon.The polygon is <51% forestland.Agricultural lands are <20% of the polygon.The remainder is undeveloped rangeland.Alternately, the polgon is >=50% rangeland, agricultural lands are <20% of the polygon, and wildland forest makes up the remainder.Mixed Forest/Agriculture: Zone 5Polygon is >=640 acres.This zone contains forest, range, and "other" lands intermingled with agricultural land. It also includes lightly forested areas where livestock grazing is suspected as a regular use of the understory.Polygon has <9 developments per 640 acres.The developments are generally scattered across the polygon.Agricultural land comprises 20% to 80% of the polygon, and the remainder is forest or "other" land except for the developments. Forest land is >=50% of the remainder.Improved road patterns are generally 0.5mile or greater.Mixed Range/Agriculture: Zone 6 (Eastern Oregon Only)Polygon is >=640 acres.This zone contains rangeland and agricultural land.Polygon has <9 developments per 640 acres.The developments are generally scattered across the polygon.Agricultural land comprises 20% to 80% of the polygon.The undeveloped portion (i.e., non-agricultural land) is <51% forestland.Improved road patterns are generally 0.5 mile or greater.Intensive Agriculture: Zone 7Polygon is >=640 acres.Polygon has <9 developments per 640 acres.The developments are generally scattered across the polygon.Agricultural land occupies >80% of the polygon, and the remainder is forest or "other" lands except for the developments.Low-Density Residential: Zone 8Polygon can be any size, but must have >=9 developments within it.The average acreage per development is generally less than 80 acres.Improved road patterns are typically 0.25 mile or less.The residential lot size is generally greater than 1 acre.This zone can also be a polygon that meets urban qualifications, but is less than 40 acres in size.Urban: Zone 9Polygon is >=40 acres.This is a commercial, service, and residential subdivided area with city road patterns and closely spaced buildings.Single-home residential developments generally have lot sizes less than 1 acre.If the following are adjacent to, or within 0.25 mile of an urban zone, they must be included in the urban zone: golf courses, industrial parks, airports, maintained parks, mills or other industrial complexes, quarries, dams. However, if these are not within 0.25 mile of an urban zone and are >=40 acres, they are classified as a low-density residential area. If not within 0.25 mile of an urban zone and <40 acres, they are absorbed into the surrounding zone.Other: Zone 10Non-vegetated areas/large bodies of water >=640 acres.This zone contains only lava, sand, reservoirs, lakes, rivers, and mountain-top rock/snow.Development/Structure Count Notes"Developments" include individual buildings and/or clusters of buildings, which may or may not be related to the management of the land they are on.Each house/dwelling is considered a development, but a cluster of barns, storage sheds, garages, and other associated buildings is collectively considered as a single development.County tax parcel layers were used for reference, when available, in counting developments. There is generally zero or one development per parcel. If multiple structures are present within a single parcel, that parcel generally has one development counted regardless of the total number of structures.When interpreting developments for delineation of land use zones, "development" means developments not related to the usage of that zone. For example, when delineating an agricultural zone, farm houses do not count toward the number of developments per 640 acres. Zone Connectivity NotesIn areas where dominant land use is not clustered and easily defined, a number of different zones can be intermingled. In these instances, a maximum distance of 0.25 mi through other zones is used in zone delineation: in order to include a parcel or section of land in a zone, it must be within 0.25 mi of that zone."Stringers" are defined as any long, narrow section of a zone. Stringers must be less than 0.25 mi in length. A minimum width of 120 feet is required for all sections of a zone.Zones were drawn by county, therefore individual polygons may be under minimum acreage requirements if the zone continues across a county line.
requirements if the zone continues across a county line.
Metadata
http://spatialdata.oregonexplorer.info/geoportal/rest/document?id=%7B66098644-28DB-4AFD-9D5A-202C090A6EB0%7D
Download
http://oe.oregonexplorer.info/ExternalContent/SpatialDataforDownload/OR_DZone_Polygons_2014.zip
Copyright Text: U.S. Forest Service Pacific Northwest Research Station, Forest Inventory and Analysis (FIA) Program; Oregon Department of Forestry, Resources Planning Program; and Oregon State University Institute for Natural Resources.
Description: Interpreters used 2014 National Agricultural Imagery Program (NAIP) color digital orthophoto imagery with one-meter spatial resolution to update the 2009 Development Zone land use polygons, producing a statewide land use polygon layer for 2014. The photo interpretation was conducted in 2015 and early 2016.Land Use Zone DefinitionsWildland Forest: Zone 1Polygon is >=640 acres.Polygon has <=4 developments per 640 acres.The developments are generally scattered across the polygon.The polygon is >80% forest land, and the remainder is agricultural or "other" land except for the developments.Wildland Range: Zone 2 (Eastern Oregon Only)Polygon is >=640 acres.Polygon has <=4 developments per 640 acres.The developments are generally scattered across the polygon.The polygon is <51% forestland.Agricultural lands are <20% of the polygon.The remainder is undeveloped rangeland.Alternately, the polgon is >=50% rangeland, agricultural lands are <20% of the polygon, and wildland forest makes up the remainder.Mixed Forest/Agriculture: Zone 5Polygon is >=640 acres.This zone contains forest, range, and "other" lands intermingled with agricultural land. It also includes lightly forested areas where livestock grazing is suspected as a regular use of the understory.Polygon has <9 developments per 640 acres.The developments are generally scattered across the polygon.Agricultural land comprises 20% to 80% of the polygon, and the remainder is forest or "other" land except for the developments. Forest land is >=50% of the remainder.Improved road patterns are generally 0.5mile or greater.Mixed Range/Agriculture: Zone 6 (Eastern Oregon Only)Polygon is >=640 acres.This zone contains rangeland and agricultural land.Polygon has <9 developments per 640 acres.The developments are generally scattered across the polygon.Agricultural land comprises 20% to 80% of the polygon.The undeveloped portion (i.e., non-agricultural land) is <51% forestland.Improved road patterns are generally 0.5 mile or greater.Intensive Agriculture: Zone 7Polygon is >=640 acres.Polygon has <9 developments per 640 acres.The developments are generally scattered across the polygon.Agricultural land occupies >80% of the polygon, and the remainder is forest or "other" lands except for the developments.Low-Density Residential: Zone 8Polygon can be any size, but must have >=9 developments within it.The average acreage per development is generally less than 80 acres.Improved road patterns are typically 0.25 mile or less.The residential lot size is generally greater than 1 acre.This zone can also be a polygon that meets urban qualifications, but is less than 40 acres in size.Urban: Zone 9Polygon is >=40 acres.This is a commercial, service, and residential subdivided area with city road patterns and closely spaced buildings.Single-home residential developments generally have lot sizes less than 1 acre.If the following are adjacent to, or within 0.25 mile of an urban zone, they must be included in the urban zone: golf courses, industrial parks, airports, maintained parks, mills or other industrial complexes, quarries, dams. However, if these are not within 0.25 mile of an urban zone and are >=40 acres, they are classified as a low-density residential area. If not within 0.25 mile of an urban zone and <40 acres, they are absorbed into the surrounding zone.Other: Zone 10Non-vegetated areas/large bodies of water >=640 acres.This zone contains only lava, sand, reservoirs, lakes, rivers, and mountain-top rock/snow.Development/Structure Count Notes"Developments" include individual buildings and/or clusters of buildings, which may or may not be related to the management of the land they are on.Each house/dwelling is considered a development, but a cluster of barns, storage sheds, garages, and other associated buildings is collectively considered as a single development.County tax parcel layers were used for reference, when available, in counting developments. There is generally zero or one development per parcel. If multiple structures are present within a single parcel, that parcel generally has one development counted regardless of the total number of structures.When interpreting developments for delineation of land use zones, "development" means developments not related to the usage of that zone. For example, when delineating an agricultural zone, farm houses do not count toward the number of developments per 640 acres. Zone Connectivity NotesIn areas where dominant land use is not clustered and easily defined, a number of different zones can be intermingled. In these instances, a maximum distance of 0.25 mi through other zones is used in zone delineation: in order to include a parcel or section of land in a zone, it must be within 0.25 mi of that zone."Stringers" are defined as any long, narrow section of a zone. Stringers must be less than 0.25 mi in length. A minimum width of 120 feet is required for all sections of a zone.Zones were drawn by county, therefore individual polygons may be under minimum acreage requirements if the zone continues across a county line.
requirements if the zone continues across a county line.
Metadata
http://spatialdata.oregonexplorer.info/geoportal/rest/document?id=%7B66098644-28DB-4AFD-9D5A-202C090A6EB0%7D
Download
http://oe.oregonexplorer.info/ExternalContent/SpatialDataforDownload/OR_DZone_Polygons_2014.zip
Service Item Id: 42d3ecd3ee814a9e840f3832f64a1400
Copyright Text: U.S. Forest Service Pacific Northwest Research Station, Forest Inventory and Analysis (FIA) Program; Oregon Department of Forestry, Resources Planning Program; and Oregon State University Institute for Natural Resources.
Description: This data layer is an element of the Oregon GIS Framework. Oregon's enterprise zones offer a unique resource to Oregon communities, and an excellent opportunity for businesses growing or locating in Oregon. Primarily, enterprise zones exempt businesses from local property taxes on new investments for a specified amount of time, which varies among the different zone programs.Sponsored by municipal or tribal governments, an enterprise zone typically serves as a focal point for local development efforts. There are currently 73 enterprise zones creating better opportunities for business investment across Oregon: 56 rural and 17 urban. For local governments interested in obtaining, retaining or amending a zone, guidance is available on these Web pages.http://www.oregon4biz.com/Oregon-Business/Tax-Incentives/Enterprise-Zones/Details/
Metadata
https://spatialdata.oregonexplorer.info/geoportal/details;id=35211e434d8141578bca4202e6192889
Download
ftp://ftp.gis.oregon.gov/adminbound/EnterpriseZones2020.zip
Description: This data layer is an element of the Oregon GIS Framework. Federal highway and transit statutes require, as a condition for spending federal highway or transit funds in urbanized areas, the designation of MPOs, which have responsibility for planning, programming and coordination of federal highway and transit investments. The federally designated MPOs are made up of large urban MPOs (population areas greater than 200,000): the Portland regional area, the Salem/Keizer area, and the Eugene/Springfield area; and small urban MPOs (population areas between 50,000 - 200,000): the Medford/Rogue Valley area, the Cities of Corvallis/Philomath, the City of Bend, Albany area, Middle Rogue, and Walla Walla Valley. Geographic Information Services (GIS) Unit, Oregon Department of Transportation (ODOT), 2013.
Metadata: http://spatialdata.oregonexplorer.info/geoportal/rest/document?id=%7B039CD9B7-D348-488D-9218-39105BBDA43E%7D
Download: http://oe.oregonexplorer.info/ExternalContent/SpatialDataforDownload/mpo_2013.zip
Description: As of April 18, 2014 this feature class contains zoning data from 156 local jursdictions. DLCD plans to continue adding to and updating this statewide zoning dataset as they receive zoning information from the local jurisdictions.Jurisdictions included in the 20140418 version of the statewide zoning geodatabase:Cities:Albany, Amity, Antelope, Ashland, Astoria, Barlow, Bay City, Beaverton, Bend, Bonanza, Brownsville, Butte Falls, Canby, Cannon Beach, Carlton, Cascade Locks, Cave Junction, Central Point, Chiloquin, Coburg, Columbia City, Cornelius, Corvallis, Cottage Grove, Creswell, Culver, Damascus, Dayton, Donald, Dufur, Dundee, Dunes City, Eagle Point, Estacada, Eugene, Fairview, Falls City, Forest Grove, Garibaldi, Gervais, Gladstone, Gold Hill, Grants Pass, Grass Valley, Halsey, Happy Valley, Harrisburg, Hermiston, Hillsboro, Hood River, Hubbard, Independence, Jacksonville, Johnson City, Junction City, Keizer, King City, Klamath Falls, La Pine, Lafayette, Lake Oswego, Lebanon, Lowell, Madras, Malin, Manzanita, Maupin, Maywood Park, Medford, Merrill, Metolius, Millersburg, Milwaukie, Molalla, Monmouth, Moro, Mosier, Myrtle Creek, Nehalem, Newberg, North Plains, Oakridge, Oregon City, Philomath, Phoenix, Portland, Prineville, Redmond, Rivergrove, Rockaway Beach, Rogue River, Rufus, Salem, Scappoose, Scio, Shady Cove, Shaniko, Sheridan, Sherwood, Silverton, Sisters, Sodaville, Springfield, St. Helens, Stayton, Sublimity, Sweet Home, Talent, Tangent, The Dalles, Tigard, Tillamook, Troutdale, Tualatin, Turner, Veneta, Vernonia, Warrenton, Wasco, Waterloo, West Linn, Westfir, Wheeler, Willamina, Wilsonville, Winston, Wood Village, Woodburn, Yamhill.Counties:Benton County, Clackamas County, Clatsop County, Columbia County, Coos County, Crook County, Curry County, Deschutes County, Douglas County, Hood River County, Jackson County, Jefferson County, Josephine County, Klamath County, Lane County, Lincoln County, Linn County, Marion County, Multnomah County, Polk County, Sherman County, Tillamook County, Wasco County, Washington County, Yamhill County.
Metadata
http://spatialdata.oregonexplorer.info/geoportal/rest/document?id=%7B9966F34D-71E7-4BD5-A91E-0D2757C91EBF%7D
Download
http://oe.oregonexplorer.info/ExternalContent/SpatialDataforDownload/OregonZoning_09_24_2014.zip
Description: As of April 18, 2014 this feature class contains zoning data from 156 local jursdictions. DLCD plans to continue adding to and updating this statewide zoning dataset as they receive zoning information from the local jurisdictions.Jurisdictions included in the 20140418 version of the statewide zoning geodatabase:Cities:Albany, Amity, Antelope, Ashland, Astoria, Barlow, Bay City, Beaverton, Bend, Bonanza, Brownsville, Butte Falls, Canby, Cannon Beach, Carlton, Cascade Locks, Cave Junction, Central Point, Chiloquin, Coburg, Columbia City, Cornelius, Corvallis, Cottage Grove, Creswell, Culver, Damascus, Dayton, Donald, Dufur, Dundee, Dunes City, Eagle Point, Estacada, Eugene, Fairview, Falls City, Forest Grove, Garibaldi, Gervais, Gladstone, Gold Hill, Grants Pass, Grass Valley, Halsey, Happy Valley, Harrisburg, Hermiston, Hillsboro, Hood River, Hubbard, Independence, Jacksonville, Johnson City, Junction City, Keizer, King City, Klamath Falls, La Pine, Lafayette, Lake Oswego, Lebanon, Lowell, Madras, Malin, Manzanita, Maupin, Maywood Park, Medford, Merrill, Metolius, Millersburg, Milwaukie, Molalla, Monmouth, Moro, Mosier, Myrtle Creek, Nehalem, Newberg, North Plains, Oakridge, Oregon City, Philomath, Phoenix, Portland, Prineville, Redmond, Rivergrove, Rockaway Beach, Rogue River, Rufus, Salem, Scappoose, Scio, Shady Cove, Shaniko, Sheridan, Sherwood, Silverton, Sisters, Sodaville, Springfield, St. Helens, Stayton, Sublimity, Sweet Home, Talent, Tangent, The Dalles, Tigard, Tillamook, Troutdale, Tualatin, Turner, Veneta, Vernonia, Warrenton, Wasco, Waterloo, West Linn, Westfir, Wheeler, Willamina, Wilsonville, Winston, Wood Village, Woodburn, Yamhill.Counties:Benton County, Clackamas County, Clatsop County, Columbia County, Coos County, Crook County, Curry County, Deschutes County, Douglas County, Hood River County, Jackson County, Jefferson County, Josephine County, Klamath County, Lane County, Lincoln County, Linn County, Marion County, Multnomah County, Polk County, Sherman County, Tillamook County, Wasco County, Washington County, Yamhill County.
Metadata
http://spatialdata.oregonexplorer.info/geoportal/rest/document?id={02E3325E-2C7C-46F1-9BC0-1AE23ED9FB17}
Download
http://oe.oregonexplorer.info/ExternalContent/SpatialDataforDownload/Oregon_Statewide_Zoning.zip
Description: Zoning Layer constructed by Benton County Development. Also Contains the Comprehensive Plan Data in the comp_plan field. The layer was constructed to support 1:24000 scale.
Metadata
http://oe.oregonexplorer.info/metadata/pln_bentonzoning_2004.htm
Download
http://oregonexplorer.info/ExternalContent/SpatialDataForDownload/pln_bentonzoning_2004.zip
Description: Jurisdictional and cartographic county areas for Oregon are derived from the State of Oregon's Bureau of Land Management (BLM OR) County Boundaries Polygon (cob_poly). Measure 49 related attribute data was derived from the Oregon Department of Land Conservation and Development (DLCD) Measure 49 database.
Description: This dataset is a record of statewide Measure 37 claims per township. Measure 37 claims were compiled by the Institute of Portland Metropolitan Studies-IMS. Measure 37 claims were joined to township polygons based on the corresponding township number and direction and range number and direction.
Metadata
http://oe.oregonexplorer.info/metadata/m37_townships.htm
Download
http://oregonexplorer.info/ExternalContent/SpatialDataForDownload/ORE_M37_Townships.zip
Description: Shows Measure 37 claims for 15 counties as complied by the Institute of Portland Mentropolitan Studies-IMS. Shows Measure 37 claims for all counties in the Willamette Valley, and Hood River County, the central Oregon coast (Lincoln, Douglas, and Lane), Crook and Deschutes counties in central Oregon, and Josephine and Jackson counties in central Oregon, and Josephine and Jackson counties in southern Oregon. These areas have been the most heavily impacted by acutal claims thus far (as of December 4, 2006.) .
Metadata
http://oe.oregonexplorer.info/metadata/m37_15co.htm
Download
http://oregonexplorer.info/ExternalContent/SpatialDataForDownload/ORE_M37_15_Counties.zip
Description: This dataset is a record of Measure 37 claims in Benton County. Measure 37 claims were compiled by the Institute of Portland Metropolitan Studies-IMS. Metadata
http://oe.oregonexplorer.info/metadata/M37_BentonCo.htm
Download
http://oregonexplorer.info/ExternalContent/SpatialDataForDownload/ORE_M37_Benton.zip
Description: This dataset is a record of Measure 37 claims in Douglas County. Measure 37 claims were compiled by the Institute of Portland Metropolitan Studies-IMS. Metadata
http://oe.oregonexplorer.info/metadata/M37_DouglasCo.htm
Download
http://oregonexplorer.info/ExternalContent/SpatialDataForDownload/UBE_Measure37_DouglasCo.zip