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/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

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

The Digital Flood Insurance Rate Map (DFIRM) 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 DFIRM Database is derived from Flood Insurance Studies (FISs), previously published Flood Insurance Rate Maps (FIRMs), flood hazard analyses performed in support of the FISs and FIRMs, and new mapping data, where available. The FISs and FIRMs are published by the Federal Emergency Management Agency (FEMA). The file is georeferenced to earth's surface using the UTM projection and coordinate system. The specifications for the horizontal control of DFIRM data files are consistent with those required for mapping at a scale of 1:12000.

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

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

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 layer is sourced from City of Portland Sewer & Stormwater Utilities.

© City of Portland, Oregon

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.

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

Heat islands are urban or developed areas that experience higher than average temperatures due to heat retained or even amplified by the built-out urban environment.The data displays the difference in surface temperature from the regional average.2017 Urban Heat Index as derived from LandSat Data.

-- Additional Information: Category: Transportation - Plan Purpose: Supplemental Information: Update Frequency: As Needed-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=54430

description: The Umpqua River drains 12,103 square kilometers (4,673 square miles) in southwest Oregon before flowing into the Pacific Ocean at Winchester Bay near the city of Reedsport. In cooperation with the Portland District of the U.S. Army Corps of Engineers (USACE), the USGS evaluated sediment transport and gravel storage along the downstream alluvial reaches of the North and South Umpqua Rivers and the entire mainstem Umpqua River. This includes the lower 46.8 kilometers (29.1 miles) of the North Umpqua River and the lower 122.6 kilometers (76.2 miles) of the South Umpqua River. The Umpqua River gravel transport study involved multiple analyses, including tracking patterns of historical channel change and estimation of a sediment budget. To support these analyses, digital channel maps were produced to depict channel and floodplain conditions along the Umpqua River system from different time periods. GIS layers defining the active channel of the Umpqua River system were developed for three time periods: 1939, 1967, and 2005. For the South Umpqua River and the 19 kilometers (12 miles) of the mainstem Umpqua River downstream from the confluence of the North and South Umpqua Rivers, GIS layers were also developed for the time periods 1994, 2000, and 2009. For this project, the active channel was defined as area typically inundated during annual high flows, and includes the low-flow channel as well as side channels, islands, and channel-flanking gravel bars. The active channel datasets were developed by digitizing from aerial photographs. Aerial photographs from 1939 and 1967 were scanned, rectified, and mosaiced for this project. Digital orthophotographs from 1994, 2000, 2005, and 2009 are publicly available (See metadata for each photograph set for more information on the rectification process and resolution of each dataset). Although our study area encompasses the Umpqua River and lower reaches of the North and South Umpqua Rivers, the extent of each dataset depended upon the underlying aerial photographs; for example, the 1967 photographs extend only as far downstream as floodplain kilometer 7, whereas the 1939 and 2005 datasets extend to the mouth of the Umpqua River at the Pacific Ocean.; abstract: The Umpqua River drains 12,103 square kilometers (4,673 square miles) in southwest Oregon before flowing into the Pacific Ocean at Winchester Bay near the city of Reedsport. In cooperation with the Portland District of the U.S. Army Corps of Engineers (USACE), the USGS evaluated sediment transport and gravel storage along the downstream alluvial reaches of the North and South Umpqua Rivers and the entire mainstem Umpqua River. This includes the lower 46.8 kilometers (29.1 miles) of the North Umpqua River and the lower 122.6 kilometers (76.2 miles) of the South Umpqua River. The Umpqua River gravel transport study involved multiple analyses, including tracking patterns of historical channel change and estimation of a sediment budget. To support these analyses, digital channel maps were produced to depict channel and floodplain conditions along the Umpqua River system from different time periods. GIS layers defining the active channel of the Umpqua River system were developed for three time periods: 1939, 1967, and 2005. For the South Umpqua River and the 19 kilometers (12 miles) of the mainstem Umpqua River downstream from the confluence of the North and South Umpqua Rivers, GIS layers were also developed for the time periods 1994, 2000, and 2009. For this project, the active channel was defined as area typically inundated during annual high flows, and includes the low-flow channel as well as side channels, islands, and channel-flanking gravel bars. The active channel datasets were developed by digitizing from aerial photographs. Aerial photographs from 1939 and 1967 were scanned, rectified, and mosaiced for this project. Digital orthophotographs from 1994, 2000, 2005, and 2009 are publicly available (See metadata for each photograph set for more information on the rectification process and resolution of each dataset). Although our study area encompasses the Umpqua River and lower reaches of the North and South Umpqua Rivers, the extent of each dataset depended upon the underlying aerial photographs; for example, the 1967 photographs extend only as far downstream as floodplain kilometer 7, whereas the 1939 and 2005 datasets extend to the mouth of the Umpqua River at the Pacific Ocean.

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

Each Rescue Plan project has one type of City of Portland allocation category. This table maps the investment area ID (from the City of Portland Rescue Plan Allocation Categories dataset) to subproject ID (from the Subprojects dataset).-- Additional Information: Category: ARPA Update Frequency: As Necessary-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=60964

Some sites within the City of Portland are located within plan districts. Plan districts may have additional regulations that can impact a project.-- Additional Information: Category: Planning Purpose: For mapping areas of additional regulations for development in Portland. Update Frequency: As Needed-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=53611

Points representing the location of street lights in the City of Portland. Attribute information includes Asset ID, owner, maintainer, location ID, power supplier, and other relevant details.-- Additional Information: Category: Transportation - Assets Purpose: For mapping and analysis of street lights in Portland. Update Frequency: Weekly-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=52801

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

The High Crash Network includes Portland’s most dangerous streets and intersections for people driving, walking, and bicycling. This dataset delineates the streets which are among the top 20 crash streets for motor vehicles, for pedestrians and for bicyclists. Many streets are high crash streets for multiple transportation modes. Together, they form a network of 30 high crash streets.-- Additional Information: Category: Transportation - Streets Purpose: To delineate streets with a high occurrence of traffic crashes. Update frequency: As needed-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=54465

Point features representing the locations of regional police stations, including City and County facilities. The attribution contains building names, coding, address, latitude, longitude,and contact info for each facility. The dataset was created by City of Portland Corporate GIS using facility contacts and internet research. It is checked periodically for accuracy by CGIS staff.--Additional Information: Category: Public Safety - Police Purpose: This dataset was primarily designed to support the information needs of Portland Maps, but should also be considered an accurate overall representation of the point locations of police facilities in the Portland Metro area. This dataset can be used for mapping of important law enforcement facilities. Update Frequency: As Needed-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=54102