Custom SQL with Lat and Long fields won't let me create a map

Jaxx · February 6, 2023, 7:32pm

I am running into the same problem as in this closed issue:

github.com/metabase/metabase

Allow any numeric fields to be selected for lat/lon to support pin maps in SQL queries

opened 09:34PM - 25 May 17 UTC

closed 04:13PM - 31 May 20 UTC

camilonova

Visualization/ Visualization/Chart Settings

Seems it is supported if you have a column for latitude and a column for longitu…de, but since a database can have geospatial information it makes sense to support a PointField. In case is not possible to support a PointField, there is a way to split a column into the values supported by the current map implementation?

When I do an SQL query including latitude and longitude fields, the result does not let those fields be used for map visualizations because it is not recognizing them as latitude and longitude fields.

I am using version v0.40.1.

Is there any workaround or other way that I can do a query combining tables and use the result for map visualizations?

Luiggi · February 8, 2023, 12:07pm

My strongest suggestion is to upgrade to the latest version, as you're running a version that has a lot of bugs. Also, your version has a lot of security issues.