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

Southeast/PrivateRoads

From waze
< Southeast
Revision as of 04:59, 7 March 2017 by Subs5 (Talk | contribs)

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


Private Road Use in the Southeast

The assumption is that you are already familiar with the wiki discussion on the use of private roads in the USA.

Improper Use of Private Roads

In general, private roads are over-used. It is easier to describe situations where the use of private road segments are not appropriate than to identify situations where their use is appropriate.

Before you set a road segment as Private, in the Southeast, understand the following: Connecting multiple private road segments to a segment of any other type does not increase the waze routing penalty for driving across those segments. In other words, connecting two private road segments together does not DOUBLE the routing penalty. In fact, the routing penalty is the same as if there were only one private segment.

See the example to the right:
Incorrect Segment Type

Important points to be noted from review of the picture include the following:

  • There is NO Private Road penalty incurred while driving in the neighborhood.
  • Since there is only one way in or out, waze will only route there (regardless of road type) when the destination is inside the neighborhood.

See the example to the right for the correct segment type in the same neighborhood.

Correct Segment Type

Note the lack of private road types in the neighborhood. They are all Parking Lot Road type. The Parking Lot Road type should be used when the roads have no name, and are not a public through route.
The private road type should only be used to create penalties to prevent through routing.

Dead End Private Roads

Private roads segments that lead to a 'dead end' are not necessary. If waze routes a U-turn over a dead-end private road segment, it's because there is no other option. Since most Driveways are dead-end, make sure you follow the guidance for Driveways. Guidance from this SouthEast discussion on private roads does not override the Driveways guidance.

Proper Private Road Type Use

The Standard Gate

Standard Gates are the most basic style of private road penalty that is allowed in the southeast. Make sure you understand how to create 'Standard gates' (see picture below) on the waze map. You need to understand the use of both gates and private road segments before adding or changing segments that are private. (Reference: Standard Gates)

Gates are for Residents

Gates are mapped in the interest of the private installation's primary user. This means that for a residential community we map for the resident, for a Industrial complex we map for the employees, and for a resort we map for the guests. Also note that Waze cannot distinguish between residents, guests or employees-- Wazers will have to decide for themselves which gate(s) is/are for their use.

If you feel a non-primary function entrance, construction entrance, service entrance, emergency gate, or otherwise should be mapped please consult your Area Managers.

No Through Traffic
Standard gate northcutt st .png
"No Through Traffic" situations: If both ends of a street, or said another way, all entries into or out of a neighborhood have signage indicating "no through traffic", standard gates are appropriate as opposed to using all private segments inside the neighborhood.

Nested Installations

Please consult your area manager, state manager or regional coordinator for mapping nested installations. These are usually inside large military bases. These involve a nested system of access, where the lower level should never route through the higher level of access. (Reference: Private Installations)