<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">ok then. I understood there was
something berried in the old geometry checker code , but thought
your question was about the new algorithm. </div>
<div class="moz-cite-prefix">The question then is to refactor, fix
and cleanup this old tool and susbequently the derived algorithms.</div>
<div class="moz-cite-prefix">I would personnaly choose the
deprecation way for this specifi algorithm. If it is buggy, and
really hard to understand, I bet its real life usage is close to
NULL. </div>
<div class="moz-cite-prefix">Deprecating can be a lot easier than
trying to fix it..</div>
<div class="moz-cite-prefix">If someone feels in a mission to clean
oldish and unused stuff, or willing to fund those little cleanups,
while contracting for something bigger, please raise your hand!</div>
<div class="moz-cite-prefix">Régis <br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 12/16/25 09:36, DelazJ via
QGIS-Developer wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAECJsSqrTsnPiHHx90vpdD+oFiJnvFjoAJDOvNmzL6crLgHeog@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Hi Régis (and devs),</div>
<div>Thanks for your input.</div>
<div>Just to clarify a point: it is not the algorithm the issue;
it is the original feature in the geometry checker that looks
buggy (tm). The algorithm (and this series of algorithms)
"simply" ports the features in the Geometry checker plugin to
Processing, as is, allowing them to be part of a workflow.</div>
<div>Anyway, according to git blame, the "Polygons must follow
boundaries" check was introduced 8 years ago in <a
href="https://github.com/qgis/QGIS/commit/13725362977087dc1fd818e04cb8b2b82a635b98#diff-533309df511fcadcebbb577daeb4098209b97c3a6f7cb8146b38159c59f48f80R593"
moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/qgis/QGIS/commit/13725362977087dc1fd818e04cb8b2b82a635b98#diff-533309df511fcadcebbb577daeb4098209b97c3a6f7cb8146b38159c59f48f80R593</a>
by Mani Sandro. The PR doesn't add much details on the feature
and there was almost no code review... Maybe does he (if still
around) remember what he tried to implement?</div>
<div><br>
</div>
<div>Kind regards,</div>
<div>Harrissou</div>
</div>
<br>
<div class="gmail_quote gmail_quote_container">
<div dir="ltr" class="gmail_attr">Le lun. 15 déc. 2025 à 21:39,
Régis Haubourg via QGIS-Developer <<a
href="mailto:qgis-developer@lists.osgeo.org"
moz-do-not-send="true" class="moz-txt-link-freetext">qgis-developer@lists.osgeo.org</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>
<div>Hi Harrissou, </div>
<div>I tried to understand the question and the history of
the QEP and PR discussions. </div>
<div>I think nobody can answer as long as such algorithm are
so difficult to understand. <br>
They will indeed never be used in real life if users need
to retro engineer the algorithm, just like you did with
Hefni. </div>
<div>Can I gently ask the developers originating this
feature to make a pedagogic effort towards our users, and
in this effort save our documentation team from such
headaches?</div>
<div>If there is a real use case, please also use real life
data to illustrate it. Test samples with square and
triangles are not helping that much. </div>
<div>All the best</div>
<div>Régis</div>
<div><br>
</div>
<div>On 11/21/25 10:17, DelazJ via QGIS-Developer wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div>Hi devs,</div>
<div>I didn't get any reply so I wonder if it is
because nobody knows, nobody cares, or something
else...</div>
<div>Other than the concern of "adding/keeping a
broken tool" in QGIS, we have a PR in the docs we
don't really know how to finalize, so a feedback
would be appreciated.</div>
<div><br>
</div>
<div>Thanks.</div>
<div>Regards,</div>
<div>Harrissou (for the docs team)</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Le mar. 28 oct.
2025 à 10:38, DelazJ <<a
href="mailto:delazj@gmail.com" target="_blank"
moz-do-not-send="true"
class="moz-txt-link-freetext">delazj@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>Hi Devs,</div>
<div>In the "Geometry checker" core plugin,
there is that option called "Polygons must
follow boundaries of layer ...", of which a
Processing alg "Polygons exceeding boundaries"
was recently created.</div>
<div>While testing the algorithm in order to
properly document it, we came across weird
results (also output by the geometry checker)
that we are unable to explain/understand their
coherence.</div>
<div><br>
</div>
<div>Issues and discussion are availabel at <a
href="https://github.com/qgis/QGIS/issues/63454" target="_blank"
moz-do-not-send="true"
class="moz-txt-link-freetext">https://github.com/qgis/QGIS/issues/63454</a>
and <a
href="https://github.com/qgis/QGIS-Documentation/pull/10314#issuecomment-3425649278"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://github.com/qgis/QGIS-Documentation/pull/10314#issuecomment-3425649278</a></div>
<div><br>
</div>
<div>1/ Does anyone <b>KNOW</b> how this option
is really supposed to check? and understand
the logic behind the output?</div>
<div>2/ If there is agreement that this tool
does not adress any real use case, is it
something we want to keep in QGIS (in this
state)?</div>
<div><br>
</div>
<div>Looking forward to your replies.</div>
<div>Regards,</div>
<div>Harrissou</div>
</div>
</blockquote>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
QGIS-Developer mailing list
<a href="mailto:QGIS-Developer@lists.osgeo.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">QGIS-Developer@lists.osgeo.org</a>
List info: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-developer"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
Unsubscribe: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-developer"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
</pre>
</blockquote>
<p><br>
</p>
</div>
_______________________________________________<br>
QGIS-Developer mailing list<br>
<a href="mailto:QGIS-Developer@lists.osgeo.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">QGIS-Developer@lists.osgeo.org</a><br>
List info: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-developer"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
Unsubscribe: <a
href="https://lists.osgeo.org/mailman/listinfo/qgis-developer"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
</blockquote>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">_______________________________________________
QGIS-Developer mailing list
<a class="moz-txt-link-abbreviated" href="mailto:QGIS-Developer@lists.osgeo.org">QGIS-Developer@lists.osgeo.org</a>
List info: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-developer">https://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>