Greater Greater Washington

Posts about Montrose Parkway

Roads


Montrose Parkway undermines White Flint's urban future

After 40 years of planning, an extension of Montrose Parkway through White Flint could soon become a reality. County and state transportation officials say the highway is needed to move cars, but residents and county planners say it contradicts their goal of making White Flint an urban center.


The existing part of Montrose Parkway. Photo by thisisbossi on Flickr.

Yesterday, the Montgomery County Planning Board recommended that the State Highway Administration and Montgomery County Department of Transportation change their plan to build a $119 million, 1.62-mile extension of Montrose Parkway from Rockville Pike to Veirs Mill Road. They questioned how it fits into the White Flint Sector Plan, which calls for the creation of a place "where people walk to work, shops and transit."

"It's hard to see this as consistent with a pedestrian-friendly environment," said Planning Board Chair Francoise Carrier, who lives near White Flint. "It detracts from our efforts to create a grid of streets ... it makes our transportation goals harder."

Work on Montrose Parkway began in the 1970's, when it was planned as part of the Outer Beltway, which was eventually built as the Intercounty Connector. Later, a portion of the highway's route between Veirs Mill Road and New Hampshire Avenue was turned into Matthew Henson State Park.

Planning for the current version of Montrose Parkway began in 1998 and resulted in the construction of the segment west of Rockville Pike, which opened in 2010. The Planning Board's recommendations, which aren't binding, will next go to the County Council for a vote. SHA officials say that construction won't begin for at least 5 years.

The proposed four-lane highway would have a stoplight at Chapman Avenue and overpasses at Nebel Street and the CSX railroad tracks. At Parklawn Drive, there would be a single-point urban interchange or SPUI (pronounced "spooey"), where drivers on Parklawn would stop at a light before turning onto the highway. A SPUI already exists at the junction of Falls Road and I-270.

SHA and MCDOT representatives insist that Montrose Parkway is needed to handle anticipated traffic from the redevelopment of White Flint. "If you build more density, you're going to have more traffic congestion," said Edgar Gonzalez, MCDOT's deputy director for transportation policy.

However, recent studies and local examples suggest that compact, mixed-use development like what's proposed here will actually reduce traffic, raising the question where MCDOT and SHA's concerns are actually valid.

Parkway would reduce east-west connections


Plan showing Montrose Parkway at Parklawn Drive if Randolph Road is closed.


Plan showing Montrose Parkway at Parklawn Drive if Randolph Road is open.

Since the latest plans for Montrose Parkway were first presented two weeks ago, residents have expressed concerns about the state's plans to close Randolph Road, a major east-west thoroughfare running parallel to the parkway, where it crosses the railroad tracks.

"One of the biggest problems in White Flint planning is the lack of east-west crossings," wrote Barnaby Zall last week. "We've been trying for years to figure out a way to bridge that gap."

SHA officials say it'll improve safety. The Federal Railroad Administration calls it the 4th most dangerous crossing in Maryland: there have been 21 collisions there in the past 35 years, including one death. Since 2007, there has been just one collision. Separating the road from the railroad tracks also means trains won't have to blow their horns when they pass through, something many neighbors have complained about.

Randolph Road would end in a cul-de-sac just east of the tracks, and anyone who wanted to go further west would have to get on Montrose Parkway. Chair Carrier worried that this would hurt access to shops along Randolph Road. "It would be hard to imagine that the businesses there would remain viable," she said.

Gonzalez said it could be a safety hazard. "You have to weigh the benefits [of access to Randolph Road] with the possibility of a future event occurring," he said. "Nobody wants to be in a train collision."

Nonetheless, board members voted to keep Randolph Road open at the railroad crossing, which planning department staff recommended because it gives travelers more options, reducing the traffic burden on any one road.

Debate over whether interchanges are "barriers"


Plan of the entire eastern segment of Montrose Parkway.

Much of the debate about Montrose Parkway revolved around the proposed interchange with Parklawn Drive. Board members worried it would become a barrier between White Flint and Twinbrook, making it difficult for people to walk or bike from one side to the other.

"We should rethink what we're doing in the context of the future land use of White Flint," said Planning Board member Casey Anderson. "We're not trying to build these huge slabs of asphalt that divide communities into pieces."

