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

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 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) System (MTS). The MTS 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 is usually 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 are often 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, 2024, 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 2024 BAS as well.

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=179 for the complete metadata.

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

© City of Portland, Oregon

This layer is sourced from CGIS Open Data.

This data contains the location and legend of mileposts markers (signs) on state owned highways.This GIS base layer can be used for planning purposes and as a reference layer on standard Oregon Department of Transportation (ODOT) city and county map formats. Full details: https://geohub-oregon-geo.hub.arcgis.com/datasets/oregon-geo::mileposts/about

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.

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).

Klamath Falls City Limits.. Maintained by Klamath County GIS Department. 305 Main St. Room 119, Klamath Falls, OR 97601

The 2022 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. The cartographic boundary files 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 generalized boundaries of most incorporated places in this file are based on those as of January 1, 2022, as reported through the Census Bureau's Boundary and Annexation Survey (BAS). The generalized boundaries of all CDPs are based on those delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

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 Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2020 Census blocks nest within every other 2020 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces

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 Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2020 Census blocks nest within every other 2020 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.

Area in which urban services are provided by the City of Portland. This includes some parts of Washington, Clackamas, and unincorporated Multnomah County.-- Additional Information: Category: Boundary Purpose: For mapping and analysis of areas where urban services are provided by the City of Portland. Update Frequency: Quarterly-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=52201

Current zoning for the City of Portland and unincorporated portions of Multnomah County that are administered by the city. Includes zoning designations, comprehensive plan designations, overlay zones, as well as plan, historic, and conservation districts. Districts are also available separately.-- Additional Information: Category: Zoning Purpose: Used for producing official zoning maps and for land use analysis. Update Frequency: As needed-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=53533

Urban Growth Boundaries (UGBs) define areas beyond the city limits that do or are slated to support urban services, thereby restraining urban sprawl out into farm and forest lands. This data is updated as the county is informed of changes to the UGB of area cities.

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 Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2020 Census blocks nest within every other 2020 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.

The 2020 cartographic boundary KMLs 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. The cartographic boundary files 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 generalized boundaries of most incorporated places in this file 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 CDPs based on those delineated as part of the Census Bureau's Participant Statistical Areas Program (PSAP) for the 2020 Census.

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 Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2020 Census blocks nest within every other 2020 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.

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 Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2020 Census blocks nest within every other 2020 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.