U.S. Open Data concluded in July 2016. This is an archival website.
  • Home
  • Blog
  • Dashboard
  • On GitHub

U.S. Open Data

Building the capacity of open data.

    We’re Hiring a Circuit Rider

    15 April 2014 Waldo Jaquith

    The U.S. Open Data Institute has an opening for a “circuit rider”: somebody who will help government agencies, businesses, and organizations produce or consume open data. We’re looking for a programmer who works well with non-technical people, who is fired up about open data, and who has experience in the open data realm, whether producing it or consuming it. This is a full-time position. We’re prepared to pay well, by non-profit standards, for the right person. This employee will be able to work from anywhere in the United States, and the hours are flexible. The position is open until filled.

    See the full job description for details.

    Applications should be submitted via Screendoor. Questions may be asked publicly on Screendoor, via Twitter, or via e-mail.

    Open Hunting and Fishing Data

    08 April 2014 Waldo Jaquith

    At the U.S. Open Data Institute, we’re launching our first major effort to bootstrap a new open data ecosystem, and we’re starting with something unusual, at least in the open data realm—open hunting and fishing data.

    Hunting and fishing is a huge business—it’s a $75 billion industry in the U.S. 33 million people fish regularly, and 14 million people hunt regularly. But unlike most pastimes and recreational activities, participating in these activities requires a significant amount of knowledge about laws and regulations. And those regulations can be dizzying.

    Want to hunt? OK, but you’ll need to know what species, with what kind of weapon, in what municipality, when in the year, at what time of day. And some of those things might be different for children, or the elderly, or people with physical disabilities. Or on public lands versus private lands, or on Sundays versus the rest of the week. Hunting Canada geese in Virginia? Then it matters which side of I-95 you’re on. Hunting bear with dogs? Better double-check the laws, because they’re different on each side of I-81…sometimes. Hunting deer? Buck or doe? Antlered or antlerless? Are you in an area where you can get a bonus buck? Are you in an area where baiting is allowed? If you’re in Wisconsin, better check the map to see if you’re in a county with chronic wasting disease. Hunting deer in Texas? You’ll need to check whether the property you’re on has a Level 2 or a Level 3 Managed Lands Deer Permit, to know if special antler restrictions apply, because then you’ll need to make sure that the buck has at least one unbranched antler or a 13” inside spread…but you can only shoot one of those. Truly, the regulations are staggering, and they’re sure to suppress participation.

    Luckily, we’re starting this work just as the Virginia Department of Game and Inland Fisheries is looking to modernize their data practices, giving us a great partner in government. Like most game agencies, the Virginia DGIF is funded mostly by user fees—hunting licenses, fishing permits, etc.—requiring that they take a customer-centric approach rarely necessary for government agencies. One could hardly design a better environment for fostering innovation within government.

    We’re going to create JSON representations of many of Virginia’s hunting, fishing, and boating regulations—currently provided in a series of booklets and as HTML and graphics on DGIF’s website—and create the software to ensure that the data can be maintained indefinitely by DGIF. That development will be done entirely in the open on our GitHub repository, and we hope that participants will include representatives from other state game agencies, appropriate federal officials, app developers, hunters, and open data developers. Of course, all of the data, software, and documentation emitted by this process are being created and released under open licenses.

    Simultaneously, we’ll be promoting this work within the private sector, to encourage the creation of tools put this data to work—websites, iPhone apps, and who knows what else. It will be exciting to see how DGIF uses this data on its own website, but surely a lot more interesting to see what brilliant things that hackers do with it.

    Open data is about so much more than government contracts, campaign finance data, laws, legislation, and so on. That’s all enormously important—there’s a reason why the open data movement has been focused on that sort of data for so long—but we need to branch out to new types of data and new markets, so that we can tell new stories to new audiences about the value of open data. Let’s create a story that we can tell to—and about—33 million fisherman and 14 million hunters.

    Sloan Funding Dat Development

    02 April 2014 Waldo Jaquith

    We’ve got two happy pieces of news at the U.S. Open Data Institute.

    The first is that board member Max Ogden is transitioning to being an employee, as we start to house and support Dat, Max’s data package management tool. Dat is a system for real-time replication, transformation, and versioning of large tabular datasets. Git is to source code as Dat is to datasets. The John S. and James L. Knight Foundation provided $50,000 to support taking Dat from an idea to a pre-alpha stage, which sustained the project until February. Now it’s becoming a US ODI project.

    This is possible because of the second announcement: the Alfred P. Sloan Foundation has provided $260,000 in funding to support the continued development of Dat. That money will be used to pay Max and two additional developers to spend the year growing Dat into a vibrant, healthy, widely used open source project. Sloan’s interest is in seeing Dat used in the sciences, which produces a great deal of data, but for reasons both cultural and technological, does not generally publish that data openly. We intend to play a role in changing that.

    Max got started yesterday. You can follow along with development of Dat at its GitHub repository.

    Our thanks to Josh Greenberg and the Sloan Foundation for their generosity and gracious support. We’re also grateful to Casey Dachs and the Miami Foundation, and the folks at the Knight Foundation for their important help in making this possible.

Previous Page: 9 of 9 Next

Find U.S. Open Data

  • Email
  • GitHub
  • Twitter

Copyright Notices

Text of this site is Copyright © U.S. Open Data under the Creative Commons Attribution 4.0 International (CC-BY) license.

HTML, CSS, images, and design are based on a design forked from PeoplesOpen.Net which was, in turn, forked from Martini’s template, reused here under the MIT License.

Aerial photo of Boston is by Kevin Tostado, reused under a CC-A-NC 2.0 license