# Pt-archiver - POINT data type and Cast / Convert Column

**URL:** <https://forums.percona.com/t/pt-archiver-point-data-type-and-cast-convert-column/34411>\
**Category:** Awards & Recognition\
**Created:** [October 16, 2024, 8:25pm UTC](https://forums.percona.com/t/pt-archiver-point-data-type-and-cast-convert-column/34411 "2024-10-16T20:25:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mulen](https://avatars.discourse-cdn.com/v4/letter/m/5fc32e/32.png) [@Mulen](https://forums.percona.com/u/Mulen)\
**Post date:** [October 16, 2024, 8:25pm UTC](https://forums.percona.com/t/pt-archiver-point-data-type-and-cast-convert-column/34411/1 "2024-10-16T20:25:13Z")

</div>

Hello.

We have a table that has a `POINT` data type column.

When we use pt-archiver to export to a csv file, the data for the `POINT` type column are a bunch of random gibberish text.

Also we can not use this file later to import it because it throws an error with these data.

Is it possible in pt-archiver to define the `--columns` option and try to convert the column, with the HEX() function so that we can have a csv file without these gibberish data?

For example something like `--columns id,HEX(coordinates)`

Is there another way to export correctly geometric data types?

Thank you.

---

<div class="post-metadata">

**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\
**Post date:** [October 17, 2024, 1:47pm UTC](https://forums.percona.com/t/pt-archiver-point-data-type-and-cast-convert-column/34411/2 "2024-10-17T13:47:39Z")

</div>

Hello @Mulen,  
This looks like a straight up bug for pt-archiver. I could not find any open bugs on it. Please open one at [https://jira.percona.com](https://jira.percona.com) and our toolkit team will investigate.