LogoLogo
HomeAcademyLoginTry for free
  • Welcome
  • What's new
    • Q2 2025
    • Q1 2025
    • Q4 2024
    • Q3 2024
    • Q2 2024
    • Q1 2024
    • Q4 2023
    • Q3 2023
    • Q2 2023
    • Q1 2023
    • Q4 2022
    • Q3 2022
  • FAQs
    • Accounts
    • Migration to the new platform
    • User & organization setup
    • General
    • Builder
    • Workflows
    • Data Observatory
    • Analytics Toolbox
    • Development Tools
    • Deployment Options
    • CARTO Basemaps
    • CARTO for Education
    • Support Packages
    • Security and Compliance
  • Getting started
    • What is CARTO?
    • Quickstart guides
      • Connecting to your data
      • Creating your first map
      • Creating your first workflow
      • Developing your first application
    • CARTO Academy
  • CARTO User Manual
    • Overview
      • Creating your CARTO organization
      • CARTO Cloud Regions
      • CARTO Workspace overview
    • Maps
      • Data sources
        • Simple features
        • Spatial Indexes
        • Pre-generated tilesets
        • Rasters
        • Defining source spatial data
        • Managing data freshness
        • Changing data source location
      • Layers
        • Point
          • Grid point aggregation
          • H3 point aggregation
          • Heatmap point aggregation
          • Cluster point aggregation
        • Polygon
        • Line
        • Grid
        • H3
        • Raster
        • Zoom to layer
      • Widgets
        • Formula widget
        • Category widget
        • Pie widget
        • Histogram widget
        • Range widget
        • Time Series widget
        • Table widget
      • SQL Parameters
        • Date parameter
        • Text parameter
        • Numeric parameter
        • Publishing SQL parameters
      • Interactions
      • Legend
      • Basemaps
        • Basemap selector
      • AI Agents
      • SQL analyses
      • Map view modes
      • Map description
      • Feature selection tool
      • Search locations
      • Measure distances
      • Exporting data
      • Download PDF reports
      • Managing maps
      • Sharing and collaboration
        • Editor collaboration
        • Map preview for editors
        • Map settings for viewers
        • Comments
        • Embedding maps
        • URL parameters
      • Performance considerations
    • Workflows
      • Workflow canvas
      • Results panel
      • Components
        • Aggregation
        • Custom
        • Data Enrichment
        • Data Preparation
        • Generative AI
        • Input / Output
        • Joins
        • Parsers
        • Raster Operations
        • Spatial Accessors
        • Spatial Analysis
        • Spatial Constructors
        • Spatial Indexes
        • Spatial Operations
        • Statistics
        • Tileset Creation
        • BigQuery ML
        • Snowflake ML
        • Google Earth Engine
        • Google Environment APIs
        • Telco Signal Propagation Models
      • Data Sources
      • Scheduling workflows
      • Sharing workflows
      • Using variables in workflows
      • Executing workflows via API
      • Temporary data in Workflows
      • Extension Packages
      • Managing workflows
      • Workflows best practices
    • Data Explorer
      • Creating a map from your data
      • Importing data
        • Importing rasters
      • Geocoding data
      • Optimizing your data
    • Data Observatory
      • Terminology
      • Browsing the Spatial Data Catalog
      • Subscribing to public and premium datasets
      • Accessing free data samples
      • Managing your subscriptions
      • Accessing your subscriptions from your data warehouse
        • Access data in BigQuery
        • Access data in Snowflake
        • Access data in Databricks
        • Access data in Redshift
        • Access data in PostgreSQL
    • Connections
      • Google BigQuery
      • Snowflake
      • Databricks
      • Amazon Redshift
      • PostgreSQL
      • CARTO Data Warehouse
      • Sharing connections
      • Deleting a connection
      • Required permissions
      • IP whitelisting
      • Customer data responsibilities
    • Applications
    • Settings
      • Understanding your organization quotas
      • Activity Data
        • Activity Data Reference
        • Activity Data Examples
        • Activity Data Changelog
      • Users and Groups
        • Inviting users to your organization
        • Managing user roles
        • Deleting users
        • SSO
        • Groups
        • Mapping groups to user roles
      • CARTO Support Access
      • Customizations
        • Customizing appearance and branding
        • Configuring custom color palettes
        • Configuring your organization basemaps
        • Enabling AI Agents
      • Advanced Settings
        • Managing applications
        • Configuring S3 Bucket for Redshift Imports
        • Configuring OAuth connections to Snowflake
        • Configuring OAuth U2M connections to Databricks
        • Configuring S3 Bucket integration for RDS for PostgreSQL Exports in Builder
        • Configuring Workload Identity Federation for BigQuery
      • Data Observatory
      • Deleting your organization
    • Developers
      • Managing Credentials
        • API Base URL
        • API Access Tokens
        • SPA OAuth Clients
        • M2M OAuth Clients
      • Named Sources
  • Data and Analysis
    • Analytics Toolbox Overview
    • Analytics Toolbox for BigQuery
      • Getting access
        • Projects maintained by CARTO in different BigQuery regions
        • Manual installation in your own project
        • Installation in a Google Cloud VPC
        • Core module
      • Key concepts
        • Tilesets
        • Spatial indexes
      • SQL Reference
        • accessors
        • clustering
        • constructors
        • cpg
        • data
        • http_request
        • import
        • geohash
        • h3
        • lds
        • measurements
        • placekey
        • processing
        • quadbin
        • random
        • raster
        • retail
        • routing
        • s2
        • statistics
        • telco
        • tiler
        • transformations
      • Guides
        • Running queries from Builder
        • Working with Raster data
      • Release notes
      • About Analytics Toolbox regions
    • Analytics Toolbox for Snowflake
      • Getting access
        • Native App from Snowflake's Marketplace
        • Manual installation
      • Key concepts
        • Spatial indexes
        • Tilesets
      • SQL Reference
        • accessors
        • clustering
        • constructors
        • data
        • http_request
        • import
        • h3
        • lds
        • measurements
        • placekey
        • processing
        • quadbin
        • random
        • raster
        • retail
        • s2
        • statistics
        • tiler
        • transformations
      • Guides
        • Running queries from Builder
        • Working with Raster data
      • Release Notes
    • Analytics Toolbox for Databricks
      • Getting access
        • Personal (former Single User) cluster
        • Standard (former Shared) cluster
      • Reference
        • lds
        • tiler
      • Guides
      • Release Notes
    • Analytics Toolbox for Redshift
      • Getting access
        • Manual installation in your database
        • Installation in an Amazon Web Services VPC
        • Core version
      • Key concepts
        • Tilesets
        • Spatial indexes
      • SQL Reference
        • clustering
        • constructors
        • data
        • http_request
        • import
        • lds
        • placekey
        • processing
        • quadbin
        • random
        • s2
        • statistics
        • tiler
        • transformations
      • Guides
        • Running queries from Builder
      • Release Notes
    • Analytics Toolbox for PostgreSQL
      • Getting access
        • Manual installation
        • Core version
      • Key concepts
        • Tilesets
        • Spatial Indexes
      • SQL Reference
        • h3
        • quadbin
        • tiler
      • Guides
        • Creating spatial index tilesets
        • Running queries from Builder
      • Release Notes
    • CARTO + Python
      • Installation
      • Authentication Methods
      • Visualizing Data
      • Working with Data
        • How to work with your data in the CARTO Data Warehouse
        • How to access your Data Observatory subscriptions
        • How to access CARTO's Analytics Toolbox for BigQuery and create visualizations via Python notebooks
        • How to access CARTO’s Analytics Toolbox for Snowflake and create visualizations via Python notebooks
        • How to visualize data from Databricks
      • Reference
    • CARTO QGIS Plugin
  • CARTO for Developers
    • Overview
    • Key concepts
      • Architecture
      • Libraries and APIs
      • Authentication methods
        • API Access Tokens
        • OAuth Access Tokens
        • OAuth Clients
      • Connections
      • Data sources
      • Visualization with deck.gl
        • Basemaps
          • CARTO Basemap
          • Google Maps
            • Examples
              • Gallery
              • Getting Started
              • Basic Examples
                • Hello World
                • BigQuery Tileset Layer
                • Data Observatory Tileset Layer
              • Advanced Examples
                • Arc Layer
                • Extrusion
                • Trips Layer
            • What's New
          • Amazon Location
            • Examples
              • Hello World
              • CartoLayer
            • What's New
        • Rapid Map Prototyping
      • Charts and widgets
      • Filtering and interactivity
      • Summary
    • Quickstart
      • Make your first API call
      • Visualize your first dataset
      • Create your first widget
    • Guides
      • Build a public application
      • Build a private application
      • Build a private application using SSO
      • Visualize massive datasets
      • Integrate CARTO in your existing application
      • Use Boundaries in your application
      • Avoid exposing SQL queries with Named Sources
      • Managing cache in your CARTO applications
    • Reference
      • Deck (@deck.gl reference)
      • Data Sources
        • vectorTableSource
        • vectorQuerySource
        • vectorTilesetSource
        • h3TableSource
        • h3QuerySource
        • h3TilesetSource
        • quadbinTableSource
        • quadbinQuerySource
        • quadbinTilesetSource
        • rasterSource
        • boundaryTableSource
        • boundaryQuerySource
      • Layers (@deck.gl/carto)
      • Widgets
        • Data Sources
        • Server-side vs. client-side
        • Models
          • getFormula
          • getCategories
          • getHistogram
          • getRange
          • getScatter
          • getTimeSeries
          • getTable
      • Filters
        • Column filters
        • Spatial filters
      • CARTO APIs Reference
    • Release Notes
    • Examples
    • CARTO for React
      • Guides
        • Getting Started
        • Views
        • Data Sources
        • Layers
        • Widgets
        • Authentication and Authorization
        • Basemaps
        • Look and Feel
        • Query Parameters
        • Code Generator
        • Sample Applications
        • Deployment
        • Upgrade Guide
      • Examples
      • Library Reference
        • Introduction
        • API
        • Auth
        • Basemaps
        • Core
        • Redux
        • UI
        • Widgets
      • Release Notes
  • CARTO Self-Hosted
    • Overview
    • Key concepts
      • Architecture
      • Deployment requirements
    • Quickstarts
      • Single VM deployment (Kots)
      • Orchestrated container deployment (Kots)
      • Advanced Orchestrated container deployment (Helm)
    • Guides
      • Guides (Kots)
        • Configure your own buckets
        • Configure an external in-memory cache
        • Enable Google Basemaps
        • Enable the CARTO Data Warehouse
        • Configure an external proxy
        • Enable BigQuery OAuth connections
        • Configure Single Sign-On (SSO)
        • Use Workload Identity in GCP
        • High availability configuration for CARTO Self-hosted
        • Configure your custom service account
      • Guides (Helm)
        • Configure your own buckets (Helm)
        • Configure an external in-memory cache (Helm)
        • Enable Google Basemaps (Helm)
        • Enable the CARTO Data Warehouse (Helm)
        • Configure an external proxy (Helm)
        • Enable BigQuery OAuth connections (Helm)
        • Configure Single Sign-On (SSO) (Helm)
        • Use Workload Identity in GCP (Helm)
        • Use EKS Pod Identity in AWS (Helm)
        • Enable Redshift imports (Helm)
        • Migrating CARTO Self-hosted installation to an external database (Helm)
        • Advanced customizations (Helm)
        • Configure your custom service account (Helm)
    • Maintenance
      • Maintenance (Kots)
        • Updates
        • Backups
        • Uninstall
        • Rotating keys
        • Monitoring
        • Change the Admin Console password
      • Maintenance (Helm)
        • Monitoring (Helm)
        • Rotating keys (Helm)
        • Uninstall (Helm)
        • Backups (Helm)
        • Updates (Helm)
    • Support
      • Get debug information for Support (Kots)
      • Get debug information for Support (Helm)
    • CARTO Self-hosted Legacy
      • Key concepts
        • Architecture
        • Deployment requirements
      • Quickstarts
        • Single VM deployment (docker-compose)
      • Guides
        • Configure your own buckets
        • Configure an external in-memory cache
        • Enable Google Basemaps
        • Enable the CARTO Data Warehouse
        • Configure an external proxy
        • Enable BigQuery OAuth connections
        • Configure Single Sign-On (SSO)
        • Enable Redshift imports
        • Configure your custom service account
        • Advanced customizations
        • Migrating CARTO Self-Hosted installation to an external database
      • Maintenance
        • Updates
        • Backups
        • Uninstall
        • Rotating keys
        • Monitoring
      • Support
    • Release Notes
  • CARTO Native App for Snowflake Containers
    • Deploying CARTO using Snowflake Container Services
  • Get Help
    • Legal & Compliance
    • Previous libraries and components
    • Migrating your content to the new CARTO platform
