Application for GSoC - Greta

GRASS GRASS developer
1

Hello everyone!

My name is Greta, and I’m excited to join this community. I’m from Spain, and I’m a programming instructor specializing in languages like Python and C++. I’ve been focusing on data modeling for some time now and am eager to give my knowledge a more practical direction. I want to apply what I’ve learned in real-world projects and contribute to the open-source community in GSoC program.

I am mainly motivated by the opportunity to work on projects that impact issues like sustainability, urban planning, and natural resource management. Through OSGeo, I can contribute to technologies that help address global challenges.

I’m particularly excited about the improvement project for grass.jupyter because I see the potential to enhance its accessibility and usability further. By contributing to this initiative, I hope to help make GRASS GIS even more intuitive so learners and practitioners can more easily engage with geospatial data analysis in an interactive environment.

For now, I’m testing the software to explore potential improvements and try creating a test for the library, as mentioned in the project description. I also planned to start with a GitHub issue labeled “good first issue.” I hope I’m on the right track.

1 Like
2

Hi Greta!

Welcome! Yes, you are on the right track. There are couple places you can start with. I saw your comment at r.proj: Add unit tests · Issue #2512 · OSGeo/grass · GitHub and that may not be the easiest task to start with, so I would suggest instead:

Also look at our contributing guidelines when contributing a PR. Feel free to ask if you are stuck. Looking forward to your contributions!

3

Thank you very much for your guidance! Today, I sent a pull request for the first one you recommended: r.proj: Add unit tests · Issue #2512 · OSGeo/grass · GitHub

4

Hi!

To create a test using pytest or unittest for a vector or raster, I searched for components that do not yet have tests. I found the following:

However, I’m unsure how to start writing tests for these two modules. Could you help me?

5

Maybe this guide can help: How to contribute to GRASS GIS development - Markus Neteler Consulting

For writing tests, you can look at the existing examples of test implementations to gain an understanding. For example, see:

For r.volume, check r.volume - GRASS GIS manual, and for v.decimate, see v.decimate - GRASS GIS manual.

1 Like
6

Hi everyone,

I’ve written the first draft of my GSoC project proposal, and I would appreciate any suggestions or feedback on improving it. Please let me know if you have any thoughts on how I can make it more precise, more detailed, or better aligned with the project goals.

Thank you in advance for your time and help!

7

Hi Greta,

I still need to talk to other mentors about the specific plan, there are couple options which features to implement. But in the meantime, can you please address [Feat] grass.jupyter.Map3D lacks save() method · Issue #5454 · OSGeo/grass · GitHub?

Thanks,
Anna

1 Like
8

I have already created the unit test for v.decimate. Now, how can I test it to check if it works correctly?

9

Ideally you would run it locally, from the testsuite directory run e.g python test_v_decimate. You can also open a PR and let it test in the CI.

10

I added a note there about the topic itself.

11

Regarding the project description, what is the preferred format? Is it better to present it in bullet points, or should I write it as a complete text, addressing each section of the template in a more narrative style?

12

Hi Greta,

You can have a look at last year’s accepted ideas here: GRASS GSoC Ideas 2024 - GRASS-Wiki.
If you go to the wiki pages, then you’ll find links to the proposals. Maybe that’s helpful :slight_smile:

Vero

13

Thanks! For now, I have improved the project using the information that annakrat and Corey gave me.