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 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 layer is a component of Countywide General-purpose Map.

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

Vegetation patches larger than 1/2 acre. Based on information from reference data sources including 6" resolution aerial photos, Parks and Recreation natural area assessments, and vegetation surveys along the banks of the Willamette and Columbia rivers. Vegetation patches area classified as forest, woodland, shrubland, or herbaceous. The mapping area includes all land within the City of Portland and the unincorporated parts of Multnomah County that are administered by the City of Portland.

--Additional Information: Category: Environmental Purpose: For analyzing vegetation within Portland's riparian and upland areas. Developed as an input to the Bureau of Planning's GIS model for identifying significant natural resources.

The key goals of the vegetation mapping project were 1) refine the location of vegetation "patches" of areas previously mapped by Metro; 2) incorporate vegetation maps generated by other agencies such as Portland Parks and Recreation and the Portland Bureau of Environmental Services and refine and improve that information where necessary; 3) map vegetation patches meeting Portland’s criteria for inclusion in the natural resource inventory a 1/2 acre minimum patch size versus the 1 to 2 acre patch size used by Metro for the regional dataset; 4) map all vegetation within a 1/4 mile of a surface stream, wetland, or regionally significant habitat resources included in Metro’s inventory; 5) classify the vegetation into four NVCS classes: forest, woodland, shrubland, and herbaceous; 6) further classify vegetation as either "natural/semi-natural" or "cultivated"; and 7) update, refine and improve the vegetation data annually as new aerial photos become available. Update Frequency: As needed

© City of Portland, Oregon

This layer is sourced from CGIS Open Data.

Scoggins Dam in northwest Oregon lies within the Gales Creek fault zone (GCF), a northwest-striking system of active faults forming the boundary between the Coast Range and the Tualatin Valley about 25 km east of Portland, Oregon. Geologic mapping published in 2020 shows the dam to lie within a block-faulted releasing stepover between the right-lateral, NW-striking Scoggins Creek and Parsons Creek strands of the GCF. The Scoggins Creek strand is presently mapped beneath the existing dam about 200 m north of the south abutment. Preliminary results from paleoseismic trenching by the U.S. Bureau of Reclamation, Portland State University, and the U.S. Geological Survey indicate that these two major fault strands have had multiple surface rupturing earthquakes in the Holocene. To confirm the accuracy of the 2020 geologic map and the geometry of the GCF in the releasing stepover region, we completed additional geologic mapping of the dam, reservoir, and an alternative dam site downstream between July 2018 and May 2020. Using high-resolution lidar topographic data and satellite imagery on handheld digital tablets, we collected data at ~500 field sites in the heavily forested terrain. We used these detailed field observations to locate and digitally map the main Scoggins Creek and Parsons Creek fault strands, as well as the cross faults linking the two main strands, to produce an improved and more detailed geologic map and cross sections of Scoggins Valley and its existing and proposed dam sites.

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=52098

This is a 10 meter Hillshade file created by Metro from USGS DEM data provided by the BLM. It covers the 3-county area (Washington, Multnomah, and Clackamas Counties). Date of last data update: 2004 This is official RLIS data. Contact Person: Joe Gordon joe.gordon@oregonmetro.gov 503-797-1587 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/2162 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

Emergency Transportation Routes in the City of Portland, for use in disaster response and recovery. From the five county MOU July 2005, ODOT No. 21,273. Based on the emergency_trans_routes_Metro layer, with minor update in Oct 2016.-- Additional Information: Category: Public Safety - Emergency Management Purpose: For city wide disaster planning and to map transportation routes which have been identified as important in an emergency. Update Frequency: As Needed-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=54396

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.

MCDD district boundaries

© Multnomah County Drainage District 1880 NE Elrod Dr., Portland, OR 97211

This layer is sourced from City of Portland Sewer & Stormwater Utilities.

© City of Portland, Oregon

County Warning Area and county boundaries for NWS Portland, Oregon Weather Forecast Office

Lidar-derived elevation data for the 2019 Oregon Lidar Consortium (OLC) West Metro 3DEP project area. The project area (PA) encompasses 486,551 acres. Data are within Multnomah County, Oregon. The nominal pulse density is eight pulses per square meter. Points that were determined to be geometrically invalid, or invalid surface returns, were removed from the data set. The hydro-flattened bare e...

County tax assessors tax lots with associated property data. Selected items from each county assessor's file are included and standardized for all three counties. The tax lot spatial features and data associated with the tax lot are compiled by Metro from existing records created and maintained by the local county assessment and taxation offices.

© City of Portland, Oregon

Depth to Fragipan represents a "restrictive layer" is a nearly continuous layer that has one or more physical, chemical, or thermal properties that significantly impede the movement of water and air through the soil of that restrict roots or otherwise provide an unfavorable root environment. Examples are bedrock, cemented layers, dense layers, and frozen layers. This theme presents the depth to any type of restrictive layer for each map unit. If more than one type of restrictive layer is described for an individual soil type, the depth to the shallowest one is presented. These data only describe map units for which a restrictive layer is present within 200cm (approximately 6.56 feet). A "representative" value indicates the expected value of this attribute for the component. For this soil property, only the representative value is used.

This layer is sourced from Stormwater System Plan.

© City of Portland, Oregon

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

U.S. Census Bureau QuickFacts statistics for South Portland city, Maine. QuickFacts data are derived from: Population Estimates, American Community Survey, Census of Population and Housing, Current Population Survey, Small Area Health Insurance Estimates, Small Area Income and Poverty Estimates, State and County Housing Unit Estimates, County Business Patterns, Nonemployer Statistics, Economic Census, Survey of Business Owners, Building Permits.