https://www.waze.com/wiki/USA/api.php?action=feedcontributions&user=Tonestertm&feedformat=atomWazeopedia - User contributions [en]2024-03-29T04:41:13ZUser contributionsMediaWiki 1.40.2https://www.waze.com/wiki/USA/index.php?title=Places/EV_charging_station&diff=178090Places/EV charging station2023-02-07T23:08:13Z<p>Tonestertm: wordsmith</p>
<hr />
<div>{{mbox<br />
| type = critical<br />
| textstyle = color: red; font-weight: bold; font-style: italic;<br />
| text = All electric vehicle charging station PURs must be reviewed in the beta WME to ensure accurate assignment of [[#Public, restricted, or private|public, restricted, or private]] attributes. <br />
| imageright = [[File:Beta wme.png|link=https://beta.waze.com/editor/|50px]]<br />
}}<br />
<br />
[[File:Evchargesign.png|thumbnail]]<br />
<br />
Many cars now on the road are hybrids or completely electrically powered. The current state of charging stations is not as robust as the network of gas stations that exist in the USA. Due to the limited range and challenges for charging, having a uniform experience for wazers who operate an electric vehicle is important.<br />
<br />
===Naming===<br />
Some EV charging stations are part of a national or regional network. These are known as "networked" charging stations. Charging stations that are not part of a network are known as "non-networked" charging stations.<br />
<br />
==== Networked charging stations ====<br />
The primary name of a networked charging station should always start with the '''network name'''. <br />
<br />
In some situations, you should also add a '''location name''', separated from the network name by a hyphen. <br />
<br />
* If the network provider provides user-friendly names for its charging stations, and the name is more than just a city name (with or without state), then add the location name after a hyphen, but remove the city and state (if it matches the city and state in the address). <br />
**Don't remove a city name that is part of another name (such as "Gulfport Premium Outlets" or "Pensacola Square").<br />
** The location name should generally match the name used by the charging network, if the charging network name is user-friendly. ChargePoint names are not generally user-friendly. <br />
* If the charging station is associated with another place (and doesn't have an official name as described above), then use the name of that place as the location name. <br />
<br />
{| class="wikitable"<br />
|+Examples<br />
!Network<br />
!Location Name (from provider)<br />
!Waze Place Primary Name<br />
|-<br />
|Electrify America<br />
|Walmart 402 Breaux Bridge<br />
|Electrify America - Walmart 402<br />
|-<br />
|Electrify America<br />
|Gulfport Premium Outlets<br />
|Electrify America - Gulfport Premium Outlets<br />
|-<br />
|Tesla Supercharger<br />
|Metairie, LA<br />
|Tesla Supercharger<br />
|-<br />
|Tesla Supercharger<br />
|Las Vegas, NV - Bridger Avenue<br />
|Tesla Supercharger - Bridger Avenue<br />
|-<br />
|Tesla Destination Charger<br />
|Arlington Resort Hotel & Spa<br />
|Tesla Destination Charger - Arlington Resort Hotel & Spa<br />
|-<br />
|Francis Energy<br />
|(none - Francis Energy does not name its locations)<br />
|Francis Energy<br />
|-<br />
|ChargePoint<br />
|ENTERGY NO LVL2 / LAFITTEGREENWAY<br />
|ChargePoint - Lafitte Greenway<br />
|-<br />
|ChargePoint<br />
|ENTERGY NO LVL2 / ROSENWALD REC<br />
|ChargePoint - Rosenwald Recreation Center<br />
|}<br />
Add "EV Charging Station" as an alternate name to all EV charging stations.<br />
<br />
==== Non-networked charging stations ====<br />
Non-networked charging stations should be named with the words "Charging Station", followed by a hyphen, followed by the location name. If possible, determine the location name the same way you would for a networked charger (including by using the name of an associated place). If there is no name or associated place, simply name it "Charging Station". For example,<br />
<br />
*Charging Station - Freedom Nissan<br />
*Charging Station - Pontchartrain Park<br />
*Charging Station - Premium Parking P376<br />
*Charging Station - Whole Foods<br />
*Charging Station - 11375 Haddaway Blvd<br />
Add "EV Charging Station" as an alternate name to all EV charging stations.<br />
<br />
===Details===<br />
<br />
==== Description ====<br />
...<br />
<br />
==== Location at venue ====<br />
EV charging stations can be hard to find. Include a short description wherever possible to help drivers find the station. For example,<br />
<br />
* On the western edge of the parking lot.<br />
* On the 6th floor lower level of the parking garage.<br />
* Near the front door, to the left (when looking at the building from the parking lot).<br />
* In the Rudy's BBQ parking lot east of the building.<br />
<br />
==== Network ====<br />
Include the network for networked chargers. Do not include a network for non-networked chargers.<br />
<br />
==== Price ====<br />
Use '''Paid''' if the average driver needs to pay to charge at the charging station, including<br />
<br />
* commercial parking facilities, even if you only pay once for parking (and charging is included in the parking rate);<br />
* paid DC fast chargers, even if some drivers have free charging plans associated with their vehicles.<br />
<br />
Use '''Free''' if the average driver can charge without paying.<br />
<br />
==== Payment methods ====<br />
Add any and all payment methods which are accepted at the charging station.<br />
<br />
* '''App''' if the user can start and pay for charging using a mobile app downloaded from the App Store, Play Store, or similar.<br />
* '''Credit card''' or '''Debit card''' if the user can start and pay for charging with a credit or debit card <u>without using an app or web browser</u>.<br />
* '''Membership card''' if the user can start and pay for charging using a membership card (whether a physical card or a mobile wallet card) issued by the charging network operator.<br />
* '''Online payment''' if the user can start and pay for charging using an online payment <u>without using an app that you have to download</u>.<br />
* '''Plug-in autocharge''' if the user can start and pay for charging by simply plugging in the car without requiring any further interaction.<br />
* '''Other''' if the user can pay with a method not listed above (including, for example, cash at a parking garage or valet parking service).<br />
<br />
==== Lock ====<br />
Lock charging stations to the same level you would a gas station in your state.<br />
<br />
=== Chargers ===<br />
The '''Chargers''' tab shows the chargers and plugs which are available at the charging station.<br />
<br />
Waze follows the Open Charge Point Interface (OCPI) protocol, which follows the structure '''Charging station » Charger » Plug'''.<br />
<br />
A '''charging station''' is a place that has at least one charger. A '''charger''' is a unit to which a vehicle connects to charge. A '''plug''' is the part of the cable that connects to the vehicle. Some chargers have more than one plug, but allow only one vehicle to charge at a time.<br />
<br />
The Chargers tab will be read-only on charging stations which are linked to an external provider. If you find an error in the Chargers tab, reach out to your (A)RC so they can address it with staff or the external provider.<br />
<br />
====Connector Type====<br />
Currently there are multiple types of connectors for charging electric vehicles, which are not universally compatible. Listing the connector type in the description field is critical to allow drivers to pick the correct charging station. The most common types of charging connectors are: J1772, J1772 CHAdeMO, NEMA520, J1772 COMBO, CHAdeMO<br />
<br />
*''J1772 Connector''<br />
<br />
====Number of spaces====<br />
An important consideration for many EV users is the number of spaces reserved for charging. Include this information in the description, especially if there is a time limit. <br />
<br />
*''2 reserved EV spaces''<br />
*''2 reserved EV spaces (30 minutes maximum)''<br />
<br />
=== More info ===<br />
<br />
====Access type====<br />
Charging stations may be available to the general public, restricted to a certain audience and time-frame, or completely private. <br />
<br />
* '''Public:''' Public chargers are available to the general public. For example, chargers at a shopping center or a public parking lot or garage. <br />
* '''Restricted:''' Restricted chargers are available to the public, but with limitations. For example, a user may charge at a restaurant's charging station, but only while dining. Another example would be a charger for hotel guests.<br />
* '''Private:''' Most private chargers will be those at homes, apartments, and workplaces. Private chargers are only available to the homeowner, business's employees and their guests. Additionally, home chargers that are shared via online "plug sharing" networks, but are not available to the public should also be considered private.<br />
{{mbox <br />
| text = {{As of|2023|02|05}} the production WME does not support marking a charging station as public, restricted, or private. '''Do not add''' any private or restricted charging stations; at this time, '''only add public charging stations'''. Any pending PURs for restricted or private locations '''should be left open''' until such time that the features are completed and available in the production WME. <br />
| type=critical }}<br />
<br />
====Website, Phone, Services, Open hours====<br />
As with any other place, include URL, phone number, services, and open hours for the charging station (no one wants to arrive late at night to find it closed). WMEPH can be helpful in ensuring harmonization of naming and details.<br />
<br />
Use the customer service '''phone number''' if there is one (for example, for a charging network or parking operator).<br />
<br />
===Resources===<br />
<br />
==== Charging network station locators ====<br />
<br />
===== National =====<br />
<br />
* [https://driver.chargepoint.com/ ChargePoint - Station Map]<br />
* [https://www.electrifyamerica.com/locate-charger/ Electrify America - Locate a Charger]<br />
* [https://www.evgo.com/find-a-charger/ EVgo - Find a Charger]<br />
* [https://www.tesla.com/findus Tesla - Find Us]<br />
<br />
===== Regional =====<br />
<br />
* [https://francisenergy.com/stations-near-you/ Francis Energy - Stations Near You] (Oklahoma)<br />
<br />
==== Other resources ====<br />
*[http://www.afdc.energy.gov/fuels/electricity_locations.html DOE charging station locations]<br />
*[https://opendata.maryland.gov/Energy-and-Environment/EV-Charging-Stations/wafg-t9bm Maryland charging station locations]<br />
<br />
===Forum===<br />
<br />
*[https://www.waze.com/forum/viewtopic.php?f=1636&t=276277 Forum discussion]</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=Places/EV_charging_station&diff=178089Places/EV charging station2023-02-07T22:51:53Z<p>Tonestertm: clarify dowloaded payment app</p>
<hr />
<div>{{mbox<br />
| type = critical<br />
| textstyle = color: red; font-weight: bold; font-style: italic;<br />
| text = All electric vehicle charging station PURs must be reviewed in the beta WME to ensure accurate assignment of [[#Public, restricted, or private|public, restricted, or private]] attributes. <br />
| imageright = [[File:Beta wme.png|link=https://beta.waze.com/editor/|50px]]<br />
}}<br />
<br />
[[File:Evchargesign.png|thumbnail]]<br />
<br />
Many cars now on the road are hybrids or completely electrically powered. The current state of charging stations is not as robust as the network of gas stations that exist in the USA. Due to the limited range and challenges for charging, having a uniformed experience for wazers who operate an electric vehicle is important.<br />
<br />
===Naming===<br />
Some EV charging stations are part of a national or regional network. These are known as "networked" charging stations. Charging stations that are not part of a network are known as "non-networked" charging stations.<br />
<br />
==== Networked charging stations ====<br />
The primary name of a networked charging station should always start with the '''network name'''. <br />
<br />
In some situations, you should also add a '''location name''', separated from the network name by a hyphen. <br />
<br />
* If the network provider provides user-friendly names for its charging stations, and the name is more than just a city name (with or without state), then add the location name after a hyphen, but remove the city and state (if it matches the city and state in the address). <br />
**Don't remove a city name that is part of another name (such as "Gulfport Premium Outlets" or "Pensacola Square").<br />
** The location name should generally match the name used by the charging network, if the charging network name is user-friendly. ChargePoint names are not generally user-friendly. <br />
* If the charging station is associated with another place (and doesn't have an official name as described above), then use the name of that place as the location name. <br />
<br />
{| class="wikitable"<br />
|+Examples<br />
!Network<br />
!Location Name (from provider)<br />
!Waze Place Primary Name<br />
|-<br />
|Electrify America<br />
|Walmart 402 Breaux Bridge<br />
|Electrify America - Walmart 402<br />
|-<br />
|Electrify America<br />
|Gulfport Premium Outlets<br />
|Electrify America - Gulfport Premium Outlets<br />
|-<br />
|Tesla Supercharger<br />
|Metairie, LA<br />
|Tesla Supercharger<br />
|-<br />
|Tesla Supercharger<br />
|Las Vegas, NV - Bridger Avenue<br />
|Tesla Supercharger - Bridger Avenue<br />
|-<br />
|Tesla Destination Charger<br />
|Arlington Resort Hotel & Spa<br />
|Tesla Destination Charger - Arlington Resort Hotel & Spa<br />
|-<br />
|Francis Energy<br />
|(none - Francis Energy does not name its locations)<br />
|Francis Energy<br />
|-<br />
|ChargePoint<br />
|ENTERGY NO LVL2 / LAFITTEGREENWAY<br />
|ChargePoint - Lafitte Greenway<br />
|-<br />
|ChargePoint<br />
|ENTERGY NO LVL2 / ROSENWALD REC<br />
|ChargePoint - Rosenwald Recreation Center<br />
|}<br />
Add "EV Charging Station" as an alternate name to all EV charging stations.<br />
<br />
==== Non-networked charging stations ====<br />
Non-networked charging stations should be named with the words "Charging Station", followed by a hyphen, followed by the location name. If possible, determine the location name the same way you would for a networked charger (including by using the name of an associated place). If there is no name or associated place, simply name it "Charging Station". For example,<br />
<br />
*Charging Station - Freedom Nissan<br />
*Charging Station - Pontchartrain Park<br />
*Charging Station - Premium Parking P376<br />
*Charging Station - Whole Foods<br />
*Charging Station - 11375 Haddaway Blvd<br />
Add "EV Charging Station" as an alternate name to all EV charging stations.<br />
<br />
===Details===<br />
<br />
==== Description ====<br />
...<br />
<br />
==== Location at venue ====<br />
EV charging stations can be hard to find. Include a short description wherever possible to help drivers find the station. For example,<br />
<br />
* On the western edge of the parking lot.<br />
* On the 6th floor lower level of the parking garage.<br />
* Near the front door, to the left (when looking at the building from the parking lot).<br />
* In the Rudy's BBQ parking lot east of the building.<br />
<br />
==== Network ====<br />
Include the network for networked chargers. Do not include a network for non-networked chargers.<br />
<br />
==== Price ====<br />
Use '''Paid''' if the average driver needs to pay to charge at the charging station, including<br />
<br />
* commercial parking facilities, even if you only pay once for parking (and charging is included in the parking rate);<br />
* paid DC fast chargers, even if some drivers have free charging plans associated with their vehicles.<br />
<br />
Use '''Free''' if the average driver can charge without paying.<br />
<br />
==== Payment methods ====<br />
Add any and all payment methods which are accepted at the charging station.<br />
<br />
* '''App''' if the user can start and pay for charging using a mobile app downloaded from the App Store, Play Store, or similar.<br />
* '''Credit card''' or '''Debit card''' if the user can start and pay for charging with a credit or debit card <u>without using an app or web browser</u>.<br />
* '''Membership card''' if the user can start and pay for charging using a membership card (whether a physical card or a mobile wallet card) issued by the charging network operator.<br />
* '''Online payment''' if the user can start and pay for charging using an online payment <u>without using an app that you have to download</u>.<br />
* '''Plug-in autocharge''' if the user can start and pay for charging by simply plugging in the car without requiring any further interaction.<br />
* '''Other''' if the user can pay with a method not listed above (including, for example, cash at a parking garage or valet parking service).<br />
<br />
==== Lock ====<br />
Lock charging stations to the same level you would a gas station in your state.<br />
<br />
=== Chargers ===<br />
The '''Chargers''' tab shows the chargers and plugs which are available at the charging station.<br />
<br />
Waze follows the Open Charge Point Interface (OCPI) protocol, which follows the structure '''Charging station » Charger » Plug'''.<br />
<br />
A '''charging station''' is a place that has at least one charger. A '''charger''' is a unit to which a vehicle connects to charge. A '''plug''' is the part of the cable that connects to the vehicle. Some chargers have more than one plug, but allow only one vehicle to charge at a time.<br />
<br />
The Chargers tab will be read-only on charging stations which are linked to an external provider. If you find an error in the Chargers tab, reach out to your (A)RC so they can address it with staff or the external provider.<br />
<br />
====Connector Type====<br />
Currently there are multiple types of connectors for charging electric vehicles, which are not universally compatible. Listing the connector type in the description field is critical to allow drivers to pick the correct charging station. The most common types of charging connectors are: J1772, J1772 CHAdeMO, NEMA520, J1772 COMBO, CHAdeMO<br />
<br />
*''J1772 Connector''<br />
<br />
====Number of spaces====<br />
An important consideration for many EV users is the number of spaces reserved for charging. Include this information in the description, especially if there is a time limit. <br />
<br />
*''2 reserved EV spaces''<br />
*''2 reserved EV spaces (30 minutes maximum)''<br />
<br />
=== More info ===<br />
<br />
====Access type====<br />
Charging stations may be available to the general public, restricted to a certain audience and time-frame, or completely private. <br />
<br />
* '''Public:''' Public chargers are available to the general public. For example, chargers at a shopping center or a public parking lot or garage. <br />
* '''Restricted:''' Restricted chargers are available to the public, but with limitations. For example, a user may charge at a restaurant's charging station, but only while dining. Another example would be a charger for hotel guests.<br />
* '''Private:''' Most private chargers will be those at homes, apartments, and workplaces. Private chargers are only available to the homeowner, business's employees and their guests. Additionally, home chargers that are shared via online "plug sharing" networks, but are not available to the public should also be considered private.<br />
{{mbox <br />
| text = {{As of|2023|02|05}} the production WME does not support marking a charging station as public, restricted, or private. '''Do not add''' any private or restricted charging stations; at this time, '''only add public charging stations'''. Any pending PURs for restricted or private locations '''should be left open''' until such time that the features are completed and available in the production WME. <br />
| type=critical }}<br />
<br />
====Website, Phone, Services, Open hours====<br />
As with any other place, include URL, phone number, services, and open hours for the charging station (no one wants to arrive late at night to find it closed). WMEPH can be helpful in ensuring harmonization of naming and details.<br />
<br />
Use the customer service '''phone number''' if there is one (for example, for a charging network or parking operator).<br />
<br />
===Resources===<br />
<br />
==== Charging network station locators ====<br />
<br />
===== National =====<br />
<br />
* [https://driver.chargepoint.com/ ChargePoint - Station Map]<br />
* [https://www.electrifyamerica.com/locate-charger/ Electrify America - Locate a Charger]<br />
* [https://www.evgo.com/find-a-charger/ EVgo - Find a Charger]<br />
* [https://www.tesla.com/findus Tesla - Find Us]<br />
<br />
===== Regional =====<br />
<br />
* [https://francisenergy.com/stations-near-you/ Francis Energy - Stations Near You] (Oklahoma)<br />
<br />
==== Other resources ====<br />
*[http://www.afdc.energy.gov/fuels/electricity_locations.html DOE charging station locations]<br />
*[https://opendata.maryland.gov/Energy-and-Environment/EV-Charging-Stations/wafg-t9bm Maryland charging station locations]<br />
<br />
===Forum===<br />
<br />
*[https://www.waze.com/forum/viewtopic.php?f=1636&t=276277 Forum discussion]</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=Places/EV_charging_station&diff=178088Places/EV charging station2023-02-07T22:16:57Z<p>Tonestertm: missing word</p>
<hr />
<div>{{mbox<br />
| type = critical<br />
| textstyle = color: red; font-weight: bold; font-style: italic;<br />
| text = All electric vehicle charging station PURs must be reviewed in the beta WME to ensure accurate assignment of [[#Public, restricted, or private|public, restricted, or private]] attributes. <br />
| imageright = [[File:Beta wme.png|link=https://beta.waze.com/editor/|50px]]<br />
}}<br />
<br />
[[File:Evchargesign.png|thumbnail]]<br />
<br />
Many cars now on the road are hybrids or completely electrically powered. The current state of charging stations is not as robust as the network of gas stations that exist in the USA. Due to the limited range and challenges for charging, having a uniformed experience for wazers who operate an electric vehicle is important.<br />
<br />
===Naming===<br />
Some EV charging stations are part of a national or regional network. These are known as "networked" charging stations. Charging stations that are not part of a network are known as "non-networked" charging stations.<br />
<br />
==== Networked charging stations ====<br />
The primary name of a networked charging station should always start with the '''network name'''. <br />
<br />
In some situations, you should also add a '''location name''', separated from the network name by a hyphen. <br />
<br />
* If the network provider provides user-friendly names for its charging stations, and the name is more than just a city name (with or without state), then add the location name after a hyphen, but remove the city and state (if it matches the city and state in the address). <br />
**Don't remove a city name that is part of another name (such as "Gulfport Premium Outlets" or "Pensacola Square").<br />
** The location name should generally match the name used by the charging network, if the charging network name is user-friendly. ChargePoint names are not generally user-friendly. <br />
* If the charging station is associated with another place (and doesn't have an official name as described above), then use the name of that place as the location name. <br />
<br />
{| class="wikitable"<br />
|+Examples<br />
!Network<br />
!Location Name (from provider)<br />
!Waze Place Primary Name<br />
|-<br />
|Electrify America<br />
|Walmart 402 Breaux Bridge<br />
|Electrify America - Walmart 402<br />
|-<br />
|Electrify America<br />
|Gulfport Premium Outlets<br />
|Electrify America - Gulfport Premium Outlets<br />
|-<br />
|Tesla Supercharger<br />
|Metairie, LA<br />
|Tesla Supercharger<br />
|-<br />
|Tesla Supercharger<br />
|Las Vegas, NV - Bridger Avenue<br />
|Tesla Supercharger - Bridger Avenue<br />
|-<br />
|Tesla Destination Charger<br />
|Arlington Resort Hotel & Spa<br />
|Tesla Destination Charger - Arlington Resort Hotel & Spa<br />
|-<br />
|Francis Energy<br />
|(none - Francis Energy does not name its locations)<br />
|Francis Energy<br />
|-<br />
|ChargePoint<br />
|ENTERGY NO LVL2 / LAFITTEGREENWAY<br />
|ChargePoint - Lafitte Greenway<br />
|-<br />
|ChargePoint<br />
|ENTERGY NO LVL2 / ROSENWALD REC<br />
|ChargePoint - Rosenwald Recreation Center<br />
|}<br />
Add "EV Charging Station" as an alternate name to all EV charging stations.<br />
<br />
==== Non-networked charging stations ====<br />
Non-networked charging stations should be named with the words "Charging Station", followed by a hyphen, followed by the location name. If possible, determine the location name the same way you would for a networked charger (including by using the name of an associated place). If there is no name or associated place, simply name it "Charging Station". For example,<br />
<br />
*Charging Station - Freedom Nissan<br />
*Charging Station - Pontchartrain Park<br />
*Charging Station - Premium Parking P376<br />
*Charging Station - Whole Foods<br />
*Charging Station - 11375 Haddaway Blvd<br />
Add "EV Charging Station" as an alternate name to all EV charging stations.<br />
<br />
===Details===<br />
<br />
==== Description ====<br />
...<br />
<br />
==== Location at venue ====<br />
EV charging stations can be hard to find. Include a short description wherever possible to help drivers find the station. For example,<br />
<br />
* On the western edge of the parking lot.<br />
* On the 6th floor lower level of the parking garage.<br />
* Near the front door, to the left (when looking at the building from the parking lot).<br />
* In the Rudy's BBQ parking lot east of the building.<br />
<br />
==== Network ====<br />
Include the network for networked chargers. Do not include a network for non-networked chargers.<br />
<br />
==== Price ====<br />
Use '''Paid''' if the average driver needs to pay to charge at the charging station, including<br />
<br />
* commercial parking facilities, even if you only pay once for parking (and charging is included in the parking rate);<br />
* paid DC fast chargers, even if some drivers have free charging plans associated with their vehicles.<br />
<br />
Use '''Free''' if the average driver can charge without paying.<br />
<br />
==== Payment methods ====<br />
Add any and all payment methods which are accepted at the charging station.<br />
<br />
* '''App''' if the user can start and pay for charging using a mobile app downloaded from the App Store, Play Store, or similar.<br />
* '''Credit card''' or '''Debit card''' if the user can start and pay for charging with a credit or debit card <u>without using an app or web browser</u>.<br />
* '''Membership card''' if the user can start and pay for charging using a membership card (whether a physical card or a mobile wallet card) issued by the charging network operator.<br />
* '''Online payment''' if the user can start and pay for charging using an online payment <u>without using an app</u>.<br />
* '''Plug-in autocharge''' if the user can start and pay for charging by simply plugging in the car without requiring any further interaction.<br />
* '''Other''' if the user can pay with a method not listed above (including, for example, cash at a parking garage or valet parking service).<br />
<br />
==== Lock ====<br />
Lock charging stations to the same level you would a gas station in your state.<br />
<br />
=== Chargers ===<br />
The '''Chargers''' tab shows the chargers and plugs which are available at the charging station.<br />
<br />
Waze follows the Open Charge Point Interface (OCPI) protocol, which follows the structure '''Charging station » Charger » Plug'''.<br />
<br />
A '''charging station''' is a place that has at least one charger. A '''charger''' is a unit to which a vehicle connects to charge. A '''plug''' is the part of the cable that connects to the vehicle. Some chargers have more than one plug, but allow only one vehicle to charge at a time.<br />
<br />
The Chargers tab will be read-only on charging stations which are linked to an external provider. If you find an error in the Chargers tab, reach out to your (A)RC so they can address it with staff or the external provider.<br />
<br />
====Connector Type====<br />
Currently there are multiple types of connectors for charging electric vehicles, which are not universally compatible. Listing the connector type in the description field is critical to allow drivers to pick the correct charging station. The most common types of charging connectors are: J1772, J1772 CHAdeMO, NEMA520, J1772 COMBO, CHAdeMO<br />
<br />
*''J1772 Connector''<br />
<br />
====Number of spaces====<br />
An important consideration for many EV users is the number of spaces reserved for charging. Include this information in the description, especially if there is a time limit. <br />
<br />
*''2 reserved EV spaces''<br />
*''2 reserved EV spaces (30 minutes maximum)''<br />
<br />
=== More info ===<br />
<br />
====Access type====<br />
Charging stations may be available to the general public, restricted to a certain audience and time-frame, or completely private. <br />
<br />
* '''Public:''' Public chargers are available to the general public. For example, chargers at a shopping center or a public parking lot or garage. <br />
* '''Restricted:''' Restricted chargers are available to the public, but with limitations. For example, a user may charge at a restaurant's charging station, but only while dining. Another example would be a charger for hotel guests.<br />
* '''Private:''' Most private chargers will be those at homes, apartments, and workplaces. Private chargers are only available to the homeowner, business's employees and their guests. Additionally, home chargers that are shared via online "plug sharing" networks, but are not available to the public should also be considered private.<br />
{{mbox <br />
| text = {{As of|2023|02|05}} the production WME does not support marking a charging station as public, restricted, or private. '''Do not add''' any private or restricted charging stations; at this time, '''only add public charging stations'''. Any pending PURs for restricted or private locations '''should be left open''' until such time that the features are completed and available in the production WME. <br />
| type=critical }}<br />
<br />
====Website, Phone, Services, Open hours====<br />
As with any other place, include URL, phone number, services, and open hours for the charging station (no one wants to arrive late at night to find it closed). WMEPH can be helpful in ensuring harmonization of naming and details.<br />
<br />
Use the customer service '''phone number''' if there is one (for example, for a charging network or parking operator).<br />
<br />
===Resources===<br />
<br />
==== Charging network station locators ====<br />
<br />
===== National =====<br />
<br />
* [https://driver.chargepoint.com/ ChargePoint - Station Map]<br />
* [https://www.electrifyamerica.com/locate-charger/ Electrify America - Locate a Charger]<br />
* [https://www.evgo.com/find-a-charger/ EVgo - Find a Charger]<br />
* [https://www.tesla.com/findus Tesla - Find Us]<br />
<br />
===== Regional =====<br />
<br />
* [https://francisenergy.com/stations-near-you/ Francis Energy - Stations Near You] (Oklahoma)<br />
<br />
==== Other resources ====<br />
*[http://www.afdc.energy.gov/fuels/electricity_locations.html DOE charging station locations]<br />
*[https://opendata.maryland.gov/Energy-and-Environment/EV-Charging-Stations/wafg-t9bm Maryland charging station locations]<br />
<br />
===Forum===<br />
<br />
*[https://www.waze.com/forum/viewtopic.php?f=1636&t=276277 Forum discussion]</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=Road_names&diff=178000Road names2023-01-15T02:37:59Z<p>Tonestertm: split changed to divided in two places</p>
<hr />
<div>{{Hatnote| This article covers the <strong>naming conventions</strong> of roads. For the types of roads, see [[Road types]].}}<br />
<br />
==Road naming==<br />
<br />
All roads in our base maps came with the names as defined in the US TIGER dataset.<br />
<br />
However, you might notice a few problems with the original road names:<br />
Some of the names are not the 'common' names (usually, Waze will display the 'name' of the highway while most people know this highway by its number).<br />
<br />
On other examples, the same highway will have a different name on each side (for example, US Hwy 101 going North, and Bayshore Fwy going South).<br />
<br />
Some roads actually have two 'common' names (for example, the NJ Turnpike is also I-95 and both are relevant names), but currently, we can only display one name per road.<br />
<br />
For all these issues, we ask that you currently leave the situation as is. We are working on a few fixes, that will automate the proper naming and also allow multiple names for each segments (with a 'Primary' name as the one being displayed, but other names that bring up the same search results).<br />
<br />
'''NOTE''': In the future we may be able to display alternate names for each segment / road, and choose which one of these is the 'common' name. This is also true for road shield generation which is partially broken so shields may or may not be displayed in your area.<br />
<br />
===Concurrent names===<br />
====Overlapping Highways====<br />
When two or more numbered highways (or interstates) run concurrently (one stretch of road has multiple route numbers), the segment should be named after the '''primary''' route designation, which usually has one or more of the following attributes:<br />
<br />
*The route whose mile markers are used for the concurrent segments<br />
*The route whose exit numbers are used for the concurrent segments<br />
*When the concurrency ends, the route whose path does '''not''' get signed as a numbered exit.<br />
<br />
The other route number(s) can be entered as alternate names. If alternate names are entered, be sure not to introduce any alternate name discontinuities which may trigger the [[Detour Prevention Mechanisms|big detour prevention mechanism]]. In particular, use cardinal (directional) names on divided highways for both primary and alternate names.<br />
<br />
====Surface-level highways through cities/towns====<br />
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:<br />
<br />
*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.<br />
*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.<br />
<br />
====Local freeway names and significant bridges====<br />
Sometimes, a numbered freeway will also have a local name or will traverse a named [[Places/Bridge|bridge]].<br />
<br />
*If the local name or bridge name is used on signage, in broadcast traffic reports, and/or colloquial conversation, the local name or bridge name should be added to the primary name after the primary route designation, separated by a bullet " • ".<br />
**This is done primarily to improve clarity and precision of traffic, incident, and closure reports, where including the local name or bridge name can make such reports easier to understand at a glance, more precise as to their specific location, or both.<br />
*Examples:<br />
**I-94 W • Dan Ryan Expwy<br />
**M-10 N • Lodge Fwy<br />
**I-5 N • Santa Ana Fwy<br />
**I-495 E • Long Island Expwy<br />
**I-10 E • Bonnet Carré Spillway Br<br />
**US-90 BUS W • Crescent City Connection<br />
<br />
===Highways===<br />
<br />
====Interstate Highways [[Image:I-95.svg.png|28px]] [[Image:I-695.svg.png|35px]]====<br />
<br />
:Components of the Interstate Highway System should be denoted as shown:<br />
::'''I-10 E''' for Interstate 10, Eastbound<br />
::'''I-310 S''' for Interstate 310, Southbound<br />
::'''I-35E N''' for Interstate 35E, Northbound (Letter suffixes are only in Minnesota and Texas)<br />
:Nearly all interstates are divided highways by necessity, and they should be drawn as such in the map for navigational accuracy.<br />
<br />
====United States Numbered Highways [[Image:US 20.svg.png|30px]]====<br />
<br />
Certain formatting guidelines must be followed to ensure that highway shields are shown in the Live Map and in the client. Note that map shield generation is not implemented for all situations, so some roads will not display a shield. Waze has said that there will eventually be a process allowing map editors to add shields to road segments in a way that is not connected to the name of that segment.<br />
<br />
;US Highways<br />
:Federal highways should be denoted as follows. Note that the trailing N, S, E, W cardinal direction indicator is used for numbered highways and interstates which are divided into two 1-way segments, [[Best_map_editing_practice#When_.28Not.29_to_Split_a_Two-Way_Road|per the guidelines]].<br />
<br />
::'''US-61 S''' for U.S. Highway 61, Southbound<br />
::'''US-425 W''' for U.S. Highway 425, Westbound<br />
::'''US-90 BUS S''' for U.S. Highway 90 Business, Southbound<br />
:::(note that BUS should be all uppercase for TTS to pronounce as "business". "Bus", "bus", etc. will pronounce as "Bus".)<br />
::'''US-90 ALT E''' for U.S. Highway 90 Alternate, Eastbound<br />
::'''US-199 SPUR''' for U.S. Highway 199 Spur<br />
<br />
:Refer to the [[#Concurrent_names|concurrent names]] section to determine if the US highway name should be the primary name when traveling through cities & towns.<br />
<br />
====State highways [[Image:State Hwy Sign 35.svg.png|30px]] [[Image:South_Carolina_170.svg.png|38px]] [[Image:Florida_60.svg.png|30px]] [[Image:Louisiana 3234.svg.png|30px]] [[Image:Alabama_5.svg.png|30px]] [[Image:MT-sec-326.svg.png|30px]] [[Image:North_Dakota_23.svg.png|30px]] [[Image:Hawaii_marker.png|30px]]====<br />
The Live Map will parse "State Rte xx" and "State Hwy yyy" and show a sign badge. However, as different states have different naming conventions (and different shields), this is not optimal for ramps. <br />
<br />
Follow your state's naming conventions as defined in the [[highway naming]] by state table. <br />
<br />
The same notes and examples for U.S. Highways above applies for state highways. Refer to the [[#Concurrent_names|concurrent names]] section to determine if the state route name should be the primary name when traveling through cities & towns. State routes may also be divided if it [[Best_map_editing_practice#When_.28Not.29_to_Split_a_Two-Way_Road|meets the guidelines]].<br />
<br />
====County and township highways and roads [[Image:Baldwin County Route 64 AL.svg.png|35px]] [[Image:St Louis County Route 7 MN.svg.png|35px]]====<br />
<br />
Text to speech on the client reads CR- as "County Road." So "CR-10" is read as "County Road Ten"<br />
<br />
Where road names are the same as cardinal directions (N, S, E, W), [[Road_names#United_States_Numbered_Highways|no special modification is necessary]] so that the voice prompt will read the letter and not say it as a direction. Ensure there are no spaces between the hyphen and the letter. Double or triple-letter roads with directional letters (e.g. CR-EN, CR-SAL) will not be spoken as directions but might be pronounced as if a word.<br />
<br />
There is no other TTS abbreviation for county-owned roads in any capacity except those listed here. For these reasons: that county shields may someday be supported (and a named standard makes this easier to implement), and for brevity's sake in turn instructions and map displays, it is suggested (but by no means required) that individual states adopt one of these standards;<br />
<br />
*CR-<br />
*CH-<br />
*TR-<br />
*TH-<br />
<br />
Another standard in use (which is longer, but you may see) is 'County Hwy XX'. The shortened format of CH- is available and is encouraged to be adopted when CR- is not appropriate.<br />
<br />
Many states have adopted the short format '''CR-xxx''' instead of the longer format. See the [[highway naming]] by state table for specific formatting of each state.<br />
<br />
:Also, refer to the [[#Concurrent_names|concurrent names]] section when the highway passes through a city or town that also has a local name for the road.<br />
<br />
For regions that have township highways, the shortened formats of TH- and TR- are also available.<br />
<br />
<br />
===Ramps and wayfinders{{Anchor|Exit|Entrance|Ramp}}===<br />
[[Image:Exit1.JPG|right|200px]][[Image:Exit2.jpg|right|200px]]<br />
Exit ramps and Entrance ramps are to be set as {{Ramp}} road type. The name of the ramp should match the exit or entrance signage as closely as possible. If the Waze instructions and display are different from the sign on the exit, Wazers may be unsure about which exit to take. Include everything that is present on the last sign prior to the exit. Do not combine all possible pre-ramp signage into the single ramp segment name.<br />
<br />
====Generally====<br />
Ramp names should generally match signage as closely as possible. This maximizes driver confidence.<br />
<br />
A ramp name is made up of one or more '''elements''', separated by '''separators'''.<br />
<br />
*'''Elements''' of a ramp name include:<br />
**Road names<br />
**Highway numbers (usually shields)<br />
**Control cities<br />
**Other non-city destinations<br />
**Exit numbers<br />
*'''Separators''' used in ramp names include:<br />
**'''Slash ( / )''', used when elements are <u>alternatives</u> to each other (e.g., alternative destinations). The TTS engine will generate a pause in its place.<br />
**'''Bullet ( • )''', used when two elements refer to alternative names for <u>the same thing</u>. The TTS engine will generate a pause in its place.<br />
***The bullet can be typed by pressing Option-8 on macOS, by holding Alt and pressing 0149 on the number pad in Windows, or by pressing Ctrl-Shift-U then typing 2022 on Chrome OS. Or, copy and paste it from this article.<br />
**'''"Toward" character ( » )''', used when one element takes you <u>toward</u> the following element. The TTS engine will say "toward" in its place. <br />
***The "toward" character can be typed by pressing Option-Shift-\ on macOS, by holding Alt and pressing 0187 on the number pad in Windows, or by pressing Ctrl-Shift-U then typing 00BB on Chrome OS. Or, copy and paste it from this article.<br />
<br />
All ramp names use the same general format, with slight modifications for different situations. The three basic forms of ramp names are as follows:<br />
<br />
*Numbered exit: {{nowrapcode|Exit [number]: [element] [/ or • or »] [element] [/ or • or »] [element]}}<br />
*All other ramps: {{nowrapcode|to [element] [/ or • or »] [element] [/ or • or »] [element]}} (unnumbered exits, on-ramps, etc.)<br />
*Wayfinder: {{nowrapcode|[element] [/ or • or »] [element] [/ or • or »] [element]}}<br />
<br />
====Exit ramps====<br />
Generally, the name of an exit ramp segment should be named using the last sign, closest to (or at) the exit.<br />
<br />
*Remember to abbreviate common words according to [[abbreviations and acronyms]].<br />
*See [[Junction Style Guide/Interchange#Ramp fork naming|Ramp fork naming in the Junction Style Guide]] for what to do when the off-ramp from main interstate or highway serves multiple exits further down the ramp.<br />
<br />
=====Numbered exits=====<br />
If an exit is signed and numbered, start with the word "Exit", followed by the exit number, followed by a colon (": "), followed by all the other '''elements''' on the sign, separated by the appropriate '''separators'''.<br />
<br />
*{{nowrapcode|Exit [number]: [element] [/ or • or »] [element] [/ or • or »] [element]}} ''(as needed)''<br />
<br />
For example,<br />
{| class="wikitable"<br />
|+Exit naming and separators<br />
!Road name<br />
!Why?<br />
!How TTS will pronounce it<br />
|-<br />
|Exit 16: I-33 » Bananaville / Celery Town<br />
|I-33 takes you toward either Bananaville or Celerytown (depending on which direction you go).<br />
|"Exit 16, I-33 toward Bananaville, Celery Town"<br />
|-<br />
|Exit 19A: US-22 N » Critter Hollow / Goop City<br />
|Northbound US-22 takes you toward both Critter Hollow and Goop City.<br />
|"Exit 19A, US-22 North toward Critter Hollow, Goop City"<br />
|-<br />
|Exit 24: US-103 • Schwarzenegger Rd<br />
|US-103 and Schwarzenegger Rd are alternative names for the same road.<br />
|"Exit 24, US-103, Schwarzenegger Road"<br />
|-<br />
|Exit 32: Terminator Blvd / Total Recall Rd<br />
|The exit takes you to either of these roads; neither road takes you to the other.<br />
|"Exit 32, Terminator Boulevard, Total Recall Road"<br />
|-<br />
|Exit 33B: Running Man St<br />
|<br />
|"Exit 33B, Running Man Street"<br />
|-<br />
|Exit 35C-B-A: Junior Dr / Twins Ave / Jingleallthe Way<br />
|The exit takes you to these three roads independently; none has a "towards" relationship with the next.<br />
|"Exit 35 C B A, Junior Drive, Twins Avenue, Jingleallthe Way"<br />
|-<br />
|Exit 1E: SR-1000 E » Sarah Connor Blvd<br />
|The exit takes you directly to SR-1000 eastbound, which in turn takes you to Sarah Connor Blvd.<br />
|"Exit 1 E, State Route 1000 East toward Sarah Connor Boulevard"<br />
|}<br />
Note:<br />
<br />
*If an exit number contains one or more letters, include it exactly as displayed on the sign. Separate sub-exit letters with a hyphen.<br />
**Do not leave spaces between the number and letter, between hyphens and adjacent letters, or between the last letter and the colon.<br />
*Note that, if the exit number contains one of the cardinal directions (N, S, E, W), that letter will be pronounced as a letter, not as the corresponding compass direction. For example, the above example will be pronounced "Exit One ''E'', State Route One Thousand ''East'' toward Sarah Connor Boulevard".<br />
*If the Exit has an official number that is documented elsewhere, but this exit number does not appear on any signs, do not use it to name the exit ramp. Waze instructions should match the signs where possible to avoid confusion. Check your [[Mapping resources|state's page]] for any local exceptions to this rule.<br />
<br />
=====Signed, unnumbered exits=====<br />
If an exit is signed and unnumbered, start with the word "to" (lowercase) and follow with all elements on the sign, separated with the appropriate separators:<br />
<br />
*{{nowrapcode|to [element] [/ or »] [element] [/ or »] [element]}} ''(as needed)''<br />
*''e.g.'',<br />
**{{nowrapcode|to SR-33 / Kindergarten Ct}} (the exit takes you to either SR-33 or Kindergarten Ct)<br />
**{{nowrapcode|to US-99 » Crazytown}} (US-99 takes you toward Crazytown)<br />
<br />
=====Unsigned exits=====<br />
If there is no sign at the exit, start with the word "to" (lowercase) and follow with the name of the road the ramp leads to. If that road has both a route number and a local name, use the route number first, followed by a slash, followed by the local name. If only a local name or only a highway designation are present, use only that. The goal is to avoid confusing the driver. <br />
<br />
*{{nowrapcode|to [element] [/ or • or »] [element]}} ''(as needed)''<br />
*''e.g.'', {{nowrapcode|to US-12 • Michigan Ave}}<br />
<br />
====Entrance ramps====<br />
Entrance ramps should be named similarly to unnumbered exits, following the format {{nowrapcode|to [element] [/ or »] [element]}}, etc. A typical entrance ramp should follow the format {{nowrapcode|to [road name of highway] [direction] » [control city]}}, where those elements are present—even if the control city is on a separate sign.<br />
<br />
*{{nowrapcode|to [element] [/ or • or »] [element]}} ''(as needed)''<br />
*{{nowrapcode|to [highway name] [direction] » [control city] / [control city]}}<br />
<br />
For example,<br />
<br />
*{{nowrapcode|to I-10 W » Baton Rouge}}<br />
*{{nowrapcode|to Clearview Pkwy N » Mandeville}}<br />
*{{nowrapcode|to US-90 BUS W}}<br />
*{{nowrapcode|to LA-1 » Thibodaux / Lockport}}<br />
*{{nowrapcode|to I-10 E • US-90 E » Lafayette}}<br />
<br />
Note:<br />
<br />
*If signs before the on-ramp provide multiple destination information, combine them into the single on-ramp name.<br />
**''e.g.'', {{nowrapcode|to US-90 BUS W / to I-10 W » Miss River Br / Baton Rouge}}<br />
*The highway name and direction should always come before the control city, even if signage is presented in the opposite order.<br />
*Do not omit the word "to", because this could cause confusion with, say, the "Select entire street" function. [[Glossary#Text_to_Speech|Text-to-speech (TTS)]] instructions will deal properly with the word "to" when it constructs turn instructions.<br />
*Do not use "Ramp to" (this would result in [turn right / exit right] to ramp to ...)<br />
*Compass directions (such as "West" or "Westbound") accompanying highway shields and road names should be [[Abbreviations and acronyms|abbreviated]] using single-letter abbreviations, such as {{nowrapcode|W}}.<br />
**e.g., the legend "WEST" above a shield for I-10 should be entered as {{nowrapcode|I-10 W}}<br />
**Do not spell out compass directions (such as "West" or "Westbound") which accompany highway shields and road names. Do not use "WB" or other non-approved abbreviations, as they are not supported by the TTS engine.<br />
*When multiple on-ramps combine before merging into the main interstate or highway, it is advised to name the last common ramp with the conventions listed above. This will usually be the last ramp which is the one which actually joins the main interstate or highway.<br />
*When naming ramps and exits that lead to state highways, refer to the road naming conventions listed in [[Highway naming]] and cross-reference the state's wiki page (therein linked).<br />
**New Jersey: {{nowrapcode|to SR-45 » Passaic}}<br />
**Louisiana: {{nowrapcode|to LA-308 » Raceland}}<br />
**North Carolina: {{nowrapcode|to NC-55 » Winston-Salem}}<br />
<br />
===Un-mapped and new streets===<br />
<br />
Sometimes, there is a brand new road we aren't sure of the name yet, it is okay to leave the name of the road blank by marking the "None" checkbox next to the '''Name''' field in the [[Creating and editing road segments#Address Properties|Address Properties]] in the editor. Always make sure to choose the proper [[Road types|road type]] and [[Creating and editing road segments#Confirm the road by updating details|confirm the other road details]] to ensure that the road appears on the client app. Add a [[map comment]] to let other editors know that the name is missing and to check at a later time if more information is available.<br />
<br />
===Incomplete segments or red roads===<br />
<br />
[[File:Incomplete.jpg|right|120px|Incomplete.jpg]] Be sure to select country, state, enter the city name or check "None", and enter a street name, or check "None". Until you do this, your road will not be routable and will not show on the client map. These incomplete segments are colored bright red in WME.<br />
<br />
This must be done on all streets created in WME and on all streets created with the client "[[Pave]]" road function.<br />
<br />
"Paved" streets must also be connected to their adjacent roads, and [[Creating and editing road segments#Set allowed turns .28connections.29 turn restrictions|turn restrictions]] must be set in order to be routable.<br />
<br />
For more detailed instructions on how to address red roads see: [[Creating and editing road segments#Confirm the road by updating details|Confirming the road by updating details]]<br />
<br />
===City names on segments===<br />
{{mbox|type=notice|text='''Every segment with addresses (House Numbers or Residential Place Points) on it, must have a city name.'''<br />
<br />
'''On segments which have the "None" checkbox marked for the primary city name, the city name designated by the U.S. Postal Service should be set as an alternate city name for that segment.'''}}<br />
<br />
[[File:EditCityData.png|right|thumb|No Primary city name with alternate city name added|right]]<br />
<br />
To keep city names from sprawling over too wide an area in the Waze app, [[WME]] and [[Live Map]], except for within [[Military Bases|military bases]] a city name should only be used as a primary name for segments located in areas determined by local leadership to be displayed as cities on the map. This generally includes incorporated cities, towns, villages, etc., as well as census-designated or other unincorporated places recognized as city names by the [https://tools.usps.com/zip-code-lookup.htm?bycitystate USPS], but rules vary by state. This may mean that many addresses on the map are in “no city” areas, particularly in rural regions. The Waze addresses on these segments are otherwise not searchable without a city name, and because many Wazers will search for a location by its postal address, U.S. community leadership has established the above editing standard.<br />
<br />
There are other standards in place for other purposes requiring adding other street data in the the alternate. The addition of the USPS data does not change any other standards but is in addition to anything existing already on those affected segments.<br />
{{Details|/City names|city naming}}<br />
<br />
{{clear}}<br />
<br />
===Navigation instructions for unnamed segments===<br />
{{:Navigation instructions for unnamed segments/Conditions|transclude=yes}}<br />
<br />
==Abbreviations and acronyms==<br />
<br />
Only abbreviations that Waze recognizes should be used within the editor. Since Waze uses TTS (Text-to-Speech) prompting, it is important that the correct abbreviations are used to produce the correct speech output.<br />
<br />
A basic rule of thumb is, "when in doubt, spell it out".<br />
<br />
Refer to the [[Abbreviations and acronyms]] page for a list of suffix and recommended abbreviations.<br />
<br />
=={{Anchor|Construction zone}}Construction zones and closed roads==<br />
No naming changes are necessary for construction zone & closed roads. <br />
<br />
''For short-term closures or closures requiring immediate attention (e.g., traffic incidents), see [[Real time closures]].''<br />
<br />
''For large, long-term closures and major (re-)construction projects, see [[Scheduled reconfiguration]].''<br />
<br />
==Official sources of mapping information==<br />
<br />
Being in the Waze community of editors means sharing information you discover and learning from the discoveries of others! You can see some of the (old) [http://www.waze.com/forum/viewtopic.php?f=129&t=13695 official sources of mapping information (US only) provided in the forum] or check out the (new) [[mapping resources]] wiki page (preferred).<br />
<br />
Feel free to add new resources as you find them.<br />
<br />
{{ReturnTo | Editing manual | the editing manual}}<br />
<br />
[[Category:USA]]</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=Template:Lock_Standard_State&diff=177384Template:Lock Standard State2022-09-13T22:18:04Z<p>Tonestertm: Update NV ramps to HRCS</p>
<hr />
<div><noinclude><br />
{{Documentation}}<br />
</noinclude><br />
<includeonly>{{#switch: {{uc:{{{1|}}}{{{st|}}}{{{ST|}}}{{{St|}}}{{{sT|}}}}}<br />
| NJ<br />
| DE<br />
| PA<br />
| NORTHEAST = {{Locking Standard<!-- per Regional SM Hangout discussion with OrbitC https://www.waze.com/forum/viewtopic.php?f=569&t=177663 --><br />
|title=Statewide<br />
|Fwy=5<br />
|Ramp=Highest rank of connected segments<br />
|MH=3<br />
|mH=3<br />
|PS=1 (Auto)<br />
|Street=1 (Auto)<br />
|Private=1 (Auto)<br />
|note={{Red|Do Not Mass Edit just to update locks to these standards}}, these can be adjusted as you find them while editing other aspects of the segments such as FC, speed limits, naming, etc.<br />
<br />
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 [[Detour Prevention Mechanisms|BDP]], [[Uturn prevention|U-turn prevention]], or using [[Glossary#mDL|micro-doglegs]], or other complex intersection setups.}}<br />
| NH<br />
| VT<br />
| RI<br />
| CT<br />
| ME<br />
| MA = {{Locking Standard<!-- per https://www.waze.com/forum/viewtopic.php?f=569&t=177663 and https://www.waze.com/forum/viewtopic.php?f=618&t=248085 --><br />
|title=Statewide<br />
|Fwy=5<br />
|Ramp=Highest rank of connected segments<br />
|MH=4<br />
|mH=3<br />
|PS=1 (Auto)<br />
|Street=1 (Auto)<br />
|Private=1 (Auto)<br />
|note={{Red|Do Not Mass Edit just to update locks to these standards}}, these can be adjusted as you find them while editing other aspects of the segments such as FC, speed limits, naming, etc.<br />
<br />
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 [[Detour Prevention Mechanisms|BDP]], [[Uturn prevention|U-turn prevention]], or using [[Glossary#mDL|micro-doglegs]], or other complex intersection setups.}}<br />
<br />
| NEW ENGLAND = {{Locking Standard<!-- per Regional SM HO discussion with OrbitC on 2/11/16 https://www.waze.com/forum/viewtopic.php?f=945&t=177664&p=1328584#p1328582 --><br />
|title=CT/MA/ME/NH/RI/VT<br />
|Fwy=5|Ramp=Highest rank of connected segment|MH=4|mH=3|PS=1 (Auto)|Street=1 (Auto)|Private=1 (Auto)<br />
|note={{Red|Do Not Mass Edit just to update locks to these standards}}, these can be adjusted as you find them while editing other aspects of the segments such as FC, speed limits, naming, etc.<br />
<br />
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 [[Detour Prevention Mechanisms|BDP]], [[Uturn prevention|U-turn prevention]], or using [[Glossary#mDL|micro-doglegs]], or other complex intersection setups.}}<br />
<br />
| NY = {{Locking Standard <!-- https://www.waze.com/forum/viewtopic.php?f=569&t=177663 --><br />
|title=NYC Only<br />
|Fwy=5|Ramp=Highest rank of connected segment|MH=5|mH=4|PS=3|Street=1 (Auto)<br />
|title2=Everywhere Else<br />
|MH2=3|mH2=3|PS2=1 (Auto)|Street=1 (Auto)|Private=1 (Auto)<br />
|note={{Red|Do Not Mass Edit just to update locks to these standards}}, these can be adjusted as you find them while editing other aspects of the segments such as FC, speed limits, naming, etc.<br />
<br />
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 [[Detour Prevention Mechanisms|BDP]], [[Uturn prevention|U-turn prevention]], or using [[Glossary#mDL|micro-doglegs]], or other complex intersection setups.}}<!--A/p wiki--><br />
| TX = {{Locking Standard<br />
|lede=In Texas 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. If you find a road locked to a higher level than its minimum, please leave it locked no lower than that level when you have finished editing.<br />
|title=Lock Level<br />
|Fwy=5<br />
|Ramp=4<br />
|MH=4<br />
|mH=3<br />
|PS=2<br />
|Private=2 <br />
|Street=Automatic (1)}}<br />
<br />
| CA = {{Locking Standard<br />
|title=Metro Areas<br />
|title2=Rural<br />
|Fwy=5<br />
|Ramp=5<br />
|MH=3<br />
|MH2=2<br />
|mH=2<br />
|PS=2<br />
|Street=1}}<br />
| UT = {{Locking Standard <!-- Per Jemay, 2015-11-19. Temporary lowering from 54-4/3-3/2-2 to 4H322 per herrchin/AoTB/Bretmcvey 2016-06-01--><br />
|caption=Utah locking standard<br />
|title=Statewide<br />
|Fwy=4<br />
|Ramp=Highest rank of connected segments<br />
|MH=3<br />
|mH=2<br />
|PS=2<br />
|Street=1<br />
|lede=In {{RootPage2}} 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.<br />
}}<br />
| NV = {{Locking Standard <!-- As per State Forum discussions, SuperDave1426, 2015-01-28 --><br />
|title=Urban Areas<br />
|title2=Rural Areas<br />
|Fwy=5|Fwy2=4<br />
|Ramp=Highest Rank of Connected Segments<br />
|MH=3<br />
|mH=2<br />
|PS=2<br />
|Street=Automatic (1)<br />
|Private=Automatic (1)<br />
|PLR=Automatic (1)<br />
}}<br />
| CO = {{Locking Standard <!-- JoshJMM CO SM - 2017-09-16 --><br />
|Fwy=5|Ramp=Highest Rank of Connected Segment|MH=4|mH=3|PS=2|Street=1}}<br />
| NM <br />
| SOUTHWEST = {{Locking Standard <!-- per Jemay - 2015-11-25 --><br />
|Fwy=5|Ramp=4|MH=4|mH=3|PS=2|Street=1<br />
|lede=Actual locks used may be more or less than values in the table, depending on area circumstance. Please consult the RC, SM, or appropriate AM for guidance.<br />
}}<br />
| AZ = {{Locking Standard <!-- per SunDevil2213 - 2022-05-17 --><br />
|Fwy=5|Ramp=Highest rank of connected segments|MH=4|mH=3|PS=2|Street=1}}<br />
<br />
<br />
| MO = {{Locking Standard <!-- Confirmed by ehepner1977 - herrchin 20190716 --><br />
|title=Statewide|Fwy=4|Ramp=Highest rank of connected segments|MH=3|mH=3|PS=2|Street=1}}<br />
<br />
| KS = {{Locking Standard <!-- Confirmed by ehepner1977 - herrchin 20190716 --><br />
|title=Statewide|Fwy=4|Ramp=Highest rank of connected segments|MH=3|mH=3|PS=2|Street=1}}<br />
<br />
| MN = {{Locking Standard <!-- Confirmed by ehepner1977 - herrchin 20190716 --><br />
|title=Statewide|Fwy=4|Ramp=Highest rank of connected segments|MH=3|mH=3|PS=2|Street=1}}<br />
<br />
| IA = {{Locking Standard <!-- Confirmed by ehepner1977 - herrchin 20190716 --><br />
|title=Statewide|Fwy=4|Ramp=Highest rank of connected segments|MH=3|mH=3|PS=2|Street=1}}<br />
<br />
| NE = {{Locking Standard <!-- Confirmed by ehepner1977 - herrchin 20190716 --><br />
|title=Statewide|Fwy=4|Ramp=Highest rank of connected segments|MH=3|mH=3|PS=2|Street=1}}<br />
<br />
| WV = {{Locking Standard <!-- 2015-07-06, stephenr1966, as discussed within state --><br />
|caption=West Virginia Locking Rank Standard Guideline<br />
|Fwy=5|Ramp=4|MH=3|mH=2|PS=1<br />
|lede=Actual locks used may be more or less than values in the table below, depending on area circumstance<br />
Please consult the RC, SM, or appropriate AM for guidance<br />
}}<br />
| VA = {{Locking Standard<br />
|caption=Virginia Locking Rank Standard Guideline<br />
|title=Urban|Fwy=5|MH=4|mH=3|PS=2<br />
|title2=Rural|MH2=3|mH2=2|PS2=1<br />
|lede=Actual locks used may be more or less than values in the table below, depending on area circumstance<br />
Please consult the RC, SM, or appropriate AM for guidance<br />
}}<br />
| WASHDC = {{Locking Standard<br />
|caption=Washington, DC Locking Rank Standard Guideline<br />
|Fwy=5|MH=4|mH=3|PS=2<br />
|lede=Actual locks used may be more or less than values in the table below, depending on area circumstance<br />
Please consult the RC, SM, or appropriate AM for guidance<br />
}}<br />
| SOUTHERN = {{Locking Standard<br />
|caption=Standard for locking roads in the southeast region:<br />
|Fwy=5|Ramp=5|MH=5|mH=4|PS=3<br />
|lede=<br />
There are some cases that do not adhere to this standard, such as any theme park type areas in Orlando (5/6). Further, all gates at gated communities / private installation should be locked to at least 5.<br />
}}<br />
| PR<br />
| VI<br />
| AS<br />
| GUAM<br />
| NMI<br />
| TERRITORIES = {{Locking Standard|title=Statewide|Fwy=5|Ramp=4|MH=4|mH=3|PS=2|Street=1}}<!-- Per nnote, RC--><br />
| OK = {{Locking Standard|title=Statewide|Fwy=5|Ramp=4|MH=4|mH=3|PS=2|Street=1|Private=2}}<br />
| MD = {{Locking Standard <!-- a/p Kodi, nzahn1 SMs --><br />
|title=Urban<br />
|title2=Rural<br />
|Fwy=5|Fwy2=4<br />
|Ramp=5|Ramp2=4<br />
|MH=3|MH2=2<br />
|mH=2<br />
|PS=2<br />
}}<br />
| MIDATLANTIC = {{Locking Standard<br />
|title=Two-Way<br />
|Fwy=5<br />
|Ramp=4<br />
|MH=4<br />
|mH=3<br />
|PS=2<br />
|Street=1<br />
|title2=One-Way<br />
|PS2=3<br />
|Street2=2}}<br />
<br />
| IN<br />
| MI<br />
| OH<br />
| WI<br />
| GLR = <!--per discussion on Discord with GLR SMs and at https://www.waze.com/forum/viewtopic.php?f=943&t=272395-->{{Locking Standard|lede=The following defines a set of ''minimum'' locking standards proposed for all '''roads''' within {{RootPage2}}.<br />
Any road of a certain type or category must be locked at least to the level in the chart below. Roads may be locked higher for protection and special situations (tricky design, frequent mistakes, imaging inaccuracies, and the like), but should not be locked lower.<br />
<br />
It is understood that more rural or inactive areas may not yet meet this standard: editors are encouraged to recruit and mentor additional editors to build coverage. <br />
<br />
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 [[Road types#Quick_reference_chart|US Road Type Standards]].<br />
|caption={{RootPage2}} Minimum Road Locking Standard|title=Two-way|title2={{Spaces|1}}One-way{{Spaces|1}}|Fwy=5|Ramp=Highest lock of connected segment|mH=3|PS=2|PS2=3|Street=1|Street2=2|Private=1|Private2=2|PLR=1|PLR2=1<sup>see note</sup>|Ferry=5|Runway=5|Other=1|Other2=2|Construction=3|Beacon=6|note=One-way PLRs used outside of parking lots, such as alleys and streets through apartment complexes, should be locked at 2. See [[USA/Great Lakes/Major roads|the GLR major roads page]] for additional information on the standards listed here.}}<br />
| IL = <!--per discussion on Discord with Hawkeygoal and other GLR SMs and at https://www.waze.com/forum/viewtopic.php?f=943&t=272395-->{{Locking Standard|lede=The following defines a set of ''minimum'' locking standards proposed for all '''roads''' within {{RootPage2}}.<br />
Any road of a certain segment type must be locked at least to the 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.<br />
<br />
It is understood that more rural or inactive areas may not yet meet this standard: editors are encouraged to recruit and mentor additional editors to build state-wide coverage. <br />
<br />
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 [[Road types#Quick_reference_chart|US Road Type Standards]].<br />
|caption={{RootPage2}} Minimum Road Locking Standard|title={{Spaces|5}}Two-way{{Spaces|4}}|title2={{Spaces|5}}One-way{{Spaces|5}}|title3=Chicago Zone|Fwy=5|MH=3|mH=3|PS=2|PS2=3|PS3=3|Street=1|Street2=2|Street3=3|Private=1|Private2=2|Private3=2|PLR=1|PLR2=1<sup>see note</sup>|PLR3=2|Ferry=5|RR=2|Runway=5|Other=1|Other2=3|Other3=3|Construction=3|note=One-way PLRs used outside of parking lots, such as alleys and streets through apartment complexes, should be locked at 2. The ''Chicago Zone'' is bordered by Lake Michigan on the east, the Chicago River on the north and west and Polk on the south. See [[USA/Great Lakes/Major roads|the GLR major roads page]] for additional information on the standards listed here.}}<br />
| KY = {{Locking Standard<br />
|title=Statewide<br />
|Fwy=5|MH=4|mH=3|PS=2<br />
|note=These are minimums and, for protection, certain segments may be at higher lock levels. Locks should be applied after the segments are correct. Remember you are putting your name on it, make sure it is correct.}}<br />
| NC = {{Locking Standard<br />
|title=Statewide<br />
|Fwy=5|MH=4|mH=3|PS=2<br />
|note=Certain areas may be locked higher than the above minimums. Please do not lower locks unless approved by the RC or SM of {{RootPage2}}.}}<br />
| SC = {{Locking Standard<br />
|title=Statewide<br />
|Fwy=5|MH=4|mH=3|PS=2<br />
|note=Certain areas may be locked higher than the above minimums. Please do not lower locks unless approved by the RC or SM of {{RootPage2}}.}} <!-- a/p crazycaveman SC SM --><br />
| TN = {{Locking Standard<br />
|title=Statewide<br />
|Fwy=5|MH=4|mH=3|PS=2}}<br />
| ND = {{Locking Standard <!-- Confirmed by ehepner1977 - herrchin 20190716 --><br />
|title=Statewide|Fwy=4|Ramp=Highest rank of connected segments|MH=3|mH=3|PS=2|Street=1}}<br />
| SD = {{Locking Standard <!-- Confirmed by ehepner1977 - herrchin 20190716 --><br />
|title=Statewide|Fwy=4|Ramp=Highest rank of connected segments|MH=3|mH=3|PS=2|Street=1}}<br />
| WY = {{Locking Standard <!-- Approved by all NWR SMs and RC - TheChrisK, 2017-09-26 --><br />
|title=Statewide<br />
|Fwy=5<br />
|Ramp=5<br />
|MH=3<br />
|mH=3<br />
|PS=2<br />
|Street=1<br />
|note=Certain roads may be locked higher than the above minimums. Please do not lower locks unless approved by the RC or SM of {{RootPage2}}.}}<br />
| ID = {{Locking Standard <!-- Approved by all NWR SMs and RC - TheChrisK, 2017-09-26 --><br />
|title=Statewide<br />
|Fwy=5<br />
|Ramp=5<br />
|MH=3<br />
|mH=3<br />
|PS=2<br />
|Street=1<br />
|note=Certain roads may be locked higher than the above minimums. Please do not lower locks unless approved by the RC or SM of {{RootPage2}}.}}<br />
| MT = {{Locking Standard <!-- Approved by all NWR SMs and RC - TheChrisK, 2017-09-26 --><br />
|title=Statewide<br />
|Fwy=5<br />
|Ramp=5<br />
|MH=3<br />
|mH=3<br />
|PS=2<br />
|Street=1<br />
|note=Certain roads may be locked higher than the above minimums. Please do not lower locks unless approved by the RC or SM of {{RootPage2}}.}}<br />
| OR = {{Locking Standard <!-- Approved by all NWR SMs and RC - TheChrisK, 2017-09-26 --><br />
|title=Statewide<br />
|Fwy=5<br />
|Ramp=5<br />
|MH=3<br />
|mH=3<br />
|PS=2<br />
|Street=1<br />
|note=Certain roads may be locked higher than the above minimums. Please do not lower locks unless approved by the RC or SM of {{RootPage2}}.}}<br />
| WA = {{Locking Standard <!-- Approved by all NWR SMs and RC - TheChrisK, 2017-09-26 --><br />
|title=Statewide<br />
|Fwy=5<br />
|Ramp=5<br />
|MH=3<br />
|mH=3<br />
|PS=2<br />
|Street=1<br />
|note=Certain roads may be locked higher than the above minimums. Please do not lower locks unless approved by the RC or SM of {{RootPage2}}.}}<br />
| AK = {{Locking Standard <!-- Approved by all NWR SMs and RC - TheChrisK, 2017-09-26 --><br />
|title=Statewide<br />
|Fwy=5<br />
|Ramp=5<br />
|MH=3<br />
|mH=3<br />
|PS=2<br />
|Street=1<br />
|note=Certain roads may be locked higher than the above minimums. Please do not lower locks unless approved by the RC or SM of {{RootPage2}}.}}<br />
|lede=In {{RootPage2}} we have a set minimum standard for [[Best_map_editing_practice#Locking_Segments|locking roads]] based on the segment type. Any road of a certain segment type must be locked to '''at least''' the [[Your_Rank_and_Points#Map_Editing_Rank|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.<br />
<br />
A great time to implement these locks is while performing the [[Functional_Classification|FC Upgrade]] of an area. Lock the roads based on the type after they've been set to [[Road_types#Quick_reference_chart|FC standards]].<!--A/p wiki--><br />
| = {{Mbox|type=critical|text={{Red|Error: The Lock Standard State template requires a state/province abbreviation or other equivalent; none was supplied, so no locking scheme can be generated}}}}<br />
| {{Mbox|type=critical|text={{Red|The Lock Standard State template cannot display the locking scheme because it does not recognize the state/province/region specified: {{{1|}}}{{{st|}}}{{{ST|}}}{{{St|}}}{{{sT|}}}}}}}<br />
}}</includeonly></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Abc1357/LG&diff=176279User:Abc1357/LG2022-07-05T16:33:14Z<p>Tonestertm: /* Lanes */</p>
<hr />
<div>=='''<big>Lanes</big>'''==<br />
''General details on Lanes and how to map them can be found on the [[Lanes|Lanes Wazeopedia page]]. Editors should consider using the [https://www.waze.com/forum/viewtopic.php?f=819&t=301158 Lane Tools script] to assist in mapping lanes correctly.''<br />
<br />
In California, we use a "common sense" approach to guidance, thus deviating slightly from national guidance. Lanes should be mapped for major intersections where the number of turn lanes deviates from what is expected. In other words, do not map Lane Guidance if you can turn right only from the far right lane and/or you can turn left only from the far left lane (as specified by California law), regardless of whether these lanes are dedicated turn lanes or shared lanes. This results in "common sense" guidance, reducing unnecessary voice prompts from the app for trivial instructions. Most of the time, the user is only prompted with lane guidance when something unusual or complex is approaching, requiring heightened attention, and guidance prompts retain their value instead of becoming part of the background noise. <br />
<br />
'''Intersections where you should map Lanes*:'''<br />
<br />
*Intersections that have two or more lanes to turn left or right.<br />
*Complex intersections where [[usa:Lanes#To_clarify_which_road_to_take|clarification of which road to take is necessary]]<br />
<br />
*In a # or H junction where there is a U-Turn, even if there is only a single left turn lane. The addition of Lanes to these intersections combined with lane heuristics enables Waze to announce a ''<code>U-Turn</code>,'' rather than a ''<code>Turn Left, Turn Left</code>''.<br />
**Verify that the first and third segments are almost parallel (i.e. sum of angles with the cross segment should be between 175° and 185°), and the angle with the cross segment should be close to 90°.<br />
**Check that there is not a parallel segment within 50m (165 ft) to the left of the segment with a single perpendicular segment connecting them. Waze heuristics could interpret that to be a U-Turn. Use a Junction Node to "break up" the median segment, and add a map comment close by to indicate why the junction is there. ''Put in a picture of Clarie Drive in Pleasant Hill'' https://www.waze.com/en-US/editor/?env=usa&lon=-122.05663&lat=37.94113&zoom=8&segments=522544024,522544023<br />
*Use the <code>[[usa:Lanes#.22View_and_hear.22_continue_straight|View and Hear]]</code> or <code>[[usa:Lanes#.22View_only.22_continue_straight|View Only]]</code> continue straight overrides where necessary<br />
<br />
<br />''* Before mapping Lanes at any intersection, review prior intersections to ensure adding Lanes at that intersection do not inadvertently cause confusion for the driver (see '''Compound Guidance needed''' section below).''<br />
<br />
<br /><br />
==='''Special Considerations'''===<br />
<br /><br />
<br />
====''At-Grade Connectors''====<br />
When reviewing intersections prior to adding Lanes, please consider whether AGCs are still needed at that intersection.<br />
<br />
For example, the AGC from westbound Walsh Avenue to northbound San Tomas Expressway is not needed. The island is extremely small. The benefits that the AGC was originally meant for, such as advanced announcement of the turn, are not needed.<blockquote>''Picture here (not uploaded to Wazeopedia yet): [https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=]''[https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing sharing]</blockquote>'''What should be done in this situation?'''<br />
<br />
*Remove the AGC and any excess Junction Nodes<br />
*Adjust Turn Restrictions as necessary to compensate for the removed AGC<br />
*Add Lanes, if needed<br />
<br />
<br /><br />
<br />
====''Compound Guidance needed''====<br />
Compound guidance is the concept whereby a driver should be directed to a specific lane or set of lanes at a prior intersection to ensure that the driver is in position to perform the subsequent turn maneuver. Unfortunately, Waze does not yet support compound guidance.<br />
<br />
''Note that some of the following is expected to change with upcoming enhancements to the WME. Check back here if and when those changes occur.''<br />
<br />
'''Lane specific guidance'''<br />
<br />
There are intersections where users should be guided to the proper lane in preparation for the next maneuver.<br />
<br />
Consider a driver going from Crow Canyon Place to I-680 North. There are 2 left turn lanes on Crow Canyon Place. An editor following lane mapping guidance would map that intersection with 2 left turns. A driver unfamiliar with that area could potentially be using the left lane of the 2 left turn lanes to turn into the left lanes on Crow Canyon Road and not be able to enter the on-ramp to I-680 North, if there is a lot of traffic blocking the movement to the right lanes in the short distance available.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1fyevKStP0wqiyM5XalC46GimBkR4PB5b/view?usp=sharing'' </blockquote> <br />
<br />
In order to properly guide the driver, some sort of compound guidance such as ''<code>Use the right of the two left turn lanes to turn left and then turn right to I-680 North Sacramento</code>'' would be ideal. <br />
<br />
'''Loss and re-gain of lane between 2 intersections'''<br />
<br />
There are intersections where a lane is lost to a dedicated turn lane, and yet, by the next intersection, a lane is re-added. A driver following the lane guidance could mistakenly enter the dedicated turn lane prematurely and may be forced to take the earlier turn. <br />
<br />
Consider a driver on [https://www.waze.com/en-US/editor/?env=usa&lon=-121.92340&lat=37.49481&zoom=6 Mission Boulevard being guided to northbound I-680]. There are 3 full lanes at the on-ramp to northbound I-680 with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1WAUh2UMG3NKWgAawNvt-ELKaMko5va6p/view?usp=sharing'' </blockquote>At the prior on-ramp to southbound I-680, there are also 3 full lanes at the on-ramp with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1pKWKjd59aFBNb4ROoViban5_5pPWkgSu/view?usp=sharing'' </blockquote>Note that since Lane Guidance is announced about ½ mile prior to the turn instruction on MH roadways (and ¼ mile for mH and lower), the driver would hear ''<code>In ½ mile, use the right lane to turn right to I-680 North toward Sacramento</code>'' at around Warm Springs Boulevard, which is 2 signaled intersections prior to the entrance to northbound I-680. There is no signage that the right lane ends until you are almost at the entrance to southbound I-680. A driver unfamiliar with the area, upon seeing or hearing the guidance, would get into the right lane. By the time the driver realizes that the lane is a dedicated lane to I-680 South, not North, there isn't much distance left to change lanes, especially when there is a lot of traffic in the next lane.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1uAPd_q-O7VRhYnAtGuvskjHI1Uf3qcqr/view?usp=sharing''</blockquote>In order to properly guide the driver, there are a few possibilities. Waze could delay announcing the Turn instruction to northbound I-680 until the driver is past the entrance to southbound I-680. A more ideal solution would be for Waze to announce ''<code>In ½ mile, stay in the middle lane and then turn right to I-680 North Sacramento</code>''. '''Note from tm - this final paragraph could be confusing and I'd like to consider removing it.''' <br />
<br />
'''What should be done in these situations?'''<br />
<br />
*Lanes should not be mapped at such intersections<br />
*Place a Map Comment so that future editors can locate these locations if Waze enhances the Lane Guidance feature to make mapping these locations possible. Adding a Map Comment could be used as a notification to current editors that the intersection has been reviewed and Lane Guidance should not be added until such time these enhancements are available.<br />
<br />
<br /></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=Nevada/Major_roads/Main&diff=176237Nevada/Major roads/Main2022-06-25T22:13:30Z<p>Tonestertm: /*Major_roads/Main*/</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
<br />
While there has been a little bit of confusion regarding the road types based on common sense. If you read the wiki, Nevada uses the DOT guidelines for the purpose of navigation routing and not based on the given name of the road. Nevada has a lot of graded gravel roads which are technically considered primary roads within WME. Before changing a road type to anything less than that which is assigned in the Nevada Department of Transportation (NDOT) functional classification check with an Area Manager, State Manager, Regional Coordinator, or Country Manager within the Nevada Forum.<br />
<br />
=== Local naming variations ===<br />
{{RootPage2}} uses '''NV-##''', and '''NV-##X''' for all state routes and their spurs, loops, etc. (e.g. '''NV-89''', '''NV-17M'''). When working on an area, if you encounter a road with the old '''SR-##''' naming, please take the time to change that name to reflect the '''NV-##''' name. This includes alternate names, if you notice them.<br />
<br />
It should be noted that while we use the '''NV-xxx''' road designation for better clarity for drivers using Waze, NDOT does not use it. When you are verifying a state route/highway number against an official source, you'll see "SR-89" instead of "NV-89", for example. This is ok, don't let that cause you concern. Just go ahead and use the NV-xxx designation (using the official route/highway ''number'') when setting/correcting a state route number.<br />
<br />
=== Functional Classifications ===<br />
{{RootPage2}} is following the [[National_resources/USA/Functional_classification|Functional Classification]] (FC) system for the USA.<br />
<br />
The following resource can help to determine the FC for some of the roads in Nevada:<br />
* [https://www.nevadadot.com/travel-info/maps/functional-classification-maps Nevada Functional Class Graphical Maps]<br />
**<span style="color:green">For historical purposes only</span> you can [http://web.archive.org/web/20140703042811/http://nevadadot.com/About_NDOT/NDOT_Divisions/Planning/Roadway_Systems/FCMGS.aspx Click here for archive version] as of July 3, 2014. Do not use this as a reference for setting FC on roads in WME.<br />
<br />
=== Lock Levels ===<br />
{{Lock Standard State|NV}}<br />
'''NOTE:''' Streets directly involved in the Las Vegas Strip area should be minimum locked at one rank (level) higher than the above minimums, to protect that vital traffic corridor.<br />
<br />
''Please note that the above lock levels are subject to change, should situations warrant. Be sure to check here for current lock level criteria if unsure.''<br />
<br />
=== U-turns ===<br />
This is interim guidance for Nevada, until such time as National standards are agreed upon.<br />
<br />
U-turns on *two-way* Primary Street through Major Highway type roads may be enabled in either of the following two circumstances: <br />
# The U-turn is _explicitly_ allowed by signage; or<br />
# The U-turn is otherwise legal and safe, and there is ''at least'' 10.1 m (33 feet) from the left edge of the departure lane to the "destination" curb. This can include any median that may exist to the left of the departure lane. (The measurement is intended to accommodate the turning radius of most passenger vehicles.)<br />
<br />
It should be noted that in Nevada per the NRS, U-Turns are legal where safe and not expressly prohibited by a sign indicating "NO U-Turn" (or the typical U-Turn arrow with a red circle and slash over it). Even if there is a sign at a signal which shows a left turn arrow and the word "ONLY" under it, as long as there is not ''also'' a sign indicating no U-Turn permitted, then it is allowed as long as it is safe. See #2 above regarding minimum size to be considered.<br />
<br />
'''NOTE:''' During various times of the day in a school zone, U-Turns are prohibited by Nevada law, even if there isn't a sign present. Other than the standard "half hour before schools starts operation" until "half hour after school completes operation," there's also a stipulation of "when children are present" that doesn't mention anything about during school hours. It could possibly be interpreted as meaning even on a weekend/holiday if there are children walking along the street, so it's best to simply not mark a U-Turn possibility as enabled inside of a school zone area.<br />
<br />
Do NOT make a point of enabling all U-turns valid under this guidance, only as you encounter them and they are necessary. Do not enable U-turns on Street type roads.<br />
<br />
Parking Lot Road (PLR) types are a special case - to further help with navigation for cars leaving a parking lot, the ends of PLR segments should have U-Turns enabled at both ends in most cases where the parking is ''straight in'' going both ways. If the actual parking spaces are at a diagonal to the actual lane, do not enable U-Turns. Don't turn this into a big project, but if you're working on PLRs in a given parking lot anyway, following these guidelines will help move things in that direction since someone won't have to go back and add U-Turns later.<br />
<br />
This guidance could change in the future. <br />
<br />
=== At-Grade Connectors (AGCs) ===<br />
{{RootPage2}} is following the [https://wazeopedia.waze.com/wiki/USA/At-grade_connectors AGC] guidelines for the USA. The following information is provided here for further clarification as to how right turns are handled when an AGC is present:<br />
<br />
# As a general rule, we do not mark a right turn at an intersection green if there is an AGC ahead of it that provides for the right turn; the turn to the AGC is marked green and the turn at the intersection is marked red, even if there is no sign or other indication that the turn is prohibited.<br />
# In certain situations, it might be allowed to do both; most commonly, if there is an actual dedicated right-turn lane at the intersection (with markings on the road or signage designating it as a right-turn lane), we will mark that with a green arrow in addition to the green arrow at the AGC on the approach to it.<br />
<br />
If unsure, please check with the state manager or regional coordinator ''before'' setting/changing turn permission at the intersection.<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Major_roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Major roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=At-grade_connectors&diff=176236At-grade connectors2022-06-25T21:52:15Z<p>Tonestertm: /* {{anchor|Turn restrictions necessary for proper connector routing}} Turn restrictions */</p>
<hr />
<div>{{UpdateImage}}<br />
<br />
When traffic moves between two roads that are at the same [[Glossary#Grade|grade]], these connecting segments are not technically [[Road types#Ramps|ramps]] to Waze (unless it falls into one of the [[#Exceptions|Exceptions]] listed below). How to handle these connectors depends on the exact situation.<br />
<br />
== Should the connector be mapped? ==<br />
<br />
First and foremost, the need to have the connector mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes.<br />
<br />
An at-grade connector should generally only be mapped with a separate segment '''where the turn lane physically separates from the main road well in advance of the intersection''', ''i.e.'', where the point of divergence (the "theoretical gore") is more than a couple car lengths before the stop line of the main lanes of traffic.<br />
<br />
Consider the addition or removal of at-grade connectors carefully. Connectors can bring the map closer to reality, but they can also add to your workload when the time comes to check connectivity, direction, name, etc., and make it impossible for heuristics to work on [[lanes]] at # or H intersections.<br />
<br />
== {{anchor|How to label the connector type}} Road type ==<br />
<br />
[[File:AGC_2018_00001.png|right|border]]Although sometimes referred to as ramps, to Waze these are '''not''' ramps. The Ramp road type in Waze should only be used for situations where two roadways have a grade separated intersection or if the situation matches one of the [[#Exceptions|Exceptions]] listed below.<br />
<br />
The connector segment's type should be set based on the '''lowest''' of the types of roads it connects, as in the following examples:<br />
<br />
*Street to Minor Highway should be Street type.<br />
*Minor Highway to Primary Street should be Primary Street type.<br />
*Primary Street to Primary Street should be Primary Street type.<br />
<br />
In the example image on the right, note how the top-left quadrant of the intersection does not have a connector mapped because it does not meet the requirement of being significantly separated from the main intersection.<br />
{{clear}}<br />
<br />
== {{anchor|How to name the connector}} Road name ==<br />
<br />
In most cases, checking None for the Street name will be sufficient. Navigation instructions will simply use the name of the next segment to which the connector segment connects.<br />
<br />
If there are specific signs at the intersection which are confusing or contrary to the destination road segment name, then a name can be applied to the connector.<br />
<br />
== {{anchor|Geometry of the connector}} {{anchor|Geometry}} Geometry and turn instructions ==<br />
<br />
=== Turn replacement AGCs ===<br />
<br />
The "typical" at-grade connector takes the place of a normal turn instruction at an intersection, giving the same turn instruction at the point when the driver enters the AGC, and giving no instruction as the driver exits the AGC. In the typical turn replacement AGC, the turning motion made by the driver is more or less consistent throughout the AGC, beginning at the gore point.<br />
<br />
Turn replacement AGCs should be mapped starting at the '''gore point''' that separates the AGC from the main lanes of traffic.<br />
<br />
<gallery><br />
File:Turnreplace1.png|Typical turn replacement AGC<br />
File:Turnreplace2.jpg|Turn replacement AGCs start at the gore, not at the solid white line<br />
File:Turnreplace3.jpg|Typical turn replacement AGCs<br />
File:Turnreplace4.jpg|Turn replacement AGCs start at the gore, not at the solid white line<br />
</gallery><br />
<br />
=== Long lead AGCs ===<br />
<br />
On some AGCs, the actual turning motion starts well ''after'' the gore. After entering the AGC, the driver's path is more or less straight for some time before the motion of the turn itself begins.<br />
<br />
Like turn replacement AGCs, long lead AGCs should be mapped starting at the '''gore point''' that separates the AGC from the main lanes of traffic.<br />
<br />
To better represent the actual motions involved, long lead AGCs should be configured with an instruction to "keep right" or "keep left" onto the AGC and, where needed, a second instruction (often "turn right" or "turn left") given as the driver exits the AGC.<br />
<br />
<gallery><br />
File:Longlead1.jpg|The painted gore separates the AGC from traffic well before the left turn motion begins<br />
File:Longlead2.jpg|The raised grassy area separates the AGC from traffic well before the left turn motion begins<br />
File:Longlead3.jpg|The painted gore creates an AGC which is in many ways similar to a freeway exit ramp<br />
</gallery><br />
<br />
The long-lead AGC configuration provides an additional benefit for left turn lanes where U turns are allowed by allowing the 2nd instruction in the two-instruction set to be "make a U turn" on the U turn path.<br />
<br />
== {{anchor|Turn restrictions necessary for proper connector routing}} Turn restrictions ==<br />
<br />
[[File:AGC_2018_00002.png|right|border]]Connectors, if simply added to the map and all turns were allowed, would cause significant routing challenges, especially between two 2-way roads. Divided roadways have their own challenges, but turn restrictions, due to the 1-way nature of the main segments, are simpler.<br />
<br />
In the US, a simple right-turn connector between two 2-way streets, requires that the right turn be restricted at both the primary intersection, and at the connector itself so Waze will not be allowed to tell the driver to turn left across the road to get onto the connector.<br />
<br />
{{clear}}<br />
<br />
[[File:AGC_2018_00003.png|left|border]]<br />
AND, at the end of the connector, the left turn must be restricted:<br />
{{clear}}<br />
<br />
[[File:AGC_2018_00004.png|right|border]]If you enable the "show all restricted connectivity arrows" function in the editor at this intersection, you can see there are many restricted turns. This is sometimes a target for someone looking to remove all restricted turns by abusing the use of the 'w' or '''Allow All''' turns function.<br />
{{clear}}<br />
<br />
== Speed Limit ==<br />
[[Speed limits#At_grade_connectors|At-Grade Connector speed limit instructions]]<br />
<br />
== Exceptions ==<br />
{{construction<br />
| contact = http://www.waze.com/forum/viewtopic.php?f=276&t=86666<br />
| contacttype = forum<br />
| draft = yes<br />
| open = no<br />
| revision = yes<br />
| section = yes<br />
| talk = no<br />
}}<br />
<br />
=== Median U turn intersection (MUTI) ===<br />
<br />
[[File:AGC_MUTI_2018_01a.png|250px|thumbnail|right]]The median crossing segments in a [http://www.fhwa.dot.gov/publications/research/safety/09057/ median U turn (aka "Michigan left") intersection] should be set to the {{Ramp}} type.{{clear}}<br />
<br />
=== Restricted crossing U turn (RCUT) intersection ===<br />
<br />
[[File:AGC_MUTI_2018_02.png|250px|thumbnail|right]]The median crossing segments in a [http://www.fhwa.dot.gov/publications/research/safety/09059/ restricted crossing U turn (aka "J turn" or "Superstreet") intersection] should be set to the {{Ramp}} type.{{clear}}<br />
<br />
=== Displaced left turn (DLT) intersection ===<br />
<br />
[[File:DLT.png|250px|thumbnail|right]]The crossover left turn lanes and the resultant elongated right turn lanes in a [http://www.fhwa.dot.gov/publications/research/safety/09055/ displaced left turn (or "continuous flow") intersection] should be set to the {{Ramp}} type.{{clear}}<br />
<br />
=== Jughandle ===<br />
<br />
[[File:AGC_Jug_2018.png|250px|thumbnail|right]][http://www.fhwa.dot.gov/publications/research/safety/07032/ Jughandle] segments should be set to the {{Ramp}} type.<br><br>For New Jersey, refer to their wiki on [[New_Jersey#Jughandles|Jughandles]].{{clear}}<br />
<br />
=== Signed, numbered exit ===<br />
[[File:GSP_10.jpg|right|border]]<br />
'''Example:''' Garden State Parkway Exit 10 in Cape May Court House, New Jersey, USA.<br />
<br />
The Garden State Parkway is mostly a freeway class toll-road that runs north/south through New Jersey. As the Parkway approaches its southern terminus, the number of lanes is reduced, and at-grade intersections with signed, numbered exits are interspersed with controlled access sections using grade-separated ramps.<br />
<br />
In order to produce an [[Junction_Style_Guide#Controlling_Turn_Instructions|instruction to Exit Right]] for the at-grade intersections, rather than Keep Right or Turn Right, we must use a junction angle of less than 45 degrees and a connector segment of a road type other than Freeway or Highway. Ramp type is ideal for this application because it does not display road names in the app. Segments for numbered exits are named to produce specific visual and TTS instructions, rather than by standard rules for at-grade connectors, and it would be inappropriate to display such names on the map.<br />
{{clear}}<br />
<br />
{|style="margin: 0 auto;"<br />
|- valign="top"<br />
| [[File:GSP_10A.jpg|x162px]]<br />
| [[File:GSP_10B.jpg|x162px]]<br />
| Going north, the right turn lane is signed as Exit 10B and the left turn lane is signed as Exit 10A (and reversed going south).<br />
|}<br />
<br />
<br />
[[Category:Style Guide]]<br />
[[Category:Update what links here]]</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=At-grade_connectors&diff=176235At-grade connectors2022-06-25T21:46:50Z<p>Tonestertm: /* {{anchor|How to label the connector type}} Road type */ cleanup syntax</p>
<hr />
<div>{{UpdateImage}}<br />
<br />
When traffic moves between two roads that are at the same [[Glossary#Grade|grade]], these connecting segments are not technically [[Road types#Ramps|ramps]] to Waze (unless it falls into one of the [[#Exceptions|Exceptions]] listed below). How to handle these connectors depends on the exact situation.<br />
<br />
== Should the connector be mapped? ==<br />
<br />
First and foremost, the need to have the connector mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes.<br />
<br />
An at-grade connector should generally only be mapped with a separate segment '''where the turn lane physically separates from the main road well in advance of the intersection''', ''i.e.'', where the point of divergence (the "theoretical gore") is more than a couple car lengths before the stop line of the main lanes of traffic.<br />
<br />
Consider the addition or removal of at-grade connectors carefully. Connectors can bring the map closer to reality, but they can also add to your workload when the time comes to check connectivity, direction, name, etc., and make it impossible for heuristics to work on [[lanes]] at # or H intersections.<br />
<br />
== {{anchor|How to label the connector type}} Road type ==<br />
<br />
[[File:AGC_2018_00001.png|right|border]]Although sometimes referred to as ramps, to Waze these are '''not''' ramps. The Ramp road type in Waze should only be used for situations where two roadways have a grade separated intersection or if the situation matches one of the [[#Exceptions|Exceptions]] listed below.<br />
<br />
The connector segment's type should be set based on the '''lowest''' of the types of roads it connects, as in the following examples:<br />
<br />
*Street to Minor Highway should be Street type.<br />
*Minor Highway to Primary Street should be Primary Street type.<br />
*Primary Street to Primary Street should be Primary Street type.<br />
<br />
In the example image on the right, note how the top-left quadrant of the intersection does not have a connector mapped because it does not meet the requirement of being significantly separated from the main intersection.<br />
{{clear}}<br />
<br />
== {{anchor|How to name the connector}} Road name ==<br />
<br />
In most cases, checking None for the Street name will be sufficient. Navigation instructions will simply use the name of the next segment to which the connector segment connects.<br />
<br />
If there are specific signs at the intersection which are confusing or contrary to the destination road segment name, then a name can be applied to the connector.<br />
<br />
== {{anchor|Geometry of the connector}} {{anchor|Geometry}} Geometry and turn instructions ==<br />
<br />
=== Turn replacement AGCs ===<br />
<br />
The "typical" at-grade connector takes the place of a normal turn instruction at an intersection, giving the same turn instruction at the point when the driver enters the AGC, and giving no instruction as the driver exits the AGC. In the typical turn replacement AGC, the turning motion made by the driver is more or less consistent throughout the AGC, beginning at the gore point.<br />
<br />
Turn replacement AGCs should be mapped starting at the '''gore point''' that separates the AGC from the main lanes of traffic.<br />
<br />
<gallery><br />
File:Turnreplace1.png|Typical turn replacement AGC<br />
File:Turnreplace2.jpg|Turn replacement AGCs start at the gore, not at the solid white line<br />
File:Turnreplace3.jpg|Typical turn replacement AGCs<br />
File:Turnreplace4.jpg|Turn replacement AGCs start at the gore, not at the solid white line<br />
</gallery><br />
<br />
=== Long lead AGCs ===<br />
<br />
On some AGCs, the actual turning motion starts well ''after'' the gore. After entering the AGC, the driver's path is more or less straight for some time before the motion of the turn itself begins.<br />
<br />
Like turn replacement AGCs, long lead AGCs should be mapped starting at the '''gore point''' that separates the AGC from the main lanes of traffic.<br />
<br />
To better represent the actual motions involved, long lead AGCs should be configured with an instruction to "keep right" or "keep left" onto the AGC and, where needed, a second instruction (often "turn right" or "turn left") given as the driver exits the AGC.<br />
<br />
<gallery><br />
File:Longlead1.jpg|The painted gore separates the AGC from traffic well before the left turn motion begins<br />
File:Longlead2.jpg|The raised grassy area separates the AGC from traffic well before the left turn motion begins<br />
File:Longlead3.jpg|The painted gore creates an AGC which is in many ways similar to a freeway exit ramp<br />
</gallery><br />
<br />
The long-lead AGC configuration provides an additional benefit for left turn lanes where U turns are allowed by allowing the 2nd instruction in the two-instruction set to be "make a U turn" on the U turn path.<br />
<br />
== {{anchor|Turn restrictions necessary for proper connector routing}} Turn restrictions ==<br />
<br />
[[File:AGC_2018_00002.png|right|border]]Connectors, if simply added to the map and all turns allowed, would cause significant routing challenges, especially between two 2-way roads. Split roadways have their own challenges, but turn restrictions, due to the 1-way nature of the main segments, are simpler.<br />
<br />
In the US, a simple right-turn connector between two 2-way streets, requires that the right turn be restricted at both the primary intersection, and at the connector itself so Waze will not be allowed to tell the driver to turn left across the road to get onto the connector.<br />
<br />
{{clear}}<br />
<br />
[[File:AGC_2018_00003.png|left|border]]<br />
AND, at the end of the connector, the left turn must be restricted:<br />
{{clear}}<br />
<br />
[[File:AGC_2018_00004.png|right|border]]If you enable the "show all restricted connectivity arrows" function in the editor at this intersection, you can see there are many restricted turns. This is sometimes a target for someone looking to remove all restricted turns by abusing the use of the 'w' or '''Allow All''' turns function.<br />
{{clear}}<br />
<br />
== Speed Limit ==<br />
[[Speed limits#At_grade_connectors|At-Grade Connector speed limit instructions]]<br />
<br />
== Exceptions ==<br />
{{construction<br />
| contact = http://www.waze.com/forum/viewtopic.php?f=276&t=86666<br />
| contacttype = forum<br />
| draft = yes<br />
| open = no<br />
| revision = yes<br />
| section = yes<br />
| talk = no<br />
}}<br />
<br />
=== Median U turn intersection (MUTI) ===<br />
<br />
[[File:AGC_MUTI_2018_01a.png|250px|thumbnail|right]]The median crossing segments in a [http://www.fhwa.dot.gov/publications/research/safety/09057/ median U turn (aka "Michigan left") intersection] should be set to the {{Ramp}} type.{{clear}}<br />
<br />
=== Restricted crossing U turn (RCUT) intersection ===<br />
<br />
[[File:AGC_MUTI_2018_02.png|250px|thumbnail|right]]The median crossing segments in a [http://www.fhwa.dot.gov/publications/research/safety/09059/ restricted crossing U turn (aka "J turn" or "Superstreet") intersection] should be set to the {{Ramp}} type.{{clear}}<br />
<br />
=== Displaced left turn (DLT) intersection ===<br />
<br />
[[File:DLT.png|250px|thumbnail|right]]The crossover left turn lanes and the resultant elongated right turn lanes in a [http://www.fhwa.dot.gov/publications/research/safety/09055/ displaced left turn (or "continuous flow") intersection] should be set to the {{Ramp}} type.{{clear}}<br />
<br />
=== Jughandle ===<br />
<br />
[[File:AGC_Jug_2018.png|250px|thumbnail|right]][http://www.fhwa.dot.gov/publications/research/safety/07032/ Jughandle] segments should be set to the {{Ramp}} type.<br><br>For New Jersey, refer to their wiki on [[New_Jersey#Jughandles|Jughandles]].{{clear}}<br />
<br />
=== Signed, numbered exit ===<br />
[[File:GSP_10.jpg|right|border]]<br />
'''Example:''' Garden State Parkway Exit 10 in Cape May Court House, New Jersey, USA.<br />
<br />
The Garden State Parkway is mostly a freeway class toll-road that runs north/south through New Jersey. As the Parkway approaches its southern terminus, the number of lanes is reduced, and at-grade intersections with signed, numbered exits are interspersed with controlled access sections using grade-separated ramps.<br />
<br />
In order to produce an [[Junction_Style_Guide#Controlling_Turn_Instructions|instruction to Exit Right]] for the at-grade intersections, rather than Keep Right or Turn Right, we must use a junction angle of less than 45 degrees and a connector segment of a road type other than Freeway or Highway. Ramp type is ideal for this application because it does not display road names in the app. Segments for numbered exits are named to produce specific visual and TTS instructions, rather than by standard rules for at-grade connectors, and it would be inappropriate to display such names on the map.<br />
{{clear}}<br />
<br />
{|style="margin: 0 auto;"<br />
|- valign="top"<br />
| [[File:GSP_10A.jpg|x162px]]<br />
| [[File:GSP_10B.jpg|x162px]]<br />
| Going north, the right turn lane is signed as Exit 10B and the left turn lane is signed as Exit 10A (and reversed going south).<br />
|}<br />
<br />
<br />
[[Category:Style Guide]]<br />
[[Category:Update what links here]]</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=At-grade_connectors&diff=176234At-grade connectors2022-06-25T21:43:01Z<p>Tonestertm: /* {{anchor|How to label the connector type}} Road type */</p>
<hr />
<div>{{UpdateImage}}<br />
<br />
When traffic moves between two roads that are at the same [[Glossary#Grade|grade]], these connecting segments are not technically [[Road types#Ramps|ramps]] to Waze (unless it falls into one of the [[#Exceptions|Exceptions]] listed below). How to handle these connectors depends on the exact situation.<br />
<br />
== Should the connector be mapped? ==<br />
<br />
First and foremost, the need to have the connector mapped needs to be established. As the driver approaches an intersection, Waze has usually given at least one warning that a turn is imminent, and we can assume that the driver is already looking for turn lanes. For most intersections, that is enough to guide the driver into the proper lane and to turn at the proper time; in other words, it is enough that the two roads intersect without separately mapped turning lanes.<br />
<br />
An at-grade connector should generally only be mapped with a separate segment '''where the turn lane physically separates from the main road well in advance of the intersection''', ''i.e.'', where the point of divergence (the "theoretical gore") is more than a couple car lengths before the stop line of the main lanes of traffic.<br />
<br />
Consider the addition or removal of at-grade connectors carefully. Connectors can bring the map closer to reality, but they can also add to your workload when the time comes to check connectivity, direction, name, etc., and make it impossible for heuristics to work on [[lanes]] at # or H intersections.<br />
<br />
== {{anchor|How to label the connector type}} Road type ==<br />
<br />
[[File:AGC_2018_00001.png|right|border]]Although sometimes referred to as ramps, to Waze these are '''not''' ramps. The Ramp road type in Waze should only be used for situations where two roadways have a grade separated intersection or if the situation matches one of the [[#Exceptions|Exceptions]] listed below.<br />
<br />
The connector segment's type should be set based on the '''lowest''' of the types of roads it connects.<br />
<br />
*Ex: Street to Minor Highway should be Street type.<br />
*Ex: Minor Highway to Primary Street should be Primary Street type.<br />
*Ex: Primary Street to Primary Street should be Primary Street type.<br />
<br />
In the example image on the right, note how the top-left quadrant of the intersection does not have a connector mapped because it does not meet the requirement of being significantly separated from the main intersection.<br />
{{clear}}<br />
<br />
== {{anchor|How to name the connector}} Road name ==<br />
<br />
In most cases, checking None for the Street name will be sufficient. Navigation instructions will simply use the name of the next segment to which the connector segment connects.<br />
<br />
If there are specific signs at the intersection which are confusing or contrary to the destination road segment name, then a name can be applied to the connector.<br />
<br />
== {{anchor|Geometry of the connector}} {{anchor|Geometry}} Geometry and turn instructions ==<br />
<br />
=== Turn replacement AGCs ===<br />
<br />
The "typical" at-grade connector takes the place of a normal turn instruction at an intersection, giving the same turn instruction at the point when the driver enters the AGC, and giving no instruction as the driver exits the AGC. In the typical turn replacement AGC, the turning motion made by the driver is more or less consistent throughout the AGC, beginning at the gore point.<br />
<br />
Turn replacement AGCs should be mapped starting at the '''gore point''' that separates the AGC from the main lanes of traffic.<br />
<br />
<gallery><br />
File:Turnreplace1.png|Typical turn replacement AGC<br />
File:Turnreplace2.jpg|Turn replacement AGCs start at the gore, not at the solid white line<br />
File:Turnreplace3.jpg|Typical turn replacement AGCs<br />
File:Turnreplace4.jpg|Turn replacement AGCs start at the gore, not at the solid white line<br />
</gallery><br />
<br />
=== Long lead AGCs ===<br />
<br />
On some AGCs, the actual turning motion starts well ''after'' the gore. After entering the AGC, the driver's path is more or less straight for some time before the motion of the turn itself begins.<br />
<br />
Like turn replacement AGCs, long lead AGCs should be mapped starting at the '''gore point''' that separates the AGC from the main lanes of traffic.<br />
<br />
To better represent the actual motions involved, long lead AGCs should be configured with an instruction to "keep right" or "keep left" onto the AGC and, where needed, a second instruction (often "turn right" or "turn left") given as the driver exits the AGC.<br />
<br />
<gallery><br />
File:Longlead1.jpg|The painted gore separates the AGC from traffic well before the left turn motion begins<br />
File:Longlead2.jpg|The raised grassy area separates the AGC from traffic well before the left turn motion begins<br />
File:Longlead3.jpg|The painted gore creates an AGC which is in many ways similar to a freeway exit ramp<br />
</gallery><br />
<br />
The long-lead AGC configuration provides an additional benefit for left turn lanes where U turns are allowed by allowing the 2nd instruction in the two-instruction set to be "make a U turn" on the U turn path.<br />
<br />
== {{anchor|Turn restrictions necessary for proper connector routing}} Turn restrictions ==<br />
<br />
[[File:AGC_2018_00002.png|right|border]]Connectors, if simply added to the map and all turns allowed, would cause significant routing challenges, especially between two 2-way roads. Split roadways have their own challenges, but turn restrictions, due to the 1-way nature of the main segments, are simpler.<br />
<br />
In the US, a simple right-turn connector between two 2-way streets, requires that the right turn be restricted at both the primary intersection, and at the connector itself so Waze will not be allowed to tell the driver to turn left across the road to get onto the connector.<br />
<br />
{{clear}}<br />
<br />
[[File:AGC_2018_00003.png|left|border]]<br />
AND, at the end of the connector, the left turn must be restricted:<br />
{{clear}}<br />
<br />
[[File:AGC_2018_00004.png|right|border]]If you enable the "show all restricted connectivity arrows" function in the editor at this intersection, you can see there are many restricted turns. This is sometimes a target for someone looking to remove all restricted turns by abusing the use of the 'w' or '''Allow All''' turns function.<br />
{{clear}}<br />
<br />
== Speed Limit ==<br />
[[Speed limits#At_grade_connectors|At-Grade Connector speed limit instructions]]<br />
<br />
== Exceptions ==<br />
{{construction<br />
| contact = http://www.waze.com/forum/viewtopic.php?f=276&t=86666<br />
| contacttype = forum<br />
| draft = yes<br />
| open = no<br />
| revision = yes<br />
| section = yes<br />
| talk = no<br />
}}<br />
<br />
=== Median U turn intersection (MUTI) ===<br />
<br />
[[File:AGC_MUTI_2018_01a.png|250px|thumbnail|right]]The median crossing segments in a [http://www.fhwa.dot.gov/publications/research/safety/09057/ median U turn (aka "Michigan left") intersection] should be set to the {{Ramp}} type.{{clear}}<br />
<br />
=== Restricted crossing U turn (RCUT) intersection ===<br />
<br />
[[File:AGC_MUTI_2018_02.png|250px|thumbnail|right]]The median crossing segments in a [http://www.fhwa.dot.gov/publications/research/safety/09059/ restricted crossing U turn (aka "J turn" or "Superstreet") intersection] should be set to the {{Ramp}} type.{{clear}}<br />
<br />
=== Displaced left turn (DLT) intersection ===<br />
<br />
[[File:DLT.png|250px|thumbnail|right]]The crossover left turn lanes and the resultant elongated right turn lanes in a [http://www.fhwa.dot.gov/publications/research/safety/09055/ displaced left turn (or "continuous flow") intersection] should be set to the {{Ramp}} type.{{clear}}<br />
<br />
=== Jughandle ===<br />
<br />
[[File:AGC_Jug_2018.png|250px|thumbnail|right]][http://www.fhwa.dot.gov/publications/research/safety/07032/ Jughandle] segments should be set to the {{Ramp}} type.<br><br>For New Jersey, refer to their wiki on [[New_Jersey#Jughandles|Jughandles]].{{clear}}<br />
<br />
=== Signed, numbered exit ===<br />
[[File:GSP_10.jpg|right|border]]<br />
'''Example:''' Garden State Parkway Exit 10 in Cape May Court House, New Jersey, USA.<br />
<br />
The Garden State Parkway is mostly a freeway class toll-road that runs north/south through New Jersey. As the Parkway approaches its southern terminus, the number of lanes is reduced, and at-grade intersections with signed, numbered exits are interspersed with controlled access sections using grade-separated ramps.<br />
<br />
In order to produce an [[Junction_Style_Guide#Controlling_Turn_Instructions|instruction to Exit Right]] for the at-grade intersections, rather than Keep Right or Turn Right, we must use a junction angle of less than 45 degrees and a connector segment of a road type other than Freeway or Highway. Ramp type is ideal for this application because it does not display road names in the app. Segments for numbered exits are named to produce specific visual and TTS instructions, rather than by standard rules for at-grade connectors, and it would be inappropriate to display such names on the map.<br />
{{clear}}<br />
<br />
{|style="margin: 0 auto;"<br />
|- valign="top"<br />
| [[File:GSP_10A.jpg|x162px]]<br />
| [[File:GSP_10B.jpg|x162px]]<br />
| Going north, the right turn lane is signed as Exit 10B and the left turn lane is signed as Exit 10A (and reversed going south).<br />
|}<br />
<br />
<br />
[[Category:Style Guide]]<br />
[[Category:Update what links here]]</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Abc1357/LG&diff=176233User:Abc1357/LG2022-06-25T21:37:05Z<p>Tonestertm: /* Compound Guidance needed */</p>
<hr />
<div>=='''<big>Lanes</big>'''==<br />
''General details on Lanes and how to map them can be found on the [[Lanes|Lanes Wazeopedia page]]. Editors should consider using the [https://www.waze.com/forum/viewtopic.php?f=819&t=301158 Lane Tools script] to assist in mapping lanes correctly.''<br />
<br />
In California, we use a "common sense" approach to guidance, thus deviating slightly from national guidance. Lanes should be mapped for major intersections where the number of turn lanes deviates from what is expected. In other words, do not map Lane Guidance if you can turn right only from the far right lane and/or you can turn left only from the far left lane (as specified by California law), regardless of whether these lanes are dedicated turn lanes or shared lanes. This results in "common sense" guidance, reducing unnecessary voice prompts from the app for trivial instructions. Most of the time, the user is only prompted with lane guidance when something unusual or complex is approaching, requiring heightened attention, and guidance prompts retain their value instead of becoming part of the background noise. <br />
<br />
'''Intersections where you should map Lanes*:'''<br />
<br />
*Intersections that have two or more lanes to turn left or right.<br />
*Complex intersections where [[usa:Lanes#To_clarify_which_road_to_take|clarification of which road to take is necessary]]<br />
<br />
*In a # or H junction where there is a U-Turn, even if there is only a single left turn lane. The addition of Lanes to these intersections combined with lane heuristics enables Waze to announce a ''<code>U-Turn</code>,'' rather than a ''<code>Turn Left, Turn Left</code>''.<br />
**Verify that the parallel segments are almost parallel (i.e. sum of angles with the cross segment should be between 175° and 185°), and the angle with the cross segment should be close to 90°.<br />
**Check that there is not a parallel segment within 50m (165 ft) to the left of the segment with a single perpendicular segment connecting them. Waze heuristics could interpret that to be a U-Turn. Use a Junction Node to "break up" the median segment, and add a map comment close by to indicate why the junction is there. ''Put in a picture of Clarie Drive in Pleasant Hill'' https://www.waze.com/en-US/editor/?env=usa&lon=-122.05663&lat=37.94113&zoom=8&segments=522544024,522544023<br />
*Use the <code>[[usa:Lanes#.22View_and_hear.22_continue_straight|View and Hear]]</code> or <code>[[usa:Lanes#.22View_only.22_continue_straight|View Only]]</code> continue straight overrides where necessary<br />
<br />
<br />''* Before mapping Lanes at any intersection, review prior intersections to ensure adding Lanes at that intersection do not inadvertently cause confusion for the driver (see '''Compound Guidance needed''' section below).''<br />
<br />
<br /><br />
==='''Special Considerations'''===<br />
<br /><br />
<br />
====''At-Grade Connectors''====<br />
When reviewing intersections prior to adding Lanes, please consider whether AGCs are still needed at that intersection.<br />
<br />
For example, the AGC from westbound Walsh Avenue to northbound San Tomas Expressway is not needed. The island is extremely small. The benefits that the AGC was originally meant for, such as advanced announcement of the turn, are not needed.<blockquote>''Picture here (not uploaded to Wazeopedia yet): [https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=]''[https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing sharing]</blockquote>'''What should be done in this situation?'''<br />
<br />
*Remove the AGC and any excess Junction Nodes<br />
*Adjust Turn Restrictions as necessary to compensate for the removed AGC<br />
*Add Lanes, if needed<br />
<br />
<br /><br />
<br />
====''Compound Guidance needed''====<br />
Compound guidance is the concept whereby a driver should be directed to a specific lane or set of lanes at a prior intersection to ensure that the driver is in position to perform the subsequent turn maneuver. Unfortunately, Waze does not yet support compound guidance.<br />
<br />
''Note that some of the following is expected to change with upcoming enhancements to the WME. Check back here if and when those changes occur.''<br />
<br />
'''Lane specific guidance'''<br />
<br />
There are intersections where users should be guided to the proper lane in preparation for the next maneuver.<br />
<br />
Consider a driver going from Crow Canyon Place to I-680 North. There are 2 left turn lanes on Crow Canyon Place. An editor following lane mapping guidance would map that intersection with 2 left turns. A driver unfamiliar with that area could potentially be using the left lane of the 2 left turn lanes to turn into the left lanes on Crow Canyon Road and not be able to enter the on-ramp to I-680 North, if there is a lot of traffic blocking the movement to the right lanes in the short distance available.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1fyevKStP0wqiyM5XalC46GimBkR4PB5b/view?usp=sharing'' </blockquote> <br />
<br />
In order to properly guide the driver, some sort of compound guidance such as ''<code>Use the right of the two left turn lanes to turn left and then turn right to I-680 North Sacramento</code>'' would be ideal. <br />
<br />
'''Loss and re-gain of lane between 2 intersections'''<br />
<br />
There are intersections where a lane is lost to a dedicated turn lane, and yet, by the next intersection, a lane is re-added. A driver following the lane guidance could mistakenly enter the dedicated turn lane prematurely and may be forced to take the earlier turn. <br />
<br />
Consider a driver on [https://www.waze.com/en-US/editor/?env=usa&lon=-121.92340&lat=37.49481&zoom=6 Mission Boulevard being guided to northbound I-680]. There are 3 full lanes at the on-ramp to northbound I-680 with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1WAUh2UMG3NKWgAawNvt-ELKaMko5va6p/view?usp=sharing'' </blockquote>At the prior on-ramp to southbound I-680, there are also 3 full lanes at the on-ramp with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1pKWKjd59aFBNb4ROoViban5_5pPWkgSu/view?usp=sharing'' </blockquote>Note that since Lane Guidance is announced about ½ mile prior to the turn instruction on MH roadways (and ¼ mile for mH and lower), the driver would hear ''<code>In ½ mile, use the right lane to turn right to I-680 North toward Sacramento</code>'' at around Warm Springs Boulevard, which is 2 signaled intersections prior to the entrance to northbound I-680. There is no signage that the right lane ends until you are almost at the entrance to southbound I-680. A driver unfamiliar with the area, upon seeing or hearing the guidance, would get into the right lane. By the time the driver realizes that the lane is a dedicated lane to I-680 South, not North, there isn't much distance left to change lanes, especially when there is a lot of traffic in the next lane.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1uAPd_q-O7VRhYnAtGuvskjHI1Uf3qcqr/view?usp=sharing''</blockquote>In order to properly guide the driver, there are a few possibilities. Waze could delay announcing the Turn instruction to northbound I-680 until the driver is past the entrance to southbound I-680. A more ideal solution would be for Waze to announce ''<code>In ½ mile, stay in the middle lane and then turn right to I-680 North Sacramento</code>''. '''Note from tm - this final paragraph could be confusing and I'd like to consider removing it.''' <br />
<br />
'''What should be done in these situations?'''<br />
<br />
*Lanes should not be mapped at such intersections<br />
*Place a Map Comment so that future editors can locate these locations if Waze enhances the Lane Guidance feature to make mapping these locations possible. Adding a Map Comment could be used as a notification to current editors that the intersection has been reviewed and Lane Guidance should not be added until such time these enhancements are available.<br />
<br />
<br /></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Abc1357/LG&diff=176232User:Abc1357/LG2022-06-25T21:30:14Z<p>Tonestertm: /* Compound Guidance needed */</p>
<hr />
<div>=='''<big>Lanes</big>'''==<br />
''General details on Lanes and how to map them can be found on the [[Lanes|Lanes Wazeopedia page]]. Editors should consider using the [https://www.waze.com/forum/viewtopic.php?f=819&t=301158 Lane Tools script] to assist in mapping lanes correctly.''<br />
<br />
In California, we use a "common sense" approach to guidance, thus deviating slightly from national guidance. Lanes should be mapped for major intersections where the number of turn lanes deviates from what is expected. In other words, do not map Lane Guidance if you can turn right only from the far right lane and/or you can turn left only from the far left lane (as specified by California law), regardless of whether these lanes are dedicated turn lanes or shared lanes. This results in "common sense" guidance, reducing unnecessary voice prompts from the app for trivial instructions. Most of the time, the user is only prompted with lane guidance when something unusual or complex is approaching, requiring heightened attention, and guidance prompts retain their value instead of becoming part of the background noise. <br />
<br />
'''Intersections where you should map Lanes*:'''<br />
<br />
*Intersections that have two or more lanes to turn left or right.<br />
*Complex intersections where [[usa:Lanes#To_clarify_which_road_to_take|clarification of which road to take is necessary]]<br />
<br />
*In a # or H junction where there is a U-Turn, even if there is only a single left turn lane. The addition of Lanes to these intersections combined with lane heuristics enables Waze to announce a ''<code>U-Turn</code>,'' rather than a ''<code>Turn Left, Turn Left</code>''.<br />
**Verify that the parallel segments are almost parallel (i.e. sum of angles with the cross segment should be between 175° and 185°), and the angle with the cross segment should be close to 90°.<br />
**Check that there is not a parallel segment within 50m (165 ft) to the left of the segment with a single perpendicular segment connecting them. Waze heuristics could interpret that to be a U-Turn. Use a Junction Node to "break up" the median segment, and add a map comment close by to indicate why the junction is there. ''Put in a picture of Clarie Drive in Pleasant Hill'' https://www.waze.com/en-US/editor/?env=usa&lon=-122.05663&lat=37.94113&zoom=8&segments=522544024,522544023<br />
*Use the <code>[[usa:Lanes#.22View_and_hear.22_continue_straight|View and Hear]]</code> or <code>[[usa:Lanes#.22View_only.22_continue_straight|View Only]]</code> continue straight overrides where necessary<br />
<br />
<br />''* Before mapping Lanes at any intersection, review prior intersections to ensure adding Lanes at that intersection do not inadvertently cause confusion for the driver (see '''Compound Guidance needed''' section below).''<br />
<br />
<br /><br />
==='''Special Considerations'''===<br />
<br /><br />
<br />
====''At-Grade Connectors''====<br />
When reviewing intersections prior to adding Lanes, please consider whether AGCs are still needed at that intersection.<br />
<br />
For example, the AGC from westbound Walsh Avenue to northbound San Tomas Expressway is not needed. The island is extremely small. The benefits that the AGC was originally meant for, such as advanced announcement of the turn, are not needed.<blockquote>''Picture here (not uploaded to Wazeopedia yet): [https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=]''[https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing sharing]</blockquote>'''What should be done in this situation?'''<br />
<br />
*Remove the AGC and any excess Junction Nodes<br />
*Adjust Turn Restrictions as necessary to compensate for the removed AGC<br />
*Add Lanes, if needed<br />
<br />
<br /><br />
<br />
====''Compound Guidance needed''====<br />
Compound guidance is the concept whereby a driver should be directed to a specific lane or set of lanes at a prior intersection to ensure that the driver is in position to perform the subsequent turn maneuver. Unfortunately, Waze does not yet support compound guidance.<br />
<br />
''Note that some of the following is expected to change with upcoming enhancements to the WME. Check back here if and when those changes occur.''<br />
<br />
'''Lane specific guidance'''<br />
<br />
There are intersections where users should be guided to the proper lane in preparation for the next maneuver.<br />
<br />
Consider a driver going from Crow Canyon Place to I-680 North. There are 2 left turn lanes on Crow Canyon Place. An editor following lane mapping guidance would map that intersection with 2 left turns. A driver unfamiliar with that area could potentially be using the left lane of the 2 left turn lanes to turn into the left lanes on Crow Canyon Road and not be able to enter the on-ramp to I-680 North, if there is a lot of traffic blocking the movement to the right lanes in the short distance available.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1fyevKStP0wqiyM5XalC46GimBkR4PB5b/view?usp=sharing'' </blockquote> <br />
<br />
In order to properly guide the driver, some sort of compound guidance such as ''<code>Use the right of the two left turn lanes to turn left and then turn right to I-680 North Sacramento</code>'' would be ideal. <br />
<br />
'''Loss and re-gain of lane between 2 intersections'''<br />
<br />
There are intersections where a lane is lost to a dedicated turn lane, and yet, by the next intersection, a lane is re-added. A driver following the lane guidance could mistakenly enter the dedicated turn lane prematurely and may be forced to take the earlier turn. <br />
<br />
Consider a driver on [https://www.waze.com/en-US/editor/?env=usa&lon=-121.92340&lat=37.49481&zoom=6 Mission Boulevard being guided to northbound I-680]. There are 3 full lanes at the on-ramp to northbound I-680 with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1WAUh2UMG3NKWgAawNvt-ELKaMko5va6p/view?usp=sharing'' </blockquote>At the prior on-ramp to southbound I-680, there are also 3 full lanes at the on-ramp with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1pKWKjd59aFBNb4ROoViban5_5pPWkgSu/view?usp=sharing'' </blockquote>Note that since Lane Guidance is announced about ½ mile prior to the turn instruction on MH roadways (and ¼ mile for mH and lower), the driver would hear ''<code>In ½ mile, use the right lane to turn right to I-680 North toward Sacramento</code>'' at around Warm Springs Boulevard, which is 2 signaled intersections prior to the entrance to northbound I-680. There is no signage that the right lane ends until you are almost at the entrance to southbound I-680. A driver unfamiliar with the area, upon seeing or hearing the guidance, would get into the right lane. By the time the driver realizes that the lane is a dedicated lane to I-680 South, not North, there isn't much distance left to change lanes, especially when there is a lot of traffic in the next lane.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1uAPd_q-O7VRhYnAtGuvskjHI1Uf3qcqr/view?usp=sharing''</blockquote>In order to properly guide the driver, there are a few possibilities. Waze could delay announcing the Turn instruction to northbound I-680 until the driver is past the entrance to southbound I-680. A more ideal solution would be for Waze to announce ''<code>In ½ mile, stay in the middle lane and then turn right to I-680 North Sacramento</code>''. <br />
<br />
'''What should be done in these situations?'''<br />
<br />
*Lanes should not be mapped at such intersections<br />
*Place a Map Comment so that future editors can locate these locations if Waze enhances the Lane Guidance feature to make mapping these locations possible. Adding a Map Comment could be used as a notification to current editors that the intersection has been reviewed and Lane Guidance should not be added until such time these enhancements are available.<br />
<br />
<br /></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Abc1357/LG&diff=176231User:Abc1357/LG2022-06-25T21:22:57Z<p>Tonestertm: /* Compound Guidance needed */</p>
<hr />
<div>=='''<big>Lanes</big>'''==<br />
''General details on Lanes and how to map them can be found on the [[Lanes|Lanes Wazeopedia page]]. Editors should consider using the [https://www.waze.com/forum/viewtopic.php?f=819&t=301158 Lane Tools script] to assist in mapping lanes correctly.''<br />
<br />
In California, we use a "common sense" approach to guidance, thus deviating slightly from national guidance. Lanes should be mapped for major intersections where the number of turn lanes deviates from what is expected. In other words, do not map Lane Guidance if you can turn right only from the far right lane and/or you can turn left only from the far left lane (as specified by California law), regardless of whether these lanes are dedicated turn lanes or shared lanes. This results in "common sense" guidance, reducing unnecessary voice prompts from the app for trivial instructions. Most of the time, the user is only prompted with lane guidance when something unusual or complex is approaching, requiring heightened attention, and guidance prompts retain their value instead of becoming part of the background noise. <br />
<br />
'''Intersections where you should map Lanes*:'''<br />
<br />
*Intersections that have two or more lanes to turn left or right.<br />
*Complex intersections where [[usa:Lanes#To_clarify_which_road_to_take|clarification of which road to take is necessary]]<br />
<br />
*In a # or H junction where there is a U-Turn, even if there is only a single left turn lane. The addition of Lanes to these intersections combined with lane heuristics enables Waze to announce a ''<code>U-Turn</code>,'' rather than a ''<code>Turn Left, Turn Left</code>''.<br />
**Verify that the parallel segments are almost parallel (i.e. sum of angles with the cross segment should be between 175° and 185°), and the angle with the cross segment should be close to 90°.<br />
**Check that there is not a parallel segment within 50m (165 ft) to the left of the segment with a single perpendicular segment connecting them. Waze heuristics could interpret that to be a U-Turn. Use a Junction Node to "break up" the median segment, and add a map comment close by to indicate why the junction is there. ''Put in a picture of Clarie Drive in Pleasant Hill'' https://www.waze.com/en-US/editor/?env=usa&lon=-122.05663&lat=37.94113&zoom=8&segments=522544024,522544023<br />
*Use the <code>[[usa:Lanes#.22View_and_hear.22_continue_straight|View and Hear]]</code> or <code>[[usa:Lanes#.22View_only.22_continue_straight|View Only]]</code> continue straight overrides where necessary<br />
<br />
<br />''* Before mapping Lanes at any intersection, review prior intersections to ensure adding Lanes at that intersection do not inadvertently cause confusion for the driver (see '''Compound Guidance needed''' section below).''<br />
<br />
<br /><br />
==='''Special Considerations'''===<br />
<br /><br />
<br />
====''At-Grade Connectors''====<br />
When reviewing intersections prior to adding Lanes, please consider whether AGCs are still needed at that intersection.<br />
<br />
For example, the AGC from westbound Walsh Avenue to northbound San Tomas Expressway is not needed. The island is extremely small. The benefits that the AGC was originally meant for, such as advanced announcement of the turn, are not needed.<blockquote>''Picture here (not uploaded to Wazeopedia yet): [https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=]''[https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing sharing]</blockquote>'''What should be done in this situation?'''<br />
<br />
*Remove the AGC and any excess Junction Nodes<br />
*Adjust Turn Restrictions as necessary to compensate for the removed AGC<br />
*Add Lanes, if needed<br />
<br />
<br /><br />
<br />
====''Compound Guidance needed''====<br />
Compound guidance is the concept where a driver should be directed to a specific lane or set of lanes at a prior intersection to ensure that the driver is in position to perform the turn maneuver. Unfortunately, Waze does not yet support compound guidance.<br />
''Note that some of the following is expected to change with upcoming enhancements to the WME. Check back here if and when those changes occur.''<br />
<br />
'''Lane specific guidance'''<br />
<br />
There are intersections where users should be guided to the proper lane in preparation for the next maneuver.<br />
<br />
Consider a driver going from Crow Canyon Place to I-680 North. There are 2 left turn lanes on Crow Canyon Place. An editor following lane mapping guidance would map that intersection with 2 left turns. A driver unfamiliar with that area could potentially be using the left lane of the 2 left turn lanes to turn into the left lanes on Crow Canyon Road and not be able to enter the on-ramp to I-680 North, if there is a lot of traffic blocking the movement to the right lanes in the short distance available.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1fyevKStP0wqiyM5XalC46GimBkR4PB5b/view?usp=sharing'' </blockquote> <br />
<br />
In order to properly guide the driver, some sort of compound guidance such as ''<code>Use the right of the two left turn lanes to turn left and then turn right to I-680 North Sacramento</code>'' would be ideal. <br />
<br />
'''Loss and re-gain of lane between 2 intersections'''<br />
<br />
There are intersections where a lane is lost to a dedicated turn lane, and yet, by the next intersection, a lane is re-added. A driver following the lane guidance could mistakenly enter the dedicated turn lane prematurely and may be forced to take the earlier turn. <br />
<br />
Consider a driver on [https://www.waze.com/en-US/editor/?env=usa&lon=-121.92340&lat=37.49481&zoom=6 Mission Boulevard being guided to northbound I-680]. There are 3 full lanes at the on-ramp to northbound I-680 with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1WAUh2UMG3NKWgAawNvt-ELKaMko5va6p/view?usp=sharing'' </blockquote>At the prior on-ramp to southbound I-680, there are also 3 full lanes at the on-ramp with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1pKWKjd59aFBNb4ROoViban5_5pPWkgSu/view?usp=sharing'' </blockquote>Note that since Lane Guidance is announced about ½ mile prior to the turn instruction on MH roadways (and ¼ mile for mH and lower), the driver would have heard ''<code>In ½ mile, use the right lane to turn right to I-680 North toward Sacramento</code>'' at around Warm Springs Boulevard, which is 2 signaled intersections prior to the entrance to northbound I-680. There is no signage that the right lane ends until you are almost at the entrance to southbound I-680. A driver unfamiliar with the area, upon seeing or hearing the guidance, would get into the right lane. By the time the driver realizes that the lane is a dedicated lane to I-680 South, not North, there isn't much distance left to change lanes, especially when there is a lot of traffic in the next lane.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1uAPd_q-O7VRhYnAtGuvskjHI1Uf3qcqr/view?usp=sharing''</blockquote>In order to properly guide the driver, there are a few possibilities. Waze could delay announcing the Turn instruction to northbound I-680 until the driver is past the entrance to southbound I-680. A more ideal solution would be for Waze to announce ''<code>In ½ mile, stay in the middle lane and then turn right to I-680 North Sacramento</code>''. <br />
<br />
'''What should be done in these situations?'''<br />
<br />
*Lanes should not be mapped at such intersections<br />
*Place a Map Comment so that future editors can locate these locations if Waze enhances the Lane Guidance feature to make mapping these locations possible. Adding a Map Comment could be used as a notification to current editors that the intersection has been reviewed and Lane Guidance should not be added until such time these enhancements are available.<br />
<br />
<br /></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Abc1357/LG&diff=176230User:Abc1357/LG2022-06-25T21:20:25Z<p>Tonestertm: /* Compound Guidance needed */</p>
<hr />
<div>=='''<big>Lanes</big>'''==<br />
''General details on Lanes and how to map them can be found on the [[Lanes|Lanes Wazeopedia page]]. Editors should consider using the [https://www.waze.com/forum/viewtopic.php?f=819&t=301158 Lane Tools script] to assist in mapping lanes correctly.''<br />
<br />
In California, we use a "common sense" approach to guidance, thus deviating slightly from national guidance. Lanes should be mapped for major intersections where the number of turn lanes deviates from what is expected. In other words, do not map Lane Guidance if you can turn right only from the far right lane and/or you can turn left only from the far left lane (as specified by California law), regardless of whether these lanes are dedicated turn lanes or shared lanes. This results in "common sense" guidance, reducing unnecessary voice prompts from the app for trivial instructions. Most of the time, the user is only prompted with lane guidance when something unusual or complex is approaching, requiring heightened attention, and guidance prompts retain their value instead of becoming part of the background noise. <br />
<br />
'''Intersections where you should map Lanes*:'''<br />
<br />
*Intersections that have two or more lanes to turn left or right.<br />
*Complex intersections where [[usa:Lanes#To_clarify_which_road_to_take|clarification of which road to take is necessary]]<br />
<br />
*In a # or H junction where there is a U-Turn, even if there is only a single left turn lane. The addition of Lanes to these intersections combined with lane heuristics enables Waze to announce a ''<code>U-Turn</code>,'' rather than a ''<code>Turn Left, Turn Left</code>''.<br />
**Verify that the parallel segments are almost parallel (i.e. sum of angles with the cross segment should be between 175° and 185°), and the angle with the cross segment should be close to 90°.<br />
**Check that there is not a parallel segment within 50m (165 ft) to the left of the segment with a single perpendicular segment connecting them. Waze heuristics could interpret that to be a U-Turn. Use a Junction Node to "break up" the median segment, and add a map comment close by to indicate why the junction is there. ''Put in a picture of Clarie Drive in Pleasant Hill'' https://www.waze.com/en-US/editor/?env=usa&lon=-122.05663&lat=37.94113&zoom=8&segments=522544024,522544023<br />
*Use the <code>[[usa:Lanes#.22View_and_hear.22_continue_straight|View and Hear]]</code> or <code>[[usa:Lanes#.22View_only.22_continue_straight|View Only]]</code> continue straight overrides where necessary<br />
<br />
<br />''* Before mapping Lanes at any intersection, review prior intersections to ensure adding Lanes at that intersection do not inadvertently cause confusion for the driver (see '''Compound Guidance needed''' section below).''<br />
<br />
<br /><br />
==='''Special Considerations'''===<br />
<br /><br />
<br />
====''At-Grade Connectors''====<br />
When reviewing intersections prior to adding Lanes, please consider whether AGCs are still needed at that intersection.<br />
<br />
For example, the AGC from westbound Walsh Avenue to northbound San Tomas Expressway is not needed. The island is extremely small. The benefits that the AGC was originally meant for, such as advanced announcement of the turn, are not needed.<blockquote>''Picture here (not uploaded to Wazeopedia yet): [https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=]''[https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing sharing]</blockquote>'''What should be done in this situation?'''<br />
<br />
*Remove the AGC and any excess Junction Nodes<br />
*Adjust Turn Restrictions as necessary to compensate for the removed AGC<br />
*Add Lanes, if needed<br />
<br />
<br /><br />
<br />
====''Compound Guidance needed''====<br />
Compound guidance is the concept where a driver should be directed to a specific lane or set of lanes at a prior intersection to ensure that the driver is in position to perform the turn maneuver. Unfortunately, Waze does not yet support compound guidance.<br />
''Note that some of the following is expected to change with upcoming enhancements to the WME. Check back here if and when those changes occur.''<br />
<br />
'''Lane specific guidance'''<br />
<br />
There are intersections where users should be guided to the proper lane in preparation for the next maneuver.<br />
<br />
Consider a driver going from Crow Canyon Place to I-680 North. There are 2 left turn lanes on Crow Canyon Place. An editor following lane mapping guidance would map that intersection with 2 left turns. A driver unfamiliar with that area could potentially be using the left lane of the 2 left turn lanes to turn into the left lanes on Crow Canyon Road and not be able to enter the on-ramp to I-680 North, if there is a lot of traffic blocking the movement to the right lanes in the short distance available.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1fyevKStP0wqiyM5XalC46GimBkR4PB5b/view?usp=sharing'' </blockquote> <br />
<br />
In order to properly guide the driver, some sort of compound guidance such as ''<code>Use the right of the two left turn lanes to turn left and then turn right to I-680 North Sacramento</code>'' would be ideal. <br />
<br />
'''Loss and re-gain of lane between 2 intersections'''<br />
<br />
There are intersections where a lane is lost to a dedicated turn lane, and yet, by the next intersection, a lane is re-added. A driver following the lane guidance could mistakenly enter the dedicated turn lane prematurely and may be forced to take the earlier turn. <br />
<br />
Consider a driver on [https://www.waze.com/en-US/editor/?env=usa&lon=-121.92340&lat=37.49481&zoom=6 Mission Boulevard being guided to northbound I-680]. There are 3 full lanes at the on-ramp to northbound I-680 with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1WAUh2UMG3NKWgAawNvt-ELKaMko5va6p/view?usp=sharing'' </blockquote>At the prior on-ramp to southbound I-680, there are also 3 full lanes at the on-ramp with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1pKWKjd59aFBNb4ROoViban5_5pPWkgSu/view?usp=sharing'' </blockquote>Note that since Lane Guidance is announced about ½ mile on MH segments (and ¼ mile for mH and lower) prior to the turn instruction, the driver would have heard ''<code>In ½ mile, use the right lane to turn right to I-680 North toward Sacramento</code>'' at around Warm Springs Boulevard, which is 2 signaled intersections prior to the entrance to northbound I-680. There is no signage that the right lane ends until you are almost at the entrance to southbound I-680. A driver unfamiliar with the area, upon seeing or hearing the guidance, would get into the right lane. By the time the driver realizes that the lane is a dedicated lane to I-680 South, not North, there isn't much distance left to change lanes, especially when there is a lot of traffic in the next lane.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1uAPd_q-O7VRhYnAtGuvskjHI1Uf3qcqr/view?usp=sharing''</blockquote>In order to properly guide the driver, there are a few possibilities. Waze could delay announcing the Turn instruction to northbound I-680 until the driver is past the entrance to southbound I-680. A more ideal solution would be for Waze to announce ''<code>In ½ mile, stay in the middle lane and then turn right to I-680 North Sacramento</code>''. <br />
<br />
'''What should be done in these situations?'''<br />
<br />
*Lanes should not be mapped at such intersections<br />
*Place a Map Comment so that future editors can locate these locations if Waze enhances the Lane Guidance feature to make mapping these locations possible. Adding a Map Comment could be used as a notification to current editors that the intersection has been reviewed and Lane Guidance should not be added until such time these enhancements are available.<br />
<br />
<br /></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Abc1357/LG&diff=176229User:Abc1357/LG2022-06-25T21:15:28Z<p>Tonestertm: /* Compound Guidance needed */ Hint at upcoming Far Lanes functionality</p>
<hr />
<div>=='''<big>Lanes</big>'''==<br />
''General details on Lanes and how to map them can be found on the [[Lanes|Lanes Wazeopedia page]]. Editors should consider using the [https://www.waze.com/forum/viewtopic.php?f=819&t=301158 Lane Tools script] to assist in mapping lanes correctly.''<br />
<br />
In California, we use a "common sense" approach to guidance, thus deviating slightly from national guidance. Lanes should be mapped for major intersections where the number of turn lanes deviates from what is expected. In other words, do not map Lane Guidance if you can turn right only from the far right lane and/or you can turn left only from the far left lane (as specified by California law), regardless of whether these lanes are dedicated turn lanes or shared lanes. This results in "common sense" guidance, reducing unnecessary voice prompts from the app for trivial instructions. Most of the time, the user is only prompted with lane guidance when something unusual or complex is approaching, requiring heightened attention, and guidance prompts retain their value instead of becoming part of the background noise. <br />
<br />
'''Intersections where you should map Lanes*:'''<br />
<br />
*Intersections that have two or more lanes to turn left or right.<br />
*Complex intersections where [[usa:Lanes#To_clarify_which_road_to_take|clarification of which road to take is necessary]]<br />
<br />
*In a # or H junction where there is a U-Turn, even if there is only a single left turn lane. The addition of Lanes to these intersections combined with lane heuristics enables Waze to announce a ''<code>U-Turn</code>,'' rather than a ''<code>Turn Left, Turn Left</code>''.<br />
**Verify that the parallel segments are almost parallel (i.e. sum of angles with the cross segment should be between 175° and 185°), and the angle with the cross segment should be close to 90°.<br />
**Check that there is not a parallel segment within 50m (165 ft) to the left of the segment with a single perpendicular segment connecting them. Waze heuristics could interpret that to be a U-Turn. Use a Junction Node to "break up" the median segment, and add a map comment close by to indicate why the junction is there. ''Put in a picture of Clarie Drive in Pleasant Hill'' https://www.waze.com/en-US/editor/?env=usa&lon=-122.05663&lat=37.94113&zoom=8&segments=522544024,522544023<br />
*Use the <code>[[usa:Lanes#.22View_and_hear.22_continue_straight|View and Hear]]</code> or <code>[[usa:Lanes#.22View_only.22_continue_straight|View Only]]</code> continue straight overrides where necessary<br />
<br />
<br />''* Before mapping Lanes at any intersection, review prior intersections to ensure adding Lanes at that intersection do not inadvertently cause confusion for the driver (see '''Compound Guidance needed''' section below).''<br />
<br />
<br /><br />
==='''Special Considerations'''===<br />
<br /><br />
<br />
====''At-Grade Connectors''====<br />
When reviewing intersections prior to adding Lanes, please consider whether AGCs are still needed at that intersection.<br />
<br />
For example, the AGC from westbound Walsh Avenue to northbound San Tomas Expressway is not needed. The island is extremely small. The benefits that the AGC was originally meant for, such as advanced announcement of the turn, are not needed.<blockquote>''Picture here (not uploaded to Wazeopedia yet): [https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=]''[https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing sharing]</blockquote>'''What should be done in this situation?'''<br />
<br />
*Remove the AGC and any excess Junction Nodes<br />
*Adjust Turn Restrictions as necessary to compensate for the removed AGC<br />
*Add Lanes, if needed<br />
<br />
<br /><br />
<br />
====''Compound Guidance needed''====<br />
Compound guidance is the concept where a driver should be directed to a specific lane or set of lanes at a prior intersection to ensure that the driver is in position to perform the turn maneuver. Unfortunately, Waze does not yet support compound guidance.<br />
''Note that some of the following is expected to change with upcoming enhancements to the WME. Check back here if and when those changes occur.''<br />
<br />
'''Lane specific guidance'''<br />
<br />
There are intersections where users should be guided to the proper lane in preparation for the next maneuver.<br />
<br />
Consider a driver going from Crow Canyon Place to I-680 North. There are 2 left turn lanes on Crow Canyon Place. An editor following lane mapping guidance would map that intersection with 2 left turns. A driver unfamiliar with that area could potentially be using the left lane of the 2 left turn lanes to turn into the left lanes on Crow Canyon Road and not be able to enter the on-ramp to I-680 North, if there is a lot of traffic blocking the movement to the right lanes in the short distance available.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1fyevKStP0wqiyM5XalC46GimBkR4PB5b/view?usp=sharing'' </blockquote> <br />
<br />
In order to properly guide the driver, some sort of compound guidance such as ''<code>Use the right of the two left turn lanes to turn left and then turn right to I-680 North Sacramento</code>'' would be ideal. <br />
<br />
'''Loss and re-gain of lane between 2 intersections'''<br />
<br />
There are intersections where a lane is lost to a dedicated turn lane, and yet, by the next intersection, a lane is re-added. A driver following the lane guidance could mistakenly enter the dedicated turn lane prematurely and may be forced to take the earlier turn. <br />
<br />
Consider a driver on [https://www.waze.com/en-US/editor/?env=usa&lon=-121.92340&lat=37.49481&zoom=6 Mission Boulevard being guided to northbound I-680]. There are 3 full lanes at the on-ramp to northbound I-680 with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1WAUh2UMG3NKWgAawNvt-ELKaMko5va6p/view?usp=sharing'' </blockquote>At the prior on-ramp to southbound I-680, there are also 3 full lanes at the on-ramp with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1pKWKjd59aFBNb4ROoViban5_5pPWkgSu/view?usp=sharing'' </blockquote>Note that since Lane Guidance is announced about ½ mile for MH (and ¼ mile for mH and lower) prior to the turn instruction, the driver would have heard ''<code>In ½ mile, use the right lane to turn right to I-680 North Sacramento</code>'' at around Warm Springs Boulevard, which is 2 signaled intersections prior to the entrance to northbound I-680. There is no signage that the right lane ends until you are almost at the entrance to southbound I-680. A driver unfamiliar with the area, upon seeing or hearing the guidance, would get into the right lane. By the time the driver realizes that the lane is a dedicated lane to I-680 South, not North, there isn't much distance left to change lanes, especially when there is a lot of traffic in the next lane.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1uAPd_q-O7VRhYnAtGuvskjHI1Uf3qcqr/view?usp=sharing''</blockquote>In order to properly guide the driver, there are a few possibilities. Waze could delay announcing the Turn instruction to northbound I-680 until the driver is past the entrance to southbound I-680. A more ideal solution would be for Waze to announce ''<code>In ½ mile, stay in the middle lane and then turn right to I-680 North Sacramento</code>''. <br />
<br />
'''What should be done in these situations?'''<br />
<br />
*Lanes should not be mapped at such intersections<br />
*Place a Map Comment so that future editors can locate these locations if Waze enhances the Lane Guidance feature to make mapping these locations possible. Adding a Map Comment could be used as a notification to current editors that the intersection has been reviewed and Lane Guidance should not be added until such time these enhancements are available.<br />
<br />
<br /></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Abc1357/LG&diff=176228User:Abc1357/LG2022-06-25T21:11:09Z<p>Tonestertm: /* At-Grade Connectors */</p>
<hr />
<div>=='''<big>Lanes</big>'''==<br />
''General details on Lanes and how to map them can be found on the [[Lanes|Lanes Wazeopedia page]]. Editors should consider using the [https://www.waze.com/forum/viewtopic.php?f=819&t=301158 Lane Tools script] to assist in mapping lanes correctly.''<br />
<br />
In California, we use a "common sense" approach to guidance, thus deviating slightly from national guidance. Lanes should be mapped for major intersections where the number of turn lanes deviates from what is expected. In other words, do not map Lane Guidance if you can turn right only from the far right lane and/or you can turn left only from the far left lane (as specified by California law), regardless of whether these lanes are dedicated turn lanes or shared lanes. This results in "common sense" guidance, reducing unnecessary voice prompts from the app for trivial instructions. Most of the time, the user is only prompted with lane guidance when something unusual or complex is approaching, requiring heightened attention, and guidance prompts retain their value instead of becoming part of the background noise. <br />
<br />
'''Intersections where you should map Lanes*:'''<br />
<br />
*Intersections that have two or more lanes to turn left or right.<br />
*Complex intersections where [[usa:Lanes#To_clarify_which_road_to_take|clarification of which road to take is necessary]]<br />
<br />
*In a # or H junction where there is a U-Turn, even if there is only a single left turn lane. The addition of Lanes to these intersections combined with lane heuristics enables Waze to announce a ''<code>U-Turn</code>,'' rather than a ''<code>Turn Left, Turn Left</code>''.<br />
**Verify that the parallel segments are almost parallel (i.e. sum of angles with the cross segment should be between 175° and 185°), and the angle with the cross segment should be close to 90°.<br />
**Check that there is not a parallel segment within 50m (165 ft) to the left of the segment with a single perpendicular segment connecting them. Waze heuristics could interpret that to be a U-Turn. Use a Junction Node to "break up" the median segment, and add a map comment close by to indicate why the junction is there. ''Put in a picture of Clarie Drive in Pleasant Hill'' https://www.waze.com/en-US/editor/?env=usa&lon=-122.05663&lat=37.94113&zoom=8&segments=522544024,522544023<br />
*Use the <code>[[usa:Lanes#.22View_and_hear.22_continue_straight|View and Hear]]</code> or <code>[[usa:Lanes#.22View_only.22_continue_straight|View Only]]</code> continue straight overrides where necessary<br />
<br />
<br />''* Before mapping Lanes at any intersection, review prior intersections to ensure adding Lanes at that intersection do not inadvertently cause confusion for the driver (see '''Compound Guidance needed''' section below).''<br />
<br />
<br /><br />
==='''Special Considerations'''===<br />
<br /><br />
<br />
====''At-Grade Connectors''====<br />
When reviewing intersections prior to adding Lanes, please consider whether AGCs are still needed at that intersection.<br />
<br />
For example, the AGC from westbound Walsh Avenue to northbound San Tomas Expressway is not needed. The island is extremely small. The benefits that the AGC was originally meant for, such as advanced announcement of the turn, are not needed.<blockquote>''Picture here (not uploaded to Wazeopedia yet): [https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=]''[https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing sharing]</blockquote>'''What should be done in this situation?'''<br />
<br />
*Remove the AGC and any excess Junction Nodes<br />
*Adjust Turn Restrictions as necessary to compensate for the removed AGC<br />
*Add Lanes, if needed<br />
<br />
<br /><br />
<br />
====''Compound Guidance needed''====<br />
Compound guidance is the concept where a driver should be directed to a specific lane or set of lanes at a prior intersection to ensure that the driver is in position to perform the turn maneuver. Unfortunately, Waze does not yet support compound guidance.<br />
<br />
'''Lane specific guidance'''<br />
<br />
There are intersections where users should be guided to the proper lane in preparation for the next maneuver.<br />
<br />
Consider a driver going from Crow Canyon Place to I-680 North. There are 2 left turn lanes on Crow Canyon Place. An editor following lane mapping guidance would map that intersection with 2 left turns. A driver unfamiliar with that area could potentially be using the left lane of the 2 left turn lanes to turn into the left lanes on Crow Canyon Road and not be able to enter the on-ramp to I-680 North, if there is a lot of traffic blocking the movement to the right lanes in the short distance available.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1fyevKStP0wqiyM5XalC46GimBkR4PB5b/view?usp=sharing'' </blockquote> <br />
<br />
In order to properly guide the driver, some sort of compound guidance such as ''<code>Use the right of the two left turn lanes to turn left and then turn right to I-680 North Sacramento</code>'' would be ideal. <br />
<br />
'''Loss and re-gain of lane between 2 intersections'''<br />
<br />
There are intersections where a lane is lost to a dedicated turn lane, and yet, by the next intersection, a lane is re-added. A driver following the lane guidance could mistakenly enter the dedicated turn lane prematurely and may be forced to take the earlier turn. <br />
<br />
Consider a driver on [https://www.waze.com/en-US/editor/?env=usa&lon=-121.92340&lat=37.49481&zoom=6 Mission Boulevard being guided to northbound I-680]. There are 3 full lanes at the on-ramp to northbound I-680 with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1WAUh2UMG3NKWgAawNvt-ELKaMko5va6p/view?usp=sharing'' </blockquote>At the prior on-ramp to southbound I-680, there are also 3 full lanes at the on-ramp with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1pKWKjd59aFBNb4ROoViban5_5pPWkgSu/view?usp=sharing'' </blockquote>Note that since Lane Guidance is announced about ½ mile for MH (and ¼ mile for mH and lower) prior to the turn instruction, the driver would have heard ''<code>In ½ mile, use the right lane to turn right to I-680 North Sacramento</code>'' at around Warm Springs Boulevard, which is 2 signaled intersections prior to the entrance to northbound I-680. There is no signage that the right lane ends until you are almost at the entrance to southbound I-680. A driver unfamiliar with the area, upon seeing or hearing the guidance, would get into the right lane. By the time the driver realizes that the lane is a dedicated lane to I-680 South, not North, there isn't much distance left to change lanes, especially when there is a lot of traffic in the next lane.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1uAPd_q-O7VRhYnAtGuvskjHI1Uf3qcqr/view?usp=sharing''</blockquote>In order to properly guide the driver, there are a few possibilities. Waze could delay announcing the Turn instruction to northbound I-680 until the driver is past the entrance to southbound I-680. A more ideal solution would be for Waze to announce ''<code>In ½ mile, stay in the middle lane and then turn right to I-680 North Sacramento</code>''. <br />
<br />
'''What should be done in these situations?'''<br />
<br />
*Lanes should not be mapped at such intersections<br />
*Place a Map Comment so that future editors can locate these locations if Waze enhances the Lane Guidance feature to make mapping these locations possible. Adding a Map Comment could be used as a notification to current editors that the intersection has been reviewed and Lane Guidance should not be added until such time these enhancements are available.<br />
<br />
<br /></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Abc1357/LG&diff=176227User:Abc1357/LG2022-06-25T21:07:11Z<p>Tonestertm: /* Lanes */</p>
<hr />
<div>=='''<big>Lanes</big>'''==<br />
''General details on Lanes and how to map them can be found on the [[Lanes|Lanes Wazeopedia page]]. Editors should consider using the [https://www.waze.com/forum/viewtopic.php?f=819&t=301158 Lane Tools script] to assist in mapping lanes correctly.''<br />
<br />
In California, we use a "common sense" approach to guidance, thus deviating slightly from national guidance. Lanes should be mapped for major intersections where the number of turn lanes deviates from what is expected. In other words, do not map Lane Guidance if you can turn right only from the far right lane and/or you can turn left only from the far left lane (as specified by California law), regardless of whether these lanes are dedicated turn lanes or shared lanes. This results in "common sense" guidance, reducing unnecessary voice prompts from the app for trivial instructions. Most of the time, the user is only prompted with lane guidance when something unusual or complex is approaching, requiring heightened attention, and guidance prompts retain their value instead of becoming part of the background noise. <br />
<br />
'''Intersections where you should map Lanes*:'''<br />
<br />
*Intersections that have two or more lanes to turn left or right.<br />
*Complex intersections where [[usa:Lanes#To_clarify_which_road_to_take|clarification of which road to take is necessary]]<br />
<br />
*In a # or H junction where there is a U-Turn, even if there is only a single left turn lane. The addition of Lanes to these intersections combined with lane heuristics enables Waze to announce a ''<code>U-Turn</code>,'' rather than a ''<code>Turn Left, Turn Left</code>''.<br />
**Verify that the parallel segments are almost parallel (i.e. sum of angles with the cross segment should be between 175° and 185°), and the angle with the cross segment should be close to 90°.<br />
**Check that there is not a parallel segment within 50m (165 ft) to the left of the segment with a single perpendicular segment connecting them. Waze heuristics could interpret that to be a U-Turn. Use a Junction Node to "break up" the median segment, and add a map comment close by to indicate why the junction is there. ''Put in a picture of Clarie Drive in Pleasant Hill'' https://www.waze.com/en-US/editor/?env=usa&lon=-122.05663&lat=37.94113&zoom=8&segments=522544024,522544023<br />
*Use the <code>[[usa:Lanes#.22View_and_hear.22_continue_straight|View and Hear]]</code> or <code>[[usa:Lanes#.22View_only.22_continue_straight|View Only]]</code> continue straight overrides where necessary<br />
<br />
<br />''* Before mapping Lanes at any intersection, review prior intersections to ensure adding Lanes at that intersection do not inadvertently cause confusion for the driver (see '''Compound Guidance needed''' section below).''<br />
<br />
<br /><br />
==='''Special Considerations'''===<br />
<br /><br />
<br />
====''At-Grade Connectors''====<br />
When reviewing intersections prior to adding Lanes, please consider whether AGCs are still needed at that intersection.<br />
<br />
For example, the AGC from westbound Walsh Avenue to northbound San Tomas Expressway is not needed. The island is extremely small. The benefits that the AGC was originally meant for, such as advanced announcement of the turn, are not needed.<blockquote>''Picture here (not uploaded to Wazeopedia yet): [https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=]''[https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing sharing]</blockquote>'''What should be done in this situation?'''<br />
<br />
*Remove the AGC and any excess Junction Nodes<br />
*Check to ensure Turn Restrictions are correct for the intersection<br />
*Add Lanes, if needed<br />
<br />
<br /><br />
<br />
====''Compound Guidance needed''====<br />
Compound guidance is the concept where a driver should be directed to a specific lane or set of lanes at a prior intersection to ensure that the driver is in position to perform the turn maneuver. Unfortunately, Waze does not yet support compound guidance.<br />
<br />
'''Lane specific guidance'''<br />
<br />
There are intersections where users should be guided to the proper lane in preparation for the next maneuver.<br />
<br />
Consider a driver going from Crow Canyon Place to I-680 North. There are 2 left turn lanes on Crow Canyon Place. An editor following lane mapping guidance would map that intersection with 2 left turns. A driver unfamiliar with that area could potentially be using the left lane of the 2 left turn lanes to turn into the left lanes on Crow Canyon Road and not be able to enter the on-ramp to I-680 North, if there is a lot of traffic blocking the movement to the right lanes in the short distance available.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1fyevKStP0wqiyM5XalC46GimBkR4PB5b/view?usp=sharing'' </blockquote> <br />
<br />
In order to properly guide the driver, some sort of compound guidance such as ''<code>Use the right of the two left turn lanes to turn left and then turn right to I-680 North Sacramento</code>'' would be ideal. <br />
<br />
'''Loss and re-gain of lane between 2 intersections'''<br />
<br />
There are intersections where a lane is lost to a dedicated turn lane, and yet, by the next intersection, a lane is re-added. A driver following the lane guidance could mistakenly enter the dedicated turn lane prematurely and may be forced to take the earlier turn. <br />
<br />
Consider a driver on [https://www.waze.com/en-US/editor/?env=usa&lon=-121.92340&lat=37.49481&zoom=6 Mission Boulevard being guided to northbound I-680]. There are 3 full lanes at the on-ramp to northbound I-680 with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1WAUh2UMG3NKWgAawNvt-ELKaMko5va6p/view?usp=sharing'' </blockquote>At the prior on-ramp to southbound I-680, there are also 3 full lanes at the on-ramp with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1pKWKjd59aFBNb4ROoViban5_5pPWkgSu/view?usp=sharing'' </blockquote>Note that since Lane Guidance is announced about ½ mile for MH (and ¼ mile for mH and lower) prior to the turn instruction, the driver would have heard ''<code>In ½ mile, use the right lane to turn right to I-680 North Sacramento</code>'' at around Warm Springs Boulevard, which is 2 signaled intersections prior to the entrance to northbound I-680. There is no signage that the right lane ends until you are almost at the entrance to southbound I-680. A driver unfamiliar with the area, upon seeing or hearing the guidance, would get into the right lane. By the time the driver realizes that the lane is a dedicated lane to I-680 South, not North, there isn't much distance left to change lanes, especially when there is a lot of traffic in the next lane.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1uAPd_q-O7VRhYnAtGuvskjHI1Uf3qcqr/view?usp=sharing''</blockquote>In order to properly guide the driver, there are a few possibilities. Waze could delay announcing the Turn instruction to northbound I-680 until the driver is past the entrance to southbound I-680. A more ideal solution would be for Waze to announce ''<code>In ½ mile, stay in the middle lane and then turn right to I-680 North Sacramento</code>''. <br />
<br />
'''What should be done in these situations?'''<br />
<br />
*Lanes should not be mapped at such intersections<br />
*Place a Map Comment so that future editors can locate these locations if Waze enhances the Lane Guidance feature to make mapping these locations possible. Adding a Map Comment could be used as a notification to current editors that the intersection has been reviewed and Lane Guidance should not be added until such time these enhancements are available.<br />
<br />
<br /></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Abc1357/LG&diff=176226User:Abc1357/LG2022-06-25T21:05:27Z<p>Tonestertm: /* Lanes */ added more common sense and reasoning.</p>
<hr />
<div>=='''<big>Lanes</big>'''==<br />
''General details on Lanes and how to map them can be found on the [[Lanes|Lanes Wazeopedia page]]. Editors should consider using the [https://www.waze.com/forum/viewtopic.php?f=819&t=301158 Lane Tools script] to assist in mapping lanes correctly.''<br />
<br />
In California, we use a "common sense" approach to guidance, thus deviating slightly from national guidance. Lanes should be mapped for major intersections where the number of turn lanes deviates from what is expected. In other words, do not map Lane Guidance if you can turn right only from the far right lane and/or you can turn left only from the far left lane (as specified by California law), regardless of whether these lanes are dedicated turn lanes or shared lanes. This results in "common sense" guidance, reducing unnecessary voice prompts from the app for trivial instructions. Most of the time, the user is only prompted with lane guidance when something unusual or complex is approaching, requiring heightened attention. <br />
<br />
'''Intersections where you should map Lanes*:'''<br />
<br />
*Intersections that have two or more lanes to turn left or right.<br />
*Complex intersections where [[usa:Lanes#To_clarify_which_road_to_take|clarification of which road to take is necessary]]<br />
<br />
*In a # or H junction where there is a U-Turn, even if there is only a single left turn lane. The addition of Lanes to these intersections combined with lane heuristics enables Waze to announce a ''<code>U-Turn</code>,'' rather than a ''<code>Turn Left, Turn Left</code>''.<br />
**Verify that the parallel segments are almost parallel (i.e. sum of angles with the cross segment should be between 175° and 185°), and the angle with the cross segment should be close to 90°.<br />
**Check that there is not a parallel segment within 50m (165 ft) to the left of the segment with a single perpendicular segment connecting them. Waze heuristics could interpret that to be a U-Turn. Use a Junction Node to "break up" the median segment, and add a map comment close by to indicate why the junction is there. ''Put in a picture of Clarie Drive in Pleasant Hill'' https://www.waze.com/en-US/editor/?env=usa&lon=-122.05663&lat=37.94113&zoom=8&segments=522544024,522544023<br />
*Use the <code>[[usa:Lanes#.22View_and_hear.22_continue_straight|View and Hear]]</code> or <code>[[usa:Lanes#.22View_only.22_continue_straight|View Only]]</code> continue straight overrides where necessary<br />
<br />
<br />''* Before mapping Lanes at any intersection, review prior intersections to ensure adding Lanes at that intersection do not inadvertently cause confusion for the driver (see '''Compound Guidance needed''' section below).''<br />
<br />
<br /><br />
==='''Special Considerations'''===<br />
<br /><br />
<br />
====''At-Grade Connectors''====<br />
When reviewing intersections prior to adding Lanes, please consider whether AGCs are still needed at that intersection.<br />
<br />
For example, the AGC from westbound Walsh Avenue to northbound San Tomas Expressway is not needed. The island is extremely small. The benefits that the AGC was originally meant for, such as advanced announcement of the turn, are not needed.<blockquote>''Picture here (not uploaded to Wazeopedia yet): [https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=]''[https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing sharing]</blockquote>'''What should be done in this situation?'''<br />
<br />
*Remove the AGC and any excess Junction Nodes<br />
*Check to ensure Turn Restrictions are correct for the intersection<br />
*Add Lanes, if needed<br />
<br />
<br /><br />
<br />
====''Compound Guidance needed''====<br />
Compound guidance is the concept where a driver should be directed to a specific lane or set of lanes at a prior intersection to ensure that the driver is in position to perform the turn maneuver. Unfortunately, Waze does not yet support compound guidance.<br />
<br />
'''Lane specific guidance'''<br />
<br />
There are intersections where users should be guided to the proper lane in preparation for the next maneuver.<br />
<br />
Consider a driver going from Crow Canyon Place to I-680 North. There are 2 left turn lanes on Crow Canyon Place. An editor following lane mapping guidance would map that intersection with 2 left turns. A driver unfamiliar with that area could potentially be using the left lane of the 2 left turn lanes to turn into the left lanes on Crow Canyon Road and not be able to enter the on-ramp to I-680 North, if there is a lot of traffic blocking the movement to the right lanes in the short distance available.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1fyevKStP0wqiyM5XalC46GimBkR4PB5b/view?usp=sharing'' </blockquote> <br />
<br />
In order to properly guide the driver, some sort of compound guidance such as ''<code>Use the right of the two left turn lanes to turn left and then turn right to I-680 North Sacramento</code>'' would be ideal. <br />
<br />
'''Loss and re-gain of lane between 2 intersections'''<br />
<br />
There are intersections where a lane is lost to a dedicated turn lane, and yet, by the next intersection, a lane is re-added. A driver following the lane guidance could mistakenly enter the dedicated turn lane prematurely and may be forced to take the earlier turn. <br />
<br />
Consider a driver on [https://www.waze.com/en-US/editor/?env=usa&lon=-121.92340&lat=37.49481&zoom=6 Mission Boulevard being guided to northbound I-680]. There are 3 full lanes at the on-ramp to northbound I-680 with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1WAUh2UMG3NKWgAawNvt-ELKaMko5va6p/view?usp=sharing'' </blockquote>At the prior on-ramp to southbound I-680, there are also 3 full lanes at the on-ramp with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1pKWKjd59aFBNb4ROoViban5_5pPWkgSu/view?usp=sharing'' </blockquote>Note that since Lane Guidance is announced about ½ mile for MH (and ¼ mile for mH and lower) prior to the turn instruction, the driver would have heard ''<code>In ½ mile, use the right lane to turn right to I-680 North Sacramento</code>'' at around Warm Springs Boulevard, which is 2 signaled intersections prior to the entrance to northbound I-680. There is no signage that the right lane ends until you are almost at the entrance to southbound I-680. A driver unfamiliar with the area, upon seeing or hearing the guidance, would get into the right lane. By the time the driver realizes that the lane is a dedicated lane to I-680 South, not North, there isn't much distance left to change lanes, especially when there is a lot of traffic in the next lane.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1uAPd_q-O7VRhYnAtGuvskjHI1Uf3qcqr/view?usp=sharing''</blockquote>In order to properly guide the driver, there are a few possibilities. Waze could delay announcing the Turn instruction to northbound I-680 until the driver is past the entrance to southbound I-680. A more ideal solution would be for Waze to announce ''<code>In ½ mile, stay in the middle lane and then turn right to I-680 North Sacramento</code>''. <br />
<br />
'''What should be done in these situations?'''<br />
<br />
*Lanes should not be mapped at such intersections<br />
*Place a Map Comment so that future editors can locate these locations if Waze enhances the Lane Guidance feature to make mapping these locations possible. Adding a Map Comment could be used as a notification to current editors that the intersection has been reviewed and Lane Guidance should not be added until such time these enhancements are available.<br />
<br />
<br /></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Abc1357/LG&diff=176225User:Abc1357/LG2022-06-25T20:59:18Z<p>Tonestertm: /* Lanes */</p>
<hr />
<div>=='''<big>Lanes</big>'''==<br />
''General details on Lanes and how to map them can be found on the [[Lanes|Lanes Wazeopedia page]]. Editors should consider using the [https://www.waze.com/forum/viewtopic.php?f=819&t=301158 Lane Tools script] to assist in mapping lanes correctly.''<br />
<br />
In California, we use a "Common Sense" approach to guidance, thus deviating slightly from national guidance. Lanes should be mapped for major intersections where the number of turn lanes deviates from what is expected. In other words, do not map Lane Guidance if you can turn right only from the right lane and/or you can turn left only from the left lane, regardless of whether these lanes are dedicated turn lanes or shared lanes.<br />
<br />
'''Intersections where you should map Lanes*:'''<br />
<br />
*Intersections that have two or more lanes to turn left or right.<br />
*Complex intersections where [[usa:Lanes#To_clarify_which_road_to_take|clarification of which road to take is necessary]]<br />
<br />
*In a # or H junction where there is a U-Turn, even if there is only a single left turn lane. The addition of Lanes to these intersections combined with lane heuristics enables Waze to announce a ''<code>U-Turn</code>,'' rather than a ''<code>Turn Left, Turn Left</code>''.<br />
**Verify that the parallel segments are almost parallel (i.e. sum of angles with the cross segment should be between 175° and 185°), and the angle with the cross segment should be close to 90°.<br />
**Check that there is not a parallel segment within 50m (165 ft) to the left of the segment with a single perpendicular segment connecting them. Waze heuristics could interpret that to be a U-Turn. Use a Junction Node to "break up" the median segment, and add a map comment close by to indicate why the junction is there. ''Put in a picture of Clarie Drive in Pleasant Hill'' https://www.waze.com/en-US/editor/?env=usa&lon=-122.05663&lat=37.94113&zoom=8&segments=522544024,522544023<br />
*Use the <code>[[usa:Lanes#.22View_and_hear.22_continue_straight|View and Hear]]</code> or <code>[[usa:Lanes#.22View_only.22_continue_straight|View Only]]</code> continue straight overrides where necessary<br />
<br />
<br />''* Before mapping Lanes at any intersection, review prior intersections to ensure adding Lanes at that intersection do not inadvertently cause confusion for the driver (see '''Compound Guidance needed''' section below).''<br />
<br />
<br /><br />
==='''Special Considerations'''===<br />
<br /><br />
<br />
====''At-Grade Connectors''====<br />
When reviewing intersections prior to adding Lanes, please consider whether AGCs are still needed at that intersection.<br />
<br />
For example, the AGC from westbound Walsh Avenue to northbound San Tomas Expressway is not needed. The island is extremely small. The benefits that the AGC was originally meant for, such as advanced announcement of the turn, are not needed.<blockquote>''Picture here (not uploaded to Wazeopedia yet): [https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=]''[https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing sharing]</blockquote>'''What should be done in this situation?'''<br />
<br />
*Remove the AGC and any excess Junction Nodes<br />
*Check to ensure Turn Restrictions are correct for the intersection<br />
*Add Lanes, if needed<br />
<br />
<br /><br />
<br />
====''Compound Guidance needed''====<br />
Compound guidance is the concept where a driver should be directed to a specific lane or set of lanes at a prior intersection to ensure that the driver is in position to perform the turn maneuver. Unfortunately, Waze does not yet support compound guidance.<br />
<br />
'''Lane specific guidance'''<br />
<br />
There are intersections where users should be guided to the proper lane in preparation for the next maneuver.<br />
<br />
Consider a driver going from Crow Canyon Place to I-680 North. There are 2 left turn lanes on Crow Canyon Place. An editor following lane mapping guidance would map that intersection with 2 left turns. A driver unfamiliar with that area could potentially be using the left lane of the 2 left turn lanes to turn into the left lanes on Crow Canyon Road and not be able to enter the on-ramp to I-680 North, if there is a lot of traffic blocking the movement to the right lanes in the short distance available.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1fyevKStP0wqiyM5XalC46GimBkR4PB5b/view?usp=sharing'' </blockquote> <br />
<br />
In order to properly guide the driver, some sort of compound guidance such as ''<code>Use the right of the two left turn lanes to turn left and then turn right to I-680 North Sacramento</code>'' would be ideal. <br />
<br />
'''Loss and re-gain of lane between 2 intersections'''<br />
<br />
There are intersections where a lane is lost to a dedicated turn lane, and yet, by the next intersection, a lane is re-added. A driver following the lane guidance could mistakenly enter the dedicated turn lane prematurely and may be forced to take the earlier turn. <br />
<br />
Consider a driver on [https://www.waze.com/en-US/editor/?env=usa&lon=-121.92340&lat=37.49481&zoom=6 Mission Boulevard being guided to northbound I-680]. There are 3 full lanes at the on-ramp to northbound I-680 with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1WAUh2UMG3NKWgAawNvt-ELKaMko5va6p/view?usp=sharing'' </blockquote>At the prior on-ramp to southbound I-680, there are also 3 full lanes at the on-ramp with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1pKWKjd59aFBNb4ROoViban5_5pPWkgSu/view?usp=sharing'' </blockquote>Note that since Lane Guidance is announced about ½ mile for MH (and ¼ mile for mH and lower) prior to the turn instruction, the driver would have heard ''<code>In ½ mile, use the right lane to turn right to I-680 North Sacramento</code>'' at around Warm Springs Boulevard, which is 2 signaled intersections prior to the entrance to northbound I-680. There is no signage that the right lane ends until you are almost at the entrance to southbound I-680. A driver unfamiliar with the area, upon seeing or hearing the guidance, would get into the right lane. By the time the driver realizes that the lane is a dedicated lane to I-680 South, not North, there isn't much distance left to change lanes, especially when there is a lot of traffic in the next lane.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1uAPd_q-O7VRhYnAtGuvskjHI1Uf3qcqr/view?usp=sharing''</blockquote>In order to properly guide the driver, there are a few possibilities. Waze could delay announcing the Turn instruction to northbound I-680 until the driver is past the entrance to southbound I-680. A more ideal solution would be for Waze to announce ''<code>In ½ mile, stay in the middle lane and then turn right to I-680 North Sacramento</code>''. <br />
<br />
'''What should be done in these situations?'''<br />
<br />
*Lanes should not be mapped at such intersections<br />
*Place a Map Comment so that future editors can locate these locations if Waze enhances the Lane Guidance feature to make mapping these locations possible. Adding a Map Comment could be used as a notification to current editors that the intersection has been reviewed and Lane Guidance should not be added until such time these enhancements are available.<br />
<br />
<br /></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Abc1357/LG&diff=176224User:Abc1357/LG2022-06-25T20:58:46Z<p>Tonestertm: /* Lanes */</p>
<hr />
<div>=='''<big>Lanes</big>'''==<br />
''General details on Lanes and how to map them can be found on the [[Lanes|Lanes Wazeopedia page]]. Editors should consider using the [https://www.waze.com/forum/viewtopic.php?f=819&t=301158 Lane Tools script] to assist in mapping lanes correctly.''<br />
<br />
In California, we use a "Common Sense" approach to guidance, deviating slightly from national guidance. Lanes should be mapped for major intersections where the number of turn lanes deviates from what is expected. In other words, do not map Lane Guidance if you can turn right only from the right lane and/or you can turn left only from the left lane, regardless of whether these lanes are dedicated turn lanes or shared lanes.<br />
<br />
'''Intersections where you should map Lanes*:'''<br />
<br />
*Intersections that have two or more lanes to turn left or right.<br />
*Complex intersections where [[usa:Lanes#To_clarify_which_road_to_take|clarification of which road to take is necessary]]<br />
<br />
*In a # or H junction where there is a U-Turn, even if there is only a single left turn lane. The addition of Lanes to these intersections combined with lane heuristics enables Waze to announce a ''<code>U-Turn</code>,'' rather than a ''<code>Turn Left, Turn Left</code>''.<br />
**Verify that the parallel segments are almost parallel (i.e. sum of angles with the cross segment should be between 175° and 185°), and the angle with the cross segment should be close to 90°.<br />
**Check that there is not a parallel segment within 50m (165 ft) to the left of the segment with a single perpendicular segment connecting them. Waze heuristics could interpret that to be a U-Turn. Use a Junction Node to "break up" the median segment, and add a map comment close by to indicate why the junction is there. ''Put in a picture of Clarie Drive in Pleasant Hill'' https://www.waze.com/en-US/editor/?env=usa&lon=-122.05663&lat=37.94113&zoom=8&segments=522544024,522544023<br />
*Use the <code>[[usa:Lanes#.22View_and_hear.22_continue_straight|View and Hear]]</code> or <code>[[usa:Lanes#.22View_only.22_continue_straight|View Only]]</code> continue straight overrides where necessary<br />
<br />
<br />''* Before mapping Lanes at any intersection, review prior intersections to ensure adding Lanes at that intersection do not inadvertently cause confusion for the driver (see '''Compound Guidance needed''' section below).''<br />
<br />
<br /><br />
==='''Special Considerations'''===<br />
<br /><br />
<br />
====''At-Grade Connectors''====<br />
When reviewing intersections prior to adding Lanes, please consider whether AGCs are still needed at that intersection.<br />
<br />
For example, the AGC from westbound Walsh Avenue to northbound San Tomas Expressway is not needed. The island is extremely small. The benefits that the AGC was originally meant for, such as advanced announcement of the turn, are not needed.<blockquote>''Picture here (not uploaded to Wazeopedia yet): [https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=]''[https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing sharing]</blockquote>'''What should be done in this situation?'''<br />
<br />
*Remove the AGC and any excess Junction Nodes<br />
*Check to ensure Turn Restrictions are correct for the intersection<br />
*Add Lanes, if needed<br />
<br />
<br /><br />
<br />
====''Compound Guidance needed''====<br />
Compound guidance is the concept where a driver should be directed to a specific lane or set of lanes at a prior intersection to ensure that the driver is in position to perform the turn maneuver. Unfortunately, Waze does not yet support compound guidance.<br />
<br />
'''Lane specific guidance'''<br />
<br />
There are intersections where users should be guided to the proper lane in preparation for the next maneuver.<br />
<br />
Consider a driver going from Crow Canyon Place to I-680 North. There are 2 left turn lanes on Crow Canyon Place. An editor following lane mapping guidance would map that intersection with 2 left turns. A driver unfamiliar with that area could potentially be using the left lane of the 2 left turn lanes to turn into the left lanes on Crow Canyon Road and not be able to enter the on-ramp to I-680 North, if there is a lot of traffic blocking the movement to the right lanes in the short distance available.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1fyevKStP0wqiyM5XalC46GimBkR4PB5b/view?usp=sharing'' </blockquote> <br />
<br />
In order to properly guide the driver, some sort of compound guidance such as ''<code>Use the right of the two left turn lanes to turn left and then turn right to I-680 North Sacramento</code>'' would be ideal. <br />
<br />
'''Loss and re-gain of lane between 2 intersections'''<br />
<br />
There are intersections where a lane is lost to a dedicated turn lane, and yet, by the next intersection, a lane is re-added. A driver following the lane guidance could mistakenly enter the dedicated turn lane prematurely and may be forced to take the earlier turn. <br />
<br />
Consider a driver on [https://www.waze.com/en-US/editor/?env=usa&lon=-121.92340&lat=37.49481&zoom=6 Mission Boulevard being guided to northbound I-680]. There are 3 full lanes at the on-ramp to northbound I-680 with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1WAUh2UMG3NKWgAawNvt-ELKaMko5va6p/view?usp=sharing'' </blockquote>At the prior on-ramp to southbound I-680, there are also 3 full lanes at the on-ramp with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1pKWKjd59aFBNb4ROoViban5_5pPWkgSu/view?usp=sharing'' </blockquote>Note that since Lane Guidance is announced about ½ mile for MH (and ¼ mile for mH and lower) prior to the turn instruction, the driver would have heard ''<code>In ½ mile, use the right lane to turn right to I-680 North Sacramento</code>'' at around Warm Springs Boulevard, which is 2 signaled intersections prior to the entrance to northbound I-680. There is no signage that the right lane ends until you are almost at the entrance to southbound I-680. A driver unfamiliar with the area, upon seeing or hearing the guidance, would get into the right lane. By the time the driver realizes that the lane is a dedicated lane to I-680 South, not North, there isn't much distance left to change lanes, especially when there is a lot of traffic in the next lane.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1uAPd_q-O7VRhYnAtGuvskjHI1Uf3qcqr/view?usp=sharing''</blockquote>In order to properly guide the driver, there are a few possibilities. Waze could delay announcing the Turn instruction to northbound I-680 until the driver is past the entrance to southbound I-680. A more ideal solution would be for Waze to announce ''<code>In ½ mile, stay in the middle lane and then turn right to I-680 North Sacramento</code>''. <br />
<br />
'''What should be done in these situations?'''<br />
<br />
*Lanes should not be mapped at such intersections<br />
*Place a Map Comment so that future editors can locate these locations if Waze enhances the Lane Guidance feature to make mapping these locations possible. Adding a Map Comment could be used as a notification to current editors that the intersection has been reviewed and Lane Guidance should not be added until such time these enhancements are available.<br />
<br />
<br /></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Abc1357/LG&diff=176223User:Abc1357/LG2022-06-25T20:35:10Z<p>Tonestertm: /* At-Grade Connectors */</p>
<hr />
<div>=='''<big>Lanes</big>'''==<br />
''General details on Lanes and how to map them can be found on the [[Lanes|Lanes Wazeopedia page]]. Editors should consider using the [https://www.waze.com/forum/viewtopic.php?f=819&t=301158 Lane Tools script] to assist in mapping lanes correctly.''<br />
<br />
In California, we use a "Common Sense" approach to guidance. Lanes should be mapped for major intersections where the number of turn lanes deviates from what is expected. In other words, do not map Lane Guidance if you can turn right only from the right lane and/or you can turn left only from the left lane, regardless of whether these lanes are dedicated turn lanes or shared lanes.<br />
<br />
'''Intersections where you should map Lanes*:'''<br />
<br />
*Intersections that have two or more lanes to turn left or right.<br />
*Complex intersections where [[usa:Lanes#To_clarify_which_road_to_take|clarification of which road to take is necessary]]<br />
<br />
*In a # or H junction where there is a U-Turn, even if there is only a single left turn lane. The addition of Lanes to these intersections combined with lane heuristics enables Waze to announce a ''<code>U-Turn</code>,'' rather than a ''<code>Turn Left, Turn Left</code>''.<br />
**Verify that the parallel segments are almost parallel (i.e. sum of angles with the cross segment should be between 175° and 185°), and the angle with the cross segment should be close to 90°.<br />
**Check that there is not a parallel segment within 50m (165 ft) to the left of the segment with a single perpendicular segment connecting them. Waze heuristics could interpret that to be a U-Turn. Use a Junction Node to "break up" the median segment, and add a map comment close by to indicate why the junction is there. ''Put in a picture of Clarie Drive in Pleasant Hill'' https://www.waze.com/en-US/editor/?env=usa&lon=-122.05663&lat=37.94113&zoom=8&segments=522544024,522544023<br />
*Use the <code>[[usa:Lanes#.22View_and_hear.22_continue_straight|View and Hear]]</code> or <code>[[usa:Lanes#.22View_only.22_continue_straight|View Only]]</code> continue straight overrides where necessary<br />
<br />
<br />''* Before mapping Lanes at any intersection, review prior intersections to ensure adding Lanes at that intersection do not inadvertently cause confusion for the driver (see '''Compound Guidance needed''' section below).''<br />
<br />
<br /><br />
==='''Special Considerations'''===<br />
<br /><br />
<br />
====''At-Grade Connectors''====<br />
When reviewing intersections prior to adding Lanes, please consider whether AGCs are still needed at that intersection.<br />
<br />
For example, the AGC from westbound Walsh Avenue to northbound San Tomas Expressway is not needed. The island is extremely small. The benefits that the AGC was originally meant for, such as advanced announcement of the turn, are not needed.<blockquote>''Picture here (not uploaded to Wazeopedia yet): [https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=]''[https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing sharing]</blockquote>'''What should be done in this situation?'''<br />
<br />
*Remove the AGC and any excess Junction Nodes<br />
*Check to ensure Turn Restrictions are correct for the intersection<br />
*Add Lanes, if needed<br />
<br />
<br /><br />
<br />
====''Compound Guidance needed''====<br />
Compound guidance is the concept where a driver should be directed to a specific lane or set of lanes at a prior intersection to ensure that the driver is in position to perform the turn maneuver. Unfortunately, Waze does not yet support compound guidance.<br />
<br />
'''Lane specific guidance'''<br />
<br />
There are intersections where users should be guided to the proper lane in preparation for the next maneuver.<br />
<br />
Consider a driver going from Crow Canyon Place to I-680 North. There are 2 left turn lanes on Crow Canyon Place. An editor following lane mapping guidance would map that intersection with 2 left turns. A driver unfamiliar with that area could potentially be using the left lane of the 2 left turn lanes to turn into the left lanes on Crow Canyon Road and not be able to enter the on-ramp to I-680 North, if there is a lot of traffic blocking the movement to the right lanes in the short distance available.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1fyevKStP0wqiyM5XalC46GimBkR4PB5b/view?usp=sharing'' </blockquote> <br />
<br />
In order to properly guide the driver, some sort of compound guidance such as ''<code>Use the right of the two left turn lanes to turn left and then turn right to I-680 North Sacramento</code>'' would be ideal. <br />
<br />
'''Loss and re-gain of lane between 2 intersections'''<br />
<br />
There are intersections where a lane is lost to a dedicated turn lane, and yet, by the next intersection, a lane is re-added. A driver following the lane guidance could mistakenly enter the dedicated turn lane prematurely and may be forced to take the earlier turn. <br />
<br />
Consider a driver on [https://www.waze.com/en-US/editor/?env=usa&lon=-121.92340&lat=37.49481&zoom=6 Mission Boulevard being guided to northbound I-680]. There are 3 full lanes at the on-ramp to northbound I-680 with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1WAUh2UMG3NKWgAawNvt-ELKaMko5va6p/view?usp=sharing'' </blockquote>At the prior on-ramp to southbound I-680, there are also 3 full lanes at the on-ramp with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1pKWKjd59aFBNb4ROoViban5_5pPWkgSu/view?usp=sharing'' </blockquote>Note that since Lane Guidance is announced about ½ mile for MH (and ¼ mile for mH and lower) prior to the turn instruction, the driver would have heard ''<code>In ½ mile, use the right lane to turn right to I-680 North Sacramento</code>'' at around Warm Springs Boulevard, which is 2 signaled intersections prior to the entrance to northbound I-680. There is no signage that the right lane ends until you are almost at the entrance to southbound I-680. A driver unfamiliar with the area, upon seeing or hearing the guidance, would get into the right lane. By the time the driver realizes that the lane is a dedicated lane to I-680 South, not North, there isn't much distance left to change lanes, especially when there is a lot of traffic in the next lane.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1uAPd_q-O7VRhYnAtGuvskjHI1Uf3qcqr/view?usp=sharing''</blockquote>In order to properly guide the driver, there are a few possibilities. Waze could delay announcing the Turn instruction to northbound I-680 until the driver is past the entrance to southbound I-680. A more ideal solution would be for Waze to announce ''<code>In ½ mile, stay in the middle lane and then turn right to I-680 North Sacramento</code>''. <br />
<br />
'''What should be done in these situations?'''<br />
<br />
*Lanes should not be mapped at such intersections<br />
*Place a Map Comment so that future editors can locate these locations if Waze enhances the Lane Guidance feature to make mapping these locations possible. Adding a Map Comment could be used as a notification to current editors that the intersection has been reviewed and Lane Guidance should not be added until such time these enhancements are available.<br />
<br />
<br /></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Abc1357/LG&diff=176222User:Abc1357/LG2022-06-25T20:21:24Z<p>Tonestertm: /* Lanes */</p>
<hr />
<div>=='''<big>Lanes</big>'''==<br />
''General details on Lanes and how to map them can be found on the [[Lanes|Lanes Wazeopedia page]]. Editors should consider using the [https://www.waze.com/forum/viewtopic.php?f=819&t=301158 Lane Tools script] to assist in mapping lanes correctly.''<br />
<br />
In California, we use a "Common Sense" approach to guidance. Lanes should be mapped for major intersections where the number of turn lanes deviates from what is expected. In other words, do not map Lane Guidance if you can turn right only from the right lane and/or you can turn left only from the left lane, regardless of whether these lanes are dedicated turn lanes or shared lanes.<br />
<br />
'''Intersections where you should map Lanes*:'''<br />
<br />
*Intersections that have two or more lanes to turn left or right.<br />
*Complex intersections where [[usa:Lanes#To_clarify_which_road_to_take|clarification of which road to take is necessary]]<br />
<br />
*In a # or H junction where there is a U-Turn, even if there is only a single left turn lane. The addition of Lanes to these intersections combined with lane heuristics enables Waze to announce a ''<code>U-Turn</code>,'' rather than a ''<code>Turn Left, Turn Left</code>''.<br />
**Verify that the parallel segments are almost parallel (i.e. sum of angles with the cross segment should be between 175° and 185°), and the angle with the cross segment should be close to 90°.<br />
**Check that there is not a parallel segment within 50m (165 ft) to the left of the segment with a single perpendicular segment connecting them. Waze heuristics could interpret that to be a U-Turn. Use a Junction Node to "break up" the median segment, and add a map comment close by to indicate why the junction is there. ''Put in a picture of Clarie Drive in Pleasant Hill'' https://www.waze.com/en-US/editor/?env=usa&lon=-122.05663&lat=37.94113&zoom=8&segments=522544024,522544023<br />
*Use the <code>[[usa:Lanes#.22View_and_hear.22_continue_straight|View and Hear]]</code> or <code>[[usa:Lanes#.22View_only.22_continue_straight|View Only]]</code> continue straight overrides where necessary<br />
<br />
<br />''* Before mapping Lanes at any intersection, review prior intersections to ensure adding Lanes at that intersection do not inadvertently cause confusion for the driver (see '''Compound Guidance needed''' section below).''<br />
<br />
<br /><br />
==='''Special Considerations'''===<br />
<br /><br />
<br />
====''At-Grade Connectors''====<br />
When reviewing intersections prior to adding Lanes, please consider whether AGCs are still needed at that intersection.<br />
<br />
For example, the AGC from westbound Walsh Avenue to northbound San Tomas Expressway is not needed. The island is extremely small. The benefits that the AGC was originally meant for, such as advanced announcement of the turn, are not needed.<blockquote>''Picture here (not uploaded to Wazeopedia yet): [https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=]''[https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing sharing]</blockquote>'''What should be done in this situation?'''<br />
<br />
*Remove the AGC and excess Junction Nodes<br />
*Check to ensure Turn Restrictions are correct for the intersection<br />
*Add Lanes, if needed<br />
<br />
<br /><br />
====''Compound Guidance needed''====<br />
Compound guidance is the concept where a driver should be directed to a specific lane or set of lanes at a prior intersection to ensure that the driver is in position to perform the turn maneuver. Unfortunately, Waze does not yet support compound guidance.<br />
<br />
'''Lane specific guidance'''<br />
<br />
There are intersections where users should be guided to the proper lane in preparation for the next maneuver.<br />
<br />
Consider a driver going from Crow Canyon Place to I-680 North. There are 2 left turn lanes on Crow Canyon Place. An editor following lane mapping guidance would map that intersection with 2 left turns. A driver unfamiliar with that area could potentially be using the left lane of the 2 left turn lanes to turn into the left lanes on Crow Canyon Road and not be able to enter the on-ramp to I-680 North, if there is a lot of traffic blocking the movement to the right lanes in the short distance available.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1fyevKStP0wqiyM5XalC46GimBkR4PB5b/view?usp=sharing'' </blockquote> <br />
<br />
In order to properly guide the driver, some sort of compound guidance such as ''<code>Use the right of the two left turn lanes to turn left and then turn right to I-680 North Sacramento</code>'' would be ideal. <br />
<br />
'''Loss and re-gain of lane between 2 intersections'''<br />
<br />
There are intersections where a lane is lost to a dedicated turn lane, and yet, by the next intersection, a lane is re-added. A driver following the lane guidance could mistakenly enter the dedicated turn lane prematurely and may be forced to take the earlier turn. <br />
<br />
Consider a driver on [https://www.waze.com/en-US/editor/?env=usa&lon=-121.92340&lat=37.49481&zoom=6 Mission Boulevard being guided to northbound I-680]. There are 3 full lanes at the on-ramp to northbound I-680 with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1WAUh2UMG3NKWgAawNvt-ELKaMko5va6p/view?usp=sharing'' </blockquote>At the prior on-ramp to southbound I-680, there are also 3 full lanes at the on-ramp with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1pKWKjd59aFBNb4ROoViban5_5pPWkgSu/view?usp=sharing'' </blockquote>Note that since Lane Guidance is announced about ½ mile for MH (and ¼ mile for mH and lower) prior to the turn instruction, the driver would have heard ''<code>In ½ mile, use the right lane to turn right to I-680 North Sacramento</code>'' at around Warm Springs Boulevard, which is 2 signaled intersections prior to the entrance to northbound I-680. There is no signage that the right lane ends until you are almost at the entrance to southbound I-680. A driver unfamiliar with the area, upon seeing or hearing the guidance, would get into the right lane. By the time the driver realizes that the lane is a dedicated lane to I-680 South, not North, there isn't much distance left to change lanes, especially when there is a lot of traffic in the next lane.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1uAPd_q-O7VRhYnAtGuvskjHI1Uf3qcqr/view?usp=sharing''</blockquote>In order to properly guide the driver, there are a few possibilities. Waze could delay announcing the Turn instruction to northbound I-680 until the driver is past the entrance to southbound I-680. A more ideal solution would be for Waze to announce ''<code>In ½ mile, stay in the middle lane and then turn right to I-680 North Sacramento</code>''. <br />
<br />
'''What should be done in these situations?'''<br />
<br />
*Lanes should not be mapped at such intersections<br />
*Place a Map Comment so that future editors can locate these locations if Waze enhances the Lane Guidance feature to make mapping these locations possible. Adding a Map Comment could be used as a notification to current editors that the intersection has been reviewed and Lane Guidance should not be added until such time these enhancements are available.<br />
<br />
<br /></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Abc1357/LG&diff=176221User:Abc1357/LG2022-06-25T20:06:58Z<p>Tonestertm: /* Lanes */</p>
<hr />
<div>=='''<big>Lanes</big>'''==<br />
''General details on Lanes and how to map them can be found on the [[Lanes|Lanes Wazeopedia page]]. Editors should consider using the [https://www.waze.com/forum/viewtopic.php?f=819&t=301158 Lane Tools script] to assist in mapping lanes correctly.''<br />
<br />
In California, we use a "Common Sense" approach to guidance. Lanes should be mapped for major intersections where the number of turn lanes deviates from what is expected. In other words, do not map Lane Guidance if you can turn right only from the right lane and/or you can turn left only from the left lane, regardless of whether these lanes are dedicated turn lanes or shared lanes.<br />
<br />
'''Intersections where you should map Lanes*:'''<br />
<br />
*Intersections that have two or more lanes to turn left or right.<br />
*Complex intersections where [[usa:Lanes#To_clarify_which_road_to_take|clarification of which road to take is necessary]]<br />
<br />
*In a # or H junction where there is a U-Turn, even if there is only a single left turn lane. The addition of Lanes to these intersections combined with lane heuristics enables Waze to announce a ''<code>U-Turn</code>,'' rather than a ''<code>Turn Left, Turn Left</code>''.<br />
**Verify that the parallel segments are almost parallel (i.e. sum of angles with the cross segment should be between 175° and 185°), and the angle with the cross segment should be close to 90°.<br />
**Check that there is not a parallel segment within 50m (165 ft) to the left of the segment with a single perpendicular segment connecting them. Waze heuristics could interpret that to be a U-Turn. Use a Junction Node to "break up" the median segment. ''Put in a picture of Clarie Drive in Pleasant Hill'' https://www.waze.com/en-US/editor/?env=usa&lon=-122.05663&lat=37.94113&zoom=8&segments=522544024,522544023<br />
*Use the <code>[[usa:Lanes#.22View_and_hear.22_continue_straight|View and Hear]]</code> or <code>[[usa:Lanes#.22View_only.22_continue_straight|View Only]]</code> continue straight overrides where necessary<br />
<br />
<br />''* Before mapping Lanes at any intersection, review prior intersections to ensure adding Lanes at that intersection do not inadvertently cause confusion for the driver (see '''Compound Guidance needed''' section below).''<br />
<br />
<br /><br />
==='''Special Considerations'''===<br />
<br /><br />
<br />
====''At-Grade Connectors''====<br />
When reviewing intersections prior to adding Lanes, please consider whether AGCs are still needed at that intersection.<br />
<br />
For example, the AGC from westbound Walsh Avenue to northbound San Tomas Expressway is not needed. The island is extremely small. The benefits that the AGC was originally meant for, such as advanced announcement of the turn, are not needed.<blockquote>''Picture here (not uploaded to Wazeopedia yet): [https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=]''[https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing sharing]</blockquote>'''What should be done in this situation?'''<br />
<br />
*Remove the AGC and excess Junction Nodes<br />
*Check to ensure Turn Restrictions are correct for the intersection<br />
*Add Lanes, if needed<br />
<br />
<br /><br />
====''Compound Guidance needed''====<br />
Compound guidance is the concept where a driver should be directed to a specific lane or set of lanes at a prior intersection to ensure that the driver is in position to perform the turn maneuver. Unfortunately, Waze does not yet support compound guidance.<br />
<br />
'''Lane specific guidance'''<br />
<br />
There are intersections where users should be guided to the proper lane in preparation for the next maneuver.<br />
<br />
Consider a driver going from Crow Canyon Place to I-680 North. There are 2 left turn lanes on Crow Canyon Place. An editor following lane mapping guidance would map that intersection with 2 left turns. A driver unfamiliar with that area could potentially be using the left lane of the 2 left turn lanes to turn into the left lanes on Crow Canyon Road and not be able to enter the on-ramp to I-680 North, if there is a lot of traffic blocking the movement to the right lanes in the short distance available.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1fyevKStP0wqiyM5XalC46GimBkR4PB5b/view?usp=sharing'' </blockquote> <br />
<br />
In order to properly guide the driver, some sort of compound guidance such as ''<code>Use the right of the two left turn lanes to turn left and then turn right to I-680 North Sacramento</code>'' would be ideal. <br />
<br />
'''Loss and re-gain of lane between 2 intersections'''<br />
<br />
There are intersections where a lane is lost to a dedicated turn lane, and yet, by the next intersection, a lane is re-added. A driver following the lane guidance could mistakenly enter the dedicated turn lane prematurely and may be forced to take the earlier turn. <br />
<br />
Consider a driver on [https://www.waze.com/en-US/editor/?env=usa&lon=-121.92340&lat=37.49481&zoom=6 Mission Boulevard being guided to northbound I-680]. There are 3 full lanes at the on-ramp to northbound I-680 with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1WAUh2UMG3NKWgAawNvt-ELKaMko5va6p/view?usp=sharing'' </blockquote>At the prior on-ramp to southbound I-680, there are also 3 full lanes at the on-ramp with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1pKWKjd59aFBNb4ROoViban5_5pPWkgSu/view?usp=sharing'' </blockquote>Note that since Lane Guidance is announced about ½ mile for MH (and ¼ mile for mH and lower) prior to the turn instruction, the driver would have heard ''<code>In ½ mile, use the right lane to turn right to I-680 North Sacramento</code>'' at around Warm Springs Boulevard, which is 2 signaled intersections prior to the entrance to northbound I-680. There is no signage that the right lane ends until you are almost at the entrance to southbound I-680. A driver unfamiliar with the area, upon seeing or hearing the guidance, would get into the right lane. By the time the driver realizes that the lane is a dedicated lane to I-680 South, not North, there isn't much distance left to change lanes, especially when there is a lot of traffic in the next lane.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1uAPd_q-O7VRhYnAtGuvskjHI1Uf3qcqr/view?usp=sharing''</blockquote>In order to properly guide the driver, there are a few possibilities. Waze could delay announcing the Turn instruction to northbound I-680 until the driver is past the entrance to southbound I-680. A more ideal solution would be for Waze to announce ''<code>In ½ mile, stay in the middle lane and then turn right to I-680 North Sacramento</code>''. <br />
<br />
'''What should be done in these situations?'''<br />
<br />
*Lanes should not be mapped at such intersections<br />
*Place a Map Comment so that future editors can locate these locations if Waze enhances the Lane Guidance feature to make mapping these locations possible. Adding a Map Comment could be used as a notification to current editors that the intersection has been reviewed and Lane Guidance should not be added until such time these enhancements are available.<br />
<br />
<br /></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Abc1357/LG&diff=176220User:Abc1357/LG2022-06-25T20:01:23Z<p>Tonestertm: </p>
<hr />
<div>=='''<big>Lanes</big>'''==<br />
''General details on Lanes and how to map them can be found on the [[Lanes|Lanes Wazeopedia page]]. Editors should consider using the [https://www.waze.com/forum/viewtopic.php?f=819&t=301158 Lane Tools script] to assist in mapping lanes correctly.''<br />
<br />
In California, we use a "Common Sense" approach to guidance. Lanes should be mapped for major intersections where the number of turn lanes deviates from what is expected. In other words, do not map Lane Guidance if you can turn right only from the right lane and/or you can turn left only from the left lane, regardless of whether these lanes are dedicated turn lanes or shared lanes.<br />
<br />
'''Intersections where you should map Lanes*:'''<br />
<br />
*Intersections that have two or more lanes to turn left or right.<br />
*Complex intersections where [[usa:Lanes#To_clarify_which_road_to_take|clarification of which road to take is necessary]]<br />
<br />
*In a # or H junction where there is a U-Turn, even if there is only a single left turn lane. The addition of Lanes to these intersections combined with lane heuristics enables Waze to announce a ''<code>U-Turn</code>,'' rather than a ''<code>Turn Left, Turn Left</code>''.<br />
**Verify that the parallel segments are almost parallel (i.e. sum of angles with the cross segment should be between 175° and 185°), and the angle with the cross segment should be close to 90°.<br />
**Check that there is not a parallel segment within 50m (165 ft) to the left of the segment with a single perpendicular segment connecting them. Waze heuristics could interpret that to be U-Turn. Use a Junction Node to "break up" the median segment. ''Put in a picture of Clarie Drive in Pleasant Hill'' https://www.waze.com/en-US/editor/?env=usa&lon=-122.05663&lat=37.94113&zoom=8&segments=522544024,522544023<br />
*Use the <code>[[usa:Lanes#.22View_and_hear.22_continue_straight|View and Hear]]</code> or <code>[[usa:Lanes#.22View_only.22_continue_straight|View Only]]</code> continue straight overrides where necessary<br />
<br />
<br />''* Before mapping Lanes at any intersection, review prior intersections to ensure adding Lanes at that intersection do not inadvertently cause confusion for the driver (see '''Compound Guidance needed''' section below).''<br />
<br />
<br /><br />
==='''Special Considerations'''===<br />
<br /><br />
<br />
====''At-Grade Connectors''====<br />
When reviewing intersections prior to adding Lanes, please consider whether AGCs are still needed at that intersection.<br />
<br />
For example, the AGC from westbound Walsh Avenue to northbound San Tomas Expressway is not needed. The island is extremely small. The benefits that the AGC was originally meant for, such as advanced announcement of the turn, are not needed.<blockquote>''Picture here (not uploaded to Wazeopedia yet): [https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=]''[https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing sharing]</blockquote>'''What should be done in this situation?'''<br />
<br />
*Remove the AGC and excess Junction Nodes<br />
*Check to ensure Turn Restrictions are correct for the intersection<br />
*Add Lanes, if needed<br />
<br />
<br /><br />
====''Compound Guidance needed''====<br />
Compound guidance is the concept where a driver should be directed to a specific lane or set of lanes at a prior intersection to ensure that the driver is in position to perform the turn maneuver. Unfortunately, Waze does not yet support compound guidance.<br />
<br />
'''Lane specific guidance'''<br />
<br />
There are intersections where users should be guided to the proper lane in preparation for the next maneuver.<br />
<br />
Consider a driver going from Crow Canyon Place to I-680 North. There are 2 left turn lanes on Crow Canyon Place. An editor following lane mapping guidance would map that intersection with 2 left turns. A driver unfamiliar with that area could potentially be using the left lane of the 2 left turn lanes to turn into the left lanes on Crow Canyon Road and not be able to enter the on-ramp to I-680 North, if there is a lot of traffic blocking the movement to the right lanes in the short distance available.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1fyevKStP0wqiyM5XalC46GimBkR4PB5b/view?usp=sharing'' </blockquote> <br />
<br />
In order to properly guide the driver, some sort of compound guidance such as ''<code>Use the right of the two left turn lanes to turn left and then turn right to I-680 North Sacramento</code>'' would be ideal. <br />
<br />
'''Loss and re-gain of lane between 2 intersections'''<br />
<br />
There are intersections where a lane is lost to a dedicated turn lane, and yet, by the next intersection, a lane is re-added. A driver following the lane guidance could mistakenly enter the dedicated turn lane prematurely and may be forced to take the earlier turn. <br />
<br />
Consider a driver on [https://www.waze.com/en-US/editor/?env=usa&lon=-121.92340&lat=37.49481&zoom=6 Mission Boulevard being guided to northbound I-680]. There are 3 full lanes at the on-ramp to northbound I-680 with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1WAUh2UMG3NKWgAawNvt-ELKaMko5va6p/view?usp=sharing'' </blockquote>At the prior on-ramp to southbound I-680, there are also 3 full lanes at the on-ramp with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1pKWKjd59aFBNb4ROoViban5_5pPWkgSu/view?usp=sharing'' </blockquote>Note that since Lane Guidance is announced about ½ mile for MH (and ¼ mile for mH and lower) prior to the turn instruction, the driver would have heard ''<code>In ½ mile, use the right lane to turn right to I-680 North Sacramento</code>'' at around Warm Springs Boulevard, which is 2 signaled intersections prior to the entrance to northbound I-680. There is no signage that the right lane ends until you are almost at the entrance to southbound I-680. A driver unfamiliar with the area, upon seeing or hearing the guidance, would get into the right lane. By the time the driver realizes that the lane is a dedicated lane to I-680 South, not North, there isn't much distance left to change lanes, especially when there is a lot of traffic in the next lane.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1uAPd_q-O7VRhYnAtGuvskjHI1Uf3qcqr/view?usp=sharing''</blockquote>In order to properly guide the driver, there are a few possibilities. Waze could delay announcing the Turn instruction to northbound I-680 until the driver is past the entrance to southbound I-680. A more ideal solution would be for Waze to announce ''<code>In ½ mile, stay in the middle lane and then turn right to I-680 North Sacramento</code>''. <br />
<br />
'''What should be done in these situations?'''<br />
<br />
*Lanes should not be mapped at such intersections<br />
*Place a Map Comment so that future editors can locate these locations if Waze enhances the Lane Guidance feature to make mapping these locations possible. Adding a Map Comment could be used as a notification to current editors that the intersection has been reviewed and Lane Guidance should not be added until such time these enhancements are available.<br />
<br />
<br /></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Abc1357/LG&diff=176219User:Abc1357/LG2022-06-25T20:00:35Z<p>Tonestertm: Common sense</p>
<hr />
<div>=='''<big>Lanes</big>'''==<br />
''General details on Lanes and how to map them can be found on the [[Lanes|Lanes Wazeopedia page]]. Editors should consider using the [https://www.waze.com/forum/viewtopic.php?f=819&t=301158 Lane Tools script] to assist in mapping lanes correctly.''<br />
<br />
In California, we use a "Common Sense" approach to guidance. Lanes should be mapped for major intersections where the number of turn lanes deviates from what is expected. In other words, do not map if you can turn right only from the right lane and/or you can turn left only from the left lane, regardless of whether these lanes are dedicated turn lanes or shared lanes.<br />
<br />
'''Intersections where you should map Lanes*:'''<br />
<br />
*Intersections that have two or more lanes to turn left or right.<br />
*Complex intersections where [[usa:Lanes#To_clarify_which_road_to_take|clarification of which road to take is necessary]]<br />
<br />
*In a # or H junction where there is a U-Turn, even if there is only a single left turn lane. The addition of Lanes to these intersections combined with lane heuristics enables Waze to announce a ''<code>U-Turn</code>,'' rather than a ''<code>Turn Left, Turn Left</code>''.<br />
**Verify that the parallel segments are almost parallel (i.e. sum of angles with the cross segment should be between 175° and 185°), and the angle with the cross segment should be close to 90°.<br />
**Check that there is not a parallel segment within 50m (165 ft) to the left of the segment with a single perpendicular segment connecting them. Waze heuristics could interpret that to be U-Turn. Use a Junction Node to "break up" the median segment. ''Put in a picture of Clarie Drive in Pleasant Hill'' https://www.waze.com/en-US/editor/?env=usa&lon=-122.05663&lat=37.94113&zoom=8&segments=522544024,522544023<br />
*Use the <code>[[usa:Lanes#.22View_and_hear.22_continue_straight|View and Hear]]</code> or <code>[[usa:Lanes#.22View_only.22_continue_straight|View Only]]</code> continue straight overrides where necessary<br />
<br />
<br />''* Before mapping Lanes at any intersection, review prior intersections to ensure adding Lanes at that intersection do not inadvertently cause confusion for the driver (see '''Compound Guidance needed''' section below).''<br />
<br />
<br /><br />
==='''Special Considerations'''===<br />
<br /><br />
<br />
====''At-Grade Connectors''====<br />
When reviewing intersections prior to adding Lanes, please consider whether AGCs are still needed at that intersection.<br />
<br />
For example, the AGC from westbound Walsh Avenue to northbound San Tomas Expressway is not needed. The island is extremely small. The benefits that the AGC was originally meant for, such as advanced announcement of the turn, are not needed.<blockquote>''Picture here (not uploaded to Wazeopedia yet): [https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=]''[https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing sharing]</blockquote>'''What should be done in this situation?'''<br />
<br />
*Remove the AGC and excess Junction Nodes<br />
*Check to ensure Turn Restrictions are correct for the intersection<br />
*Add Lanes, if needed<br />
<br />
<br /><br />
====''Compound Guidance needed''====<br />
Compound guidance is the concept where a driver should be directed to a specific lane or set of lanes at a prior intersection to ensure that the driver is in position to perform the turn maneuver. Unfortunately, Waze does not yet support compound guidance.<br />
<br />
'''Lane specific guidance'''<br />
<br />
There are intersections where users should be guided to the proper lane in preparation for the next maneuver.<br />
<br />
Consider a driver going from Crow Canyon Place to I-680 North. There are 2 left turn lanes on Crow Canyon Place. An editor following lane mapping guidance would map that intersection with 2 left turns. A driver unfamiliar with that area could potentially be using the left lane of the 2 left turn lanes to turn into the left lanes on Crow Canyon Road and not be able to enter the on-ramp to I-680 North, if there is a lot of traffic blocking the movement to the right lanes in the short distance available.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1fyevKStP0wqiyM5XalC46GimBkR4PB5b/view?usp=sharing'' </blockquote> <br />
<br />
In order to properly guide the driver, some sort of compound guidance such as ''<code>Use the right of the two left turn lanes to turn left and then turn right to I-680 North Sacramento</code>'' would be ideal. <br />
<br />
'''Loss and re-gain of lane between 2 intersections'''<br />
<br />
There are intersections where a lane is lost to a dedicated turn lane, and yet, by the next intersection, a lane is re-added. A driver following the lane guidance could mistakenly enter the dedicated turn lane prematurely and may be forced to take the earlier turn. <br />
<br />
Consider a driver on [https://www.waze.com/en-US/editor/?env=usa&lon=-121.92340&lat=37.49481&zoom=6 Mission Boulevard being guided to northbound I-680]. There are 3 full lanes at the on-ramp to northbound I-680 with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1WAUh2UMG3NKWgAawNvt-ELKaMko5va6p/view?usp=sharing'' </blockquote>At the prior on-ramp to southbound I-680, there are also 3 full lanes at the on-ramp with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1pKWKjd59aFBNb4ROoViban5_5pPWkgSu/view?usp=sharing'' </blockquote>Note that since Lane Guidance is announced about ½ mile for MH (and ¼ mile for mH and lower) prior to the turn instruction, the driver would have heard ''<code>In ½ mile, use the right lane to turn right to I-680 North Sacramento</code>'' at around Warm Springs Boulevard, which is 2 signaled intersections prior to the entrance to northbound I-680. There is no signage that the right lane ends until you are almost at the entrance to southbound I-680. A driver unfamiliar with the area, upon seeing or hearing the guidance, would get into the right lane. By the time the driver realizes that the lane is a dedicated lane to I-680 South, not North, there isn't much distance left to change lanes, especially when there is a lot of traffic in the next lane.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1uAPd_q-O7VRhYnAtGuvskjHI1Uf3qcqr/view?usp=sharing''</blockquote>In order to properly guide the driver, there are a few possibilities. Waze could delay announcing the Turn instruction to northbound I-680 until the driver is past the entrance to southbound I-680. A more ideal solution would be for Waze to announce ''<code>In ½ mile, stay in the middle lane and then turn right to I-680 North Sacramento</code>''. <br />
<br />
'''What should be done in these situations?'''<br />
<br />
*Lanes should not be mapped at such intersections<br />
*Place a Map Comment so that future editors can locate these locations if Waze enhances the Lane Guidance feature to make mapping these locations possible. Adding a Map Comment could be used as a notification to current editors that the intersection has been reviewed and Lane Guidance should not be added until such time these enhancements are available.<br />
<br />
<br /></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Abc1357/LG&diff=176060User:Abc1357/LG2022-06-02T17:18:39Z<p>Tonestertm: /* Lanes */</p>
<hr />
<div>=='''<big>Lanes</big>'''==<br />
''General details on Lanes and how to map them can be found on the [[Lanes|Lanes Wazeopedia page]]. Editors should consider using the [https://www.waze.com/forum/viewtopic.php?f=819&t=301158 Lane Tools script] to assist in mapping lanes correctly.''<br />
<br />
In California, Lanes should be mapped for major intersections where the number of turn lanes deviates from what is expected. In other words, do not map if you can turn right only from the right lane and/or you can turn left only from the left lane, regardless of whether these lanes are dedicated turn lanes or shared lanes.<br />
<br />
'''Intersections where you should map Lanes*:'''<br />
<br />
*Intersections that have two or more lanes to turn left or right.<br />
*Complex intersections where [[usa:Lanes#To_clarify_which_road_to_take|clarification of which road to take is necessary]]<br />
<br />
*In a # or H junction where there is a U-Turn, even if there is only a single left turn lane. The addition of Lanes to these intersections combined with lane heuristics enables Waze to announce a ''<code>U-Turn</code>,'' rather than a ''<code>Turn Left, Turn Left</code>''.<br />
**Verify that the parallel segments are almost parallel (i.e. sum of angles with the cross segment should be between 175° and 185°), and the angle with the cross segment should be close to 90°.<br />
**Check that there is not a parallel segment within 50m (165 ft) to the left of the segment with a single perpendicular segment connecting them. Waze heuristics could interpret that to be U-Turn. Use a Junction Node to "break up" the median segment. ''Put in a picture of Clarie Drive in Pleasant Hill'' https://www.waze.com/en-US/editor/?env=usa&lon=-122.05663&lat=37.94113&zoom=8&segments=522544024,522544023<br />
*Use the <code>[[usa:Lanes#.22View_and_hear.22_continue_straight|View and Hear]]</code> or <code>[[usa:Lanes#.22View_only.22_continue_straight|View Only]]</code> continue straight overrides where necessary<br />
<br />
<br />''* Before mapping Lanes at any intersection, review prior intersections to ensure adding Lanes at that intersection do not inadvertently cause confusion for the driver (see '''Compound Guidance needed''' section below).''<br />
<br />
<br /><br />
==='''Special Considerations'''===<br />
<br /><br />
<br />
====''At-Grade Connectors''====<br />
When reviewing intersections prior to adding Lanes, please consider whether AGCs are still needed at that intersection.<br />
<br />
For example, the AGC from westbound Walsh Avenue to northbound San Tomas Expressway is not needed. The island is extremely small. The benefits that the AGC was originally meant for, such as advanced announcement of the turn, are not needed.<blockquote>''Picture here (not uploaded to Wazeopedia yet): [https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=]''[https://drive.google.com/file/d/1a-Iif-n8G-cW0yQEbR1n0SBz9_Qpia_q/view?usp=sharing sharing]</blockquote>'''What should be done in this situation?'''<br />
<br />
*Remove the AGC and excess Junction Nodes<br />
*Check to ensure Turn Restrictions are correct for the intersection<br />
*Add Lanes, if needed<br />
<br />
<br /><br />
====''Compound Guidance needed''====<br />
Compound guidance is the concept where a driver should be directed to a specific lane or set of lanes at a prior intersection to ensure that the driver is in position to perform the turn maneuver. Unfortunately, Waze does not yet support compound guidance.<br />
<br />
'''Lane specific guidance'''<br />
<br />
There are intersections where users should be guided to the proper lane in preparation for the next maneuver.<br />
<br />
Consider a driver going from Crow Canyon Place to I-680 North. There are 2 left turn lanes on Crow Canyon Place. An editor following lane mapping guidance would map that intersection with 2 left turns. A driver unfamiliar with that area could potentially be using the left lane of the 2 left turn lanes to turn into the left lanes on Crow Canyon Road and not be able to enter the on-ramp to I-680 North, if there is a lot of traffic blocking the movement to the right lanes in the short distance available.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1fyevKStP0wqiyM5XalC46GimBkR4PB5b/view?usp=sharing'' </blockquote> <br />
<br />
In order to properly guide the driver, some sort of compound guidance such as ''<code>Use the right of the two left turn lanes to turn left and then turn right to I-680 North Sacramento</code>'' would be ideal. <br />
<br />
'''Loss and re-gain of lane between 2 intersections'''<br />
<br />
There are intersections where a lane is lost to a dedicated turn lane, and yet, by the next intersection, a lane is re-added. A driver following the lane guidance could mistakenly enter the dedicated turn lane prematurely and may be forced to take the earlier turn. <br />
<br />
Consider a driver on [https://www.waze.com/en-US/editor/?env=usa&lon=-121.92340&lat=37.49481&zoom=6 Mission Boulevard being guided to northbound I-680]. There are 3 full lanes at the on-ramp to northbound I-680 with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1WAUh2UMG3NKWgAawNvt-ELKaMko5va6p/view?usp=sharing'' </blockquote>At the prior on-ramp to southbound I-680, there are also 3 full lanes at the on-ramp with the right lane dedicated to the freeway entrance. <blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1pKWKjd59aFBNb4ROoViban5_5pPWkgSu/view?usp=sharing'' </blockquote>Note that since Lane Guidance is announced about ½ mile for MH (and ¼ mile for mH and lower) prior to the turn instruction, the driver would have heard ''<code>In ½ mile, use the right lane to turn right to I-680 North Sacramento</code>'' at around Warm Springs Boulevard, which is 2 signaled intersections prior to the entrance to northbound I-680. There is no signage that the right lane ends until you are almost at the entrance to southbound I-680. A driver unfamiliar with the area, upon seeing or hearing the guidance, would get into the right lane. By the time the driver realizes that the lane is a dedicated lane to I-680 South, not North, there isn't much distance left to change lanes, especially when there is a lot of traffic in the next lane.<blockquote>''Picture here (not uploaded to Wazeopedia yet): https://drive.google.com/file/d/1uAPd_q-O7VRhYnAtGuvskjHI1Uf3qcqr/view?usp=sharing''</blockquote>In order to properly guide the driver, there are a few possibilities. Waze could delay announcing the Turn instruction to northbound I-680 until the driver is past the entrance to southbound I-680. A more ideal solution would be for Waze to announce ''<code>In ½ mile, stay in the middle lane and then turn right to I-680 North Sacramento</code>''. <br />
<br />
'''What should be done in these situations?'''<br />
<br />
*Lanes should not be mapped at such intersections<br />
*Place a Map Comment so that future editors can locate these locations if Waze enhances the Lane Guidance feature to make mapping these locations possible. Adding a Map Comment could be used as a notification to current editors that the intersection has been reviewed and Lane Guidance should not be added until such time these enhancements are available.<br />
<br />
<br /></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Tonestertm/California_GIS_sources&diff=174937User:Tonestertm/California GIS sources2021-10-02T01:23:30Z<p>Tonestertm: /* Ventura County */ New link for Ventura County. Thanks ojlaw!</p>
<hr />
<div><span style="color:#FF0000">This page is under construction.</span> If you'd like to help out, please, [http://www.waze.com/forum/ucp.php?i=pm&mode=compose&username=tonestertm PM tonestertm] before making any changes.<br />
<br />
<br />
'''A Collection of interactive GIS maps for municipalities throughout California.'''<br />
<br />
<br />
Caltrans has a [https://caltrans.maps.arcgis.com/apps/webappviewer/index.html?id=026e830c914c495797c969a3e5668538 new interactive map] with layers for Functional Classification, counties, Caltrans Districts, and a few other useful things. Note that the FC data on here is the same as the CRS Grid maps accessible through the [https://wazeopedia.waze.com/wiki/USA/User:Tonestertm/CRS_grid_bookmarklet CRS Grid bookmarklet].<br />
<br />
The [http://portal.gis.ca.gov/geoportal/viewer/index.jsp California Geoportal Viewer] is an all-state viewer, with only a Roads layer. It is very quick and easy to use, but may not be quite as up to date as local maps. <br />
<br />
''Note: In most cases, the links below will land you on the map itself, but sometimes it is is necessary to accept a disclaimer before viewing the map. A few maps require the use of Internet Explorer (noted), others require installation of the Silverlight plugin, and still others require an Autodesk plugin. Where there is no ''County'' interactive viewer, static map pages are linked and so indicated (I hope, let me know) by italics. A few counties do not yet publish online maps; use the Geoportal Viewer for these. '' <br />
<br />
Above all, understand that map availability is constantly changing. If you don't see what you're looking for here, try a search for "GIS" and the location you're looking for; it's quite possible there's a map now. And if you find one, let me know, so I can add it! <br />
<br />
Thanks to users '''ababcock, abc1357, AquaZR1, bwawsc, citeman, Cardyin, dfortney, robertonthego, turbomkt''' for contributing! (Anyone I've missed? Please let me know) <br />
<br />
[[File:California_counties_outline_map.png|right|California counties outline map]]<br />
<br />
====[http://www.acgov.org/assessor/resources/parcel_viewer.htm Alameda County]====<br />
<br />
Alameda<br />
Albany<br />
[http://www.cityofberkeley.info/ContentDisplay.aspx?id=55706 Berkeley]<br />
Dublin<br />
Emeryville<br />
Fremont<br />
Hayward<br />
Livermore<br />
Newark<br />
[http://mapgis.oaklandnet.com/planmap/ Oakland]<br />
Piedmont<br />
Pleasanton<br />
San Leandro<br />
Union City<br />
<br />
====Alpine County====<br />
<br />
No Cities<br />
<br />
====[https://gisviewer.amadorgov.org/gpv/Viewer.aspx Amador County]====<br />
<br />
<br />
Amador<br />
Ione<br />
Jackson<br />
Plymouth<br />
Sutter Creek<br />
<br />
====[http://gis.buttecounty.net/public/index.html?viewer=pwsearch/ Butte County]====<br />
<br />
Biggs<br />
Chico<br />
Gridley<br />
Oroville<br />
Paradise<br />
<br />
====[http://mapserver.co.calaveras.ca.us/genplan_pub/index.html Calaveras County]====<br />
<br />
Angels Camp<br />
<br />
====[http://colusacountydpw.maps.arcgis.com/apps/webappviewer/index.html?id=ba6fd932ef964ce7b9f17e6fdfd2f6f2 Colusa County]==== <br />
<br />
Colusa<br />
Williams<br />
<br />
====[https://ccmap.cccounty.us/Html5/index.html?viewer=CCMAP Contra Costa County]====<br />
<br />
[http://www.antiochprospector.com/ Antioch]<br />
Brentwood<br />
Clayton<br />
Concord<br />
Danville<br />
El Cerrito<br />
Hercules<br />
Lafayette<br />
Martinez<br />
Moraga<br />
Oakley<br />
Orinda<br />
Pinole<br />
Pittsburg<br />
Pleasant Hill<br />
[http://www.ci.richmond.ca.us/index.aspx?NID=865 Richmond]<br />
San Pablo<br />
San Ramon<br />
Walnut Creek<br />
<br />
====Del Norte County====<br />
<br />
Crescent City<br />
<br />
====[https://see-eldorado.edcgov.us/ugotnet/ El Dorado County]====<br />
<br />
Placerville<br />
South Lake Tahoe<br />
<br />
====[https://gisportal.co.fresno.ca.us/portal/apps/webappviewer/index.html?id=b921843d343d4df998b5b3c6a301756a Fresno County]====<br />
<br />
Clovis<br />
Coalinga<br />
Firebaugh<br />
Fowler<br />
[http://gis4u.fresno.gov/viewer/ Fresno]<br />
Huron<br />
Kerman<br />
Kingsburg<br />
Mendota<br />
Orange Cove<br />
Parlier<br />
Reedley<br />
Sanger<br />
Selma<br />
<br />
====[http://gis.gcppwa.net/districts/ Glenn County]====<br />
<br />
Orland<br />
Willows<br />
<br />
====[http://gis.co.humboldt.ca.us/Freeance/Client/PublicAccess1/index.html?appconfig=podgis4 Humboldt County]====<br />
<br />
Arcata<br />
Blue Lake<br />
Eureka<br />
Ferndale<br />
Fortuna<br />
Rio Dell<br />
Trinidad<br />
<br />
====[https://www.geoviewer8.com/?username=icpublic&password=icpublic Imperial County]====<br />
<br />
Brawley<br />
Calexico<br />
Calipatria<br />
El Centro<br />
Holtville<br />
Imperial<br />
Westmorland<br />
<br />
====[https://inyocounty.maps.arcgis.com/apps/webappviewer/index.html?id=f3db09212fcf4d5eb0beee16f26e040c Inyo County]====<br />
<br />
Bishop<br />
<br />
====[http://maps.co.kern.ca.us/H5/index.html?viewer=public Kern County]====<br />
<br />
Arvin<br />
[https://cob.maps.arcgis.com/apps/webappviewer/index.html?id=9174f084addc450286ac067a56fdb83f Bakersfield] <br />
California City<br />
Delano<br />
Maricopa<br />
Mcfarland<br />
Ridgecrest<br />
Shafter<br />
Taft<br />
Tehachapi<br />
Wasco<br />
<br />
====[http://www.kingscountygis.com/maps/ Kings County]====<br />
<br />
Avenal<br />
Corcoran<br />
Hanford<br />
Lemoore<br />
<br />
====Lake County====<br />
<br />
Clearlake<br />
Lakeport<br />
<br />
====Lassen County====<br />
<br />
Susanville<br />
<br />
====[http://rpgis.isd.lacounty.gov/Html5Viewer/index.html?viewer=GISNET_Public.GIS-NET_Public Los Angeles County]==== <br />
<br />
[http://maps.assessor.lacounty.gov/GVH_2_2/Index.html?configBase=http://maps.assessor.lacounty.gov/Geocortex/Essentials/REST/sites/PAIS/viewers/PAIS_hv/virtualdirectory/Resources/Config/Default LA County Assessor's map]<br />
<br />
Agoura Hills<br />
Alhambra<br />
Arcadia<br />
Artesia<br />
Avalon<br />
Azusa<br />
Baldwin Park<br />
Bell<br />
Bellflower<br />
Bell Gardens<br />
Beverly Hills<br />
Bradbury<br />
[http://burbankca.maps.arcgis.com/apps/Solutions/s2.html?appid=06adc1d9e2c84c5f9a366014cbef7cb0 Burbank]<br />
Calabasas<br />
[http://www.carsonproperty.info/ Carson]<br />
Cerritos<br />
Claremont<br />
Commerce<br />
Compton<br />
Covina<br />
Cudahy<br />
[http://gisproxy.culvercity.org/SilverlightViewer_1_8/Viewer.html?Viewer=ExternalInfo Culver City - ''requires Silverlight'']<br />
Diamond Bar<br />
Downey<br />
Duarte<br />
El Monte<br />
[http://www.elsegundo.org/civicax/filebank/blobdload.aspx?blobid=7552 ''El Segundo'']<br />
Gardena<br />
Glendale<br />
Glendora<br />
Hawaiian Gardens<br />
Hawthorne<br />
[http://www.hermosabch.org/modules/showdocument.aspx?documentid=417 ''Hermosa Beach'']<br />
Hidden Hills<br />
Huntington Park<br />
Industry<br />
Inglewood<br />
Irwindale<br />
La Canada Flintridge<br />
La Habra Heights<br />
Lakewood<br />
La Mirada<br />
Lancaster<br />
La Puente<br />
La Verne<br />
Lawndale<br />
Lomita<br />
Long Beach<br />
[http://navigatela.lacity.org/navigatela/ Los Angeles]<br />
Lynwood<br />
Malibu<br />
[http://manhattanbeach.geocortex.com/maps/ Manhattan Beach]<br />
Maywood<br />
Monrovia<br />
Montebello<br />
Monterey Park<br />
Norwalk<br />
[http://maps.cityofpalmdale.org/FMv2/default.aspx Palmdale]<br />
Palos Verdes Estates<br />
Paramount<br />
Pasadena<br />
Pico Rivera<br />
Pomona<br />
Rancho Palos Verdes<br />
Redondo Beach<br />
Rolling Hills<br />
Rolling Hills Estates<br />
Rosemead<br />
San Dimas<br />
San Fernando<br />
San Gabriel<br />
San Marino<br />
[http://gis.santa-clarita.com/html5/MasterPUB.html Santa Clarita] [http://gis.santa-clarita.com/slv/?Viewer=MasterPUB Santa Clarita Alt - ''requires Silverlight'']<br />
Santa Fe Springs<br />
[http://csmgisweb.smgov.net/Html5Viewer/Index.html?configBase=http://csmgisweb.smgov.net/Geocortex/Essentials/REST/sites/laco_test/viewers/LACO_base_test_html5/virtualdirectory/Resources/Config/Default Santa Monica]<br />
Sierra Madre<br />
Signal Hill<br />
South El Monte<br />
South Gate<br />
South Pasadena<br />
Temple City<br />
[http://www.torranceca.gov/PDF/StnxmapTARA(everything)2016_24X36.pdf Torrance]<br />
Vernon<br />
Walnut<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/westcovina/prerelease_index.aspx# West Covina]<br />
West Hollywood<br />
Westlake Village<br />
Whittier<br />
<br />
====[http://countymadera.maps.arcgis.com/apps/Solutions/s2.html?appid=894807923d764977bdacde99fb4508ae Madera County]====<br />
<br />
Chowchilla<br />
Madera<br />
<br />
====[http://www.marinmap.org/Html5Viewer/Index.html?viewer=mmdataviewer Marin County]====<br />
<br />
Belvedere<br />
Corte Madera<br />
Fairfax<br />
Larkspur<br />
Mill Valley<br />
Novato<br />
Ross<br />
San Anselmo<br />
San Rafael<br />
Sausalito<br />
Tiburon<br />
<br />
====Mariposa County====<br />
<br />
No Cities<br />
<br />
====[http://www.co.mendocino.ca.us/econdev/gis/mapping.htm Mendocino County]====<br />
<br />
Fort Bragg<br />
Point Arena<br />
Ukiah<br />
Willits<br />
<br />
====[http://map.co.merced.ca.us/SL/?Viewer=mapmerced Merced County]====<br />
[http://mcaggis.com/MCAGBaseMap/ Alternate map]<br />
<br />
Atwater<br />
Dos Palos<br />
Gustine<br />
Livingston<br />
Los Banos<br />
Merced<br />
<br />
====Modoc County====<br />
<br />
Alturas<br />
<br />
====[https://monomammoth.maps.arcgis.com/apps/Viewer/index.html?appid=8670c63cda0540b39c3ae388cdd7db78 Mono County]====<br />
(not exactly a GIS, but seems to be official assessor info)<br />
<br />
Mammoth Lakes<br />
<br />
====[http://65.249.61.35/MCo_MapViewer/ Monterey County]====<br />
<br />
Carmel-By-The-Sea<br />
Del Rey Oaks<br />
Gonzales<br />
Greenfield<br />
King City<br />
Marina<br />
Monterey<br />
Pacific Grove<br />
Salinas<br />
Sand City<br />
Seaside<br />
Soledad<br />
<br />
====[http://gis.napa.ca.gov/html5viewer/?viewer=public_html Napa County]====<br />
<br />
American Canyon<br />
Calistoga<br />
Napa<br />
St Helena<br />
<br />
====[http://gis.nevcounty.net/MyNeighborhood/ Nevada County]====<br />
<br />
Grass Valley<br />
Nevada City<br />
[https://townoftruckee.maps.arcgis.com/apps/webappviewer/index.html?id=902bc3bcf8bb4c1b94f45d9b10c343f6 Truckee]<br />
<br />
====[https://www.ocgis.com/ocpw/landrecords/ Orange County]====<br />
<br />
[https://alisoviejo.maps.arcgis.com/apps/webappviewer/index.html?id=9ee5473b3ccb41c69c340ab16fdbfdf8 Aliso Viejo]<br />
Anaheim<br />
Brea<br />
Buena Park<br />
Costa Mesa<br />
Cypress<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/danapoint/index.aspx Dana Point]<br />
Fountain Valley<br />
[http://fullertoncagis.maps.arcgis.com/apps/webappviewer/index.html?id=ff9b168a7d2c448abefe7d406e14b549 Fullerton]<br />
Garden Grove<br />
Huntington Beach<br />
[http://gis.cityofirvine.org/onlineparcel/ Irvine]<br />
[http://gisweb.lagunabeachcity.net/Html5Viewer/index.html?configBase=http://gisweb.lagunabeachcity.net/Geocortex/Essentials/REST/sites/GISMap3/viewers/HTML5_22/virtualdirectory/Resources/Config/Default Laguna Beach]<br />
Laguna Hills<br />
[http://gis.cityoflagunaniguel.org/PublicViewer/ Laguna Niguel]<br />
Laguna Woods<br />
La Habra<br />
[http://www.lakeforestca.gov/DocumentCenter/View/1191 ''Lake Forest'']<br />
La Palma<br />
Los Alamitos<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/Missionviejo/index.aspx Mission Viejo]<br />
[http://nbgis.newportbeachca.gov/NewportHTML5Viewer/?viewer=publicsite Newport Beach]<br />
[http://gis.cityoforange.org/maps/centerlineties.html Orange]<br />
Placentia<br />
Rancho Santa Margarita<br />
San Clemente<br />
San Juan Capistrano<br />
[http://maps.digitalmapcentral.com/production/vecommunityview/cities/santaana/index.aspx# Santa Ana]<br />
Seal Beach<br />
Stanton<br />
Tustin<br />
Villa Park<br />
Westminster<br />
Yorba Linda<br />
<br />
====[http://placer.ca.gov/map-search Placer County]====<br />
<br />
Auburn<br />
Colfax<br />
Lincoln<br />
Loomis<br />
Rocklin<br />
[http://www.roseville.ca.us/eservices/maps_n_data/map_center.asp Roseville]<br />
<br />
====[https://secure.simplelayers.com/?do=start&project=1111&application=CG3Viewer&embedded=1&bgcolor=ffffff&width=975&height=735&context=22 Plumas County]====<br />
<br />
Portola<br />
<br />
====[https://gis1.countyofriverside.us/Html5Viewer/index.html?viewer=MMC_Public Riverside County]====<br />
<br />
Banning<br />
[http://beaumontca.gov/index.aspx?NID=983 Beaumont]<br />
Blythe<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/calimesa/index.aspx# Calimesa]<br />
Canyon Lake<br />
Cathedral City<br />
Coachella<br />
[http://cityofcorona.maps.arcgis.com/apps/webappviewer/index.html?id=36c7d42973f441819670d6f812b6b280 Corona]<br />
Desert Hot Springs<br />
[http://www.eastvaleca.gov/index.aspx?page=43 Eastvale]<br />
Hemet<br />
Indian Wells<br />
Indio<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/JurupaValley/index.aspx Jurupa Valley]<br />
Lake Elsinore<br />
La Quinta<br />
Menifee<br />
[http://www.moreno-valley.ca.us/city_hall/city_maps.shtml Moreno Valley]<br />
Murrieta<br />
Norco<br />
Palm Desert<br />
Palm Springs<br />
[http://maps.digitalmapcentral.com/production/vecommunityview/cities/perris/index.aspx Perris]<br />
[https://www.ranchomirageca.gov/content_files/pdf/about_rancho_mirage/city_map.pdf Rancho Mirage]<br />
Riverside<br />
San Jacinto<br />
Temecula<br />
Wildomar<br />
<br />
====[http://generalmap.gis.saccounty.net/JSViewer/county_portal.html Sacramento County]====<br />
[http://assessorparcelviewer.saccounty.net/GISViewer/Default.aspx Assessor map] for addresses / House Numbers<br />
<br />
Citrus Heights<br />
[http://elkgrovemap.gis.saccounty.net/jsviewer/elkgrove.html Elk Grove]<br />
Folsom<br />
Galt<br />
Isleton<br />
Rancho Cordova<br />
Sacramento<br />
<br />
====[https://cosb.maps.arcgis.com/home/webmap/viewer.html?webmap=4071773f6b004aaf8ee8d275b6b400b2 San Benito County]====<br />
Problem: http://www.lynxgis.com/sanbenitoco/index2.cfm<br />
Hollister<br />
San Juan Bautista<br />
<br />
====[https://www.arcgis.com/apps/webappviewer/index.html?id=87e70bb9b6994559ba7512792588d57a San Bernardino County]====<br />
<br />
Adelanto<br />
Apple Valley<br />
Barstow<br />
Big Bear Lake<br />
[http://www.cityofchino.org/home/showdocument?id=409 ''Chino'']<br />
Chino Hills<br />
Colton<br />
Fontana<br />
Grand Terrace<br />
Hesperia<br />
Highland<br />
Loma Linda<br />
Montclair<br />
Needles<br />
Ontario<br />
Rancho Cucamonga<br />
Redlands<br />
Rialto<br />
San Bernardino<br />
Twentynine Palms<br />
Upland<br />
Victorville<br />
Yucaipa<br />
Yucca Valley<br />
<br />
====[http://www.sangis.org/ San Diego County]====<br />
<br />
Carlsbad<br />
Chula Vista<br />
Coronado<br />
[http://delmar.geoviewer.io/ Del Mar]<br />
El Cajon<br />
Encinitas<br />
Escondido<br />
Imperial Beach<br />
La Mesa<br />
Lemon Grove<br />
National City<br />
[http://oceansidefiles.com/uploads/Water/PlanningViewer/index.html Oceanside]<br />
Poway<br />
San Diego<br />
San Marcos<br />
Santee<br />
Solana Beach<br />
[https://gis.cityofvista.com/VistaGIS/ Vista]<br />
<br />
====[http://sfgov.maps.arcgis.com/home/webmap/viewer.html?useExisting=1 San Francisco County]====<br />
<br />
San Francisco City and County are one and the same<br />
<br />
====[http://www.sjmap.org/DistrictViewer/Disclaimer.htm San Joaquin County]====<br />
<br />
Escalon<br />
Lathrop<br />
Lodi<br />
Manteca<br />
Ripon<br />
[http://www.stocktongov.com/government/departments/communityDevelop/genPlanMap.html Stockton]<br />
Tracy<br />
<br />
====[http://www.sloplanning.org/PermitView/MapSearch San Luis Obispo County]====<br />
<br />
Arroyo Grande<br />
Atascadero<br />
El Paso De Robles<br />
Grover Beach<br />
Morro Bay<br />
Pismo Beach<br />
San Luis Obispo<br />
<br />
====[https://gis.smcgov.org/Html5Viewer/?viewer=raster San Mateo County]====<br />
<br />
Atherton<br />
Belmont<br />
Brisbane<br />
Burlingame<br />
Colma<br />
Daly City<br />
East Palo Alto<br />
Foster City<br />
Half Moon Bay<br />
Hillsborough<br />
Menlo Park<br />
Millbrae<br />
Pacifica<br />
Portola Valley<br />
Redwood City<br />
San Bruno<br />
San Carlos<br />
San Mateo<br />
South San Francisco<br />
Woodside<br />
<br />
====[https://secure.simplelayers.com/?do=start&project=939&application=CG3Viewer&embedded=1&query_url=0&context=2 Santa Barbara County]====<br />
<br />
Buellton<br />
Carpinteria<br />
Goleta<br />
Guadalupe<br />
Lompoc<br />
Santa Barbara<br />
Santa Maria<br />
Solvang<br />
<br />
====[http://www.sccgov.org/gis/SCCPubInteractiveMap/# Santa Clara County]====<br />
<br />
Campbell<br />
Cupertino<br />
Gilroy<br />
Los Altos<br />
Los Altos Hills<br />
Los Gatos<br />
Milpitas<br />
Monte Sereno<br />
Morgan Hill<br />
Mountain View<br />
Palo Alto<br />
San Jose<br />
Santa Clara<br />
Saratoga<br />
Sunnyvale<br />
<br />
====[http://gis.co.santa-cruz.ca.us/PublicGISWeb/ Santa Cruz County]====<br />
<small>Recommend setting Base Map to None for above</small><br />
<br />
Capitola<br />
Santa Cruz<br />
Scotts Valley<br />
Watsonville<br />
<br />
====[http://gis.co.shasta.ca.us/Parcels/ Shasta County]====<br />
<br />
Anderson<br />
[http://maps.ci.redding.ca.us/redding_pub/home/index.aspx Redding]<br />
Shasta Lake<br />
<br />
====[http://demos2.calcad.com:8080/SierraCountyPublic/fusion.php Sierra County]====<br />
<br />
Loyalton<br />
<br />
====Siskiyou County====<br />
<br />
Dorris<br />
Dunsmuir<br />
Etna<br />
Fort Jone<br />
Montague<br />
Mount Shasta<br />
Tulelake<br />
Weed<br />
Yreka<br />
<br />
====[http://regis.solanocounty.com/Html5Viewer/Index.html?configBase=http://regis.solanocounty.com/Geocortex/Essentials/REST/sites/TaxParcelViewerNO/viewers/TaxParcelViewer-Solano_GIS_Viewer/virtualdirectory/Resources/Config/Default Solano County]====<br />
<br />
Benicia<br />
Dixon<br />
Fairfield<br />
Rio Vista<br />
Suisun City<br />
Vacaville<br />
[http://gis.zoomprospector.com/client/Vallejo/ Vallejo]<br />
<br />
====[https://sonomamap.maps.arcgis.com/apps/webappviewer/index.html?id=06ac7fe1b8554171b4682dc141293962 Sonoma County]====<br />
<br />
Cloverdale<br />
Cotati<br />
Healdsburg<br />
Petaluma<br />
Rohnert Park<br />
Santa Rosa<br />
Sebastopol<br />
Sonoma Windsor<br />
<br />
====[http://gis.stancounty.com/giscentral/public/map/esri/flex/parcelfinder/index.jsp# Stanislaus County]====<br />
<br />
Ceres<br />
Hughson<br />
[http://gis.modestogov.com/ Modesto*]<br />
Newman<br />
Oakdale<br />
Patterson<br />
Riverbank<br />
Turlock<br />
Waterford<br />
<br />
====Sutter County====<br />
[http://www.co.sutter.ca.us/doc/apps/road_closures Construction and Road Closures]<br />
<br />
Live Oak<br />
Yuba City<br />
<br />
====[http://www.arcgis.tehamacountypublicworks.ca.gov/ Tehama County]====<br />
<br />
Corning<br />
[http://planningsites.org/RedBluffPlanning/ Red Bluff]<br />
Tehama<br />
<br />
====[http://trinitycounty.maps.arcgis.com/apps/Viewer/index.html?appid=320cf1c1558c43c8b1f2f70c23d35026 Trinity County]====<br />
<br />
No Cities<br />
<br />
====Tulare County====<br />
<br />
:[http://tularecounty.ca.gov/tcict/index.cfm/geographic-information-system-gis/gis-maps/dinuba-city-map-jan-2008/ Dinuba] 2008 static map<br />
<br />
:[http://tularecounty.ca.gov/tcict/index.cfm/geographic-information-system-gis/gis-maps/exeter-city-map-jan-2008/ Exeter] 2008 Static map<br />
<br />
:[http://tularecounty.ca.gov/tcict/index.cfm/geographic-information-system-gis/gis-maps/farmersville-city-map-jan-2008/ Farmersville] 2008 Static map<br />
<br />
Lindsay<br />
[http://www.ci.porterville.ca.us/depts/CommunityDevelopment/webmaps/PublicWebmapPortal/webmap.html Porterville]<br />
[http://www.tulare.ca.gov/departments/community-development/development-services/planning/zoning-map Tulare] <br />
[http://visalia.maps.arcgis.com/apps/webappviewer/index.html?id=e78dfbb593044bf6bc1cf4f0d63c9160 Visalia]<br />
Woodlake<br />
<br />
====[http://gis.co.tuolumne.ca.us:8093/flexviewers/General%20Plan%20And%20Zoning/ Tuolumne County]====<br />
<br />
Sonora<br />
<br />
====[https://maps.ventura.org/countyview/ Ventura County]====<br />
<br />
Camarillo<br />
Fillmore<br />
Moorpark<br />
Ojai<br />
Oxnard<br />
Port Hueneme<br />
San Buenaventura<br />
Santa Paula<br />
Simi Valley<br />
Thousand Oaks<br />
Ventura<br />
<br />
====[http://yolo-gis-prod.yolocounty.org/SilverlightViewer_2_1/Viewer.html?ViewerConfig=http://yolo-gis-prod.yolocounty.org/Geocortex/Essentials/INTERNETPUBLIC/REST/sites/GIS_Public_Viewer/viewers/GIS_Public_Viewer/virtualdirectory/Config/Viewer.xml Yolo County]====<br />
<br />
Davis<br />
West Sacramento<br />
Winters<br />
Woodland<br />
<br />
====[http://gis.co.yuba.ca.us/portal_apps/parcelapp.html Yuba County]====<br />
<br />
Marysville<br />
Wheatland</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=California/Area_Managers/Main&diff=174680California/Area Managers/Main2021-08-25T19:51:27Z<p>Tonestertm: */Area manager table update*/ update tonestertm entry in AM table</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE -------------------------------<br />
------------------------------------------------------------------------------------<br />
--><noinclude>{{:USA/CommonState/ReturnPurge|{{#titleparts:{{PAGENAME}}|-1|-2}}}}</noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------<br />
---- Area Managers: Cancel edit and use link on table next to "Area Managers". -----<br />
---- Other Area Editors: Cancel edit and use link on table next to "Other Area<br />
---- Editors". If does not exist, that section can be added from talk page.---- Country/State Managers: Continue.<br />
------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this <br />
---- state. When first setting up this page, remove the example users for Country<br />
---- and State managers. Area Managers are changed in a different section as noted<br />
---- above. When adding a new user, use the following template: <br />
{{AM/Editor|Username|Area Managed|Other Comment}}<br />
---- If any fields are skipped, ensure all three the pipe "|" characters are present.<br />
---- Note the badge1, badge2, badge3 entries are only what is defined under:{{AM/Badge}}<br />
---- This link can be reached from http://wiki.waze.com/wiki/Template:AM/Badge or<br />
---- search the Wiki for:<br />
Template:AM/Badge<br />
---- When adding a new user, place the new template based on Rank (highest first)<br />
---- and then alphabetical order in that rank.<br />
------------------------------------------------------------------------------------<br />
--------------------- AREA MANAGER TABLE BEGINS BELOW ------------------------------<br />
---------------------------- EDIT BELOW LINE ---------------------------------------<br />
-----------------------------------------------------------------------------------><br />
{{AM/Top}}<!-- Top of the table --><br />
{{AM/Country}}<!-- Defines the start of the country manager section --><br />
{{AM/Editor|ottonomy|6|Statewide|Lifetime Los Angeles resident|badge1=rc|badge2=mgc|badge3=cm}}<br />
{{AM/Editor|jemay|6|Focused on Southern CA|Southern California resident|badge1=arc|badge2=mgc|badge3=cm}}<br />
{{AM/Editor|tonestertm|6|Statewide|L.A. born/based, SWR ARC|badge1=arc|badge2=sm|badge3=lc}}<br />
{{AM/Editor|kentsmith9|6|Focused on Northern CA and ID|Lifetime SF Bay Area resident|badge1=gc|badge2=cm}}<br />
{{AM/Editor|turbomkt|6|Statewide|Southern California|badge1=lc|badge2=mlc|badge3=sm}}<br />
{{AM/Editor|Machete808|6|Southern CA Focused - Statewide Assistance|Also Hawaii SM, Thailand CM|badge1=lc|badge2=mlc|badge3=sm}}<br />
{{AM/Editor|ply8808|6|Arizona|Neighboring support manager|badge1=mlc|badge2=cm}}<br />
{{AM/Editor|SkiDooGuy|6|Statewide - San Diego Enthusiast|badge1=mlc|badge2=cm}}<br />
{{User:Dmcrandall/AM}}<br />
{{AM/State}}<!-- Defines the start of the state manager section --><br />
{{AM/Editor|tonestertm|6|Statewide|LA born/based, lifetime California traveler, and ARC for Southwest Region|badge1=arc|badge2=sm|badge3=lc}}<br />
{{AM/Editor|turbomkt|6|Statewide|Southern California|badge1=lc|badge2=mlc|badge3=sm}}<br />
{{AM/Editor|citeman|5|Statewide|Long Beach born: LA/OC based|badge1=sm}}<br />
{{AM/Editor|nivekeel|5|Statewide|Southern California|badge1=sm}}<br />
{{AM/Editor|abc1357|5|Statewide|Northern California|badge1=sm}}<br />
{{AM/AreaLink}}<!-- Defines the start of the area manager section --><br />
{{#ifexist: {{BasePage2}}/AM/Editor/Area |<!--<br />
-->{{:{{BasePage2}}/AM/Editor/Area}}<!-- Area managers are edited through the main page link accessed from within the table itself. Do not add them here.--><br />
}}<!-- End ifexist --><br />
{{AM/Bottom}}<!-- Bottom of the table; must be the last line of table. -------------<br />
------------------------------------------------------------------------------------<br />
-->{{#ifexist: {{BasePage2}}/AM/Editor/Area2 <!-- If other table exists --><br />
| {{AM/Area2Link}}<!--then display Other Table, or skip --><br />
}}<!-- End ifexist --></includeonly><br />
<!-----------------------------------------------------------------------------------><br />
<!------------------------ DO NOT ADD CODE BELOW THE TABLE --------------------------></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=Template:RC/Data&diff=174679Template:RC/Data2021-08-25T19:47:50Z<p>Tonestertm: </p>
<hr />
<div><!-- If changes are made to the order of variables, the same change must be made<br />
---- on Template:RC/Data. First variable listed is area-type to then determine<br />
---- which variables can be extracted from then on.<br />
----<br />
---- Region = area-type | region-id | regional-coordinator | arc1 | arc2 | arc3 | arc4<br />
---- | state-list | state-list-long<br />
----<br />
---- State = area-type | state-id | region-name <br />
----<br />
---- Changes to regional coordinators should also be changed on Template:RC/Editors<br />
---- (if set up).<br />
----<br />
--><includeonly><!--includeonly here prevents error display on the template page when viewed directly -->{{#switch: {{{1}}}<br />
| Northwest = {{RC/Data/Core|{{{2|}}}|region|565|SunnyRaynbows|FzNk||||[[AK]]/[[ID]]/[[MT]]/[[OR]]/[[WA]]/[[WY]]|[[Alaska]]&nbsp;/ [[Idaho]]&nbsp;/ [[Montana]]&nbsp;/ [[Oregon]]&nbsp;/ [[Washington]]&nbsp;/ [[Wyoming]]}}<br />
| AK|Alaska = {{RC/Data/Core|{{{2|}}}|state|254|Northwest}}<br />
| ID|Idaho = {{RC/Data/Core|{{{2|}}}|state|648|Northwest}}<br />
| MT|Montana = {{RC/Data/Core|{{{2|}}}|state|649|Northwest}}<br />
| OR|Oregon = {{RC/Data/Core|{{{2|}}}|state|647|Northwest}}<br />
| WA|Washington = {{RC/Data/Core|{{{2|}}}|state|201|Northwest}}<br />
| WY|Wyoming = {{RC/Data/Core|{{{2|}}}|state|650|Northwest}}<br />
<!----><br />
| Southwest = {{RC/Data/Core|{{{2|}}}|region|566|ottonomy|jemay|tonestertm|turbomkt||[[AZ]]/[[CA]]/[[CO]]/[[HI]]/[[NV]]/[[NM]]/[[UT]]|[[Arizona]]&nbsp;/ [[California]]&nbsp;/ [[Colorado]]&nbsp;/ [[Hawaii]]&nbsp;/ [[Nevada]]&nbsp;/ [[New&nbsp;Mexico]]&nbsp;/ [[Utah]]}}<br />
| AZ|Arizona = {{RC/Data/Core|{{{2|}}}|state|652|Southwest}}<br />
| CA|California = {{RC/Data/Core|{{{2|}}}|state|251|Southwest}}<br />
| CO|Colorado = {{RC/Data/Core|{{{2|}}}|state|654|Southwest}}<br />
| HI|Hawaii = {{RC/Data/Core|{{{2|}}}|state|305|Southwest}}<br />
| NV|Nevada = {{RC/Data/Core|{{{2|}}}|state|651|Southwest}}<br />
| NM|New Mexico = {{RC/Data/Core|{{{2|}}}|state|653|Southwest}}<br />
| UT|Utah = {{RC/Data/Core|{{{2|}}}|state|364|Southwest}}<br />
<!----><br />
| Plains = {{RC/Data/Core|{{{2|}}}|region|567|bretmcvey|ehepner1977|SunnyRaynbows|||[[IA]]/[[KS]]/[[MN]]/[[MO]]/[[NE]]/[[ND]]/[[SD]]|[[Iowa]]&nbsp;/ [[Kansas]]&nbsp;/ [[Minnesota]]&nbsp;/ [[Missouri]]&nbsp;/ [[Nebraska]]&nbsp;/ [[North&nbsp;Dakota]]&nbsp;/ [[South&nbsp;Dakota]]}}<br />
| IA|Iowa = {{RC/Data/Core|{{{2|}}}|state|632|Plains}}<br />
| KS|Kansas = {{RC/Data/Core|{{{2|}}}|state|628|Plains}}<br />
| MN|Minnesota = {{RC/Data/Core|{{{2|}}}|state|259|Plains}}<br />
| MO|Missouri = {{RC/Data/Core|{{{2|}}}|state|414|Plains}}<br />
| NE|Nebraska = {{RC/Data/Core|{{{2|}}}|state|634|Plains}}<br />
| ND|North Dakota = {{RC/Data/Core|{{{2|}}}|state|624|Plains}}<br />
| SD|South Dakota = {{RC/Data/Core|{{{2|}}}|state|626|Plains}}<br />
<!----><br />
| South Central = {{RC/Data/Core|{{{2|}}}|region|568|karlcr9911|sketch||||[[AR]]/[[LA]]/[[MS]]/[[OK]]/[[TX]]|[[Arkansas]]&nbsp;/ [[Louisiana]]&nbsp;/ [[Mississippi]]&nbsp;/ [[Oklahoma]]&nbsp;/ [[Texas]]}}<br />
| AR|Arkansas = {{RC/Data/Core|{{{2|}}}|state|598|South Central}}<br />
| LA|Louisiana = {{RC/Data/Core|{{{2|}}}|state|594|South Central}}<br />
| MS|Mississippi = {{RC/Data/Core|{{{2|}}}|state|596|South Central}}<br />
| OK|Oklahoma = {{RC/Data/Core|{{{2|}}}|state|600|South Central}}<br />
| TX|Texas = {{RC/Data/Core|{{{2|}}}|state|237|South Central}}<br />
<!----><br />
| Great Lakes = {{RC/Data/Core|{{{2|}}}|region|943|JoeRodriguez12|GizmoGuy411|Roadtechie|SkiDooGuy||[[IL]]/[[IN]]/[[MI]]/[[OH]]/[[WI]]|[[Illinois]]&nbsp;/ [[Indiana]]&nbsp;/ [[Michigan]]&nbsp;/ [[Ohio]]&nbsp;/ [[Wisconsin]]}}<br />
| IL|Illinois = {{RC/Data/Core|{{{2|}}}|state|253|Great Lakes}}<br />
| IN|Indiana = {{RC/Data/Core|{{{2|}}}|state|631|Great Lakes}}<br />
| MI|Michigan = {{RC/Data/Core|{{{2|}}}|state|630|Great Lakes}}<br />
| OH|Ohio = {{RC/Data/Core|{{{2|}}}|state|261|Great Lakes}}<br />
| WI|Wisconsin = {{RC/Data/Core|{{{2|}}}|state|387|Great Lakes}}<br />
<!----><br />
| South Atlantic = {{RC/Data/Core|{{{2|}}}|region|570|xanderb|dfortney||||[[KY]]/[[NC]]/[[SC]]/[[TN]]|[[Kentucky]]&nbsp;/ [[North&nbsp;Carolina]]&nbsp;/ [[South&nbsp;Carolina]]&nbsp;/ [[Tennessee]]}}<br />
| KY|Kentucky = {{RC/Data/Core|{{{2|}}}|state|571|South Atlantic}}<br />
| NC|North Carolina = {{RC/Data/Core|{{{2|}}}|state|255|South Atlantic}}<br />
| SC|South Carolina = {{RC/Data/Core|{{{2|}}}|state|256|South Atlantic}}<br />
| TN|Tennessee = {{RC/Data/Core|{{{2|}}}|state|210|South Atlantic}}<br />
<!----><br />
| Southeast = {{RC/Data/Core|{{{2|}}}|region|944|itzwolf|driving79||||[[AL]]/[[FL]]/[[GA]]|[[Alabama]]&nbsp;/ [[Florida]]&nbsp;/ [[Georgia]]}}<br />
| AL|Alabama = {{RC/Data/Core|{{{2|}}}|state|213|Southeast}}<br />
| FL|Florida = {{RC/Data/Core|{{{2|}}}|state|193|Southeast}}<br />
| GA|Georgia = {{RC/Data/Core|{{{2|}}}|state|214|Southeast}}<br />
<!----><br />
| New England = {{RC/Data/Core|{{{2|}}}|region|945|orbitc|Banished||||[[CT]]/[[ME]]/[[MA]]/[[NH]]/[[RI]]/[[VT]]|[[Connecticut]]&nbsp;/ [[Maine]]&nbsp;/ [[Massachusetts]]&nbsp;/ [[New&nbsp;Hampshire]]&nbsp;/ [[Rhode&nbsp;Island]]&nbsp;/ [[Vermont]]}}<br />
| CT|Connecticut = {{RC/Data/Core|{{{2|}}}|state|247|New England}}<br />
| ME|Maine = {{RC/Data/Core|{{{2|}}}|state|583|New England}}<br />
| MA|Massachusetts = {{RC/Data/Core|{{{2|}}}|state|618|New England}}<br />
| NH|New Hampshire = {{RC/Data/Core|{{{2|}}}|state|585|New England}}<br />
| RI|Rhode Island = {{RC/Data/Core|{{{2|}}}|state|577|New England}}<br />
| VT|Vermont = {{RC/Data/Core|{{{2|}}}|state|587|New England}}<br />
<!----><br />
| Northeast = {{RC/Data/Core|{{{2|}}}|region|569|orbitc|PhantomSoul|RussPA|||[[DE]]/[[NJ]]/[[NY]]/[[PA]]|[[Delaware]]&nbsp;/ [[New&nbsp;Jersey]]&nbsp;/ [[New&nbsp;York]]&nbsp;/ [[Pennsylvania]]}}<br />
| DE|Delaware = {{RC/Data/Core|{{{2|}}}|state|575|Northeast}}<br />
| NJ|New Jersey = {{RC/Data/Core|{{{2|}}}|state|249|Northeast}}<br />
| NY|New York = {{RC/Data/Core|{{{2|}}}|state|250|Northeast}}<br />
| PA|Pennsylvania = {{RC/Data/Core|{{{2|}}}|state|215|Northeast}}<br />
<!----><br />
| Mid Atlantic = {{RC/Data/Core|{{{2|}}}|region|946|nzahn1|ct13|ldriveskier|||[[DC]]/[[MD]]/[[VA]]/[[WV]]|[[District&nbsp;of&nbsp;Columbia]]&nbsp;/ [[Maryland]]&nbsp;/ [[Virginia]]&nbsp;/ [[West&nbsp;Virginia]]}}<br />
| DC|Washington DC|District of Columbia = {{RC/Data/Core|{{{2|}}}|district|258|Mid Atlantic}}<br />
| MD|Maryland = {{RC/Data/Core|{{{2|}}}|state|246|Mid Atlantic}}<br />
| VA|Virginia = {{RC/Data/Core|{{{2|}}}|state|580|Mid Atlantic}}<br />
| WV|West Virginia = {{RC/Data/Core|{{{2|}}}|state|582|Mid Atlantic}}<br />
<!----><br />
| Territories = {{RC/Data/Core|{{{2|}}}|region|953|nnote|||||[[AS]]/[[GU]]/[[Northern Mariana Islands|MP]]/[[PR]]/[[VI]]|[[American&nbsp;Samoa]]&nbsp;/ [[Guam]]&nbsp;/ [[Northern&nbsp;Mariana&nbsp;Islands]]&nbsp;/ [[Puerto&nbsp;Rico]]&nbsp;/ [[Virgin&nbsp;Islands]]}}<br />
| AS|American Samoa = {{RC/Data/Core|{{{2|}}}|territory|954|Territories}}<br />
| GU|Guam = {{RC/Data/Core|{{{2|}}}|territory|954|Territories}}<br />
| MP|Northern Mariana Islands = {{RC/Data/Core|{{{2|}}}|territory|954|Territories}}<br />
| PR|Puerto Rico = {{RC/Data/Core|{{{2|}}}|territory|202|Territories}}<br />
| VI|Virgin Islands = {{RC/Data/Core|{{{2|}}}|territory|677|Territories}}<br />
| South Pacific Territories = {{RC/Data/Core|{{{2|}}}|territory|954|Territories}}<br />
<!-- Other territories need to be added --><br />
<!----><br />
<!-- This below is for the CommonState template pages when viewed directly --><br />
| Testing|RC|CommonRegion|RC/CommonRegion = {{RC/Data/Core|{{{2|}}}|region|192|UserName1|UserName2|UserName3|UserName4|UserName5|[[XX]]/[[YY]]|[[XXXX]]&nbsp;/ [[YYYY]]}}<br />
| TestState|USA|CommonState|Intro|Forum|USA/CommonState<br />
= {{RC/Data/Core|{{{2|}}}|state|192|Testing}}<br />
<!----><br />
<!-- Default USA forum; doesn't work perfectly for all combos, but can show errors --><br />
| {{RC/Data/Core|{{{2|}}}|state|129|USA}}<!-- default USA forum--><br />
}}</includeonly><noinclude>{{documentation}}<!-- <br />
Add categories and interwikis to the /doc subpage, not here! <br />
--></noinclude></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=Template:RC/Data&diff=174678Template:RC/Data2021-08-25T19:45:07Z<p>Tonestertm: Add turbomkt to Southwest</p>
<hr />
<div><!-- If changes are made to the order of variables, the same change must be made<br />
---- on Template:RC/Data. First variable listed is area-type to then determine<br />
---- which variables can be extracted from then on.<br />
----<br />
---- Region = area-type | region-id | regional-coordinator | arc1 | arc2 | arc3 | arc4<br />
---- | state-list | state-list-long<br />
----<br />
---- State = area-type | state-id | region-name <br />
----<br />
---- Changes to regional coordinators should also be changed on Template:RC/Editors<br />
---- (if set up).<br />
----<br />
--><includeonly><!--includeonly here prevents error display on the template page when viewed directly -->{{#switch: {{{1}}}<br />
| Northwest = {{RC/Data/Core|{{{2|}}}|region|565|SunnyRaynbows|FzNk||||[[AK]]/[[ID]]/[[MT]]/[[OR]]/[[WA]]/[[WY]]|[[Alaska]]&nbsp;/ [[Idaho]]&nbsp;/ [[Montana]]&nbsp;/ [[Oregon]]&nbsp;/ [[Washington]]&nbsp;/ [[Wyoming]]}}<br />
| AK|Alaska = {{RC/Data/Core|{{{2|}}}|state|254|Northwest}}<br />
| ID|Idaho = {{RC/Data/Core|{{{2|}}}|state|648|Northwest}}<br />
| MT|Montana = {{RC/Data/Core|{{{2|}}}|state|649|Northwest}}<br />
| OR|Oregon = {{RC/Data/Core|{{{2|}}}|state|647|Northwest}}<br />
| WA|Washington = {{RC/Data/Core|{{{2|}}}|state|201|Northwest}}<br />
| WY|Wyoming = {{RC/Data/Core|{{{2|}}}|state|650|Northwest}}<br />
<!----><br />
| Southwest = {{RC/Data/Core|{{{2|}}}|region|566|ottonomy|jemay|tonestertm|turbomkt|||[[AZ]]/[[CA]]/[[CO]]/[[HI]]/[[NV]]/[[NM]]/[[UT]]|[[Arizona]]&nbsp;/ [[California]]&nbsp;/ [[Colorado]]&nbsp;/ [[Hawaii]]&nbsp;/ [[Nevada]]&nbsp;/ [[New&nbsp;Mexico]]&nbsp;/ [[Utah]]}}<br />
| AZ|Arizona = {{RC/Data/Core|{{{2|}}}|state|652|Southwest}}<br />
| CA|California = {{RC/Data/Core|{{{2|}}}|state|251|Southwest}}<br />
| CO|Colorado = {{RC/Data/Core|{{{2|}}}|state|654|Southwest}}<br />
| HI|Hawaii = {{RC/Data/Core|{{{2|}}}|state|305|Southwest}}<br />
| NV|Nevada = {{RC/Data/Core|{{{2|}}}|state|651|Southwest}}<br />
| NM|New Mexico = {{RC/Data/Core|{{{2|}}}|state|653|Southwest}}<br />
| UT|Utah = {{RC/Data/Core|{{{2|}}}|state|364|Southwest}}<br />
<!----><br />
| Plains = {{RC/Data/Core|{{{2|}}}|region|567|bretmcvey|ehepner1977|SunnyRaynbows|||[[IA]]/[[KS]]/[[MN]]/[[MO]]/[[NE]]/[[ND]]/[[SD]]|[[Iowa]]&nbsp;/ [[Kansas]]&nbsp;/ [[Minnesota]]&nbsp;/ [[Missouri]]&nbsp;/ [[Nebraska]]&nbsp;/ [[North&nbsp;Dakota]]&nbsp;/ [[South&nbsp;Dakota]]}}<br />
| IA|Iowa = {{RC/Data/Core|{{{2|}}}|state|632|Plains}}<br />
| KS|Kansas = {{RC/Data/Core|{{{2|}}}|state|628|Plains}}<br />
| MN|Minnesota = {{RC/Data/Core|{{{2|}}}|state|259|Plains}}<br />
| MO|Missouri = {{RC/Data/Core|{{{2|}}}|state|414|Plains}}<br />
| NE|Nebraska = {{RC/Data/Core|{{{2|}}}|state|634|Plains}}<br />
| ND|North Dakota = {{RC/Data/Core|{{{2|}}}|state|624|Plains}}<br />
| SD|South Dakota = {{RC/Data/Core|{{{2|}}}|state|626|Plains}}<br />
<!----><br />
| South Central = {{RC/Data/Core|{{{2|}}}|region|568|karlcr9911|sketch||||[[AR]]/[[LA]]/[[MS]]/[[OK]]/[[TX]]|[[Arkansas]]&nbsp;/ [[Louisiana]]&nbsp;/ [[Mississippi]]&nbsp;/ [[Oklahoma]]&nbsp;/ [[Texas]]}}<br />
| AR|Arkansas = {{RC/Data/Core|{{{2|}}}|state|598|South Central}}<br />
| LA|Louisiana = {{RC/Data/Core|{{{2|}}}|state|594|South Central}}<br />
| MS|Mississippi = {{RC/Data/Core|{{{2|}}}|state|596|South Central}}<br />
| OK|Oklahoma = {{RC/Data/Core|{{{2|}}}|state|600|South Central}}<br />
| TX|Texas = {{RC/Data/Core|{{{2|}}}|state|237|South Central}}<br />
<!----><br />
| Great Lakes = {{RC/Data/Core|{{{2|}}}|region|943|JoeRodriguez12|GizmoGuy411|Roadtechie|SkiDooGuy||[[IL]]/[[IN]]/[[MI]]/[[OH]]/[[WI]]|[[Illinois]]&nbsp;/ [[Indiana]]&nbsp;/ [[Michigan]]&nbsp;/ [[Ohio]]&nbsp;/ [[Wisconsin]]}}<br />
| IL|Illinois = {{RC/Data/Core|{{{2|}}}|state|253|Great Lakes}}<br />
| IN|Indiana = {{RC/Data/Core|{{{2|}}}|state|631|Great Lakes}}<br />
| MI|Michigan = {{RC/Data/Core|{{{2|}}}|state|630|Great Lakes}}<br />
| OH|Ohio = {{RC/Data/Core|{{{2|}}}|state|261|Great Lakes}}<br />
| WI|Wisconsin = {{RC/Data/Core|{{{2|}}}|state|387|Great Lakes}}<br />
<!----><br />
| South Atlantic = {{RC/Data/Core|{{{2|}}}|region|570|xanderb|dfortney||||[[KY]]/[[NC]]/[[SC]]/[[TN]]|[[Kentucky]]&nbsp;/ [[North&nbsp;Carolina]]&nbsp;/ [[South&nbsp;Carolina]]&nbsp;/ [[Tennessee]]}}<br />
| KY|Kentucky = {{RC/Data/Core|{{{2|}}}|state|571|South Atlantic}}<br />
| NC|North Carolina = {{RC/Data/Core|{{{2|}}}|state|255|South Atlantic}}<br />
| SC|South Carolina = {{RC/Data/Core|{{{2|}}}|state|256|South Atlantic}}<br />
| TN|Tennessee = {{RC/Data/Core|{{{2|}}}|state|210|South Atlantic}}<br />
<!----><br />
| Southeast = {{RC/Data/Core|{{{2|}}}|region|944|itzwolf|driving79||||[[AL]]/[[FL]]/[[GA]]|[[Alabama]]&nbsp;/ [[Florida]]&nbsp;/ [[Georgia]]}}<br />
| AL|Alabama = {{RC/Data/Core|{{{2|}}}|state|213|Southeast}}<br />
| FL|Florida = {{RC/Data/Core|{{{2|}}}|state|193|Southeast}}<br />
| GA|Georgia = {{RC/Data/Core|{{{2|}}}|state|214|Southeast}}<br />
<!----><br />
| New England = {{RC/Data/Core|{{{2|}}}|region|945|orbitc|Banished||||[[CT]]/[[ME]]/[[MA]]/[[NH]]/[[RI]]/[[VT]]|[[Connecticut]]&nbsp;/ [[Maine]]&nbsp;/ [[Massachusetts]]&nbsp;/ [[New&nbsp;Hampshire]]&nbsp;/ [[Rhode&nbsp;Island]]&nbsp;/ [[Vermont]]}}<br />
| CT|Connecticut = {{RC/Data/Core|{{{2|}}}|state|247|New England}}<br />
| ME|Maine = {{RC/Data/Core|{{{2|}}}|state|583|New England}}<br />
| MA|Massachusetts = {{RC/Data/Core|{{{2|}}}|state|618|New England}}<br />
| NH|New Hampshire = {{RC/Data/Core|{{{2|}}}|state|585|New England}}<br />
| RI|Rhode Island = {{RC/Data/Core|{{{2|}}}|state|577|New England}}<br />
| VT|Vermont = {{RC/Data/Core|{{{2|}}}|state|587|New England}}<br />
<!----><br />
| Northeast = {{RC/Data/Core|{{{2|}}}|region|569|orbitc|PhantomSoul|RussPA|||[[DE]]/[[NJ]]/[[NY]]/[[PA]]|[[Delaware]]&nbsp;/ [[New&nbsp;Jersey]]&nbsp;/ [[New&nbsp;York]]&nbsp;/ [[Pennsylvania]]}}<br />
| DE|Delaware = {{RC/Data/Core|{{{2|}}}|state|575|Northeast}}<br />
| NJ|New Jersey = {{RC/Data/Core|{{{2|}}}|state|249|Northeast}}<br />
| NY|New York = {{RC/Data/Core|{{{2|}}}|state|250|Northeast}}<br />
| PA|Pennsylvania = {{RC/Data/Core|{{{2|}}}|state|215|Northeast}}<br />
<!----><br />
| Mid Atlantic = {{RC/Data/Core|{{{2|}}}|region|946|nzahn1|ct13|ldriveskier|||[[DC]]/[[MD]]/[[VA]]/[[WV]]|[[District&nbsp;of&nbsp;Columbia]]&nbsp;/ [[Maryland]]&nbsp;/ [[Virginia]]&nbsp;/ [[West&nbsp;Virginia]]}}<br />
| DC|Washington DC|District of Columbia = {{RC/Data/Core|{{{2|}}}|district|258|Mid Atlantic}}<br />
| MD|Maryland = {{RC/Data/Core|{{{2|}}}|state|246|Mid Atlantic}}<br />
| VA|Virginia = {{RC/Data/Core|{{{2|}}}|state|580|Mid Atlantic}}<br />
| WV|West Virginia = {{RC/Data/Core|{{{2|}}}|state|582|Mid Atlantic}}<br />
<!----><br />
| Territories = {{RC/Data/Core|{{{2|}}}|region|953|nnote|||||[[AS]]/[[GU]]/[[Northern Mariana Islands|MP]]/[[PR]]/[[VI]]|[[American&nbsp;Samoa]]&nbsp;/ [[Guam]]&nbsp;/ [[Northern&nbsp;Mariana&nbsp;Islands]]&nbsp;/ [[Puerto&nbsp;Rico]]&nbsp;/ [[Virgin&nbsp;Islands]]}}<br />
| AS|American Samoa = {{RC/Data/Core|{{{2|}}}|territory|954|Territories}}<br />
| GU|Guam = {{RC/Data/Core|{{{2|}}}|territory|954|Territories}}<br />
| MP|Northern Mariana Islands = {{RC/Data/Core|{{{2|}}}|territory|954|Territories}}<br />
| PR|Puerto Rico = {{RC/Data/Core|{{{2|}}}|territory|202|Territories}}<br />
| VI|Virgin Islands = {{RC/Data/Core|{{{2|}}}|territory|677|Territories}}<br />
| South Pacific Territories = {{RC/Data/Core|{{{2|}}}|territory|954|Territories}}<br />
<!-- Other territories need to be added --><br />
<!----><br />
<!-- This below is for the CommonState template pages when viewed directly --><br />
| Testing|RC|CommonRegion|RC/CommonRegion = {{RC/Data/Core|{{{2|}}}|region|192|UserName1|UserName2|UserName3|UserName4|UserName5|[[XX]]/[[YY]]|[[XXXX]]&nbsp;/ [[YYYY]]}}<br />
| TestState|USA|CommonState|Intro|Forum|USA/CommonState<br />
= {{RC/Data/Core|{{{2|}}}|state|192|Testing}}<br />
<!----><br />
<!-- Default USA forum; doesn't work perfectly for all combos, but can show errors --><br />
| {{RC/Data/Core|{{{2|}}}|state|129|USA}}<!-- default USA forum--><br />
}}</includeonly><noinclude>{{documentation}}<!-- <br />
Add categories and interwikis to the /doc subpage, not here! <br />
--></noinclude></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Tonestertm/California_GIS_sources&diff=174392User:Tonestertm/California GIS sources2021-07-19T19:45:20Z<p>Tonestertm: /* San Mateo County */ Update county link</p>
<hr />
<div><span style="color:#FF0000">This page is under construction.</span> If you'd like to help out, please, [http://www.waze.com/forum/ucp.php?i=pm&mode=compose&username=tonestertm PM tonestertm] before making any changes.<br />
<br />
<br />
'''A Collection of interactive GIS maps for municipalities throughout California.'''<br />
<br />
<br />
Caltrans has a [https://caltrans.maps.arcgis.com/apps/webappviewer/index.html?id=026e830c914c495797c969a3e5668538 new interactive map] with layers for Functional Classification, counties, Caltrans Districts, and a few other useful things. Note that the FC data on here is the same as the CRS Grid maps accessible through the [https://wazeopedia.waze.com/wiki/USA/User:Tonestertm/CRS_grid_bookmarklet CRS Grid bookmarklet].<br />
<br />
The [http://portal.gis.ca.gov/geoportal/viewer/index.jsp California Geoportal Viewer] is an all-state viewer, with only a Roads layer. It is very quick and easy to use, but may not be quite as up to date as local maps. <br />
<br />
''Note: In most cases, the links below will land you on the map itself, but sometimes it is is necessary to accept a disclaimer before viewing the map. A few maps require the use of Internet Explorer (noted), others require installation of the Silverlight plugin, and still others require an Autodesk plugin. Where there is no ''County'' interactive viewer, static map pages are linked and so indicated (I hope, let me know) by italics. A few counties do not yet publish online maps; use the Geoportal Viewer for these. '' <br />
<br />
Above all, understand that map availability is constantly changing. If you don't see what you're looking for here, try a search for "GIS" and the location you're looking for; it's quite possible there's a map now. And if you find one, let me know, so I can add it! <br />
<br />
Thanks to users '''ababcock, abc1357, AquaZR1, bwawsc, citeman, Cardyin, dfortney, robertonthego, turbomkt''' for contributing! (Anyone I've missed? Please let me know) <br />
<br />
[[File:California_counties_outline_map.png|right|California counties outline map]]<br />
<br />
====[http://www.acgov.org/assessor/resources/parcel_viewer.htm Alameda County]====<br />
<br />
Alameda<br />
Albany<br />
[http://www.cityofberkeley.info/ContentDisplay.aspx?id=55706 Berkeley]<br />
Dublin<br />
Emeryville<br />
Fremont<br />
Hayward<br />
Livermore<br />
Newark<br />
[http://mapgis.oaklandnet.com/planmap/ Oakland]<br />
Piedmont<br />
Pleasanton<br />
San Leandro<br />
Union City<br />
<br />
====Alpine County====<br />
<br />
No Cities<br />
<br />
====[https://gisviewer.amadorgov.org/gpv/Viewer.aspx Amador County]====<br />
<br />
<br />
Amador<br />
Ione<br />
Jackson<br />
Plymouth<br />
Sutter Creek<br />
<br />
====[http://gis.buttecounty.net/public/index.html?viewer=pwsearch/ Butte County]====<br />
<br />
Biggs<br />
Chico<br />
Gridley<br />
Oroville<br />
Paradise<br />
<br />
====[http://mapserver.co.calaveras.ca.us/genplan_pub/index.html Calaveras County]====<br />
<br />
Angels Camp<br />
<br />
====[http://colusacountydpw.maps.arcgis.com/apps/webappviewer/index.html?id=ba6fd932ef964ce7b9f17e6fdfd2f6f2 Colusa County]==== <br />
<br />
Colusa<br />
Williams<br />
<br />
====[https://ccmap.cccounty.us/Html5/index.html?viewer=CCMAP Contra Costa County]====<br />
<br />
[http://www.antiochprospector.com/ Antioch]<br />
Brentwood<br />
Clayton<br />
Concord<br />
Danville<br />
El Cerrito<br />
Hercules<br />
Lafayette<br />
Martinez<br />
Moraga<br />
Oakley<br />
Orinda<br />
Pinole<br />
Pittsburg<br />
Pleasant Hill<br />
[http://www.ci.richmond.ca.us/index.aspx?NID=865 Richmond]<br />
San Pablo<br />
San Ramon<br />
Walnut Creek<br />
<br />
====Del Norte County====<br />
<br />
Crescent City<br />
<br />
====[https://see-eldorado.edcgov.us/ugotnet/ El Dorado County]====<br />
<br />
Placerville<br />
South Lake Tahoe<br />
<br />
====[https://gisportal.co.fresno.ca.us/portal/apps/webappviewer/index.html?id=b921843d343d4df998b5b3c6a301756a Fresno County]====<br />
<br />
Clovis<br />
Coalinga<br />
Firebaugh<br />
Fowler<br />
[http://gis4u.fresno.gov/viewer/ Fresno]<br />
Huron<br />
Kerman<br />
Kingsburg<br />
Mendota<br />
Orange Cove<br />
Parlier<br />
Reedley<br />
Sanger<br />
Selma<br />
<br />
====[http://gis.gcppwa.net/districts/ Glenn County]====<br />
<br />
Orland<br />
Willows<br />
<br />
====[http://gis.co.humboldt.ca.us/Freeance/Client/PublicAccess1/index.html?appconfig=podgis4 Humboldt County]====<br />
<br />
Arcata<br />
Blue Lake<br />
Eureka<br />
Ferndale<br />
Fortuna<br />
Rio Dell<br />
Trinidad<br />
<br />
====[https://www.geoviewer8.com/?username=icpublic&password=icpublic Imperial County]====<br />
<br />
Brawley<br />
Calexico<br />
Calipatria<br />
El Centro<br />
Holtville<br />
Imperial<br />
Westmorland<br />
<br />
====[https://inyocounty.maps.arcgis.com/apps/webappviewer/index.html?id=f3db09212fcf4d5eb0beee16f26e040c Inyo County]====<br />
<br />
Bishop<br />
<br />
====[http://maps.co.kern.ca.us/H5/index.html?viewer=public Kern County]====<br />
<br />
Arvin<br />
[https://cob.maps.arcgis.com/apps/webappviewer/index.html?id=9174f084addc450286ac067a56fdb83f Bakersfield] <br />
California City<br />
Delano<br />
Maricopa<br />
Mcfarland<br />
Ridgecrest<br />
Shafter<br />
Taft<br />
Tehachapi<br />
Wasco<br />
<br />
====[http://www.kingscountygis.com/maps/ Kings County]====<br />
<br />
Avenal<br />
Corcoran<br />
Hanford<br />
Lemoore<br />
<br />
====Lake County====<br />
<br />
Clearlake<br />
Lakeport<br />
<br />
====Lassen County====<br />
<br />
Susanville<br />
<br />
====[http://rpgis.isd.lacounty.gov/Html5Viewer/index.html?viewer=GISNET_Public.GIS-NET_Public Los Angeles County]==== <br />
<br />
[http://maps.assessor.lacounty.gov/GVH_2_2/Index.html?configBase=http://maps.assessor.lacounty.gov/Geocortex/Essentials/REST/sites/PAIS/viewers/PAIS_hv/virtualdirectory/Resources/Config/Default LA County Assessor's map]<br />
<br />
Agoura Hills<br />
Alhambra<br />
Arcadia<br />
Artesia<br />
Avalon<br />
Azusa<br />
Baldwin Park<br />
Bell<br />
Bellflower<br />
Bell Gardens<br />
Beverly Hills<br />
Bradbury<br />
[http://burbankca.maps.arcgis.com/apps/Solutions/s2.html?appid=06adc1d9e2c84c5f9a366014cbef7cb0 Burbank]<br />
Calabasas<br />
[http://www.carsonproperty.info/ Carson]<br />
Cerritos<br />
Claremont<br />
Commerce<br />
Compton<br />
Covina<br />
Cudahy<br />
[http://gisproxy.culvercity.org/SilverlightViewer_1_8/Viewer.html?Viewer=ExternalInfo Culver City - ''requires Silverlight'']<br />
Diamond Bar<br />
Downey<br />
Duarte<br />
El Monte<br />
[http://www.elsegundo.org/civicax/filebank/blobdload.aspx?blobid=7552 ''El Segundo'']<br />
Gardena<br />
Glendale<br />
Glendora<br />
Hawaiian Gardens<br />
Hawthorne<br />
[http://www.hermosabch.org/modules/showdocument.aspx?documentid=417 ''Hermosa Beach'']<br />
Hidden Hills<br />
Huntington Park<br />
Industry<br />
Inglewood<br />
Irwindale<br />
La Canada Flintridge<br />
La Habra Heights<br />
Lakewood<br />
La Mirada<br />
Lancaster<br />
La Puente<br />
La Verne<br />
Lawndale<br />
Lomita<br />
Long Beach<br />
[http://navigatela.lacity.org/navigatela/ Los Angeles]<br />
Lynwood<br />
Malibu<br />
[http://manhattanbeach.geocortex.com/maps/ Manhattan Beach]<br />
Maywood<br />
Monrovia<br />
Montebello<br />
Monterey Park<br />
Norwalk<br />
[http://maps.cityofpalmdale.org/FMv2/default.aspx Palmdale]<br />
Palos Verdes Estates<br />
Paramount<br />
Pasadena<br />
Pico Rivera<br />
Pomona<br />
Rancho Palos Verdes<br />
Redondo Beach<br />
Rolling Hills<br />
Rolling Hills Estates<br />
Rosemead<br />
San Dimas<br />
San Fernando<br />
San Gabriel<br />
San Marino<br />
[http://gis.santa-clarita.com/html5/MasterPUB.html Santa Clarita] [http://gis.santa-clarita.com/slv/?Viewer=MasterPUB Santa Clarita Alt - ''requires Silverlight'']<br />
Santa Fe Springs<br />
[http://csmgisweb.smgov.net/Html5Viewer/Index.html?configBase=http://csmgisweb.smgov.net/Geocortex/Essentials/REST/sites/laco_test/viewers/LACO_base_test_html5/virtualdirectory/Resources/Config/Default Santa Monica]<br />
Sierra Madre<br />
Signal Hill<br />
South El Monte<br />
South Gate<br />
South Pasadena<br />
Temple City<br />
[http://www.torranceca.gov/PDF/StnxmapTARA(everything)2016_24X36.pdf Torrance]<br />
Vernon<br />
Walnut<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/westcovina/prerelease_index.aspx# West Covina]<br />
West Hollywood<br />
Westlake Village<br />
Whittier<br />
<br />
====[http://countymadera.maps.arcgis.com/apps/Solutions/s2.html?appid=894807923d764977bdacde99fb4508ae Madera County]====<br />
<br />
Chowchilla<br />
Madera<br />
<br />
====[http://www.marinmap.org/Html5Viewer/Index.html?viewer=mmdataviewer Marin County]====<br />
<br />
Belvedere<br />
Corte Madera<br />
Fairfax<br />
Larkspur<br />
Mill Valley<br />
Novato<br />
Ross<br />
San Anselmo<br />
San Rafael<br />
Sausalito<br />
Tiburon<br />
<br />
====Mariposa County====<br />
<br />
No Cities<br />
<br />
====[http://www.co.mendocino.ca.us/econdev/gis/mapping.htm Mendocino County]====<br />
<br />
Fort Bragg<br />
Point Arena<br />
Ukiah<br />
Willits<br />
<br />
====[http://map.co.merced.ca.us/SL/?Viewer=mapmerced Merced County]====<br />
[http://mcaggis.com/MCAGBaseMap/ Alternate map]<br />
<br />
Atwater<br />
Dos Palos<br />
Gustine<br />
Livingston<br />
Los Banos<br />
Merced<br />
<br />
====Modoc County====<br />
<br />
Alturas<br />
<br />
====[https://monomammoth.maps.arcgis.com/apps/Viewer/index.html?appid=8670c63cda0540b39c3ae388cdd7db78 Mono County]====<br />
(not exactly a GIS, but seems to be official assessor info)<br />
<br />
Mammoth Lakes<br />
<br />
====[http://65.249.61.35/MCo_MapViewer/ Monterey County]====<br />
<br />
Carmel-By-The-Sea<br />
Del Rey Oaks<br />
Gonzales<br />
Greenfield<br />
King City<br />
Marina<br />
Monterey<br />
Pacific Grove<br />
Salinas<br />
Sand City<br />
Seaside<br />
Soledad<br />
<br />
====[http://gis.napa.ca.gov/html5viewer/?viewer=public_html Napa County]====<br />
<br />
American Canyon<br />
Calistoga<br />
Napa<br />
St Helena<br />
<br />
====[http://gis.nevcounty.net/MyNeighborhood/ Nevada County]====<br />
<br />
Grass Valley<br />
Nevada City<br />
[https://townoftruckee.maps.arcgis.com/apps/webappviewer/index.html?id=902bc3bcf8bb4c1b94f45d9b10c343f6 Truckee]<br />
<br />
====[https://www.ocgis.com/ocpw/landrecords/ Orange County]====<br />
<br />
[https://alisoviejo.maps.arcgis.com/apps/webappviewer/index.html?id=9ee5473b3ccb41c69c340ab16fdbfdf8 Aliso Viejo]<br />
Anaheim<br />
Brea<br />
Buena Park<br />
Costa Mesa<br />
Cypress<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/danapoint/index.aspx Dana Point]<br />
Fountain Valley<br />
[http://fullertoncagis.maps.arcgis.com/apps/webappviewer/index.html?id=ff9b168a7d2c448abefe7d406e14b549 Fullerton]<br />
Garden Grove<br />
Huntington Beach<br />
[http://gis.cityofirvine.org/onlineparcel/ Irvine]<br />
[http://gisweb.lagunabeachcity.net/Html5Viewer/index.html?configBase=http://gisweb.lagunabeachcity.net/Geocortex/Essentials/REST/sites/GISMap3/viewers/HTML5_22/virtualdirectory/Resources/Config/Default Laguna Beach]<br />
Laguna Hills<br />
[http://gis.cityoflagunaniguel.org/PublicViewer/ Laguna Niguel]<br />
Laguna Woods<br />
La Habra<br />
[http://www.lakeforestca.gov/DocumentCenter/View/1191 ''Lake Forest'']<br />
La Palma<br />
Los Alamitos<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/Missionviejo/index.aspx Mission Viejo]<br />
[http://nbgis.newportbeachca.gov/NewportHTML5Viewer/?viewer=publicsite Newport Beach]<br />
[http://gis.cityoforange.org/maps/centerlineties.html Orange]<br />
Placentia<br />
Rancho Santa Margarita<br />
San Clemente<br />
San Juan Capistrano<br />
[http://maps.digitalmapcentral.com/production/vecommunityview/cities/santaana/index.aspx# Santa Ana]<br />
Seal Beach<br />
Stanton<br />
Tustin<br />
Villa Park<br />
Westminster<br />
Yorba Linda<br />
<br />
====[http://placer.ca.gov/map-search Placer County]====<br />
<br />
Auburn<br />
Colfax<br />
Lincoln<br />
Loomis<br />
Rocklin<br />
[http://www.roseville.ca.us/eservices/maps_n_data/map_center.asp Roseville]<br />
<br />
====[https://secure.simplelayers.com/?do=start&project=1111&application=CG3Viewer&embedded=1&bgcolor=ffffff&width=975&height=735&context=22 Plumas County]====<br />
<br />
Portola<br />
<br />
====[https://gis1.countyofriverside.us/Html5Viewer/index.html?viewer=MMC_Public Riverside County]====<br />
<br />
Banning<br />
[http://beaumontca.gov/index.aspx?NID=983 Beaumont]<br />
Blythe<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/calimesa/index.aspx# Calimesa]<br />
Canyon Lake<br />
Cathedral City<br />
Coachella<br />
[http://cityofcorona.maps.arcgis.com/apps/webappviewer/index.html?id=36c7d42973f441819670d6f812b6b280 Corona]<br />
Desert Hot Springs<br />
[http://www.eastvaleca.gov/index.aspx?page=43 Eastvale]<br />
Hemet<br />
Indian Wells<br />
Indio<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/JurupaValley/index.aspx Jurupa Valley]<br />
Lake Elsinore<br />
La Quinta<br />
Menifee<br />
[http://www.moreno-valley.ca.us/city_hall/city_maps.shtml Moreno Valley]<br />
Murrieta<br />
Norco<br />
Palm Desert<br />
Palm Springs<br />
[http://maps.digitalmapcentral.com/production/vecommunityview/cities/perris/index.aspx Perris]<br />
[https://www.ranchomirageca.gov/content_files/pdf/about_rancho_mirage/city_map.pdf Rancho Mirage]<br />
Riverside<br />
San Jacinto<br />
Temecula<br />
Wildomar<br />
<br />
====[http://generalmap.gis.saccounty.net/JSViewer/county_portal.html Sacramento County]====<br />
[http://assessorparcelviewer.saccounty.net/GISViewer/Default.aspx Assessor map] for addresses / House Numbers<br />
<br />
Citrus Heights<br />
[http://elkgrovemap.gis.saccounty.net/jsviewer/elkgrove.html Elk Grove]<br />
Folsom<br />
Galt<br />
Isleton<br />
Rancho Cordova<br />
Sacramento<br />
<br />
====[https://cosb.maps.arcgis.com/home/webmap/viewer.html?webmap=4071773f6b004aaf8ee8d275b6b400b2 San Benito County]====<br />
Problem: http://www.lynxgis.com/sanbenitoco/index2.cfm<br />
Hollister<br />
San Juan Bautista<br />
<br />
====[https://www.arcgis.com/apps/webappviewer/index.html?id=87e70bb9b6994559ba7512792588d57a San Bernardino County]====<br />
<br />
Adelanto<br />
Apple Valley<br />
Barstow<br />
Big Bear Lake<br />
[http://www.cityofchino.org/home/showdocument?id=409 ''Chino'']<br />
Chino Hills<br />
Colton<br />
Fontana<br />
Grand Terrace<br />
Hesperia<br />
Highland<br />
Loma Linda<br />
Montclair<br />
Needles<br />
Ontario<br />
Rancho Cucamonga<br />
Redlands<br />
Rialto<br />
San Bernardino<br />
Twentynine Palms<br />
Upland<br />
Victorville<br />
Yucaipa<br />
Yucca Valley<br />
<br />
====[http://www.sangis.org/ San Diego County]====<br />
<br />
Carlsbad<br />
Chula Vista<br />
Coronado<br />
[http://delmar.geoviewer.io/ Del Mar]<br />
El Cajon<br />
Encinitas<br />
Escondido<br />
Imperial Beach<br />
La Mesa<br />
Lemon Grove<br />
National City<br />
[http://oceansidefiles.com/uploads/Water/PlanningViewer/index.html Oceanside]<br />
Poway<br />
San Diego<br />
San Marcos<br />
Santee<br />
Solana Beach<br />
[https://gis.cityofvista.com/VistaGIS/ Vista]<br />
<br />
====[http://sfgov.maps.arcgis.com/home/webmap/viewer.html?useExisting=1 San Francisco County]====<br />
<br />
San Francisco City and County are one and the same<br />
<br />
====[http://www.sjmap.org/DistrictViewer/Disclaimer.htm San Joaquin County]====<br />
<br />
Escalon<br />
Lathrop<br />
Lodi<br />
Manteca<br />
Ripon<br />
[http://www.stocktongov.com/government/departments/communityDevelop/genPlanMap.html Stockton]<br />
Tracy<br />
<br />
====[http://www.sloplanning.org/PermitView/MapSearch San Luis Obispo County]====<br />
<br />
Arroyo Grande<br />
Atascadero<br />
El Paso De Robles<br />
Grover Beach<br />
Morro Bay<br />
Pismo Beach<br />
San Luis Obispo<br />
<br />
====[https://gis.smcgov.org/Html5Viewer/?viewer=raster San Mateo County]====<br />
<br />
Atherton<br />
Belmont<br />
Brisbane<br />
Burlingame<br />
Colma<br />
Daly City<br />
East Palo Alto<br />
Foster City<br />
Half Moon Bay<br />
Hillsborough<br />
Menlo Park<br />
Millbrae<br />
Pacifica<br />
Portola Valley<br />
Redwood City<br />
San Bruno<br />
San Carlos<br />
San Mateo<br />
South San Francisco<br />
Woodside<br />
<br />
====[https://secure.simplelayers.com/?do=start&project=939&application=CG3Viewer&embedded=1&query_url=0&context=2 Santa Barbara County]====<br />
<br />
Buellton<br />
Carpinteria<br />
Goleta<br />
Guadalupe<br />
Lompoc<br />
Santa Barbara<br />
Santa Maria<br />
Solvang<br />
<br />
====[http://www.sccgov.org/gis/SCCPubInteractiveMap/# Santa Clara County]====<br />
<br />
Campbell<br />
Cupertino<br />
Gilroy<br />
Los Altos<br />
Los Altos Hills<br />
Los Gatos<br />
Milpitas<br />
Monte Sereno<br />
Morgan Hill<br />
Mountain View<br />
Palo Alto<br />
San Jose<br />
Santa Clara<br />
Saratoga<br />
Sunnyvale<br />
<br />
====[http://gis.co.santa-cruz.ca.us/PublicGISWeb/ Santa Cruz County]====<br />
<small>Recommend setting Base Map to None for above</small><br />
<br />
Capitola<br />
Santa Cruz<br />
Scotts Valley<br />
Watsonville<br />
<br />
====[http://gis.co.shasta.ca.us/Parcels/ Shasta County]====<br />
<br />
Anderson<br />
[http://maps.ci.redding.ca.us/redding_pub/home/index.aspx Redding]<br />
Shasta Lake<br />
<br />
====[http://demos2.calcad.com:8080/SierraCountyPublic/fusion.php Sierra County]====<br />
<br />
Loyalton<br />
<br />
====Siskiyou County====<br />
<br />
Dorris<br />
Dunsmuir<br />
Etna<br />
Fort Jone<br />
Montague<br />
Mount Shasta<br />
Tulelake<br />
Weed<br />
Yreka<br />
<br />
====[http://regis.solanocounty.com/Html5Viewer/Index.html?configBase=http://regis.solanocounty.com/Geocortex/Essentials/REST/sites/TaxParcelViewerNO/viewers/TaxParcelViewer-Solano_GIS_Viewer/virtualdirectory/Resources/Config/Default Solano County]====<br />
<br />
Benicia<br />
Dixon<br />
Fairfield<br />
Rio Vista<br />
Suisun City<br />
Vacaville<br />
[http://gis.zoomprospector.com/client/Vallejo/ Vallejo]<br />
<br />
====[https://sonomamap.maps.arcgis.com/apps/webappviewer/index.html?id=06ac7fe1b8554171b4682dc141293962 Sonoma County]====<br />
<br />
Cloverdale<br />
Cotati<br />
Healdsburg<br />
Petaluma<br />
Rohnert Park<br />
Santa Rosa<br />
Sebastopol<br />
Sonoma Windsor<br />
<br />
====[http://gis.stancounty.com/giscentral/public/map/esri/flex/parcelfinder/index.jsp# Stanislaus County]====<br />
<br />
Ceres<br />
Hughson<br />
[http://gis.modestogov.com/ Modesto*]<br />
Newman<br />
Oakdale<br />
Patterson<br />
Riverbank<br />
Turlock<br />
Waterford<br />
<br />
====Sutter County====<br />
[http://www.co.sutter.ca.us/doc/apps/road_closures Construction and Road Closures]<br />
<br />
Live Oak<br />
Yuba City<br />
<br />
====[http://www.arcgis.tehamacountypublicworks.ca.gov/ Tehama County]====<br />
<br />
Corning<br />
[http://planningsites.org/RedBluffPlanning/ Red Bluff]<br />
Tehama<br />
<br />
====[http://trinitycounty.maps.arcgis.com/apps/Viewer/index.html?appid=320cf1c1558c43c8b1f2f70c23d35026 Trinity County]====<br />
<br />
No Cities<br />
<br />
====Tulare County====<br />
<br />
:[http://tularecounty.ca.gov/tcict/index.cfm/geographic-information-system-gis/gis-maps/dinuba-city-map-jan-2008/ Dinuba] 2008 static map<br />
<br />
:[http://tularecounty.ca.gov/tcict/index.cfm/geographic-information-system-gis/gis-maps/exeter-city-map-jan-2008/ Exeter] 2008 Static map<br />
<br />
:[http://tularecounty.ca.gov/tcict/index.cfm/geographic-information-system-gis/gis-maps/farmersville-city-map-jan-2008/ Farmersville] 2008 Static map<br />
<br />
Lindsay<br />
[http://www.ci.porterville.ca.us/depts/CommunityDevelopment/webmaps/PublicWebmapPortal/webmap.html Porterville]<br />
[http://www.tulare.ca.gov/departments/community-development/development-services/planning/zoning-map Tulare] <br />
[http://visalia.maps.arcgis.com/apps/webappviewer/index.html?id=e78dfbb593044bf6bc1cf4f0d63c9160 Visalia]<br />
Woodlake<br />
<br />
====[http://gis.co.tuolumne.ca.us:8093/flexviewers/General%20Plan%20And%20Zoning/ Tuolumne County]====<br />
<br />
Sonora<br />
<br />
====[http://gis.ventura.org/Html5Viewer/index.html?viewer=CountyView.CountyView_gvh Ventura County]====<br />
<br />
Camarillo<br />
Fillmore<br />
Moorpark<br />
Ojai<br />
Oxnard<br />
Port Hueneme<br />
San Buenaventura<br />
Santa Paula<br />
Simi Valley<br />
Thousand Oaks<br />
Ventura<br />
<br />
====[http://yolo-gis-prod.yolocounty.org/SilverlightViewer_2_1/Viewer.html?ViewerConfig=http://yolo-gis-prod.yolocounty.org/Geocortex/Essentials/INTERNETPUBLIC/REST/sites/GIS_Public_Viewer/viewers/GIS_Public_Viewer/virtualdirectory/Config/Viewer.xml Yolo County]====<br />
<br />
Davis<br />
West Sacramento<br />
Winters<br />
Woodland<br />
<br />
====[http://gis.co.yuba.ca.us/portal_apps/parcelapp.html Yuba County]====<br />
<br />
Marysville<br />
Wheatland</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Tonestertm/California_GIS_sources&diff=174302User:Tonestertm/California GIS sources2021-07-03T17:10:09Z<p>Tonestertm: /* Riverside County */ Update Riverside County link. Thanks, turbomkt!</p>
<hr />
<div><span style="color:#FF0000">This page is under construction.</span> If you'd like to help out, please, [http://www.waze.com/forum/ucp.php?i=pm&mode=compose&username=tonestertm PM tonestertm] before making any changes.<br />
<br />
<br />
'''A Collection of interactive GIS maps for municipalities throughout California.'''<br />
<br />
<br />
Caltrans has a [https://caltrans.maps.arcgis.com/apps/webappviewer/index.html?id=026e830c914c495797c969a3e5668538 new interactive map] with layers for Functional Classification, counties, Caltrans Districts, and a few other useful things. Note that the FC data on here is the same as the CRS Grid maps accessible through the [https://wazeopedia.waze.com/wiki/USA/User:Tonestertm/CRS_grid_bookmarklet CRS Grid bookmarklet].<br />
<br />
The [http://portal.gis.ca.gov/geoportal/viewer/index.jsp California Geoportal Viewer] is an all-state viewer, with only a Roads layer. It is very quick and easy to use, but may not be quite as up to date as local maps. <br />
<br />
''Note: In most cases, the links below will land you on the map itself, but sometimes it is is necessary to accept a disclaimer before viewing the map. A few maps require the use of Internet Explorer (noted), others require installation of the Silverlight plugin, and still others require an Autodesk plugin. Where there is no ''County'' interactive viewer, static map pages are linked and so indicated (I hope, let me know) by italics. A few counties do not yet publish online maps; use the Geoportal Viewer for these. '' <br />
<br />
Above all, understand that map availability is constantly changing. If you don't see what you're looking for here, try a search for "GIS" and the location you're looking for; it's quite possible there's a map now. And if you find one, let me know, so I can add it! <br />
<br />
Thanks to users '''ababcock, abc1357, AquaZR1, bwawsc, citeman, Cardyin, dfortney, robertonthego, turbomkt''' for contributing! (Anyone I've missed? Please let me know) <br />
<br />
[[File:California_counties_outline_map.png|right|California counties outline map]]<br />
<br />
====[http://www.acgov.org/assessor/resources/parcel_viewer.htm Alameda County]====<br />
<br />
Alameda<br />
Albany<br />
[http://www.cityofberkeley.info/ContentDisplay.aspx?id=55706 Berkeley]<br />
Dublin<br />
Emeryville<br />
Fremont<br />
Hayward<br />
Livermore<br />
Newark<br />
[http://mapgis.oaklandnet.com/planmap/ Oakland]<br />
Piedmont<br />
Pleasanton<br />
San Leandro<br />
Union City<br />
<br />
====Alpine County====<br />
<br />
No Cities<br />
<br />
====[https://gisviewer.amadorgov.org/gpv/Viewer.aspx Amador County]====<br />
<br />
<br />
Amador<br />
Ione<br />
Jackson<br />
Plymouth<br />
Sutter Creek<br />
<br />
====[http://gis.buttecounty.net/public/index.html?viewer=pwsearch/ Butte County]====<br />
<br />
Biggs<br />
Chico<br />
Gridley<br />
Oroville<br />
Paradise<br />
<br />
====[http://mapserver.co.calaveras.ca.us/genplan_pub/index.html Calaveras County]====<br />
<br />
Angels Camp<br />
<br />
====[http://colusacountydpw.maps.arcgis.com/apps/webappviewer/index.html?id=ba6fd932ef964ce7b9f17e6fdfd2f6f2 Colusa County]==== <br />
<br />
Colusa<br />
Williams<br />
<br />
====[https://ccmap.cccounty.us/Html5/index.html?viewer=CCMAP Contra Costa County]====<br />
<br />
[http://www.antiochprospector.com/ Antioch]<br />
Brentwood<br />
Clayton<br />
Concord<br />
Danville<br />
El Cerrito<br />
Hercules<br />
Lafayette<br />
Martinez<br />
Moraga<br />
Oakley<br />
Orinda<br />
Pinole<br />
Pittsburg<br />
Pleasant Hill<br />
[http://www.ci.richmond.ca.us/index.aspx?NID=865 Richmond]<br />
San Pablo<br />
San Ramon<br />
Walnut Creek<br />
<br />
====Del Norte County====<br />
<br />
Crescent City<br />
<br />
====[https://see-eldorado.edcgov.us/ugotnet/ El Dorado County]====<br />
<br />
Placerville<br />
South Lake Tahoe<br />
<br />
====[https://gisportal.co.fresno.ca.us/portal/apps/webappviewer/index.html?id=b921843d343d4df998b5b3c6a301756a Fresno County]====<br />
<br />
Clovis<br />
Coalinga<br />
Firebaugh<br />
Fowler<br />
[http://gis4u.fresno.gov/viewer/ Fresno]<br />
Huron<br />
Kerman<br />
Kingsburg<br />
Mendota<br />
Orange Cove<br />
Parlier<br />
Reedley<br />
Sanger<br />
Selma<br />
<br />
====[http://gis.gcppwa.net/districts/ Glenn County]====<br />
<br />
Orland<br />
Willows<br />
<br />
====[http://gis.co.humboldt.ca.us/Freeance/Client/PublicAccess1/index.html?appconfig=podgis4 Humboldt County]====<br />
<br />
Arcata<br />
Blue Lake<br />
Eureka<br />
Ferndale<br />
Fortuna<br />
Rio Dell<br />
Trinidad<br />
<br />
====[https://www.geoviewer8.com/?username=icpublic&password=icpublic Imperial County]====<br />
<br />
Brawley<br />
Calexico<br />
Calipatria<br />
El Centro<br />
Holtville<br />
Imperial<br />
Westmorland<br />
<br />
====[https://inyocounty.maps.arcgis.com/apps/webappviewer/index.html?id=f3db09212fcf4d5eb0beee16f26e040c Inyo County]====<br />
<br />
Bishop<br />
<br />
====[http://maps.co.kern.ca.us/H5/index.html?viewer=public Kern County]====<br />
<br />
Arvin<br />
[https://cob.maps.arcgis.com/apps/webappviewer/index.html?id=9174f084addc450286ac067a56fdb83f Bakersfield] <br />
California City<br />
Delano<br />
Maricopa<br />
Mcfarland<br />
Ridgecrest<br />
Shafter<br />
Taft<br />
Tehachapi<br />
Wasco<br />
<br />
====[http://www.kingscountygis.com/maps/ Kings County]====<br />
<br />
Avenal<br />
Corcoran<br />
Hanford<br />
Lemoore<br />
<br />
====Lake County====<br />
<br />
Clearlake<br />
Lakeport<br />
<br />
====Lassen County====<br />
<br />
Susanville<br />
<br />
====[http://rpgis.isd.lacounty.gov/Html5Viewer/index.html?viewer=GISNET_Public.GIS-NET_Public Los Angeles County]==== <br />
<br />
[http://maps.assessor.lacounty.gov/GVH_2_2/Index.html?configBase=http://maps.assessor.lacounty.gov/Geocortex/Essentials/REST/sites/PAIS/viewers/PAIS_hv/virtualdirectory/Resources/Config/Default LA County Assessor's map]<br />
<br />
Agoura Hills<br />
Alhambra<br />
Arcadia<br />
Artesia<br />
Avalon<br />
Azusa<br />
Baldwin Park<br />
Bell<br />
Bellflower<br />
Bell Gardens<br />
Beverly Hills<br />
Bradbury<br />
[http://burbankca.maps.arcgis.com/apps/Solutions/s2.html?appid=06adc1d9e2c84c5f9a366014cbef7cb0 Burbank]<br />
Calabasas<br />
[http://www.carsonproperty.info/ Carson]<br />
Cerritos<br />
Claremont<br />
Commerce<br />
Compton<br />
Covina<br />
Cudahy<br />
[http://gisproxy.culvercity.org/SilverlightViewer_1_8/Viewer.html?Viewer=ExternalInfo Culver City - ''requires Silverlight'']<br />
Diamond Bar<br />
Downey<br />
Duarte<br />
El Monte<br />
[http://www.elsegundo.org/civicax/filebank/blobdload.aspx?blobid=7552 ''El Segundo'']<br />
Gardena<br />
Glendale<br />
Glendora<br />
Hawaiian Gardens<br />
Hawthorne<br />
[http://www.hermosabch.org/modules/showdocument.aspx?documentid=417 ''Hermosa Beach'']<br />
Hidden Hills<br />
Huntington Park<br />
Industry<br />
Inglewood<br />
Irwindale<br />
La Canada Flintridge<br />
La Habra Heights<br />
Lakewood<br />
La Mirada<br />
Lancaster<br />
La Puente<br />
La Verne<br />
Lawndale<br />
Lomita<br />
Long Beach<br />
[http://navigatela.lacity.org/navigatela/ Los Angeles]<br />
Lynwood<br />
Malibu<br />
[http://manhattanbeach.geocortex.com/maps/ Manhattan Beach]<br />
Maywood<br />
Monrovia<br />
Montebello<br />
Monterey Park<br />
Norwalk<br />
[http://maps.cityofpalmdale.org/FMv2/default.aspx Palmdale]<br />
Palos Verdes Estates<br />
Paramount<br />
Pasadena<br />
Pico Rivera<br />
Pomona<br />
Rancho Palos Verdes<br />
Redondo Beach<br />
Rolling Hills<br />
Rolling Hills Estates<br />
Rosemead<br />
San Dimas<br />
San Fernando<br />
San Gabriel<br />
San Marino<br />
[http://gis.santa-clarita.com/html5/MasterPUB.html Santa Clarita] [http://gis.santa-clarita.com/slv/?Viewer=MasterPUB Santa Clarita Alt - ''requires Silverlight'']<br />
Santa Fe Springs<br />
[http://csmgisweb.smgov.net/Html5Viewer/Index.html?configBase=http://csmgisweb.smgov.net/Geocortex/Essentials/REST/sites/laco_test/viewers/LACO_base_test_html5/virtualdirectory/Resources/Config/Default Santa Monica]<br />
Sierra Madre<br />
Signal Hill<br />
South El Monte<br />
South Gate<br />
South Pasadena<br />
Temple City<br />
[http://www.torranceca.gov/PDF/StnxmapTARA(everything)2016_24X36.pdf Torrance]<br />
Vernon<br />
Walnut<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/westcovina/prerelease_index.aspx# West Covina]<br />
West Hollywood<br />
Westlake Village<br />
Whittier<br />
<br />
====[http://countymadera.maps.arcgis.com/apps/Solutions/s2.html?appid=894807923d764977bdacde99fb4508ae Madera County]====<br />
<br />
Chowchilla<br />
Madera<br />
<br />
====[http://www.marinmap.org/Html5Viewer/Index.html?viewer=mmdataviewer Marin County]====<br />
<br />
Belvedere<br />
Corte Madera<br />
Fairfax<br />
Larkspur<br />
Mill Valley<br />
Novato<br />
Ross<br />
San Anselmo<br />
San Rafael<br />
Sausalito<br />
Tiburon<br />
<br />
====Mariposa County====<br />
<br />
No Cities<br />
<br />
====[http://www.co.mendocino.ca.us/econdev/gis/mapping.htm Mendocino County]====<br />
<br />
Fort Bragg<br />
Point Arena<br />
Ukiah<br />
Willits<br />
<br />
====[http://map.co.merced.ca.us/SL/?Viewer=mapmerced Merced County]====<br />
[http://mcaggis.com/MCAGBaseMap/ Alternate map]<br />
<br />
Atwater<br />
Dos Palos<br />
Gustine<br />
Livingston<br />
Los Banos<br />
Merced<br />
<br />
====Modoc County====<br />
<br />
Alturas<br />
<br />
====[https://monomammoth.maps.arcgis.com/apps/Viewer/index.html?appid=8670c63cda0540b39c3ae388cdd7db78 Mono County]====<br />
(not exactly a GIS, but seems to be official assessor info)<br />
<br />
Mammoth Lakes<br />
<br />
====[http://65.249.61.35/MCo_MapViewer/ Monterey County]====<br />
<br />
Carmel-By-The-Sea<br />
Del Rey Oaks<br />
Gonzales<br />
Greenfield<br />
King City<br />
Marina<br />
Monterey<br />
Pacific Grove<br />
Salinas<br />
Sand City<br />
Seaside<br />
Soledad<br />
<br />
====[http://gis.napa.ca.gov/html5viewer/?viewer=public_html Napa County]====<br />
<br />
American Canyon<br />
Calistoga<br />
Napa<br />
St Helena<br />
<br />
====[http://gis.nevcounty.net/MyNeighborhood/ Nevada County]====<br />
<br />
Grass Valley<br />
Nevada City<br />
[https://townoftruckee.maps.arcgis.com/apps/webappviewer/index.html?id=902bc3bcf8bb4c1b94f45d9b10c343f6 Truckee]<br />
<br />
====[https://www.ocgis.com/ocpw/landrecords/ Orange County]====<br />
<br />
[https://alisoviejo.maps.arcgis.com/apps/webappviewer/index.html?id=9ee5473b3ccb41c69c340ab16fdbfdf8 Aliso Viejo]<br />
Anaheim<br />
Brea<br />
Buena Park<br />
Costa Mesa<br />
Cypress<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/danapoint/index.aspx Dana Point]<br />
Fountain Valley<br />
[http://fullertoncagis.maps.arcgis.com/apps/webappviewer/index.html?id=ff9b168a7d2c448abefe7d406e14b549 Fullerton]<br />
Garden Grove<br />
Huntington Beach<br />
[http://gis.cityofirvine.org/onlineparcel/ Irvine]<br />
[http://gisweb.lagunabeachcity.net/Html5Viewer/index.html?configBase=http://gisweb.lagunabeachcity.net/Geocortex/Essentials/REST/sites/GISMap3/viewers/HTML5_22/virtualdirectory/Resources/Config/Default Laguna Beach]<br />
Laguna Hills<br />
[http://gis.cityoflagunaniguel.org/PublicViewer/ Laguna Niguel]<br />
Laguna Woods<br />
La Habra<br />
[http://www.lakeforestca.gov/DocumentCenter/View/1191 ''Lake Forest'']<br />
La Palma<br />
Los Alamitos<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/Missionviejo/index.aspx Mission Viejo]<br />
[http://nbgis.newportbeachca.gov/NewportHTML5Viewer/?viewer=publicsite Newport Beach]<br />
[http://gis.cityoforange.org/maps/centerlineties.html Orange]<br />
Placentia<br />
Rancho Santa Margarita<br />
San Clemente<br />
San Juan Capistrano<br />
[http://maps.digitalmapcentral.com/production/vecommunityview/cities/santaana/index.aspx# Santa Ana]<br />
Seal Beach<br />
Stanton<br />
Tustin<br />
Villa Park<br />
Westminster<br />
Yorba Linda<br />
<br />
====[http://placer.ca.gov/map-search Placer County]====<br />
<br />
Auburn<br />
Colfax<br />
Lincoln<br />
Loomis<br />
Rocklin<br />
[http://www.roseville.ca.us/eservices/maps_n_data/map_center.asp Roseville]<br />
<br />
====[https://secure.simplelayers.com/?do=start&project=1111&application=CG3Viewer&embedded=1&bgcolor=ffffff&width=975&height=735&context=22 Plumas County]====<br />
<br />
Portola<br />
<br />
====[https://gis1.countyofriverside.us/Html5Viewer/index.html?viewer=MMC_Public Riverside County]====<br />
<br />
Banning<br />
[http://beaumontca.gov/index.aspx?NID=983 Beaumont]<br />
Blythe<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/calimesa/index.aspx# Calimesa]<br />
Canyon Lake<br />
Cathedral City<br />
Coachella<br />
[http://cityofcorona.maps.arcgis.com/apps/webappviewer/index.html?id=36c7d42973f441819670d6f812b6b280 Corona]<br />
Desert Hot Springs<br />
[http://www.eastvaleca.gov/index.aspx?page=43 Eastvale]<br />
Hemet<br />
Indian Wells<br />
Indio<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/JurupaValley/index.aspx Jurupa Valley]<br />
Lake Elsinore<br />
La Quinta<br />
Menifee<br />
[http://www.moreno-valley.ca.us/city_hall/city_maps.shtml Moreno Valley]<br />
Murrieta<br />
Norco<br />
Palm Desert<br />
Palm Springs<br />
[http://maps.digitalmapcentral.com/production/vecommunityview/cities/perris/index.aspx Perris]<br />
[https://www.ranchomirageca.gov/content_files/pdf/about_rancho_mirage/city_map.pdf Rancho Mirage]<br />
Riverside<br />
San Jacinto<br />
Temecula<br />
Wildomar<br />
<br />
====[http://generalmap.gis.saccounty.net/JSViewer/county_portal.html Sacramento County]====<br />
[http://assessorparcelviewer.saccounty.net/GISViewer/Default.aspx Assessor map] for addresses / House Numbers<br />
<br />
Citrus Heights<br />
[http://elkgrovemap.gis.saccounty.net/jsviewer/elkgrove.html Elk Grove]<br />
Folsom<br />
Galt<br />
Isleton<br />
Rancho Cordova<br />
Sacramento<br />
<br />
====[https://cosb.maps.arcgis.com/home/webmap/viewer.html?webmap=4071773f6b004aaf8ee8d275b6b400b2 San Benito County]====<br />
Problem: http://www.lynxgis.com/sanbenitoco/index2.cfm<br />
Hollister<br />
San Juan Bautista<br />
<br />
====[https://www.arcgis.com/apps/webappviewer/index.html?id=87e70bb9b6994559ba7512792588d57a San Bernardino County]====<br />
<br />
Adelanto<br />
Apple Valley<br />
Barstow<br />
Big Bear Lake<br />
[http://www.cityofchino.org/home/showdocument?id=409 ''Chino'']<br />
Chino Hills<br />
Colton<br />
Fontana<br />
Grand Terrace<br />
Hesperia<br />
Highland<br />
Loma Linda<br />
Montclair<br />
Needles<br />
Ontario<br />
Rancho Cucamonga<br />
Redlands<br />
Rialto<br />
San Bernardino<br />
Twentynine Palms<br />
Upland<br />
Victorville<br />
Yucaipa<br />
Yucca Valley<br />
<br />
====[http://www.sangis.org/ San Diego County]====<br />
<br />
Carlsbad<br />
Chula Vista<br />
Coronado<br />
[http://delmar.geoviewer.io/ Del Mar]<br />
El Cajon<br />
Encinitas<br />
Escondido<br />
Imperial Beach<br />
La Mesa<br />
Lemon Grove<br />
National City<br />
[http://oceansidefiles.com/uploads/Water/PlanningViewer/index.html Oceanside]<br />
Poway<br />
San Diego<br />
San Marcos<br />
Santee<br />
Solana Beach<br />
[https://gis.cityofvista.com/VistaGIS/ Vista]<br />
<br />
====[http://sfgov.maps.arcgis.com/home/webmap/viewer.html?useExisting=1 San Francisco County]====<br />
<br />
San Francisco City and County are one and the same<br />
<br />
====[http://www.sjmap.org/DistrictViewer/Disclaimer.htm San Joaquin County]====<br />
<br />
Escalon<br />
Lathrop<br />
Lodi<br />
Manteca<br />
Ripon<br />
[http://www.stocktongov.com/government/departments/communityDevelop/genPlanMap.html Stockton]<br />
Tracy<br />
<br />
====[http://www.sloplanning.org/PermitView/MapSearch San Luis Obispo County]====<br />
<br />
Arroyo Grande<br />
Atascadero<br />
El Paso De Robles<br />
Grover Beach<br />
Morro Bay<br />
Pismo Beach<br />
San Luis Obispo<br />
<br />
====[http://maps.smcgov.org/planning/ San Mateo County]====<br />
<br />
Atherton<br />
Belmont<br />
Brisbane<br />
Burlingame<br />
Colma<br />
Daly City<br />
East Palo Alto<br />
Foster City<br />
Half Moon Bay<br />
Hillsborough<br />
Menlo Park<br />
Millbrae<br />
Pacifica<br />
Portola Valley<br />
Redwood City<br />
San Bruno<br />
San Carlos<br />
San Mateo<br />
South San Francisco<br />
Woodside<br />
<br />
====[https://secure.simplelayers.com/?do=start&project=939&application=CG3Viewer&embedded=1&query_url=0&context=2 Santa Barbara County]====<br />
<br />
Buellton<br />
Carpinteria<br />
Goleta<br />
Guadalupe<br />
Lompoc<br />
Santa Barbara<br />
Santa Maria<br />
Solvang<br />
<br />
====[http://www.sccgov.org/gis/SCCPubInteractiveMap/# Santa Clara County]====<br />
<br />
Campbell<br />
Cupertino<br />
Gilroy<br />
Los Altos<br />
Los Altos Hills<br />
Los Gatos<br />
Milpitas<br />
Monte Sereno<br />
Morgan Hill<br />
Mountain View<br />
Palo Alto<br />
San Jose<br />
Santa Clara<br />
Saratoga<br />
Sunnyvale<br />
<br />
====[http://gis.co.santa-cruz.ca.us/PublicGISWeb/ Santa Cruz County]====<br />
<small>Recommend setting Base Map to None for above</small><br />
<br />
Capitola<br />
Santa Cruz<br />
Scotts Valley<br />
Watsonville<br />
<br />
====[http://gis.co.shasta.ca.us/Parcels/ Shasta County]====<br />
<br />
Anderson<br />
[http://maps.ci.redding.ca.us/redding_pub/home/index.aspx Redding]<br />
Shasta Lake<br />
<br />
====[http://demos2.calcad.com:8080/SierraCountyPublic/fusion.php Sierra County]====<br />
<br />
Loyalton<br />
<br />
====Siskiyou County====<br />
<br />
Dorris<br />
Dunsmuir<br />
Etna<br />
Fort Jone<br />
Montague<br />
Mount Shasta<br />
Tulelake<br />
Weed<br />
Yreka<br />
<br />
====[http://regis.solanocounty.com/Html5Viewer/Index.html?configBase=http://regis.solanocounty.com/Geocortex/Essentials/REST/sites/TaxParcelViewerNO/viewers/TaxParcelViewer-Solano_GIS_Viewer/virtualdirectory/Resources/Config/Default Solano County]====<br />
<br />
Benicia<br />
Dixon<br />
Fairfield<br />
Rio Vista<br />
Suisun City<br />
Vacaville<br />
[http://gis.zoomprospector.com/client/Vallejo/ Vallejo]<br />
<br />
====[https://sonomamap.maps.arcgis.com/apps/webappviewer/index.html?id=06ac7fe1b8554171b4682dc141293962 Sonoma County]====<br />
<br />
Cloverdale<br />
Cotati<br />
Healdsburg<br />
Petaluma<br />
Rohnert Park<br />
Santa Rosa<br />
Sebastopol<br />
Sonoma Windsor<br />
<br />
====[http://gis.stancounty.com/giscentral/public/map/esri/flex/parcelfinder/index.jsp# Stanislaus County]====<br />
<br />
Ceres<br />
Hughson<br />
[http://gis.modestogov.com/ Modesto*]<br />
Newman<br />
Oakdale<br />
Patterson<br />
Riverbank<br />
Turlock<br />
Waterford<br />
<br />
====Sutter County====<br />
[http://www.co.sutter.ca.us/doc/apps/road_closures Construction and Road Closures]<br />
<br />
Live Oak<br />
Yuba City<br />
<br />
====[http://www.arcgis.tehamacountypublicworks.ca.gov/ Tehama County]====<br />
<br />
Corning<br />
[http://planningsites.org/RedBluffPlanning/ Red Bluff]<br />
Tehama<br />
<br />
====[http://trinitycounty.maps.arcgis.com/apps/Viewer/index.html?appid=320cf1c1558c43c8b1f2f70c23d35026 Trinity County]====<br />
<br />
No Cities<br />
<br />
====Tulare County====<br />
<br />
:[http://tularecounty.ca.gov/tcict/index.cfm/geographic-information-system-gis/gis-maps/dinuba-city-map-jan-2008/ Dinuba] 2008 static map<br />
<br />
:[http://tularecounty.ca.gov/tcict/index.cfm/geographic-information-system-gis/gis-maps/exeter-city-map-jan-2008/ Exeter] 2008 Static map<br />
<br />
:[http://tularecounty.ca.gov/tcict/index.cfm/geographic-information-system-gis/gis-maps/farmersville-city-map-jan-2008/ Farmersville] 2008 Static map<br />
<br />
Lindsay<br />
[http://www.ci.porterville.ca.us/depts/CommunityDevelopment/webmaps/PublicWebmapPortal/webmap.html Porterville]<br />
[http://www.tulare.ca.gov/departments/community-development/development-services/planning/zoning-map Tulare] <br />
[http://visalia.maps.arcgis.com/apps/webappviewer/index.html?id=e78dfbb593044bf6bc1cf4f0d63c9160 Visalia]<br />
Woodlake<br />
<br />
====[http://gis.co.tuolumne.ca.us:8093/flexviewers/General%20Plan%20And%20Zoning/ Tuolumne County]====<br />
<br />
Sonora<br />
<br />
====[http://gis.ventura.org/Html5Viewer/index.html?viewer=CountyView.CountyView_gvh Ventura County]====<br />
<br />
Camarillo<br />
Fillmore<br />
Moorpark<br />
Ojai<br />
Oxnard<br />
Port Hueneme<br />
San Buenaventura<br />
Santa Paula<br />
Simi Valley<br />
Thousand Oaks<br />
Ventura<br />
<br />
====[http://yolo-gis-prod.yolocounty.org/SilverlightViewer_2_1/Viewer.html?ViewerConfig=http://yolo-gis-prod.yolocounty.org/Geocortex/Essentials/INTERNETPUBLIC/REST/sites/GIS_Public_Viewer/viewers/GIS_Public_Viewer/virtualdirectory/Config/Viewer.xml Yolo County]====<br />
<br />
Davis<br />
West Sacramento<br />
Winters<br />
Woodland<br />
<br />
====[http://gis.co.yuba.ca.us/portal_apps/parcelapp.html Yuba County]====<br />
<br />
Marysville<br />
Wheatland</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Tonestertm/California_GIS_sources&diff=174199User:Tonestertm/California GIS sources2021-05-28T18:22:27Z<p>Tonestertm: /* San Bernardino County */ Updating URL, thanks khytak!</p>
<hr />
<div><span style="color:#FF0000">This page is under construction.</span> If you'd like to help out, please, [http://www.waze.com/forum/ucp.php?i=pm&mode=compose&username=tonestertm PM tonestertm] before making any changes.<br />
<br />
<br />
'''A Collection of interactive GIS maps for municipalities throughout California.'''<br />
<br />
<br />
Caltrans has a [https://caltrans.maps.arcgis.com/apps/webappviewer/index.html?id=026e830c914c495797c969a3e5668538 new interactive map] with layers for Functional Classification, counties, Caltrans Districts, and a few other useful things. Note that the FC data on here is the same as the CRS Grid maps accessible through the [https://wazeopedia.waze.com/wiki/USA/User:Tonestertm/CRS_grid_bookmarklet CRS Grid bookmarklet].<br />
<br />
The [http://portal.gis.ca.gov/geoportal/viewer/index.jsp California Geoportal Viewer] is an all-state viewer, with only a Roads layer. It is very quick and easy to use, but may not be quite as up to date as local maps. <br />
<br />
''Note: In most cases, the links below will land you on the map itself, but sometimes it is is necessary to accept a disclaimer before viewing the map. A few maps require the use of Internet Explorer (noted), others require installation of the Silverlight plugin, and still others require an Autodesk plugin. Where there is no ''County'' interactive viewer, static map pages are linked and so indicated (I hope, let me know) by italics. A few counties do not yet publish online maps; use the Geoportal Viewer for these. '' <br />
<br />
Above all, understand that map availability is constantly changing. If you don't see what you're looking for here, try a search for "GIS" and the location you're looking for; it's quite possible there's a map now. And if you find one, let me know, so I can add it! <br />
<br />
Thanks to users '''ababcock, abc1357, AquaZR1, bwawsc, citeman, Cardyin, dfortney, robertonthego, turbomkt''' for contributing! (Anyone I've missed? Please let me know) <br />
<br />
[[File:California_counties_outline_map.png|right|California counties outline map]]<br />
<br />
====[http://www.acgov.org/assessor/resources/parcel_viewer.htm Alameda County]====<br />
<br />
Alameda<br />
Albany<br />
[http://www.cityofberkeley.info/ContentDisplay.aspx?id=55706 Berkeley]<br />
Dublin<br />
Emeryville<br />
Fremont<br />
Hayward<br />
Livermore<br />
Newark<br />
[http://mapgis.oaklandnet.com/planmap/ Oakland]<br />
Piedmont<br />
Pleasanton<br />
San Leandro<br />
Union City<br />
<br />
====Alpine County====<br />
<br />
No Cities<br />
<br />
====[https://gisviewer.amadorgov.org/gpv/Viewer.aspx Amador County]====<br />
<br />
<br />
Amador<br />
Ione<br />
Jackson<br />
Plymouth<br />
Sutter Creek<br />
<br />
====[http://gis.buttecounty.net/public/index.html?viewer=pwsearch/ Butte County]====<br />
<br />
Biggs<br />
Chico<br />
Gridley<br />
Oroville<br />
Paradise<br />
<br />
====[http://mapserver.co.calaveras.ca.us/genplan_pub/index.html Calaveras County]====<br />
<br />
Angels Camp<br />
<br />
====[http://colusacountydpw.maps.arcgis.com/apps/webappviewer/index.html?id=ba6fd932ef964ce7b9f17e6fdfd2f6f2 Colusa County]==== <br />
<br />
Colusa<br />
Williams<br />
<br />
====[https://ccmap.cccounty.us/Html5/index.html?viewer=CCMAP Contra Costa County]====<br />
<br />
[http://www.antiochprospector.com/ Antioch]<br />
Brentwood<br />
Clayton<br />
Concord<br />
Danville<br />
El Cerrito<br />
Hercules<br />
Lafayette<br />
Martinez<br />
Moraga<br />
Oakley<br />
Orinda<br />
Pinole<br />
Pittsburg<br />
Pleasant Hill<br />
[http://www.ci.richmond.ca.us/index.aspx?NID=865 Richmond]<br />
San Pablo<br />
San Ramon<br />
Walnut Creek<br />
<br />
====Del Norte County====<br />
<br />
Crescent City<br />
<br />
====[https://see-eldorado.edcgov.us/ugotnet/ El Dorado County]====<br />
<br />
Placerville<br />
South Lake Tahoe<br />
<br />
====[https://gisportal.co.fresno.ca.us/portal/apps/webappviewer/index.html?id=b921843d343d4df998b5b3c6a301756a Fresno County]====<br />
<br />
Clovis<br />
Coalinga<br />
Firebaugh<br />
Fowler<br />
[http://gis4u.fresno.gov/viewer/ Fresno]<br />
Huron<br />
Kerman<br />
Kingsburg<br />
Mendota<br />
Orange Cove<br />
Parlier<br />
Reedley<br />
Sanger<br />
Selma<br />
<br />
====[http://gis.gcppwa.net/districts/ Glenn County]====<br />
<br />
Orland<br />
Willows<br />
<br />
====[http://gis.co.humboldt.ca.us/Freeance/Client/PublicAccess1/index.html?appconfig=podgis4 Humboldt County]====<br />
<br />
Arcata<br />
Blue Lake<br />
Eureka<br />
Ferndale<br />
Fortuna<br />
Rio Dell<br />
Trinidad<br />
<br />
====[https://www.geoviewer8.com/?username=icpublic&password=icpublic Imperial County]====<br />
<br />
Brawley<br />
Calexico<br />
Calipatria<br />
El Centro<br />
Holtville<br />
Imperial<br />
Westmorland<br />
<br />
====[https://inyocounty.maps.arcgis.com/apps/webappviewer/index.html?id=f3db09212fcf4d5eb0beee16f26e040c Inyo County]====<br />
<br />
Bishop<br />
<br />
====[http://maps.co.kern.ca.us/H5/index.html?viewer=public Kern County]====<br />
<br />
Arvin<br />
[https://cob.maps.arcgis.com/apps/webappviewer/index.html?id=9174f084addc450286ac067a56fdb83f Bakersfield] <br />
California City<br />
Delano<br />
Maricopa<br />
Mcfarland<br />
Ridgecrest<br />
Shafter<br />
Taft<br />
Tehachapi<br />
Wasco<br />
<br />
====[http://www.kingscountygis.com/maps/ Kings County]====<br />
<br />
Avenal<br />
Corcoran<br />
Hanford<br />
Lemoore<br />
<br />
====Lake County====<br />
<br />
Clearlake<br />
Lakeport<br />
<br />
====Lassen County====<br />
<br />
Susanville<br />
<br />
====[http://rpgis.isd.lacounty.gov/Html5Viewer/index.html?viewer=GISNET_Public.GIS-NET_Public Los Angeles County]==== <br />
<br />
[http://maps.assessor.lacounty.gov/GVH_2_2/Index.html?configBase=http://maps.assessor.lacounty.gov/Geocortex/Essentials/REST/sites/PAIS/viewers/PAIS_hv/virtualdirectory/Resources/Config/Default LA County Assessor's map]<br />
<br />
Agoura Hills<br />
Alhambra<br />
Arcadia<br />
Artesia<br />
Avalon<br />
Azusa<br />
Baldwin Park<br />
Bell<br />
Bellflower<br />
Bell Gardens<br />
Beverly Hills<br />
Bradbury<br />
[http://burbankca.maps.arcgis.com/apps/Solutions/s2.html?appid=06adc1d9e2c84c5f9a366014cbef7cb0 Burbank]<br />
Calabasas<br />
[http://www.carsonproperty.info/ Carson]<br />
Cerritos<br />
Claremont<br />
Commerce<br />
Compton<br />
Covina<br />
Cudahy<br />
[http://gisproxy.culvercity.org/SilverlightViewer_1_8/Viewer.html?Viewer=ExternalInfo Culver City - ''requires Silverlight'']<br />
Diamond Bar<br />
Downey<br />
Duarte<br />
El Monte<br />
[http://www.elsegundo.org/civicax/filebank/blobdload.aspx?blobid=7552 ''El Segundo'']<br />
Gardena<br />
Glendale<br />
Glendora<br />
Hawaiian Gardens<br />
Hawthorne<br />
[http://www.hermosabch.org/modules/showdocument.aspx?documentid=417 ''Hermosa Beach'']<br />
Hidden Hills<br />
Huntington Park<br />
Industry<br />
Inglewood<br />
Irwindale<br />
La Canada Flintridge<br />
La Habra Heights<br />
Lakewood<br />
La Mirada<br />
Lancaster<br />
La Puente<br />
La Verne<br />
Lawndale<br />
Lomita<br />
Long Beach<br />
[http://navigatela.lacity.org/navigatela/ Los Angeles]<br />
Lynwood<br />
Malibu<br />
[http://manhattanbeach.geocortex.com/maps/ Manhattan Beach]<br />
Maywood<br />
Monrovia<br />
Montebello<br />
Monterey Park<br />
Norwalk<br />
[http://maps.cityofpalmdale.org/FMv2/default.aspx Palmdale]<br />
Palos Verdes Estates<br />
Paramount<br />
Pasadena<br />
Pico Rivera<br />
Pomona<br />
Rancho Palos Verdes<br />
Redondo Beach<br />
Rolling Hills<br />
Rolling Hills Estates<br />
Rosemead<br />
San Dimas<br />
San Fernando<br />
San Gabriel<br />
San Marino<br />
[http://gis.santa-clarita.com/html5/MasterPUB.html Santa Clarita] [http://gis.santa-clarita.com/slv/?Viewer=MasterPUB Santa Clarita Alt - ''requires Silverlight'']<br />
Santa Fe Springs<br />
[http://csmgisweb.smgov.net/Html5Viewer/Index.html?configBase=http://csmgisweb.smgov.net/Geocortex/Essentials/REST/sites/laco_test/viewers/LACO_base_test_html5/virtualdirectory/Resources/Config/Default Santa Monica]<br />
Sierra Madre<br />
Signal Hill<br />
South El Monte<br />
South Gate<br />
South Pasadena<br />
Temple City<br />
[http://www.torranceca.gov/PDF/StnxmapTARA(everything)2016_24X36.pdf Torrance]<br />
Vernon<br />
Walnut<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/westcovina/prerelease_index.aspx# West Covina]<br />
West Hollywood<br />
Westlake Village<br />
Whittier<br />
<br />
====[http://countymadera.maps.arcgis.com/apps/Solutions/s2.html?appid=894807923d764977bdacde99fb4508ae Madera County]====<br />
<br />
Chowchilla<br />
Madera<br />
<br />
====[http://www.marinmap.org/Html5Viewer/Index.html?viewer=mmdataviewer Marin County]====<br />
<br />
Belvedere<br />
Corte Madera<br />
Fairfax<br />
Larkspur<br />
Mill Valley<br />
Novato<br />
Ross<br />
San Anselmo<br />
San Rafael<br />
Sausalito<br />
Tiburon<br />
<br />
====Mariposa County====<br />
<br />
No Cities<br />
<br />
====[http://www.co.mendocino.ca.us/econdev/gis/mapping.htm Mendocino County]====<br />
<br />
Fort Bragg<br />
Point Arena<br />
Ukiah<br />
Willits<br />
<br />
====[http://map.co.merced.ca.us/SL/?Viewer=mapmerced Merced County]====<br />
[http://mcaggis.com/MCAGBaseMap/ Alternate map]<br />
<br />
Atwater<br />
Dos Palos<br />
Gustine<br />
Livingston<br />
Los Banos<br />
Merced<br />
<br />
====Modoc County====<br />
<br />
Alturas<br />
<br />
====[https://monomammoth.maps.arcgis.com/apps/Viewer/index.html?appid=8670c63cda0540b39c3ae388cdd7db78 Mono County]====<br />
(not exactly a GIS, but seems to be official assessor info)<br />
<br />
Mammoth Lakes<br />
<br />
====[http://65.249.61.35/MCo_MapViewer/ Monterey County]====<br />
<br />
Carmel-By-The-Sea<br />
Del Rey Oaks<br />
Gonzales<br />
Greenfield<br />
King City<br />
Marina<br />
Monterey<br />
Pacific Grove<br />
Salinas<br />
Sand City<br />
Seaside<br />
Soledad<br />
<br />
====[http://gis.napa.ca.gov/html5viewer/?viewer=public_html Napa County]====<br />
<br />
American Canyon<br />
Calistoga<br />
Napa<br />
St Helena<br />
<br />
====[http://gis.nevcounty.net/MyNeighborhood/ Nevada County]====<br />
<br />
Grass Valley<br />
Nevada City<br />
[https://townoftruckee.maps.arcgis.com/apps/webappviewer/index.html?id=902bc3bcf8bb4c1b94f45d9b10c343f6 Truckee]<br />
<br />
====[https://www.ocgis.com/ocpw/landrecords/ Orange County]====<br />
<br />
[https://alisoviejo.maps.arcgis.com/apps/webappviewer/index.html?id=9ee5473b3ccb41c69c340ab16fdbfdf8 Aliso Viejo]<br />
Anaheim<br />
Brea<br />
Buena Park<br />
Costa Mesa<br />
Cypress<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/danapoint/index.aspx Dana Point]<br />
Fountain Valley<br />
[http://fullertoncagis.maps.arcgis.com/apps/webappviewer/index.html?id=ff9b168a7d2c448abefe7d406e14b549 Fullerton]<br />
Garden Grove<br />
Huntington Beach<br />
[http://gis.cityofirvine.org/onlineparcel/ Irvine]<br />
[http://gisweb.lagunabeachcity.net/Html5Viewer/index.html?configBase=http://gisweb.lagunabeachcity.net/Geocortex/Essentials/REST/sites/GISMap3/viewers/HTML5_22/virtualdirectory/Resources/Config/Default Laguna Beach]<br />
Laguna Hills<br />
[http://gis.cityoflagunaniguel.org/PublicViewer/ Laguna Niguel]<br />
Laguna Woods<br />
La Habra<br />
[http://www.lakeforestca.gov/DocumentCenter/View/1191 ''Lake Forest'']<br />
La Palma<br />
Los Alamitos<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/Missionviejo/index.aspx Mission Viejo]<br />
[http://nbgis.newportbeachca.gov/NewportHTML5Viewer/?viewer=publicsite Newport Beach]<br />
[http://gis.cityoforange.org/maps/centerlineties.html Orange]<br />
Placentia<br />
Rancho Santa Margarita<br />
San Clemente<br />
San Juan Capistrano<br />
[http://maps.digitalmapcentral.com/production/vecommunityview/cities/santaana/index.aspx# Santa Ana]<br />
Seal Beach<br />
Stanton<br />
Tustin<br />
Villa Park<br />
Westminster<br />
Yorba Linda<br />
<br />
====[http://placer.ca.gov/map-search Placer County]====<br />
<br />
Auburn<br />
Colfax<br />
Lincoln<br />
Loomis<br />
Rocklin<br />
[http://www.roseville.ca.us/eservices/maps_n_data/map_center.asp Roseville]<br />
<br />
====[https://secure.simplelayers.com/?do=start&project=1111&application=CG3Viewer&embedded=1&bgcolor=ffffff&width=975&height=735&context=22 Plumas County]====<br />
<br />
Portola<br />
<br />
====[https://gis.countyofriverside.us/Html5Viewer/?viewer=MMC_Public Riverside County]====<br />
<br />
Banning<br />
[http://beaumontca.gov/index.aspx?NID=983 Beaumont]<br />
Blythe<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/calimesa/index.aspx# Calimesa]<br />
Canyon Lake<br />
Cathedral City<br />
Coachella<br />
[http://cityofcorona.maps.arcgis.com/apps/webappviewer/index.html?id=36c7d42973f441819670d6f812b6b280 Corona]<br />
Desert Hot Springs<br />
[http://www.eastvaleca.gov/index.aspx?page=43 Eastvale]<br />
Hemet<br />
Indian Wells<br />
Indio<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/JurupaValley/index.aspx Jurupa Valley]<br />
Lake Elsinore<br />
La Quinta<br />
Menifee<br />
[http://www.moreno-valley.ca.us/city_hall/city_maps.shtml Moreno Valley]<br />
Murrieta<br />
Norco<br />
Palm Desert<br />
Palm Springs<br />
[http://maps.digitalmapcentral.com/production/vecommunityview/cities/perris/index.aspx Perris]<br />
[https://www.ranchomirageca.gov/content_files/pdf/about_rancho_mirage/city_map.pdf Rancho Mirage]<br />
Riverside<br />
San Jacinto<br />
Temecula<br />
Wildomar<br />
<br />
====[http://generalmap.gis.saccounty.net/JSViewer/county_portal.html Sacramento County]====<br />
[http://assessorparcelviewer.saccounty.net/GISViewer/Default.aspx Assessor map] for addresses / House Numbers<br />
<br />
Citrus Heights<br />
[http://elkgrovemap.gis.saccounty.net/jsviewer/elkgrove.html Elk Grove]<br />
Folsom<br />
Galt<br />
Isleton<br />
Rancho Cordova<br />
Sacramento<br />
<br />
====[https://cosb.maps.arcgis.com/home/webmap/viewer.html?webmap=4071773f6b004aaf8ee8d275b6b400b2 San Benito County]====<br />
Problem: http://www.lynxgis.com/sanbenitoco/index2.cfm<br />
Hollister<br />
San Juan Bautista<br />
<br />
====[https://www.arcgis.com/apps/webappviewer/index.html?id=87e70bb9b6994559ba7512792588d57a San Bernardino County]====<br />
<br />
Adelanto<br />
Apple Valley<br />
Barstow<br />
Big Bear Lake<br />
[http://www.cityofchino.org/home/showdocument?id=409 ''Chino'']<br />
Chino Hills<br />
Colton<br />
Fontana<br />
Grand Terrace<br />
Hesperia<br />
Highland<br />
Loma Linda<br />
Montclair<br />
Needles<br />
Ontario<br />
Rancho Cucamonga<br />
Redlands<br />
Rialto<br />
San Bernardino<br />
Twentynine Palms<br />
Upland<br />
Victorville<br />
Yucaipa<br />
Yucca Valley<br />
<br />
====[http://www.sangis.org/ San Diego County]====<br />
<br />
Carlsbad<br />
Chula Vista<br />
Coronado<br />
[http://delmar.geoviewer.io/ Del Mar]<br />
El Cajon<br />
Encinitas<br />
Escondido<br />
Imperial Beach<br />
La Mesa<br />
Lemon Grove<br />
National City<br />
[http://oceansidefiles.com/uploads/Water/PlanningViewer/index.html Oceanside]<br />
Poway<br />
San Diego<br />
San Marcos<br />
Santee<br />
Solana Beach<br />
[https://gis.cityofvista.com/VistaGIS/ Vista]<br />
<br />
====[http://sfgov.maps.arcgis.com/home/webmap/viewer.html?useExisting=1 San Francisco County]====<br />
<br />
San Francisco City and County are one and the same<br />
<br />
====[http://www.sjmap.org/DistrictViewer/Disclaimer.htm San Joaquin County]====<br />
<br />
Escalon<br />
Lathrop<br />
Lodi<br />
Manteca<br />
Ripon<br />
[http://www.stocktongov.com/government/departments/communityDevelop/genPlanMap.html Stockton]<br />
Tracy<br />
<br />
====[http://www.sloplanning.org/PermitView/MapSearch San Luis Obispo County]====<br />
<br />
Arroyo Grande<br />
Atascadero<br />
El Paso De Robles<br />
Grover Beach<br />
Morro Bay<br />
Pismo Beach<br />
San Luis Obispo<br />
<br />
====[http://maps.smcgov.org/planning/ San Mateo County]====<br />
<br />
Atherton<br />
Belmont<br />
Brisbane<br />
Burlingame<br />
Colma<br />
Daly City<br />
East Palo Alto<br />
Foster City<br />
Half Moon Bay<br />
Hillsborough<br />
Menlo Park<br />
Millbrae<br />
Pacifica<br />
Portola Valley<br />
Redwood City<br />
San Bruno<br />
San Carlos<br />
San Mateo<br />
South San Francisco<br />
Woodside<br />
<br />
====[https://secure.simplelayers.com/?do=start&project=939&application=CG3Viewer&embedded=1&query_url=0&context=2 Santa Barbara County]====<br />
<br />
Buellton<br />
Carpinteria<br />
Goleta<br />
Guadalupe<br />
Lompoc<br />
Santa Barbara<br />
Santa Maria<br />
Solvang<br />
<br />
====[http://www.sccgov.org/gis/SCCPubInteractiveMap/# Santa Clara County]====<br />
<br />
Campbell<br />
Cupertino<br />
Gilroy<br />
Los Altos<br />
Los Altos Hills<br />
Los Gatos<br />
Milpitas<br />
Monte Sereno<br />
Morgan Hill<br />
Mountain View<br />
Palo Alto<br />
San Jose<br />
Santa Clara<br />
Saratoga<br />
Sunnyvale<br />
<br />
====[http://gis.co.santa-cruz.ca.us/PublicGISWeb/ Santa Cruz County]====<br />
<small>Recommend setting Base Map to None for above</small><br />
<br />
Capitola<br />
Santa Cruz<br />
Scotts Valley<br />
Watsonville<br />
<br />
====[http://gis.co.shasta.ca.us/Parcels/ Shasta County]====<br />
<br />
Anderson<br />
[http://maps.ci.redding.ca.us/redding_pub/home/index.aspx Redding]<br />
Shasta Lake<br />
<br />
====[http://demos2.calcad.com:8080/SierraCountyPublic/fusion.php Sierra County]====<br />
<br />
Loyalton<br />
<br />
====Siskiyou County====<br />
<br />
Dorris<br />
Dunsmuir<br />
Etna<br />
Fort Jone<br />
Montague<br />
Mount Shasta<br />
Tulelake<br />
Weed<br />
Yreka<br />
<br />
====[http://regis.solanocounty.com/Html5Viewer/Index.html?configBase=http://regis.solanocounty.com/Geocortex/Essentials/REST/sites/TaxParcelViewerNO/viewers/TaxParcelViewer-Solano_GIS_Viewer/virtualdirectory/Resources/Config/Default Solano County]====<br />
<br />
Benicia<br />
Dixon<br />
Fairfield<br />
Rio Vista<br />
Suisun City<br />
Vacaville<br />
[http://gis.zoomprospector.com/client/Vallejo/ Vallejo]<br />
<br />
====[https://sonomamap.maps.arcgis.com/apps/webappviewer/index.html?id=06ac7fe1b8554171b4682dc141293962 Sonoma County]====<br />
<br />
Cloverdale<br />
Cotati<br />
Healdsburg<br />
Petaluma<br />
Rohnert Park<br />
Santa Rosa<br />
Sebastopol<br />
Sonoma Windsor<br />
<br />
====[http://gis.stancounty.com/giscentral/public/map/esri/flex/parcelfinder/index.jsp# Stanislaus County]====<br />
<br />
Ceres<br />
Hughson<br />
[http://gis.modestogov.com/ Modesto*]<br />
Newman<br />
Oakdale<br />
Patterson<br />
Riverbank<br />
Turlock<br />
Waterford<br />
<br />
====Sutter County====<br />
[http://www.co.sutter.ca.us/doc/apps/road_closures Construction and Road Closures]<br />
<br />
Live Oak<br />
Yuba City<br />
<br />
====[http://www.arcgis.tehamacountypublicworks.ca.gov/ Tehama County]====<br />
<br />
Corning<br />
[http://planningsites.org/RedBluffPlanning/ Red Bluff]<br />
Tehama<br />
<br />
====[http://trinitycounty.maps.arcgis.com/apps/Viewer/index.html?appid=320cf1c1558c43c8b1f2f70c23d35026 Trinity County]====<br />
<br />
No Cities<br />
<br />
====Tulare County====<br />
<br />
:[http://tularecounty.ca.gov/tcict/index.cfm/geographic-information-system-gis/gis-maps/dinuba-city-map-jan-2008/ Dinuba] 2008 static map<br />
<br />
:[http://tularecounty.ca.gov/tcict/index.cfm/geographic-information-system-gis/gis-maps/exeter-city-map-jan-2008/ Exeter] 2008 Static map<br />
<br />
:[http://tularecounty.ca.gov/tcict/index.cfm/geographic-information-system-gis/gis-maps/farmersville-city-map-jan-2008/ Farmersville] 2008 Static map<br />
<br />
Lindsay<br />
[http://www.ci.porterville.ca.us/depts/CommunityDevelopment/webmaps/PublicWebmapPortal/webmap.html Porterville]<br />
[http://www.tulare.ca.gov/departments/community-development/development-services/planning/zoning-map Tulare] <br />
[http://visalia.maps.arcgis.com/apps/webappviewer/index.html?id=e78dfbb593044bf6bc1cf4f0d63c9160 Visalia]<br />
Woodlake<br />
<br />
====[http://gis.co.tuolumne.ca.us:8093/flexviewers/General%20Plan%20And%20Zoning/ Tuolumne County]====<br />
<br />
Sonora<br />
<br />
====[http://gis.ventura.org/Html5Viewer/index.html?viewer=CountyView.CountyView_gvh Ventura County]====<br />
<br />
Camarillo<br />
Fillmore<br />
Moorpark<br />
Ojai<br />
Oxnard<br />
Port Hueneme<br />
San Buenaventura<br />
Santa Paula<br />
Simi Valley<br />
Thousand Oaks<br />
Ventura<br />
<br />
====[http://yolo-gis-prod.yolocounty.org/SilverlightViewer_2_1/Viewer.html?ViewerConfig=http://yolo-gis-prod.yolocounty.org/Geocortex/Essentials/INTERNETPUBLIC/REST/sites/GIS_Public_Viewer/viewers/GIS_Public_Viewer/virtualdirectory/Config/Viewer.xml Yolo County]====<br />
<br />
Davis<br />
West Sacramento<br />
Winters<br />
Woodland<br />
<br />
====[http://gis.co.yuba.ca.us/portal_apps/parcelapp.html Yuba County]====<br />
<br />
Marysville<br />
Wheatland</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=Utah/Major_roads/Main&diff=174163Utah/Major roads/Main2021-05-22T23:28:34Z<p>Tonestertm: /*Major_roads/Main*/Correcting usage of "split"</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
<br />
=== State Highway Naming ===<br />
<br />
The approved format for State Highway naming in {{RootPage2}} is: '''SR-##'''<br />
<br />
=== Locking Standard ===<br />
{{Lock Standard State|UT}}<br />
<br />
=== Functional Classification ===<br />
<br />
Please refer to this forum topic for more information on FC - [http://www.waze.com/forum/viewtopic.php?f=276&t=85397 Road Types (USA) – comprehensive overhaul of drivable roads]<br />
<br />
The Utah Functional Classification system is on par with the Nationwide standard, and consists of 7 Road Types.<br />
<br />
==== UT to Waze FC conversion ====<br />
<br />
Utah's Dept of Transportation has made Functional Classification maps available online, in PDF format, for each county. They also provide an interactive statewide map.<br />
<br />
===== Resource Links =====<br />
<br />
* UDOT [http://www.arcgis.com/home/webmap/viewer.html?webmap=494d57208ea4464bb664ac2da38f9c91 Interactive Functional Classification Map] - ArcGIS<br />
* UDOT [http://www.udot.utah.gov/main/f?p=100:pg:0::::V,T:,1226 Functional Classification Maps] by County (PDF Format) (May be out of Date)<br />
<br />
===== UDOT GIS class and color description =====<br />
[[File:UTFC.png|left|GIS Legend]]<br />
The Utah Classification and Color scheme come from the official Utah D.O.T (UDOT) Functional Classification (FC) map that is published by UDOT. The legend shows what classifications UDOT uses and what color is assigned to each class.<br />
{{clear}}<br />
<br />
==== UDOT to Waze conversion table ====<br />
<br />
<br />
<div style="font-size:smaller"><br />
{| border="1" style="border-collapse:collapse; text-align:center"<br />
! scope="row" rowspan="2" colspan="2"| <br />
! colspan="7"| <big>Highway Systems</big><br />
|-<br />
! Interstate<br />
! Interstate Business Loop/Spur<br />
! US Hwy (incl. some [[wikipedia:special routes|special routes]])<br />
! State Hwy (incl. some special routes)<br />
! State Hwy BUS, SPUR, LOOP<ref>When a state highway "SPUR" route is used to connect a state highway with another state highway, a US highway, or an Interstate (i.e., when it is used as a connector/CONN route), use the first state highway column.</ref><br />
! Locally-maintained<br />
|-<br />
|<br />
| ''example>>>>>''<br />
| I-15 N<br />
| I-15 BUS<br />
| US-89<br />
| SR-28<br />
| SR-24 Spur<br />
| Fremont St<br />
|- <br />
! scope="row" rowspan="7" style="width:28px"| <big>F<br>u<br>n<br>c<br>t<br>i<br>o<br>n<br>a<br>l<br> <br>C<br>l<br>a<br>s<br>s</big><!-- Temp placeholder --><br />
| {{Road | style = color: black; background-color: #ffffff; border-color: #5ed6ff | Interstate (1) }}||{{Freeway|Fw}}||n/a||n/a||n/a||n/a||n/a<br />
|- <br />
| {{Road | style = color: black; background-color: #e2c54c; | Other Freeway/Expy (2)}}||n/a||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}<br />
|- <br />
| {{Road | style = color: white; background-color: #ff0000; | Other Principal Arterial (3)}}||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}<br />
|- <br />
| {{Road | style = color: black; background-color: #7cd0b2; | Minor Arterial (4)}}||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}<br />
|- <br />
| {{Road | style = color: white; background-color: #d14cff; | Major Collector (5)}}||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}||{{Primary Street|PS}}<br />
|- <br />
| {{Road | style = color: black; background-color: #ffff00; | Minor Collector (6)}}||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}||{{Primary Street|PS}}<br />
|- <br />
| {{Street|Local (7)}}||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}<ref>All FC "Local" roads with a State Route designation (SR-XXX) discovered ''so far'' have been local roads serving a state facility campus, and are more appropriately typed as Primary Street, Street, or even Parking Lot Road. Check with a state manager for any of these.</ref>||{{Primary Street|PS}}||{{Street|Street}}<br />
|}<br />
<br />
<br />
References: {{reflist}}<br />
</div><br />
<br />
If you encounter a specific type of road (Interstate/US Hwy Business route, etc) that is not shown, reference the main [[Road types#Quick_reference_chart | FC Quick Reference chart]]<br />
<br />
==== Functional Classification Exceptions ====<br />
<br />
These roads have changed from the recommended Functional Classification for the reason noted.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Road Name !! New Type !! Area !! Link !! Reason !! Approved<br />
|-<br />
| SR-59 || Major Highway || Washington|| [https://www.waze.com/editor/?env=usa&lon=-113.05354&lat=37.08720&zoom=0 Link] || Corrects routing from US-89 to I-15 || [[User:Jemay|RC]]<br />
|- <br />
| SR-291 || Parking Lot Road || Ogden || [https://www.waze.com/editor/?env=usa&lon=-111.94511&lat=41.25086&zoom=6&mode=0 Link] || State facility parking lot roads || [[User:herrchin|SM]]<br />
|- <br />
| SR-296 || Street || American Fork || [https://www.waze.com/editor/?env=usa&lon=-111.77559&lat=40.39731&zoom=5&mode=0 Link] || State facility campus roads || [[User:herrchin|SM]]<br />
|- <br />
| SR-298 || Parking Lot Road || South Ogden || [https://www.waze.com/editor/?env=usa&lon=-111.96534&lat=41.16787&zoom=7&mode=0 Link] || State facility parking lot roads || [[User:herrchin|SM]]<br />
|}<br />
<br />
=== U-turns ===<br />
<br />
U-turns are permitted in Utah where they are safe {{ref label|1|1}}, except where prohibited by signage or restricted by local municipal law. Legal U-turns includes those made from a two-way (i.e. shared) turn lane. {{ref label|2|2}}<br />
<br />
U-turns on Primary Street through Major Highway type roads may be enabled in either of the following two circumstances (Do not enable U-turns on Street type roads):<br />
<br />
#) The U-turn is ''explicitly'' allowed by signage; or<br />
#) The U-turn is otherwise legal and safe, and there is ''at least'' 10.1 m (33 feet) from the left edge of the departure lane to the "destination" curb. This can include any median that may exist to the left of the departure lane. (The measurement is intended to accommodate the turning radius of most passenger vehicles.)<br />
<br />
Do ''not'' make a point of enabling all U-turns valid under this guidance, only as you encounter them and they are necessary. For Waze routing, U-turns should only be enabled where they provide for improved routing, which includes recovering from missed turns. A common example is a median-divided primary street that has homes/businesses with their driveways/entrances directly on it, where reaching them would otherwise require lengthy, multi-turn deviations through side roads in order to end up on the correct side of the median.<br />
<br />
Note that when editing, a functional U-turn can arise from more than just the u-turn flag on a road segment, such as with these common scenarios:<br />
<br />
# Divided roads with box and partial-box intersections where the median segment is 15 m (49 feet) or longer.<br />
# Divided roads with explicitly-mapped inside turn lanes unless the turn arrow in the u-turn direction is disabled.<br />
<br />
{{note|1|1}} [http://le.utah.gov/xcode/Title41/Chapter6a/41-6a-S802.html | Utah Code 41-6a-802 (2)]<br />
<br />
{{note|2|2}} [http://le.utah.gov/xcode/Title41/Chapter6a/41-6a-S801.html | Utah Code 41-6a-801 (3)(b)]<br />
<br />
=== Speed Limits ===<br />
<br />
Utah follows the Waze [[speed limits]] guidance. Please read that page carefully before editing any Speed Limits (SLs).<br />
<br />
Utah does not alter speed limits for temporary reductions such as school zones or work zones, unless the work zone duration will exceed 3 months and the signs present are fixed-speed and on permanent style mountings (no digital variable speed limit signs, no portable signs).<br />
<br />
==== Speed Limit standards ====<br />
The following are the [https://le.utah.gov/xcode/Title41/Chapter6A/41-6a-S601.html speed limits laws of Utah], except where posted signs indicate differently (higher or lower speed limits).<br />
<br />
* Urban district: '''25''' mph.<br />
* All other locations: '''55''' mph. <br />
<br />
==== Speed Limit Resources ====<br />
* [http://utahvalley360.com/wp-content/uploads/2013/09/80-mph-Speed-Limit-Map1.jpg Year 2013 Fwy 80mph changes]<br />
* [http://img.deseretnews.com/images/article/graphic/1440798/1440798.jpg Late 2014 Fwy speed changes]. [http://www.deseretnews.com/article/865615529/Wasatch-Front-freeway-speed-to-be-70-mph-but-UHP-not-in-favor.html?pg=all An article]. [http://www.sltrib.com/news/1821647-155/speed-limit-mph-udot-davis-increase Another article].<br />
<br />
==== Useful Scripts For Editing Speed Limits ====<br />
* [https://www.waze.com/forum/viewtopic.php?f=819&t=167387 WME Color Speeds]<br />
* [https://www.waze.com/forum/viewtopic.php?f=819&t=178371 WME Context Menu]<br />
* [https://www.waze.com/forum/viewtopic.php?f=819&t=166746 WME Speedhelper]<br />
* [https://www.waze.com/forum/viewtopic.php?f=819&t=166497 WME Speeds]<br />
<br />
=== Road Elevations ===<br />
Utah practices "True Elevation" where almost all segments are set with elevation ''Ground'' unless they are passing over/beneath another segment, major waterway, or natural feature.<br />
* Drivable and non-drivable (Railroad, etc.) segments are handled by the same rules.<br />
* Only segments that "cannot see the sky" should have negative elevation (e.g. tunnels, underground parking garages)<br />
* Only set elevation as high as necessary, with the relative elevations representing the true physical relationships. Example: Nothing should be +2 unless it is crossing over a +1 segment, which is crossing over a Ground level segment.<br />
* If you use the Bridge tool to join segments, be aware that it raises the elevation of the newly-joined segment. Lower the joined segment as appropriate.<br />
* Only elevate/lower the actual bridge/tunnel section of the road.<br />
* Bridges should be cut with a junction node at the start/end of the bridge where the land falls away. You can typically see guardrail at the start/end of the bridge section, an expansion gap in the pavement where the bridge starts/ends, and/or a pavement change (asphalt to concrete, for example).<br />
* Don't create elevated bridges for water unless the waterway is of significance (i.e. don't bridge every 5 foot rural box culvert).<br />
* Tunnels should be cut with a junction node at least 15m / 50ft before and after the tunnel, to allow time for the GPS to regain signal. Set the "Tunnel" checkbox as well.<br />
* Do not cut segments for elevation purposes if the bridge/tunnel starts/stops within 60m/200ft of an existing junction. Re-use that junction that is "close enough." Also be aware of cutting segments "too close" (which is always relative) to an intersection.<br />
* '''The use of common sense is paramount in using True Elevation.'''<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Major_roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Major roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=Audible_instructions&diff=173947Audible instructions2021-03-26T22:54:17Z<p>Tonestertm: /* TTS */ Update to mention newer US-English TTS voices</p>
<hr />
<div>When navigating in Waze with all sound turned on (rather than alerts only), Waze will issue various audible instructions at various times in order to prepare and inform the user to make a certain movement.<br />
[[File:Voicelist.png|thumb]]<br />
The occurrence, timing and format of these instructions do not depend upon the language of the voice, but they do depend upon whether the voice chosen to speak the instructions ''includes street names''. Voices that include street names are speech synthesizers, which convert text to speech (TTS). Voices that do not include street names are simple collections of recorded phrases. We'll call these two categories of voices "TTS" and "non-TTS" respectively.<br />
<br />
== TTS ==<br />
TTS voices are sophisticated speech engines, which say not only street names, but also place names and more detailed information in general regarding navigation and alerts. These include Jane, Sarah, and Ben, which speak US English; Kate and Thomas, which speak UK English; and Ariane, Marusya and many others in various non-English languages. All examples in this section were documented using Jane, which, at the time of testing, was the only TTS voice in Waze that spoke US English and was the only TTS voice maintained by the US Waze community. In the examples which follow, any time "Jane" is used, "Ben" and "Sarah" are equivalent.<br />
<br />
From a TTS voice there are four possible audible instructions before a movement. Depending upon speed, distance, and timing, anywhere from one to four of these instructions may be heard. We'll call them the '''initial''', '''attention''', '''approach''' and '''final''' instructions. For simplicity we'll also assign them the letters '''A''' through '''D'''.<br />
<br />
=== Initial instruction (A) ===<br />
Instruction A is given a few seconds after the previous movement (or, if the previous movement is onto a ramp, a few seconds after exiting the ramp(s) onto which the previous instruction brought you), unless you are so close to the next movement that there is not enough time to give both instruction A and D (in which case only instruction D is given).<br />
<br />
Format depends on distance to next movement.<br />
* If distance to next movement > 4.35 mi (7.0 km), "Continue straight for (x hours and) y minutes to [street name]"<br />
* If distance to next movement < 4.35 mi (7.0 km), "In [distance], [instruction] [on/to] [street name]"<br />
<br />
{| class="wikitable" style="text-align: left;"<br />
|-<br />
! Distance to next movement<br />
! Example<br />
|-<br />
| rowspan="2" style="border-bottom: 1px solid #93c4d3;" | > 4.35 mi (7.0 km)<br />
| Continue straight for 15 minutes to Rue Royale<br />
|-<br />
| style="border-bottom: 1px solid #93c4d3;" | Continue straight for 2 hours and 15 minutes to Exit 123: I-45 N / Bakerstown<br />
|-<br />
| rowspan="2" | < 4.35 mi (7.0 km)<br />
| In 700 feet, turn left on Brightview Blvd<br />
|-<br />
| In 2.1 miles, exit to Exit 98: SR-76 / Chilltown<br />
|-<br />
|}<br />
<br />
=== Attention instruction (B) ===<br />
Instruction B is intended to bring the driver's attention back to navigation after a long period of stasis. It is given at the point where the movement is expected to be 5 minutes away, but only if it's been at least 15-20 minutes since instruction A. While the timing of the instruction is time-based, the instruction is given in distance.<br />
<br />
Format: "In [x] miles, [instruction] [on/to] [street name]"<br />
{| class="wikitable" style="text-align: left;"<br />
|-<br />
! examples<br />
|-<br />
| In 3.4 miles, turn left on Brightview Blvd<br />
|-<br />
| In 6 miles, exit right to Exit 98: SR-76 / Chilltown<br />
|-<br />
|}<br />
<br />
=== Approach instruction (C) ===<br />
Instruction C is given at a certain distance from the movement depending on your speed as detected at that point, unless the prior instruction was given too close to the timing of instruction C. The street name may or may not be included, depending on how long it has been since Instruction A (a couple minutes).<br />
<br />
Format: "In [distance], [instruction] ([on/to] [street name]"<br />
<br />
{| class="wikitable" style="text-align: left;"<br />
|-<br />
! speed range<br />
! distance <br />
! example<br />
|-<br />
| 0 – 43.5 mph (0 – 70 km/h)<br />
|1000 ft<br />
| In one thousand feet, turn right<br />
|-<br />
|43.5 – 55.9 mph (70 – 90 km/h)<br />
| 0.5 mi<br />
| In half a mile, exit left<br />
|-<br />
| 55.9 – 93.2 mph (90 – 150 km/h)<br />
| 1 mi<br />
| In one mile, stay to the right to I-75 N<br />
|-<br />
| 93.2+ mph (150+ km/h)<br />
| 2 mi<br />
| In two miles, exit right<br />
|-<br />
|}<br />
<br />
=== Final instruction (D) ===<br />
Instruction D is given every time, just before the movement (unless you make the turn before Waze has a chance to call it out).<br />
<br />
Format: "[instruction] [on/to] [street name]"<br />
{| class="wikitable" style="text-align: left;"<br />
|-<br />
! examples<br />
|-<br />
| Turn right on Main St<br />
|-<br />
| Exit left to Exit 234B: Poydras St / Superdome<br />
|-<br />
|}<br />
<br />
=== Combined instructions ===<br />
If, based on collected speed data for the time of day and day of the week, Waze expects the following movement to occur within about 30 seconds after the upcoming movement, it will add an instruction after instructions C and D, beginning with "then".<br />
* Format after C: "In [distance], [instruction] ([on/to] [street name])*, then [instruction]"<br />
** *street name only said if street names following both instructions are identical or [[Navigation instructions for unnamed segments|inherited]]<br />
* Format after D: "[instruction] ([on/to] [street name])**, then [instruction] [on/to] [street name]"<br />
** **first street name only said if street names following each instruction are different<br />
{| class="wikitable" style="text-align: left;"<br />
|-<br />
! examples<br />
|-<br />
| In two miles, exit right to Exit 5A: I-71 S / Cincinnati, then stay to the left<br />
|-<br />
| Turn left on N High St, then turn right on Arcadia Ave<br />
|}<br />
<br />
=== Preposition choice ===<br />
When Jane says street names, those names are preceded by "on" or "to" according to a couple factors:<br />
* Following an instruction to exit or stay to the left or right, Waze always says "to" and the street name.<br />
* Following an instruction to turn left or right, continue straight, make a U-turn or do anything at a roundabout, Waze says either "to" or "on" depending on the road type of the next segment past the instruction.<br />
** If the next segment is a {{Ramp}}, Waze says "to" and the street name.<br />
** If the next segment is any other road type, Waze says "on" and the street name.<br />
The word "to" at the beginning of any street name, which is [[Road names#Exit ramps and entrance ramps .28on-ramps.29|common on ramp names in the USA]], is never a factor in whether Waze says "to" or "on" and is actually ignored in audible instructions. This means that if the name of a ramp is [[Navigation instructions for unnamed segments|inherited]] through an unnamed non-ramp segment, Waze will say "on" and will omit the "to" completely. For example, turning left through a roundabout made of non-ramp segments and onto a ramp with the name "to US-33 W / Lancaster" will produce the audible instruction "at the roundabout, turn left on US-33 W / Lancaster."<br />
<br />
=== Occurrence === <br />
The following is the order of the most common occurrence:<br />
* D<br />
* A, D<br />
* A, C, D<br />
* A, B, C, D<br />
This is another way of saying:<br />
* Instruction D is (virtually) always given. <br />
* Instruction A is given only if there will be instruction D and there is enough time for both. <br />
* Instruction C is given only if there was instruction A and there has been enough time since instruction A. <br />
* Instruction B is given only if there will be instruction C (and therefore there was instruction A) and there has been enough time since instruction A.<br />
<br />
=== Notes ===<br />
* Any English-speaking TTS voice does not say the exit direction after instruction A. This can be confusing where a left exit follows shortly after another movement on a highway, since drivers may assume a right exit based.<br />
* Jane says "stay to the" rather than "keep" for keep left/right instructions.<br />
* Jane never says street names after "at the roundabout continue straight" or "at the roundabout make a U-turn" instructions unless they are combined with a different instruction.<br />
<br />
=== Flowchart ===<br />
[[File:TTS Flowchart.png]]<br />
<br />
== Non-TTS ==<br />
[[File:Voicerecorder.png|thumb]]<br />
Non-TTS voices are sets of recorded phrases. These include Amy and Nathan, any novelty voice like Boy Band, most other voices in other languages, and any user-recorded voices. The voice recorder contains the extent of what all non-TTS voices can say, and it is viewable in the app by tapping "record new voice" in the Waze voice menu.<br />
<br />
From a non-TTS voice there are three possible audible instructions before a movement. Depending upon speed, distances, and timing, anywhere from one to three of these instructions may be heard. We'll call them '''first approach''', '''second approach''', and '''final''' instructions. For simplicity, we'll also assign them numbers '''1''' through '''3'''.<br />
<br />
=== First approach instruction (1) ===<br />
The first approach instruction is given when enough time and advance distance is available for it. The actual distance from the previous movement to the next movement is rounded up to give the distance used in the instruction.<br />
<br />
Format: "In [distance], [instruction]"<br />
{| class="wikitable" style="text-align: left;"<br />
|-<br />
! speed and/or distance to next movement<br />
! example<br />
|-<br />
|style="border-bottom: 1px solid #93c4d3"|< 0.1 mi<br />
|style="border-bottom: 1px solid #93c4d3"|In 0.1 miles, continue straight<br />
|-<br />
|style="border-bottom: 1px solid #93c4d3"|0.1 mi - 0.25 mi<br />
|style="border-bottom: 1px solid #93c4d3"|In a quarter of a mile, turn right<br />
|-<br />
|style="border-bottom: 1px solid #93c4d3"|0.25 - 0.5 mi<br />
|rowspan="2" style="border-bottom: 1px solid #93c4d3"|In half a mile, at the roundabout turn left<br />
|-<br />
|style="white-space: nowrap; border-bottom: 1px solid #93c4d3"|0-43.5 mph (0-70 km/h) and > 0.25 mi<br />
|-<br />
|style="border-bottom: 1px solid #93c4d3"|43.5+ mph (70+ km/h) and > 0.5 mi<br />
|style="border-bottom: 1px solid #93c4d3"|In 1 mile, make a U-turn<br />
|}<br />
<br />
=== Second approach instruction (2) ===<br />
A second approach instruction is given at a certain distance from the movement depending on your speed, unless the first approach instruction was given too close to the timing of the second.<br />
<br />
Format: "In [distance], [instruction]"<br />
{| class="wikitable"<br />
!Speed<br />
!Example<br />
|-<br />
|0-43.5 mph (0-70 km/h)<br />
|In 0.1 miles, keep right<br />
|-<br />
|43.5+ mph (70+ km/h)<br />
|In a quarter of a mile, exit left<br />
|}<br />
<br />
=== Final instruction (3) ===<br />
The final instruction is given every time, just before the movement (unless you make the turn before Waze has a chance to call it out).<br />
<br />
Format: "[instruction]"<br />
{| class="wikitable"<br />
!Examples<br />
|-<br />
|Turn left<br />
|-<br />
|At the roundabout take the fifth exit<br />
|}<br />
<br />
=== Combined instructions ===<br />
If a second movement is planned less than around 500 feet from the first, Waze will tack a second instruction onto the end of any instruction less than a quarter of a mile away from the first movement, separated by "and then".<br />
<br />
Format: "(In [distance],) [instruction], and then [instruction]"<br />
{| class="wikitable"<br />
!Examples<br />
|-<br />
|In 0.1 miles, turn left, and then turn right<br />
|-<br />
|Exit right, and then keep left<br />
|}<br />
=== Occurrence === <br />
The following is the order of the most common occurrence:<br />
* 3<br />
* 1, 3<br />
* 1, 2, 3<br />
This is another way of saying:<br />
* Instruction 3 is (virtually) always given. <br />
* Instruction 1 is given only if there will be instruction 3 and there is enough time for both. <br />
* Instruction 2 is given only if there was instruction 1 and there has been enough time since instruction 1.</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=Audible_instructions&diff=173946Audible instructions2021-03-26T07:40:26Z<p>Tonestertm: /* Combined instructions */ wordsmith</p>
<hr />
<div>When navigating in Waze with all sound turned on (rather than alerts only), Waze will issue various audible instructions at various times in order to prepare and inform the user to make a certain movement.<br />
[[File:Voicelist.png|thumb]]<br />
The occurrence, timing and format of these instructions do not depend upon the language of the voice, but they do depend upon whether the voice chosen to speak the instructions ''includes street names''. Voices that include street names are speech synthesizers, which convert text to speech (TTS). Voices that do not include street names are simple collections of recorded phrases. We'll call these two categories of voices "TTS" and "non-TTS" respectively.<br />
<br />
== TTS ==<br />
TTS voices are sophisticated speech engines, which say not only street names, but also place names and more detailed information in general regarding navigation and alerts. These include Jane, which speaks US English; Kate and Thomas, which speak UK English; and also Ariane, Marusya and dozens of others in various languages. All examples in this section were documented using Jane, as this is the only TTS voice in Waze that speaks US English and the only TTS voice maintained by the US Waze community.<br />
<br />
From a TTS voice there are four possible audible instructions before a movement. Depending upon speed, distances, and timing, anywhere from one to four of these instructions may be heard. We'll call them the '''initial''', '''attention''', '''approach''' and '''final''' instructions. For simplicity we'll also assign them the letters '''A''' through '''D'''.<br />
<br />
=== Initial instruction (A) ===<br />
Instruction A is given a few seconds after the previous movement (or, if the previous movement is onto a ramp, a few seconds after exiting the ramp(s) onto which the previous instruction brought you), unless you are so close to the next movement that there is not enough time to give both instruction A and D (in which case only instruction D is given).<br />
<br />
Format depends on distance to next movement.<br />
* If distance to next movement > 4.35 mi (7.0 km), "Continue straight for (x hours and) y minutes to [street name]"<br />
* If distance to next movement < 4.35 mi (7.0 km), "In [distance], [instruction] [on/to] [street name]"<br />
<br />
{| class="wikitable" style="text-align: left;"<br />
|-<br />
! Distance to next movement<br />
! Example<br />
|-<br />
| rowspan="2" style="border-bottom: 1px solid #93c4d3;" | > 4.35 mi (7.0 km)<br />
| Continue straight for 15 minutes to Rue Royale<br />
|-<br />
| style="border-bottom: 1px solid #93c4d3;" | Continue straight for 2 hours and 15 minutes to Exit 123: I-45 N / Bakerstown<br />
|-<br />
| rowspan="2" | < 4.35 mi (7.0 km)<br />
| In 700 feet, turn left on Brightview Blvd<br />
|-<br />
| In 2.1 miles, exit to Exit 98: SR-76 / Chilltown<br />
|-<br />
|}<br />
<br />
=== Attention instruction (B) ===<br />
Instruction B is intended to bring the driver's attention back to navigation after a long period of stasis. It is given at the point where the movement is expected to be 5 minutes away, but only if it's been at least 15-20 minutes since instruction A. While the timing of the instruction is time-based, the instruction is given in distance.<br />
<br />
Format: "In [x] miles, [instruction] [on/to] [street name]"<br />
{| class="wikitable" style="text-align: left;"<br />
|-<br />
! examples<br />
|-<br />
| In 3.4 miles, turn left on Brightview Blvd<br />
|-<br />
| In 6 miles, exit right to Exit 98: SR-76 / Chilltown<br />
|-<br />
|}<br />
<br />
=== Approach instruction (C) ===<br />
Instruction C is given at a certain distance from the movement depending on your speed as detected at that point, unless the prior instruction was given too close to the timing of instruction C. The street name may or may not be included, depending on how long it has been since Instruction A (a couple minutes).<br />
<br />
Format: "In [distance], [instruction] ([on/to] [street name]"<br />
<br />
{| class="wikitable" style="text-align: left;"<br />
|-<br />
! speed range<br />
! distance <br />
! example<br />
|-<br />
| 0 – 43.5 mph (0 – 70 km/h)<br />
|1000 ft<br />
| In one thousand feet, turn right<br />
|-<br />
|43.5 – 55.9 mph (70 – 90 km/h)<br />
| 0.5 mi<br />
| In half a mile, exit left<br />
|-<br />
| 55.9 – 93.2 mph (90 – 150 km/h)<br />
| 1 mi<br />
| In one mile, stay to the right to I-75 N<br />
|-<br />
| 93.2+ mph (150+ km/h)<br />
| 2 mi<br />
| In two miles, exit right<br />
|-<br />
|}<br />
<br />
=== Final instruction (D) ===<br />
Instruction D is given every time, just before the movement (unless you make the turn before Waze has a chance to call it out).<br />
<br />
Format: "[instruction] [on/to] [street name]"<br />
{| class="wikitable" style="text-align: left;"<br />
|-<br />
! examples<br />
|-<br />
| Turn right on Main St<br />
|-<br />
| Exit left to Exit 234B: Poydras St / Superdome<br />
|-<br />
|}<br />
<br />
=== Combined instructions ===<br />
If, based on collected speed data for the time of day and day of the week, Waze expects the following movement to occur within about 30 seconds after the upcoming movement, it will add an instruction after instructions C and D, beginning with "then".<br />
* Format after C: "In [distance], [instruction] ([on/to] [street name])*, then [instruction]"<br />
** *street name only said if street names following both instructions are identical or [[Navigation instructions for unnamed segments|inherited]]<br />
* Format after D: "[instruction] ([on/to] [street name])**, then [instruction] [on/to] [street name]"<br />
** **first street name only said if street names following each instruction are different<br />
{| class="wikitable" style="text-align: left;"<br />
|-<br />
! examples<br />
|-<br />
| In two miles, exit right to Exit 5A: I-71 S / Cincinnati, then stay to the left<br />
|-<br />
| Turn left on N High St, then turn right on Arcadia Ave<br />
|}<br />
<br />
=== Preposition choice ===<br />
When Jane says street names, those names are preceded by "on" or "to" according to a couple factors:<br />
* Following an instruction to exit or stay to the left or right, Waze always says "to" and the street name.<br />
* Following an instruction to turn left or right, continue straight, make a U-turn or do anything at a roundabout, Waze says either "to" or "on" depending on the road type of the next segment past the instruction.<br />
** If the next segment is a {{Ramp}}, Waze says "to" and the street name.<br />
** If the next segment is any other road type, Waze says "on" and the street name.<br />
The word "to" at the beginning of any street name, which is [[Road names#Exit ramps and entrance ramps .28on-ramps.29|common on ramp names in the USA]], is never a factor in whether Waze says "to" or "on" and is actually ignored in audible instructions. This means that if the name of a ramp is [[Navigation instructions for unnamed segments|inherited]] through an unnamed non-ramp segment, Waze will say "on" and will omit the "to" completely. For example, turning left through a roundabout made of non-ramp segments and onto a ramp with the name "to US-33 W / Lancaster" will produce the audible instruction "at the roundabout, turn left on US-33 W / Lancaster."<br />
<br />
=== Occurrence === <br />
The following is the order of the most common occurrence:<br />
* D<br />
* A, D<br />
* A, C, D<br />
* A, B, C, D<br />
This is another way of saying:<br />
* Instruction D is (virtually) always given. <br />
* Instruction A is given only if there will be instruction D and there is enough time for both. <br />
* Instruction C is given only if there was instruction A and there has been enough time since instruction A. <br />
* Instruction B is given only if there will be instruction C (and therefore there was instruction A) and there has been enough time since instruction A.<br />
<br />
=== Notes ===<br />
* Any English-speaking TTS voice does not say the exit direction after instruction A. This can be confusing where a left exit follows shortly after another movement on a highway, since drivers may assume a right exit based.<br />
* Jane says "stay to the" rather than "keep" for keep left/right instructions.<br />
* Jane never says street names after "at the roundabout continue straight" or "at the roundabout make a U-turn" instructions unless they are combined with a different instruction.<br />
<br />
=== Flowchart ===<br />
[[File:TTS Flowchart.png]]<br />
<br />
== Non-TTS ==<br />
[[File:Voicerecorder.png|thumb]]<br />
Non-TTS voices are sets of recorded phrases. These include Amy and Nathan, any novelty voice like Boy Band, most other voices in other languages, and any user-recorded voices. The voice recorder contains the extent of what all non-TTS voices can say, and it is viewable in the app by tapping "record new voice" in the Waze voice menu.<br />
<br />
From a non-TTS voice there are three possible audible instructions before a movement. Depending upon speed, distances, and timing, anywhere from one to three of these instructions may be heard. We'll call them '''first approach''', '''second approach''', and '''final''' instructions. For simplicity, we'll also assign them numbers '''1''' through '''3'''.<br />
<br />
=== First approach instruction (1) ===<br />
The first approach instruction is given when enough time and advance distance is available for it. The actual distance from the previous movement to the next movement is rounded up to give the distance used in the instruction.<br />
<br />
Format: "In [distance], [instruction]"<br />
{| class="wikitable" style="text-align: left;"<br />
|-<br />
! speed and/or distance to next movement<br />
! example<br />
|-<br />
|style="border-bottom: 1px solid #93c4d3"|< 0.1 mi<br />
|style="border-bottom: 1px solid #93c4d3"|In 0.1 miles, continue straight<br />
|-<br />
|style="border-bottom: 1px solid #93c4d3"|0.1 mi - 0.25 mi<br />
|style="border-bottom: 1px solid #93c4d3"|In a quarter of a mile, turn right<br />
|-<br />
|style="border-bottom: 1px solid #93c4d3"|0.25 - 0.5 mi<br />
|rowspan="2" style="border-bottom: 1px solid #93c4d3"|In half a mile, at the roundabout turn left<br />
|-<br />
|style="white-space: nowrap; border-bottom: 1px solid #93c4d3"|0-43.5 mph (0-70 km/h) and > 0.25 mi<br />
|-<br />
|style="border-bottom: 1px solid #93c4d3"|43.5+ mph (70+ km/h) and > 0.5 mi<br />
|style="border-bottom: 1px solid #93c4d3"|In 1 mile, make a U-turn<br />
|}<br />
<br />
=== Second approach instruction (2) ===<br />
A second approach instruction is given at a certain distance from the movement depending on your speed, unless the first approach instruction was given too close to the timing of the second.<br />
<br />
Format: "In [distance], [instruction]"<br />
{| class="wikitable"<br />
!Speed<br />
!Example<br />
|-<br />
|0-43.5 mph (0-70 km/h)<br />
|In 0.1 miles, keep right<br />
|-<br />
|43.5+ mph (70+ km/h)<br />
|In a quarter of a mile, exit left<br />
|}<br />
<br />
=== Final instruction (3) ===<br />
The final instruction is given every time, just before the movement (unless you make the turn before Waze has a chance to call it out).<br />
<br />
Format: "[instruction]"<br />
{| class="wikitable"<br />
!Examples<br />
|-<br />
|Turn left<br />
|-<br />
|At the roundabout take the fifth exit<br />
|}<br />
<br />
=== Combined instructions ===<br />
If a second movement is planned less than around 500 feet from the first, Waze will tack a second instruction onto the end of any instruction less than a quarter of a mile away from the first movement, separated by "and then".<br />
<br />
Format: "(In [distance],) [instruction], and then [instruction]"<br />
{| class="wikitable"<br />
!Examples<br />
|-<br />
|In 0.1 miles, turn left, and then turn right<br />
|-<br />
|Exit right, and then keep left<br />
|}<br />
=== Occurrence === <br />
The following is the order of the most common occurrence:<br />
* 3<br />
* 1, 3<br />
* 1, 2, 3<br />
This is another way of saying:<br />
* Instruction 3 is (virtually) always given. <br />
* Instruction 1 is given only if there will be instruction 3 and there is enough time for both. <br />
* Instruction 2 is given only if there was instruction 1 and there has been enough time since instruction 1.</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=Audible_instructions&diff=173945Audible instructions2021-03-26T07:15:52Z<p>Tonestertm: /* Combined instructions */ corrected condition for a "then" prompt</p>
<hr />
<div>When navigating in Waze with all sound turned on (rather than alerts only), Waze will issue various audible instructions at various times in order to prepare and inform the user to make a certain movement.<br />
[[File:Voicelist.png|thumb]]<br />
The occurrence, timing and format of these instructions do not depend upon the language of the voice, but they do depend upon whether the voice chosen to speak the instructions ''includes street names''. Voices that include street names are speech synthesizers, which convert text to speech (TTS). Voices that do not include street names are simple collections of recorded phrases. We'll call these two categories of voices "TTS" and "non-TTS" respectively.<br />
<br />
== TTS ==<br />
TTS voices are sophisticated speech engines, which say not only street names, but also place names and more detailed information in general regarding navigation and alerts. These include Jane, which speaks US English; Kate and Thomas, which speak UK English; and also Ariane, Marusya and dozens of others in various languages. All examples in this section were documented using Jane, as this is the only TTS voice in Waze that speaks US English and the only TTS voice maintained by the US Waze community.<br />
<br />
From a TTS voice there are four possible audible instructions before a movement. Depending upon speed, distances, and timing, anywhere from one to four of these instructions may be heard. We'll call them the '''initial''', '''attention''', '''approach''' and '''final''' instructions. For simplicity we'll also assign them the letters '''A''' through '''D'''.<br />
<br />
=== Initial instruction (A) ===<br />
Instruction A is given a few seconds after the previous movement (or, if the previous movement is onto a ramp, a few seconds after exiting the ramp(s) onto which the previous instruction brought you), unless you are so close to the next movement that there is not enough time to give both instruction A and D (in which case only instruction D is given).<br />
<br />
Format depends on distance to next movement.<br />
* If distance to next movement > 4.35 mi (7.0 km), "Continue straight for (x hours and) y minutes to [street name]"<br />
* If distance to next movement < 4.35 mi (7.0 km), "In [distance], [instruction] [on/to] [street name]"<br />
<br />
{| class="wikitable" style="text-align: left;"<br />
|-<br />
! Distance to next movement<br />
! Example<br />
|-<br />
| rowspan="2" style="border-bottom: 1px solid #93c4d3;" | > 4.35 mi (7.0 km)<br />
| Continue straight for 15 minutes to Rue Royale<br />
|-<br />
| style="border-bottom: 1px solid #93c4d3;" | Continue straight for 2 hours and 15 minutes to Exit 123: I-45 N / Bakerstown<br />
|-<br />
| rowspan="2" | < 4.35 mi (7.0 km)<br />
| In 700 feet, turn left on Brightview Blvd<br />
|-<br />
| In 2.1 miles, exit to Exit 98: SR-76 / Chilltown<br />
|-<br />
|}<br />
<br />
=== Attention instruction (B) ===<br />
Instruction B is intended to bring the driver's attention back to navigation after a long period of stasis. It is given at the point where the movement is expected to be 5 minutes away, but only if it's been at least 15-20 minutes since instruction A. While the timing of the instruction is time-based, the instruction is given in distance.<br />
<br />
Format: "In [x] miles, [instruction] [on/to] [street name]"<br />
{| class="wikitable" style="text-align: left;"<br />
|-<br />
! examples<br />
|-<br />
| In 3.4 miles, turn left on Brightview Blvd<br />
|-<br />
| In 6 miles, exit right to Exit 98: SR-76 / Chilltown<br />
|-<br />
|}<br />
<br />
=== Approach instruction (C) ===<br />
Instruction C is given at a certain distance from the movement depending on your speed as detected at that point, unless the prior instruction was given too close to the timing of instruction C. The street name may or may not be included, depending on how long it has been since Instruction A (a couple minutes).<br />
<br />
Format: "In [distance], [instruction] ([on/to] [street name]"<br />
<br />
{| class="wikitable" style="text-align: left;"<br />
|-<br />
! speed range<br />
! distance <br />
! example<br />
|-<br />
| 0 – 43.5 mph (0 – 70 km/h)<br />
|1000 ft<br />
| In one thousand feet, turn right<br />
|-<br />
|43.5 – 55.9 mph (70 – 90 km/h)<br />
| 0.5 mi<br />
| In half a mile, exit left<br />
|-<br />
| 55.9 – 93.2 mph (90 – 150 km/h)<br />
| 1 mi<br />
| In one mile, stay to the right to I-75 N<br />
|-<br />
| 93.2+ mph (150+ km/h)<br />
| 2 mi<br />
| In two miles, exit right<br />
|-<br />
|}<br />
<br />
=== Final instruction (D) ===<br />
Instruction D is given every time, just before the movement (unless you make the turn before Waze has a chance to call it out).<br />
<br />
Format: "[instruction] [on/to] [street name]"<br />
{| class="wikitable" style="text-align: left;"<br />
|-<br />
! examples<br />
|-<br />
| Turn right on Main St<br />
|-<br />
| Exit left to Exit 234B: Poydras St / Superdome<br />
|-<br />
|}<br />
<br />
=== Combined instructions ===<br />
If, based on collected speed data for the time of day and day of the week, Waze expects the following movement to occur within about 30 seconds after the upcoming movement, it will add an additional instruction after instructions C and D, beginning with "then".<br />
* Format after C: "In [distance], [instruction] ([on/to] [street name])*, then [instruction]"<br />
** *street name only said if street names following both instructions are identical or [[Navigation instructions for unnamed segments|inherited]]<br />
* Format after D: "[instruction] ([on/to] [street name])**, then [instruction] [on/to] [street name]"<br />
** **first street name only said if street names following each instruction are different<br />
{| class="wikitable" style="text-align: left;"<br />
|-<br />
! examples<br />
|-<br />
| In two miles, exit right to Exit 5A: I-71 S / Cincinnati, then stay to the left<br />
|-<br />
| Turn left on N High St, then turn right on Arcadia Ave<br />
|}<br />
<br />
=== Preposition choice ===<br />
When Jane says street names, those names are preceded by "on" or "to" according to a couple factors:<br />
* Following an instruction to exit or stay to the left or right, Waze always says "to" and the street name.<br />
* Following an instruction to turn left or right, continue straight, make a U-turn or do anything at a roundabout, Waze says either "to" or "on" depending on the road type of the next segment past the instruction.<br />
** If the next segment is a {{Ramp}}, Waze says "to" and the street name.<br />
** If the next segment is any other road type, Waze says "on" and the street name.<br />
The word "to" at the beginning of any street name, which is [[Road names#Exit ramps and entrance ramps .28on-ramps.29|common on ramp names in the USA]], is never a factor in whether Waze says "to" or "on" and is actually ignored in audible instructions. This means that if the name of a ramp is [[Navigation instructions for unnamed segments|inherited]] through an unnamed non-ramp segment, Waze will say "on" and will omit the "to" completely. For example, turning left through a roundabout made of non-ramp segments and onto a ramp with the name "to US-33 W / Lancaster" will produce the audible instruction "at the roundabout, turn left on US-33 W / Lancaster."<br />
<br />
=== Occurrence === <br />
The following is the order of the most common occurrence:<br />
* D<br />
* A, D<br />
* A, C, D<br />
* A, B, C, D<br />
This is another way of saying:<br />
* Instruction D is (virtually) always given. <br />
* Instruction A is given only if there will be instruction D and there is enough time for both. <br />
* Instruction C is given only if there was instruction A and there has been enough time since instruction A. <br />
* Instruction B is given only if there will be instruction C (and therefore there was instruction A) and there has been enough time since instruction A.<br />
<br />
=== Notes ===<br />
* Any English-speaking TTS voice does not say the exit direction after instruction A. This can be confusing where a left exit follows shortly after another movement on a highway, since drivers may assume a right exit based.<br />
* Jane says "stay to the" rather than "keep" for keep left/right instructions.<br />
* Jane never says street names after "at the roundabout continue straight" or "at the roundabout make a U-turn" instructions unless they are combined with a different instruction.<br />
<br />
=== Flowchart ===<br />
[[File:TTS Flowchart.png]]<br />
<br />
== Non-TTS ==<br />
[[File:Voicerecorder.png|thumb]]<br />
Non-TTS voices are sets of recorded phrases. These include Amy and Nathan, any novelty voice like Boy Band, most other voices in other languages, and any user-recorded voices. The voice recorder contains the extent of what all non-TTS voices can say, and it is viewable in the app by tapping "record new voice" in the Waze voice menu.<br />
<br />
From a non-TTS voice there are three possible audible instructions before a movement. Depending upon speed, distances, and timing, anywhere from one to three of these instructions may be heard. We'll call them '''first approach''', '''second approach''', and '''final''' instructions. For simplicity, we'll also assign them numbers '''1''' through '''3'''.<br />
<br />
=== First approach instruction (1) ===<br />
The first approach instruction is given when enough time and advance distance is available for it. The actual distance from the previous movement to the next movement is rounded up to give the distance used in the instruction.<br />
<br />
Format: "In [distance], [instruction]"<br />
{| class="wikitable" style="text-align: left;"<br />
|-<br />
! speed and/or distance to next movement<br />
! example<br />
|-<br />
|style="border-bottom: 1px solid #93c4d3"|< 0.1 mi<br />
|style="border-bottom: 1px solid #93c4d3"|In 0.1 miles, continue straight<br />
|-<br />
|style="border-bottom: 1px solid #93c4d3"|0.1 mi - 0.25 mi<br />
|style="border-bottom: 1px solid #93c4d3"|In a quarter of a mile, turn right<br />
|-<br />
|style="border-bottom: 1px solid #93c4d3"|0.25 - 0.5 mi<br />
|rowspan="2" style="border-bottom: 1px solid #93c4d3"|In half a mile, at the roundabout turn left<br />
|-<br />
|style="white-space: nowrap; border-bottom: 1px solid #93c4d3"|0-43.5 mph (0-70 km/h) and > 0.25 mi<br />
|-<br />
|style="border-bottom: 1px solid #93c4d3"|43.5+ mph (70+ km/h) and > 0.5 mi<br />
|style="border-bottom: 1px solid #93c4d3"|In 1 mile, make a U-turn<br />
|}<br />
<br />
=== Second approach instruction (2) ===<br />
A second approach instruction is given at a certain distance from the movement depending on your speed, unless the first approach instruction was given too close to the timing of the second.<br />
<br />
Format: "In [distance], [instruction]"<br />
{| class="wikitable"<br />
!Speed<br />
!Example<br />
|-<br />
|0-43.5 mph (0-70 km/h)<br />
|In 0.1 miles, keep right<br />
|-<br />
|43.5+ mph (70+ km/h)<br />
|In a quarter of a mile, exit left<br />
|}<br />
<br />
=== Final instruction (3) ===<br />
The final instruction is given every time, just before the movement (unless you make the turn before Waze has a chance to call it out).<br />
<br />
Format: "[instruction]"<br />
{| class="wikitable"<br />
!Examples<br />
|-<br />
|Turn left<br />
|-<br />
|At the roundabout take the fifth exit<br />
|}<br />
<br />
=== Combined instructions ===<br />
If a second movement is planned less than around 500 feet from the first, Waze will tack a second instruction onto the end of any instruction less than a quarter of a mile away from the first movement, separated by "and then".<br />
<br />
Format: "(In [distance],) [instruction], and then [instruction]"<br />
{| class="wikitable"<br />
!Examples<br />
|-<br />
|In 0.1 miles, turn left, and then turn right<br />
|-<br />
|Exit right, and then keep left<br />
|}<br />
=== Occurrence === <br />
The following is the order of the most common occurrence:<br />
* 3<br />
* 1, 3<br />
* 1, 2, 3<br />
This is another way of saying:<br />
* Instruction 3 is (virtually) always given. <br />
* Instruction 1 is given only if there will be instruction 3 and there is enough time for both. <br />
* Instruction 2 is given only if there was instruction 1 and there has been enough time since instruction 1.</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Tonestertm/California_GIS_sources&diff=173632User:Tonestertm/California GIS sources2021-01-08T09:09:06Z<p>Tonestertm: /* Orange County */ Update OC link</p>
<hr />
<div><span style="color:#FF0000">This page is under construction.</span> If you'd like to help out, please, [http://www.waze.com/forum/ucp.php?i=pm&mode=compose&username=tonestertm PM tonestertm] before making any changes.<br />
<br />
<br />
'''A Collection of interactive GIS maps for municipalities throughout California.'''<br />
<br />
<br />
Caltrans has a [https://caltrans.maps.arcgis.com/apps/webappviewer/index.html?id=026e830c914c495797c969a3e5668538 new interactive map] with layers for Functional Classification, counties, Caltrans Districts, and a few other useful things. Note that the FC data on here is the same as the CRS Grid maps accessible through the [https://wazeopedia.waze.com/wiki/USA/User:Tonestertm/CRS_grid_bookmarklet CRS Grid bookmarklet].<br />
<br />
The [http://portal.gis.ca.gov/geoportal/viewer/index.jsp California Geoportal Viewer] is an all-state viewer, with only a Roads layer. It is very quick and easy to use, but may not be quite as up to date as local maps. <br />
<br />
''Note: In most cases, the links below will land you on the map itself, but sometimes it is is necessary to accept a disclaimer before viewing the map. A few maps require the use of Internet Explorer (noted), others require installation of the Silverlight plugin, and still others require an Autodesk plugin. Where there is no ''County'' interactive viewer, static map pages are linked and so indicated (I hope, let me know) by italics. A few counties do not yet publish online maps; use the Geoportal Viewer for these. '' <br />
<br />
Above all, understand that map availability is constantly changing. If you don't see what you're looking for here, try a search for "GIS" and the location you're looking for; it's quite possible there's a map now. And if you find one, let me know, so I can add it! <br />
<br />
Thanks to users '''ababcock, abc1357, AquaZR1, bwawsc, citeman, Cardyin, dfortney, robertonthego, turbomkt''' for contributing! (Anyone I've missed? Please let me know) <br />
<br />
[[File:California_counties_outline_map.png|right|California counties outline map]]<br />
<br />
==== [http://www.acgov.org/assessor/resources/parcel_viewer.htm Alameda County] ====<br />
<br />
Alameda<br />
Albany<br />
[http://www.cityofberkeley.info/ContentDisplay.aspx?id=55706 Berkeley]<br />
Dublin<br />
Emeryville<br />
Fremont<br />
Hayward<br />
Livermore<br />
Newark<br />
[http://mapgis.oaklandnet.com/planmap/ Oakland]<br />
Piedmont<br />
Pleasanton<br />
San Leandro<br />
Union City<br />
<br />
==== Alpine County ====<br />
<br />
No Cities<br />
<br />
==== [https://gisviewer.amadorgov.org/gpv/Viewer.aspx Amador County] ====<br />
<br />
<br />
Amador<br />
Ione<br />
Jackson<br />
Plymouth<br />
Sutter Creek<br />
<br />
==== [http://gis.buttecounty.net/public/index.html?viewer=pwsearch/ Butte County] ====<br />
<br />
Biggs<br />
Chico<br />
Gridley<br />
Oroville<br />
Paradise<br />
<br />
==== [http://mapserver.co.calaveras.ca.us/genplan_pub/index.html Calaveras County] ====<br />
<br />
Angels Camp<br />
<br />
==== [http://colusacountydpw.maps.arcgis.com/apps/webappviewer/index.html?id=ba6fd932ef964ce7b9f17e6fdfd2f6f2 Colusa County] ==== <br />
<br />
Colusa<br />
Williams<br />
<br />
==== [https://ccmap.cccounty.us/Html5/index.html?viewer=CCMAP Contra Costa County] ====<br />
<br />
[http://www.antiochprospector.com/ Antioch]<br />
Brentwood<br />
Clayton<br />
Concord<br />
Danville<br />
El Cerrito<br />
Hercules<br />
Lafayette<br />
Martinez<br />
Moraga<br />
Oakley<br />
Orinda<br />
Pinole<br />
Pittsburg<br />
Pleasant Hill<br />
[http://www.ci.richmond.ca.us/index.aspx?NID=865 Richmond]<br />
San Pablo<br />
San Ramon<br />
Walnut Creek<br />
<br />
==== Del Norte County ====<br />
<br />
Crescent City<br />
<br />
==== [https://see-eldorado.edcgov.us/ugotnet/ El Dorado County] ====<br />
<br />
Placerville<br />
South Lake Tahoe<br />
<br />
==== [https://gisportal.co.fresno.ca.us/portal/apps/webappviewer/index.html?id=b921843d343d4df998b5b3c6a301756a Fresno County] ====<br />
<br />
Clovis<br />
Coalinga<br />
Firebaugh<br />
Fowler<br />
[http://gis4u.fresno.gov/viewer/ Fresno]<br />
Huron<br />
Kerman<br />
Kingsburg<br />
Mendota<br />
Orange Cove<br />
Parlier<br />
Reedley<br />
Sanger<br />
Selma<br />
<br />
==== [http://gis.gcppwa.net/districts/ Glenn County] ====<br />
<br />
Orland<br />
Willows<br />
<br />
==== [http://gis.co.humboldt.ca.us/Freeance/Client/PublicAccess1/index.html?appconfig=podgis4 Humboldt County] ====<br />
<br />
Arcata<br />
Blue Lake<br />
Eureka<br />
Ferndale<br />
Fortuna<br />
Rio Dell<br />
Trinidad<br />
<br />
==== [https://www.geoviewer8.com/?username=icpublic&password=icpublic Imperial County ]====<br />
<br />
Brawley<br />
Calexico<br />
Calipatria<br />
El Centro<br />
Holtville<br />
Imperial<br />
Westmorland<br />
<br />
==== [https://inyocounty.maps.arcgis.com/apps/webappviewer/index.html?id=f3db09212fcf4d5eb0beee16f26e040c Inyo County] ====<br />
<br />
Bishop<br />
<br />
==== [http://maps.co.kern.ca.us/H5/index.html?viewer=public Kern County] ====<br />
<br />
Arvin<br />
[https://cob.maps.arcgis.com/apps/webappviewer/index.html?id=9174f084addc450286ac067a56fdb83f Bakersfield] <br />
California City<br />
Delano<br />
Maricopa<br />
Mcfarland<br />
Ridgecrest<br />
Shafter<br />
Taft<br />
Tehachapi<br />
Wasco<br />
<br />
==== [http://www.kingscountygis.com/maps/ Kings County] ====<br />
<br />
Avenal<br />
Corcoran<br />
Hanford<br />
Lemoore<br />
<br />
==== Lake County ====<br />
<br />
Clearlake<br />
Lakeport<br />
<br />
==== Lassen County ====<br />
<br />
Susanville<br />
<br />
====[http://rpgis.isd.lacounty.gov/Html5Viewer/index.html?viewer=GISNET_Public.GIS-NET_Public Los Angeles County] ==== <br />
<br />
[http://maps.assessor.lacounty.gov/GVH_2_2/Index.html?configBase=http://maps.assessor.lacounty.gov/Geocortex/Essentials/REST/sites/PAIS/viewers/PAIS_hv/virtualdirectory/Resources/Config/Default LA County Assessor's map]<br />
<br />
Agoura Hills<br />
Alhambra<br />
Arcadia<br />
Artesia<br />
Avalon<br />
Azusa<br />
Baldwin Park<br />
Bell<br />
Bellflower<br />
Bell Gardens<br />
Beverly Hills<br />
Bradbury<br />
[http://burbankca.maps.arcgis.com/apps/Solutions/s2.html?appid=06adc1d9e2c84c5f9a366014cbef7cb0 Burbank]<br />
Calabasas<br />
[http://www.carsonproperty.info/ Carson]<br />
Cerritos<br />
Claremont<br />
Commerce<br />
Compton<br />
Covina<br />
Cudahy<br />
[http://gisproxy.culvercity.org/SilverlightViewer_1_8/Viewer.html?Viewer=ExternalInfo Culver City - ''requires Silverlight'']<br />
Diamond Bar<br />
Downey<br />
Duarte<br />
El Monte<br />
[http://www.elsegundo.org/civicax/filebank/blobdload.aspx?blobid=7552 ''El Segundo'']<br />
Gardena<br />
Glendale<br />
Glendora<br />
Hawaiian Gardens<br />
Hawthorne<br />
[http://www.hermosabch.org/modules/showdocument.aspx?documentid=417 ''Hermosa Beach'']<br />
Hidden Hills<br />
Huntington Park<br />
Industry<br />
Inglewood<br />
Irwindale<br />
La Canada Flintridge<br />
La Habra Heights<br />
Lakewood<br />
La Mirada<br />
Lancaster<br />
La Puente<br />
La Verne<br />
Lawndale<br />
Lomita<br />
Long Beach<br />
[http://navigatela.lacity.org/navigatela/ Los Angeles]<br />
Lynwood<br />
Malibu<br />
[http://manhattanbeach.geocortex.com/maps/ Manhattan Beach]<br />
Maywood<br />
Monrovia<br />
Montebello<br />
Monterey Park<br />
Norwalk<br />
[http://maps.cityofpalmdale.org/FMv2/default.aspx Palmdale]<br />
Palos Verdes Estates<br />
Paramount<br />
Pasadena<br />
Pico Rivera<br />
Pomona<br />
Rancho Palos Verdes<br />
Redondo Beach<br />
Rolling Hills<br />
Rolling Hills Estates<br />
Rosemead<br />
San Dimas<br />
San Fernando<br />
San Gabriel<br />
San Marino<br />
[http://gis.santa-clarita.com/html5/MasterPUB.html Santa Clarita] [http://gis.santa-clarita.com/slv/?Viewer=MasterPUB Santa Clarita Alt - ''requires Silverlight'']<br />
Santa Fe Springs<br />
[http://csmgisweb.smgov.net/Html5Viewer/Index.html?configBase=http://csmgisweb.smgov.net/Geocortex/Essentials/REST/sites/laco_test/viewers/LACO_base_test_html5/virtualdirectory/Resources/Config/Default Santa Monica]<br />
Sierra Madre<br />
Signal Hill<br />
South El Monte<br />
South Gate<br />
South Pasadena<br />
Temple City<br />
[http://www.torranceca.gov/PDF/StnxmapTARA(everything)2016_24X36.pdf Torrance]<br />
Vernon<br />
Walnut<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/westcovina/prerelease_index.aspx# West Covina]<br />
West Hollywood<br />
Westlake Village<br />
Whittier<br />
<br />
====[http://countymadera.maps.arcgis.com/apps/Solutions/s2.html?appid=894807923d764977bdacde99fb4508ae Madera County ]====<br />
<br />
Chowchilla<br />
Madera<br />
<br />
==== [http://www.marinmap.org/Html5Viewer/Index.html?viewer=mmdataviewer Marin County] ====<br />
<br />
Belvedere<br />
Corte Madera<br />
Fairfax<br />
Larkspur<br />
Mill Valley<br />
Novato<br />
Ross<br />
San Anselmo<br />
San Rafael<br />
Sausalito<br />
Tiburon<br />
<br />
==== Mariposa County ====<br />
<br />
No Cities<br />
<br />
==== [http://www.co.mendocino.ca.us/econdev/gis/mapping.htm Mendocino County] ====<br />
<br />
Fort Bragg<br />
Point Arena<br />
Ukiah<br />
Willits<br />
<br />
==== [http://map.co.merced.ca.us/SL/?Viewer=mapmerced Merced County] ====<br />
[http://mcaggis.com/MCAGBaseMap/ Alternate map]<br />
<br />
Atwater<br />
Dos Palos<br />
Gustine<br />
Livingston<br />
Los Banos<br />
Merced<br />
<br />
==== Modoc County ====<br />
<br />
Alturas<br />
<br />
==== [https://monomammoth.maps.arcgis.com/apps/Viewer/index.html?appid=8670c63cda0540b39c3ae388cdd7db78 Mono County] ====<br />
(not exactly a GIS, but seems to be official assessor info)<br />
<br />
Mammoth Lakes<br />
<br />
==== [http://65.249.61.35/MCo_MapViewer/ Monterey County] ====<br />
<br />
Carmel-By-The-Sea<br />
Del Rey Oaks<br />
Gonzales<br />
Greenfield<br />
King City<br />
Marina<br />
Monterey<br />
Pacific Grove<br />
Salinas<br />
Sand City<br />
Seaside<br />
Soledad<br />
<br />
==== [http://gis.napa.ca.gov/html5viewer/?viewer=public_html Napa County] ====<br />
<br />
American Canyon<br />
Calistoga<br />
Napa<br />
St Helena<br />
<br />
==== [http://gis.nevcounty.net/MyNeighborhood/ Nevada County] ====<br />
<br />
Grass Valley<br />
Nevada City<br />
[https://townoftruckee.maps.arcgis.com/apps/webappviewer/index.html?id=902bc3bcf8bb4c1b94f45d9b10c343f6 Truckee]<br />
<br />
==== [https://www.ocgis.com/ocpw/landrecords/ Orange County] ====<br />
<br />
[https://alisoviejo.maps.arcgis.com/apps/webappviewer/index.html?id=9ee5473b3ccb41c69c340ab16fdbfdf8 Aliso Viejo]<br />
Anaheim<br />
Brea<br />
Buena Park<br />
Costa Mesa<br />
Cypress<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/danapoint/index.aspx Dana Point]<br />
Fountain Valley<br />
[http://fullertoncagis.maps.arcgis.com/apps/webappviewer/index.html?id=ff9b168a7d2c448abefe7d406e14b549 Fullerton]<br />
Garden Grove<br />
Huntington Beach<br />
[http://gis.cityofirvine.org/onlineparcel/ Irvine]<br />
[http://gisweb.lagunabeachcity.net/Html5Viewer/index.html?configBase=http://gisweb.lagunabeachcity.net/Geocortex/Essentials/REST/sites/GISMap3/viewers/HTML5_22/virtualdirectory/Resources/Config/Default Laguna Beach]<br />
Laguna Hills<br />
[http://gis.cityoflagunaniguel.org/PublicViewer/ Laguna Niguel]<br />
Laguna Woods<br />
La Habra<br />
[http://www.lakeforestca.gov/DocumentCenter/View/1191 ''Lake Forest'']<br />
La Palma<br />
Los Alamitos<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/Missionviejo/index.aspx Mission Viejo]<br />
[http://nbgis.newportbeachca.gov/NewportHTML5Viewer/?viewer=publicsite Newport Beach]<br />
[http://gis.cityoforange.org/maps/centerlineties.html Orange]<br />
Placentia<br />
Rancho Santa Margarita<br />
San Clemente<br />
San Juan Capistrano<br />
[http://maps.digitalmapcentral.com/production/vecommunityview/cities/santaana/index.aspx# Santa Ana]<br />
Seal Beach<br />
Stanton<br />
Tustin<br />
Villa Park<br />
Westminster<br />
Yorba Linda<br />
<br />
==== [http://placer.ca.gov/map-search Placer County] ====<br />
<br />
Auburn<br />
Colfax<br />
Lincoln<br />
Loomis<br />
Rocklin<br />
[http://www.roseville.ca.us/eservices/maps_n_data/map_center.asp Roseville]<br />
<br />
==== [https://secure.simplelayers.com/?do=start&project=1111&application=CG3Viewer&embedded=1&bgcolor=ffffff&width=975&height=735&context=22 Plumas County] ====<br />
<br />
Portola<br />
<br />
==== [https://gis.countyofriverside.us/Html5Viewer/?viewer=MMC_Public Riverside County] ====<br />
<br />
Banning<br />
[http://beaumontca.gov/index.aspx?NID=983 Beaumont]<br />
Blythe<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/calimesa/index.aspx# Calimesa]<br />
Canyon Lake<br />
Cathedral City<br />
Coachella<br />
[http://cityofcorona.maps.arcgis.com/apps/webappviewer/index.html?id=36c7d42973f441819670d6f812b6b280 Corona]<br />
Desert Hot Springs<br />
[http://www.eastvaleca.gov/index.aspx?page=43 Eastvale]<br />
Hemet<br />
Indian Wells<br />
Indio<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/JurupaValley/index.aspx Jurupa Valley]<br />
Lake Elsinore<br />
La Quinta<br />
Menifee<br />
[http://www.moreno-valley.ca.us/city_hall/city_maps.shtml Moreno Valley]<br />
Murrieta<br />
Norco<br />
Palm Desert<br />
Palm Springs<br />
[http://maps.digitalmapcentral.com/production/vecommunityview/cities/perris/index.aspx Perris]<br />
[https://www.ranchomirageca.gov/content_files/pdf/about_rancho_mirage/city_map.pdf Rancho Mirage]<br />
Riverside<br />
San Jacinto<br />
Temecula<br />
Wildomar<br />
<br />
==== [http://generalmap.gis.saccounty.net/JSViewer/county_portal.html Sacramento County] ====<br />
[http://assessorparcelviewer.saccounty.net/GISViewer/Default.aspx Assessor map] for addresses / House Numbers<br />
<br />
Citrus Heights<br />
[http://elkgrovemap.gis.saccounty.net/jsviewer/elkgrove.html Elk Grove]<br />
Folsom<br />
Galt<br />
Isleton<br />
Rancho Cordova<br />
Sacramento<br />
<br />
==== [https://cosb.maps.arcgis.com/home/webmap/viewer.html?webmap=4071773f6b004aaf8ee8d275b6b400b2 San Benito County] ====<br />
Problem: http://www.lynxgis.com/sanbenitoco/index2.cfm<br />
Hollister<br />
San Juan Bautista<br />
<br />
==== [http://maps.sanbag.ca.gov/flexviewer/default.htm San Bernardino County] ====<br />
<br />
Adelanto<br />
Apple Valley<br />
Barstow<br />
Big Bear Lake<br />
[http://www.cityofchino.org/home/showdocument?id=409 ''Chino'']<br />
Chino Hills<br />
Colton<br />
Fontana<br />
Grand Terrace<br />
Hesperia<br />
Highland<br />
Loma Linda<br />
Montclair<br />
Needles<br />
Ontario<br />
Rancho Cucamonga<br />
Redlands<br />
Rialto<br />
San Bernardino<br />
Twentynine Palms<br />
Upland<br />
Victorville<br />
Yucaipa<br />
Yucca Valley<br />
<br />
==== [http://www.sangis.org/ San Diego County] ====<br />
<br />
Carlsbad<br />
Chula Vista<br />
Coronado<br />
[http://delmar.geoviewer.io/ Del Mar]<br />
El Cajon<br />
Encinitas<br />
Escondido<br />
Imperial Beach<br />
La Mesa<br />
Lemon Grove<br />
National City<br />
[http://oceansidefiles.com/uploads/Water/PlanningViewer/index.html Oceanside]<br />
Poway<br />
San Diego<br />
San Marcos<br />
Santee<br />
Solana Beach<br />
[https://gis.cityofvista.com/VistaGIS/ Vista]<br />
<br />
==== [http://sfgov.maps.arcgis.com/home/webmap/viewer.html?useExisting=1 San Francisco County] ====<br />
<br />
San Francisco City and County are one and the same<br />
<br />
==== [http://www.sjmap.org/DistrictViewer/Disclaimer.htm San Joaquin County] ====<br />
<br />
Escalon<br />
Lathrop<br />
Lodi<br />
Manteca<br />
Ripon<br />
[http://www.stocktongov.com/government/departments/communityDevelop/genPlanMap.html Stockton]<br />
Tracy<br />
<br />
==== [http://www.sloplanning.org/PermitView/MapSearch San Luis Obispo County] ====<br />
<br />
Arroyo Grande<br />
Atascadero<br />
El Paso De Robles<br />
Grover Beach<br />
Morro Bay<br />
Pismo Beach<br />
San Luis Obispo<br />
<br />
==== [http://maps.smcgov.org/planning/ San Mateo County] ====<br />
<br />
Atherton<br />
Belmont<br />
Brisbane<br />
Burlingame<br />
Colma<br />
Daly City<br />
East Palo Alto<br />
Foster City<br />
Half Moon Bay<br />
Hillsborough<br />
Menlo Park<br />
Millbrae<br />
Pacifica<br />
Portola Valley<br />
Redwood City<br />
San Bruno<br />
San Carlos<br />
San Mateo<br />
South San Francisco<br />
Woodside<br />
<br />
==== [https://secure.simplelayers.com/?do=start&project=939&application=CG3Viewer&embedded=1&query_url=0&context=2 Santa Barbara County] ====<br />
<br />
Buellton<br />
Carpinteria<br />
Goleta<br />
Guadalupe<br />
Lompoc<br />
Santa Barbara<br />
Santa Maria<br />
Solvang<br />
<br />
==== [http://www.sccgov.org/gis/SCCPubInteractiveMap/# Santa Clara County] ====<br />
<br />
Campbell<br />
Cupertino<br />
Gilroy<br />
Los Altos<br />
Los Altos Hills<br />
Los Gatos<br />
Milpitas<br />
Monte Sereno<br />
Morgan Hill<br />
Mountain View<br />
Palo Alto<br />
San Jose<br />
Santa Clara<br />
Saratoga<br />
Sunnyvale<br />
<br />
==== [http://gis.co.santa-cruz.ca.us/PublicGISWeb/ Santa Cruz County] ====<br />
<small>Recommend setting Base Map to None for above</small><br />
<br />
Capitola<br />
Santa Cruz<br />
Scotts Valley<br />
Watsonville<br />
<br />
==== [http://gis.co.shasta.ca.us/Parcels/ Shasta County] ====<br />
<br />
Anderson<br />
[http://maps.ci.redding.ca.us/redding_pub/home/index.aspx Redding]<br />
Shasta Lake<br />
<br />
==== [http://demos2.calcad.com:8080/SierraCountyPublic/fusion.php Sierra County] ====<br />
<br />
Loyalton<br />
<br />
==== Siskiyou County ====<br />
<br />
Dorris<br />
Dunsmuir<br />
Etna<br />
Fort Jone<br />
Montague<br />
Mount Shasta<br />
Tulelake<br />
Weed<br />
Yreka<br />
<br />
==== [http://regis.solanocounty.com/Html5Viewer/Index.html?configBase=http://regis.solanocounty.com/Geocortex/Essentials/REST/sites/TaxParcelViewerNO/viewers/TaxParcelViewer-Solano_GIS_Viewer/virtualdirectory/Resources/Config/Default Solano County] ====<br />
<br />
Benicia<br />
Dixon<br />
Fairfield<br />
Rio Vista<br />
Suisun City<br />
Vacaville<br />
[http://gis.zoomprospector.com/client/Vallejo/ Vallejo]<br />
<br />
==== [https://sonomamap.maps.arcgis.com/apps/webappviewer/index.html?id=06ac7fe1b8554171b4682dc141293962 Sonoma County] ====<br />
<br />
Cloverdale<br />
Cotati<br />
Healdsburg<br />
Petaluma<br />
Rohnert Park<br />
Santa Rosa<br />
Sebastopol<br />
Sonoma Windsor<br />
<br />
==== [http://gis.stancounty.com/giscentral/public/map/esri/flex/parcelfinder/index.jsp# Stanislaus County] ====<br />
<br />
Ceres<br />
Hughson<br />
[http://gis.modestogov.com/ Modesto*]<br />
Newman<br />
Oakdale<br />
Patterson<br />
Riverbank<br />
Turlock<br />
Waterford<br />
<br />
==== Sutter County ====<br />
[http://www.co.sutter.ca.us/doc/apps/road_closures Construction and Road Closures]<br />
<br />
Live Oak<br />
Yuba City<br />
<br />
==== [http://www.arcgis.tehamacountypublicworks.ca.gov/ Tehama County] ====<br />
<br />
Corning<br />
[http://planningsites.org/RedBluffPlanning/ Red Bluff]<br />
Tehama<br />
<br />
==== [http://trinitycounty.maps.arcgis.com/apps/Viewer/index.html?appid=320cf1c1558c43c8b1f2f70c23d35026 Trinity County ] ====<br />
<br />
No Cities<br />
<br />
==== Tulare County ====<br />
<br />
:[http://tularecounty.ca.gov/tcict/index.cfm/geographic-information-system-gis/gis-maps/dinuba-city-map-jan-2008/ Dinuba] 2008 static map<br />
<br />
:[http://tularecounty.ca.gov/tcict/index.cfm/geographic-information-system-gis/gis-maps/exeter-city-map-jan-2008/ Exeter] 2008 Static map<br />
<br />
:[http://tularecounty.ca.gov/tcict/index.cfm/geographic-information-system-gis/gis-maps/farmersville-city-map-jan-2008/ Farmersville] 2008 Static map<br />
<br />
Lindsay<br />
[http://www.ci.porterville.ca.us/depts/CommunityDevelopment/webmaps/PublicWebmapPortal/webmap.html Porterville]<br />
[http://www.tulare.ca.gov/departments/community-development/development-services/planning/zoning-map Tulare] <br />
[http://visalia.maps.arcgis.com/apps/webappviewer/index.html?id=e78dfbb593044bf6bc1cf4f0d63c9160 Visalia]<br />
Woodlake<br />
<br />
==== [http://gis.co.tuolumne.ca.us:8093/flexviewers/General%20Plan%20And%20Zoning/ Tuolumne County] ====<br />
<br />
Sonora<br />
<br />
====[http://gis.ventura.org/Html5Viewer/index.html?viewer=CountyView.CountyView_gvh Ventura County] ====<br />
<br />
Camarillo<br />
Fillmore<br />
Moorpark<br />
Ojai<br />
Oxnard<br />
Port Hueneme<br />
San Buenaventura<br />
Santa Paula<br />
Simi Valley<br />
Thousand Oaks<br />
Ventura<br />
<br />
==== [http://yolo-gis-prod.yolocounty.org/SilverlightViewer_2_1/Viewer.html?ViewerConfig=http://yolo-gis-prod.yolocounty.org/Geocortex/Essentials/INTERNETPUBLIC/REST/sites/GIS_Public_Viewer/viewers/GIS_Public_Viewer/virtualdirectory/Config/Viewer.xml Yolo County] ====<br />
<br />
Davis<br />
West Sacramento<br />
Winters<br />
Woodland<br />
<br />
==== [http://gis.co.yuba.ca.us/portal_apps/parcelapp.html Yuba County] ====<br />
<br />
Marysville<br />
Wheatland</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=Nevada/Major_roads/Main&diff=173103Nevada/Major roads/Main2020-09-03T17:54:11Z<p>Tonestertm: /*Major_roads/Main*/Updated link to Functional Classification maps</p>
<hr />
<div><!-- 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><!--<br />
------ DO NOT MODIFY ABOVE THIS LINE -------- DO NOT MODIFY ABOVE THIS LINE ------> <br />
<br />
While there has been a little bit of confusion regarding the road types based on common sense. If you read the wiki, Nevada uses the DOT guidelines for the purpose of navigation routing and not based on the given name of the road. Nevada has a lot of graded gravel roads which are technically considered primary roads within WME. Before changing a road type to anything less than that which is assigned in the Nevada Department of Transportation (NDOT) functional classification check with an Area Manager, State Manager, Regional Coordinator, or Country Manager within the Nevada Forum.<br />
<br />
=== Local naming variations ===<br />
{{RootPage2}} uses '''NV-##''', and '''NV-##X''' for all state routes and their spurs, loops, etc. (e.g. '''NV-89''', '''NV-17M'''). When working on an area, if you encounter a road with the old '''SR-##''' naming, please take the time to change that name to reflect the '''NV-##''' name. This includes alternate names, if you notice them.<br />
<br />
It should be noted that while we use the '''NV-xxx''' road designation for better clarity for drivers using Waze, NDOT does not use it. When you are verifying a state route/highway number against an official source, you'll see "SR-89" instead of "NV-89", for example. This is ok, don't let that cause you concern. Just go ahead and use the NV-xxx designation (using the official route/highway ''number'') when setting/correcting a state route number.<br />
<br />
=== Functional Classifications ===<br />
{{RootPage2}} is following the [[National_resources/USA/Functional_classification|Functional Classification]] (FC) system for the USA.<br />
<br />
The following resource can help to determine the FC for some of the roads in Nevada:<br />
* [https://www.nevadadot.com/travel-info/maps/functional-classification-maps Nevada Functional Class Graphical Maps]<br />
**<span style="color:green">For historical purposes only</span> you can [http://web.archive.org/web/20140703042811/http://nevadadot.com/About_NDOT/NDOT_Divisions/Planning/Roadway_Systems/FCMGS.aspx Click here for archive version] as of July 3, 2014. Do not use this as a reference for setting FC on roads in WME.<br />
<br />
=== Lock Levels ===<br />
{{Lock Standard State|NV}}<br />
'''NOTE:''' Streets directly involved in the Las Vegas Strip area should be minimum locked at one rank (level) higher than the above minimums, to protect that vital traffic corridor.<br />
<br />
''Please note that the above lock levels are subject to change, should situations warrant. Be sure to check here for current lock level criteria if unsure.''<br />
<br />
<!---- DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ------ DO NOT MODIFY BELOW ----<br />
-------------------------------------------------------------------------------------<br />
---- This page is only transcluded into (displayed on) the main page for this state.<br />
---- It directly follows the common guidelines applicable to all states. When this<br />
---- page is present (even if blanked), it displaces any optional code that might be<br />
---- in that section.<br />
---- If the original optional code from the main page for this section is still<br />
---- desired, it can be restored by adding the following code to the first line <br />
---- between the "DO NOT MODIFY" lines on this page:<br />
---- {{:USA/CommonState/Major_roads|optional}}<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- If there will be a full page for this section, use code similar to the wording<br />
---- below to provide a hyperlink to that page. When creating the full page, use the<br />
---- link on the talk page to ensure the preload data is provided to help with<br />
---- formatting the page. Don't just use the red link from this section once it is<br />
---- saved.<br />
----<br />
See [[{{BasePage2}}/Major roads]] for guidance in {{RootPage2}} that may not be universal to all other states.<br />
----<br />
-------------------------------------------------------------------------------------<br />
---- This section has three possible purposes:<br />
---- 1. It is only providing a hyperlink to the full page for this section.<br />
---- 2. It is only providing some unique guidance for this state that differs from<br />
---- other states.<br />
---- 3. It is intentionally wiping out the general optional content for this section<br />
---- for this state.<br />
------------------------------------------------------------------------------------></div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=User:Tonestertm/California_GIS_sources&diff=172808User:Tonestertm/California GIS sources2020-06-15T18:55:42Z<p>Tonestertm: /* Orange County */ Update Irvine link. Thanks, turbomkt!</p>
<hr />
<div><span style="color:#FF0000">This page is under construction.</span> If you'd like to help out, please, [http://www.waze.com/forum/ucp.php?i=pm&mode=compose&username=tonestertm PM tonestertm] before making any changes.<br />
<br />
<br />
'''A Collection of interactive GIS maps for municipalities throughout California.'''<br />
<br />
<br />
Caltrans has a [https://caltrans.maps.arcgis.com/apps/webappviewer/index.html?id=026e830c914c495797c969a3e5668538 new interactive map] with layers for Functional Classification, counties, Caltrans Districts, and a few other useful things. Note that the FC data on here is the same as the CRS Grid maps accessible through the [https://wazeopedia.waze.com/wiki/USA/User:Tonestertm/CRS_grid_bookmarklet CRS Grid bookmarklet].<br />
<br />
The [http://portal.gis.ca.gov/geoportal/viewer/index.jsp California Geoportal Viewer] is an all-state viewer, with only a Roads layer. It is very quick and easy to use, but may not be quite as up to date as local maps. <br />
<br />
''Note: In most cases, the links below will land you on the map itself, but sometimes it is is necessary to accept a disclaimer before viewing the map. A few maps require the use of Internet Explorer (noted), others require installation of the Silverlight plugin, and still others require an Autodesk plugin. Where there is no ''County'' interactive viewer, static map pages are linked and so indicated (I hope, let me know) by italics. A few counties do not yet publish online maps; use the Geoportal Viewer for these. '' <br />
<br />
Above all, understand that map availability is constantly changing. If you don't see what you're looking for here, try a search for "GIS" and the location you're looking for; it's quite possible there's a map now. And if you find one, let me know, so I can add it! <br />
<br />
Thanks to users '''ababcock, abc1357, AquaZR1, bwawsc, citeman, Cardyin, dfortney, robertonthego, turbomkt''' for contributing! (Anyone I've missed? Please let me know) <br />
<br />
[[File:California_counties_outline_map.png|right|California counties outline map]]<br />
<br />
==== [http://www.acgov.org/assessor/resources/parcel_viewer.htm Alameda County] ====<br />
<br />
Alameda<br />
Albany<br />
[http://www.cityofberkeley.info/ContentDisplay.aspx?id=55706 Berkeley]<br />
Dublin<br />
Emeryville<br />
Fremont<br />
Hayward<br />
Livermore<br />
Newark<br />
[http://mapgis.oaklandnet.com/planmap/ Oakland]<br />
Piedmont<br />
Pleasanton<br />
San Leandro<br />
Union City<br />
<br />
==== Alpine County ====<br />
<br />
No Cities<br />
<br />
==== [https://gisviewer.amadorgov.org/gpv/Viewer.aspx Amador County] ====<br />
<br />
<br />
Amador<br />
Ione<br />
Jackson<br />
Plymouth<br />
Sutter Creek<br />
<br />
==== [http://gis.buttecounty.net/public/index.html?viewer=pwsearch/ Butte County] ====<br />
<br />
Biggs<br />
Chico<br />
Gridley<br />
Oroville<br />
Paradise<br />
<br />
==== [http://mapserver.co.calaveras.ca.us/genplan_pub/index.html Calaveras County] ====<br />
<br />
Angels Camp<br />
<br />
==== [http://colusacountydpw.maps.arcgis.com/apps/webappviewer/index.html?id=ba6fd932ef964ce7b9f17e6fdfd2f6f2 Colusa County] ==== <br />
<br />
Colusa<br />
Williams<br />
<br />
==== [https://ccmap.cccounty.us/Html5/index.html?viewer=CCMAP Contra Costa County] ====<br />
<br />
[http://www.antiochprospector.com/ Antioch]<br />
Brentwood<br />
Clayton<br />
Concord<br />
Danville<br />
El Cerrito<br />
Hercules<br />
Lafayette<br />
Martinez<br />
Moraga<br />
Oakley<br />
Orinda<br />
Pinole<br />
Pittsburg<br />
Pleasant Hill<br />
[http://www.ci.richmond.ca.us/index.aspx?NID=865 Richmond]<br />
San Pablo<br />
San Ramon<br />
Walnut Creek<br />
<br />
==== Del Norte County ====<br />
<br />
Crescent City<br />
<br />
==== [https://see-eldorado.edcgov.us/ugotnet/ El Dorado County] ====<br />
<br />
Placerville<br />
South Lake Tahoe<br />
<br />
==== [https://gisportal.co.fresno.ca.us/portal/apps/webappviewer/index.html?id=b921843d343d4df998b5b3c6a301756a Fresno County] ====<br />
<br />
Clovis<br />
Coalinga<br />
Firebaugh<br />
Fowler<br />
[http://gis4u.fresno.gov/viewer/ Fresno]<br />
Huron<br />
Kerman<br />
Kingsburg<br />
Mendota<br />
Orange Cove<br />
Parlier<br />
Reedley<br />
Sanger<br />
Selma<br />
<br />
==== [http://gis.gcppwa.net/districts/ Glenn County] ====<br />
<br />
Orland<br />
Willows<br />
<br />
==== [http://gis.co.humboldt.ca.us/Freeance/Client/PublicAccess1/index.html?appconfig=podgis4 Humboldt County] ====<br />
<br />
Arcata<br />
Blue Lake<br />
Eureka<br />
Ferndale<br />
Fortuna<br />
Rio Dell<br />
Trinidad<br />
<br />
==== [https://www.geoviewer8.com/?username=icpublic&password=icpublic Imperial County ]====<br />
<br />
Brawley<br />
Calexico<br />
Calipatria<br />
El Centro<br />
Holtville<br />
Imperial<br />
Westmorland<br />
<br />
==== [https://inyocounty.maps.arcgis.com/apps/webappviewer/index.html?id=f3db09212fcf4d5eb0beee16f26e040c Inyo County] ====<br />
<br />
Bishop<br />
<br />
==== [http://maps.co.kern.ca.us/H5/index.html?viewer=public Kern County] ====<br />
<br />
Arvin<br />
[https://cob.maps.arcgis.com/apps/webappviewer/index.html?id=9174f084addc450286ac067a56fdb83f Bakersfield] <br />
California City<br />
Delano<br />
Maricopa<br />
Mcfarland<br />
Ridgecrest<br />
Shafter<br />
Taft<br />
Tehachapi<br />
Wasco<br />
<br />
==== [http://www.kingscountygis.com/maps/ Kings County] ====<br />
<br />
Avenal<br />
Corcoran<br />
Hanford<br />
Lemoore<br />
<br />
==== Lake County ====<br />
<br />
Clearlake<br />
Lakeport<br />
<br />
==== Lassen County ====<br />
<br />
Susanville<br />
<br />
====[http://rpgis.isd.lacounty.gov/Html5Viewer/index.html?viewer=GISNET_Public.GIS-NET_Public Los Angeles County] ==== <br />
<br />
[http://maps.assessor.lacounty.gov/GVH_2_2/Index.html?configBase=http://maps.assessor.lacounty.gov/Geocortex/Essentials/REST/sites/PAIS/viewers/PAIS_hv/virtualdirectory/Resources/Config/Default LA County Assessor's map]<br />
<br />
Agoura Hills<br />
Alhambra<br />
Arcadia<br />
Artesia<br />
Avalon<br />
Azusa<br />
Baldwin Park<br />
Bell<br />
Bellflower<br />
Bell Gardens<br />
Beverly Hills<br />
Bradbury<br />
[http://burbankca.maps.arcgis.com/apps/Solutions/s2.html?appid=06adc1d9e2c84c5f9a366014cbef7cb0 Burbank]<br />
Calabasas<br />
[http://www.carsonproperty.info/ Carson]<br />
Cerritos<br />
Claremont<br />
Commerce<br />
Compton<br />
Covina<br />
Cudahy<br />
[http://gisproxy.culvercity.org/SilverlightViewer_1_8/Viewer.html?Viewer=ExternalInfo Culver City - ''requires Silverlight'']<br />
Diamond Bar<br />
Downey<br />
Duarte<br />
El Monte<br />
[http://www.elsegundo.org/civicax/filebank/blobdload.aspx?blobid=7552 ''El Segundo'']<br />
Gardena<br />
Glendale<br />
Glendora<br />
Hawaiian Gardens<br />
Hawthorne<br />
[http://www.hermosabch.org/modules/showdocument.aspx?documentid=417 ''Hermosa Beach'']<br />
Hidden Hills<br />
Huntington Park<br />
Industry<br />
Inglewood<br />
Irwindale<br />
La Canada Flintridge<br />
La Habra Heights<br />
Lakewood<br />
La Mirada<br />
Lancaster<br />
La Puente<br />
La Verne<br />
Lawndale<br />
Lomita<br />
Long Beach<br />
[http://navigatela.lacity.org/navigatela/ Los Angeles]<br />
Lynwood<br />
Malibu<br />
[http://manhattanbeach.geocortex.com/maps/ Manhattan Beach]<br />
Maywood<br />
Monrovia<br />
Montebello<br />
Monterey Park<br />
Norwalk<br />
[http://maps.cityofpalmdale.org/FMv2/default.aspx Palmdale]<br />
Palos Verdes Estates<br />
Paramount<br />
Pasadena<br />
Pico Rivera<br />
Pomona<br />
Rancho Palos Verdes<br />
Redondo Beach<br />
Rolling Hills<br />
Rolling Hills Estates<br />
Rosemead<br />
San Dimas<br />
San Fernando<br />
San Gabriel<br />
San Marino<br />
[http://gis.santa-clarita.com/html5/MasterPUB.html Santa Clarita] [http://gis.santa-clarita.com/slv/?Viewer=MasterPUB Santa Clarita Alt - ''requires Silverlight'']<br />
Santa Fe Springs<br />
[http://csmgisweb.smgov.net/Html5Viewer/Index.html?configBase=http://csmgisweb.smgov.net/Geocortex/Essentials/REST/sites/laco_test/viewers/LACO_base_test_html5/virtualdirectory/Resources/Config/Default Santa Monica]<br />
Sierra Madre<br />
Signal Hill<br />
South El Monte<br />
South Gate<br />
South Pasadena<br />
Temple City<br />
[http://www.torranceca.gov/PDF/StnxmapTARA(everything)2016_24X36.pdf Torrance]<br />
Vernon<br />
Walnut<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/westcovina/prerelease_index.aspx# West Covina]<br />
West Hollywood<br />
Westlake Village<br />
Whittier<br />
<br />
====[http://countymadera.maps.arcgis.com/apps/Solutions/s2.html?appid=894807923d764977bdacde99fb4508ae Madera County ]====<br />
<br />
Chowchilla<br />
Madera<br />
<br />
==== [http://www.marinmap.org/Html5Viewer/Index.html?viewer=mmdataviewer Marin County] ====<br />
<br />
Belvedere<br />
Corte Madera<br />
Fairfax<br />
Larkspur<br />
Mill Valley<br />
Novato<br />
Ross<br />
San Anselmo<br />
San Rafael<br />
Sausalito<br />
Tiburon<br />
<br />
==== Mariposa County ====<br />
<br />
No Cities<br />
<br />
==== [http://www.co.mendocino.ca.us/econdev/gis/mapping.htm Mendocino County] ====<br />
<br />
Fort Bragg<br />
Point Arena<br />
Ukiah<br />
Willits<br />
<br />
==== [http://map.co.merced.ca.us/SL/?Viewer=mapmerced Merced County] ====<br />
[http://mcaggis.com/MCAGBaseMap/ Alternate map]<br />
<br />
Atwater<br />
Dos Palos<br />
Gustine<br />
Livingston<br />
Los Banos<br />
Merced<br />
<br />
==== Modoc County ====<br />
<br />
Alturas<br />
<br />
==== [https://monomammoth.maps.arcgis.com/apps/Viewer/index.html?appid=8670c63cda0540b39c3ae388cdd7db78 Mono County] ====<br />
(not exactly a GIS, but seems to be official assessor info)<br />
<br />
Mammoth Lakes<br />
<br />
==== [http://65.249.61.35/MCo_MapViewer/ Monterey County] ====<br />
<br />
Carmel-By-The-Sea<br />
Del Rey Oaks<br />
Gonzales<br />
Greenfield<br />
King City<br />
Marina<br />
Monterey<br />
Pacific Grove<br />
Salinas<br />
Sand City<br />
Seaside<br />
Soledad<br />
<br />
==== [http://gis.napa.ca.gov/html5viewer/?viewer=public_html Napa County] ====<br />
<br />
American Canyon<br />
Calistoga<br />
Napa<br />
St Helena<br />
<br />
==== [http://gis.nevcounty.net/MyNeighborhood/ Nevada County] ====<br />
<br />
Grass Valley<br />
Nevada City<br />
[https://townoftruckee.maps.arcgis.com/apps/webappviewer/index.html?id=902bc3bcf8bb4c1b94f45d9b10c343f6 Truckee]<br />
<br />
==== [http://landrecords.ocpublicworks.com/ocsl/ Orange County] ====<br />
<br />
[https://alisoviejo.maps.arcgis.com/apps/webappviewer/index.html?id=9ee5473b3ccb41c69c340ab16fdbfdf8 Aliso Viejo]<br />
Anaheim<br />
Brea<br />
Buena Park<br />
Costa Mesa<br />
Cypress<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/danapoint/index.aspx Dana Point]<br />
Fountain Valley<br />
[http://fullertoncagis.maps.arcgis.com/apps/webappviewer/index.html?id=ff9b168a7d2c448abefe7d406e14b549 Fullerton]<br />
Garden Grove<br />
Huntington Beach<br />
[http://gis.cityofirvine.org/onlineparcel/ Irvine]<br />
[http://gisweb.lagunabeachcity.net/Html5Viewer/index.html?configBase=http://gisweb.lagunabeachcity.net/Geocortex/Essentials/REST/sites/GISMap3/viewers/HTML5_22/virtualdirectory/Resources/Config/Default Laguna Beach]<br />
Laguna Hills<br />
[http://gis.cityoflagunaniguel.org/PublicViewer/ Laguna Niguel]<br />
Laguna Woods<br />
La Habra<br />
[http://www.lakeforestca.gov/DocumentCenter/View/1191 ''Lake Forest'']<br />
La Palma<br />
Los Alamitos<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/Missionviejo/index.aspx Mission Viejo]<br />
[http://nbgis.newportbeachca.gov/NewportHTML5Viewer/?viewer=publicsite Newport Beach]<br />
[http://gis.cityoforange.org/maps/centerlineties.html Orange]<br />
Placentia<br />
Rancho Santa Margarita<br />
San Clemente<br />
San Juan Capistrano<br />
[http://maps.digitalmapcentral.com/production/vecommunityview/cities/santaana/index.aspx# Santa Ana]<br />
Seal Beach<br />
Stanton<br />
Tustin<br />
Villa Park<br />
Westminster<br />
Yorba Linda<br />
<br />
==== [http://placer.ca.gov/map-search Placer County] ====<br />
<br />
Auburn<br />
Colfax<br />
Lincoln<br />
Loomis<br />
Rocklin<br />
[http://www.roseville.ca.us/eservices/maps_n_data/map_center.asp Roseville]<br />
<br />
==== [https://secure.simplelayers.com/?do=start&project=1111&application=CG3Viewer&embedded=1&bgcolor=ffffff&width=975&height=735&context=22 Plumas County] ====<br />
<br />
Portola<br />
<br />
==== [https://gis.countyofriverside.us/Html5Viewer/?viewer=MMC_Public Riverside County] ====<br />
<br />
Banning<br />
[http://beaumontca.gov/index.aspx?NID=983 Beaumont]<br />
Blythe<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/calimesa/index.aspx# Calimesa]<br />
Canyon Lake<br />
Cathedral City<br />
Coachella<br />
[http://cityofcorona.maps.arcgis.com/apps/webappviewer/index.html?id=36c7d42973f441819670d6f812b6b280 Corona]<br />
Desert Hot Springs<br />
[http://www.eastvaleca.gov/index.aspx?page=43 Eastvale]<br />
Hemet<br />
Indian Wells<br />
Indio<br />
[http://maps.digitalmapcentral.com/production/VECommunityView/cities/JurupaValley/index.aspx Jurupa Valley]<br />
Lake Elsinore<br />
La Quinta<br />
Menifee<br />
[http://www.moreno-valley.ca.us/city_hall/city_maps.shtml Moreno Valley]<br />
Murrieta<br />
Norco<br />
Palm Desert<br />
Palm Springs<br />
[http://maps.digitalmapcentral.com/production/vecommunityview/cities/perris/index.aspx Perris]<br />
[https://www.ranchomirageca.gov/content_files/pdf/about_rancho_mirage/city_map.pdf Rancho Mirage]<br />
Riverside<br />
San Jacinto<br />
Temecula<br />
Wildomar<br />
<br />
==== [http://generalmap.gis.saccounty.net/JSViewer/county_portal.html Sacramento County] ====<br />
[http://assessorparcelviewer.saccounty.net/GISViewer/Default.aspx Assessor map] for addresses / House Numbers<br />
<br />
Citrus Heights<br />
[http://elkgrovemap.gis.saccounty.net/jsviewer/elkgrove.html Elk Grove]<br />
Folsom<br />
Galt<br />
Isleton<br />
Rancho Cordova<br />
Sacramento<br />
<br />
==== [https://cosb.maps.arcgis.com/home/webmap/viewer.html?webmap=4071773f6b004aaf8ee8d275b6b400b2 San Benito County] ====<br />
Problem: http://www.lynxgis.com/sanbenitoco/index2.cfm<br />
Hollister<br />
San Juan Bautista<br />
<br />
==== [http://maps.sanbag.ca.gov/flexviewer/default.htm San Bernardino County] ====<br />
<br />
Adelanto<br />
Apple Valley<br />
Barstow<br />
Big Bear Lake<br />
[http://www.cityofchino.org/home/showdocument?id=409 ''Chino'']<br />
Chino Hills<br />
Colton<br />
Fontana<br />
Grand Terrace<br />
Hesperia<br />
Highland<br />
Loma Linda<br />
Montclair<br />
Needles<br />
Ontario<br />
Rancho Cucamonga<br />
Redlands<br />
Rialto<br />
San Bernardino<br />
Twentynine Palms<br />
Upland<br />
Victorville<br />
Yucaipa<br />
Yucca Valley<br />
<br />
==== [http://www.sangis.org/ San Diego County] ====<br />
<br />
Carlsbad<br />
Chula Vista<br />
Coronado<br />
[http://delmar.geoviewer.io/ Del Mar]<br />
El Cajon<br />
Encinitas<br />
Escondido<br />
Imperial Beach<br />
La Mesa<br />
Lemon Grove<br />
National City<br />
[http://oceansidefiles.com/uploads/Water/PlanningViewer/index.html Oceanside]<br />
Poway<br />
San Diego<br />
San Marcos<br />
Santee<br />
Solana Beach<br />
[https://gis.cityofvista.com/VistaGIS/ Vista]<br />
<br />
==== [http://sfgov.maps.arcgis.com/home/webmap/viewer.html?useExisting=1 San Francisco County] ====<br />
<br />
San Francisco City and County are one and the same<br />
<br />
==== [http://www.sjmap.org/DistrictViewer/Disclaimer.htm San Joaquin County] ====<br />
<br />
Escalon<br />
Lathrop<br />
Lodi<br />
Manteca<br />
Ripon<br />
[http://www.stocktongov.com/government/departments/communityDevelop/genPlanMap.html Stockton]<br />
Tracy<br />
<br />
==== [http://www.sloplanning.org/PermitView/MapSearch San Luis Obispo County] ====<br />
<br />
Arroyo Grande<br />
Atascadero<br />
El Paso De Robles<br />
Grover Beach<br />
Morro Bay<br />
Pismo Beach<br />
San Luis Obispo<br />
<br />
==== [http://maps.smcgov.org/planning/ San Mateo County] ====<br />
<br />
Atherton<br />
Belmont<br />
Brisbane<br />
Burlingame<br />
Colma<br />
Daly City<br />
East Palo Alto<br />
Foster City<br />
Half Moon Bay<br />
Hillsborough<br />
Menlo Park<br />
Millbrae<br />
Pacifica<br />
Portola Valley<br />
Redwood City<br />
San Bruno<br />
San Carlos<br />
San Mateo<br />
South San Francisco<br />
Woodside<br />
<br />
==== [https://secure.simplelayers.com/?do=start&project=939&application=CG3Viewer&embedded=1&query_url=0&context=2 Santa Barbara County] ====<br />
<br />
Buellton<br />
Carpinteria<br />
Goleta<br />
Guadalupe<br />
Lompoc<br />
Santa Barbara<br />
Santa Maria<br />
Solvang<br />
<br />
==== [http://www.sccgov.org/gis/SCCPubInteractiveMap/# Santa Clara County] ====<br />
<br />
Campbell<br />
Cupertino<br />
Gilroy<br />
Los Altos<br />
Los Altos Hills<br />
Los Gatos<br />
Milpitas<br />
Monte Sereno<br />
Morgan Hill<br />
Mountain View<br />
Palo Alto<br />
San Jose<br />
Santa Clara<br />
Saratoga<br />
Sunnyvale<br />
<br />
==== [http://gis.co.santa-cruz.ca.us/PublicGISWeb/ Santa Cruz County] ====<br />
<small>Recommend setting Base Map to None for above</small><br />
<br />
Capitola<br />
Santa Cruz<br />
Scotts Valley<br />
Watsonville<br />
<br />
==== [http://gis.co.shasta.ca.us/Parcels/ Shasta County] ====<br />
<br />
Anderson<br />
[http://maps.ci.redding.ca.us/redding_pub/home/index.aspx Redding]<br />
Shasta Lake<br />
<br />
==== [http://demos2.calcad.com:8080/SierraCountyPublic/fusion.php Sierra County] ====<br />
<br />
Loyalton<br />
<br />
==== Siskiyou County ====<br />
<br />
Dorris<br />
Dunsmuir<br />
Etna<br />
Fort Jone<br />
Montague<br />
Mount Shasta<br />
Tulelake<br />
Weed<br />
Yreka<br />
<br />
==== [http://regis.solanocounty.com/Html5Viewer/Index.html?configBase=http://regis.solanocounty.com/Geocortex/Essentials/REST/sites/TaxParcelViewerNO/viewers/TaxParcelViewer-Solano_GIS_Viewer/virtualdirectory/Resources/Config/Default Solano County] ====<br />
<br />
Benicia<br />
Dixon<br />
Fairfield<br />
Rio Vista<br />
Suisun City<br />
Vacaville<br />
[http://gis.zoomprospector.com/client/Vallejo/ Vallejo]<br />
<br />
==== [https://sonomamap.maps.arcgis.com/apps/webappviewer/index.html?id=06ac7fe1b8554171b4682dc141293962 Sonoma County] ====<br />
<br />
Cloverdale<br />
Cotati<br />
Healdsburg<br />
Petaluma<br />
Rohnert Park<br />
Santa Rosa<br />
Sebastopol<br />
Sonoma Windsor<br />
<br />
==== [http://gis.stancounty.com/giscentral/public/map/esri/flex/parcelfinder/index.jsp# Stanislaus County] ====<br />
<br />
Ceres<br />
Hughson<br />
[http://gis.modestogov.com/ Modesto*]<br />
Newman<br />
Oakdale<br />
Patterson<br />
Riverbank<br />
Turlock<br />
Waterford<br />
<br />
==== Sutter County ====<br />
[http://www.co.sutter.ca.us/doc/apps/road_closures Construction and Road Closures]<br />
<br />
Live Oak<br />
Yuba City<br />
<br />
==== [http://www.arcgis.tehamacountypublicworks.ca.gov/ Tehama County] ====<br />
<br />
Corning<br />
[http://planningsites.org/RedBluffPlanning/ Red Bluff]<br />
Tehama<br />
<br />
==== [http://trinitycounty.maps.arcgis.com/apps/Viewer/index.html?appid=320cf1c1558c43c8b1f2f70c23d35026 Trinity County ] ====<br />
<br />
No Cities<br />
<br />
==== Tulare County ====<br />
<br />
:[http://tularecounty.ca.gov/tcict/index.cfm/geographic-information-system-gis/gis-maps/dinuba-city-map-jan-2008/ Dinuba] 2008 static map<br />
<br />
:[http://tularecounty.ca.gov/tcict/index.cfm/geographic-information-system-gis/gis-maps/exeter-city-map-jan-2008/ Exeter] 2008 Static map<br />
<br />
:[http://tularecounty.ca.gov/tcict/index.cfm/geographic-information-system-gis/gis-maps/farmersville-city-map-jan-2008/ Farmersville] 2008 Static map<br />
<br />
Lindsay<br />
[http://www.ci.porterville.ca.us/depts/CommunityDevelopment/webmaps/PublicWebmapPortal/webmap.html Porterville]<br />
[http://www.tulare.ca.gov/departments/community-development/development-services/planning/zoning-map Tulare] <br />
[http://visalia.maps.arcgis.com/apps/webappviewer/index.html?id=e78dfbb593044bf6bc1cf4f0d63c9160 Visalia]<br />
Woodlake<br />
<br />
==== [http://gis.co.tuolumne.ca.us:8093/flexviewers/General%20Plan%20And%20Zoning/ Tuolumne County] ====<br />
<br />
Sonora<br />
<br />
====[http://gis.ventura.org/Html5Viewer/index.html?viewer=CountyView.CountyView_gvh Ventura County] ====<br />
<br />
Camarillo<br />
Fillmore<br />
Moorpark<br />
Ojai<br />
Oxnard<br />
Port Hueneme<br />
San Buenaventura<br />
Santa Paula<br />
Simi Valley<br />
Thousand Oaks<br />
Ventura<br />
<br />
==== [http://yolo-gis-prod.yolocounty.org/SilverlightViewer_2_1/Viewer.html?ViewerConfig=http://yolo-gis-prod.yolocounty.org/Geocortex/Essentials/INTERNETPUBLIC/REST/sites/GIS_Public_Viewer/viewers/GIS_Public_Viewer/virtualdirectory/Config/Viewer.xml Yolo County] ====<br />
<br />
Davis<br />
West Sacramento<br />
Winters<br />
Woodland<br />
<br />
==== [http://gis.co.yuba.ca.us/portal_apps/parcelapp.html Yuba County] ====<br />
<br />
Marysville<br />
Wheatland</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=Lanes&diff=172705Lanes2020-05-31T23:42:54Z<p>Tonestertm: /* Hash intersections */ Re-worked a number of sentences for clarity.</p>
<hr />
<div>{{construction | contact = https://www.waze.com/forum/viewtopic.php?f=1636&t=301141 | contacttype = forum | draft = no | open = no | revision = no | section = no | talk = no}}<br />
Lane guidance is a new Waze app feature that shows the user exactly which lanes they should use to make their next movement. This feature boosts Wazer confidence by providing reassurance in junctions both typical and unusual. <br />
Lane guidance data is added via the [[Waze Map Editor|Waze Map Editor (WME)]]. When a single segment is selected in the WME, an additional tab called Lanes is available in the left pane. The Lanes tab allows map editors to tell Waze which lane to display to the driver for lane guidance in the mobile app. <br><br />
<br />
There are some important considerations regarding lane guidance in Waze:<br />
* '''Lane guidance does not affect routing''' - it is merely a visual feature.<br />
* '''Lane guidance does not affect audio instructions''', with the exception of u-turn instructions resulting from [[#Lanes_on_divided_roadways|heuristics for intersections on divided roads]].<br />
* '''Lane guidance will only be displayed when a navigation instruction is given.''' If the [[How_Waze_determines_turn_/_keep_/_exit_maneuvers#Best_Continuation|best continuation]] is straight ahead, lane guidance will not be shown, unless there is a [[Turn_instruction_override|continue straight TIO]].<br />
{{mbox | type = protection | text = {{As of|2020|05|28}} the Lanes tab is only visible in the WME to [[Editing restrictions|rank 3 editors]] and lane guidance in the App is only visible to beta testers.}}<br />
{{mbox| type = caution| text = {{As of|2020|05|30}} the lane mapping feature of WME and the lane guidance feature of the mobile app are both still under development. Please check this guide frequently for updates to features and guidance.}}<br />
== Mapping guidance ==<br />
=== What counts as a lane? ===<br />
'''Q: How many lanes should you map at the end of a segment? What counts as a lane?'''<br><br />
'''A: Map any lane that achieves full and consistent width BEFORE the turn itself.''' For a freeway exit lane, this means a lane that is full width BEFORE [https://mutcd.fhwa.dot.gov/HTM/2003/part3/fig3b-08-1_longdesc.htm the gore point]. If someone travelling in the right lane can continue straight without changing lanes, then map this as a straight/turn lane. <br><br />
Consider what the road looks like to a driver - make the number of lanes in the lane guidance display conform to what the driver will see.<br />
==== Freeway exits and other ramps ====<br />
'''<big>Example 1: Not a Separate Lane</big>'''[[File:NotALane2.png|880px|The exit lane does not reach full width until the gore point; map as part of the rightmost continue-straight lane]]<br />
The exit lane does not reach full width until the gore point; map as part of the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 2: Not a Separate Lane</big>'''[[File:NotALane3.png|880px|The exit lane does not reach full width until the gore point; mapped as part of the rightmost continue-straight lane.]]<br />
The exit lane does not reach full width until the gore point; mapped as part of the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 3: Separate Lane</big>'''[[File:SeperateLane2.png|880px|When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.]]<br />
When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 4: Separate Lane</big>'''[[File:SeperateLane1.png|880px|When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.]]<br />
When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.<br />
==== Center two-way left-turn lanes ====<br />
[[File:TwoWayLeftTurnLanes.png|thumb|right|Center two-way turn lane: Separate turn lane if a left is allowed; no turn lane if left is not allowed.]]<br />
Many two-way streets have a center lane marked as a two-way left turn lane (TWLTL), also known as a ‘suicide lane’ or ‘chicken lane’. In the US, this lane is bordered on either side by two yellow lines - the inner line is broken or dashed, the outer line is solid. Pavement marking arrows may or may not be present. Where lane guidance is applied and the left turn lane is possible, these should be marked as separate left-turn lanes.<br />
==== HOV or other restricted lanes ====<br />
HOV (high-occupancy vehicle) restrictions or vehicle restrictions may sometimes only apply to a portion of the roadway. Only include these restricted lanes in lane guidance if they are available to users on the segment in question. In the example below, the bus lane allows for right turning vehicles to use the lane, so it is included in lane guidance. <br />
<gallery><br />
File:Lanes_HOVcount.png|HOV lanes that are on the same segment (not physically separated) should be included in lanes. <br />
File:Lanes_BusResticted.png|Bus, bike, or other restricted lanes should be included. In this case, right turns are allowed from the bus lane, so it is shown as a right turn lane. <br />
File:Lanes_CenterBus.png|In this case, the bus lane (red, center) is the only lane that proceeds straight ahead. It should be included, as it will be shown (though faded) to drivers when they are directed using the outside lanes to turn left or right. <br />
File:Lanes_Choices3.png|The HOV lane is clearly visible to all traffic, and would be considered by most drivers to be a lane, it should be included in the count of lanes at the segments ending at the exit.<br />
</gallery><br />
<br />
=== When to map lanes ===<br />
Generally, lanes should be mapped where there is more than one lane and only a subset of the lanes is available for turns. Also lanes should be mapped in potentially confusing locations where lane guidance can significantly improve safety and the driver experience.<br />
==== When the driver needs to choose the correct lane ====<br />
[[File:Lanes DriversChoice.png|thumb|right]] Any time there are two or more lanes AND an instruction is given at the node. In the example below, the street running east/west has only two lanes in either direction, but only one of those lanes may turn south onto the side street. Lane guidance should be added.<br clear=all><br />
==== To clarify which road to take ====<br />
Before now, Waze could not show the driver the difference between slight, 90°, and sharp turns. Without lanes, intersections with multiple right or multiple left turns could be confusing to drivers. Lane guidance can clear up this confusion by showing drivers whether to take, for example, the slight turn or the sharp turn.<br />
{{mbox | text = This situation is generally the only place where it is useful to add lanes where there is only one lane in the relevant direction of travel.}}<br />
<gallery>File:Lanes_Choices.png|example 1<br />
File:Lanes_Choices2.png|example 2</gallery><br />
==== When the driver needs reinforcement or reassurance for safety ====<br />
[[File:Lanes_Reassurance.png|thumb|right|For this freeway off-ramp onto a one-way roadway, reinforce “no left turn”; either lane is fine.]]<br />
There are some cases where lanes should be added to reassure drivers that they need not switch lanes, or that they may not turn from the lane they are in. In the example below, both lanes of the highway off-ramp must turn right — drivers have no choice. Lane guidance should be added to reassure drivers in the left lane that they need not change lanes and to reinforce the prohibition on the left turn to reduce the chance of them making a wrong-way turn.<br />
<br />
=== When not to map lanes ===<br />
==== When drivers have no choice ====<br />
[[File:Nolanessimple.png|150px|thumb|right|Suburban local streets typically don't have multiple lanes, and don't need lane guidance.]] Generally, don’t add lanes when there is only one lane, or at a node where no instruction is to be given. An exception to this general rule is at confusing intersections and interchanges where the driver needs reassurance that a lane change will not be necessary before the next turn or exit maneuver, or reinforcement that what might look like a valid turn is not allowed (see the reinforcement and reassurance example above).<br clear=all><br />
<br />
==== Merges and new lanes ====<br />
Waze does not offer lane guidance for a reduction in the number of lanes.<br />
[[File:MergeLanes.png|left|frame|Lane guidance is not appropriate for freeway lane reductions that do not occur near an interchange]]<br clear=all><br />
=== How Waze selects 'Waze Selected' lane arrows ===<br />
Waze Selected lane arrows are displayed for us both in the edit dialog (to the left of the checkboxes for each outbound segment) and in the Lanes pane (once changes are applied).{{Collapsible section top|expand=no}}<br />
''Expand for more information...''{{Collapsible section content}}<br />
The determination is mostly simple and mostly based on angles. Consider there is a pizza pie on the map. Cutting the pizza pie into 8 slices, outbound segments in the top slice (i.e., turn angles from 0° up to 22.5° either way) might show straight, slight left, or slight right depending on context; the top-left and top-right slice (i.e., turn angles from 22.5° to 67.5° either way) will show slight left or slight right arrows; the left slice and right slice (between 67.5° and 112.5°) will have regular turn left or turn right arrows; and the bottom 3 slices (between 112.5° and 180°) will have sharp left/sharp right arrows. Capische? Mamma mia.<br />
Regarding the top slice, when there is only one outbound segment within the <22.5° slice, that segment will get the “straight” arrows. However, if multiple segments exist within this slice, some form of the “best continuation” analysis is used to determine which one gets the straight arrow, and other arrows in that slice get slight left or slight right arrows. If there is no “best continuation”, then the segment that is closer to 0° gets the straight arrow, and the other one(s)]]<br />
{{Collapsible section bottom}}<br />
=== When to override lane arrows ===<br />
See [[#How Waze selects 'Waze Selected' lane arrows|How Waze selects lane arrows]] for information on the default turn arrows.<br />
<br />
Always review the lane arrows displayed in the Lanes pane carefully once you have applied your edits. Use override when it makes sense to do so, and leave the “Waze selected” setting in place otherwise. Do what makes sense to the person in the driver’s seat—choose the arrow which is going to make the most sense to the driver based on what they are going to have to do (continue straight, U turn, slight right, etc.) and what they are going to see as they approach the intersection or interchange where they need to make the maneuver.<br />
<br />
This does not necessarily mean that the lane arrows should be forced to match the instruction—for example, there are times when a "keep left" instruction is best paired with "straight" arrows, or when a "turn right" instruction is paired with a slight right arrow. The lane arrows should be set according to how a driver would perceive the lane configuration, but the audio guidance should reflect the action to be taken.<br />
<br />
When you change the arrow associated with one outgoing segment, check the remaining segments. In most situations, no two outgoing segments should use the same arrow.<br />
==== When more than one outbound segment have the same 'Waze selected' arrow ====<br />
Change one or more of them in a way that makes sense.<br />
==== Where segment geometry doesn’t match reality ====<br />
[[File:Lanes Override2.png|150px|thumb]]This happens in some locations because Waze road segment width does not match the real life road width. This can result in turn angles on the map which are somewhat different from the true turn angle. Lane arrow override may be necessary.<br clear=all><br />
<br />
==== Where the Waze selected arrow doesn't match reality ====<br />
Even in areas with very high quality maps, the Waze arrow selection mechanism can create arrow configurations which are confusing to the driver. This is particularly likely at nodes where there are multiple outbound segments essentially straight ahead (within a couple dozen degrees either way) from the inbound segment.<br />
These potentially-confusing generated arrows are most often found at ramp splits, wayfinders, and forks in the road, discussed in the section immediately below.<br />
<br />
However, these situations occur in other places as well. For example, in situations where a main road veers off in one direction, and a side road continues straight ahead, the Waze selected arrows will sometimes give straight-ahead arrows to the continuation of the main road, and a “slight turn” arrow to the straight-ahead side road. This does not make sense from a driver’s perspective. In such cases, use lane angle overrides to achieve the desired result.<br />
<br />
[[File:Jeff-sv sm.jpg|400px|frameless|left]] [[File:Jeff-sat sm.jpg|400px|frameless|right]]<br clear=all><br />
<big>In this example, the continuing road veers left, while the side road exits straight ahead. Both street level and overhead imagery clearly shows the driver's perspective and the need for adjustments.</big> <br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Waze selected arrows do not match reality.'''<br />
| style="width: 50%; text-align:center" | '''Use lane angle overrides to create reality.'''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:Jeff-no.png|300px|frameless]]<br />
| style="width: 50%; text-align:center" | [[File:Jeff-yes.png|300px|frameless]]<br />
|}<br />
<br />
==== Ramp splits, wayfinders, and forks in the road ====<br />
Sometimes the Waze selected lane arrows are the best choice and sometimes they are not. Look at both overhead and street views to consider what makes the most sense from the driver’s perspective. Given the processes by which Waze selects the “Waze selected” selection, sometimes the “Waze selected” straight-ahead arrow does not match well with the actual geometry of a junction. <br><br />
<br />
Generally, only one outbound segment (if any) should have the “straight” arrow. If both outbound segments at a split or wayfinder take you down an equally-straight or equally-not straight path (whether immediately or foreseeably ahead), then neither should use the straight arrow. If one of the outbound segments leads to a straighter path than the other, however, then that one should have the straight arrow. If this is already happening, great. If not, use lane override to make it happen (and to ensure that the other path doesn’t keep it).<br />
<br />
== Adding lanes to the map ==<br />
Before adding lane information, check both aerial and street view to make sure how many lanes there are on the segment at the node(s) where you are about to add lanes. See [[#What counts as a lane?|What counts as a lane?]] for more.<br />
{{mbox | type = warning | text = {{As of|2020|04|27}} the lanes tab shows when a segment is selected at zoom level 4 (500 ft) or closer. If you don’t see the tab, try zooming and panning until it shows. The node you are editing must also be in the window.}}<br />
=== Adding lanes to a segment ===<br />
1. Select the segment to which you would like to add lanes.<br />
2. In the left pane, click the Lanes tab.[[File:Lanes tab.png|thumb|center|300px|The lanes tab appears in the left pane]]<br />
3. For two-way segments, ensure you are editing the correct end of the segment. The “B” end (for A-to-B traffic) will show first, followed by the “A” end (for B-to-A traffic). The text at the top of each ‘end’ will describe the directionality of the lanes below. [[File:Lanes tab2.png|300px|thumb|center|For two-way segments, there is a section for each direction of lanes]]<br />
4. Click "Add lane guidance". [[File:Lanes_AddLaneGuidance.png|300px|thumb|center|For two-way segments, there is a section for each direction of lanes]]<br />
5. Enter the number of lanes (NOT the number of possible directions). Use the number of lanes that connect to the next segment, even if there are a different number of lanes at some other point on the segment. See the [[#What counts as a lane?|What counts as a lane?]] section above for more information.[[File:Lanes_NumberOf.png|300px|thumb|center|Count the numbers of lanes at the end of the segment.]]<br />
6. Use the checkboxes to assign the available lanes for each outbound movement. Confirm using street-level imagery, where available. Note that the same lane may be used for more than one movement (e.g., the right lane may be used for both continuing and right-turning traffic).[[File:Lanes_Checkbox1.png|300px|thumb|left|Each lane is dedicated to a specific movement.]][[File:Lanes_Checkbox2.png|300px|thumb|right|The right lane is shared for continuing and turning traffic.]]<br clear=all><br />
7. Click Apply, then save your changes when you are ready. Changes will go live in the app after the next map tile update. <br />
{{mbox|text=Mousing-over the turn arrow in the lanes panel will<br><br />
highlight that turn arrow on the map.|imageright=[[File:WME_LG_Arrow_Highlight.png|thumb|100px]]}}<br />
<br />
=== Editing existing lanes ===<br />
Editing existing Lane Guidance for a segment is done similarly to adding the lanes for the first time:<br><br />
1. Select the segment.<br><br />
2. In the left pane, click the Lanes tab.<br><br />
3. Click "Edit lane guidance" to bring up the Lane Guidance editing console.<br>[[File:EditLaneGuidance.png|300px|thumb|center|Click 'Edit lane guidance']]<br clear=all><br />
<br />
=== Lane errors ===<br />
[[File:Lanes error.png|150px|thumb|right]] If lane data is incomplete, or has been corrupted due to edits on connected segments, then an error alert symbol will appear on the affected segment and on the Lanes tab when the segment is selected.<br clear=all><br />
=== Overriding a turn angle {{Anchor|Overriding a turn angle|Turn angle override|TAO}} === <br />
[[File:Lanes Override3.png|100px|thumb|right|Turn angle override controls]] In some cases, the displayed turn angle may need to be adjusted. Rather than adjusting the geometry of the road segments, an override function is available in the Lanes tab. <br />
# Select the segment.<br />
# In the left pane, click the Lanes tab.<br />
# Click “Edit lane guidance”.<br />
# Click the given turn angle icon under the TURNS header to open the Override turn angle menu. <br />
# Select a new turn angle, or the ‘Waze selected’ angle. <br clear=all><br />
<br />
=== Junction Boxes ===<br />
Lane information can be added to segments which are part of a [[Junction Box]] just as they can be added to any other segment. In order for lane guidance to work, all turn arrows on the segments underlying a Junction Box must be green (unrestricted) '''if''' they are on a route allowed by the overlaid Junction Box. Use the Junction Box itself to restrict any necessary routes.<br />
{{mbox | type = warning | text = If a junction box uses a [[turn instruction override]] to override the Waze-selected turn instructions along one of the junction box routes, then the underlying lane data may not be displayed in the app.}}<br />
<br />
=== Lanes on divided roadways {{Anchor|Lanes on divided roadways|'H' and '#' intersections}} ===<br />
At intersections where one or both roads are divided, lanes cannot always be added directly.<br><br />
<br />
Many such intersections can be classified as either “H” intersections (where only one road is divided) or “#” intersections (where both roads are divided).<br><br />
{{mbox|text=On the divided roadway approaches to an “H” intersection, lanes can be added directly to the segments.}}<br />
For some “#” intersections, and on the undivided roadway approaches to some “H” intersections, Waze can combine lane guidance information from more than one segment into a single set of lanes that includes both left and right turns, as the driver expects. {{Anchor|divided roadway criteria}} This will only be possible if all of these conditions are met:<br />
# Both left and right turns are possible at the intersection;<br />
# The two portions of the divided roadway are essentially parallel to each other;<br />
# The two intersecting roads are more or less perpendicular to each other;<br />
# The median segment in question is 50 m or shorter; and<br />
# The number of lanes entering the intersection is equal to the total number of lanes exiting the intersection (total number of lanes exiting intersection = number of lanes on the median segment + number of right-turn only lanes on the entry segment—in other words, no new lanes are added in the median).<br />
If these conditions are met, then follow the guidance in the [[#Mapping lanes on divided roadways|next section]] to add lane information.<br />
{{mbox|text=The purpose of the heuristics is to combine left turn, straight, and right turn arrows into a single lane set. At intersections where either left turns or right turns are disallowed, lanes can be added directly, and heuristics are not needed—in other words, there is no need to add “straight only” lane information. In the example below, right-turning traffic will get the full set of lanes from the entry segment; adding lanes to the median segment would serve no purpose. <br><br />
[[File:LanesMedianNA1.png|frameless|300px]] [[File:LanesMedianNA2.png|frameless|300px]]<br />
}}<br />
{{mbox<br />
| type = important<br />
| text = One side effect of the H/# heuristics is that in many cases the server will identify 'turn left, then turn left' movements across a H/# intersection (when they are not prohibited by [[Junction_Style_Guide/Intersections#Avoiding_U_turns|the U-turn prevention algorithm]]) as a U-turn, and display the U-turn lane guidance arrow in the app. In addition to the visual display of the U-turn arrow, the app's voice turn-by-turn instructions will vocalize the movement as a u-turn. <br />
}}<br />
==== Mapping lanes on divided roadways ====<br />
===== Hash intersections =====<br />
[[File:Median-entry.jpg|300px|thumb|right|Entry and Median Segments (for each direction of travel)]]<br />
First, make sure that the intersection and the turn you are mapping for meet the [[#divided roadway criteria|guidelines above]]. Handle one direction of travel at a time.<br><br />
<br />
For each direction of travel, lanes must be mapped on two segments: the “entry segment” (immediately before the median) and the “median segment” (within the median). ''See the adjacent figure. ''<br />
# On the entry segment, include the total number of lanes entering the intersection.<br />
## Any lane that can be used to either turn left or continue straight should be mapped as a continuing straight lane.<br />
## Any right turn lanes should be mapped as usual.<br />
# On the median segment, include the total number of lanes which actually exist in the median. The number of lanes on the median segment should equal the number of lanes that can continue straight from the entry segment.<br clear=all><br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Entry segment: '''<br />
| style="width: 50%; text-align:center" | '''Median segment: '''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:Lanes_entry.png|350px|frameless]]<br />
| style="width: 50%; text-align:center" | [[File:Lanes_median.png|350px|frameless]]<br />
|}<br />
The heuristic in the routing server will combine these two sets of lanes together and provide a single set for drivers making either left or right turns. Unfortunately, there is no way to visualize the result in WME.<br><br />
<br />
'''<big>Lanes resulting from heuristics:</big>'''<br />
[[File:Lanes result.png|224px|frameless|left]]<br clear=all><br />
<br />
===== H Intersections =====<br />
The same heuristic applies to the undivided road side of an H junction. No heuristic is necessary for the divided road side.<br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Undivided road side:'''<br />
| style="width: 50%; text-align:center" | '''Divided road side:'''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:LanesH1.png|350px|frameless]]<br />
| rowspan="2" style="width: 50%; text-align:center" | [[File:LanesH3.png|350px|frameless]]<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:LanesH2resubmit.png|350px|frameless]]<br />
| style="width: 50%; text-align:center" | <br />
|}<br />
{{mbox|text=The median segments of # and H junctions are a rare instance where, on occasion, it is proper to add “1 lane” to a segment. This will be necessary any time there are multiple lanes on the entry segment but only one lane remaining on the median segment (because any other lane was right turn only).<br><br />
[[File:LanesHBox1resubmit.png|frameless|300px]] [[File:LanesHBox2.png|frameless|300px]]<br />
}}<br />
===== Checking your work =====<br />
There are a few things you can do to double-check your work on divided-roadway intersections that need to be mapped with heuristics.<br />
# The total number of lanes on the entry segment should equal the total number of lanes at the intersection:<br />
#* total lanes (intersection) = total lanes (entry)<br />
# The total number of lanes on the median segment should equal the difference between the total number of lanes on the entry segment and the number of right-turn only lanes on the entry segment:<br />
#* total lanes (median) = total lanes (entry) – right turn only lanes (entry)<br />
# The number of straight-ahead lanes on the entry segment (i.e., the number of boxes checked for the straight-ahead movement) should equal the total number of lanes on the median segment:<br />
#* straight-ahead lanes (entry) = total lanes (median)<br />
If these conditions are not met, the heuristic method may not function as expected, and it is best to leave lanes off for the time being.</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=Lanes&diff=172700Lanes2020-05-30T23:10:03Z<p>Tonestertm: /* Lanes on divided roadways {{Anchor|Lanes on divided roadways|'H' and '#' intersections}} */</p>
<hr />
<div>{{construction | contact = https://www.waze.com/forum/viewtopic.php?f=1636&t=301141 | contacttype = forum | draft = no | open = no | revision = no | section = no | talk = no}}<br />
Lane guidance is a new Waze app feature that shows the user exactly which lanes they should use to make their next movement. This feature boosts Wazer confidence by providing reassurance in junctions both typical and unusual. <br />
Lane guidance data is added via the [[Waze Map Editor|Waze Map Editor (WME)]]. When a single segment is selected in the WME, an additional tab called Lanes is available in the left pane. The Lanes tab allows map editors to tell Waze which lane to display to the driver for lane guidance in the mobile app. <br><br />
<br />
There are some important considerations regarding lane guidance in Waze:<br />
* '''Lane guidance does not affect routing''' - it is merely a visual feature.<br />
* '''Lane guidance does not affect audio instructions''', with the exception of u-turn instructions resulting from [[#Lanes_on_divided_roadways|heuristics for intersections on divided roads]].<br />
* '''Lane guidance will only be displayed when a navigation instruction is given.''' If the [[How_Waze_determines_turn_/_keep_/_exit_maneuvers#Best_Continuation|best continuation]] is straight ahead, lane guidance will not be shown, unless there is a [[Turn_instruction_override|continue straight TIO]].<br />
{{mbox | type = protection | text = {{As of|2020|05|28}} the Lanes tab is only visible in the WME to [[Editing restrictions|rank 3 editors]] and lane guidance in the App is only visible to beta testers.}}<br />
{{mbox| type = caution| text = {{As of|2020|05|30}} the lane mapping feature of WME and the lane guidance feature of the mobile app are both still under development. Please check this guide frequently for updates to features and guidance.}}<br />
== Mapping guidance ==<br />
=== What counts as a lane? ===<br />
'''Q: How many lanes should you map at the end of a segment? What counts as a lane?'''<br><br />
'''A: Map any lane that achieves full and consistent width BEFORE the turn itself.''' For a freeway exit lane, this means a lane that is full width BEFORE [https://mutcd.fhwa.dot.gov/HTM/2003/part3/fig3b-08-1_longdesc.htm the gore point]. If someone travelling in the right lane can continue straight without changing lanes, then map this as a straight/turn lane. <br><br />
Consider what the road looks like to a driver - make the number of lanes in the lane guidance display conform to what the driver will see.<br />
==== Freeway exits and other ramps ====<br />
'''<big>Example 1: Not a Separate Lane</big>'''[[File:NotALane2.png|880px|The exit lane does not reach full width until the gore point; map as part of the rightmost continue-straight lane]]<br />
The exit lane does not reach full width until the gore point; map as part of the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 2: Not a Separate Lane</big>'''[[File:NotALane3.png|880px|The exit lane does not reach full width until the gore point; mapped as part of the rightmost continue-straight lane.]]<br />
The exit lane does not reach full width until the gore point; mapped as part of the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 3: Separate Lane</big>'''[[File:SeperateLane2.png|880px|When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.]]<br />
When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 4: Separate Lane</big>'''[[File:SeperateLane1.png|880px|When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.]]<br />
When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.<br />
==== Center two-way left-turn lanes ====<br />
[[File:TwoWayLeftTurnLanes.png|thumb|right|Center two-way turn lane: Separate turn lane if a left is allowed; no turn lane if left is not allowed.]]<br />
Many two-way streets have a center lane marked as a two-way left turn lane (TWLTL), also known as a ‘suicide lane’ or ‘chicken lane’. In the US, this lane is bordered on either side by two yellow lines - the inner line is broken or dashed, the outer line is solid. Pavement marking arrows may or may not be present. Where lane guidance is applied and the left turn lane is possible, these should be marked as separate left-turn lanes.<br />
==== HOV or other restricted lanes ====<br />
HOV (high-occupancy vehicle) restrictions or vehicle restrictions may sometimes only apply to a portion of the roadway. Only include these restricted lanes in lane guidance if they are available to users on the segment in question. In the example below, the bus lane allows for right turning vehicles to use the lane, so it is included in lane guidance. <br />
<gallery><br />
File:Lanes_HOVcount.png|HOV lanes that are on the same segment (not physically separated) should be included in lanes. <br />
File:Lanes_BusResticted.png|Bus, bike, or other restricted lanes should be included. In this case, right turns are allowed from the bus lane, so it is shown as a right turn lane. <br />
File:Lanes_CenterBus.png|In this case, the bus lane (red, center) is the only lane that proceeds straight ahead. It should be included, as it will be shown (though faded) to drivers when they are directed using the outside lanes to turn left or right. <br />
File:Lanes_Choices3.png|The HOV lane is clearly visible to all traffic, and would be considered by most drivers to be a lane, it should be included in the count of lanes at the segments ending at the exit.<br />
</gallery><br />
<br />
=== When to map lanes ===<br />
Generally, lanes should be mapped where there is more than one lane and only a subset of the lanes is available for turns. Also lanes should be mapped in potentially confusing locations where lane guidance can significantly improve safety and the driver experience.<br />
==== When the driver needs to choose the correct lane ====<br />
[[File:Lanes DriversChoice.png|thumb|right]] Any time there are two or more lanes AND an instruction is given at the node. In the example below, the street running east/west has only two lanes in either direction, but only one of those lanes may turn south onto the side street. Lane guidance should be added.<br clear=all><br />
==== To clarify which road to take ====<br />
Before now, Waze could not show the driver the difference between slight, 90°, and sharp turns. Without lanes, intersections with multiple right or multiple left turns could be confusing to drivers. Lane guidance can clear up this confusion by showing drivers whether to take, for example, the slight turn or the sharp turn.<br />
{{mbox | text = This situation is generally the only place where it is useful to add lanes where there is only one lane in the relevant direction of travel.}}<br />
<gallery>File:Lanes_Choices.png|example 1<br />
File:Lanes_Choices2.png|example 2</gallery><br />
==== When the driver needs reinforcement or reassurance for safety ====<br />
[[File:Lanes_Reassurance.png|thumb|right|For this freeway off-ramp onto a one-way roadway, reinforce “no left turn”; either lane is fine.]]<br />
There are some cases where lanes should be added to reassure drivers that they need not switch lanes, or that they may not turn from the lane they are in. In the example below, both lanes of the highway off-ramp must turn right — drivers have no choice. Lane guidance should be added to reassure drivers in the left lane that they need not change lanes and to reinforce the prohibition on the left turn to reduce the chance of them making a wrong-way turn.<br />
<br />
=== When not to map lanes ===<br />
==== When drivers have no choice ====<br />
[[File:Nolanessimple.png|150px|thumb|right|Suburban local streets typically don't have multiple lanes, and don't need lane guidance.]] Generally, don’t add lanes when there is only one lane, or at a node where no instruction is to be given. An exception to this general rule is at confusing intersections and interchanges where the driver needs reassurance that a lane change will not be necessary before the next turn or exit maneuver, or reinforcement that what might look like a valid turn is not allowed (see the reinforcement and reassurance example above).<br clear=all><br />
<br />
==== Merges and new lanes ====<br />
Waze does not offer lane guidance for a reduction in the number of lanes.<br />
[[File:MergeLanes.png|left|frame|Lane guidance is not appropriate for freeway lane reductions that do not occur near an interchange]]<br clear=all><br />
=== How Waze selects 'Waze Selected' lane arrows ===<br />
Waze Selected lane arrows are displayed for us both in the edit dialog (to the left of the checkboxes for each outbound segment) and in the Lanes pane (once changes are applied).{{Collapsible section top|expand=no}}<br />
''Expand for more information...''{{Collapsible section content}}<br />
The determination is mostly simple and mostly based on angles. Consider there is a pizza pie on the map. Cutting the pizza pie into 8 slices, outbound segments in the top slice (i.e., turn angles from 0° up to 22.5° either way) might show straight, slight left, or slight right depending on context; the top-left and top-right slice (i.e., turn angles from 22.5° to 67.5° either way) will show slight left or slight right arrows; the left slice and right slice (between 67.5° and 112.5°) will have regular turn left or turn right arrows; and the bottom 3 slices (between 112.5° and 180°) will have sharp left/sharp right arrows. Capische? Mamma mia.<br />
Regarding the top slice, when there is only one outbound segment within the <22.5° slice, that segment will get the “straight” arrows. However, if multiple segments exist within this slice, some form of the “best continuation” analysis is used to determine which one gets the straight arrow, and other arrows in that slice get slight left or slight right arrows. If there is no “best continuation”, then the segment that is closer to 0° gets the straight arrow, and the other one(s)]]<br />
{{Collapsible section bottom}}<br />
=== When to override lane arrows ===<br />
See [[#How Waze selects 'Waze Selected' lane arrows|How Waze selects lane arrows]] for information on the default turn arrows.<br />
<br />
Always review the lane arrows displayed in the Lanes pane carefully once you have applied your edits. Use override when it makes sense to do so, and leave the “Waze selected” setting in place otherwise. Do what makes sense to the person in the driver’s seat—choose the arrow which is going to make the most sense to the driver based on what they are going to have to do (continue straight, U turn, slight right, etc.) and what they are going to see as they approach the intersection or interchange where they need to make the maneuver.<br />
<br />
This does not necessarily mean that the lane arrows should be forced to match the instruction—for example, there are times when a "keep left" instruction is best paired with "straight" arrows, or when a "turn right" instruction is paired with a slight right arrow. The lane arrows should be set according to how a driver would perceive the lane configuration, but the audio guidance should reflect the action to be taken.<br />
<br />
When you change the arrow associated with one outgoing segment, check the remaining segments. In most situations, no two outgoing segments should use the same arrow.<br />
==== When more than one outbound segment have the same 'Waze selected' arrow ====<br />
Change one or more of them in a way that makes sense.<br />
==== Where segment geometry doesn’t match reality ====<br />
[[File:Lanes Override2.png|150px|thumb]]This happens in some locations because Waze road segment width does not match the real life road width. This can result in turn angles on the map which are somewhat different from the true turn angle. Lane arrow override may be necessary.<br clear=all><br />
<br />
==== Where the Waze selected arrow doesn't match reality ====<br />
Even in areas with very high quality maps, the Waze arrow selection mechanism can create arrow configurations which are confusing to the driver. This is particularly likely at nodes where there are multiple outbound segments essentially straight ahead (within a couple dozen degrees either way) from the inbound segment.<br />
These potentially-confusing generated arrows are most often found at ramp splits, wayfinders, and forks in the road, discussed in the section immediately below.<br />
<br />
However, these situations occur in other places as well. For example, in situations where a main road veers off in one direction, and a side road continues straight ahead, the Waze selected arrows will sometimes give straight-ahead arrows to the continuation of the main road, and a “slight turn” arrow to the straight-ahead side road. This does not make sense from a driver’s perspective. In such cases, use lane angle overrides to achieve the desired result.<br />
<br />
[[File:Jeff-sv sm.jpg|400px|frameless|left]] [[File:Jeff-sat sm.jpg|400px|frameless|right]]<br clear=all><br />
<big>In this example, the continuing road veers left, while the side road exits straight ahead. Both street level and overhead imagery clearly shows the driver's perspective and the need for adjustments.</big> <br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Waze selected arrows do not match reality.'''<br />
| style="width: 50%; text-align:center" | '''Use lane angle overrides to create reality.'''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:Jeff-no.png|300px|frameless]]<br />
| style="width: 50%; text-align:center" | [[File:Jeff-yes.png|300px|frameless]]<br />
|}<br />
<br />
==== Ramp splits, wayfinders, and forks in the road ====<br />
Sometimes the Waze selected lane arrows are the best choice and sometimes they are not. Look at both overhead and street views to consider what makes the most sense from the driver’s perspective. Given the processes by which Waze selects the “Waze selected” selection, sometimes the “Waze selected” straight-ahead arrow does not match well with the actual geometry of a junction. <br><br />
<br />
Generally, only one outbound segment (if any) should have the “straight” arrow. If both outbound segments at a split or wayfinder take you down an equally-straight or equally-not straight path (whether immediately or foreseeably ahead), then neither should use the straight arrow. If one of the outbound segments leads to a straighter path than the other, however, then that one should have the straight arrow. If this is already happening, great. If not, use lane override to make it happen (and to ensure that the other path doesn’t keep it).<br />
<br />
== Adding lanes to the map ==<br />
Before adding lane information, check both aerial and street view to make sure how many lanes there are on the segment at the node(s) where you are about to add lanes. See [[#What counts as a lane?|What counts as a lane?]] for more.<br />
{{mbox | type = warning | text = {{As of|2020|04|27}} the lanes tab shows when a segment is selected at zoom level 4 (500 ft) or closer. If you don’t see the tab, try zooming and panning until it shows. The node you are editing must also be in the window.}}<br />
=== Adding lanes to a segment ===<br />
1. Select the segment to which you would like to add lanes.<br />
2. In the left pane, click the Lanes tab.[[File:Lanes tab.png|thumb|center|300px|The lanes tab appears in the left pane]]<br />
3. For two-way segments, ensure you are editing the correct end of the segment. The “B” end (for A-to-B traffic) will show first, followed by the “A” end (for B-to-A traffic). The text at the top of each ‘end’ will describe the directionality of the lanes below. [[File:Lanes tab2.png|300px|thumb|center|For two-way segments, there is a section for each direction of lanes]]<br />
4. Click "Add lane guidance". [[File:Lanes_AddLaneGuidance.png|300px|thumb|center|For two-way segments, there is a section for each direction of lanes]]<br />
5. Enter the number of lanes (NOT the number of possible directions). Use the number of lanes that connect to the next segment, even if there are a different number of lanes at some other point on the segment. See the [[#What counts as a lane?|What counts as a lane?]] section above for more information.[[File:Lanes_NumberOf.png|300px|thumb|center|Count the numbers of lanes at the end of the segment.]]<br />
6. Use the checkboxes to assign the available lanes for each outbound movement. Confirm using street-level imagery, where available. Note that the same lane may be used for more than one movement (e.g., the right lane may be used for both continuing and right-turning traffic).[[File:Lanes_Checkbox1.png|300px|thumb|left|Each lane is dedicated to a specific movement.]][[File:Lanes_Checkbox2.png|300px|thumb|right|The right lane is shared for continuing and turning traffic.]]<br clear=all><br />
7. Click Apply, then save your changes when you are ready. Changes will go live in the app after the next map tile update. <br />
{{mbox|text=Mousing-over the turn arrow in the lanes panel will<br><br />
highlight that turn arrow on the map.|imageright=[[File:WME_LG_Arrow_Highlight.png|thumb|100px]]}}<br />
<br />
=== Editing existing lanes ===<br />
Editing existing Lane Guidance for a segment is done similarly to adding the lanes for the first time:<br><br />
1. Select the segment.<br><br />
2. In the left pane, click the Lanes tab.<br><br />
3. Click "Edit lane guidance" to bring up the Lane Guidance editing console.<br>[[File:EditLaneGuidance.png|300px|thumb|center|Click 'Edit lane guidance']]<br clear=all><br />
<br />
=== Lane errors ===<br />
[[File:Lanes error.png|150px|thumb|right]] If lane data is incomplete, or has been corrupted due to edits on connected segments, then an error alert symbol will appear on the affected segment and on the Lanes tab when the segment is selected.<br clear=all><br />
=== Overriding a turn angle {{Anchor|Overriding a turn angle|Turn angle override|TAO}} === <br />
[[File:Lanes Override3.png|100px|thumb|right|Turn angle override controls]] In some cases, the displayed turn angle may need to be adjusted. Rather than adjusting the geometry of the road segments, an override function is available in the Lanes tab. <br />
# Select the segment.<br />
# In the left pane, click the Lanes tab.<br />
# Click “Edit lane guidance”.<br />
# Click the given turn angle icon under the TURNS header to open the Override turn angle menu. <br />
# Select a new turn angle, or the ‘Waze selected’ angle. <br clear=all><br />
<br />
=== Junction Boxes ===<br />
Lane information can be added to segments which are part of a [[Junction Box]] just as they can be added to any other segment. In order for lane guidance to work, all turn arrows on the segments underlying a Junction Box must be green (unrestricted) '''if''' they are on a route allowed by the overlaid Junction Box. Use the Junction Box itself to restrict any necessary routes.<br />
{{mbox | type = warning | text = If a junction box uses a [[turn instruction override]] to override the Waze-selected turn instructions along one of the junction box routes, then the underlying lane data may not be displayed in the app.}}<br />
<br />
=== Lanes on divided roadways {{Anchor|Lanes on divided roadways|'H' and '#' intersections}} ===<br />
At intersections where one or both roads are divided, lanes cannot always be added directly.<br><br />
<br />
Many such intersections can be classified as either “H” intersections (where only one road is divided) or “#” intersections (where both roads are divided).<br><br />
{{mbox|text=On the divided roadway approaches to an “H” intersection, lanes can be added directly to the segments.}}<br />
For some “#” intersections, and on the undivided roadway approaches to some “H” intersections, Waze can combine lane guidance information from more than one segment into a single set of lanes that includes both left and right turns, as the driver expects. {{Anchor|divided roadway criteria}} This will only be possible if all of these conditions are met:<br />
# Both left and right turns are possible at the intersection;<br />
# The two portions of the divided roadway are essentially parallel to each other;<br />
# The two intersecting roads are more or less perpendicular to each other;<br />
# The median segment in question is 50 m or shorter; and<br />
# The number of lanes entering the intersection is equal to the total number of lanes exiting the intersection (total number of lanes exiting intersection = number of lanes on the median segment + number of right-turn only lanes on the entry segment—in other words, no new lanes are added in the median).<br />
If these conditions are met, then follow the guidance in the [[#Mapping lanes on divided roadways|next section]] to add lane information.<br />
{{mbox|text=The purpose of the heuristics is to combine left turn, straight, and right turn arrows into a single lane set. At intersections where either left turns or right turns are disallowed, lanes can be added directly, and heuristics are not needed—in other words, there is no need to add “straight only” lane information. In the example below, right-turning traffic will get the full set of lanes from the entry segment; adding lanes to the median segment would serve no purpose. <br><br />
[[File:LanesMedianNA1.png|frameless|300px]] [[File:LanesMedianNA2.png|frameless|300px]]<br />
}}<br />
{{mbox<br />
| type = important<br />
| text = One side effect of the H/# heuristics is that in many cases the server will identify 'turn left, then turn left' movements across a H/# intersection (when they are not prohibited by [[Junction_Style_Guide/Intersections#Avoiding_U_turns|the U-turn prevention algorithm]]) as a U-turn, and display the U-turn lane guidance arrow in the app. In addition to the visual display of the U-turn arrow, the app's voice turn-by-turn instructions will vocalize the movement as a u-turn. <br />
}}<br />
==== Mapping lanes on divided roadways ====<br />
===== Hash intersections =====<br />
[[File:Median-entry.jpg|300px|thumb|right|Entry and Median Segments (for each direction of travel)]]<br />
First, make sure that the intersection and the turn you are mapping for meet the [[#divided roadway criteria|guidelines above]]. Handle one direction of travel at a time.<br><br />
<br />
For each direction of travel, lanes must be mapped on two segments: the “entry segment” (immediately before the median) and the “median segment” (within the median). ''See the adjacent figure. ''<br />
# On the entry segment, include the total number of lanes entering the segment.<br />
## Any lane that can be used to either turn left or continue straight should be mapped as a continuing straight lane.<br />
## Right turn lanes should be mapped as normal.<br />
# On the median segment, include the total number of lanes on the median segment (which should equal the number of lanes on the entry segment minus the number of right turn only lanes).<br clear=all><br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Entry segment: '''<br />
| style="width: 50%; text-align:center" | '''Median segment: '''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:Lanes_entry.png|350px|frameless]]<br />
| style="width: 50%; text-align:center" | [[File:Lanes_median.png|350px|frameless]]<br />
|}<br />
The heuristic in the routing server will combine these two sets of lanes together and provide a single set for drivers making either left or right turns. Unfortunately, there is no way to visualize the result in WME.<br><br />
<br />
'''<big>Lanes resulting from heuristics:</big>'''<br />
[[File:Lanes result.png|224px|frameless|left]]<br clear=all><br />
===== H Intersections =====<br />
The same heuristic applies to the undivided road side of an H junction. No heuristic is necessary for the divided road side.<br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Undivided road side:'''<br />
| style="width: 50%; text-align:center" | '''Divided road side:'''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:LanesH1.png|350px|frameless]]<br />
| rowspan="2" style="width: 50%; text-align:center" | [[File:LanesH3.png|350px|frameless]]<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:LanesH2resubmit.png|350px|frameless]]<br />
| style="width: 50%; text-align:center" | <br />
|}<br />
{{mbox|text=The median segments of # and H junctions are a rare instance where, on occasion, it is proper to add “1 lane” to a segment. This will be necessary any time there are multiple lanes on the entry segment but only one lane remaining on the median segment (because any other lane was right turn only).<br><br />
[[File:LanesHBox1resubmit.png|frameless|300px]] [[File:LanesHBox2.png|frameless|300px]]<br />
}}<br />
===== Checking your work =====<br />
There are a few things you can do to double-check your work on divided-roadway intersections that need to be mapped with heuristics.<br />
# The total number of lanes on the entry segment should equal the total number of lanes at the intersection:<br />
#* total lanes (intersection) = total lanes (entry)<br />
# The total number of lanes on the median segment should equal the difference between the total number of lanes on the entry segment and the number of right-turn only lanes on the entry segment:<br />
#* total lanes (median) = total lanes (entry) – right turn only lanes (entry)<br />
# The number of straight-ahead lanes on the entry segment (i.e., the number of boxes checked for the straight-ahead movement) should equal the total number of lanes on the median segment:<br />
#* straight-ahead lanes (entry) = total lanes (median)<br />
If these conditions are not met, the heuristic method may not function as expected, and it is best to leave lanes off for the time being.</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=Lanes&diff=172699Lanes2020-05-30T22:38:10Z<p>Tonestertm: /* Overriding a turn angle {{Anchor|Overriding a turn angle|Turn angle override|TAO}} */ Click -> Select</p>
<hr />
<div>{{construction | contact = https://www.waze.com/forum/viewtopic.php?f=1636&t=301141 | contacttype = forum | draft = no | open = no | revision = no | section = no | talk = no}}<br />
Lane guidance is a new Waze app feature that shows the user exactly which lanes they should use to make their next movement. This feature boosts Wazer confidence by providing reassurance in junctions both typical and unusual. <br />
Lane guidance data is added via the [[Waze Map Editor|Waze Map Editor (WME)]]. When a single segment is selected in the WME, an additional tab called Lanes is available in the left pane. The Lanes tab allows map editors to tell Waze which lane to display to the driver for lane guidance in the mobile app. <br><br />
<br />
There are some important considerations regarding lane guidance in Waze:<br />
* '''Lane guidance does not affect routing''' - it is merely a visual feature.<br />
* '''Lane guidance does not affect audio instructions''', with the exception of u-turn instructions resulting from [[#Lanes_on_divided_roadways|heuristics for intersections on divided roads]].<br />
* '''Lane guidance will only be displayed when a navigation instruction is given.''' If the [[How_Waze_determines_turn_/_keep_/_exit_maneuvers#Best_Continuation|best continuation]] is straight ahead, lane guidance will not be shown, unless there is a [[Turn_instruction_override|continue straight TIO]].<br />
{{mbox | type = protection | text = {{As of|2020|05|28}} the Lanes tab is only visible in the WME to [[Editing restrictions|rank 3 editors]] and lane guidance in the App is only visible to beta testers.}}<br />
{{mbox| type = caution| text = {{As of|2020|05|30}} the lane mapping feature of WME and the lane guidance feature of the mobile app are both still under development. Please check this guide frequently for updates to features and guidance.}}<br />
== Mapping guidance ==<br />
=== What counts as a lane? ===<br />
'''Q: How many lanes should you map at the end of a segment? What counts as a lane?'''<br><br />
'''A: Map any lane that achieves full and consistent width BEFORE the turn itself.''' For a freeway exit lane, this means a lane that is full width BEFORE [https://mutcd.fhwa.dot.gov/HTM/2003/part3/fig3b-08-1_longdesc.htm the gore point]. If someone travelling in the right lane can continue straight without changing lanes, then map this as a straight/turn lane. <br><br />
Consider what the road looks like to a driver - make the number of lanes in the lane guidance display conform to what the driver will see.<br />
==== Freeway exits and other ramps ====<br />
'''<big>Example 1: Not a Separate Lane</big>'''[[File:NotALane2.png|880px|The exit lane does not reach full width until the gore point; map as part of the rightmost continue-straight lane]]<br />
The exit lane does not reach full width until the gore point; map as part of the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 2: Not a Separate Lane</big>'''[[File:NotALane3.png|880px|The exit lane does not reach full width until the gore point; mapped as part of the rightmost continue-straight lane.]]<br />
The exit lane does not reach full width until the gore point; mapped as part of the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 3: Separate Lane</big>'''[[File:SeperateLane2.png|880px|When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.]]<br />
When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 4: Separate Lane</big>'''[[File:SeperateLane1.png|880px|When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.]]<br />
When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.<br />
==== Center two-way left-turn lanes ====<br />
[[File:TwoWayLeftTurnLanes.png|thumb|right|Center two-way turn lane: Separate turn lane if a left is allowed; no turn lane if left is not allowed.]]<br />
Many two-way streets have a center lane marked as a two-way left turn lane (TWLTL), also known as a ‘suicide lane’ or ‘chicken lane’. In the US, this lane is bordered on either side by two yellow lines - the inner line is broken or dashed, the outer line is solid. Pavement marking arrows may or may not be present. Where lane guidance is applied and the left turn lane is possible, these should be marked as separate left-turn lanes.<br />
==== HOV or other restricted lanes ====<br />
HOV (high-occupancy vehicle) restrictions or vehicle restrictions may sometimes only apply to a portion of the roadway. Only include these restricted lanes in lane guidance if they are available to users on the segment in question. In the example below, the bus lane allows for right turning vehicles to use the lane, so it is included in lane guidance. <br />
<gallery><br />
File:Lanes_HOVcount.png|HOV lanes that are on the same segment (not physically separated) should be included in lanes. <br />
File:Lanes_BusResticted.png|Bus, bike, or other restricted lanes should be included. In this case, right turns are allowed from the bus lane, so it is shown as a right turn lane. <br />
File:Lanes_CenterBus.png|In this case, the bus lane (red, center) is the only lane that proceeds straight ahead. It should be included, as it will be shown (though faded) to drivers when they are directed using the outside lanes to turn left or right. <br />
File:Lanes_Choices3.png|The HOV lane is clearly visible to all traffic, and would be considered by most drivers to be a lane, it should be included in the count of lanes at the segments ending at the exit.<br />
</gallery><br />
<br />
=== When to map lanes ===<br />
Generally, lanes should be mapped where there is more than one lane and only a subset of the lanes is available for turns. Also lanes should be mapped in potentially confusing locations where lane guidance can significantly improve safety and the driver experience.<br />
==== When the driver needs to choose the correct lane ====<br />
[[File:Lanes DriversChoice.png|thumb|right]] Any time there are two or more lanes AND an instruction is given at the node. In the example below, the street running east/west has only two lanes in either direction, but only one of those lanes may turn south onto the side street. Lane guidance should be added.<br clear=all><br />
==== To clarify which road to take ====<br />
Before now, Waze could not show the driver the difference between slight, 90°, and sharp turns. Without lanes, intersections with multiple right or multiple left turns could be confusing to drivers. Lane guidance can clear up this confusion by showing drivers whether to take, for example, the slight turn or the sharp turn.<br />
{{mbox | text = This situation is generally the only place where it is useful to add lanes where there is only one lane in the relevant direction of travel.}}<br />
<gallery>File:Lanes_Choices.png|example 1<br />
File:Lanes_Choices2.png|example 2</gallery><br />
==== When the driver needs reinforcement or reassurance for safety ====<br />
[[File:Lanes_Reassurance.png|thumb|right|For this freeway off-ramp onto a one-way roadway, reinforce “no left turn”; either lane is fine.]]<br />
There are some cases where lanes should be added to reassure drivers that they need not switch lanes, or that they may not turn from the lane they are in. In the example below, both lanes of the highway off-ramp must turn right — drivers have no choice. Lane guidance should be added to reassure drivers in the left lane that they need not change lanes and to reinforce the prohibition on the left turn to reduce the chance of them making a wrong-way turn.<br />
<br />
=== When not to map lanes ===<br />
==== When drivers have no choice ====<br />
[[File:Nolanessimple.png|150px|thumb|right|Suburban local streets typically don't have multiple lanes, and don't need lane guidance.]] Generally, don’t add lanes when there is only one lane, or at a node where no instruction is to be given. An exception to this general rule is at confusing intersections and interchanges where the driver needs reassurance that a lane change will not be necessary before the next turn or exit maneuver, or reinforcement that what might look like a valid turn is not allowed (see the reinforcement and reassurance example above).<br clear=all><br />
<br />
==== Merges and new lanes ====<br />
Waze does not offer lane guidance for a reduction in the number of lanes.<br />
[[File:MergeLanes.png|left|frame|Lane guidance is not appropriate for freeway lane reductions that do not occur near an interchange]]<br clear=all><br />
=== How Waze selects 'Waze Selected' lane arrows ===<br />
Waze Selected lane arrows are displayed for us both in the edit dialog (to the left of the checkboxes for each outbound segment) and in the Lanes pane (once changes are applied).{{Collapsible section top|expand=no}}<br />
''Expand for more information...''{{Collapsible section content}}<br />
The determination is mostly simple and mostly based on angles. Consider there is a pizza pie on the map. Cutting the pizza pie into 8 slices, outbound segments in the top slice (i.e., turn angles from 0° up to 22.5° either way) might show straight, slight left, or slight right depending on context; the top-left and top-right slice (i.e., turn angles from 22.5° to 67.5° either way) will show slight left or slight right arrows; the left slice and right slice (between 67.5° and 112.5°) will have regular turn left or turn right arrows; and the bottom 3 slices (between 112.5° and 180°) will have sharp left/sharp right arrows. Capische? Mamma mia.<br />
Regarding the top slice, when there is only one outbound segment within the <22.5° slice, that segment will get the “straight” arrows. However, if multiple segments exist within this slice, some form of the “best continuation” analysis is used to determine which one gets the straight arrow, and other arrows in that slice get slight left or slight right arrows. If there is no “best continuation”, then the segment that is closer to 0° gets the straight arrow, and the other one(s)]]<br />
{{Collapsible section bottom}}<br />
=== When to override lane arrows ===<br />
See [[#How Waze selects 'Waze Selected' lane arrows|How Waze selects lane arrows]] for information on the default turn arrows.<br />
<br />
Always review the lane arrows displayed in the Lanes pane carefully once you have applied your edits. Use override when it makes sense to do so, and leave the “Waze selected” setting in place otherwise. Do what makes sense to the person in the driver’s seat—choose the arrow which is going to make the most sense to the driver based on what they are going to have to do (continue straight, U turn, slight right, etc.) and what they are going to see as they approach the intersection or interchange where they need to make the maneuver.<br />
<br />
This does not necessarily mean that the lane arrows should be forced to match the instruction—for example, there are times when a "keep left" instruction is best paired with "straight" arrows, or when a "turn right" instruction is paired with a slight right arrow. The lane arrows should be set according to how a driver would perceive the lane configuration, but the audio guidance should reflect the action to be taken.<br />
<br />
When you change the arrow associated with one outgoing segment, check the remaining segments. In most situations, no two outgoing segments should use the same arrow.<br />
==== When more than one outbound segment have the same 'Waze selected' arrow ====<br />
Change one or more of them in a way that makes sense.<br />
==== Where segment geometry doesn’t match reality ====<br />
[[File:Lanes Override2.png|150px|thumb]]This happens in some locations because Waze road segment width does not match the real life road width. This can result in turn angles on the map which are somewhat different from the true turn angle. Lane arrow override may be necessary.<br clear=all><br />
<br />
==== Where the Waze selected arrow doesn't match reality ====<br />
Even in areas with very high quality maps, the Waze arrow selection mechanism can create arrow configurations which are confusing to the driver. This is particularly likely at nodes where there are multiple outbound segments essentially straight ahead (within a couple dozen degrees either way) from the inbound segment.<br />
These potentially-confusing generated arrows are most often found at ramp splits, wayfinders, and forks in the road, discussed in the section immediately below.<br />
<br />
However, these situations occur in other places as well. For example, in situations where a main road veers off in one direction, and a side road continues straight ahead, the Waze selected arrows will sometimes give straight-ahead arrows to the continuation of the main road, and a “slight turn” arrow to the straight-ahead side road. This does not make sense from a driver’s perspective. In such cases, use lane angle overrides to achieve the desired result.<br />
<br />
[[File:Jeff-sv sm.jpg|400px|frameless|left]] [[File:Jeff-sat sm.jpg|400px|frameless|right]]<br clear=all><br />
<big>In this example, the continuing road veers left, while the side road exits straight ahead. Both street level and overhead imagery clearly shows the driver's perspective and the need for adjustments.</big> <br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Waze selected arrows do not match reality.'''<br />
| style="width: 50%; text-align:center" | '''Use lane angle overrides to create reality.'''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:Jeff-no.png|300px|frameless]]<br />
| style="width: 50%; text-align:center" | [[File:Jeff-yes.png|300px|frameless]]<br />
|}<br />
<br />
==== Ramp splits, wayfinders, and forks in the road ====<br />
Sometimes the Waze selected lane arrows are the best choice and sometimes they are not. Look at both overhead and street views to consider what makes the most sense from the driver’s perspective. Given the processes by which Waze selects the “Waze selected” selection, sometimes the “Waze selected” straight-ahead arrow does not match well with the actual geometry of a junction. <br><br />
<br />
Generally, only one outbound segment (if any) should have the “straight” arrow. If both outbound segments at a split or wayfinder take you down an equally-straight or equally-not straight path (whether immediately or foreseeably ahead), then neither should use the straight arrow. If one of the outbound segments leads to a straighter path than the other, however, then that one should have the straight arrow. If this is already happening, great. If not, use lane override to make it happen (and to ensure that the other path doesn’t keep it).<br />
<br />
== Adding lanes to the map ==<br />
Before adding lane information, check both aerial and street view to make sure how many lanes there are on the segment at the node(s) where you are about to add lanes. See [[#What counts as a lane?|What counts as a lane?]] for more.<br />
{{mbox | type = warning | text = {{As of|2020|04|27}} the lanes tab shows when a segment is selected at zoom level 4 (500 ft) or closer. If you don’t see the tab, try zooming and panning until it shows. The node you are editing must also be in the window.}}<br />
=== Adding lanes to a segment ===<br />
1. Select the segment to which you would like to add lanes.<br />
2. In the left pane, click the Lanes tab.[[File:Lanes tab.png|thumb|center|300px|The lanes tab appears in the left pane]]<br />
3. For two-way segments, ensure you are editing the correct end of the segment. The “B” end (for A-to-B traffic) will show first, followed by the “A” end (for B-to-A traffic). The text at the top of each ‘end’ will describe the directionality of the lanes below. [[File:Lanes tab2.png|300px|thumb|center|For two-way segments, there is a section for each direction of lanes]]<br />
4. Click "Add lane guidance". [[File:Lanes_AddLaneGuidance.png|300px|thumb|center|For two-way segments, there is a section for each direction of lanes]]<br />
5. Enter the number of lanes (NOT the number of possible directions). Use the number of lanes that connect to the next segment, even if there are a different number of lanes at some other point on the segment. See the [[#What counts as a lane?|What counts as a lane?]] section above for more information.[[File:Lanes_NumberOf.png|300px|thumb|center|Count the numbers of lanes at the end of the segment.]]<br />
6. Use the checkboxes to assign the available lanes for each outbound movement. Confirm using street-level imagery, where available. Note that the same lane may be used for more than one movement (e.g., the right lane may be used for both continuing and right-turning traffic).[[File:Lanes_Checkbox1.png|300px|thumb|left|Each lane is dedicated to a specific movement.]][[File:Lanes_Checkbox2.png|300px|thumb|right|The right lane is shared for continuing and turning traffic.]]<br clear=all><br />
7. Click Apply, then save your changes when you are ready. Changes will go live in the app after the next map tile update. <br />
{{mbox|text=Mousing-over the turn arrow in the lanes panel will<br><br />
highlight that turn arrow on the map.|imageright=[[File:WME_LG_Arrow_Highlight.png|thumb|100px]]}}<br />
<br />
=== Editing existing lanes ===<br />
Editing existing Lane Guidance for a segment is done similarly to adding the lanes for the first time:<br><br />
1. Select the segment.<br><br />
2. In the left pane, click the Lanes tab.<br><br />
3. Click "Edit lane guidance" to bring up the Lane Guidance editing console.<br>[[File:EditLaneGuidance.png|300px|thumb|center|Click 'Edit lane guidance']]<br clear=all><br />
<br />
=== Lane errors ===<br />
[[File:Lanes error.png|150px|thumb|right]] If lane data is incomplete, or has been corrupted due to edits on connected segments, then an error alert symbol will appear on the affected segment and on the Lanes tab when the segment is selected.<br clear=all><br />
=== Overriding a turn angle {{Anchor|Overriding a turn angle|Turn angle override|TAO}} === <br />
[[File:Lanes Override3.png|100px|thumb|right|Turn angle override controls]] In some cases, the displayed turn angle may need to be adjusted. Rather than adjusting the geometry of the road segments, an override function is available in the Lanes tab. <br />
# Select the segment.<br />
# In the left pane, click the Lanes tab.<br />
# Click “Edit lane guidance”.<br />
# Click the given turn angle icon under the TURNS header to open the Override turn angle menu. <br />
# Select a new turn angle, or the ‘Waze selected’ angle. <br clear=all><br />
<br />
=== Junction Boxes ===<br />
Lane information can be added to segments which are part of a [[Junction Box]] just as they can be added to any other segment. In order for lane guidance to work, all turn arrows on the segments underlying a Junction Box must be green (unrestricted) '''if''' they are on a route allowed by the overlaid Junction Box. Use the Junction Box itself to restrict any necessary routes.<br />
{{mbox | type = warning | text = If a junction box uses a [[turn instruction override]] to override the Waze-selected turn instructions along one of the junction box routes, then the underlying lane data may not be displayed in the app.}}<br />
<br />
=== Lanes on divided roadways {{Anchor|Lanes on divided roadways|'H' and '#' intersections}} ===<br />
At intersections where one or both roads are divided, lanes cannot always be added directly.<br><br />
<br />
Many such intersections can be classified as either “H” intersections (where only one road is divided) or “#” intersections (where both roads are divided).<br><br />
{{mbox|text=On the divided roadway approaches to an “H” intersection, lanes can be added directly to the segments.}}<br />
For some “#” intersections, and on the undivided roadway approaches to some “H” intersections, Waze can combine lane guidance information from more than one segment into a single set of lanes that includes both left and right turns, as the driver expects. {{Anchor|divided roadway criteria}} This will only be possible if all of these conditions are met:<br />
# Both left and right turns are possible at the intersection;<br />
# The two portions of the divided roadway are essentially parallel to each other;<br />
# The two intersecting roads are more or less perpendicular to each other;<br />
# The median segment in question is 50 m or shorter; and<br />
# The number of lanes entering the intersection is equal to the total number of lanes exiting the intersection (total number of lanes exiting intersection = number of lanes on the median segment + number of right-turn only lanes on the entry segment—in other words, no new lanes are added in the median).<br />
If these conditions are met, then follow the guidance in the [[#Mapping lanes on divided roadways|next section]] to add lane information.<br />
{{mbox|text=The purpose of the heuristics is to combine left turn, straight, and right turn arrows into a single lane set. At intersections where either left turns or right turns are disallowed, lanes can be added directly, and heuristics are not needed—in other words, there is no need to add “straight only” lane information. In the example below, right-turning traffic will get the full set of lanes from the entry segment; adding lanes to the median segment would serve no purpose. <br><br />
[[File:LanesMedianNA1.png|frameless|300px]] [[File:LanesMedianNA2.png|frameless|300px]]<br />
}}<br />
{{mbox<br />
| type = important<br />
| text = One side effect of the H/# heuristics is that in many cases the server will identify 'turn left, then turn left' movements across a H/# intersection (when they are not prohibited by [[Junction_Style_Guide/Intersections#Avoiding_U_turns|the U-turn prevention algorithm]]) as a U-turn, and display the U-turn lane guidance arrow in the app. In addition to the visual display of the U-turn arrow, the app's voice turn-by-turn instructions will vocalize the movement as a u-turn. <br />
}}<br />
==== Mapping lanes on divided roadways ====<br />
===== Hash intersections =====<br />
[[File:Median-entry.jpg|300px|thumb|right|Entry and Median Segments (for each direction of travel)]]<br />
First, make sure that the intersection and the turn you are mapping for meet the [[#divided roadway criteria|guidelines above]]. Handle one direction of travel at a time.<br><br />
<br />
For each direction of travel, lanes must be mapped on two segments: the “entry segment” (immediately before the median) and the “median segment” (within the median). ''See the adjacent figure. ''<br />
# On the entry segment, include the total number of lanes entering the segment.<br />
## Any lane that can be used to either turn left or continue straight should be mapped as a continuing straight lane.<br />
## Right turn lanes should be mapped as normal.<br />
# On the median segment, include the total number of lanes on the median segment (which should equal the number of lanes on the entry segment minus the number of right turn only lanes).<br clear=all><br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Entry segment: '''<br />
| style="width: 50%; text-align:center" | '''Median segment: '''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:Lanes_entry.png|350px|frameless]]<br />
| style="width: 50%; text-align:center" | [[File:Lanes_median.png|350px|frameless]]<br />
|}<br />
The heuristic in the routing server will combine these two sets of lanes together and provide a single set for drivers making either left or right turns. Unfortunately, there is no way to visualize the result in WME.<br><br />
<br />
'''<big>Lanes resulting from heuristics:</big>'''<br />
[[File:Lanes result.png|224px|frameless|left]]<br clear=all><br />
===== H Intersections =====<br />
The same heuristic applies to the undivided road side of an H junction. No heuristic is necessary for the divided road side.<br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Undivided road side:'''<br />
| style="width: 50%; text-align:center" | '''Divided road side:'''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:LanesH1.png|350px|frameless]]<br />
| rowspan="2" style="width: 50%; text-align:center" | [[File:LanesH3.png|350px|frameless]]<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:LanesH2resubmit.png|350px|frameless]]<br />
| style="width: 50%; text-align:center" | <br />
|}<br />
{{mbox|text=The median segments of # and H junctions is a rare instance where, on occasion, it is proper to add “1 lane” to a segment. This will be necessary any time there are multiple lanes on the entry segment but only one lane remaining on the median segment (because any other lane was right turn only).<br><br />
[[File:LanesHBox1resubmit.png|frameless|300px]] [[File:LanesHBox2.png|frameless|300px]]<br />
}}<br />
===== Checking your work =====<br />
There are a few things you can do to double-check your work on divided-roadway intersections that need to be mapped with heuristics.<br />
# The total number of lanes on the entry segment should equal the total number of lanes at the intersection:<br />
#* total lanes (intersection) = total lanes (entry)<br />
# The total number of lanes on the median segment should equal the difference between the total number of lanes on the entry segment and the number of right-turn only lanes on the entry segment:<br />
#* total lanes (median) = total lanes (entry) – right turn only lanes (entry)<br />
# The number of straight-ahead lanes on the entry segment (i.e., the number of boxes checked for the straight-ahead movement) should equal the total number of lanes on the median segment:<br />
#* straight-ahead lanes (entry) = total lanes (median)<br />
If these conditions are not met, the heuristic method may not function as expected, and it is best to leave lanes off for the time being.</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=Lanes&diff=172698Lanes2020-05-30T22:36:16Z<p>Tonestertm: /* Editing existing lanes */ Replace placeholder image</p>
<hr />
<div>{{construction | contact = https://www.waze.com/forum/viewtopic.php?f=1636&t=301141 | contacttype = forum | draft = no | open = no | revision = no | section = no | talk = no}}<br />
Lane guidance is a new Waze app feature that shows the user exactly which lanes they should use to make their next movement. This feature boosts Wazer confidence by providing reassurance in junctions both typical and unusual. <br />
Lane guidance data is added via the [[Waze Map Editor|Waze Map Editor (WME)]]. When a single segment is selected in the WME, an additional tab called Lanes is available in the left pane. The Lanes tab allows map editors to tell Waze which lane to display to the driver for lane guidance in the mobile app. <br><br />
<br />
There are some important considerations regarding lane guidance in Waze:<br />
* '''Lane guidance does not affect routing''' - it is merely a visual feature.<br />
* '''Lane guidance does not affect audio instructions''', with the exception of u-turn instructions resulting from [[#Lanes_on_divided_roadways|heuristics for intersections on divided roads]].<br />
* '''Lane guidance will only be displayed when a navigation instruction is given.''' If the [[How_Waze_determines_turn_/_keep_/_exit_maneuvers#Best_Continuation|best continuation]] is straight ahead, lane guidance will not be shown, unless there is a [[Turn_instruction_override|continue straight TIO]].<br />
{{mbox | type = protection | text = {{As of|2020|05|28}} the Lanes tab is only visible in the WME to [[Editing restrictions|rank 3 editors]] and lane guidance in the App is only visible to beta testers.}}<br />
{{mbox| type = caution| text = {{As of|2020|05|30}} the lane mapping feature of WME and the lane guidance feature of the mobile app are both still under development. Please check this guide frequently for updates to features and guidance.}}<br />
== Mapping guidance ==<br />
=== What counts as a lane? ===<br />
'''Q: How many lanes should you map at the end of a segment? What counts as a lane?'''<br><br />
'''A: Map any lane that achieves full and consistent width BEFORE the turn itself.''' For a freeway exit lane, this means a lane that is full width BEFORE [https://mutcd.fhwa.dot.gov/HTM/2003/part3/fig3b-08-1_longdesc.htm the gore point]. If someone travelling in the right lane can continue straight without changing lanes, then map this as a straight/turn lane. <br><br />
Consider what the road looks like to a driver - make the number of lanes in the lane guidance display conform to what the driver will see.<br />
==== Freeway exits and other ramps ====<br />
'''<big>Example 1: Not a Separate Lane</big>'''[[File:NotALane2.png|880px|The exit lane does not reach full width until the gore point; map as part of the rightmost continue-straight lane]]<br />
The exit lane does not reach full width until the gore point; map as part of the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 2: Not a Separate Lane</big>'''[[File:NotALane3.png|880px|The exit lane does not reach full width until the gore point; mapped as part of the rightmost continue-straight lane.]]<br />
The exit lane does not reach full width until the gore point; mapped as part of the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 3: Separate Lane</big>'''[[File:SeperateLane2.png|880px|When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.]]<br />
When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 4: Separate Lane</big>'''[[File:SeperateLane1.png|880px|When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.]]<br />
When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.<br />
==== Center two-way left-turn lanes ====<br />
[[File:TwoWayLeftTurnLanes.png|thumb|right|Center two-way turn lane: Separate turn lane if a left is allowed; no turn lane if left is not allowed.]]<br />
Many two-way streets have a center lane marked as a two-way left turn lane (TWLTL), also known as a ‘suicide lane’ or ‘chicken lane’. In the US, this lane is bordered on either side by two yellow lines - the inner line is broken or dashed, the outer line is solid. Pavement marking arrows may or may not be present. Where lane guidance is applied and the left turn lane is possible, these should be marked as separate left-turn lanes.<br />
==== HOV or other restricted lanes ====<br />
HOV (high-occupancy vehicle) restrictions or vehicle restrictions may sometimes only apply to a portion of the roadway. Only include these restricted lanes in lane guidance if they are available to users on the segment in question. In the example below, the bus lane allows for right turning vehicles to use the lane, so it is included in lane guidance. <br />
<gallery><br />
File:Lanes_HOVcount.png|HOV lanes that are on the same segment (not physically separated) should be included in lanes. <br />
File:Lanes_BusResticted.png|Bus, bike, or other restricted lanes should be included. In this case, right turns are allowed from the bus lane, so it is shown as a right turn lane. <br />
File:Lanes_CenterBus.png|In this case, the bus lane (red, center) is the only lane that proceeds straight ahead. It should be included, as it will be shown (though faded) to drivers when they are directed using the outside lanes to turn left or right. <br />
File:Lanes_Choices3.png|The HOV lane is clearly visible to all traffic, and would be considered by most drivers to be a lane, it should be included in the count of lanes at the segments ending at the exit.<br />
</gallery><br />
<br />
=== When to map lanes ===<br />
Generally, lanes should be mapped where there is more than one lane and only a subset of the lanes is available for turns. Also lanes should be mapped in potentially confusing locations where lane guidance can significantly improve safety and the driver experience.<br />
==== When the driver needs to choose the correct lane ====<br />
[[File:Lanes DriversChoice.png|thumb|right]] Any time there are two or more lanes AND an instruction is given at the node. In the example below, the street running east/west has only two lanes in either direction, but only one of those lanes may turn south onto the side street. Lane guidance should be added.<br clear=all><br />
==== To clarify which road to take ====<br />
Before now, Waze could not show the driver the difference between slight, 90°, and sharp turns. Without lanes, intersections with multiple right or multiple left turns could be confusing to drivers. Lane guidance can clear up this confusion by showing drivers whether to take, for example, the slight turn or the sharp turn.<br />
{{mbox | text = This situation is generally the only place where it is useful to add lanes where there is only one lane in the relevant direction of travel.}}<br />
<gallery>File:Lanes_Choices.png|example 1<br />
File:Lanes_Choices2.png|example 2</gallery><br />
==== When the driver needs reinforcement or reassurance for safety ====<br />
[[File:Lanes_Reassurance.png|thumb|right|For this freeway off-ramp onto a one-way roadway, reinforce “no left turn”; either lane is fine.]]<br />
There are some cases where lanes should be added to reassure drivers that they need not switch lanes, or that they may not turn from the lane they are in. In the example below, both lanes of the highway off-ramp must turn right — drivers have no choice. Lane guidance should be added to reassure drivers in the left lane that they need not change lanes and to reinforce the prohibition on the left turn to reduce the chance of them making a wrong-way turn.<br />
<br />
=== When not to map lanes ===<br />
==== When drivers have no choice ====<br />
[[File:Nolanessimple.png|150px|thumb|right|Suburban local streets typically don't have multiple lanes, and don't need lane guidance.]] Generally, don’t add lanes when there is only one lane, or at a node where no instruction is to be given. An exception to this general rule is at confusing intersections and interchanges where the driver needs reassurance that a lane change will not be necessary before the next turn or exit maneuver, or reinforcement that what might look like a valid turn is not allowed (see the reinforcement and reassurance example above).<br clear=all><br />
<br />
==== Merges and new lanes ====<br />
Waze does not offer lane guidance for a reduction in the number of lanes.<br />
[[File:MergeLanes.png|left|frame|Lane guidance is not appropriate for freeway lane reductions that do not occur near an interchange]]<br clear=all><br />
=== How Waze selects 'Waze Selected' lane arrows ===<br />
Waze Selected lane arrows are displayed for us both in the edit dialog (to the left of the checkboxes for each outbound segment) and in the Lanes pane (once changes are applied).{{Collapsible section top|expand=no}}<br />
''Expand for more information...''{{Collapsible section content}}<br />
The determination is mostly simple and mostly based on angles. Consider there is a pizza pie on the map. Cutting the pizza pie into 8 slices, outbound segments in the top slice (i.e., turn angles from 0° up to 22.5° either way) might show straight, slight left, or slight right depending on context; the top-left and top-right slice (i.e., turn angles from 22.5° to 67.5° either way) will show slight left or slight right arrows; the left slice and right slice (between 67.5° and 112.5°) will have regular turn left or turn right arrows; and the bottom 3 slices (between 112.5° and 180°) will have sharp left/sharp right arrows. Capische? Mamma mia.<br />
Regarding the top slice, when there is only one outbound segment within the <22.5° slice, that segment will get the “straight” arrows. However, if multiple segments exist within this slice, some form of the “best continuation” analysis is used to determine which one gets the straight arrow, and other arrows in that slice get slight left or slight right arrows. If there is no “best continuation”, then the segment that is closer to 0° gets the straight arrow, and the other one(s)]]<br />
{{Collapsible section bottom}}<br />
=== When to override lane arrows ===<br />
See [[#How Waze selects 'Waze Selected' lane arrows|How Waze selects lane arrows]] for information on the default turn arrows.<br />
<br />
Always review the lane arrows displayed in the Lanes pane carefully once you have applied your edits. Use override when it makes sense to do so, and leave the “Waze selected” setting in place otherwise. Do what makes sense to the person in the driver’s seat—choose the arrow which is going to make the most sense to the driver based on what they are going to have to do (continue straight, U turn, slight right, etc.) and what they are going to see as they approach the intersection or interchange where they need to make the maneuver.<br />
<br />
This does not necessarily mean that the lane arrows should be forced to match the instruction—for example, there are times when a "keep left" instruction is best paired with "straight" arrows, or when a "turn right" instruction is paired with a slight right arrow. The lane arrows should be set according to how a driver would perceive the lane configuration, but the audio guidance should reflect the action to be taken.<br />
<br />
When you change the arrow associated with one outgoing segment, check the remaining segments. In most situations, no two outgoing segments should use the same arrow.<br />
==== When more than one outbound segment have the same 'Waze selected' arrow ====<br />
Change one or more of them in a way that makes sense.<br />
==== Where segment geometry doesn’t match reality ====<br />
[[File:Lanes Override2.png|150px|thumb]]This happens in some locations because Waze road segment width does not match the real life road width. This can result in turn angles on the map which are somewhat different from the true turn angle. Lane arrow override may be necessary.<br clear=all><br />
<br />
==== Where the Waze selected arrow doesn't match reality ====<br />
Even in areas with very high quality maps, the Waze arrow selection mechanism can create arrow configurations which are confusing to the driver. This is particularly likely at nodes where there are multiple outbound segments essentially straight ahead (within a couple dozen degrees either way) from the inbound segment.<br />
These potentially-confusing generated arrows are most often found at ramp splits, wayfinders, and forks in the road, discussed in the section immediately below.<br />
<br />
However, these situations occur in other places as well. For example, in situations where a main road veers off in one direction, and a side road continues straight ahead, the Waze selected arrows will sometimes give straight-ahead arrows to the continuation of the main road, and a “slight turn” arrow to the straight-ahead side road. This does not make sense from a driver’s perspective. In such cases, use lane angle overrides to achieve the desired result.<br />
<br />
[[File:Jeff-sv sm.jpg|400px|frameless|left]] [[File:Jeff-sat sm.jpg|400px|frameless|right]]<br clear=all><br />
<big>In this example, the continuing road veers left, while the side road exits straight ahead. Both street level and overhead imagery clearly shows the driver's perspective and the need for adjustments.</big> <br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Waze selected arrows do not match reality.'''<br />
| style="width: 50%; text-align:center" | '''Use lane angle overrides to create reality.'''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:Jeff-no.png|300px|frameless]]<br />
| style="width: 50%; text-align:center" | [[File:Jeff-yes.png|300px|frameless]]<br />
|}<br />
<br />
==== Ramp splits, wayfinders, and forks in the road ====<br />
Sometimes the Waze selected lane arrows are the best choice and sometimes they are not. Look at both overhead and street views to consider what makes the most sense from the driver’s perspective. Given the processes by which Waze selects the “Waze selected” selection, sometimes the “Waze selected” straight-ahead arrow does not match well with the actual geometry of a junction. <br><br />
<br />
Generally, only one outbound segment (if any) should have the “straight” arrow. If both outbound segments at a split or wayfinder take you down an equally-straight or equally-not straight path (whether immediately or foreseeably ahead), then neither should use the straight arrow. If one of the outbound segments leads to a straighter path than the other, however, then that one should have the straight arrow. If this is already happening, great. If not, use lane override to make it happen (and to ensure that the other path doesn’t keep it).<br />
<br />
== Adding lanes to the map ==<br />
Before adding lane information, check both aerial and street view to make sure how many lanes there are on the segment at the node(s) where you are about to add lanes. See [[#What counts as a lane?|What counts as a lane?]] for more.<br />
{{mbox | type = warning | text = {{As of|2020|04|27}} the lanes tab shows when a segment is selected at zoom level 4 (500 ft) or closer. If you don’t see the tab, try zooming and panning until it shows. The node you are editing must also be in the window.}}<br />
=== Adding lanes to a segment ===<br />
1. Select the segment to which you would like to add lanes.<br />
2. In the left pane, click the Lanes tab.[[File:Lanes tab.png|thumb|center|300px|The lanes tab appears in the left pane]]<br />
3. For two-way segments, ensure you are editing the correct end of the segment. The “B” end (for A-to-B traffic) will show first, followed by the “A” end (for B-to-A traffic). The text at the top of each ‘end’ will describe the directionality of the lanes below. [[File:Lanes tab2.png|300px|thumb|center|For two-way segments, there is a section for each direction of lanes]]<br />
4. Click "Add lane guidance". [[File:Lanes_AddLaneGuidance.png|300px|thumb|center|For two-way segments, there is a section for each direction of lanes]]<br />
5. Enter the number of lanes (NOT the number of possible directions). Use the number of lanes that connect to the next segment, even if there are a different number of lanes at some other point on the segment. See the [[#What counts as a lane?|What counts as a lane?]] section above for more information.[[File:Lanes_NumberOf.png|300px|thumb|center|Count the numbers of lanes at the end of the segment.]]<br />
6. Use the checkboxes to assign the available lanes for each outbound movement. Confirm using street-level imagery, where available. Note that the same lane may be used for more than one movement (e.g., the right lane may be used for both continuing and right-turning traffic).[[File:Lanes_Checkbox1.png|300px|thumb|left|Each lane is dedicated to a specific movement.]][[File:Lanes_Checkbox2.png|300px|thumb|right|The right lane is shared for continuing and turning traffic.]]<br clear=all><br />
7. Click Apply, then save your changes when you are ready. Changes will go live in the app after the next map tile update. <br />
{{mbox|text=Mousing-over the turn arrow in the lanes panel will<br><br />
highlight that turn arrow on the map.|imageright=[[File:WME_LG_Arrow_Highlight.png|thumb|100px]]}}<br />
<br />
=== Editing existing lanes ===<br />
Editing existing Lane Guidance for a segment is done similarly to adding the lanes for the first time:<br><br />
1. Select the segment.<br><br />
2. In the left pane, click the Lanes tab.<br><br />
3. Click "Edit lane guidance" to bring up the Lane Guidance editing console.<br>[[File:EditLaneGuidance.png|300px|thumb|center|Click 'Edit lane guidance']]<br clear=all><br />
<br />
=== Lane errors ===<br />
[[File:Lanes error.png|150px|thumb|right]] If lane data is incomplete, or has been corrupted due to edits on connected segments, then an error alert symbol will appear on the affected segment and on the Lanes tab when the segment is selected.<br clear=all><br />
=== Overriding a turn angle {{Anchor|Overriding a turn angle|Turn angle override|TAO}} === <br />
[[File:Lanes Override3.png|100px|thumb|right|Turn angle override controls]] In some cases, the displayed turn angle may need to be adjusted. Rather than adjusting the geometry of the road segments, an override function is available in the Lanes tab. <br />
# Click the segment.<br />
# In the left pane, click the Lanes tab.<br />
# Click “Edit lane guidance”.<br />
# Click the given turn angle icon under the TURNS header to open the Override turn angle menu. <br />
# Select a new turn angle, or the ‘Waze selected’ angle. <br clear=all><br />
=== Junction Boxes ===<br />
Lane information can be added to segments which are part of a [[Junction Box]] just as they can be added to any other segment. In order for lane guidance to work, all turn arrows on the segments underlying a Junction Box must be green (unrestricted) '''if''' they are on a route allowed by the overlaid Junction Box. Use the Junction Box itself to restrict any necessary routes.<br />
{{mbox | type = warning | text = If a junction box uses a [[turn instruction override]] to override the Waze-selected turn instructions along one of the junction box routes, then the underlying lane data may not be displayed in the app.}}<br />
<br />
=== Lanes on divided roadways {{Anchor|Lanes on divided roadways|'H' and '#' intersections}} ===<br />
At intersections where one or both roads are divided, lanes cannot always be added directly.<br><br />
<br />
Many such intersections can be classified as either “H” intersections (where only one road is divided) or “#” intersections (where both roads are divided).<br><br />
{{mbox|text=On the divided roadway approaches to an “H” intersection, lanes can be added directly to the segments.}}<br />
For some “#” intersections, and on the undivided roadway approaches to some “H” intersections, Waze can combine lane guidance information from more than one segment into a single set of lanes that includes both left and right turns, as the driver expects. {{Anchor|divided roadway criteria}} This will only be possible if all of these conditions are met:<br />
# Both left and right turns are possible at the intersection;<br />
# The two portions of the divided roadway are essentially parallel to each other;<br />
# The two intersecting roads are more or less perpendicular to each other;<br />
# The median segment in question is 50 m or shorter; and<br />
# The number of lanes entering the intersection is equal to the total number of lanes exiting the intersection (total number of lanes exiting intersection = number of lanes on the median segment + number of right-turn only lanes on the entry segment—in other words, no new lanes are added in the median).<br />
If these conditions are met, then follow the guidance in the [[#Mapping lanes on divided roadways|next section]] to add lane information.<br />
{{mbox|text=The purpose of the heuristics is to combine left turn, straight, and right turn arrows into a single lane set. At intersections where either left turns or right turns are disallowed, lanes can be added directly, and heuristics are not needed—in other words, there is no need to add “straight only” lane information. In the example below, right-turning traffic will get the full set of lanes from the entry segment; adding lanes to the median segment would serve no purpose. <br><br />
[[File:LanesMedianNA1.png|frameless|300px]] [[File:LanesMedianNA2.png|frameless|300px]]<br />
}}<br />
{{mbox<br />
| type = important<br />
| text = One side effect of the H/# heuristics is that in many cases the server will identify 'turn left, then turn left' movements across a H/# intersection (when they are not prohibited by [[Junction_Style_Guide/Intersections#Avoiding_U_turns|the U-turn prevention algorithm]]) as a U-turn, and display the U-turn lane guidance arrow in the app. In addition to the visual display of the U-turn arrow, the app's voice turn-by-turn instructions will vocalize the movement as a u-turn. <br />
}}<br />
==== Mapping lanes on divided roadways ====<br />
===== Hash intersections =====<br />
[[File:Median-entry.jpg|300px|thumb|right|Entry and Median Segments (for each direction of travel)]]<br />
First, make sure that the intersection and the turn you are mapping for meet the [[#divided roadway criteria|guidelines above]]. Handle one direction of travel at a time.<br><br />
<br />
For each direction of travel, lanes must be mapped on two segments: the “entry segment” (immediately before the median) and the “median segment” (within the median). ''See the adjacent figure. ''<br />
# On the entry segment, include the total number of lanes entering the segment.<br />
## Any lane that can be used to either turn left or continue straight should be mapped as a continuing straight lane.<br />
## Right turn lanes should be mapped as normal.<br />
# On the median segment, include the total number of lanes on the median segment (which should equal the number of lanes on the entry segment minus the number of right turn only lanes).<br clear=all><br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Entry segment: '''<br />
| style="width: 50%; text-align:center" | '''Median segment: '''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:Lanes_entry.png|350px|frameless]]<br />
| style="width: 50%; text-align:center" | [[File:Lanes_median.png|350px|frameless]]<br />
|}<br />
The heuristic in the routing server will combine these two sets of lanes together and provide a single set for drivers making either left or right turns. Unfortunately, there is no way to visualize the result in WME.<br><br />
<br />
'''<big>Lanes resulting from heuristics:</big>'''<br />
[[File:Lanes result.png|224px|frameless|left]]<br clear=all><br />
===== H Intersections =====<br />
The same heuristic applies to the undivided road side of an H junction. No heuristic is necessary for the divided road side.<br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Undivided road side:'''<br />
| style="width: 50%; text-align:center" | '''Divided road side:'''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:LanesH1.png|350px|frameless]]<br />
| rowspan="2" style="width: 50%; text-align:center" | [[File:LanesH3.png|350px|frameless]]<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:LanesH2resubmit.png|350px|frameless]]<br />
| style="width: 50%; text-align:center" | <br />
|}<br />
{{mbox|text=The median segments of # and H junctions is a rare instance where, on occasion, it is proper to add “1 lane” to a segment. This will be necessary any time there are multiple lanes on the entry segment but only one lane remaining on the median segment (because any other lane was right turn only).<br><br />
[[File:LanesHBox1resubmit.png|frameless|300px]] [[File:LanesHBox2.png|frameless|300px]]<br />
}}<br />
===== Checking your work =====<br />
There are a few things you can do to double-check your work on divided-roadway intersections that need to be mapped with heuristics.<br />
# The total number of lanes on the entry segment should equal the total number of lanes at the intersection:<br />
#* total lanes (intersection) = total lanes (entry)<br />
# The total number of lanes on the median segment should equal the difference between the total number of lanes on the entry segment and the number of right-turn only lanes on the entry segment:<br />
#* total lanes (median) = total lanes (entry) – right turn only lanes (entry)<br />
# The number of straight-ahead lanes on the entry segment (i.e., the number of boxes checked for the straight-ahead movement) should equal the total number of lanes on the median segment:<br />
#* straight-ahead lanes (entry) = total lanes (median)<br />
If these conditions are not met, the heuristic method may not function as expected, and it is best to leave lanes off for the time being.</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=Lanes&diff=172693Lanes2020-05-30T21:41:12Z<p>Tonestertm: /* Lanes on divided roadways {{Anchor|Lanes on divided roadways|'H' and '#' intersections}} */ which -> when they</p>
<hr />
<div>{{construction | contact = https://www.waze.com/forum/viewtopic.php?f=1636&t=301141 | contacttype = forum | draft = no | open = no | revision = no | section = no | talk = no}}<br />
Lane guidance is a new Waze app feature that shows the user exactly which lanes they should use to make their next movement. This feature boosts Wazer confidence by providing reassurance in junctions both typical and unusual. <br />
Lane guidance data is added via the [[Waze Map Editor|Waze Map Editor (WME)]]. When a single segment is selected in the WME, an additional tab called Lanes is available in the left pane. The Lanes tab allows map editors to tell Waze which lane to display to the driver for lane guidance in the mobile app. <br><br />
<br />
There are some important considerations regarding lane guidance in Waze:<br />
* '''Lane guidance does not affect routing''' - it is merely a visual feature.<br />
* '''Lane guidance does not affect audio instructions''', with the exception of u-turn instructions resulting from [[#Lanes_on_divided_roadways|heuristics for intersections on divided roads]].<br />
* '''Lane guidance will only be displayed when a navigation instruction is given.''' If the [[How_Waze_determines_turn_/_keep_/_exit_maneuvers#Best_Continuation|best continuation]] is straight ahead, lane guidance will not be shown, unless there is a [[Turn_instruction_override|continue straight TIO]].<br />
{{mbox | type = protection | text = {{As of|2020|05|28}} the Lanes tab is only visible in the WME to [[Editing restrictions|rank 3 editors]] and lane guidance in the App is only visible to beta testers.}}<br />
{{mbox| type = caution| text = {{As of|2020|05|30}} the lane mapping feature of WME and the lane guidance feature of the mobile app are both still under development. Please check this guide frequently for updates to features and guidance.}}<br />
== Mapping guidance ==<br />
=== What counts as a lane? ===<br />
'''Q: How many lanes should you map at the end of a segment? What counts as a lane?'''<br><br />
'''A: Map any lane that achieves full and consistent width BEFORE the turn itself.''' For a freeway exit lane, this means a lane that is full width BEFORE [https://mutcd.fhwa.dot.gov/HTM/2003/part3/fig3b-08-1_longdesc.htm the gore point]. If someone travelling in the right lane can continue straight without changing lanes, then map this as a straight/turn lane. <br><br />
Consider what the road looks like to a driver - make the number of lanes in the lane guidance display conform to what the driver will see.<br />
==== Freeway exits and other ramps ====<br />
'''<big>Example 1: Not a Separate Lane</big>'''[[File:NotALane2.png|880px|The exit lane does not reach full width until the gore point; map as part of the rightmost continue-straight lane]]<br />
The exit lane does not reach full width until the gore point; map as part of the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 2: Not a Separate Lane</big>'''[[File:NotALane3.png|880px|The exit lane does not reach full width until the gore point; mapped as part of the rightmost continue-straight lane.]]<br />
The exit lane does not reach full width until the gore point; mapped as part of the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 3: Separate Lane</big>'''[[File:SeperateLane2.png|880px|When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.]]<br />
When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 4: Separate Lane</big>'''[[File:SeperateLane1.png|880px|When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.]]<br />
When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.<br />
==== Center two-way left-turn lanes ====<br />
[[File:TwoWayLeftTurnLanes.png|thumb|right|Center two-way turn lane: Separate turn lane if a left is allowed; no turn lane if left is not allowed.]]<br />
Many two-way streets have a center lane marked as a two-way left turn lane (TWLTL), also known as a ‘suicide lane’ or ‘chicken lane’. In the US, this lane is bordered on either side by two yellow lines - the inner line is broken or dashed, the outer line is solid. Pavement marking arrows may or may not be present. Where lane guidance is applied and the left turn lane is possible, these should be marked as separate left-turn lanes.<br />
==== HOV or other restricted lanes ====<br />
HOV (high-occupancy vehicle) restrictions or vehicle restrictions may sometimes only apply to a portion of the roadway. Only include these restricted lanes in lane guidance if they are available to users on the segment in question. In the example below, the bus lane allows for right turning vehicles to use the lane, so it is included in lane guidance. <br />
<gallery><br />
File:Lanes_HOVcount.png|HOV lanes that are on the same segment (not physically separated) should be included in lanes. <br />
File:Lanes_BusResticted.png|Bus, bike, or other restricted lanes should be included. In this case, right turns are allowed from the bus lane, so it is shown as a right turn lane. <br />
File:Lanes_CenterBus.png|In this case, the bus lane (red, center) is the only lane that proceeds straight ahead. It should be included, as it will be shown (though faded) to drivers when they are directed using the outside lanes to turn left or right. <br />
File:Lanes_Choices3.png|The HOV lane is clearly visible to all traffic, and would be considered by most drivers to be a lane, it should be included in the count of lanes at the segments ending at the exit.<br />
</gallery><br />
<br />
=== When to map lanes ===<br />
Generally, lanes should be mapped where there is more than one lane and only a subset of the lanes is available for turns. Also lanes should be mapped in potentially confusing locations where lane guidance can significantly improve safety and the driver experience.<br />
==== When the driver needs to choose the correct lane ====<br />
[[File:Lanes DriversChoice.png|thumb|right]] Any time there are two or more lanes AND an instruction is given at the node. In the example below, the street running east/west has only two lanes in either direction, but only one of those lanes may turn south onto the side street. Lane guidance should be added.<br clear=all><br />
==== To clarify which road to take ====<br />
Before now, Waze could not show the driver the difference between slight, 90°, and sharp turns. Without lanes, intersections with multiple right or multiple left turns could be confusing to drivers. Lane guidance can clear up this confusion by showing drivers whether to take, for example, the slight turn or the sharp turn.<br />
{{mbox | text = This situation is generally the only place where it is useful to add lanes where there is only one lane in the relevant direction of travel.}}<br />
<gallery>File:Lanes_Choices.png|example 1<br />
File:Lanes_Choices2.png|example 2</gallery><br />
==== When the driver needs reinforcement or reassurance for safety ====<br />
[[File:Lanes_Reassurance.png|thumb|right|For this freeway off-ramp onto a one-way roadway, reinforce “no left turn”; either lane is fine.]]<br />
There are some cases where lanes should be added to reassure drivers that they need not switch lanes, or that they may not turn from the lane they are in. In the example below, both lanes of the highway off-ramp must turn right — drivers have no choice. Lane guidance should be added to reassure drivers in the left lane that they need not change lanes and to reinforce the prohibition on the left turn to reduce the chance of them making a wrong-way turn.<br />
<br />
=== When not to map lanes ===<br />
==== When drivers have no choice ====<br />
[[File:Nolanessimple.png|150px|thumb|right|Suburban local streets typically don't have multiple lanes, and don't need lane guidance.]] Generally, don’t add lanes when there is only one lane, or at a node where no instruction is to be given. An exception to this general rule is at confusing intersections and interchanges where the driver needs reassurance that a lane change will not be necessary before the next turn or exit maneuver, or reinforcement that what might look like a valid turn is not allowed (see the reinforcement and reassurance example above).<br clear=all><br />
<br />
==== Merges and new lanes ====<br />
Waze does not offer lane guidance for a reduction in the number of lanes.<br />
[[File:MergeLanes.png|left|frame|Lane guidance is not appropriate for freeway lane reductions that do not occur near an interchange]]<br clear=all><br />
=== How Waze selects 'Waze Selected' lane arrows ===<br />
Waze Selected lane arrows are displayed for us both in the edit dialog (to the left of the checkboxes for each outbound segment) and in the Lanes pane (once changes are applied).{{Collapsible section top|expand=no}}<br />
''Expand for more information...''{{Collapsible section content}}<br />
The determination is mostly simple and mostly based on angles. Consider there is a pizza pie on the map. Cutting the pizza pie into 8 slices, outbound segments in the top slice (i.e., turn angles from 0° up to 22.5° either way) might show straight, slight left, or slight right depending on context; the top-left and top-right slice (i.e., turn angles from 22.5° to 67.5° either way) will show slight left or slight right arrows; the left slice and right slice (between 67.5° and 112.5°) will have regular turn left or turn right arrows; and the bottom 3 slices (between 112.5° and 180°) will have sharp left/sharp right arrows. Capische? Mamma mia.<br />
Regarding the top slice, when there is only one outbound segment within the <22.5° slice, that segment will get the “straight” arrows. However, if multiple segments exist within this slice, some form of the “best continuation” analysis is used to determine which one gets the straight arrow, and other arrows in that slice get slight left or slight right arrows. If there is no “best continuation”, then the segment that is closer to 0° gets the straight arrow, and the other one(s)]]<br />
{{Collapsible section bottom}}<br />
=== When to override lane arrows ===<br />
See [[#How Waze selects 'Waze Selected' lane arrows|How Waze selects lane arrows]] for information on the default turn arrows.<br />
<br />
Always review the lane arrows displayed in the Lanes pane carefully once you have applied your edits. Use override when it makes sense to do so, and leave the “Waze selected” setting in place otherwise. Do what makes sense to the person in the driver’s seat—choose the arrow which is going to make the most sense to the driver based on what they are going to have to do (continue straight, U turn, slight right, etc.) and what they are going to see as they approach the intersection or interchange where they need to make the maneuver.<br />
<br />
This does not necessarily mean that the lane arrows should be forced to match the instruction—for example, there are times when a "keep left" instruction is best paired with "straight" arrows, or when a "turn right" instruction is paired with a slight right arrow. The lane arrows should be set according to how a driver would perceive the lane configuration, but the audio guidance should reflect the action to be taken.<br />
<br />
When you change the arrow associated with one outgoing segment, check the remaining segments. In most situations, no two outgoing segments should use the same arrow.<br />
==== When more than one outbound segment have the same 'Waze selected' arrow ====<br />
Change one or more of them in a way that makes sense.<br />
==== Where segment geometry doesn’t match reality ====<br />
[[File:Lanes Override2.png|150px|thumb]]This happens in some locations because Waze road segment width does not match the real life road width. This can result in turn angles on the map which are somewhat different from the true turn angle. Lane arrow override may be necessary.<br clear=all><br />
<br />
==== Where the Waze selected arrow doesn't match reality ====<br />
Even in areas with very high quality maps, the Waze arrow selection mechanism can create arrow configurations which are confusing to the driver. This is particularly likely at nodes where there are multiple outbound segments essentially straight ahead (within a couple dozen degrees either way) from the inbound segment.<br />
These potentially-confusing generated arrows are most often found at ramp splits, wayfinders, and forks in the road, discussed in the section immediately below.<br />
<br />
However, these situations occur in other places as well. For example, in situations where a main road veers off in one direction, and a side road continues straight ahead, the Waze selected arrows will sometimes give straight-ahead arrows to the continuation of the main road, and a “slight turn” arrow to the straight-ahead side road. This does not make sense from a driver’s perspective. In such cases, use lane angle overrides to achieve the desired result.<br />
<br />
[[File:Jeff-sv sm.jpg|400px|frameless|left]] [[File:Jeff-sat sm.jpg|400px|frameless|right]]<br clear=all><br />
<big>In this example, the continuing road veers left, while the side road exits straight ahead. Both street level and overhead imagery clearly shows the driver's perspective and the need for adjustments.</big> <br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Waze selected arrows do not match reality.'''<br />
| style="width: 50%; text-align:center" | '''Use lane angle overrides to create reality.'''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:Jeff-no.png|300px|frameless]]<br />
| style="width: 50%; text-align:center" | [[File:Jeff-yes.png|300px|frameless]]<br />
|}<br />
<br />
==== Ramp splits, wayfinders, and forks in the road ====<br />
Sometimes the Waze selected lane arrows are the best choice and sometimes they are not. Look at both overhead and street views to consider what makes the most sense from the driver’s perspective. Given the processes by which Waze selects the “Waze selected” selection, sometimes the “Waze selected” straight-ahead arrow does not match well with the actual geometry of a junction. <br><br />
<br />
Generally, only one outbound segment (if any) should have the “straight” arrow. If both outbound segments at a split or wayfinder take you down an equally-straight or equally-not straight path (whether immediately or foreseeably ahead), then neither should use the straight arrow. If one of the outbound segments leads to a straighter path than the other, however, then that one should have the straight arrow. If this is already happening, great. If not, use lane override to make it happen (and to ensure that the other path doesn’t keep it).<br />
<br />
== Adding lanes to the map ==<br />
Before adding lane information, check both aerial and street view to make sure how many lanes there are on the segment at the node(s) where you are about to add lanes. See [[#What counts as a lane?|What counts as a lane?]] for more.<br />
{{mbox | type = warning | text = {{As of|2020|04|27}} the lanes tab shows when a segment is selected at zoom level 4 (500 ft) or closer. If you don’t see the tab, try zooming and panning until it shows. The node you are editing must also be in the window.}}<br />
=== Adding lanes to a segment ===<br />
1. Select the segment to which you would like to add lanes.<br />
2. In the left pane, click the Lanes tab.[[File:Lanes tab.png|thumb|center|300px|The lanes tab appears in the left pane]]<br />
3. For two-way segments, ensure you are editing the correct end of the segment. The “B” end (for A-to-B traffic) will show first, followed by the “A” end (for B-to-A traffic). The text at the top of each ‘end’ will describe the directionality of the lanes below. [[File:Lanes tab2.png|300px|thumb|center|For two-way segments, there is a section for each direction of lanes]]<br />
4. Click "Add lane guidance". [[File:Lanes_AddLaneGuidance.png|300px|thumb|center|For two-way segments, there is a section for each direction of lanes]]<br />
5. Enter the number of lanes (NOT the number of possible directions). Use the number of lanes that connect to the next segment, even if there are a different number of lanes at some other point on the segment. See the [[#What counts as a lane?|What counts as a lane?]] section above for more information.[[File:Lanes_NumberOf.png|300px|thumb|center|Count the numbers of lanes at the end of the segment.]]<br />
6. Use the checkboxes to assign the available lanes for each outbound movement. Confirm using street-level imagery, where available. Note that the same lane may be used for more than one movement (e.g., the right lane may be used for both continuing and right-turning traffic).[[File:Lanes_Checkbox1.png|300px|thumb|left|Each lane is dedicated to a specific movement.]][[File:Lanes_Checkbox2.png|300px|thumb|right|The right lane is shared for continuing and turning traffic.]]<br clear=all><br />
7. Click Apply, then save your changes when you are ready. Changes will go live in the app after the next map tile update. <br />
{{mbox|text=Mousing-over the turn arrow in the lanes panel will<br><br />
highlight that turn arrow on the map.|imageright=[[File:WME_LG_Arrow_Highlight.png|thumb|100px]]}}<br />
<br />
=== Editing existing lanes ===<br />
Editing existing Lane Guidance for a segment is done similarly to adding the lanes for the first time:<br><br />
1. Select the segment.<br><br />
2. In the left pane, click the Lanes tab.<br><br />
3. Click "Edit lane guidance" to bring up the Lane Guidance editing console.[[File:Lanes Edit.png|300px|thumb|center|Click 'Edit lane guidance']]<br clear=all><br />
<br />
=== Lane errors ===<br />
[[File:Lanes error.png|150px|thumb|right]] If lane data is incomplete, or has been corrupted due to edits on connected segments, then an error alert symbol will appear on the affected segment and on the Lanes tab when the segment is selected.<br clear=all><br />
=== Overriding a turn angle {{Anchor|Overriding a turn angle|Turn angle override|TAO}} === <br />
[[File:Lanes Override3.png|100px|thumb|right|Turn angle override controls]] In some cases, the displayed turn angle may need to be adjusted. Rather than adjusting the geometry of the road segments, an override function is available in the Lanes tab. <br />
# Click the segment.<br />
# In the left pane, click the Lanes tab.<br />
# Click “Edit lane guidance”.<br />
# Click the given turn angle icon under the TURNS header to open the Override turn angle menu. <br />
# Select a new turn angle, or the ‘Waze selected’ angle. <br clear=all><br />
=== Junction Boxes ===<br />
Lane information can be added to segments which are part of a [[Junction Box]] just as they can be added to any other segment. In order for lane guidance to work, all turn arrows on the segments underlying a Junction Box must be green (unrestricted) '''if''' they are on a route allowed by the overlaid Junction Box. Use the Junction Box itself to restrict any necessary routes.<br />
{{mbox | type = warning | text = If a junction box uses a [[turn instruction override]] to override the Waze-selected turn instructions along one of the junction box routes, then the underlying lane data may not be displayed in the app.}}<br />
<br />
=== Lanes on divided roadways {{Anchor|Lanes on divided roadways|'H' and '#' intersections}} ===<br />
At intersections where one or both roads are divided, lanes cannot always be added directly.<br><br />
<br />
Many such intersections can be classified as either “H” intersections (where only one road is divided) or “#” intersections (where both roads are divided).<br><br />
{{mbox|text=On the divided roadway approaches to an “H” intersection, lanes can be added directly to the segments.}}<br />
For some “#” intersections, and on the undivided roadway approaches to some “H” intersections, Waze can combine lane guidance information from more than one segment into a single set of lanes that includes both left and right turns, as the driver expects. {{Anchor|divided roadway criteria}} This will only be possible if all of these conditions are met:<br />
# Both left and right turns are possible at the intersection;<br />
# The two portions of the divided roadway are essentially parallel to each other;<br />
# The two intersecting roads are more or less perpendicular to each other;<br />
# The median segment in question is 50 m or shorter; and<br />
# The number of lanes entering the intersection is equal to the total number of lanes exiting the intersection (total number of lanes exiting intersection = number of lanes on the median segment + number of right-turn only lanes on the entry segment—in other words, no new lanes are added in the median).<br />
If these conditions are met, then follow the guidance in the [[#Mapping lanes on divided roadways|next section]] to add lane information.<br />
{{mbox|text=The purpose of the heuristics is to combine left turn, straight, and right turn arrows into a single lane set. At intersections where either left turns or right turns are disallowed, lanes can be added directly, and heuristics are not needed—in other words, there is no need to add “straight only” lane information. In the example below, right-turning traffic will get the full set of lanes from the entry segment; adding lanes to the median segment would serve no purpose. <br><br />
[[File:LanesMedianNA1.png|frameless|300px]] [[File:LanesMedianNA2.png|frameless|300px]]<br />
}}<br />
{{mbox<br />
| type = important<br />
| text = One side effect of the H/# heuristics is that in many cases the server will identify 'turn left, then turn left' movements across a H/# intersection (when they are not prohibited by [[Junction_Style_Guide/Intersections#Avoiding_U_turns|the U-turn prevention algorithm]]) as a U-turn, and display the U-turn lane guidance arrow in the app. In addition to the visual display of the U-turn arrow, the app's voice turn-by-turn instructions will vocalize the movement as a u-turn. <br />
}}<br />
==== Mapping lanes on divided roadways ====<br />
===== Hash intersections =====<br />
[[File:Median-entry.jpg|300px|thumb|right|Entry and Median Segments (for each direction of travel)]]<br />
First, make sure that the intersection and the turn you are mapping for meet the [[#divided roadway criteria|guidelines above]]. Handle one direction of travel at a time.<br><br />
<br />
For each direction of travel, lanes must be mapped on two segments: the “entry segment” (immediately before the median) and the “median segment” (within the median). ''See the adjacent figure. ''<br />
# On the entry segment, include the total number of lanes entering the segment.<br />
## Any lane that can be used to either turn left or continue straight should be mapped as a continuing straight lane.<br />
## Right turn lanes should be mapped as normal.<br />
# On the median segment, include the total number of lanes on the median segment (which should equal the number of lanes on the entry segment minus the number of right turn only lanes).<br clear=all><br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Entry segment: '''<br />
| style="width: 50%; text-align:center" | '''Median segment: '''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:Lanes_entry.png|350px|frameless]]<br />
| style="width: 50%; text-align:center" | [[File:Lanes_median.png|350px|frameless]]<br />
|}<br />
The heuristic in the routing server will combine these two sets of lanes together and provide a single set for drivers making either left or right turns. Unfortunately, there is no way to visualize the result in WME.<br><br />
<br />
'''<big>Lanes resulting from heuristics:</big>'''<br />
[[File:Lanes result.png|224px|frameless|left]]<br clear=all><br />
===== H Intersections =====<br />
The same heuristic applies to the undivided road side of an H junction. No heuristic is necessary for the divided road side.<br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Undivided road side:'''<br />
| style="width: 50%; text-align:center" | '''Divided road side:'''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:LanesH1.png|350px|frameless]]<br />
| rowspan="2" style="width: 50%; text-align:center" | [[File:LanesH3.png|350px|frameless]]<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:LanesH2resubmit.png|350px|frameless]]<br />
| style="width: 50%; text-align:center" | <br />
|}<br />
{{mbox|text=The median segments of # and H junctions is a rare instance where, on occasion, it is proper to add “1 lane” to a segment. This will be necessary any time there are multiple lanes on the entry segment but only one lane remaining on the median segment (because any other lane was right turn only).<br><br />
[[File:LanesHBox1resubmit.png|frameless|300px]] [[File:LanesHBox2.png|frameless|300px]]<br />
}}<br />
===== Checking your work =====<br />
There are a few things you can do to double-check your work on divided-roadway intersections that need to be mapped with heuristics.<br />
# The total number of lanes on the entry segment should equal the total number of lanes at the intersection:<br />
#* total lanes (intersection) = total lanes (entry)<br />
# The total number of lanes on the median segment should equal the difference between the total number of lanes on the entry segment and the number of right-turn only lanes on the entry segment:<br />
#* total lanes (median) = total lanes (entry) – right turn only lanes (entry)<br />
# The number of straight-ahead lanes on the entry segment (i.e., the number of boxes checked for the straight-ahead movement) should equal the total number of lanes on the median segment:<br />
#* straight-ahead lanes (entry) = total lanes (median)<br />
If these conditions are not met, the heuristic method may not function as expected, and it is best to leave lanes off for the time being.</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=Lanes&diff=172692Lanes2020-05-30T20:44:49Z<p>Tonestertm: /* Junction Boxes */ typo: an -> a</p>
<hr />
<div>{{construction | contact = https://www.waze.com/forum/viewtopic.php?f=1636&t=301141 | contacttype = forum | draft = no | open = no | revision = no | section = no | talk = no}}<br />
Lane guidance is a new Waze app feature that shows the user exactly which lanes they should use to make their next movement. This feature boosts Wazer confidence by providing reassurance in junctions both typical and unusual. <br />
Lane guidance data is added via the [[Waze Map Editor|Waze Map Editor (WME)]]. When a single segment is selected in the WME, an additional tab called Lanes is available in the left pane. The Lanes tab allows map editors to tell Waze which lane to display to the driver for lane guidance in the mobile app. <br><br />
<br />
There are some important considerations regarding lane guidance in Waze:<br />
* '''Lane guidance does not affect routing''' - it is merely a visual feature.<br />
* '''Lane guidance does not affect audio instructions''', with the exception of u-turn instructions resulting from [[#Lanes_on_divided_roadways|heuristics for intersections on divided roads]].<br />
* '''Lane guidance will only be displayed when a navigation instruction is given.''' If the [[How_Waze_determines_turn_/_keep_/_exit_maneuvers#Best_Continuation|best continuation]] is straight ahead, lane guidance will not be shown, unless there is a [[Turn_instruction_override|continue straight TIO]].<br />
{{mbox | type = protection | text = {{As of|2020|05|28}} the Lanes tab is only visible in the WME to [[Editing restrictions|rank 3 editors]] and lane guidance in the App is only visible to beta testers.}}<br />
{{mbox| type = caution| text = {{As of|2020|05|30}} the lane mapping feature of WME and the lane guidance feature of the mobile app are both still under development. Please check this guide frequently for updates to features and guidance.}}<br />
== Mapping guidance ==<br />
=== What counts as a lane? ===<br />
'''Q: How many lanes should you map at the end of a segment? What counts as a lane?'''<br><br />
'''A: Map any lane that achieves full and consistent width BEFORE the turn itself.''' For a freeway exit lane, this means a lane that is full width BEFORE [https://mutcd.fhwa.dot.gov/HTM/2003/part3/fig3b-08-1_longdesc.htm the gore point]. If someone travelling in the right lane can continue straight without changing lanes, then map this as a straight/turn lane. <br><br />
Consider what the road looks like to a driver - make the number of lanes in the lane guidance display conform to what the driver will see.<br />
==== Freeway exits and other ramps ====<br />
'''<big>Example 1: Not a Separate Lane</big>'''[[File:NotALane2.png|880px|The exit lane does not reach full width until the gore point; map as part of the rightmost continue-straight lane]]<br />
The exit lane does not reach full width until the gore point; map as part of the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 2: Not a Separate Lane</big>'''[[File:NotALane3.png|880px|The exit lane does not reach full width until the gore point; mapped as part of the rightmost continue-straight lane.]]<br />
The exit lane does not reach full width until the gore point; mapped as part of the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 3: Separate Lane</big>'''[[File:SeperateLane2.png|880px|When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.]]<br />
When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 4: Separate Lane</big>'''[[File:SeperateLane1.png|880px|When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.]]<br />
When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.<br />
==== Center two-way left-turn lanes ====<br />
[[File:TwoWayLeftTurnLanes.png|thumb|right|Center two-way turn lane: Separate turn lane if a left is allowed; no turn lane if left is not allowed.]]<br />
Many two-way streets have a center lane marked as a two-way left turn lane (TWLTL), also known as a ‘suicide lane’ or ‘chicken lane’. In the US, this lane is bordered on either side by two yellow lines - the inner line is broken or dashed, the outer line is solid. Pavement marking arrows may or may not be present. Where lane guidance is applied and the left turn lane is possible, these should be marked as separate left-turn lanes.<br />
==== HOV or other restricted lanes ====<br />
HOV (high-occupancy vehicle) restrictions or vehicle restrictions may sometimes only apply to a portion of the roadway. Only include these restricted lanes in lane guidance if they are available to users on the segment in question. In the example below, the bus lane allows for right turning vehicles to use the lane, so it is included in lane guidance. <br />
<gallery><br />
File:Lanes_HOVcount.png|HOV lanes that are on the same segment (not physically separated) should be included in lanes. <br />
File:Lanes_BusResticted.png|Bus, bike, or other restricted lanes should be included. In this case, right turns are allowed from the bus lane, so it is shown as a right turn lane. <br />
File:Lanes_CenterBus.png|In this case, the bus lane (red, center) is the only lane that proceeds straight ahead. It should be included, as it will be shown (though faded) to drivers when they are directed using the outside lanes to turn left or right. <br />
File:Lanes_Choices3.png|The HOV lane is clearly visible to all traffic, and would be considered by most drivers to be a lane, it should be included in the count of lanes at the segments ending at the exit.<br />
</gallery><br />
<br />
=== When to map lanes ===<br />
Generally, lanes should be mapped where there is more than one lane and only a subset of the lanes is available for turns. Also lanes should be mapped in potentially confusing locations where lane guidance can significantly improve safety and the driver experience.<br />
==== When the driver needs to choose the correct lane ====<br />
[[File:Lanes DriversChoice.png|thumb|right]] Any time there are two or more lanes AND an instruction is given at the node. In the example below, the street running east/west has only two lanes in either direction, but only one of those lanes may turn south onto the side street. Lane guidance should be added.<br clear=all><br />
==== To clarify which road to take ====<br />
Before now, Waze could not show the driver the difference between slight, 90°, and sharp turns. Without lanes, intersections with multiple right or multiple left turns could be confusing to drivers. Lane guidance can clear up this confusion by showing drivers whether to take, for example, the slight turn or the sharp turn.<br />
{{mbox | text = This situation is generally the only place where it is useful to add lanes where there is only one lane in the relevant direction of travel.}}<br />
<gallery>File:Lanes_Choices.png|example 1<br />
File:Lanes_Choices2.png|example 2</gallery><br />
==== When the driver needs reinforcement or reassurance for safety ====<br />
[[File:Lanes_Reassurance.png|thumb|right|For this freeway off-ramp onto a one-way roadway, reinforce “no left turn”; either lane is fine.]]<br />
There are some cases where lanes should be added to reassure drivers that they need not switch lanes, or that they may not turn from the lane they are in. In the example below, both lanes of the highway off-ramp must turn right — drivers have no choice. Lane guidance should be added to reassure drivers in the left lane that they need not change lanes and to reinforce the prohibition on the left turn to reduce the chance of them making a wrong-way turn.<br />
<br />
=== When not to map lanes ===<br />
==== When drivers have no choice ====<br />
[[File:Nolanessimple.png|150px|thumb|right|Suburban local streets typically don't have multiple lanes, and don't need lane guidance.]] Generally, don’t add lanes when there is only one lane, or at a node where no instruction is to be given. An exception to this general rule is at confusing intersections and interchanges where the driver needs reassurance that a lane change will not be necessary before the next turn or exit maneuver, or reinforcement that what might look like a valid turn is not allowed (see the reinforcement and reassurance example above).<br clear=all><br />
<br />
==== Merges and new lanes ====<br />
Waze does not offer lane guidance for a reduction in the number of lanes.<br />
[[File:MergeLanes.png|left|frame|Lane guidance is not appropriate for freeway lane reductions that do not occur near an interchange]]<br clear=all><br />
=== How Waze selects 'Waze Selected' lane arrows ===<br />
Waze Selected lane arrows are displayed for us both in the edit dialog (to the left of the checkboxes for each outbound segment) and in the Lanes pane (once changes are applied).{{Collapsible section top|expand=no}}<br />
''Expand for more information...''{{Collapsible section content}}<br />
The determination is mostly simple and mostly based on angles. Consider there is a pizza pie on the map. Cutting the pizza pie into 8 slices, outbound segments in the top slice (i.e., turn angles from 0° up to 22.5° either way) might show straight, slight left, or slight right depending on context; the top-left and top-right slice (i.e., turn angles from 22.5° to 67.5° either way) will show slight left or slight right arrows; the left slice and right slice (between 67.5° and 112.5°) will have regular turn left or turn right arrows; and the bottom 3 slices (between 112.5° and 180°) will have sharp left/sharp right arrows. Capische? Mamma mia.<br />
Regarding the top slice, when there is only one outbound segment within the <22.5° slice, that segment will get the “straight” arrows. However, if multiple segments exist within this slice, some form of the “best continuation” analysis is used to determine which one gets the straight arrow, and other arrows in that slice get slight left or slight right arrows. If there is no “best continuation”, then the segment that is closer to 0° gets the straight arrow, and the other one(s)]]<br />
{{Collapsible section bottom}}<br />
=== When to override lane arrows ===<br />
See [[#How Waze selects 'Waze Selected' lane arrows|How Waze selects lane arrows]] for information on the default turn arrows.<br />
<br />
Always review the lane arrows displayed in the Lanes pane carefully once you have applied your edits. Use override when it makes sense to do so, and leave the “Waze selected” setting in place otherwise. Do what makes sense to the person in the driver’s seat—choose the arrow which is going to make the most sense to the driver based on what they are going to have to do (continue straight, U turn, slight right, etc.) and what they are going to see as they approach the intersection or interchange where they need to make the maneuver.<br />
<br />
This does not necessarily mean that the lane arrows should be forced to match the instruction—for example, there are times when a "keep left" instruction is best paired with "straight" arrows, or when a "turn right" instruction is paired with a slight right arrow. The lane arrows should be set according to how a driver would perceive the lane configuration, but the audio guidance should reflect the action to be taken.<br />
<br />
When you change the arrow associated with one outgoing segment, check the remaining segments. In most situations, no two outgoing segments should use the same arrow.<br />
==== When more than one outbound segment have the same 'Waze selected' arrow ====<br />
Change one or more of them in a way that makes sense.<br />
==== Where segment geometry doesn’t match reality ====<br />
[[File:Lanes Override2.png|150px|thumb]]This happens in some locations because Waze road segment width does not match the real life road width. This can result in turn angles on the map which are somewhat different from the true turn angle. Lane arrow override may be necessary.<br clear=all><br />
<br />
==== Where the Waze selected arrow doesn't match reality ====<br />
Even in areas with very high quality maps, the Waze arrow selection mechanism can create arrow configurations which are confusing to the driver. This is particularly likely at nodes where there are multiple outbound segments essentially straight ahead (within a couple dozen degrees either way) from the inbound segment.<br />
These potentially-confusing generated arrows are most often found at ramp splits, wayfinders, and forks in the road, discussed in the section immediately below.<br />
<br />
However, these situations occur in other places as well. For example, in situations where a main road veers off in one direction, and a side road continues straight ahead, the Waze selected arrows will sometimes give straight-ahead arrows to the continuation of the main road, and a “slight turn” arrow to the straight-ahead side road. This does not make sense from a driver’s perspective. In such cases, use lane angle overrides to achieve the desired result.<br />
<br />
[[File:Jeff-sv sm.jpg|400px|frameless|left]] [[File:Jeff-sat sm.jpg|400px|frameless|right]]<br clear=all><br />
<big>In this example, the continuing road veers left, while the side road exits straight ahead. Both street level and overhead imagery clearly shows the driver's perspective and the need for adjustments.</big> <br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Waze selected arrows do not match reality.'''<br />
| style="width: 50%; text-align:center" | '''Use lane angle overrides to create reality.'''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:Jeff-no.png|300px|frameless]]<br />
| style="width: 50%; text-align:center" | [[File:Jeff-yes.png|300px|frameless]]<br />
|}<br />
<br />
==== Ramp splits, wayfinders, and forks in the road ====<br />
Sometimes the Waze selected lane arrows are the best choice and sometimes they are not. Look at both overhead and street views to consider what makes the most sense from the driver’s perspective. Given the processes by which Waze selects the “Waze selected” selection, sometimes the “Waze selected” straight-ahead arrow does not match well with the actual geometry of a junction. <br><br />
<br />
Generally, only one outbound segment (if any) should have the “straight” arrow. If both outbound segments at a split or wayfinder take you down an equally-straight or equally-not straight path (whether immediately or foreseeably ahead), then neither should use the straight arrow. If one of the outbound segments leads to a straighter path than the other, however, then that one should have the straight arrow. If this is already happening, great. If not, use lane override to make it happen (and to ensure that the other path doesn’t keep it).<br />
<br />
== Adding lanes to the map ==<br />
Before adding lane information, check both aerial and street view to make sure how many lanes there are on the segment at the node(s) where you are about to add lanes. See [[#What counts as a lane?|What counts as a lane?]] for more.<br />
{{mbox | type = warning | text = {{As of|2020|04|27}} the lanes tab shows when a segment is selected at zoom level 4 (500 ft) or closer. If you don’t see the tab, try zooming and panning until it shows. The node you are editing must also be in the window.}}<br />
=== Adding lanes to a segment ===<br />
1. Select the segment to which you would like to add lanes.<br />
2. In the left pane, click the Lanes tab.[[File:Lanes tab.png|thumb|center|300px|The lanes tab appears in the left pane]]<br />
3. For two-way segments, ensure you are editing the correct end of the segment. The “B” end (for A-to-B traffic) will show first, followed by the “A” end (for B-to-A traffic). The text at the top of each ‘end’ will describe the directionality of the lanes below. [[File:Lanes tab2.png|300px|thumb|center|For two-way segments, there is a section for each direction of lanes]]<br />
4. Click "Add lane guidance". [[File:Lanes_AddLaneGuidance.png|300px|thumb|center|For two-way segments, there is a section for each direction of lanes]]<br />
5. Enter the number of lanes (NOT the number of possible directions). Use the number of lanes that connect to the next segment, even if there are a different number of lanes at some other point on the segment. See the [[#What counts as a lane?|What counts as a lane?]] section above for more information.[[File:Lanes_NumberOf.png|300px|thumb|center|Count the numbers of lanes at the end of the segment.]]<br />
6. Use the checkboxes to assign the available lanes for each outbound movement. Confirm using street-level imagery, where available. Note that the same lane may be used for more than one movement (e.g., the right lane may be used for both continuing and right-turning traffic).[[File:Lanes_Checkbox1.png|300px|thumb|left|Each lane is dedicated to a specific movement.]][[File:Lanes_Checkbox2.png|300px|thumb|right|The right lane is shared for continuing and turning traffic.]]<br clear=all><br />
7. Click Apply, then save your changes when you are ready. Changes will go live in the app after the next map tile update. <br />
{{mbox|text=Mousing-over the turn arrow in the lanes panel will<br><br />
highlight that turn arrow on the map.|imageright=[[File:WME_LG_Arrow_Highlight.png|thumb|100px]]}}<br />
<br />
=== Editing existing lanes ===<br />
Editing existing Lane Guidance for a segment is done similarly to adding the lanes for the first time:<br><br />
1. Select the segment.<br><br />
2. In the left pane, click the Lanes tab.<br><br />
3. Click "Edit lane guidance" to bring up the Lane Guidance editing console.[[File:Lanes Edit.png|300px|thumb|center|Click 'Edit lane guidance']]<br clear=all><br />
<br />
=== Lane errors ===<br />
[[File:Lanes error.png|150px|thumb|right]] If lane data is incomplete, or has been corrupted due to edits on connected segments, then an error alert symbol will appear on the affected segment and on the Lanes tab when the segment is selected.<br clear=all><br />
=== Overriding a turn angle {{Anchor|Overriding a turn angle|Turn angle override|TAO}} === <br />
[[File:Lanes Override3.png|100px|thumb|right|Turn angle override controls]] In some cases, the displayed turn angle may need to be adjusted. Rather than adjusting the geometry of the road segments, an override function is available in the Lanes tab. <br />
# Click the segment.<br />
# In the left pane, click the Lanes tab.<br />
# Click “Edit lane guidance”.<br />
# Click the given turn angle icon under the TURNS header to open the Override turn angle menu. <br />
# Select a new turn angle, or the ‘Waze selected’ angle. <br clear=all><br />
=== Junction Boxes ===<br />
Lane information can be added to segments which are part of a [[Junction Box]] just as they can be added to any other segment. In order for lane guidance to work, all turn arrows on the segments underlying a Junction Box must be green (unrestricted) '''if''' they are on a route allowed by the overlaid Junction Box. Use the Junction Box itself to restrict any necessary routes.<br />
{{mbox | type = warning | text = If a junction box uses a [[turn instruction override]] to override the Waze-selected turn instructions along one of the junction box routes, then the underlying lane data may not be displayed in the app.}}<br />
<br />
=== Lanes on divided roadways {{Anchor|Lanes on divided roadways|'H' and '#' intersections}} ===<br />
At intersections where one or both roads are divided, lanes cannot always be added directly.<br><br />
<br />
Many such intersections can be classified as either “H” intersections (where only one road is divided) or “#” intersections (where both roads are divided).<br><br />
{{mbox|text=On the divided roadway approaches to an “H” intersection, lanes can be added directly to the segments.}}<br />
For some “#” intersections, and on the undivided roadway approaches to some “H” intersections, Waze can combine lane guidance information from more than one segment into a single set of lanes that includes both left and right turns, as the driver expects. {{Anchor|divided roadway criteria}} This will only be possible if all of these conditions are met:<br />
# Both left and right turns are possible at the intersection;<br />
# The two portions of the divided roadway are essentially parallel to each other;<br />
# The two intersecting roads are more or less perpendicular to each other;<br />
# The median segment in question is 50 m or shorter; and<br />
# The number of lanes entering the intersection is equal to the total number of lanes exiting the intersection (total number of lanes exiting intersection = number of lanes on the median segment + number of right-turn only lanes on the entry segment—in other words, no new lanes are added in the median).<br />
If these conditions are met, then follow the guidance in the [[#Mapping lanes on divided roadways|next section]] to add lane information.<br />
{{mbox|text=The purpose of the heuristics is to combine left turn, straight, and right turn arrows into a single lane set. At intersections where either left turns or right turns are disallowed, lanes can be added directly, and heuristics are not needed—in other words, there is no need to add “straight only” lane information. In the example below, right-turning traffic will get the full set of lanes from the entry segment; adding lanes to the median segment would serve no purpose. <br><br />
[[File:LanesMedianNA1.png|frameless|300px]] [[File:LanesMedianNA2.png|frameless|300px]]<br />
}}<br />
{{mbox<br />
| type = important<br />
| text = One side effect of the H/# heuristics is that in many cases the server will identify 'turn left, then turn left' movements across a H/# intersection (which are not prohibited by [[Junction_Style_Guide/Intersections#Avoiding_U_turns|the U-turn prevention algorithm]]) as a U-turn, and display the U-turn lane guidance arrow in the app. In addition to the visual display of the U-turn arrow, the app's voice turn-by-turn instructions will vocalize the movement as a u-turn. <br />
}}<br />
==== Mapping lanes on divided roadways ====<br />
===== Hash intersections =====<br />
[[File:Median-entry.jpg|300px|thumb|right|Entry and Median Segments (for each direction of travel)]]<br />
First, make sure that the intersection and the turn you are mapping for meet the [[#divided roadway criteria|guidelines above]]. Handle one direction of travel at a time.<br><br />
<br />
For each direction of travel, lanes must be mapped on two segments: the “entry segment” (immediately before the median) and the “median segment” (within the median). ''See the adjacent figure. ''<br />
# On the entry segment, include the total number of lanes entering the segment.<br />
## Any lane that can be used to either turn left or continue straight should be mapped as a continuing straight lane.<br />
## Right turn lanes should be mapped as normal.<br />
# On the median segment, include the total number of lanes on the median segment (which should equal the number of lanes on the entry segment minus the number of right turn only lanes).<br clear=all><br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Entry segment: '''<br />
| style="width: 50%; text-align:center" | '''Median segment: '''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:Lanes_entry.png|350px|frameless]]<br />
| style="width: 50%; text-align:center" | [[File:Lanes_median.png|350px|frameless]]<br />
|}<br />
The heuristic in the routing server will combine these two sets of lanes together and provide a single set for drivers making either left or right turns. Unfortunately, there is no way to visualize the result in WME.<br><br />
<br />
'''<big>Lanes resulting from heuristics:</big>'''<br />
[[File:Lanes result.png|224px|frameless|left]]<br clear=all><br />
===== H Intersections =====<br />
The same heuristic applies to the undivided road side of an H junction. No heuristic is necessary for the divided road side.<br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Undivided road side:'''<br />
| style="width: 50%; text-align:center" | '''Divided road side:'''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:LanesH1.png|350px|frameless]]<br />
| rowspan="2" style="width: 50%; text-align:center" | [[File:LanesH3.png|350px|frameless]]<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:LanesH2resubmit.png|350px|frameless]]<br />
| style="width: 50%; text-align:center" | <br />
|}<br />
{{mbox|text=The median segments of # and H junctions is a rare instance where, on occasion, it is proper to add “1 lane” to a segment. This will be necessary any time there are multiple lanes on the entry segment but only one lane remaining on the median segment (because any other lane was right turn only).<br><br />
[[File:LanesHBox1resubmit.png|frameless|300px]] [[File:LanesHBox2.png|frameless|300px]]<br />
}}<br />
===== Checking your work =====<br />
There are a few things you can do to double-check your work on divided-roadway intersections that need to be mapped with heuristics.<br />
# The total number of lanes on the entry segment should equal the total number of lanes at the intersection:<br />
#* total lanes (intersection) = total lanes (entry)<br />
# The total number of lanes on the median segment should equal the difference between the total number of lanes on the entry segment and the number of right-turn only lanes on the entry segment:<br />
#* total lanes (median) = total lanes (entry) – right turn only lanes (entry)<br />
# The number of straight-ahead lanes on the entry segment (i.e., the number of boxes checked for the straight-ahead movement) should equal the total number of lanes on the median segment:<br />
#* straight-ahead lanes (entry) = total lanes (median)<br />
If these conditions are not met, the heuristic method may not function as expected, and it is best to leave lanes off for the time being.</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=Lanes&diff=172691Lanes2020-05-30T20:43:05Z<p>Tonestertm: /* Editing existing lanes */ Click -> Select</p>
<hr />
<div>{{construction | contact = https://www.waze.com/forum/viewtopic.php?f=1636&t=301141 | contacttype = forum | draft = no | open = no | revision = no | section = no | talk = no}}<br />
Lane guidance is a new Waze app feature that shows the user exactly which lanes they should use to make their next movement. This feature boosts Wazer confidence by providing reassurance in junctions both typical and unusual. <br />
Lane guidance data is added via the [[Waze Map Editor|Waze Map Editor (WME)]]. When a single segment is selected in the WME, an additional tab called Lanes is available in the left pane. The Lanes tab allows map editors to tell Waze which lane to display to the driver for lane guidance in the mobile app. <br><br />
<br />
There are some important considerations regarding lane guidance in Waze:<br />
* '''Lane guidance does not affect routing''' - it is merely a visual feature.<br />
* '''Lane guidance does not affect audio instructions''', with the exception of u-turn instructions resulting from [[#Lanes_on_divided_roadways|heuristics for intersections on divided roads]].<br />
* '''Lane guidance will only be displayed when a navigation instruction is given.''' If the [[How_Waze_determines_turn_/_keep_/_exit_maneuvers#Best_Continuation|best continuation]] is straight ahead, lane guidance will not be shown, unless there is a [[Turn_instruction_override|continue straight TIO]].<br />
{{mbox | type = protection | text = {{As of|2020|05|28}} the Lanes tab is only visible in the WME to [[Editing restrictions|rank 3 editors]] and lane guidance in the App is only visible to beta testers.}}<br />
{{mbox| type = caution| text = {{As of|2020|05|30}} the lane mapping feature of WME and the lane guidance feature of the mobile app are both still under development. Please check this guide frequently for updates to features and guidance.}}<br />
== Mapping guidance ==<br />
=== What counts as a lane? ===<br />
'''Q: How many lanes should you map at the end of a segment? What counts as a lane?'''<br><br />
'''A: Map any lane that achieves full and consistent width BEFORE the turn itself.''' For a freeway exit lane, this means a lane that is full width BEFORE [https://mutcd.fhwa.dot.gov/HTM/2003/part3/fig3b-08-1_longdesc.htm the gore point]. If someone travelling in the right lane can continue straight without changing lanes, then map this as a straight/turn lane. <br><br />
Consider what the road looks like to a driver - make the number of lanes in the lane guidance display conform to what the driver will see.<br />
==== Freeway exits and other ramps ====<br />
'''<big>Example 1: Not a Separate Lane</big>'''[[File:NotALane2.png|880px|The exit lane does not reach full width until the gore point; map as part of the rightmost continue-straight lane]]<br />
The exit lane does not reach full width until the gore point; map as part of the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 2: Not a Separate Lane</big>'''[[File:NotALane3.png|880px|The exit lane does not reach full width until the gore point; mapped as part of the rightmost continue-straight lane.]]<br />
The exit lane does not reach full width until the gore point; mapped as part of the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 3: Separate Lane</big>'''[[File:SeperateLane2.png|880px|When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.]]<br />
When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 4: Separate Lane</big>'''[[File:SeperateLane1.png|880px|When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.]]<br />
When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.<br />
==== Center two-way left-turn lanes ====<br />
[[File:TwoWayLeftTurnLanes.png|thumb|right|Center two-way turn lane: Separate turn lane if a left is allowed; no turn lane if left is not allowed.]]<br />
Many two-way streets have a center lane marked as a two-way left turn lane (TWLTL), also known as a ‘suicide lane’ or ‘chicken lane’. In the US, this lane is bordered on either side by two yellow lines - the inner line is broken or dashed, the outer line is solid. Pavement marking arrows may or may not be present. Where lane guidance is applied and the left turn lane is possible, these should be marked as separate left-turn lanes.<br />
==== HOV or other restricted lanes ====<br />
HOV (high-occupancy vehicle) restrictions or vehicle restrictions may sometimes only apply to a portion of the roadway. Only include these restricted lanes in lane guidance if they are available to users on the segment in question. In the example below, the bus lane allows for right turning vehicles to use the lane, so it is included in lane guidance. <br />
<gallery><br />
File:Lanes_HOVcount.png|HOV lanes that are on the same segment (not physically separated) should be included in lanes. <br />
File:Lanes_BusResticted.png|Bus, bike, or other restricted lanes should be included. In this case, right turns are allowed from the bus lane, so it is shown as a right turn lane. <br />
File:Lanes_CenterBus.png|In this case, the bus lane (red, center) is the only lane that proceeds straight ahead. It should be included, as it will be shown (though faded) to drivers when they are directed using the outside lanes to turn left or right. <br />
File:Lanes_Choices3.png|The HOV lane is clearly visible to all traffic, and would be considered by most drivers to be a lane, it should be included in the count of lanes at the segments ending at the exit.<br />
</gallery><br />
<br />
=== When to map lanes ===<br />
Generally, lanes should be mapped where there is more than one lane and only a subset of the lanes is available for turns. Also lanes should be mapped in potentially confusing locations where lane guidance can significantly improve safety and the driver experience.<br />
==== When the driver needs to choose the correct lane ====<br />
[[File:Lanes DriversChoice.png|thumb|right]] Any time there are two or more lanes AND an instruction is given at the node. In the example below, the street running east/west has only two lanes in either direction, but only one of those lanes may turn south onto the side street. Lane guidance should be added.<br clear=all><br />
==== To clarify which road to take ====<br />
Before now, Waze could not show the driver the difference between slight, 90°, and sharp turns. Without lanes, intersections with multiple right or multiple left turns could be confusing to drivers. Lane guidance can clear up this confusion by showing drivers whether to take, for example, the slight turn or the sharp turn.<br />
{{mbox | text = This situation is generally the only place where it is useful to add lanes where there is only one lane in the relevant direction of travel.}}<br />
<gallery>File:Lanes_Choices.png|example 1<br />
File:Lanes_Choices2.png|example 2</gallery><br />
==== When the driver needs reinforcement or reassurance for safety ====<br />
[[File:Lanes_Reassurance.png|thumb|right|For this freeway off-ramp onto a one-way roadway, reinforce “no left turn”; either lane is fine.]]<br />
There are some cases where lanes should be added to reassure drivers that they need not switch lanes, or that they may not turn from the lane they are in. In the example below, both lanes of the highway off-ramp must turn right — drivers have no choice. Lane guidance should be added to reassure drivers in the left lane that they need not change lanes and to reinforce the prohibition on the left turn to reduce the chance of them making a wrong-way turn.<br />
<br />
=== When not to map lanes ===<br />
==== When drivers have no choice ====<br />
[[File:Nolanessimple.png|150px|thumb|right|Suburban local streets typically don't have multiple lanes, and don't need lane guidance.]] Generally, don’t add lanes when there is only one lane, or at a node where no instruction is to be given. An exception to this general rule is at confusing intersections and interchanges where the driver needs reassurance that a lane change will not be necessary before the next turn or exit maneuver, or reinforcement that what might look like a valid turn is not allowed (see the reinforcement and reassurance example above).<br clear=all><br />
<br />
==== Merges and new lanes ====<br />
Waze does not offer lane guidance for a reduction in the number of lanes.<br />
[[File:MergeLanes.png|left|frame|Lane guidance is not appropriate for freeway lane reductions that do not occur near an interchange]]<br clear=all><br />
=== How Waze selects 'Waze Selected' lane arrows ===<br />
Waze Selected lane arrows are displayed for us both in the edit dialog (to the left of the checkboxes for each outbound segment) and in the Lanes pane (once changes are applied).{{Collapsible section top|expand=no}}<br />
''Expand for more information...''{{Collapsible section content}}<br />
The determination is mostly simple and mostly based on angles. Consider there is a pizza pie on the map. Cutting the pizza pie into 8 slices, outbound segments in the top slice (i.e., turn angles from 0° up to 22.5° either way) might show straight, slight left, or slight right depending on context; the top-left and top-right slice (i.e., turn angles from 22.5° to 67.5° either way) will show slight left or slight right arrows; the left slice and right slice (between 67.5° and 112.5°) will have regular turn left or turn right arrows; and the bottom 3 slices (between 112.5° and 180°) will have sharp left/sharp right arrows. Capische? Mamma mia.<br />
Regarding the top slice, when there is only one outbound segment within the <22.5° slice, that segment will get the “straight” arrows. However, if multiple segments exist within this slice, some form of the “best continuation” analysis is used to determine which one gets the straight arrow, and other arrows in that slice get slight left or slight right arrows. If there is no “best continuation”, then the segment that is closer to 0° gets the straight arrow, and the other one(s)]]<br />
{{Collapsible section bottom}}<br />
=== When to override lane arrows ===<br />
See [[#How Waze selects 'Waze Selected' lane arrows|How Waze selects lane arrows]] for information on the default turn arrows.<br />
<br />
Always review the lane arrows displayed in the Lanes pane carefully once you have applied your edits. Use override when it makes sense to do so, and leave the “Waze selected” setting in place otherwise. Do what makes sense to the person in the driver’s seat—choose the arrow which is going to make the most sense to the driver based on what they are going to have to do (continue straight, U turn, slight right, etc.) and what they are going to see as they approach the intersection or interchange where they need to make the maneuver.<br />
<br />
This does not necessarily mean that the lane arrows should be forced to match the instruction—for example, there are times when a "keep left" instruction is best paired with "straight" arrows, or when a "turn right" instruction is paired with a slight right arrow. The lane arrows should be set according to how a driver would perceive the lane configuration, but the audio guidance should reflect the action to be taken.<br />
<br />
When you change the arrow associated with one outgoing segment, check the remaining segments. In most situations, no two outgoing segments should use the same arrow.<br />
==== When more than one outbound segment have the same 'Waze selected' arrow ====<br />
Change one or more of them in a way that makes sense.<br />
==== Where segment geometry doesn’t match reality ====<br />
[[File:Lanes Override2.png|150px|thumb]]This happens in some locations because Waze road segment width does not match the real life road width. This can result in turn angles on the map which are somewhat different from the true turn angle. Lane arrow override may be necessary.<br clear=all><br />
<br />
==== Where the Waze selected arrow doesn't match reality ====<br />
Even in areas with very high quality maps, the Waze arrow selection mechanism can create arrow configurations which are confusing to the driver. This is particularly likely at nodes where there are multiple outbound segments essentially straight ahead (within a couple dozen degrees either way) from the inbound segment.<br />
These potentially-confusing generated arrows are most often found at ramp splits, wayfinders, and forks in the road, discussed in the section immediately below.<br />
<br />
However, these situations occur in other places as well. For example, in situations where a main road veers off in one direction, and a side road continues straight ahead, the Waze selected arrows will sometimes give straight-ahead arrows to the continuation of the main road, and a “slight turn” arrow to the straight-ahead side road. This does not make sense from a driver’s perspective. In such cases, use lane angle overrides to achieve the desired result.<br />
<br />
[[File:Jeff-sv sm.jpg|400px|frameless|left]] [[File:Jeff-sat sm.jpg|400px|frameless|right]]<br clear=all><br />
<big>In this example, the continuing road veers left, while the side road exits straight ahead. Both street level and overhead imagery clearly shows the driver's perspective and the need for adjustments.</big> <br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Waze selected arrows do not match reality.'''<br />
| style="width: 50%; text-align:center" | '''Use lane angle overrides to create reality.'''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:Jeff-no.png|300px|frameless]]<br />
| style="width: 50%; text-align:center" | [[File:Jeff-yes.png|300px|frameless]]<br />
|}<br />
<br />
==== Ramp splits, wayfinders, and forks in the road ====<br />
Sometimes the Waze selected lane arrows are the best choice and sometimes they are not. Look at both overhead and street views to consider what makes the most sense from the driver’s perspective. Given the processes by which Waze selects the “Waze selected” selection, sometimes the “Waze selected” straight-ahead arrow does not match well with the actual geometry of a junction. <br><br />
<br />
Generally, only one outbound segment (if any) should have the “straight” arrow. If both outbound segments at a split or wayfinder take you down an equally-straight or equally-not straight path (whether immediately or foreseeably ahead), then neither should use the straight arrow. If one of the outbound segments leads to a straighter path than the other, however, then that one should have the straight arrow. If this is already happening, great. If not, use lane override to make it happen (and to ensure that the other path doesn’t keep it).<br />
<br />
== Adding lanes to the map ==<br />
Before adding lane information, check both aerial and street view to make sure how many lanes there are on the segment at the node(s) where you are about to add lanes. See [[#What counts as a lane?|What counts as a lane?]] for more.<br />
{{mbox | type = warning | text = {{As of|2020|04|27}} the lanes tab shows when a segment is selected at zoom level 4 (500 ft) or closer. If you don’t see the tab, try zooming and panning until it shows. The node you are editing must also be in the window.}}<br />
=== Adding lanes to a segment ===<br />
1. Select the segment to which you would like to add lanes.<br />
2. In the left pane, click the Lanes tab.[[File:Lanes tab.png|thumb|center|300px|The lanes tab appears in the left pane]]<br />
3. For two-way segments, ensure you are editing the correct end of the segment. The “B” end (for A-to-B traffic) will show first, followed by the “A” end (for B-to-A traffic). The text at the top of each ‘end’ will describe the directionality of the lanes below. [[File:Lanes tab2.png|300px|thumb|center|For two-way segments, there is a section for each direction of lanes]]<br />
4. Click "Add lane guidance". [[File:Lanes_AddLaneGuidance.png|300px|thumb|center|For two-way segments, there is a section for each direction of lanes]]<br />
5. Enter the number of lanes (NOT the number of possible directions). Use the number of lanes that connect to the next segment, even if there are a different number of lanes at some other point on the segment. See the [[#What counts as a lane?|What counts as a lane?]] section above for more information.[[File:Lanes_NumberOf.png|300px|thumb|center|Count the numbers of lanes at the end of the segment.]]<br />
6. Use the checkboxes to assign the available lanes for each outbound movement. Confirm using street-level imagery, where available. Note that the same lane may be used for more than one movement (e.g., the right lane may be used for both continuing and right-turning traffic).[[File:Lanes_Checkbox1.png|300px|thumb|left|Each lane is dedicated to a specific movement.]][[File:Lanes_Checkbox2.png|300px|thumb|right|The right lane is shared for continuing and turning traffic.]]<br clear=all><br />
7. Click Apply, then save your changes when you are ready. Changes will go live in the app after the next map tile update. <br />
{{mbox|text=Mousing-over the turn arrow in the lanes panel will<br><br />
highlight that turn arrow on the map.|imageright=[[File:WME_LG_Arrow_Highlight.png|thumb|100px]]}}<br />
<br />
=== Editing existing lanes ===<br />
Editing existing Lane Guidance for a segment is done similarly to adding the lanes for the first time:<br><br />
1. Select the segment.<br><br />
2. In the left pane, click the Lanes tab.<br><br />
3. Click "Edit lane guidance" to bring up the Lane Guidance editing console.[[File:Lanes Edit.png|300px|thumb|center|Click 'Edit lane guidance']]<br clear=all><br />
<br />
=== Lane errors ===<br />
[[File:Lanes error.png|150px|thumb|right]] If lane data is incomplete, or has been corrupted due to edits on connected segments, then an error alert symbol will appear on the affected segment and on the Lanes tab when the segment is selected.<br clear=all><br />
=== Overriding a turn angle {{Anchor|Overriding a turn angle|Turn angle override|TAO}} === <br />
[[File:Lanes Override3.png|100px|thumb|right|Turn angle override controls]] In some cases, the displayed turn angle may need to be adjusted. Rather than adjusting the geometry of the road segments, an override function is available in the Lanes tab. <br />
# Click the segment.<br />
# In the left pane, click the Lanes tab.<br />
# Click “Edit lane guidance”.<br />
# Click the given turn angle icon under the TURNS header to open the Override turn angle menu. <br />
# Select a new turn angle, or the ‘Waze selected’ angle. <br clear=all><br />
=== Junction Boxes ===<br />
Lane information can be added to segments which are part of a [[Junction Box]] just as they can be added to any other segment. In order for lane guidance to work, all turn arrows on the segments underlying a Junction Box must be green (unrestricted) '''if''' they are on an route allowed by the overlaid Junction Box. Use the Junction Box itself to restrict any necessary routes.<br />
{{mbox | type = warning | text = If a junction box uses a [[turn instruction override]] to override the Waze-selected turn instructions along one of the junction box routes, then the underlying lane data may not be displayed in the app.}}<br />
<br />
=== Lanes on divided roadways {{Anchor|Lanes on divided roadways|'H' and '#' intersections}} ===<br />
At intersections where one or both roads are divided, lanes cannot always be added directly.<br><br />
<br />
Many such intersections can be classified as either “H” intersections (where only one road is divided) or “#” intersections (where both roads are divided).<br><br />
{{mbox|text=On the divided roadway approaches to an “H” intersection, lanes can be added directly to the segments.}}<br />
For some “#” intersections, and on the undivided roadway approaches to some “H” intersections, Waze can combine lane guidance information from more than one segment into a single set of lanes that includes both left and right turns, as the driver expects. {{Anchor|divided roadway criteria}} This will only be possible if all of these conditions are met:<br />
# Both left and right turns are possible at the intersection;<br />
# The two portions of the divided roadway are essentially parallel to each other;<br />
# The two intersecting roads are more or less perpendicular to each other;<br />
# The median segment in question is 50 m or shorter; and<br />
# The number of lanes entering the intersection is equal to the total number of lanes exiting the intersection (total number of lanes exiting intersection = number of lanes on the median segment + number of right-turn only lanes on the entry segment—in other words, no new lanes are added in the median).<br />
If these conditions are met, then follow the guidance in the [[#Mapping lanes on divided roadways|next section]] to add lane information.<br />
{{mbox|text=The purpose of the heuristics is to combine left turn, straight, and right turn arrows into a single lane set. At intersections where either left turns or right turns are disallowed, lanes can be added directly, and heuristics are not needed—in other words, there is no need to add “straight only” lane information. In the example below, right-turning traffic will get the full set of lanes from the entry segment; adding lanes to the median segment would serve no purpose. <br><br />
[[File:LanesMedianNA1.png|frameless|300px]] [[File:LanesMedianNA2.png|frameless|300px]]<br />
}}<br />
{{mbox<br />
| type = important<br />
| text = One side effect of the H/# heuristics is that in many cases the server will identify 'turn left, then turn left' movements across a H/# intersection (which are not prohibited by [[Junction_Style_Guide/Intersections#Avoiding_U_turns|the U-turn prevention algorithm]]) as a U-turn, and display the U-turn lane guidance arrow in the app. In addition to the visual display of the U-turn arrow, the app's voice turn-by-turn instructions will vocalize the movement as a u-turn. <br />
}}<br />
==== Mapping lanes on divided roadways ====<br />
===== Hash intersections =====<br />
[[File:Median-entry.jpg|300px|thumb|right|Entry and Median Segments (for each direction of travel)]]<br />
First, make sure that the intersection and the turn you are mapping for meet the [[#divided roadway criteria|guidelines above]]. Handle one direction of travel at a time.<br><br />
<br />
For each direction of travel, lanes must be mapped on two segments: the “entry segment” (immediately before the median) and the “median segment” (within the median). ''See the adjacent figure. ''<br />
# On the entry segment, include the total number of lanes entering the segment.<br />
## Any lane that can be used to either turn left or continue straight should be mapped as a continuing straight lane.<br />
## Right turn lanes should be mapped as normal.<br />
# On the median segment, include the total number of lanes on the median segment (which should equal the number of lanes on the entry segment minus the number of right turn only lanes).<br clear=all><br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Entry segment: '''<br />
| style="width: 50%; text-align:center" | '''Median segment: '''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:Lanes_entry.png|350px|frameless]]<br />
| style="width: 50%; text-align:center" | [[File:Lanes_median.png|350px|frameless]]<br />
|}<br />
The heuristic in the routing server will combine these two sets of lanes together and provide a single set for drivers making either left or right turns. Unfortunately, there is no way to visualize the result in WME.<br><br />
<br />
'''<big>Lanes resulting from heuristics:</big>'''<br />
[[File:Lanes result.png|224px|frameless|left]]<br clear=all><br />
===== H Intersections =====<br />
The same heuristic applies to the undivided road side of an H junction. No heuristic is necessary for the divided road side.<br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Undivided road side:'''<br />
| style="width: 50%; text-align:center" | '''Divided road side:'''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:LanesH1.png|350px|frameless]]<br />
| rowspan="2" style="width: 50%; text-align:center" | [[File:LanesH3.png|350px|frameless]]<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:LanesH2resubmit.png|350px|frameless]]<br />
| style="width: 50%; text-align:center" | <br />
|}<br />
{{mbox|text=The median segments of # and H junctions is a rare instance where, on occasion, it is proper to add “1 lane” to a segment. This will be necessary any time there are multiple lanes on the entry segment but only one lane remaining on the median segment (because any other lane was right turn only).<br><br />
[[File:LanesHBox1resubmit.png|frameless|300px]] [[File:LanesHBox2.png|frameless|300px]]<br />
}}<br />
===== Checking your work =====<br />
There are a few things you can do to double-check your work on divided-roadway intersections that need to be mapped with heuristics.<br />
# The total number of lanes on the entry segment should equal the total number of lanes at the intersection:<br />
#* total lanes (intersection) = total lanes (entry)<br />
# The total number of lanes on the median segment should equal the difference between the total number of lanes on the entry segment and the number of right-turn only lanes on the entry segment:<br />
#* total lanes (median) = total lanes (entry) – right turn only lanes (entry)<br />
# The number of straight-ahead lanes on the entry segment (i.e., the number of boxes checked for the straight-ahead movement) should equal the total number of lanes on the median segment:<br />
#* straight-ahead lanes (entry) = total lanes (median)<br />
If these conditions are not met, the heuristic method may not function as expected, and it is best to leave lanes off for the time being.</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=Lanes&diff=172690Lanes2020-05-30T20:42:08Z<p>Tonestertm: /* Adding lanes to the map */ amended wording in mbox regarding zoom level</p>
<hr />
<div>{{construction | contact = https://www.waze.com/forum/viewtopic.php?f=1636&t=301141 | contacttype = forum | draft = no | open = no | revision = no | section = no | talk = no}}<br />
Lane guidance is a new Waze app feature that shows the user exactly which lanes they should use to make their next movement. This feature boosts Wazer confidence by providing reassurance in junctions both typical and unusual. <br />
Lane guidance data is added via the [[Waze Map Editor|Waze Map Editor (WME)]]. When a single segment is selected in the WME, an additional tab called Lanes is available in the left pane. The Lanes tab allows map editors to tell Waze which lane to display to the driver for lane guidance in the mobile app. <br><br />
<br />
There are some important considerations regarding lane guidance in Waze:<br />
* '''Lane guidance does not affect routing''' - it is merely a visual feature.<br />
* '''Lane guidance does not affect audio instructions''', with the exception of u-turn instructions resulting from [[#Lanes_on_divided_roadways|heuristics for intersections on divided roads]].<br />
* '''Lane guidance will only be displayed when a navigation instruction is given.''' If the [[How_Waze_determines_turn_/_keep_/_exit_maneuvers#Best_Continuation|best continuation]] is straight ahead, lane guidance will not be shown, unless there is a [[Turn_instruction_override|continue straight TIO]].<br />
{{mbox | type = protection | text = {{As of|2020|05|28}} the Lanes tab is only visible in the WME to [[Editing restrictions|rank 3 editors]] and lane guidance in the App is only visible to beta testers.}}<br />
{{mbox| type = caution| text = {{As of|2020|05|30}} the lane mapping feature of WME and the lane guidance feature of the mobile app are both still under development. Please check this guide frequently for updates to features and guidance.}}<br />
== Mapping guidance ==<br />
=== What counts as a lane? ===<br />
'''Q: How many lanes should you map at the end of a segment? What counts as a lane?'''<br><br />
'''A: Map any lane that achieves full and consistent width BEFORE the turn itself.''' For a freeway exit lane, this means a lane that is full width BEFORE [https://mutcd.fhwa.dot.gov/HTM/2003/part3/fig3b-08-1_longdesc.htm the gore point]. If someone travelling in the right lane can continue straight without changing lanes, then map this as a straight/turn lane. <br><br />
Consider what the road looks like to a driver - make the number of lanes in the lane guidance display conform to what the driver will see.<br />
==== Freeway exits and other ramps ====<br />
'''<big>Example 1: Not a Separate Lane</big>'''[[File:NotALane2.png|880px|The exit lane does not reach full width until the gore point; map as part of the rightmost continue-straight lane]]<br />
The exit lane does not reach full width until the gore point; map as part of the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 2: Not a Separate Lane</big>'''[[File:NotALane3.png|880px|The exit lane does not reach full width until the gore point; mapped as part of the rightmost continue-straight lane.]]<br />
The exit lane does not reach full width until the gore point; mapped as part of the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 3: Separate Lane</big>'''[[File:SeperateLane2.png|880px|When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.]]<br />
When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 4: Separate Lane</big>'''[[File:SeperateLane1.png|880px|When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.]]<br />
When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.<br />
==== Center two-way left-turn lanes ====<br />
[[File:TwoWayLeftTurnLanes.png|thumb|right|Center two-way turn lane: Separate turn lane if a left is allowed; no turn lane if left is not allowed.]]<br />
Many two-way streets have a center lane marked as a two-way left turn lane (TWLTL), also known as a ‘suicide lane’ or ‘chicken lane’. In the US, this lane is bordered on either side by two yellow lines - the inner line is broken or dashed, the outer line is solid. Pavement marking arrows may or may not be present. Where lane guidance is applied and the left turn lane is possible, these should be marked as separate left-turn lanes.<br />
==== HOV or other restricted lanes ====<br />
HOV (high-occupancy vehicle) restrictions or vehicle restrictions may sometimes only apply to a portion of the roadway. Only include these restricted lanes in lane guidance if they are available to users on the segment in question. In the example below, the bus lane allows for right turning vehicles to use the lane, so it is included in lane guidance. <br />
<gallery><br />
File:Lanes_HOVcount.png|HOV lanes that are on the same segment (not physically separated) should be included in lanes. <br />
File:Lanes_BusResticted.png|Bus, bike, or other restricted lanes should be included. In this case, right turns are allowed from the bus lane, so it is shown as a right turn lane. <br />
File:Lanes_CenterBus.png|In this case, the bus lane (red, center) is the only lane that proceeds straight ahead. It should be included, as it will be shown (though faded) to drivers when they are directed using the outside lanes to turn left or right. <br />
File:Lanes_Choices3.png|The HOV lane is clearly visible to all traffic, and would be considered by most drivers to be a lane, it should be included in the count of lanes at the segments ending at the exit.<br />
</gallery><br />
<br />
=== When to map lanes ===<br />
Generally, lanes should be mapped where there is more than one lane and only a subset of the lanes is available for turns. Also lanes should be mapped in potentially confusing locations where lane guidance can significantly improve safety and the driver experience.<br />
==== When the driver needs to choose the correct lane ====<br />
[[File:Lanes DriversChoice.png|thumb|right]] Any time there are two or more lanes AND an instruction is given at the node. In the example below, the street running east/west has only two lanes in either direction, but only one of those lanes may turn south onto the side street. Lane guidance should be added.<br clear=all><br />
==== To clarify which road to take ====<br />
Before now, Waze could not show the driver the difference between slight, 90°, and sharp turns. Without lanes, intersections with multiple right or multiple left turns could be confusing to drivers. Lane guidance can clear up this confusion by showing drivers whether to take, for example, the slight turn or the sharp turn.<br />
{{mbox | text = This situation is generally the only place where it is useful to add lanes where there is only one lane in the relevant direction of travel.}}<br />
<gallery>File:Lanes_Choices.png|example 1<br />
File:Lanes_Choices2.png|example 2</gallery><br />
==== When the driver needs reinforcement or reassurance for safety ====<br />
[[File:Lanes_Reassurance.png|thumb|right|For this freeway off-ramp onto a one-way roadway, reinforce “no left turn”; either lane is fine.]]<br />
There are some cases where lanes should be added to reassure drivers that they need not switch lanes, or that they may not turn from the lane they are in. In the example below, both lanes of the highway off-ramp must turn right — drivers have no choice. Lane guidance should be added to reassure drivers in the left lane that they need not change lanes and to reinforce the prohibition on the left turn to reduce the chance of them making a wrong-way turn.<br />
<br />
=== When not to map lanes ===<br />
==== When drivers have no choice ====<br />
[[File:Nolanessimple.png|150px|thumb|right|Suburban local streets typically don't have multiple lanes, and don't need lane guidance.]] Generally, don’t add lanes when there is only one lane, or at a node where no instruction is to be given. An exception to this general rule is at confusing intersections and interchanges where the driver needs reassurance that a lane change will not be necessary before the next turn or exit maneuver, or reinforcement that what might look like a valid turn is not allowed (see the reinforcement and reassurance example above).<br clear=all><br />
<br />
==== Merges and new lanes ====<br />
Waze does not offer lane guidance for a reduction in the number of lanes.<br />
[[File:MergeLanes.png|left|frame|Lane guidance is not appropriate for freeway lane reductions that do not occur near an interchange]]<br clear=all><br />
=== How Waze selects 'Waze Selected' lane arrows ===<br />
Waze Selected lane arrows are displayed for us both in the edit dialog (to the left of the checkboxes for each outbound segment) and in the Lanes pane (once changes are applied).{{Collapsible section top|expand=no}}<br />
''Expand for more information...''{{Collapsible section content}}<br />
The determination is mostly simple and mostly based on angles. Consider there is a pizza pie on the map. Cutting the pizza pie into 8 slices, outbound segments in the top slice (i.e., turn angles from 0° up to 22.5° either way) might show straight, slight left, or slight right depending on context; the top-left and top-right slice (i.e., turn angles from 22.5° to 67.5° either way) will show slight left or slight right arrows; the left slice and right slice (between 67.5° and 112.5°) will have regular turn left or turn right arrows; and the bottom 3 slices (between 112.5° and 180°) will have sharp left/sharp right arrows. Capische? Mamma mia.<br />
Regarding the top slice, when there is only one outbound segment within the <22.5° slice, that segment will get the “straight” arrows. However, if multiple segments exist within this slice, some form of the “best continuation” analysis is used to determine which one gets the straight arrow, and other arrows in that slice get slight left or slight right arrows. If there is no “best continuation”, then the segment that is closer to 0° gets the straight arrow, and the other one(s)]]<br />
{{Collapsible section bottom}}<br />
=== When to override lane arrows ===<br />
See [[#How Waze selects 'Waze Selected' lane arrows|How Waze selects lane arrows]] for information on the default turn arrows.<br />
<br />
Always review the lane arrows displayed in the Lanes pane carefully once you have applied your edits. Use override when it makes sense to do so, and leave the “Waze selected” setting in place otherwise. Do what makes sense to the person in the driver’s seat—choose the arrow which is going to make the most sense to the driver based on what they are going to have to do (continue straight, U turn, slight right, etc.) and what they are going to see as they approach the intersection or interchange where they need to make the maneuver.<br />
<br />
This does not necessarily mean that the lane arrows should be forced to match the instruction—for example, there are times when a "keep left" instruction is best paired with "straight" arrows, or when a "turn right" instruction is paired with a slight right arrow. The lane arrows should be set according to how a driver would perceive the lane configuration, but the audio guidance should reflect the action to be taken.<br />
<br />
When you change the arrow associated with one outgoing segment, check the remaining segments. In most situations, no two outgoing segments should use the same arrow.<br />
==== When more than one outbound segment have the same 'Waze selected' arrow ====<br />
Change one or more of them in a way that makes sense.<br />
==== Where segment geometry doesn’t match reality ====<br />
[[File:Lanes Override2.png|150px|thumb]]This happens in some locations because Waze road segment width does not match the real life road width. This can result in turn angles on the map which are somewhat different from the true turn angle. Lane arrow override may be necessary.<br clear=all><br />
<br />
==== Where the Waze selected arrow doesn't match reality ====<br />
Even in areas with very high quality maps, the Waze arrow selection mechanism can create arrow configurations which are confusing to the driver. This is particularly likely at nodes where there are multiple outbound segments essentially straight ahead (within a couple dozen degrees either way) from the inbound segment.<br />
These potentially-confusing generated arrows are most often found at ramp splits, wayfinders, and forks in the road, discussed in the section immediately below.<br />
<br />
However, these situations occur in other places as well. For example, in situations where a main road veers off in one direction, and a side road continues straight ahead, the Waze selected arrows will sometimes give straight-ahead arrows to the continuation of the main road, and a “slight turn” arrow to the straight-ahead side road. This does not make sense from a driver’s perspective. In such cases, use lane angle overrides to achieve the desired result.<br />
<br />
[[File:Jeff-sv sm.jpg|400px|frameless|left]] [[File:Jeff-sat sm.jpg|400px|frameless|right]]<br clear=all><br />
<big>In this example, the continuing road veers left, while the side road exits straight ahead. Both street level and overhead imagery clearly shows the driver's perspective and the need for adjustments.</big> <br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Waze selected arrows do not match reality.'''<br />
| style="width: 50%; text-align:center" | '''Use lane angle overrides to create reality.'''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:Jeff-no.png|300px|frameless]]<br />
| style="width: 50%; text-align:center" | [[File:Jeff-yes.png|300px|frameless]]<br />
|}<br />
<br />
==== Ramp splits, wayfinders, and forks in the road ====<br />
Sometimes the Waze selected lane arrows are the best choice and sometimes they are not. Look at both overhead and street views to consider what makes the most sense from the driver’s perspective. Given the processes by which Waze selects the “Waze selected” selection, sometimes the “Waze selected” straight-ahead arrow does not match well with the actual geometry of a junction. <br><br />
<br />
Generally, only one outbound segment (if any) should have the “straight” arrow. If both outbound segments at a split or wayfinder take you down an equally-straight or equally-not straight path (whether immediately or foreseeably ahead), then neither should use the straight arrow. If one of the outbound segments leads to a straighter path than the other, however, then that one should have the straight arrow. If this is already happening, great. If not, use lane override to make it happen (and to ensure that the other path doesn’t keep it).<br />
<br />
== Adding lanes to the map ==<br />
Before adding lane information, check both aerial and street view to make sure how many lanes there are on the segment at the node(s) where you are about to add lanes. See [[#What counts as a lane?|What counts as a lane?]] for more.<br />
{{mbox | type = warning | text = {{As of|2020|04|27}} the lanes tab shows when a segment is selected at zoom level 4 (500 ft) or closer. If you don’t see the tab, try zooming and panning until it shows. The node you are editing must also be in the window.}}<br />
=== Adding lanes to a segment ===<br />
1. Select the segment to which you would like to add lanes.<br />
2. In the left pane, click the Lanes tab.[[File:Lanes tab.png|thumb|center|300px|The lanes tab appears in the left pane]]<br />
3. For two-way segments, ensure you are editing the correct end of the segment. The “B” end (for A-to-B traffic) will show first, followed by the “A” end (for B-to-A traffic). The text at the top of each ‘end’ will describe the directionality of the lanes below. [[File:Lanes tab2.png|300px|thumb|center|For two-way segments, there is a section for each direction of lanes]]<br />
4. Click "Add lane guidance". [[File:Lanes_AddLaneGuidance.png|300px|thumb|center|For two-way segments, there is a section for each direction of lanes]]<br />
5. Enter the number of lanes (NOT the number of possible directions). Use the number of lanes that connect to the next segment, even if there are a different number of lanes at some other point on the segment. See the [[#What counts as a lane?|What counts as a lane?]] section above for more information.[[File:Lanes_NumberOf.png|300px|thumb|center|Count the numbers of lanes at the end of the segment.]]<br />
6. Use the checkboxes to assign the available lanes for each outbound movement. Confirm using street-level imagery, where available. Note that the same lane may be used for more than one movement (e.g., the right lane may be used for both continuing and right-turning traffic).[[File:Lanes_Checkbox1.png|300px|thumb|left|Each lane is dedicated to a specific movement.]][[File:Lanes_Checkbox2.png|300px|thumb|right|The right lane is shared for continuing and turning traffic.]]<br clear=all><br />
7. Click Apply, then save your changes when you are ready. Changes will go live in the app after the next map tile update. <br />
{{mbox|text=Mousing-over the turn arrow in the lanes panel will<br><br />
highlight that turn arrow on the map.|imageright=[[File:WME_LG_Arrow_Highlight.png|thumb|100px]]}}<br />
<br />
=== Editing existing lanes ===<br />
Editing existing Lane Guidance for a segment is done similarly to adding the lanes for the first time:<br><br />
1. Click the segment.<br><br />
2. In the left pane, click the Lanes tab.<br><br />
3. Click "Edit lane guidance" to bring up the Lane Guidance editing console.[[File:Lanes Edit.png|300px|thumb|center|Click 'Edit lane guidance']]<br clear=all><br />
=== Lane errors ===<br />
[[File:Lanes error.png|150px|thumb|right]] If lane data is incomplete, or has been corrupted due to edits on connected segments, then an error alert symbol will appear on the affected segment and on the Lanes tab when the segment is selected.<br clear=all><br />
=== Overriding a turn angle {{Anchor|Overriding a turn angle|Turn angle override|TAO}} === <br />
[[File:Lanes Override3.png|100px|thumb|right|Turn angle override controls]] In some cases, the displayed turn angle may need to be adjusted. Rather than adjusting the geometry of the road segments, an override function is available in the Lanes tab. <br />
# Click the segment.<br />
# In the left pane, click the Lanes tab.<br />
# Click “Edit lane guidance”.<br />
# Click the given turn angle icon under the TURNS header to open the Override turn angle menu. <br />
# Select a new turn angle, or the ‘Waze selected’ angle. <br clear=all><br />
=== Junction Boxes ===<br />
Lane information can be added to segments which are part of a [[Junction Box]] just as they can be added to any other segment. In order for lane guidance to work, all turn arrows on the segments underlying a Junction Box must be green (unrestricted) '''if''' they are on an route allowed by the overlaid Junction Box. Use the Junction Box itself to restrict any necessary routes.<br />
{{mbox | type = warning | text = If a junction box uses a [[turn instruction override]] to override the Waze-selected turn instructions along one of the junction box routes, then the underlying lane data may not be displayed in the app.}}<br />
<br />
=== Lanes on divided roadways {{Anchor|Lanes on divided roadways|'H' and '#' intersections}} ===<br />
At intersections where one or both roads are divided, lanes cannot always be added directly.<br><br />
<br />
Many such intersections can be classified as either “H” intersections (where only one road is divided) or “#” intersections (where both roads are divided).<br><br />
{{mbox|text=On the divided roadway approaches to an “H” intersection, lanes can be added directly to the segments.}}<br />
For some “#” intersections, and on the undivided roadway approaches to some “H” intersections, Waze can combine lane guidance information from more than one segment into a single set of lanes that includes both left and right turns, as the driver expects. {{Anchor|divided roadway criteria}} This will only be possible if all of these conditions are met:<br />
# Both left and right turns are possible at the intersection;<br />
# The two portions of the divided roadway are essentially parallel to each other;<br />
# The two intersecting roads are more or less perpendicular to each other;<br />
# The median segment in question is 50 m or shorter; and<br />
# The number of lanes entering the intersection is equal to the total number of lanes exiting the intersection (total number of lanes exiting intersection = number of lanes on the median segment + number of right-turn only lanes on the entry segment—in other words, no new lanes are added in the median).<br />
If these conditions are met, then follow the guidance in the [[#Mapping lanes on divided roadways|next section]] to add lane information.<br />
{{mbox|text=The purpose of the heuristics is to combine left turn, straight, and right turn arrows into a single lane set. At intersections where either left turns or right turns are disallowed, lanes can be added directly, and heuristics are not needed—in other words, there is no need to add “straight only” lane information. In the example below, right-turning traffic will get the full set of lanes from the entry segment; adding lanes to the median segment would serve no purpose. <br><br />
[[File:LanesMedianNA1.png|frameless|300px]] [[File:LanesMedianNA2.png|frameless|300px]]<br />
}}<br />
{{mbox<br />
| type = important<br />
| text = One side effect of the H/# heuristics is that in many cases the server will identify 'turn left, then turn left' movements across a H/# intersection (which are not prohibited by [[Junction_Style_Guide/Intersections#Avoiding_U_turns|the U-turn prevention algorithm]]) as a U-turn, and display the U-turn lane guidance arrow in the app. In addition to the visual display of the U-turn arrow, the app's voice turn-by-turn instructions will vocalize the movement as a u-turn. <br />
}}<br />
==== Mapping lanes on divided roadways ====<br />
===== Hash intersections =====<br />
[[File:Median-entry.jpg|300px|thumb|right|Entry and Median Segments (for each direction of travel)]]<br />
First, make sure that the intersection and the turn you are mapping for meet the [[#divided roadway criteria|guidelines above]]. Handle one direction of travel at a time.<br><br />
<br />
For each direction of travel, lanes must be mapped on two segments: the “entry segment” (immediately before the median) and the “median segment” (within the median). ''See the adjacent figure. ''<br />
# On the entry segment, include the total number of lanes entering the segment.<br />
## Any lane that can be used to either turn left or continue straight should be mapped as a continuing straight lane.<br />
## Right turn lanes should be mapped as normal.<br />
# On the median segment, include the total number of lanes on the median segment (which should equal the number of lanes on the entry segment minus the number of right turn only lanes).<br clear=all><br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Entry segment: '''<br />
| style="width: 50%; text-align:center" | '''Median segment: '''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:Lanes_entry.png|350px|frameless]]<br />
| style="width: 50%; text-align:center" | [[File:Lanes_median.png|350px|frameless]]<br />
|}<br />
The heuristic in the routing server will combine these two sets of lanes together and provide a single set for drivers making either left or right turns. Unfortunately, there is no way to visualize the result in WME.<br><br />
<br />
'''<big>Lanes resulting from heuristics:</big>'''<br />
[[File:Lanes result.png|224px|frameless|left]]<br clear=all><br />
===== H Intersections =====<br />
The same heuristic applies to the undivided road side of an H junction. No heuristic is necessary for the divided road side.<br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Undivided road side:'''<br />
| style="width: 50%; text-align:center" | '''Divided road side:'''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:LanesH1.png|350px|frameless]]<br />
| rowspan="2" style="width: 50%; text-align:center" | [[File:LanesH3.png|350px|frameless]]<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:LanesH2resubmit.png|350px|frameless]]<br />
| style="width: 50%; text-align:center" | <br />
|}<br />
{{mbox|text=The median segments of # and H junctions is a rare instance where, on occasion, it is proper to add “1 lane” to a segment. This will be necessary any time there are multiple lanes on the entry segment but only one lane remaining on the median segment (because any other lane was right turn only).<br><br />
[[File:LanesHBox1resubmit.png|frameless|300px]] [[File:LanesHBox2.png|frameless|300px]]<br />
}}<br />
===== Checking your work =====<br />
There are a few things you can do to double-check your work on divided-roadway intersections that need to be mapped with heuristics.<br />
# The total number of lanes on the entry segment should equal the total number of lanes at the intersection:<br />
#* total lanes (intersection) = total lanes (entry)<br />
# The total number of lanes on the median segment should equal the difference between the total number of lanes on the entry segment and the number of right-turn only lanes on the entry segment:<br />
#* total lanes (median) = total lanes (entry) – right turn only lanes (entry)<br />
# The number of straight-ahead lanes on the entry segment (i.e., the number of boxes checked for the straight-ahead movement) should equal the total number of lanes on the median segment:<br />
#* straight-ahead lanes (entry) = total lanes (median)<br />
If these conditions are not met, the heuristic method may not function as expected, and it is best to leave lanes off for the time being.</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=Lanes&diff=172689Lanes2020-05-30T20:19:29Z<p>Tonestertm: /* Adding lanes to a segment */ tiny word changes</p>
<hr />
<div>{{construction | contact = https://www.waze.com/forum/viewtopic.php?f=1636&t=301141 | contacttype = forum | draft = no | open = no | revision = no | section = no | talk = no}}<br />
Lane guidance is a new Waze app feature that shows the user exactly which lanes they should use to make their next movement. This feature boosts Wazer confidence by providing reassurance in junctions both typical and unusual. <br />
Lane guidance data is added via the [[Waze Map Editor|Waze Map Editor (WME)]]. When a single segment is selected in the WME, an additional tab called Lanes is available in the left pane. The Lanes tab allows map editors to tell Waze which lane to display to the driver for lane guidance in the mobile app. <br><br />
<br />
There are some important considerations regarding lane guidance in Waze:<br />
* '''Lane guidance does not affect routing''' - it is merely a visual feature.<br />
* '''Lane guidance does not affect audio instructions''', with the exception of u-turn instructions resulting from [[#Lanes_on_divided_roadways|heuristics for intersections on divided roads]].<br />
* '''Lane guidance will only be displayed when a navigation instruction is given.''' If the [[How_Waze_determines_turn_/_keep_/_exit_maneuvers#Best_Continuation|best continuation]] is straight ahead, lane guidance will not be shown, unless there is a [[Turn_instruction_override|continue straight TIO]].<br />
{{mbox | type = protection | text = {{As of|2020|05|28}} the Lanes tab is only visible in the WME to [[Editing restrictions|rank 3 editors]] and lane guidance in the App is only visible to beta testers.}}<br />
{{mbox| type = caution| text = {{As of|2020|05|30}} the lane mapping feature of WME and the lane guidance feature of the mobile app are both still under development. Please check this guide frequently for updates to features and guidance.}}<br />
== Mapping guidance ==<br />
=== What counts as a lane? ===<br />
'''Q: How many lanes should you map at the end of a segment? What counts as a lane?'''<br><br />
'''A: Map any lane that achieves full and consistent width BEFORE the turn itself.''' For a freeway exit lane, this means a lane that is full width BEFORE [https://mutcd.fhwa.dot.gov/HTM/2003/part3/fig3b-08-1_longdesc.htm the gore point]. If someone travelling in the right lane can continue straight without changing lanes, then map this as a straight/turn lane. <br><br />
Consider what the road looks like to a driver - make the number of lanes in the lane guidance display conform to what the driver will see.<br />
==== Freeway exits and other ramps ====<br />
'''<big>Example 1: Not a Separate Lane</big>'''[[File:NotALane2.png|880px|The exit lane does not reach full width until the gore point; map as part of the rightmost continue-straight lane]]<br />
The exit lane does not reach full width until the gore point; map as part of the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 2: Not a Separate Lane</big>'''[[File:NotALane3.png|880px|The exit lane does not reach full width until the gore point; mapped as part of the rightmost continue-straight lane.]]<br />
The exit lane does not reach full width until the gore point; mapped as part of the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 3: Separate Lane</big>'''[[File:SeperateLane2.png|880px|When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.]]<br />
When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 4: Separate Lane</big>'''[[File:SeperateLane1.png|880px|When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.]]<br />
When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.<br />
==== Center two-way left-turn lanes ====<br />
[[File:TwoWayLeftTurnLanes.png|thumb|right|Center two-way turn lane: Separate turn lane if a left is allowed; no turn lane if left is not allowed.]]<br />
Many two-way streets have a center lane marked as a two-way left turn lane (TWLTL), also known as a ‘suicide lane’ or ‘chicken lane’. In the US, this lane is bordered on either side by two yellow lines - the inner line is broken or dashed, the outer line is solid. Pavement marking arrows may or may not be present. Where lane guidance is applied and the left turn lane is possible, these should be marked as separate left-turn lanes.<br />
==== HOV or other restricted lanes ====<br />
HOV (high-occupancy vehicle) restrictions or vehicle restrictions may sometimes only apply to a portion of the roadway. Only include these restricted lanes in lane guidance if they are available to users on the segment in question. In the example below, the bus lane allows for right turning vehicles to use the lane, so it is included in lane guidance. <br />
<gallery><br />
File:Lanes_HOVcount.png|HOV lanes that are on the same segment (not physically separated) should be included in lanes. <br />
File:Lanes_BusResticted.png|Bus, bike, or other restricted lanes should be included. In this case, right turns are allowed from the bus lane, so it is shown as a right turn lane. <br />
File:Lanes_CenterBus.png|In this case, the bus lane (red, center) is the only lane that proceeds straight ahead. It should be included, as it will be shown (though faded) to drivers when they are directed using the outside lanes to turn left or right. <br />
File:Lanes_Choices3.png|The HOV lane is clearly visible to all traffic, and would be considered by most drivers to be a lane, it should be included in the count of lanes at the segments ending at the exit.<br />
</gallery><br />
<br />
=== When to map lanes ===<br />
Generally, lanes should be mapped where there is more than one lane and only a subset of the lanes is available for turns. Also lanes should be mapped in potentially confusing locations where lane guidance can significantly improve safety and the driver experience.<br />
==== When the driver needs to choose the correct lane ====<br />
[[File:Lanes DriversChoice.png|thumb|right]] Any time there are two or more lanes AND an instruction is given at the node. In the example below, the street running east/west has only two lanes in either direction, but only one of those lanes may turn south onto the side street. Lane guidance should be added.<br clear=all><br />
==== To clarify which road to take ====<br />
Before now, Waze could not show the driver the difference between slight, 90°, and sharp turns. Without lanes, intersections with multiple right or multiple left turns could be confusing to drivers. Lane guidance can clear up this confusion by showing drivers whether to take, for example, the slight turn or the sharp turn.<br />
{{mbox | text = This situation is generally the only place where it is useful to add lanes where there is only one lane in the relevant direction of travel.}}<br />
<gallery>File:Lanes_Choices.png|example 1<br />
File:Lanes_Choices2.png|example 2</gallery><br />
==== When the driver needs reinforcement or reassurance for safety ====<br />
[[File:Lanes_Reassurance.png|thumb|right|For this freeway off-ramp onto a one-way roadway, reinforce “no left turn”; either lane is fine.]]<br />
There are some cases where lanes should be added to reassure drivers that they need not switch lanes, or that they may not turn from the lane they are in. In the example below, both lanes of the highway off-ramp must turn right — drivers have no choice. Lane guidance should be added to reassure drivers in the left lane that they need not change lanes and to reinforce the prohibition on the left turn to reduce the chance of them making a wrong-way turn.<br />
<br />
=== When not to map lanes ===<br />
==== When drivers have no choice ====<br />
[[File:Nolanessimple.png|150px|thumb|right|Suburban local streets typically don't have multiple lanes, and don't need lane guidance.]] Generally, don’t add lanes when there is only one lane, or at a node where no instruction is to be given. An exception to this general rule is at confusing intersections and interchanges where the driver needs reassurance that a lane change will not be necessary before the next turn or exit maneuver, or reinforcement that what might look like a valid turn is not allowed (see the reinforcement and reassurance example above).<br clear=all><br />
<br />
==== Merges and new lanes ====<br />
Waze does not offer lane guidance for a reduction in the number of lanes.<br />
[[File:MergeLanes.png|left|frame|Lane guidance is not appropriate for freeway lane reductions that do not occur near an interchange]]<br clear=all><br />
=== How Waze selects 'Waze Selected' lane arrows ===<br />
Waze Selected lane arrows are displayed for us both in the edit dialog (to the left of the checkboxes for each outbound segment) and in the Lanes pane (once changes are applied).{{Collapsible section top|expand=no}}<br />
''Expand for more information...''{{Collapsible section content}}<br />
The determination is mostly simple and mostly based on angles. Consider there is a pizza pie on the map. Cutting the pizza pie into 8 slices, outbound segments in the top slice (i.e., turn angles from 0° up to 22.5° either way) might show straight, slight left, or slight right depending on context; the top-left and top-right slice (i.e., turn angles from 22.5° to 67.5° either way) will show slight left or slight right arrows; the left slice and right slice (between 67.5° and 112.5°) will have regular turn left or turn right arrows; and the bottom 3 slices (between 112.5° and 180°) will have sharp left/sharp right arrows. Capische? Mamma mia.<br />
Regarding the top slice, when there is only one outbound segment within the <22.5° slice, that segment will get the “straight” arrows. However, if multiple segments exist within this slice, some form of the “best continuation” analysis is used to determine which one gets the straight arrow, and other arrows in that slice get slight left or slight right arrows. If there is no “best continuation”, then the segment that is closer to 0° gets the straight arrow, and the other one(s)]]<br />
{{Collapsible section bottom}}<br />
=== When to override lane arrows ===<br />
See [[#How Waze selects 'Waze Selected' lane arrows|How Waze selects lane arrows]] for information on the default turn arrows.<br />
<br />
Always review the lane arrows displayed in the Lanes pane carefully once you have applied your edits. Use override when it makes sense to do so, and leave the “Waze selected” setting in place otherwise. Do what makes sense to the person in the driver’s seat—choose the arrow which is going to make the most sense to the driver based on what they are going to have to do (continue straight, U turn, slight right, etc.) and what they are going to see as they approach the intersection or interchange where they need to make the maneuver.<br />
<br />
This does not necessarily mean that the lane arrows should be forced to match the instruction—for example, there are times when a "keep left" instruction is best paired with "straight" arrows, or when a "turn right" instruction is paired with a slight right arrow. The lane arrows should be set according to how a driver would perceive the lane configuration, but the audio guidance should reflect the action to be taken.<br />
<br />
When you change the arrow associated with one outgoing segment, check the remaining segments. In most situations, no two outgoing segments should use the same arrow.<br />
==== When more than one outbound segment have the same 'Waze selected' arrow ====<br />
Change one or more of them in a way that makes sense.<br />
==== Where segment geometry doesn’t match reality ====<br />
[[File:Lanes Override2.png|150px|thumb]]This happens in some locations because Waze road segment width does not match the real life road width. This can result in turn angles on the map which are somewhat different from the true turn angle. Lane arrow override may be necessary.<br clear=all><br />
<br />
==== Where the Waze selected arrow doesn't match reality ====<br />
Even in areas with very high quality maps, the Waze arrow selection mechanism can create arrow configurations which are confusing to the driver. This is particularly likely at nodes where there are multiple outbound segments essentially straight ahead (within a couple dozen degrees either way) from the inbound segment.<br />
These potentially-confusing generated arrows are most often found at ramp splits, wayfinders, and forks in the road, discussed in the section immediately below.<br />
<br />
However, these situations occur in other places as well. For example, in situations where a main road veers off in one direction, and a side road continues straight ahead, the Waze selected arrows will sometimes give straight-ahead arrows to the continuation of the main road, and a “slight turn” arrow to the straight-ahead side road. This does not make sense from a driver’s perspective. In such cases, use lane angle overrides to achieve the desired result.<br />
<br />
[[File:Jeff-sv sm.jpg|400px|frameless|left]] [[File:Jeff-sat sm.jpg|400px|frameless|right]]<br clear=all><br />
<big>In this example, the continuing road veers left, while the side road exits straight ahead. Both street level and overhead imagery clearly shows the driver's perspective and the need for adjustments.</big> <br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Waze selected arrows do not match reality.'''<br />
| style="width: 50%; text-align:center" | '''Use lane angle overrides to create reality.'''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:Jeff-no.png|300px|frameless]]<br />
| style="width: 50%; text-align:center" | [[File:Jeff-yes.png|300px|frameless]]<br />
|}<br />
<br />
==== Ramp splits, wayfinders, and forks in the road ====<br />
Sometimes the Waze selected lane arrows are the best choice and sometimes they are not. Look at both overhead and street views to consider what makes the most sense from the driver’s perspective. Given the processes by which Waze selects the “Waze selected” selection, sometimes the “Waze selected” straight-ahead arrow does not match well with the actual geometry of a junction. <br><br />
<br />
Generally, only one outbound segment (if any) should have the “straight” arrow. If both outbound segments at a split or wayfinder take you down an equally-straight or equally-not straight path (whether immediately or foreseeably ahead), then neither should use the straight arrow. If one of the outbound segments leads to a straighter path than the other, however, then that one should have the straight arrow. If this is already happening, great. If not, use lane override to make it happen (and to ensure that the other path doesn’t keep it).<br />
<br />
== Adding lanes to the map ==<br />
Before adding lane information, check both aerial and street view to make sure how many lanes there are on the segment at the node(s) where you are about to add lanes. See [[#What counts as a lane?|What counts as a lane?]] for more.<br />
{{mbox | type = warning | text = {{As of|2020|04|27}} the lanes tab shows at zoom level 4 and higher. If you don’t see the tab, try zooming and panning until it shows. The node you are editing must also be in the window.}}<br />
=== Adding lanes to a segment ===<br />
1. Select the segment to which you would like to add lanes.<br />
2. In the left pane, click the Lanes tab.[[File:Lanes tab.png|thumb|center|300px|The lanes tab appears in the left pane]]<br />
3. For two-way segments, ensure you are editing the correct end of the segment. The “B” end (for A-to-B traffic) will show first, followed by the “A” end (for B-to-A traffic). The text at the top of each ‘end’ will describe the directionality of the lanes below. [[File:Lanes tab2.png|300px|thumb|center|For two-way segments, there is a section for each direction of lanes]]<br />
4. Click "Add lane guidance". [[File:Lanes_AddLaneGuidance.png|300px|thumb|center|For two-way segments, there is a section for each direction of lanes]]<br />
5. Enter the number of lanes (NOT the number of possible directions). Use the number of lanes that connect to the next segment, even if there are a different number of lanes at some other point on the segment. See the [[#What counts as a lane?|What counts as a lane?]] section above for more information.[[File:Lanes_NumberOf.png|300px|thumb|center|Count the numbers of lanes at the end of the segment.]]<br />
6. Use the checkboxes to assign the available lanes for each outbound movement. Confirm using street-level imagery, where available. Note that the same lane may be used for more than one movement (e.g., the right lane may be used for both continuing and right-turning traffic).[[File:Lanes_Checkbox1.png|300px|thumb|left|Each lane is dedicated to a specific movement.]][[File:Lanes_Checkbox2.png|300px|thumb|right|The right lane is shared for continuing and turning traffic.]]<br clear=all><br />
7. Click Apply, then save your changes when you are ready. Changes will go live in the app after the next map tile update. <br />
{{mbox|text=Mousing-over the turn arrow in the lanes panel will<br><br />
highlight that turn arrow on the map.|imageright=[[File:WME_LG_Arrow_Highlight.png|thumb|100px]]}}<br />
<br />
=== Editing existing lanes ===<br />
Editing existing Lane Guidance for a segment is done similarly to adding the lanes for the first time:<br><br />
1. Click the segment.<br><br />
2. In the left pane, click the Lanes tab.<br><br />
3. Click "Edit lane guidance" to bring up the Lane Guidance editing console.[[File:Lanes Edit.png|300px|thumb|center|Click 'Edit lane guidance']]<br clear=all><br />
=== Lane errors ===<br />
[[File:Lanes error.png|150px|thumb|right]] If lane data is incomplete, or has been corrupted due to edits on connected segments, then an error alert symbol will appear on the affected segment and on the Lanes tab when the segment is selected.<br clear=all><br />
=== Overriding a turn angle {{Anchor|Overriding a turn angle|Turn angle override|TAO}} === <br />
[[File:Lanes Override3.png|100px|thumb|right|Turn angle override controls]] In some cases, the displayed turn angle may need to be adjusted. Rather than adjusting the geometry of the road segments, an override function is available in the Lanes tab. <br />
# Click the segment.<br />
# In the left pane, click the Lanes tab.<br />
# Click “Edit lane guidance”.<br />
# Click the given turn angle icon under the TURNS header to open the Override turn angle menu. <br />
# Select a new turn angle, or the ‘Waze selected’ angle. <br clear=all><br />
=== Junction Boxes ===<br />
Lane information can be added to segments which are part of a [[Junction Box]] just as they can be added to any other segment. In order for lane guidance to work, all turn arrows on the segments underlying a Junction Box must be green (unrestricted) '''if''' they are on an route allowed by the overlaid Junction Box. Use the Junction Box itself to restrict any necessary routes.<br />
{{mbox | type = warning | text = If a junction box uses a [[turn instruction override]] to override the Waze-selected turn instructions along one of the junction box routes, then the underlying lane data may not be displayed in the app.}}<br />
<br />
=== Lanes on divided roadways {{Anchor|Lanes on divided roadways|'H' and '#' intersections}} ===<br />
At intersections where one or both roads are divided, lanes cannot always be added directly.<br><br />
<br />
Many such intersections can be classified as either “H” intersections (where only one road is divided) or “#” intersections (where both roads are divided).<br><br />
{{mbox|text=On the divided roadway approaches to an “H” intersection, lanes can be added directly to the segments.}}<br />
For some “#” intersections, and on the undivided roadway approaches to some “H” intersections, Waze can combine lane guidance information from more than one segment into a single set of lanes that includes both left and right turns, as the driver expects. {{Anchor|divided roadway criteria}} This will only be possible if all of these conditions are met:<br />
# Both left and right turns are possible at the intersection;<br />
# The two portions of the divided roadway are essentially parallel to each other;<br />
# The two intersecting roads are more or less perpendicular to each other;<br />
# The median segment in question is 50 m or shorter; and<br />
# The number of lanes entering the intersection is equal to the total number of lanes exiting the intersection (total number of lanes exiting intersection = number of lanes on the median segment + number of right-turn only lanes on the entry segment—in other words, no new lanes are added in the median).<br />
If these conditions are met, then follow the guidance in the [[#Mapping lanes on divided roadways|next section]] to add lane information.<br />
{{mbox|text=The purpose of the heuristics is to combine left turn, straight, and right turn arrows into a single lane set. At intersections where either left turns or right turns are disallowed, lanes can be added directly, and heuristics are not needed—in other words, there is no need to add “straight only” lane information. In the example below, right-turning traffic will get the full set of lanes from the entry segment; adding lanes to the median segment would serve no purpose. <br><br />
[[File:LanesMedianNA1.png|frameless|300px]] [[File:LanesMedianNA2.png|frameless|300px]]<br />
}}<br />
{{mbox<br />
| type = important<br />
| text = One side effect of the H/# heuristics is that in many cases the server will identify 'turn left, then turn left' movements across a H/# intersection (which are not prohibited by [[Junction_Style_Guide/Intersections#Avoiding_U_turns|the U-turn prevention algorithm]]) as a U-turn, and display the U-turn lane guidance arrow in the app. In addition to the visual display of the U-turn arrow, the app's voice turn-by-turn instructions will vocalize the movement as a u-turn. <br />
}}<br />
==== Mapping lanes on divided roadways ====<br />
===== Hash intersections =====<br />
[[File:Median-entry.jpg|300px|thumb|right|Entry and Median Segments (for each direction of travel)]]<br />
First, make sure that the intersection and the turn you are mapping for meet the [[#divided roadway criteria|guidelines above]]. Handle one direction of travel at a time.<br><br />
<br />
For each direction of travel, lanes must be mapped on two segments: the “entry segment” (immediately before the median) and the “median segment” (within the median). ''See the adjacent figure. ''<br />
# On the entry segment, include the total number of lanes entering the segment.<br />
## Any lane that can be used to either turn left or continue straight should be mapped as a continuing straight lane.<br />
## Right turn lanes should be mapped as normal.<br />
# On the median segment, include the total number of lanes on the median segment (which should equal the number of lanes on the entry segment minus the number of right turn only lanes).<br clear=all><br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Entry segment: '''<br />
| style="width: 50%; text-align:center" | '''Median segment: '''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:Lanes_entry.png|350px|frameless]]<br />
| style="width: 50%; text-align:center" | [[File:Lanes_median.png|350px|frameless]]<br />
|}<br />
The heuristic in the routing server will combine these two sets of lanes together and provide a single set for drivers making either left or right turns. Unfortunately, there is no way to visualize the result in WME.<br><br />
<br />
'''<big>Lanes resulting from heuristics:</big>'''<br />
[[File:Lanes result.png|224px|frameless|left]]<br clear=all><br />
===== H Intersections =====<br />
The same heuristic applies to the undivided road side of an H junction. No heuristic is necessary for the divided road side.<br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Undivided road side:'''<br />
| style="width: 50%; text-align:center" | '''Divided road side:'''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:LanesH1.png|350px|frameless]]<br />
| rowspan="2" style="width: 50%; text-align:center" | [[File:LanesH3.png|350px|frameless]]<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:LanesH2resubmit.png|350px|frameless]]<br />
| style="width: 50%; text-align:center" | <br />
|}<br />
{{mbox|text=The median segments of # and H junctions is a rare instance where, on occasion, it is proper to add “1 lane” to a segment. This will be necessary any time there are multiple lanes on the entry segment but only one lane remaining on the median segment (because any other lane was right turn only).<br><br />
[[File:LanesHBox1resubmit.png|frameless|300px]] [[File:LanesHBox2.png|frameless|300px]]<br />
}}<br />
===== Checking your work =====<br />
There are a few things you can do to double-check your work on divided-roadway intersections that need to be mapped with heuristics.<br />
# The total number of lanes on the entry segment should equal the total number of lanes at the intersection:<br />
#* total lanes (intersection) = total lanes (entry)<br />
# The total number of lanes on the median segment should equal the difference between the total number of lanes on the entry segment and the number of right-turn only lanes on the entry segment:<br />
#* total lanes (median) = total lanes (entry) – right turn only lanes (entry)<br />
# The number of straight-ahead lanes on the entry segment (i.e., the number of boxes checked for the straight-ahead movement) should equal the total number of lanes on the median segment:<br />
#* straight-ahead lanes (entry) = total lanes (median)<br />
If these conditions are not met, the heuristic method may not function as expected, and it is best to leave lanes off for the time being.</div>Tonestertmhttps://www.waze.com/wiki/USA/index.php?title=Lanes&diff=172688Lanes2020-05-30T19:57:17Z<p>Tonestertm: typos - uncapitalized</p>
<hr />
<div>{{construction | contact = https://www.waze.com/forum/viewtopic.php?f=1636&t=301141 | contacttype = forum | draft = no | open = no | revision = no | section = no | talk = no}}<br />
Lane guidance is a new Waze app feature that shows the user exactly which lanes they should use to make their next movement. This feature boosts Wazer confidence by providing reassurance in junctions both typical and unusual. <br />
Lane guidance data is added via the [[Waze Map Editor|Waze Map Editor (WME)]]. When a single segment is selected in the WME, an additional tab called Lanes is available in the left pane. The Lanes tab allows map editors to tell Waze which lane to display to the driver for lane guidance in the mobile app. <br><br />
<br />
There are some important considerations regarding lane guidance in Waze:<br />
* '''Lane guidance does not affect routing''' - it is merely a visual feature.<br />
* '''Lane guidance does not affect audio instructions''', with the exception of u-turn instructions resulting from [[#Lanes_on_divided_roadways|heuristics for intersections on divided roads]].<br />
* '''Lane guidance will only be displayed when a navigation instruction is given.''' If the [[How_Waze_determines_turn_/_keep_/_exit_maneuvers#Best_Continuation|best continuation]] is straight ahead, lane guidance will not be shown, unless there is a [[Turn_instruction_override|continue straight TIO]].<br />
{{mbox | type = protection | text = {{As of|2020|05|28}} the Lanes tab is only visible in the WME to [[Editing restrictions|rank 3 editors]] and lane guidance in the App is only visible to beta testers.}}<br />
{{mbox| type = caution| text = {{As of|2020|05|30}} the lane mapping feature of WME and the lane guidance feature of the mobile app are both still under development. Please check this guide frequently for updates to features and guidance.}}<br />
== Mapping guidance ==<br />
=== What counts as a lane? ===<br />
'''Q: How many lanes should you map at the end of a segment? What counts as a lane?'''<br><br />
'''A: Map any lane that achieves full and consistent width BEFORE the turn itself.''' For a freeway exit lane, this means a lane that is full width BEFORE [https://mutcd.fhwa.dot.gov/HTM/2003/part3/fig3b-08-1_longdesc.htm the gore point]. If someone travelling in the right lane can continue straight without changing lanes, then map this as a straight/turn lane. <br><br />
Consider what the road looks like to a driver - make the number of lanes in the lane guidance display conform to what the driver will see.<br />
==== Freeway exits and other ramps ====<br />
'''<big>Example 1: Not a Separate Lane</big>'''[[File:NotALane2.png|880px|The exit lane does not reach full width until the gore point; map as part of the rightmost continue-straight lane]]<br />
The exit lane does not reach full width until the gore point; map as part of the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 2: Not a Separate Lane</big>'''[[File:NotALane3.png|880px|The exit lane does not reach full width until the gore point; mapped as part of the rightmost continue-straight lane.]]<br />
The exit lane does not reach full width until the gore point; mapped as part of the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 3: Separate Lane</big>'''[[File:SeperateLane2.png|880px|When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.]]<br />
When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.<br><br />
<br><br />
'''<big>Example 4: Separate Lane</big>'''[[File:SeperateLane1.png|880px|When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.]]<br />
When the exit lane reaches full width before the gore point, map it as a lane separate from the rightmost continue-straight lane.<br />
==== Center two-way left-turn lanes ====<br />
[[File:TwoWayLeftTurnLanes.png|thumb|right|Center two-way turn lane: Separate turn lane if a left is allowed; no turn lane if left is not allowed.]]<br />
Many two-way streets have a center lane marked as a two-way left turn lane (TWLTL), also known as a ‘suicide lane’ or ‘chicken lane’. In the US, this lane is bordered on either side by two yellow lines - the inner line is broken or dashed, the outer line is solid. Pavement marking arrows may or may not be present. Where lane guidance is applied and the left turn lane is possible, these should be marked as separate left-turn lanes.<br />
==== HOV or other restricted lanes ====<br />
HOV (high-occupancy vehicle) restrictions or vehicle restrictions may sometimes only apply to a portion of the roadway. Only include these restricted lanes in lane guidance if they are available to users on the segment in question. In the example below, the bus lane allows for right turning vehicles to use the lane, so it is included in lane guidance. <br />
<gallery><br />
File:Lanes_HOVcount.png|HOV lanes that are on the same segment (not physically separated) should be included in lanes. <br />
File:Lanes_BusResticted.png|Bus, bike, or other restricted lanes should be included. In this case, right turns are allowed from the bus lane, so it is shown as a right turn lane. <br />
File:Lanes_CenterBus.png|In this case, the bus lane (red, center) is the only lane that proceeds straight ahead. It should be included, as it will be shown (though faded) to drivers when they are directed using the outside lanes to turn left or right. <br />
File:Lanes_Choices3.png|The HOV lane is clearly visible to all traffic, and would be considered by most drivers to be a lane, it should be included in the count of lanes at the segments ending at the exit.<br />
</gallery><br />
<br />
=== When to map lanes ===<br />
Generally, lanes should be mapped where there is more than one lane and only a subset of the lanes is available for turns. Also lanes should be mapped in potentially confusing locations where lane guidance can significantly improve safety and the driver experience.<br />
==== When the driver needs to choose the correct lane ====<br />
[[File:Lanes DriversChoice.png|thumb|right]] Any time there are two or more lanes AND an instruction is given at the node. In the example below, the street running east/west has only two lanes in either direction, but only one of those lanes may turn south onto the side street. Lane guidance should be added.<br clear=all><br />
==== To clarify which road to take ====<br />
Before now, Waze could not show the driver the difference between slight, 90°, and sharp turns. Without lanes, intersections with multiple right or multiple left turns could be confusing to drivers. Lane guidance can clear up this confusion by showing drivers whether to take, for example, the slight turn or the sharp turn.<br />
{{mbox | text = This situation is generally the only place where it is useful to add lanes where there is only one lane in the relevant direction of travel.}}<br />
<gallery>File:Lanes_Choices.png|example 1<br />
File:Lanes_Choices2.png|example 2</gallery><br />
==== When the driver needs reinforcement or reassurance for safety ====<br />
[[File:Lanes_Reassurance.png|thumb|right|For this freeway off-ramp onto a one-way roadway, reinforce “no left turn”; either lane is fine.]]<br />
There are some cases where lanes should be added to reassure drivers that they need not switch lanes, or that they may not turn from the lane they are in. In the example below, both lanes of the highway off-ramp must turn right — drivers have no choice. Lane guidance should be added to reassure drivers in the left lane that they need not change lanes and to reinforce the prohibition on the left turn to reduce the chance of them making a wrong-way turn.<br />
<br />
=== When not to map lanes ===<br />
==== When drivers have no choice ====<br />
[[File:Nolanessimple.png|150px|thumb|right|Suburban local streets typically don't have multiple lanes, and don't need lane guidance.]] Generally, don’t add lanes when there is only one lane, or at a node where no instruction is to be given. An exception to this general rule is at confusing intersections and interchanges where the driver needs reassurance that a lane change will not be necessary before the next turn or exit maneuver, or reinforcement that what might look like a valid turn is not allowed (see the reinforcement and reassurance example above).<br clear=all><br />
<br />
==== Merges and new lanes ====<br />
Waze does not offer lane guidance for a reduction in the number of lanes.<br />
[[File:MergeLanes.png|left|frame|Lane guidance is not appropriate for freeway lane reductions that do not occur near an interchange]]<br clear=all><br />
=== How Waze selects 'Waze Selected' lane arrows ===<br />
Waze Selected lane arrows are displayed for us both in the edit dialog (to the left of the checkboxes for each outbound segment) and in the Lanes pane (once changes are applied).{{Collapsible section top|expand=no}}<br />
''Expand for more information...''{{Collapsible section content}}<br />
The determination is mostly simple and mostly based on angles. Consider there is a pizza pie on the map. Cutting the pizza pie into 8 slices, outbound segments in the top slice (i.e., turn angles from 0° up to 22.5° either way) might show straight, slight left, or slight right depending on context; the top-left and top-right slice (i.e., turn angles from 22.5° to 67.5° either way) will show slight left or slight right arrows; the left slice and right slice (between 67.5° and 112.5°) will have regular turn left or turn right arrows; and the bottom 3 slices (between 112.5° and 180°) will have sharp left/sharp right arrows. Capische? Mamma mia.<br />
Regarding the top slice, when there is only one outbound segment within the <22.5° slice, that segment will get the “straight” arrows. However, if multiple segments exist within this slice, some form of the “best continuation” analysis is used to determine which one gets the straight arrow, and other arrows in that slice get slight left or slight right arrows. If there is no “best continuation”, then the segment that is closer to 0° gets the straight arrow, and the other one(s)]]<br />
{{Collapsible section bottom}}<br />
=== When to override lane arrows ===<br />
See [[#How Waze selects 'Waze Selected' lane arrows|How Waze selects lane arrows]] for information on the default turn arrows.<br />
<br />
Always review the lane arrows displayed in the Lanes pane carefully once you have applied your edits. Use override when it makes sense to do so, and leave the “Waze selected” setting in place otherwise. Do what makes sense to the person in the driver’s seat—choose the arrow which is going to make the most sense to the driver based on what they are going to have to do (continue straight, U turn, slight right, etc.) and what they are going to see as they approach the intersection or interchange where they need to make the maneuver.<br />
<br />
This does not necessarily mean that the lane arrows should be forced to match the instruction—for example, there are times when a "keep left" instruction is best paired with "straight" arrows, or when a "turn right" instruction is paired with a slight right arrow. The lane arrows should be set according to how a driver would perceive the lane configuration, but the audio guidance should reflect the action to be taken.<br />
<br />
When you change the arrow associated with one outgoing segment, check the remaining segments. In most situations, no two outgoing segments should use the same arrow.<br />
==== When more than one outbound segment have the same 'Waze selected' arrow ====<br />
Change one or more of them in a way that makes sense.<br />
==== Where segment geometry doesn’t match reality ====<br />
[[File:Lanes Override2.png|150px|thumb]]This happens in some locations because Waze road segment width does not match the real life road width. This can result in turn angles on the map which are somewhat different from the true turn angle. Lane arrow override may be necessary.<br clear=all><br />
<br />
==== Where the Waze selected arrow doesn't match reality ====<br />
Even in areas with very high quality maps, the Waze arrow selection mechanism can create arrow configurations which are confusing to the driver. This is particularly likely at nodes where there are multiple outbound segments essentially straight ahead (within a couple dozen degrees either way) from the inbound segment.<br />
These potentially-confusing generated arrows are most often found at ramp splits, wayfinders, and forks in the road, discussed in the section immediately below.<br />
<br />
However, these situations occur in other places as well. For example, in situations where a main road veers off in one direction, and a side road continues straight ahead, the Waze selected arrows will sometimes give straight-ahead arrows to the continuation of the main road, and a “slight turn” arrow to the straight-ahead side road. This does not make sense from a driver’s perspective. In such cases, use lane angle overrides to achieve the desired result.<br />
<br />
[[File:Jeff-sv sm.jpg|400px|frameless|left]] [[File:Jeff-sat sm.jpg|400px|frameless|right]]<br clear=all><br />
<big>In this example, the continuing road veers left, while the side road exits straight ahead. Both street level and overhead imagery clearly shows the driver's perspective and the need for adjustments.</big> <br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Waze selected arrows do not match reality.'''<br />
| style="width: 50%; text-align:center" | '''Use lane angle overrides to create reality.'''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:Jeff-no.png|300px|frameless]]<br />
| style="width: 50%; text-align:center" | [[File:Jeff-yes.png|300px|frameless]]<br />
|}<br />
<br />
==== Ramp splits, wayfinders, and forks in the road ====<br />
Sometimes the Waze selected lane arrows are the best choice and sometimes they are not. Look at both overhead and street views to consider what makes the most sense from the driver’s perspective. Given the processes by which Waze selects the “Waze selected” selection, sometimes the “Waze selected” straight-ahead arrow does not match well with the actual geometry of a junction. <br><br />
<br />
Generally, only one outbound segment (if any) should have the “straight” arrow. If both outbound segments at a split or wayfinder take you down an equally-straight or equally-not straight path (whether immediately or foreseeably ahead), then neither should use the straight arrow. If one of the outbound segments leads to a straighter path than the other, however, then that one should have the straight arrow. If this is already happening, great. If not, use lane override to make it happen (and to ensure that the other path doesn’t keep it).<br />
<br />
== Adding lanes to the map ==<br />
Before adding lane information, check both aerial and street view to make sure how many lanes there are on the segment at the node(s) where you are about to add lanes. See [[#What counts as a lane?|What counts as a lane?]] for more.<br />
{{mbox | type = warning | text = {{As of|2020|04|27}} the lanes tab shows at zoom level 4 and higher. If you don’t see the tab, try zooming and panning until it shows. The node you are editing must also be in the window.}}<br />
=== Adding lanes to a segment ===<br />
1. Select the segment for which you would like to add lanes.<br />
2. In the left pane, click the Lanes tab.[[File:Lanes tab.png|thumb|center|300px|The lanes tab appears in the left pane]]<br />
3. For two-way segments, ensure you are editing the correct end of the segment. The “B” end (for A-to-B traffic) will show first, followed by the “A” end (for B-to-A traffic). The text at the top of each ‘end’ will describe the directionality of the lanes below. [[File:Lanes tab2.png|300px|thumb|center|For two-way segments, there is a section for each direction of lanes]]<br />
4. Click "Add lane guidance". [[File:Lanes_AddLaneGuidance.png|300px|thumb|center|For two-way segments, there is a section for each direction of lanes]]<br />
5. Add the number of lanes (NOT the number of possible directions). Use the number of lanes that connect to the next segment, even if there are a different number of lanes at some other point on the segment. See the [[#What counts as a lane?|What counts as a lane?]] section above for more information.[[File:Lanes_NumberOf.png|300px|thumb|center|Count the numbers of lanes at the end of the segment.]]<br />
6. Use the checkboxes to assign the available lanes for each outbound movement. Confirm using street-level imagery, where available. Note that the same lane may be used for more than one movement (e.g., the right lane may be used for both continuing and right-turning traffic).[[File:Lanes_Checkbox1.png|300px|thumb|left|Each lane is dedicated to a specific movement.]][[File:Lanes_Checkbox2.png|300px|thumb|right|The right lane is shared for continuing and turning traffic.]]<br clear=all><br />
7. Click Apply, then save your changes when you are ready. Changes will go live in the app after the next map tile update. <br />
{{mbox|text=Mousing-over the turn arrow in the lanes panel will<br><br />
highlight that turn arrow on the map.|imageright=[[File:WME_LG_Arrow_Highlight.png|thumb|100px]]}}<br />
=== Editing existing lanes ===<br />
Editing existing Lane Guidance for a segment is done similarly to adding the lanes for the first time:<br><br />
1. Click the segment.<br><br />
2. In the left pane, click the Lanes tab.<br><br />
3. Click "Edit lane guidance" to bring up the Lane Guidance editing console.[[File:Lanes Edit.png|300px|thumb|center|Click 'Edit lane guidance']]<br clear=all><br />
=== Lane errors ===<br />
[[File:Lanes error.png|150px|thumb|right]] If lane data is incomplete, or has been corrupted due to edits on connected segments, then an error alert symbol will appear on the affected segment and on the Lanes tab when the segment is selected.<br clear=all><br />
=== Overriding a turn angle {{Anchor|Overriding a turn angle|Turn angle override|TAO}} === <br />
[[File:Lanes Override3.png|100px|thumb|right|Turn angle override controls]] In some cases, the displayed turn angle may need to be adjusted. Rather than adjusting the geometry of the road segments, an override function is available in the Lanes tab. <br />
# Click the segment.<br />
# In the left pane, click the Lanes tab.<br />
# Click “Edit lane guidance”.<br />
# Click the given turn angle icon under the TURNS header to open the Override turn angle menu. <br />
# Select a new turn angle, or the ‘Waze selected’ angle. <br clear=all><br />
=== Junction Boxes ===<br />
Lane information can be added to segments which are part of a [[Junction Box]] just as they can be added to any other segment. In order for lane guidance to work, all turn arrows on the segments underlying a Junction Box must be green (unrestricted) '''if''' they are on an route allowed by the overlaid Junction Box. Use the Junction Box itself to restrict any necessary routes.<br />
{{mbox | type = warning | text = If a junction box uses a [[turn instruction override]] to override the Waze-selected turn instructions along one of the junction box routes, then the underlying lane data may not be displayed in the app.}}<br />
<br />
=== Lanes on divided roadways {{Anchor|Lanes on divided roadways|'H' and '#' intersections}} ===<br />
At intersections where one or both roads are divided, lanes cannot always be added directly.<br><br />
<br />
Many such intersections can be classified as either “H” intersections (where only one road is divided) or “#” intersections (where both roads are divided).<br><br />
{{mbox|text=On the divided roadway approaches to an “H” intersection, lanes can be added directly to the segments.}}<br />
For some “#” intersections, and on the undivided roadway approaches to some “H” intersections, Waze can combine lane guidance information from more than one segment into a single set of lanes that includes both left and right turns, as the driver expects. {{Anchor|divided roadway criteria}} This will only be possible if all of these conditions are met:<br />
# Both left and right turns are possible at the intersection;<br />
# The two portions of the divided roadway are essentially parallel to each other;<br />
# The two intersecting roads are more or less perpendicular to each other;<br />
# The median segment in question is 50 m or shorter; and<br />
# The number of lanes entering the intersection is equal to the total number of lanes exiting the intersection (total number of lanes exiting intersection = number of lanes on the median segment + number of right-turn only lanes on the entry segment—in other words, no new lanes are added in the median).<br />
If these conditions are met, then follow the guidance in the [[#Mapping lanes on divided roadways|next section]] to add lane information.<br />
{{mbox|text=The purpose of the heuristics is to combine left turn, straight, and right turn arrows into a single lane set. At intersections where either left turns or right turns are disallowed, lanes can be added directly, and heuristics are not needed—in other words, there is no need to add “straight only” lane information. In the example below, right-turning traffic will get the full set of lanes from the entry segment; adding lanes to the median segment would serve no purpose. <br><br />
[[File:LanesMedianNA1.png|frameless|300px]] [[File:LanesMedianNA2.png|frameless|300px]]<br />
}}<br />
{{mbox<br />
| type = important<br />
| text = One side effect of the H/# heuristics is that in many cases the server will identify 'turn left, then turn left' movements across a H/# intersection (which are not prohibited by [[Junction_Style_Guide/Intersections#Avoiding_U_turns|the U-turn prevention algorithm]]) as a U-turn, and display the U-turn lane guidance arrow in the app. In addition to the visual display of the U-turn arrow, the app's voice turn-by-turn instructions will vocalize the movement as a u-turn. <br />
}}<br />
==== Mapping lanes on divided roadways ====<br />
===== Hash intersections =====<br />
[[File:Median-entry.jpg|300px|thumb|right|Entry and Median Segments (for each direction of travel)]]<br />
First, make sure that the intersection and the turn you are mapping for meet the [[#divided roadway criteria|guidelines above]]. Handle one direction of travel at a time.<br><br />
<br />
For each direction of travel, lanes must be mapped on two segments: the “entry segment” (immediately before the median) and the “median segment” (within the median). ''See the adjacent figure. ''<br />
# On the entry segment, include the total number of lanes entering the segment.<br />
## Any lane that can be used to either turn left or continue straight should be mapped as a continuing straight lane.<br />
## Right turn lanes should be mapped as normal.<br />
# On the median segment, include the total number of lanes on the median segment (which should equal the number of lanes on the entry segment minus the number of right turn only lanes).<br clear=all><br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Entry segment: '''<br />
| style="width: 50%; text-align:center" | '''Median segment: '''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:Lanes_entry.png|350px|frameless]]<br />
| style="width: 50%; text-align:center" | [[File:Lanes_median.png|350px|frameless]]<br />
|}<br />
The heuristic in the routing server will combine these two sets of lanes together and provide a single set for drivers making either left or right turns. Unfortunately, there is no way to visualize the result in WME.<br><br />
<br />
'''<big>Lanes resulting from heuristics:</big>'''<br />
[[File:Lanes result.png|224px|frameless|left]]<br clear=all><br />
===== H Intersections =====<br />
The same heuristic applies to the undivided road side of an H junction. No heuristic is necessary for the divided road side.<br />
{| class="wikitable" style="width: 100%;"<br />
| style="width: 50%; text-align:center" | '''Undivided road side:'''<br />
| style="width: 50%; text-align:center" | '''Divided road side:'''<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:LanesH1.png|350px|frameless]]<br />
| rowspan="2" style="width: 50%; text-align:center" | [[File:LanesH3.png|350px|frameless]]<br />
|-<br />
| style="width: 50%; text-align:center" | [[File:LanesH2resubmit.png|350px|frameless]]<br />
| style="width: 50%; text-align:center" | <br />
|}<br />
{{mbox|text=The median segments of # and H junctions is a rare instance where, on occasion, it is proper to add “1 lane” to a segment. This will be necessary any time there are multiple lanes on the entry segment but only one lane remaining on the median segment (because any other lane was right turn only).<br><br />
[[File:LanesHBox1resubmit.png|frameless|300px]] [[File:LanesHBox2.png|frameless|300px]]<br />
}}<br />
===== Checking your work =====<br />
There are a few things you can do to double-check your work on divided-roadway intersections that need to be mapped with heuristics.<br />
# The total number of lanes on the entry segment should equal the total number of lanes at the intersection:<br />
#* total lanes (intersection) = total lanes (entry)<br />
# The total number of lanes on the median segment should equal the difference between the total number of lanes on the entry segment and the number of right-turn only lanes on the entry segment:<br />
#* total lanes (median) = total lanes (entry) – right turn only lanes (entry)<br />
# The number of straight-ahead lanes on the entry segment (i.e., the number of boxes checked for the straight-ahead movement) should equal the total number of lanes on the median segment:<br />
#* straight-ahead lanes (entry) = total lanes (median)<br />
If these conditions are not met, the heuristic method may not function as expected, and it is best to leave lanes off for the time being.</div>Tonestertm