<div dir="ltr">Subject: Re: GSoC 2026 Draft Proposal : JSON Handling Toolkit for the QGIS Processing Framework<br><br>Hi Valentin,<br>Thank you for the detailed feedback it's very helpful, and thanks for guiding through.<br>The point about the two-headed proposal makes complete sense. I've already started reworking the proposal to make the JSON toolkit the clear centre of gravity. The ogrinfo typed parameter work is out I'm replacing those weeks with 2 additional JSON algorithms (JSONFromAttributes and MergeJSONArrays), bringing the total to 6 C++ algorithms that together cover the full JSON data lifecycle inside a QGIS model.On the QEP I understand the timing issue you raised and appreciate you flagging it. I'll draft the QEP during the community bonding period and submit it for community review before coding begins, so it doesn't block the proposal submission if that is fine?<br>I also went through the Qt JSON documentation you linked. The implementation plan is built entirely around Qt's built-in JSON classes QJsonDocument, QJsonObject, QJsonArray, and QJsonValue no third-party libraries needed.<br>I'll share the updated proposal with you .Please let me know if there's anything else you'd like me to address.<br>Kind regards,<br>Sionigdha</div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, 17 Mar 2026 at 17:14, Valentin Buira <<a href="mailto:valentin.buira@gmail.com">valentin.buira@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="auto"><div>Hi Sionigdha, </div><div><br></div><div>I concur with Nyall on the technical part, new algorithms require a c++ implementation, thought you don't have to write a json parser from scratch, take a look at how json is handled in Qt [1]</div><div><br></div><div>On another note, I know you were initially interested in GDAL, but you run the risk to have a "two headed proposal" . Maybe changing the input parameters of GDAL algorithms is not the core of your proposal ? And more JSON integration / algorithms would be more suitable for the proposal ? </div><div><br></div><div>>
Just FYI you'll need to submit a QEP before doing any of this work -- see <a href="https://github.com/qgis/QGIS-Enhancement-Proposals" rel="noreferrer noreferrer" target="_blank">https://github.com/qgis/QGIS-Enhancement-Proposals</a>.</div><div><br></div><div>An accepted QEP would certainly weigh in your favor for your proposal. But the deadline for submission of the GSoC is on 31 March, which makes it really tight for the QEP process to go through.</div><div><br></div><div>
When I advertised GSoC[2] I did not mention the QEP process, and I would prefer not changing the requirements midway.</div><div><br></div><div><br></div><div><br></div><div>Lastly a note for potential mentors and the QGIS maintainers : </div><div><br></div><div>The articulation between GSoC and QEP needs to be clarify:</div><div><br></div><div>* Historically on the last two GSoC proposals we had (2024 and 2019), there were no QEP</div><div>* OSGeo requires it's own template for a proposal that is different from our QEP</div><div>* I'd like to keep GSoC as a space of freedom of experimentation, sandbox for idea etc... which could clash with the consensus nature of the QEP</div><div>* But... At the same time a GSoC without a QEP runs the risk of not getting merged in the end. </div><div>* When I wrote the GSoC ideas this year I took care of not diving into technical details nor writing a QEP because I believe it's the student's job to write it and gain insight of the source code from it.</div><div>* Do we want students to invest time in a QEP while they are not sure of being accepted ? Or just improve their initial proposal instead ? Should we reserve the QEP for the community bounding periods ?</div><div><br></div><div>
<div> Maybe we could change the GSoC process for next year ? Any thoughts on this @Nyall ? </div>
<br></div><div>Kind regards,</div><div>Valentin</div><div dir="auto"><br></div><div dir="auto">[1] <a href="https://doc.qt.io/qt-6/json.html" target="_blank">https://doc.qt.io/qt-6/json.html</a></div><div dir="auto">[2] <a href="https://github.com/qgis/QGIS/wiki/Google-Summer-of-Code-2026-Ideas" target="_blank">https://github.com/qgis/QGIS/wiki/Google-Summer-of-Code-2026-Ideas</a><br><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">Le mar. 17 mars 2026, 07:00, Nyall Dawson <<a href="mailto:nyall.dawson@gmail.com" rel="noreferrer" target="_blank">nyall.dawson@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 17 Mar 2026 at 15:52, Sionigdha Sadhukhan via QGIS-Developer <<a href="mailto:qgis-developer@lists.osgeo.org" rel="noreferrer noreferrer" target="_blank">qgis-developer@lists.osgeo.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div id="m_-7393103621381406068m_-8891501101028496414m_-2605334531069251020m_-2929603130124222488m_-2717309708719966844gmail-:13c" style="direction:ltr;margin:8px 0px 0px;padding:0px;font-size:0.875rem;overflow-x:hidden;font-family:"Google Sans",Roboto,RobotoDraft,Helvetica,Arial,sans-serif"><div id="m_-7393103621381406068m_-8891501101028496414m_-2605334531069251020m_-2929603130124222488m_-2717309708719966844gmail-:13d" style="direction:ltr;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;font-size-adjust:none;font-kerning:auto;font-feature-settings:normal;font-stretch:normal;font-size:small;line-height:1.5;font-family:Arial,Helvetica,sans-serif;overflow:auto hidden"><div id="m_-7393103621381406068m_-8891501101028496414m_-2605334531069251020m_-2929603130124222488m_-2717309708719966844gmail-avWBGd-161"><div dir="ltr"><p>Hello,</p><p>I’ve prepared a draft of my GSoC proposal for improving JSON handling in the QGIS Processing framework and wanted to share it here and recieve your valuable feedback.</p><p>I’ve attached the current version.I tried to incorporate the earlier suggestion about looking at JSON handling more broadly in the processing framework rather than focusing only on the <code>ogrinfo</code> parameters. If there’s anything that seems unclear, unrealistic, or that should be approached differently, I would really appreciate any feedback.</p></div></div></div></div></div></blockquote><div><br></div><div>Thanks for sending this through Sionigdha!</div><div><br></div><div>Just FYI you'll need to submit a QEP before doing any of this work -- see <a href="https://github.com/qgis/QGIS-Enhancement-Proposals" rel="noreferrer noreferrer" target="_blank">https://github.com/qgis/QGIS-Enhancement-Proposals</a>. One sticking point that stood out to me is that you're proposing to implement the new algorithms in Python. That's explicitly blocked now, we want all new algorithms to be written in c++ (unless they rely on a specific python library).</div><div><br></div><div>Kind regards,</div><div>Nyall</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div id="m_-7393103621381406068m_-8891501101028496414m_-2605334531069251020m_-2929603130124222488m_-2717309708719966844gmail-:13c" style="direction:ltr;margin:8px 0px 0px;padding:0px;font-size:0.875rem;overflow-x:hidden;font-family:"Google Sans",Roboto,RobotoDraft,Helvetica,Arial,sans-serif"><div id="m_-7393103621381406068m_-8891501101028496414m_-2605334531069251020m_-2929603130124222488m_-2717309708719966844gmail-:13d" style="direction:ltr;font-variant-numeric:normal;font-variant-east-asian:normal;font-variant-alternates:normal;font-size-adjust:none;font-kerning:auto;font-feature-settings:normal;font-stretch:normal;font-size:small;line-height:1.5;font-family:Arial,Helvetica,sans-serif;overflow:auto hidden"><div id="m_-7393103621381406068m_-8891501101028496414m_-2605334531069251020m_-2929603130124222488m_-2717309708719966844gmail-avWBGd-161"><div dir="ltr"><p>Thanks for your time.</p><p>Kind regards,<font color="#888888"><br>Sionigdha.</font></p></div><div></div><div></div></div></div></div><div id="m_-7393103621381406068m_-8891501101028496414m_-2605334531069251020m_-2929603130124222488m_-2717309708719966844gmail-:131" style="font-size:0.875rem;margin:15px 0px;clear:both;font-family:"Google Sans",Roboto,RobotoDraft,Helvetica,Arial,sans-serif"></div><br></div>
_______________________________________________<br>
QGIS-Developer mailing list<br>
<a href="mailto:QGIS-Developer@lists.osgeo.org" rel="noreferrer noreferrer" target="_blank">QGIS-Developer@lists.osgeo.org</a><br>
List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</blockquote></div></div>
</blockquote></div></div></div>
</div>
</blockquote></div>