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.

This layer is a component of Countywide General-purpose Map.

The Digital Flood Insurance Rate Map (DFIRM) Database depicts flood risk information and supporting data used to develop the risk data. The primary risk classifications used are the 1-percent-annual-chance flood event, the 0.2-percent-annual- chance flood event, and areas of minimal flood risk. The DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA).

This layer is a component of Countywide General-purpose Map.

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.

This theme shows line and polygon representation of the jurisdictional and cartographic county perimeters for Oregon. (BLM, 2015)

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

Geospatial data about Marion County, Oregon Roads. Export to CAD, GIS, PDF, CSV and access via API.

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.

This product is for informational purposes and may not have been prepared for, or be suitable for legal, engineering, or surveying purposes.

Users of this information should review or consult the primary data and information sources to ascertain the usability of the information.

To access the tax lot layer you will need to contact the county Assessor's office. ORMAP is a statewide digital cadastral base map that is publicly accessible, continually maintained, supports the Oregon property tax system, supports a multi-purpose land information system, strives to comply with appropriate state and national standards, and will continue to be improved over time.

Clackamas, Clark, Multnomah, Washington, Polk, Columbia, Tillamook, Marion, Hood River, and Yamhill county boundaries in Oregon and Clark, Cowlitz, Skamania county boundary in Washington. Date of last data update: 2024-12-30 This is official RLIS data. Contact Person: Christine Rutan christine.rutan@oregonmetro.gov 503-797-1669 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/1437 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

Geospatial data about Marion County, Oregon Urban Growth Boundary. Export to CAD, GIS, PDF, CSV and access via API.

This data layer is an element of the Oregon GIS Framework. 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.

Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census and beyond, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

Geospatial data about Lane County, Oregon Major Rivers. Export to CAD, GIS, PDF, CSV and access via API.

FEMA Framework Basemap datasets comprise six of the seven FGDC themes of geospatial data that are used by most GIS applications (Note: the seventh framework theme, orthographic imagery, is packaged in a separate NFIP Metadata Profile): cadastral, geodetic control, governmental unit, transportation, general structures, hydrography (water areas & lines. These data include an encoding of the geographic extent of the features and a minimal number of attributes needed to identify and describe the features. (Source: Circular A16, p. 13)

description: This digital map database, compiled from previously published and unpublished data, and new mapping by the authors, represents the general distribution of bedrock and surficial deposits of the Deer Island 7.5-minute quadrangle. The database delineates map units that are identified by general age and lithology following the stratigraphic nomenclature of the U.S. Geological Survey. The scale of the source maps limits the spatial resolution (scale) of the database to 1:24,000 or smaller.; abstract: This digital map database, compiled from previously published and unpublished data, and new mapping by the authors, represents the general distribution of bedrock and surficial deposits of the Deer Island 7.5-minute quadrangle. The database delineates map units that are identified by general age and lithology following the stratigraphic nomenclature of the U.S. Geological Survey. The scale of the source maps limits the spatial resolution (scale) of the database to 1:24,000 or smaller.

Map showing public lands in Jackson County. The map document is 34 inches by 44 inches.

This dataset was created by Jackson County GIS by incoorporating fuels treatment data from various State, Local, and Federal agencies responsible for maintaining fuels treatment data. The feature class was developed for use within the Community and Agency Fuels Effectiveness (CAFE) map hosted by Jackson County through a federal grant. The fuels treatments are updated at least annually based on agency input.