Show your support for community science. Donate to Public Lab »
stories from the Public Lab community
The sheer number of posts on publiclab.org by contributors from all over the world about 1) how to build tools better, and 2) how to use them for making environmental observations is breathtaking, and at times, boggling. As Public Lab has grown, so much content has been generated that it has become unnecessarily difficult to know what the "latest and greatest" version is, what the next development challenges are, or simply where newcomers should begin.
In the past couple weeks, staff have begun "gardening" on PublicLab.org and writing some new web features.
People on the spectroscopy and near-infrared lists have been discussing how to better present the overall research areas to make it easier to get involved. For each of those two research areas, we made a new top-level page. See them at spectrometry and multispectral-imaging. On those new pages, we constructed a couple tables -- the main table organizes relevant research notes into a "ladder" of activities others can replicate. There are columns to describe what type of activity it is, the status of its documentation, and how many people have replicated it.
We made a "Request A Guide" button to capture ideas about what people would like to do but don't see listed yet:
We also drafted two other kinds of tables, one to track upgrades (additions, modifications) that people have made to particular tools (for instance, the desktop spectrometer):
...and another to hold questions related to a particular research area (for instance, spectrometry):
Check out this much easier, automated way to organize content into grids:
After creating the first grids manually, WebWorkingGroup quickly created an automated way to make the grids. We created a power tag to add an Activity Grid to your wiki page with just a few characters, like this:
This automated Activity Grid fills itself in with all research notes tagged with the key word you used. Consider the keyword "spectrometry": a grid on a wiki page created with the powertag
[activities:spectrometry] will pull in all content (notes/questions) tagged with the powertag
activity:spectrometry. Check it out on https://publiclab.org/wiki/sandbox, look at the tables, then click "edit" to see how the tables were generated. The tables have various columns, such as "difficulty" (like easy, moderate, or hard), which can be filled out by adding more tags on the research notes. We're working on a tagging interface to make tagging less mysterious:
These draft "Activity Grids" are ready for you to test drive! How?
...and to pipe content into the grid, go back to your original notes and add the powertag
activity:spectrometry. To fill out the columns for each activity, use the tagging interface to add additional powertags or directly type:
If you want any assistance, email firstname.lastname@example.org and we'll help you get it going!
Follow related tags:
collaboration blog with:warren with:gretchengehrke
We've had some tremendous work on Public Lab software this past summer through our Google-supported Google Summer of Code program, where five students and several mentors have spent innumerable hours cooking up new features and abilities both on the PublicLab website and in the independent #webjack project.
Even just in the past month, we've seen (via Github Pulse):
Excluding merges, 9 authors have pushed 368 commits to master. 321 files have changed and there have been 7,047 additions and 1,217 deletions.
The program wraps up this week with many of the features having gone live over the past few weeks. Our five students have written up their work in a series of notes, which I'll link to here:
Thanks to all of our mentors for their ongoing input and support, with special thanks to the Community Development team, @liz and @stevie. I'd also like to shout out to @david-days, as well, who put an enormous amount of work into the Advanced Search project, and in particular, whose work was just merged for the first time last week in an epic rebase of hundreds of files and thousands of lines of code.
These projects, from including more languages on PublicLab.org to making it easier to find people and resources near you, all have helped to make Public Lab's collaborative model stronger, and we're eager to see how the new features promote the growth of our community.
All of our students this year were extremely productive, and we had our best-ever GSoC program, beyond all doubt. The fast pace of merging (twice weekly) was exciting and really ensured that student work tracked the master branch closely, and that new changes (with corresponding tests) were quickly and consistently integrated into production code instead of drifting off and resulting in larger, more difficult merges later. Thanks to all of our students for keeping up with this fast pace (and occasionally going faster than I could!). It was great to have students who knew how to do pull requests, write and run tests, and rebase their changes to make things efficient, so we could focus on doing great work.
One of the things which really made the difference this year was the way our #new-contributors work helped to ease students' entrance into the codebase, and we've asked the students to, in turn, produce some `help-wanted` and `first-timers-only` issues to draw yet more contributors into the project:
Amazingly, this has worked very well, and two new contributors (carolineh101 and ykl7) have committed code in the past two weeks, directly resulting from these outreach efforts. With so many well-documented and welcoming issues, we hope this is just the beginning. See the screenshot below for just a portion of our
So, all in all, a fantastic summer, and thanks to all who helped out!
Follow related tags:
software gsoc web blog
Hello everyone -- Jeff Warren and Gretchen Gehrke here, Public Lab's Research Director and Data Quality and Advocacy Manager, respectively. Over the next few months, we're hoping to share a series of posts covering different aspects of the concept of evidence. What is it evidence, what factors contribute to the importance of evidence, and how does all that relate to environment sensing?
We spend a lot of time thinking about different kinds of data and how to collect it. Well, imagine you've got some data. How does it compare to other kinds of data? How's it been used for action? How was it analyzed, stored, sent, presented?
We have a lot of questions and we'll be talking to a number of different people, from environmental lawyers to formal scientists, regulators and activists who've gone through this and have experience with the ins and outs of evidence. We're also looking to co-author blog posts and research notes with other individuals or groups, so if you're interested, please reach out! (email@example.com)
In particular, we're going to look at some specific types of data we're interested in, related to the use of photography as evidence: for example, timelapses of turbidity events in water, or photographs of microscopic silica. We want to research how such data has been used in the past, but also document and discuss best practices for storing, transporting, and presenting it, with an eye toward environmental outcomes.
Broadly, we're thinking of doing posts on some of the following topics:
Before we kick this off, we'd like to share some of the questions that have motivated us, and ask you to chip in with your own questions -- and resources! We've already had a great opportunity to chat with Chris Nidel, who participated in an OpenHour on "proof" a few months ago, and we're eager to talk with a broad range of folks. In the comments, please list out some of the things you want to know about how environmental data can become evidence, and if possible, share a bit of background to help situate your questions.
These are just a few of our many questions, but please add your own below!
We'll also be adding some of our questions into the new Q&A system which was recently added to this site. As people add questions on the topic of
evidence, they'll appear here:
|How do you merge GPS logger data into photographs?||@warren||over 2 years ago||1||11|
|Who can vouch for, or interpret, evidence in court, and how is it weighed?||@warren||about 3 years ago||1||2|
|What are the limits to what can be interpreted from a photograph without an expert witness?||@warren||about 3 years ago||0||0|
|What are ways to strengthen photographic evidence in court?||@warren||about 3 years ago||1||0|
|What's the best way to archive/store a timelapse video?||@warren||over 3 years ago||1||3|
Follow related tags:
evidence blog with:gretchengehrke evidence-project
It has been a month since Public Lab has left Val Verde, and a month since a very intensive Barnraising in which we literally met in a barn with incredibly interesting, creative and dedicated people. Sharing the event with the greater Public Lab community was foremost in our minds, until we got distracted with recent events – apologies for the late report.
Before I start, and because I plan to share this with my community, I want to answer the question that a lot of neighbors asked me: What is Public Lab and what do they do?
Okay, so. Public Lab is a lot of things: they focus on low-cost approaches to fill data deficits; they provide a crucial platform for interested parties and stakeholders to share ideas; they communicate with communities and help to uncover and research areas of human health and industry that are not being addressed. They help to provide tools and support to enable researchers to map the world's urban population who live in unauthorized settlements, for instance.
But what is Public Lab really do -- Without all of the language -- What do they do? In my opinion, I believe that Public Lab’s mission, the most important thing that they do, is spread this gospel:
The most efficient way to solve a problem is to communicate.
As a newcomer to the Public Lab community, Public Lab truly is an altruistic group of people who have a method and way of organization that works to solve problems. The regional barnraising event is another tool for Public Lab to share their innovative approach with other regions. We were very fortunate to have been able to host the event and want to thank Public Lab for the opportunity to be influenced by PL's way of thinking.
Public Lab does something different in that they do not place primary value on the outcome, but rather the work and the process. This is a refreshing point of view when you are locked in a battle as my community is with a local polluter. The focus is always the outcome.
If I can be allowed to be sentimental, since the Olympics are underway, successful athletes think this way. They focus on process, the moment and also employ innovation in finding ways to make their hard work take them further.
On a less local level, if each of us learns to communicate and collaborate with others to solve very real, pressing, human issues – such as biodegradability of ocean plastics – we have a chance to make change that we desire and leave the world not only in a better place. We can also leave the world a better place not only because pollution has decreased, we can leave the world a better place because we have learned to communicate and value each other -- a foundation for global peace and understanding.
Enough of that.
(Stay tuned for more pictures and events from the July Regional Barnraising in Val Verde).
Follow related tags:
landfill barnraising blog val-verde
Hello,我想和大家分享我在中国江西使用Balloon Mapping Kit的经历。首先呢，这里是中国江西省的东南部，寻乌县三标乡的东江源村。东江源村位于东江的源头，而东江则是珠三角东岸众多城市的水源地，如广州、深圳、香港。就是说，我家的自来水很有可能就是从这一路流到我家的水龙头呢。
那么，这是我们第一次使用Balloon Mapping Kit。除了想体验把氦气球放到天空中拍摄图片的过程，我们在这里使用Balloon Mapping Kit，还有是希望了解东江源的实时地理概况，了解村庄和附近河流的情况，帮助我们更熟悉这个村庄。
我们在制作氦气球的过程中发现了许多可能会影响氦气球升空的因素。 第一，如何绑气球使气球的承重最少，并且保证绳结不容易松开。 首先我们选择了不易断裂的麻绳。然后我们用了一种可以活动一边绳子的打结方法，这样即使气球活动，也能减少绳子的磨损。我们尽可能的减少打结的次数，因为何珊老师说每打一个结就会使气球的整体承重增加。最后我们把11个气球分别拴在一个橡胶环上，这样能保证即使一个气球飞走了，摄像机也不会立刻下坠到地面。 第二，用什么材料的气球才能使气球不容易漏气和破裂，并且能充入更多气体。 我们用了3个大橡胶气球和8个铝膜气球，因为橡胶气球的拉伸限度大，可以在一个气球中充入大量的氦气，尽可能使气球的浮力更大，而铝膜气球不容易漏气和破裂。
然后呢，从这次拍摄和制作地图过程中，我们发现了原来位于村子旁的这条河流在2015年的时候还是一条土河，河流是在今年才变成我们现在所看到的样子。 Google Earth上显示的地图:
那么，在使用Balloon Mapping Kit的过程中，我们觉得最限制氦气球升空的因素就是，气球的拉伸限度不够大，无法在同样的重量下充入更多的氦气，还有就是气球比较容易漏气，这也是我们无法把气球升到更高的原因。
可能PublicLab和Balloon Mapping Kit在中国只有极少数人知道。所以我们希望能通过这次航拍来向身边的人宣传PublicLab和气球航拍,让大家都可以自主的了解自己的生活环境。并且，我们希望能通过这次实践来了解如何使用Balloon Mapping Kit。
Follow related tags:
Update 9/2016, the Code of Conduct is live at this link: https://publiclab.org/conduct
Last year we celebrated our 5th anniversary as a thriving, growing community of people from numerous backgrounds. Many of us met for the first time through Public Lab, have found collaborators and people to discuss a range of topics with, and some of us have had the opportunity to connect with one another in person through Public Lab and non-Public Lab events. Public Lab has always been a friendly community that attempts to welcome and include as many voices as are interested in joining the conversation. As we've grown in numbers though, it has become increasingly important to note the ways that we can maintain the important values that this group was born from.
During the 2015 Annual Barnraising, we tried out a new in-person structure where four members of the community-- Carla, Klie Kliebert, Nick Shapiro and myself (Shannon Dosemagen)-- acted as team facilitators. We were available to help facilitate conversations, make sure everyone felt welcome in the space and listen if someone wanted to sit and chat for a moment. Coming out of this gathering, we were happy that although facilitation was unnecessary during this event, knowing that the group and structure were available was well received by those in attendance. Over the last several months, we've expanded this initial event specific facilitation model into a Public Lab Code of Conduct, which will be adopted across the community. Interacting and making decisions with people who geographically span the globe and whose experiences are similarly as broad can be difficult to navigate - our goal with this document is to specify values that we as a community can reference, agree to and abide by.
We want everyone to not only have this important document, but to also be able to replicate the process. Through our many conversations, research and work sessions, we realized that writing a Code of Conduct was similar to other research that we do, so we're sharing below the journey along with the outcomes. We've included details, steps, and reference documents that describe our process (thus far), which we hope will help others who may be in need of a Code of Conduct for their group or organization. We continue to maintain that being open, learning together and offering space for questions and improvement is what makes our communities, research and work stronger.
Please take a look over the Code of Conduct (linked below), and add your comments or questions by July 15th. We'll be using it in the current form during the regional Val Verde Barnraising this weekend, but afterwards comments will be reviewed and incorporated and a final version released on July 20th.
Read on for more from @liz on our research and drafting process.
Here is a link to the document in GoogleDrive. To add comments, please just request access and we'll grant it right away. https://docs.google.com/document/d/1azLoPNGF7oo9WKmlj4n_bEcZWI2PMQpcf2Si8VXPZfs/edit
We framed the very top of the document with language from in-person democratic space holding that emphasizes the combination of respect and responsibility. The sentiment of "for democracy to work for everybody..." as practiced by the Highlander Center for grassroots organizing and movement building in Appalachia / the South is described in the book by Miles Horton "The Long Haul: an autobiography". Also see http://highlandercenter.org/. We also drew from the Jemez Principles for Democratic Organizing which was written in 1996 by forty people of color and European-American representatives who met in Jemez, New Mexico with an "intention of hammering out common understandings between participants from different cultures, politics and organizations." Carla added the clarifying points on dignity during interactions.
For the fundamentals, we looked to the Ada Initiative guide to writing Codes of Conduct (CoCs) https://adainitiative.org/2014/02/18/howto-design-a-code-of-conduct-for-your-community/, specifically these three points:
Over that, we added a heavy overlay of JoyConf consent and empathy culture: https://github.com/maitria/code-of-welcome/blob/master/coc.md
Follow related tags:
blog with:thegreencommunitygarden with:liz with:nshapiro