Requesting an update for Almer Lane, Chester,Va 23836. Unfortunately, it is a mile long stretch end to end and both need equal a better result in travel time to Meadowville Road.
The two ends could be divided at the intersection Almer LANE and Almer COURT.
Example: lowest addresses are the closest to Meadowville Road, but per the map, travelers are redirected through an entire subdivision to get to the exact point +\- a few feet onto Meadowville Road. The current path causes unnecessary traffic and increases extra time in calculating the best route.
Would be a really slight change on waze mapping to reduce frustration especially when the travel time calculations. Vendors will be very happy!
Thanks for the message. Before anything can be reviewed or changed, we need a bit more precision.
To help the editors understand exactly what you’re seeing, please clarify the following:
Start point and end point. What address entering, and where are you navigating to ?
Observed route vs expected route. What path does Waze currently send you on, and what path do you believe should be used instead?
Direction of travel. Is this happening when traveling toward Meadowville Road, away from it, or both?
Consistency. Does this happen every time, or only intermittently?
Almer Lane is long and routing behavior can change based on where along the road the destination pin actually lands. Without exact coordinates or addresses, it’s not possible to tell whether this is a pin placement issue, a routing preference issue, or a road attribute issue.
Once you provide the specific start and end points and the route comparison, a local editor can evaluate whether a change in Waze is appropriate or if the current routing is working as designed.