This statewide file includes all state owned highways, connections, frontage roads. Major changes/updates included in the 2017 layer: US-18 Dundee Bypass, I-5 Fern Valley, I-5 Woodburn Interchange, OR-140, OR-214 Sunrise Expressway, US-20 Pioneer Mountain to Eddyville.Additional metadata resouce: https://geoportalprod-ordot.msappproxy.net/geoportal/catalog/main/home.page

This data set depicts Oregon state highways that have been identified as tier 1, 2, or 3 seismic lifelines and identifies seismic lifelines for implementation of Policy 1E, Lifeline Routes, in the 1999 Oregon Highway Plan. This is the final work product for the Oregon Seismic Lifelines Identification project, completed by ODOT Transportation Development Division in May 2012. This shapefile was initially derived from the ODOT shapefiles "high_routes.shp."Additional metadata resouce: https://geoportalprod-ordot.msappproxy.net/geoportal/catalog/main/home.page

This data contains the location and legend of mileposts markers (signs) on state owned highways.This GIS base layer can be used for planning purposes and as a reference layer on standard Oregon Department of Transportation (ODOT) city and county map formats. Full details: https://geohub-oregon-geo.hub.arcgis.com/datasets/oregon-geo::mileposts/about

This is a list of all Oregon DMV field office locations

This data contains the location and legend of mileposts markers (signs) on state owned highways.

Additional metadata resouce: https://geoportalprod-ordot.msappproxy.net/geoportal/catalog/main/home.page

The base for the roads layer was developed by the BLM using BLM data, USFS data, USGS DLG and other sources and is what was referred to as the GTRN dataset. The road layer is comprised of the best available data. This means that when road linework is enhanced through the protection map process or through district or program mapping efforts that the enhanced linework will replace or be integrated with the statewide layer. This road layer has specific designations for Protection Map display.

This data represents the State of Oregon city limit boundaries. Each city limit is defined as a continuous area within the statutory boundary of an incorporated city, which is the smallest subdivision of an annexed area. It is represented as spatial data (polygon with label point).

description: This theme delineates Urban Growth Boundaries (UGBs) in the state of Oregon. Oregon land use laws limit development outside of urban growth boundaries. The line work was created by various sources including the Oregon Department of Land Conservation and Development (DLCD), the Oregon Department of Transportation (ODOT), Metro Regional Council of Governments (Metro), county and city GIS departments, and the Oregon Department of Administrative Services - Geospatial Enterprise Office (DAS-GEO).Urban growth boundaries (UGBs) are lines drawn on planning and zoning maps to show where a city expects to experience growth for the next 20 years. UGBs were established under Oregon Statewide Planning Goals in 1973 by the Oregon State Legislature (Senate Bill 100). Source: Dept. of Land Conservation and Development, 1:24,000 (2015).; abstract: This theme delineates Urban Growth Boundaries (UGBs) in the state of Oregon. Oregon land use laws limit development outside of urban growth boundaries. The line work was created by various sources including the Oregon Department of Land Conservation and Development (DLCD), the Oregon Department of Transportation (ODOT), Metro Regional Council of Governments (Metro), county and city GIS departments, and the Oregon Department of Administrative Services - Geospatial Enterprise Office (DAS-GEO).Urban growth boundaries (UGBs) are lines drawn on planning and zoning maps to show where a city expects to experience growth for the next 20 years. UGBs were established under Oregon Statewide Planning Goals in 1973 by the Oregon State Legislature (Senate Bill 100). Source: Dept. of Land Conservation and Development, 1:24,000 (2015).

This data layer is an element of the Oregon GIS Framework. This theme delineates urban growth boundaries (UGBs) in the state of Oregon. The line work was created by various sources including the Oregon Department of Land Conservation and Development (DLCD), the Oregon Department of Transportation (ODOT), Metro Regional Council of Governments (Metro), county and city GIS departments, and the Oregon Department of Administrative Services - Geospatial Enterprise Office (DAS-GEO). UGB areas consist of unincorporated lands surrounding a city that show where the city plans to grow over the next 20 years. When a city needs to develop more residential, commercial, industrial, or public land, it annexes the needed area from its UGB. If a city runs out of needed land within the UGB, it can expand its UGB. Original UGBs were established under the Oregon Statewide Planning Goals in 1973 by the Oregon State Legislature (Senate Bill 100). Goal 14 of the statewide planning program is, "To provide for an orderly and efficient transition from rural to urban land use, to accommodate urban population and urban employment inside urban growth boundaries, to ensure efficient use of land, and to provide for livable communities." The process and requirements for designating and amending UGBs are in Oregon Administrative Rules, Chapter 660, Division 24 (OAR 660-024). Designating or amending a UGB requires a public process, as required by Planning Goal 1, followed by approval by both the city and county elected officials and acknowledgement by the DLCD. This process includes the city submitting a Post Acknowledgement Plan Amendment (PAPA) to DLCD to review for consistency with Goal 14. The PAPA submittal includes GIS files that delineate the changes to the UGB. DLCD aggregates the local GIS layers into the statewide UGB layer. UGB line work and attributes are verified with the city PAPA submittals entered in DLCD’s tabular database to ensure that all UGB updates reported to DLCD have been included in this dataset. UGBs that are currently in the appeal process at the time of publication of this layer are not included. The effDate attribute indicates the year in which the UGB amendment was acknowledged by DLCD. In 2022, DLCD acknowledged amendments to the following UGBs: Central Point, Dayton, Phoenix, and Turner. Corrections were also made to the Astoria and Condon UGBs to reflect the current acknowledged boundary.

