https://www.waze.com/wiki/USA/api.php?action=feedcontributions&user=Phuz&feedformat=atomWazeopedia - User contributions [en]2024-03-29T11:33:09ZUser contributionsMediaWiki 1.40.2https://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=177970User:Phuz2023-01-07T23:44:07Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
***Mentored by voludu2<br />
**R5 (May 2021)<br />
***Mentored by RussPA<br />
*'''Leadership'''<br />
**'''Country Manager (September 2022)'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****Recruited new members and brought up to speed on DE standards and gave guidance on problem areas<br />
****Worked with DelDOT personnel to help provide editors with more accurate closure information<br />
****Closely monitored the I-95 corridor through Wilmington for the "Restore the Corridor" project to ensure closures and contraflow locations were up to date<br />
*****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
****Entire State (May 2021)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
*****Maintain seasonal speed limits from Corolla to Cape Hatteras<br />
*****Assist with URs and heavy PUR load during tourist season<br />
*****Work with towns that incorporate road closures during turnover days<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaids'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
**Luzerne Co, PA HN Mini-Raid (March 2021)<br />
*'''Other Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
***Populate data for statewide CDPs to determine which should be seeded within WME<br />
**NOR Closure Bot (July 2020 - Present)<br />
***Co-developed with [[usa:User:Doctorblah|'''doctorblah''']]<br />
***Incorporate feeds from each state's DOT traffic reporting system to provide immediate posting in the state's closure channel with detailed information and WME Permalink of the location<br />
**WME DOT Cameras [SCRIPT] (July 2020-Present)<br />
***Co-developed with [[usa:User:Doctorblah|'''doctorblah''']]<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
***Provides camera icon overlays in WME to show the location of the state's DOT cameras. When clicked, a popup will either show the live stream or the still image of that location.<br />
**WME DOT Advisories [SCRIPT] (October 2020 - Present)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
***Provides advisory markers in WME to show the location of live incidents and traffic advisories, sourced from the state's DOT feed. When clicked, the popup will provide the description from the DOT, pertinent dates, and any additional hyperlinks (if applicable)<br />
**WME Fix UR Interface [SCRIPT]<br />
***https://greasyfork.org/en/scripts/438755-wme-fix-ur-interface<br />
***Restores the original look & feel of the UR interface after Waze developers modified it significantly in January 2022<br />
**JB U-Turn Sheet Missing Data (February - March 2021)<br />
***Scanned all segments in sheets to backfill missing data for all regions in US<br />
**Global Closure Bot (August 2022 - Present)<br />
***Developed a bot to replace the existing closure bot webhook which ran on google sheets. Existing bot was unreliable and would often duplicate announcements or be severely delayed which led to users becoming desensitized to its reporting.<br />
***Additional features were incorporated into this bot, such as showing the full comment history on closures, as well as making it a little more aesthetic.<br />
***Bot is active in US, Canada, and 15 other countries as of December 2022.<br />
*'''Mentoring'''<br />
**Mentored DaWeatherBoy<br />
**Mentored SMac3265<br />
**Mentored GoBuckEyes3333<br />
**Mentored Drummin4JC<br />
*'''Beta Programs'''<br />
**WME<br />
**iOS<br />
*'''Meetups / Waze Cafes'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)<br />
**Hershey, PA (July 2021) (organizer)<br />
**Virtual (February 2021) (organizer)<br />
**Virtual NA Mega Meetup (February 21, 2021)<br />
<br />
{| class="wikitable"<br />
|-<br />
!Script!!Link<br />
|-<br />
|WME DOT Cameras||https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
|-<br />
|WME DOT Advisories||https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
|-<br />
|WME Fix UR Interface<br />
|https://www.waze.com/forum/viewtopic.php?t=338947<br />
|-<br />
|WME Disable Closed Updates<br />
|https://greasyfork.org/en/scripts/418411-wme-disable-closed-updates<br />
|}<br />
[[File:Script.png|thumb|[https://www.waze.com/forum/viewtopic.php?f=819&t=304760]]]</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Waze_Closures_Bot&diff=177794Waze Closures Bot2022-12-04T18:30:07Z<p>Phuz: </p>
<hr />
<div>The Waze Closures Bot is an automated chat bot for use in the Waze Discord servers developed by {{Username|phuz|rank=5}}. The Waze Closures Bot is to help assist editors in modifying and implementing closures that have been entered by Wazers. The Waze Closures Bot is to be used in conjunction with the guidance in [[Real_time_closures|Real Time Closures]] and regional wiki guidance.<br />
<br />
==== Who can use it ====<br />
Any editor editing in USA or Canada can use the bot if it is activated in a regional Discord channel.<br />
<br />
===== Current regions where the bot is live=====<br />
<br />
[[USA/Great Lakes|GLR (USA)]], [[USA/Mid Atlantic|MAR (USA)]], [[USA/Northeast|NER (USA), NOR (USA)]], [[USA/Northwest|NWR (USA)]], [[USA/Plains|PLN (USA)]], [[USA/South Atlantic|SAT (USA)]], [[USA/South Central|SCR (USA)]], [[USA/Southeast|SER (USA)]], [[USA/Southwest|SWR (USA)]],<br />
<br />
==== Actions for the editor ====<br />
* Research the reported closures to confirm they are valid.<br />
* Implement/modify the closure to make it active in the WME app. (''Functionality currently restricted to L3+)'' <br />
<br />
==== Examples ====<br />
[[File:Waze Closure Bot Examples.png|400px|Waze Closure Bot Examples]]<br /><br />
[[File:Waze Closure Bot Comment Example.png|450px|Waze Closure Bot Comment]]<br />
<br />
==== Definitions ====<br />
<br />
'''{?} (Wazer Ranking)''' - Range: 1-10<br /><br />
The reporting Wazer's closure reliability based on the success of past closures.<br><br />
''Note: L6 will always be 10 and L5 will always be 9. Only 5+ show up on LiveMap''<br /><br /><br />
'''Closure Expires In''' - The remaining time of the closure duration that was selected by the reporting Waze. (Unknown, Less than an hour, Several hours, All day, Several Days, or Long term).<br /><br /><br />
'''Rating''' - Range: 0-5<br /><br />
Assigned number based on the reporting Wazer's interaction with the app. Can change over time.<br /><br /><br />
'''Severity''' - Range: 1-5<br /><br />
Assigned number based on a combination of road type, amount of traffic and the importance of the road.<br /><br /><br />
<br />
===== Links =====<br />
'''Wazer username''' - Opens a new editor profile tab to the reporter or commenter.<br /><br />
'''Waze editor username''' ''(Comments only)'' - Opens a new editor profile tab to the closing editor.<br /><br />
'''PM link''' ''(if the Wazer has a forum account)'' - Opens a new forum PM tab allow communication to the commenter or closing editor.<br /><br />
'''Live Map''' - Opens a new Livemap tab with a point at the closure location.<br /><br />
'''WME''' - Opens a new Waze Map Editor (WME) tab with the closure segment highlighted.<br /><br />
'''App''' - Opens the Waze app at the closure location. ''hint: To reply to closures.''<br /><br />
<br />
====Repeat count color code====<br />
<br />
{| class="wikitable"<br />
|-<br />
! Color !! Definition<br />
|-<br />
| {{font color|white|grey|Grey}} || New Reported closure.<br />
|-<br />
| {{font color|white|orange|Orange}} || Same closure has been reported between 2-4 times over the previous 7 days.<br />
|-<br />
| {{font color|white|red|Red}} || Same closure reported at least 5 times in the previous 7 days.<br />
|-<br />
| {{font color|white|black|Black}} || Comment on closure from Wazer<br />
|}<br />
<br />
====FAQ====<br />
=====I have made an in app closure and it wasn't picked up by the bot how is that possible?=====<br />
There are multiple possible causes.<br /><br />
# One of the rating or reliability values was too low for the closure to become visible (not on live map).<br />
# The chosen duration was too short and due to the bot retrieval interval it was missed.<br />
# The bot failed.</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=177551User:Phuz2022-11-02T20:03:32Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
***Mentored by voludu2<br />
**R5 (May 2021)<br />
***Mentored by RussPA<br />
*'''Leadership'''<br />
**'''Country Manager (September 2022)'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****Recruited new members and brought up to speed on DE standards and gave guidance on problem areas<br />
****Worked with DelDOT personnel to help provide editors with more accurate closure information<br />
****Closely monitored the I-95 corridor through Wilmington for the "Restore the Corridor" project to ensure closures and contraflow locations were up to date<br />
*****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
****Entire State (May 2021)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
*****Maintain seasonal speed limits from Corolla to Cape Hatteras<br />
*****Assist with URs and heavy PUR load during tourist season<br />
*****Work with towns that incorporate road closures during turnover days<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaids'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
**Luzerne Co, PA HN Mini-Raid (March 2021)<br />
*'''Other Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
***Populate data for statewide CDPs to determine which should be seeded within WME<br />
**NOR Closure Bot (July 2020 - Present)<br />
***Co-developed with [[usa:User:Doctorblah|'''doctorblah''']]<br />
***Incorporate feeds from each state's DOT traffic reporting system to provide immediate posting in the state's closure channel with detailed information and WME Permalink of the location<br />
**WME DOT Cameras [SCRIPT] (July 2020-Present)<br />
***Co-developed with [[usa:User:Doctorblah|'''doctorblah''']]<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
***Provides camera icon overlays in WME to show the location of the state's DOT cameras. When clicked, a popup will either show the live stream or the still image of that location.<br />
**WME DOT Advisories [SCRIPT] (October 2020 - Present)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
***Provides advisory markers in WME to show the location of live incidents and traffic advisories, sourced from the state's DOT feed. When clicked, the popup will provide the description from the DOT, pertinent dates, and any additional hyperlinks (if applicable)<br />
**WME Fix UR Interface [SCRIPT]<br />
***https://greasyfork.org/en/scripts/438755-wme-fix-ur-interface<br />
***Restores the original look & feel of the UR interface after Waze developers modified it significantly in January 2022<br />
**JB U-Turn Sheet Missing Data (February - March 2021)<br />
***Scanned all segments in sheets to backfill missing data for all regions in US<br />
**Closure Bot (August 2022 - Present)<br />
***Teamed up to with SAT region MSM '''The_Cre8r'''<br />
***Developed a bot to replace the existing closure bot webhook which runs on google sheets. Existing bot was unreliable and would often duplicate announcements which led to users becoming desensitized to its reporting.<br />
***Additional features were incorporated into this bot, such as showing the full comment history on closures, as well as making it a little more aesthetic.<br />
***Bot is being deployed in NOR and SAT initially and will eventually move into every region before becoming a global replacement.<br />
*'''Mentoring'''<br />
**Mentored DaWeatherBoy<br />
**Mentored SMac3265<br />
**Mentored GoBuckEyes3333<br />
**Mentored Drummin4JC<br />
*'''Beta Programs'''<br />
**WME<br />
**iOS<br />
*'''Meetups / Waze Cafes'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)<br />
**Hershey, PA (July 2021) (organizer)<br />
**Virtual (February 2021) (organizer)<br />
**Virtual NA Mega Meetup (February 21, 2021)<br />
<br />
{| class="wikitable"<br />
|-<br />
!Script!!Link<br />
|-<br />
|WME DOT Cameras||https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
|-<br />
|WME DOT Advisories||https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
|-<br />
|WME Fix UR Interface<br />
|https://www.waze.com/forum/viewtopic.php?t=338947<br />
|-<br />
|WME Disable Closed Updates<br />
|https://greasyfork.org/en/scripts/418411-wme-disable-closed-updates<br />
|}<br />
[[File:Script.png|thumb|[https://www.waze.com/forum/viewtopic.php?f=819&t=304760]]]</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Delaware/Major_roads/Main&diff=177474Delaware/Major roads/Main2022-10-26T16:19:41Z<p>Phuz: </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 />
* {{RootPage2}} uses '''SR-##''' for all state routes (e.g. '''SR-58''')<br />
* If the primary name is a street name and the road also has a US or state route (SR), add it to the alt name (e.g. Primary Name: Capitol Trl, Alternate Name1: SR-2, Alternate Name2: Kirkwood Hwy). If a divided road, also add the cardinal direction to the alt name. e.g. "SR-7 N" on the northbound side and "SR-7 S" on the southbound side. When using alt names, be sure to be consistent and avoid gaps in naming, as this can cause routing issues with detour prevention. If the road switches back and forth between divided and two-way you should add a simple SR-## Alt Name for the entire length as well to avoid detour prevention.<br />
* Generally, regarding state route numbers, even numbers run east-west and odd numbers run north-south<br />
* Some {{RootPage2}} routes are continuations from other neighboring state routes. e.g., SR-273, SR-896, SR-299. <br />
<br />
==== Locking standard ====<br />
{{Lock Standard State|NORTHEAST}}<br />
<br />
<!-- <br />
{{Locking Standard|title=Statewide|Fwy=5|Ramp=Highest rank of connected segments|MH=3|mH=3|PS=1|Street=1}}<br />
--><br />
<br />
=== Speed Limits ===<br />
{{RootPage2}} follows the [[Speed limits|national guideline]] for speed limits, with a few exceptions listed below.<br />
====Delaware guidelines====<br />
* When a speed limit changes at an intersection, the sign for the new speed zone can be found up to 200 feet after the intersection. Map the change at the junction if signs immediately after the junction on each side are different speed limits. <br />
* If the speed limit changes more than 200 feet from the intersection, add a junction at the sign and make the speed limit change there. <br />
* If opposing speed limit signs are opposite each other, attempt to make the change as close as possible to the actual speed limit signs but do not create a new segment if within 200 feet of a junction. When adding changing speed limits, choose the junction that is on the higher speed limit side. Basically if the change is going to happen slightly early or late, best to have a lower speed limit come earlier and a higher speed limit come later.<br />
* Long term work zone speed limits may be mapped instead of the "ordinary time" speed limits. If placing a work zone limit, use Livemap to place a UR there, note that it is a temporary speed limit, and add [CONSTRUCTION] somewhere in the comment. <br />
* If no speed limit sign is posted, the default speed limits in Delaware are<br />
** Residential or business district: 25 MPH<br />
** Two lane road: 50 MPH<br />
** Divided highway: 55 MPH<br />
<br />
==== Town Speed Limits ====<br />
<br />
Do not assume every housing development is 25 MPH. Some localities have lower limits. Below is a list of some of them:<br />
<br />
* [http://www.southbethany.org/index.php?content=16 Bethany Beach]: 20 MPH<br />
* Elsmere: 20 MPH<br />
<br />
==== Special notes ====<br />
<br />
Delaware (especially NCCo) is really bad about signing speed limits on many roads. So even though the law says an unsigned road is above values, outside or rural areas of the state, that is probably not the case. May need to infer some speed limits based on signage pretty far down the highway. <br />
<br />
<br />
====Summary of National Guidelines====<br />
* Only map speeds found on '''regulatory''' white rectangular signs with black lettering.<br />
* Do not map '''advisory''' speed limits (generally an orange or amber rectangular sign with black lettering).<br />
* Where there are variable speed limits, map only the speed limit which is in effect most of the time during daylight hours (most hours of the day, days of the week).<br />
* Do not map special speed limits for special vehicles. Waze only supports speed limits for private passenger cars.<br />
<br />
=====Link to Delaware speed limit laws=====<br />
*[http://delcode.delaware.gov/title21/c041/sc08/index.shtml Delaware code regarding speed limits]<br />
<br />
=== Elevation ===<br />
<br />
{{RootPage2}} uses a '''real elevation''' method to set road elevations. This method sometimes requires the use of extra segments. This has the benefit of an enhanced look in the Live Map, and, more importantly, makes it easier to close a bridge or tunnel without affecting traffic to nearby homes and businesses.<br />
<br />
[[File:LABridge.png|550px|center|border]]<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 />
------------------------------------------------------------------------------------><br />
<br />
=== {{Anchor|FC cross reference}}Functional Classification Reference Chart ===<br />
<br />
Use this chart to determine the road type for Delaware roads based on the functional class.<br />
<br />
First, find the functional class of the road and determine if it is a signed, numbered highway in one of the highway systems.<br />
{| class="wikitable"<br />
|-<br />
!County!!Link<br />
|-<br />
|New Castle||https://www.deldot.gov/Publications/shop_de_maps/pdfs/Functional_Classification_NC.pdf<br />
|-<br />
|Kent||https://www.deldot.gov/Publications/shop_de_maps/pdfs/Functional_Classification_KC.pdf<br />
|-<br />
|Sussex||https://www.deldot.gov/Publications/shop_de_maps/pdfs/Functional_Classification_SC.pdf<br />
|-<br />
|}<br />
<br />
Follow the column for the road's highway system down to the row for the road's functional class to find the proper road type for that particular road.<br />
<br />
The DelDOT color coding is cross-referenced in the first column of the table for your convenience.<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="8"| <big>Highway Systems</big><br />
|-<br />
! Interstate<br />
! Interstate Business, Loop, Spur<br />
! US Hwy (incl. some [[wikipedia:special routes|special routes]])<br />
! US Hwy BUS, SPUR, LOOP<br />
! State Route Shielded<br />
! State Route Unshielded <br />
! Locally Maintained<br />
|-<br />
|<br />
| Examples<br />
| I-95<br />
| I-94 Business<br />
| US-113<br />
| US-13 Business<br />
| SR-30 SR-24<br />
| SR-2006<br />
| Roberts St<br />
|- <br />
! scope="row" rowspan="8" 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 />
| '''Interstate'''<br>[[File:DE Blue.png]]||{{Freeway|Fw}}||n/a||n/a||n/a||n/a||n/a||n/a<br />
|- <br />
| '''Other Freeway'''{{ref label|a|a}}[[File:DE DarkRed.png]]||n/a||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}<br />
|- <br />
| '''Other Expressway'''{{ref label|a|a}}[[File:DE DarkRed.png]]||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}<br />
|- <br />
| '''Other Principal Arterial'''[[File:DE Red.png]]||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}<br />
|- <br />
| '''Minor Arterial'''[[File:DE Green.png]]||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}<br />
|- <br />
| '''Urban or Rural-Major Collector'''[[File:DE Purple.png]]||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}||{{Primary Street|PS}}<br />
|- <br />
| '''Rural Minor Collector'''<br />
[[File:DE Yellow.png]]<br />
||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}<br/>{{Street}}||{{Street}}<br />
|- <br />
| '''Local Roads or <br>Not Classified''' [[File:DE Gray.png]]||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}<br/>{{Street}}||{{Street}}<br />
|}<br />
{{note|a|a}}Since Delaware combines these two classes, use the criteria from the [[Road_types#Freeway|Freeway page]] to determine if the road should typed as a freeway or major highway.<br />
<br />
</div></div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Delaware/Major_roads/Main&diff=177473Delaware/Major roads/Main2022-10-26T16:14:35Z<p>Phuz: </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 />
* {{RootPage2}} uses '''SR-##''' for all state routes (e.g. '''SR-58''')<br />
* If the primary name is a street name and the road also has a US or state route (SR), add it to the alt name (e.g. Primary Name: Capitol Trl, Alternate Name1: SR-2, Alternate Name2: Kirkwood Hwy). If a divided road, also add the cardinal direction to the alt name. e.g. "SR-7 N" on the northbound side and "SR-7 S" on the southbound side. When using alt names, be sure to be consistent and avoid gaps in naming, as this can cause routing issues with detour prevention. If the road switches back and forth between divided and two-way you should add a simple SR-## Alt Name for the entire length as well to avoid detour prevention.<br />
* Generally, regarding state route numbers, even numbers run east-west and odd numbers run north-south<br />
* Some {{RootPage2}} routes are continuations from other neighboring state routes. e.g., SR-273, SR-896, SR-299. <br />
<br />
==== Locking standard ====<br />
{{Lock Standard State|NORTHEAST}}<br />
<br />
<!-- <br />
{{Locking Standard|title=Statewide|Fwy=5|Ramp=Highest rank of connected segments|MH=3|mH=3|PS=1|Street=1}}<br />
--><br />
<br />
=== Speed Limits ===<br />
{{RootPage2}} follows the [[Speed limits|national guideline]] for speed limits, with a few exceptions listed below.<br />
====Delaware guidelines====<br />
* When a speed limit changes at an intersection, the sign for the new speed zone can be found up to 200 feet after the intersection. Map the change at the junction if signs immediately after the junction on each side are different speed limits. <br />
* If the speed limit changes more than 200 feet from the intersection, add a junction at the sign and make the speed limit change there. <br />
* If opposing speed limit signs are opposite each other, attempt to make the change as close as possible to the actual speed limit signs but do not create a new segment if within 200 feet of a junction. When adding changing speed limits, choose the junction that is on the higher speed limit side. Basically if the change is going to happen slightly early or late, best to have a lower speed limit come earlier and a higher speed limit come later.<br />
* Long term work zone speed limits may be mapped instead of the "ordinary time" speed limits. If placing a work zone limit, use Livemap to place a UR there, note that it is a temporary speed limit, and add [CONSTRUCTION] somewhere in the comment. <br />
* If no speed limit sign is posted, the default speed limits in Delaware are<br />
** Residential or business district: 25 MPH<br />
** Two lane road: 50 MPH<br />
** Divided highway: 55 MPH<br />
<br />
==== Town Speed Limits ====<br />
<br />
Do not assume every housing development is 25 MPH. Some localities have lower limits. Below is a list of some of them:<br />
<br />
* [http://www.southbethany.org/index.php?content=16 Bethany Beach]: 20 MPH<br />
* Elsmere: 20 MPH<br />
<br />
==== Special notes ====<br />
<br />
Delaware (especially NCCo) is really bad about signing speed limits on many roads. So even though the law says an unsigned road is above values, outside or rural areas of the state, that is probably not the case. May need to infer some speed limits based on signage pretty far down the highway. <br />
<br />
<br />
====Summary of National Guidelines====<br />
* Only map speeds found on '''regulatory''' white rectangular signs with black lettering.<br />
* Do not map '''advisory''' speed limits (generally an orange or amber rectangular sign with black lettering).<br />
* Where there are variable speed limits, map only the speed limit which is in effect most of the time during daylight hours (most hours of the day, days of the week).<br />
* Do not map special speed limits for special vehicles. Waze only supports speed limits for private passenger cars.<br />
<br />
=====Link to Delaware speed limit laws=====<br />
*[http://delcode.delaware.gov/title21/c041/sc08/index.shtml Delaware code regarding speed limits]<br />
<br />
=== Elevation ===<br />
<br />
{{RootPage2}} uses a '''real elevation''' method to set road elevations. This method sometimes requires the use of extra segments. This has the benefit of an enhanced look in the Live Map, and, more importantly, makes it easier to close a bridge or tunnel without affecting traffic to nearby homes and businesses.<br />
<br />
[[File:LABridge.png|550px|center|border]]<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 />
------------------------------------------------------------------------------------><br />
<br />
=== {{Anchor|FC cross reference}}Functional Classification Reference Chart ===<br />
<br />
Use this chart to determine the road type for Delaware roads based on the functional class.<br />
<br />
First, find the functional class of the road and determine if it is a signed, numbered highway in one of the highway systems.<br />
{| class="wikitable"<br />
|-<br />
!County!!Link<br />
|-<br />
|New Castle||https://www.deldot.gov/Publications/shop_de_maps/pdfs/Functional_Classification_NC.pdf<br />
|-<br />
|Kent||https://www.deldot.gov/Publications/shop_de_maps/pdfs/Functional_Classification_KC.pdf<br />
|-<br />
|Sussex||https://www.deldot.gov/Publications/shop_de_maps/pdfs/Functional_Classification_SC.pdf<br />
|-<br />
|}<br />
<br />
Follow the column for the road's highway system down to the row for the road's functional class to find the proper road type for that particular road.<br />
<br />
The DelDOT color coding is cross-referenced in the first column of the table for your convenience.<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="8"| <big>Highway Systems</big><br />
|-<br />
! Interstate<br />
! Interstate Business, Loop, Spur<br />
! US Hwy (incl. some [[wikipedia:special routes|special routes]])<br />
! US Hwy BUS, SPUR, LOOP<br />
! State Route Shielded<br />
! State Route Unshielded <br />
! Locally Maintained<br />
|-<br />
|<br />
| Examples<br />
| I-95<br />
| US-113<br />
| US-13 Business<br />
| SR-30 SR-24<br />
| SR-2006<br />
| Roberts St<br />
|- <br />
! scope="row" rowspan="8" 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 />
| '''Interstate'''<br>[[File:DE Blue.png]]||{{Freeway|Fw}}||n/a||n/a||n/a||n/a||n/a||n/a<br />
|- <br />
| '''Other Freeway'''{{ref label|a|a}}[[File:DE DarkRed.png]]||n/a||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}<br />
|- <br />
| '''Other Expressway'''{{ref label|a|a}}[[File:DE DarkRed.png]]||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}<br />
|- <br />
| '''Other Principal Arterial'''[[File:DE Red.png]]||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}<br />
|- <br />
| '''Minor Arterial'''[[File:DE Green.png]]||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}<br />
|- <br />
| '''Urban or Rural-Major Collector'''[[File:DE Purple.png]]||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}||{{Primary Street|PS}}<br />
|- <br />
| '''Rural Minor Collector'''<br />
[[File:DE Yellow.png]]<br />
||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}<br/>{{Street}}||{{Street}}<br />
|- <br />
| '''Local Roads or <br>Not Classified''' [[File:DE Gray.png]]||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}<br/>{{Street}}||{{Street}}<br />
|}<br />
{{note|a|a}}Since Delaware combines these two classes, use the criteria from the [[Road_types#Freeway|Freeway page]] to determine if the road should typed as a freeway or major highway.<br />
<br />
</div></div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Delaware/Major_roads/Main&diff=177472Delaware/Major roads/Main2022-10-26T16:05:44Z<p>Phuz: </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 />
* {{RootPage2}} uses '''SR-##''' for all state routes (e.g. '''SR-58''')<br />
* If the primary name is a street name and the road also has a US or state route (SR), add it to the alt name (e.g. Primary Name: Capitol Trl, Alternate Name1: SR-2, Alternate Name2: Kirkwood Hwy). If a divided road, also add the cardinal direction to the alt name. e.g. "SR-7 N" on the northbound side and "SR-7 S" on the southbound side. When using alt names, be sure to be consistent and avoid gaps in naming, as this can cause routing issues with detour prevention. If the road switches back and forth between divided and two-way you should add a simple SR-## Alt Name for the entire length as well to avoid detour prevention.<br />
* Generally, regarding state route numbers, even numbers run east-west and odd numbers run north-south<br />
* Some {{RootPage2}} routes are continuations from other neighboring state routes. e.g., SR-273, SR-896, SR-299. <br />
<br />
==== Locking standard ====<br />
{{Lock Standard State|NORTHEAST}}<br />
<br />
<!-- <br />
{{Locking Standard|title=Statewide|Fwy=5|Ramp=Highest rank of connected segments|MH=3|mH=3|PS=1|Street=1}}<br />
--><br />
<br />
=== Speed Limits ===<br />
{{RootPage2}} follows the [[Speed limits|national guideline]] for speed limits, with a few exceptions listed below.<br />
====Delaware guidelines====<br />
* When a speed limit changes at an intersection, the sign for the new speed zone can be found up to 200 feet after the intersection. Map the change at the junction if signs immediately after the junction on each side are different speed limits. <br />
* If the speed limit changes more than 200 feet from the intersection, add a junction at the sign and make the speed limit change there. <br />
* If opposing speed limit signs are opposite each other, attempt to make the change as close as possible to the actual speed limit signs but do not create a new segment if within 200 feet of a junction. When adding changing speed limits, choose the junction that is on the higher speed limit side. Basically if the change is going to happen slightly early or late, best to have a lower speed limit come earlier and a higher speed limit come later.<br />
* Long term work zone speed limits may be mapped instead of the "ordinary time" speed limits. If placing a work zone limit, use Livemap to place a UR there, note that it is a temporary speed limit, and add [CONSTRUCTION] somewhere in the comment. <br />
* If no speed limit sign is posted, the default speed limits in Delaware are<br />
** Residential or business district: 25 MPH<br />
** Two lane road: 50 MPH<br />
** Divided highway: 55 MPH<br />
<br />
==== Town Speed Limits ====<br />
<br />
Do not assume every housing development is 25 MPH. Some localities have lower limits. Below is a list of some of them:<br />
<br />
* [http://www.southbethany.org/index.php?content=16 Bethany Beach]: 20 MPH<br />
* Elsmere: 20 MPH<br />
<br />
==== Special notes ====<br />
<br />
Delaware (especially NCCo) is really bad about signing speed limits on many roads. So even though the law says an unsigned road is above values, outside or rural areas of the state, that is probably not the case. May need to infer some speed limits based on signage pretty far down the highway. <br />
<br />
<br />
====Summary of National Guidelines====<br />
* Only map speeds found on '''regulatory''' white rectangular signs with black lettering.<br />
* Do not map '''advisory''' speed limits (generally an orange or amber rectangular sign with black lettering).<br />
* Where there are variable speed limits, map only the speed limit which is in effect most of the time during daylight hours (most hours of the day, days of the week).<br />
* Do not map special speed limits for special vehicles. Waze only supports speed limits for private passenger cars.<br />
<br />
=====Link to Delaware speed limit laws=====<br />
*[http://delcode.delaware.gov/title21/c041/sc08/index.shtml Delaware code regarding speed limits]<br />
<br />
=== Elevation ===<br />
<br />
{{RootPage2}} uses a '''real elevation''' method to set road elevations. This method sometimes requires the use of extra segments. This has the benefit of an enhanced look in the Live Map, and, more importantly, makes it easier to close a bridge or tunnel without affecting traffic to nearby homes and businesses.<br />
<br />
[[File:LABridge.png|550px|center|border]]<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 />
------------------------------------------------------------------------------------><br />
<br />
=== {{Anchor|FC cross reference}}Functional Classification Reference Chart ===<br />
<br />
Use this chart to determine the road type for Delaware roads based on the functional class.<br />
<br />
First, find the functional class of the road and determine if it is a signed, numbered highway in one of the highway systems.<br />
New Castle County: [https://www.deldot.gov/Publications/shop_de_maps/pdfs/Functional_Classification_NC.pdf]<br />
Kent County: [https://www.deldot.gov/Publications/shop_de_maps/pdfs/Functional_Classification_KC.pdf]<br />
Sussex County: [https://www.deldot.gov/Publications/shop_de_maps/pdfs/Functional_Classification_SC.pdf]<br />
<br />
Follow the column for the road's highway system down to the row for the road's functional class to find the proper road type for that particular road.<br />
<br />
The DelDOT color coding is cross-referenced in the first column of the table for your convenience.<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="8"| <big>Highway Systems</big><br />
|-<br />
! Interstate<br />
! Interstate Business, Loop, Spur<br />
! US Hwy (incl. some [[wikipedia:special routes|special routes]])<br />
! US Hwy BUS, SPUR, LOOP<br />
! State Route Shielded<br />
! State Route Unshielded <br />
! Locally Maintained<br />
|-<br />
|<br />
| Examples<br />
| I-95<br />
| US-113<br />
| US-13 Business<br />
| SR-30 SR-24<br />
| SR-2006<br />
| Roberts St<br />
|- <br />
! scope="row" rowspan="8" 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 />
| '''Interstate'''<br>[[File:DE Blue.png]]||{{Freeway|Fw}}||n/a||n/a||n/a||n/a||n/a||n/a<br />
|- <br />
| '''Other Freeway'''{{ref label|a|a}}[[File:DE DarkRed.png]]||n/a||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}||{{Freeway|Fw}}<br />
|- <br />
| '''Other Expressway'''{{ref label|a|a}}[[File:DE DarkRed.png]]||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}<br />
|- <br />
| '''Other Principal Arterial'''[[File:DE Red.png]]||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Major Highway|Major}}<br />
|- <br />
| '''Minor Arterial'''[[File:DE Green.png]]||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}<br />
|- <br />
| '''Urban or Rural-Major Collector'''[[File:DE Purple.png]]||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}||{{Primary Street|PS}}<br />
|- <br />
| '''Rural Minor Collector'''<br />
[[File:DE Yellow.png]]<br />
||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}<br/>{{Street}}||{{Street}}<br />
|- <br />
| '''Local Roads or <br>Not Classified''' [[File:DE Gray.png]]||n/a||{{Major Highway|Major}}||{{Major Highway|Major}}||{{Minor Highway|Minor}}||{{Minor Highway|Minor}}||{{Primary Street|PS}}<br/>{{Street}}||{{Street}}<br />
|}<br />
{{note|a|a}}Since Delaware combines these two classes, use the criteria from the [[Road_types#Freeway|Freeway page]] to determine if the road should typed as a freeway or major highway.<br />
<br />
</div></div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=176764User:Phuz2022-08-13T16:28:22Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
***Mentored by voludu2<br />
**R5 (May 2021)<br />
***Mentored by RussPA<br />
*'''Leadership'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****Recruited new members and brought up to speed on DE standards and gave guidance on problem areas<br />
****Worked with DelDOT personnel to help provide editors with more accurate closure information<br />
****Closely monitored the I-95 corridor through Wilmington for the "Restore the Corridor" project to ensure closures and contraflow locations were up to date<br />
*****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
****Entire State (May 2021)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
*****Maintain seasonal speed limits from Corolla to Cape Hatteras<br />
*****Assist with URs and heavy PUR load during tourist season<br />
*****Work with towns that incorporate road closures during turnover days<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaids'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
**Luzerne Co, PA HN Mini-Raid (March 2021)<br />
*'''Other Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
***Populate data for statewide CDPs to determine which should be seeded within WME<br />
**NOR Closure Bot (July 2020 - Present)<br />
***Co-developed with [[usa:User:Doctorblah|'''doctorblah''']]<br />
***Incorporate feeds from each state's DOT traffic reporting system to provide immediate posting in the state's closure channel with detailed information and WME Permalink of the location<br />
**WME DOT Cameras [SCRIPT] (July 2020-Present)<br />
***Co-developed with [[usa:User:Doctorblah|'''doctorblah''']]<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
***Provides camera icon overlays in WME to show the location of the state's DOT cameras. When clicked, a popup will either show the live stream or the still image of that location.<br />
**WME DOT Advisories [SCRIPT] (October 2020 - Present)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
***Provides advisory markers in WME to show the location of live incidents and traffic advisories, sourced from the state's DOT feed. When clicked, the popup will provide the description from the DOT, pertinent dates, and any additional hyperlinks (if applicable)<br />
**WME Fix UR Interface [SCRIPT]<br />
***https://greasyfork.org/en/scripts/438755-wme-fix-ur-interface<br />
***Restores the original look & feel of the UR interface after Waze developers modified it significantly in January 2022<br />
**JB U-Turn Sheet Missing Data (February - March 2021)<br />
***Scanned all segments in sheets to backfill missing data for all regions in US<br />
**Closure Bot (August 2022 - Present)<br />
***Teamed up to with SAT region MSM '''The_Cre8r'''<br />
***Developed a bot to replace the existing closure bot webhook which runs on google sheets. Existing bot was unreliable and would often duplicate announcements which led to users becoming desensitized to its reporting.<br />
***Additional features were incorporated into this bot, such as showing the full comment history on closures, as well as making it a little more aesthetic.<br />
***Bot is being deployed in NOR and SAT initially and will eventually move into every region before becoming a global replacement.<br />
*'''Mentoring'''<br />
**Mentored DaWeatherBoy<br />
**Mentored SMac3265<br />
**Mentored GoBuckEyes3333<br />
**Mentored Drummin4JC<br />
*'''Beta Programs'''<br />
**WME<br />
**iOS<br />
*'''Meetups / Waze Cafes'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)<br />
**Hershey, PA (July 2021) (organizer)<br />
**Virtual (February 2021) (organizer)<br />
**Virtual NA Mega Meetup (February 21, 2021)<br />
<br />
{| class="wikitable"<br />
|-<br />
!Script!!Link<br />
|-<br />
|WME DOT Cameras||https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
|-<br />
|WME DOT Advisories||https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
|-<br />
|WME Fix UR Interface<br />
|https://www.waze.com/forum/viewtopic.php?t=338947<br />
|-<br />
|WME Disable Closed Updates<br />
|https://greasyfork.org/en/scripts/418411-wme-disable-closed-updates<br />
|}<br />
[[File:Script.png|thumb|[https://www.waze.com/forum/viewtopic.php?f=819&t=304760]]]</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=176763User:Phuz2022-08-13T16:27:36Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
***Mentored by voludu2<br />
**R5 (May 2021)<br />
***Mentored by RussPA<br />
*'''Leadership'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****Recruited new members and brought up to speed on DE standards and gave guidance on problem areas<br />
****Worked with DelDOT personnel to help provide editors with more accurate closure information<br />
****Closely monitored the I-95 corridor through Wilmington for the "Restore the Corridor" project to ensure closures and contraflow locations were up to date<br />
*****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
****Entire State (May 2021)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
*****Maintain seasonal speed limits from Corolla to Cape Hatteras<br />
*****Assist with URs and heavy PUR load during tourist season<br />
*****Work with towns that incorporate road closures during turnover days<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaids'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
**Luzerne Co, PA HN Mini-Raid (March 2021)<br />
*'''Other Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
***Populate data for statewide CDPs to determine which should be seeded within WME<br />
**NOR Closure Bot (July 2020 - Present)<br />
***Co-developed with [[usa:User:Doctorblah|'''doctorblah''']]<br />
***Incorporate feeds from each state's DOT traffic reporting system to provide immediate posting in the state's closure channel with detailed information and WME Permalink of the location<br />
**WME DOT Cameras [SCRIPT] (July 2020-Present)<br />
***Co-developed with [[usa:User:Doctorblah|'''doctorblah''']]<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
***Provides camera icon overlays in WME to show the location of the state's DOT cameras. When clicked, a popup will either show the live stream or the still image of that location.<br />
**WME DOT Advisories [SCRIPT] (October 2020 - Present)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
***Provides advisory markers in WME to show the location of live incidents and traffic advisories, sourced from the state's DOT feed. When clicked, the popup will provide the description from the DOT, pertinent dates, and any additional hyperlinks (if applicable)<br />
**WME Fix UR Interface [SCRIPT]<br />
***https://greasyfork.org/en/scripts/438755-wme-fix-ur-interface<br />
***Restores the original look & feel of the UR interface after Waze developers modified it significantly in January 2022<br />
**JB U-Turn Sheet Missing Data (February - March 2021)<br />
***Scanned all segments in sheets to backfill missing data for all regions in US<br />
**Closure Bot (August 2022 - Present)<br />
***Teamed up to with SAT region MSM '''The_Cre8r'''<br />
***Developed a bot to replace the existing closure bot webhook which runs on google sheets. Existing bot was unreliable and would often duplicate announcements which led to users becoming desensitized to its reporting.<br />
***Additional features were incorporated into this bot, such as showing the full comment history on closures, as well as making it a little more aesthetic.<br />
***Bot is being deployed in NOR and SAT initially and will eventually move into every region before become a global replacement.<br />
*'''Mentoring'''<br />
**Mentored DaWeatherBoy<br />
**Mentored SMac3265<br />
**Mentored GoBuckEyes3333<br />
**Mentored Drummin4JC<br />
*'''Beta Programs'''<br />
**WME<br />
**iOS<br />
*'''Meetups / Waze Cafes'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)<br />
**Hershey, PA (July 2021) (organizer)<br />
**Virtual (February 2021) (organizer)<br />
**Virtual NA Mega Meetup (February 21, 2021)<br />
<br />
{| class="wikitable"<br />
|-<br />
!Script!!Link<br />
|-<br />
|WME DOT Cameras||https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
|-<br />
|WME DOT Advisories||https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
|-<br />
|WME Fix UR Interface<br />
|https://www.waze.com/forum/viewtopic.php?t=338947<br />
|-<br />
|WME Disable Closed Updates<br />
|https://greasyfork.org/en/scripts/418411-wme-disable-closed-updates<br />
|}<br />
[[File:Script.png|thumb|[https://www.waze.com/forum/viewtopic.php?f=819&t=304760]]]</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=176139User:Phuz2022-06-16T01:12:34Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
***Mentored by voludu2<br />
**R5 (May 2021)<br />
***Mentored by RussPA<br />
*'''Leadership'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****Recruited new members and brought up to speed on DE standards and gave guidance on problem areas<br />
****Worked with DelDOT personnel to help provide editors with more accurate closure information<br />
****Closely monitored the I-95 corridor through Wilmington for the "Restore the Corridor" project to ensure closures and contraflow locations were up to date<br />
*****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
****Entire State (May 2021)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
*****Maintain seasonal speed limits from Corolla to Cape Hatteras<br />
*****Assist with URs and heavy PUR load during tourist season<br />
*****Work with towns that incorporate road closures during turnover days<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaids'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
**Luzerne Co, PA HN Mini-Raid (March 2021)<br />
*'''Other Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
***Populate data for statewide CDPs to determine which should be seeded within WME<br />
**NOR Closure Bot (July 2020-Present)<br />
***Co-developed with [[usa:User:Doctorblah|doctorblah]]<br />
***Incorporate feeds from each state's DOT traffic reporting system to provide immediate posting in the state's closure channel with detailed information and WME Permalink of the location<br />
**WME DOT Cameras [SCRIPT] (July 2020-Present)<br />
***Co-developed with [[usa:User:Doctorblah|doctorblah]]<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
***Provides camera icon overlays in WME to show the location of the state's DOT cameras. When clicked, a popup will either show the live stream or the still image of that location<br />
**WME DOT Advisories [SCRIPT] (October 2020-Present)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
***Provides advisory markers in WME to show the location of live incidents and traffic advisories, sourced from the state's DOT feed. When clicked, the popup will provide the description from the DOT, pertinent dates, and any additional hyperlinks (if applicable)<br />
**WME Fix UR Interface [SCRIPT]<br />
***https://greasyfork.org/en/scripts/438755-wme-fix-ur-interface<br />
***Restores the original look & feel of the UR interface after Waze developers modified it significantly in January 2022<br />
**JB U-Turn Sheet Missing Data (February-March 2021)<br />
***Scanned all segments in sheets to backfill missing data for all regions in US<br />
*'''Mentoring'''<br />
**Mentored DaWeatherBoy<br />
**Mentored SMac3265<br />
**Mentored GoBuckEyes3333<br />
**Mentored Drummin4JC<br />
*'''Beta Programs'''<br />
**WME<br />
**iOS<br />
*'''Meetups / Waze Cafes'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)<br />
**Hershey, PA (July 2021) (organizer)<br />
**Virtual (February 2021) (organizer)<br />
**Virtual NA Mega Meetup (February 21, 2021)<br />
<br />
{| class="wikitable"<br />
|-<br />
!Script!!Link<br />
|-<br />
|WME DOT Cameras||https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
|-<br />
|WME DOT Advisories||https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
|-<br />
|WME Fix UR Interface<br />
|https://www.waze.com/forum/viewtopic.php?t=338947<br />
|-<br />
|WME Disable Closed Updates<br />
|https://greasyfork.org/en/scripts/418411-wme-disable-closed-updates<br />
|}<br />
[[File:Script.png|thumb|[https://www.waze.com/forum/viewtopic.php?f=819&t=304760]]]</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=176079User:Phuz2022-06-08T21:38:07Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
***Mentored by voludu2<br />
**R5 (May 2021)<br />
***Mentored by RussPA<br />
*'''Leadership'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****Recruited new members and brought up to speed on DE standards and gave guidance on problem areas<br />
****Worked with DelDOT personnel to help provide editors with more accurate closure information<br />
****Closely monitored the I-95 corridor through Wilmington for the "Restore the Corridor" project to ensure closures and contraflow locations were up to date<br />
*****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
****Entire State (May 2021)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaid'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
**Luzerne Co, PA HN Mini-Raid (March 2021)<br />
*'''Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
**NOR Closure Bot (July 2020-Present)<br />
***Co-developed with doctorblah<br />
***Incorporate feeds from each state's DOT traffic reporting system to provide immediate posting in the state's closure channel with detailed information and WME Permalink of the location.<br />
**WME DOT Cameras [SCRIPT] (July 2020-Present)<br />
***Co-developed with doctorblah<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
***Provides camera icon overlays in WME to show the location of the state's DOT cameras. When clicked, a popup will either show the live stream or the still image of that location.<br />
**WME DOT Advisories [SCRIPT] (October 2020-Present)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
***Provides advisory markers in WME to show the location of live incidents and traffic advisories, sourced from the state's DOT feed. When clicked, the popup will provide the description from the DOT, pertinent dates, and any additional hyperlinks (if applicable).<br />
**JB U-Turn Sheet Missing Data (February-March 2021)<br />
***Scanned all segments in sheets to backfill missing data for all regions in US<br />
*'''Mentoring'''<br />
**Mentored DaWeatherBoy<br />
**Mentored SMac3265<br />
**Mentored GoBuckEyes3333<br />
**Mentored Drummin4JC<br />
*'''Beta Programs'''<br />
**WME<br />
***LG<br />
***Shields<br />
**iOS<br />
*'''Meetup / Waze Cafe'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)<br />
**Hershey, PA (July 2021) (organizer)<br />
**Virtual (February 2021) (organizer)<br />
**Virtual NA Mega Meetup (February 21, 2021)<br />
<br />
{| class="wikitable"<br />
|-<br />
!Script!!Link<br />
|-<br />
|WME DOT Cameras||https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
|-<br />
|WME DOT Advisories||https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
|-<br />
|WME Fix UR Interface<br />
|https://www.waze.com/forum/viewtopic.php?t=338947<br />
|-<br />
|WME Disable Closed Updates<br />
|https://greasyfork.org/en/scripts/418411-wme-disable-closed-updates<br />
|}<br />
[[File:Script.png|thumb|[https://www.waze.com/forum/viewtopic.php?f=819&t=304760]]]</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=175797User:Phuz2022-03-15T16:25:32Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
***Mentored by voludu2<br />
**R5 (May 2021)<br />
***Mentored by RussPA<br />
*'''Leadership'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
****Entire State (May 2021)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaid'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
**Luzerne Co, PA HN Mini-Raid (March 2021)<br />
*'''Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
**NOR Closure Bot (July 2020-Present)<br />
***Co-developed with doctorblah<br />
**WME DOT Cameras [SCRIPT] (July 2020-Present)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
**WME DOT Advisories [SCRIPT] (October 2020-Present)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
**JB U-Turn Sheet Missing Data (February-March 2021)<br />
***Scanned all segments in sheets to backfill missing data for all regions in US<br />
*'''Mentoring'''<br />
**Mentored DaWeatherBoy for R1 to R2<br />
*'''Beta Programs'''<br />
**WME<br />
***LG<br />
***Shields<br />
**iOS<br />
*'''Meetup / Waze Cafe'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)<br />
**Hershey, PA (July 2021) (organizer)<br />
**Virtual (February 2021) (organizer)<br />
**Virtual NA Mega Meetup (February 21, 2021)<br />
<br />
{| class="wikitable"<br />
|-<br />
!Script!!Link<br />
|-<br />
|WME DOT Cameras||https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
|-<br />
|WME DOT Advisories||https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
|-<br />
|WME Fix UR Interface<br />
|https://www.waze.com/forum/viewtopic.php?t=338947<br />
|-<br />
|WME Disable Closed Updates<br />
|https://greasyfork.org/en/scripts/418411-wme-disable-closed-updates<br />
|}<br />
[[File:Script.png|thumb|[https://www.waze.com/forum/viewtopic.php?f=819&t=304760]]]</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=175796User:Phuz2022-03-15T16:24:02Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
***Mentored by voludu2<br />
**R5 (May 2021)<br />
***Mentored by RussPA<br />
*'''Leadership'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
****Entire State (May 2021)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaid'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
**Luzerne Co, PA HN Mini-Raid (March 2021)<br />
*'''Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
**DelDOT Closure Bot (July 2020-Present)<br />
**WME DOT Cameras [SCRIPT] (July 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
**WME DOT Advisories [SCRIPT] (October 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
**JB U-Turn Sheet Missing Data (February-March 2021)<br />
***Scanned all segments in sheets to backfill missing data for all regions in US<br />
*'''Mentoring'''<br />
**Mentored DaWeatherBoy for R1 to R2<br />
*'''Beta Programs'''<br />
**WME<br />
***LG<br />
***Shields<br />
**iOS<br />
*'''Meetup / Waze Cafe'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)<br />
**Hershey, PA (July 2021) (organizer)<br />
**Virtual (February 2021) (organizer)<br />
**Virtual NA Mega Meetup (February 21, 2021)<br />
<br />
{| class="wikitable"<br />
|-<br />
!Script!!Link<br />
|-<br />
|WME DOT Cameras||https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
|-<br />
|WME DOT Advisories||https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
|-<br />
|WME Fix UR Interface<br />
|https://www.waze.com/forum/viewtopic.php?t=338947<br />
|-<br />
|WME Disable Closed Updates<br />
|https://greasyfork.org/en/scripts/418411-wme-disable-closed-updates<br />
|}<br />
[[File:Script.png|thumb|[https://www.waze.com/forum/viewtopic.php?f=819&t=304760]]]</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Places/Parking_lot&diff=175656Places/Parking lot2022-02-17T23:14:04Z<p>Phuz: Updated guidance</p>
<hr />
<div>{{mbox|text=The development of the parking feature has been tabled and efforts should focus on improving Parking Lot Areas that have substantial benefit (ie, parking garage, college campus, sports complex, etc.)}}<br />
[[File:Parking_sign.png|300px|thumb|right]]<br />
<br />
The&nbsp;'''Parking Lot Area (PLA)'''&nbsp;Place marks a well-defined area constructed for off-street public or private parking, including parking structures and garages as well as at-grade lots. The parking lot feature in the app will recommend parking lots to Wazers navigating to a nearby destination. Waze will recommend lots within ⅔ mile of a Wazer's destination. As the feature matures, Waze will recommend the 'most popular' lots that other Wazers have chosen when navigating to the same destination.<br />
<br />
=={{@|Area or point}}==<br />
{{Anchor|Area or Point}}Parking lots can ONLY be added as an area as of August 1st, 2016. They are a special place category; you cannot add other categories to a parking lot place, or convert/add a Parking Lot category to another kind of place.<br />
<br />
==={{@|Parking lot point places}}===<br />
{{Anchor|The Parking-Lot Point Place}}As of this writing, you can no longer add Parking Lots as a point place.<br />
<br />
Existing point places should be evaluated for inclusion and either converted to an area if applicable or deleted to solve the [[Map Problems in Waze Map Editor#Parking lot input as point|Map Problem]] (MP) report.<br />
<br />
=={{@|Scope}}==<br />
{{Anchor|Principles|General Public Use|General Purpose Use|Distinctive and Significant|Interpreting_.27distinctive_and_significant.27}}At this time, parking lot areas (PLA) should be added to '''all lots''' including businesses with small parking lots (less than 10 spaces). Start by adding parking lots to event venues, shopping centers, airports, public use lots, garages, multi-use parking lots, popular lots with heavy usage or [[Glossary#UR|UR]]s, etc.<br />
[[File:Waze_PLA_Mall_Example.jpg|400px|thumb|right|Shopping Center PLA Example]]<br />
<u>For a mall or large shopping center</u>, break the parking lot up into multiple lots, as shown in the image to the right (use your discretion or discuss with your State Manager(s) or RC for official guidance if necessary.)<br />
<br />
<u>If a lot is stacked</u> (underground + surface), map it as one place covering the footprint of the parking lot / garage. Future UI enhancements may allow for better modeling of these lots.<br />
<br />
<u>If a lot has different entrances</u> serving different levels of a multi-level garage and you cannot drive from one level to another to park, but rather the levels are served independently by different entrances, then they should be mapped as multiple places. <br />
<br />
Care must be taken that stacked areas like this do not obscure each other. You do not want two areas with identical boundaries stacked on top of each other as it will be hard to notice or select the right one for editing in WME.<br />
<br />
As with all Area Places, a Parking Lot Area Place's geometry nodes should not be allowed to "snap" to adjacent road segments or junctions while being adjusted. Doing so can make the Area Place, as well as the adjacent segments or junctions, more difficult to modify.<br />
<br />
==={{@|On-premises parking}}===<br />
<br />
*It is important to create 2 separate places - one for the complex / place, and one for its designated parking lot.<br />
*Multiple parking lots for one place: Create separate parking lots so the best parking lot can be recommended.<br />
*Valet parking - Valet is a service attribute of a place but is also an attribute for a parking lot.<br />
*Multi-level lots should be created as single place with the shape of the overall parking surface outlined.<br />
<br />
==={{@|Underground parking lots}}===<br />
<br />
*It is still important to map these correctly so they can be routed to properly, and recommended appropriately in the client to users. Since the underground portion of the garage is not visible to drivers, it is not important to be displayed fully in the app.<br />
*To support the internal features of the client; The polygon must include all above ground areas, and the areas where it starts to go underground. See the [[#Drawing|Drawing section]] below for more details and examples on how to draw these lots.<br />
*If parking lots overlap with a Place, do not add "Parking Lot" category to a Place. Create a separate Area polygon for the parking lot.<br />
<br />
==={{@|Rental-car lots}}===<br />
<br />
*{{Anchor|Rental-car return|Rental-car return lots}}With the availability of the "Car Rental" Place, rental car facilities and returns, including at airports, should be marked with the Car Rental Place category for the desk and/or the building. If there is any customer parking, or return vehicle parking, then mark that area with the Parking Lot category.<br />
<br />
==={{@|Temporary lots}}===<br />
<br />
*Temporary lots for use at festivals, parades, concerts, etc., where temporary parking is being established specifically for the event can be added and named accordingly. Taking care to ensure that any temporary lots that are added, are removed as soon as the event is complete. '''On-street parking should not be added as a temporary lot.'''<br />
<br />
=={{@|Creating and editing parking lot areas}}==<br />
{{Anchor|Implementation}}<br />
{{mbox|type=caution|text=[[File:PlacesMenu.png|right]]<br />
When editing or creating parking lots and related URs, MPs, & PURs, please make sure you have the Parking Lots [[Map_Editor_Interface_and_Controls#Layers|layer]] enabled (under Places) so the existing PLAs on the map are not hidden.}}<br />
[[File:Waze_PLA_Example.jpg|300px|thumb|right|Outline building footprint only]]<br />
==={{@|Drawing}}===<br />
{{Anchor|Extent}}<br />
The Parking Lot Area (PLA) polygon should be drawn to include all parking spaces in the parking lot and the access lanes used to reach each parking space. To prevent creating overly complex polygons and unnecessary geometry points, small medians, curbed areas, and building corners on the scale of around 5 meters or less may be overlapped by the polygon and not cut out by extra geometry points. For multi-level garages, only the footprint of the structure should be outlined.<br />
<br />
Parking lots should never be attached, snapped or have their geometry extremely close to roads as this tends to make editing them difficult. Avoid including or touching any roads outside the parking lot. If a lot spans both sides of a street (excluding Parking Lot Roads), it must be mapped so '''the polygon does not overlap the street'''. This may require drawing the lot as separate places. ''If the lot is elevated above the street and the lot actually covers the street, then the PLA may overlap the street as well.''<br />
<br />
The entry/exit location should be added to the place and adjusted to the appropriate location.<br />
<br />
The following are examples of Parking Lot Areas with excessive and sufficient detail:<br />
<br />
<center><br />
{| class="wikitable"<br />
| style="background: red;" |[[File:Excessive_Detail.jpg|350px|thumb|center|Overly complex shape]]<br />
| style="background: lawngreen;" |[[File:Sufficient_Detail.jpg|350px|thumb|center|Accurate shape with sufficient detail]]<br />
|}</center><br />
<br />
For underground garages it is not important to draw the polygon to match the internal perimeter since there is no GPS signal underground. It is important that the polygon includes any above ground areas, and the underground areas near any entrances or exits in a single polygon. If a lot has more than one entrance/exit the polygon must be made to connect all the entrances and exits. You may use a PLR to show multiple entrances as well, allowing the routing to choose the best route to access the lot, just as an above ground lot is drawn. It is not important however to draw the polygon to the entire footprint of the garage. The accuracy of the entry point ([[Places#Setting_the_stop_point_for_a_Place|'''Setting the stop point''']]) is very important. {{Clear}}<br />
<center><br />
{| class="wikitable"<br />
| colspan="2;" style="background: #BEDCE5;" align="center" |'''[http://www.waze.com/editor/?env=usa&lon=-73.98899&lat=40.74062&zoom=7&venues=187433367.1874399210.3624518 Icon Parking]'''<br />
|-<br />
| style="background: red;" |[[File:Underground_lot_mapped_to_perimeter.png|400px|thumb|center|WRONG: Mapped to estimated underground Perimeter]]<br />
| style="background: lawngreen;" |[[File:Underground lot mapped to entrance.png|350px|thumb|center|CORRECT: mapped above ground, and entry/exit areas]]<br />
|-<br />
| colspan="2;" style="background: #BEDCE5;" align="center" |'''[http://www.waze.com/editor/?env=usa&lon=-85.75334&lat=38.25737&zoom=6&venues=179700095.1797328626.3614708 Parking Garage - Yum! Center]'''<br />
|-<br />
| style="background: red;" |[[File:Underground lot with multiple places.png|375px|thumb|center|WRONG: Multiple access points mapped as individual places for a single underground garage.]]<br />
| style="background: lawngreen;" |[[File:Underground lot with multiple access.png|350px|thumb|center|CORRECT: multiple access points included in a single polygon for an underground lot, the underground perimeter is not important.]]<br />
|-<br />
| style="background: #BEDCE5;" align="center" |'''[http://www.waze.com/editor/?env=usa&lon=-123.03897&lat=44.94261&zoom=7&mode=0&venueFilter=2&venues=155320769.1552945550.3513573 Chemeketa Parkade]'''<br />
| style="background: #BEDCE5;" align="center" |'''[http://www.waze.com/editor/?env=usa&lon=-73.58783&lat=40.73257&zoom=6&venueFilter=2 Nassau Community College]'''<br />
|-<br />
| style="background: lawngreen;" |[[File:Elevated lot over street.png|375px|thumb|center|CORRECT: Elevated lot built above street, mapped as a single PLA overlapping the street.]]<br />
| style="background: lawngreen;" |[[File:Ground level lots spanning streets mapped separate.png|375px|thumb|center|CORRECT:Ground level lots spanning streets mapped as separate PLAs. On-street parking not mapped as a PLA.]]<br />
<br />
|}</center><br />
<br />
==={{@|Naming}}===<br />
If a parking facility or area has a documented identity, such as {{nowrapcode|Beach Street Garage}}, {{nowrapcode|18th Avenue/Geary Lot}}, {{nowrapcode|Lot 7 - <Stadium name>}}, {{nowrapcode|Short-Term Parking - <Airport name>}}, {{nowrapcode|Cell Phone Lot - <Airport name>}}, etc., its Place should reflect that name to facilitate searches. Generic park-and-ride lots should be named consistently according to local custom, for example as {{nowrapcode|Park & Ride}}.<br />
<br />
The foundational guidance for naming a PLA when the lot serves another entity, is to follow this basic format:<br /><br />
'''<code>[Parking&nbsp;Descriptor]&nbsp;<restrictions>&nbsp;-&nbsp;[Entity&nbsp;served]</code>'''<br /><br />
The framework is {{u|not}} recursive. In other words, there is only one business served in any lot name, and the rest of the name is the descriptor. ''As a rule the descriptor will always have a word in it identifying it as parking, e.g. parking, garage, or lot.'' '''The descriptor can be:'''<br />
<br />
*'''Completely generic - ''' For single-business - single-lot<br />
<br />
::{{nowrapcode|Parking - Starbucks}}<br />
<br />
*'''Purpose descriptive -''' Where there is only one lot of the type<br />
<br />
::{{nowrapcode|Customer Parking - Office Depot}}, {{nowrapcode|Employee Parking - Office Depot}}, {{nowrapcode|Visitor Parking - LSU Eunice}}, {{nowrapcode|Employee Parking - MSY}} [airport]<br />
<br />
*'''Location descriptive -''' Where more than one lot serve the same purpose for the same place<br />
<br />
::{{nowrapcode|Southeast Lot - Big Hill Shopping Center}}, {{nowrapcode|Macy's Lot - Big Hill Shopping Center}}, {{nowrapcode|Grand Blvd Lot - Big Hill Shopping Center}}, {{nowrapcode|Target Garage - Big Hill Shopping Center}}, {{nowrapcode|Dillard's South Lot - Big Hill Shopping Center}}, {{nowrapcode|North Lot - Offices at Buildingtown Plaza}}<br />
<br />
*'''Named -''' Where the lot is given an official name<br />
<br />
::{{nowrapcode|Garage 2A - Mercedes-Benz Superdome}}, {{nowrapcode|Credit Card Lot - MSY}}<br />
<br />
===={{@|Examples}}====<br />
<br />
If a Parking Lot Area Place is contained within a larger Area Place, do not repeat the larger Area's full name. For example, if the Domestic Garage is contained within the "SFO San Francisco International Airport" Area Place boundaries, it need not be named "SFO San Francisco International Airport Domestic Garage"; "Domestic Garage - SFO" is sufficient.<br />
<br />
If a mall or shopping center has several lots which can be associated with various anchor stores in the mall/shopping center, the lots can be named for the anchor stores. For example: "Macy's Lot - Big Hill Shopping Center" <br />
<br />
In rare cases, a municipality or district provides public parking distinct from any other Area Place but without any documented or signed identity. These can be named after the municipality or district, for example, "Redwood City Public Parking". Do not use completely generic names such as "Parking" or "Public Parking" for anonymous parking facilities. <br />
<br />
A block range or specific address '''should not be used''' to name a lot. If the lot does not have an official and/or signed name, then leave the name blank, and be sure to add the address details in the address field. Some imported PLAs were created with the address or address block range as the name, these names should be removed accordingly. Check your local guidance for any variations.<br />
<br />
:'''NOTE:''' It is very important if there is no name for the lot that there be a proper address in the address field. If you don't know the exact address you should at least put the street the main entrance is on, and - if you can - an approximate house number. The address is needed to be displayed in the search results, and differentiate the lot from all the others. Users can see the address displayed, and know which lot it is when viewing the results list.<br />
<br />
===={{@|Restricted parking}}====<br />
If there are posted signs restricting the lot to only one certain category of users (e.g. Customers, Residents, Staff, Attendees, Permit Holders, Faculty, Students, etc.) ONLY, then put that restriction in the name. If the lot is restricted to more than one category of users, then put "(restricted access)" in the name. Also put the details of the restriction in the [[#description|description]].<br><br />
<br />
{{mbox|text=Omit the restriction in the name if it is self-explanatory (e.g., {{nowrapcode|Parking - Starbucks}}, is obviously for Starbucks patrons only).}}<br />
<br />
'''Examples:'''<br />
<br />
*{{nowrapcode|Lot D (attendees only) - Cheery Stadium}}<br />
*{{nowrapcode|Alpha Lot (permit only) - StudyHard University}} ''Parking allowed by permit only ( even if permits are available to multiple groups (eg for Students, and Faculty)''<br />
*{{nowrapcode|123 Somewhere St Lot (residents only)}}<br />
*{{nowrapcode|Bravo Lot (restricted access) - StudyHard University}} ''Parking allowed for Students, and Faculty ONLY''<br />
*{{nowrapcode|345 Other St Lot (restricted access)}} ''Parking allowed for resident, guests, and staff''<br />
<br />
==={{@|Description}}===<br />
Any lot which is fully restricted in some way (e.g. permit/resident/customer only), and not open to the public for general parking, must include that information as the first line of the description. If only some of the available spots are restricted, but there are some spots in the lot open to the public for general parking, then it should not be mentioned.<br><br />
'''Examples:'''<br />
<br />
*"Parking by permit only."<br />
*"Parking only for customers of John Doe's Supermarket"<br />
*"Parking only for residents of 123 Something St, and their guests"<br />
*"Parking restricted to 15 minutes or less"<br />
*"Valet parking only"<br />
<br />
If you know the details or times of the restrictions you may add that information in the descriptions as well for users to see. This will also help for when those features become available in WME to have the details handy for mapping.<br />
<br />
==={{@|Operator}}===<br />
When there is a recognized parking operator, select it from the list, otherwise, leave this field blank. If an Operator is missing from the list that you feel should be added, please send the information to your [[Regional Coordinator]] (RC).<br />
<br />
==={{@|Lot Type}}===<br />
[[File:Parking lot type.png|right]]<br />
At the top of the 'More Info' tab when a parking lot is selected you can set the Primary Lot Type. This setting affects whether a lot will be recommended in the client app when a Wazer searches for nearby parking, or as a suggested lot when searching for a destination. '''Any lots marked here as Restricted or Private {{U|will not be recommended}} to any users in the app for the time being.''' As the feature is further developed, there will be the ability to set more details on these restrictions so the lots may be recommended under certain circumstances. {{As of|2017|03}} these are the guidelines accepted for the application of these settings, designed for optimal user experience.<br />
<br />
*Mark all parking lots with unrestricted public access as '''Public'''. This includes free and publicly owned parking lots, as well as for-profit garages, in which a Wazer may park, regardless of intent.<br />
*Mark parking lots where some restrictions apply (customers, patrons, visitors), but the ability to see or select between them is useful to a Wazer, as '''Public'''. For example, a university campus with multiple student, visitor, or faculty parking lots, or a large shopping center that contains multiple patron-only parking lots. A suburban fast food chain's parking lot is not.<br />
**Otherwise, mark parking lots where some restrictions apply (customers, patrons, visitors) as '''Restricted'''.<br />
*Mark parking lots where parking is restricted to a specific audience (residents of an apartment parking lot, employee garage of an office complex), but the ability to see or select between them is useful to a Wazer, as '''Public'''. For example, Employee, or permit parking at an airport, or large compound, large housing developments with multiple permitted lot, etc.<br />
**Otherwise, mark parking lots where parking is restricted to a specific audience (residents of an apartment parking lot, employee garage of an office complex) as '''Private'''.<br />
<br />
==={{@|Locking standards}}===<br />
Due to this major shift in editing guidelines, it is recommended that once a Parking Lot Area (PLA) has been added, that it be locked to 3 to avoid newer editors, or those not familiar with the change, from editing or deleting the PLA.<br />
<br />
=={{@|Interface - more info}}==<br />
[[File:WME_PLA_UI_081016.jpg|thumb|right|WME User Interface - More info tab]]<br />
<br />
'''Opening hours''' - Hours lot is open. Set open times for the lot or select each day and the ''All day'' radio button for lots open 24 hours a day / 7 days a week. <br />
<br />
*''Cars can exit when lot is closed'' - Check if the lot or garage does not restrict egress after the lot is considered closed.<br />
*'''Cost'''{{Anchor|Free versus paid parking}}<br />
**Cost determination should be made based on parking lot fees for other similar and nearby lots for the same type of venue.<br />
***Example #1: Adding / editing parking lots near an airport; terminal parking may be the most expensive at $25/day, express parking the next level down (moderate) at $15/day and remote parking the next best option at $5/day (low).<br />
***Example #2: Hotel parking; on-site $50/day (expensive), self-parking garage at $30/day (moderate), and off-site parking at $15/day (low)<br />
**Each lot within approximately ⅔ mile (1 km) radius should be taken into consideration for PLA cost determination where appropriate.<br />
<br />
*'''Services '''(select services listed below)<br />
**Reservations - Lot accepts reservations or accepts pre-paid parking passes or permits.<br />
**Disability parking - Spaces exist for handicap parking / wheelchair accessible spaces.<br />
**Carpool Parking - Reserved spots exist for people who carpool to the location.<br />
**EV Charging - Lot contains a station to charge electric vehicles.<br />
{{mbox | type = important| text = If adding the EV Charging Station attribute, also add a separate point Place for the EV station, as described in the [[Places/Charging station]] wiki.}}<br />
<br />
**Car wash - A car wash is on premises within the parking lot (some airports and other venues have amenities such as this for those parking within the lot).<br />
**Security - On-site security for the specific lot exists<br />
*'''Number of Spots'''<br />
**List the most accurate number of spots within the specified parking lot area polygon.<br />
*'''Contact info'''<br />
**A link to the main venue to which the parking lot belongs or to the parking lot vendor's site (if applicable) is permissible here.<br />
*'''Phone'''<br />
**The phone number for the main venue to which the parking lot belongs or to the parking lot vendor is permissible here.<br />
{{clear}}<br />
<br />
=={{@|Parking lot photos}}==<br />
[[File:PLA photo.jpg|750px|center]]<br />
An ideal photo for a parking lot place should show the parking lot entrance, including any signage that would help a driver select the correct lot. Photos that show the parking lot in the context of surrounding structures are also useful.<br />
<br />
=={{@|Parking lot roads}}==<br />
Don't forget to map any necessary [[parking lot roads]], to allow for proper navigation into and out of the parking lot. The parking lot place is not a substitute for properly mapped PLRs, as the two features are independent of each other. The [[Best map editing practice#Parking Lots|best practices page]] provides detailed guidance on how to map roads in parking lots.<br />
<br />
'''Parking lot roads are not required simply because a PLA exists.''' It is OK for small lots which do not qualify for their own PLRs to still be mapped as a PLA.<br />
<br />
=={{@|What does not qualify as a PLA?}}==<br />
<br />
==={{@|On-street parking}}===<br />
[[File:LotsnoStreet.png|thumb|right|The surrounding parking lots have been mapped, but on-street parking along State St and College Ave has not been mapped.]]{{Anchor|Examples}}{{Red|On-street parking should not be added at this time.}}<br />
<br />
==={{@|Gas stations}}===<br />
<br />
[[Places/Gas station#Area_size|Gas stations]] are already drawn on the map as an area and typical usage includes parking to get gas or enter the convenience store (when present). They are therefore handled specially by the servers, and '''do not require an additional PLA to be drawn on top of the gas station area'''. However, if there is a significant parking area which is worthy to be recommended to users who are navigating to nearby venues (e.g. a truck stop, etc.), then you ''may'' add a PLA there.<br />
<br />
==={{@|Valet only facility}}===<br />
Parking lots or garages accessed exclusively by valet staff, and situated away from the valet drop off point should not be added to the map. (If regular drivers are not allowed to drive up to the valet facility, and rather must drop the vehicle at a different location, and the valet drivers are the only ones driving to this facility location, then it serves no purpose being recommended ever.<br />
<br />
In such cases, where the valet drop off is not near the stop point for the place it services, the valet drop off may be added as a PLA, and marked as valet only in the name.<br />
<br />
If regular drivers are allowed to drop their vehicle at the valet facility, or there is mixed use of the facility where non-valet users can park as well, then a PLA '''should''' be added.<br />
<!--[[File:No_PLA.jpg|500px|thumb|center|Where PLAs are not needed]]--></div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=175632User:Phuz2022-02-09T17:47:45Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
**R5 (May 2021)<br />
*'''Leadership'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
****Entire State (May 2021)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaid'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
**Luzerne Co, PA HN Mini-Raid (March 2021)<br />
*'''Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
**DelDOT Closure Bot (July 2020-Present)<br />
**WME DOT Cameras [SCRIPT] (July 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
**WME DOT Advisories [SCRIPT] (October 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
**JB U-Turn Sheet Missing Data (February-March 2021)<br />
***Scanned all segments in sheets to backfill missing data for all regions in US<br />
*'''Mentoring'''<br />
**Mentored by G_W1Z (R1 through R3 informally)<br />
**Mentored by voludu2 for R4 (formal)<br />
**Mentored by RussPA for R5<br />
**Mentored DaWeatherBoy for R1 to R2<br />
*'''Beta Programs'''<br />
**WME<br />
***LG<br />
***Shields<br />
**iOS<br />
*'''Meetup / Waze Cafe'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)<br />
**Hershey, PA (July 2021) (organizer)<br />
**Virtual (February 2021) (organizer)<br />
**Virtual NA Mega Meetup (February 21, 2021)<br />
<br />
{| class="wikitable"<br />
|-<br />
!Script!!Link<br />
|-<br />
|WME DOT Cameras||https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
|-<br />
|WME DOT Advisories||https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
|-<br />
|WME Fix UR Interface<br />
|https://www.waze.com/forum/viewtopic.php?t=338947<br />
|-<br />
|WME Disable Closed Updates<br />
|https://greasyfork.org/en/scripts/418411-wme-disable-closed-updates<br />
|}<br />
[[File:Script.png|thumb|[https://www.waze.com/forum/viewtopic.php?f=819&t=304760]]]</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Railroad_crossing&diff=175523Railroad crossing2022-01-29T12:16:00Z<p>Phuz: /* Relative to the railroad */ Updated zoom level</p>
<hr />
<div>{{construction<br />
| contact = https://www.waze.com/forum/viewtopic.php?t=335756<br />
| contacttype = forum<br />
| draft = no<br />
| open = yes<br />
| revision = no<br />
| section = no<br />
| talk = no<br />
}}<br />
[[File:RRC simple.png|thumb|right]]<br />
The ''Railroad crossing (RRC)'' feature was added to the Waze app in response to long-standing feature requests from users, railroad safety advocates, and emergency managers. Acting as a permanent hazard, RRCs alert users as they approach the RRC to ensure awareness of hazards such as uneven road surfaces, stopped traffic, and to ensure vehicles do not turn down the railroad tracks instead of nearby parallel road. The ''Railroad crossing'' notifications can be disabled by users in the app's alert settings. <br />
<br />
RRCs can only be added via the WME. To see RRCs on the WME, enable the ``Railroad crossings`` layer in the [[Map_Editor_Interface_and_Controls#Layers|layers menu]]. <br />
==When to Add==<br />
A RRC should be added to every segment that intersects a functional railroad line at grade AND has a gate, sign, or other control device. Because each RRC works on only one segment, this means that RRCs must also be placed on AGCs that cross the railroad independently of the relevant main road. <br />
==Placement==<br />
To add a RRC, select ''Railroad crossing'' from the ''Roads'' dropdown menu in the toolbar at the top of the WME. RRC should be added to the Waze map where the road meets the railroad tracks. This is very similar to the [[Cameras]] feature. <br />
===Generally===<br />
Important: the location of the railroad crossing in the app is set by the RRC icon itself. The red dot is only a handle used for alignment. Therefore, make all functional decisions based on the RRC icon, not on the red dot.<br />
===Relative to the road===<br />
On one-way segments (including the sides of a divided road), the RRC icon should be placed more or less on top of the segment which actually crosses the railroad. On two-way segments, the RRC icons should be offset slightly from the segment, on top of their respective lanes of traffic. Just make sure that the segment closest to the RRC icon is the one that actually crosses the railroad (important in tight areas—zoom in judiciously!).<br />
===Relative to the railroad===<br />
The icon should be made to touch the railroad “where the rubber meets the rail”—i.e., when the driver first hits the tracks with their wheels—at a tight zoom level (around 20). This is pretty straightforward at simple perpendicular crossings, but is important to consider when railroads cross roads at oblique angles.<br />
==Alignment==<br />
Similar to the [[Cameras]] feature, use the red handle to rotate the RRC icon to "face" in the direction of car/truck traffic. <br />
<br />
Align the road part of the RRC icon with the road segment that intersects the railroad. Again, it is the road part that must be parallel with the road segment.<br />
<br />
The railroad tracks part of the RRC icon should be pointed toward the front, relative to the direction of travel. If the RRC icon represents a car driving across the railroad, the railroad tracks represent the front of that car.</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=175475User:Phuz2022-01-20T10:45:39Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
**R5 (May 2021)<br />
*'''Leadership'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
****Entire State (May 2021)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaid'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
**Luzerne Co, PA HN Mini-Raid (March 2021)<br />
*'''Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
**DelDOT Closure Bot (July 2020-Present)<br />
**WME DOT Cameras [SCRIPT] (July 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
**WME DOT Advisories [SCRIPT] (October 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
**JB U-Turn Sheet Missing Data (February-March 2021)<br />
***Scanned all segments in sheets to backfill missing data for all regions in US<br />
*'''Mentoring (Unofficial)'''<br />
**Mentored by G_W1Z (R1 through R3)<br />
**Mentored by voludu2 for R4<br />
**Mentored by RussPA for R5<br />
*'''Beta Programs'''<br />
**WME<br />
***LG<br />
***Shields<br />
**iOS<br />
*'''Meetup / Waze Cafe'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)<br />
**Hershey, PA (July 2021) (organizer)<br />
**Virtual (February 2021) (organizer)<br />
**Virtual NA Mega Meetup (February 21, 2021)<br />
<br />
{| class="wikitable"<br />
|-<br />
!Script!!Link<br />
|-<br />
|WME DOT Cameras||https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
|-<br />
|WME DOT Advisories||https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
|-<br />
|WME Fix UR Interface<br />
|https://www.waze.com/forum/viewtopic.php?t=338947<br />
|-<br />
|WME Disable Closed Updates<br />
|https://greasyfork.org/en/scripts/418411-wme-disable-closed-updates<br />
|}<br />
[[File:Script.png|thumb|[https://www.waze.com/forum/viewtopic.php?f=819&t=304760]]]</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=175474User:Phuz2022-01-20T10:43:18Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
**R5 (May 2021)<br />
*'''Manager'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
****Entire State (May 2021)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaid'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
**Luzerne Co, PA HN Mini-Raid (March 2021)<br />
*'''Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
**DelDOT Closure Bot (July 2020-Present)<br />
**WME DOT Cameras [SCRIPT] (July 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
**WME DOT Advisories [SCRIPT] (October 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
**JB U-Turn Sheet Missing Data (February-March 2021)<br />
***Scanned all segments in sheets to backfill missing data for all regions in US<br />
*'''Mentoring (Unofficial)'''<br />
**Mentored by G_W1Z (R1 through R3)<br />
**Mentored by voludu2 for R4<br />
**Mentored by RussPA for R5<br />
*'''Beta Programs'''<br />
**WME<br />
***LG<br />
***Shields<br />
**iOS<br />
*'''Meetup / Waze Cafe'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)<br />
**Hershey, PA (July 2021) (organizer)<br />
**Virtual (February 2021) (organizer)<br />
**Virtual NA Mega Meetup (February 21, 2021)<br />
<br />
{| class="wikitable"<br />
|-<br />
!Script!!Link<br />
|-<br />
|WME DOT Cameras||https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
|-<br />
|WME DOT Advisories||https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
|-<br />
|WME Fix UR Interface<br />
|https://www.waze.com/forum/viewtopic.php?t=338947<br />
|-<br />
|WME Disable Closed Updates<br />
|https://greasyfork.org/en/scripts/418411-wme-disable-closed-updates<br />
|}<br />
[[File:Script.png|thumb|[https://www.waze.com/forum/viewtopic.php?f=819&t=304760]]]</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=175466User:Phuz2022-01-13T19:34:09Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
**R5 (May 2021)<br />
*'''Manager'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
****Entire State (May 2021)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaid'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
**Luzerne Co, PA HN Mini-Raid (March 2021)<br />
*'''Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
**DelDOT Closure Bot (July 2020-Present)<br />
**WME DOT Cameras [SCRIPT] (July 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
**WME DOT Advisories [SCRIPT] (October 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
**JB U-Turn Sheet Missing Data (February-March 2021)<br />
***Scanned all segments in sheets to backfill missing data for all regions in US<br />
*'''Mentoring (Unofficial)'''<br />
**Mentored by G_W1Z (R1 through R3)<br />
**Mentored by voludu2 for R4<br />
**Mentored by RussPA for R5<br />
*'''Beta Programs'''<br />
**WME<br />
***LG<br />
***Shields<br />
**iOS<br />
*'''Meetup / Waze Cafe'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)<br />
**Hershey, PA (July 2021) (organizer)<br />
**Virtual (February 2021) (organizer)<br />
**Virtual NA Mega Meetup (February 21, 2021)<br />
<br />
{| class="wikitable"<br />
|-<br />
!Script!!Link<br />
|-<br />
|WME DOT Cameras||https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
|-<br />
|WME DOT Advisories||https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
|}<br />
[[File:Script.png|thumb|[https://www.waze.com/forum/viewtopic.php?f=819&t=304760]]]</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Roundabout&diff=175446Roundabout2022-01-10T21:41:45Z<p>Phuz: Added more context to the normal vs. non-normal roundabout radius criteria</p>
<hr />
<div><br />
{{ReturnTo | Editing manual | the editing manual}}<br />
<br />
Roundabouts, rotaries, or traffic circles, are unique segments of roadway in the Waze routing system. When a driver approaches a roundabout, a specific icon is displayed in the turn direction area of the display with a number corresponding to the exit count from the driver's entry into the roundabout or with a symbol of the movement through the roundabout. Manually creating a circular road will not produce these instructions.<br />
<br />
==What is a roundabout and what is not==<br />
In general when there is a clear roundabout in imagery, it is best to have it mapped as a roundabout in the road layer. There are a few cases that should '''not''' be mapped as roundabouts.<br />
<br />
{| class="wikitable unsortable" border="1"<br />
|+These are not drawn as roundabouts<br />
|-<br />
!Description<br />
!Image<br />
|- style="background:#FFFFFF; color:black"<br />
|Streets intersect, but there is no center island preventing left turns. There are no signs indicating a roundabout approaching the intersection or painted on the ground.<br />
|[[Image:RdAbt-Not1.png|100px]]<br />
|-<br />
|A single road segment leading to a cul-de-sac should be drawn as a [[Junction_Style_Guide#Dead_Ends|dead end]]. With very large roads it might be advisable to create a [[Junction_Style_Guide#Loops|three-segment loop]] but not a roundabout.<br />
|[[Image:Jct cul-de-sac island ex.png|100px]]<br />
|-<br />
|[https://safety.fhwa.dot.gov/saferjourney1/library/countermeasures/27.htm Small traffic-calming circles] are usually not drawn as roundabouts, especially if they do not increase the size of the intersection greater than that of a simple four-way intersection, have no roundabout signs or yield signs and have stop signs on at least one approach. Check with local leadership on how to map traffic circles.<br />
|[[Image:TrafficCircleSquare.png|100px]]<br />
|- <br />
|}<br />
<br />
==Creation from an intersection==<br />
[[File:AdjustforRA.png|300x300px|right|alt=]] First, move the junction to the center of the roundabout. Click and drag the junction to where it should be. We also need to adjust the incoming segments so that they align with the roads leading into the roundabout. When roundabouts are built at existing intersections, the approaching segments are usually realigned for drivers to reach optimal speeds when entering and exiting the roundabout and/or to allow the roundabout to be placed at appropriate distances from existing structures. If roads have been added, removed or reconfigured in other ways near the roundabout, make these changes now.<br />
<br />
[[File:RATracks.png|350x350px|left|alt=]]Oftentimes roundabouts are completed before aerial imagery is updated. In these cases, enable the GPS tracks layer in the map editor by pressing Shift+G, and use the tracks to guide your preparations. If the roads approaching the roundabout meet [[Best map editing practice#Divided and un-divided highways|the criteria for dividing roads]], make the roads divided where they will connect to the roundabout. Note that where road changes do not match aerial imagery, leaving a [[map comment]] is advised.<br />
<br />
Once all preparations are made, hover the cursor over the Roads icon on the [[Map_Editor_Interface_and_Controls#The_Tool_Bar|toolbar]] and click '''Roundabout'''. You can also use the [[keyboard shortcut]] {{Key press|O}}.<br />
[[File:BuildRA.png|300x300px|right|alt=]] Move the cursor to the center of the actual roundabout. The cursor will be a crosshair '''+''' to indicate that it is in roundabout creation mode. Click once at the center and then move the mouse any direction towards the perimeter of the roundabout. An orange circle will grow and shrink as you move the mouse, with the numbers in the center of the circle displaying the radius of the resulting roundabout.<br />
<br />
[[File:ConfirmRA.png|300x300px|right|alt=]]Click once when satisfied with the size and shape of the roundabout, which will create new 1-way segments in between each road segment contacted by the edge of the orange circle. Each approaching segment is disconnected from the junction in the center and reconnected to the roundabout with allowed turns already set, but with some turns [[Soft and hard turns|unconfirmed]]. Make sure that each turn is confirmed.<br />
{{Red|Any segments ''completely within'' the roundabout area will be deleted.}}<br />
[[File:CompleteRA.png|300x300px|right|alt=]]Like all new roads, each roundabout segment needs the country, state and city filled in. Please see the [[Creating and editing road segments#Updating_details_to_confirm_the_road|updating details to confirm the road]] section for details on this process. If the roundabout doesn't have a name, which is usually the case, click the None box next to Street. If the roundabout is a named circle on local signs, its segments can be named just like any other road. This is particularly important if addresses are on the roundabout.To determine the road type, see [[User:Kartografer/Roundabout#Road type|the road type section below]]. To determine the speed limit, if applicable, see [[Speed limits#Roundabouts|the speed limits section on roundabouts]]. When the process is complete, all other attributes have been set, and the edits are saved, this is how the new roundabout looks:<br />
<br />
Other considerations:<br />
<br />
*If this roundabout is a local [[landmark]], such as Dupont Circle in Washington, DC, an [[Places|area place]] may also be drawn inside it with the Park and/or Junction/Interchange categories, as appropriate.<br />
*If signage for any roundabout exit does not match what would be generated by the primary name of the exiting segment, add a customized [[turn instruction]] at the exit.<br />
*Some new roundabouts may be announced by local authorities before their construction, complete with road closures. If this is the case, map the roundabout in this way while following the procedures outlined for [[scheduled reconfigurations]].<br />
*For further reference, please [http://www.youtube.com/watch?v=hOPjWKjGCio watch this video on roundabout creation].<br />
<br />
===Oval, large or unusual shapes===<br />
[[File:PeanutRA.png|thumb|This roundabout is shaped like a peanut; it was created with the roundabout tool and then manually squished into this shape. It has closures ending on its opening date and a map comment.]]If an oval or elliptical roundabout is required, hold down the '''Shift''' key during roundabout creation''.'' At this time only oval roundabouts along the north/south or east/west axis can be created. If an alternate shape or axis is desired, create a circular roundabout that is close to the correct shape and adjust the [[Creating and editing road segments#Adjusting_road_geometry_.28nodes.29|geometry handles]] manually.<br />
<br />
Note that roundabouts cannot be created over a maximum of {{:Roundabouts/Maximum}} in radius because of the danger that erasing all roads in the center could accidentally wipe out an entire city of roads. If a larger radius is required, create the roundabout at the maximum size allowed by the creation tool, then manually [[User:Kartografer/Roundabout#Adjusting geometry|adjust its geometry]] to make it bigger.<br />
<br />
{{Clear}}<br />
<br />
==Creation from nothing==<br />
[[Image:FixRAB-03.png|200x200px|alt=|right]]Draw all of the road segments that will lead to the roundabout and ensure they extend into the center of the roundabout area. Use the visual map to align the roads. From there, create the roundabout just as described in the section above.<br />
<br />
At least one segment must intersect the roundabout when it is being created; otherwise, nothing will happen. To avoid problems with [[loops]], it is best to make the roundabout intersect segments in at least three places.<br />
<br />
==Road type==<br />
It is common to have multiple [[road types]] meeting at a roundabout. For proper routing and consistent appearance, the correct road type must be assigned to the roundabout itself. The road types of interest in are, in order from highest to lowest, {{Freeway}}, {{Major Highway}}, {{Minor Highway}}, {{Primary Street}}, {{Street}}, {{Parking Lot Road}}, and {{Private Road}}. Since a roundabout is not a [[Junction Style Guide/Interchange|limited-access interchange]], two freeways should never meet at a roundabout; however, it is conceivable that a freeway might begin or end at one. <br />
<br />
To determine what road type to use for the Roundabout:<br />
<br />
#Identify the two connected [[segment]]s with the ''highest'' type listed above:<br />
#*If a particular road goes through a roundabout, count the road as two separate segments, one on each side of the roundabout.<br />
#*If a road on one side of the roundabout is a divided roadway made of two one-way road segments, count the pair of one-way segments as a single segment.<br />
#*The two connected segments with the highest type may have the same type or different types.<br />
#*If a ramp connects to the Roundabout, use the road type to which that ramp connects.<br />
#Select the roundabout and set the road type as follows.<br />
#*If the two highest-type segments have the same type, use that type.<br />
#*If the two highest-type segments have different types, use the ''lower'' type of those two segments.<br><br />
<br />
{| class="wikitable unsortable" border="1"<br />
|+Roundabout Road Type Guide<br />
|-<br />
!Description<br />
! scope="col" width="120px" |Top 2 Road Types <div style="border: 3px solid #DD2200; display:inline-block; border-radius: 1em; padding-left:15px; padding-right:15px; line-height: 1.1em; font-weight: normal">RA Type</div><br />
!Example<br />
|-<br />
|A Primary Street and a Street cross at a Roundabout so we have two Street segments connected and two Primary Street segments connected.<br />
| style="text-align: center;" |{{Primary Street}}<br />
{{Primary Street|style=border: 4px solid #DD2200;}}<br />
|[[Image:RdAbt_PrPr.png| 110px]]<br />
|- <br />
|One Primary Street segment and three Street segments meet.<br />
| style="text-align: center;" |{{Primary Street}}<br />
{{Street|style=border: 4px solid #DD2200;}}<br />
|[[Image:RdAbt_PrSt.png| 110px]]<br />
|- <br />
|Three Primary Street segments and one Street segment meet.<br />
| style="text-align: center;" |{{Primary Street}}<br />
{{Primary Street|style=border: 4px solid #DD2200;}}<br />
|[[Image:RdAbt_PrPr3.png| 110px]]<br />
|- <br />
|A Major Highway and a Minor Highway cross so we have two segments of each type.<br />
| style="text-align: center;" |{{Major Highway}}<br />
{{Major Highway|style=border: 4px solid #DD2200;}}<br />
|[[Image:RdAbt_MjMj.png| 110px]]<br />
|-<br />
|Three Major Highway segments and one Minor Highway segment meet.<br />
| style="text-align: center;" |{{Major Highway}}<br />
{{Major Highway|style=border: 4px solid #DD2200;}}<br />
|[[Image:RdAbt_MjMj3.png| 110px]]<br />
|-<br />
|A Major Highway, two Primary Streets, and one Street segment meet. (The Major Highway can be thought to start/end at the Roundabout.)<br />
| style="text-align: center;" |{{Major Highway}}<br />
{{Primary Street|style=border: 4px solid #DD2200;}}<br />
|[[Image:RdAbt_MjPr.png| 110px]]<br />
|-<br />
|A Major Highway, a Primary Street, and two Street segments meet at a Roundabout.<br />
| style="text-align: center;" |{{Major Highway}}<br />
{{Primary Street|style=border: 4px solid #DD2200;}}<br />
|[[Image:RdAbt_MjPr2.png| 110px]]<br />
|-<br />
|A Major Highway, a Minor Highway, and two Primary Street segments meet. (If we used Primary Street, routing would be penalized going from the Minor Highway to the Major Highway.)<br />
| style="text-align: center;" |{{Major Highway}}<br />
{{Minor Highway|style=border: 4px solid #DD2200;}}<br />
|[[Image:RdAbt_MjMn.png| 110px]]<br />
|-<br />
|Same as above, except the Major Highway and Minor Highway are divided roadways. (Recall that a divided roadway is treated as one "segment" for this rule.)<br />
| style="text-align: center;" |{{Major Highway}}<br />
{{Minor Highway|style=border: 4px solid #DD2200;}}<br />
|[[Image:Roundabout_-_split_roads.png| 110px]]<br />
|-<br />
|A Ramp (connected to a Major Highway), a Minor Highway, and two Primary Street segments meet. (Recall that the type connected to the ramp is used in the analysis. Effectively, it's the same as the previous two examples.)<br />
| style="text-align: center;" |{{Major Highway}}<br />
{{Minor Highway|style=border: 4px solid #DD2200;}}<br />
|[[Image:Roundabout_-_ramp.png| 110px]]<br />
|-<br />
|Only Ramp segments are connected to a Roundabout. If every segment connected is a Ramp, so is the Roundabout. (When only Ramps connect to a Roundabout, none of the connected road types are considered.)<br />
| style="text-align: center;" |{{Ramp|style=border: 4px solid #DD2200;}}<br />
|[[Image:Roundabout_-_all_ramps.png| 110px]]<br />
|-<br />
|}<br />
==Understanding navigation instructions==<br />
Waze supports two different styles of roundabout navigation instructions. One style instructs simply to turn or continue at the roundabout, while the other instructs how many exits one must pass before leaving the roundabout. The US editing community terms these two instruction styles as "normal" and "non-normal" respectively. The term "normal" is used here in its mathematical sense to mean "orthogonal", "perpendicular", or "at right angles".<br />
<br />
This section will explain the difference between normal and non-normal roundabout instructions.<br />
<br /><br />
Normal roundabout instructions: <br />
<br />
*Require '''all''' of these conditions:<br />
**2-4 nodes<br />
**All exit nodes aligned within "normal" range of the entry node<br />
**A radius less than 25 meters (82 feet) as indicated when drawing a new roundabout; diameter less than 50 meters (164 feet) as indicated by WME RA Util<br />
*Comprise the following:<br />
**"[[Interactive junction instruction algorithm#At the roundabout turn right|At the roundabout, turn right]]"<br />
**"[[Interactive junction instruction algorithm#At the roundabout continue straight|At the roundabout, continue straight]]"<br />
**"[[Interactive junction instruction algorithm#At the roundabout turn left|At the roundabout, turn left]]"<br />
**"[[Interactive junction instruction algorithm#At the roundabout make a U-turn|At the roundabout, make a U-turn]]"<br />
<br />
Non-normal roundabout instructions:<br />
<br />
*Require '''at least one''' of these conditions:<br />
**'''5''' or more nodes<br />
**Nodes outside the normal roundabout angle range<br />
**A radius greater than 25 meters (82 feet) as indicated when drawing a new roundabout; diameter less than 50 meters (164 feet) as indicated by WME RA Util<br />
*Comprise the following:<br />
**"[[Interactive junction instruction algorithm#At the roundabout take the .23xx exit|At the roundabout, take the ''n''th exit]]"<br />
<br />
''A roundabout can be both normal and non-normal at the same time depending on your entry node, because the roundabout angle is calculated from where one enters the roundabout.''<br /><br />
===Roundabout angle===<br />
<br />
The '''''roundabout angle''''' is the angle of any segment connected to the roundabout from the perspective of ''the origin''. This is basically the same as the [[wikipedia:Central_angle|central angle]] of a circle. The actual ''turn angle'' of the segments is irrelevant.<br>To explain;<br />
<br />
*Draw an imaginary line through the center of the roundabout to the other side of the roundabout from the junction node where ''the origin'' joins the roundabout. This will represent a 0° '''''roundabout angle''''', any deviation to the right or left will increase the angle.<br />
*Draw another imaginary line across the roundabout through the center and perpendicular to the first imaginary line. This will represent a 90° '''''roundabout angle''''' to either side.<br />
<br />
{| class="Wikitable" style="text-align:center; border: 1px solid darkgray;" cellpadding="5" border="1"<br />
! colspan="2" scope="col" |Roundabouts<br />
|-<br />
|Normal||Non-normal<br />
|-<br />
|[[File:Roundabout 3 normal.png|301px]]||<br />
[[File:Roundabout 3 non-normal.png|301px]]<br />
|-<br />
|All other segments are within the allowed ±15° from either 0° or 90°.<br />
|Not all other segments are within the allowed ±15° from either 0° or 90°.<br />
|}<br />
===Examples===<br />
<br />
====Segment angles====<br />
[[File:RABent1.png|frameless|left]]<br />
[[File:RAStraight1.png|frameless|right]]<br />
Since the angles of the segments approaching the nodes do not matter, both of these layouts will give the same instructions. Only the angles between the nodes and the center of the roundabout (roundabout angles) determine which instructions are given.{{Clear}}<br />
<br /><br />
<br />
====Three incoming segments====<br />
[[File:RANormal1.png|thumb|Both exit nodes have roundabout angles within the normal range of ±15° from 0° or 90°.|alt=]]Let's assume this roundabout has a radius of less than 25 meters, so the other criteria are met for normal instructions.<br />
'''Coming from node 1, this is how we see the roundabout:'''<br />
<br />
:*With respect to node 1, nodes 2 and 3 have roundabout angles within the normal range (90&deg;&plusmn;15&#176; & 0&deg;&plusmn;15&deg;).<br />
:*Exiting at node 2 produces [[File:Nav icon roundabout right 1.jpg|50x50px]] "at the roundabout, turn right".<br />
:*Exiting at node 3 produces [[File:Nav icon roundabout straight.JPG|50x50px]] "at the roundabout, continue straight".<br />
<br />
[[File:RANNormal1.png|thumb|Node 2 has a roundabout angle that is outside the normal range of ±15° from 90°|alt=]]<br />
'''Coming from node 3, this is how we see the roundabout:'''<br />
<br />
:*With respect to node 3, node 1 is within the normal roundabout angle range, but node 2 is not.<br />
:*Exiting at node 1 produces [[File:Nav icon roundabout 1.JPG|50x50px]] "at the roundabout, take the first exit".<br />
:*Exiting at node 2 produces [[File:Nav icon roundabout 2.JPG|50x50px]] "at the roundabout, take the second exit".<br />
<br />
'''All exits must be within the normal range with respect to a given entrance in order to generate "turn left", "turn right", "continue straight" or "make a U-turn" instructions from this entrance.'''<br />
<br />
==Entries and exits==<br />
[[Image:RdAbt-NoDivRd.png|150px|right]][[Image:RdAbt-DivRd.png|150px|right]]<br />
If the road segments approaching a roundabout do not meet the [[Best map editing practice#Divided and un-divided highways|criteria for dividing roads]], they are generally drawn as simple two-way roads connected perpendicular (90 degrees) to the roundabout circle itself. If they do meet the criteria for dividing, each entry or exit segment should be connected to its own node on the roundabout, and the segments should be drawn in a way that fits with the natural flow of traffic. This will almost always cause the roundabout instructions to be non-normal. Due to historical reasons, some regions of the USA have a preponderance of normal or non-normal roundabouts, and the users in those regions are accustomed to one or the other set of instructions. Check with your regional leadership to determine which instructions are preferred when drawing roundabouts.<br />
<br />
===Multiple segments at one node===<br />
It is usually inappropriate to join two segments at the same node on a roundabout and tends to cause problems. If both segments are one way in opposing directions, and the exit is to the left of the entrance, such as with both roadways of a divided highway, these will be treated correctly like a single two-way segment in navigation instructions. However, this geometry results in sharp turns that rarely fit the natural flow of traffic turning into and out of the roundabout, and it is often better simply to join each one-way segment at its own node on a roundabout.<br />
<br />
Do not connect an entry belonging to one road to or past an exit belonging to the next road to the right, as this causes the first exit not to be counted and the subsequent exits to be numbered incorrectly. Even if the movement into and out of the roundabout is prohibited at this point (often the case in [[#At-grade connector|roundabouts with bypasses]]), if it is physically possible, users will tend to count it as the first exit, and we need to provide a consistent experience when mapping.<br />
<br />
Do not connect more than one exit (either two-way segments or outgoing one-way segments) to the same node at a roundabout, as this causes Waze not to number any exit. In these cases Waze will show an empty circle for the roundabout instruction and will truncate the spoken instruction to "at the roundabout."<br />
==Adjusting geometry==<br />
When adjusting roundabouts, drag the junction nodes and move/delete the geometry points of the segments. This is better than disconnecting and reconnecting, because disconnection results in the loss of turn data. The script [[Scripts/WME RA Util|WME RA Util]] makes adjustment of roundabouts much easier.<br />
==Bypass==<br />
Some roundabouts are designed with physically separated '''bypass roads''' or '''[[at-grade connectors]] (AGCs)'''. In many cases, roundabout bypasses can be mapped just like any other, but some roundabouts with bypasses have persistent routing problems.<br />
<br />
===Correcting inappropriate avoidance of roundabout bypasses===<br />
Where bypasses have been built to allow right-turning or straight traffic to avoid the roundabout altogether, Waze might send traffic through the roundabout anyway. This is often confusing to drivers when it is contrary to regulatory or informative signs. In these cases, use a [[junction box]] to restrict the invalid route through the roundabout, which will force the bypass to be routed.<br />
<br />
====What not to do====<br />
[[File:RA-bad.png|thumb|Entrances of one road connected to exits of a different road at the same nodes give incorrect normal instructions (left). Entrances of one road connected past exits of the next road give incorrectly numbered non-normal instructions (right).]][[File:RAhacks.png|thumb|Hacks to activate the [[Routing penalties/Controlling U-turn penalties|U-turn penalty]] (left) and the [[Detour Prevention Mechanisms|detour prevention penalty]] (right) should no longer be used.]]Before junction boxes were developed to work with roundabouts, various hacks were used to force bypass routing. Some involved connecting the entrance of one road at or past the exit of the next road, in order to prevent the redundant turn through the roundabout and force routing through the bypass. Others involved the activation of penalties on the redundant turn to force routing through the bypass. None of these should be used.<br />
<br />
*Do not junction the incoming and outgoing segment at the same node in order to prevent the redundant turn. [[#Multiple segments at one node|Joining multiple entrances or exits at one node]] causes incorrect exit numbering, and, in some cases the distortion can cause incorrect ''normal'' instructions, (for example - "at the roundabout, turn right" to users continuing straight, if they travel through only 90° of the roundabout from entry to exit).<br />
*Do not move the incoming segment after the outgoing segment to make Waze avoid the exit. This is also a distortion if the roundabout and can cause incorrect roundabout instructions.<br />
*Do not activate fake U-turn and detour penalties by means of unconventional road names and types or unnatural geometry.<br />
<br />
Wherever found, these deviations '''should be removed and replaced''' with junction boxes as described in the next section.<br />
<br />
==Junction box==<br />
[[File:JuBRA.png|thumb|A junction box has been used to force right turning traffic on US-41 S to use the bypass rather than being routed through the roundabout. Normal turn instructions have also been specified in accordance with regional norms, lane markings and signage]]Junction boxes can be used over roundabouts, covering them either partially or fully. In addition to providing better timing, using a junction box on a roundabout can accomplish these goals:<br />
<br />
#As mentioned above, they may be used to correct routing problems.<br />
#They may be used to provide customized [[Turn instruction|turn instructions]] where signage for a particular exit is different when coming from different entrances.<br />
#They may also be used to override the default navigation instructions.<br />
#*For example, divided roads may meet at a small roundabout, where drivers would expect normal instructions based on signs, lane markings and what's common in the region. Rather than using unnatural geometry to force the normal instructions, draw a junction box to encircle the roundabout and set the [[voice prompt]] for each path through the roundabout to Turn left, Turn right, U-turn or Continue.<br />
#*Conversely, where non-normal instructions are desired that would otherwise be normal, make a junction box voice prompt of Let Waze count the exit number.<br />
#*Where [https://safety.fhwa.dot.gov/saferjourney1/library/countermeasures/27.htm small traffic-calming circles] have been mapped as roundabouts, a junction box may be used to suppress unnecessary "at the roundabout, continue straight" instructions. Check with local leadership on how to handle traffic-calming circles.<br />
<br />
If the junction box completely contains only nodes on the roundabout, its voice prompts will produce the proper roundabout spoken and visual instructions, such as "at the roundabout, turn right" and "at the roundabout, take the fourth exit". Normal and non-normal instructions can be used in the same roundabout. If nodes '''outside the roundabout''' are included in the junction box, the navigation instructions '''will not work as expected''', so be sure to only include roundabout segments when using a junction box to control roundabout instructions.<br />
<br />
{{ReturnTo | Editing manual | the editing manual}}</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Delaware/Places/Main&diff=175296Delaware/Places/Main2021-12-16T12:45:34Z<p>Phuz: </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 />
Editors are encouraged to use the Place Harmonizer script "''WMEPH''" when editing places, this will help you follow state + national standards. Use caution with the automatic options and be aware of what it is changing.<br />
<br />
Any editor may edit any place in their EA. If it is locked above their rank a PUR will be generated for a senior editor to review and approve.<br />
<br />
Delaware locking standards for places differ in some ways from the US standard:<br />
<br />
;<nowiki>Locking Standard</nowiki><br />
:Once you have correctly filled in as as much information as is available, Places should be locked to a minimum level of Rank '''2'''. This prevents "trusted Wazers" who are not editors from automatically adding photos to places.<br />
<br />
:These areas below are more sensitive + important to Wazers and should be locked higher, reach out to a senior editor if needed for assistance in locking new places:<br />
: <br />
:Lock at 3:<br />
:<br />
:::* College / University<br />
:::* Courthouse <br />
:::* Government <br />
:::* Jail / Prison / Correctional Facility <br />
:::* Military <br />
:::* Parking Lot<br />
: <br />
:Lock at 4:<br />
:<br />
:::* Fire Department<br />
:::* Gas station<br />
:::* Hospital / Urgent Care<br />
:::* Park<br />
:::* Police Station<br />
: <br />
:Lock at 5:<br />
::<br />
:::* Airport<br />
;<br />
;Address:<br />
:Fill out address information completely, this is not used for navigation, it is informational-only but is important for the Waze user.<br />
<br />
:For the City field, consider what the business uses on their website and what will make the most sense to the Waze user. You can use the city name from a nearby road, or use an other local city or CDP name that WME offers as an auto-complete.<br />
<br />
:R4+ editors, do NOT create a "new" city name, check with a State Manager if you feel none of the names is sufficient since creating a "new" City makes that available to other editors for roads too.<br />
<br />
;Naming Fire Departments:<br />
:Fire Departments exist as agencies and can have identifiers such as stations or equipment. When naming a fire department, use the following format:<br />
<br />
:Name - Identifier (if applicable)<br />
:Examples: Lewes Fire Department - Engine 3 & Ladder 1<br />
<!-- Removed until needed in the future------<br />
See [[{{BasePage2}}/Places]] for guidance in {{RootPage2}} that may not be universal to all other states and territories.--><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/Places|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}}/Places]] 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>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Delaware/Places/Main&diff=175295Delaware/Places/Main2021-12-16T12:45:03Z<p>Phuz: </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 />
Editors are encouraged to use the Place Harmonizer script "''WMEPH''" when editing places, this will help you follow state + national standards. Use caution with the automatic options and be aware of what it is changing.<br />
<br />
Any editor may edit any place in their EA. If it is locked above their rank a PUR will be generated for a senior editor to review and approve.<br />
Delaware locking standards for places differ in some ways from the US standard:<br />
;<nowiki>Locking Standard</nowiki><br />
:Once you have correctly filled in as as much information as is available, Places should be locked to a minimum level of Rank '''2'''. This prevents "trusted Wazers" who are not editors from automatically adding photos to places.<br />
<br />
:These areas below are more sensitive + important to Wazers and should be locked higher, reach out to a senior editor if needed for assistance in locking new places:<br />
: <br />
:Lock at 3:<br />
:<br />
:::* College / University<br />
:::* Courthouse <br />
:::* Government <br />
:::* Jail / Prison / Correctional Facility <br />
:::* Military <br />
:::* Parking Lot<br />
: <br />
:Lock at 4:<br />
:<br />
:::* Fire Department<br />
:::* Gas station<br />
:::* Hospital / Urgent Care<br />
:::* Park<br />
:::* Police Station<br />
: <br />
:Lock at 5:<br />
::<br />
:::* Airport<br />
;<br />
;Address:<br />
:Fill out address information completely, this is not used for navigation, it is informational-only but is important for the Waze user.<br />
<br />
:For the City field, consider what the business uses on their website and what will make the most sense to the Waze user. You can use the city name from a nearby road, or use an other local city or CDP name that WME offers as an auto-complete.<br />
<br />
:R4+ editors, do NOT create a "new" city name, check with a State Manager if you feel none of the names is sufficient since creating a "new" City makes that available to other editors for roads too.<br />
<br />
;Naming Fire Departments:<br />
:Fire Departments exist as agencies and can have identifiers such as stations or equipment. When naming a fire department, use the following format:<br />
<br />
:Name - Identifier (if applicable)<br />
:Examples: Lewes Fire Department - Engine 3 & Ladder 1<br />
<!-- Removed until needed in the future------<br />
See [[{{BasePage2}}/Places]] for guidance in {{RootPage2}} that may not be universal to all other states and territories.--><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/Places|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}}/Places]] 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>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Delaware/Places/Main&diff=175294Delaware/Places/Main2021-12-16T12:38:42Z<p>Phuz: </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 />
Delaware standards for places differ in some ways from the US standard:<br />
<br />
Editors are encouraged to use the Place Harmonizer script "''WMEPH''" when editing places, this will help you follow state + national standards. Use caution with the automatic options and be aware of what it is changing.<br />
<br />
Any editor may edit any place in their EA. If it is locked above their rank a PUR will be generated for a senior editor to review and approve.<br />
<br />
;<nowiki>Locking Standard</nowiki><br />
:Once you have correctly filled in as as much information as is available, Places should be locked to a minimum level of Rank '''2'''. This prevents "trusted Wazers" who are not editors from automatically adding photos to places.<br />
<br />
:These areas below are more sensitive + important to Wazers and should be locked higher, reach out to a senior editor if needed for assistance in locking new places:<br />
: <br />
:Lock at 3:<br />
:<br />
:::* College / University<br />
:::* Courthouse <br />
:::* Government <br />
:::* Jail / Prison / Correctional Facility <br />
:::* Military <br />
:::* Parking Lot<br />
: <br />
:Lock at 4:<br />
:<br />
:::* Fire Department<br />
:::* Gas station<br />
:::* Hospital / Urgent Care<br />
:::* Park<br />
:::* Police Station<br />
: <br />
:Lock at 5:<br />
::<br />
:::* Airport<br />
;<br />
;Address:<br />
:Fill out address information completely, this is not used for navigation, it is informational-only but is important for the Waze user.<br />
<br />
:For the City field, consider what the business uses on their website and what will make the most sense to the Waze user. You can use the city name from a nearby road, or use an other local city or CDP name that WME offers as an auto-complete.<br />
<br />
:R4+ editors, do NOT create a "new" city name, check with a State Manager if you feel none of the names is sufficient since creating a "new" City makes that available to other editors for roads too.<br />
<br />
;Naming Fire Departments:<br />
:Fire Departments exist as agencies and can have identifiers such as stations or equipment. When naming a fire department, use the following format:<br />
<br />
:Name - Identifier (if applicable)<br />
:Examples: Lewes Fire Department - Engine 3 & Ladder 1<br />
<!-- Removed until needed in the future------<br />
See [[{{BasePage2}}/Places]] for guidance in {{RootPage2}} that may not be universal to all other states and territories.--><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/Places|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}}/Places]] 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>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Delaware/Places/Main&diff=175293Delaware/Places/Main2021-12-16T12:32:38Z<p>Phuz: </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 />
Editors are encouraged to use the Place Harmonizer script "''WMEPH''" when editing places, this will help you follow state + national standards. Use caution with the automatic options and be aware of what it is changing.<br />
<br />
Any editor may edit any place in their EA. If it is locked above their rank a PUR will be generated for a senior editor to review and approve.<br />
<br />
Delaware standards for places differ in some ways from the US standard:<br />
<br />
;<nowiki>Locking Standard</nowiki><br />
:Once you have correctly filled in as as much information as is available, Places should be locked to a minimum level of Rank '''2'''. This prevents "trusted Wazers" who are not editors from automatically adding photos to places.<br />
<br />
:These areas below are more sensitive + important to Wazers and should be locked higher, reach out to a senior editor if needed for assistance in locking new places:<br />
: <br />
:Lock at 3:<br />
:<br />
:::* College / University<br />
:::* Courthouse <br />
:::* Government <br />
:::* Jail / Prison / Correctional Facility <br />
:::* Military <br />
:::* Parking Lot<br />
: <br />
:Lock at 4:<br />
:<br />
:::* Fire Department<br />
:::* Gas station<br />
:::* Hospital / Urgent Care<br />
:::* Park<br />
:::* Police Station<br />
: <br />
:Lock at 5:<br />
::<br />
:::* Airport<br />
;<br />
;Address:<br />
:Fill out address information completely, this is not used for navigation, it is informational-only but is important for the Waze user.<br />
<br />
:For the City field, consider what the business uses on their website and what will make the most sense to the Waze user. You can use the city name from a nearby road, or use an other local city or CDP name that WME offers as an auto-complete.<br />
<br />
:R4+ editors, do NOT create a "new" city name, check with a State Manager if you feel none of the names is sufficient since creating a "new" City makes that available to other editors for roads too.<br />
<br />
;Naming Fire Departments:<br />
:Fire Departments exist as agencies and can have identifiers such as stations or equipment. When naming a fire department, use the following format:<br />
<br />
:Name - Identifier (if applicable)<br />
:Examples: Lewes Fire Department - Engine 3 & Ladder 1<br />
<!-- Removed until needed in the future------<br />
See [[{{BasePage2}}/Places]] for guidance in {{RootPage2}} that may not be universal to all other states and territories.--><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/Places|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}}/Places]] 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>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Delaware/Places/Main&diff=175292Delaware/Places/Main2021-12-16T12:31:00Z<p>Phuz: </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 />
Editors are encouraged to use the Place Harmonizer script "''WMEPH''" when editing places, this will help you follow state + national standards. Use caution with the automatic options and be aware of what it is changing.<br />
<br />
Any editor may edit any place in their EA. If it is locked above their rank a PUR will be generated for a senior editor to review and approve.<br />
<br />
Delaware standards for places differ in some ways from the US standard:<br />
<br />
=== Locking Standard ===<br />
:Once you have correctly filled in as as much information as is available, Places should be locked to a minimum level of Rank '''2'''. This prevents "trusted Wazers" who are not editors from automatically adding photos to places.<br />
<br />
:These areas below are more sensitive + important to Wazers and should be locked higher, reach out to a senior editor if needed for assistance in locking new places:<br />
: <br />
:Lock at 3:<br />
:<br />
:::* College / University<br />
:::* Courthouse <br />
:::* Government <br />
:::* Jail / Prison / Correctional Facility <br />
:::* Military <br />
:::* Parking Lot<br />
: <br />
:Lock at 4:<br />
:<br />
:::* Fire Department<br />
:::* Gas station<br />
:::* Hospital / Urgent Care<br />
:::* Park<br />
:::* Police Station<br />
: <br />
:Lock at 5:<br />
::<br />
:::* Airport<br />
;<br />
;Address:<br />
:Fill out address information completely, this is not used for navigation, it is informational-only but is important for the Waze user.<br />
<br />
:For the City field, consider what the business uses on their website and what will make the most sense to the Waze user. You can use the city name from a nearby road, or use an other local city or CDP name that WME offers as an auto-complete.<br />
<br />
:R4+ editors, do NOT create a "new" city name, check with a State Manager if you feel none of the names is sufficient since creating a "new" City makes that available to other editors for roads too.<br />
<br />
;Naming Fire Departments:<br />
:Fire Departments exist as agencies and can have identifiers such as stations or equipment. When naming a fire department, use the following format:<br />
<br />
:Name - Identifier (if applicable)<br />
:Examples: Lewes Fire Department - Engine 3 & Ladder 1<br />
<!-- Removed until needed in the future------<br />
See [[{{BasePage2}}/Places]] for guidance in {{RootPage2}} that may not be universal to all other states and territories.--><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/Places|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}}/Places]] 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>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Delaware/Places/Main&diff=175291Delaware/Places/Main2021-12-16T12:27:56Z<p>Phuz: </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 />
=== Locking Standard ===<br />
:Once you have correctly filled in as as much information as is available, Places should be locked to a minimum level of Rank '''2'''. This prevents "trusted Wazers" who are not editors from automatically adding photos to places.<br />
<br />
:These areas below are more sensitive + important to Wazers and should be locked higher, reach out to a senior editor if needed for assistance in locking new places:<br />
: <br />
:Lock at 3:<br />
:<br />
:::* College / University<br />
:::* Courthouse <br />
:::* Government <br />
:::* Jail / Prison / Correctional Facility <br />
:::* Military <br />
:::* Parking Lot<br />
: <br />
:Lock at 4:<br />
:<br />
:::* Fire Department<br />
:::* Gas station<br />
:::* Hospital / Urgent Care<br />
:::* Park<br />
:::* Police Station<br />
: <br />
:Lock at 5:<br />
::<br />
:::* Airport<br />
;<br />
<br />
<!-- Removed until needed in the future------<br />
See [[{{BasePage2}}/Places]] for guidance in {{RootPage2}} that may not be universal to all other states and territories.--><br />
<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/Places|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}}/Places]] 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>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Delaware/AM/Editor/Area2&diff=175290Delaware/AM/Editor/Area22021-12-16T12:21:42Z<p>Phuz: */Other Area editor table update*/</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE ------------------------------<br />
------------------------ SCROLL DOWN FOR INSTRUCTIONS -----------------------------><noinclude><!--Keep hard coded due to unique page address--><div class="center"><span class="noprint plainlinks purgelink" style="{{Road/style}}background-color:#93c4d3">[{{FULLURL:{{#titleparts:{{PAGENAME}}|-3}}|action=purge}}#Other_Area_Editors <span title="Return to the Other Area Editor table">&nbsp;Press here to return to the Other Area Editors table to see your changes&nbsp;</span>]</span></div></noinclude><includeonly><!--<br />
-------------------------------------------------------------------------------------<br />
-- Editors: To add yourself to this Other Editor Area table, copy and paste the<br />
-- following template into the space below with the other {{AM/Editor|...}}<br />
-- templates. Add yourself into rank order (higher at top)then alphabetical order<br />
-- by user name (A-Z)<br />
-------------------------------------------------------------------------------------<br />
{{AM/Editor|YOUR_USER_NAME|YOUR_RANK#|YOUR_AREA|ANY_COMMENT}}<br />
-------------------------------------------------------------------------------------<br />
-- then in the Summary field enter "Added YOUR_USER_NAME" and press "Save page"<br />
-------------------------------------------------------------------------------------<br />
---------------------- DO NOT MODIFY CONTENT ABOVE THE LINE -------------------------<br />
--------------------------------------------------------------------------------->|-<br />
{{AM/Editor|Jdelosa|5|Statewide|NOR MSM, NYC Closure Team|badge1=SM|badge2=mr|badge3=m|badge4=LAM|gho=John ( JD )|pic=File:Avatar jdelosa.jpg}}<br />
{{AM/Editor|mrsmith66|5|Statewide|NOR MSM, NJ SM|badge1=SM|gho=Mark Smith}}<br />
<!-----------------------------------------------------------------------------------<br />
---------------------- DO NOT MODIFY CONTENT BELOW THE LINE -------------------------<br />
-------------------------------------------------------------------------------------<br />
-------------------------------------------------------------------------------------<br />
--></includeonly></div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=National_resources/Functional_classification&diff=174460National resources/Functional classification2021-08-07T11:24:02Z<p>Phuz: Updated Pennsylvania interactive map</p>
<hr />
<div>'''Functional classification''' is a system by which roads are classified using a set of criteria selected by the [[wikipedia:Federal Highway Administration|Federal Highway Administration]] (FHWA). These criteria include not only the physical attributes of the road but also efficiency of travel, number of access points, speed limits, route spacing, actual usage, and continuity. This can lead to quite different classifications for roads that appear similar. For example, a six-lane divided road in an urbanized area may be a Collector (Primary Street); a two-lane road through the middle of a town may be a principal arterial (Major Highway).<br />
<br />
In Waze, functional classification is used to determine [[Road types|road type in the United States]].<br />
<br />
Functional classification is a national standard, but functional classification maps are published by state departments of transportation. Links to functional classification maps for each state can be found in the table below.<br />
<br />
==Reason for changes==<br />
The [http://www.waze.com/forum/viewtopic.php?f=276&t=85397&hilit=+functional+classification Waze forum] holds a lengthy discussion on why the Functional Classification changes are being made. <br />
<br />
==Functional classification maps by state==<br />
<br />
{| class="wikitable"<br />
|-<br />
!State<br />
!Interactive map<br />
!Static maps<br />
!Notes<br />
|-<br />
|{{anchor|Alabama}}Alabama<br />
|<br />
|[https://www.dot.state.al.us/maweb/surveyMapping/HFCMaps.html ALDOT]<br />
|<br />
|-<br />
|{{anchor|Alaska}}Alaska<br />
|[http://www.dot.state.ak.us/stwdplng/fclass/fclassmaps.shtml Alaska DOT]<br />
|<br />
|<br />
|-<br />
|{{anchor|Arizona}}Arizona<br />
|<br />
|[https://works.maps.arcgis.com/apps/webappviewer/index.html?id=4bcb96763e48482799906407a0cdb7cb ADOT]<br />
|<br />
|-<br />
|{{anchor|Arkansas}}Arkansas<br />
|ArcGIS Viewer<br />
|<br />
|AHTD FC Overlay for ArcGIS - To use the overlay, click on the "Modify Map" in the upper right corner of ArcGIS. On the left side an "Add+" tab will pop up. Click on it and select "Add Layer from Web" and paste in this URL: <nowiki>http://gis.arkansas.gov/arcgis/rest/services/FEATURESERVICES/Transportation/MapServer/8</nowiki><br />
|-<br />
|{{anchor|California}}[[California/Functional Classifications Grids|California]]<br />
|[https://caltrans.maps.arcgis.com/apps/webappviewer/index.html?id=026e830c914c495797c969a3e5668538 California Road System (CRS) Maps]<br />
|[http://dot.ca.gov/hq/tsip/hseb/func_clas.html Caltrans]<br />
|Caltrans Earth has been replaced by California Road System (CRS) Maps<br />
|-<br />
|{{anchor|Colorado}}Colorado<br />
|[http://dtdapps.coloradodot.info/Otis/Flex/MapView CDOT MapView]<br />
|<br />
|<br />
|-<br />
|{{anchor|Connecticut}}Connecticut<br />
|<br />
|[http://www.ct.gov/dot/cwp/view.asp?a=3529&q=305564 Connecticut DOT]<br />
|<br />
|-<br />
|{{anchor|Delaware}}Delaware<br />
|<br />
|[http://deldot.maps.arcgis.com/apps/webappviewer/index.html?id=42d4764d105a4c278226e1b0a04879a9 DelDOT]<br />
|<br />
|-<br />
|{{anchor|District of Columbia}}District of Columbia<br />
|<br />
|[http://ddot.dc.gov/node/573602 DDOT]<br />
|<br />
|-<br />
|{{anchor|Florida}}Florida<br />
|[http://www.dot.state.fl.us/planning/statistics/gis/default.shtm FDOT's Downloadable GIS files]<br />
|See [https://wiki.waze.com/wiki/Southeast#Florida Southeast Region Wiki]<br />
|Please DO NOT use the FDOT Enterprise IMAP for doing Functional Classification Changes. It is out of date.<br />
|-<br />
|{{anchor|Georgia}}Georgia<br />
|[https://itos.maps.arcgis.com/apps/webappviewer/index.html?id=962a2591f91a4303aeafe016ba8db96b Georgia DOT]<br />
|[https://atlantaregional.org/transportation-mobility/roads-highways/roadway-functional-classification/ Atlanta Metro]<br />
|Note that these maps are years out of date. Confer with the Waze State Manager before making large changes.<br />
|-<br />
|{{anchor|Hawaii}}Hawaii<br />
|[http://hwypgis.dot.hawaii.gov/HDOT/Default.asp Hawaii DOT]<br />
|<br />
|The updated HDOT GIS Website requires the Adobe SVG Viewer.<br />
|-<br />
|{{anchor|Idaho}}Idaho<br />
|[http://iplan.maps.arcgis.com/home/webmap/viewer.html?webmap=3321e504a78549e79ac76e3984c90295 ArcGIS Webmap]<br />
|<br />
|<br />
|-<br />
|{{anchor|Illinois}}Illinois<br />
|[http://www.gettingaroundillinois.com/gai.htm?mt=fc Getting Around Illinois]<br />
|[http://www.idot.illinois.gov/transportation-system/Network-Overview/highway-system/maps#FiveYear Illinois DOT]<br />
|If interactive and static map disagree, use the interactive map classification and please notify Illinois SM's of the road and map in error.<br />
|-<br />
|{{anchor|Indiana}}Indiana<br />
|[http://www.arcgis.com/home/webmap/viewer.html?webmap=0c70853e457149aeacd2db298a01bf06&extent=-91.1257,36.1344,-74.8989,43.2661 INDOT FC Layer]<br />
|<br />
|<br />
|-<br />
|{{anchor|Iowa}}Iowa<br />
|<br />
|[http://www.iowadot.gov/systems_planning/fedfuncclass.html IowaDOT]<br />
|<br />
|-<br />
|{{anchor|Kansas}}Kansas<br />
|<br />
|[http://www.ksdot.org/burtransplan/maps/CountyFunClass.asp KDOT]<br />
|<br />
|-<br />
|{{anchor|Kentucky}}Kentucky<br />
|[http://maps.kytc.ky.gov/photolog/?config=functionalclass KYTC Functional Class]<br />
|[http://transportation.ky.gov/Planning/Pages/Functional-Classification.aspx Kentucky Transportation Cabinet]<br />
|<br />
|-<br />
|{{anchor|Louisiana}}Louisiana<br />
|[http://www.arcgis.com/home/webmap/viewer.html?webmap=8a893b672da94be793b83b4581ca877d&extent=-95.3652,28.8529,-88.6196,33.4989 LaDOTD Interactive Online Map]<br />
|[http://wwwsp.dotd.la.gov/Inside_LaDOTD/Divisions/Multimodal/Data_Collection/Mapping/Pages/Proposed_Highway_Functional_Classification_Maps.aspx LaDOTD]<br />
|<br />
|-<br />
|{{anchor|Maine}}Maine<br />
|[http://www.maine.gov/mdot/mapviewer/index.html MaineDOT]<br />
|[http://www.maine.gov/mdot/hss/mhc.htm MaineDOT]<br />
|<br />
|-<br />
|{{anchor|Maryland}}Maryland<br />
|[http://sites.google.com/site/nzahn1waze/resources MD SHA via nzahn1]<br />
|[http://sha.md.gov/pages/hlr.aspx?PageId=832 MD SHA]<br />
|Interactive Maps transformed from MD SHA data to Google Earth(.kml) by&nbsp;[[User:Nzahn1|nzahn1]]<br />
|-<br />
|{{anchor|Massachusetts}}Massachusetts<br />
|[http://services.massdot.state.ma.us/maptemplate/roadinventory Road Inventory Map]<br />
|[http://www.massdot.state.ma.us/planning/Main/MapsDataandReports/Maps/FunctionalClassification.aspx massDOT]<br />
|Select Federal Functional Classification from pulldown list on Road Inventory Map.<br />
|-<br />
|{{anchor|Michigan}}Michigan<br />
|[http://www.mcgi.state.mi.us/prfinder/mapBasic.aspx?type=nfc MDOT PR Finder]<br />
|[http://mdotcf.state.mi.us/public/maps_nfc/ MDOT]<br />
|<br />
|-<br />
|{{anchor|Minnesota}}Minnesota<br />
|[http://gisservices.dot.state.mn.us/mndot-basemap/ MnDOT Basemap]<br />
|[http://www.dot.state.mn.us/roadway/data/functional_class.html MnDOT]<br />
|<br />
|-<br />
|{{anchor|Mississippi}}Mississippi<br />
|<br />
|[http://mdot.ms.gov/portal/planning.aspx?open=Maps MDOT]<br />
|<br />
|-<br />
|{{anchor|Missouri}}Missouri<br />
|<br />
|[http://www.modot.org/newsandinfo/functionalclassificationmaps/ MoDOT]<br />
|<br />
|-<br />
|{{anchor|Montana}}Montana<br />
|[http://www.arcgis.com/home/webmap/viewer.html?webmap=3fe8695311b04116bdbbb776d44dd96b&extent=-116.6406,44.2346,-103.1494,49.2725 ArcGIS Webmap]<br />
|[http://mdt.mt.gov/travinfo/maps/urban_maps.shtml MDT]<br />
[http://www.mdt.mt.gov/travinfo/docs/funct-classification.pdf Statewide PDF]<br />
|<br />
|-<br />
|{{anchor|Nebraska}}Nebraska<br />
|<br />
|[http://www.transportation.nebraska.gov/maps/func-city-by-cnty-maps.htm Nebraska Department of Roads]<br />
|<br />
|-<br />
|{{anchor|Nevada}}Nevada<br />
|<br />
|[http://www.nevadadot.com/About_NDOT/NDOT_Divisions/Planning/Roadway_Systems/FCMGS.aspx Nevada DOT]<br />
|<br />
|-<br />
|{{anchor|New Hampshire}}New Hampshire<br />
|<br />
|[http://www.nh.gov/dot/org/projectdevelopment/planning/gis-data-catalog/ New Hampshire DOT]<br />
|<br />
|-<br />
|{{anchor|New Jersey}}New Jersey<br />
|<br />
|[http://www.state.nj.us/transportation/refdata/roadway/fcmaps.shtm NJDOT]<br />
|<br />
|-<br />
|{{anchor|New Mexico}}New Mexico<br />
|[http://nmdot.maps.arcgis.com/apps/webappviewer/index.html?id=f2fc877d107b4e338deb789f70a8779e NMDOT]<br />
|[http://dot.state.nm.us/content/dam/nmdot/planning/Federal_Function_Classification.pdf NMDOT]<br />
|<br />
|-<br />
|{{anchor|New York}}New York<br />
|[https://gis3.dot.ny.gov/html5viewer/?viewer=FC NY State DOT FC Viewer]<br />
|<br />
|<br />
|-<br />
|{{anchor|North Carolina}}North Carolina<br />
|[http://ncdot.maps.arcgis.com/home/ NCDOT]<br />
|<br />
|<br />
|-<br />
|{{anchor|North Dakota}}North Dakota<br />
|<br />
|[http://www.dot.nd.gov/road-map/functional-class/index-county.htm NDDOT]<br />
|<br />
|-<br />
|{{anchor|Ohio}}Ohio<br />
|[https://gis.dot.state.oh.us/tims/map TIMS]<br />
|<br />
[http://www.dot.state.oh.us/Divisions/Planning/ProgramManagement/MajorPrograms/Pages/RoadwayFunctionalClass.aspx Ohio DOT]<br />
|<br />
|-<br />
|{{anchor|Oklahoma}}Oklahoma<br />
|[http://okdot.maps.arcgis.com/apps/Viewer/index.html?appid=00907358f2934cf28c2121457df23d10 ODOT ArcGIS]<br />
|[http://www.okladot.state.ok.us/maps../index.htm ODOT]<br />
|<br />
|-<br />
|{{anchor|Oregon}}Oregon<br />
|[http://gis.odot.state.or.us/transgis/ ODOT TransGIS]<br />
|[http://www.oregon.gov/ODOT/TD/TDATA/pages/rics/functionalclassification.aspx ODOT]<br />
|<br />
|-<br />
|{{anchor|Pennsylvania}}Pennsylvania<br />
|[https://gis.penndot.gov/onemap/ PennDOT] <br />
[https://gis.penndot.gov/onemap/ One Map]<br />
|<s> [http://www.penndot.gov/ProjectAndPrograms/Planning/TrafficInformation/Pages/County-Functional-Class-Maps.aspx PennDOT]</s><br />
|In the MPMSIQ map, use the operational > FC layer. <br\>Information in the older static maps is out of date.<br />
|-<br />
|{{anchor|Rhode Island}}Rhode Island<br />
|<br />
|[http://www.planning.ri.gov/statewideplanning/transportation/highway.php RI Division of Planning]<br />
|<br />
|-<br />
|{{anchor|South Carolina}}South Carolina<br />
|<br />
|[http://info.scdot.org/sites/GIS/SitePages/default.aspx SCDOT GIS/Mapping]<br />
|<br />
|-<br />
|{{anchor|South Dakota}}South Dakota<br />
|<br />
|[http://sddot.com/transportation/highways/classification/Default.aspx SDDOT]<br />
|<br />
|-<br />
|{{anchor|Tennessee}}Tennessee<br />
|<br />
|[https://www.tn.gov/tdot/driver-how-do-i/look-at-or-order-state-maps/maps/annual-average-daily-traffic-maps1.html TDOT]<br />
|<br />
|-<br />
|{{anchor|Texas}}Texas<br />
|[http://www.txdot.gov/apps/statewide_mapping/StatewidePlanningMap.html TxDOT Statewide Planning Map]<br />
|<br />
|<br />
|-<br />
|{{anchor|Utah}}Utah<br />
|[http://www.udot.utah.gov/main/f?p=100:pg:0::::V,T:,1224 UDOT]<br />
|<br />
|<br />
|-<br />
|{{anchor|Vermont}}Vermont<br />
|<br />
|[http://vtransplanning.vermont.gov/research/highway/publications VTrans]<br />
|<br />
|-<br />
|{{anchor|Virginia}}Virginia<br />
|<br />
|[http://www.virginiadot.org/projects/fxn_class/maps.asp VDOT]<br />
|<br />
|-<br />
|{{anchor|Washington}}Washington<br />
|[http://www.wsdot.wa.gov/mapsdata/travel/hpms/functionalclass.htm WSDOT]<br />
|<br />
|<br />
|-<br />
|{{anchor|West Virginia}}West Virginia<br />
|<br />
|[http://www.transportation.wv.gov/highways/programplanning/gti/GIS/MAPS/Pages/default.aspx WV DOT]<br />
|<br />
|-<br />
|{{anchor|Wisconsin}}Wisconsin<br />
|<br />
|[http://wisconsindot.gov/Pages/projects/data-plan/plan-res/function.aspx WisDOT]<br />
|<br />
|-<br />
|{{anchor|Wyoming}}Wyoming<br />
|<br />
|[http://www.dot.state.wy.us/files/live/sites/wydot/files/shared/Environmental_Services/Forest%20Service%20Liasion/State%20Map%20with%20Forests.pdf WYDOT]<br />
|Appears on [http://www.dot.state.wy.us/home/engineering_technical_programs/environmental_services/usfs_wydot_liaison.html U.S. Forest Service - WYDOT Liaison Program]<br>Other urban FC maps appear on various WY city government pages<br />
|}<br />
<br />
[[Category:USA]]</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Delaware/To_do/Main&diff=174405Delaware/To do/Main2021-07-21T14:23:27Z<p>Phuz: </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 />
* Add postal city name to alternate street name on streets outside of incorporated areas and remove primary name for segments outside of incorporated areas. [[Road names/USA/City names|See wiki page for more information on this.]]<br />
* Always needed: Handle URs (update requests)<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/To_do|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}}/To_do]] 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>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Delaware/AM/Editor/Area&diff=174404Delaware/AM/Editor/Area2021-07-21T14:11:24Z<p>Phuz: */Area manager table update*/</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE ------------------------------<br />
------------------------ SCROLL DOWN FOR INSTRUCTIONS -----------------------------<br />
-----------------------------------------------------------------------------------><noinclude><!--Keep hard coded due to unique page address--><div class="center"><span class="noprint plainlinks purgelink" style="{{Road/style}}background-color:#93c4d3">[{{FULLURL:{{#titleparts:{{PAGENAME}}|-3}}|action=purge}}#Area_Managers <span title="Return to the Area Manager table">&nbsp;Press here to return to the Area Managers table to see your changes&nbsp;</span>]</span></div></noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ------------------------------------- INSTRUCTIONS - START READING HERE ------------------------------------- --------------------<br />
-------------------------------------------------------------------------------------<br />
-- Country/State Managers: Cancel this edit and use the link at the top of the table.<br />
<br />
-------------------------------------------------------------------------------------<br />
<br />
-- Editors: To add yourself to this Area Manager table, copy and paste the following<br />
<br />
-- template into the space below with the other {{AM/Editor|...}} templates. Add<br />
-- yourself into rank order (higher at top)then alphabetical order by user name (A-Z)<br />
-------------------------------------------------------------------------------------<br />
{{AM/Editor|YOUR_USER_NAME|YOUR_RANK#|YOUR_AREA|ANY_COMMENT}}<br />
-------------------------------------------------------------------------------------<br />
-- then in the Summary field enter "Added YOUR_USER_NAME" and press "Save page"<br />
-------------------------------------------------------------------------------------<br />
------------------- DO NOT MODIFY CONTENT ABOVE THE EQUAL SIGN ----------------------<br />
================================================================================-->|-<br />
{{AM/Editor|TR-11|4|Delaware LAM|Contributor to Lancaster County, PA and Eastern Shore, MD}}<br />
{{AM/Editor|Drummin4JC|4|Area Manager (AM) Northern Half of State|gho=Adam|pic=File:ProfilePic2.jpg|Resident of PA|badge1=am|badge2=mr}}<br />
{{AM/Editor|BC21620|4|New Castle County, Delaware|AM Upper Eastern Shore of Maryland}}<br />
{{AM/Editor|SMac3265|3|Dover, Delaware|Lewes, DE}}<br />
<br />
<!--+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br />
------------------- DO NOT MODIFY CONTENT BELOW THE PLUS SIGN -----------------------<br />
-------------------------------------------------------------------------------------<br />
-------------------------------------------------------------------------------------<br />
--></includeonly></div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Delaware/AM/Editor/Area&diff=174347Delaware/AM/Editor/Area2021-07-13T19:51:59Z<p>Phuz: */Area manager table update*/</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE ------------------------------<br />
------------------------ SCROLL DOWN FOR INSTRUCTIONS -----------------------------<br />
-----------------------------------------------------------------------------------><noinclude><!--Keep hard coded due to unique page address--><div class="center"><span class="noprint plainlinks purgelink" style="{{Road/style}}background-color:#93c4d3">[{{FULLURL:{{#titleparts:{{PAGENAME}}|-3}}|action=purge}}#Area_Managers <span title="Return to the Area Manager table">&nbsp;Press here to return to the Area Managers table to see your changes&nbsp;</span>]</span></div></noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ------------------------------------- INSTRUCTIONS - START READING HERE ------------------------------------- --------------------<br />
-------------------------------------------------------------------------------------<br />
-- Country/State Managers: Cancel this edit and use the link at the top of the table.<br />
<br />
-------------------------------------------------------------------------------------<br />
<br />
-- Editors: To add yourself to this Area Manager table, copy and paste the following<br />
<br />
-- template into the space below with the other {{AM/Editor|...}} templates. Add<br />
-- yourself into rank order (higher at top)then alphabetical order by user name (A-Z)<br />
-------------------------------------------------------------------------------------<br />
{{AM/Editor|YOUR_USER_NAME|YOUR_RANK#|YOUR_AREA|ANY_COMMENT}}<br />
-------------------------------------------------------------------------------------<br />
-- then in the Summary field enter "Added YOUR_USER_NAME" and press "Save page"<br />
-------------------------------------------------------------------------------------<br />
------------------- DO NOT MODIFY CONTENT ABOVE THE EQUAL SIGN ----------------------<br />
================================================================================-->|-<br />
{{AM/Editor|TR-11|4|Delaware LAM|Contributor to Lancaster County, PA and Eastern Shore, MD}}<br />
{{AM/Editor|Drummin4JC|4|Area Manager (AM) Northern Half of State|gho=Adam|pic=File:ProfilePic2.jpg|Resident of PA|badge1=am|badge2=mr}}<br />
{{AM/Editor|BC21620|4|New Castle County, Delaware|AM Upper Eastern Shore of Maryland}}<br />
<br />
<!--+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br />
------------------- DO NOT MODIFY CONTENT BELOW THE PLUS SIGN -----------------------<br />
-------------------------------------------------------------------------------------<br />
-------------------------------------------------------------------------------------<br />
--></includeonly></div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Delaware/Area_Managers/Main&diff=174346Delaware/Area Managers/Main2021-07-13T19:50:57Z<p>Phuz: */Area manager table update*/</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.<br />
---- 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|gho=yes|badge1=x|badge2=x|badge3=x}}<br />
---- If any fields are skipped, ensure the first three pipe "|" characters are<br />
---- present. Note the badge1, badge2, badge3 entries are optional, and the "x"<br />
---- is replaced only by 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: "Template:AM/Badge"<br />
<br />
----<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|orbitc|6|Entire State of DE, also NY, NJ, PA. CT, ME, MA, NH, RI, VT|Region 9 Northeast & 8 New England|gho=Orbit C|pic=File:Avatar OrbitC.jpg|badge1=RC|badge2=mr|badge3=GC|badge4=MGC}}<br />
<!-- {{AM/Editor|voludu2|5|Entire State of DE|PA State Manager|gho=voludu2|pic=File:Avatar voludu2.jpeg|badge1=AM|badge2=SM|badge3=CM}} --><br />
{{AM/State}}<!-- Defines the start of the state manager section --><br />
{{AM/Editor|Poncewattle|5|Statewide|State Manager|gho=Nigel|pic=File:Avatar Poncewattle.jpg|badge1=SM|badge2=M}}<br />
{{AM/Editor|phuz|5|Statewide|State Manager|gho=Matt|badge1=SM|badge2=M}}<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>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Best_map_editing_practice&diff=174312Best map editing practice2021-07-06T11:04:49Z<p>Phuz: Punctuation</p>
<hr />
<div>{{construction<br />
| contact = https://www.waze.com/forum/viewtopic.php?f=1636&t=273406<br />
| contacttype = forum<br />
| draft = yes<br />
| open = yes<br />
| section = no<br />
| talk = no<br />
}}<br />
<br />
{{ReturnTo | Editing manual | the editing manual}}<br />
<br />
The purpose of this page is to help all map editors design maps that work best for the end-user--the driving public--while minimizing the amount of (re)work you have to do because of common mistakes or subtle limitations of the tools. For those who are an [[Area Manager]], many helpful pages already exist on your responsibilities, including how to use [[Waze Map Editor]], identify and solve [[Map problems]] and [[Update Requests]], set standards for [[Road types and names|labeling roads]], and a general [[Frequently Asked Questions (FAQ)]]. These same sources are incredibly useful for newer editors as well and should be reviewed to become familiar with the various elements of Waze map editing before getting too deep with your edits.<br />
<br />
If you find something missing from this page or any page of the Wiki, either be bold and edit the page to add or modify the information (if you are confident that is how it works), or you can post a comment in the [http://www.waze.com/forum/viewforum.php?f=276 Wiki improvement forum].<br />
<br />
{{LocalGuidance}}<br />
<br /><br />
{{TOC}}<br />
<br />
==Overall Goals==<br />
<br />
===Usability===<br />
When it comes to the map, the first and foremost goal of editing is to provide the driver with a map that is easy to follow on a small display and to produce sensible verbal instructions when (and only when) they are needed.<br />
<br />
===Simplicity===<br />
It is ''not'' a goal to model the physical roadway lane-by-lane. Doing so often leads to unnecessary complexity--which means a cluttered map, confusing verbal directions, and lots and lots (and lots!) of extra map maintenance.<br />
<br />
===Retention===<br />
Because Waze users drive over them, road segments retain certain information (e.g., average speed) that is used in route optimization. When a segment is deleted, the information in the segment is discarded. Given a choice between deleting a tangle of segments and creating new ones in their place, vs. untangling them and reusing them, it is better to "recycle."<br />
<br />
==In Practice==<br />
<br />
===Divided and un-divided highways===<br />
===={{anchor|When (Not) to Split a Two-Way Road|When to Split a Two-Way Road (and when not to)|When to divide a TwoWay Road (and when not to)}}When to divide a two-way road (and when not to)====<br />
<!-- After this anchor is updated to the new term, update the glossary to link back here for the entry [[Glossary#Dual carriageway]] --><br />
Generally, a road should be divided in Waze ''if and only if'' it is divided in reality—that is, if there is a median that cannot physically or legally be crossed. Consider these points:<br />
<br />
*Using one two-way segment to represent a divided road leads to<br />
*#premature arrival notifications for anyone with a destination on the opposite side of the median, and<br />
*#poor start-of-route routing behavior.<br />
*Using two one-way segments to represent an undivided road leads to<br />
*#incorrect end-of-route instructions, including unnecessary U turns, for anyone with a destination on the opposite side of the road which can legally and physically be reached by simply turning across the roadway centerline, and<br />
*#incorrect start-of-route instructions, including unnecessary U turns, for anyone starting a route from the opposite side of their intended initial direction of travel.<br />
*Roads often alternate between undivided and divided sections. It's important to get these transitions right so that navigation works properly along the entire road.<br />
*If you are unsure whether to divide or un-divide a road, consult with local leadership for assistance.<br />
<br />
<br /> <br />
<br />
'''A road should be divided when <u>any</u> of the following conditions is met:'''<br />
<br />
*It is an Interstate Highway, other freeway, or other controlled- or limited-access road with separated directions of travel, or<br />
*There is a physical median or other traffic control device which makes it impossible or illegal to turn left onto or off of the road, including but not limited to where<br />
**Houses, businesses, or other destinations are located directly on the street but are not accessible from the opposite direction of travel due to a median or other traffic control device that either physically or legally prohibits such access, or<br />
**U-turns are required for proper navigation to or from side roads or destinations.<br />
<br />
'''A road should <u>not</u> be divided when any of the following conditions is met:'''<br />
<br />
*There is a shared two-way center turn lane (of any width) between the directions of travel, or<br />
*It is both possible and legal to make a left turn across the roadway centerline at any point along the road (''e.g.'', across a normal double yellow line to enter a driveway).<br />
{{clear}}<br />
<br />
Remember that dividing and un-dividing roads are delicate processes, and special care must be taken to ensure that each junction and segment is set up correctly. Also, remember that both dividing and un-dividing processes cause a temporary but significant loss of traffic data, which can result in poor ETA and routing behavior in the weeks following the edit.<br />
<br />
====How to divide a two-way road====<br />
<br />
Real writeup coming.<br />
<br />
In the meantime:<br />
<br />
*Take note of any existing turn restrictions, lanes, and attribute (''e.g.'', speed limit, elevation, city name, street name) changes along the section you intent to divide. You may find it helpful to use temporary map comments (set to expire in a day or two) to mark these locations for yourself. However, note that existing U turn restriction data in particular might not be accurate.<br />
*Take note of any [[house number]]s on the segment, noting any unusual stop point locations.<br />
*Then, follow this video tutorial for the process of dividing the road itself:<br />
<br />
https://youtu.be/LhFqxMM1vMk<br />
<br />
*Once you have physically divided the road, ensure that all turn restrictions (including U turn restrictions), lanes, and attributes are set correctly.<br />
*Add a [[Junction Box]] to any intersection where it becomes necessary to prohibit or allow U turns and/or to disambiguate between straight-ahead and left-turning traffic.<br />
<br />
===={{anchor|How to "Un-Split" two One-Way Roads|How to "Un-divide" two One-Way Roads}}How to un-divide two one-way roads====<br />
Unfortunately, there is no easy way to merge two one-way roads back into a two-way road--which is why you should always give a lot of thought before dividing a road in the first place. And then think some more.<br />
<br />
When you come across a road in your area that has been divided but shouldn't have been, you have some major map surgery ahead of you. Because of this high complexity in this process, it is recommended NOT to merge the two one-way roads UNLESS there are Update Requests related to the road caused by it being divided.<br />
<br />
{{Red|The process to un-divide a road (convert from two one-way roads to one two-way road) written below has been specifically designed to preserve the underlying address information embedded in the street segments. It is very important that you do not simply delete one of the two roads because that deletes the house address data on that part of the road. They would have to be looked up and manually added back to the new road.}}<br />
<br />
The steps below show how to properly merge two one-way roads and preserve the underlying house numbers.<br />
<br />
This is our example road segment. For the entire length of the road you need to:<br />
<br />
[[File:DivideRoads 2018 00001.png]]<br />
<br />
1. Select the two segments to be merged and set them both to two-way.<br />
<br />
[[File:DivideRoads 2018 00002.png]]<br />
<br />
2. Disconnect both segments from one side of the section being un-divided. It is best to disconnect alternate ends of each segment as shown.<br />
<br />
[[File:DivideRoads 2018 00003.png]]<br />
<br />
3. Bring the two disconnected ends together in the middle (and realign the roads as necessary, removing the unnecessary segments as shown). You can remove the junction point you just created by selecting it and clicking the trash can icon or using the Delete key (Fn + Delete on Mac). Please note that the 2 aligned sections must have matching road information (name, type, direction, speed limit, elevation, and lock) or the junction point will not allow removal!<br />
<br />
[[File:DivideRoads 2018 00004.png]]<br />
<br /><br />
{{clear}}<br />
[[File:DivideRoads 2018 00005.png]]<br />
<br />
The following video was recorded by an editor merging two one-way roads so the addresses were preserved. This video follows the described steps above but may help seeing it happening in real time. Press the "enlarge button in the lower right corner to see it full screen.<br />
<br />
{{#ev:youtube|6blRMtGwaYA}}<br />
[https://www.youtube.com/watch?v=6blRMtGwaYA Un-Dividing Roads and Preserve HN - Video Reference]<br />
<br /><br /><br />
[https://youtu.be/rkrxrz-gIC0 Un-Dividing Roads WME 2018 - Video Reference]<br />
<br /><br />
<br />
After BOTH sides are merged into one, you need to re-align house number to the street so that it lines up with driveway/entrance of the building the bubble is over.<br />
<br />
#With the street/road selected, click ‘Edit house numbers’.<br />
#From the house number editing view, you need to select each house number one-by-one.<br />
#With the house number selected, you see the dashed line is attached to a circle on the street.<br />
#Select the circle and move it along the road closest to the entrance of the driveway to the building.<br />
<br />
Also be sure to check the following:<br />
<br />
#Remove all "orphaned" junctions.<br />
#Change the direction of the preserved segments to two-way.<br />
#Check/fix the connectivity of all the roads already connect to the side you kept.<br />
#Connect (and set connectivity) of all the roads that used to be connected to the other side.<br />
#Make sure all the new two-way segments are connected.<br />
#Adjust the geometry to move the two-way road segments to the middle of the road.<br />
<br />
<br />
Now repeat the entire process for the remaining segments matching the two opposite from each other.<br />
<br />
It isn't difficult once you have gone through the process a couple of times.<br />
<br />
'''Caveat:''' If you decide to be clever and edit the road properties of multiple segments at a time, first familiarize yourself with the known problems with mass-editing. It can be done -- but if you're not careful, you'll find that all the road segments have reverted to Streets...in Alabama...and any alternate road names are lost.<br />
<br />
===Highways and Ramps===<br />
<br />
Useful long-range navigation is impossible with Waze if the highways are broken. Because limited-access roads -- typically Freeways &amp; Major Highways -- offer more to think about (and more opportunities to mess them up) than typical surface-road work, this section is very important.<br />
<br />
====Roads====<br />
<br />
The term "limited-access road" here refers to a road that is multi-laned in each direction, with a physical barrier between directions, and which can be entered and exited solely by ramps. Such roads should almost always be mapped as separate one-way segments -- and other roads should almost never be.<br />
<br />
====Ramps====<br />
<br />
As stated elsewhere, off-ramps should be named according to their exit number if they have one, as well as whatever is on the actual exit sign; e.g., "Exit 7: Rte 3 S / Braintree / Cape Cod". On-ramps should be named "to" whatever they lead to; e.g., "to I-93 S / Quincy / Providence RI". Because ramps often run especially close to other ramps that flow in the opposite direction, a ramp should be locked to preserve directionality. <!-- ((This bug has been fixed:))(Not locking ramps means you will end up coming back later to fix a ramp that has become two-way--and has started directing traffic accordingly.) --> <br />
<br />
Remember to check connectivity and turn restrictions while you're there.<br />
<br />
*There is a more detailed description of [[Road names/USA#Exit ramps and Entrance ramps (on-ramps)|How to label Exit ramps and Entrance ramps]].<br />
<br />
*Be sure to understand the difference between ramps and [[at-grade connectors]].<br />
<br />
====Overpasses &amp; Underpasses====<br />
<br />
Setting the road elevation can be tricky. Sometimes it is more important to know that road elevation is an issue for a particular segment (e.g., a mile-long stretch of highway that extends well beyond the screen boundaries), than what its actual value is, or of maintaining a consistent elevation across multiple segments of the same road.<br />
<br />
Ground level should be considered as a "sentinel value" that signifies a segment has no overpasses or underpasses. When editing an over/underpass, if either segment is at ground level, set the other one to a non-zero value that reflects its relative elevation to the one marked at ground level. If both elevations are already non-zero, either they are already correct (in which case no further action is required) or they are incorrect in which case the area needs to be studied carefully so as not to "break" other intersections that have already been evaluated and assigned.<br />
<br />
In many cases, the conflict can be resolved simply by adjusting the elevation of one segment, or perhaps of several segments. Proceed with caution. In really complicated situations, it might help to draw a picture, or to start by looking for the top-most or bottom-most segment.<br />
<br />
Occasionally you run into a situation in which no set of values will work. For example, three segments named A, B, and C: A crosses over B, B crosses over C, and C crosses over A. So A > B > C > A... now what? Either pretend that one of the segments crosses over both of the others, or add a junction to one of the segments so that it can have two different elevations as needed and hope nobody deletes that "unnecessary" junction without investigating why it might be there. In this example it might even make sense to add junctions to all three segments, just to make it clearer to the next AM what you're trying to accomplish.<br />
<br />
====Caveat re. Elevation====<br />
<br />
No matter what elevation road segments are assigned, if you pin a junction through them, they now form a navigable intersection, and Waze '''will''' instruct people to turn off of bridges and onto the cross-streets below. If you are looking at an over/underpass, and there is a junction where the roads cross, get rid of it. First, make sure the elevations of the road segments are correct, and that all the other information of each pair of road segments match. At that point, deleting the junction will most likely work. If that does not work, refer to [[Map Editing Quick-start Guide#Delete a Junction|deleting a junction]] for more information.<br />
<br />
See also [[Creating and editing road segments#Road elevation|Road Elevation]].<br />
<br />
====Bridging Roads====<br />
<br />
Select the two segments that cross over/under the intersection, then click on the "Bridge" link. If all goes well, the selected segments will be separated from the underlying junction, consolidated into a single segment, and their elevation increased by 1. Failing that, you may have to disconnect both sides of the over/underpassing road from the junction, make sure their elevations are correct, and then re-connect them.<br />
<br />
====Handling Restricted Lanes====<br />
{{mbox<br />
| type = cleanup<br />
| textstyle = color: red; font-weight: bold; font-style: italic;<br />
| text = There have been major changes to the way [[Partial restrictions]] are handled in the WME. The text below is out of date and should not be utilized when editing the map<br />
}}<br />
<br />
<span style="text-decoration: line-through;">At this time, Waze does not have a facility to handle restricted lanes; e.g., high-occupancy/"carpool" lanes. This is important because these lanes sometimes have their own ramps that the regular lanes do not have, and they often run alongside the main road so that GPS has a hard time discriminating between the two. The result is driving instructions that can range from incorrect to deadly.<br></span><br />
<br />
The most direct solution might appear to be omitting/deleting these lanes from the map. Please '''do not''' delete these lanes. As Waze implements more features, it helps (in terms of testing and making the feature available) if these lanes are already mapped.<br><br />
<br />
<span style="text-decoration: line-through;">The best partial solution the community has come up with is described in detail on the [[Carpool, HOV, Transit lanes]] page. The lanes should be set with the appropriate road type for the road they are part of, and the entrance (and in some cases exit) ramps set with the appropriate restrictions for vehicle type (and time). If the lanes are reversible then they will have to be set with separately timed restrictions for each direction on the lanes themselves as well.<br></span><br />
<br />
<span style="text-decoration: line-through;">This "solution" gives routing onto these special lanes a very high [[Routing penalties|penalty]] when they are being enforced, and reduce the likelihood that Waze will create a route over them. It does not prevent Waze from snapping a driver to the segments if it determines they are on such a lane, and any recalculation of the route from these segments is correct as well. However, as noted above, the fact that these lanes are usually quite close to the normal/open freeway or highway makes it unlikely Waze will automatically recognize their true location due to GPS inaccuracy and margin of error.</span><br />
<br />
{{details|Carpool, HOV, Transit lanes}}<br />
<br />
====High Occupancy Toll (HOT) Roads/Lanes (USA)====<br />
The United States DOT has been working with local governments to introduce a new type of roadway called High Occupancy Toll (HOT) lanes/roads. In many cases, these roads replace existing [[Carpool%2C_HOV%2C_Transit_lanes|HOV lanes]] and run in the median between different directions of non-toll traffic along a freeway.<br />
<br />
[[Image:I-15-express-lanes.jpg]]<br />
<br />
HOT roadways have the following features:<br />
<br />
*These lanes/roads allow both toll traffic and HOV traffic to traverse the same lanes.<br />
*There are no toll plazas or booths for paying by cash. All tolls are paid electronically to maintain traffic speed.<br />
*Entrances and exits to the HOT lanes are limited to help maintain high speeds.<br />
*There are no entrance/exit combinations where the toll fare rules don't apply.<br />
*Tolls are discounted or waived for users that meet High Occupancy Vehicle (HOV) requirements. These requirements may change based on time of day.<br />
<br />
HOT lanes are often marketed as "Express Lanes"; however, the term "Express Lanes" is also used by various regional governments for non-HOT lanes. In order to be considered a HOT lane for Waze purposes, a road needs to meet all criteria listed above.<br />
<br />
{{mbox<br />
| type = cleanup<br />
| textstyle = color: red; font-weight: bold; font-style: italic;<br />
| text = There have been major changes to the way [[Carpool,_HOV,_Transit_lanes|HOV lanes]] are handled in the WME. The text below is out of date and should not be utilized when editing the map<br />
}}<br />
<br />
<span style="text-decoration: line-through;">The entrances to HOT lanes should be marked with the toll flag. This prevents Waze from routing those wishing to avoid tolls onto the HOT lanes, while allowing Waze to use the HOT lanes for routing for those willing to pay a toll for a faster commute.</span><br />
<br />
<span style="text-decoration: line-through;">The lanes of the HOT itself should not be flagged as a toll road, to prevent Waze from trying to route HOV users out of the HOT lanes if they have toll avoidance active in the client.</span><br />
<br />
<span style="text-decoration: line-through;">Because Waze does not currently support HOV lanes, HOV users with toll avoidance turned on are not routed onto the HOT lanes. Just as with the current HOV best practices, those that meet the HOV requirements and wish to use the HOT lanes need to navigate themselves to the HOT lanes; they are not be routed onto them by the Waze client. As with standard HOV lanes, HOV users need to recalculate the route for Waze to snap them to the HOT lane.</span><br />
<br />
<span style="text-decoration: line-through;">Because HOT lanes are still considered "experimental" there may be some variation in local implementation. If the HOT lane does not meet all the requirements listed above, check with an experienced local editor or Country Manager before making any changes. When in doubt seek advice on the forum; a change to the guidelines or an exception may need to be made for the local variation.</span><br />
<br />
===Toll roads===<br />
<br />
Roads with tolls can be indicated using the checkbox '''Toll road''' in the Add Restrictions menu on the [[Creating and editing road segments#Road Properties|road segment properties]] tab. Mark a segment as a toll road only if there is a toll booth, transponder reader, or other tolling device within or at either end of the segment. Do not set segments as toll roads if they are leading up to the final toll segment, even if they have no other exit except the final toll segment.<br />
<br />
In the case of a bridge that is tolled in only one direction, divide the road where the toll is collected and mark only the segment with the toll booth as a toll road.<br />
<br />
For more information, see the [[toll]] page.<br />
<br />
===Time Restricted Turns===<br />
The Waze Map Editor and routing engine support scheduled restrictions (time of day, day of week, turns, traffic flow direction, vehicle type, etc.).<br />
<br />
Please see the [[Partial restrictions]] page for full documentation on this feature.<br />
<br />
<br />
===When to Use Ramps in an Intersection===<br />
Please see the discussion on [[at-grade connectors]].<br />
<br />
<br />
===When to Create a Roundabout===<br />
In the author's editing and driving experience, once you learn [[Creating and Editing a roundabout|how to create a roundabout]], it is '''always''' the right time to replace an ''ad hoc'' traffic circle (built from regular road segments) with a proper roundabout. The voice cues produced by an ad-hoc circle can be terribly misleading, and the client display almost always looks unprofessionally sloppy. Replacing this with a roundabout is an instant, orders-of-magnitude improvement on both counts.<br />
<br />
'''''Note:''' A roundabout should never be used in place of an end-node on dead-end or cul-de-sac street. See: [[Junction_Style_Guide#Cul-de-sacs|Junction Style Guide]]''<br />
<br />
<br />
===Locking Segments===<br />
In some regions, there are locking rank standards applied based on road type. In these regions, all roads of a certain type are locked to a minimum rank and should be locked even in residential areas. Check [[Template:Countries|your local wiki]] for your local standards to see if these apply in your editing area. Locking should otherwise be used on high-value roads and complicated junctions to prevent inexperienced lower rank editors from making changes.<br />
<br />
NEVER lock a segment unless you are sure that it and everything that touches it (junctions, turn restrictions, and other segments) is 100% complete and correct.<br />
<br />
If you run into a segment or junction that is locked by someone at a higher editing rank than you, refer to the page on [[Editing restrictions#Unlocking an object above your rank|unlocking an object above your rank]] for more information.<br />
<br />
'''Locking should be used sparingly and carefully.'''<br />
<br />
<br />
===Junction Style Guide===<br />
When creating or editing a junction, it is very important to understand the nuances of how the Waze routing engine looks at the map segments and junctions. The [[Junction Style Guide]] provides the best practices with the many different types of junctions.<br />
<br />
<br />
===Parking Lots===<br />
{{mbox | type=important | text = {{As of | 2018 | 10}}, guidance changed to recommend more detailed mapping of Parking Lot roads, in those lots which should be mapped. There is no priority to adapt existing lots to the new standards unless working on or near the lot for other reasons or there is guidance from a senior editor to pursue it.}} <br />
<br />
Mapping the roads inside parking lots serves the following purposes:<br />
<br />
#It allows Waze to provide door-to-door directions to Places within the lot.<br />
#It allows Waze to recognize that the client is off the main road, avoiding erroneous traffic reports.<br />
#The '''[[Road_types#Parking_lot_road|Parking Lot Road]]''' road type prevents routes from transiting the lots to other destinations.<br />
#It allows Waze to calculate estimated times for walking from the parking lot to destinations, and to calculate walking times for users leaving Places near the lot.<br />
<br />
For information on how to map '''Parking Lot Area (PLA) Places''', see the [[Places/Parking_lot]] page. Parking lot roads are not limited to use with PLAs, though they are best used in combination.<br />
<br />
The '''Parking Lot Road''' type exists to allow proper navigation into and out of parking lots while discouraging routes through parking lots. Waze applies a penalty to routes which transition from Parking Lot Road to other road types. This transition penalty decreases the chances that Waze will route through a parking lot as a shortcut but doesn't interfere with navigation to or from points within parking lots. Avoid mixing road types within a parking lot so as to avoid triggering the transition penalty unnecessarily. See [[Road_types#Parking_lot_roads]] for more information on this road type. <br />
<br />
{{mbox | type = neweditor | text = All roads, including parking lot roads, [[Creating_and_editing_road_segments#Confirm_the_road_by_updating_details|must be verified]] by having a street and city name applied or by utilizing the ‘None’ checkboxes.<br /><br />
<br />If [[Places#Residential_point_place|Residential Point Places (RPPs)]] are used along the parking lot, adding alternate street/city names could be required if the RPP is some distance from the named road. If an RPP fails to save near an unnamed PLR, or if in-app routing fails to navigate to the PLR, add the street & city names as an alternate on the PLR. One or more tile updates may be required before RPPs function near PLRs with alternate street/city names.}}<br />
<br />
====Large Parking Lots====<br />
When mapping large parking lots, map each aisle of the parking lot. Add any appropriate turn restrictions, one-way segments, etc., as you would with any road.<br />
<br />
On any two-way segment which travels directly along perpendicular parking spaces, set the U-turns at either end of the segment to Allowed. This enables the routing server to implicitly direct the user to exit their parking spot in the optimal direction. Typically aisles for angled parking are one-way, and U-turns are not available. In rare cases, angled two-way parking may occur, and in this case, u-turns should be Prohibited. <br />
<br />
{| class="wikitable" style="margin: auto;"<br />
|-<br />
|[[File:Perpendicular Parking Lot Parking.PNG]]<br />
|-<br />
|PLR aisles with perpendicular parking (u-turn on ends of green star segments)<br />
|-<br />
|[[File:Angular Parking.png]]<br />
|-<br />
|PLR aisles with angled parking (u-turn on ends of green check segments)<br />
|}<br />
<br />
====Parking Garages==== <br />
[[File:ParkingGaragePLRs.jpg|thumb|right|PLRs for a Parking Garage]] Parking garages should not have each lane visible on the uppermost parking level mapped. Instead, each entry and exit road should be mapped as one-way or two-way as appropriate. {{As of | 2018 | 10}}, [[Places/Parking_lot|Parking Lot Areas (“PLA”)]] do not support multiple entries. For this reason, connect the entry and exit road segments to a single segment, with the PLA’s entry point set along that segment. This allows Waze to choose the best entry to the garage depending on the route’s starting location. <br />
<br />
====Small Parking Lots====<br />
[[File:OneWayPairPLR.jpg|right|frame|Using a single two-way segment to approximate two one-way aisles]] For small lots, if there is only one entrance and one exit, or if there are multiple entrances/exits near to each other on the same road, then it may not be necessary to add PLRs at all, especially if the entrances and exits are on a divided or one-way road (so there's effectively only one way in and one way out). Small parking lots should be mapped if:<br />
<br />
#there are entrances/exits to the lot on more than one street;<br />
#there are nearby PLRs that might cause a user to be snapped to the wrong lot;<br />
#the Place served is a gas station or has a drive-thru.<br />
<br />
If the small lot is on at the corner of two or more non-PLR roads, the value of the lot should be carefully weighed against the damage to (turn timing) done by adding nodes near an intersection. Consider if the addition of a [[Junction Box]] is needed to resolve data collection concerns.<br />
<br />
If it is determined that PLRs are desirable in a small lot, then follow the same instructions as when mapping a large lot. However, in cases where a small store-front parking lot has a pair of one-way aisles, such as at a ‘strip mall’, it is acceptable to use a single two-way road segment that approximates the location of both aisles. In this case, enable the u-turns on either end of the segment, so users traveling in either aisle will get efficient routes. <br />
<br />
====Drive-Through Lots====<br />
<br />
Because drive-through lots can be narrow and congested, with one-way sections, the best way to represent them is often a one-way drive-through loop. ''Caveat: because both ends of a segment cannot connect to the same junction, if the lot has only one entrance/exit, it is necessary to build the [[Junction Style Guide#Loops|loop using three segments]].''<br />
<br />
====Two parking lots connected to the same street====<br />
<br />
Bad routing can occur when two parking lots connect to the same street. This can happen, for example, where two lots face each other. If you connect both parking lots to the street using ''the same junction'' as the connection point for both, Waze will treat them as one parking lot. <br />
<br />
If there are no turn restrictions preventing routing across the street, Waze may route the driver through one parking lot to reach a destination in the other parking lot. Waze is designed to avoid such routes, but in this configuration, Waze does not apply the expected penalty - because crossing through the junction from one parking lot segment to the other is not considered a transition, even though there is also a street running through the junction. This may be most easily understood by looking at the example image below.<br />
<br />
If it is not legal to cross from one lot to the other, [[turn restrictions]] will prevent any sort of routing between the lots. However, if it is possible to route from one lot to the other, then a different method is required to prevent routing through one lot to reach the other. <br />
<br />
To be sure that Waze will apply the transition penalty when routing through one parking lot from another, the two parking lots must be isolated from the each other such that passing from one to the other requires driving over a standard road segment (not a parking lot road or [[Private road|private road]]). You should use a short "stub" length no less than {{:Segment length/Minimum}} of a standard road segment. This segment will run from the junction to the entry/exit segment of one of the lots. With this configuration, exiting the parking lot will have a consistent penalty, whether the route exits the first parking lot to the street or the route leads to another parking lot at the same junction. The short stub may reduce display impact and will also signal other editors that the use of a different road type is not accidental.<br />
<br />
Parking lots do not have to be across the street from each other. In a strip mall, if the exit segment of one business is joined to the entrance segment of the next business, the same problem can occur.<br />
<br />
=====Illustration=====<br />
<br />
For example, in the configuration shown below, if routing from the west parking lot, there is no transition penalty to route through the gas station parking lot on the east side of the street if routing east on Riva Rd. Conversely, if routing to the west parking lot from Riva Rd. there is no transition penalty to use the gas station. <br />
<br />
[[File:PLA.png|center]] {{clear}}<br />
<br />
<br />
[[File:PLB.png|right]]This potential problem arises when two parking lots on opposite sides of a street connect at the same junction node on the street.{{clear}}<br />
[[File:PLC.png|right]]If this configuration causes routing problems it can be solved by changing the road type of one (or both) of the parking lot roads that intersect with the street.{{clear}}<br />
[[File:PLD.png|right]]A {{:Segment length/Minimum}} or longer stub of a different road type will accomplish the same result.{{clear}}<br />
[[File:PLE.png|left]]If the street is a divided highway, then the road type of the crossover segment may be changed (this may also allow [[U-turn_prevention#Avoiding_U_turns|U-turns]] at the crossover segment).<br />
{{clear}}<br />
<br />
==New Roads==<br />
===Recorded via Client===<br />
Once you start editing a road, it changes from red (a new road) to the color of a road type (by default a white street) and will then appear on the next [[Timeline of updating process|update of the Live Map]] which goes out to all Waze users.<br />
<br />
So it is '''less than helpful''' if you do an incomplete job. At least if the road is red, then someone else knows that it needs work. If it is white, perhaps even with a street name, then it may look correct. But Waze may not view it as navigable.<br />
<br />
Follow these simple steps, as best you can, and get it right the first time. [[Waze Map Editor|Map Editing]] explains how to carry out these steps.<br />
<br />
#Align the [[glossary|geometry]] of the road to the aerial image unless that is [[Warning on possible lack of accuracy in aerial images|not appropriate in your area]]<br />
#Enter the correct name and road type for your road, following the standards for your country<br />
#Make sure the road has the correct [[glossary|directionality]]. Most roads should be Two Way.<br />
#Add junctions where the road intersects with other roads. By default tick "Enable all turns". Restrict any turns that are not allowed. If a junction appears, just add a junction over the top. Chances are it does not have all turns enabled. Waze automatically handles turn restrictions for one-way roads.<br />
<br />
<br />
===Roundabouts===<br />
<br />
*A proper roundabout (i.e., produces "at the roundabout..." verbal cues) can only be created in WME.<br />
*When it is first created, the segments are configured as new roads - they need to be edited as above before they become part of the live map.<br />
*Please see [[Creating and Editing a roundabout]] for more information on creating these special intersections.<br />
<br />
{{ReturnTo | Editing manual | the editing manual}}<br />
<br />
[[Category:Style Guides]]<br />
[[Category:Convert to Subpages]]<br />
[[Category:Add Wikilinks]]</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=174276User:Phuz2021-06-15T16:55:43Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
**R5 (May 2021)<br />
*'''Manager'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
****Entire State (May 2021)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaid'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
**Luzerne Co, PA HN Mini-Raid (March 2021)<br />
*'''Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
**DelDOT Closure Bot (July 2020-Present)<br />
**WME DOT Cameras [SCRIPT] (July 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
**WME DOT Advisories [SCRIPT] (October 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
**JB U-Turn Sheet Missing Data (February-March 2021)<br />
***Scanned all segments in sheets to backfill missing data for all regions in US<br />
*'''Mentoring (Unofficial)'''<br />
**Mentored by G_W1Z (R1 through R3)<br />
**Mentored by voludu2 for R4<br />
**Mentored by RussPA for R5<br />
*'''Beta Programs'''<br />
**WME<br />
***LG<br />
***Shields<br />
**iOS<br />
*'''Meetup / Waze Cafe'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)<br />
**Virtual (February 2021) (organizer)<br />
**Virtual NA Mega Meetup (February 21, 2021)<br />
<br />
{| class="wikitable"<br />
|-<br />
!Script!!Link<br />
|-<br />
|WME DOT Cameras||https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
|-<br />
|WME DOT Advisories||https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
|}<br />
[[File:Script.png|thumb|[https://www.waze.com/forum/viewtopic.php?f=819&t=304760]]]</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=174198User:Phuz2021-05-27T17:10:35Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
*'''Manager'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
****Entire State (May 2021)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaid'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
**Luzerne Co, PA HN Mini-Raid (March 2021)<br />
*'''Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
**DelDOT Closure Bot (July 2020-Present)<br />
**WME DOT Cameras [SCRIPT] (July 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
**WME DOT Advisories [SCRIPT] (October 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
**JB U-Turn Sheet Missing Data (February-March 2021)<br />
***Scanned all segments in sheets to backfill missing data for all regions in US<br />
*'''Mentoring (Unofficial)'''<br />
**Mentored by G_W1Z (R1 through R3)<br />
**Mentored by voludu2 for R4<br />
**Mentored by RussPA for R5<br />
*'''Beta Programs'''<br />
**WME<br />
***LG<br />
***Shields<br />
**iOS<br />
*'''Meetup / Waze Cafe'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)<br />
**Virtual (February 2021) (organizer)<br />
**Virtual NA Mega Meetup (February 21, 2021)<br />
<br />
{| class="wikitable"<br />
|-<br />
!Script!!Link<br />
|-<br />
|WME DOT Cameras||https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
|-<br />
|WME DOT Advisories||https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
|}<br />
[[File:Script.png|thumb|[https://www.waze.com/forum/viewtopic.php?f=819&t=304760]]]</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=174135User:Phuz2021-05-16T12:30:25Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
*'''Manager'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaid'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
**Luzerne Co, PA HN Mini-Raid (March 2021)<br />
*'''Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
**DelDOT Closure Bot (July 2020-Present)<br />
**WME DOT Cameras [SCRIPT] (July 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
**WME DOT Advisories [SCRIPT] (October 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
**JB U-Turn Sheet Missing Data (February-March 2021)<br />
***Scanned all segments in sheets to backfill missing data for all regions in US<br />
*'''Mentoring (Unofficial)'''<br />
**Mentored by G_W1Z (R1 through R3)<br />
**Mentored by voludu2 for R4<br />
**Mentored by RussPA for R5<br />
*'''Beta Programs'''<br />
**WME<br />
***LG<br />
***Shields<br />
**iOS<br />
*'''Meetup / Waze Cafe'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)<br />
**Virtual (February 2021) (organizer)<br />
**Virtual NA Mega Meetup (February 21, 2021)<br />
<br />
{| class="wikitable"<br />
|-<br />
!Script!!Link<br />
|-<br />
|WME DOT Cameras||https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
|-<br />
|WME DOT Advisories||https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
|}<br />
[[File:Script.png|thumb|[https://www.waze.com/forum/viewtopic.php?f=819&t=304760]]]</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=174042User:Phuz2021-04-13T15:37:54Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
*'''Manager'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaid'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
**Luzerne Co, PA HN Mini-Raid (March 2021)<br />
*'''Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
**DelDOT Closure Bot (July 2020-Present)<br />
**WME DOT Cameras [SCRIPT] (July 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
**WME DOT Advisories [SCRIPT] (October 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
**JB U-Turn Sheet Missing Data (February-March 2021)<br />
***Scanned all segments in sheets to backfill missing data for all regions in US<br />
*'''Mentoring (Unofficial)'''<br />
**Mentored by G_W1Z (R1 through R3)<br />
**Mentored by voludu2<br />
*'''Beta Programs'''<br />
**WME<br />
***LG<br />
***Shields<br />
**iOS<br />
*'''Meetup / Waze Cafe'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)<br />
**Virtual (February 2021) (organizer)<br />
**Virtual NA Mega Meetup (February 21, 2021)<br />
<br />
{| class="wikitable"<br />
|-<br />
!Script!!Link<br />
|-<br />
|WME DOT Cameras||https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
|-<br />
|WME DOT Advisories||https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
|}<br />
[[File:Script.png|thumb|[https://www.waze.com/forum/viewtopic.php?f=819&t=304760]]]</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Delaware/Area_Managers/Main&diff=174016Delaware/Area Managers/Main2021-04-11T15:57:47Z<p>Phuz: */Area manager table update*/</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.<br />
---- 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|gho=yes|badge1=x|badge2=x|badge3=x}}<br />
---- If any fields are skipped, ensure the first three pipe "|" characters are<br />
---- present. Note the badge1, badge2, badge3 entries are optional, and the "x"<br />
---- is replaced only by 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: "Template:AM/Badge"<br />
<br />
----<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|orbitc|6|Entire State of DE, also NY, NJ, PA. CT, ME, MA, NH, RI, VT|Region 9 Northeast & 8 New England|gho=Orbit C|pic=File:Avatar OrbitC.jpg|badge1=RC|badge2=mr|badge3=GC|badge4=MGC}}<br />
<!-- {{AM/Editor|voludu2|5|Entire State of DE|PA State Manager|gho=voludu2|pic=File:Avatar voludu2.jpeg|badge1=AM|badge2=SM|badge3=CM}} --><br />
{{AM/State}}<!-- Defines the start of the state manager section --><br />
{{AM/Editor|Poncewattle|5|Statewide|State Manager|gho=Nigel|pic=File:Avatar Poncewattle.jpg|badge1=SM|badge2=M}}<br />
{{AM/Editor|phuz|4|Statewide|State Manager|gho=Matt|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>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=173977User:Phuz2021-04-02T12:31:33Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
*'''Manager'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaid'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
**Luzerne Co, PA HN Mini-Raid (March 2021)<br />
*'''Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
**DelDOT Closure Bot (July 2020-Present)<br />
**WME DOT Cameras [SCRIPT] (July 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
**WME DOT Advisories [SCRIPT] (October 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
**JB U-Turn Sheet Missing Data (February-March 2021)<br />
***Scanned all segments in sheets to backfill missing data for all regions in US<br />
*'''Mentoring (Unofficial)'''<br />
**Mentored by G_W1Z (R1 through R3)<br />
**Mentored by voludu2<br />
*'''Beta Programs'''<br />
**WME<br />
**iOS<br />
*'''Meetup / Waze Cafe'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)<br />
**Virtual (February 2021) (organizer)<br />
**Virtual NA Mega Meetup (February 21, 2021)<br />
<br />
{| class="wikitable"<br />
|-<br />
!Script!!Link<br />
|-<br />
|WME DOT Cameras||https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
|-<br />
|WME DOT Advisories||https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
|}<br />
[[File:Script.png|thumb|[https://www.waze.com/forum/viewtopic.php?f=819&t=304760]]]</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=173935User:Phuz2021-03-21T13:34:33Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
*'''Manager'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaid'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
**Luzerne Co, PA HN Mini-Raid (March 2021)<br />
*'''Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
**DelDOT Closure Bot (July 2020-Present)<br />
**WME DOT Cameras [SCRIPT] (July 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
**WME DOT Advisories [SCRIPT] (October 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
**JB U-Turn Sheet Missing Data (February-March 2021)<br />
***Scanned all segments in sheets to backfill missing data for all regions in US<br />
*'''Mentoring (Unofficial)'''<br />
**Mentored by G_W1Z (R1 through R3)<br />
**Mentored by voludu2<br />
*'''Beta Programs'''<br />
**WME<br />
**iOS<br />
*'''Waze Cafe'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)<br />
**Virtual (February 2021) (organizer)<br />
<br />
{| class="wikitable"<br />
|-<br />
!Script!!Link<br />
|-<br />
|WME DOT Cameras||https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
|-<br />
|WME DOT Advisories||https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
|}<br />
[[File:Script.png|thumb|[https://www.waze.com/forum/viewtopic.php?f=819&t=304760]]]</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=173862User:Phuz2021-02-23T21:55:04Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
*'''Manager'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaid'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
*'''Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
**DelDot Data Feed Bot (July 2020)<br />
**WME DOT Cameras [SCRIPT] (July 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
**WME DOT Advisories [SCRIPT] (October 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
*'''Mentoring'''<br />
**Mentored by G_W1Z (R1 through R3)<br />
**Mentored by voludu2<br />
*'''Beta Programs'''<br />
**WME<br />
**iOS<br />
*'''Waze Cafe'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)<br />
**Virtual (February 2021) (organizer)<br />
<br />
{| class="wikitable"<br />
|-<br />
!Script!!Link<br />
|-<br />
|WME DOT Cameras||https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
|-<br />
|WME DOT Advisories||https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
|}<br />
[[File:Script.png|thumb|[https://www.waze.com/forum/viewtopic.php?f=819&t=304760]]]</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=173861User:Phuz2021-02-23T21:39:14Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
*'''Manager'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaid'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
*'''Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
**DelDot Data Feed Bot (July 2020)<br />
**WME DOT Cameras [SCRIPT] (July 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
**WME DOT Advisories [SCRIPT] (October 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
*'''Mentoring'''<br />
**Mentored by G_W1Z (R1 through R3)<br />
**Mentored by voludu2<br />
*'''Beta Programs'''<br />
**WME<br />
**iOS<br />
*'''Waze Cafe'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)<br />
**Virtual (February 2021) (organizer)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Script !! Link<br />
|-<br />
| WME DOT Cameras || https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
|-<br />
| WME DOT Advisories || https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
|}</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=173860User:Phuz2021-02-23T21:32:35Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
*'''Manager'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaid'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
*'''Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
**DelDot Data Feed Bot (July 2020)<br />
**WME DOT Cameras [SCRIPT] (July 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
**WME DOT Advisories [SCRIPT] (October 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
*'''Mentoring'''<br />
**Mentored by G_W1Z (R1 through R3)<br />
**Mentored by voludu2<br />
*'''Beta Programs'''<br />
**WME<br />
**iOS<br />
*'''Waze Cafe'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)<br />
**Virtual (February 2021) (organizer)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Link !! Script<br />
|-<br />
| [img src="https://storage.googleapis.com/wazeopedia-files/thumb/c/cb/Script.png/120px-Script.png"] || Example<br />
|-<br />
| Example || Example<br />
|}</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=173859User:Phuz2021-02-23T14:18:17Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
*'''Manager'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaid'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
*'''Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
**DelDot Data Feed Bot (July 2020)<br />
**WME DOT Cameras [SCRIPT] (July 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
**WME DOT Advisories [SCRIPT] (October 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
*'''Mentoring'''<br />
**Mentored by G_W1Z (R1 through R3)<br />
**Mentored by voludu2<br />
*'''Beta Programs'''<br />
**WME<br />
**iOS<br />
*'''Waze Cafe'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)<br />
**Virtual (February 2021) (organizer)</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Delaware/Notice/Main&diff=173778Delaware/Notice/Main2021-02-10T13:48:03Z<p>Phuz: /*Notice/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 />
{{Mbox|image=none|text=Delaware editors use Discord for fast communication, guidance, and mentorship. Use of Discord will provide you with quick access to senior editors, unlocks, and help with editing. Please send a PM to Poncewattle to be invited into the group. Discord can be accessed via a web browser, desktop app, or as an app for your smartphone.}}<br />
<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/Notice|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}}/Notice]] 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>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Delaware/AM/Editor/Area&diff=173761Delaware/AM/Editor/Area2021-02-05T10:48:51Z<p>Phuz: */Area manager table update*/</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE ------------------------------<br />
------------------------ SCROLL DOWN FOR INSTRUCTIONS -----------------------------<br />
-----------------------------------------------------------------------------------><noinclude><!--Keep hard coded due to unique page address--><div class="center"><span class="noprint plainlinks purgelink" style="{{Road/style}}background-color:#93c4d3">[{{FULLURL:{{#titleparts:{{PAGENAME}}|-3}}|action=purge}}#Area_Managers <span title="Return to the Area Manager table">&nbsp;Press here to return to the Area Managers table to see your changes&nbsp;</span>]</span></div></noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ------------------------------------- INSTRUCTIONS - START READING HERE ------------------------------------- --------------------<br />
-------------------------------------------------------------------------------------<br />
-- Country/State Managers: Cancel this edit and use the link at the top of the table.<br />
<br />
-------------------------------------------------------------------------------------<br />
<br />
-- Editors: To add yourself to this Area Manager table, copy and paste the following<br />
<br />
-- template into the space below with the other {{AM/Editor|...}} templates. Add<br />
-- yourself into rank order (higher at top)then alphabetical order by user name (A-Z)<br />
-------------------------------------------------------------------------------------<br />
{{AM/Editor|YOUR_USER_NAME|YOUR_RANK#|YOUR_AREA|ANY_COMMENT}}<br />
-------------------------------------------------------------------------------------<br />
-- then in the Summary field enter "Added YOUR_USER_NAME" and press "Save page"<br />
-------------------------------------------------------------------------------------<br />
------------------- DO NOT MODIFY CONTENT ABOVE THE EQUAL SIGN ----------------------<br />
================================================================================-->|-<br />
{{AM/Editor|TR-11|4|Delaware LAM|Contributor to Lancaster County, PA and Eastern Shore, MD}}<br />
<br />
<br />
<!--+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br />
------------------- DO NOT MODIFY CONTENT BELOW THE PLUS SIGN -----------------------<br />
-------------------------------------------------------------------------------------<br />
-------------------------------------------------------------------------------------<br />
--></includeonly></div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Delaware/AM/Editor/Area&diff=173760Delaware/AM/Editor/Area2021-02-05T10:47:54Z<p>Phuz: */Area manager table update*/</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE ------------------------------<br />
------------------------ SCROLL DOWN FOR INSTRUCTIONS -----------------------------<br />
-----------------------------------------------------------------------------------><noinclude><!--Keep hard coded due to unique page address--><div class="center"><span class="noprint plainlinks purgelink" style="{{Road/style}}background-color:#93c4d3">[{{FULLURL:{{#titleparts:{{PAGENAME}}|-3}}|action=purge}}#Area_Managers <span title="Return to the Area Manager table">&nbsp;Press here to return to the Area Managers table to see your changes&nbsp;</span>]</span></div></noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ------------------------------------- INSTRUCTIONS - START READING HERE ------------------------------------- --------------------<br />
-------------------------------------------------------------------------------------<br />
-- Country/State Managers: Cancel this edit and use the link at the top of the table.<br />
<br />
-------------------------------------------------------------------------------------<br />
<br />
-- Editors: To add yourself to this Area Manager table, copy and paste the following<br />
<br />
-- template into the space below with the other {{AM/Editor|...}} templates. Add<br />
-- yourself into rank order (higher at top)then alphabetical order by user name (A-Z)<br />
-------------------------------------------------------------------------------------<br />
{{AM/Editor|YOUR_USER_NAME|YOUR_RANK#|YOUR_AREA|ANY_COMMENT}}<br />
-------------------------------------------------------------------------------------<br />
-- then in the Summary field enter "Added YOUR_USER_NAME" and press "Save page"<br />
-------------------------------------------------------------------------------------<br />
------------------- DO NOT MODIFY CONTENT ABOVE THE EQUAL SIGN ----------------------<br />
================================================================================-->|-<br />
{{AM/Editor|mishterhaz|3|New Castle County|Also AM in North Eastern MD and Northern NJ}}<br />
{{AM/Editor|TR-11|4|Delaware LAM|Contributor to Lancaster County, PA and Eastern Shore, MD}}<br />
<br />
<br />
<!--+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br />
------------------- DO NOT MODIFY CONTENT BELOW THE PLUS SIGN -----------------------<br />
-------------------------------------------------------------------------------------<br />
-------------------------------------------------------------------------------------<br />
--></includeonly></div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=173756User:Phuz2021-02-04T17:00:44Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
*'''Manager'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaid'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
*'''Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
**DelDot Data Feed Bot (July 2020)<br />
**WME DOT Cameras [SCRIPT] (July 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
**WME DOT Advisories [SCRIPT] (October 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
*'''Mentoring'''<br />
**Mentored by G_W1Z (R1 through R3)<br />
**Mentored by voludu2<br />
*'''Beta Programs'''<br />
**WME<br />
**iOS<br />
*'''Waze Cafe'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)</div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Pennsylvania/AM/Editor/Area&diff=173678Pennsylvania/AM/Editor/Area2021-01-21T18:17:38Z<p>Phuz: */Area manager table update*/</p>
<hr />
<div><!---------------------- DO NOT MODIFY THIS TOP CODE ------------------------------<br />
------------------------ SCROLL DOWN FOR INSTRUCTIONS -----------------------------<br />
-----------------------------------------------------------------------------------><noinclude><!--Keep hard coded due to unique page address--><div class="center"><span class="noprint plainlinks purgelink" style="{{Road/style}}background-color:#93c4d3">[{{FULLURL:{{#titleparts:{{PAGENAME}}|-3}}|action=purge}}#Area_Managers <span title="Return to the Area Manager table">&nbsp;Press here to return to the Area Managers table to see your changes&nbsp;</span>]</span></div></noinclude><includeonly><!--<br />
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ------------------------------------- INSTRUCTIONS - START READING HERE ------------------------------------- --------------------<br />
-------------------------------------------------------------------------------------<br />
-- Country/State Managers: Cancel this edit and use the link at the top of the table.<br />
<br />
-------------------------------------------------------------------------------------<br />
<br />
-- Editors: To add yourself to this Area Manager table, copy and paste the following<br />
<br />
-- template into the space below with the other {{AM/Editor|...}} templates. Add<br />
-- yourself into rank order (higher at top)then alphabetical order by user name (A-Z)<br />
-------------------------------------------------------------------------------------<br />
{{AM/Editor|YOUR_USER_NAME|YOUR_RANK#|YOUR_AREA|ANY_COMMENT}}<br />
-------------------------------------------------------------------------------------<br />
-- then in the Summary field enter "Added YOUR_USER_NAME" and press "Save page"<br />
-------------------------------------------------------------------------------------<br />
------------------- DO NOT MODIFY CONTENT ABOVE THE EQUAL SIGN ----------------------<br />
================================================================================-->|-<br />
{{AM/Editor|dhschneider|5|Area Manager|gho=dhschneider|Eastern Pennsylvania|badge1=am|badge2=mr}}<br />
{{AM/Editor|Jdelosa|5|NOR Multi-State Manager, NYC Closure Team|badge1=SM|badge2=mr|badge3=m|badge4=LAM|gho=John ( JD )|pic=File:Avatar jdelosa.jpg}}<br />
{{AM/Editor|Happy_Lyn|5|Area Manager in Cameron, Elk, McKean, and Potter counties|badge1=SM|badge2=mr|badge3=m|gho=Lyn|pic=File:Avatar HappyLyn.png|SM in Michigan, LAM in West Virginia}}<br />
{{AM/Editor|no1uknow|5|All of Pennsylvania||badge1=SM|badge2=M|gho=Aaron}}<br />
{{AM/Editor|G_W1Z|4|Large Area Manager (LAM)|gho=Vince|All of Pennsylvania, AM in Maine|badge1=am|badge2=mr}}<br />
{{AM/Editor|phuz|4|Southeast PA, DE SM||gho=Matt|badge1=sm|badge2=am|badge3=mr}}<br />
{{AM/Editor|Drummin4JC|3|Area Manager (AM) Fayette County|Resident of state, Most active in SW PA|gho=Adam|badge1=am}}<br />
{{AM/Editor|HillsSnackBar|3|Large Area Manager (LAM)|gho=Zach|pic=File:ordoincfrylock.jpg|Editor in Southwestern PA, Resident of PA, Formerly TheRealOrdizzle|badge1=am}}<br />
{{AM/Editor|Hobbz1701|3|Lackawanna, Luzerne, Lehigh|gho=Ron|Resident of PA|badge1=am}}<br />
{{AM/Editor|JDTech4U|3|Western PA|badge1=am|badge2=mr|gho=Ike|}}<br />
{{AM/Editor|RRM47|3|Philadelphia area, primarily Chester County|gho=RRM47|Resident of PA|badge1=am}}<br />
{{AM/Editor|smitty15|3|Central Pa, Montour & Columbia counties|gho=Todd Smith|badge1=am}}<br />
{{AM/Editor|tckma|3|Southern portions of Adams and York Counties|Resident of MD near PA line. I currently work in King of Prussia (long story) so also edit in Montgomery and Chester counties.|gho=Tom}}<br />
{{AM/Editor|tp8106|3|Central PA||gho=Nate|badge1=am}}<br />
{{AM/Editor|XC_Runner18|3|Delaware, Montgomery PA, Pittsburg Area|gho=Noah}}<br />
<br />
<!--+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br />
------------------- DO NOT MODIFY CONTENT BELOW THE PLUS SIGN -----------------------<br />
-------------------------------------------------------------------------------------<br />
-------------------------------------------------------------------------------------<br />
--></includeonly></div>Phuzhttps://www.waze.com/wiki/USA/index.php?title=Delaware/Area_Managers/Main&diff=173670Delaware/Area Managers/Main2021-01-18T19:44:06Z<p>Phuz: */Area manager table update*/</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.<br />
---- 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|gho=yes|badge1=x|badge2=x|badge3=x}}<br />
---- If any fields are skipped, ensure the first three pipe "|" characters are<br />
---- present. Note the badge1, badge2, badge3 entries are optional, and the "x"<br />
---- is replaced only by 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: "Template:AM/Badge"<br />
<br />
----<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|orbitc|6|Entire State of DE, also NY, NJ, PA. CT, ME, MA, NH, RI, VT|Region 9 Northeast & 8 New England|gho=Orbit C|pic=File:Avatar OrbitC.jpg|badge1=RC|badge2=mr|badge3=GC|badge4=MGC}}<br />
<!-- {{AM/Editor|voludu2|5|Entire State of DE|PA State Manager|gho=voludu2|pic=File:Avatar voludu2.jpeg|badge1=AM|badge2=SM|badge3=CM}} --><br />
{{AM/State}}<!-- Defines the start of the state manager section --><br />
{{AM/Editor|Poncewattle|5|Statewide|State Manager|gho=Nigel|pic=File:Avatar Poncewattle.jpg|badge1=SM|badge2=M}}<br />
{{AM/Editor|phuz|4|Statewide|State Manager|gho=phuz|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>Phuzhttps://www.waze.com/wiki/USA/index.php?title=User:Phuz&diff=173669User:Phuz2021-01-18T19:13:48Z<p>Phuz: </p>
<hr />
<div>*'''Ranks'''<br />
**R1 (November 2014)<br />
**R2 (September 2018)<br />
**R3 (December 2018)<br />
**R4 (February 2020)<br />
*'''Manager'''<br />
**'''State Manager'''<br />
***Delaware (January 2021)<br />
****<br />
**'''Area Manager'''<br />
***Pennsylvania <br />
****(Berks/Lancaster area) (February 2019)<br />
****District 8 Expansion (August 2019)<br />
****District 6 Expansion (November 2019)<br />
***North Carolina<br />
****Outer Banks (May 2019)<br />
***Delaware<br />
****Lower Half (March 2020)<br />
****Full State (June 2020)<br />
*'''MapRaid / Project'''<br />
**Pakistan Raid (March/April 2019)<br />
**NYC UR Project (June 2019)<br />
**Plains KS-MO Raid (August, 2019)<br />
**AL/FL Raid (October/November, 2019)<br />
**NY Lightning Raid (April 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**ME Raid (May/June 2020)<br />
***Provided Initial Google Map Pins for Issues<br />
**Falcon Raid (Fall 2020)<br />
*'''Projects'''<br />
**PA CDP Project (November 2019 - Current)<br />
**DelDot Data Feed Bot (July 2020)<br />
**WME DOT Cameras [SCRIPT] (July 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=304760<br />
**WME DOT Advisories [SCRIPT] (October 2020)<br />
***https://www.waze.com/forum/viewtopic.php?f=819&t=308141<br />
*'''Mentoring'''<br />
**Mentored by G_W1Z (R1 through R3)<br />
**Mentored by voludu2<br />
*'''Beta Programs'''<br />
**WME<br />
**iOS<br />
*'''Waze Cafe'''<br />
**West Chester, PA (March 2019) (organizer)<br />
**Harrisburg, PA (May 2019) (organizer)<br />
**Royersford, PA (March 2020) (organizer)</div>Phuz