waze.com

berestovskyy wrote:

dbraughlr wrote:The error is that the name is invalid and should be updated either because the construction zone has expired or the name needs to be changed to have the "(closed)" suffix.

Please note at the moment the marker is case-sensitive "(Closed)". Let me know if I shall ignore the case.

I'll cast my vote for making it case insensitive. While I will enter it that way, I suspect there are way too many people who won't. No point in flagging something just because the case of the closed text is "wrong."

CBenson wrote:

berestovskyy wrote:- NEW for ALL: 'More than 55 letters Ramp'

bedo2991 wrote:Edit: another thing that might be useful worldwide could be a warn: "Ramp streetname is too long". (Maybe 65 chars, not to bee too restrictive). We have some editors that take all the possible destination shown in the road signs and put them all in the ramp streetnames...

Hmm, that's exactly what I do - put all the possible destinations shown on the road sign in ramp streetnames. If the check is useful to others that's fine. But I'm not limiting my ramp names to 65 characters.

[ img ]

sketch wrote:Regarding "(Closed)" / "(Construction Zone)" / "CONST ZN":

The "CONST ZN" suffix was a relic from a time before text-to-speech. It's pronounced "Const Zee Enn", which makes no sense. Adding the parentheses adds a pause, and now it says what it means, and it's easier to read, too. Also, when applied to closed roads, "CONST ZN" isn't really descriptive. I wouldn't expect the standard to change again unless Waze gives us a construction zone flag with a little digging man icon. One change to the Wiki in 3-4 years isn't too bad

Ok, thanks. At least that makes the rather sudden change make more sense.

As such, the Validator should show results for anything containing "Construction Zone", "Closed", or "CONST ZN". The first two as a reminder, and the last so it can be changed.

You're talking about flagging the first two without parentheses, correct?

cactusmonkey1966 wrote:I'm thinking I need to delete WME Validator and reinstall it. But my Chrome doesn't seem to give me that option. Any insight into getting this installed properly now that I messed up and played around without knowing what I'm doing?

First, congratulations (or condolences, as appropriate ) on the new AM status.

Exactly what steps are you taking to try to remove the Validator extension from Chrome?

pjlasl wrote:I noticed that street names that begin with numbers (i.e. 8th Steet) are being flagged with the following message: #170 The street name starts with a lowercase word.

Yup, this morning I found a whole bunch of stuff suddenly highlighed by the validator complaining about lowercase street names, and they were all streets such as "W 2nd St" and so on. Needs to be fixed.

I would also exclude the word "to" from the lower case filter selection as shown here

I thought that "to" already was exempted previously, since that's used as part of an onramp name and it's almost always been lowercase. Definitely agree that if the Validator has started flagging those, that's something else that needs to be fixed.

Edit: Yup, I can confirm that it's flagging "to" as longercase name on ramps. It seems to happen to ramp segments that aren't directly connected to a freeway. Here is an example. It needs to not flag "to" on a ramp name, regardless of what it's connected to.

berestovskyy wrote:PS. I hope I'll get #170 fixed soon, sorry

Ok, I guess you know about and are working on all that stuff then.

Fredo-p: Actually, all that did was just cause you to load the newer version, which he seems to have just put out. You can achieve the same effect by going to the extensions settings within Chrome and clicking on the "Update extensions now" button.

berestovskyy, thanks for the fast fix!

berestovskyy wrote:Filter by username is available only for Country Managers and only in that countries. Due to privacy concerns, there are no plans to change this nor implement any editor identification for custom checks.

With all due respect: What "privacy concerns???"

1. Most, if not the vast majority/all people editing (or even just logging into the Waze app) are using a pseudonym of some type, not their real name.
2. All you have to do is click on a given road segment and you can see who last edited it, so nothing is being hidden for "privacy concerns" there.
3. All such a filter does is help someone to see who's been editing a given set of roads, NOT where they live. Maybe they edit near where they live, but nothing in such a filtering specifically reveals that location.

So I fail to see how this type of filtering would be a privacy concern issue.

The lack of such a filtering feature isn't an issue for me (and there's another script I use which happily lets me filter based on editor name, so if I wanted to check who's been doing what in the area I manage, I can do so - I mention this just so you realize I have no vested interest in such a feature in the Validator), but I do have a hard time considering a filter that helps you to see who edited what as being any kind of valid privacy concern.

berestovskyy wrote:

SuperDave1426 wrote:So I fail to see how this type of filtering would be a privacy concern issue.

Maybe I used the wrong term, but I would not like to see editors to lynch other editors using Validator.

Fair enough, I suppose (though I'm kind-of at a loss regarding editors "lynching" other editors). Although to me it seems like there's more value in being able to easily spot of someone is putting in bad edits - since the sooner those can be caught and corrected, the better for the map (and its users) overall...

bgodette wrote:

SuperDave1426 wrote:All such a filter does is help someone to see who's been editing a given set of roads, NOT where they live.

Um actually about that... While there usually isn't enough information available directly in WME to determine where someone lives, it does provide a really large side-channel.

A large side-channel that still doesn't provide any specific information regarding exactly where someone lives.

Figure out where I live (more specifically than just what city) based on my edits and I'll send you a box of cookies.

bgodette wrote:Half a residential block close enough? Because that's how close info in WME can usually get you.

It's been a known issue for four years and unofficially discussed at each NA meet. It's not really something that can be solved either without hamstringing the community's ability to police the map under the current system of edits with no approval. It's not particularly high-priority issue either since editing is voluntary and a public activity.

I value my privacy (what little of it there is, these days), but half a residential block isn't something that would make me too terribly nervous for someone to figure out (I realize that others might not feel that way).

So, sure, I'll take you up on that. PM me if you think you've got it, with where you think it is. Just be sure that you're sure before you make the call - I'll only give one shot on it and I'm not going to play "if you guess wrong you get another chance." <grin> I'm curious to see if it can really be done just from looking at my map edits; if it works the way you seem to be implying that it does, you should be able to get there without playing "process of elimination" with me.

Oh, and if you do get it: Since the cookies are my treat, they're my choice (unless you truly hate the ones I pick out; I'll inform you ahead of time when I ask for where to ship them to, assuming you hit the mark).

Oh, one last item: Talking to my RC on the subject would be considered cheating and would thus invalidate the bet.

bgodette wrote:

SuperDave1426 wrote:I value my privacy (what little of it there is, these days), but half a residential block isn't something that would make me too terribly nervous for someone to figure out (I realize that others might not feel that way).

So no concerns about someone sitting around to see who gets into a car with a phone mount?

Heck, someone can do that now, completely unrelated to Waze.