Portland IDC Approved City Council DistrictsWWW.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=123 for the complete metadata.

--Additional Information: Category: Boundary Purpose: No purpose information available. Update Frequency: Unknown

© City of Portland, Oregon

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

© City of Portland, Oregon

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.

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

© City of Portland, Oregon

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.

This dataset contains Assessor data collected from the Portland Maps API, which provides information on building permits issued in the city of Portland, Oregon. The data covers over 144,000 unique permit IDs, with the oldest permit dating back to 1996. The dataset is updated daily.

Project Ideas

Residential Infill Project Rezoning and Permits: Analyze the impact of Portland's Residential Infill Project and Oregon House Bill 2001 on building permits in Portland. Look at the number and type of permits issued before and after the adoption of RIP, and examine the location and size of properties where permits are issued to understand the effects of these changes on the housing market.

Permit Issuance and Valuation Prediction: Model the predicted change in home value resulting from a permit being issued for a specific property. Use historical permit data and property features, such as location, size, and zoning, to train the model.

ADU Impact on Home Value: Investigate the effect of Accessory Dwelling Units (ADUs) on home values in Portland. Look at the number of ADU permits issued over time, and compare the home values of properties with and without ADUs.

Permit Issuance Trends Over Time: Identify trends in permit issuance over time, including changes in the number and type of permits issued each year, as well as differences across neighborhoods or property types.

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 layer is sourced from Fire MDT Data Update confirmation map..

© City of Portland, Oregon

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

Street trees mapped and identified by Portland Parks & Recreation's Urban Forestry division

--Additional Information: Category: Parks Purpose: No purpose information available. Update Frequency: Annually

© City of Portland, Oregon

This layer is sourced from CGIS Open Data.

Benchmarks are survey markers that provide a point of particular elevation used as a reference for determining elevations of other points in a survey. They are used by surveyors, engineers, planners, and contractors for establishing elevations for planning, designing, and/or construction of various projects.The City of Portland is responsible for establishing and maintaining a network of benchmarks throughout the city, each having a known elevation expressed in feet in the City of Portland’s own datum (established in 1896). Most of the City of Portland’s Benchmarks are brass disks about 2 ½" in diameter, and all are marked "City of Portland Bench Mark No. nnnn " and usually set in the curbs of streets. Occasionally you’ll see larger disks of 3 ¾" diameter which are "Class A" monuments, and some benchmarks are set in retaining walls, bridge wing walls, culvert headwalls, concrete steps, or wherever the most stable and accessible placement was determined to be for a specific location. You might also see benchmarks similar to those of the City of Portland’s but with another governmental agency’s or private firm’s name stamped on it. Occasionally the City of Portland Benchmark Book will refer to these monuments and provide elevations, but more often you’ll have to contact the appropriate institution for more information. The benchmark numbers the City assigned to outside agency monuments are for indexing purposes only; PDOT does not stamp a City of Portland benchmark number on other agencies' monuments.-- Additional Information: Category: Survey Purpose: For mapping and analysis related to the maintenance of survey benchmarks. Update Frequency: As needed-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=53238

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.

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

Contour dataset represents the earth's surface with all vegetation and man-made structures removed representing just the physical ground surface. Features represent approximated elevations.-- Additional Information: Category: Land Purpose: For general mapping purposes. Update Frequency: None Planned-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=54338

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

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 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 - Plan 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=61189