mistercrunch commented on issue #3337: Error in SQL Query results on Spatial columns URL: https://github.com/apache/incubator-superset/issues/3337#issuecomment-323438290 What is the database backend? Postgres? Druid? One path towards a solution is to improve the json serializer function `utils.json_iso_dttm_ser` to handle that specific object type in a specific way. We may want Superset to support some sort of spacial pivot format that we'd serialize towards. Something as simple as `[lat, long]` in json. Then we'd have to add support for that in a fancy spacial control where you'd have the choice to select one of these new spacial column, or point to a 2 different columns for lat and long (like we do currently in the mapbox viz). People may have a spacial column, or they may have a lat and a long column. Superset should work with both. In the meantime, if you just want stuff to work, you need to write 2 column expressions, one for lat and one for long, using your database's engine builtin function. I'd assume there's some sort of `get_longitude(spacial_typed_column)` function you can use, and used that in the mapbox viz. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
With regards, Apache Git Services
