'QuickSight "Geographical fields aren't supported in joins between data sources"
I've been trying to work around this issue for a couple of days by now without success so far.
Imagine you have these two dummy datasets
dataset_1
id,latitud,longitude
1,-0.023437,-0.070068
2,-0.069099,-0.069099
dataset_2
id,name
1,"site one"
2,"site two"
and you want to JOIN them by id. This is very straightforward with the QuickSight dataset editor. The issue happens when you change the data type of latitud and longitude to their geospatial type, since the error shown in the title pops-up and won't let you save the dataset.
The weird thing is that the error suggests the fields latitude and/or longitude being used to make the JOIN instead of id.
Before contacting AWS for a possible bug have anyone had and solved this issue before?
Solution 1:[1]
This seems to be a limitation with quicksight. Can you do the join in custom sql and then add the fields as geographical coordinates in data preparation?
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | darcoli |
