It’s already in the main wiki at [[Waze Map Editor/Welcome]]
Sent using Tapatalk for Android 4.4.2
:oops: :oops: :oops: :oops: :oops: :oops: :oops: :oops: :oops: :oops:
I’m going back to bed. :lol:
Made those two changes. Get Well Soon.
Almost going to ask if you’re psychic. Yeah, I’ve been home sick for the past two days and have been in and out of bed a lot.
Thanks.
This is great! Thanks everyone for stepping up. I’d love to have the Delaware Wiki up to par with the other Northeast states. We should have a discussion about setting state standards. Perhaps we can go through the NY, NJ, and or PA Wiki pages to determine what needs to be standardized?
For instance, I think we need to make sure we’re consistent with city names. Unlike PA & NJ, there are large portions of Delaware that are unincorporated (Hundreds don’t count). We need to set a policy for that.
In PA, townships count, but in DE, hundreds don’t count?
That leaves no city for most of DE.
But addresses don’t work without a city.
Most of Newcastle county seems to have a Wilmington Mailing address.
But zip is not city.
putting city or post office /zip/mailing city on segments is a really stupid idea Waze had.
But we are probably stuck with it for a while longer.
For your consideration on the city thing, the Virginia standard
In short, in unincorporated areas, city name is left empty except in densely populated northern VA.
https://www.waze.com/forum/viewtopic.php?f=580&t=61223&start=30#p936545
This creates some problems when doing searches for addresses. If a city name is missing, it will default to the Google search result – which may be wrong, unless you specifically search for an address with no city name.
https://www.waze.com/forum/viewtopic.php?f=5&t=111106&p=910851
The notable quote on that thread:
As for Hundreds, I don’t know of anyone who searches for addresses based on hundreds, so not sure that is a good idea.
I think there’s a strong consideration to make that this is a navigation app first and foremost so anything that aids in that end is something that should be strongly considered, so, for example, even though my house is not in Newark, DE proper, it’s mailing address is in Newark and I think if someone was searching for it they’d look for it based on my mailing address – especially if I was in their contact list. Basically people search for addresses. And addresses are based on postal mailing addresses. And Waze uses the city field to find addresses. So the city name should be what the post office thinks it is because that would aid in helping people find places.
Yeah, that’d mean “Wilmington” would spread all over the northern part of the state if you turn the city layer on.
We’d also have to decide on some aliases too. Like 19808 is considered both Wilmington and Marshallton by the post office. (Nothing is every easy…)
The Waze model for putting city name on the segments is just fundamentally flawed.
That’s the problem.
In PA, you can live in Tredyffrin township, in Chester County, which is a place everyone around there recognizes, but your mail might come through the Wayne post office in Delaware county because that’s how the USPS organizes its delivery routes. So you have a Wayne zip code. But you wouldn’t actually drive to Wayne to find the person’s house.
It’s like this all over the country.
Waze needs to move place information into a separate polygon layer that can be edited and locked.
And create even one more layer for zip code polygons (readily available in the US from several sources, based on mail route info supplied by the USPS), and probably the same for postal codes in other countries.
Until then, what to do with the city information is a real head scratcher, because someone driving to an address in Chesterbrook might type it in as Chesterbrook (which is not actually a place, according to the state of PA), Tredyffrin (which does), or Wayne (which is the post office that serves chesterbrook), and expect to get directions to the home or business.
Google handles this OK; if waze wants to get away from depending on google for address lookup, it will have to learn to handle it as well.
Until then, there is no sane way for map editors to handle city information, because nothing we can do will help very much. And the cities layer is really a smudged mess because of competing needs for how to use it – for visual orientation as well as for routing. and also because of editor ignorance, confusion, and disinterest in the whole problem.
So … while we hash out how to fix the city problem, can there be a consensus to move the Delaware page from “test” to replace the live one out there now?! 
As for the city discussion, guess we can look at what it’d look at and decide using real life examples:
For example — http://www.zipmap.net/Delaware/New_Castle_County/New_Castle.htm
I realize that’s copyrighted so not saying to use this for anything beyond conceptual discussion right now, but it shows the outline of the town boundaries of New Castle versus the zip code of New Castle which extends quite a bit further. Within the northern area of that zip code is “Wilmington Manor” which is currently mapped in Waze as a “city” but I always considered it more as a suburban development.
I guess a good question to ask is, are there any other states using postal definitions of cities to define cities in Waze?
I am all for this.
I think there are many states with confusion between municipalities and postal codes.
We aren’t going to be able to hash it all out here.
You cannot make the move, a wiki admin must do it when ready.
To prepare the current page should be copied to a new location as a backup with all the subpages. I think you did this already at the start of this project.
Then go through and confirm all the original information has been transferred over.
Then as a wiki check for any existing wikilinks to the original page, and subpages, change them to point to the proper new location.
PM a wiki admin to make the move when ready. (Kentsmith9 is one)
Then check all incoming links again to confirm they work, and remove any double redirects.
Sent using Tapatalk for Android 4.4.2
One more thing, I finally copied over the PLACES locking standard from New York with a minor change. I made it rank 3, not 4. The logic being that Delaware currently has a dearth of 4+ editors so I think that’s a good compromise between security and flexibility. @MReiser4670 and/or @PesachZ – I’ll respect your decision on this one of course!
I wouldn’t mind either way except for things like emergency services, and critical infrastructure, (police, hospital, airport, etc)
Sent using Tapatalk for Android 4.4.2
Makes sense. OK, critical ones changed. Thanks.
FYI all… PM sent to kentsmith9 asking to move the page into place.
Edit: OK, it’s live. I had to log in to see it. I assume it’s a cache issue that eventually clears up on its own.
It looks great, thanks!
Here is something I posted to NJ forum that applies here:
https://www.waze.com/forum/viewtopic.php?p=863761#p863761
In a nutshell, don’t get twisted up worrying about all the variables in address search, it is beyond our capabilities anyhow. Just worry about making the best map.
I agree.
Making the best map means some changes to city-name standards.
Because some places that do not qualify as cities by the current standards in many states are useful to have on the map, because they are useful to help wazers orient themselves.
And thank you for putting it more simply than I did.