Powered by GitBook
On this page
  • Create H3 Aggregation Tileset
  • Create Point Aggregation Tileset
  • Create Quadbin Aggregation Tileset
  • Create Vector Tileset

Was this helpful?

Export as PDF
  1. CARTO User Manual
  2. Workflows
  3. Components

Tileset Creation

PreviousStatisticsNextBigQuery ML

Last updated 7 months ago

Was this helpful?

Components to create tilesets out of vector and spatial index data.

These components require installed in the chosen connection to build the workflow.

Valid table names for tileset's destination:

Provided FQNs need to follow convention on each data warehouse. Invalid names (according to each data warehouse constraints) will make the component fail. Check the documentation for each.

Create H3 Aggregation Tileset

Description

This component creates an aggregation tileset from an input containing H3 cell indexes. On each level of the tileset, cells will be aggregated into their parents, along with their associated properties.

Inputs

  • Input table: This component expects a table that has at least one column containing H3 indexes.

Settings

  • Tileset destination: select a destination that is available on your connection to store the resulting tileset table.

  • H3 column: The column in he input table that contains the H3 index.

  • H3 input data resolution: It is required to manually enter the actual resolution of the indexes contained in your input.

  • Minimum H3 tileset resolution: Your tileset will be generated at a range of different H3 resolutions. This setting specifies the minimum resolution in that range. Take into account that H3 resolutions don't match exactly the zoom levels in a web map.

  • Maximum H3 tileset resolution: Your tileset will be generated at a range of different H3 resolutions. This setting specifies the maximum resolution in that range. Take into account that H3 resolutions don't match exactly the zoom levels in a web map.

  • Aggregation resolution: On each resolution level in the range set by the minimum and maximum tileset resolution, cells will be aggregated into their parent cells, along with their properties. This setting controls the granularity of that aggregation. For example, let's take a dataset that contains H3 cells of resolution 14. When generating the lower resolution levels of the tileset (bigger cells), the original cells are smaller than a pixel on your screen and can't be visualized. In this case, assuming that 'Aggregation resolution' is set to 5:

    • at resolution 4, the original cells are going to be aggregated into their level 9 parents (4+5);

    • at resolution 5, original cells will be aggregated into their level 10 parents (5+5)s;

    • at resolution 6, original cells will be aggregated into their level 11 parents (6+5).

    • In general, cells will be aggregated into a resolution level that is the result of: current resolution level + aggregation resolution.

