39 datasets found
  1. d

    Zoning

    • catalog.data.gov
    • data.oregon.gov
    • +3more
    Updated Jan 31, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Karen Grosulak-McCord (2025). Zoning [Dataset]. https://catalog.data.gov/dataset/zoning-5b12a
    Explore at:
    Dataset updated
    Jan 31, 2025
    Dataset provided by
    Karen Grosulak-McCord
    Description

    This Zoning feature class is an element of the Oregon GIS Framework statewide, Zoning spatial data. This version is authorized for public use. Attributes include zoning districts that have been generalized to state classes. As of June 30, 2023, this feature class contains zoning data from 229 local jurisdictions. 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 latest version of the statewide zoning geodatabase: Cities: Adams, Adrian, Albany, Amity, Antelope, Ashland, Astoria, Athena, Aurora, Banks, Barlow, Bay City, Beaverton, Bend, Boardman, Bonanza, Brookings, Brownsville, Burns, Butte Falls, Canby, Cannon Beach, Carlton, Cascade Locks, Cave Junction, Central Point, Chiloquin, Coburg, Columbia City, Coos Bay, Cornelius, Corvallis, Cottage Grove, Creswell, Culver, Dayton, Detroit, Donald, Drain, Dufur, Dundee, Dunes City, Durham, Eagle Point, Echo, Enterprise, Estacada, Eugene, Fairview, Falls City, Florence, Forest Grove, Fossil, Garibaldi, Gaston, Gates, Gearhart, Gervais, Gladstone, Gold Beach, Gold Hill, Grants Pass, Grass Valley, Gresham, Halsey, Happy Valley, Harrisburg, Helix, Hermiston, Hillsboro, Hines, Hood River, Hubbard, Idanha, Independence, Jacksonville, Jefferson, Johnson City, Jordan Valley, Junction City, Keizer, King City, Klamath Falls, La Grande, La Pine, Lafayette, Lake Oswego, Lebanon, Lincoln City, Lowell, Lyons, Madras, Malin, Manzanita, Maupin, Maywood Park, McMinnville, Medford, Merrill, Metolius, Mill City, Millersburg, Milton-Freewater, Milwaukie, Mitchell, Molalla, Monmouth, Moro, Mosier, Mount Angel, Myrtle Creek, Myrtle Point, Nehalem, Newberg, Newport, North Bend, North Plains, Nyssa, Oakridge, Ontario, Oregon City, Pendleton, Philomath, Phoenix, Pilot Rock, Port Orford, Portland, Prescott, Prineville, Rainier, Redmond, Reedsport, Rivergrove, Rockaway Beach, Rogue River, Roseburg, Rufus, Saint Helens, Salem, Sandy, Scappoose, Scio, Scotts Mills, Seaside, Shady Cove, Shaniko, Sheridan, Sherwood, Silverton, Sisters, Sodaville, Spray, Springfield, Stanfield, Stayton, Sublimity, Sutherlin, Sweet Home, Talent, Tangent, The Dalles, Tigard, Tillamook, Toledo, Troutdale, Tualatin, Turner, Ukiah, Umatilla, Vale, Veneta, Vernonia, Warrenton, Wasco, Waterloo, West Linn, Westfir, Weston, Wheeler, Willamina, Wilsonville, Winston, Wood Village, Woodburn, Yamhill. Counties: Baker County, Benton County, Clackamas County, Clatsop County, Columbia County, Coos County, Crook County, Curry County, Deschutes County, Douglas County, Harney County, Hood River County, Jackson County, Jefferson County, Josephine County, Klamath County, Lane County, Lincoln County, Linn County, Malheur County, Marion County, Multnomah County, Polk County, Sherman County, Tillamook County, Umatilla County, Union County, Wasco County, Washington County, Wheeler County, Yamhill County. R emaining jurisdictions either chose not to share data to incorporate into the public, statewide dataset or did not respond to DLCD’s request for data. These jurisdictions’ attributes are designated “not shared” in the orZDesc field and “NS” in the orZCode field.

  2. d

    Bancroft's Map of Oregon, Washington, Idaho and British Columbia

    • catalog.data.gov
    • esri-olympia-office.hub.arcgis.com
    • +1more
    Updated Nov 30, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Idaho Geospatial Data Clearinghouse (2020). Bancroft's Map of Oregon, Washington, Idaho and British Columbia [Dataset]. https://catalog.data.gov/dataset/bancrofts-map-of-oregon-washington-idaho-and-british-columbia
    Explore at:
    Dataset updated
    Nov 30, 2020
    Dataset provided by
    Idaho Geospatial Data Clearinghouse
    Area covered
    Idaho, British Columbia, Oregon
    Description

    This georectified digital map portrays Oregon, Washington, Idaho and British Columbia. Map date: 1863. The original paper map was scanned, georeferenced, and rectified to broaden access and to facilitate use in GIS software.Georeferenced source data: https://insideidaho.org/data/ago/uofi/library/historic-maps-spec/bancroftsMapOfORWAID.tif.zipNon-georeferenced source data: https://digital.lib.uidaho.edu/digital/collection/spec_hm/id/6/rec/1Original printed map is in Special Collections and Archives, University of Idaho Library, Moscow, ID 83844-2350; http://www.lib.uidaho.edu/special-collections/.

  3. a

    Boundary of Washington County, Oregon

    • washcoopendata-washco.hub.arcgis.com
    Updated Jan 1, 1990
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Washington County, Oregon (1990). Boundary of Washington County, Oregon [Dataset]. https://washcoopendata-washco.hub.arcgis.com/datasets/boundary-of-washington-county-oregon/about
    Explore at:
    Dataset updated
    Jan 1, 1990
    Dataset authored and provided by
    Washington County, Oregon
    Area covered
    Description

    Boundary of Washington County, Oregon.

  4. o

    Metro District Boundary

    • rlisdiscovery.oregonmetro.gov
    • hub.arcgis.com
    Updated Jan 1, 1988
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Metro (1988). Metro District Boundary [Dataset]. https://rlisdiscovery.oregonmetro.gov/datasets/drcMetro::metro-district-boundary/about
    Explore at:
    Dataset updated
    Jan 1, 1988
    Dataset authored and provided by
    Metro
    Area covered
    Description

    The political boundary showing the area that is subject to Metro's regulatory and taxing authority and the area that has elected representation on the Metro Council. The Oregon Legislature drew the Metro boundary that covers the Portland metropolitan area. Date of last data update: 2025-06-23 This is official RLIS data. Contact Person: Al Mowbray al.mowbray@oregonmetro.gov 503-797-1843 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/177 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

  5. o

    Hillshade -- 10 meter

    • rlisdiscovery.oregonmetro.gov
    Updated Feb 1, 2008
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Metro (2008). Hillshade -- 10 meter [Dataset]. https://rlisdiscovery.oregonmetro.gov/maps/0f4713a375094b018107a67f1b799743
    Explore at:
    Dataset updated
    Feb 1, 2008
    Dataset authored and provided by
    Metro
    Description

    This is a 10 meter Hillshade file created by Metro from USGS DEM data provided by the BLM. It covers the 3-county area (Washington, Multnomah, and Clackamas Counties). Date of last data update: 2004 This is official RLIS data. Contact Person: Joe Gordon joe.gordon@oregonmetro.gov 503-797-1587 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/2162 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

  6. a

    Tax Lots

    • washcoopendata-washco.hub.arcgis.com
    Updated Jul 4, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Washington County, Oregon (2020). Tax Lots [Dataset]. https://washcoopendata-washco.hub.arcgis.com/datasets/tax-lots/about
    Explore at:
    Dataset updated
    Jul 4, 2020
    Dataset authored and provided by
    Washington County, Oregon
    Area covered
    Description

    Tax lots, right-of-way outlines and tax account numbers as represented on Washington County Assessment & Taxation records. Each lot is a polygon with an associated tax lot number which is the "hook" to A&T's tabular data base. Selected items from the Assessor's file are included.

  7. a

    County Boundaries

    • gis-pdx.opendata.arcgis.com
    • hub.arcgis.com
    Updated May 24, 2023
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Portland, Oregon (2023). County Boundaries [Dataset]. https://gis-pdx.opendata.arcgis.com/datasets/county-boundaries
    Explore at:
    Dataset updated
    May 24, 2023
    Dataset authored and provided by
    City of Portland, Oregon
    Area covered
    Description

    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

  8. Digital Geologic-GIS Map of Whitman Mission National Historic Site and...

    • catalog.data.gov
    Updated Jun 5, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    National Park Service (2024). Digital Geologic-GIS Map of Whitman Mission National Historic Site and Vicinity, Washington and Oregon (NPS, GRD, GRI, WHMI, WHMI digital map) adapted from a Washington Division of Geology and Earth Resources Geologic Map by Derkey, Stradling, Lindsey and Tolan (2006) [Dataset]. https://catalog.data.gov/dataset/digital-geologic-gis-map-of-whitman-mission-national-historic-site-and-vicinity-washington
    Explore at:
    Dataset updated
    Jun 5, 2024
    Dataset provided by
    National Park Servicehttp://www.nps.gov/
    Description

    The Digital Geologic-GIS Map of Whitman Mission National Historic Site and Vicinity, Washington and Oregon is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (whmi_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (whmi_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (whmi_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) this file (whmi_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (whmi_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (whmi_geology_metadata_faq.pdf). Please read the whmi_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: Washington Division of Geology and Earth Resources. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (whmi_geology_metadata.txt or whmi_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

  9. a

    Land Use Districts (zoning / plan)

    • washcoopendata-washco.hub.arcgis.com
    Updated Sep 12, 2015
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Washington County, Oregon (2015). Land Use Districts (zoning / plan) [Dataset]. https://washcoopendata-washco.hub.arcgis.com/datasets/land-use-districts-zoning-plan
    Explore at:
    Dataset updated
    Sep 12, 2015
    Dataset authored and provided by
    Washington County, Oregon
    Area covered
    Description

    Washington County's plan designations for both the urban and rural portions of the unincorporated area. This data represents the adopted land use districts for the eleven urban community plans, Comprehensive Framework Plan for the Urban Area and the Rural/Natural Resource Plan.

  10. A

    Digital Geologic map of Whitman Mission National Historic Site and vicinity,...

    • data.amerigeoss.org
    xml, zip
    Updated Sep 22, 2008
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    United States (2008). Digital Geologic map of Whitman Mission National Historic Site and vicinity, Washington and Oregon (NPS, GRD, GRE, WHMI, WHMI digital map) [Dataset]. https://data.amerigeoss.org/pl/dataset/digital-geologic-map-of-whitman-mission-national-historic-site-and-vicinity-washington-and-oreg
    Explore at:
    zip, xmlAvailable download formats
    Dataset updated
    Sep 22, 2008
    Dataset provided by
    United States
    Area covered
    Oregon
    Description

    The Digital Geologic map of Whitman Mission National Historic Site and vicinity, Washington and Oregon is composed of GIS data layers complete with ArcMap 9.2 layer (.LYR) files, two ancillary GIS tables, a Windows Help File with ancillary map text, figures and tables, a FGDC metadata record and a 9.2 ArcMap (.MXD) Document that displays the digital map in 9.2 ArcGIS. The data were completed as a component of the Geologic Resource Evaluation (GRE) program, a National Park Service (NPS) Inventory and Monitoring (I&M) funded program that is administered by the NPS Geologic Resources Division (GRD). Source geologic maps and data used to complete this GRE digital dataset were provided by the following: Washington Division of Geology and Earth Resources. Detailed information concerning the sources used and their contribution the GRE product are listed in the Source Citation sections(s) of this metadata record (whmi_metadata.txt; available at http://nrdata.nps.gov/whmi/nrdata/geology/gis/whmi_metadata.xml). All GIS and ancillary tables were produced as per the NPS GRE Geology-GIS Geodatabase Data Model v. 2.0. (available at: http://science.nature.nps.gov/im/inventory/geology/GeologyGISDataModel.cfm). The GIS data is available as a 9.2 personal geodatabase (whmi_geology.mdb), and as shapefile (.SHP) and DBASEIV (.DBF) table files. The GIS data projection is NAD83, UTM Zone 11N. That data is within the area of interest of Whitman Mission National Historic Site.

  11. K

    Oregon City, Oregon Building Outlines

    • koordinates.com
    csv, dwg, geodatabase +6
    Updated Apr 23, 2019
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Oregon City, Oregon (2019). Oregon City, Oregon Building Outlines [Dataset]. https://koordinates.com/layer/99988-oregon-city-oregon-building-outlines/
    Explore at:
    pdf, csv, mapinfo tab, kml, mapinfo mif, dwg, geodatabase, geopackage / sqlite, shapefileAvailable download formats
    Dataset updated
    Apr 23, 2019
    Dataset authored and provided by
    Oregon City, Oregon
    Area covered
    Description

    Geospatial data about Oregon City, Oregon Building Outlines. Export to CAD, GIS, PDF, CSV and access via API.

  12. a

    City and County Comprehensive Plan Designations

    • arc-gis-hub-home-arcgishub.hub.arcgis.com
    • data.oregon.gov
    • +4more
    Updated May 31, 2019
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    State of Oregon (2019). City and County Comprehensive Plan Designations [Dataset]. https://arc-gis-hub-home-arcgishub.hub.arcgis.com/datasets/76882e24c07b41949bfdd5a6a0e60b81
    Explore at:
    Dataset updated
    May 31, 2019
    Dataset authored and provided by
    State of Oregon
    Area covered
    Description

    The data was collected from local jurisdictions in the state and then assembled into a single dataset. The attributes were generalized to a set of comp plan codes that could be applied to data from all jurisdictions. The list of state comp plan codes and their descriptions can be found in this metadata. Please contact the local jurisdictions for the more detailed (not generalized) data. As of May 31, 2019 this feature class contains comprehensive plan data from 189 local jurisdictions. DLCD plans to continue adding to and updating this statewide comp plan dataset as they receive information from the local jurisdictions. New releases of this data by DLCD are planned for publication every 2 years. Note: This data layer has gaps in the data and is not complete for the entire state of Oregon. Participating cities and counties are listed below. City data included:Adams, Adrian, Albany, Amity, Arlington, Ashland, Athena, Aumsville, Aurora, Baker City, Bandon, Bay City, Bend, Burns, Canby, Cannon Beach, Canyonville, Carlton, Cave Junction, Central Point, Clatskanie, Coburg, Columbia City, Condon, Coos Bay, Corvallis, Cottage Grove, Creswell, Culver, Dallas, Depoe Bay, Detroit, Donald, Dufur, Dundee, Dunes City, Eagle Point, Enterprise, Eugene, Falls City, Florence, Garibaldi, Gaston, Gates, Gearhart, Gervais, Glendale, Gold Hill, Grants Pass, Grass Valley, Haines, Harrisburg, Hermiston, Hines, Hubbard, Huntington, Idanha, Independence, Jacksonville, Jefferson, Jordan Valley, Joseph, Junction City, Keizer, La Pine, Lafayette, Lakeview, Lebanon, Lincoln City, Lostine, Lowell, Lyons, Madras, Malin, Manzanita, Maupin, Medford, Metolius, Mill City, Millersburg, Milton-Freewater, Monmouth, Mosier, Mt. Angel, Myrtle Creek, Nehalem, Newberg, Newport, North Bend, Nyssa, Oakridge, Ontario, Paisley, Philomath, Phoenix, Prineville, Redmond, Richland, Riddle, Rockaway Beach, Rogue River, Roseburg, Salem, Scappoose, Scio, Scotts Mills, Seaside, Seneca, Shady Cove, Shaniko, Sheridan, Silverton, Sisters, Sodaville, St. Helens, St. Paul, Stanfield, Stayton, Sublimity, Sweet Home, Talent, Tangent, The Dalles, Tillamook, Turner, Umatilla, Vale, Veneta, Vernonia, Wallowa, Westfir, Wheeler, Willamina, Woodburn and all the cities in Metro.County data included:Baker, Benton, Clackamas, Clatsop, Columbia, Coos, Crook, Deschutes, Douglas, Grant, Harney, Hood River, Jackson, Jefferson, Josephine, Klamath, Lake, Lane, Linn, Malheur, Marion, Multnomah, Polk, Tillamook, Umatilla, Wallowa, Wasco, Washington and Yamhill

  13. Mapped forest resources for Washington and Oregon, from a 1930s survey

    • agdatacommons.nal.usda.gov
    bin
    Updated Jan 22, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Constance A. Harrington (2025). Mapped forest resources for Washington and Oregon, from a 1930s survey [Dataset]. http://doi.org/10.2737/RDS-2023-0064
    Explore at:
    binAvailable download formats
    Dataset updated
    Jan 22, 2025
    Dataset provided by
    U.S. Department of Agriculture Forest Servicehttp://fs.fed.us/
    Authors
    Constance A. Harrington
    License

    CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
    License information was derived automatically

    Area covered
    Washington, Oregon
    Description

    Forest resources in Washington and Oregon were surveyed in the 1930s by employees of the USDA Forest Service, Pacific Northwest Forest Experiment Station. As part of this process, forest cover maps were created on paper at an original scale of 1:253,440. Forest and land cover types recorded include classifications such as: agricultural, balsam fir mountain hemlock, cedar-redwood, deforested burns, Douglas-fir, hardwood, juniper, lodgepole pine, non-forest pine mix, ponderosa pine, recent cutover, spruce-hemlock, subalpine and non-commercial, water, etc. An additional subcategory classification is also provided which gives additional insight into tree size classes for conifers or species group for hardwoods. These forest and land cover types are provided as both a shapefile and geopackage for Washington and Oregon combined.The 1928 McSweeney-McNary Forestry Research Act (P.L. 70-466, 45 Stat. 699-702) directed the Secretary of Agriculture to make and keep current a comprehensive inventory and analysis of the nation's forest resources. The decision was made to begin the nationwide survey with the Douglas-fir region and shortly thereafter to expand to the other forested lands of Washington and Oregon. Surveys were conducted between 1930 and 1936. Results of these surveys were reported in many formats including quarter state maps (4 maps per state) as well as many printed reports.The history of this project and copies of some of the early results as well, were published in Harrington (2003) which included a CD with a digital map (an ArcView GIS shapefile) for all of Washington and Oregon.

  14. d

    Shoreline Data Rescue Project of Lower Columbia River, Washington and...

    • catalog.data.gov
    • fisheries.noaa.gov
    Updated Oct 31, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    NGS Communications and Outreach Branch (Point of Contact, Custodian) (2024). Shoreline Data Rescue Project of Lower Columbia River, Washington and Oregon, PH50 [Dataset]. https://catalog.data.gov/dataset/shoreline-data-rescue-project-of-lower-columbia-river-washington-and-oregon-ph501
    Explore at:
    Dataset updated
    Oct 31, 2024
    Dataset provided by
    NGS Communications and Outreach Branch (Point of Contact, Custodian)
    Area covered
    Shoreline, Washington, Oregon, Columbia River
    Description

    These data were automated to provide an accurate high-resolution historical shoreline of Lower Columbia River, Washington and Oregon suitable as a geographic information system (GIS) data layer. These data are derived from shoreline maps that were produced by the NOAA National Ocean Service including its predecessor agencies which were based on an office interpretation of imagery and/or field survey. The NGS attribution scheme 'Coastal Cartographic Object Attribute Source Table (C-COAST)' was developed to conform the attribution of various sources of shoreline data into one attribution catalog. C-COAST is not a recognized standard, but was influenced by the International Hydrographic Organization's S-57 Object-Attribute standard so the data would be more accurately translated into S-57. This resource is a member of https://www.fisheries.noaa.gov/inport/item/39808

  15. d

    Shoreline Data Rescue Project of Columbia River to Clatop Plains, Washington...

    • catalog.data.gov
    • datasets.ai
    • +1more
    Updated Oct 31, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    NGS Communications and Outreach Branch (Point of Contact, Custodian) (2024). Shoreline Data Rescue Project of Columbia River to Clatop Plains, Washington and Oregon, PH155A [Dataset]. https://catalog.data.gov/dataset/shoreline-data-rescue-project-of-columbia-river-to-clatop-plains-washington-and-oregon-ph155a1
    Explore at:
    Dataset updated
    Oct 31, 2024
    Dataset provided by
    NGS Communications and Outreach Branch (Point of Contact, Custodian)
    Area covered
    Columbia River, Oregon
    Description

    These data were automated to provide an accurate high-resolution historical shoreline of Columbia River to Clatop Plains, Washington and Oregon suitable as a geographic information system (GIS) data layer. These data are derived from shoreline maps that were produced by the NOAA National Ocean Service including its predecessor agencies which were based on an office interpretation of imagery and/or field survey. The NGS attribution scheme 'Coastal Cartographic Object Attribute Source Table (C-COAST)' was developed to conform the attribution of various sources of shoreline data into one attribution catalog. C-COAST is not a recognized standard, but was influenced by the International Hydrographic Organization's S-57 Object-Attribute standard so the data would be more accurately translated into S-57. This resource is a member of https://inport.nmfs.noaa.gov/inport/item/39808

  16. d

    County Lines

    • catalog.data.gov
    • geohub.oregon.gov
    • +2more
    Updated Jan 31, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Bureau of Land Management (2025). County Lines [Dataset]. https://catalog.data.gov/dataset/county-lines
    Explore at:
    Dataset updated
    Jan 31, 2025
    Dataset provided by
    Bureau of Land Management
    Description

    COB_ARC: This theme shows line representation of the jurisdictional and cartographic county perimeters for Oregon and Washington.

  17. O

    Existing Vegetation

    • data.oregon.gov
    • geohub.oregon.gov
    • +2more
    csv, xlsx, xml
    Updated May 31, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2024). Existing Vegetation [Dataset]. https://data.oregon.gov/dataset/Existing-Vegetation/e3ii-23iy
    Explore at:
    xml, xlsx, csvAvailable download formats
    Dataset updated
    May 31, 2024
    Description

    This is a dataset download, not a document. The Open Document button will start the download.

    This data layer is an element of the Oregon GIS Framework. This data layer represents the Existing Vegetation data element. This statewide grid was created by combining four independently-generated datasets: one for western Oregon (USGS zones 2 and 7), and two for eastern Oregon (USGS zones 8 and 9; forested and non-forested lands), and selected wetland types from the Oregon Wetlands geodatabase. The landcover grid for zones 2 and 7 was produced using a modification of Breiman's Random Forest classifier to model landcover. Multi-season satellite imagery (Landsat ETM+, 1999-2003) and digital elevation model (DEM) derived datasets (e.g. elevation, landform, aspect, etc.) were utilized to build two predictive models for the forested landcover classes, and the nonforested landcover classes. The grids resulting from the models were then modified to improve the distribution of the following classes: volcanic systems and wetland vegetation. Along the eastern edge, the sagebrush systems were modified to help match with the map for the adjacent region. Additional classes were then layered on top of the modified models from other sources. These include disturbed classes (harvested and burned), cliffs, riparian, and NLCD's developed, agriculture, and water classes. A validation for forest classes was performed on a withheld of the sample data to assess model performance. Due to data limitations, the nonforest classes were evaluated using the same data that were used to build the original nonforest model. Two independent grids were combined to map landcover in adjacent zones 8 and 9. Tree canopy greater than 10% (from NLCD 2001), complemented with a disturbance grid, served as a mask to delineate forested areas. A grid of non-forested areas was extracted from a larger, regional grid (Sagemap) created using decision tree classifier and other techniques. Multi-season satellite imagery (Landsat ETM+, 1999-2003) and digital elevation model (DEM) derived datasets (e.g. elevation, landform, aspect, etc.) were utilized to derive rule sets for the various landcover classes. Eleven mapping areas, each characterized by similar ecological and spectral characteristics, were modeled independently of one another and mosaicked. An internal validation for modeled classes was performed on a withheld 20% of the sample data to assess model performance. The portion of this original grid corresponding to USGS map zones 8 and 9 was extracted and split into three mapping areas (one for USGS zone 8, two for USGS zone 9: Northern Basin and Range in the south, Blue Mountains in the north) and modified to improve the distribution of the following classes: cliffs, subalpine zone, dunes, lava flows, silver sagebrush, ash beds, playas, scabland, and riparian vegetation. Agriculture and urban areas were extracted from NLCD 2001. A forest grid was generated using Gradient Nearest Neighbor (GNN) imputation process. GNN uses multivariate gradient modeling to integrate data from regional grids of field plots with satellite imagery and mapped environmental data. A suite of fine-scale plot variables is imputed to each pixel in a digital map, and regional maps can be created for most of the same vegetation attributes available from the field plots. However, due to lack of sampling plots in the southern half of zone 9, the GNN model proved unreliable there; forest data from Landfire were used instead. To compensate for known under-representation of wetlands, selected wetland types from the Oregon Wetlands Geodatabase (version 2009-1030) were converted to raster and overlaid (replaced) pixel value assignments from the previous steps just detailed. See Process Steps for more information. The ecological systems were crosswalked to landcover (based on Oregon landcover standard, modified from NLCD 2001) and to wildlife habitats (based on integrated habitats used in the Oregon, Washington, and Idaho Dept of Fish & Wildlife conservation strategies). These codes and names are included in the value attribute table provided with the ecological systems grid.

  18. d

    BLM OR Oregon Washington State Boundary Polygon Hub

    • catalog.data.gov
    • res1catalogd-o-tdatad-o-tgov.vcapture.xyz
    Updated Nov 20, 2024
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Bureau of Land Management (2024). BLM OR Oregon Washington State Boundary Polygon Hub [Dataset]. https://catalog.data.gov/dataset/blm-or-oregon-washington-state-boundary-polygon-hub-57bbe
    Explore at:
    Dataset updated
    Nov 20, 2024
    Dataset provided by
    Bureau of Land Management
    Area covered
    Oregon
    Description

    state_poly: This theme shows the jurisdictional and cartographic state perimeters for Oregon and Washington.

  19. a

    Windshield Survey Map Sector Boundary

    • geo-orgig.hub.arcgis.com
    Updated Oct 3, 2019
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Washington County, Oregon (2019). Windshield Survey Map Sector Boundary [Dataset]. https://geo-orgig.hub.arcgis.com/datasets/washco::windshield-survey-map-sector-boundary
    Explore at:
    Dataset updated
    Oct 3, 2019
    Dataset authored and provided by
    Washington County, Oregon
    Area covered
    Description

    The polygons in the feature class are used to divide Washington County, and Northwest Clackamas County into the map sectors. The sectors are of as suitable size for a single inspection team of staff in a vehicle to drive to each facility within the sector and visually assess its functional status.

  20. a

    BLM Districts (Oregon and Washington)

    • oregon-explorer-osugisci.hub.arcgis.com
    Updated Jun 17, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Oregon State University GISci (2025). BLM Districts (Oregon and Washington) [Dataset]. https://oregon-explorer-osugisci.hub.arcgis.com/datasets/blm-districts-oregon-and-washington
    Explore at:
    Dataset updated
    Jun 17, 2025
    Dataset authored and provided by
    Oregon State University GISci
    Area covered
    Description

    DOB_LAND_POLY: This theme shows the polygon representation of Bureau of Land Management Districts for Oregon and Washington up to the coastline and including the off-shore islands within the district boundaries.For more information see: https://gbp-blm-egis.hub.arcgis.com/datasets/BLM-EGIS::blm-or-district-boundary-polygon-hub/about

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
Karen Grosulak-McCord (2025). Zoning [Dataset]. https://catalog.data.gov/dataset/zoning-5b12a

Zoning

Explore at:
Dataset updated
Jan 31, 2025
Dataset provided by
Karen Grosulak-McCord
Description

This Zoning feature class is an element of the Oregon GIS Framework statewide, Zoning spatial data. This version is authorized for public use. Attributes include zoning districts that have been generalized to state classes. As of June 30, 2023, this feature class contains zoning data from 229 local jurisdictions. 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 latest version of the statewide zoning geodatabase: Cities: Adams, Adrian, Albany, Amity, Antelope, Ashland, Astoria, Athena, Aurora, Banks, Barlow, Bay City, Beaverton, Bend, Boardman, Bonanza, Brookings, Brownsville, Burns, Butte Falls, Canby, Cannon Beach, Carlton, Cascade Locks, Cave Junction, Central Point, Chiloquin, Coburg, Columbia City, Coos Bay, Cornelius, Corvallis, Cottage Grove, Creswell, Culver, Dayton, Detroit, Donald, Drain, Dufur, Dundee, Dunes City, Durham, Eagle Point, Echo, Enterprise, Estacada, Eugene, Fairview, Falls City, Florence, Forest Grove, Fossil, Garibaldi, Gaston, Gates, Gearhart, Gervais, Gladstone, Gold Beach, Gold Hill, Grants Pass, Grass Valley, Gresham, Halsey, Happy Valley, Harrisburg, Helix, Hermiston, Hillsboro, Hines, Hood River, Hubbard, Idanha, Independence, Jacksonville, Jefferson, Johnson City, Jordan Valley, Junction City, Keizer, King City, Klamath Falls, La Grande, La Pine, Lafayette, Lake Oswego, Lebanon, Lincoln City, Lowell, Lyons, Madras, Malin, Manzanita, Maupin, Maywood Park, McMinnville, Medford, Merrill, Metolius, Mill City, Millersburg, Milton-Freewater, Milwaukie, Mitchell, Molalla, Monmouth, Moro, Mosier, Mount Angel, Myrtle Creek, Myrtle Point, Nehalem, Newberg, Newport, North Bend, North Plains, Nyssa, Oakridge, Ontario, Oregon City, Pendleton, Philomath, Phoenix, Pilot Rock, Port Orford, Portland, Prescott, Prineville, Rainier, Redmond, Reedsport, Rivergrove, Rockaway Beach, Rogue River, Roseburg, Rufus, Saint Helens, Salem, Sandy, Scappoose, Scio, Scotts Mills, Seaside, Shady Cove, Shaniko, Sheridan, Sherwood, Silverton, Sisters, Sodaville, Spray, Springfield, Stanfield, Stayton, Sublimity, Sutherlin, Sweet Home, Talent, Tangent, The Dalles, Tigard, Tillamook, Toledo, Troutdale, Tualatin, Turner, Ukiah, Umatilla, Vale, Veneta, Vernonia, Warrenton, Wasco, Waterloo, West Linn, Westfir, Weston, Wheeler, Willamina, Wilsonville, Winston, Wood Village, Woodburn, Yamhill. Counties: Baker County, Benton County, Clackamas County, Clatsop County, Columbia County, Coos County, Crook County, Curry County, Deschutes County, Douglas County, Harney County, Hood River County, Jackson County, Jefferson County, Josephine County, Klamath County, Lane County, Lincoln County, Linn County, Malheur County, Marion County, Multnomah County, Polk County, Sherman County, Tillamook County, Umatilla County, Union County, Wasco County, Washington County, Wheeler County, Yamhill County. R emaining jurisdictions either chose not to share data to incorporate into the public, statewide dataset or did not respond to DLCD’s request for data. These jurisdictions’ attributes are designated “not shared” in the orZDesc field and “NS” in the orZCode field.

Search
Clear search
Close search
Google apps
Main menu