[QGIS-Developer] GSoC 2026 — Enhancing ogrinfo Processing Algorithms in QGIS

Valentin Buira valentin.buira at gmail.com
Mon Mar 9 13:02:52 PDT 2026


Hi Sionigdha

First off congrats to your first PR(s) merged, and taking on the 
challenge of a GSoC !

As Andreas said the missing ogrinfo parameter are already exposed as an 
advanced parameter. And you could theoretically achieve what you want 
with the "string concatenation" tool in modeler albeit with more 
difficulty than what you propose.
Also remember we can't outright remove an existing parameter. because it 
would break the API, but it can be set as deprecated and kept around, 
see [1 
<https://github.com/qgis/QGIS/commit/5bde6fec42ccc10b9fd1c4fc822fbe1a4ae05a30#diff-2f887124009e37c4f965e787aee9ac3c82f892ff2472580e037ab546d8369102R191>]
But overall I think it's a good idea to have them as separate parameters.

 > Make ogrinfojson output structured and chainable within the processing
 > framework  field count, feature count, geometry type, extent as named
 > outputs

* I think that's also a good idea to have more outputs like that in 
general. One thing that could be improved is that in the modeler, there 
is no specific output for extent, or CRS, we rely on a string output (
`QgsProcessingOutputString`) with a specific format to connect further 
in the parameters. I would like to see a One to One mapping between 
parameter and output type.

* Another way you could improve the output of the ogrinfo json is to 
take a step back and improve json handling in general in the processing. 
with a dedicated output and algorithms :  to flatten json, extract 
values etc...

It's up to you which direction you want to go. At the moment I think 
it's a bit light to be a GSoC proposal on it's own (And since you 
already contributed to GDAL/QGIS you might complete it too quickly :-)  
).  But it is good to have your own idea and I encourage you to build 
upon it, and to get more feedbacks on it.

If you want to lean more on the GDAL side, it is absolutely fine. But 
GDAL is not my area of expertise, I need to dive into the code a bit 
more myself before giving you confirmation that I can mentor you on this 
project. (Or maybe another person in the community could step in as a 
mentor ? )

Kind regards,
Valentin Buira

[1] 
https://github.com/qgis/QGIS/commit/5bde6fec42ccc10b9fd1c4fc822fbe1a4ae05a30#diff-2f887124009e37c4f965e787aee9ac3c82f892ff2472580e037ab546d8369102R191 
<https://github.com/qgis/QGIS/commit/5bde6fec42ccc10b9fd1c4fc822fbe1a4ae05a30#diff-2f887124009e37c4f965e787aee9ac3c82f892ff2472580e037ab546d8369102R191>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20260309/c4637892/attachment.htm>


More information about the QGIS-Developer mailing list