[QGIS-Developer] Remove "Polygons must follow boundaries of layer ..." check in Geometry checker plugin?

[Régis Haubourg]

Hi Harrissou,
I tried to understand the question and the history of the QEP and PR 
discussions.
I think nobody can answer as long as such algorithm are so difficult to 
understand.
They will indeed never be used in real life if users need to retro 
engineer the algorithm, just like you did with Hefni.
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?
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.
All the best
Régis

On 11/21/25 10:17, DelazJ via QGIS-Developer wrote:
> Hi devs,
> I didn't get any reply so I wonder if it is because nobody knows, 
> nobody cares, or something else...
> 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.
>
> Thanks.
> Regards,
> Harrissou (for the docs team)
>
> Le mar. 28 oct. 2025 à 10:38, DelazJ <delazj at gmail.com> a écrit :
>
>     Hi Devs,
>     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.
>     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.
>
>     Issues and discussion are availabel at
>     https://github.com/qgis/QGIS/issues/63454 and
>     https://github.com/qgis/QGIS-Documentation/pull/10314#issuecomment-3425649278
>
>     1/ Does anyone *KNOW* how this option is really supposed to check?
>     and understand the logic behind the output?
>     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)?
>
>     Looking forward to your replies.
>     Regards,
>     Harrissou
>
>
> _______________________________________________
> QGIS-Developer mailing list
> QGIS-Developer at lists.osgeo.org
> List info:https://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe:https://lists.osgeo.org/mailman/listinfo/qgis-developer

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