in Newton, the discussion about parking in new developments is going in circles*. There’s a way out: stop worrying about on-street parking capacity.

Here’s how it goes. A developer files for a special permit to build more housing near transit. City councilors and their allies for whom fighting climate change and adding housing are priorities say there’s too much on-site parking in the plan. Cheap and convenient car storage leads to more driving. Other councilors and near neighbors say there’s not enough on-site parking. Without enough parking on-site, both residents of the new building and their guests will use already limited on-street parking in the area, at the expense of the existing neighbors. Still other councilors note that if there’s too much on-site parking, it’s not really transit-oriented development, and, therefore, there’s no need for as much housing.

Neighborhood concern about on-street parking results in too much off-street parking, which results in this precious commodity — homes near transit — being taken by folks who aren’t inclined to use transit, diminishing the positive impact of transit-accessible housing on climate change.

This conversation plays out again and again, most recently at 967 Washington St., a proposed 28-unit condo apartment building that is before the City Council as a special permit petition. (Six of the units will be permanently affordable.) All three arguments were made in the course of Land Use committee meetings on the petition.

Building excess parking capacity is not good. Access to convenient parking is correlated with higher car use. The cost to build parking, especially if it is underground or partially underground, drives up the cost of the housing the parking supports. Basic spatial limitations means that parking requirements act as a practical limit on the number of homes that can be built on a given property.

In Newton, there seems to be consensus that we need to build housing near transit to allow those who have transit-accessible jobs to avoid a car commute. And, since our transit is also near village centers, what would otherwise be car-trip generators, like groceries and schools, are accessible by foot. But, if we build too much parking, those who can and want to live car-free or car-lite compete for homes against those who need or choose to drive, wasting the opportunity to reduce motor vehicle travel. A common refrain from councilors objecting to the scale of projects like 287 Washington St.: this isn’t transit-oriented development, because there’s too much parking. Fair point.

Of course, the issues compound. If the city required less parking at a development like 967 Washington, there could be more homes overall and a greater percentage would be taken by those who need to drive less. 

There is a downside to providing less on-site/off-street parking at a new development: if on-site parking is insufficient, residents of the development and their guests may/will park on the street. There’s a fixed amount of on-street parking. And, neighbors typically don’t want to give up that on-street parking. They either use it themselves or they don’t want the street parked up. Or, both.

The desire to protect the available on-street parking is understandable. If you’re used to being able to park on your street and used to there being an available spot pretty much all the time, having to compete with new residents and their guests for those spots is going to be a pain in the ass. Who wants that?

But, if we’re going to get the climate benefit of housing near transit, we’re going to have to make hard choices and sacrifices. In this case, we’re just going to have to stop worrying about on-street parking. It’s a fixed resource. And, we’re going to run out of it. So, we might as well accept that and move on. Because, until we have no more available on-street parking, limits on off-street/on-site parking won’t generate the kind of transit-oriented development we need: households who choose to live near transit and near village centers and drive a whole lot less.

My wife and I used to live in the South End. The two-building complex had probably a space for every two or three apartments. The spots were leased and wicked expensive. For about half the time we lived there, we had no car. We just walked, biked, and used the T. At some point we decided to buy a car. And, parking it was a huge hassle. We’d sometimes drive around for 30 minutes to get an on-street spot. Though we didn’t sell the car, we regretted owning it.

If either my wife or I had had a job that wasn’t walk-,bike-, or T-accessible, we would not have moved to the South End. If developments like 967 Washington St. aren’t forced to include too much parking and the neighborhood on-street parking gets used up, then prospective residents will do a similar calculus and self-select in or out. 

The perceived need to protect an inventory of readily accessible on-street parking spaces acts as a block to meeting our climate objectives. The solution is to enact parking maximums for developments within a reasonable walk of transit. Until then, councilors need to decide which is the higher priority: protecting the globe or protecting neighbors’ access to convenient parking, which enables convenient driving. 

Seems like a no-brainer.

A note about the need for commercial parking. As we build more housing around village centers, village-center businesses will need to rely less and less on people who come to village centers by car. But, during this transition, we’ll continue to need need parking for business patrons. Parking regulations can ensure that at least some of the fixed inventory of on-street parking is available for shoppers, diners, and other customers. Which might mean less is available for residents and their guests. Which would be a good thing. See above.

* The allusion is intentional. If you know, you know.