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 Afr…

Hi @DanielH see also [image] Quicksight dividing latitude and longitude values by 1000 Question & Answer 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 t…

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

Q&A

DanielH November 7, 2023, 2:40pm 3

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

After joining the datasets, the latitude-longitude value changes

Topic		Replies	Views
Quicksight dividing latitude and longitude values by 1000 Q&A formatting , quick-sight , visuals , dataset , Business-Intelligence-Engineer	8	1307	November 12, 2024
Longitude and latitude not working Q&A quick-sight , Business-Intelligence-Engineer	3	198	March 14, 2025
After joining the datasets, the latitude-longitude value changes Q&A error , quick-sight , Business-Intelligence-Engineer	4	271	March 18, 2024
Issue with decimal formatting in latitude and longitude Fields on Quick Sight Points on maps Q&A error , quick-sight , dashboard , Business-Intelligence-Engineer	6	392	April 29, 2024
Rounded Longitud Field in Quick Sight dataset definition from Athena Connector Q&A data-source , feature-request , quick-sight	5	437	September 5, 2023

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

Related topics