# ODK code only sometime converts to accurate polygons on maps, but not always?

**URL:** <https://forum.getodk.org/t/odk-code-only-sometime-converts-to-accurate-polygons-on-maps-but-not-always/35346>\
**Category:** Support\
**Created:** [October 11, 2021, 12:06pm UTC](https://forum.getodk.org/t/odk-code-only-sometime-converts-to-accurate-polygons-on-maps-but-not-always/35346 "2021-10-11T12:06:37Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![mathieubossaert](https://getodk.b-cdn.net/user_avatar/forum.getodk.org/mathieubossaert/32/6131_2.png) [@mathieubossaert](https://forum.getodk.org/u/mathieubossaert)\
**Post date:** [October 14, 2021, 4:05pm UTC](https://forum.getodk.org/t/odk-code-only-sometime-converts-to-accurate-polygons-on-maps-but-not-always/35346/5 "2021-10-14T16:05:05Z")

</div>

I just post a new version of the sample geoshp2wkt xlsform here :

> [@ODK geoshape/geotrace/geopoint to WKT](https://forum.getodk.org/t/odk-geoshape-geotrace-geopoint-to-wkt/21062/17):
>
> Thanks to @Xiphware explanations here : I had a test to handle cases when geo strings contains '; ' as separator instead of the only semicolon. This problem occurs sometimes and @davidbaines faced it here : In such cases, point can be considered as a space-separated list of values with one more space and one more column index. [geoshape2wkt.xls](https://forum.getodk.org/uploads/short-url/3PIuAQdMai2wt1aqGqQWSzyaX8O.xls) (8 KB)

You should just have to adapt it it in your form. Please let me know if it is ok for you.

I tried it with both ";" and "; " separated geoshapes and it works fine 😉

---

_[View the full topic](https://forum.getodk.org/t/odk-code-only-sometime-converts-to-accurate-polygons-on-maps-but-not-always/35346)._