I would like to post this to bring up an issue that should be resolved and may be specific to Washington and/or Clark County (I haven’t looked into other areas).
Summary: Waze uses CDPs (Census Designated Place) as ‘cities’ in the map editor. This can be confusing as much of the public hasn’t even heard of many of them, e.g. they might or might not know where the ‘Five Corners’ area is, but they probably know that there isn’t a city called Five Corners, WA nearby. Some uniformity and clarification is needed for mapping places and roads – do we use the city name from the street/mailing address? Or do we use the CDP name for the City name?
As an example, I typed in “costco” into the navigation search and this is what I got. I know roughly where Walnut Grove is and I know that the Costco is on NE 88th Street, but Walnut Grove listed as the city will confuse a lot of people as many have never heard of it and may easily think it is a Costco in some other city somewhere. The mailing, billing, and street address lists it as Vancouver, WA - even though it’s not in the actual City of Vancouver (city limits).
I encountered this almost as soon as I started editing and was told to use the Waze identified CDPs and check the federal CDP map if unsure of the boundary lines. In Clark County, there are a few actual cities with their own jurisdiction, addresses, and their own road names and numbering systems. Outside of the city limits, the road system goes back to the City of Vancouver grid system with the origin in the center of the city itself (west of I-5). Here is a screen shot from Waze where I’ve roughly marked the cities and their approximate limits. I used it because it also clearly shows some of the CDPs. If you want more detail, here is a GIS map with the correct layer turned on. The point is that addresses in the areas outside of the individual city limits don’t the CDP name for their city, they generally use the name of the nearest city, even if it the address is a long way from the city limits. There are some exceptions.
My thoughts:
First; regarding places, I believe their street/mailing address should be used. If I give someone my business card or my personal address and they search for the location on Waze, it needs to show up as Vancouver, WA, not as Orchards, WA or Barberton, WA or they’ll think it’s the wrong place. Some CDPs are really obscure and unknown, especially to visitors or people new to the area.
Next; regarding the roads on the map editor, it gets a little more complicated. I’m not exactly sure how the coding works or what, if any, the ramifications are (to routing efficiency) if roads & PLRs in an area have all mixed city/no city listings. But still, okay, maybe there is a better case to be made for using CDPs names for roads and parking lots in WME right? Nobody sees those, WME already has a nice color city layer outlining the edges (no need to dig for other reference material), and perhaps uniform city listings help with the program. Okay, that sounds reasonable to me and is what I’ve been doing.
However, the biggest problem I’ve seen with this is when adding a new development to the map. I add the roads and addresses and list the city according to the CDP name. The problem is that this is a new development, so builders, construction supply delivery trucks, realtors, home buyers, etc. put in an address (e.g. 11291 NE 147th Ave, Vancouver, WA) and… it doesn’t show up in their search results. However, that appears to be because I’ve listed the roads with the city name Orchards (the CDP). So when I edit addresses, it shows up as 11219 NE 147th Ave, Orchards, WA. Problem is, nobody will ever search that or even think that the two are the same address. Some people may know it’s sort of in the Orchards area, but most won’t. Here is a PL to this example location. A work-around (after a lot of experimenting with HNs) is to add a point place marker (with the address listed as Vancouver, WA) as this seems to override everything in the Waze search algorithm. But I’m not adding 54 place markers for a single new residential development. This also leads to disillusionment with adding HNs as I’ve already experienced this same thing on other very new developments that also don’t search correctly on Google. “You can’t get here on google maps, use Waze instead, it’s much better anyway.” – except it needs to work.
At any rate, that might be a mix of two problems, listing the CDP as the city, and an issue with Waze not using HNs in their search algorithm. I’m not exactly saying that the listed city for roads should all be switched (that would be a huge task), but if someone’s address is NE 28th Ct, Vancouver, WA, then it doesn’t make sense to list the road as NE 28th Ct, Barberton, WA in WME – unless there is some other underlying coding reason? Also, it doesn’t matter for older addresses, because when searched as Vancouver, WA, Waze will pull up the correct location (because it’s not using the listed city from the road in WME, it’s pulling from somewhere else).
Which also leads me to wonder, if not used for address locations, does it even make a difference if a segment is listed as ‘no city’? Or if it has a city name attached to it? Or an incorrect city name?
In summary, for the sake of uniformity:
- How do we list Places – with the city name from the street address or with the CDP name as the city name?
- What city name should be applied to roads? The CDP name? Or the city name as indicated by addresses on that road?