695 Exit 13 to MD 144 closure

Moderators: jondrush, CBenson

Re: 695 Exit 13 to MD 144 closure

Postby CBenson » Mon Feb 10, 2014 3:11 pm

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.
Regional Coordinator: Mid-Altantic, US
Verizon, Droid Razr Maxx HD, Android 4.1.2, Waze 3.7.9.909
CBenson
Global Champ Mentor
Global Champ Mentor
 
Posts: 6890
Joined: Wed Nov 03, 2010 9:13 pm
Location: Crownsville, MD, US
Has thanked: 438 times
Been thanked: 991 times

695 Exit 13 to MD 144 closure

Postby elliottp » Sun Feb 09, 2014 9:38 pm

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.

Pictures of the signs.

Segment location on WME
elliottp
 
Posts: 56
Joined: Tue Feb 02, 2010 1:12 am
Location: Baltimore, MD
Has thanked: 13 times
Been thanked: 14 times

Re: 695 Exit 13 to MD 144 closure

Postby kodi75 » Mon Feb 10, 2014 12:15 am

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.
kodi75
 
Posts: 301
Joined: Mon Jul 02, 2012 3:43 am
Location: Central Maryland
Has thanked: 216 times
Been thanked: 45 times

Re: 695 Exit 13 to MD 144 closure

Postby kodi75 » Wed Feb 19, 2014 5:17 pm

A status update from SHA:
2/5/2014 CONSTRUCTION UPDATE - WINTER 2014

SHA and its contractor have closed the existing ramp from the inner loop I-695 to Frederick Road, 24 hours a day, seven days a week. This ramp closure is necessary for crews to construct a new interchange ramp on a new alignment to meet the width and height of the new Frederick Road bridge over I-695 and improve interchange ramp traffic operations.

Due to the unusually low temperatures and number of snowstorms this year, construction work at the ramp has been delayed. The ramp relocation work for the project will proceed once weather conditions permit.

Detour: northbound I-695 to Edmondson Avenue, exit 14, turn left onto westbound Edmondson Avenue, turn right onto the ramp to southbound I-695 and then exit onto Frederick Road.
kodi75
 
Posts: 301
Joined: Mon Jul 02, 2012 3:43 am
Location: Central Maryland
Has thanked: 216 times
Been thanked: 45 times

Re: 695 Exit 13 to MD 144 closure

Postby nzahn1 » Mon Feb 10, 2014 12:46 am

I physically disconnected and locked the ramp the week the closure started in 2013. I'm not sure what happened in the mean time.
Rank 3, Area Manager, 18K+ edits
Baltimore, MARYLAND Apple iPhone 5, iOS 7.1, Waze 3.7.8
Image Image Image Image Image Image
nzahn1
 
Posts: 305
Joined: Sun Apr 25, 2010 6:45 pm
Location: Baltimore, MD, USA
Has thanked: 113 times
Been thanked: 90 times

Re: 695 Exit 13 to MD 144 closure

Postby nzahn1 » Tue Feb 11, 2014 3:14 pm

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.
Rank 3, Area Manager, 18K+ edits
Baltimore, MARYLAND Apple iPhone 5, iOS 7.1, Waze 3.7.8
Image Image Image Image Image Image
nzahn1
 
Posts: 305
Joined: Sun Apr 25, 2010 6:45 pm
Location: Baltimore, MD, USA
Has thanked: 113 times
Been thanked: 90 times

695 Exit 13 to MD 144 closure

Postby trooster10 » Mon Feb 10, 2014 3:49 am

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.
Thomas R. - Level 4 Editor
Area Manager - Maryland's Eastern Shore
Apple iOS 7.0.3 - Waze 3.7.6
Maryland Wiki
trooster10
 
Posts: 231
Joined: Mon Apr 15, 2013 6:54 pm
Location: Baltimore, MD
Has thanked: 73 times
Been thanked: 36 times


Return to Maryland

Who is online

Users browsing this forum: No registered users