Builder

What methods can I use to create a map layer?

How can I run spatial analyses in Builder?

When working with SQL Editor in Builder I receive the following error message: "The geospatial support selected and the one used in the query are different"


What methods can I use to create a map layer?

To add a data source to a map as a new layer you can either:

  • Pick a table or tileset from one of your active connections to cloud data warehouses

  • Add data resulting from applying a custom SQL Query. You can also leverage the SQL functions available in CARTO’s Analytics Toolbox.

  • Importing data from a local or remote file. Right now we currently support GeoJSON, Shapefile (in a zip package), and CSV files. We’re working to support more formats in the future.


How can I run spatial analyses in Builder?

The SQL Editor (accessible when adding a data source as a custom query) allows you to push SQL commands directly to your cloud data warehouse, supporting everything you have available in that platform (e.g. BigQuery, Snowflake, etc.).

Additionally, you can also leverage the UDFs and store procedures that have been curated by us and which are part of the Analytics Toolbox.

In the coming months we will be adding more functionality into Builder in order to allow you to run spatial analysis with a click-based approach.


When working with SQL Editor in Builder I receive the following error message: "The geospatial support selected and the one used in the query are different"

When you encounter the error "The geospatial support selected and the one used in the query are different" in SQL Editor in Builder, it indicates Builder cannot identify a correct spatial data column and/or there is a mismatch between the column naming and the spatial data type used in your query. To resolve this:

  • For standard geometries like points, lines, and polygons, ensure your column is named geom.

  • For H3 Ids, the column should be named h3.

  • For Quadbin Ids, name the column quadbin.

  • Additionally, confirm that the spatial column's name correctly matches the expected spatial data type: geometry for standard geometries, h3 for H3 Ids, and quadbin for Quadbin Ids.

Last updated