palmerit wrote:It'd also be cool if we could come up with "regional best practices" like freeway/major/minor/primary conventions. It looks like the country as a whole is going to have a hard time picking something that satisfies everyone
I certainly don't want to snow on anyone's effort to advance the cause, but I've been at this since Sep '09 (lifer alert!), been fairly involved in the forums, attended the Palo Alto Meetup...and am convinced a single standard is unobtainable at a national level, and unlikely at a regional level. Why? Here's a few examples:
1. New AMs request unlocks and those that can unlock it, do, leaving the new AM to do what they want without having read the wikis. It's even more disconcerting when the road is in your local area (where you live) and it's an AM from outside your area. As a level 4 I can assure you that if you edit in another AM's assigned area, even if you were editing there before they could even spell "Waze," they can get persnickety. There's no pride of ownership allowed in this editing system, but we all have it to varying degrees.
2. It is possible to edit maps within a mile of anywhere you drive, so an unregistered user can edit and most certainly have not read the wikis.
3. The wikis aren't written by Waze, but by motivated users such as ourselves. As such, they cannot be seen as rules, but as guidelines or "best practices." The result is you will always be trying to convince people to follow the guidelines or "best practices," but ultimately they are not required and cannot be forced to do so.
4. Agreement at the Meetup to use hyphens in road names (e.g., US-52 vs. US Hwy 52) morphed afterwards to, "We'll do it when Waze fixes it so the new syntax doesn't break the shields."
5. Agreement at the Meetup to use slashes to separate concurrent road names instead of the TTS understandable comma (e.g., US-52 / US-102 vs. US-52, US-102) based on Waze stating they'll change TTS behavior to pause on a slash the same way it does on a comma, morphed afterwards to, "We'll use slashes even if it does break TTS understandability." (Yes, Sketch, I know how much you like, nay, LOVE commas! )
Note that 4 and 5 are both predicated on things that have not been implemented by Waze and it is uncertain when they will get to it. I'm onboard with the US-xx and comma format now. I'll be onboard with the slashes when Waze implements the TTS delay. (NOTE: TTS comes from a 3rd party, so Waze has to submit the change request to them.)
I've have come to accept that this is just the way things are. All said, I am no longer certain a national, one-size-fits-all standard is even desirable, let alone obtainable. There's too many variations at the state level.
The good news is that we are not that awfully far from a standard; there's just a few devilish details around which there are infinite and intense circular discussions. I could accept the slash format to separate concurrent road names now, before Waze actually implements it at some unknown future date, but cannot bring myself to accept the "Hwy" format.