| 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.
Vermont currently observes the following Standardized Name nomenclature for Numbered Routes:
|Road Type||Standardized Name|
State Highway numbering includes spurs and loops (E.g. VT-67A).
These naming conventions should also be applied to "Old" numbered routes that have become local streets after the completion of new highway alignments. For example, "Old State Rte ##" and "Old US Hwy ##" Should be renamed "Old VT-##" and "Old US-##" respectively. In some cases, it may be necessary to research whether the old route was formerly a state or US highway.
State Highway Signage
Most state highways are maintained by the Vermont Agency of Transportation (VTrans). However, some entire routes, and portions of others, are maintained by local governments, such as towns or cities, instead. These town-maintained routes are internally called "state-designated town highways" and are typically designated as "class 1 town highways".
Map editors should treat both types of state highways the same when dealing with road types.
These are the general guidelines for elevation in Vermont. Note that these guidelines are currently under revision on the National level, and are subject to change:
- Drivable and non-drivable segments are handled the same way with elevation.
- Set elevation to Ground on all non-tunneled segments that are not passing over/beneath another segment or waterway.
- Only segments that "cannot see the sky" should have negative elevation (i.e. tunnels).
- Only set elevation as high as necessary.
- Elevation of overlapping segments should be set relative to each other, with the lowest segment as Ground (unless a tunnel).
- 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.
Regarding Local and Alternate Names:
In situations where a highway passes through a town, the road in those areas is typically named something other than the numbered route. In these situations the road should be named based on the following conditions:
- If the local street signs provide guidance with the local name, that should be used as the primary name in the Waze map. The numbered route should be added as an alternate name.
- If the local signs only indicate the route number, then that should be the primary name and the local road name should be added as an alternate name.
In Vermont 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.
|Highest rank of connected segments|
Note: Do Not Mass Edit just to update locks to these standards, these can adjusted as you find while editing other aspects of the segments such as FC, speed limits, naming, etc.
Some segments still warrant higher locks and care should be taken when setting segment lock to these standards to look for and protect these special setups with higher locks. Some examples; segments which are part of BDP, U-turn prevention, or using micro-doglegs, or other complex intersection setups.