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

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

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

This feature class identifies the legal speed limit for Portland streets. Not every street segment in the City is included. The dataset includes the speed limits for surface streets where the limit was implemented by an ODOT speed zone order or where a speed limit was authorized by statutes governing speeds in business districts, around schools, along roadways with bicycle or pedestrian improvements, or on non-arterial, residential streets.-- Additional Information: Category: Transportation - Streets Purpose: To identify designated speed limits on Portland streets. Update Frequency: As Needed-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?=DisplayLayer=54340

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

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 EnviroAtlas dataset presents environmental benefits of the urban forest in 1176 block groups in Portland, Oregon. Carbon attributes, temperature reduction, pollution removal and value, and runoff effects are calculated for each block group using i-Tree models (www.itreetools.org), local weather data, pollution data, EPA provided city boundary and land cover data, and U.S. Census derived block group boundary data. This dataset was produced by the USDA Forest Service with support from The Davey Tree Expert Company to support research and online mapping activities related to EnviroAtlas. EnviroAtlas (https://www.epa.gov/enviroatlas) allows the user to interact with a web-based, easy-to-use, mapping application to view and analyze multiple ecosystem services for the contiguous United States. The dataset is available as downloadable data (https://edg.epa.gov/data/Public/ORD/EnviroAtlas) or as an EnviroAtlas map service. Additional descriptive information about each attribute in this dataset can be found in its associated EnviroAtlas Fact Sheet (https://www.epa.gov/enviroatlas/enviroatlas-fact-sheets).

A comprehensive dark gray basemap with labels for the Portland metropolitan region with annotation. Includes the following layers: city boundaries, county boundaries, major arterials & streets, outdoor recreation and conservation areas (ORCA), rivers & streams, taxlots, building footprints, and airports. Also includes county, city, highway, major arterial & street, ORCA and river labels. Some data layers are scale dependent and only visible at larger scales. Date of last data update: 2025-02-11 This is official RLIS data. Contact Person: Jihoon Son jihoon.son@oregonmetro.gov 503-797-1589 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/3750 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

A comprehensive light gray basemap with labels for the Portland metropolitan region with annotation. Includes the following layers: city boundaries, county boundaries, major arterials & streets, trails, outdoor recreation and conservation areas (ORCA), rivers & streams, taxlots, building footprints, and airports. Also includes county, city, highway, major arterial & street, ORCA, trail and river labels. Some data layers are scale dependent and only visible at larger scales. This is a vector tile version of this basemap hosted in ArcGIS Online published from a vector tile package. Custom vector styles that you create based on this vector tile package can break when updates are made to the original tile package, such as when data sources are changed, removed, or renamed. Date of last data update: 2025-09-24 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/3706 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

A simplified comprehensive basemap for the Portland metropolitan region without annotation. Includes the following layers: city boundaries, county boundaries, major arterials & streets, trails, outdoor recreation and conservation areas (ORCA), rivers & streams, and airports. Some data layers are scale dependent and only visible at larger scales. Designed to be layered with the baseAnno and baseActive basemaps. This is a vector tile version of this basemap hosted in ArcGIS Online published from a vector tile package. Custom vector styles that you create based on this vector tile package can break when updates are made to the original tile package, such as when data sources are changed, removed, or renamed. Date of last data update: 2025-09-24 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/3703 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

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.

The amount of floor area in relation to the amount offsite area, expressed in square feet. For example, a floor area ratio of 2 to 1means two square feet of floor area for every one square foot of site area. FAR is different based on zoning, and works with maximum height to control the overall bulk of buildings. See Zoning Code chapter 500 for details. https://www.portlandoregon.gov/bps/34563-- Additional Information: Category: Zoning Code Purpose: To regulate the amount of use on a site. Update Frequency: As Needed-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=54382

A comprehensive gray scale topographic basemap for the Portland metropolitan region without annotation. Includes the following layers: city boundaries, county boundaries, major arterials & streets, trails, outdoor recreation and conservation areas (ORCA), rivers & streams, hillshade, taxlots, building footprints, and airports. Some data layers are scale dependent and only visible at larger scales. Date of last data update: 2025-09-24 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/3705 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

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

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.

Portland City Council Districts. Established by the Independent District Commission, August 21, 2023.-- Additional Information: Category: Boundary Purpose: Portland City Council Districts comprised of census blocks from the 2020 Decennial Census P.L. 94-171 Redistricting Summary File. The configuration of the districts was established by the Independent District Commission via a series of work sessions, trainings, and public hearings that occurred from February 15, 2023 to August 21,2023. The districts were drawn to be consistent with state and federal laws and were approved by the Independent District Commission on August 21, 2023. The Council District Boundaries were developed form the 2020 census blocks from the Census Bureau. Those geometries might not align with other features. Legal descriptions of the districts can be found at: https://www.portland.gov/transition/districtcommission/documents/idc-legal-description-districts/download Supplemental Information: Recommend spatial location queries using 'Have their center in'. Update Frequency: As Needed-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=61106

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