# What's new

{% hint style="success" %}
This page will always reflect the latest changes in the CARTO platform. Older release notes will be archived and are available in the left menu and the search bar.
{% endhint %}

## Reorder categorical legend entries in Builder

April 20th, 2026

<mark style="color:orange;">**Improvement**</mark>  *Builder*

Categorical and ordinal legend entries can now be reordered in Builder to improve map readability.  Categories can be sorted by frequency or alphabetically, in ascending or descending order. \
\
Reordering only affects the legend’s reading order, colors remain fixed to each category, so the map visualization does not change.&#x20;

Learn more in our [Legend documentation](https://docs.carto.com/carto-user-manual/maps/legend).&#x20;

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2F45gPsbKWsIRQ0Saez1SN%2Flegendreordering.gif?alt=media&#x26;token=f3ac2bd2-4d32-4dca-b65b-d089c2e49985" alt=""><figcaption></figcaption></figure>

## Click interactions now show every overlapping feature

April 15th, 2026

<mark style="color:orange;">**Improvement**</mark>  *Builder*

Click interactions in Builder now paginate across every feature at clicked location, in both pop-up and info panel modes. When overlapping polygons, overlapping lines, or multiple records sharing the same geometry sit at the same spot, you can step through all of them within a layer instead of only seeing the top one. \
\
Previously, clicking a stacked location surfaced only a single feature and the rest were unreachable without zooming in or filtering the data. The new prev/next controls let you browse all of them, with the map highlighting updating as you paginate.&#x20;

Learn more in our [Click interactions documentation](https://docs.carto.com/carto-user-manual/maps/interactions#click-type-interactions).&#x20;

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2FNxB8l42Pe1SBMRaZ7JK1%2Fimage.png?alt=media&#x26;token=de4e3db0-ebcf-4052-adfa-e96c5b72fbad" alt=""><figcaption></figcaption></figure>

## Build AI-first spatial apps with CARTO Agentic Tools for developers

Mar 30th, 2026

<mark style="color:green;">**New**</mark> *CARTO for Developers*

Building AI-powered apps with geospatial capabilities just got a lot easier. We're releasing `@carto/agentic-deckgl`, an open-source TypeScript library built on [CARTO + deck.gl](https://carto.com/blog/modern-spatial-app-development-carto/) that lets any AI Agent create and style map layers, run spatial analytics, and interact with the map through natural language — with one npm install. It's framework-agnostic, includes Zod-validated tool definitions, a geospatial system prompt builder, and SDK converters for major AI frameworks.

The library gives AI Agents full control over the map experience: creating and styling vector tile, H3, GeoJSON, and raster layers from any CARTO data source; navigating the globe with smooth transitions; switching basemaps; placing and managing markers; applying spatial filters from user-drawn areas or analytical workflows; and managing widgets, visual effects, and layer ordering.

Learn more about this new library in our [product announcement](https://carto.com/blog/carto-agentic-tools-for-developers/).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2FcSGr8I4LEpeUId1KDoXO%2Fagentic-tools-zoom-california.gif?alt=media&#x26;token=156f3a62-d96c-404a-855b-868d03deb0aa" alt=""><figcaption></figcaption></figure>

## Create AI Agents through conversation with the new Configuration Assistant

Mar 30th, 2026

<mark style="color:green;">**New**</mark> *Builder*

Creating [AI Agents](https://docs.carto.com/carto-user-manual/ai-agents) just got significantly easier. The new **Agent Configuration Assistant** lets you design, set up, and iterate on your agents using natural language.

Instead of manually defining instructions, selecting tools, and configuring capabilities step by step, you can now **simply describe what your agent should do**. The Assistant generates a complete configuration for you — including the use case, structured instructions, model selection, tool setup, capabilities, and a tailored introduction message.

The Assistant is context-aware, meaning its recommendations are grounded in your actual map. It understands your datasets, layers, widgets, and available tools, helping you create more accurate and relevant agents from the start. You can refine any part of the configuration through conversation or combine it with manual edits for full control.

[Learn more about the Agent Config Assistant in our documentation.](https://docs.carto.com/carto-user-manual/ai-agents/agent-config-assistant)

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2FF7w08MUZpdwCUDwuAwvV%2Fassistant_final_smooth.gif?alt=media&#x26;token=53eebbd7-c590-4cbe-8ef5-b3cead2cdba1" alt=""><figcaption></figcaption></figure>

## Viewer Mode for Workflows

Mar 27th, 2026

<mark style="color:green;">**New**</mark> *Workflows*

Workflows can now be shared with **Viewer Mode**, allowing editors to publish interactive workflows that other users can run without editing the canvas. This opens up new possibilities for delivering analytical tools and reports to stakeholders and business users.

* **Viewer parameters**: Editors define which variables are exposed to viewers as configurable parameters, with custom display names and helper text. Supported types include Number, String, and the new **Geo** type, which lets viewers draw geographic features on a map.
* **Viewer Result Output**: A new component that defines which node's output is displayed to viewers, giving editors full control over what results are visible.
* **Viewer settings**: Granular controls over the viewer experience, including toggling the canvas visibility, SQL preview, data export, result caching, and more.

[Learn more about Viewer Mode in our documentation](https://docs.carto.com/carto-user-manual/workflows/viewer-mode).

{% embed url="<https://vimeo.com/1177627305?autoplay=1>" %}

## Claude 4.6 models now available for AI Agents

Mar 19th, 2026

<mark style="color:orange;">**Improvement**</mark> *CARTO platform*

We've expanded the AI models available for AI Agents with the latest generation of Anthropic models.

* **More CARTO-managed models:** Claude Opus 4.6 and Claude Sonnet 4.6 are now available out of the box with no additional configuration.
* **Broader bring-your-own-model support:** You can now use Claude Opus 4.6 and Claude Sonnet 4.6 through any of our supported providers, including Vertex AI, AWS Bedrock, Azure OpenAI, Anthropic, Snowflake Cortex, and Databricks Serving Model.

The 4.6 models deliver better performance across reasoning, tool usage, and complex geospatial workflows.

Configure your models in **Settings > CARTO A**I — see the [CARTO AI documentation](https://docs.carto.com/carto-user-manual/settings/carto-ai) for the full list of supported models and providers.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2F1QXZMM0yvXbMIGBy2A2k%2Fclaude-4.6.gif?alt=media&#x26;token=e305dcc2-3298-454c-9d5e-738b1102463d" alt=""><figcaption></figcaption></figure>

## Additional AI models to power your Agents

February 17th, 2026

<mark style="color:orange;">**Improvement**</mark> *CARTO platform*

We've expanded the AI models available for AI Agents with more advanced models from Anthropic, Google, and OpenAI.

* **More CARTO-managed models:** Claude Opus 4.5, Claude Sonnet 4.5, Gemini 3 Pro, and Gemini 3 Flash are now available out of the box with no additional configuration.
* **Broader bring-your-own-model support:** You can now use Gemini 3, Claude Opus 4.5, and GPT-5.2 through any of our supported providers, including Vertex AI, Google AI Studio, Snowflake Cortex, Databricks Serving Model, AWS Bedrock, Azure OpenAI, OpenAI, and Anthropic.

We recommend upgrading to the newest models available — you'll see a significant improvement in agent performance, reasoning, and tool usage.

Configure your models in **Settings > CARTO AI** — see the [CARTO AI documentation](https://docs.carto.com/carto-user-manual/settings/carto-ai) for the full list of supported models and providers.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2FrV1P5UZ0BRhACbbqzFlx%2Fnew%20models.gif?alt=media&#x26;token=1eb9b0cc-782b-473b-ae91-37d789bfcee6" alt=""><figcaption></figcaption></figure>

## AI Agents now create interactive charts

February 9th, 2026

<mark style="color:orange;">**Improvement**</mark> *Builder*

[AI Agents](https://docs.carto.com/carto-user-manual/ai-agents) can now generate and render interactive charts directly inside the conversation. Users can ask for data visualizations and see charts rendered inline — no need to leave the chat.

Charts expand the way AI Agents can communicate insights, complementing map layers with statistical visualizations like bar charts for comparisons, line charts for trends, or histograms for distributions. Combined with other tools, AI Agents can query your data, analyze it, and present findings in the format that best fits the question.

[Learn more about AI Agent tools in our documentation](https://docs.carto.com/carto-user-manual/ai-agents/working-with-tools).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fq5B1Vj4xgutx5ztqDdPL%2Frender_chart.png?alt=media&#x26;token=3bf38905-5a93-4307-b863-2185fbc8559d" alt=""><figcaption></figcaption></figure>

## Introducing our new Command-line Interface

January 29th, 2026

<mark style="color:green;">**New**</mark> *CARTO platform*

We're excited to announce the [CARTO CLI](https://carto.com/blog/carto-cli-automateed-carto-management-build-for-ai-agents), which brings command line power to your CARTO organization. Manage Maps, Workflows, connections and credentials; transfer assets between organizations, and query your organization's activity data; all from the terminal!

The CLI supports structured JSON output, non-interactive execution, and headless authentication, making it a natural interface to script and automate. To get started, head over to our [CARTO CLI documentation](https://docs.carto.com/carto-user-manual/carto-cli).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2FugXMuBXUzs4rloStI6a8%2Fimage.png?alt=media&#x26;token=89b2cfbd-2132-4ae5-81eb-0247ace0933f" alt="" width="375"><figcaption></figcaption></figure>

## Tracking activity data from public maps

January 29th, 2026

<mark style="color:orange;">**Improvement**</mark> *Workspace*

Public maps are the way to distribute geospatial data and insights across wider audiences outside your organization. From coverage maps to deforestation storytelling, many geospatial dashboards are making an impact on public websites thanks to CARTO.

Starting now, CARTO administrators can measure that impact, and answer questions like:

* **How many times my public maps have been viewed**
* **Which are my most active public maps**
* **How many exports from public maps last month...**

We've automatically added to our [Activity Data](https://docs.carto.com/carto-user-manual/settings/activity-data) the data coming from your public maps thanks to a robust, secure, event pipeline that can track millions of events coming from unauthenticated users.

To get started, simply [export your Activity Data](https://docs.carto.com/carto-user-manual/settings/activity-data) or [integrate it via API](https://docs.carto.com/carto-user-manual/settings/activity-data#access-via-api).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2F5pJkp7wQd8ASLnTvWUBL%2FActivity%20Data%20Public%20Maps.jpg?alt=media&#x26;token=1f6cf676-ef50-4fae-9ca5-cab97f1e97b1" alt=""><figcaption></figcaption></figure>

## New AI provider and LLM integrations to power your AI Agents

January 20th, 2026

<mark style="color:green;">**New**</mark> *CARTO platform*

CARTO now supports seven additional AI providers, expanding the AI and LLM integrations available to power **AI Agents**.

Previously limited to **OpenAI** and **Google AI Studio**, you can now connect AI Agents to models hosted on your preferred cloud or data platform:

* **Google Vertex AI**: Enterprise GCP deployments with service account authentication.
* **Amazon Bedrock**: Claude models through AWS infrastructure.
* **Snowflake Cortex**: AI models within your Snowflake environment.
* **Databricks Model Serving**: Models through Databricks endpoints.
* **Oracle Generative AI**: Access to models via OCI.
* **Anthropic**: Direct access to Claude models.
* **Azure OpenAI Service**: OpenAI models through Azure.

These new integrations allow AI Agents to run on your preferred cloud or data platform, leverage existing cloud contracts, meet data residency requirements, and access the latest large language models available from each provider.

Configure providers in **Settings > CARTO AI**. See the [CARTO AI documentation](https://docs.carto.com/carto-user-manual/settings/carto-ai) for setup instructions.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2FcfkBzHAMq1zw3mnBVtCY%2FScreenshot%202026-01-20%20at%2013.46.49.png?alt=media&#x26;token=81d2b9c0-a7ae-44b6-b8f4-cfed33e23f6f" alt=""><figcaption></figcaption></figure>

## CARTO Basemap labels now stay on top of your layers

January 14th, 2026

<mark style="color:orange;">**Improvement**</mark> *Builder*

When using CARTO Basemaps, labels (like city and street names) now automatically appear on top of your map layers instead of being hidden underneath them.

This makes it easier to read your maps, especially when working with multiple overlapping layers. You can still turn labels off in the basemap settings if you prefer a cleaner look.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2FRJ1gBuBvGxHSA307yRNk%2Finterleavebasemaps.gif?alt=media&#x26;token=03faacae-3f09-4904-8007-7ea686640fc3" alt=""><figcaption></figcaption></figure>

## H3-based isochrones powered by TravelTime

January 12th, 2026

<mark style="color:green;">**New**</mark> *Workflows, Analytics Toolbox*

A new capability is now available for generating **H3-based isochrones** using [TravelTime](https://docs.traveltime.com/api/reference/h3), expanding how accessibility and travel-time analysis can be performed in CARTO.

This release introduces a new endpoint in the **Location Data Services (LDS) API** that leverages TravelTime’s H3 isochrone support. In addition, corresponding functions are available in the **Analytics Toolbox** (for [BigQuery](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-bigquery/sql-reference/lds#create_h3_isolines), [Snowflake](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-snowflake/sql-reference/lds#create_h3_isolines), [Databricks](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-databricks/reference/lds#create_h3_isolines) and [Redshift](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-redshift/sql-reference/lds#create_h3_isolines)), along with a new [Create H3 Isolines](https://docs.carto.com/carto-user-manual/workflows/components/spatial-constructors#create-h3-isolines) component in **Workflows**, enabling low-code and programmatic access to this functionality.

Customers can now generate H3-indexed isochrones directly, with support for the same configuration options provided by the underlying TravelTime API, including **departure time** and **transport mode**. Using H3 as the output format simplifies downstream analysis, aggregation, and visualization, particularly for workflows that already rely on hexagonal indexing.

{% embed url="<https://vimeo.com/1153538127?autoplay=1>" %}

## Full support for new Databricks Spatial SQL functions and data types

January 7th, 2026

<mark style="color:green;">**New**</mark> *CARTO Platform*

A new [Databricks connection](https://docs.carto.com/carto-user-manual/connections/databricks) type is now generally available across all CARTO accounts, delivering deeper and more modern support for Databricks as a data warehouse and compute platform.

This integration adopts **Databricks SQL Warehouses** as the sole compute resource, providing a serverless, cloud-native experience without the need to manage traditional compute clusters. It also leverages Databricks’ [**native spatial capabilities**](https://www.databricks.com/blog/introducing-spatial-sql-databricks-80-functions-high-performance-geospatial-analytics?utm_source=chatgpt.com), including the GEOMETRY data type and Spatial SQL functions documented by Databricks, enabling efficient storage and processing of spatial data directly in SQL without external libraries.

Connectivity options include **Personal Access Tokens (PAT), M2M, and U2M integrations**, offering flexibility in how authentication and access are managed. Builder and Workflows fully support Databricks tables with geometry types out of the box, including query sources, SQL parameters, Location Data Services, and Create Builder Map workflows — no additional data preparation is required to work with spatial columns.

The [**Analytics Toolbox**](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-databricks) now installs directly into the Databricks Unity Catalog with no external dependencies, simplifying governance and deployment. Older Databricks connection types remain available for existing accounts that used them previously. This release represents a significant step in CARTO’s support for major cloud data warehouse providers and extends CARTO’s capabilities for spatial analytics on modern data platforms.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2FjzMdIw4iSZsSWPjv9N81%2FScreenshot%202026-01-07%20at%2016.38.04.png?alt=media&#x26;token=302e9390-aac7-424b-bb60-b54de226b6bf" alt=""><figcaption></figcaption></figure>

## Track map changes over time with Version history

December 29th, 2025

<mark style="color:green;">**New**</mark> *Builder*

We've introduced **Version history** in Builder, giving you the ability to track and manage different versions of your maps over time.

CARTO automatically saves versions as you work, and you can also manually save named versions to mark important milestones. You can view the full history of changes, restore any previous version to undo unwanted changes, or duplicate from a historical version to create variations without affecting the current map.

Version history works seamlessly with collaborative maps—all changes are tracked with the collaborator's name and timestamp, providing a complete audit trail. When you publish a map, the published version is marked with a badge so you always know which version is live.

[Learn more in our documentation](https://docs.carto.com/carto-user-manual/maps/version-history).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2FzrqGyD5Jq46G7A4OLOeL%2Fversion%20history.gif?alt=media&#x26;token=bffd7074-5f14-465b-9940-e511774ff44c" alt=""><figcaption></figcaption></figure>

## **New components to run spatial analytics techniques on embeddings from Geospatial Foundation Models**

December 12th, 2025

<mark style="color:green;">**New**</mark> *Workflows*

We’re introducing the **Analytics on Embeddings** extension package for **CARTO Workflows**, a new set of components that bring high-dimensional vector embedding analytics into spatial workflows. This extension enables users to analyze, cluster, compare, and visualize embedding representations (whether derived from geospatial foundation models, satellite data, or other spatial sources) directly within their Workflows pipelines.

Key capabilities in this package include:

* [**Change Detection**](https://docs.carto.com/carto-user-manual/workflows/components/embedding-analytics#change-detection): Quantifies temporal changes in embedding vectors to monitor dynamics over time.
* [**Clustering**](https://docs.carto.com/carto-user-manual/workflows/components/embedding-analytics#clustering): Groups locations based on similarity in embedding space, with optional dimensionality reduction to improve performance.
* [**Similarity Search**](https://docs.carto.com/carto-user-manual/workflows/components/embedding-analytics#similarity-search): Identifies regions with similar spatial or contextual characteristics relative to one or more reference locations.
* [**Visualization**](https://docs.carto.com/carto-user-manual/workflows/components/embedding-analytics#visualization): Converts high-dimensional embeddings into RGB colors for intuitive mapping and pattern discovery.

These components work seamlessly with embedding vectors stored as table columns and support integration with the [**Geospatial Foundation Models**](https://docs.carto.com/carto-user-manual/workflows/components/google-pdfm-embeddings) extension, enabling richer insights from learned representations without leaving the low-code Workflows environment.

## Manage developer credentials from the asset management table

December 9th, 2025

<mark style="color:orange;">**Improvement**</mark> *Workspace*

Superadmin users can now view and manage all developer credentials in their organization, including **API Access Tokens**, **SPA OAuth Clients**, and **M2M OAuth Clients**. From the Asset Management table of the settings, Superadmins now can:

* Find credentials by type, name and owner
* Transfer credentials to another user (only available for API Access Tokens and SPA OAuth Clients)
* Delete credentials

This improvement simplifies team collaboration by allowing credentials to be transferred between users seamlessly, preventing disruptions if the credential owner is unavailable or leaves.

For more information, see our section on the [Superadmin role](https://docs.carto.com/carto-user-manual/settings/users-and-groups/managing-user-roles#superadmin).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2FZfDkKXmo6rw1WyCoNgkV%2FScreenshot%202025-12-09%20at%2018.40.10.png?alt=media&#x26;token=8be444fd-9ca8-4b5e-bd3f-fb1d6d86da54" alt=""><figcaption></figcaption></figure>

## Unified access to Data Observatory subscriptions and improved subscription management

November 18th, 2025

<mark style="color:orange;">**Improvement**</mark> *Workspace*

With this release, we’re making it simpler and more consistent for users to access and work with data from their Data Observatory subscriptions. Access to data has now been fully unified to always be via your own data warehouse connections. Additionally we've also improved the way Admin users can manage the organization's Data Observatory subscriptions from the Settings section in the CARTO Workspace.

* We’ve unified access to the data from Data Observatory subscriptions to always be rom the end-user data warehouse connections. As announced earlier this year, we have **deprecated the Data Observatory tab in Data Explorer, Builder, and Workflows**. This tab previously exposed subscriptions only through a small set of connections (i.e. CARTO Data Warehouse and BigQuery US multi-region). Since all subscriptions are now available directly via data warehouse connections, the tab has been removed to avoid confusion.
* The [Data Observatory section](https://docs.carto.com/carto-user-manual/settings/data-observatory) in Settings has been significantly improved. It now serves as the central place to manage your organization’s subscriptions, showing to which data warehouse each subscription has been transferred, and allowing users to request new transfers so the data is available directly in their data warehouses.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-1857dc1829d33835dcd4f6ee47ce39f360b40696%2Fdosettings.png?alt=media" alt=""><figcaption></figcaption></figure>

## Starring data assets for quicker access

November 18th, 2025

<mark style="color:orange;">**Improvement**</mark> *Workspace*

Users are now able to star items at any level in the Data Explorer, including connections, projects/databases/schemas, and the data tables themselves. Simply click on the star icon next to any item in the Data Explorer and then use the *Starred only* filter to show just your starred items.

This is especially helpful to users that have connections or data assets that are recurrently used in their maps and workflows. No more browsing the data tree until you find what you need!

Your starred items are now also easily accessible from the "Add data source" flow in CARTO Builder and from the data sources panel in CARTO Workflows.

To learn more about starring items and the Data Explorer in general, check out our [documentation](https://docs.carto.com/carto-user-manual/data-explorer).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-a4b7b78aac7520f14522a3d78a526e8ae17eaf57%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

## Integrate CARTO maps anywhere with the new authenticated embeds and reactive map events

November 7th, 2025

<mark style="color:orange;">**Improvement**</mark> *Builder*

Embedding maps from CARTO in other webpages and applications just became exponentially easier and more powerful thanks to two additions to our platform:

* **New methods for seamless and secure private embedding:** We added two new strategies to embed private maps securely, without having to publish the map or forcing the users to login in a different tab or browser. Developers can also re-use existing authorization in their applications. [Learn more about private embedding strategies](https://docs.carto.com/carto-user-manual/maps/sharing-and-collaboration/embedding-maps#private-embedding).
* **Build bi-directional interactive experiences with our embedded events:** Embedded maps from CARTO now send `postMessage` events every time something changes in the map. This allows the parent application to react, creating bi-directional interactive experiences when combined with our embed URL parameters. [Learn more about embedding events](https://docs.carto.com/carto-user-manual/maps/sharing-and-collaboration/embedding-maps#listening-to-events-from-embedded-maps).

We're excited to see where you will embed your next CARTO map!

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-a2791068d7de978be682c5113cb37c4364641e30%2FScreenshot%202025-11-06%20at%2021.34.30.png?alt=media" alt=""><figcaption></figcaption></figure>

## New map interaction tools for AI Agents

November 6th, 2025

<mark style="color:green;">**New**</mark> *Builder*

AI Agents can now interact directly with your maps through two new tools:

**Dynamic marker placement**: Ask the AI Agent to mark specific locations, and it will instantly place markers on your map. Simply provide an address, place name, or coordinates—the agent handles geocoding and placement automatically.

**Spatial filtering by area**: The AI Agent can define custom areas of interest to filter your data dynamically. When an area is set, all map widgets and layers update automatically to show only data within that region.

These tools enable your AI Agent to provide immediate visual context and perform focused analysis on specific geographic areas without manual configuration.

[Learn more in our documentation](https://docs.carto.com/carto-user-manual/ai-agents/working-with-tools#map-tools).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-81034c8df363d93346073967272fccd4bcf248aa%2Fnew%20map%20interactions%20tools%20for%20ai%20agents.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Introducing Agentic GIS in CARTO: making spatial insights available to everyone

October 8th, 2025

<mark style="color:green;">**New**</mark> *Builder*

We are incredibly excited to announce new features that bring enterprise-grade geospatial agentic experiences to CARTO.

* **Introducing AI Agents in Builder:** [CARTO AI Agents](https://docs.carto.com/carto-user-manual/ai-agents) (now in General Availability) provide a conversational interface in your maps where your end users can get instant and actionable geospatial insights through natural language.
* **AI Agents can now query sources, generate layers and more:** We've added a ton of exciting capabilities that allow agents to reason and perform geospatial analysis autonomously.
* **Integrate Workflows as tools for your AI Agents:** From building operational dashboards to running complex analyses, your AI Agent can be supercharged with your own custom workflows [enabled as MCP tools](https://docs.carto.com/carto-user-manual/workflows/workflows-as-mcp-tools).
* **Evolved experience to tailor your Agent:** You can now reference tools, sources, and other context available in the map when customizing your agent.
* **Use your own AI models:** [Configure your own AI models](https://docs.carto.com/carto-user-manual/settings/carto-ai) and maintain total control over the AI technology used. Supported providers include Google Gemini and Open AI, with others coming soon.

With CARTO you can now create and share access to powerful geospatial AI Agents tailored to your specific needs. Combine your custom prompt instructions with CARTO's built-in geospatial intelligence and your own workflows, and **build trustworthy AI solutions that make complex geospatial analysis accessible to any user within your organization**.

Get started today by [enabling CARTO AI in your organization](https://docs.carto.com/carto-user-manual/settings/carto-ai).

And learn more about Agentic GIS in our [announcement blog post](https://carto.com/blog/agentic-gis-bringing-ai-driven-spatial-analysis-to-everyone)!

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-cd4e59c1cff03c337eb1147bb11fab37907a3c5f%2Faiagent_location.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Turn your AI Agents into geospatial experts with CARTO MCP Server

October 8th, 2025

<mark style="color:green;">**New**</mark> *Workflows*

CARTO now supports the **Model Context Protocol (MCP)**, a standard that enables AI Agents to interact with external tools and data sources. With the new **CARTO MCP Server**, organizations can now expose their own geospatial [Workflows as MCP Tools](https://docs.carto.com/carto-user-manual/workflows/workflows-as-mcp-tools) that any MCP-compliant agent can use.

This release allows GIS teams to design custom workflows in CARTO—defining inputs, outputs, and logic specific to their spatial problems—and make them available to AI Agents through the MCP Server. Each tool includes detailed metadata following the MCP specification, ensuring interoperability across agentic AI environments.

By combining Workflows and the MCP Server, organizations can empower AI Agents to perform advanced spatial analysis, automate geospatial decision-making, and connect AI-driven applications to their cloud data infrastructure.

{% embed url="<https://vimeo.com/1125236398?autoplay=1>" %}

## Territory Balancing and Location Allocation components in Workflows

September 30th, 2025

<mark style="color:green;">**New**</mark> *Workflows*

CARTO's new [Territory Planning Extension Package](https://docs.carto.com/carto-user-manual/workflows/components/territory-planning) for Workflows has been built to power location allocation and territory balancing directly within CARTO and your data warehouse, this extension helps analysts and planners create fair, efficient, and data-driven territory strategies.

* [Territory Balancing](https://docs.carto.com/carto-user-manual/workflows/components/territory-planning#territory-balancing) – Divide an area into continuous, optimized territories that are balanced according to a chosen metric (e.g. consumer demand or other business KPIs), while keeping each territory internally cohesive. Learn more about this new capability following this [tutorial](https://academy.carto.com/creating-workflows/step-by-step-tutorials/optimizing-workload-distribution-through-territory-balancing).
* [Location Allocation](https://docs.carto.com/carto-user-manual/workflows/components/territory-planning#location-allocation) – Find the optimal locations to open facilities (stores, warehouses, service hubs) and efficiently assign demand points (retail stores, populated regions) to them, minimizing costs or maximizing coverage. Take a look at this [tutorial](https://academy.carto.com/creating-workflows/step-by-step-tutorials/transforming-telco-network-management-decisions-with-location-allocation) to learn more!.

This extension package is currently available for Google BigQuery and Snowflake.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-e05d33dc695d692916cb079eb13f92a3c804e4f2%2F68dd3d5a742c9cdcc8bd04cc_aa1ced39.png?alt=media" alt=""><figcaption></figcaption></figure>

## Improved flow for deleting connections

August 28th, 2025

<mark style="color:orange;">**Improvement**</mark> *Workspace*

We've added a new option for users deleting connections so that all maps, workflows, tokens, etc. using the connection are updated to use another connection. Previously, users had to either update each asset individually or delete the connection along with all assets using it.

This new option vastly facilitates migrating from one connection to another, which is a common case when upgrading authentication types (changing from username/password to key pair or OAuth, for example).

Alternatively, users can still choose to delete the connection along with all assets that use it. For more information, see our article on [deleting connections](https://docs.carto.com/carto-user-manual/connections/deleting-a-connection).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-45dc1bae277d1f0908c8fa7820327fba22726896%2FScreenshot%202025-09-11%20at%2012.45.03.png?alt=media" alt=""><figcaption></figcaption></figure>

## Improvements to importing geospatial data into cloud data warehouses

August 28th, 2025

<mark style="color:orange;">**Improvement**</mark> *Workspace*

Recent updates have enhanced the experience of importing geospatial data into cloud data warehouses, with improvements in performance, scalability, and raster support.

Import operations now run faster thanks to a new, optimized process. The maximum supported file size has also been raised from **1GB to 5GB**, addressing a very frequent need when working with large geospatial datasets.

Raster-processing capabilities have been extended in **BigQuery and Snowflake**, supporting the import of non-COG GeoTIFF rasters into warehouse tables following the [Raquet specification](https://github.com/CartoDB/raquet?utm_source=chatgpt.com). This removes the strict preparation steps previously required for Cloud Optimized GeoTIFFs, making the process considerably simpler. Combined with the higher size limit, these updates provide a more efficient way for customers to bring raster data into their cloud environment.

{% embed url="<https://vimeo.com/1114283760?autoplay=1&share=copy>" %}

## **Drag and drop reordering of properties in Table and Interactions**

August 27th, 2025

<mark style="color:orange;">**Improvement**</mark> *Builder*

We've introduced the ability to reorder the properties shown in the Table widget and Tooltip via simple drag and drop functionality.

Until now, users could configure which properties to show, but changing the order they are presented often meant clearing the setup and starting over again. With this enhancement, it’s easier than ever to customize how data is displayed, improving readability and enabling tailored views for different audiences.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-a27a1d985066b306440fe2ed4f6ac024fc3f1345%2Fgif_drag_drop.gif?alt=media" alt=""><figcaption></figcaption></figure>

## **Control Components in Workflows: Conditional Split & Success/Error Split**

August 12th, 2025

<mark style="color:green;">**New**</mark> *Workflows*

We’ve added two new [control components](https://docs.carto.com/carto-user-manual/workflows/components#control) to CARTO Workflows that make it easier to control how your workflows execute and respond to different scenarios.

* [**Conditional Split**](https://docs.carto.com/carto-user-manual/workflows/components/control#conditional-split) – Direct your workflow into **If** and **Else** branches based on a condition you define. Build the condition with a simple UI (column + aggregation + operator + value) or use a custom SQL expression for more complex logic.\
  Some usage examples:
  * “If the **count of underserved households** in a service area is greater than 500, trigger a fiber expansion workflow; otherwise plan for wireless coverage.”
  * “If the **average property value** in a high-risk flood zone is above $1M, apply the high-risk pricing model; otherwise, use the standard pricing model.”
* [**Success/Error Split**](https://docs.carto.com/carto-user-manual/workflows/components/control#success-error-split) – Branch execution depending on whether the previous step ran successfully or failed.\
  Some usage examples:
  * “If network quality metrics fail to load, send an alert; otherwise continue with churn prediction.”
  * “If address geocoding fails, switch to a backup geocoder; otherwise proceed with claims analysis.”

These components let you build workflows that adapt to your data, add robust error-handling, and reduce the need for manual monitoring — helping teams act faster on reliable insights.

{% embed url="<https://vimeo.com/1109408145?autoplay=1&share=copy>" %}

## **Separation of working locations for improved data governance**

August 5th, 2025

<mark style="color:orange;">**Improvement**</mark> *Workspace*

We have introduced a clearer separation of datasets/schemas that CARTO creates and manages in connected data warehouses. This change improves data governance and prevents persistent objects from being stored alongside temporary workflow tables.

**New locations per connection:**

* **CARTO temp location** – stores only temporary tables created during workflow execution.
* **CARTO Workspace location** – stores persistent objects related to workflows, such as API stored procedures and imported files.
* **CARTO Extensions location** – stores Extension Package resources, including shared stored procedures and metadata. Only for BigQuery and Snowflake.

**Additional notes:**

* For connections shared requiring Viewer Credentials, `carto_temp_<user>` and `carto_workspace_<user>` are created per user.
* The Extensions location is always shared across all users in a connection, ensuring consistent access to installed packages.
* Default names can be overridden in the connection’s advanced options.
* Locations are automatically created as needed (`CREATE IF NOT EXISTS`).

This update applies to all supported warehouses. Find specific documentation on the *Advanced settings* section for each warehouse in the [Connections](https://docs.carto.com/carto-user-manual/connections) section of the documentation.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-c3eee370be70bff8959fec0365c52b1aa450a80e%2FScreenshot%202025-08-13%20at%2012.29.59.png?alt=media" alt=""><figcaption></figcaption></figure>

## Support for adding sources without associated layer in Builder

July 29th, 2025

<mark style="color:green;">**New**</mark> *Builder*

Editor users can now add data sources to a Builder map **without displaying associated layers**. These sources can be used to power widgets, SQL parameters, and even be used by AI Agents to generate insights.

This is especially useful when a dataset is needed for interactivity or calculations, but not for visualization. It helps keep your maps cleaner, more focused, and easier to maintain.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-15654767df4835c10ef5fc901b90765a87a73462%2FSources%20without%20layers.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Organization Governance Settings for Admins

July 17th, 2025

<mark style="color:green;">**New**</mark> *Workspace*

Admins can now set up custom governance policies through the new **Governance** section in Settings. These controls give you the tools to manage data access, sharing, and feature usage across your organization with precision.

Control who can create new Data Warehouse connections with granular settings for providers and authentication methods. Manage connection sharing, disable the CARTO Data Warehouse, and fine-tune Builder features like Download PDF report, export viewport data, and more!

To see all the new settings, check our section on [Organization Governance](https://docs.carto.com/carto-user-manual/settings/organization-governance).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-cb8dee038f25f722ea637fb9d625e5c10022777a%2FScreenshot%202025-07-17%20at%2016.58.33.png?alt=media" alt=""><figcaption></figcaption></figure>

## Support for Widgets linked to Raster sources in Builder

July 15th, 2025

<mark style="color:orange;">**Improvement**</mark> *Builder*

You can now use Widgets with raster sources in Builder — just like you already can with vector sources. This improvement allows for richer exploration and analysis of raster sources stored in your data warehouse directly from the map.

Use the Formula Widget to calculate metrics like tree coverage in your current view. Leverage Category and Pie Widgets to list distinct values in your raster layer, or use the Histogram Widget to explore data distributions such as precipitation.

These widgets can also be used for filtering, letting you interactively refine what’s shown on the map and extract insights more effectively.

[Learn more in our documentation](https://docs.carto.com/carto-user-manual/maps/widgets).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-6a968bc9b521010d5e424636365d17aa02cfcc17%2Fwidgetsupportforrastersources.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Audit all queries with the CARTO SQL audit trails

July 8th, 2025

<mark style="color:green;">**New**</mark> *Workspace*

When a map or workflow is opened, CARTO launches a set of SQL queries to your data warehouse to visualize your data and run your analysis. And from now on, each of those SQL queries will contain a **rich audit trail** in the form of SQL comments at the beginning or the end of the query.

This audit information allows data warehouse administrators to monitor CARTO and answer questions such as: *How many queries did CARTO run in a period of time? Which workflows or maps have processed more data? What are some common performance or cost patterns?*

To start using this information in your audits, check our [Auditing SQL queries documentation](https://docs.carto.com/carto-user-manual/connections/auditing-sql-queries-from-carto).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-8dee28579192fc2fd1adcce235cfd53b7101efb6%2FsqlAuditTrailsCarto.png?alt=media" alt=""><figcaption></figcaption></figure>

## Collaborative edition in Workflows

June 30th, 2025

<mark style="color:orange;">**Improvement**</mark> *Workflows*

Workflows now supports [**collaborative editing**](https://docs.carto.com/carto-user-manual/workflows/sharing-workflows#editor-collaboration) for teams. Editors can share workflows with their entire organization, SSO groups, or specific users to enable collaborative development.

This feature eliminates the need to duplicate workflows for minor changes, ensuring teams work from a single, consistent source of truth. Asynchronous editing with a request/approval model reduces conflicts while supporting smooth, coordinated teamwork.

Editor collaboration makes it easier for organizations to use Workflows at scale and promotes more frequent, effective use across teams.

{% embed url="<https://vimeo.com/1097574791?autoplay=1&share=copy>" %}

## Cross-filtering multiple data sources from map widgets

June 25th, 2025

<mark style="color:green;">**New**</mark> *Builder*

You can now use a **single widget to filter multiple sources** in your Builder map as long as they share the same field.

Previously, widgets could only filter a single source. Now, widgets like Category or Time Series will update multiple sources and their related elements (like other widgets or layers) when the filtering property matches.

This is especially useful when working with complementary datasets. For example, filtering both sales and demographic data by region to uncover richer insights.

Learn more in our [Widget Behavior](https://docs.carto.com/carto-user-manual/maps/widgets#widget-behavior) section of the documentation.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-22ae821bbc9029273e56fe98e7e739a6d0be1da7%2Fcross-filtering.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Custom aggregation support on Category, Pie and Time Series Widget

June 19th, 2025

<mark style="color:orange;">**Improvement**</mark> *Builder, CARTO for Developers*

You can now define **custom aggregation** operations directly in [**Category**](https://docs.carto.com/carto-user-manual/maps/widgets/category-widget), [**Pie**](https://docs.carto.com/carto-user-manual/maps/widgets/pie-widget), and [**Time Series**](https://docs.carto.com/carto-user-manual/maps/widgets/time-series-widget) widgets, previously only available in Formula widgets.

This enhancement enables more advanced use cases by allowing tailored **SQL expressions** within the widget configuration, giving users greater control over how insights are calculated and displayed.

Custom aggregations are supported in both **CARTO Builder** and the **CARTO Developer framework** for programmatically creating widgets.\
\
Learn more in the [Widget*s*](https://docs.carto.com/carto-user-manual/maps/widgets) section of Builder or the CARTO for Developers [technical reference](https://docs.carto.com/carto-for-developers/reference/carto-widgets-reference).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-7b2bcf760cfa8e87a0038bd2477527a0d3d69118%2Fimage%20(737).png?alt=media" alt=""><figcaption></figcaption></figure>

## Integrate CARTO Builder maps at scale in your custom applications using fetchMap

May 30th, 2025

<mark style="color:orange;">**Improvement**</mark> *CARTO for Developers*

Developers have now access to an extended set of tools to bring maps from CARTO Builder into their applications, **allowing collaboration with non-developer users** who can be in charge of the cartography, or simply, accelerating the styling process of layers. Key points are:

* Non-developers can prototype and build [maps in Builder](https://docs.carto.com/carto-user-manual/maps) as usual.
* Developers use `fetchMap` to retrieve maps from CARTO into their code.
* The map properties can then be integrated and customized, to perfectly blend in your application. This includes **layers, legend,** and **interactions** (tooltips, popups, hover...).
* Works with private and public maps.

Learn more about the improvements to fetchMap in our [technical reference](https://docs.carto.com/carto-for-developers/reference/fetchmap), or check [how we built our example](https://docs.carto.com/carto-for-developers/examples#fetchmap).

{% embed url="<https://vimeo.com/1088837980?share=copy>" %}

## Support for sharing maps with Guest viewers

May 29th, 2025

<mark style="color:green;">**New**</mark> Accounts

We've introduced a new user role, [**Guest viewer**](https://docs.carto.com/carto-user-manual/settings/users-and-groups/managing-user-roles#guest-viewers), designed for organizations that want to share maps with external partners, clients or collaborators.

Users with this new role can only see the maps that have been explicitly shared with them, which improves collaboration with external users as it removes the need to make sensitive maps public. As these are authenticated users, Editors can grant or revoke Guest viewer access to any map at any point, while Admins can view a complete audit trail of their activity.

For more information, head to our section on [Guest viewers](https://docs.carto.com/carto-user-manual/settings/users-and-groups/managing-user-roles#guest-viewers).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-4a185b83d80b4baebe9b4d18749725f70d8949ef%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

## **Routing Matrix support in the Analytics Toolbox, Workflows, and LDS API**

May 26th, 2025

<mark style="color:green;">**New**</mark> Workflows and Analytics Toolbox

CARTO now supports computing **travel time and distance origin–destination matrices** using third-party APIs from TravelTime and TomTom. New functions in the Analytics Toolbox allow users to build routing matrices with full control over input parameters, enabling accurate and optimized travel time analysis.

This capability is also available through a new component in Workflows, providing a low-code way to integrate travel time data into broader spatial processes. A new endpoint in the **Location Data Services (LDS) API** has been introduced to support this functionality across the Analytics Toolbox and Workflows, ensuring robust and scalable access to routing services.

The new functions and components are available in [Workflows](https://docs.carto.com/carto-user-manual/workflows/components/spatial-constructors#create-routing-matrix) and the Analytics Toolbox for [BigQuery](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-bigquery/sql-reference/lds#create_routing_matrix), [Snowflake](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-snowflake/sql-reference/lds#create_routing_matrix) and [Redshift](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-redshift/sql-reference/lds#create_routing_matrix).

{% embed url="<https://player.vimeo.com/video/1087758614?autoplay=1>" %}

## Enhanced collaboration with User Comments now available in Builder

May 13th, 2025

<mark style="color:green;">**New**</mark> *Builder*

You can now collaborate directly in your Builder maps using **Comments**. Add notes tied to specific locations, start threaded discussions, and tag teammates to bring everyone into the conversation—right where decisions are made.

Built for collaboration, Comments help reduce back-and-forth, speed up decision-making, and turn your maps into **collaborative mapping experiences**.

Ready to start? Check our the [documentation](https://docs.carto.com/carto-user-manual/maps/sharing-and-collaboration/comments) to learn more.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-58c15e426af79d8339841d9520cd208494911001%2Fcomments.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Automate the creation of maps with the new Create Builder Map component in Workflows

May 12th, 2025

<mark style="color:green;">**New**</mark> *Workflows*

A new component is now available in CARTO Workflows to automate the creation and update of Builder maps. With support for three modes—**Create copy**, **Overwrite**, and **Update**—this component gives users full control over how maps are generated and maintained as part of a workflow.

This functionality allows users to integrate map generation into larger geospatial processes, ensuring that maps stay up to date with the latest analytical results. Whether you're building templated workflows, maintaining a dashboard, or running scheduled processes, this component helps reduce manual steps and ensures consistency across your visual outputs.

Check the [documentation](https://docs.carto.com/carto-user-manual/workflows/components/input-output#create-builder-map) to get started.

{% embed url="<https://vimeo.com/1083589811?autoplay=1&share=copy>" %}

## New developer framework-agnostic widgets for Tileset and Raster sources

April 3rd, 2025

<mark style="color:green;">**New**</mark> *CARTO for Developers*

Developers building custom, scalable geospatial apps with CARTO can now add custom charts and widgets on top of their **tileset** and **raster** sources, enriching their application with additional GPU-powered **filtering** capabilities. These widgets have the same features as all our developer widgets:

* **Fully-customizable:** using flexible data models and your own UI charting library.
* **Easily sync your widgets** with the deck.gl map, and seamlessly use widgets to **filter**.
* **Framework-agnostic, with minimal dependencies:** built with pure JS and Typescript, it integrates nicely in your own stack (Angular, React, Vue...).

Use cases include land use treemap charts, NDVI average scorecards, or frequency histograms over huge tilesets with millions of points, and everything in between... Get creative!

Ready to get started? Check the [technical reference](https://docs.carto.com/carto-for-developers/reference/carto-widgets-reference) or play with our [examples](https://docs.carto.com/carto-for-developers/examples)!

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-ec4bbef225ca27576519f68928aa439a7b66c2be%2FtilesetRasterWidgets.gif?alt=media" alt=""><figcaption></figcaption></figure>

## View all assets in your organization with the new Superadmin role

April 3rd, 2025

<mark style="color:orange;">**Improvement**</mark> *Accounts*

We have introduced a new user role –Superadmin– capable of viewing and managing all assets (Maps, Workflows and Connections) in the organization, regardless of who owns them or their visibility settings. This new role will help facilitate the administration and governance of large organizations with many users and many assets:

* Delete and transfer assets in bulk
* Filter assets by owner
* View detailed asset relationships, such as the Connection used by a Workflow.

For more information, see our section on the [Superadmin role](https://docs.carto.com/carto-user-manual/settings/users-and-groups/managing-user-roles#superadmin-role).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-b315eb4148e47ab51d0ccde47db8449de1b7b20d%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

## Control layer presence in Builder’s map layer list

March 19th, 2025

<mark style="color:orange;">**Improvement**</mark> *Builder*

Editor users can now manage the presence of a layer in the map layer list directly from the [Legend](https://docs.carto.com/carto-user-manual/maps/legend) tab in Builder. Previously, it was only possible to show or hide a layer’s legend. With this update, you now have full control over whether a layer itself should appear in the map layer list — what end-users see and interact with during map exploration.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-20d000cde1b71f62a301bf604fdd7207380a1839%2Fcontrol_layers.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Manage your maps, workflows, and connections at scale with our new Resources APIs

March 19th, 2025

<mark style="color:green;">**New**</mark> *CARTO for Developers*

As organizations expand their usage of CARTO and *break the GIS data silo* using cloud-native maps and workflows, it becomes important to have the right tools to manage all resources at scale. This is why, starting today, all users in CARTO have access to a **new set of API endpoints where they can programmatically list and delete their maps, workflows, and connections**.

Additionally, to empower *Superadmins* on their journey to enable CARTO for large organizations, we're exposing the following functionality via the new APIs:

* List all the maps, workflows, and connections in a CARTO organization
* Bulk delete of multiple assets with a single API request
* Transfer the ownership of an asset (map, workflow, or connection) to another user

Ready to scale up? Head over to our [API reference](https://api-docs.carto.com) to get started.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-4db3d346d15e1233a608718800d4ae8fd3a1c9e9%2FWorkspace%20APIs.jpg?alt=media" alt=""><figcaption></figcaption></figure>

## Connect to Databricks using OAuth authentication

March 13th, 2025

<mark style="color:green;">**New**</mark> *Workspace*

Users can now connect to their Databricks account using OAuth authentication, with both Machine-to-Machine (M2M) and User-to-Machine (U2M) authentication flows supported! This adds an extra layer of security for Databricks users since OAuth tokens are automatically refreshed by default and do not require the direct management of the access token. For these reasons, Databricks is strongly recommending its users to choose OAuth over Personal Access Tokens.

Want to learn more? head over to our [section on Databricks connections](https://docs.carto.com/carto-user-manual/connections/databricks).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-aba3ddbdc06a3527ce349283f686e18c764e6a77%2FScreenshot%202025-03-13%20at%2018.23.49.png?alt=media" alt=""><figcaption></figcaption></figure>

## Visualize rasters in Builder, directly from your data warehouse

February 27th, 2025

<mark style="color:green;">**New**</mark> *Builder*

Raster visualization is now available in Builder, marking a major milestone in CARTO’s end-to-end support for raster data. With this release, you can seamlessly import, analyze, and visualize raster datasets stored in Google BigQuery, Snowflake and Databricks—all within CARTO.

This new capability unlocks powerful use cases, allowing you to explore and analyze data at scale, seamlessly within your cloud environment, without additional data movement. Interesting in learning more? [Check our documentation](https://docs.carto.com/carto-user-manual/maps/layers/raster).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-8c3e1f0728723260af793b8805dbf7e664f9775c%2Fraster_builder.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Introducing AI Agents for maps - now available in Public Preview

February 20th, 2025

<mark style="color:green;">**New**</mark> *Builder*

We’re excited to announce the Public Preview of CARTO [AI Agents](https://docs.carto.com/carto-user-manual/ai-agents), designed to make interacting with your maps in Builder more intuitive and dynamic. With AI Agents, users can seamlessly zoom to specific regions based on conversational input, explore map details, and apply filters using widgets—all through a natural language interface.

✨ Stay tuned—this is just the beginning. We’re already working on making AI Agents faster, smarter, and more powerful to elevate your mapping experience even further.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-4341b9006c1992631a22639d2e511b74829f6014%2Fgif5.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Expanding CARTO for Databricks: Location Data Services & Data Enrichment

February 18th, 2025

<mark style="color:green;">**New**</mark> *Workflows*

We’re introducing **Location Data Services (LDS) support** and **new data enrichment components** in **CARTO for Databricks**, enabling more seamless geospatial analysis across different user roles and workflows.

* **Location Data Services (LDS) Support**: Now available in both the [**Analytics Toolbox for Databricks**](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-databricks) and as **Workflows components**.\
  Users can perform [**geocoding**](https://docs.carto.com/carto-user-manual/workflows/components/spatial-constructors#st-geocode)**,** [**routing**](https://docs.carto.com/carto-user-manual/workflows/components/spatial-constructors#create-routes)**, and** [**isoline**](https://docs.carto.com/carto-user-manual/workflows/components/spatial-constructors#create-isolines) calculations via CARTO’s standard providers. The Analytics Toolbox enables direct use within **Databricks notebooks and SQL workflows**, while CARTO Workflows provides a **low-code interface**, integrating LDS into broader spatial analysis pipelines. LDS usage is subject to **CARTO licensing and quotas**, but users can also bring their own provider credentials, just as with other data warehouses.
* **Data Enrichment Components**: These new Workflows components simplify use cases like demographic enrichment, POI data integration, and trade area analysis. Users can enhance datasets with information from **CARTO’s Data Observatory** or their **own geospatial sources**, whether structured as **spatial indexes, points, or polygons**. By embedding enrichment within **CARTO Workflows**, users can more easily integrate this step into their existing analysis.

These updates further **reduce complexity** for Databricks users working with spatial data. Data scientists can leverage LDS functions directly within their Databricks environment, while Workflows opens up more advanced spatial analysis to less technical users. By bringing LDS and enrichment into CARTO Workflows, we make it easier to build complete geospatial pipelines without writing custom code.

{% embed url="<https://vimeo.com/1057936039>" %}

## Bringing cloud-native spatial analytics to your desktop GIS with the new CARTO QGIS Plugin

February 6th, 2025

<mark style="color:green;">**New**</mark> *Integrations*

The new [**CARTO QGIS Plugin**](https://docs.carto.com/data-and-analysis/carto-qgis-plugin) allows you to access, visualize, and edit spatial data from leading cloud data warehouses directly within QGIS. With this plugin, you can seamlessly check out data from Google BigQuery, Snowflake, Databricks, AWS Redshift, and PostgreSQL, edit it within QGIS, and commit changes back to your data warehouse—all powered by the CARTO platform.

Simply connect your cloud data warehouse to CARTO, install the QGIS plugin, and gain full control over your geospatial data in a familiar GIS environment. This enables smooth workflows for spatial data management, enrichment, and analysis while ensuring your data remains centralized and up to date in your cloud ecosystem.\\

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-89200952b1b87f52b40535ce6d54a347d4ff1d7c%2Fcrop_gif.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Connect to Snowflake using Key-pair authentication

February 3rd, 2025

<mark style="color:green;">**New**</mark> *Workspace*

Snowflake users can now connect to their Data Warehouse using **Key-pair authentication**! This is a much more secure alternative to basic username/password authentication as it is highly resistant to brute-force attacks, eliminates password management complexities, and can be easily used as the authentication mechanism for scripts and applications.

We've also added support for Key-pair rotation, enabling users to update the private key of Key-pair connections they own. For more information, see our section on [Key-pair authentication for Snowflake connections](https://docs.carto.com/carto-user-manual/connections/snowflake#connecting-to-snowflake-using-key-pair-authentication).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-b74e475d75f7a91a63c29e777f7d31186c961d18%2FScreenshot%202025-02-03%20at%2019.16.43.png?alt=media" alt=""><figcaption></figcaption></figure>

## Support for aggregating data sources by identical geometries in Builder

*January 30th, 2025*

<mark style="color:green;">**New**</mark> *Builder*

Are you working with datasets where multiple rows share the same geometry but have varying attributes, such as administrative boundaries, roads, or infrastructure locations?

The new [aggregate by geometry](https://docs.carto.com/carto-user-manual/maps/layers#aggregate-by-geometry) functionality allows you to aggregate those features in your layer visualization and interactions, improving performance while keeping access to detailed insights.

With this update, you can:

* Aggregate geometries in your layer to ensure optimal performance.
* Aggregate styling and interaction attributes to retrieve relevant information linked to your aggregated feature.
* Maintain widget functionality over the original source, enabling drill-down operations for deeper analysis.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-18b734ea49e888a0fa9d31a8e0dc360016f98d47%2FAggregate%20by%20geometry.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Expand and tailor Workflows functionality with Extension Packages

*January 30th, 2025*

<mark style="color:green;">**New**</mark> *Workflows*

With this new release, users and partners can now extend the capabilities of our low-code analytics tool CARTO Workflows by creating, integrating and distributing custom components tailored to their specific spatial analytics needs.

To start creating your own Workflows Extension Packages we have published [this public GitHub template](https://github.com/CartoDB/workflows-extension-template). Kick off your own repository out the template and start developing extensions for BigQuery and Snowflake connections.

Additionally, we have published a set of extensions readily available to be installed from the Workflows UI. The initial release boasts a curated collection of extensions, including:

* [**BigQuery ML**](https://docs.carto.com/carto-user-manual/workflows/components/bigquery-ml)**:** Integrate machine learning workflows with your geospatial data using BigQuery ML directly within Workflows.
* [**Google Earth Engine**](https://docs.carto.com/carto-user-manual/workflows/components/google-earth-engine)**:** Unleash the power of Google Earth Engine for advanced spatial analysis tasks.
* [**Google Environment APIs**](https://docs.carto.com/carto-user-manual/workflows/components/google-environment-apis)**:** Bring the power of Google Environment APIs (Solar, Air Quality, Pollen) into your geospatial analytics workflows.
* [**Telco Signal Propagation Models**](https://docs.carto.com/carto-user-manual/workflows/components/telco-signal-propagation-models)**:** Analyze telecommunication signals with path profiles, propagation modeling, and obstacle identification.

Head over to the CARTO Workflows documentation to learn more about [Extension Packages](https://docs.carto.com/carto-user-manual/workflows/extension-packages) and explore the initial release offerings.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-62f8c4517a4627817a357d714bbd417a0bd59c4f%2F20250103-workflows_extension_packages.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Support for sharing maps with specific users

January 17th, 2025

<mark style="color:green;">**New**</mark> *Workspace*

We've introduced the ability to share maps with individual users! Previously, maps could only be shared with your entire organization, specific user groups, or made publicly accessible via a link.

With this new feature, Editors now have more granular control over map access permissions. Users can select exactly which individuals should have access to a map (and they can revoke it at any time), making it easier to collaborate on specific projects while maintaining security. For more information, visit our section on [publishing and sharing maps](https://docs.carto.com/carto-user-manual/maps/sharing-and-collaboration).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-415a54bdd48801661744e2e745ba4cccc845c186%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

## Connect CARTO and Google BigQuery using Workload Identity Federation

January 10th, 2025

<mark style="color:green;">**New**</mark> *Workspace*

We’re excited to announce that CARTO now supports connecting to Google BigQuery via **Workload Identity Federation**! This new capability enables secure, seamless authentication without requiring service account keys, making it easier to manage access and improving security for your cloud-native maps, workflows and applications.

With Workload Identity Federation, you can set up a trust relationship between CARTO and your Google Cloud projects for a smooth integration — In other words, you will be managing permissions to each of your CARTO users directly in Google Cloud, using IAM rules.

Another benefit of this method is that it provides a framework to effortlessly scale and distribute granular permissions across large-scale teams using CARTO and BigQuery. To get started:

* Administrators will need to set up an [integration to configure Workload Identity Federation in CARTO](https://docs.carto.com/carto-user-manual/settings/advanced-settings/workload-identity-federation).
* Once the integration is set up, all users will be able to [use Workload Identity Federation when connecting CARTO and BigQuery](https://docs.carto.com/carto-user-manual/connections/bigquery#using-workload-identity-federation).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-aa0288cafe426905cec1cfdf9df9a91e75459f2e%2FWIFCARTO.png?alt=media" alt=""><figcaption></figcaption></figure>

## Develop completely custom widgets powered by H3 and Quadbin spatial index-based sources

January 7th, 2025

<mark style="color:orange;">**Improvement**</mark> *CARTO for Developers*

A few months ago we introduced our [framework-agnostic widgets](https://docs.carto.com/q4-2024#new-framework-agnostic-widgets-in-carto-for-developers), a new system for developers to add scalable and highly-performant charts and other data components to their CARTO + deck.gl application, with support for vector-based data sources: *points*, *lines* and *polygons*.

Today, we're extremely happy to announce that developers can now build completely custom widgets using **spatial index sources** as well. These sources aggregate the data in a spatial index system, such as **H3** or **Quadbin,** for increased performance and scalability. The main benefits of the new framework-agnostic widgets apply to spatial index-based widgets as well:

* Build anything using H3 and Quadbin sources: from scorecards to bar charts, tables, time series, and everything in between.
* Bring your own UI: Use your favorite charting library or custom HTML components.
* Easily sync your widgets with the deck.gl map.
* Seamlessly use widgets to filter the map and other widgets, fully leveraging your cloud data warehouse computing power.
* Built using JS and Typescript only, they are fully compatible with the framework of your choice (Angular, React, Vue...), adding minimal dependencies.

Ready to learn more? Get started by reading the [technical reference](https://docs.carto.com/carto-for-developers/reference/carto-widgets-reference) or by exploring the [examples](https://docs.carto.com/carto-for-developers/examples).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-0b4a852d9535b8b7afa2f83071b84245d83e83b7%2FspatialIndexWidgets.png?alt=media" alt=""><figcaption></figcaption></figure>

## Improved SSO group management

*December 13th, 2024*

<mark style="color:orange;">**Improvement**</mark> *Workspace*

We've introduced several improvements to help Admins of organizations using SSO groups manage them more effectively. Admins can now view the composition of groups, search for specific users within them, and delete unused groups. Additionally, we've implemented a new method to synchronize only a subset of groups into CARTO. For more details, visit our article on [SSO Groups](https://docs.carto.com/carto-user-manual/settings/users-and-groups/managing-user-groups).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-f21104e0129547e77cc4abab8a5a4e4990a8905b%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

## Discover spatial data like never before: Meet the new Data Observatory Catalog!

*December 4th, 2024*

<mark style="color:orange;">**Improvement**</mark> *Data Observatory*

We’re thrilled to announce a major update to the CARTO Data Observatory catalog! The new version introduces a completely redesigned interface, making it easier than ever to browse and discover spatial datasets. Whether you're searching for demographic insights, mobility or environmental data, the improved catalog helps you navigate a vast array of options with greater clarity and efficiency.

In addition to the new design, the updated catalog now includes richer metadata for each dataset. You can access detailed descriptions, links to product documentation, Frequently Asked Questions, and relevant use-cases for each product, enabling more informed decision-making when assessing external datasets to enrich your geospatial analysis.

[Log in](https://app.carto.com/) today to explore the new Data Observatory catalog and unlock the full potential of your projects! Access more information about the Data Observatory in our [product documentation](https://docs.carto.com/carto-user-manual/data-observatory).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-7c5f205b8adf892f2fc2ca439f9008ff5bf8674d%2Fdo_catalog_whatsnew2.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Avoid exposing SQL in your CARTO applications with Named Sources

*November 24th, 2024*

<mark style="color:green;">**New**</mark> *CARTO for Developers*

There are no trade-offs between simplicity, flexibility and security: developers using CARTO can now use Named Sources to avoid exposing the SQL queries used under the hood in their applications, and without necessarily having to add additional backend or proxy services.

Developers can manage their Named Sources manually via UI or programmatically via API. To get started with Named Sources, check the [documentation](https://docs.carto.com/carto-user-manual/developers/named-sources) and the [developer guides](https://docs.carto.com/carto-for-developers/guides/avoid-exposing-sql-queries-with-named-sources).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-d26cd0e8d4992b4633428652cc837facb88b1904%2FNamed%20Sources%20(2).png?alt=media" alt=""><figcaption></figcaption></figure>

## Fully deploy CARTO within Snowflake using Container Services

*November 21st, 2024*

<mark style="color:green;">**New**</mark> *Deployment Methods*

You can now deploy your own instance of CARTO fully inside of Snowflake, as a Native App using Snowflake-managed Container Services.

From additional security benefits (from a closed environment within Snowflake) to streamlined installation, there are multiple reasons to be excited about this new deployment method, currently in BETA for specific customers.

Learn more about [deploying CARTO within Snowflake using Container Services](https://docs.carto.com/carto-mcp-server/carto-mcp-server) in our documentation or read about it in our [blog post](https://carto.com/blog/product-announcement-deploy-the-carto-platform-inside-snowflake).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-8a5fe0da0737be21814dd2607cd514a32868788b%2F673f45bd4881957128334f6d_Blogpost_Asset1_LinkedIn_1200x628%20(1).png?alt=media" alt=""><figcaption></figcaption></figure>

## Seamless data source switching in Builder maps

November 21st, 2024

<mark style="color:green;">**New**</mark> *Builder*

Builder users can now modify the location or connection of data sources directly in Builder without breaking the map configuration. This ensures that maps retain their overall configuration, as long as the fields in the updated data source have the same name and type.

For map components such as style properties, widgets, or interactions that rely on properties not found in the updated data source, the configuration will gracefully fall back to its default settings, ensuring the map remains functional.

This functionality allows users to repurpose their maps effortlessly, even when the data source location in their data warehouse changes—eliminating the need to recreate maps from scratch.\
\
[Learn more in our documentation.](https://docs.carto.com/carto-user-manual/maps/data-sources/changing-data-source-location)

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-b0e9bfb6bb943419919ea9ec998567e81572e4b1%2Fchanging_data_source.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Reusable custom color palettes in Builder

November 11th, 2024

<mark style="color:green;">**New**</mark> *Builder*

Admin users can now define custom color palettes for their CARTO organization, removing the need to manually add custom color styling in each new Builder map individually. This is a quick and easy way to apply styles consistently across various maps, available to all Editors within an organization.

Custom color palettes can be created from the Settings and are applied directly in CARTO Builder. For more information, see our article on [**creating and applying custom color palettes**](https://docs.carto.com/carto-user-manual/settings/customizations/configuring-custom-color-palettes).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-9afc88d9ba59788e645a5a56afbd6d14c458bf4a%2FcolorPalettes.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Databricks support for CARTO Workflows

October 31st, 2024

<mark style="color:green;">**New**</mark> *Workflows*

We are thrilled to announce that CARTO Workflows now supports direct connections to Databricks, significantly enhancing our integration capabilities for the Databricks platform. This new feature empowers Databricks' vast community of data engineers, data scientists, and analysts to seamlessly perform geospatial analysis within CARTO Workflows.

This release caps off a series of Databricks-focused updates rolled out over recent months:

* We have introduced support for SQL Warehouses and Unity Catalog in [CARTO connections](https://docs.carto.com/carto-user-manual/connections/databricks).
* Made Databricks connections available in [Builder and other maps](https://docs.carto.com/carto-user-manual/maps/data-sources/simple-features) across the platform, as well as geospatial applications developed with CARTO.
* Enabled [table preparation](https://docs.carto.com/carto-user-manual/maps/performance-considerations#tiles-postgresql) and [tileset creation](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-databricks/reference/legacy/tiler) for high-performance visualizations.

Workflows for Databricks leverages [Databricks Spatial SQL](https://carto.com/blog/enhancing-geospatial-analytics-with-carto-databricks), [Apache Sedona](https://sedona.apache.org/latest/) and the[ CARTO Analytics Toolbox](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-databricks) to make geospatial analysis easier and more performant than ever for data scientists, engineers and analysts on Databricks. Being a cloud-native integration, CARTO pushes down all processing to Databricks, profiting from the massive computation capabilities.

By embedding these tools directly in Databricks, we are breaking down the geospatial data silo, making geospatial insights more accessible and actionable for enterprise teams.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-fdc8c98b291f04eb8dae31f2f42e78e35201751d%2F20241031-databricks_create_workflow.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Search, highlight and zoom with Builder's Table widget

October 17th, 2024

<mark style="color:orange;">**Improvement**</mark> *Builder*

Navigating large geospatial datasets is now faster with our upgraded [Table Widget](https://docs.carto.com/carto-user-manual/maps/widgets/table-widget), featuring **search**, **highlight**, and **zoom** capabilities.

You can now easily **search** for specific features within the Table Widget, making them quick to locate. **Hover** over a table row to instantly **highlight** the corresponding feature on the map, and with a click, the map will automatically **zoom** to and center on that feature.

We’ve also improved the widget’s configuration, allowing you to label, format, and reorder columns without altering your data source.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-78f143cea4ffaa00f0d85aeb9cb2d5090e7e5ac4%2Fsearch_zoom.gif?alt=media" alt=""><figcaption></figcaption></figure>

## New basemap selector in Builder

October 15th, 2024

<mark style="color:green;">**New**</mark> *Builder*

Many times, a single basemap doesn't fully meet all of your mapping needs. Now, with the new [basemap selector](https://docs.carto.com/carto-user-manual/maps/basemaps/basemap-selector) in Builder, users can easily switch between different basemaps available in your organization. This feature allows you to tailor the visual context of your maps to specific use cases, enhancing the overall data exploration experience.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-22df2b625afcc1ad027d7c0caa24087ec7b57ccd%2Fbasemap_selector.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Elevate your point visualizations with the new `_carto_point_density` property

October 14th, 2024

<mark style="color:green;">**New**</mark> *Builder,* *CARTO for Developers*

We’ve added a new styling property, `_carto_point_density`, for point dynamic tiling sources, perfect for visualizing point density. You can use this property in Builder or your custom apps to style your points by radius, fill, or stroke color, making your maps more insightful and visually appealing. Learn more about it in our [documentation](https://docs.carto.com/carto-user-manual/maps/layers/point#using-_carto_point_density-attribute).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-2381cfd2ed4b949ef2a3be476d9ef1fed3db303d%2Fpointdensity.gif?alt=media" alt=""><figcaption></figcaption></figure>

## New framework-agnostic widgets in CARTO for Developers

October 9th, 2024

<mark style="color:green;">**New**</mark> *CARTO for Developers*

Developers using CARTO + deck.gl are scaling and accelerating their geospatial apps with powerful layers, using live data from their cloud data warehouse. **Now, they can also add scalable, interactive charts and widgets to their geospatial applications.**

This is what we love about the new [CARTO Widgets](https://docs.carto.com/carto-for-developers/key-concepts/charts-and-widgets):

* Use flexible and scalable data models to achieve exactly and quickly what you need: From scorecards to bar charts, tables, time series, and everything in between.
* Bring your own UI: Use your favorite charting library or custom HTML components.
* Easily sync your widgets with the deck.gl map.
* Seamlessly use widgets to filter the map and other widgets, fully leveraging your cloud data warehouse computing power.
* Built with JS and Typescript, they are fully compatible with the framework of your choice (Angular, React, Vue...), adding minimal dependencies.

**We're excited to see what you build!** — To get started, head over to the [technical documentation](https://docs.carto.com/carto-for-developers/key-concepts/charts-and-widgets) or check the [**new examples for CARTO Widgets**](https://docs.carto.com/carto-for-developers/examples).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-0d14ce64c90454decb859e5edd9c35cb4e378310%2Fwidgets.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Dynamic aggregation of point layer into clusters

October 7th, 2024

<mark style="color:green;">**New**</mark> *Builder*

We've introduced a new functionality in Builder to dynamically visualize your point data as **clusters**, helping you gain deeper insights and uncover trends more effectively. By aggregating point data into clustering, you can:

* **Reduce Visual Clutter**: Automatically group nearby points into clusters as you zoom out, helping you maintain clarity and readability, even with dense datasets.
* **Enhanced Performance**: Clustering improves performance by reducing the number of individual features rendered, making it easier to handle large datasets without compromising speed.
* **Meaningful Aggregation**: See patterns emerge as points are grouped into clusters, helping you identify hotspots, trends, and areas of interest quickly and effectively.
* **Interactive Exploration**: As you zoom in and out, clusters dynamically adjust, revealing individual points as you get closer, giving you seamless interaction with your data at different scales.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-0a81caf59fa165ac8d9e664af0d80fb673fb0cd0%2Fcluster.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Enforcing SSO for all users within an organization

October 4th, 2024

<mark style="color:green;">**New**</mark> *Accounts*

We've introduced a new toggle in the settings that allows Admins to enforce SSO within their organization. When enabled, every single user in that organization will have to authenticate using Single Sign-On, regaldless of their role. Users that try to authenticate with other mechanisms, such as *User/Password* and *Google Account* will not be allowed to log in.

For more details, check out our section on [SSO](https://docs.carto.com/carto-user-manual/settings/sso).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-6d77264588a64b3e0d568984398dbe369d3f6011%2FScreenshot%202024-08-22%20at%2018.22.56.png?alt=media" alt=""><figcaption></figcaption></figure>

## New Export Feature and Enhanced Security for Workflows

September 26th, 2024

<mark style="color:green;">**New**</mark> *Workflows*

We’re pleased to introduce several updates to **Workflows** designed to improve both functionality and security:

**Export Data from Any Node**

A new [**Export**](https://docs.carto.com/carto-user-manual/workflows/results-panel#data) button is now available on the Data tab for every executed node in your workflow canvas, allowing you to export data directly. This asynchronous export process can be tracked via the Activity Panel, similar to how [exports are managed in **Builder**](https://docs.carto.com/carto-user-manual/maps/exporting-data#exporting-data-as-an-editor).

**Enhanced Security for Enterprise-Ready Components**

In line with our ongoing platform-wide security initiative, we've implemented the following updates:

* [**Send by Email**](https://docs.carto.com/carto-user-manual/workflows/components/input-output#save-as-table) now works without requiring attached data, offering more flexibility in workflow automation.
* You can now specify a **custom bucket location** when using the **Send by Email** component, giving you control over where your data is sent.
* [**Export to Bucket**](https://docs.carto.com/carto-user-manual/workflows/components/input-output#export-to-bucket) no longer uses public buckets. Users are now required to specify their own **bucket locations**, ensuring more secure data management.

These updates make **Workflows** an even more powerful tool for enterprise users while maintaining a focus on security and ease of use.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-99807d38f2f0e074b412786a378b24224665dfc1%2Fexport_node.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Require Viewer Credentials for Snowflake OAuth connections

September 11th, 2024

<mark style="color:green;">**New**</mark> *Workspace*

Users can now require viewer credentials for their Snowflake OAuth connections. When this option is enabled, anyone accessing data through the connection — whether they're consuming maps, running workflows, or using the data explorer — will need to authenticate with their own credentials.

This ensures that security policies set in the database, such as Row-Level Security, are enforced. For more details, visit our section on [Sharing connections](https://docs.carto.com/carto-user-manual/connections/sharing-a-connection).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-10499312edbf91c81bf23d7d9589606bf743cdc2%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

## Monitor what's happening in your CARTO organization with the new Activity Data

August 30th, 2024

<mark style="color:green;">**New**</mark> *Workspace*

As organizations roll out CARTO to different teams and larger groups of users, it becomes increasingly important **for administrators to understand and monitor how their organization is using CARTO,** and this is now easy, powerful and flexible thanks to the **new** [**CARTO Activity Data**](https://docs.carto.com/carto-user-manual/settings/activity-data) **feature**

Administrator can now easily export (manually or programmatically via API) a comprehensive data collection of everything that happened within their CARTO organization.

The new Activity Data can be then analyzed to deeply understand things like:

* Basic engagement indicators: *weekly active users, workflows run per week*...
* Most used features: *most used workflow components...*
* Quota consumption: *who is consuming more quota and why*
* And many more insights about your CARTO organization

Want to get started? Head over to the [CARTO Activity Data](https://docs.carto.com/carto-user-manual/settings/activity-data) documentation. Make sure to also check the full [Activity Data Reference](https://docs.carto.com/carto-user-manual/settings/activity-data/activity-data-reference), as well as the [Examples](https://docs.carto.com/carto-user-manual/settings/activity-data/activity-data-examples) where we share practical guides and SQL queries on how to analyze this data.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-4eb67950c45b7acd3bb436e1e9929e5445e6d7ec%2FActivity_Data.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Improved asset ownership transfer

July 31st, 2024

<mark style="color:orange;">**Improvement**</mark> *Workspace*

We've introduced an improved flow for transferring user assets (maps, workflows, connections, etc) when deleting a user or when downgrading an Editor/Admin to Viewer. From now on, Admins will be able to select the specific user that will receive the assets.

For more information, check our documentation on [Deleting users](https://docs.carto.com/carto-user-manual/settings/users-and-groups/deleting-users) and [Managing user roles](https://docs.carto.com/carto-user-manual/settings/users-and-groups/managing-user-roles).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-09702ce1657261b7586fa789ade7892d87d85d3f%2Fimage.png?alt=media" alt=""><figcaption><p>Selecting the user that will inherit the assets of a deleted user</p></figcaption></figure>

## Dynamic aggregation of point layer into H3 cells

July 31st, 2024

<mark style="color:green;">**New**</mark> *Builder*

We've introduced a new functionality in Builder to dynamically visualize your point data as H3 aggregations, helping you gain deeper insights and uncover trends more effectively.

By aggregating point data, you can:

* **Simplify Complex Data**: Aggregate large volumes of point data into meaningful patterns and trends, making it easier to interpret and analyze.
* **Enhance Performance**: Improve rendering times and performance, especially with large datasets, by reducing the number of individual points displayed.
* **Identify Hotspots**: Quickly identify areas of high density or activity, helping you make data-driven decisions.
* **Visual Clarity**: Reduce visual clutter by grouping nearby points, providing a clearer and more informative map visualization.

Simply select this new visualization type and enjoy the benefits of aggregated data visualization, all with exceptional performance thanks to CARTO's native support for spatial indexes.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-59b062a0eb0a21b7b419d8417b960bed6d29e7cc%2Fh3%20point%20aggregation.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Enhanced layer panel and spatial source definition in Builder

July 29th, 2024

<mark style="color:orange;">**Improvement**</mark> *Builder*

We are excited to introduce an improved panel in Builder for configuring your layers. This update significantly enhances the UI and UX of this panel, making the experience of creating visualizations in Builder even more enjoyable and efficient.

The redesigned panel features a cleaner layout and includes a new 'Data' section at the top. In this new section, you can define the spatial definition of the data source linked to your layer. This is especially useful if your source contains multiple spatial columns or if Builder cannot recognize the spatial column by looking at our default conventions.

Learn more about the spatial definition of your sources [here](https://docs.carto.com/carto-user-manual/maps/data-sources/defining-source-spatial-data). Also, explore our [updated documentation section](https://docs.carto.com/carto-user-manual/maps/layers) for layers to get the most out of this update.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-d9a179eca388be2ea3a38bffd596d99c54c946c9%2FLayer%20Revamp.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Workflow Templates now available directly from your workspace

July 29th, 2024

<mark style="color:green;">**New**</mark> *Workflows*

We are pleased to announce the integration of our [collection of Workflow templates](https://academy.carto.com/creating-workflows/workflow-templates) directly within the CARTO Workspace. This feature aims to streamline your workflow creation process, making it faster and more efficient to [access and utilize pre-built templates](https://docs.carto.com/carto-user-manual/workflows#workflow-templates).

* **Integrated Collection**: Access a wide range of workflow templates hosted on the CARTO Academy website, now readily available in the CARTO Workspace.
* **Simplified Process**: Users no longer need to visit the Academy site to download and import templates. The new feature allows you to easily recreate templates by selecting ‘New Workflow > From template’ within the Workspace.
* **Enhanced Usability**: This integration ensures that all available templates can be accessed with just a few clicks, promoting best practices and facilitating quicker setup of workflows.

This feature is designed to ease the learning curve by providing immediate access to valuable workflow templates that illustrate both building blocks for common geospatial analytics and more complex use cases, like industry-specific analysis for Telco, Insurance, Retail and CPG, Out of Home advertising, etc

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-df2f7cce8ca3c842d292965292867244fd0d27b3%2Fwf_templates.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Zoom to layer extent in Builder maps

July 19th, 2024

<mark style="color:green;">**New**</mark> *Builder*

We are excited to introduce the zoom to layer functionality in Builder, which allows you to easily zoom to the layer extent, providing an immediate view of your dataset. When layers are filtered by widgets or parameters, the zoom focuses on the filtered data, ensuring you see exactly what's relevant.

Additionally, we have incorporated a "Show only this/Show all layers" feature, allowing you to quickly toggle all layers on and off with a single action, especially useful for maps including multiple layers.

Whether you're exploring vast datasets or gathering insights on geospatially distributed features, these new features will ensure a better exploration experience!\
\
Learn more about this feature in our [documentation](https://docs.carto.com/carto-user-manual/maps/layers/zoom-to-layer).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-e4e8509d6ae4a3391558da5d790d2bdffba420d0%2Fzoomnew.gif?alt=media" alt=""><figcaption></figcaption></figure>

## New Workflows Components for Creating Tilesets

July 15th, 2024

<mark style="color:green;">**New**</mark> *Workflows*

We are excited to introduce a powerful new set of components in Workflows that significantly enhance your geospatial data processing capabilities. These components are designed to facilitate the creation of various types of tilesets, allowing for efficient visualization and analysis of large spatial datasets. Here are the key features:

**Create Vector Tileset**

Generate vector tilesets from point, line, or polygon tables, enabling smooth and interactive map experiences.

**Create Point Aggregation Tileset**

Aggregate point data along with their properties into tilesets, ideal for visualizing dense point data on maps.

**Create Quadbin Aggregation Tileset**

Generate tilesets by aggregating quadbin indices, providing a fast and scalable way to manage spatial hierarchies and visualize large datasets.

**Create H3 Aggregation Tileset**

Utilize H3 hexagonal indexing to create aggregated tilesets, perfect for detailed spatial analysis and representation.

These new components enable you to transform your spatial data into highly efficient and scalable tilesets, which can be seamlessly integrated into your mapping applications. For more detailed information on how to use these components, visit [our documentation](https://docs.carto.com/carto-user-manual/workflows/components/tileset-creation).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-7db4acc41d77d3326bf47c79127ded0a2c105a16%2FScreenshot%202024-07-19%20at%2015.45.04.png?alt=media" alt=""><figcaption></figcaption></figure>

## Support for organizing and filtering maps and workflows with tags

June 28th, 2024

<mark style="color:green;">**New**</mark> *Workspace*

We are happy to announce a new system that allows users to classify and filter maps and workflows in the CARTO Workspace with tags. With this new feature, editor users will be able to create, apply and filter maps and workflows by tags, considerably improving the organization of assets within CARTO. With this new enhancement:

* You can create, apply and remove tags by editing the Map/Workflow properties from the Workspace;
* We have added a tag filter to the Workspace so you can filter by one or several tags;
* Once a tag filter is applied, you can copy the URL for sharing that Workspace view internally;
* Tags will be automatically removed when they are no longer applied to any map or workflow.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-9bd908aea55c556c920ef468abd22cc59b6c60c6%2Fcreate_tag%20(1).gif?alt=media" alt=""><figcaption><p>Creating and applying a tag in the Maps Workspace</p></figcaption></figure>

## Network planning and coverage analysis for Telco with the Analytics Toolbox for BigQuery

June 28th, 2024

<mark style="color:green;">**New**</mark> *Analytics Toolbox*

We are thrilled to announce our new functions for line of sight and signal propagation analysis in the Analytics Toolbox for BigQuery. These new procedures, available in the [telco](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-bigquery/sql-reference/telco) module, enable network planners to run **coverage analysis** natively within BigQuery. With this functions users can now assess the geographical areas where current or potential new network's signal is available and evaluate its quality.

This release includes procedures for:

* **Path profile** analysis to evaluate the **line of sight** and identify potential obstructions between two points;
* **Path loss** estimation of a signal as it propagates through an environment, with options for the [Close In](https://arxiv.org/pdf/1602.07533) and [Extended Hata models](https://www.itu.int/dms_pub/itu-r/opb/rep/R-REP-SM.2028-2-2017-PDF-E.pdf).

Learn more about these new features in our [documentation](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-bigquery/sql-reference/telco), and start testing them by following our step-by-step [tutorial](https://academy.carto.com/advanced-spatial-analytics/spatial-analytics-for-bigquery/step-by-step-tutorials/analyzing-signal-coverage-with-line-of-sight-calculation-and-path-loss-estimation).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-94e4e4fc4ca697626f5a95f4f10747f57f4e5bf5%2Faaa_coverage_analysis_v2.gif?alt=media" alt=""><figcaption></figcaption></figure>

## New space-time analysis capabilities in the Analytics Toolbox for BigQuery

June 28th, 2024

<mark style="color:green;">**New**</mark> *Analytics Toolbox*

We are excited to announce the addition of two new space-time analyses available in the [statistics](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-bigquery/sql-reference/statistics) module of the Analytics Toolbox for BigQuery:

* [**Space-time hotspot classification**](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-bigquery/sql-reference/statistics#spacetime_hotspots_classification)**,** to classify hotspots based on changes in their intensity over time, such as strengthening hotspots, declining hotspots, occasional hotspots, and more;
* [**Time-series clustering**](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-bigquery/sql-reference/statistics#time_series_clustering)**,** to identify locations with similar temporal behaviors.

Learn more on how to perform these spatiotemporal analyses by exploring our tutorials for [space-time hotspot classification](https://academy.carto.com/advanced-spatial-analytics/spatial-analytics-for-bigquery/step-by-step-tutorials/spacetime-hotspot-classification-understanding-collision-patterns) and [time-series clustering](https://academy.carto.com/advanced-spatial-analytics/spatial-analytics-for-bigquery/step-by-step-tutorials/time-series-clustering-identifying-areas-with-similar-traffic-accident-patterns).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-a1b434c3d8f1739ebf0a013ad3d694dc51376954%2Faaa_spacetime_gif.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Heatmap visualizations at scale for massive point-based data

June 20th, 2024

<mark style="color:green;">**New**</mark> *Builder, CARTO for Developers*

We are thrilled to announce density heatmap visualization supporting very large scale point-based datasets! This new feature allows you to render massive point datasets as a heatmap in a scalable and performant manner. Available now in **Builder**, you can easily identify hotspot patterns and gain insights from your data.

Developers can also build their own large-scale heatmaps in their apps using **CARTO + deck.gl**, with the new `heatmapTileLayer` (Experimental). Learn more from our [documentation](https://deck.gl/docs/api-reference/carto/heatmap-tile-layer) and [examples](https://github.com/CartoDB/deck.gl-examples/tree/master/dynamic-tiling-heatmap).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-b8bbab3f73480fb87ed375b51095bd4c74053427%2Fheatmap.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Improved Data Importing Capabilities in Workflows

June 19th, 2024

<mark style="color:green;">**New**</mark> *Workflows*

We are excited to introduce enhanced data importing capabilities in CARTO Workflows. This new release includes a variety of features designed to simplify and expand the ways you can import data into your workflows, providing greater flexibility and functionality.

#### New Features:

**Import from URL Component**

* This [**new component**](https://docs.carto.com/carto-user-manual/workflows/components/input-output#import-from-url) allows users to import data directly from a public URL. It is compatible with BigQuery, Snowflake, Redshift, and PostgreSQL. By leveraging the CARTO Import API, this component ensures seamless data integration across different database systems.
* The [**Import from URL** ](https://docs.carto.com/carto-user-manual/workflows/components/input-output#import-from-url)component supports workflows that run on a schedule or are executed via API, providing more robust and automated data management options.

**Sunset of Previous Method**

* The [previous data importing method](https://docs.carto.com/carto-user-manual/workflows/workflow-canvas#import-a-file-to-your-workflow), which was limited to UI-based operations, will be deprecated. The new Import from URL component provides a more versatile and powerful alternative.

**Quick Import from your desktop**

* Users can now quickly [**import files**](https://docs.carto.com/carto-user-manual/workflows/data-sources#files) from their computers directly into the workflow canvas. This feature supports drag-and-drop functionality, making it easier to integrate local files into your workflows.
* Files uploaded in this manner remain accessible within each workflow, ensuring consistent data availability and management.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-674860ea3a9875ecb625ebaefa469f3797621c17%2Fdraganddrop_files.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Support for calling external API services from Workflows

June 3rd, 2024

<mark style="color:green;">**New**</mark> *Builder*

We are thrilled to announce a powerful new feature for Workflows: the ability to connect your workflows with external API services. With this new capability, we enabling use cases like the following:

* Retrieve Data from External APIs: Augment your datasets by pulling in information from APIs such as Google Environment APIs, government, cadaster, parcel data, and other specialized data sources.
* Trigger Actions via API: Automatically trigger external processes, send notifications, or execute commands directly from your workflows, like:
  * Notify on chat applications: Send real-time notifications to your company's channels to keep your team updated on workflow executions.
  * Integrations with automation tools: Integrate with automation tools to trigger external actions from a Workflow execution.
* Send data from your Workflows to external APIs: Use data from any node in your workflow to build the body for a request.

Leverage all this new functionality by using the new [**HTTP Request**](https://docs.carto.com/carto-user-manual/workflows/components/input-output#http-request) component: A dedicated Workflows component that facilitates making requests to external APIs, providing enhanced versatility and extensibility. It uses the `http_request` module from the CARTO Analytics Toolbox.\
\
It also supports [custom expressions and variables](https://docs.carto.com/carto-user-manual/workflows/using-variables-in-workflows#using-variables-and-expressions-in-components) to embed logic directly into component settings using SQL operators combined with variable and column values.\\

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-b32371d4e19496777c962c5f80fd2b61bc052ea6%2Fhttp_request.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Support for custom basemaps in Builder

May 16th, 2024

<mark style="color:green;">**New**</mark> *Builder*

A basemap is a crucial component of any map, providing essential context, spatial features, and the visual foundation for your creations. To meet the unique needs of each organization, we now enable you to bring your own basemap directly into your CARTO organization.

Admin users at CARTO can now upload custom basemaps and tailor the basemap gallery options available to Editor users in Builder. Unleash your creativity and enjoy an enhanced map-making experience while maintaining a cohesive and consistent selection of basemaps throughout your organization.\
\
To learn more about how you can upload custom basemaps to the CARTO platform and the supported formats, check [this page](https://docs.carto.com/carto-user-manual/settings/customizations/configuring-your-organization-basemaps). For a step-by-step guide on custom basemaps, check out our [new tutorial](https://academy.carto.com/building-interactive-maps/data-visualization/customize-your-visualization-with-tailored-made-basemaps) in the Academy.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-c565bc91dc612a6543cc8f004b58f6612f25cd4f%2Fcustombasemap1.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Performance optimizations in Builder maps

May 14th, 2024

<mark style="color:orange;">**Improvement**</mark> *Builder*

We are excited to introduce a set of enhancements in CARTO Builder designed to further improve the performance of our interactive map visualizations. With these improvements, Builder will:

* **Load only essential properties**: Builder will now load only the essential properties from your tables or SQL queries when they are needed in the map. This reduces unnecessary data transfer and speeds up processing.
* **Reduce tile requests**: The number of tile requests has been significantly reduced, resulting in faster map loading times and a smoother user experience.
* **Limit simultaneous queries**: To enhance stability and prevent overload, Builder will limit the number of simultaneous queries, ensuring a more reliable performance.

These enhancements are part of our ongoing commitment to providing the best possible experience with CARTO Builder.\\

<figure><img src="https://lh7-us.googleusercontent.com/DHKsMLKqCbffRfMrj4FVXCPyOaqgMhQgVCbIynNHGOiniFC1otnAa0EK6ixfaq5uejJ85aNmYhU0ACJKSBeDAI8Szy-YitWsxkOh1VmfgrBQYh1QSlmhXoIyzh-aVi1Kg429toJ9oq26-HDMozj9327z-w=s2048" alt=""><figcaption></figcaption></figure>

## Redesigning our Developers section in CARTO Workspace

April 29th, 2024

<mark style="color:orange;">**Improvement**</mark> *Workspace*

We believe that all paths to success start from the CARTO Workspace, and the path to successfully developing powerful geospatial apps isn't an exception. With this in mind, we've carefully redesigned the experience when accessing the Developers section, and these are the highlights:

* New Overview with a curated list of [documentation, guides and examples](https://github.com/CartoDB/gitbook-documentation/blob/master/whats-new/broken-reference/README.md).
* A simplified [Credentials](https://docs.carto.com/carto-user-manual/developers/managing-credentials) system to manage all your authentication methods.
  * This change unifies the management of API Access Tokens and OAuth Clients (*previously known as Applications*) in a single section, making more clear what each method is best for.
* A new list containing all your [API-enabled Workflows](https://docs.carto.com/carto-user-manual/workflows/executing-workflows-via-api), for easy access.

Additionally, we've simplified the way that organizations decide the content in their [Applications](https://docs.carto.com/carto-user-manual/applications) section. Before, it was a mix of developer credentials and apps registered by the administrator. Now, administrators in CARTO are in full control of [managing Applications](https://docs.carto.com/carto-user-manual/settings/advanced-settings/managing-registered-apps), including the visibility/sharing settings.

*Developer credentials created before April 25th have been duplicated as applications to maintain the same visibility level as previously.* [*Read more here.*](https://docs.carto.com/carto-user-manual/developers/managing-credentials)

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-ad7aec2a3cd68b3ea252236a3d5ef22a3261cc5b%2FScreenshot%202024-04-29%20at%2018.03.21.png?alt=media" alt=""><figcaption></figcaption></figure>

## Extended support for raster data sources in Imports, Data Explorer and Workflows

April 24th, 2024

<mark style="color:green;">**New**</mark> *Workspace, Workflows*

We're happy to introduce a suite of powerful new features that are set to enable working with raster data in CARTO. Before these were available, working with raster data required using external CLI applications and dealing with SQL queries manually in order to leverage the analytical capabilities of the CARTO Analytics Toolbox for Snowflake and BigQuery.

**Import Cloud Optimized GeoTIFFs**: We have made raster data ingestion processes a lot easier: with our latest enhancements, you can now effortlessly import Cloud Optimized GeoTIFFs to [Snowflake](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-snowflake/guides/working-with-raster-data) and [BigQuery](https://docs.carto.com/data-and-analysis/analytics-toolbox-for-bigquery/guides/working-with-raster-data) via both the Import API and the [Workspace UI](https://docs.carto.com/carto-user-manual/data-explorer/importing-data). This provides a streamlined and efficient method for ingesting raster files into BigQuery and Snowflake, ensuring optimal storage efficiency and fast query access.

**Raster Tables in Data Explorer**: Dive deeper into your raster data in the data warehouse with full support for raster tables in the Data Explorer. Gain access to a specific set of metadata and custom actions for raster tables.

**Workflow Components for Raster Analysis**: Take your spatial analyses to the next level with our new Workflow components designed specifically for working with raster data sources. Whether you're looking to extract raster values or perform complex intersect and aggregate operations, our new components, including "[Get Raster Values](https://docs.carto.com/carto-user-manual/workflows/components/raster-operations#get-values-from-raster)" and "[Intersect and Aggregate Raster](https://docs.carto.com/carto-user-manual/workflows/components/raster-operations#intersect-and-aggregate-raster)", provide you with the tools you need to unlock valuable insights from your raster datasets.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-0b6e395146230aff92bca7f992dc499a3e235b92%2Fimport_raster.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Generate PDF reports from your Builder maps

April 17th, 2024

<mark style="color:green;">**New**</mark> *Builder*

We’ve launched a new feature that allows you to download detailed PDF reports of your interactive Builder maps. These reports capture everything from the current map extent to widgets, parameters, and the map description.

Whether you're sharing insights with colleagues, presenting to stakeholders, or documenting your analysis, this new feature packs the richness of your interactive maps into a portable, easy-to-share format.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-3c1343ff2105b61feeccadf87d2c8cf40c79b085%2Fexportpdf.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Get quicker, better answers with the new AI-powered help sidebar

April 11th, 2024

<mark style="color:orange;">**Improvement**</mark> *Workspace*

A new **AI-powered help assistant** can now be found in the Help sidebar, available at all times from CARTO Workspace, Builder and Workflows.

It will provide quick answers based on our documentation and will link to the most relevant resource. With our documentation evolving and growing in size and depth, this AI-powered tool will save precious time and will guide you in the right direction without leaving CARTO. Ask anything!

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-0000be35be080384afa16a0815e86f0674b22888%2FNEW%20HELP%20SIDEBAR.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Preview Builder maps during edition

March 31st, 2024

<mark style="color:green;">**New**</mark> *Builder*

This new feature simplifies the map-making process by letting Editor users switch seamlessly between editing and previewing. With [Preview mode](https://docs.carto.com/carto-user-manual/maps/sharing-and-collaboration/map-preview-for-editors), these users can easily see how the map will look like to viewers, allowing them to review and refine it before sharing. This smooth workflow ensures that maps are well-presented and meet the highest standards of clarity and effectiveness.

Additionally we've enhanced our map-sharing functionality to deliver a smoother and more intuitive experience. This update focuses on streamlining the process of sharing maps with others, ensuring a more seamless interaction. Dive into the details of these improvements in our [documentation](https://docs.carto.com/carto-user-manual/maps/sharing-and-collaboration).

<figure><img src="https://lh7-us.googleusercontent.com/PkJbbKvVqhiFRIzQsb77-lfhKKxBm3WAZFOLd6M2kBzArwdQ4csXPhIconCCVZBPUYtEfWtL74AQnKXQtra8yiGqaRmaNl7b-b2pNExuFd8pylNCuzCrIZ_YI7oulWLdlTbU7a3zEh2uSXXuM8U5N8U" alt=""><figcaption></figcaption></figure>

## Introducing: deck.gl v9

March 27th, 2024

<mark style="color:green;">**New**</mark> *CARTO for Developers*

A **new major version of deck.gl** is out. deck.gl is the open-source visualization library that powers all CARTO visualizations, and one of the main components of [CARTO for Developers](https://github.com/CartoDB/gitbook-documentation/blob/master/whats-new/broken-reference/README.md).

* For a complete changelog, visit the official [**deck.gl what's new**](https://deck.gl/docs/whats-new).
* To address breaking changes, read the official [**deck.gl upgrade guide**](https://deck.gl/docs/upgrade-guide). Changes in the CARTO module are also addressed there.
* We have also published a complete set of [**new examples using CARTO + deck.gl**](https://docs.carto.com/carto-for-developers/examples).

We're very happy to see CARTO joining efforts with many other contributors from the vis.gl and OpenJS Foundation communities. Read more about this release in the [CARTO blog](https://carto.com/blog/announcing-deck-gl-v9-webgpu-ready-with-typescript-support).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-8564962ebfc580723e0a60edee244fe079ca7821%2F660458f270898847e0f6b955_Announcing%20Deck.gl%20v9%20WebGPU%20ready%20and%20with%20TypeScript%20support%20(2)-p-800.png?alt=media" alt=""><figcaption></figcaption></figure>

## Support for scheduling the execution of workflows

March 21st, 2024

<mark style="color:green;">**New**</mark> *Workflows*

With this new capability, analytical pipelines created with Workflows can be [**scheduled**](https://docs.carto.com/carto-user-manual/workflows/scheduling-workflows) so they are executed on a specific period:

* **Hours:** The workflow will be executed every X hours, at o'clock times.
* **Days:** The workflow will be executed every day at a specific time.
* **Weeks:** The workflow will be executed weekly, on a specific day, at a specific time.
* **Months:** The workflow will be executed monthly, on a specific day, at a specific time.
* **Custom:** Use a custom expression to define the schedule.

CARTO leverages native scheduling capabilities on each data warehouse to provide this functionality in all CARTO Data Warehouse, BigQuery, Snowflake and PostgreSQL connections.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-2213e5ee0e2a255b2a48e2ae511e320e02ce9aee%2Fworkflow_schedule_zoomed.gif?alt=media" alt=""><figcaption></figcaption></figure>

## Support for private embedding of CARTO Builder maps

March 14th, 2024

<mark style="color:orange;">**Improvements**</mark> *Builder*

Maps created with CARTO Builder can now be embedded anywhere — **even when they're not shared publicly**. With private embedding you can restrict and maintain control over who can view these maps when embedded on web pages or apps.

To leverage private embedding simply share your map with the organization or with the specific groups you want to share the map with. These users need to be previously logged-in to CARTO to view the embedded map. Learn more at our [Embedding maps documentation](https://docs.carto.com/carto-user-manual/maps/sharing-and-collaboration/embedding-maps).

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-b04b70215bab58d076ee85a69c897d9aedaa266b%2FScreenshot%202024-03-14%20at%2016.42.53.png?alt=media" alt=""><figcaption><p>An example of a private embedded map where the user does not have access to the embedded content</p></figcaption></figure>

## New Workflows components for low-code geospatial analytics

February 29th, 2024

<mark style="color:green;">**New**</mark> *Workflows*

During the last few weeks, we’ve been progressively adding new and improved components in CARTO Workflows:

* [**Case When**](https://docs.carto.com/carto-user-manual/workflows/components/data-preparation#case-when) component for supporting column values based on conditional expressions.
* [**Edit Schema**](https://docs.carto.com/carto-user-manual/workflows/components/data-preparation#edit-schema) component (replacing Refactor Columns): clean schemas, rename and cast columns.
* Added ‘Append’ mode to [**Save as Table**](https://docs.carto.com/carto-user-manual/workflows/components/import-export#save_as_table)**.**
* Added ‘Maximum distance’ setting to [**K-Nearest Neighbors**](https://docs.carto.com/carto-user-manual/workflows/components/spatial-analysis#knn_neighbors).
* Added [**Extract from JSON**](https://docs.carto.com/carto-user-manual/workflows/components/data-preparation#extract-from-json) for extracting values from JSON columns using the native syntax from each data warehouse.
* Added ‘Mode’ setting to [**H3 Polyfill**](https://docs.carto.com/carto-user-manual/workflows/components/spatial-indexes#h3_polyfill) and [**Quadbin Polyfill** ](https://docs.carto.com/carto-user-manual/workflows/components/spatial-indexes#quadbin_polyfill)components.
* [**Subdivide**](https://docs.carto.com/carto-user-manual/workflows/components/spatial-operations#subdivide) to split larger geometries into easier-to-process smaller features.
* New UI for [**Draw Custom Features**](https://docs.carto.com/carto-user-manual/workflows/components/parsers#draw-custom-features) component
* [**Composite Score Supervised**](https://docs.carto.com/carto-user-manual/workflows/components/statistics#composite-score-supervised): Create composite scores with the supervised method using this component. [Take a look at the example template](https://academy.carto.com/creating-workflows/workflow-templates/statistics#create-a-composite-score-with-the-supervised-method-bigquery).
* [**Composite Score Unsupervised**](https://docs.carto.com/carto-user-manual/workflows/components/statistics#composite-score-unsupervised)**:** Create composite scores with the supervised method using this component. [Take a look at the example ](https://academy.carto.com/creating-workflows/workflow-templates/statistics#create-a-composite-score-with-the-unsupervised-method-bigquery)template

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-d616d3c25a00402dc3d7a2a36dec105f83f26786%2FCaptura%20de%20pantalla%202024-03-07%20a%20las%2019.24.53.png?alt=media" alt=""><figcaption></figcaption></figure>

## Extended support for URL parameters in Builder maps

February 21st, 2024

<mark style="color:orange;">**Improvements**</mark> *Builder*

Exciting news – CARTO Builder has expanded its [URL parameter](https://docs.carto.com/carto-user-manual/maps/sharing-and-collaboration/url-parameters) capabilities to include widgets, SQL parameters, search locations, and feature selections. Now, when viewers interact with these elements, the URL updates in real time, making it easier to share customized map views. This update opens up possibilities for creating varied views from a single map, simplifying sharing, and minimizing the need for multiple map versions. It also enhances the embedding of maps into websites or apps, providing a seamless user experience without unnecessary redirections.

<figure><img src="https://3029946802-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FybPdpmLltPkzGFvz7m8A%2Fuploads%2Fgit-blob-4f1aa050d74d59f4be1ce5390850b9d541c75329%2FScreen%20Recording%202024-02-21%20at%2018.46.41.gif?alt=media" alt=""><figcaption></figcaption></figure>