In the past, county planners have recommended putting a stoplight there instead. Former planning director Rollin Stanley argued that interchanges in White Flint "[reinforce] the view that Rockville Pike is a runway to get through White Flint versus moving through the area as a destination itself." Last fall, acting planning director Rose Krasnow wrote a letter asking MCDOT and SHA to consider it, but was rebuffed by MCDOT director Arthur Holmes, who said the interchange would "improve safety and reduce barriers by separating conflicting flows" of cars, pedestrians and bicyclists.

Likewise, Gonzalez said that an at-grade intersection, which would require that Montrose Parkway be 9 or 10 lanes wide to handle projected traffic, which would be just as bad for pedestrians and bicyclists.

Planner Larry Cole argued that it's because the county and state's plans are "overdesigned" and overestimate the amount of future car traffic in White Flint. "The reason [Montrose Parkway] is this big is that the space is available," he said.

Nonetheless, the board eventually voted in favor of keeping the interchange after officials from MCDOT and SHA promised to look at ways to make crossing the interchange safer and more pleasant for pedestrians, such as restricting right turns on red. The parkway will already have a 10-foot path for bicyclists and pedestrians on the north side and a 5-foot sidewalk on the south side.

Over time, the vision for White Flint has changed a lot. Forty years ago, the Outer Beltway was supposed to pass through it. Twenty years ago, the Planning Board sought to build multiple interchanges along Rockville Pike. Even the White Flint and Twinbrook sector plans, which are less than 5 years old, included the Montrose Parkway.

However, these neighborhoods are envisioned as urban places where people will be able to drive less, and to succeed it needs a street network where people feel comfortable and safe not driving, and Montrose Parkway as proposed could undermine that. The Montgomery County Department of Transportation and State Highway Administration work for pedestrians, bicyclists and transit users, not just drivers, and their plans for places like White Flint must reflect that.

Crossposted on the Friends of White Flint blog.

Budget


It's not Wheaton vs. Bethesda, but smart growth vs. bad

Montgomery officials say there isn't enough money in the capital budget to pay for both a new Bethesda Metro entrance and redeveloping Wheaton. But there is plenty of money, if only the county deferred some of the new and wasteful highways that will only worsen sprawl and shift the county's growth away from the places that can best accommodate it.


Downtown Wheaton. Image from Montgomery Planning.

Wheaton residents are eager for a redevelopment project which will bring new offices, residences, a hotel and a town square to the area around the Metro station. Meanwhile, to prepare for the Purple Line (and ease crowding today), the county needs to add a second entrance to the Bethesda Metro.

County Executive Ike Leggett's budget eliminated funding for the Bethesda entrance, and general services director David Dise told the Wheaton Redevelopment Advisory Committee that the county could probably not fund both the $40 million Wheaton plan and the $80 million Bethesda Metro south entrance.

Actually, it can, easily. And it can afford $12 million for the Metropolitan Branch Trail, which Leggett also cut from the current capital budget. All the county has to do is defer some of the $359 million in new highways in the 6-year Capital Improvement Program (CIP). That $359 million is all for new capacity, over and above the necessary cost of maintaining the county's existing roads and bridges.

The projects include widening Goshen Road, which costs $129 million, but the justification in the CIP suggests it's not needed until 2025. Building Montrose Parkway East, for $56 million, will further despoil Rock Creek Park, while the completed western portion has already created a "Berlin Wall" that will hamper a future walkable, mixed-use neighborhood growing north of White Flint.

Widening Snouffer School Road and Snouffer School Road North, 2 projects costing $45 million, would meet "demands of existing and future land uses" in an area which "is experiencing growth with plans for future residential and commercial development."

Why does the County Executive claim that it doesn't have enough money for the Bethesda Metro, a necessary step for the Purple Line in the part of the county that generates the most tax revenue, and Wheaton, a prime spot for new mixed-use growth and an already-thriving community right on top of another Metro station, but can spend money on new roads in car-dependent areas which may grow in the future?

These new road projects would increase traffic congestion through induced demand, offer no economic development, and destroy irreplaceable Chesapeake Bay watersheds. Montgomery County has already agreed, through long public debates, to make the Purple Line, the Metropolitan Branch Trail, and growth in Wheaton top priorities. But Leggett's budget does not reflect this.

