The new Waze Wiki, aka Wazeopedia, is now live at Wazeopedia.waze.com! While this legacy wiki will remain accessible for the time being, it is no longer updated by the community. For the most up-to-date guidance, please visit your local Wazeopedia.

Please do not make any more updates to these legacy wiki pages, all future updates should be made in your country's local Wazeopedia.

Clock over a larger globe

Maryland/Speed limits

From waze
< Maryland
Revision as of 14:40, 24 July 2017 by Nzahn1 (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Speed Limit 70.png

Maryland follows the national guidelines for adding speed limits to the map. There are a few items left up to local guidance which will be enumerated below.

Maryland law

Maryland law includes the following restrictions on the designation of speed limits. [1]

  • Maximum speed limits are as follows, unless otherwise signed/posted:
District Highway Type
Undivided Divided
Business 30 mph
Residential 30 mph 35 mph
Other Locations 50 mph 55 mph
  • Speed limits may be revised after a traffic study and then posted, but no limit may exceed 70 mph
  • Maximum speed limits for local jurisdictions include:
  • 15 miles an hour in alleys in Baltimore County

National guidance recap

  • The ONLY speed limits which should be added to the map are Regulatory Speed Limits. These are marked with black lettering on white rectangular signs.
  • Advisory Speed Plaque.png
    'Advisory' or speciality speed limits that are unsupported by the WME and the Waze app, and MUST NOT be added to road segments in the WME, including:
  • Advisory speeds
  • Truck speed limits
  • Night speed limits
  • Time day plaque.png
    Segments with time based different speed limits should use the speed limit which is in effect the majority of the time (most hours of the day, days of the week).
  • Speed limits should change where they legally go in effect. When a speed limit changes in the middle of a segment, a new junction should added to support the SL change. However a new junction should never be added for a SL if it will be within 200 feet of an existing junction, or potential junction.

Work zone speed limits

Work zone SL.png

A work zone (WZ) may have a lower advisory speed limit (SL) posted in black on orange Advisory Speed Plaque.png, or a regulatory speed limit posted in black on white with an orange "Work Zone" banner across the top Work zone SL.png.

We only consider the regulatory signs, and never map advisory speed limits.

Adding WZ SLs to segments is generally allowed.

  • Typically only projects which are expected to last at least 3 months should be added to the map.
  • The underlying SL, and expected project completion date should be documented in a map comment
  • Projects of shorter duration may be added as well, IF the editor has access to frequent status updates on the project, and is willing to monitor and adjust as soon as the SL is restored.

Where speed limits change

The Maryland supplement to the MUTCD stipulates that: A Speed Limit sign in a speed zone shall be located at or just beyond the point where the zone begins. If the zone begins at an intersection, the first Speed Limit sign for that zone shall be the Speed Limit sign normally erected beyond the intersection conforming to the standard sequence of signs at intersections.[2]

Maryland is a state where the speed limits are absolute and are enforceable from statute; speed limits need-not be posted to be enforced.

When adding speed limits to WME we should try to be as accurate as reasonable, while still preserving data for turn delays. Therefore if a speed limit changes in middle of a segment we will create a new junction to support the SL change. However if there is already an existing junction, or we can see the need to create a new junction to connect another segment to the road within 200 feet of the speed limit sign, we should mark the SL change using that existing (potential) junction node.

If at the editor's discretion in consultation with local managers, it is determined that a new junction to support a SL change between 200 - 1,000 feet away from a junction would have a negative impact on turn delay calculations, they may instead affect the SL change at an existing (potential) junction up to 1,000 feet away from the SL sign. This may be because the SL change is posted in middle of turning or exit lane where traffic regularly backs up from the following junction to before the position of the SL sign.

  1. , MD Transportation Article §21–801.1
  2. , Maryland MUTCD, updated 2011