# Geoshape and (new function) intersections

**URL:** <https://forum.getodk.org/t/geoshape-and-new-function-intersections/57739>\
**Category:** Support\
**Tags:** odk-collect\
**Created:** [February 20, 2026, 12:35pm UTC](https://forum.getodk.org/t/geoshape-and-new-function-intersections/57739 "2026-02-20T12:35:33Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Grzesiek2010](https://getodk.b-cdn.net/user_avatar/forum.getodk.org/grzesiek2010/32/2881_2.png) [@Grzesiek2010](https://forum.getodk.org/u/Grzesiek2010)\
**Post date:** [February 25, 2026, 1:22pm UTC](https://forum.getodk.org/t/geoshape-and-new-function-intersections/57739/7 "2026-02-25T13:22:34Z")

</div>

Ahh, I see, the way coordinates are saved changed in v2026.1.

Previously, there was no space between two coordinate entries; they were separated only by a semicolon:

`19.53545266559179 -50.42645417153835 0.0 0.0;-10.748231888662367 -45.33697362989187 0.0 0.0;-0.8309302882938091 -12.323532029986382 0.0 0.0`

Because of that, `count-selected` treated it as 3 elements in each point, as explained in:[ODK geofence (v1)](https://forum.getodk.org/t/odk-geofence-v1/18656)

> Each geopoint actually consists of only three _list_ elements, because the accuracy value of the previous geopoint is prepended to the latitude of the latter, eg "0;-40.550261", except for the last geopoint.

Currently, there is a space and `count-selected` sees 4 elements in every point which makes more sense.

@Edmonds As I said above, please update your constraint from `(count-selected(.) -1) div 3` to `count-selected(.) div 4`.

---

_[View the full topic](https://forum.getodk.org/t/geoshape-and-new-function-intersections/57739)._