This is an unfortunate pattern with this County Executive. The Leggett administration consistently cries poverty when it comes to smart growth-oriented projects like these, or making Rockville Pike a boulevard in White Flint. However, it seems that no sprawl-oriented road project is too expensive to fund.

Whether it's putting up roadblocks to BRT, pushing harmful skybridges and underpasses, or a bizarre focus on resurrecting bad "zombie road" proposals from the 1960s, the County Executive's decisions do not embody Montgomery County's and Maryland's stated smart growth policies.

Fortunately, it appears the County Council does not share the County Executive's misplaced priorities. A council committee has since voted to restore funding for the Bethesda Metro entrance, and the full council will consider it soon. The council should also restore funding for the Metropolitan Branch Trail.

Despite claims to the contrary, these worthy projects need not compete with each other. The council can simply choose the least valuable of the plan's many expensive road projects and use the money to ensure Wheaton, Metro riders at Bethesda, the future Purple Line, and a valuable bicycle connection from Silver Spring to DC get the attention they deserve. Our county, state and region cannot afford more delay.

Roads


White Flint's "Berlin Wall" will hamper White Flint II

Development in the White Flint area is getting underway. After completing a number of other Sector Plans for other areas of Montgomery County, next year the Planning Department will begin studying White Flint II, covering areas north, east, and west of the adopted White Flint Sector Plan.


White Flint phase I and II sector plan areas.

In some cases, the street grid and walkable development can just spread into surrounding areas. But to the north, the Sector Plan will run into a major constraint: the barrier created by the Montrose Parkway underpass. It is, in effect, White Flint's Berlin Wall.

Yesterday, I discussed the underpass (or overpass, depending upon which way you are traveling). The graphic below superimposes one of the sketch plans we received for a several-block area in the heart of White Flint over the area occupied by the Montrose underpass. It is apparent how much land the underpass "sterilized" for future growth, housing, revenue and more importantly, the real impact it has on the possibilities for the White Flint II area.


Image from Montgomery County Planning Department.

10 or 15 years from now, as White Flint hits its stride, there will be plenty of destinations drawing people into the area. Some will take transit, but most will drive. They will seek out parking and walk along new pedestrian-friendly streets lined with windows and activity. Many will work and live in this emerging community.

Rockville Pike near the underpass.
Will those same people look north to the White Flint II area and say, "Hey, let's go shop or eat over there?" And if they are making this decision, will they walk? No way. It will be a barrier. As the new streets and activities emerge in White Flint, they will not extend the grid across the underpass.

Would you really drive ¼ or ½ mile north and find a new parking spot in White Flint II to shop or eat? It's unlikely you'd find something there that will not already be in White Flint. And this is the challenge of White Flint II. What can it become? What can happen there that will make it distinct from White Flint?

This question would be different if the Montrose/355 intersection had remained at-grade. The street grid could have extended north to south. The building infrastructure could have created a seamless transition across the intersection, not much different than, say, Georgia and Colesville Road in Silver Spring. People could and would walk across the area into White Flint II because the transition would be lined with active uses day and evening.

The Montrose Underpass simply reinforces the view that Rockville Pike is a runway to get through White Flint versus moving through the area as a destination itself. Keep in mind that for a driver in a car to make eye contact with a pedestrian, they have to be travelling at about 23 mph (30 kph). So as long as we keep building our roads as expressways, we prevent the opportunity for "engaged" streets where a number of activities coexist safely.

So as we prepare to look at the White Flint II area, we have to take a hard look at what is possible. We have White Flint becoming known as NoBe (North of Bethesda), we have Rockville to the north, with White Flint II mostly in the middle. Will it be SoRo (South of Rockville) or can it establish its own identity? Can we expect the same demand for high-rise construction in White Flint II as in WF I? Will traffic modeling reveal that White Flint I occupies the bulk of the available and projected road capacity?

Or should we expect more like Twinbrook Station, a recent successful project north and east of White Flint at lower densities with a residential focus? Should this be the future of White Flint II, with splashes of retailing that are more convenience-focused than destination oriented? Will there still be a market for destination retail like the Container Store north of Montrose?

