davipt wrote:rottielover wrote:http://www.waze.com/wiki/index.php/Automatic_map_updates_and_the_locking_of_roads
Which advises, in part: "...It will change the directionality of a road, enable turns, and reportedly it will change the geometry or layout of a road.
This can cause map errors, especially in areas where there are few wazers. One wazer who always travels one way down a road may change a correctly recorded two-way road into one-way."
I was once curious about this one so we have setup a certain remote and not used one-way segment as two-way and have, two guys, driven there every day for some weeks to test it. It never changed to one-way. It may apply if the road becomes automatically two-ways because of people driving both ways, and later become one-way if people starts driving only one way, but after setting it manually to two ways it never changed. And obviously it wasn't locked.
Anyway we're not arguing against each other here, if we are all in this thread we all surely know the power of this script and the amazing help it provides, as well as dangerous damages it can potentially do. And I see no issues for a entire small town to be set as two-ways (even all directions), and I have plenty of cases like those, but personally I do prefer people to drive there and have waze automatically learn the directions and the position of the road. Mostly because of lazyness and having other more important fixes to do
Agreed, I don't feel this is an "argument", I enjoy discussion, I try and learn something new everyday!
Example, today I found out what the NbWays column was (btw, Is there more documentation somewhere?)
The other thing to keep in mind as well is that the map needs to function. In a few of these towns I was getting "crazy" routing, because the basemap import was just "all jacked up" (no other term for it)...