Taking the above into consideration, bear this formula in mind:

Maximum H3 tileset resolution + Aggregation resolution <= H3 input data resolution

If your settings don't follow this rule, you will get an error when generating the tileset.

  • Properties: Select a property from the input columns and an aggregation method to add aggregated properties to the tileset. The aggregation will be computed for every cell on each resolution level, considering the child cells in the input's data.

  • Add custom expression: Check this option to define additional custom properties. The custom properties are specified on a JSON object that needs to follow this format: { "new_prop_name": { "formula": "COUNT(*)", "type": "Number" }, "most_common_category": { "formula": "APPROX_TOP_COUNT(category, 1)[OFFSET(0)].value", "type": "String" }, ... } The expression in formula needs to follow your data warehouse's SQL syntax.

Advanced options

  • Metadata: Use this setting (as a JSON input) to define "name", "description" and "legend" metata objects to be included in the TileJSON. Other custom objects with arbitrary names can also be added, resulting in a "extra_metadata" object in the TileJSON.

Output

This component doesn't have an output that can be connected to other nodes downstream. The generated tileset will be stored on the specified destination table.

Create Point Aggregation Tileset

Description

This component creates a tileset from an input containing Points. It will aggregate points close to each other and their properties.

Inputs

  • Input table: This component expects a table that has at least one geospatial column containing points of type GEOMETRY or GEOGRAPHY column depending on the connection provider.

