Hello, I noticed that exit 13 is closed on the innerloop of 695. Someone named it “closed” on the editor, but the app still routed me that way. I checked and there is no turn restriction on that ramp. I marked it as closed on the app. Perhaps an L3 editor can change the turn restriction because I find that the in app closures are not ‘sticky’ very long.
I did see that last Sunday driving to old town Ellicott City, but Waze was already routing me via Wilkens so I thought the Frederick Rd ramp had already been taken care of.
I placed a 24/7 restriction on the ramp.
Do you know when it will re-open? The SHA Project page is vague.
I physically disconnected and locked the ramp the week the closure started in 2013. I’m not sure what happened in the mean time.
This was my doing - see the MD construction thread for a few posts on this. A CM contacted me about this specific ramp, and told me that I needed to reconnect segments like this that we’ve disconnected due to construction, and instead use full-time segment restrictions, since Waze was going to start flagging these gaps (not sure exactly what he meant). I was skeptical that users could still be routed along it, but I made the changes to appease him and see if it would work since it’d make opening/closing segments a little easier. Thankfully I only did this in one place since it clearly didn’t function as intended. Do we think that adding the turn restriction will be enough, or do we need to disconnect it again?
Also, I don’t know when the ramp will reopen. The 3-week closure has lasted 2 months.
I not sure I understand the problem with disconnecting the road even if waze is going to flag the gaps. Flags would be for editors to verify if there is a problem, not necessarily to indicate that something must be changed. I’m not convinced that turn restrictions or time based restrictions are the way to go as there are conditions when waze will route through both.
Drove thru the area last night and tried for get waze to route me on the ramp. I wasn’t allowed. Just a anecdote, but it appears the turn/type restriction is working; for now.
I still prefer the disconnect route.
In addition, I would have preferred to “pave” the new road rather than guesstimate. I prefer ground truthed data.
A status update from SHA: