I’m requesting assistance adding a truck restriction on George Street in Middletown, CT, for the entire length of the street between Washington Street and Middlefield Street. ID: 8933456, 85917544, 533353868, 533353869
George St is a narrow residential road with posted “No Truck Thru” signage. The roadway has no centerline or edge markings, and is not designed to function as a cut-through between Washington Street and Middlefield St.
I’m unable to add truck restrictions myself due to editor permissions.
If someone could apply Truck prohibited (both directions) to all George St segments, that would be greatly appreciated. I can provide photos of the signage if helpful.
Thanks for the clarification. I appreciate the response.
Understood that Waze does not support vehicle specific restrictions for trucks on public roads. Given that, I wanted to ask if there is anything else within Waze guidelines that can help discourage rush hour cut through traffic on George Street.
The road is very narrow, has no centerline or edge markings, and in practice often functions as single lane due to on street parking. During peak hours, opposing traffic frequently has to stop and yield, which leads to backups and conflicts.
I am not looking to restrict legal access. I am just wondering if there are any editor supported adjustments such as road classification, geometry, or turn handling that better reflect the street’s residential character so it is not favored as a through route.
Happy to defer to best practices here. Thanks again for taking a look.
Out of curiosity I took a look, and there do not appear to be any mapping mitigations that would be appropriate here. The road is already classified as Street, which is the lowest type that wouldn’t have adverse impacts to local traffic on adjacent streets (e.g. mapping George St as a Private Road would be effectively restricting routes to residents on the street only). Inspecting the traffic speeds, it appears Waze already treats it as routing slower than the posted speed limit, 22 MPH on average instead of 25. Depending on start and stop point, Waze does not seem to be favoring George St over Boston Rd or Middlefield St or Peters Ln which are all faster. George St only comes up when it’s roughly along a straight line between the start and stop points (e.g. Ross Rd to Camp St) and therefore the most direct route. On the backend, Waze doesn’t care about geometry (road width, sharp curves, terrain) when building routes, just the time to transit from one segment to the next.
So from a mapping perspective there is nothing the editing community can do. Waze leadership has repeatedly stated they never intend to support Trucks as a vehicle type or provide routes that are aware of height, weight, or width restrictions or truck prohibitions like this street has.
If traffic delays worsen on the street, like more frequent stopping and yielding to let vehicles pass a tight spot, Waze will learn those patterns and slower speeds and adjust routes if advantageous. As a user, if you feel the road is uncharacteristically unsafe or slow compared to alternates, you of course are welcome to deviate from Waze’s recommended routes and it will learn your preferred routes and be more likely to offer an alternate. Otherwise, it’s going to be up to the local town to make a change to either make George St slower (or local traffic only or more enforcement) or make adjacent streets faster to make a noticeable change in routing behavior.