The Greater Baltimore Technology Council announced last week that its Groundwork data hackathon has been rescheduled until sometime “likely in late September.”
As Sharon Paley wrote on the GBTC website:
Some very nice people (of the state and federal variety) with access to extremely important (but not yet open) data, heard about Groundwork and proposed that they give the Baltimore tech community first crack at data which has never before seen the light of day. They also offered to bring in some key influencers who can help us usefully mine the data sets. [more]
This means that Groundwork will now take place after the GBTC’s UnWIREd event, taking place late this month on Johns Hopkins University‘s campus.
Click here to register for UnWIREd on August 24-25.
The UnWIREd event will convene local educators, officials, policy makers and creative-class types to tackle two main questions, according to GBTC: “How can we use new technologies to empower business, social service providers, neighborhood residents, and policy makers? How can networked citizens join together to improve our city and our region?”
“What we’ve come to understand is it’s not the data [from Groundwork] that’s going to drive UnWIREd,” says GBTC’s Jason Hardebeck. “It’s UnWIREd that’s going to drive the data. Groundwork makes more sense after doing UnWIREd because now we can provide focus to what specifically we’re looking for [in the data] to support ideas and projects that come out of UnWIREd.”
Groundwork will be a chance for hackers, developers, data analysts ”to conduct research and analysis to gain a better understanding of Baltimore’s true resources and greatest opportunities to improve the lives of citizens and the way they are served,” according to GBTC.
Hardebeck says a useful analogy for Groundwork is that of Lewis and Clark, who had “the canoes and the provisions, but they need Sacagawea to interpret the local flora and fauna.”
“By bringing the technologists and creatives together with the people who can make sense of the data,” says Hardebeck, “[we’ll] provide some insight as to why something may or may not be.”
Before you go...
Please consider supporting Technical.ly to keep our independent journalism strong. Unlike most business-focused media outlets, we don’t have a paywall. Instead, we count on your personal and organizational support.
3 ways to support our work:- Contribute to the Journalism Fund. Charitable giving ensures our information remains free and accessible for residents to discover workforce programs and entrepreneurship pathways. This includes philanthropic grants and individual tax-deductible donations from readers like you.
- Use our Preferred Partners. Our directory of vetted providers offers high-quality recommendations for services our readers need, and each referral supports our journalism.
- Use our services. If you need entrepreneurs and tech leaders to buy your services, are seeking technologists to hire or want more professionals to know about your ecosystem, Technical.ly has the biggest and most engaged audience in the mid-Atlantic. We help companies tell their stories and answer big questions to meet and serve our community.
Join our growing Slack community
Join 5,000 tech professionals and entrepreneurs in our community Slack today!