Settings

  • Tileset destination: select a destination that is available on your connection to store the resulting tileset table.

  • Geo column: A column in the input table that contains the Points.

  • Minimum zoom level: Your tileset will be generated at a range of different zoom levels. This setting specifies the lower limit in that range.

  • Maximum zoom level: Your tileset will be generated at a range of different zoom levels. This setting specifies the higher limit in that range.

  • Aggregation resolution: On each zoom level in the range set with the options above, points will be aggregated into a grid, along with their properties. This setting controls the granularity of that aggregation. In other words, it controls the the size of the grid cells used to compute the aggregation. For example, assuming the Aggregation resolution is set to 8:

    • at zoom level 6, the points will be aggregated into a grid where cells are equivalent to tiles of zoom level 14 (6+8).

    • At zoom level 7, the points will be aggregated into a grid where cells are equivalent to tiles of zoom level 15 (7+8).

    • At zoom level 8, the points will be aggregated into a grid where cells are equivalent to tiles of zoom level 16 (8+8).

    • In general, the size of the grid's cells is going to be determined by current zoom level + aggregation resolution.

  • Aggregation placement: Since points are aggregated into a grid, there are different options for the resulting placement:

    • cell-centroid: The resulting feature in the tileset is a point a the cell's centroid.

    • cell: The resulting feature in the tileset is the cell's boundary.

    • features-any: The resulting feature in the tileset is a random point from the ones that are being aggregated on that cell. This helps avoiding a gridded effect on the visualization

    • features-centroid: The resulting feature in the tileset is a point that represents the centroid of the points aggregated on that cell. This helps avoiding a gridded effect, while keeping a sense of the distribution of points within the cell.

  • Properties: Select a property from the input columns and an aggregation method to add aggregated properties to the tileset. The aggregation will be computed for every cell on each resolution level, considering the child cells in the input's data.

  • Add custom expression: Check this option to define additional custom properties. The custom properties are specified on a JSON object that needs to follow this format: { "new_prop_name": { "formula": "COUNT(*)", "type": "Number" }, "most_common_category": { "formula": "APPROX_TOP_COUNT(category, 1)[OFFSET(0)].value", "type": "String" }, ... } The expression in formula needs to follow your data warehouse's SQL syntax.

