Should North Conway be used as a city in Waze?
I was editing in the Conway/North Conway area and was trying to find the line between Conway and North Conway, which led me to discover that North Conway is a village/ census designated place, not a town.
I then checked the Waze NH City/Town list and saw that North Conway was not listed, since NH only uses real cities and towns.
I’m wondering if North Conway should be an exception, and should be added to the NH City and Town list. 1) It is a well known tourist destination 2) Many businesses/lodging/restaurants advertise themselves as being in North Conway 3) We have many segments and places already named North Conway. If we switch all of the "North Conway"s to “Conway” what happens when people search for North Conway?
My thought is North Conway should be an exception and be added to the official list, as I think most people would think it is a separate town (at least us flat landers and visitors from outside of Coos County).
I would recommend against including North Conway separately. There should be an all or nothing approach to villages or unincorporated places within a town/city given how Waze handles addresses/routing. Good catch on the different names on those segments. Interested to hear how these will be resolved.
Great work identifying the issue, and thanks for raising it, derrydrivin.
I did an experiment with one of the “North Conway” hotels. I changed the City to “Conway”, and waited for a tile update.
Now, when I search for it, the autocomplete provides both a “Conway” item and a “North Conway” item, both with the same street address. I’m assuming that the “North Conway” entry is pulled from Google. When I complete the manual search, only the “Conway” address is returned. This change can be made to other Places, with little impact on user confusion, I believe.
I agree with nhmapguy that there is no reason to deviate from our NH standard of “official” towns and cities only, as listed in the wiki.