Several property owners own land both north and south of Montrose. How they lease south of the road in White Flint Iwhether to big box retailers or smaller retailwill have a big impact on what happens to the north in White Flint II. That model does not fit into the urban character of White Flint. Property owners will lease according to the market, and will avoid investments that compete with other uses in the area. This will not only impact the retail market but the residential market as well.

If White Flint I is to be higher-density condo and rental, there may not be enough market share for both areas in the next 15 years. Perhaps White Flint II will be about managing expectations, meaning it may take awhile for the collective vision to emerge. This is the approach that we are investigating for the Long Branch neighborhood, where the near and long term goals are differentiated by the actions we can take to create incremental change.

Maybe 20 years from now the Montrose underpass may be MoCo's elevated expressway. The mistake realized decades later in places like Seattle, Toronto and San Francisco, where lots of money was invested to reverse the damage and open up new opportunities for creating better environments for people, not autos.

Several years ago, a portion of the one elevated expressway that reached downtown Toronto was torn down, about 1.5 miles of it. Support is now building to take down the rest. This is one of the locations around the world where the benefits of tearing down 1950/'60s era transportation infrastructure has and will open up new economic opportunities that also meld well with the greening of urban areas.

There are lots of things to consider when we start the White Flint II Sector Plan.We hope for engaged conversations with property owners, residents and business operatorsall of whom will help guide the possibilities that White Flint II can be.

Crossposted at The Director's Blog.

Roads


White Flint interchange could have been a great place

Last week, I was invited to Boston by the Federal Highway Administration to talk about livability. Five years ago, would anyone have thought that would be possible?


Montrose Parkway at Rockville Pike. Photo by thisisbossi on Flickr.

Less than 1% of the $30 billion-plus spent on highway funding is currently spent on pedestrians. It seems like a huge ship we have to turn around. However, federal leadership through the EPA, HUD, DOT, and their joint Sustainable Commu­ni­ties Initiative, has created an energy that will bring a new direction to federal highway spending.

Can we translate that into a shift in local thinking as well?

When I arrived in Montgomery County in 2008, the White Flint property owners and members of my staff tried to divert $50 million in funding for the Montrose Parkway underpass, the first phase to reconstruct Rockville Pike, to study a future transit line along the Pike. Our efforts were unsuccessful. While I am sure many love to drive through the underpass, think of the missed opportunity.

I have driven the underpass on several occasions. Frankly, it is not that great. Connectivity is expedited in one directioneast-westbut getting off the road to head north or south is a pain. A regular at-grade intersection with turn lanes, appropriate signaling, pedestrian infrastructure and plantings would have been wonderful and much more effective for the broader public.

Image from Google Maps. Click for interactive map.

You can forget the pedestrian environment on the overpass. I watched a bike commuter ride across and was struck by how brave he was. With new condos just south of Montrose and major mixed-use development plans on the way in White Flint, the whole Montrose project works against what the new master plan is trying to create.

People do not walk over overpasses, they walk where there is something at the edge of the sidewalk that enlivens the space. Current and future residents will have to drive to the shopping north of Montrose if, as White Flint develops, they go north of Montrose at all.

Graphic from Montgomery County Planning Dept.
The graphic at right illustrates the point about the Montrose underpass. It shows the I-270/I-370 interchange overlaid on top of Bethesda's Woodmont Triangle.

The Rockville Pike/Montrose Parkway interchange sterilized huge tracts of land that could have been used to create a vibrant urban intersection with buildings framing the street, people on the sidewalks interacting along the street edge, traffic moving at effective speeds and with room for future surface public transportation.

Not doable, some say? I pass along the best example of a street designed effectively for both high motor vehicle traffic and high pedestrian activity: the Champs-Elysées. Think about it. This street has some of the most expensive shopping in the world. Cars stop along the curb to drop or pick up Europe's elite to patronize those shops.

There is a sidewalk that can best be described as too big, tourist numbers beyond comprehension, views that astound, trees galore, yet the road itself carries more cars per hour than many interstate highways. You can cross the Champs on foot at numerous signalized intersections, yet the traffic still moves, except of course on the last day of the Tour de France.


Champs-Elysées. Photo by David Forster on Flickr.
I am not saying the Montrose underpass should have been the Champs-Elysées, but it could have been an at-grade intersection that offered a terrific urban pedestrian experience. That would have also opened up land for development that has been consumed by roadways and created the urban experience White Flint needs while generating a heck of a lot more property tax for the county.

