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 dataset was created by Casey Cushing
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
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
© 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 layer is an overlay measuring the level of "completeness" of areas within the City of Portland. Completeness is defined by a neighborhood's proximity to various amenities, such as grocery stores, parks and recreation facilities, commercial services, elementary schools, pedestrian and bicycle infrastructure, and transit. The overlay was generated by calculating the areas where at least five of the seven total "completeness" indicator overlays are present.-- Additional Information: Category: Planning Purpose: Update Frequency: Unknown-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=54195
MCDD district boundaries
© Multnomah County Drainage District 1880 NE Elrod Dr., Portland, OR 97211
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
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
This community-driven map shows live data regarding incidents in Portland due to the recent protests. Incidents that could be dangerous to people in the area are reported. If you are in an affected area and see something potentially dangerous, you can right click (or long-tap on mobile) on the map to create a marker.
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.
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.
Civic and Neighborhood Corridors in Zoning Code chapter 120 - Multi-Dwelling Zones and 130 - Commercial Mixed Use Zones.Corridors derived from PBOT TSP Street Design Classifications of Civic Main Street, Neighborhood Main Street, Civic Corridor and Neighborhood Corridor.Central City is not included as it has specific standards.-- Additional Information: Category: Zoning Code Purpose: Map location of civic and neighborhood corridors zoning code map 120-1 and 130-3 Update Frequency: As Needed-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=54763
This data is not recommended for downloading. Use the "Affordable Housing - Download" item to download the feature class and related table in a zipped file geodatabase. An ongoing inventory of affordable housing for the Portland metropolitan area. Intended to assist in prioritizing investment and guiding regional policymaking. Date of last data update: 2020-12-31 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/3432 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use
This EnviroAtlas dataset shows the boundary of the Portland, OR Atlas Area. It represents the outside edge of all the block groups included in the EnviroAtlas Area. This dataset was produced by the US EPA to support research and online mapping activities related to EnviroAtlas. EnviroAtlas (http:/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://res1edgd-o-tepad-o-tgov.vcapture.xyz/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://res1wwwd-o-tepad-o-tgov.vcapture.xyz/enviroatlas/enviroatlas-fact-sheets).
This web scene in 3D shows the number of trees in the city of Portland, Oregon. The map's purposes is to aid in the city's urban tree management. It depicts where the trees are located and the real-world heights in an urban setting.
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.
description: This EnviroAtlas dataset estimates green space along walkable roads. Green space within 25 meters of the road centerline is included and the percentage is based on the total area between street intersections. Green space provides valuable benefits to neighborhood residents and walkers by providing shade, improved aesthetics, and outdoor gathering spaces. This dataset was produced by the US EPA 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 ).; abstract: This EnviroAtlas dataset estimates green space along walkable roads. Green space within 25 meters of the road centerline is included and the percentage is based on the total area between street intersections. Green space provides valuable benefits to neighborhood residents and walkers by providing shade, improved aesthetics, and outdoor gathering spaces. This dataset was produced by the US EPA 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 ).
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