stories from the Public Lab community
Go out into the wetlands. Find a quiet, secluded area. Be very quiet. Be still. After about a minute of silence, you'll start to hear birds. You'll hear the wind in the trees. You'll hear the water trickling. You'll see nature coming back to life.
This is how Howard Page helped share nature with a group of youths from the Forest Heights Boys and Girls Club in North Gulfport, Mississippi. "The kids really were amazed. It was remarkable that it could be one of the first times where some of these kids took the time to be truly quiet---an observer in nature, and not just stumbling through it," he says.
The children meet up after school at a center that backs up to the Turkey Creek Watershed, a popular waterway for canoeing and fishing, where Howard helped organize a series of workshops with students ages 10-15. "The idea was to have a series of experiences where the kids, in a very hands-on fashion, learned about the wetlands, but also learned about ways to do science, to do research, to document things, record, and report things," he shares. "We wanted to take them into their backyards, the wetlands, and give them fun, interesting ways to embrace and own the wetlands."
A Gulfport native, Howard grew up hunting and fishing in the area, with a love of the local coastal wetlands. Now as a community organizer with the North Gulfport Community Land Trust and Sierra Club, he's working with partners like Public Lab and the Gulf Restoration Network to teach kids to explore the wetlands through activities like balloon mapping, water testing, trekking, and photography.
"Everything was designed to be aspirational," says Howard. "I wanted the kids to not just learn science and how to fly balloons, but teach them that they can be educators too---and teaching them the jobs they can get by learning biology and chemistry. And that when they read these books about nature, they can write the books and take the photographs. We didn't want them to just meet professionals but wanted to make sure they knew they could become those professionals, and teach them what it would take to do that."
As a preservationist, taking science out of the classroom and into the field is important to Howard. "As a young person grows up in this community and gains an understanding of the wetlands, the goal is that in a few years, they'll be great voices for protecting them," he says. And the area can use all the advocates it can get. Development in Gulfport has led to a loss of wetlands, meaning a loss of vital flood protection. Stormwater control often fails to work properly, resulting in sewer and septic systems spilling untreated waste into the streets. "If there's untreated water rising up around your house, it may be out there where kids are walking and playing." He adds, "And aside from the obvious health related issues, there are psychological effects of constantly wondering 'Is my house going to flood and am I safe?'"
Howard has been closely involved with recent success with community efforts to protect local wetlands. "Because of community engagement, we've been able to identify areas where sewer systems leak into the wetlands, leading to better management practices," he shares. "One day, we hope to get these areas into conservation."
For now, Howard is helping to create a new generation of conservationists. "I asked the kids to go home and research what things live in the wetlands," he retells. "They came back the next week with answers. We talked about birds and snakes and cypress trees. And even moose! But there's one thing you're forgetting, I told them. You are one of the creatures that live in the wetlands. They really got a kick out of that."
gulf-coast balloon-mapping water-quality blog
Have you heard of the Coquí? They are sonorous frogs from Puerto Rico, and the subject of an awesome Menudo video from the 1980s.
The Coquí is a Puerto Rican frog that makes a "CO" and then a "KEE" sound at night
The Coquí frogs (and sort of the Menudo video) were our inspiration for naming the Public Lab Coquí, an easy, do-it-yourself circuit that makes a buzz-buzzing sound when you dip it in water.
Illustration by Akshaya Sawant
The Coquí circuit measures conductivity, a key water quality parameter. Conductivity is a measure of how "conductive" water is of electricity. If water is very pure H2O then the conductivity will be low because electricity doesn't pass well through water. But if there is a lot of stuff other than water in the water -- like mud, chlorine, or salt -- then water conductivity will be higher. High conductivity is not always a "bad" thing -- lots of rivers carry organic material, for example. And likewise, low conductivity doesn't always correlate to good water quality. Water with a ton of sugar in it would show up as low conductivity because sugar also doesn't conduct electricity very well. That said, water conductivity is a generally interesting indicator for how much "not water" is in your water and can help you ask questions about what that "not water" might be.
The Coquí was developed by Don Blair and Jeff Warren along with the Open Water Project based at the Public Lab. It's designed to be used in educational settings, and it doesn't measure precise values for water conductivity. Rather, it outputs a conductivity measure as a sound. You dip the Coquí's probe into water and it makes a high-pitched sound for higher conductivity and a low-pitched sound for lower conductivity.
Video from Chelsea Tremblay's sensor journalism research note
So while it's not a tool for collecting precise scientific measurements (if you want that you might want to check out the Riffle or some of the data loggers available from KAPtery), the Coquí is a great tool for introducing newcomers to building circuits, water conductivity, and civic science. Here are the benefits:
I teach data journalism and I have used the Coquí with my undergraduate journalism students to collect water samples from the community, test their conductivity, and then reflect on the role of journalists in regards to "sensors". Below is a map the students made of water conductivity in the Greater Boston area.
Water conductivity map made from samples the students collected around the Boston area
After running this module several times, I worked with graduate student Akshaya Sawant to create a free, illustrated guide to running a sensor journalism workshop. You can use this to help you get started using the Coquí inside or outside the classroom.
The Sensor Journalism Guide for Educators uses the Coquí to walk journalists and storytellers through an exercise in sensor journalism.
The Coquí kit is available from the public lab store. If you use it in the classroom or workshops, we want to hear about it! Post your research notes or ask a question and use the tags "Coquí" and "water-quality".
Catherine D'Ignazio is an organizer with Public Lab and an assistant professor of Civic Media and Data Visualization in the Journalism Department at Emerson College. Learn more about her work at www.kanarinka.com.
education kits water-quality blog
The Public Lab Kits Initiative uses Raspberry Pi cameras more and more, and was in need of a workflow to generate customized operating system images for specific needs such as the Microscope and Lego Spectrometer Kits.
In general, while Raspberry Pi mini-computer boards are amazing, there's a significant barrier for many people to use them, which is the installation and configuration of the memory card with useful software -- like camera software, for example!
We wanted to have a way to generate different pre-loaded SD cards, repeatably and reliably, for different uses. And we wanted people to be able to simply insert an SD card, plug in the camera and power, and start using the Raspberry Pi as a camera as quickly as possible.
We also had a desire to build a process whereby the community could participate in the construction of the operating system that we distribute with our kits and also to share recipes and ready-made images for usage in specific scenarios.
The default operating system image is meant to simplify the workflow for kit users, so these well-defined features needed to be set up:
I was contracted for this and so I had to come up with great shoulders to stand on in order to deliver all features! Disclosure: I am also Public Lab's part time Systems Administrator.
Fortunately thanks to the great work of the Hypriot Project, and the Gitlab CI service, we are able to iterate quickly and collaboratively, from an orderly and flexible base.
Please consider this release a Beta to try out
The documentation is included with the combined image. You may also read it online.
We also have a page for Q&A, troubleshooting, and activity guides here.
Adding a new "recipe" is quite easy -- it is possible to fork our repository, make your modifications and open a pull request, which our system will use to generate a new custom image. You can then download a fully built customized image ready to be burnt into your Pi¹.
¹: Tested on Pi Zero W only.
We'll be thrilled to see this repository evolve in alignment with the communities's needs.
raspberry-pi blog raspbian with:warren
Today we're announcing a new feature you may have noticed over the past few weeks! For a long time, emails about new posts or comments on PublicLab.org have been from an address called firstname.lastname@example.org -- how unfriendly! But it's because, unlike a mailing list, you couldn't just write a reply email. Remember this?
Thanks to amazing work by a number of Google Summer of Code fellows (#soc), but primarily by Naman Gupta, you can now just write back a reply email, as long as you're sending from the same email you're signed up with. (log in and check this here)
(This will work for any email you get from email@example.com that has a post id in the subject line, like this:
Title of the email (#1234) -- that's most of them!)
It's a new feature, so give it a try, and report back if you have any trouble!
This means that, soon enough, we will be relying more on the PublicLab.org website as a forum, rather than on our old Google Groups. To stay in touch with others working on topics you care about, be sure to SUBSCRIBE using the many prompts on the site, for example at the top of any topic page (linked to from your dashboard, or the front of PublicLab.org!):
You may have noticed a lot of changes on PublicLab.org recently -- this has been made possible by a dramatically growing community of software contributors, joining us through our new coding Welcome Page at code.publiclab.org, as well as through programs like Rails Girls, Outreachy, Google Summer of Code and Google Code-In -- and with support from the DIAL Open Source Center and the Schmidt Foundation's 11th Hour Project.
Hundreds of new people (see the bottom of code.publiclab.org) have started showing up to help fix bugs, implement new features, and help others in turn join in our efforts -- a very Public Lab spirit! And we've made serious efforts to reach out to and welcome members of groups that are under-represented in open source. You can read about our outreach work here. The result is that the collaboration systems we use across this community are getting refined and improved faster than ever!
Our code contributor community is built on a commitment to mutual benefit -- we can't create good software without welcoming in newcomers, and we are deeply invested in supporting contributors to learn new skills and grow as coders, designers, project leaders, and "cooperators". Unlike many open source communities, much of our capacity is aimed at helping people become proficient coders, and to learn and apply new skills.
But we also seek to change coding culture by recognizing how important communication, mutual support, and affirmative and welcoming tone are. As part of this, we seek to improve ourselves and help contributors learn how to support one another, welcome in a diverse and inclusive community, and build a more positive and equitable society by doing things a little differently.
community gsoc blog code
At the Public Lab non-profit, we are committed to the ethical and respectful use of personal information. In our work, and to serve our community and those we work with, we need to make use of personal information in a number of ways. We always seek to protect individual privacy while we fulfill our responsibilities and mission, and when these must be balanced, we seek to do so transparently and in good faith.
We've done our best to explain things in plain language, and as thoroughly as possible, even providing new information on IP-address anonymization at a supporting page here: https://publiclab.org/wiki/location-privacy#Privacy+Policy+Location
Most of it affects only those people who sign up and create an account on PublicLab.org, attend an event, or otherwise interact actively with Public Lab websites and systems.
Finally, it's been our intent in this document to explain why we handle different kinds of data in order to fulfill our role hosting these spaces and fulfilling the Public Lab mission.
Please give it a look -- thank you!
blog privacy privacy-policy gdpr
This Northeast regional Barnraising was like no other because it started with people exchanging stories of disaster. It was an appropriate ice breaker since the first day was dedicated to crisis convening. I shared my experience of an earthquake that hit while I was at a café in Philadelphia. I remember my inner dialogue went from "possible subway work" to "nearby construction" to the gut instinct that this was an earth shaking event. How much time did I lose arguing with myself? What would I do differently next time? As others shared their encounters questions arose: How many people have experienced natural disasters? What does emergency relief look like? What should it look like?
It's hard to compare a small earthquake that merely puts people on edge, to a hurricane with flooding that causes loss of homes, jobs, food and electricity. Testimonies from flood survivors, (who I'm now renaming flood wranglers) provided details of rising waters and destruction in so many communities---New Jersey, Texas, Florida, El Salvador and Puerto Rico. I know I was swept by the emotions of sadness, fear and anger hearing about their situations. Yet there were also stories of community leaders, bartering and rebuilding that brought hope. After another day of Barnraising, the stories started to sound similar. In fact, you could have exchanged locations and faces, but the same problems were surfacing.
The greatest thing about a Barnraising is that it not only provides a safe place to discuss problems, but it also encourages sharing current solutions while working on new ones. One of the best tools I heard presented was the common bicycle. They can be used for transporting supplies and medical aids, as they are nimble when most roads are jammed or impassible. Bikes are also able to be hacked to become generators to recharge phones--that's something everyone should have in place!
One of the sessions that got me most excited was creating a "Communication Checklist". Solid ideas were put on paper about the best ways to communicate during a disaster when electricity fails. Details include using flyers with bold/cultural images to communicate meeting places and times, connecting with community leaders, using libraries as hubs, encouraging face-to-face communication and supplying printouts of resources.
Choices of resources are often not controlled by communities, and one session addressed that problem by creating a blueprint for a Rapid RFP (Request for Proposal). It includes a transition/handoff plan, deliverables, timeline and transparent budget. This entire process would help to ensure that a community receives the right help it needs and would also put into place a checks and balances for how the process is working out.
Checks and balances is probably just the shadow of what I encountered on this Barnraising. The most memorable part was hearing quavering voices as truths were shared across all disasters including government mistrust, racism, receiving inappropriate supplies, neglect, hunger, sickness and homelessness. Still these discussions are so fresh in my mind and I'm so thankful for those that were able to stand up in front of the group and be so honest. We need to hear this---the world needs to hear this. So, what can we do to make disasters less disastrous? Here's what I learned so far:
We cannot escape that all things are interconnected and I know that I'm still learning how to ask for and accept help. For those that attended the Barnraising, please do add in your thoughts on what you learned or what could be helpful in a disaster. I remain in awe of flood wranglers and those serving in disasters.
community barnraising newark blog