Federal highway and transit statutes require, as a condition for spending federal highway or transit funds in urbanized areas, the designation of MPOs, which have responsibility for planning, programming and coordination of federal highway and transit investments. The federally designated MPOs are made up of large urban MPOs (population areas greater than 200,000): the Portland Metro regional area, the Salem/Keizer area, and the Eugene/Springfield area; and small urban MPOs (population areas between 50,000 - 200,000): the Medford/Rogue Valley area, the Cities of Corvallis/Philomath, the City of Bend, Albany area, Middle Rogue, Longview/Kelso/Rainier and Walla Walla Valley. Additional metadata resouce: https://geoportalprod-ordot.msappproxy.net/geoportal/catalog/main/home.page

This data identifies point locations of known culverts. The data was taken from the Drainage Facilities Management System (DFMS) and TransInfo (TI). Additional metadata resouce: https://geoportalprod-ordot.msappproxy.net/geoportal/catalog/main/home.page

Crash Map is an interactive mapping tool developed by Metro to help people access and explore historic motor-vehicle related crash data in Clackamas, Multnomah and Washington Counties. The most recent five-years of crash data available is included in the tool.Crash information is collected statewide by the Oregon Department of Motor Vehicles. It is then aggregated and geocoded (mapped) by the Oregon Department of Transportation’s Crash Analysis and Reporting Unit. The 2018 Motor Vehicle Traffic Analysis and Code Manual provides information on how crash information is coded, including unlocatable crashes. Aggregated, geo-coded crash data is typically available to Metro and other agencies two years after the crash occurred. Metro processes the crash data for the greater Portland area and supports this map for public access.

Regionally-designated priority routes to assist in response and recovery in the event of an emergency. Metro and RDPO in collaboration with numerous local, regional and state agencies identified regional emergency transportation routes (RETRs) for the five-county Portland-Vancouver metropolitan region, which include Clackamas, Columbia, Multnomah and Washington counties in Oregon and Clark County in Washington. These routes will assist in the response and recovery through connecting critical infrastructure and facilities and providing access to vulnerable and isolated populations. This layer represents the routes after Phase 1 of the Regional Emergency Transportation Route (RETR) Update. The routes are subject to further review, refinement, and prioritization as part of the Phase 2 work. Date of last data update: 2022-05-19 This is official RLIS data. Contact Person: Matthew Hampton matthew.hampton@oregonmetro.gov 503-797-1748 RLIS Metadata Viewer: https://gis.oregonmetro.gov/rlis-metadata/#/details/3699 RLIS Terms of Use: https://rlisdiscovery.oregonmetro.gov/pages/terms-of-use

This file includes all signed Interstate, US, and State routes for the State of Oregon.Additional metadata resouce: https://geoportalprod-ordot.msappproxy.net/geoportal/catalog/main/home.page

With 204 GPS-collared mule deer, the Beulah-Malheur herd is one of the most extensively recorded mule deer herds in Oregon. Mule deer primarily winter along the Malheur River and the Stinkingwater Mountains, with some as far south as the Owyhee River. Winter ranges are covered by Artemisia tridentata (big sagebrush), grassland, and encroaching Juniperus occidentalis (western juniper). Although spatially dispersed, much of the Beulah-Malheur herd collectively migrates northwest to reach summer ranges across the upper elevations of the Malheur National Forest, Pedro Mountain, and Cottonwood Mountain. Primary summer range vegetation includes A. t. vaseyana (mountain big sagebrush), Pinus ponderosa (ponderosa pine), and western juniper with mixed-conifer forests and mountain shrub communities at higher elevations. In 2014, the Buzzard Complex fire burned approximately 398,596 acres (161,306 ha) between Riverside, Oregon and State Route 78, allowing Taeniatherum caput-medusae (medusahead) and other invasive annual grasses to proliferate in areas originally lacking perennial plant cover. Mule deer cross several major roadways during migration, including U.S. Highway 20, U.S. Route 26, and U.S. Route 395, while Interstate 84 is a complete barrier on the east. U.S. Highway 20 transects winter ranges for both migratory and resident mule deer and the section between mileposts 135 and 258 along the Malheur River accounted for an average of 179 mule deer-vehicle collisions each year from 2010 to 2022. The Burns-Paiute Tribe is working with the Oregon Department of Fish and Wildlife (ODFW) and Oregon Department of Transportation (ODOT) to identify wildlife passage solutions on U.S. Highway 20. These mapping layers show the location of the winter ranges for mule deer (Odocoileus hemionus) in the Beulah-Malheur population in Oregon. They were developed from 303 migration sequences collected from a sample size of 179 animals comprising GPS locations collected every 5-13 hours.

