Okay, I see that exit 49C is closed and traffic to I-66 W should use exit 49A. I have thus marked the left exit ramp as no entrance. Someone who is more familiar with the construction should feel free to delete it.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
I was surprised to see that this has been reconnected. Can anyone who frequently drives through this construction confirm that the ramp remains closed or whether it has been reopenned or replaced?
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Mike-1323 did the reconnect. I've PMd him and asked him join this discussion. I have no news or DOT info beyond the discussion of the closing of the ramp. The gps points are still there from the old ramp. The reconnected ramp follows the gps points.
I don't really think there is to be a new ramp. If I understand correctly, Lexus lanes are being added to this section of the Beltway and the new bridge is to service the Lexus lanes.
I don't really think there is to be a new ramp. If I understand correctly, Lexus lanes are being added to this section of the Beltway and the new bridge is to service the Lexus lanes.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Given that the update request was submitted 5 days after the last edit to ramp, I have gone ahead and disconnected the ramp again. If anyone has information that this is incorrect, please bring it forward.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Manorbe(6) reconnected it. I really wish we could annotate the edit map to explain why changes have been made.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
I've gone ahead and disconnected it again based on the following from Manor:
Hi carl,
The ramp was reconnected because of a reoccurring navigation problem.
according to the gps points there was movment on that ramp in the past few weeks, in addition users navigated through that ramp (thus creating the navigation problems), so based on that information the ramp should be connected.
we are not aware of any construction work on that ramp nor do we check for these type of things, we rely on waze users to update the map because they
pretty much knows what's best.
if the ramp is closed for any reason feel free to disconnect it again, i will make sure that we wont reconnect it again.
Kind Regards,
Manor.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Thanks for the confirmation. We'll see if we can keep it disconnected.
Being on the other side of DC I really can't keep track of all the construction in Virginia.
Being on the other side of DC I really can't keep track of all the construction in Virginia.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
See my PM. For some reason I was able to unlock the critical segments.
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Hey, it looks like this interchange is changing again on Saturday. Does anyone drive through there enough to map the new configuration?
Regional Coordinator: Mid-Atlantic, US
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
Verizon, Nexus 6, Android 6.0.1, Waze 4.7.0.902
I'm sensing a little negativity from the mighty 'Berg today!
Re: ASAP - I-495 intx I-66 in Washington, DC Area