FHI 360, 1825 Connecticut Ave NW #2, Washington, DC 20009
Your organizers are Josh Tauberer, Eric Mill, and Julia Bezgacheva. Please find us if you need anything.
Election-Year APIs, by Lindsay Young (Sat 10:15)A brief overview of API basics, followed by an in-depth look at the FEC API. Then, we’ll work with some resources from Pro Publica and Open Secrets.slideslidess, json chrome extension,
Intro to Command Line & Coding, by Jessica Garson (Sat 1:30) In this class you will learn the basics of the command line, write your first two Python programs, and discuss resources for further learning. Slides and Scripts: https://github.com/JessicaGarson/Open-Data-Day-Intro-to-Coding My twitter profile is @jessicagarson
Intro to D3.js, by Chris Given (Sat 3:15): D3 is an expressive and powerful tool used to create many of the interactive data visualizations we see on the web today. If you’re trying to do more with your data than is possible in Excel or Tableau, or if you’re making websites that require interactive, data-driven graphics, this workshop will lead you through the build of a complete D3 project
Please add your project by adding a link here to a new page on this hackpad for your project.
Best practices: Clearly state the Problem, resources(e.g. datasets) available, suggested solution, skillset requested of volunteers, how solutions will be sustained post-hacking, and contact for point person.
Problem: we want more voters to use available early voting centers in order to reduce the possibility of long lines at polling stations on Election Day. By analyzing voter demographics and past voting patterns, can we determine where and to whom we should be promoting early voting?
Bullets for the Mayor (AKA what we accomplished at OpenDataDay DC on Saturday March 5, 2016):
Today with the work of a dozen volunteers, we developed a custom app interface, built a prototype app, and wrote code to parse UPC databases to help build an app for volunteers at the Capital Area Food Bank (CAFB) to more quickly classify bulk donated salvage packaged food into "wellness" or "not wellness". We also made progress in using Census and CDC data on were there are higher concentrations of diet related health problems in the DC Maryland Virginia (DMV) area so CAFB initiatives can better target those areas. Github link: https://github.com/cafbdk. We even had some progress on another mapping project where the American Red Cross may want to consider installing Smoke Alarms across the US.
The next step is to tie all 3 aspects of the app all together into an alpha version during our event on April 2 and build a first version of the diet-related health map of the DMV. After that, we will work with the Capital Area Food Bank to further refine this prototype with their feedback. Here's the link to the Meetup placeholder to RSVP for the next event: http://www.meetup.com/DataKind-DC/events/229365671/
the trello board says it is private...how does one get access?
Darron FIf the data is available, we would like to improve the model to support job and opportunity matching at the skills level and have more detail of specific jobs. This approach should result in a better "fit" between tracts (or blocks) of low-employment and tracts offering opportunity and provide an enhanced decision management tool for city officials. Furthermore this profit-maximizing framework can be extended down to the automated decisioning of matching job seekers directly to employers with available jobs. Update 4/20/16: Began working with the American Time Use Survey (ATUS) which asks respondents to provide details into their daily activities as well as their employment status. The ATUS has specific questions regarding Employment and Underemployment and also could be used to better understand the skills of the respondents based upon the data of their logged activities.
Here's what better (not yet "good", I'd say) data looks like - apparently this is really possible since some places have done it
Today our task is to do some prioritizing and consensus-building about what we need to get moving in our own cities so we can use it to do our jobs/organizing. What things could we do--or do better--if we could see the data (we need this, commswise, to make the case for data asks)?
Who are the people who can make the decisions to get this data opened up, and what relationships can we mobilize to get to them?
How do we do that, next stepswise (who/when/what)?
We are bringing together prototype teams in both DC and Baltimore and want to figure out how to facilitate them working together while meeting locally. The next build day (hackathon) will be in May in Baltimore. DC is re-energizing so we need to breathe life back into teams before we can justifiably plan a demo day. If folks want to join us feel free to connect them to me after the event.
Criminal justice data: usually the first thing people think about is crime data, usually the last thing they think about is the root causes, which turns us to reentry
Summary sentence: “This breakout session will touch on reentry data: what it includes, where it succeeds and needs improvement, and steps forward for building tools and policy that make it a higher priority in the criminal justice space.”
BLDS - The Building & Land Development Specification (BLDS) is a standard for sharing open data on building and construction permits issued by municipal governments. More information on the BLDS Specification can be found here: http://permitdata.org/.