It seems that there is a limitation in joining data sets with longitude/latitude. Are there any workarounds to this problem? Would love to understand why this is a limitation and would like to recommend it be added to a feature request board.
I’ve found this resource to be helpful.
Let me know if that helps you.
Yes, @Max, this is a definite workaround. Thank you!
After following @Max’s provided steps I was able to build the desired dataset but now have realtime issues. The original dataset was created in QS with Custom SQL and joined to two Aurora datasets. This dataset can only be in Spice (no option for direct query) and it appears that there is a parent/child relationship between the original dataset and the dataset that I created from this one meaning that the new dataset cannot be realtime.
Can you join the two datasets in sql? That should be able to solve both problems.