Locked Segment Problem - US Rt. 40 in Bear, DE

Map Editors Community United States Delaware
1

The intersection at the following location is incorrect, and is locked by a level 6 editor. As an AM I cannot fix it. Please unlock the segment of US Rt. 40/Pulaski Hwy so it can be fixed.

https://www.waze.com/editor/?lon=-75.67813&lat=39.62491&zoom=7&layers=BFTFTTTTTTFTTTTTTTTTFT

Thanks!

2

Unlocked.

3

Great, thanks. Just updated the intersection.

4

Need an entire section of US Rt. 40 unlocked.

Basically, there are a few junctions that are incorrect, and the designation of “Major Highway” is incorrect–the speed limit on this road varies between 35 and 55, and the over-categorization of “Major Highway” is causing Waze’s traffic algorithms to improperly report slow traffic merely because of traffic lights.

https://www.waze.com/editor/?zoom=2&lat=39.62248&lon=-75.68024&layers=BFTFTTTTTTFTTTTTTTTTFT

Also, it seems some other AMs and higher editors are really inconsistently (and seemingly randomly) locking segments of the road. Makes fixing these errors pretty annoying :\

5

That was set to Major from the beginning because it is a US highway. I went through in the past and fixed some things but did not change the type. It looks like it is a good candidate for downgrade to minor. so I changed the segments I found. permalink any I missed.

Most of my locks are because of complicated turns, but some are based on early Waze problems with directions being changed automatically on split roads due to bad GPS tracking and weak algorithms on the part of Waze.

This intersection had some disconnected segments and other problems. I went through and fixed it the way I would expect it to work best. Please comment.

6

awhile back I had upgrade much of Rt. 40 through DE and MD (its what I drive everyday for my commute) to a Major Hwy. After a lot of consideration, I realized that because of the numerous traffic lights and varying speed limits, it fit the “minor hwy” category better. Should hopefully help with more accurate traffic prediction now as well.

Here’s a couple segments you missed:
https://www.waze.com/editor/?zoom=6&lat=39.60801&lon=-75.71345&layers=BFTFTTTTTTTTTTTTTTTTFT
https://www.waze.com/editor/?zoom=5&lat=39.64779&lon=-75.62946&layers=BFTFTTTTTTTTTTTTTTTTFT

As for the Rt-40 and 896 intersection–I’ve debated how to approach that in the past. I think the way you have it is pretty logical, and should work a little better with routing. Next tile refresh, I’ll drive it a couple times with routing on to see how it works. I think it should be less confusing than the previous intersection.

Only thing I would change is increase the length of the “exit” lane for the left/right turns. That intersection in particular gets very congested and crazy during rush hour, and the more time someone has to change lanes for an exit, the better. See below for visual representation of what I’m talking about:

7

Sorry, forget to write that those two segments were last edited by a Waze employee. I can’t change them. You will have to open a support ticket to get them changed.

Per the US community standards, we’ve decided to start turn lanes at the mandatory portion, defined by the solid white line. Waze does a good job of early alerts, so those few feet shouldn’t make more than a fraction of a second difference in the voice command timing.

8

Ah OK. I’ll open a support ticket to get the other segments fixed.

As for the turn lane, thanks for the clarification. When the tiles update, I’ll test it out.

9

Just wanted to revisit this intersection.

I have set the road type to “ramp” for the exits, as I wanted to match signage in the area as a wayfinder segment.

https://www.waze.com/editor/?zoom=6&lat=39.606&lon=-75.74092&layers=BTTFTTTTTTTTTTTFTTTTFT

Now, the TTS will tell you to exit according to the signage in the area, instead of “turn right at S College Ave” – which is very ambiguous, particularly since there are no signs on Rt. 40 that indicate Rt 896 as “S College Ave”. Delaware’s wonderful naming schemes for their roads are ridiculous.

Thoughts?

10

I have a few thoughts:

  1. I know that there has been much resistance to using ramp types at at-grade intersections. But I do think the legitimate exception is where are the are big green signs that have information that should be included in the turn instructions as is the case here.
  2. It seems odd to me that only this one turn lane is not named. But I haven’t driven through that intersection in a while and don’t remember the signage.
  3. I have been trying to get my head around turn instructions at roads that terminate at a one-way road, but haven’t had the time to fully figure it out. But I’m wondering with the angle of deflection being over 45 degrees at the end of these segments whether you won’t get a turn instruction at both the beginning and the end of these segments. Thus, if turning north on 896 from westbound 40 will you get a first instruction to “turn left at State Rt 896 N to I-95 / Newark” and a second instruction to “turn left at S College Ave?”
11

May be resistance but a similar case is documented in the wiki :wink:
http://www.waze.com/wiki/index.php/At-Grade_Connectors#Exceptions
We can update/add to the wiki based on this case if we think it would be helpful.

12

This is definitely one of those exception cases, as WeeeZer14 noted. The big green signs on both Rt. 40 and Rt. 896 don’t necessarily match the road names (Pulaksi Hwy and S College Ave), so in this case I feel it’s necessary for the wayfinder segments. Much like this area.

That is odd, I’m not sure how the name got removed. I might have missed hitting “apply” or something. Fixed that, good catch.

I will test it again, but I am fairly certain the last time I went through this area, it just instructed the ramp segment, and did not say “turn left at S College Ave”. I will give it a try today to be sure–that would definitely be a bit of a problem.

The only other question is that if you are going northbound on 895, and navigation wants to to go left to Rt. 40 W, there is no wayfinder segment that matches the sign. The same is true for going 896 S to Rt. 40 E. However, it would probably become a jumbled mess if we tried to add wayfinder segments for those portions.

Thoughts?