# Abbreviations and acronyms (Australia)

**URL:** https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144
**Category:** Australia
**Created:** [March 5, 2015, 4:26am UTC](https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144 "2015-03-05T04:26:37Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![ispyisail](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/i/1BAB50/32.png) [@ispyisail](https://www.waze.com/discuss/u/ispyisail)
#### Post date: [March 5, 2015, 4:26am UTC](https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144/1 "2015-03-05T04:26:37Z")

</div>

Hi all

The official Abbreviations and acronyms (Australia) wiki is found [here](https://wiki.waze.com/wiki/Abbreviations_and_acronyms_%28Australia%29)

There has been some discussion in he CM and RM forum simplifying this wiki?

If you want to get pedantic there are over 200 possible abbreviations for Australia.  
examples found here [here](https://www.telstrawholesale.com.au/download/document/street-type-abbreviations.pdf)

It is unknown how many abbreviations that the Waze client understands?

If you go through the wiki you will also see that there are also exceptions. So you need to know all the abbreviations plus exceptions. I’m not saying its impossible to remember but its a big list and ts growing and getting harder to remember.

One suggestion has been to cap the abbreviations to the top 10 most commonly used the use the full name for all the rest?

Thoughts?

---

<div class="post-metadata">

### Author: ![ispyisail](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/i/1BAB50/32.png) [@ispyisail](https://www.waze.com/discuss/u/ispyisail)
#### Post date: [March 5, 2015, 6:52am UTC](https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144/2 "2015-03-05T06:52:15Z")

</div>

I probably should have said does anybody have any objection to this?

---

<div class="post-metadata">

### Author: ![ispyisail](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/i/1BAB50/32.png) [@ispyisail](https://www.waze.com/discuss/u/ispyisail)
#### Post date: [March 5, 2015, 11:07am UTC](https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144/3 "2015-03-05T11:07:44Z")

</div>

have you got a copy of this standard?

---

<div class="post-metadata">

### Author: ![TimAThing](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/t/FFC400/32.png) [@TimAThing](https://www.waze.com/discuss/u/TimAThing)
#### Post date: [March 5, 2015, 11:12am UTC](https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144/4 "2015-03-05T11:12:59Z")

</div>

Switching to a smaller set makes sense. For quite a number of the less-common items on there, their “abbreviation” is spelled out in full anyway - for the others, I don’t think we can be confident that the TTS will always render them correctly, particularly if the abbreviation is used elsewhere in the world for a different word.

While AS 4819 compliance might be desirable, it is less important than ensuring that Waze works correctly, i.e.

- When someone searches for a street they want to navigate to, Waze finds it.
- When they are driving along, the TTS instructions are helpful not unhelpful.  
If for example TTS renders “Ave” as “Avenue” correctly, but doesn’t do so for “Av” (note: I haven’t tested this), then unthinking AS compliance actually does us and other Waze users a disservice. If someone sees “Raw Sq” on a street sign but “Raw Square” in Waze, they’re not going to jump to a conclusion that Waze has taken them to the wrong street.

I’d suggest this list, based on what is common and has a confirmed-working abbreviation:

- Ave
- Blvd/Bvd (personally, I’d lean to just Blvd but happy for contra opinions)
- Cres/Cr (personally, I’d lean to Cr only)
- Dr (pretty sure this should be marked as working)
- Expy
- Fwy
- Ln
- Mtwy
- Pde
- Pl
- Rd
- St  
and maybe
- Plz
- Tce
- If Cct worked, I’d vote for it too.

If it helps for comparison, this is my current WME Validator template for finding misspelled street endings:

`
!/ (Aly|Arc|Ave|Blvd|Bvd|Br|Brk|Byp|Cp|Cyn|Cpe|Circuit|Cl|Clf|Cr|Cres|Crk|Ct|Dr|Expy|Fwy|Gr|Hwy|Ln|Mtwy|Mtn|Oval|Opas|Pde|Pk|Pky|Pass|Path|Pl|Plz|Pt|Riv|Rd|Rte|Row|Run|Sq|Sta|Strm|St|Ter|Tce|Trl|Tunl|Upas|Un|Vly|Vlg|Vl|Vw|Walk|Way|Wy|North|East|West|South)$|^$/`  
although I have to admit that in my time here I don’t think I’ve seen half of those used.

---

<div class="post-metadata">

### Author: ![TimAThing](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/t/FFC400/32.png) [@TimAThing](https://www.waze.com/discuss/u/TimAThing)
#### Post date: [March 5, 2015, 1:31pm UTC](https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144/5 "2015-03-05T13:31:54Z")

</div>

> [@ituajr](#):
>
> There is an Australian/New Zealand Standard for addressing (see [http://www.icsm.gov.au/street/](http://www.icsm.gov.au/street/), which includes an Appendix A (for Australia) giving the approved abbreviation for Road Types (ie, Rd, St, Av etc). AS/NZS 4819:2011 is described as the authoritative document for best practice in Australia and New Zealand. The various AU State governments seem to be moving to this standard:  
> WA: [https://www.landgate.wa.gov.au/corporate.nsf/web/Property+Street+Addressing+Useful+Links](https://www.landgate.wa.gov.au/corporate.nsf/web/Property+Street+Addressing+Useful+Links)  
> SA: [https://www.lga.sa.gov.au/webdata/resources/files/Rural\_and\_Urban\_Addressing.pdf](https://www.lga.sa.gov.au/webdata/resources/files/Rural_and_Urban_Addressing.pdf)  
> NSW: [http://www.lpi.nsw.gov.au/\_\_data/assets/pdf\_file/0005/195791/Local\_government\_addressing\_practices\_research\_study\_2012\_FINAL.pdf](http://www.lpi.nsw.gov.au/__data/assets/pdf_file/0005/195791/Local_government_addressing_practices_research_study_2012_FINAL.pdf)  
> and so on.

The file you mentioned for NSW indicated that local councils were generally not using AS 4819 for street naming. Certainly the relatively new streets I’ve mapped (or entered names for) in Waze do not show high conformance to the draft version of AS 4819 you provided a link to - and I’m not particularly keen to spend $150+ to get my own copy to see if the final version differs from the draft.

---

<div class="post-metadata">

### Author: ![ispyisail](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/i/1BAB50/32.png) [@ispyisail](https://www.waze.com/discuss/u/ispyisail)
#### Post date: [March 5, 2015, 6:00pm UTC](https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144/6 "2015-03-05T18:00:17Z")

</div>

My sole objective is to simplify and make functional something that i think is getting quite overly complex.

In a lot of cases we are only saving a few letters.

---

<div class="post-metadata">

### Author: ![ispyisail](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/i/1BAB50/32.png) [@ispyisail](https://www.waze.com/discuss/u/ispyisail)
#### Post date: [March 6, 2015, 5:34am UTC](https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144/7 "2015-03-06T05:34:43Z")

</div>

If it was me I would use the top 10 or 15 abbreviations in that standard then use the full name for all the rest.

200+ is too much for my brain to remember 🙂

---

<div class="post-metadata">

### Author: ![ispyisail](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/i/1BAB50/32.png) [@ispyisail](https://www.waze.com/discuss/u/ispyisail)
#### Post date: [March 7, 2015, 2:50am UTC](https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144/8 "2015-03-07T02:50:06Z")

</div>

I’ve made a spreadsheet based on AS/NZS 4819

I’ve selected the top 10 Abbreviations

[http://goo.gl/FZkMHQ](http://goo.gl/FZkMHQ)

Thoughts?

---

<div class="post-metadata">

### Author: ![Traveling\_Gav](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/t/FD804B/32.png) [@Traveling\_Gav](https://www.waze.com/discuss/u/Traveling_Gav)
#### Post date: [March 7, 2015, 10:15am UTC](https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144/9 "2015-03-07T10:15:33Z")

</div>

I think it would be handy to know what Waze’s plans are for expanding the TTS understanding of abbreviations. If they NEVER plan to add any more then there is a weight of argument to expand those (not working) abbreviations. However if they do intend to expand the coverage (CCT anyone!) then I think it would be premature of us to jump the gun and go against abbreviating.

---

<div class="post-metadata">

### Author: ![ispyisail](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/i/1BAB50/32.png) [@ispyisail](https://www.waze.com/discuss/u/ispyisail)
#### Post date: [March 7, 2015, 7:42pm UTC](https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144/10 "2015-03-07T19:42:50Z")

</div>

@ituajr

Can you tell use the top 50 abbreviation in order

---

<div class="post-metadata">

### Author: ![Caradellino](https://www.waze.com/discuss/user_avatar/www.waze.com/caradellino/32/25401_2.png) [@Caradellino](https://www.waze.com/discuss/u/Caradellino)
#### Post date: [March 8, 2015, 9:20am UTC](https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144/11 "2015-03-08T09:20:23Z")

</div>

> [@ituajr](#):
>
> …the principle that Waze should show what the driver sees on the sign…

Waze is far from that in a world wide pov…

Sidenote:  
Thes discussion within CM and RM has been initiated byispyisail as well. So feel free to further contribute to the discussion, but it has not been considered a pressing issue.

Still, of course, any improvement (as on anything in Waze) can - once ripe for it - be implemented in the Oz-Wiki

---

<div class="post-metadata">

### Author: ![ps\_au](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/p/0099FF/32.png) [@ps\_au](https://www.waze.com/discuss/u/ps_au)
#### Post date: [March 10, 2015, 7:54am UTC](https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144/12 "2015-03-10T07:54:28Z")

</div>

So all those abbreviations listed, does TTS recognize them to correctly pronounce them?

---

<div class="post-metadata">

### Author: ![ispyisail](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/i/1BAB50/32.png) [@ispyisail](https://www.waze.com/discuss/u/ispyisail)
#### Post date: [March 10, 2015, 8:23am UTC](https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144/13 "2015-03-10T08:23:10Z")

</div>

> [@ps\_au](#):
>
> So all those abbreviations listed, does TTS recognize them to correctly pronounce them?

“all” no

e.g. Cct

My guess it that most don’t and that is where some of the problem lies?

---

<div class="post-metadata">

### Author: ![ps\_au](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/p/0099FF/32.png) [@ps\_au](https://www.waze.com/discuss/u/ps_au)
#### Post date: [March 10, 2015, 5:55pm UTC](https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144/14 "2015-03-10T17:55:06Z")

</div>

I don’t think they have ever updated or improved the tts engine, so the extra abbr we want is pretty low on the fixit list. Personally don’t see any changes regarding this any time soon.

---

<div class="post-metadata">

### Author: ![ispyisail](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/i/1BAB50/32.png) [@ispyisail](https://www.waze.com/discuss/u/ispyisail)
#### Post date: [March 10, 2015, 6:01pm UTC](https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144/15 "2015-03-10T18:01:10Z")

</div>

> [@ps\_au](#):
>
> I don’t think they have ever updated or improved the tts engine, so the extra abbr we want is pretty low on the fixit list. Personally don’t see any changes regarding this any time soon.

yeah

That’s the first problem

The second problem is remembering all 200 abbreviations and there exemptions

---

<div class="post-metadata">

### Author: ![theclem54](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/t/FF5252/32.png) [@theclem54](https://www.waze.com/discuss/u/theclem54)
#### Post date: [March 11, 2015, 10:26am UTC](https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144/16 "2015-03-11T10:26:46Z")

</div>

No need to remember them all, just keep the page open beside the editor, how often does an unusual one pop up in reality? It’s easy to remember the top 5 or 10, the wiki page is there for the rest. That’s the reason reference books exist.

---

<div class="post-metadata">

### Author: ![ispyisail](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/i/1BAB50/32.png) [@ispyisail](https://www.waze.com/discuss/u/ispyisail)
#### Post date: [March 11, 2015, 6:10pm UTC](https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144/17 "2015-03-11T18:10:04Z")

</div>

> [@theclem54](#):
>
> No need to remember them all, just keep the page open beside the editor, how often does an unusual one pop up in reality? It’s easy to remember the top 5 or 10, the wiki page is there for the rest. That’s the reason reference books exist.

Yep this rule would apply well with NZ but you should have a look at Melbourne, its just crazy (anecdotal evidence)

---

<div class="post-metadata">

### Author: ![ispyisail](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/i/1BAB50/32.png) [@ispyisail](https://www.waze.com/discuss/u/ispyisail)
#### Post date: [March 15, 2015, 8:28am UTC](https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144/18 "2015-03-15T08:28:42Z")

</div>

you guys seen this this?

[https://docs.google.com/spreadsheet/ccc?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E#gid=0](https://docs.google.com/spreadsheet/ccc?key=0AgVtBjo5tTNgdG5vVHN5RmVzaWdlWk1VLTRzYUhGN0E#gid=0)

from here

[https://www.waze.com/forum/viewtopic.php?f=10&t=15178](https://www.waze.com/forum/viewtopic.php?f=10&t=15178)

---

<div class="post-metadata">

### Author: ![ispyisail](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/i/1BAB50/32.png) [@ispyisail](https://www.waze.com/discuss/u/ispyisail)
#### Post date: [March 15, 2015, 8:50am UTC](https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144/19 "2015-03-15T08:50:16Z")

</div>

I’ve been going through this list and there is issues everywhere

Question: Do we want align where possible with “AS/NZS 4819”

Are we happy if I change the wiki to reflect this?

example  
Now “Lane = Ln”

AS/NZS “Lane = Lane”

and so on…

---

<div class="post-metadata">

### Author: ![TimAThing](https://www.waze.com/discuss/letter_avatar_proxy/v4/letter/t/FFC400/32.png) [@TimAThing](https://www.waze.com/discuss/u/TimAThing)
#### Post date: [March 15, 2015, 11:55am UTC](https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144/20 "2015-03-15T11:55:38Z")

</div>

> [@ispyisail](#):
>
> I’ve been going through this list and there is issues everywhere

Confirmed - but I’ve also noticed that this list contains different results to the results shown on the wiki for Australia. For example: Dv is listed as a working abbreviation for Drive on the US list, but is shown as a working abbreviation for Divide on the AU list. Assuming that the testing status on both sources is correct, this leads to the conclusion that the TTS for US/CA contains different instructions to the TTS for AU - which seems reasonable to my mind, given that they are different voices for different markets.

> [@](#):
>
> Question: Do we want align where possible with “AS/NZS 4819”

No, because I think that would deliver negative value.

The underlying question is “what is/are the purpose/s for the street abbreviations on streets in Waze?”. This can be open to debate, but I’d argue that the points are:

- To enable streets to be searched and identified (particularly where there are, say, a Road and a  
Lane with the same name in the same suburb/city).
- To enable Waze to give spoken navigation instructions (TTS: Text-to-speech) that make sense (i.e. we want it to pronounce “Circuit” not “C-C-T”).
- To enable the driver to see if they are on (or moving onto) the correct road.
- To minimise the text displayed on screen (i.e. convey the relevant information in the smallest amount of screen real estate available.

I’d similarly argue that the following are not purposes/goals of the abbreviations:

- To exactly match what is shown on the street sign (especially since this may vary anyway, e.g. signs at different intersections using different abbreviations or spelling out in full; 90%+ of drivers should be able to conclude that if they see La on a sign but Ln on Waze, they’re still in the right place).
- Compliance with AS/NZS 4819 (given that the councils and state road authorities’ compliance to this standard is not high, Waze is not supposed to be an authoritative reference, and AFAIK we are not trying to exchange any data with systems that expect AS/NZS 4819 compliance.)
- Making the list of abbreviations easy to remember. (It is easy enough to have the list open in another tab or window and scan/search through it as required.)

If we agree that those are the goals, then the obvious conclusion is to continue working as per the wiki (combined with trying to verify any unverified abbreviations we can, working with Waze to add the abbreviations that would be beneficial to TTS, and spelling out any words that aren’t in TTS).

If we don’t agree that those are the goals (yes, this is an invitation for opposing arguments) then the conclusion we reach might be different. There is no perfect decision we can make because we don’t have control over the externals (signage, TTS), but whatever decision we do make should at least fit a sensible set of goals.

[Next page](https://www.waze.com/discuss/t/abbreviations-and-acronyms-australia/257144.md?page=2)
