# Export polygon from Aggregate **URL:** \ **Category:** Support\ **Created:** [October 17, 2018, 9:10am UTC](https://forum.getodk.org/t/export-polygon-from-aggregate/15740 "2018-10-17T09:10:29Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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 17, 2018, 2:16pm UTC](https://forum.getodk.org/t/export-polygon-from-aggregate/15740/2 "2018-10-17T14:16:23Z")
geometry storage into aggregate is not "standard". The string stores 4 dimension for each edge and ends with the first one (to close the line). We faced it and then created a function on PostgreSQL to generate proper geometries. So this post might help you if you store your datas into PostgreSQL : > [@Geo fields should be stored in wkt format (Well Known Text)](https://forum.getodk.org/t/geo-fields-should-be-stored-in-wkt-format-well-known-text/7048): > > Good evening everybody, I would like to suggest some improvement of the spatial data storage. Actually, geopoint are stored into 4 attributes (longitude, latitude, elevation and accuracy), Geotrace and geoshape are stored in a text field. The format of that string is not so simple. The use of Well Known Text format could be a great enhancement. All the databases supported by odk do understand that GIS format. [https://fr.wikipedia.org/wiki/Well-known\_text](https://fr.wikipedia.org/wiki/Well-known_text) Actually we have to create some fun sq… And, in any case, this discussion will be interesting to follow : [Add a GeoJSON export to Briefcase and Aggregate](https://forum.getodk.org/t/add-a-geojson-export-to-briefcase-and-aggregate/15184) --- _[View the full topic](https://forum.getodk.org/t/export-polygon-from-aggregate/15740)._