Sat Jan 09, 2016 3:49 am
Sat Jan 09, 2016 5:29 pm
Mon Jan 11, 2016 2:25 am
Tue Jan 12, 2016 4:07 am
Kinematic wrote:Big problems with Turah though, it's overlay is close to a mile NW of the actual city. This is where CDP can cause a problem. The only map I cold find is from Maptechnica. With towns like this what is your proposal? The city boundary currently on WME doesn't match up with either of the two.
Kinematic wrote:herrchin wrote:Propose to keep city name usage to within official city limits. No apparent detrimental effect to suburban or rural navigation. Use CDP name (regardless of city limits) if it's commonly-used locally. Otherwise "No City".
You're saying for Traffic locks and Dirt Roads we use the City name for "Street Name" instead of leaving the field empty? If so what is the benefit of inputting the name and how does it benefit routing? Obviously if they are within the city boundary and have a street named they will be labeled as such. If we are putting segments as DR inside of a city we have to consider whether or not they are navigable by a low profile vehicle. Is it detrimental to the overall navigation for that DR to be mapped at all, and is it beneficial. Just because it's there doesn't mean it needs to be mapped. A good way to find this is by turning on GPS layer. ( Still that is inconsistent depending on data coverage in certain areas. )
Sat Jan 16, 2016 5:57 pm
Mon Jan 18, 2016 6:35 pm
Sat Jan 09, 2016 3:21 am
Sat Jan 09, 2016 5:02 pm
herrchin wrote:Postal addresses in some states may always use the nearest incorporated town with a US postal office, which in some cases can be dozens of miles away. I'd find it a bit silly to list those far-away streets as being part of the city, as that'd be a huge smudge on the map. Places though, I give the city name, as that's what's needed in a search.
herrchin wrote:1) The floating city name in the mobile app as your approach
Unfortunately at this time iOS doesn't show the city boundary.herrchin wrote:2) Uniquely identifying a point when doing an address-based search (since the same road name can be used in multiple cities within a state)
For #2, I suppose there could be rural conflicts if generic road names exist such as "County Road 3". I'm not sure how we best address that without having cities that are potentially huge compared to their functional urban boundaries.
Sorry but I'm not sure I completely understand this example. Even if the address can be navigated to w/o a city name their is no need to add it. Am I close??herrchin wrote:If the Belgrade suburb is taxed as Belgrade, identifies as Belgrade and no other name, is probably provided utility services as Belgrade (due to taxation), then functionally it is Belgrade, right?
It's an excellent point to bring up . I suppose the urban boundary electrical power is supplied by the city , additionally they have a USPS by the city . I would likely assume that they run off of a well or even retrieve water from the nearby municipal water tower . That then brings up several other factors .
1.) Can the address be navigated to w/o a city name?
2.) How are we to distinguish all of this?
3.) In the event that we leave segments within the urban boundaries with out a city name and they cannot be navigated to with out a city name do we leave them as is and manage just user request issues that could occur or include the city name ?
I'm a big supporter for including city names within urban boundaries however am also open to suggestions .herrchin wrote:Related question would be how to handle unincorporated towns. No City, nearest incorporated city, or use their local name?
Tue Jan 12, 2016 2:30 am
herrchin wrote:[*]A regional or state standard should be established and clear so that all editors are consistent.[/list]
- In New Jersey, every single segment has a city name entry. In order of preference: CDP (census designated place, if the area is commonly known by it), then city/town/village, then township. https://wiki.waze.com/wiki/New_Jersey#Cities_and_towns
In the Southeast region, something a little different is used. Notably, roads outside the official limits of an incorporated municipality that are also not part of a CDP are "No City". https://wiki.waze.com/wiki/USA/Southeast/City_Field
herrchin wrote:Belgrade is a great example to use for discussion as it's a complex scenario. If we can establish rules that solve Belgrade, we should have a standard that works everywhere else.
Those parcels are taxed by Belgrade? (can I get a confirmation on this? I haven't found anything official yet, and there's a statement by Belgrade that some of these developed areas aren't paying "their just and equal share".)
herrchin wrote:Therefore, by keeping the city name usage tight to the official city limits, we preserve accuracy of the various city displays, at no apparent sacrifice to Wazing. Again, this recommendation is specific to Montana, not necessarily proposed guidance for other states.
As far as CDPs go, I would recommend they are used if they are the commonly used name for that area. If the CDP is not locally used, then use the city name if the segment is within city limits, otherwise No City.
herrchin wrote:TL;DR: Propose to keep city name usage to within official city limits. No apparent detrimental effect to suburban or rural navigation. Use CDP name (regardless of city limits) if it's commonly-used locally. Otherwise "No City".
Tue Jan 12, 2016 5:32 am
herrchin wrote:My understanding is that if we clear out all the "smudge" segment city names that are in the wrong spots, and have them correctly set on the correct segments, then within a few map update cycles the WME cities layer should update correctly. In extreme cases, such as city renames or deletes, we may need to fill out the form to have Waze update the DB manually. I had to do that with a "St Helena" to "St. Helena" rename. However, for Turah, initial searches show that as just an unincorporated community, not a full CDP?
herrchin wrote:I think there was a miscommunication, as I'm only ever talking about what is used in the city field? Nothing about street name.