<div dir="ltr"><div class="gmail-ii gmail-gt" id="gmail-: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 class="gmail-a3s gmail-aiL" id="gmail-: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="gmail-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><p>Thanks for your time.</p><p>Kind regards,<font color="#888888"><br>Sionigdha.</font></p></div><div class="gmail-yj6qo"></div><div class="gmail-adL"></div></div></div></div><div class="gmail-hq gmail-gt" id="gmail-:131" style="font-size:0.875rem;margin:15px 0px;clear:both;font-family:"Google Sans",Roboto,RobotoDraft,Helvetica,Arial,sans-serif"></div><br class="gmail-Apple-interchange-newline"></div>