In Montgomery County, we are fortunate that both County and the State leaders are looking in a different direction.

Consider all the initiatives underway:

  • The growth policy the Planning Department advocated and that the County Council adopted calls for a part of impact fees assessed on developers to be dedicated to transit.
  • Zoning that assigns increased density for places close to basic services like groceries and dry cleaners.
  • Master plans like White Flint, the Purple Line plans for Takoma Langley Crossroads, Long Branch and Chevy Chase Lake, and the soon-to-be-released Wheaton and Kensington Sector Plans.
  • The state has their "ag print" and "green print" initiatives that are leading into the emerging Plan Maryland program which we hope will result in a rethink of the priority funding areas (areas of growth for each county).
  • Maryland DOT's leadership in funding infrastructure through smart growth is a national model.

In participating at the FHWA session, it became obvious that here in Maryland we are leading the nation in not only thinking about change, but in preparing for the future as well. It is a great time to be planning here in MoCo.

The Planning Department, the County Council and the state Departments of Planning and Transportation are in sync at many levels. Together we can shift the thinking from one of moving cars, to moving people.

Crossposted at The Director's Blog.

Roads


ICC Junior: Montrose Parkway

The multibillion-dollar Intercounty Connector may get the lion's share of attention, but it isn't Montgomery County's only major road construction project. And while the ICC's cost overruns have already threatened other transportation projects in Maryland, the other new expressway is still moving forward: Montrose Parkway.


Montrose Parkway construction. Photo by Joe Hatfield on Flickr.

Montrose Parkway is a partly controlled-access highway slated to run between I-270 and Viers Mill Road. The alignment for this highway occupies much of the right-of-way set aside for the original Outer Beltway, the precursor to the ICC. The western portion has already been constructed, splitting off Montrose Road just east of the I-270 interchange and ending on Old Georgetown Road just west of Rockville Pike (MD-355).

The planned eastern portion will run underneath Rockville Pike, connecting with an interchange (a SPUI, I believe), veer north from Randolph Road along a stretch of undeveloped land, and end at the Veirs Mill Road intersection with Parkland Drive. Construction has already begun, creating traffic jams on Rockville Pike.

The Parkway will dump freeway-like traffic onto Parkland Drive, a two-lane street through a low-density residential neighborhood. This will no doubt lead to excessive traffic on Parkland Drive and Aspen Hill Road, another minor artery through the neighborhood that intersects Parkland Drive before it ends on a side street a few blocks north. Effectively, what Montrose Parkway will do is ease traffic at on intersection and move the problem into a residential neighborhood.


Red: Existing Montrose Parkway. Blue: Currently planned portion. Peach: Original Outer Beltway alignment. View larger map.

I don't think a road here is a bad idea in theory. If constructed with community involvement, it could connect disjointed neighborhoods and serve walkers and mass transit. But if constructed as a quasi-freeway, it will only induce more car trips, not relieve traffic. Randolph Road, which Montrose Parkway will supposedly relieve, will not likely see a decline in automobile trips, since the county plans to build a new interchange at Georgia Avenue, while Montrose Parkway has no direct access to Georgia.

I have a bad feeling that this situation will result in a call to continue the parkway east along the old Outer Beltway plan to the ICC. Residents of the Aspen Hill neighborhood, through which Parkland Drive runs, will certainly not put up with freeway-density traffic through their quiet residential streets. They might lobby to continue the parkway east through Matthew Henson State Park (a swath of trees originally set aside for a freeway) to Connecticut Avenue (where exit ramp stubs still exist from the Outer Beltway planning days), then Georgia Avenue, Layhill Road, and on to the ICC.

A road along the route of Montrose Parkway could better connect communities east to west across Montgomery County. As currently deesigned, though, it could wind up being a spur off the ICC, partitioning the landscape with a freeway. And considering the lack of attention the construction of this road has received in the shadow of the ICC debate, that is a frighteningly likely possibility.

DC Maryland Virginia Arlington Alexandria Montgomery Prince George's Fairfax Charles Prince William Loudoun Howard Anne Arundel Frederick Tysons Corner Baltimore Falls Church Fairfax City
CC BY-NC