Written by Clay Johnson, Date 08/27/2009
Sources: http://sunlightlabs.com/blog/2009/dealing-inaccurate-government-data/
Noted by : http://www.egov.vic.gov.au
NB: We
promote also on this blog the reuse of EU data (the so-called PSI) by NGOs …
See: http://europa-eu-audience.typepad.com/en/1_registersregistres/
Developers are good at getting bits to line up, importing data and getting
great conclusions out of it. Designers are great at making things look great
and making those conclusions and bits easily digestible. But in all the apps
I've seen, they all ultimately suffer from the same fatal flaw: accuracy.
As developers we must not only focus on making compelling visualizations
and user experiences out of the data we pull out of government, but also make
the information we get as accurate as possible. We must do a better job
than government does -- and this is difficult, because we're taking inaccurate
data that comes from government.
Read more on http://sunlightlabs.com/blog/2009/dealing-inaccurate-government-data/
See also
DataMasher: Visualize and Share data.gov Data
http://infosthetics.com/archives/2009/08/datamasher_visualize_and_share_datagov_data.html
The Federal Register at your fingertips: http://govpulse.us/
What's
This We Know? http://www.thisweknow.org/
Our mission is to present the information the U.S. government collects
about every community. By publishing this data in an easy to understand and
consistent manner, we seek to empower citizens to act on what's known.
In
this first phase of development, we focused on a handful of nationwide data
sets from six different agencies in thedata.gov catalog. We picked data sets that each had
a spatial component. All the data sets were converted to RDFand loaded into a RDF database that serves as the foundation for this website.
Comments