# Understanding invalid polygon (Self-Intersecting) issues in Collect

**URL:** <https://forum.getodk.org/t/understanding-invalid-polygon-self-intersecting-issues-in-collect/56940>\
**Category:** Ideas\
**Tags:** collect\
**Created:** [October 17, 2025, 11:28pm UTC](https://forum.getodk.org/t/understanding-invalid-polygon-self-intersecting-issues-in-collect/56940 "2025-10-17T23:28:08Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![LN](https://getodk.b-cdn.net/user_avatar/forum.getodk.org/ln/32/1605_2.png) [@LN](https://forum.getodk.org/u/LN)\
**Post date:** [December 4, 2025, 7:21pm UTC](https://forum.getodk.org/t/understanding-invalid-polygon-self-intersecting-issues-in-collect/56940/15 "2025-12-04T19:21:02Z")

</div>

Many thanks to all who have chimed in here! I want to make sure you've seen [the latest proposal](https://forum.getodk.org/t/blocking-invalid-self-intersecting-polygons-in-collect/57009) for how we plan to give form designers the option to detect and reject self-intersections in lines and traces.

We have now released [v2025.4.0-beta.2](https://forum.getodk.org/t/odk-collect-v2025-4-beta-guidance-hints-shown-by-default-new-markup-and-signature-exit-dialog/56920/6) which includes an implementation for the [`intersects`](https://forum.getodk.org/t/odk-xforms-spec-proposal-add-intersects-xpath-function-to-detect-geotrace-shape-intersections/57121) function. You can try it out with [this form](https://docs.google.com/spreadsheets/d/1-g9W4MyUoHGk5Ajo7r6lJUNf75zH4rcrWJq1gq252Z8) and check @seadowg's math! You'll soon be able to use this function to give immediate feedback to data collectors within the trace/shape capture experience but also show warning notes or use it anywhere else you use functions.

One interesting thing to note is that some cases that look like intersections may not actually be. That's because points and lines are displayed with thickness that they don't have in reality. Here's an example where it looks like there are two intersections but none are computed because it's the fake thickness of the points/lines that intersect:

 ![screenshot-1764874669531](https://getodk.b-cdn.net/uploads/default/original/3X/1/8/188a8ffae947a39e41fe56e92b2d97c4fde384dc.png)

---

_[View the full topic](https://forum.getodk.org/t/understanding-invalid-polygon-self-intersecting-issues-in-collect/56940)._
