<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>Here some additional info: <a href="http://lin-ear-th-inking.blogspot.com/2020/06/jts-overlayng-noding-strategies.html">http://lin-ear-th-inking.blogspot.com/2020/06/jts-overlayng-noding-strategies.html</a></p>
<p>Maybe it would be good to open a QEP for this? Since I am not so familiar with QGIS inner architecture, it would be best if someone who knows it better, would start such a QEP.</p>
<p>I will suggest the Swiss QGIS user group to invest next year in data quality improvements - so any outcome/follow-up work of such a discussion could potentially be funded.</p>
<p>Andreas</p>
<p id="reply-intro">On 2020-11-27 09:16, Andreas Neumann wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div id="replybody1">
<div style="font-size: 10pt; font-family: Verdana,Geneva,sans-serif;">
<p>Hi,</p>
<p>GEOS 3.9 will have some significant improvements for us.</p>
<p>I'm citing from an e-mail thread from strk:</p>
<p><span>"GEOS-3.9 will have the new overlay engine enabled by default, so </span><span>nothing to do there. Martin (Davis) believes there will be no more </span><span>TopologyExceptions with the new code but I think in order to be </span><span>100% sure a fixed precision model should be used, which is possible </span><span>to do with the newly exposed functions taking a grid size. In case </span><span>QGIS uses some kind of precision model, it would be good to use those."</span></p>
<p><span>-----------</span></p>
<p>Recent QGIS versions also have a "precision / grid" setting per layer in the layer properties dialog (Geometry and Topology restrictions). There you could set the geometry precision, let's say to mm.</p>
<p>I'd like to discuss with you devs how the QGIS and GEOS precision settings can be "integrated" in the future - and used more extensively throughout QGIS. E.g. a processing algorithm or model could automatically read these values and pass them on to GEOS for running the geometry operations. Also, when using the interactive editing tools (e.g. splitting and merging, basically anything that involves GEOS), this precision setting should be honored.</p>
<p>I'd like to get an idea if this is useful/feasible and how much effort would be necessary (approximately) - will this require funding?</p>
<p>--------------</p>
<p>Also - it would be good to discuss when the switch to GEOS 3.9 will/should be made, esp. for OSGEO4W.</p>
<p>Thanks for joining this discussion,</p>
<p>Andreas</p>
</div>
</div>
<br />
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">_______________________________________________<br />QGIS-Developer mailing list<br /><a href="mailto:QGIS-Developer@lists.osgeo.org">QGIS-Developer@lists.osgeo.org</a><br />List info: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br />Unsubscribe: <a href="https://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank" rel="noopener noreferrer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a></div>
</blockquote>
<p><br /></p>
</body></html>