And how to handle when the users ignore the directions to make ridiculous u-turns and the problem is generated? I'm not even taking about the ones where it may actually be faster to take the u-turn route, but the ones that make no sense. Like when the routes that turn right into a cul-de-sac, u-turn and then turn right out of the cul-de-sac traveling in the same direction as going straight through the intersection. No stop light or turn restrictions causing it either. Is that a solved (the maps correct) or not identified (don't know why the routing server screwed up)?
[img]https:///L6ziL[/img] [img]https:///0NAfp[/img]
Required reading: Quick Start Guide, Best Practices, USA Road Types
This routing down dead end streets has me wondering if the terminal junction on the segment is corrupt or has some connectivity issues. I've noticed that sometimes the JNF script will actually 'fix' the terminal node on a dead end even though the highlights scrip doesn't indicate anything's wrong. I think a self connected terminal node may cause, or at least allow, this type of route to come out of the server.kentsmith9 wrote:Here is another with a similar config. Both this one and my last post had no problem on the straight through route. The route proposed is a single dead end street with no city or road name. It was edited by Staff on January 1 this year. Not the road next to it is untouched and still shows Portola Valley. Note sure why the script did not fix that road as well.
[img]https:///L6ziL[/img] [img]https:///0NAfp[/img]
Required reading: Quick Start Guide, Best Practices, USA Road Types
The way that I've chosen to interpret that type of routing is that there is such a large delay in the junction transit time when waiting for a red light at an intersection that the routing server calculates it is faster to take a low-delay right turn, two low-delay left turns and another low-delay right turn. Of course this theory falls apart when the routing server directs somebody to make a u-turn on a dead end and then continue in the same direction on the original road when there's no light or stop sign along the original road.j2brown wrote:Possibly related: I've noticed a few cases recently where Waze won't route straight through what appears to me to be a correct intersection, but instead send folks down the side street to make a U turn, then return to the route of travel and continue in the same direction. (right turn, left handed u-turn, another right turn). It's usually at the intersection of two divided roads ( # ). At first I thought that the short segments in the intersection (making up the box) might be the issue, but they appear to be of the proper road type, in the proper direction, with the proper turns allowed/restricted.
Unfortunately I don't have a handy example of that.
Thoughts?
[img]https:///L6ziL[/img] [img]https:///0NAfp[/img]
Required reading: Quick Start Guide, Best Practices, USA Road Types
This new detection system is great! Solved at least a dozen in my area already this morning where otherwise it wasn't reported by any user. This should greatly improve the map overall in the next couple of weeks. There were several that was based on old data but no matter, I would suspect we should see less of those as time goes on.
POINTS!! Hahaha! I like it, seems to catch alot of bad turn restrictions. Also finding waze tries to route people down uneeded side roads alot...
USA Territories Regional Coordinator : USA Champ : L6 State Manager Arizona
https://www.waze.com/wiki/images/6/6b/W ... _0M_6c.png
Waze Arizona Twitter
https://www.waze.com/wiki/images/6/6b/W ... _0M_6c.png
Waze Arizona Twitter
Save button unavailable. Also very slow this morn.
These auto generated are also showing me where alot of times waze is trying to cut a corner of an intersection where people are turning left. Instead of turn left at a light, it tries to send them down a side street to turn left onto that major road. I'd rather turn left at a light then from a side street..
These auto generated are also showing me where alot of times waze is trying to cut a corner of an intersection where people are turning left. Instead of turn left at a light, it tries to send them down a side street to turn left onto that major road. I'd rather turn left at a light then from a side street..
USA Territories Regional Coordinator : USA Champ : L6 State Manager Arizona
https://www.waze.com/wiki/images/6/6b/W ... _0M_6c.png
Waze Arizona Twitter
https://www.waze.com/wiki/images/6/6b/W ... _0M_6c.png
Waze Arizona Twitter
[quote="shawndoc"]They didn't start showing up for me until I cleared my cache.[/quote]
How do you clear the cache? I was working on an area with quite a few problems, but they just disappeared when I fixed one of them.
How do you clear the cache? I was working on an area with quite a few problems, but they just disappeared when I fixed one of them.
-
outtolunch
- Posts: 17
- Has thanked: 10 times
Thanks. That got a couple to show back up. Someone else must have fixed the others.
-
outtolunch
- Posts: 17
- Has thanked: 10 times
That is one issue filled map LOLjoshellis625 wrote:sweet baby jesus I have never seen so many SRP's before.
[img]https:///EcBKq[/img] [img]https:///L6ziL[/img] [img]https:///pIzEJ8[/img]
AM: Texas
CM: USA
Champ: USA
Mentor: USA
Best Practices for Map Editing | Texas Wiki| Unlock Request for US | Mentoring
AM: Texas
CM: USA
Champ: USA
Mentor: USA
Best Practices for Map Editing | Texas Wiki| Unlock Request for US | Mentoring
About one out of 10 times:
https://www.waze.com/editor/?zoom=0&lat ... TTTTTTTTFT
I see a few dozen "Most users did not follow the suggested route" automatic reports. Most times the radar is clean.
When I try to resolve one, the "save" button is unavailable. But if I click between solved and unidentified enough times, the save button becomes available and I can save it.
Here's what I think is happening: there's one Waze server out of a dozen that is out of sync with the others, and it's causing both symptoms.
Is anyone else noticing this behavior?
https://www.waze.com/editor/?zoom=0&lat ... TTTTTTTTFT
I see a few dozen "Most users did not follow the suggested route" automatic reports. Most times the radar is clean.
When I try to resolve one, the "save" button is unavailable. But if I click between solved and unidentified enough times, the save button becomes available and I can save it.
Here's what I think is happening: there's one Waze server out of a dozen that is out of sync with the others, and it's causing both symptoms.
Is anyone else noticing this behavior?
SocksLabs
Area Manager: Shrewsbury/Northboro/Westboro, MA
https://www.waze.com/wiki/images/5/5a/W ... M_only.png
Helpful resources: Map Editor | Best Practices
Area Manager: Shrewsbury/Northboro/Westboro, MA
https://www.waze.com/wiki/images/5/5a/W ... M_only.png
Helpful resources: Map Editor | Best Practices
Re: Changes to Editor - New Automatic Detected Problem