<html> <head><style type ="text/css">body { font-family: "Bloomberg Prop Unicode I", Verdana, sans-serif; font-size:125%; letter-spacing: -0.3pt; color: #FF9F0F; background-color: #000000; text-align: left; } p {line-height: 1.25em; max-width:900px; width:expression(document.body.clientWidth > 900? "900px": "auto" );} h1, h2, h3 { text-align: left; font-weight: normal; color: #FFFFFF; } h1 { font-size: 130%; } h2 { font-size: 115%; } h3 { font-size: 100%; } #bb-style { font-size: 90%; max-width:900px; width:expression(document.body.clientWidth > 900? "900px": "auto" ); } b, strong { font-weight: bold; } i, em { color: #FEC54A; } pre { font-family: "Andale Mono", "Monaco", "Lucida Console"; letter-spacing: -0.3pt; line-height: 1.25em; } table { border: 0; font-size: 90%; width: 100%; margin-left: auto; margin-right: auto; } td, tr { text-align: left; } td.numeric { text-align: right; } a:link { color:#53B2F5; text-decoration: none; } a:visited {color:#53B2F5} a:active {color:#53B2F5} a:hover {color:#53B2F5} </style> </head> <body> <p>By Josh Barro</p> <p>When I wrote last month about the Census Bureau's <a href="http://www.bloomberg.com/news/2012-06-21/should-the-federal-government-be-more-like-wawa-.html">horrible website,</a> I got a lot of messages from other reporters and policy researchers agreeing that Census.gov makes them want to tear their hair out.</p> <p>But it gets worse! Today, I learned that the new version of American FactFinder -- just one borderline-unusable section of the much larger universe of brain-melting user experiences that is Census.gov -- was developed by IBM at a <a href="http://www.politico.com/blogs/charlie-mahtesian/2012/07/factfinder-price-tag-million-128699.html">cost to taxpayers</a> of $33.3 million. Census has a website that isn't just terrible, it's also extremely expensive.</p> <p>But there is one ray of hope: After I wrote my initial post, I got an e-mail from a public affairs officer at Census, highlighting the bureau's launch in May of an application programming interface (API) that will <a href="http://www.census.gov/developers/">allow outside parties</a> to build alternative front-end systems for accessing Census data. You can think of this as Census admitting that it's bad at websites and allowing outside entities to take over its web development.</p> <p>For example, the Brookings-Urban Tax Policy Center has a tool called the <a href="http://slfdqs.taxpolicycenter.org/">State and Local Finance Data Query System</a>. All the data available in SLFDQS come from Census, but unlike the Census website itself, SLFDQS is easy to use. The problem is that TPC has to manually update SLFDQS every time there is a new Census of State and Local Governments release, which is labor intensive and results in a data delay. With an API, SLFDQS could access Census data directly and automatically, and tools like this could become more popular.</p> <p>Unfortunately, the data currently available through the API are very limited. But if Census expands this tool, eventually we could all be freed from the need to struggle with Census.gov, and Census wouldn't have to overpay IBM for any more terrible websites.</p> <p>(Josh Barro is lead writer for the Ticker. <a href="https://twitter.com/#%21/jbarro">Follow</a> him on Twitter.)</p> <p>Read more breaking commentary from Josh Barro and other Bloomberg View columnists and editors at <a href="http://www.bloomberg.com/view/the-ticker/">the Ticker</a>.</p> <p> </p> </body> </html>