Hi @annakrat ,
I’m currently preparing my proposal for “Adding JSON output to different tools” in GRASS and drafting a list of modules to reference in the timeline section.
At the moment, I have included the following modules:
v.qcount, r.surf.area, v.normal, g.gisenv, r.coin, r.quantile, r.sunmask, r.covar, r3.stats, v.proj, t.info, v.net, v.build, v.clean
I have not yet reviewed the Python tools in depth, and I still need to examine the grass-addons repository to identify additional suitable candidates.
Could you please let me know whether these modules seem like reasonable choices, or if there are other tools you would recommend prioritizing instead?
Also, I am still refining my proposal, but I would appreciate a quick review if possible:
Proposal Link
(Note: I have referenced NumFOCUS since GRASS participates in GSoC under it.)
Thank you for your guidance.
Some addon tools that might benefit from JSON support are r.neighborhoodmatrix, v.neighborhoodmatrix, r.stream.stats, v.nnstat, r3.profile, and r3.what.
Also, for r3.profile, I noticed some examples referencing r.profile in the documentation, maybe I’m wrong here, but shouldn’t those be r3.profile instead? I haven’t reviewed it fully yet, just asking.
Thanks! These look relevant overall. The particular order is not that important, we would finalize the choice and priorities later on. The title should have the project name in it (given NumFOCUS is an umbrella organization) and note that GRASS has dropped GIS from it’s name.
One thing to consider is we are probably going to have multiple people applying for this topic. I am not sure what are the current rules about submitting more applications, but it may be worth looking into other topics you would be interested in.
1 Like