Advanced options

  • Minimum zoom column: A column that controls the minimum zoom level where that specific point should be considered to be included in the tile.

  • Maximum zoom column: A column that controls the maximum zoom level where that specific point should be considered to be included in the tile.

  • Maximum features per tile: The maximum number of features that can be included in the tileset. This setting is applied after the aggregation is computed. When the limit is reached, points are going to be dropped from the tile.

    • This setting is not available in all data warehouses.

  • Maximum kilobytes per tile: The maximum resulting size in kilobytes. This limit is based on an estimation that only considers the size of the geometries and not the included properties. When the limit is reached, points are going to be dropped from the tile.

    • This setting is not available in all data warehouses.

  • Tile feature order: When any of the limits above is reached, points are dropped from the tile. This setting expects a SQL expression to define the order of priority on the resulting points. The higher in the ordering, the less likely to be dropped.

  • Metadata: Use this setting (as a JSON input) to define "name", "description" and "legend" metata objects to be included in the TileJSON. Other custom objects with arbitrary names can also be added, resulting in a "extra_metadata" object in the TileJSON.

Output

This component doesn't have an output that can be connected to other nodes downstream. The generated tileset will be stored on the specified destination table.

Create Quadbin Aggregation Tileset

Description

This component creates an aggregation tileset from an input containing Quadbin cell indexes. On each level of the tileset, cells will be aggregated into their parents, along with their associated properties.

Inputs

  • Input table: This component expects a table that has at least one column containing H3 indexes.

