Introducing myself + a few GRASS contributions (Jupyter, tests, small fixes)

[Valyrian-Code]

Hi OSGeo community :] ,

I’m Rajveer (@Valyrian-Code on GitHub), a computer science student interested in open-source software and systems programming. I started contributing to GRASS to learn more about geospatial software and have been getting familiar with the project by building it from source, fixing bugs, and adding tests.

So far, I’ve contributed a few fixes and tests to both grass-tutorials and the main GRASS repository, including work on grass.jupyter, d.correlate, i.spectral, and test coverage improvements. A few of the open PRs:

• #7485 — d.correlate: exit on insufficient input + fix a reused-variable crash
• #7488 — i.spectral: fix the -t text output (was writing a Python tuple repr)
• #7489 — grass.jupyter: use the Tools API in reproject_latlon
• #7486 / #7487 — tests for grass.jupyter utils and r.colors.stddev

I’ve found myself particularly interested in the Jupyter/notebook experience, both through the tutorials and the grass.jupyter codebase.

A few quick questions:

• Is additional work on the Jupyter/notebook area currently needed, and is there someone I should coordinate with?

• For grass.jupyter, would more tests, Tools API migration, or feature work be most valuable?

• Are there any areas with known testing gaps or issues where contributions would be especially helpful?

Thanks for the warm community. I’m looking forward to learning more and contributing further.

Rajveer Bishnoi ✨
Linkedin : www.linkedin.com/in/rajveer-bishnoi-576b62356

[petrasovaa]

@Valyrian-Code thanks for the PRs, please give us time to get to your open PRs before submitting more, we have a large backlog.

[Valyrian-Code]

@Valyrian-Code thanks for the PRs, please give us time to get to your open PRs before submitting more, we have a large backlog.

Absolutely, no rush on the open PRs, I'll hold off on new ones while you work through the backlog. Whenever there's time later, I'd be glad to talk through the vector styling and legend direction, no hurry. Thanks for all you do on GRASS. ✌️

[Valyrian-Code]

Thanks for merging the r.sim.water and r.fillnulls PRs. As you suggested, I've been keeping new PRs small and focused while letting the existing queue gradually drain.

When there's time (no rush), I'd like to revisit the vector styling direction you mentioned for InteractiveMap.

At the moment, add_vector() passes styling directly through to the backend, which means users need to write backend-specific code such as:

• folium: style_function
• ipyleaflet: style and style_callback

As a result, styling is not portable between backends. Switching from one backend to another often requires rewriting styling logic, with opacity being the only option currently normalized across both.

I was thinking about introducing a small backend-agnostic styling layer consisting of:

1. Simple styling options (color, fill, weight, opacity, etc.) that are translated into the appropriate backend-specific representation.

2. Optional attribute-driven styling, such as:

   • Categorical styling (color by category/column value)
   • Graduated styling (continuous color ramps based on a numeric column)

The core translation logic could be implemented as a pure function, making it straightforward to unit test. Conceptually, it would be a natural extension of the existing opacity normalization.

Does that align with what you had in mind?

If so, I'd be happy to open an issue with a more detailed proposal before writing any code. And if you'd prefer that I wait until more of my open PRs are merged first, that's completely fine as well.

[Valyrian-Code]

Quick follow-up. Most of my open PRs have merged now, so the queue's looking a lot better. Since the InteractiveMap legend is already underway in #7072, I was thinking of moving on to vector styling next.

I'll open an issue first with the proposed design before writing any code. One quick question whenever you have a chance: should the styling follow d.vect's options, or would you prefer a simple GeoJSON-style dictionary?