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

Difference between revisions of "Virginia/Special roads/Main"

From waze
Jump to: navigation, search
(*/Special_roads/Main*/)
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
{{USRedirect}}
 
<!-- This page is only transcluded into (displayed on) the main page for this state. See more detailed instructions below. --><noinclude>{{:USA/CommonState/ReturnPurge|{{SubPage2}}}}<br/></noinclude><!--
 
<!-- This page is only transcluded into (displayed on) the main page for this state. See more detailed instructions below. --><noinclude>{{:USA/CommonState/ReturnPurge|{{SubPage2}}}}<br/></noinclude><!--
 
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------>  
 
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------>  
  
*[[Best map editing practice#When (Not) to Split a Two-Way Road|Divided Highways]]
+
===== State specific special road guidelines =====
*[[Carpool, HOV, Transit lanes]]
+
The following special roads are managed slightly uniquely in some states and territories.
*[[Creating and Editing a roundabout|Roundabouts/Traffic Circles]]
+
 
*[[Creating and Editing street segments#Fix the end-node on cul-de-sacs and dead-ends|Cul-de-sac's]]
+
======Parking Lot Roads======
*[[Road types/USA#Parking Lot Road|Parking Lot Roads]]
+
{{RootPage2}} uses the following national standard guidelines found in the Wiki for [[Road_types/USA#Parking_Lot_Road|Parking Lot Roads]].
*[[Best map editing practice#Toll roads|Toll Roads]]
+
 
 +
======Alleys======
 +
{{RootPage2}} uses the following guidelines for mapping alleys.
  
=== Alleys ===
 
 
*Alleys should always be mapped if they have a name.
 
*Alleys should always be mapped if they have a name.
 
*Alleys should always be mapped if they are the sole access to a home or business.
 
*Alleys should always be mapped if they are the sole access to a home or business.
 
*Alleys should always be set to "Private"
 
*Alleys should always be set to "Private"
 
*Alleys are normally mapped if they are acknowledged by the municipality.
 
*Alleys are normally mapped if they are acknowledged by the municipality.
 +
 
If an alley does not meet the above criteria, mapping is optional. Leave the name field blank.
 
If an alley does not meet the above criteria, mapping is optional. Leave the name field blank.
  
=== Non-drivable roads ===
+
Be careful adding alleys which will be closer to the destination pins for house numbers, or from Google, as this can cause all navigation to all the addresses on that block to route onto the alley instead. It may be better not to map these alleys, or you may have to adjust all the address pins to be closer to the actual roads.
 +
 
 +
====== Off-road / Not Maintained Road ======
 +
Virginia uses the following national standard guidelines found in the Wiki for [[Road_types/USA#Dirt|Off-road / Not Maintained Road]]. These were formerly called Dirt Roads (until Nov 2016).
 +
 
 +
====== Non-drivable roads ======
 +
 
 
Generally, if a path can't be driven on (e.g. Walking Trail, Pedestrian Boardwalk, Stairway, Runway/Taxiway) then it not normally mapped, unless approved by a Virginia State Manager or the Mid-Atlantic Regional Coordinator. If it is mapped, it should not be connected to any roads, its elevation should be set to 9 and it should be locked at Level 5.  This is due to the way the routing engine works, as Waze '''will''' route users to drive on these "Non-Drivable" road types.
 
Generally, if a path can't be driven on (e.g. Walking Trail, Pedestrian Boardwalk, Stairway, Runway/Taxiway) then it not normally mapped, unless approved by a Virginia State Manager or the Mid-Atlantic Regional Coordinator. If it is mapped, it should not be connected to any roads, its elevation should be set to 9 and it should be locked at Level 5.  This is due to the way the routing engine works, as Waze '''will''' route users to drive on these "Non-Drivable" road types.
  

Latest revision as of 03:08, 7 March 2017




State specific special road guidelines

The following special roads are managed slightly uniquely in some states and territories.

Parking Lot Roads

Virginia uses the following national standard guidelines found in the Wiki for Parking Lot Roads.

Alleys

Virginia uses the following guidelines for mapping alleys.

  • Alleys should always be mapped if they have a name.
  • Alleys should always be mapped if they are the sole access to a home or business.
  • Alleys should always be set to "Private"
  • Alleys are normally mapped if they are acknowledged by the municipality.

If an alley does not meet the above criteria, mapping is optional. Leave the name field blank.

Be careful adding alleys which will be closer to the destination pins for house numbers, or from Google, as this can cause all navigation to all the addresses on that block to route onto the alley instead. It may be better not to map these alleys, or you may have to adjust all the address pins to be closer to the actual roads.

Off-road / Not Maintained Road

Virginia uses the following national standard guidelines found in the Wiki for Off-road / Not Maintained Road. These were formerly called Dirt Roads (until Nov 2016).

Non-drivable roads

Generally, if a path can't be driven on (e.g. Walking Trail, Pedestrian Boardwalk, Stairway, Runway/Taxiway) then it not normally mapped, unless approved by a Virginia State Manager or the Mid-Atlantic Regional Coordinator. If it is mapped, it should not be connected to any roads, its elevation should be set to 9 and it should be locked at Level 5. This is due to the way the routing engine works, as Waze will route users to drive on these "Non-Drivable" road types.

The "Railroad" road type serves two purposes in Waze. First, it provides drivers with visual orientation relative to railroad and light-rail tracks. More importantly, in the common case where passenger-carrying tracks lie parallel with roads, mapping the tracks allows Waze to recognize spurious speed data from people Wazing on the train and prevent it from corrupting speed data for the adjacent road. Please see USA Road Types wiki page for more information on mapping railroads.