| Feed me your cars! Photo by Alan Durning. |
News Roundup: June 17, 2013
Do remote state capitals produce less effective governments?
Last month, the Atlantic Cities reported on a very interesting study by Harvard researchers linking the distance of state capitals from major population centers to corruption. Generally speaking, the more remote the capital, the more corruption there was in that state (as measured by federal convictions). As ever, correlation is not causation and there are plenty of outliers, but the findings are intriguing nonetheless.
They also got me to thinking: beyond its potential role in facilitating the occasional corrupt act by an individual or small group of individuals, could the isolation of state capitals have an impact on the average quality of all bureaucratic talent? Corruption is obviously a big deal, but usually limited in scope; a systemic under-recruitment of talented, ambitious public employees at the state level could have far more devastating effects in the long term.
To see why our remote capitals might be doing a disservice to good governance, we don't even need to look at government employment. To some extent, publicly- and privately-owned businesses are already responding to the heightened attraction of the "major population centers" those Harvard researchers were referring to: Twitter decided to locate in San Francisco, Google put offices in New York City, Amazon is rapidly expanding operations in the core of Seattle. These are expensive markets, and superficially it might seem like a waste of money, but these major corporations have reached the conclusion that they need to be located in dense, walkable, transit-rich cities if they want to attract the talent they need to continue to be successful. Why should it be any different for state employees?
Of course, there are plenty of highly qualified and capable people that actually prefer to live in the smaller-city/suburban atmosphere. That's fine. In cities like Albany or Olympia or Sacramento, though, you're significantly limited in the type of lifestyle you can lead. It's basically suburban car-dependence or bust. And while there are many millions of people who want exactly that, there are as many or more who don't want anything like it, or at least wouldn't rank it highly if they had complete freedom of choice.
Austin's urban capital building in the background. (source)
Large cities, on the other hand, can provide a place for a much larger group of people with a much broader set of interests. The woman who wants to live downtown and spend her leisure time in coffee shops and bars, and seeing live music and poetry readings is free to do so; the man who wants to spend most of his time in his room blogging and reading (ahem) but values the convenience of a grocery store down the road and work within bicycling distance can get what he wants; those that do want the two-car garage, front and back yards, and relative seclusion of the suburbs can always find it without venturing too far. If you can capture a wider swathe of the population (both demographically and in absolute number) in your commute-shed (if that's a word) then you can pick from a larger pool of applicants for your Auditor's office, Liquor Control Board, Department of Health, and on and on. Some of those applicants wouldn't have been interested if the job had been in a remote town, and some of those will be extremely good at their jobs.
The method by which you might study this question is something I'd be interested in hearing from readers about. How do you measure the impact of a more effective workforce? Per-capita income or population-adjusted GDP seems like an obvious choice, but it's likely that if the distance of capitals has any impact it's on the order of a few percentage points of growth and could easily be swamped by other internal or external factors (like a giant recession, for example). And what's the control group? There are also definitely potential benefits like better institutional design that improves responsiveness to constituent concerns or higher quality web sites (read: http://www.altcew.org/), neither of which would necessarily show up in the state's economy but would improve people's lives nonetheless.
One additional note: I just want to make it clear that I'm not saying our current public officials are underqualified or generally doing a poor job--this isn't a critique on existing bureaucratic efficiency or effectiveness at all. In the spirit of this blog's name, it's simply a recognition that things can always be better, and we should be open to considering anything that might fulfill that mission.
News Roundup: June 14, 2013
News Roundup: June 12, 2013
34th and Stone: the Burke-Gilman's most dangerous intersection?
The Burke-Gilman trail is an incredible transportation and recreational resource for the city of Seattle. Not only do I (along with hundreds if not thousands of others) use it nearly every day for commuting to work from Ballard, I also credit it with getting me back into riding my bicycle several years ago. Jumping straight into riding the streets of Seattle was daunting after growing up in the suburbs and not getting on a bike since my sixteenth birthday; the Burke-Gilman offered me a safe, comfortable place to regain my skills and ultimately opened up the rest of the city to me and my bike.
With special concern for newer riders, and those who are just new to the Burke-Gilman, I have to draw attention to the very unsafe conditions in Fremont at North 34th St and Stone Way. Anyone who's biked through here is probably familiar with the problem. I was motivated to write this post after seeing a bicyclist come within a few inches of being hit by a taxi today, and while I'm tempted to blame the generally manic and dangerous driving of cab drivers here, the fact is that neither the driver nor the bicyclist really did anything egregiously wrong. To see why, we need to look at the intersection.
First, here's the view headed westbound on the Burke Gilman:
I've marked the lanes in question with letters: the space below the "A" between the fence and the dark building is the Burke-Gilman trail, and the space below the "B" is the eastbound car lane. What you can probably gather from this image is that the people going eastbound on the Burke-Gilman (i.e., toward me, traveling down the "A" lane) can't see what's going on in the "B" lane as they approach the crosswalk.
The following image illustrates the scale of this blind spot even better:
For more than 100 feet the bicyclist is unable to see what's going on in the car lane, and vice versa. The problem is actually worse than that, since the car lane is at a higher elevation than the trail up until the building blocks the view, so neither drivers nor bicyclists have any idea what to expect until they get to the crosswalk. And as I highlighted in the above image, the bicyclist is sometimes being told during the length of this blind spot that he or she is cleared to ride through the crosswalk.
Here's what it looks like from the eastbound car lane, at the stop line on 34th St. at Stone Way:
The reason this is a problem, of course, is that crosswalk signals tend to say "walk" when the parallel vehicle lanes's traffic lights are green, so cars can and do take right turns through the crosswalk while bicyclists and pedestrians are using it. And although I'm sure it's technically illegal for a car to take a right turn through a crosswalk without taking due care to look for pedestrians and bicyclists, in practice this isn't done very easily; drivers really can't see who might be coming up from behind that Solsticio building without already starting to encroach on the crosswalk. I'm certainly not trying to defend their actions, but this is at least partially the fault of the road design making it very difficult to see potential hazards (i.e., people).
On the flip side, some of the blame goes to bicyclists who don't slow down enough while moving through the crosswalk. (I'm guilty of this.) Even with a walk signal it's a very risky move to roll through a crosswalk at 15 mph or more when cars just a few feet away have a green light to pass through the crosswalk. We can get indignant about the fact that we have the greater right to the space, and we probably should, but that doesn't change the fact that if there's a collision we're the ones getting hurt.
Currently, the crosswalk signal only says "walk" for a portion of the time that the parallel car lanes are green, so in theory bikes and pedestrians get their chance to get through then cars get theirs. In reality this is a very busy, often backed-up road for cars, and if they see what looks like a clear crosswalk during the walk signal period they're usually going to go for it. If it hasn't happened already (and I'd be very surprised if that were the case), it's just a matter of time before someone is hit and possibly seriously injured. And it's especially likely to be a bicyclist who doesn't know to be wary of cars they can't see until the last minute. Something needs to be done.
What should it be? I'm not sure. Because of the amount of traffic on 34th St during rush hours and the lack of a right-turn-only lane it seems unlikely that we'll see any kind of partial limitations on right turns--if they were prevented until the crosswalk signal said "stop" you'd end up with the one driver waiting to turn blocking dozens of cars behind him for half the duration of the green light. I don't honestly care what the solution is as long as it works, but the first idea that comes to mind is to eliminate all right turns from the eastbound lane of 34th St.:
Alternate route for 34th St drivers, along N Northlake Pl.
At worst this would divert drivers a few blocks, and, based on my own anecdotal experience, many of them are headed east of Gas Works park (which starts at the bottom right of the above map) anyway. A possible compromise could be engineered in which drivers can take a right at Stone Way during the car-only phase but must travel through otherwise, but that might be overly complex.
Regardless of the solution, the city needs to take a look at this and start work on a solution. If the several near-misses I've seen in the past few months are any indication, the status quo is a serious accident waiting to happen.
News Roundup: June 10, 2013
How To Calm The Urban Parking Wars (Slate)
Report: the FRA makes trains less safe, more expensive (Vibrant Bay Area)
News Roundup: June 06, 2013
Why Conservatives Hate Citi Bike So Much, in One Venn Diagram (NY Mag)
Dual court rulings reaffirm Bloomberg taxi service goals, consumers benefit
Taxi service in NYC just got a lot better thanks to a couple of appellate court rulings, clearing the way for an additional 18,000 livery cabs to serve northern Manhattan and the other boroughs, and the use of smart-phone apps to better connect riders to drivers. From the New York Times:
As early as next month, thousands of the newly designated taxis — bearing fresh apple green paint, new roof lights and taximeters — will begin to descend on neighborhoods where yellow cabs rarely visit, addressing an inequity that has existed for decades. [...]
The ruling, which overturns a lower-court ruling that had stalled the action last year, also clears the way for the city to generate as much as $1 billion by auctioning off 2,000 medallions for wheelchair-accessible yellow taxis; the measure required that 20 percent of the livery vehicles be wheelchair-accessible.
Predictably, the Metropolitan Taxicab Board of Trade, which represents taxi fleet owners who benefit financially from caps on the total number of taxi cabs, does not approve. More from the NYT:
And many yellow-taxi operators, disinclined to share street hailing with livery cabs, have challenged the plan since its inception. The Metropolitan Taxicab Board of Trade, a plaintiff in one of the suits, called the decision “a crushing blow to New Yorkers who loathe the brand of end-run politics that created this law.”
“The court’s finding that somehow hailing livery cabs in the Bronx is a ‘matter of substantial state interest’ — code words that were used to bypass the New York City Council — is alarming,” the group said in a statement. “The ruling kicks open the door for systematic abuses for future executives in cities throughout the state, but particularly in New York City.”
Their arguments refer to how the Bloomberg administration brought their case to the state when the city council shut down their plans to expand taxi service, and it certainly is unfortunate that things had to go that route. But note something very important: there's nothing in the Metropolitan Taxicab Board of Trade's complaint about the impact of these rulings on consumers--all they talk about is "end-run politics" and "open[ing] the door for systematic abuses".
And why is that? Because this is a huge win for consumers and the taxi fleet owners know it. They can't very well say, "Shucks, people in Queens are definitely going to get better service and the drivers are going to be better paid at more consistent rates, but... but... our profits!!!" The fleet owners are the only ones who really benefit from an artificially limited supply of cabs, so doom-saying it is.
The taxi business is one of the most highly (and unnecessarily) regulated and uncompetitive service sectors in the country, and this is introducing a little bit of competition into that system, in New York at least. It's very likely that fleet owners will lose out a bit as a result of these rulings, and perhaps even taxi drivers themselves, who already make far less money than they deserve. I think most people would agree that the benefit to the 8 million people living in NYC and the millions more who vacation or work in the area exceeds the losses of the taxi industry--and if you're concerned about the taxi drivers themselves (as you probably should be), then your real qualm is with the medallion system.
Taxi medallion price appreciation since 2004, from Carpe Diem.
News Roundup: June 05, 2013
Report: The New Majority is Pedaling Toward Equity (League of American Bicyclists)
Behind the Rise in House Prices, Wall Street Buyers (New York Times)