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

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

This resource is a member of a series. 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. The TIGER/Line shapefiles include both incorporated places (legal entities) and census designated places or CDPs (statistical entities). An incorporated place is established to provide governmental functions for a concentration of people as opposed to a minor civil division (MCD), which generally is created to provide services or administer an area without regard, necessarily, to population. Places always nest within a state, but may extend across county and county subdivision boundaries. An incorporated place usually is a city, town, village, or borough, but can have other legal descriptions. CDPs are delineated for the decennial census as the statistical counterparts of incorporated places. CDPs are delineated to provide data for settled concentrations of population that are identifiable by name, but are not legally incorporated under the laws of the state in which they are located. The boundaries for CDPs often are defined in partnership with state, local, and/or tribal officials and usually coincide with visible features or the boundary of an adjacent incorporated place or another legal entity. CDP boundaries often change from one decennial census to the next with changes in the settlement pattern and development; a CDP with the same name as in an earlier census does not necessarily have the same boundary. The only population/housing size requirement for CDPs is that they must contain some housing and population. The boundaries of most incorporated places in this shapefile are as of January 1, 2023, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The boundaries of all CDPs were delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census, but some CDPs were added or updated through the 2023 BAS as well.

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

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.

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 2020 cartographic boundary shapefiles are simplified representations of selected geographic areas from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). These boundary files are specifically designed for small-scale thematic mapping. When possible, generalization is performed with the intent to maintain the hierarchical relationships among geographies and to maintain the alignment of geographies within a file set for a given year. Geographic areas may not align with the same areas from another year. Some geographies are available as nation-based files while others are available only as state-based files. 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. In MCD states where no MCD exists or no MCD is 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 generalized boundaries of legal MCDs are based on those as of January 1, 2020 as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The generalized boundaries of all CCDs, delineated in 21 states, are those as reported as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

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

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 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 data is maintained by and obtained from Metro Data Resource Center. Please go to http://rlisdiscovery.oregonmetro.gov/metadataviewer/display.cfm?meta_layer_id=123 for the complete metadata.

--Additional Information: Category: Boundary Purpose: No purpose information available. Update Frequency: Unknown

© City of Portland, Oregon

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

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.

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)

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). The file is georeferenced to earth's surface using the UTM projection and coordinate system. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12000.

The Assessor's real property viewer provides a simple, mobile-friendly mapping application to view property information for properties in Marion County. This application works in together with the Assessor's Property Records website to allow users to visualize the geographical setting of properties.

This data layer is an element of the Oregon GIS Framework. This theme delineates urban growth boundaries (UGBs) in the state of Oregon. The line work was created by various sources including the Oregon Department of Land Conservation and Development (DLCD), the Oregon Department of Transportation (ODOT), Metro Regional Council of Governments (Metro), county and city GIS departments, and the Oregon Department of Administrative Services - Geospatial Enterprise Office (DAS-GEO). UGB areas consist of unincorporated lands surrounding a city that show where the city plans to grow over the next 20 years. When a city needs to develop more residential, commercial, industrial, or public land, it annexes the needed area from its UGB. If a city runs out of needed land within the UGB, it can expand its UGB. Original UGBs were established under the Oregon Statewide Planning Goals in 1973 by the Oregon State Legislature (Senate Bill 100). Goal 14 of the statewide planning program is, "To provide for an orderly and efficient transition from rural to urban land use, to accommodate urban population and urban employment inside urban growth boundaries, to ensure efficient use of land, and to provide for livable communities." The process and requirements for designating and amending UGBs are in Oregon Administrative Rules, Chapter 660, Division 24 (OAR 660-024). Designating or amending a UGB requires a public process, as required by Planning Goal 1, followed by approval by both the city and county elected officials and acknowledgement by the DLCD. This process includes the city submitting a Post Acknowledgement Plan Amendment (PAPA) to DLCD to review for consistency with Goal 14. The PAPA submittal includes GIS files that delineate the changes to the UGB. DLCD aggregates the local GIS layers into the statewide UGB layer. UGB line work and attributes are verified with the city PAPA submittals entered in DLCD’s tabular database to ensure that all UGB updates reported to DLCD have been included in this dataset. UGBs that are currently in the appeal process at the time of publication of this layer are not included. The effDate attribute indicates the year in which the UGB amendment was acknowledged by DLCD. In 2022, DLCD acknowledged amendments to the following UGBs: Central Point, Dayton, Phoenix, and Turner. Corrections were also made to the Astoria and Condon UGBs to reflect the current acknowledged boundary.

Use the app to find the downloadable area within Jackson County - 2 Foot Contour MapThe 2-foot Contour Map shows contours that were derived from several different LiDAR projects in the Rogue Valley over the last 10 years. The map can be used to both download and view the contour data. To use the map, search or zoom in to an address. When zoomed in to a specific scale, the map will change from the downloadable areas layer to 2-foot interval contour lines. The LiDAR Project Dates layer can be used to identify the date when the elevation was collected in an area. Please note that data is available only for the valley floor areas at this time.The 2ft contours were created from 1-meter pixel DEM and then cleaned to remove very small elevation changes and to create a smooth contour line. This information should not be used to create topographic surveys or other applications where the precise elevation of a location is required. For additional information on LiDAR in Oregon or to download the source data, please visit the DOGAMI Lidar Viewer.The downloadable data is a zipped ESRI Shapefile and is projected to Oregon State Plane South (Intl Feet) with NAD 1983 datum.

This theme delineates Urban Growth Boundaries (UGBs) in the state of Oregon. Oregon land use laws limit development outside of urban growth boundaries. The line work was created by various sources including the Oregon Department of Land Conservation and Development (DLCD), the Oregon Department of Transportation (ODOT), Metro Regional Council of Governments (Metro), county and city GIS departments, and the Oregon Department of Administrative Services - Geospatial Enterprise Office (DAS-GEO).