Waze forum

davipt wrote: Setting all roads to two-ways is a no-no according to the waze wiki. If the road is direction unknown or one-way, waze will learn the right way when people drive there. If you manually set the road to two-way, one-way roads will become two-way and people will be directed there against traffic.

Ah.... that old fallacy.

BTW, where in the wiki does it say that?

davipt wrote: What do you mean fallacy? No of course I can't find the exact sentence on the wiki,

Then you shouldn't say the Wiki says so, cause it probably doesn't.

davipt wrote:but isn't it well known that streets do change from unknown to one-way and to two-way, but will never ever be able to learn and switch back from two-way to one-way?

No. I've had a street go from two-way to one-way, simply because I was the only person driving down it, and I always drove in the same direction.

davipt wrote:Also routes will prefer segments manually set to two-way over segments marked as unknown?

Maybe. But if you have local knowledge and know all the streets are two-way, then it's better to set them all to two-way, as that is what they should be. As long as you then take the time to add all the other data - road names, turn restrictions, etc.

doctorkb wrote:Invented is reporting that street names are getting lost.

I am seeing this too, but I am seeing it when I use "select entire street" or ctrl-A. I don't think this has to just do with the WME scripts and landmarks.

I have been renaming a lot of roads for a couple reasons. One is to unsplit US-70 where it should not have been split in the first place. I am renaming via Ctrl-A, US-70 W or US Hwy 70 W to US-70, for instance.

In some cases, even when I am down at the 20m level and Ctrl-A only selects one or a few segments, the name and city information will be wiped out. I only noticed it because such segments now turn red. I also noticed this in another area I had edited a while back, but the changes were off the screen. I went back later and the roads were red and all city and street name information was wiped out.

There definitely is a bug in the machine somewhere regarding this issue. I was trying to reproduce it reliably so I could post about it, but saw this thread and decided to mention it. It seems sporadic, so I have not been able to always reproduce.

after you update the latest version of the tools http://www.waze.com/wiki/index.php/Hous ... or#Toolbar, and will not let me install the addons, the uninstall me ......

orbitc wrote:

walbing wrote:after you update the latest version of the tools http://www.waze.com/wiki/index.php/Hous ... or#Toolbar, and will not let me install the addons, the uninstall me ......

What browser do you use? if you are ferering to wme add on, already been updated and working fine.

and works very well!
tks gilles

in English works, but when I switch to Spanish language no longer works

I do??

Best regards

gdu1971 wrote:Hi all,
I've granted edit/commit access to the google repository for some guys who recently provides me good patches. I hope they will provide you the next release very soon.

Hi all,
thank Gill

There's new version 0.45, changelog:

1) added new beta editor url
2) added link to other maps: Google, Google Beta, Bing, ViaMichelin
3) injectit.user.js now works under Chrome+TamperMonkey & FireFox+GreaseMonkey just click on link, in Chrome with TamperMonkey no more download with drag&drops, autoupdate, manual update of all script with 1 click

v0.45 for Chrome+TamperMonkey & FireFox+GreaseMonkey:
https://wme-addons.googlecode.com/svn/b ... it.user.js

v0.45 for Chrome CRX:
https://wme-addons.googlecode.com/svn/b ... addons.crx

PS:
I use TamperMonkey with all most popular WME extensions