Rounded Longitud Field in QuickSight dataset definition from Athena Connector

Question & Answer
1

Hi,

I have the following value for my varchar column ‘gps_longitude’ defined in a Athena View table

image

If i try to convert this column to Geospatial Longitud Field in QuickSight, my values are rounded and after that, i obtain duplicated for some records when i group this values in a pointed map.

image
image1869×624 113 KB

does exists some work around to avoid QuickSight round my vaues?

Thanks in advance

2

Hi @dromeroc,

Welcome to QuickSight communities! We are glad to have you here!

Have you tried changing the number of decimal places in the Formatting options?

image

image

Kind regards,
Andres.

1 Like
3

Hi Andres,
Thanks for your answer.

Yes, i tried it. But at Analysis level, the field longitud is already rounded and the value does not change (It is already biased from the dataset editor), continuing with the same record:

image
image1162×749 143 KB

if i build a custom query, the result is same:

image
image733×657 51.1 KB

4

Hi,

I see, do you have a use case where the 7 decimal places on latitude and longitude are not enough? I was looking a little deeper at the precision and based on wiki it looks like 6 decimal places will give you .1m of accurancy and extrapolating 7 decimal places look like it will be .01m.

I am trying to find out documentation about the decimal accurancy on QuickSight, will let you know if I find something.

Kind regards,
Andres.

5

Hi Andres,thank you very much for your effort.
My geospatial data point acts as iot devices location, so i can have until 11 position for decimal scale over just 3 cases as following:

image
image1122×670 33.9 KB

Therefore, when i use visual pointed map with clustering, this 3 duplicates (for 7 scale positions) become in one record when grouping by geospatial fields, losing counting devices.

Thanks again Andres for your time.
Regards

6

Hi,

I have not found this piece of information in our documentation, I have asked for it to be reviewed and the specific details of the decimal possitions and the reason why it is set at 7 decimal.

I am sorry, but I cannot think of any workarround for this.

As at this moment we support only 7 decimal places and you need 11, I will tag this as a feature request.

Kind regards,
Andres.