heckmandm wrote:These two sources indicate that the best thing would be to update those transit-only sections to the type "Private Road" and disallow all turns onto those roads from other segments. This should keep Waze from routing onto those roads.
I'm aware of that solution, however we have a new BRT line that bypases a significant amount of congested traffic that moves very slowly during rush hour. This BRT line has underpasses (the adjacent traffic does not) and buses travel at 80km/h, rather than the traditional speed of cars that would be moving at 50km/h at the most during rush hour. Due to the vast differences in speed, I feel that making this new BRT transit route has to be disconnected all together to avoid Waze routing traffic down this road. This route is an exception, I have all the other transit routes listed as a private road with all turns disallowed.
My problem is that once the transit buses get back onto the regular roads, the users using Waze will be updating incorrect speed data and messing up the roads. If we had a particular road designated to transit, we could at least eliminate the 'drives' from updating information to waze on road speed, where people had used these roads.