When importing latitude and longitude data into QuickSight, sometimes the scaling is wrong by a factor of 1/1000

[DanielH]

When importing place data with latitude and longitude columns from a PostgreSQL database into a QS Dataset, the imported data is sometimes divided by 1000 [UPDATE: Maybe it is not just the scaling].

Because of this all points are almost at the same location (somewhere in the ocean south of West Africa) although the points should be all over the UK.

This seems to happen only sometimes when creating the QuickSight Dataset from database data.

[ErikG]

Hi @DanielH
see also

Quicksight dividing latitude and longitude values by 1000

I am trying to create a “Points on map” visual in my Quicksight dashboard. The latitude and longitude values appear correct in the dataset, however when I try to use the fields in my map I see it has divided the original value by 1000. For example, a latitude of 40.8422403 in the dataset shows up as a value of .04 (which I’ve checked by viewing the latitude/longitude values in a table visual). The fields are correctly tagged as Latitude and Longitude in the dataset. This is making it impossible …

it is also an CSV datasets.
BR

[DanielH]

Casting the float value as decimal solved the issue for us.