stories from the Public Lab community
This week, we wrapped up our 2019 Outreachy and Google Summer of Code with the largest team of fellows ever -- 15, with two joining via Outreachy and 13 via GSoC. We also had our most successful summer ever, with a huge number of amazing projects and some incredible collaborations.
This past Tuesday, we had an extra-long OpenHour (2-hours, actually) and folks got to give short presentations on their projects.You can watch them here on YouTube!
One thing I noted was that we had much more collaborative work this summer than in the past, with multiple 2-person teams working in close concert with each other, as well as a number of different bigger teams coordinating in parallel and across major integration projects -- MapKnitter being the biggest example of this!
I think this speaks to how we've grown as a community and developed strong cooperative practices! I also wanted to high-five everyone for opening MANY first-timers-only issues, and inviting many newcomers into their projects. It shows great leadership, and was crucial to the success of the summer's projects.
Overall, I was super impressed, and wanted to offer a big CONGRATULATIONS to everyone who participated: students/interns/fellows, mentors, and also all the newcomers who came and joined in on these projects.
Here are everyone's final reports. And again, GREAT WORK!!! 🎉 🎉 🎉 🎉
|Congratulations to our 2019 Outreachy and Google Summer of Code team!||@warren||3 months ago||5||2|
|GSoC Final Report for UI Improvements||@gautami_gg||3 months ago||1||0|
|Outreachy Final Blog : An awesome Journey||@lekhidugtal||3 months ago||5||6|
|Google Summer of Code 2019 Report||@alaxallves||3 months ago||4||12|
|Google Summer of Code 2019 - Final Work Product - Isha Gupta||@IshaGupta18||3 months ago||4||18|
|Introducing Community Toolbox 2.0||@icode365||3 months ago||5||11|
|GSOC 2019: Final Project Report||@aashnaaashna||3 months ago||0||1|
|GSoC'19 with Public Lab||@lit2017001||4 months ago||1||2|
|Google Summer of Code 2019 Final Report||@sidntrivedi012||4 months ago||1||3|
|GSOC 2019 wrapup||@vidit||4 months ago||3||1|
|Google Summer of Code 2019: Work Product||@namangupta||4 months ago||1||1|
|GSoC19: Mapknitter Rails Upgrade||@kaustubh_nair||4 months ago||3||2|
|Google Summer of Code 2019 Public Lab Final Work Product: Pranshu Srivastava||@rexagod||4 months ago||3||4|
|Google Summer of Code 2019 Work Product 2019||@namangupta||4 months ago||1||1|
|GSoC 2019: Mapknitter Image Management - Divya Baid||@divyabaid16||4 months ago||4||5|
|Wrapping up Outreachy and GSoC 2019||@warren||4 months ago||1||4|
|SOC 2019: A small proposal for global environmental monitoring||@MaggPi||8 months ago||1||13||Show more|
Follow related tags:
gsoc blog code wwg
Here in this post I would be summing up my contribution for this summer. We do have this one single link to checkout the whole contribution in project -
My project was about revamping the design of various sections pages, sidebar etc. Me and gautamig did it together. We divided an issue of one section into small checklists and get ourselves assigned with those small parts and then starting working on it. We have covered Tags, People,Profile,Individual tags, Questions pages along with sidebar. Along with that, it included various bug-fixing.
The first section we covered in the summer of code was people's section as we had already begin working on the major parts. I started off with my parts which were addition of cards for the list of users which included info and other stuff. #5740. It was great experience with review process and working on responsiveness (@~_@~). After that I moved forward with small fixes of responsiveness. #5754. Then till now, we had a card with details like user info but not tags the user is associated with. So I added in the most recent tags by user on its card #5765.
Gautami completed her portions and then we went to next section.
Yay !! Done with one section. (✖╭╮✖)
The next Section was Questions section , I created a new shadow page for questions page and added first section which included few info #5787. The idea of shadow thing still looks so COOL !!! (⊙⊙)(☉_☉)(⊙⊙)
After that I added featured Question part #5861 for which I took bit of time as it included changes in lots of cells (^_^;). I need to check the whole path of calling and adding a shadow function in back-end for popular questions only. We needed to show two features questions and this was third section for questions part.
Yay !! Done with with another one (✖╭╮✖)
Then we went to Individual Section page. I started off with #5903 absolute fixing of wikis page if included for that tag in background and if not then add default grey with the addition of followers to that particular tag. I guess this PR of mine did create lots of bugs and broke many major things. (. _ . )( . _ .)(⌣̩̩́_⌣̩̩̀)
Then we went onto to next, I moved forward to as per new design draft changing navs, tabs to dropdowns and vice versa. One of that included distincting between notes questions [#5925] (https://github.com/publiclab/plots2/pull/5925). I wrote my very first extra-small screenshot test here after checking out the code written by jywarren. (✖╭╮✖) It was of getting redirected to tag page, clicking the button and getting a screenshot of dropdown.
This is another design change of side-vertical search results 5851
And then then then, I moved to next part which was actually something major #5948. Its not one or two anymore but changing the design of all the cards with all the info for that particular page. I did this kind of work into parts before. But here i went for all in one go. (︶︿︶) And it also included changing the UI test as per new design. Woah !! Done with another one (✖╭╮✖)
And Finally we came to profile section. I tried something completely new here. _へ__(‾◡◝ )> I tried building whole profile page in one single go #5990. (︶︿︶) No taking small cases anymore. It was long review process with a lot of requested changes. As it was building up whole section in one PR , so lots of bugs and problems were there (~ _ ~;). And finally after 26 days, It was merged :'). Hurray !! ♪
Me and Gautami tried to do various portions altogether. As the portions were dependent on each other and we had to wait for some parts. till that time, I went for sidebar. It was addition of toggle icons 😄 #6011, We can't leave our sidebar out when all his siblings sections are upgrading with new designs ¯(°_o)/¯
Ohk !! trying to build profile page in one go left some features (⌣̩̩́_⌣̩̩̀) and bugs. Then addition of some buttons and info required as per new design #6079. And after that addition of popular tags by that user to be shown on its profile section was added #6120.
Also, few of the bug-fixing because of the new designs - 5766
And more than that, I somehow created lots of bugs ¯(° _ o)/¯, And thus created many first-timer and other bug issues for others to get them fixed. (҂⌣̀ _ ⌣́)
First-timers are: First-timer only issues link
Otherwise, we have lot more issues - Click to see issues
And some of the recent PRs which are still under revewing process (・_・;) - #6103 One of them is fixing the mismatch working of subscribe button as earlier we were subscribing to related tags but not that particular tags. And having dropdown for related tag. And if a user is subscribed, then we should have post option.
#6217 And another is addition of all the extra info of questions,notes,wiki to sidebar into
So Right now, we have one main section left which is Dashbaord. I'll keep on contributing. So My next target is dashboard now. (@~_@~).
I had an awesome collaboration with Gautami. Special shoutout to @warren for being such a patient mentor.(ø_ø) Thanks to mentors for solving and answering the silly questions I asked.
And Thanks to PublicLab for being such a wonderful community.
I guess I did miss various openhour calls sessions and was not much of active speaker if attended. (˘_˘٥)
I'll keep on contributing to PublicLab in future too. Thanks !!
Follow related tags:
design blog barnstar:basic blog-submission
For a few years now, Public Lab's open hardware community has been developing not only DIY tools for taking multispectral photos, but also software tools to process and analyze these photos---the Infragram project, and more recently the Image Sequencer project. These have enabled many people to take multispectral (near infrared/visible) imagery and do NDVI plant health analysis at home, on a shoestring budget.
We hope that this library makes it easier to get started for people looking to work with multispectral imagery, whether you're teaching it in a classroom, taking your own aerial multispectral imagery, or making use of NASA's amazing imagery resources.
The online demo demonstrates how you can use different colormaps, processing algorithms, and so forth, with your image overlay.
(Note I haven't aligned the above images at all, so they're just floating. Sorry!)
Learn about multi-band imagery and some of it's uses at this great blog post by Charlie Lloyd of Mapbox:
To get started, you can find some sources of multispectral Landsat 8 data here:
While this library is intended for NRG or near infrared images used as overlays, we have more plans for this technique---coming soon... Leaflet.TileFilter -- a project to apply the same principles to full map tile layers!
Follow related tags:
ndvi multispectral nasa infragram
Over the past six months, we've overhauled almost every part of the MapKnitter website, and I wanted to share a bit about all the people who made this possible. Between our Google-funded MapKnitter code fellowships and our Google Summer of Code (#GSoC) fellows, we've had contributions from five continents and more than ten people, all coming together to build this complex system!
In March, we put out a call for Mapping Fellows to help lead mapping events in their communities and give feedback on their experiences using MapKnitter.org to stitch together their aerial images. We partnered with Mo, who worked with youth asylum seekers and refugees to do balloon mapping in their new home in Nottingham. We also partnered with Sairam, who worked with community members in Bangalore to map local waste sites and analyze optimum sites for installing solar panels. Mo and Sairam provided detailed user interface feedback on MapKnitter's design, from the overall workflow to specific organization and styling of buttons and tabs. See for example this annotated screenshot, which we are using to refine the UI:
Meanwhile, Cess Wairimu in Nairobi and our GSoC fellows Alax Alves in Brasília and Kaustubh Nair in Bangalore were hard at work tearing out and rebuilding the Ruby on Rails foundation of the application, upgrading it and cleaning up old code. Much of the code hadn't been touched in years, and things really got refreshed, restructured, and brought up to date.
Meanwhile, Varun Gupta (a GSoC alum) in New Delhi and Sebastian Silva (our sysadmin) in Madre de Dios, Peru worked hard on a cloud-based exporting system to offload heavy image-processing jobs to a cluster in Google Cloud, implementing both Node.js and Ruby workflows, and linking MapKnitter to our new image-processing library, Image Sequencer.
Stéfanni Brasil (a former Rails Girls Summer of Code fellow) joined in from Vancouver and brought our UI up to Bootstrap version 4, while Cess stepped in again to build on Stefanni's work in launching a new front page design that highlights mappers' work from around the world.
Finally, hard work by Ananya Arun in Hyderabad and Sagarpreet Chadha in New Delhi has made the new "tour" feature possible, highlighting MapKnitter maps around the world.
It's been an amazing journey, and there's still a lot left to do through the end of the summer. But the launch this week of MapKnitter 3.0 (bigger announcement coming soon!) proved how input from so many folks can make for a really fantastic and cohesive project! It also shows the geographic breadth of the Google Summer of Code, Outreachy, and Public Lab communities!
Thanks to everyone who's helped make this possible, from fellows to students to mentors, as well as the Outreachy program and the Google Open Source office. We're looking forward to a new wave of mapmakers on this fabulous rebooted project, and the many Community Atlases they'll go on to create!
Follow related tags:
balloon-mapping mapknitter collaboration software
Public Lab is excited to announce that with support from the National Academies of Sciences, Engineering, and Medicine’s Gulf Research program we will be working on building the scientific capacity of the next generation. To this end, Public Lab is partnering with educators along the Gulf Coast to pilot a curriculum designed to support students as they use community science methodologies to explore environmental challenges facing their community. This project centers students as knowledge producers, rather than knowledge consumers, on a path toward becoming scientifically literate citizens. As a team, students undertake problem identification, study design, data collection and analysis, and sharing results back to their community. Throughout the project, students will utilize Public Lab to connect to a larger network of community scientists, experts, and locals working in their field.
This project utilizes four phases and a problem-based learning approach to allow students to progress from problem identification to sharing their story with the community. You can learn more about the project or check out lesson plans at the Student-Led Community Science Wiki or see an overview above.
In the first year of this program, educators @amallozzi, @jeanell873, and @fwagner will be working to adapt and refine the program for their classrooms. You can follow along on the projects progress by subscribing to the tag #student-community-science.
Over the course of three days in New Orleans, LA our team gathered to workshop lesson plans, discuss connecting classrooms to the larger communities, and share our experiences with student-led inquiry. We worked together to set goals for this year of our project. You can take a look at our goal setting in this document. These goals include:
Throughout the workshop, we began a list of things to share with educators who are facilitating student led inquiry for the first time. Here are some of our key takeaways:
Our students will be asking questions, sharing their work, and looking for feedback throughout their projects. If you'd like to follow their work, provide help, or cheer them on, subscribe the tag #working-together. If there are specific topics where you feel you'd be most helpful, let us know in the comments and be sure to subscribe to tags.
We're working to share our lessons as frequently and openly as possible. Share helpful feedback on lesson plans, or try them out and let us know how it goes. You can see the full lesson plans here.
In the 2020-2021 school year we'll continue to refine this curriculum. If you're an educator in the gulf coast, let is know that you're interested by completing the form below.
Follow related tags:
education workshop blog with:stevie
Since my first evaluation post (https://publiclab.org/notes/molangmuir10/06-10-2019/mapknitter-ui-evaluation) I have encountered some different additional user interface experiences...
As with anything, mapknitter gets quicker and easier the more you use it!
I have made a screen recording video to highlight some of my key experiences and issues when using Mapknitter...
Sometimes it is hard to move the photo to the EXACT point on which you want it. If you could click the photo and use arrow keys to move the selected photo this could help with the accuracy. At the moment pressing the arrow keys moves the whole map. This is also a good feature. Keep this but add a way of clicking on the photo which selects it so you can then use arrow keys to move accurately.
It would be good to have a photo cropper -- some of my images had one bit that was off/blurred but the rest of the image useable. I know this can be done by cropping the original file and reuploading, but it would be much quicker if you could do this in situ.
It would be nice to have a save button. Feels scary closing the window without knowing what's happened!
I also was thinking if it were possible to make an off-line extension? Particularly for remote research areas or 'on-the-go'.
Uploading map through to Publiclab's page was straightforward
Follow related tags:
balloon-mapping mapknitter community mapping