I have a report from a wazer on 295 in NewCastle being directed to 13 for .8 mile.
I also have several reports of the same problem in state road 1 south of the C&D canal
I cannot see anything in particular about the map that could be changed to improve things.
To save 30 seconds? The penalty is not high enough or else the algorithm should prefer to stay on the same named road unless it can save some longer period of time. Maybe 45 seconds. Maybe a 2 minutes?
Is there anything map editors can do? Or should we make a habit of reporting when we see URs reporting these issues? Is the waze team interested in this issue?
I replied to this issue on your other post
https://www.waze.com/forum/viewtopic.php?f=575&t=104441#p863952
Basically have to check to make sure everything is set up to ensure detour prevention is working.
Details in that thread 
Thanks for your comments on detour prevention. That’s a new topic for me!
https://www.waze.com/forum/viewtopic.php?f=622&t=104561#p864466 should help with that section of 295.
So I should look for something similar on SR-1, if I can narrow down the section where this is happening (of course, the waze-reported section does not include the detour).
I guess I’ll need to take this discussion up in the DE forum, because, if there is no nearby city, I might have to use the hundreds name for the area.
I see you put in a unlock request that is kinda a dupe of mine. Problem is, the alt street names are taken into consideration too and that northern end of the ramp has an alt name that has to be removed, so that’s going to have to be removed regardless of whether city names are removed or added.
I do editing in rural Virginia too and the rule there is basically city names just in incorporated towns else it’s no city. Not sure what the rule is for Delaware. That part of the county is outside of New Castle proper but is part of the 19720 zip code – but then there’s that “Wilmington Manor” development that has all of its streets with a “city” name of Wilmington Manor even though it’s inside the New Castle zip code.
Anyway, veering off topic a bit except to say that what to put in the city name around here is really unclear to me right now… and those are some of my examples why.
Here’s another on-off issue… Waze is routing inbound 95 traffic to Wilmington down to 13 and back to avoid some of the 95 backup (only during morning rush). It claims this saves about 9 minutes. I don’t think detour prevention is going to work in this case because the segment before the detour is I-95 N and the segment after the detour is I-95 N with 202 N as an alt name and since that part is also really US 202 I don’t believe we should just edit it out.
Besides, if saving 9 minutes is really the case, it’s not a bad detour!
Do you have an unlock request on that same segment? If so, then I’ll stay out.
I put a question on the DE board about what city to name DE SR-1 south of the canal.
If we actually name the segments of SR-1 after the city it runs through, these will not deter detours because the wazer is routed OFF 1 on the north side of Smyrna, then back ON 1 on the north side of Odessa – so the city will have changed anyway. And the wazer will still be annoyed.
It would be possible to name all those segments after the county for consistency, but that seems like a really ugly solution.
“City” vs “no city” is a problematic criterion for detour avoidance. It’s a proxy for trying to figure out which roads are real roads and which are slip roads, This is just overloading that property with meanings it ought not have. I bet it is not at the exact top of the waze team’s list, though, and we map editors cannot fix that ourselves.
To quote the detour prevention page https://wiki.waze.com/wiki/Detour_Prevention_Mechanisms
Since those segments share a name (even though they don’t share the alternate name), then criterion 1 is met. Presumably the, one or more of 2 or 3 is not met. Probably 3. Unless the wiki page is incorrect. Not sure how to check #3.
You’re parsing the docs as if you’re a machine executing a program and that they are 100% accurate. I’m not so sure. “or” means either condition has to be met for it to be true. However if that was the case then the detour avoidance for the case I just posted with the pic should be working since the primary name matches and the city name matches, but it’s NOT working. The only difference is one has no alt names, the other does. Hence why I think the alt names are checked.
In order to understand the best way to do things, we kind of need help from the waze team, to understand how the machine running the routing algorithm does parse these things.
If we have not-quite correct info, we wind up wasting time.
I wish waze had someone available to help us develop correct information for map editors. so we could help maximize the potential of waze.
But, yes. Something failed to prevent that detour, and we cannot know if it is 1 or 3 or else condition #4b that we have never heard of because…
Please try the experiment of renaming the segments and see if it makes the difference.
Thanks.