* [http://www.oregon.gov/ODOT/TD/asset_mgmt/docs/OTMS/Routes2HwyCrossRef.pdf Oregon Route to Highway Cross Reference]
* [http://keiko36.odot.state.or.us/whalecomfb751917efb5683a9c287df8a9ad831f7e55a2048a/whalecom0/cf/dvl ODOT Digital Video Log (DVL)]
* [http://highway.odot.state.or.us/cf/highwayreports/aml_summary_parms_by_route_no.cfm Oregon highway summary by Route] shows you all the Oregon highways which comprise state and US routes.
* [http://gis.odot.state.or.us/transgis/ ODOT TransGIS] can be used to view all manner of roadway attributes, including Functional Classification. To view functional classifications, go to Display->Layer Catalog->Highway Classifications. Select both/either State and Non-State.
* [http://www.zipmap.net/Oregon Oregon Zipcode Map] from ZipMap.net
* [http://en.wikipedia.org/wiki/State_highways_in_Oregon State Highways in Oregon] on wikipedia
* [http://public.govdelivery.com/accounts/ORDOT/subscriber/new?preferences=true ODOT Updates via email]
* [http://www.oregon.gov/ODOT/HWY/TRAFFIC-ROADWAY/docs/pdf/Descriptions_of_US_and_Oregon_Routes.pdf US and Oregon Routes Descriptions] (talks about where routes go, as compared to Oregon highways
== Counties ==
* [http://en.wikipedia.org/wiki/List_of_counties_in_Oregon List of counties in Oregon]
This page serves as the primary resource for editors of Oregon. Review all the sections to better understand how the guidelines for this state might deviate from the overall USA or worldwide guidelines. If you have any comments or questions about this page or state refer to the community links below.
Please remember to only assign road shields to signed route number(s). Road shields currently hide the street name so if we have the street name set as primary because it has the most important/visible signage, it should be left without a shield for now.
Introduction
Oregon is a part of the Northwest region, which includes the states and/or territories of:
Before editing the maps in Oregon, be sure to fully review and understand the editing manual.
The Waze user community follows the Waze etiquette guidelines discussed in the Wiki. Be sure to familiarize yourself with these guiding principals while editing the maps and this Wiki, as well as when communicating with other Waze users.
Functional Classification
Oregon follows the Functional Classification (FC) system for both state and non-state roads.
While TransGIS Is a useful tool for determining functional classification, it does not perfectly match how roads should be classified in WME. TransGIS often includes functional classifications for planned or proposed roads or other projects. TransGIS will also often not show a complete connections of classified roads, especially when they are divided highways. If you believe a significant deviation from the suggested functional classification is needed, please contact a State Manager.
Below are examples & explanations of some current deviations from TransGIS;
This segment of Everett St in Portland is classified in TransGIS as a Local Street. However, it provides an important connection between MLK and the I-84 E on-ramp. Without this change, Waze would likely ignore this route as an alternative to I-5 S.
Oak & Pine Streets in Grants Pass are currently mapped in TransGIS as Minor Arterial & Local Street, respectively. This is likely due to a proposed route that would connect Oak to the north side of town via Dimmick St. Viewing the roads from street view, Pine has right of way between G St and Bridge St, which often indicates that a road has a higher classification than the intersecting streets and Waze will benefit from preferring this route though the neighborhood. Conversely, Oak has stop signs at each intersection so it is likely being treated like a normal street.
ODOT TransGIS can be used to view all manner of roadway attributes, including Functional Classification. To view functional classifications, go to Display->Layer Catalog->Highway Classifications. Select both/either State and Non-State.
PLEASE NOTE: Many counties use base maps which are copyrighted. Only information provided by the county (addresses, road names, etc.) may be used to map in Waze.
The Waze forum is a great place to find answers to previously asked questions and also a place to ask new ones. Below are links to the forums specific to Oregon.
New editors should consider checking into the formal mentoring program available at no charge.
Discord (Chat)
Oregon uses Discord to chat with local editors and area/state/regional management. If you're a new/existing editor in Oregon or even if you're just visiting and want to relay information to local editors you can do so by clicking the link below to jump onto the server.
Discord has a free app available on Android and iOS devices as well as stand-alone clients for Windows/Mac/Linux and a web-based client.
Cities and towns
One of the most common errors when editing the maps is when an editor creates a road and does not confirm the road by setting the city and road name (or stating it has none).
The purpose of the Oregon Major Roads page is to inform map editors on what is being worked on or is completed in the State of Oregon, as well as what is planned according to ODOT or other cities as we find out about them.
Locking standard
In Oregon we have a set minimum standard for locking roads based on segment type. Any road of a certain segment type must be locked at least to the rank (level) in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, imaging inaccuracies, and the like), but should not be locked lower.
A great time to implement these locks is while bringing the road types of an area into compliance with the current US road type standards (FC and highway systems). Lock the roads based on type after they've been set to current US road type standards.
Oregon Minimum Locking Rank Standard
Segment Type
Statewide
Freeway
5
Ramp
5
Major Highway
3
Minor Highway
3
Primary Street
2
Street
1
• • • • Ferry • • • •
5
|-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-|
2
Note: Certain roads may be locked higher than the above minimums. Please do not lower locks unless approved by the RC or SM of Oregon.
Road Elevations
These are the general guidelines for elevation in Oregon:
Drivable and non-drivable segments are handled the same way with elevation.
Set elevation to ground in most cases.
Segment(s) passing over other segment(s), rivers, major waterways, and all bridges shall have higher elevation, relative to ground.
Only elevate/lower the actual bridge/tunnel section of the road.
Elevation of overlapping segments should be set relative to each other, with the lowest segment as Ground (unless a tunnel).
Tunneled segments shall have lower elevation, relative to ground.
Only segments that "cannot see the sky" should have negative elevation (i.e. tunnels).
Only set elevation as low/high as necessary.
If you use the Bridge tool to join segments, be aware that it raises the elevation of the joined segment. Lower the joined segment as appropriate.
Review the Wiki guidelines for non-drivable roads to ensure compliance with the general guidelines.
Forest Service Road Numbers
Explanation of Forest Service road types & signsLow-standard route signs
While Oregon follows the national guidance for Forest Service roads, the guidance for road numbers does not cover the Forest Service's numbering convention used in Oregon. Forest Service roads in Oregon are all assigned a 7-digit number that can be found in the Motor Vehicle Use Map (MVUM). To avoid unnecessarily long names for general use, Forest Service road signs and many map products use an abbreviated version of the MVUM number which also aligns with Waze's needs. As stated in the national guidance, roads with signed or popular names should have those set as the primary name with the Forest Service road number as an alternate. Road numbers should be assigned as follows:
Primary Routes: Use the first two digits of the MVUM number.
NOTE: A road with the MVUM # 1800000 may be a primary route (FS-18) or a secondary route (FS-1800). This distinction can not generally be determined from the MVUM alone.
Mapping Resources
Currently, the most useful reference map known for Waze editing in National Forests is the Forest Service Topographical (FSTopo) Map Service. This map is believed to provide the most up-to-date road types and road condition assessments among the many products provided by the Forest Service, including the MVUM.
Closures
When managing a section of roadway under construction or being closed for a major event, follow the Wiki guidelines on construction zones and Real time closures.
This section contains details about road closures currently in place in Waze, usually through disconnecting of segments to prevent Waze from routing along a certain stretch of road. If you perform a closure in Waze, please document it here so other area managers can ensure the roads are reconnected at the appropriate time.
Road Name
Editor
Closed Date
Est Open Date
Links and comments
Old McKenzie Pass OR-242
FzNk
11-5-2020
Summer 2021
Closed for the winter season.
KEEP THE FOLLOWING FOR FUTURE REFERENCE:
Area Places for the closure gates should be large in the winter for better app visibility. Shrink the area in the summer.
Oregon follows the USA standard for Places. Do not deviate from the guidelines without first obtaining consensus to do so via the state forum linked on this page.
Oregon Place Locking Standards
To prevent loss of data due to automatic acceptance of submissions from "trusted users", all area places and points with complete data should be locked to Level 3 at a minimum.
Additionally, please consult the following table for minimum lock level for completed places.
Place Type
Minimum Lock Level
Hospital/Urgent Care
4
Airport
4
Cameras
Not every camera-looking device at an intersection is a speed or red light camera. Generally speaking:
a speed camera takes a photograph of a vehicle when it passes by the camera at too high a speed.
a red light camera takes a photograph of a vehicle that enters an intersection after the light is red. In some areas, it takes the photograph when a vehicle is not clear of the intersection some period after the light turns red.
When adding a camera, be sure to review the camera placement recommendations.
Laws regarding speed and red light cameras vary between the states and territories, so be sure to understand the details of camera legality in Oregon.
Based on information researched at the time this page was created, the limited legality of speed cameras in Oregon is described in this page, and red light cameras are permitted statewide in Oregon.
No other camera types should be mapped in Waze.
To do list
Many states and territories keep an active list of pending or closed actions that need to be done in the state by the editors. All editors are welcome to contribute to the list of activities.
This state does not currently have an active "to do" list at this time. Check in the Oregon section of the Waze forums to discuss creating one.
Area Managers
The table below identifies the editors also designated as Area Managers or higher who are editing in Oregon. If you have any questions, please consider contacting them directly as needed. If you are an Area Manager that covers Oregon, or a USA Country Manager that does a lot of work in Oregon, please add yourself to this list (alphabetical by username) in the correct rank section.
The editor who also serves as the Regional Coordinator for Oregon is automatically listed at the top of the table. That editor may not be highly active in this state and therefore may not be listed separately in the table.
Oregon — Area, State, Country Managers, and Regional Coordinators
