gettingthere wrote:CBenson wrote:Does anyone see any particular obstacles to implementing time based road directionality?
* Getting the data correct in Waze
* The data changing with updated signs being posted
Lets say there is a major commuter artery for a city that changes direction completely during the rush hours and has for years. Getting the data correct would be easy. Set the speed data to zero for a few dozen segments max during the times the road is closed in a particular direction. In this case wouldn't it be worth it for waze to go in and tweak the data to make the routing work.
gettingthere wrote:* Day of the week differences (eg. no left turn Monday - Friday 9am - 11am)
Right, but the speed data now includes day of the week differences (at least Monday-Friday vs. Saturday-Sunday, which is all that is required.)
gettingthere wrote:* Building the interface to allow data entry based on clicking an arrow in the editor, currently there is not extra data for a turn, only allowed or denied
That's exactly why I bring this up. I'm not talking about putting in any data regarding a turn. Rather simply set the existing speed data to zero (as drivers can't add speed data during these times in these directions, the existing data may well simply be the default values, why not just change them to zero).
gettingthere wrote:* Adding the extra data to the database - it's my understanding that all database changes are 'frozen' until at least July 2012 for Waze to complete infrastructure changes.
Again, there is no need for extra data, just change some existing data to zeros.
gettingthere wrote:* etc, etc.
I'm thinking that where a reversing road really messes up a city's routing in waze it would be worth it for waze to address the road. It doesn't look like it should be difficult at all from where I sit.