Anonymous wrote:
Anonymous wrote:
Anonymous wrote:
Anonymous wrote:
Anonymous wrote:
Anonymous wrote:
Anonymous wrote:
Anonymous wrote:I say this as someone who usually aims to get to the airport 60 mins before a flight and am often not there until 50 mins before (takeoff, not boarding time).
I would plan to be there by 10am. There is SO MUCH that can go wrong with your transit, there may be increased security, etc. I wouldn’t mess around tomorrow.
Saturday is by the quietest day at DCA. OP will be sitting around for 4 hours with this advice. I agree it will probably take longer than normal and OP may have to cross the river on the beltway and maybe come in on 66 and then snake around the Pentagon, but this is over the top.
OP, just pull up Waze at say 11 AM and see how long it is taking to drive to DCA. I am willing to bet it will be 10 minutes longer than normal because of the redirections. Regular people will not be anywhere near the central part of the area tomorrow, most roads will be quieter than normal.
And if you look for 9 PM on Sunday, it says "typically 30-40 minutes" and suggests going via GW Parkway.
Do not listen to this person. They are wildly incorrect with their assumptions about tomorrow.
Right now Google Maps says 40 minutes drive from downtown Bethesda to DCA Terminal 2. I will check at 11 AM tomorrow, and will post back here, and take my blows if it's more than an hour. If I had the ability, I would easily bet $5k at even odds it will.be under an hour.
And you’re absolutely positively sure that Google Maps is taking the parade and the military celebrations into account, as well as the as-yet uncounted numbers of people who may be unfamiliar with area roads in making this estimate? If so, hats off to Google Maps.
They use live data from actual travelers, so yes.
OK I'm really curious about how this works - live data is for today, correct? How would they anticipate what the traffic will be 24 hours in the future?
Yes live data is based on people who have Google Maps running on their phones, it collects the GPS data as they drive, calculates speeds, collects it all to show lower speeds than normal, etc.
Projections for the future generally give you a range of time based on historic data for that day/time. But yes that's why it would be hard to tell what tomorrow will look like, because it won't be a normal June Saturday. Hence the need to look tomorrow at the specific time.
If you look right now for noon tomorrow, it says "typically 28 minutes to 1:05" and yes, does show a proposed route that avoids the GW Parkway where it is closed tomorrow.