About Me

Name : Barun Acharya

Github : https://github.com/daemon1024

Project Title : Geographic Features Refinements

Gitter : daemon1024

Affiliation : Jaypee Institute of Information Technology, India

Location : Noida, India

Student year: Sophomore (second-year student)

Field of study: Computer Science and Engineering, B.Tech.

Portfolio : https://daemon1024.github.io/

Project Description

Abstract/Summary (<20 Words)

Smoothen, expand and refine the various geographical features under Public Lab's website. This includes standardizing, adding new leaflet environmental layers, increasing content on https://publiclab.org/map and various other refinements.

Problems

Standardize "Spreadsheet to Layer"

We have an awesome utility to add a leaflet environmental layer using data sourced from a spreadsheet, more details at https://github.com/publiclab/leaflet-environmental-layers#spreadsheet-based-layers. But currently it's not feasible for non programmers to use this utility or how to source the data for the layer to be based upon.

Workflow

The above workflow doesn't need a server dependency as it is automated using GitHub API and actions, and in case of any failure it still provides a manual alternative.

The intended workflow would start with volunteers submitting the form, which automatically opens up an issue, which in turn triggers the GitHub action, the script runs in the action environment and finally generates a pull request with the new layer.

The proposed workflow has fallback for each and every step, in case any step has a failure there will be a provision to complete it manually.

In case every automation fails, the fallback and most basic workflow is providing the volunteer with instructions to open up an issue. Once a public lab contributor picks it up, they have to manually run the script to generate the new layer and make a pull request linking it back to the issue.

I understand that the primary audience might not all be developers and will try to maintain a smooth workflow for them while detailing out each and every fallbacks and progress while making the whole process extremely accessible.

Details about spreadsheet2layer.js:

• Provide an abstraction for https://github.com/publiclab/leaflet-environmental-layers/blob/master/src/util/googleSpreadsheetLayer.js
• Has minimum required user inputs
• Auto Generate tests for the generated layer
• An extremely simplified function code to generate the layers

Some additional points to note:

• We can provide "Open Gitpod to try out new layer" option in the generated pull request.
• Providing an independent file/code which can be included/copied over to anyone's codebase so as to include the generated layer. We can see some examples at https://github.com/publiclab/leaflet-environmental-layers#adding-layers-individually but they still require LEL dependency. We can refactor some of the internal dependency so as anyone can include them.
• We can generate sample previews using these independent components and deploy them to static pages using github pages or alternatives.

Add and refine environmental layers as part of the Leaflet Environmental Layers library

Since we would have a new standardized process to add spreadsheet based layers, it will open up ample opportunity to add various layers.

Also there are many issues open regarding layer requests, broken layers or need for optimizations publiclab/leaflet-environmental-layers/issues. I will try to address them.

Increase amount of content shown per page-view at /map

Currently the content on https://publiclab.org/map on initial load shows very few users/pages and gradually increases.

The current possible solution includes developing a microservice which scrapes the Public Lab API. This micro-service intends to replace the current direct API access.

Details about the microservice:

• Cache data from API to reduce server load?
• Provide data more in line with how we want to display content
• Provide a bbox-queryable GeoJSON service
• Ensuring the content is ranked by some filters like recency, views, comments, likes etc. . . as well as adding an option to provide custom filters.

The current API at /api/nearbyPeople returns data in the form of

