Oz Street Name Check

A new version of Street Name Check is available.

Download version 2.31.4 from https://greasyfork.org/en/scripts/371038-wme-street-name-check

This version has the following changes:

  • Replaced deprecated method which was causing console warnings.
  • Fixed compatibility issues with WME Color Highlights. Both now play nicely. :smiley:
  • Added option to choose dashed highlight.
  • Added option to choose either orange or magenta for highlight colour.
  • Other code cleanup bits and pieces.

As with most scripts I don’t have the time to test thoroughly so please post any issues here (I don’t guarantee that I will be able to do anything about it though :mrgreen: ).

Street Name Check will check street name abbreviations on the map (eg, Ave, Cres) against the list of recommended abbreviations as listed at https://wazeopedia.waze.com/wiki/Australia/Abbreviations_and_Acronyms and highlight any that don’t match.

Happy editing!

Version 2.1 available.

Changes include:

  • Added option to ignore ā€˜Ave, Cres, Blvd’. In case you want to concentrate on the others first as these are pronounced correctly by TTS
  • Repositioned ā€˜Named parking lot roads’ to make it’s purpose more obvious
  • Removed the necessity for the script to loop once a second
  • Miscellaneous code clean ups

Couple of small changes in V2.11.

Added option to turn layer off in Layers menu in ā€˜Scripts’ group.
Road types in left side panel reflect locale, eg. if you use the en-GB browser it should say ā€˜Parking Roads’ instead of ā€˜Parking Lot Roads.’

Version 2.22 now available.

Changes:

  • Fixed bug causing page to become unresponsive when many segments highlighted
  • Added following valid suffixes: Wynd|Gateway|Ford|Cross|Pursuit|Quadrant|Waters|Common|Hill|Turn|Nook|Run|Green
  • Added option to highlight segments last edited by an L1 editor

https://greasyfork.org/en/scripts/371038-wme-street-name-check

I’m bringing this question here from Discord as it’ll help me keep track of it.

The list of abbreviations has changed significantly since SNC was first built. I intend to bring it up to date to match the current list however there are some that are causing problems with RPPs. Discussion here.

It has been suggested that we don’t highlight the problematic ones until the problems are sorted but SNC works by highlighting any segment that does not match a list of given abbreviations. I propose having SNC accept any of the ones under discussion as valid (ie. not highlight them) until the current issues are sorted out, at which point I will update it.

Another issue is that of service roads. I seem to recall a discussion concluding that either ā€œBlah St Service Rdā€ or ā€œBlah St Service Roadā€ is acceptable. Should SNC accept both?

Does that mean that this and other similarly named roads should be changed to Market Street North or the equivalent?

Highlighting service roads, etc. isn’t a problem, personally. The script is a tool to draw my attention to 95% of problems, it won’t replace my editing discretion, and I know what I need to ignore. Maybe you could add some advice of what to ignore into the ā€œsettings pageā€ though?

Thanks again, Big K, for maintaining this script! It’s incredibly valuable to me as I find the highlighter tool extension on RSel unreliable. :slight_smile:

And darn, there are some good points I didn’t consider either.

Right. New version 2.26 available.

  • Settings now persist after switching to Event mode and back.
  • The valid abbreviations have been updated to match the wiki.
  • I have changed the Ignore list to include the proposed abbreviations listed at the discussion above – with the exception of ā€˜Ter’ – so that you can choose to include them or not.

And I just remembered I forgot to do anything about service roads so I’ll include that in the next update.

Let me know if you find anything that needs to be added.

Another small update.

SNC will no longer highlight ā€œService Rdā€
Added ā€œhttps://beta.waze.com/*ā€ to included servers.

Cheers.

Currently if a street starts with "The " it will not trigger as being invalid. This is to allow names such as ā€œThe Corsoā€ and ā€œThe Esplanadeā€, etc.

However it will highlight if the word ā€œTheā€ is not at the start of the name. This results in a valid name such as ā€œC312 - The Circuitā€ being highlighted. To address this I propose changing it so that the word ā€œTheā€ followed by any other word anywhere in the name will not trigger the highlight. Can anyone see a problem with this approach?

Whitelisting ā€˜The’ isn’t triggering any mental alarms that I can think of. Good on you.

Looks like there’s a bug in the script as it is still highlighting unnamed parking lot, private, etc despite the setting set to FALSE. I’ve reported it to the dev.

Wrong thread

I think you meant to post that in another topic. :wink:

Can this be rolled back as there are ramp names which are also affected. I would suggest his change is causing way more issues than the attempt to fix the Saint problem.

I’m a bit confused by this Saint/Street thing. The way SNC works – and it’s been this way from the start – is it will allow ā€˜St’ at the end of the string. If ā€˜St’ appears anywhere else in the string it will highlight.

It is the opposite for ā€˜St.’ It will allow ā€˜St.’ at the start and middle but not at the end. This has worked with the way TTS was set up because TTS would pronounce ā€˜St’ as ā€˜Street’ and ā€˜St.’ as ā€˜Saint.’

My plan was to wait until all this Saint/Street thing was sorted out and then make any adjustments if necessary. If anyone has an example of where it is highlighting incorrectly post a permalink and I’ll check it out.

[Edit] Some confusion might be coming from the fact that ā€œService Roadā€ is treated as a valid extension such as ā€œEastā€, ā€œWestā€ etc and is trimmed off before the test is made. So ā€œMurray St Service Roadā€ would be treated as if it were ā€œMurray Stā€

Came on here to try & find out why my Waze has recently started calling local streets ā€œSaintā€ instead of street. I guess it’s a problem for others too.

I’m finding it to be inconsistent - some streets are fine, but the next street is not. On a drive yesterday I went from a Street, into a Saint, then another Saint and back into a Street.

Yup, we’re currently waiting for the fix to be implemented.

So this is being rolled back?

I don’t know if the editor (I used it to test) uses the same code as the app but still no go if it appears in the middle.

https://www.waze.com/editor/?env=row&lon=153.01170&lat=-27.46592&zoom=6&segments=101710819

All right, finally got around to making some changes. V2.28 now available https://greasyfork.org/en/scripts/371038-wme-street-name-check

Changes:

  • Added PLRs to highlight options
  • Added Elbow and Copse as valid suffixes
  • Will no longer highlight if ā€˜St’ in the middle of a name
  • Put ā€˜Ave’ back in the list for the Ignore option
  • Changed so the word ā€˜The’ in the middle of a name won’t trigger highlight