GSoC 2025: Week 1 Report | Add JSON output to different tools in C for GRASS

[Nishant]

1. What did I get done this week?

• g.mapset: Added JSON output support, now you can use -p and -l flags (with format=json) to get JSON-formatted results. (See PR #5810)
• r.univar: Fixed a bug causing an uninitialized zone_value. (See PR #5821)
• r.what.color: Implemented JSON output support. (See PR #5822)
• r.info (regression tests): To maintain backward compatibility while updating its interface, I added strong regression tests. (See PR #5842)
• r.info (interface improvements): Began improving the module’s interface. (See PR #5859)

2. What do I plan on doing next week?

• Address review comments on my open PRs.
• Add JSON output support to g.version (see issue #5816).
• Add JSON output support to i.group (see issue #5815).
• If time permits, write tests for r.stats (see issue #5814).

Question for mentors:

Are these weekly deliverables sufficient for the project, or should I push myself further? The timeline has shifted from my original plan, so I’d appreciate your guidance.

3. Am I blocked on anything?

• No, I am not currently blocked on anything.

4. Additional Information

• Project Wiki Page: GRASS GSoC 2025 Add JSON output to different tools in C - GRASS-Wiki
• Public Repository: GitHub - NishantBansal2003/grass: GRASS GIS - free and open-source geospatial processing engine
• Personal Wiki Page: User:Nishantbansal2003 - OSGeo

– Nishant Bansal

[annakrat]

@Nishant

Are these weekly deliverables sufficient for the project, or should I push myself further? The timeline has shifted from my original plan, so I’d appreciate your guidance.

We need to shift that, the priorities have changed and that’s fine. Priority is to have tools with well designed and correct behavior, the quantity is secondary.