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.

This layer is a component of Streetmap.

© Metro DRC, Multnomah County

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

The City of Portland, Bureau of Planning, Natural Resource Inventory Update project GIS model relative riparian resource value. For more information about the City of Portland Natural Resource Inventory Update project, visit the project homepage at:http://www.portlandonline.com/planning/index.cfm?c=40437 For more information on the Natural Resource Inventory GIS model, refer to:http://www.portlandonline.com/shared/cfm/image.cfm?id=165937

--Additional Information: Category: Planning Purpose: This information is intended to update Portland's existing natural resource inventories and inform existing environmental program implementation, current and future planning efforts, and future resource management decisions. Update Frequency: As needed

© City of Portland, Oregon

This layer is sourced fromCGIS Open Data.

The Board of County Commissioners meet in the Multnomah Building, 501 SE Hawthorne Blvd., Portland, Oregon, Commissioners Board Room 100 - off the lobby.Other than meeting start time, listed agenda item times are approximate. Agenda items may start earlier or later unless listed as a Time Certain.View upcoming and past Board meetings.

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.

Points representing the locations of verified active addresses in the Portland Metro Region. Addresses been culled from the City of Portland Master Address Repository, Multnomah County Assessor Records and the RLIS Master Address Points dataset.--Additional Information: Category: Address Purpose: For mapping, geocoding, mailing, and analysis of addresses in the Portland Metro Region. Update Frequency: Twice Weekly-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=54157

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.

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

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

Urban reserves are lands currently outside the urban growth boundary that are suitable for accommodating urban development over the next 50 years. Rural reserves are lands outside the current urban growth boundary that are high value working farms and forests or have important natural features like rivers, wetlands, buttes and floodplains. These areas will be protected from urbanization for the next 50 years.

On 08/19/2011 the Oregon Land Conservation and Development Commission (LCDC) acknowledged (approved) the revised urban and rural reserves map for Washington County. Reserves for Multnomah and Clackamas counties were approved previously. Date of last data update: 2025-05-05 This is official RLIS data. Contact Person: Al Mowbray al.mowbray@oregonmetro.gov 503-797-1843 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/2427 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

Generalized zoning designations for the City of Portland and unincorporated portions of Multnomah County that are administered by the city.

Street centerline network for the City of Portland, Multnomah County, Clark County and Washington County. This dataset does not yet include the data fields and structure necessary for performing routing operations.--Additional Information: Category: Transportation - Streets Purpose: Provides a base for addressing, street maintenance planning and tracking for street segments in the City of Portland. Displays the transportation infrastructure for the region including the City of Portland. Update Frequency: Weekly-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=52057

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

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

Street centerline network for the City of Portland, Multnomah County, Clackamas County and Washington County developed for geocoding purposes. This dataset has a character (textual) street number field to better allow for locating addresses that have leading zeros (e.g., 0680 SW Bancroft St.). This dataset does not yet include the data fields and structure necessary for performing routing operations.-- Additional Information: Category: Transportation - Streets Purpose: Provides a dataset including all address segments to be used for geocoding (locating) addresses in the Portland Region. Includes the capability to search those addresses whose street number begins with a zero. Update Frequency: Weekly-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=52062

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-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=52135

The FEMA Flood Hazard Layer represents the location and attributes of flood insurance risk zones from the Flood Insurance Rate Map (FIRM) databases published by the Federal Emergency Management Agency (FEMA), and any Letters of Map Revision (LOMRs) that have been issued against those databases since their publication date. It is updated on a monthly basis.

The FIRM Database is the digital, geospatial version of the flood hazard information shown on the published paper FIRMs. The FIRM 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 floodway, 100-year floodplain/SFHA (Special Flood Hazard Area), and the 500-year floodplain are all derived from this dataset.--Additional Information: Category: Hazard Purpose: The FIRM is the basis for floodplain management, mitigation, and insurance activities for the National Flood Insurance Program (NFIP). Insurance applications include enforcement of the mandatory purchase requirement of the Flood Disaster Protection Act, which "... requires the purchase of flood insurance by property owners who are being assisted by Federal programs or by Federally supervised, regulated or insured agencies or institutions in the acquisition or improvement of land facilities located or to be located in identified areas having special flood hazards, " Section 2 (b) (4) of the Flood Disaster Protection Act of 1973. In addition to the identification of Special Flood Hazard Areas (SFHAs), the risk zones shown on the FIRMs are the basis for the establishment of premium rates for flood coverage offered through the NFIP. The FIRM Database presents the flood risk information depicted on the FIRM in a digital format suitable for use in electronic mapping applications. The FIRM Database serves to archive the information collected during the Flood Risk Project. Update Frequency: As needed-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=54347