Improve site architecture and add features to Orcamap

[ivanoats]

Project - Improve site architecture and add features to the Orcamap

Bring the orcamap features over to a new repo orcamap-react in order to improve code organization, testability, and integration with the orcasite repo.

When an orca call is detected through the Orcasound web app (by humans and/or machines), visualize it spatially by plotting it on a dynamic map.

Orcasound community member Christian Sarason developed an open-source repository that contains code to create a Map-box based interface that can both accept user input (a series of points where orcas have been seen or heard) and display locations as confirmed after they have been vetted through by experts via a Google spreadsheet. As tracked in the Orcamap development Trello board, there are three top-requested features could be added this summer: hydrophone locations that “light up” when orcas are being heard via the Orcasound web app; a scale bar to aid accurate input of sighting data; and temporally-filtered views (one of which could manifest as a dynamic map to replace the static ones currently within the v2 UI Orcasound web app). A stretch goal could be to visualize the movement of whales (e.g. by connecting dots with arrows) and the likely predicted locations (e.g. with a circle that grows according to the mean swim speed or orcas).

Required skills: Node, Javascript, Google sheets API, ReactJS
Bonus skills: Open Layers (MapBox)
Possible mentors: Ivan, Scott and Val (with technical assistance from Orcasound community member Christian)

References and open-source building blocks:

• Orcamap project synopsis in the Orcasound-wide on-boarding Gdoc
• Orcamap notes from hackathon - Nov 2020, including emerging real-time sighting data sources to complement acoustic presence/absence information...
• Deployed prototype

Orcasound Github issue for this project
Orcasound/orcamap-react repository

Please see orcasound/orcamap-react#23 and https://github.com/orcasound/orcamap-react/blob/main/CONTRIBUTING.md before commenting

[azanbinzahid]

Please update the issue link (to this) in Project Ideas doc.

[ivanoats]

@azanbinzahid done

[riteshsp2000]

Hey @ivanoats @azanbinzahid. I would like to work on this. Any plan of action as of now?

[Devesh21700Kumar]

i would like to take this one.. really excited to contribute here in GSOC 2021

[Devesh21700Kumar]

will we be given permissions to the google sheets key? i guess we need to add it in our env variables

[ivanoats]

We need to think of a better security policy if there are several contributors. For now, could you use your own google ID and google sheets API key? I think we would need an example sheet.

[Devesh21700Kumar]

We need to think of a better security policy if there are several contributors. For now, could you use your own google ID and google sheets API key? I think we would need an example sheet.

yeah figured so. I've created one for myself and have made a PR. Please do check it out

[arnab15]

@ivanoats I'm Arnab Sahoo, Currently pursuing undergraduate studies I'm a MERN stack developer and open-source Enthusiast. I'm very excited to contribute here to GSOC 2021. I want to work on this issue.

[ivanoats]

@arnab15 Please see https://github.com/orcasound/orcamap-react/blob/main/CONTRIBUTING.md and orcasound/orcamap-react#23

[imacchiavello]

i am really excited to be able to contribute here in GSOC 2021

[scottveirs]

@ivanoats @cpsarason I've added a few links in project description to help provide context, history, and the beginnings of a longer-range road map for the GSoC students. Also added a link to the prototype deployed via netlify.