Wednesday, January 27, 2010

Prufrock

Let us go then, you and I,
To a deluxe apartment in the sky.

-T.S. Eliot meets The Jeffersons

Thursday, January 21, 2010

SD-FO ought to STFU

The next person who mentions the terms "structurally deficient" or "functionally obsolete" in my hearing will be punched in the mouth.

From talking heads on cable news to engineers and policymakers who really ought to know better, misuse of these terms has been rampant since at least August 2007. Let's set things straight with a healthy dose of facts and the not-so-subtle threat of violence.

Structurally deficient (SD) means that load-carrying elements of the bridge have been rated as "poor" or worse (4 or below on the National Bridge Inspection Standards scale of 0-9, where nine is brand-new and zero means the bridge has fallen into the river) or that the waterway opening provided by the bridge is inadequate1.

Functionally obsolete (FO) means the bridge is inadequate from the perspective of roadway geometry issues1 (traffic capacity, roadway shoulder width, and approach sight lines, for example).

Let's examine the abuse of these terms in detail:

First, and most importantly, SD and FO are planning, not structural engineering, terms. They do not necessarily reflect the safety or serviceability of a bridge. Bridges designated as SD or FO get higher priority for repair and rehabilitation. As a consequence of this, it can actually be good for a county engineer to have a bridge designated SD or FO - state or federal money may then become available.

Structurally deficient is not a synonym for "unsafe" or "near collapse." Recall that the SD designation is based upon a load-carrying element being rated 4 or below on the National Bridge Inspection Standards (NBIS) scale. 4 is basically the lowest rating at which an element can be left in place as-is. You have probably driven over a bridge with an element rated 4 within the last seven days. That doesn't mean your life was in danger.

Reporting the sum of SD and FO bridges is especially meaningless from a bridge safety perspective. I can't tell you how many presentations I've attended where the first words from the speaker's mouth were "Since X percent of the nation's bridges are structurally deficient or functionally obsolete..." - from a safety perspective, this is about as meaningful as saying "X percent of the nation's bridges are painted green." FO has absolutely no structural safety meaning. A bridge can be rated FO because its shoulders are too narrow, or because it has an old-style guardrail. That doesn't mean the bridge is going to fall down. One very common cause of an FO designation is that traffic has increased on the route carried by the bridge. A bridge can be deemed FO even if it has a good structural rating of 7, 8, or 9. So, while FO bridges ought to be upgraded or replaced to maintain good levels of service throughout the network, an FO designation doesn't provide any more indication of a bridge's safety or serviceability than the color of the bridge paint. If you're trying to make a point about structural capacity, don't inflate your numbers by counting FO bridges too.

The federal definition of a "bridge" is any structure with a clear span of at least 20 feet2. That includes everything from the Golden Gate Bridge down to structures that are little more than oversized culverts. The SD and FO criteria may be applied to any structure in this spectrum. When we refer to the number of SD/FO bridges, an outdated bridge on a low-volume county road counts the same as the heavily traveled (and both SD and FO) Milton-Madison (Kentucky/Indiana) Bridge, a regionally important Ohio River crossing which, if out of service, necessitates a detour of 55 miles. Of the 600,000 or so bridges in the United States, the vast majority are "boring" bridges with relatively short spans and lots of built-in redundancy. That means that even if a structural member is deteriorated, there is still enough load capacity too keep the bridge in service.

Bridge collapses are shocking in part because they're so rare. Regular inspections in keeping with the National Bridge Inspection Standards help keep them that way. Yes, we should be sure that bridge maintenance and inspection is adequately funded; yes, research into improved methods for structure evaluation and testing should continue - but there's no reason to panic over big numbers with scary-sounding sames that ultimately have little meaning from a safety perspective.


1. Federal Highway Administration: Bridge System Conditions - Explanation of Bridge Deficiencies

2. United States Code: 23 CFR 650.305 (2009).

Wednesday, January 13, 2010

Flags: District of Columbia

I am pleased to write about a flag that is doubly special: (1) it is the flag not of a state of the Union, but the Federal District, and (2) I am currently in this District. I love when my travel schedule aligns with my geographic nerdosity.

The authorization for a special federal district, not to be a part of any state, as the seat of national government was laid out in Article I, Section 8 of the Constitution, which grants the Congress authority

To exercise exclusive Legislation in all Cases whatsoever, over such District (not exceeding ten Miles square) as may, by Cession of particular States, and the acceptance of Congress, become the Seat of the Government of the United States, and to exercise like Authority over all Places purchased by the Consent of the Legislature of the State in which the Same shall be, for the Erection of Forts, Magazines, Arsenals, dock-Yards, and other needful Buildings;

Conveniently, the Constitution now spends most of its time in "such District." Now, I once thought that the creation of the Federal District was mandated by the Constitution, but the excerpt above suggests that Congress was allowed, but not required, to establish a seat of federal government distinct from any state. Anyway, the Federal District was established along the Potomac River, on land ceded from Maryland and Virginia - though Virginia got its cession back in 1846. Until then, the District of Columbia had been divided into two counties: the county of Washington on the north bank, and the county of Arlington on the south. Similarly, there were multiple municipalities in the District: until 1871, letters could be properly addressed to Georgetown, DC. The Organic Act of 1871 unified the City of Georgetown, the City of Washington, and the County of Washington into a single legal entity, the District of Columbia.

So, while DC as we know it came into existence in 1871, it wasn't until 1938 that it adopted its spiffy red-and-white flag. The banner is based on the three stars and stripes from the shield on George Washington's family coat of arms. I heartily approve - it is instantly recognizable, and simple enough for schoolchildren to draw. The citizens of the Federal City seem to dig it - it appears on non-governmental logos and is flown from non-governmental buildings throughout the District.

The official motto of the District - Justitia omnibus ("Justice for all") - and the license plate slogan, "Taxation Without Representation," are not-so-subtle digs at the governance of the Federal City. Citizens of DC have a non-voting delegate in the House of Representatives, and only won the right to vote in presidential elections in 1961, with the ratification of the 23rd Amendment to the Constitution (they didn't actually get to vote until the presidential election in 1964).

As far as I can tell, the selection of the wood thrush (Hylocichla mustelina) as the official bird, or the scarlet oak as the official tree, of the District carries no specific political message. Too bad.