Settings

  • Tileset destination: select a destination that is available on your connection to store the resulting tileset table.

  • Quadbin column: The column int he input table that contains the Quadbin index.

  • Quadbin input data resolution: It is required to manually enter the actual resolution of the indexes contained in your input.

  • Minimum Quadbin tileset resolution: Your tileset will be generated at a range of different Quadbin resolutions. This setting specifies the minimum resolution in that range. Take into account that Quadbin resolutions levels are equivalent to zoom levels on a CARTO map.

  • Maximum Quadbin tileset resolution: Your tileset will be generated at a range of different Quadbin resolutions. This setting specifies the maximum resolution in that range.

  • Aggregation resolution: On each resolution level in the range set by the minimum and maximum tileset resolution, cells will be aggregated into their parent cells, along with their properties. This setting controls the granularity of that aggregation. For example, let's take a dataset that contains Quadbin cells of resolution 14. When generating the lower resolution levels of the tileset (bigger cells), the original cells are smaller than a pixel on your screen and can't be visualized. In this case, assuming that 'Aggregation resolution' is set to 5:

    • at resolution 4, the original cells are going to be aggregated into their level 9 parents (4+5);

    • at resolution 5, original cells will be aggregated into their level 10 parents (5+5)s;

    • at resolution 6, original cells will be aggregated into their level 11 parents (6+5).

    • In general, cells will be aggregated into a resolution level that is the result of: current resolution level + aggregation resolution.

Taking the above into consideration, bear this formula in mind:

Maximum Quadbin tileset resolution + Aggregation resolution <= Quadbin input data resolution

If your settings don't follow this rule, you will get an error when generating the tileset.

  • Properties: Select a property from the input columns and an aggregation method to add aggregated properties to the tileset. The aggregation will be computed for every cell on each resolution level, considering the child cells in the input's data.

  • Add custom expression: Check this option to define additional custom properties. The custom properties are specified on a JSON object that needs to follow this format: { "new_prop_name": { "formula": "COUNT(*)", "type": "Number" }, "most_common_category": { "formula": "APPROX_TOP_COUNT(category, 1)[OFFSET(0)].value", "type": "String" }, ... } The expression in formula needs to follow your data warehouse's SQL syntax.

Advanced options

  • Metadata: Use this setting (as a JSON input) to define "name", "description" and "legend" metata objects to be included in the TileJSON. Other custom objects with arbitrary names can also be added, resulting in a "extra_metadata" object in the TileJSON.

Output

This component doesn't have an output that can be connected to other nodes downstream. The generated tileset will be stored on the specified destination table.

Create Vector Tileset

Description

This component creates a tileset from an input containing Point, Lines or Polygons.

Inputs

  • Input table: This component expects a table that has at least one geospatial column of type GEOMETRY or GEOGRAPHY depending on the connection provider.

Settings

  • Tileset destination: select a destination that is available on your connection to store the resulting tileset table.

  • Geo column: A column in the input table that contains the Points.

  • Minimum zoom level: Your tileset will be generated at a range of different zoom levels. This setting specifies the lower limit in that range.

  • Maximum zoom level: Your tileset will be generated at a range of different zoom levels. This setting specifies the higher limit in that range.

  • Properties: Select a list of properties from the input columns.

Advanced options

  • Minimum zoom column: A column that controls the minimum zoom level where that specific point should be considered to be included in the tile.

  • Maximum zoom column: A column that controls the maximum zoom level where that specific point should be considered to be included in the tile.

  • Maximum features per tile: The maximum number of features that can be included in the tileset. This setting is applied after the aggregation is computed. When the limit is reached, points are going to be dropped from the tile.

    • This setting is not available in all data warehouses.

  • Maximum kilobytes per tile: The maximum resulting size in kilobytes. This limit is based on an estimation that only considers the size of the geometries and not the included properties. When the limit is reached, points are going to be dropped from the tile.

    • This setting is not available in all data warehouses.

  • Tile feature order: When any of the limits above is reached, points are dropped from the tile. This setting expects a SQL expression to define the order of priority on the resulting points. The higher in the ordering, the less likely to be dropped.

  • Metadata: Use this setting (as a JSON input) to define "name", "description" and "legend" metata objects to be included in the TileJSON. Other custom objects with arbitrary names can also be added, resulting in a "extra_metadata" object in the TileJSON.

Output

This component doesn't have an output that can be connected to other nodes downstream. The generated tileset will be stored on the specified destination table.

Generate this tileset as a custom boundary for CARTO + deck.gl: Check this option if your tileset is going to be used as a boundary. .

the CARTO Analytics Toolbox
BigQuery
Snowflake
Databricks
Redshift
PostgreSQL
Learn more about Boundaries