Welcome to Virginia’s way to systematically make all addresses properly route within the state and help clean up base map along the way. Waze’s current method of only routing to a house number (HN) or residential point place (RPP) if the street name has the matching city as used in the search means that the vast majority of streets need an alternate city name added. Basically we need to have the USPS city name that 99.99999% of users use to match what is in Waze Map Editor. “None” or a weird Census Designated Place names (CDP) don’t cut it for proper navigation.
So how do we eat this elephant? Same as the old saying, one bite at a time. Our “bite” is a permalink at the Zoom=2. Go through and get the proper road names and city names added for primary and alternate names. Add the HNs (preferentially or RPPs if needed). Add the speed limit, etc.
So jump in and help clean up Virginia and make the routing work throughout the Commonwealth!
Here is the Wazeopedia explanation and details of Virginia 2025
We are focusing in on editing areas that you already have, requests for new EAs are treated like any other EA request for time frame from last one and how you have been handling your current EA and editing abilities.
There is a new update to the US Government boundaries that shows the USPS routes so you can figure out what city to use for rural areas. Script is located here.
Since this is a long-term project with road and interchange changes it creates temporary, but long-term issues, it would be nice to be able to indicate these, at least the dangerous ones. This is not unique to Virginia so I imagine it would take quite an effort to tag them all. Nonetheless the dangerous impacts should be highlighted. or the ability to annotate them from the screen other then the “construction” button.
Example announcement and duration: “In January, the three-lane traffic pattern, with a reversible lane, between I-495 and Route 123 shifted from the northbound lanes to the southbound lanes of the parkway. The NPS expects this three-lane traffic pattern to be in effect through late 2025.” (From the National Park Service website: https://www.nps.gov/gwmp/planyourvisit/conditions.htm ).
Example dangerous modification of traffic flow: The merge lane to the GWNP at Rt. 123 has been removed and a stop sign has been added. This creates direct insertion to traffic from a standing stop with no merge. This will be here for some time and is not documented anywhere. The evening rush hour traffic is well, hugely impacted. There are several other major impacts to safety and routing.
I recognize the difficulty of identifying and posting so many programs and projects like this as infrastructure ages and needs repair and replacement. That does not alleviate the need to have the ability to identify such changes.
Note Waze does not post stop signs or stop lights.
The Virginia 2025 project is a different focus.
The personal hazards is a new item that marks dangerous curves and difficult merges and recommend that you read the criteria for them and can post URs where you think they should be added.
There is a lot to get the map up to snuff and the new abilities just add to more work to do. Please feel free to join the volunteer editors. Recommend joining MidAtlantic Discord server to interact and to get unlocks if needed.