Nashua Exit 1 Slip Road

I’ve seen numerous URs complaining about being routed off Route 3 in Nashua only to be routed back on.

https://www.waze.com/editor/?lon=-71.45225&lat=42.70433&zoom=5&layers=BFTFFTTTTTTTFTTTTTTTTTFTTTTTTTTTTTTTT&segments=74051179

I have an idea that would help this problem, and I think that there would be no down-side: eliminate segment 74051179 (selected in the above permalink), and join the junction at the ends of segments 57597180 and 74051178 to the junction at the beginning of segments 31595580 and 31625492. Then, set a restriction so that traffic cannot proceed from segment 57597180 to 31625492 (similar to what is usually done at interstate highway exit/on-ramps to prevent drivers from being routed off to be routed back on).

Thoughts?

My thoughts,

  1. I vaguely remember this interchange being discussed regarding this issue before, but I can’t find it.
  2. Your solution sounds good to me. The only issue is that I have heard reports that restricting a turn like this eliminates the keep right instruction at the junction. Not sure if that is currently the case or not.
  3. The state line complicates matters. I’m not sure where exactly the state line is, but if this segment could be changed to be named “Frederick E Everett Tpke” and given a city/state of Nashua/New Hampshire that should prevent the routing off/on Route 3. That however would not prevent the early exit for Circumferential Hwy as your solution would.

Hi,

Thanks for your thoughts.

Regarding point 2 above, drive this area every workday. I will test that. If there is no “keep right” announcement, that is unacceptable, and I think we’d have to find another way or revert back.

Regarding point 3, the state line is just prior to the end of the segment you linked to. We should probably move that junction back (to where the pavement color changes in the Bing aerials), but leave the ramp entirely in NH with a separate junction (in the same location as the current junction).

Any other thoughts?

Sounds great. I’ll be interested to see your results.

This sounds good to me. Although, if your solution works and gives appropriate turn instructions, then this may not be required to provide good routing.

I’m going to wait until the weekend to implement this, to allow time for more comments.

My plan is to implement my original proposal (but not changing the state-line junction) and see what the impact on routing is. I will report back after testing the routing on Monday and Tuesday.

I agree with Chris that the state line being shared with the junction for the ramp is the problem -

Slide the ramp back to where it should be mapped - the drop dead point (where the line between the highway & the ramp turns solid) and keep the state line where it is/should be. This will give you something that looks like (south to north):

== US-3 (MA) == Everett Tpke (NH) == == Everett Tpke (NH) ==
                                    \\
                                      == Exit 1 ==

Ok, AndyPoms, thanks.

Seeing that this is locked at “5”, is that something you could do for us, please?

The state line is actually where the pavement changes color, so I think the ramp should remain where it is, and the change from US-3 (MA) ==> Everett Tpke (NH) should happen at the color change.

I will hold off on all other changes until we can see the imact of that change.

Taken care of… I didn’t get to do this till 7pm, so it probably missed the update cycle - the changes should be visible Saturday or Sunday (as long as the update cycle works - see http://status.waze.com for info about that.

It has been about 5 months without a report, but we got a UR today from someone who Waze directed to use the slip road as a bypass.

Can this be further tweaked?

https://www.waze.com/editor/?lon=-71.44855&lat=42.70103&zoom=5&layers=TBFTFFTTTTTTTFTTTTTTTTTTTTT&segments=75159133&env=usa

Is the user being routed back to Everett Tpke or onto Circumferential Hwy?

What’s the total length of the slip road?

Just looked at it - the total length of the ramps is 2236m - all ramps… The main road is named correctly - name & city.

User replied. They say it’s better to take Exit 2 to get on Route 1A (??? Would that be for Route 3A?)

I agree that the reporter meant Rte 3A. To confuse things, there is an Exit 1A after taking Exit 1 that would take drivers to Rte 3A (essentially, exit 1A connects the slip road to Exit 2).

So, we can surmise that the driver was headed from the Everett Tpke to Route 3A, and instead of sending the driver to Exit 2, Waze sent the reporter to Exit 1, then to Exit 1A to get to Route 3A.

I take Exit 2 as part of my daily commute every evening since I started using Waze 9 or 10 months ago, and Waze has never routed me this way.

I hope this helps.

Does Waze send you the correct way (Exit 2) or does Waze sends you the wrong way (Exit 1 -> 1A) on your daily commute?

Hi,

Waze always sends me the correct way (exit 2). Sorry if I was not clear.

Hi,

Would deleting this segment, then closing the gap, then prohibiting going straight from this segment solve the problem without causing new problems?

That will likely eliminate the second “keep right to Exit 1” instruction. So it depends on whether that is a problem or not.

Thanks, CBenson. I think the drivers would benefit from the second “Keep Right” instruction, so let’s not consider my suggestion any further.

I reported the problem. I travel to NH for work everyday. Normally, Waze directs me to Exit 4, occasionally, it directs me to Exit 6. This particular day, I went in an hour earlier and Waze directed me to get off at Exit 1. I thought it was going to send me down Spit Brook Rd but it directed me to stay left for Rt 3A and continued to direct me to Rt 3A. I was surprised by this since my preference is to take Exit 2 when I’m going to take Rt 3A. But hey, I’m game to follow Waze when I’m not in a hurry so I can see where it will send me. I think the direction to take Exit 1 to Rt 3A is not the best - unless there’s an accident at Exit 2.

Thanks!

This may have been a traffic routing and not a map problem at all.