{
  "items": [
    {
      "doc_id",
      "doc_type",
      "doc_url",
      "doc_title",
      "latitude": "42",
      "longitude": "-71",
      "blurred": true,
       .
       .
    },

Since the microservice would be a GeoJSON service, the proposed form of data returned would be:

{
  "type": "PlacesCollection",
  "places": [
    {
      "type": "place",
      "geometry": {
        "type": "Point",
        "coordinates": [102.0, 0.5]
      },
      "properties": {
        "blurred": "",
        "id":"",
        "name":,
        data
        .
        .
        .
      }
    },
  ],
  "type": "PeopleCollection",
  "People": [
    {
      "type": "Person",
      "geometry": {
        "type": "Point",
        "coordinates": [102.0, 0.5]
      },
      "properties": {
        "profile": "",
        "id":"",
        "name":,
        data
        .
        .
        .
      }
    },
  ]
}

Since GeoJSON would be a standardized format of data it would help integrate PL data with other applications as well. For legacy support, we can choose to provide them both and only respond with GeoJSON when the API request type is application/geo+json.

Improving Load Times

We are currently loading individual nodes while monitoring loads. I propose to pre cluster various nodes based on zoom levels and we dynamically create requests based on the current bounding box. The simplest way is to use a plugin such as Marker Clusterer. Clusterer helps the rendering on the client side greatly as it means the client computer doesn't have to draw hundreds/thousands of points, it just draws 10-40.

Ensure empty people grid squares don't generate pop-ups and ensuring grid squares with blurred locations are tinted

Currently every empty grid square generates this pop-up. This pop-up should only be generated on grid squares which are actually blurred in line with https://github.com/publiclab/leaflet-blurred-location and these grid squares should be tinted and should be visibly different from other grid elements.

Timeline

I have only listed down the potential priority and focus tasks for each week in the above timeline, In addition to that my work in each week would be a blend of the following :

• Breaking down issues into smaller modular tasks
• Interacting and getting feedback from mentors
• Team meetings
• Helping out other contributors

• Testing

  Testing is a very important aspect of software development. It helps in more accurate, consistent and reliable results. I plan to add all unit, functional, integration and system tests, since we need them all for all 'units' to work cohesively. I will be adding unit tests after completing each unit/functions. For integration tests, I prefer the top-down approach and testing each unit integration step by step and expanding. Functional tests for handling edge cases and other behavioral tests.

• Outreach

  • Writing blog post sharing my progress and GSoC experience along the way
  • Opening up FTO's for new contributors and help review any pull requests.
  • Improve Documentation, making them beginner friendly so as to make new contributors feel more guided through them.

Contributions

I have been an active contributor throughout the Public Lab ecosystem of repositories - with significant contributions to Public Lab's Image Sequencer and Plots2. Not only contributing with code and pull requests but being an active member by reviewing PRs, helping other fellow contributors, engaging in discussions and such. I am also part of the Image Sequencer CLI maintainers team and am working on the new test suite for sequencer CLI.

Comments

Issues

Pull Requests

Experience

I feel very passionate about developing software and automating things. I feel very happy when my software helps people out and make their lives easier and more fun!

I primarily program in JavaScript and Go but not limited by them. I have worked on projects in various languages including Python, Ruby, Rust and C++.

Some of my notable projects are:

• Needzo - https://devpost.com/software/needzo | Auth0 Hackathon (Fifth-Community)
  Needzo lets those under self-isolation and other vulnerable groups request deliveries and allows local volunteers to sort through, claim, and complete those deliveries with a gamified approach.
• EndangAR - https://devfolio.co/submissions/endangar-bfce | Bitbox Winner - EchoAR Showcase We wanted to spread and create more empathy and knowledge towards the environment and wildlife out there. EndangAR is our project through which we spread awareness of endangered flora and fauna through an interactive map interface and rendering plant and animal models in 3D as well as Augmented Reality
• Bikeshed - https://github.com/daemon1024/bikeshed
  A friendly neighborhood GitHub bot which automates trivial tasks for an organization and aims to provides a welcoming environment for newcomers.
• Bolt262 - https://github.com/daemon1024/bolt262
  It is CLI utility to run test262 tests for various hosts ( currently tested with node ). It currently aims to be as fast as possible and optimizations wherever possible.
• TabuRei - https://github.com/daemon1024/TabuRei
  TabuRei is an all-in-one browser extension to manage and store your tab clutter and restore them on the fly. It is fully Open-Source, and loaded with features. Try it at https://addons.mozilla.org/en-US/firefox/addon/taburei/

I take workshops and talks to bridge the gap between newcomers and development and spread awareness for FOSS at Open Source Developers Community(OSDC). Some of the projects I have collaborated at OSDC :

• Community Tools API OSDC - https://github.com/osdc/ct-api Proposed and Working on the automation of organizing meetups and notifying the attendees for OSDC.
• OSDC Bots - https://github.com/osdc/bots/commits?author=daemon1024 Maintaining and Contributing various fun and automation features to the community bots available for discord and telegram.

Other open source contributions:

• Add remove-members helper tool implemented in go - https://github.com/kubernetes/org/pull/2575
• Implement getting resource list for a service - https://github.com/keptn/keptn/pull/3232
• Consistently note in algorithms wherever steps may be inserted/modified elsewhere - https://github.com/tc39/ecma262/pull/2196
• Make Pycon India 2020 site responsive - https://github.com/pythonindia/inpycon2020/pull/78
• Add graphiql create-react-app example - https://github.com/graphql/graphiql/pull/1510
• Fix confusing error message in fs.utils - https://github.com/nodejs/node/pull/32896
• Handle detached arrays in XRView - https://github.com/servo/servo/pull/26185

Teamwork

I have participated in various hackathons and collaboratively made solutions to various societal problems with teams of 3/4 and have accomplishments in many of them. I volunteer at OSDC and we conduct meetups and events as well as work on projects with the entire community and thus, know how to work in a community. I am a firm believer of collaborative development and working with communities which is visible through most of my open source contributions.

Passion

I have been involved with Public Lab for quite a while now, and I started contributing because how caring and progressive the community was and I am really passionate about giving back to the community and continuing as well as improving this welcoming environment in the future.

Audience

This project aims to ease the process of adding interactive statistical map layers for volunteers and scientists which in-turn will help them display there research in much more intuitive manner. It will also attract developers and contributors who can leverage the LEL ecosystem. With additional optimized content on the /map page, it will improve the discoverability of research notes and community projects, bringing the Public Lab community closer and more interactive.

Commitment

There is no conflict of interest in coding phase as of now and I don't plan to have any other commitment during the period. If there will be any sudden changes in university schedule, I will discuss with the mentors.

I'd like to mention that I will, as I have done previously, continue to actively interact with the newer contributors and provide insight and any help that I can regarding their PRs and issues during (and after) my GSoC period. Hence, I firmly believe that I will deliver my assignments with commitment and promptness.

I look forward to working with the awesome community of Public Lab for a long time!

Needs

Help and guidance of my mentors as well as coordination from other contributors is all I need.