User:Subs5/Virginia 2025 View history

 
(40 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Virginia 2025 goal ==
== Virginia 2025 goal ==


The primary goal of the '''Virginia 2025''' is to vastly improve a user's drive by having the destination's '''ADDRESS''' properly located and searchable within the app.
The primary goal of the '''Virginia 2025''' is to vastly improve a user's drive by having the destination's '''ADDRESS''' properly located and searchable within the app.


=== Goal scope and discussion ===
=== Goal scope and discussion ===
Yes overall this is a large project, but taking small bites (in this case each bite is a permalink at zoom=2) will allow us to complete this grand quest. Virginia 2025 is designed to do this effort in a managable and controlled manner.
Yes, this is a large project, but taking small bites (in this case each bite is a permalink at zoom=2) will allow us to complete this grand quest. Virginia 2025 is designed to do this effort in a managable and controlled manner. Businesses come and go, but until a building is torn down and/or rebuilt the address will generally remain the same; therefore getting all the residential and business addresses properly mapped will have a significant and lasting effect for all current and future Wazers.  
 
Businesses come and go, but until a building is torn down and/or rebuilt the address will generally remain the same; therefore getting all the residential and business addresses properly mapped will have a significant and lasting effect for all current and future Wazers.  


The desire is to get the road segments (base map and urban/suburban) to have proper road names, proper city name(s), direction(s) of travel, turn restrictions, house numbers, and speed limits. This effort improves the connectivity of the Waze map while making the destination addresses work properly. Note when a house number doesn't provide proper routing then use a residential place point (RPP), but only if absolutely necessary.
The desire is to get the road segments (base map and urban/suburban) to have proper road names, proper city name(s), direction(s) of travel, turn restrictions, house numbers, and speed limits. This effort improves the connectivity of the Waze map while making the destination addresses work properly. Note when a house number doesn't provide proper routing then use a residential place point (RPP), but only if absolutely necessary.
Line 16: Line 14:
=== Basemap items ===
=== Basemap items ===
#*Please review the [[Basemap|Basemap Wiki]] for steps to, and a guide for, editing basemap/connectivity
#*Please review the [[Basemap|Basemap Wiki]] for steps to, and a guide for, editing basemap/connectivity
#*For R1 and R2 editors who have deletion restrictions, remember that merging two segments together is not considered a deletion. Only merge if the road data will not be corrupted for the remaining segment(s), but if there are many segments that do not belong (powerline right of ways, rivers, etc) then combine them into one segment that can be deleted at the end of your editing day.
#*For R1 and R2 editors who have deletion restrictions, remember that merging two segments together is not considered a deletion. Only merge if the road data will not be corrupted for the remaining segment(s), but if there are many segments that do not belong (powerline right of ways, rivers, etc) then combine them into one segment that can be deleted at the end of your editing session/day.
#*In addition to the steps in the Basemap wiki, please pay special attention to the following:
#*In addition to the steps in the Basemap wiki, please pay special attention to the following:
#**Verify road names and verify/add appropriate street and city alt-names
#**Verify road names and verify/add appropriate street and city alt-names
Line 22: Line 20:
#**Add Speed Limits (SL) - Virginia's default is 25 mph with incorporated city/town/village limits. 55 mph in rural areas. Remember you can also use nearby streets with streetview to get a feel for what the typcial speed is in the area.
#**Add Speed Limits (SL) - Virginia's default is 25 mph with incorporated city/town/village limits. 55 mph in rural areas. Remember you can also use nearby streets with streetview to get a feel for what the typcial speed is in the area.


== Communication ==
== Virginia 2025 spreadsheet ==
''Discord '' is the primary means to communicate. '''You must be in the [[MAR]] Discord server to be able to edit in Virginia 2025.'''
 
But since some don't have 24/7 access to Discord you can edit while not able to be on Discord temporarily. Please be [[Waze Map Editor/Chat#Visible.2FInvisible|set yourself visible]] and enable the [[Map Editor Interface and Controls#Live Users|Live Users]] layer when editing in Virigina. That way people can see you via Live Users and reach out via WME Chat if required; additionally ask to be added to the Virginia Google Hangout channel, if available, since it is synched to Discord.


If you do not understand anything, '''please ask'''ǃ If you need help figuring out where to start, '''please askǃ''' If you think you did something correctly, but aren't sure, '''please askǃ''' Between editors in various time zones and editors that work different shifts, it is likely there be someone online to help at most times that can help.
[[File:Virginia_2025_PL_Map.PNG|300px|right]]The picture to the right is Virginia as made up of permalinks within a spreadsheet. Each editor participating in Virginia 2025 should select one area at a time. Zoom=2 was selected to give a decent amount of area to work but not be so overwhelming that you will never complete the area. Since permalinks are different sizes based on an editor's computer settings. The magnification of the screen plays into account so selecting two adjacent PLs may leave a gap in coverage on your screen while there is overlap on another editors' screen.


When you are editing in the raid area, please [[Waze Map Editor/Chat#Visible.2FInvisible|set yourself visible]] and enable the [[Map Editor Interface and Controls#Live Users|Live Users]] layer.
Note some areas have overlap with neighboring states, some areas have only water, and some areas have very few roads. So like these are like Forrest Gump's box of chocolates, "You never know what you're gonna get" until you jump in and look at it.  


== Editor restrictions ==
=== Selecting an area ===


=== WV Mapraid Segment Update Request ===
* Select '''''ONE''''' area that you want to work on.
Welcome R1 and R2 editors and thanks for your participation in the 2018 WV MapRaid. We know how frustrating it can be to not be able to delete (or do many name changes on) segments that you did not create. We feel your pain and have come up with a handy script so you can mark segments that need to be updated and know that a more senior editor will address those issues.
* Preferentially pick an area that is already within your editing area. (Driving/AM/LAM)
* Copy the permalink and look at it on your computer.
* If you like that area:
** Change the background color to yellow for your chosen area on the first tab "PL Map".
** Change to the spreadsheet's second tab, "Editor Assignment", and overwrite the PL with your editor name.
* Commence editing in the area, if you already have editing rights.
** If all areas in your editing area are done, then you may submit for an Area Manager expansion by using the [https://docs.google.com/forms/d/e/1FAIpQLSd95_HHfhitLmIEBjOgJc1wtb9z1qINrtRTBbYV0jsAo4W9Tg/viewform?c=0&w=1 Area Manager application] to the MAR Regional Coordinator.
** Note the submission for AM will go through the normal AM request process for review and needs to meet the normal AM request requirements.
** The AM will be a permanent AM assignment, it is not a temporary Virginia 2025 area; this is not a map raid for two weeks.


The script can be found at [https://greasyfork.org/en/scripts/39520-wme-form-filler-wvmr WME Form Filler WVMR].
=== Edit the area ===
* Enter/verify correct road names, including proper abbreviations used
* Enter proper city name(s)
** Primary city name is:
*** City/village/town if with incorporated boundary
*** Census Designated Place if matches USPS mailing address city
*** '''None''' if not either of the above options
** Alternate city name is:
*** The USPS city name if different than the primary city listed above
*** A second city name if road segment is on the boder between areas that meet the first two primary cities above
* Edit the segment for correct direction(s) of travel
* Edit the segment for proper turn restrictions, including time based turn restictions
* Edit the segment for proper time based segment restrictions if applicable
* Verify the segment's road type compared to the VDOT functional classification
* Add/edit the segment for house numbers
** Use WME house numbers if at all possible
** Use a residential place point if
*** A WME house number does not provide proper routing to a place that is not on the named road segment
*** Another house exists within Virginia's borders with the same house number, road name, '''AND''' the primary city is ''None''; you will receive an error message that the HN already exisits and you cannot force the Save.


As with most scripts of this type you need to have [https://tampermonkey.net/ Tampermonkey] installed.
=== Finished the area ===
** Change your area's background color to '''GREEN''' for your chosen area on the first tab "PL Map".
** Change to the spreadsheet's second tab, "Editor Assignment"; leave your editor name there and change the background color to '''GREEN'''.
** A good way to see if you have done all of the area is to use JustinS83's [https://greasyfork.org/en/scripts/27035-wme-beenthere| Been There script]. Make a box around the PL at zoom=2 and then zoom into one corner and mark it with a box, survey/scan to make sure all segments are complete. Move to the edge of the smaller box and then mark the new section and survey/scan; repeat as necessary. Once all the larger box is filled in with the smaller boxes. then your area is complete. [[File:Been There Boxes.PNG|300px|center]]
** Had fun and want some more? Then go ahead and grab your next one!


The script will pull much of the necessary information into the WV Mapraid Segment Update Request Form for you, saving you time and (hopefully) getting your requested edits addressed in a timely fashion. You can also ask for help in your group Discord channel or work directly with a higher ranked editor.
== Communication ==
''Discord '' is the primary means to communicate during this effort. '''You must be in the [[MAR]] Discord server to participate in Virginia 2025.'''


While we would like everyone to focus on the primary goal of this MapRaid, we are offering the additional goals that are also very beneficial to the map as a way to give you a break from the editor restrictions.
Therefore, if not already on the MAR Discord server, then please request to join by filling out [https://docs.google.com/forms/d/e/1FAIpQLSc9Z1yeGdfzrzUHHUM05X7kuqxfWipgNmr8WLFfnn2m4QSgkA/viewform '''the MAR Discord request form'''].


=== Segment Update Request Script Usage ===
But since some don't have 24/7 access to Discord you '''CAN''' edit while not able to be on Discord temporarily. Please [[Waze Map Editor/Chat#Visible.2FInvisible|set yourself visible]] and enable the [[Map Editor Interface and Controls#Live Users|Live Users]] layer when editing in Virigina. That way people can see you via Live Users and reach out via WME Chat if required; additionally ask to be added to the Virginia Google Hangout channel, if GHO is available to you, since it is synched to Discord.
* Make sure you have the [https://greasyfork.org/en/scripts/39520-wme-form-filler-wvmr WME Form Filler WVMR] script installed.
* Select a segment or segments that need to be changed by a more senior editor. This should bring up a dialogue in the top of the left panel.
* Click on the "Go to Form" button.
* You'll notice that the top section of the form has been automatically filled in for you.
* Scroll down to and fill in the Type of Update, Source of Update, and Notes Sections
* Click on the "SUBMIT" button to submit your answers
* Move on to the rest of your editing and remember to submit any further Segment Update Requests as you go.


=== R3+ Editors ===
Virginia 2025  is not a map raid; therefore it will not have specific group leaders. Please ask your questions or post up/downlock requests in the Virginia Discord channel/GHO.
We need your help in keeping up to date with the changes that these R1 and R2 editors are making.


Visit the [https://docs.google.com/spreadsheets/d/1yTCbY0sbqPEjJkV42Yqf0cFm1T1HsPcx5Ix6MpBZfn0/edit#gid=1902503822 Segment Update Spreadsheet] and help to make the necessary updates to the map. Please be sure to update the Responder and Status columns appropriately and follow-up if necessary.
If you do not understand anything, please askǃ If you need help figuring out where to start, please askǃ If you think you did something correctly, but aren't sure, please askǃ The MAR community is more than happy to help resolve your question/concern and more than likely there is someone else who is pondering the same item.


== Raid Areas ==
== Editor restrictions ==
 
[[File:WVMR2018 areas.JPG|800px|thumbnail|center]]
 
== Raid Leadership Team ==
{| class="wikitable"
|-
! Username !! Comments
|-
| '''{{Username|Ldriveskier|rank=5}}''' || '''West Virginia SM''', MAR MSM
|-
| '''{{username|roadtechie|rank=6}}''' || '''West Virginia SM''', USA CM, LC, GLR ARC
|-
|{{Username|AnorestesX|rank=3}} ||Michigan AM, West Virginia AM
|-
| {{Username|Happy_Lyn|rank=3}} || Michigan AM, West Virginia AM
|-
| {{Username|JasonN899|rank=4}} || Maryland SM
|-
| {{Username|Kwrigh01|rank=4}} || West Virginia MAR-LAM
|-
| {{Username|LennyNRPD|rank=5}} || Virginia SM, MAR MSM
|-
| {{Username|mtb2314|rank=4}} || Maryland MAR-LAM
|-
| {{Username|subs5|rank=5}} || Virginia SM, USA CM
|}
 
This MapRaid will not have specific group leaders, but we have assigned members of our Raid Leadership Team to each group. These "Leadership contacts" will either be able to answer any questions/concerns about the raid or about West Virginia specific topics or they will bring them back to the Raid Leadership Team and/or WV SMs as appropriate. Many other senior editors may also be able to answer questions.
 
All Raiders are encouraged to work together and help one another. Please feel free to ask questions and/or offer your assistance in your group. The more experienced editors are encouraged to share their knowledge by doing informal mentoring throughout the MapRaid with less experienced editors. The "OK everyone - what's going on with this example?" type of interaction is a wonderful learning benefit of a MapRaid.
 
== Raid Groups ==
 
{| border="1" cellpadding="2"
| colspan="3" style="background-color:#E2EFF3; text-align:center" |{{large|[[https://www.waze.com/editor/?env=usa&lon=-79.96173&lat=39.37150&zoom=0 Group 1 - Morgantown]]}}<br/>Leadership contacts: {{Username|kwrigh01}} - {{Username|subs5}}
|- align="center" style="color:black"
! scope="col" width="250px" bgcolor="#93c4d3"|Username (rank)
! scope="col" width="100px" bgcolor="#93c4d3"|Group
! scope="col" width="125px" bgcolor="#93c4d3"|Comments
{{AM/Editor|stephenr1966|6|1|badge1=lc}}
{{AM/Editor|doryphore_6|5|1|badge1=sm}}
{{AM/Editor|jbayes|5|1|badge1=sm}}
{{AM/Editor|johnsninja58|5|1|badge1=sm}}
{{AM/Editor|Joyriding|5|1|badge1=sm}}
{{AM/Editor|Michelle-s|5|1|badge1=sm}}
{{AM/Editor|Nacron|5|1|badge1=sm}}
{{AM/Editor|RussPA|5|1|badge1=cm}}
{{AM/Editor|subs5|5|1|badge1=cm}}
{{AM/Editor|zohar760|5|1|badge1=sm}}
{{AM/Editor|abc1357|4|1|badge1=am}}
{{AM/Editor|Dangottschalk|4|1|badge1=sm}}
{{AM/Editor|Fish1552|4|1|badge1=am}}
{{AM/Editor|GeekDriverPeaceful|4|1|badge1=am}}
{{AM/Editor|kwrigh01|4|1|badge1=am}}
{{AM/Editor|SpencerFG|4|1|badge1=am}}
{{AM/Editor|steelpanz|4|1|badge1=am}}
{{AM/Editor|ababcock|3|1|badge1=am}}
{{AM/Editor|Bestscoutmom|3|1|badge1=am}}
{{AM/Editor|ehcool68|3|1|badge1=am}}
{{AM/Editor|jalondon628|3|1|badge1=am}}
{{AM/Editor|Kirkyelise|3|1|badge1=am}}
{{AM/Editor|NDFinster|3|1}}
{{AM/Editor|Phlipnull |3|1}}
{{AM/Editor|RodeNinja|3|1|badge1=am}}
{{AM/Editor|taminas|3|1}}
{{AM/Editor|angeloscuro|2|1}}
{{AM/Editor|daveacincy|2|1}}
{{AM/Editor|Hobbz1701|2|1|badge1=am}}
{{AM/Editor|jushag|2|1}}
{{AM/Editor|turbo_jjr|2|1}}
{{AM/Editor|Clayton324|1|1}}
{{AM/Editor|Nazairian|1|1}}
|}


{| border="1" cellpadding="2"
=== R1/R2 editor restrictions ===
| colspan="3" style="background-color:#E2EFF3; text-align:center" |{{large|[[https://www.waze.com/editor/?env=usa&lon=-80.99170&lat=38.93221&zoom=0 Group 2 - Parkersburg]]}}<br/>Leadership contacts: {{Username|roadtechie}} - {{Username|Happy_Lyn}}
Welcome R1 and R2 editors and thanks for your participation in the Virginia 2025. We know how frustrating it can be to not be able to delete (or do many name changes on) segments that you did not create. We feel your pain, but this is a long term project so relax, you can get to it tomorrow. If you absolutely positively need us to address it now, just ask in Discord and we'll be more than happy to help with deletions or renamings.
|- align="center" style="color:black"
! scope="col" width="250px" bgcolor="#93c4d3"|Username (rank)
! scope="col" width="100px" bgcolor="#93c4d3"|Group
! scope="col" width="125px" bgcolor="#93c4d3"|Comments
{{AM/Editor|roadtechie|6|2|badge1=lc}}
{{AM/Editor|dfw_gis|5|2|badge1=sm}}
{{AM/Editor|JB15TM|5|2|badge1=sm}}
{{AM/Editor|Joerodriguez12|5|2|badge1=sm}}
{{AM/Editor|jr1982jr|5|2|badge1=sm}}
{{AM/Editor|N4DOG|5|2|badge1=sm}}
{{AM/Editor|ojlaw|5|2|badge1=sm}}
{{AM/Editor|Bassdan7403|4|2|badge1=am}}
{{AM/Editor|DCLemur|4|2|badge1=am}}
{{AM/Editor|HippocampusLol|4|2|badge1=am}}
{{AM/Editor|j-d-|4|2|badge1=am}}
{{AM/Editor|JasonN899|4|2|badge1=sm}}
{{AM/Editor|juliansean|4|2|badge1=am}}
{{AM/Editor|MrNicGuy|4|2|badge1=sm}}
{{AM/Editor|Rainman3699|4|2|badge1=am}}
{{AM/Editor|toolmanzwief|4|2|badge1=am}}
{{AM/Editor|dodgingcones|3|2}}
{{AM/Editor|DrHenryJonesSr|3|2|badge1=am}}
{{AM/Editor|EmilGz|3|2|badge1=am}}
{{AM/Editor|Happy_Lyn|3|2|badge1=am}}
{{AM/Editor|jalondon628 |3|2|badge1=am}}
{{AM/Editor|mdswbkq|3|2|badge1=am}}
{{AM/Editor|texasthered|3|2|badge1=am}}
{{AM/Editor|ZenBullitt911|3|2}}
{{AM/Editor|Chronos74|2|2}}
{{AM/Editor|mvan231|2|2}}
{{AM/Editor|Mythdraug|2|2}}
{{AM/Editor|nightshadeNOLA|2|2}}
{{AM/Editor|RivrGuy|2|2}}
{{AM/Editor|kidkart72|1|2}}
{{AM/Editor|Mikejwb|1|2}}
|}


{| border="1" cellpadding="2"
'''Complete each segment before moving on'''. When you find a point on the map to do an edit, please take the time to finish all the associated items with that edit before moving on. The basemap wiki is an excellent checklist for editing roads even if you are working on a road that is not basemap.  
| colspan="3" style="background-color:#E2EFF3; text-align:center" |{{large|[[https://www.waze.com/en-US/editor?env=usa&lon=-81.95437&lat=38.20207&zoom=0 Group 3 - Charleston]]}}<br/>Leadership contacts: {{Username|ldriveskier}} - {{Username|AnorestesX}}
|- align="center" style="color:black"
! scope="col" width="250px" bgcolor="#93c4d3"|Username (rank)
! scope="col" width="100px" bgcolor="#93c4d3"|Group
! scope="col" width="125px" bgcolor="#93c4d3"|Comments
{{AM/Editor|ct13|6|3|badge1=lc}}
{{AM/Editor|Jdelosa|5|3|badge1=sm}}
{{AM/Editor|jwe252|5|3|badge1=cm}}
{{AM/Editor|ldriveskier|5|3|badge1=sm}}
{{AM/Editor|Nimbus-|5|3|badge1=sm}}
{{AM/Editor|OldDentsideFordLover|5|3|badge1=sm}}
{{AM/Editor|SanzClew|5|3|badge1=cm}}
{{AM/Editor|uscwaller|5|3|badge1=sm}}
{{AM/Editor|whathappened15|5|3|badge1=sm}}
{{AM/Editor|apeachypanda|4|3|badge1=am}}
{{AM/Editor|BenEnmen|4|3|badge1=am}}
{{AM/Editor|bummerdude69|4|3|badge1=sm}}
{{AM/Editor|doctorblah|4|3|badge1=sm}}
{{AM/Editor|mhh60|4|3|badge1=am}}
{{AM/Editor|SirGadwall|4|3|badge1=am}}
{{AM/Editor|tinfoilhattie|4|3|badge1=sm}}
{{AM/Editor|turbomkt|4|3|badge1=sm}}
{{AM/Editor|airchair|3|3|badge1=am}}
{{AM/Editor|AnorestesX|3|3|badge1=am}}
{{AM/Editor|buckeyemondo|3|3|badge1=am}}
{{AM/Editor|Dino6451|3|3|badge1=am}}
{{AM/Editor|FalloutRanger|3|3|badge1=am}}
{{AM/Editor|Huybee3|3|3|badge1=am}}
{{AM/Editor|Kyhtak|3|3}}
{{AM/Editor|MFCoolCool|3|3|badge1=am}}
{{AM/Editor|Tlknows|3|3}}
{{AM/Editor|fweewayze94|2|3}}
{{AM/Editor|KeepSloanWeird|2|3}}
{{AM/Editor|megg2004|2|3|badge1=am}}
{{AM/Editor|NoahKarateKidLol|2|3}}
{{AM/Editor|UEFL|2|3}}
{{AM/Editor|Cm1o416|1|3}}
{{AM/Editor|kohenkatz|1|3}}
|}
 
{| border="1" cellpadding="2"
| colspan="3" style="background-color:#E2EFF3; text-align:center" |{{large|[[https://www.waze.com/editor?env=usa&lon=-80.96697&lat=37.70396&zoom=0 Group 4 - Beckley]]}}<br/>Leadership contacts: {{Username|LennyNRPD}} - {{Username|mtb2314}}
|- align="center" style="color:black"
! scope="col" width="250px" bgcolor="#93c4d3"|Username (rank)
! scope="col" width="100px" bgcolor="#93c4d3"|Group
! scope="col" width="125px" bgcolor="#93c4d3"|Comments
{{AM/Editor|jemay|6|4|badge1=gc}}
{{AM/Editor|dhschneider|5|4|badge1=am}}
{{AM/Editor|LennyNRPD|5|4|badge1=sm}}
{{AM/Editor|Ocstagetech|5|4|badge1=am}}
{{AM/Editor|red-nax|5|4|badge1=am}}
{{AM/Editor|Rfrsw101|5|4|badge1=sm}}
{{AM/Editor|SkyviewGuru|5|4|badge1=sm}}
{{AM/Editor|Tango259|5|4|badge1=am}}
{{AM/Editor|AugieAStL|4|4|badge1=am}}
{{AM/Editor|dchary2418|4|4|badge1=am}}
{{AM/Editor|drudoyle|4|4|badge1=am}}
{{AM/Editor|Dude495|4|4|badge1=am}}
{{AM/Editor|hiroaki27609|4|4|badge1=am}}
{{AM/Editor|mtb2314|4|4|badge1=am}}
{{AM/Editor|oldbeeg|4|4|badge1=am}}
{{AM/Editor|Rainman3699|4|4|badge1=am}}
{{AM/Editor|RichardPyne|4|4|badge1=am}}
{{AM/Editor|willdanneriv|4|4|badge1=am}}
{{AM/Editor|Beachbumli247|3|4|badge1=am}}
{{AM/Editor|burgher_2|3|4|badge1=am}}
{{AM/Editor|cparishjr|3|4|badge1=am}}
{{AM/Editor|krzycholub|3|4|badge1=am}}
{{AM/Editor|KTCAOP|3|4|badge1=am}}
{{AM/Editor|Larryhayes7|3|4|badge1=am}}
{{AM/Editor|m-103|3|4}}
{{AM/Editor|MacroNav|3|4|badge1=am}}
{{AM/Editor|heartpoam|2|4}}
{{AM/Editor|JakePost|2|4}}
{{AM/Editor|mwfrans|2|4}}
{{AM/Editor|NASASK|2|4}}
{{AM/Editor|utechtl|2|4|badge1=am}}
{{AM/Editor|WayzrBill|2|4}}
{{AM/Editor|StrategicIntervention|1|4}}
|}
 
== Important! ==
'''Focus on the main goals of the MapRaid.''' We realize there are several changes in national guidance that have not yet been instituted across all of West Virginia, however it is more important to get basic routing working at this time. Unless you're also making edits that are part of the goals of this MapRaid, don't edit otherwise routable segments for the sole purpose of bringing them up to current guidance.
 
'''Please do not edit any of the following road segments without first consulting a<nowiki/>'' ''[[West_Virginia/WV_MapRaid_2018#Raid_Leadership_Team|West Virginia SM]]''': Freeways, Ramps
 
'''Please do not mass-edit''' Make edits that will affect large numbers of segments at once with care. Mass editing can lead to errors and loss of data.
 
'''Complete each segment before moving on'''. When you find a point on the map to do an edit, please take the time to finish all the associated items with that edit before moving on. The basemap wiki is an excellent checklist for editing roads even if you are working on a road that is not basemap. Please refer to the guidance in the MapRaid Goals section for more information.
 
'''Anything locked at 5 or 6 (or locked above the minimum lock standards)?''' Please check with a '' ''[[West_Virginia/WV_MapRaid_2018#Raid_Leadership_Team|West Virginia SM]]''' before making changes. Rank 5 and 6 editors - consider keeping highlights active for locks.
 
'''West Virginia uses the concept of True Elevation on segments within the State.''' The use of True Elevation is to better represent segments in relationship with its surroundings/ground level. For more information please review the [[West_Virginia#True_Elevation|WV True Elevation Guidance]] page. Note that we do '''NOT''' use True Elevation on Freeway or Ramp segments.


==Local Guidance==
==Local Guidance==
=== WV Roads/Routes ===
=== VA Roads/Routes ===
Road names in West Virginia follow the nationwide [[Road names/USA|Road Name]] guidance. Pay specific attention to the list of approved [[Abbreviations and acronyms]], and when in doubt: "spell it out". See the [[usa:West_Virginia/Major_roads|West Virginia Wiki for Major Roads]] for WV Specific Naming and Type.
Road names in Virginia use the noun name as the primary segment name with the route number as an alternate.  If addresses are using the route number AND there is signage for the route number but not the noun name then the route number can be the primary name. Follow the nationwide [[Road names/USA|Road Name]] guidance. Pay specific attention to the list of approved [[Abbreviations and acronyms]], and when in doubt: "spell it out". If you have any other questions or concerns please contact a MAR Large Area Manager or a MAR State Manager.
==== Road Naming ====
# The city name for the primary name is either the incorporated city/town/village name, CDP name, or None.
In general, use the data you find first on this list as the primary name and all other names/numbers as alternates. ̈If you get confused digging through all of the different GIS sites, which will probably happen (it has to all of us), please contact a member of the ''' [[West_Virginia/WV_MapRaid_2018#Raid_Leadership_Team|Raid Leadership team]] '''for guidance.
# If the segment falls within an incorporated city/town/village or CDP, then '''all''' alternate segment names should also include the same primary city name for the city/town/village/CDP.   
# Use SV to find [[BGS]]/LGS - if available, this is the primary name.
# If the segment falls outside of a city/town/village/CDP, then the primary city name should be left blank and the "None" check box selected. The segment's primary road name should be duplicated in the alternates and '''all''' alternate names should use the USPS Zip Code City name. Do not check "None" for any of the alternate city names. If there is more than one listed USPS Zip Code City for a given ZIP, use the city name used for that address. Using another "default" name will mean the Waze house number or residential place point is not used.  
# Use WVDOT data to find local name and route numbering (for the MapRaid, you’ll generally need the County Route information, CR-x or CR-x/y, but confirm higher named roads)
# If the segment runs along the border between two cities or CDPs, then the primary city name should be left blank and the "None" check box selected. The primary segment name should be duplicated in the alternates for both city/CDP names as well as the alternate segment names. Do not check "None" for any of the alternate city names.  This guidance should also be applied when the segment falls outside of a city/CDP but borders two USPS Zip Code City.
#* WVDOT GIS:  consider installing the [https://greasyfork.org/en/scripts/27965-wme-wv-gis-map WME WV GIS Map script]. This script adds a "WVGIS" link to the bottom toolbar in WMEClick it to open a GIS map that contains data pulled from most of the relevant state and county (where available) GIS sources.  The link will turn green to indicate the GIS map location is sync'ed to the WME map -- moving the WME map will move the GIS map (but not vice versa).  If the link turns black, e.g. after refreshing WME, the location sync is broken.  Simply click the WVGIS link again to restore the sync.
#* [http://www.transportation.wv.gov/highways/programplanning/gti/GIS/MAPS/Pages/WVMapGISSelect.aspx WVDOT County Maps] (PDF): even if using the WVDOT GIS script, the PDF maps are a good overview of the different routes.
# County GIS maps
#* We highly recommend that you install the [https://greasyfork.org/en/scripts/21228-wme-gis-buttons WME GIS Buttons script]. This script will make it a lot easier to access the multiple County GIS websites.
#* If you do not wish to install these scripts please visit the [https://docs.google.com/spreadsheets/d/1VU8T5szPl6-M4ylwlIhQcmTVxlvs9qrklVvwsuPBzDg/edit#gid=1300549893 West Virginia GIS Links] spreadsheet for all GIS links. '''NOTE''': Not all WV counties have GIS links.
# Parcel/lot information from County GIS sources and/or the [https://greasyfork.org/en/scripts/37072-wme-gis-layers WME GIS Layers] script. Note that the County GIS sources from step #3 are a more complete set of the sources. The WVGIS and GIS Layers scripts contain '''some''' of the County information, but not all of it.  '''Please use caution with the GIS Layers script as information may be inconsistent due to the E911 changes in West Virginia. Use the chart below to help determine the most reliable sources from this script.'''
# USPS Address Search - check addresses and add as an alternate, as appropriate per the [[Road names/USA/City names|City Name]] guidance (which is clarified for West Virginia below).
'''Notes:'''
* If data is only available from a single source, use it.
* If multiple sources conflict with a single source, use the road name confirmed by multiple sources and add the other names as alternates.
* If it isn't possible to be sure about the primary name and there is already a primary name on the segment that matches any of the possibilities, then leave that name as primary and add the others as alternates.
* Always include the name from the BGS/LGS '''and''' the name from parcel data.
* If an address is outside the bounds of a [[Glossary#CDP|CDP]], include the USPS City as an alternate.
* Steps 3 and 4 above may be included in the wme-wv-gis-map script (step 2), depending on the County.
* Use this chart as a reference for which Layers in the GIS Layers script are the most reliable for West Virginiaː
{{#widget:Iframe
|url=https://docs.google.com/spreadsheets/d/e/2PACX-1vR6qwM1xLsXjyzpzDarPGSdWUIc_MlEiGh5XFYrTdk2dE9-4g4Gw4lg57B1IjJShcBIhy2zaOKcHstJ/pubhtml?gid=107135603&amp;single=true&amp;widget=true&amp;headers=false
|width=80%
|height=400
|border=0
}}
 
==== Route Naming ====
West Virginia uses the WV-XXX format for all State Routes. For County Routes, CR-XX or CR-XX/YY is used. There are no Township Roads (TR-XXX) in West Virginia. In a few limited cases, there are special road names in use; if you see one, please do not delete it or ask a question first prior to deleting it. More detail and examples can be found here on the [[West Virginia/Major roads|WV Route Naming]] page.
 
==== City Names ====
This is clarification for City Name guidance done during this MapRaid. Full guidance for West Virginia can be found on the [[West Virginia/Cities and towns|WV Cities and Towns]] page. If you have any other questions or concerns please contact a member of the ''' [[West_Virginia/WV_MapRaid_2018#Raid_Leadership_Team|Raid Leadership team]]'''.  Please ensure that you have the [[West Virginia/WV_MapRaid_2018#Recommended Tools for MR West Virginia|Recommended Tools]] installed as these will help with Identifying City/CDP and USPS Zip Codes.
# The city name for the primary name is either the CDP name, incorporated city name, or None.
# If the segment falls within a City or CDP, then '''all''' alternate segment names should also include the same City/CDP.  '''Do not''' add any USPS Zip Code City as an alternate city name. Example:[[File:PrimaryCDP.JPG|center]]
# If the segment falls outside of a City or CDP, then the primary city name should be left blank and the "None" check box selected. The primary segment name should be duplicated in the alternates and '''all''' alternate names should use the USPS Zip Code City name. Do not check "None" for any of the alternate city names[[File:Friars_hill_2.PNG|center]]If there is more than one listed USPS Zip Code City for a given ZIP, use only the default city name. DO NOT use any of the other city names recognized in the ZIP Code unless there are URs regarding navigation issues to that city name.[[File:USPS_City_Names.JPG|center]]
# If the segment runs along the border between two Cities or CDPs, then the primary city name should be left blank and the "None" check box selected. The primary segment name should be duplicated in the alternates for both CIty/CDP names as well as the alternate segment names. Do not check "None" for any of the alternate city names.  This guidance should also be applied when the segment falls outside of a City/CDP but borders two USPS Zip Code City. Example:'' ''[[File:PrimaryNone.JPG|center]]


==== Alleys ====
==== Alleys ====
Alleys in West Virginia follow the MAR guidance for [[USA/Mid Atlantic#Road Segment Naming|Alleys]]. '''Do NOT use the new road type "Alley" in West Virginia.'''  
Alleys in Virginia follow the MAR guidance for [[USA/Mid Atlantic#Road Segment Naming|Alleys]]. '''Do NOT use the new road type "Narrow Street/Alley" in Virginia.'''


=== Functional Classification ===
=== Functional Classification ===


Information on functional classification in West Virginia can be found [[usa:West_Virginia/Major_roads#Functional_Classification|here]].
Information on functional classification in Virginia can be found [[usa:Virginia/Major_roads#Functional_Classification|here]]. For editors rank 3 and above see the functional classification script in the Virginia Wazeopedia page.
 
=== MAR Minimum Road Lock Standard ===
=== MAR Minimum Road Lock Standard ===
{| class="wikitable" style="text-align:center"
{| class="wikitable" style="text-align:center"
Line 364: Line 150:




Note that these are minimums and, for protection, certain segments may be at higher lock levels. If you find a road locked to a higher level than its minimum, please leave it locked no lower than that level when you have finished editing.
Note that these are minimums and, for protection, certain segments may be at higher lock levels. If you find a road locked to a higher level than its minimum, please ask for clarification.


=== West Virginia Update Request Management ===
=== Virginia Update Request Management ===


This will not be a "''primary focus''" of the raid, but please feel free to work any UR/PUR/MP's in your editable area. Remember to follow the [[usa:West_Virginia#West_Virginia_User_Report_Management|West Virginia Response Timeline]].  
This will not be a "''primary focus''" of the Virginia 2025, but please feel free to work any UR/PUR/MP's in your editable area. If you receive an AM assignment then the UR/PUR/MP's are definitely within that role, so jump in. Remember to follow the [[usa:Virginia_User_Report_Management| Virginia Response Timeline]].


=== Cameras ===
=== Cameras ===
'''Cameras will not be mapped'''
'''Very few cameras will not be mapped'''


[http://www.legis.state.wv.us/WVCODE/ChapterEntire.cfm?chap=17c&art=6&section=7A#06 §17C-6-7a] of the West Virginia Code prohibits use of cameras to detect or prove traffic law violations. Please remove any Red Light or Speed Camera you find mapped in WV.
Most places in Virginia do not allow red light cameras. Special permission has to be obtained to have them. You may see some fake cameras on the map. Cameras that were in place have been left as a visual deterrent; therefore they are marked as fake. Virginia does not allow speed cameras.


=== Place Editing ===
=== Place Editing ===
West Virginia follows the national [[Places]] guidance.
Virginia follows the national [[Places]] guidance.


For specific WV naming standards please review the [[West_Virginia#Naming_Standards|WV Naming Standards]]
For specific VA naming standards please review the [[Virginia#Naming_Standards| VA Naming Standards]]


To prevent loss of data due to automatic acceptance of submissions from "trusted users", all area places and points with complete data should be locked to Level 2 at a minimum.
To prevent loss of data due to automatic acceptance of submissions from "trusted users", all area places and points with complete data should be locked to Level 2 at a minimum.
Line 403: Line 189:
== Reference Links ==
== Reference Links ==


=== West Virginia Wiki Page ===
=== Virginia Wazeopedia Page ===
If you have any questions regarding WV standards during editing and you cannot find the answer on this page, please visit the [[West_Virginia|West Virginia Wiki Page]] and/or the [[USA/Mid Atlantic|MAR Wiki Page]].
If you have any questions regarding VA standards during editing and you cannot find the answer on this page, please visit the [[Virginia|Virginia Wazeopedia Page]] and/or the [[USA/Mid Atlantic|MAR Wiki Page]].
=== New Editors ===
If you are new or relatively new to map editing, please [[West_Virginia/Resources|CLICK HERE]] for some tips to get started; including settings, options, scripts, Wiki References, and instructions on lock requests and how to create a Permalink (PL). You do not need to join the WV Discord channel, you will be given an invitation to MapRaid specific Discord channels.  


=== Recommended Tools for West Virginia MapRaid ===
=== Recommended Tools for Virginia 2025 ===
There are many scripts and extensions that editors use to assist with editing that not only make some jobs easier, but verifies what we do is correct.  The use of these scripts is highly encouraged and those listed below are the ones you should install, at a minimum, to get started.  
There are many scripts and extensions that editors use to assist with editing that not only make some jobs easier, but verifies what we do is correct.  The use of these scripts is highly encouraged and those listed below are the ones you should install, at a minimum, to get started.  


Line 421: Line 205:


You will need to install a browser extension to manage the additional scripts. Some scripts do not work with the current version of GreaseMonkey, so we recommend [[Scripts#General_installation_instructions|installation of TamperMonkey]].
You will need to install a browser extension to manage the additional scripts. Some scripts do not work with the current version of GreaseMonkey, so we recommend [[Scripts#General_installation_instructions|installation of TamperMonkey]].
'''WV specific scripts'''
Install the following scripts that are specific to West Virginia or to this MapRaid.
# [https://greasyfork.org/en/scripts/27965-wme-wv-gis-map WV GIS Map] Opens a WV GIS map in another window, at the same location as the WME map. Keeps the location of the GIS map synced to WME. Note that this script may require the creation of a <u>free</u> account.
# [https://greasyfork.org/en/scripts/25897-wme-wv-mapraid-overlay WV MapRaid Overlay] Provides an indication of which MapRaid area you are editing in.


'''Essential scripts'''
'''Essential scripts'''
Install the following scripts to give you County, City, Town, and Census Designated Place (CDP) outlines that are essential in determining the [[West_Virginia/WV_MapRaid_2018#City Names|City Name]] that is needed for every segment in West Virginia.


# [http://greasyfork.org/en/scripts/25631-wme-us-government-boundaries WME US Government Boundaries] displays USPS Zip Code boundaries and County boundaries.
# [http://greasyfork.org/en/scripts/25631-wme-us-government-boundaries WME US Government Boundaries] displays USPS Zip Code boundaries and County boundaries.
# [https://greasyfork.org/en/scripts/40837-wme-cities-overlay WME Cities Overlay] provides outlines of CDPs in West Virginia.
# [https://greasyfork.org/en/scripts/40837-wme-cities-overlay WME Cities Overlay] provides outlines of CDPs in Virginia.
# [https://greasyfork.org/en/scripts/21228-wme-gis-buttons WME GIS Buttons script] links to the multiple County GIS websites.
# [https://greasyfork.org/en/scripts/21228-wme-gis-buttons WME GIS Buttons script] links to the multiple County GIS websites.
#[https://greasyfork.org/en/scripts/37072-wme-gis-layers WME GIS Layers] adds GIS layers to WME for states and counties that provide a public ESRI/ArcGIS interface. Typically, these layers include tax parcels (often with address labels) and/or address points. '''Please use caution with these layers as information may be inconsistent due to the E911 changes in West Virginia. Use the chart in the [[West_Virginia/WV_MapRaid_2018#Road_Naming|Road Naming]] section to help determine the most reliable sources from this script.'''
#[https://greasyfork.org/en/scripts/369632-wme-gis-layers WME GIS Layers] adds GIS layers to WME for states and counties that provide a public ESRI/ArcGIS interface. Typically, these layers include tax parcels (often with address labels) and/or address points.  
# [https://chrome.google.com/webstore/detail/wme-validator/baojhpeknpmkhplkcnpdcficcaaniaih WME Validator] validates a map area & highlights issues and generates a very detailed report with WOP references and solutions.  
# [https://greasyfork.org/en/scripts/14674-wme-validator-virginia-localization-2 WME Validator Virginia Localization] this is an add-on script to Validator 
 
{{mbox|type=important|text= WME US Government Boundaries layer will display the '''ESTIMATED''' USPS city name for the '''CENTER''' of the displayed screen.  At the boundaries it can be inaccurate.  Some areas shifting a few pixels can change the city name between four different cities (or a few states).  So remember it is a tool and can be checked with individual addresses by checking the zip code for an address.}}


If you prefer, the CDP outlines can be loaded into WME using the [https://greasyfork.org/en/scripts/8129-wme-geometries WME Geometries script], then loading this [https://drive.google.com/open?id=1XG-Pq9P-FEABIp5RJRQ6lHkue7PODFDM tl_2017_54_place.geojson] file. Or, simply view and search the CDPs on a standalone [https://www.google.com/maps/d/u/0/viewer?mid=1FcVWls_1QPKFfNuClKBEW8TEQT0&ll=38.950335619649195%2C-80.17033950000001&z=7 Google Map].  
If you prefer, the CDP outlines can be loaded into WME using the [https://greasyfork.org/en/scripts/8129-wme-geometries WME Geometries script].


'''Other Recommended Scripts'''  
'''Other Recommended Scripts'''  


#[https://greasyfork.org/en/scripts/38921-wme-status-always-visible WME status always visible] will ensure you are visible while working on the MapRaid.
#[https://greasyfork.org/en/scripts/38921-wme-status-always-visible WME status always visible] will ensure you are visible while working on the Virginia 2025 project.
# [https://waze.xpto.org/magic/ Magic] is a tool for highlighting additional errors.
# [https://waze.xpto.org/magic/ Magic] is a tool for highlighting additional errors.
# [http://greasyfork.org/en/scripts/21779-wme-hn-tool-justins83-fork WME HN Tool (JustinS83 fork)] highlights un-nudged house numbers.  
# [http://greasyfork.org/en/scripts/21779-wme-hn-tool-justins83-fork WME HN Tool (JustinS83 fork)] highlights un-nudged house numbers.  
# [https://greasyfork.org/scripts/21378-wme-quick-hn/code/WME%20Quick%20HN.user.js Quick HN] Allows you to set starting HN and then go up by +1 (T), +2 (R), or user selected increment (E)
# [https://greasyfork.org/en/scripts/35547-wme-junction-angle-info WME Junction Angle Info] helps with junction maintenance. If two connected segments are selected, it shows the turn angle, and estimates navigation instructions. Otherwise it shows the the angle between each segment.
# [https://greasyfork.org/en/scripts/35547-wme-junction-angle-info WME Junction Angle Info] helps with junction maintenance. If two connected segments are selected, it shows the turn angle, and estimates navigation instructions. Otherwise it shows the the angle between each segment.
# [http://greasyfork.org/en/scripts/18089-wme-simple-permalink-from-wme-keepmylayers WME Simple Permalink] shortens WME permalinks by removing any layer and filter specifications.
# [http://greasyfork.org/en/scripts/18089-wme-simple-permalink-from-wme-keepmylayers WME Simple Permalink] shortens WME permalinks by removing any layer and filter specifications.
# [http://github.com/WazeUSA/WME-Place-Harmonizer/raw/master/WME-Place-Harmonizer.user.js Place Harmonizer (WMEPH)]. harmonizes, formats and locks a selected place.
# [http://github.com/WazeUSA/WME-Place-Harmonizer/raw/master/WME-Place-Harmonizer.user.js Place Harmonizer (WMEPH)]. harmonizes, formats and locks a selected place.
# [https://greasyfork.org/en/scripts/28097-wme-fs-mvum-gis-map/ WME FS MVUM GIS Map] opens a Forest Service Motor Vehicle Use Map in another window, at the same location as the WME map. Keeps the location of the GIS map synced to WME.
# [https://greasyfork.org/en/scripts/28097-wme-fs-mvum-gis-map/ WME FS MVUM GIS Map] opens a Forest Service Motor Vehicle Use Map in another window, at the same location as the WME map. Keeps the location of the GIS map synced to WME.

Latest revision as of 16:29, 27 February 2019

Virginia 2025 goal

The primary goal of the Virginia 2025 is to vastly improve a user's drive by having the destination's ADDRESS properly located and searchable within the app.

Goal scope and discussion

Yes, this is a large project, but taking small bites (in this case each bite is a permalink at zoom=2) will allow us to complete this grand quest. Virginia 2025 is designed to do this effort in a managable and controlled manner. Businesses come and go, but until a building is torn down and/or rebuilt the address will generally remain the same; therefore getting all the residential and business addresses properly mapped will have a significant and lasting effect for all current and future Wazers.

The desire is to get the road segments (base map and urban/suburban) to have proper road names, proper city name(s), direction(s) of travel, turn restrictions, house numbers, and speed limits. This effort improves the connectivity of the Waze map while making the destination addresses work properly. Note when a house number doesn't provide proper routing then use a residential place point (RPP), but only if absolutely necessary.

Since the Virginia 2025 effort can take a few passes on a road to get it groomed to standards, this is a slow methodical effort and not a fast dash. You will be working on all sorts of regions from major metropolitan areas (Northern Virginia/Richmond/Norfolk/etc) to basemap in the wilds of western Virginia. So there is something for everyone's particular taste.

Mapping will never achieve perfection, since there is always some change going on throughout the Commonwealth of Virginia. Construction of new homes and their roads, improving major highways with diverging diamond interchanges, and even adding Express Lanes or HOV Lanes are fairly common occurances. But the goal is to get as close to a snapshot of perfection as can be achieved. Most areas will stay in that perfection mode for a long long time.

Basemap items

    • Please review the Basemap Wiki for steps to, and a guide for, editing basemap/connectivity
    • For R1 and R2 editors who have deletion restrictions, remember that merging two segments together is not considered a deletion. Only merge if the road data will not be corrupted for the remaining segment(s), but if there are many segments that do not belong (powerline right of ways, rivers, etc) then combine them into one segment that can be deleted at the end of your editing session/day.
    • In addition to the steps in the Basemap wiki, please pay special attention to the following:
      • Verify road names and verify/add appropriate street and city alt-names
      • Look for and correct other state names on segments (MD/WV/KY/TN/NC/DC)
      • Add Speed Limits (SL) - Virginia's default is 25 mph with incorporated city/town/village limits. 55 mph in rural areas. Remember you can also use nearby streets with streetview to get a feel for what the typcial speed is in the area.

Virginia 2025 spreadsheet

The picture to the right is Virginia as made up of permalinks within a spreadsheet. Each editor participating in Virginia 2025 should select one area at a time. Zoom=2 was selected to give a decent amount of area to work but not be so overwhelming that you will never complete the area. Since permalinks are different sizes based on an editor's computer settings. The magnification of the screen plays into account so selecting two adjacent PLs may leave a gap in coverage on your screen while there is overlap on another editors' screen.

Note some areas have overlap with neighboring states, some areas have only water, and some areas have very few roads. So like these are like Forrest Gump's box of chocolates, "You never know what you're gonna get" until you jump in and look at it.

Selecting an area

  • Select ONE area that you want to work on.
  • Preferentially pick an area that is already within your editing area. (Driving/AM/LAM)
  • Copy the permalink and look at it on your computer.
  • If you like that area:
    • Change the background color to yellow for your chosen area on the first tab "PL Map".
    • Change to the spreadsheet's second tab, "Editor Assignment", and overwrite the PL with your editor name.
  • Commence editing in the area, if you already have editing rights.
    • If all areas in your editing area are done, then you may submit for an Area Manager expansion by using the Area Manager application to the MAR Regional Coordinator.
    • Note the submission for AM will go through the normal AM request process for review and needs to meet the normal AM request requirements.
    • The AM will be a permanent AM assignment, it is not a temporary Virginia 2025 area; this is not a map raid for two weeks.

Edit the area

  • Enter/verify correct road names, including proper abbreviations used
  • Enter proper city name(s)
    • Primary city name is:
      • City/village/town if with incorporated boundary
      • Census Designated Place if matches USPS mailing address city
      • None if not either of the above options
    • Alternate city name is:
      • The USPS city name if different than the primary city listed above
      • A second city name if road segment is on the boder between areas that meet the first two primary cities above
  • Edit the segment for correct direction(s) of travel
  • Edit the segment for proper turn restrictions, including time based turn restictions
  • Edit the segment for proper time based segment restrictions if applicable
  • Verify the segment's road type compared to the VDOT functional classification
  • Add/edit the segment for house numbers
    • Use WME house numbers if at all possible
    • Use a residential place point if
      • A WME house number does not provide proper routing to a place that is not on the named road segment
      • Another house exists within Virginia's borders with the same house number, road name, AND the primary city is None; you will receive an error message that the HN already exisits and you cannot force the Save.

Finished the area

    • Change your area's background color to GREEN for your chosen area on the first tab "PL Map".
    • Change to the spreadsheet's second tab, "Editor Assignment"; leave your editor name there and change the background color to GREEN.
    • A good way to see if you have done all of the area is to use JustinS83's Been There script. Make a box around the PL at zoom=2 and then zoom into one corner and mark it with a box, survey/scan to make sure all segments are complete. Move to the edge of the smaller box and then mark the new section and survey/scan; repeat as necessary. Once all the larger box is filled in with the smaller boxes. then your area is complete.
    • Had fun and want some more? Then go ahead and grab your next one!

Communication

Discord is the primary means to communicate during this effort. You must be in the MAR Discord server to participate in Virginia 2025.

Therefore, if not already on the MAR Discord server, then please request to join by filling out the MAR Discord request form.

But since some don't have 24/7 access to Discord you CAN edit while not able to be on Discord temporarily. Please set yourself visible and enable the Live Users layer when editing in Virigina. That way people can see you via Live Users and reach out via WME Chat if required; additionally ask to be added to the Virginia Google Hangout channel, if GHO is available to you, since it is synched to Discord.

Virginia 2025 is not a map raid; therefore it will not have specific group leaders. Please ask your questions or post up/downlock requests in the Virginia Discord channel/GHO.

If you do not understand anything, please askǃ If you need help figuring out where to start, please askǃ If you think you did something correctly, but aren't sure, please askǃ The MAR community is more than happy to help resolve your question/concern and more than likely there is someone else who is pondering the same item.

Editor restrictions

R1/R2 editor restrictions

Welcome R1 and R2 editors and thanks for your participation in the Virginia 2025. We know how frustrating it can be to not be able to delete (or do many name changes on) segments that you did not create. We feel your pain, but this is a long term project so relax, you can get to it tomorrow. If you absolutely positively need us to address it now, just ask in Discord and we'll be more than happy to help with deletions or renamings.

Complete each segment before moving on. When you find a point on the map to do an edit, please take the time to finish all the associated items with that edit before moving on. The basemap wiki is an excellent checklist for editing roads even if you are working on a road that is not basemap.

Local Guidance

VA Roads/Routes

Road names in Virginia use the noun name as the primary segment name with the route number as an alternate. If addresses are using the route number AND there is signage for the route number but not the noun name then the route number can be the primary name. Follow the nationwide Road Name guidance. Pay specific attention to the list of approved Abbreviations and acronyms, and when in doubt: "spell it out". If you have any other questions or concerns please contact a MAR Large Area Manager or a MAR State Manager.

  1. The city name for the primary name is either the incorporated city/town/village name, CDP name, or None.
  2. If the segment falls within an incorporated city/town/village or CDP, then all alternate segment names should also include the same primary city name for the city/town/village/CDP.
  3. If the segment falls outside of a city/town/village/CDP, then the primary city name should be left blank and the "None" check box selected. The segment's primary road name should be duplicated in the alternates and all alternate names should use the USPS Zip Code City name. Do not check "None" for any of the alternate city names. If there is more than one listed USPS Zip Code City for a given ZIP, use the city name used for that address. Using another "default" name will mean the Waze house number or residential place point is not used.
  4. If the segment runs along the border between two cities or CDPs, then the primary city name should be left blank and the "None" check box selected. The primary segment name should be duplicated in the alternates for both city/CDP names as well as the alternate segment names. Do not check "None" for any of the alternate city names. This guidance should also be applied when the segment falls outside of a city/CDP but borders two USPS Zip Code City.

Alleys

Alleys in Virginia follow the MAR guidance for Alleys. Do NOT use the new road type "Narrow Street/Alley" in Virginia.

Functional Classification

Information on functional classification in Virginia can be found here. For editors rank 3 and above see the functional classification script in the Virginia Wazeopedia page.

MAR Minimum Road Lock Standard

Minimum Road Lock Standard
Segment Type Direction Lock
 Freeway  5
 Ramp  4
 Major Highway  4
 Minor Highway  3
 Primary Street  One-way
Two-Way
3
2
 Street  Private Road  One-way
Two-Way
2
1
 |-|-|-|-|-|-|-|-|-| Railroad |-|-|-|-|-|-|-|-|-|  2
 • • • • Ferry • • • •   5
 ⁃     ⁃        ⁃        ⁃        ⁃ Runway ⁃        ⁃        ⁃        ⁃        ⁃  4
Other Named Types 5


Note that these are minimums and, for protection, certain segments may be at higher lock levels. If you find a road locked to a higher level than its minimum, please ask for clarification.

Virginia Update Request Management

This will not be a "primary focus" of the Virginia 2025, but please feel free to work any UR/PUR/MP's in your editable area. If you receive an AM assignment then the UR/PUR/MP's are definitely within that role, so jump in. Remember to follow the Virginia Response Timeline.

Cameras

Very few cameras will not be mapped

Most places in Virginia do not allow red light cameras. Special permission has to be obtained to have them. You may see some fake cameras on the map. Cameras that were in place have been left as a visual deterrent; therefore they are marked as fake. Virginia does not allow speed cameras.

Place Editing

Virginia follows the national Places guidance.

For specific VA naming standards please review the VA Naming Standards

To prevent loss of data due to automatic acceptance of submissions from "trusted users", all area places and points with complete data should be locked to Level 2 at a minimum. Additionally, please consult the following table for minimum lock level for completed places.

Place Type Minimum Lock Level
Area/Point Places 2
Gas Stations 3
Hospital/Medical Care 4
Fire Department 4
Police Station 4
Airports 4
Parking Lot Area (PLA) 3

Reference Links

Virginia Wazeopedia Page

If you have any questions regarding VA standards during editing and you cannot find the answer on this page, please visit the Virginia Wazeopedia Page and/or the MAR Wiki Page.

Recommended Tools for Virginia 2025

There are many scripts and extensions that editors use to assist with editing that not only make some jobs easier, but verifies what we do is correct. The use of these scripts is highly encouraged and those listed below are the ones you should install, at a minimum, to get started.

Toolbox

Once you have installed Toolbox, press the Toolbox Icon and select a minimum of the following options:

TamperMonkey

You will need to install a browser extension to manage the additional scripts. Some scripts do not work with the current version of GreaseMonkey, so we recommend installation of TamperMonkey.

Essential scripts

  1. WME US Government Boundaries displays USPS Zip Code boundaries and County boundaries.
  2. WME Cities Overlay provides outlines of CDPs in Virginia.
  3. WME GIS Buttons script links to the multiple County GIS websites.
  4. WME GIS Layers adds GIS layers to WME for states and counties that provide a public ESRI/ArcGIS interface. Typically, these layers include tax parcels (often with address labels) and/or address points.
  5. WME Validator validates a map area & highlights issues and generates a very detailed report with WOP references and solutions.
  6. WME Validator Virginia Localization this is an add-on script to Validator
WME US Government Boundaries layer will display the ESTIMATED USPS city name for the CENTER of the displayed screen. At the boundaries it can be inaccurate. Some areas shifting a few pixels can change the city name between four different cities (or a few states). So remember it is a tool and can be checked with individual addresses by checking the zip code for an address.

If you prefer, the CDP outlines can be loaded into WME using the WME Geometries script.

Other Recommended Scripts

  1. WME status always visible will ensure you are visible while working on the Virginia 2025 project.
  2. Magic is a tool for highlighting additional errors.
  3. WME HN Tool (JustinS83 fork) highlights un-nudged house numbers.
  4. Quick HN Allows you to set starting HN and then go up by +1 (T), +2 (R), or user selected increment (E)
  5. WME Junction Angle Info helps with junction maintenance. If two connected segments are selected, it shows the turn angle, and estimates navigation instructions. Otherwise it shows the the angle between each segment.
  6. WME Simple Permalink shortens WME permalinks by removing any layer and filter specifications.
  7. Place Harmonizer (WMEPH). harmonizes, formats and locks a selected place.
  8. WME FS MVUM GIS Map opens a Forest Service Motor Vehicle Use Map in another window, at the same location as the WME map. Keeps the location of the GIS map synced to WME.