I have a custom query that returns latitude and longitude data. I spent hours trying to use it in a “Points on map” visual. The type has to be set to “geospatial” and it would only let me change the type to either decimal, integer, or string.
Long story short, after extreme frustration and following outdated documentation and AI that gave impossible/nonsense instructions, I realized you have to use the old legacy dataset editor to have geospatial as an option. I tried everything in the new one. It is nowhere to be found. In the legacy version it auto detects geospatial fields and lists it as an option.
The new dataset editor also has a tiny little window for writing code, and if you use your mouse scroll wheel it jumps WAY too far. You scroll just one tiny notch and it teleports you half way down your code.
The worst part is, after you realize the new one (which is set as the default now too!) is unusable, you can’t change back. You have to copy everything to a new dataset and make sure to choose legacy before you publish.