What is a CARTO Dataset?

Overview

A CARTO dataset is essentially a PostgreSQL table that has been processed for use within the CARTO platform. While the backend uses the term “table,” CARTO’s ecosystem refers to processed tables as “datasets.”

Why CARTO Datasets Matter

You should understand this distinction if you:

• Want to know how Postgres tables differ from CARTO datasets
• Are confused why a table created with CREATE TABLE() doesn’t appear in your dashboard

What Processing Adds

When a table becomes a CARTO dataset, three indexed columns are automatically added:

1. cartodb_id — A primary key with unique, non-null values
2. the_geom — Stores geometries (points, lines, polygons) in EPSG:4326 projection (WGS84)
3. the_geom_webmercator — A hidden field storing geometries in EPSG:3857 projection (Web Mercator), used for map rendering and automatically updated when the_geom changes

Additionally, triggers are added to automatically generate cartodb_id values and maintain indexes as new rows are inserted.

When Processing Occurs

Tables are automatically registered when imported through CARTO’s import API.

Manual Processing

If you create a table using PostgreSQL’s CREATE TABLE function via CARTO’s SQL API, manually process it using:

SELECT cdb_cartodbfytable({table_name});

Enterprise users must include the organization username:

SELECT cdb_cartodbfytable({username}, {table_name});