User:DCLemur/VA2025 Update

Summary of Changes: Adjusted instructions to reflect natural order of data fields as well as waze vocabulary utilized in WME. Fixed grammatical and style issues.

EXISTING:

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 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.

. . .

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.

. . .

PROPOSED: The primary goal of the Virginia 2025 is to vastly improve a user's drive experience by ensuring that each valid ADDRESS is properly located and searchable within the app. (This effort also improves the connectivity of the Waze map.)

. . .

The objective is to ensure that each road segment is appropriately identified with a street name and city name(s), road type (functional class), direction(s) of travel, turn restrictions, speed limits, house numbers. Note: when a house number doesn't provide proper routing, add a residential place point (RPP), but only if absolutely necessary.

. . .

Mapping will never achieve perfection; on-going growth is the norm throughout much of the Commonwealth of Virginia. Construction of new homes and their roads as well as major highway improvements (including diverging diamond interchanges and additional Express and HOV Lanes) are fairly common occurrences.

. . .