How bout TEMP CLOSED, California?
https://www.waze.com/editor/?zoom=4&lat=34.03137&lon=-118.41613&layers=BFTFFTTTFTTFTTTTFTTTTFT
Anyone have edit access in the Heathcote Suburb in Sydney or the town in Victoria. You guys have a smudge to one another that shows up here in the ACT on its way. Perhaps add the state tags to some street names?
I’ve taken it on myself to update the Wiki for the World Waze server to make the recommendation for the inclusion of the name of the Australian state to be included in the City field to be of the form “City, State” to ensure that a city boundary is contained within a state, and that the City field is unique within Australia: http://world.waze.com/wiki/index.php/Australian_City_Names
After a suitable period of time has elapsed, then maybe we can change this from a recommendation to a requirement - unless Waze adds an appropriate State field so this problem is removed.
Well thought out, Jinglee and Coogee can’t be titled in Western Australia as there are the same in the Far East. There are suburbs listed as Inglewood and Inglewood WA. It would solve both problems.
This approach is being quite commonly used here around for duplicate city names, belonging to different districts.
I’ve been automatically converting City names to “City, State” format wherever I find it in metro Sydney (as this is my area), regardless of whether the suburb is unique or not.
My reasoning is as follows:
- It’s consistent in naming
- It should help Waze in the future when they implement a separate field in their database. When that happens, a simple computer script by the database administrators can take the text string after the ", " in the City: (“Suburb, State”) field to become the new State field. Without this, Waze won’t necessarily know in which state a suburb is located and will have to match the suburb name with the state (admittedly this may not be that difficult).
- As I tend to work on one suburb at a time, it is easier to see suburbs that I have not checked over as there is a “Suburb” label in the area of the “Suburb, State” label. Once a suburb has been thoroughly worked over, you should only see one City label. At the same time as changing the City: field, I also check for typos in the Street: field, but I also make sure the street names use the recommended short form of the name, as this assists the user when they see the street name in their client. They will see a longer suburb name, but all the street names should be the short form, and the user will see many more street names when using Waze so I think on balance it’s better.
I think most of Sydney’s suburbs now use the “Suburb, State” format - I don’t know about other states. For this reason, when I added this recommendation to the Waze Wiki I didn’t make this mandatory for suburbs that are unique until we have some sort of consensus on whether this should be done everywhere.
I have noticed that some streets have had the suburb listed as “No City” (or “Sydney”): I’m not sure why. Either:
a) Someone knew a street name but wasn’t sure which suburb the street was in,
b) Someone thought that the street name is unique in Australia, possibly because it’s a famous street
c) The street spans multiple suburbs - I think the naming of some streets with the City name of “Sydney” might be for this reason. Tunnels that have no real connection with the suburbs above it would seem reasonable reasons for why people would name them with a trans-suburb name. I’m more in favour of segment names for highways that reflect the local suburb names. Tunnel names I’m not so sure of. Using meta suburb names like “Sydney” will distort the suburb boundaries on the map.
I personally have been leaving unique suburbs without the state to keep the on screen display clear and concise.
I have been adding the state field to suburbs which are not unique. I’ve found the WME Colour Highlights plug-in brilliant for this. It helps to ensure that entire suburbs have the same suburb name.