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

Portland Neighborhood association boundaries. BPS maintains GIS data under direction of ONI.-- Additional Information: Category: Boundary Purpose: Mapped by-law boundaries of Portland neighborhoods. Update Frequency: As Needed-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=53509

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/123 for the complete metadata.-- Additional Information: Category: Boundary Purpose: For mapping of jurisdictional boundaries in the Portland region. Update Frequency: Quarterly-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=53542

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.

Incorporated city boundaries in and around the Portland metropolitan area, derived from Boundary Commission and Oregon Secretary of State filed annexations. Date of last data update: 2025-07-21 This is official RLIS data. Contact Person: Clint Chiavarini clinton.chiavarini@oregonmetro.gov 503-797-1738 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/1436 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

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

Portland IDC Approved City Council Districts With Neighborhood boundariesWWW.PORTLAND.GOV/Auditor Created Date: 10-25-2023 WWW.PORTLAND.GOV/GIS Email: Maps@portlandoregon.gov

The basis for these features is U.S. Geological Survey Scientific Investigation Report 2017-5024 Flood Inundation Mapping Data for Johnson Creek near Sycamore, Oregon. The domain of the HEC-RAS hydraulic model is a 12.9 mile reach of Johnson Creek from just upstream of SE 174th Avenue in Portland, Oregon to its confluence with the Willamette River. Some of the hydraulics used in the model were taken from Federal Emergency Management Agency, 2010, Flood Insurance Study, City of Portland, Oregon, Multnomah, Clackamas and Washington Counties, Volume 1 of 3, November 26, 2010. The Digital Elevation Model (DEM) utilized for the project was developed from LiDAR data flown in 2015 and provided by the Oregon Department of Geology and Mineral Industries. Bridge decks are generally removed from DEMs as standard practice. Therefore, these features may be shown as inundated when they are not. Judgement should be used when estimating the usefulness of a bridge during flood flow. Comparing the bridge to the surrounding ground can be more informative in this respect than simply looking at the bridge itself. Two model plans were used in the creation of the flood layers. The first is a stable model plan using unsteady flow in which the maximum streamflow is held in place for a long period of time (a number of days) in order to replicate a steady model using an unsteady plan. The stable model plan produced the areas of uncertainty contained in the sycor_breach.shp shapefile. The second is an unstable model plan that uses unsteady flow in which the full hydrograph (rising and falling limb) is represented based on the hydrograph shape of the December 2015 peak annual flood. The unstable model plan produced the flood extent polygons contained in the sycor.shp shapefile and the depth rasters and represents the best estimate of flood inundation for the given streamflow at U.S. Geological Survey streamgage 14211500.

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.

Fire protection taxing districts in the Portland metropolitan region. The political boundaries for the fire districts represent where taxes are collected for that district. There are areas where the districts do not represent the response areas. Contractual agreements between the response organizations define differences between the political boundaries and their response areas. City service areas are not taxing districts and their boundary data is not maintained by Metro, therefore they are not included in this layer. Date of last data update: 2025-10-27 This is official RLIS data. Contact Person: Clint Chiavarini clinton.chiavarini@oregonmetro.gov 503-797-1738 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/696 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

The City boundaries layer 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.

Maximum height limits how tall a building can be. Maximum height limits vary by zone, and work with other development standards such as FAR or maximum building coverage to maintain the character of an area. See Zoning Code chapter 500 for details. https://www.portlandoregon.gov/bps/34563-- Additional Information: Category: Zoning Code Purpose: To regulate the scale of buildings and in keeping with the overall character of a zone. Update Frequency: As Needed-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=54385

Neighborhoods regions. Overlapping areas assigned to each neighborhood individually creating overlaps in the data.-- Additional Information: Category: Boundary Purpose: Identifies full area of each neighborhood individually with ID number to assign contact information. Update Frequency: As Needed-- Metadata Link https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=54371

Campus Institution boundaries in Chapter 150 of Zoning Code.-- Additional Information: Category: Zoning Code Purpose: Map campus boundaries. Update Frequency: Unknown-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=54603

The Transportation Systems Plan (TSP) is the long-range plan to guide transportation investments in Portland. Originally developed in 2002 and last updated in 2007, the TSP meets state and regional planning requirements and addresses local transportation needs for cost-effective street, transit, freight, bicycle and pedestrian infrastructure improvements. The plan will provide transportation options for residents, employees, visitors, and firms doing business in Portland, making it more convenient to walk, bike, take transit -- and drive less -- while meeting their daily needs. Forecasted 20 year revenues are only ? to ½ of the amount needed to implement the City and other agency candidate projects and programs. City staff will use performance-based evaluation criteria, along with public comments, to recommend which projects to place on the higher priority 'Financially Constrained' list in the 2015 TSP. TSP Project Areas represent area (polygon) locations of proposed transportation projects over the next 20 years. Planned TSP projects are also represented as lines (Comprehensive Plan TSP Project Lines) and areas (Comprehensive Plan TSP Project Areas) in separate GIS datasets.-- Additional Information: Category: Planning - Comprehensive Plan Purpose: For mapping TSP boundaries. Update Frequency: As Needed-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=52099

Portland's business districts and neighorhoods inherently support each other in many ways. Since 1986 Venture Portland has invested in the smart, strategic growth of Portland’s unique neighborhood business districts. These dynamic districts, which together make up a majority of the city’s businesses and nearly half of its jobs, play a vital role in Portland’s economic prosperity and collectively represent local, regional, national and international demand for goods and services.-- Additional Information: Category: Boundary Purpose: For mapping and analysis of business districts in Portland. Update Frequency: As Needed-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=53652

Boundaries representing the 4 Neighborhood District Coalition Offices-- Additional Information: Category: Boundary Purpose: Boundaries representing the 4 Neighborhood District Coalition Offices Update Frequency: As Needed-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=61159

Boundaries representing the 4 Neighborhood District Coalition Offices-- Additional Information: Category: Boundary Purpose: Boundaries representing the 4 Neighborhood District Coalition Offices Update Frequency: As Needed-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=61159

Willamette River Study Boundary by reach (North, Central, South Waterfront, South) for Planning purposes.-- Additional Information: Category: Boundary Purpose: Map river reach boundaries defined for River Environmental Planning. Update Frequency: Infrequent-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=60873

Freight district boundaries with linkages to Transportation System Plan (TSP) TransPlanIDs.-- Additional Information: Category: Boundary Purpose: For mapping and analysis of freight districts in the context of the Transportation System Plan. Update Frequency: Frequent-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=52502