I don’t think we need to worry too much about how the US Postal Service does things, we have enough to worry about with what we need to do for Australia. It’s just going to complicate things.
Well I know that the following are valid names, especially in new subdivisions that are being built lately.
Can you show us an example of one of the above abbreviations shown on a street sign (street view/ screen shot)
I suspect they use the full word?
Thanks
Its one thing I have never liked about Waze, there is never one correct answer.
US postal service as an example
How flexible are we with the list provided to Waze?
Can we provide a cut-down list of known in-use abbreviations that can then be appended to as developers try to get fancy in the future?
Not sure whether this is the correct thread for this issue but I have noticed that the Waze TTS cannot handle some of our Australian road abbreviations, eg. Cl (see-ell) and Tce (tee-see).
Yes, and Cr for Crescent doesn’t work on the TTS either. (Cres works).
Elsewhere it is mentioned that the list would be provided to Waze so that the TTS could be updated, but as the discussion about the list seems to be continuing, I assume that hasn’t happened.
IMHO I don’t think the wiki should have been updated until the list was finalised and the TTS changes implemented.
In the meantime, that is until the TTS works with this list, I think we should only use the abbreviations that are known to work with the TTS.
Word!
Also it is not helpful to have different threads on the same subject. Also, for reasons of coordination, it is strongly recomended in general to check intended changes of the Wiki with the Australia Country Admin Team prior to perform changes.
A UR that came up recently was to do with “Mount St”. Although “St” is usually pronounced “Street”, in this instance, TTS came up with “Mount Saint”. It seems that the “Mount” overrode the “St” in determining the type of landmark.
Yes, there is something odd going on with St. Every street I drive works fine except one which is read as Martin Saint. I tried deleting the name and then putting it back
I’ve been working on this with wazeHQ for some weeks now.
Australia can now submit any abbreviation they like via a simple google sheet (same as NZ)
Do to circumstances I’ve handed this project over to ps_au
In this sheet I’ve loaded all the abbreviations in the current Australian wiki and all that is required to push the green button. The powers that be may choose a different route?
Needless to say it is now a simple process to select whatever is required.
This most likely will be my last Waze project in Australia, good luck guys.
Thanks Ispyisail,
Can anyone advise how the transition from the current set of abbreviations to the new set will work. Assuming we are changing Cres to Cr for example, will all the Cres suddenly stop working until we can update them on the map? Or can we specify that both the old and new should work as valid abbreviations? We could then not show the old one in the wiki so that overtime we get to a point that 99% have been updated in the map to accord with the new abbreviation but those 1% we haven’t got to still work…
In summary, is there a transition plan? If so what is it?
Here you are:
FYI: as per info from Waze HQ currently just the following abbreviations are live
We will have some consultations among the CM and RM (as it should be done, when working as a team), go over the pros and cons of the various ways to go ahead and come up with a way to deal with it.
Will have a word with Waze Localisations on that, for
We’ll be back on you when there are news to tell (T.G.I.F. and Waze HQ is in weekend, so ot will take time to get a reply)
FYI: I’ve locked the parallel topics now to keep information consistant.
I’m a bit confused by this. Do you mean that there are now only 6 supported abbreviations & we should disregard all abbreviations here:
https://wiki.waze.com/wiki/Abbreviations_and_acronyms_(Australia)
?
No, absolutely not.
i.e. St and Rd and such are out of the question necessities.
Wiki change has been made in good intentions but without consent, so expect changes.
Still the one and simple rule stands: follow the Wiki. In fact, there is little to do else, we need to work along reference.
But this makes it crystal clear, it cannot be that such reference is changed by just anyone.
You either need consent or the proper position within the Waze (community) structure. To have one guy having the final word Waze installed the community leader (ps_au in Oz), his Waze counterpart is the Community manager (currently Unholy). Also there are the Global Champs who are trusted by Waze with some amount of confidential information, and sometimes specific missions (like my being here with you in general). Waze and it’s community is an enormous big team, so all in all it’s about teamplay…
We have had a abbreviation sheet in NZ for many weeks (maybe months now) and for what ever reason many abbreviations not on this list still worked.
I tried to get any answer about this from wazeHQ but I didn’t really get an answer (I don’t think they knew)
Possible answers?
As you can see the Oz list (google sheet) has only 6 abbreviations listed but we know many others not listed still work for example “Rd”
I know its none of my business any more but I was always keen on pure AS/NZS_4819:2011
https://wiki.waze.com/wiki/Abbreviations_and_acronyms_(AS/NZS_4819:2011)
Unfortunately the list is quite short (I haven’t left any out, honest)
WazeHQ purchased the AS/NZS_4819:2011 document for NZ.
If you want to know how your local area lines up with the current wiki (official or unofficial?)
https://wiki.waze.com/wiki/Abbreviations_and_acronyms_(Australia)
21/11/2015
use validator and add this custom search
${typeRank}:${street}/(10|11):(?!The |.*(St|Pky?|Bl?vd|Dr|Pl|Rd|Pde|Tce|Ln|Ave) (North|South|East|West)$|.* Service(Road|Lane)$|.*(Accs|Ally|Alwy|Ambl|App|Arc|Art|Av|Basn|Bch|Blk|Blf|Bwlk|Bvd|Brce|Br|Brk|Bdge|Bdwy|Bypa|Bywy|Cyn|Caus|Ctr|Cnwy|Ch|Cir|Clt|Cct|Crcs|Cl|Clde|Cmmn|Con|Cps|Cnr|Cso|Crse|Ct|Ctyd|Crk|Cr|Crst|Crsg|Crd|Cowy|Cuwy|Cds|Cttg|Devn|Dstr|Dv|Dr|Drwy|Ent|Esp|Est|Exp|Extn|Fawy|Ftrk|Ftrl|Folw|Ftwy|Fshr|Form|Fwy|Frnt|Frtg|Gdn|Gdns|Gte|Gtes|Gld|Gra|Grn|Grnd|Gr|Gly|Hts|Hrd|Hwy|Intg|Intn|Jnc|Ldg|Lane|Lnwy|Lt|Lkt|Loop|Lwr|Mall|Mdw|Mndr|Mews|Mwy|Mt|Mtn|Otlk|Opas|Pde|Park|Pkld|Pwy|Psge|Path|Piaz|Pl|Pln|Plat|Plza|Pnt|Prom|Qy|Qys|Rmbl|Ramp|Rnge|Rch|Res|Rtt|Rdge|Rgwy|Rowy|Rise|Rvr|Rvwy|Rvra|Rd|Rnde|Rnd|Rte|Swy|Sdng|Slpe|Snd|Sq|Strs|Sta|SH|Stps|Stra|St|Sbwy|Smt|Tce|Thor|Thwy|Tlwy|Twrs|Trk|Trfy|Trl|Trlr|Tri|Tkwy|Tunl|Tpk|Upas|Upr|Vly|Vdct|View|Vll|Vlg|Vlls|Vsta|Walk|Wkwy|Wtr|Way|Whrf)$|^$|$)/Then scan your area
So what is the plan of action, and what can we do to help progress it? Some of us were trying to build a list that reflected AU requirements and a reasonable interpretation of what should/shouldn’t be considered authoritative (as there is no single clear correct answer), and that could be provided to WazeHQ to define the abbreviations that are needed. Wikis are, after all, useful as a collaboration platform not just a reference tool. I want to be part of the solution, not part of the problem - so apologies if my work on the wiki entry is seen as problematic - but I don’t want to sit around doing nothing if no-one actually has the time and space to work on this known problem.
No need to apologise for anything, Tim, it was never ment as a rebuke on you, for you did in the best of intentions to the best of your knowledge. The difference is just, the approach has to be done in teamwork rather than uncoordinated action prior to consent. Currently there are two debates in progress, one on system based possibilities/necessities on TTS with Waze and one amoung the regional managers on abbreviation implementation. The connection between those two is obvious, for as the current situation proves, regardless of what we decide should be abbreviated has to be supported by TTS.
For a little immediate at once action I’d like you to do one thing: for people started to change current Names to unabbreviated (because of the TTS fail) you might add sthg to the Wiki:
Despite the broken TTS, street naming is to be done according to the rules stated in the Wiki. TTS problems will be handled seperately.
No need of course to change your revised list yet, before we reached consent, it’s too early to say, if it even needs to be changed or not.
So you see, it’s not that you are not invited to contribute to the Wiki, quite the opposite, we are happy you are able (as proven) and willing 