Mobility Hubs are places that provide connections between different types of transportation options, often including transit, micromobility, and on-demand services. Mobility hubs may be co-located with transit centers, secondary transit hubs, or places where routes intersect to facilitate easy transfers. Additional mobility options presented at these hubs expand access to transit, and hubs typically include physical and digital information that makes access to these services seamless and easy to navigate. This point feature class includes all Mobility Hubs as defined by the Bend TSP.Data is updated as changes are approved by Bend City Council.

Bend’s Transportation System Plan (TSP) describes the City’s transportation policies and investment priorities to address its needs and fulfill its visions for an economically vital, healthy, and equitable community. To support how people and goods move within and through the City and complement Bend’s land use and growth management strategies, the TSP establishes a system of transportation facilities, programs, and policies that will guide transportation infrastructure development over the next 20 years. The TSP is the transportation element of Bend’s Comprehensive Plan.The City of Bend TSP incorporates the BPRD Trails Map into its planning. BPRD and the City of Bend recognize that path and trail alignments are conceptual and subject to refinement. This line feature class includes all existing paths and trails as defined by the Bend TSP.

Field Name DescriptionObjectIDFor internal use.FacilityIDThe tracking number for each street segment.InstallDateInstallation date for the street segment.LifeCycleStatusFor internal use.LocationDescriptionLocation of street segment, from cross street to cross street.CommentsComment field for location.EAM_PARENTFor internal use.EAM_PARENTORGFor internal use.GISOBJIDInfor object ID field.EAM_UOMFor internal use.EAM_UOMREFFor internal use.EAM_PRECISIONFor internal use.StreetClassType of street, such as Residential, Minor arterial, Collector, etc.SubZoneFor internal use.LaneMilesLength of segment, in miles.GlobalIDFor internal use.PCIQuality of road condition, as a percent.WidthWidth of street segment, in feet.ShapeFor internal use.created_userFor internal use.created_dateFor internal use.last_edited_userFor internal use.last_edited_dateFor internal use.StreetSaverFor internal use.UPDATE_COUNTFor internal use.StreetSaverIDID value for StreetSaver.LanesNumber of lanes within street segment.Shape.STLength()For internal use.

This data layer is an element of the Oregon GIS Framework. This theme delineates Urban Growth Boundaries (UGBs) in the state of Oregon. Oregon land use laws limit development outside of urban growth boundaries. The line work was created by various sources including the Oregon Department of Land Conservation and Development (DLCD), the Oregon Department of Transportation (ODOT), Metro Regional Council of Governments (Metro), county and city GIS departments, and the Oregon Department of Administrative Services - Geospatial Enterprise Office (DAS-GEO). Urban growth boundaries (UGBs) are lines drawn on planning and zoning maps to show where a city expects to experience growth for the next 20 years. UGBs were established under Oregon Statewide Planning Goals in 1973 by the Oregon State Legislature (Senate Bill 100). Goal 14 specifically deals with UGBs (OAR 660-15-0000(4)). Other specific ORS that relate to the designation and delineation of UGBs are: 197.626 Expanding urban growth boundary and designating urban reserve area subject to periodic review. A city with a population of 2,500 or more within its urban growth boundary that amends the urban growth boundary to include more than 50 acres or that designates urban reserve areas under ORS 195.145 shall submit the amendment or designation to the Land Conservation and Development Commission in the manner provided for periodic review under ORS 197.628 to 197.650. [1999 c.622 §14; 2001 c.672 §10] and 197.628 Periodic review; policy; conditions that indicate need for periodic review.(1) It is the policy of the State of Oregon to require the periodic review of comprehensive plans and land use regulations in order to respond to changes in local, regional and state conditions to ensure that the plans and regulations remain in compliance with the statewide planning goals adopted pursuant to ORS 197.230, and to ensure that the plans and regulations make adequate provision for needed housing, employment, transportation and public facilities and services. Determining UGBs in Oregon is done based on input from city and county governments. Such special districts as public safety and utilities also participate because they provide important services. Local citizens and other interested people also provide input at public hearings, and by voting. After local governments determine the UGB, they submit a Post Acknowledgement Plan Amendment and the state Department of Land Conservation and Development (DLCD) reviews it for consistency with Goal 14. As part of this process jurisdictions send GIS files to DLCD highlighting the amended area. UGBs that are currently in the appeal process at the time of publication are not included. The effDate attribute is populated to indicate the data version and year in which the UGB was updated. UGB amendments are verified with DLCD’s Post Acknowledgement Plan Amendment (PAPA) database to ensure that all UGB updates reported to DLCD have been included in this data. In 2019 DLCD acknowledged amendments to the following UGBs: Madras, Mill City, Redmond, Springfield and Stanfield.

This feature class identifies the location, type, style and material of delineators in Portland Bureau of Transportation’s (PBOT) GIS.-- Additional Information: Category: Transportation - Assets Purpose: This dataset represent PBOT’s GIS inventory of delineators. Update Frequency: Weekly-- Metadata Link:https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=52790