This data is maintained by and obtained from Metro GIS. Click the link above to view the Metro GIS metadata for this dataset.
This data is maintained by and obtained from Metro Data Resource Center. Please go to https://gis.oregonmetro.gov/rlis-metadata/#/details/155 for the complete metadata.-- Additional Information: Category: Boundary Purpose: For use as a "base" layer on map products to shade county areas and in analysis to capture areas within each county. Update Frequency: None planned-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=155
The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. County subdivisions are the primary divisions of counties and their equivalent entities for the reporting of Census Bureau data. They include legally- recognized minor civil divisions (MCDs) and statistical census county divisions (CCDs), and unorganized territories. For the 2010 Census, the MCDs are the primary governmental and/or administrative divisions of counties in 29 States and Puerto Rico; Tennessee changed from having CCDs for Census 2000 to having MCDs for the 2010 Census. In MCD States where no MCD exists or is not defined, the Census Bureau creates statistical unorganized territories to complete coverage. The entire area of the United States, Puerto Rico, and the Island Areas are covered by county subdivisions. The boundaries of most legal MCDs are as of January 1, 2019, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CCDs, delineated in 20 states, are those as reported as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2010 Census.
Polygon vector map data covering urban growth boundaries for Lane County, Oregon containing 12 features.
Boundary GIS (Geographic Information System) data is spatial information that delineates the geographic boundaries of specific geographic features. This data typically includes polygons representing the outlines of these features, along with attributes such as names, codes, and other relevant information.
Boundary GIS data is used for a variety of purposes across multiple industries, including urban planning, environmental management, public health, transportation, and business analysis.
Available for viewing and sharing as a map in a Koordinates map viewer. This data is also available for export to DWG for CAD, PDF, KML, CSV, and GIS data formats, including Shapefile, MapInfo, and Geodatabase.
The purpose of the Oregon Department of Fish and Wildlife (ODFW or the Department) sage-grouse core area approach to conservation (OAR 635-140-0015) is ‘to address greater sage-grouse management from a conservation biology perspective that identifies the most productive populations and habitat that meets all life history needs.’ Under this overarching goal, ODFW identified and mapped sage-grouse habitats necessary to conserve 90% of Oregon’s greater sage-grouse population, defined as ‘Core Areas’, or 'core habitat'. Similarly, ODFW identified low-density habitats, which provide additional breeding, summer, and migratory habitats for Oregon’s greater sage-grouse populations. The ODFW sage-grouse core and low-density habitat map was originally delineated in 2011 as one component of the Oregon Sage-Grouse Conservation Assessment and Strategy (CAAS). Sage-grouse core areas were named in 2011, and these named core areas were adopted as Sage-Grouse Priority Areas for Conservation (PACs), a range-wide designation, by the Greater Sage-Grouse Conservation Objectives Team (COT) and published in the Team’s 2013 Report. ODFW sage-grouse core habitat and sage-grouse PACs are analogous.The Goal 5 sage-grouse rule (OAR 660-023-0115) was adopted by the Land Conservation and Development Commission (LCDC) in 2015. This rule defines core and low-density sage-grouse habitat and makes specific reference to the sage-grouse map delineated by ODFW and outlined in the CAAS. The LCDC adopted the 2011 ODFW sage-grouse core and low-density habitat map into OAR 660-023-0115 as the controlling document identifying significant sage-grouse habitat. The Goal 5 sage-grouse rule (OAR 660-023-0115) defines significant sage-grouse habitat and identifies types of land use that could conflict with the conservation of Oregon's sage-grouse populations. The Rule directs counties to review applications for development permits using the mitigation hierarchy (avoidance, minimization, and mitigation; defined in OAR 635-140-0000 through 0025) and sets development thresholds that limit the amount of significant sage-grouse habitat impacted due to new large-scale development.The core and low-density habitat map was updated by ODFW in 2023 with the Department's most recent sage-grouse data and the best available science, following the methodology outlined in the CAAS (see 'Sage-Grouse Core Area Habitat Categorization and Conservation Recommendations using ODFW Fish and Wildlife Habitat Mitigation Policy'). During the final phases of the update process, the draft map was reviewed by ODFW District Biologists, cooperating agency biologists, elected county officials or their representatives in counties with sage-grouse habitat, Oregon's Sage-Grouse Local Implementation Teams (LITs), conservation partners, and the public to ground-truth and refine the boundaries at a 1:10,000 scale. The updated core and low-density map adopted by the Oregon Fish and Wildlife Commission on 15 December 2023. Updated sage-grouse PAC boundaries were delineated within the final approved core habitat and appropriately named. The Department expects the LCDC to adopt the updated (2023) sage-grouse core and low-density habitat map as part of the Goal 5 sage-grouse rule (OAR 660-023-0115), thereby replacing the deprecated 2011 map. Until the updated (2023) sage-grouse habitat map is adopted by the LCDC to replace the 2011 map, the 2011 map will continue to apply for OAR 660-023-0115.Spatial ReferenceProjected Coordinate System: NAD 1983 Oregon Statewide Lambert (Intl Feet)Projection: Lambert Conformal ConicWKID: 2992Authority: EPSGLinear Unit: Feet (0.3048)Geographic Coordinate System: NAD 1983WKID: 4269Authority: EPSGAngular Unit: Degree (0.0174532925199433)Datum: D North American 1983
description: This dataset is a compilation of borehole temperature observations compiled by the Oregon Department of Geology and Mineral Industries, published as a web feature service, a web map service, an ESRI service and as an Excel spreadsheet for the National Geothermal Data System.The document contains 6 worksheets, including information about the template, notes related to revisions of the template, Resource provider information, the data, a field list (data mapping view) and a worksheet with vocabularies for use in populating the spreadsheet (data valid terms). Data from 5192 wells are included. Fields in the data table include ObservationURI, WellName, APINo, HeaderURI, OtherID, OtherName, BoreholeName, Operator, LeaseOwner, LeaseNo, SpudDate, EndedDrillingDate, WellType, Status, CommodityOfInterest, StatusDate, Function, Production, Field, County, State, PLSS_Meridians, TWP, RGE, Section, SectionPart, etc.; abstract: This dataset is a compilation of borehole temperature observations compiled by the Oregon Department of Geology and Mineral Industries, published as a web feature service, a web map service, an ESRI service and as an Excel spreadsheet for the National Geothermal Data System.The document contains 6 worksheets, including information about the template, notes related to revisions of the template, Resource provider information, the data, a field list (data mapping view) and a worksheet with vocabularies for use in populating the spreadsheet (data valid terms). Data from 5192 wells are included. Fields in the data table include ObservationURI, WellName, APINo, HeaderURI, OtherID, OtherName, BoreholeName, Operator, LeaseOwner, LeaseNo, SpudDate, EndedDrillingDate, WellType, Status, CommodityOfInterest, StatusDate, Function, Production, Field, County, State, PLSS_Meridians, TWP, RGE, Section, SectionPart, etc.
This layer is an inventory of existing landslides deposits in the Little North Santiam River Basin, Oregon (2009). Each landslide deposit shown on this map has been classified according to a number of specific characteristics identified at the time recorded in the GIS database. The classification scheme was developed by the Oregon Department of Geology and Mineral Industries (Burns and Madin, 2009). Several significant landslide characteristics recorded in the database are portrayed with symbology on this map. The specific characteristics shown for each landslide are the activity of landsliding, landslide features, deep or shallow failure, type of landslide movement, and confidence of landslide interpretation. These landslide characteristics are determined primarily on the basis of geomorphic features, or landforms, observed for each landslide.
This work was completed as part of the Master's thesis "Turbidity Monitoring and LiDAR Imagery Indicate Landslides are Primary Source of Suspended-Sediment Load in the Little North Santiam River Basin, Oregon, Winter 2009-2010" by Steven Sobieszczyk, Portland State University and U.S. Geological Survey.
Data layers in this geodatabase include: landslide deposit boundaries (Deposits); field-verfied location imagery (Photos); head scarp or scarp flanks (Scarp_Flanks); and secondary scarp features (Scarps).The geodatabase template was developed by the Oregon Department of Geology and Mineral Industries (Burns and Madin, 2009).
Not seeing a result you expected?
Learn how you can add new datasets to our index.
This data is maintained by and obtained from Metro GIS. Click the link above to view the Metro GIS metadata for this dataset.
This data is maintained by and obtained from Metro Data Resource Center. Please go to https://gis.oregonmetro.gov/rlis-metadata/#/details/155 for the complete metadata.-- Additional Information: Category: Boundary Purpose: For use as a "base" layer on map products to shade county areas and in analysis to capture areas within each county. Update Frequency: None planned-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=155