Release Notes
For Self-Hosted deployments
Last updated
Was this helpful?
For Self-Hosted deployments
Last updated
Was this helpful?
View this release on GitHub -> |
Analytics Toolbox version required
This version is intended to work with the following Analytics Toolbox versions:
BigQuery
Snowflake
Databricks
Redshift
PostgreSQL
If you're using Helm or Docker Compose, please ensure that your installation is running the latest customer package version. Keeping your deployment up to date ensures access to support services and provides the latest features, bug fixes, and security enhancements.
New:
Onboarding improvements: We've added a series of onboarding improvements for new CARTO users, including new introductory videos in the Workspace and a few minor tweaks to the onboarding tasks in the onboarding checklist.
Partial dry-runs in Workflows: We’re introducing partial dry-runs in Workflows to improve stability and performance. Dry-run queries will now only be executed for components with non-deterministic schemas —such as Custom SQL, Custom Python, Call Procedure, and others.
Asset management table improvements: We've added an Owned by filter to the asset management table in the settings, which is only visible to .
Improvements:
We've increased the timeout for the LDS API from one minute to three minutes.
Improved widget accuracy for dynamic tiling sources using Quadbin or H3 spatial indexes when a mask or viewport is used as the spatial filter in Builder. Aggregation resolution is now determined by the spatial extent rather than the zoom level, providing higher precision in smaller areas and ensuring stable, accurate widget results across zoom levels.
Record counts in Workflows’ nodes are now obtained via table stats instead of count queries. They're only shown when a component is selected.
Added support for additional TomTom options in the LDS async batch geocoding endpoint.
The /v3/lds/geocoding/job endpoint now supports more TomTom parameters—such as lat, lon, radius, countrySet, topLeft, btmRight, view, and entityTypeSet—instead of only language. This enhances flexibility when using the GEOCODE_TABLE_AT function.
Fixes from last release:
Fixed an issue with API executions of a Workflow when a variable was used more than once in the same Workflow.
Fixed an issue that was causing a generalised 500 error if the map thumbnail generation failed. We are now returning an empty thumbnail in those cases and catching the errors properly.
Fixed an issue with M2M credentials and the new Resource APIs. Resource APIs will now work with M2M-based authentication when using new or updated M2M OAuth Clients.
Known issues:
Known issues from past releases:
Analytics Toolbox version required
This version is intended to work with the following Analytics Toolbox versions:
BigQuery
Snowflake
Databricks
Redshift
PostgreSQL
New:
Improvements:
When group-role mapping is enabled, user groups are no longer automatically assigned the Viewer role by default. Instead, they remain in an undefined state until an Admin explicitly assigns a role—preventing unintended role downgrades.
Editors now have enhanced control over layers in the map. In addition to toggling the visibility of a layer’s legend, they can now decide whether the layer itself appears in the map’s layer list—directly from the Legend tab.
The user method now includes the SSO IdP identifier for users with the same email, ensuring better identity resolution in multi-provider environments.
The Data Observatory tab in Builder and Workflows will be deprecated on September 30th, 2025. A message now informs users of this upcoming change.
Fixes from last release:
Fixed an issue that caused the screen to freeze when adding grants to an API access token.
The existing DataSourceCreated and DataSourceUpdated events now include a mapId field. Additionally, a new event—DataSourceDeleted—has been added to track sources being removed from Builder maps, also including the mapId.
Fixed an issue in the Telco Signal Propagation extension package where installation from the built-in catalog failed. The package can now be installed directly from the catalog.
Fixed an issue in Workflows when running without cache and using the “Append to existing table” option in the Save as Table component. New rows are not correctly appended.
Fixed a bug that prevented users from creating workflows from examples during onboarding (only applicable when using the CARTO Data Warehouse).
Known issues:
Known issues from past releases:
Analytics Toolbox version required
This version is intended to work with the following Analytics Toolbox versions:
BigQuery
Snowflake
Databricks
Redshift
PostgreSQL
New:
Data Enrichment components in Workflows for Databricks, to 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.
Click-type interactions in Builder are now server-side, which reduces significantly the size of the map tiles.
Improvements:
Improved health-checks for our APIs in the Helm chart
Added the possibility to create Snowflake connections that don't use a refresh token, and improved the reconnect experience in different parts of the application when the token has expired.
Support virtual scroll on Category Widget in Builder ensuring good performance even when searching, exploring and filtering more than 2,000 of categories.
In Databricks connections, all binary columns are typed as ‘geometry’ in all Data Explorer instances. They're expected to contain valid WKB geometry. Other types of data stored in a binary column will just return errors in map instantiations.
Fixes from last release:
Fixed an issue with the Create Routes component in Workflows that prevented usage from API.
Fixed an issue that prevented execution of some workflows via API when cache is disabled.
Fixed front-end performance issues in Workflows, related to excessive memory usage and inefficient node state management.
Fixed executed nodes consistency issues in Workflows. When a workflow has been run, its “executed” state is now consistent across refreshes.
Fixed to ensure the color scale is not reset when applying property to style stroke color on spatial index.
Known issues:
Known issues from past releases:
Improvements:
The router-metrics component has been thoroughly improved, resulting in a more stable component that requires less memory resources.
Fixes from last release:
Fixed an issue in CARTO Builder where the Others bucket in a category widget would incorrectly display the SUM of all averages in that category, instead of the AVG.
Fixed an issue in CARTO Builder where sometimes the color scale set to quantile/quantize would lose its configuration after refreshing
Fixed an issue in CARTO Builder where viewers of a map could edit the name of SQL Parameter controls (even if the changes wouldn't be saved in the map)
Known issues from past releases:
In Workflows for Databricks connections, when selecting a destination table for Save as Table and tileset components, an overwrite warning always appear, regardless of the destination table name.
When Running a Workflow in Databricks, the count of some components (like Simple filter or Spatial filter) does not return the number of rows and columns correctly.
When creating a map from a raster table in Workflows and having the map in Builder, the query contains the job information.
The Get Values from Raster component produces a map preview from the node that was previously selected.
In a connection's credentials settings, Save changes should be disabled if no changes have been made.
We're not showing an error message when selecting an invalid column and spatial data type in Builder.
In Workflows for BigQuery, an Extension Package cannot be uninstalled neither from the list view nor from the tree view.
Improvements:
Added HTTP2 support for router-http component when it has HTTPs enabled.
The zoom level for point geometries in the Table Widget in Builder has been updated from 20 to 17.
The Unmatch output in the Spatial Filter component now returns the difference between the input table and the match output.
Fixes from last release:
Fixed an issue on Dynamic Tiling for PostgreSQL that was producing excessively large tiles due to an inefficient aggregation of points.
Fixed an issue when performing ANY_VALUE aggregation for Dynamic Tiling using point geometries.
Snowflake connections can now be created while using an external proxy.
Fixed a minor issue that resulted in the URL flashing when tags were selected and the user changed the workspace section.
Fixed the OpenBuilderMap event for authenticated viewers. The event is now fired for all authenticated users, allowing you to build map-related metrics (except for public maps) through your Activity Data.
Known issues from past releases:
In Workflows for Databricks connections, when selecting a destination table for Save as Table and tileset components, an overwrite warning always appear, regardless of the destination table name.
When Running a Workflow in Databricks, the count of some components (like Simple filter or Spatial filter) does not return the number of rows and columns correctly.
When creating a map from a raster table in Workflows and having the map in Builder, the query contains the job information.
The Get Values from Raster component produces a map preview from the node that was previously selected.
In a connection's credentials settings, Save changes should be disabled if no changes have been made.
We're not showing an error message when selecting an invalid column and spatial data type in Builder.
In Workflows for BigQuery, an Extension Package cannot be uninstalled neither from the list view nor from the tree view.
Improvements:
Enhanced persistence of user roles in the database.
Upgraded the Create Isolines component in Workflows to include provider-specific settings directly in the component's UI, offering greater flexibility and control.
Improved support for higher precision when importing geospatial data.
Fixes from last release:
Disabled unsupported MODE aggregation for string fields in Redshift in Builder's field selector.
Fixed Search functionality in the Table widget when working with long SQL query sources.
Fixed an issue limiting hex color code styles to 20 values under certain scenarios due to cache issues.
Fixed “Facilitate CARTO access” for organizations with SSO.
Fixed a minor styling issue when previewing tilesets in the Data Explorer.
Fixed an issue that prevented users from previewing single-column tables.
Fixed issues with the “Enrich Polygons with Weights” component in Workflows.
Fixed an issue related to highlighting and zooming from the Table widget with PostgreSQL BigInt H3 sources.
Fixed an issue where changes to credentials (SPA OAuth Clients and M2M OAuth Clients) were slow to appear.
Known issues:
Snowflake not supported when using external proxy.
Workflows for Databricks connections, when selecting a destination table for Save as Table and tileset components, an overwrite warning always appear, regardless of the destination table name.
When Running a Workflow in Databricks, the count of some components (like Simple filter or Spatial filter) does not return the number of rows and columns correctly
Known issues from past releases:
The 'refresh' button and the link from the 'Update AT' chip should be removed from Snowflake connection cards.
When creating a map from a raster table in Workflows and viewing the map in the Builder, the query contains the job information.
The Get Values from Raster component in Workflows is displaying the map preview from the node that was previously selected, not the current one.
The URL flashes when filtering by a tag in Maps and then going to Workflows (and vice versa).
In the Developers section, Credentials tab: if you open a credential (View or edit credential), the Save changes button should be disabled if no changes have been made.
There is no error message when selecting an invalid column and spatial data type in the Builder.
In a BigQuery connection in Workflows, an Extension Package cannot be uninstalled neither from the list view nor from the tree view.
New:
Improvements:
Widgets and exports for dynamic spatial index sources are now working server-side in Builder. The widget can now be configured as Global, with support for the Time Series Widget and direct usage of properties without aggregation during configuration.
The Table Widget in Builder now supports Global mode across all current data sources, with the exception of pre-generated tilesets. This global functionality extends to both the data displayed within the widget and the new Search feature, allowing consistent filtering and data exploration.
The "Enrich Polygons with Weights" component has been added to Workflows created with BigQuery connections.
The Enrichment UI feature has been removed, and enrichments have been fully transitioned to Workflows.
Changes to how Workflows fetches schemas for each node improve stability and resolve a number of existing issues.
Fixes from last release:
Fixed an issue in Workflows that prevented the "Import from URL" feature from working correctly on imported workflows and templates.
Fixed a warning issue related to SQL parameters, which did not appear when filtering by empty rows with spatial index sources in Redshift.
Fixed the removal of unnecessary events when users log in.
Fixed an issue where the token search box in the developer section disappeared if the search returned no results.
Fixed issues preventing some users from joining their organization through invitations.
Fixed the display of the aggregation option MODE, which is not supported for Redshift spatial index sources in Builder.
Known issues:
Search in Table widget not functioning for very long SQL query sources in Builder.
Known issues from past releases:
When creating a map from a raster table in Workflows and viewing the map in the Builder, the query contains the job information.
The Get Values from Raster component in Workflows is displaying the map preview from the node that was previously selected, not the current one.
The URL flashes when filtering by a tag in Maps and then going to Workflows (and vice versa).
In the Developers section, Credentials tab: if you open a credential (View or edit credential), the Save changes button should be disabled if no changes have been made.
Also in this section: when editing credentials (SPA OAuth Clients and M2M OAuth Clients) the changes are slow to appear.
There is no error message when selecting an invalid column and spatial data type in the Builder.
The geometry column becomes string type in category and pie widgets in the Builder.
In a BigQuery connection in Workflows, an Extension Package cannot be uninstalled neither from the list view nor from the tree view.
New:
Improvements:
The system to control access to new features and previews has changed. Now it's fully controlled within your instance, and does not require connectivity. We've removed events.launchdarkly.com, stream.launchdarkly.com, clientstream.launchdarkly.com from the optional network egress requirements.
When creating a connection to Snowflake, the Account Name field now also accepts a full Account URL (eg: https://test.us-east-2.aws.snowflakecomputing.com).
Now Data Explorer shows the number of rows for BigQuery views.
Activity Data can now be exported up to 60 days (instead of 30).
The Workflows temp. location field in Connections now accepts custom 2-level paths, such as project.dataset for BigQuery connections.
Fixes:
Fixed an issue where the Maps list wouldn't scroll past the first 96 maps.
Fixed an issue with the Union All component in Workflows that could cause a syntax error on the generated SQL code.
Fixed an issue that could prevent data sources in Workflows from loading correctly when they were connected to aggregation components.
We've ensured that the layer selector in Builder for split view mode acts independently for each view. Before, the layer selector may affect both sides of the split.
Fixed an issue in Builder where styling would fail for spatial index layers (eg: H3) under specific circumstances involving column names.
Fixed an issue in Builder where SQL parameters in public maps may end in errors related to authorization.
Fixed an issue in Workflows where numeric parameters in the Create Vector Tileset component would not work as expected.
Fixed an issue in the router-metrics container where it would take too long to be deleted.
Activity Data: fixed UserLogins event, now correctly sent for every login. Fixed CartoAccessConsent event, now correctly sending the userId that gave consent.
Fixed an issue when deleting a workflow from Workspace when filter and tag filters were applied.
Other minor UI and copy fixes in Data Explorer and Connections.
Known issues from past releases:
When creating a map from a raster table in Workflows and viewing the map in the Builder, the query contains the job information.
The Get Values from Raster component in Workflows is displaying the map preview from the node that was previously selected, not the current one.
The URL flashes when filtering by a tag in Maps and then going to Workflows (and vice versa).
In the Developers section, Credentials tab: if you open a credential (View or edit credential), the Save changes button should be disabled if no changes have been made.
Also in this section: when editing credentials (SPA OAuth Clients and M2M OAuth Clients) the changes are slow to appear.
There is no error message when selecting an invalid column and spatial data type in the Builder.
The geometry column becomes string type in category and pie widgets in the Builder.
In a BigQuery connection in Workflows, an Extension Package cannot be uninstalled neither from the list view nor from the tree view.
New:
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.
Improvements:
We updated the base image from Debian Buster (out of support) to Ubuntu Jammy in some of the containers.
We introduced a new Superadmin role for viewing, deleting and transferring any Map/Connection/Workflow within the organization.
An NPS survey service to gather product feedback from our users.
We’ve made slight changes to the design of the Map/Workflow cards in the Workspace.
Fixes:
We have removed Hexcolor styling for Heatmap layer visualizations since it wasn't supported there.
We fixed a bug where tags were not being automatically deleted when the map or workflow where they were applied was deleted.
Signing up as part of the Just-in-time (JIT) flow will now always redirect to the "Join organization" page.
We were displaying an ID instead of the group name (Alias) in the group input of the share map modal. The alias is now displayed.
Fixed a typo in Number of Points component's name in Workflows.
Fixed an issue where granting SQL API in the “Allowed APIs” field of an API Access Token would not grant access to all endpoints of the SQL API.
Known issues:
When creating a map from a raster table in Workflows and viewing the map in the Builder, the query contains the job information.
The Get Values from Raster component in Workflows is displaying the map preview from the node that was previously selected, not the current one.
The URL flashes when filtering by a tag in Maps and then going to Workflows (and vice versa).
In the Developers section, Credentials tab: if you open a credential (View or edit credential), the Save changes button should be disabled if no changes have been made.
Also in this section: when editing credentials (SPA OAuth Clients and M2M OAuth Clients) the changes are slow to appear.
There is no error message when selecting an invalid column and spatial data type in the Builder.
The geometry column becomes string type in category and pie widgets in the Builder.
In a BigQuery connection in Workflows, an Extension Package cannot be uninstalled neither from the list view nor from the tree view.
New:
Simplified application management. Before, the Applications section in Workspace was a mix of developer credentials and apps registered by the administrator. Now, administrators in CARTO are in full control of managing Applications, including the visibility/sharing settings.
Support for loading, storage and visualization of raster pyramids. CARTO Import API and raster-loader will now support pre-existing overviews in Cloud Optimized GeoTIFF files. Once loaded as raster tables, overviews will be used by CARTO Maps API to visualize raster data at different zoom levels.
Activity Data (Preview/Beta): Using Activity Data, administrators can export detailed activity logs and API usage data from their CARTO organization. Get in touch through your usual CARTO representative to preview the feature.
Improvements:
By requesting larger tiles, we have reduced the number of tile requests from Builder, resulting in faster map loading times and a smoother user experience.
Organization ID and CARTO Self Hosted version are now displayed in Workspace Settings section.
We introduced an improvement to how SSO groups are searched and displayed in the front end.
Fixes:
Changed Content-Security-Policy header in router, for /map and /viewer paths. With this, public maps can be embedded into any website. The img-src CSP attribute is set to “any value”.
CARTO containers now use readonly root filesystems.
Architecture changes in Workflows application storage that fixes a number of issues and increases stability.
Fixed an error when reporting big table's row count on Redshift.
Fixed an issue where some SVG images throughout the Workspace were not being displayed properly.
Added a fix for showing all CARTO user invitations in the UI.
Improved performance on Dynamic Tiling for PostgreSQL and Redshift when generating polygons or lines tiles.
Introduced a fix to avoid inaccurate line geometries from tilesets when zoomed into higher zoom levels.
Known issues:
Builder: Heatmap layer visualization does not support Hexcolor styling. This option will be removed from the UI in the next Self-Hosted release.
Workflows: 'Get Values from Raster' component shows the map preview from the previously selected node.
Workspace: Error when selecting a label and changing a section.
Workspace: Credentials - There is slight delay in displaying changes when editing credentials (SPA OAuth Clients and M2M OAuth Clients).
New:
Improvements:
When importing a file in the Data Explorer, we now suggest importing it in the location from which the import action is triggered.
New shortcut to invite new users from the main menu.
Commercial Hotspots component in Workflows renamed to Hotspot Analysis and moved to the Statistics category.
Improved error handling in Builder when incorrectly using selection tool.
Measure tool improvements on tooltip for better usability.
Improvements on occasional scroll issues on Builder layer panel.
Enhancement on layer rendering when the stroke size is based on a property.
Configuration for Import API components has changed to allow up to 2GB of RAM allocation.
Fixes from last release:
Fix issue when selecting time ranges in SQL Date Parameter.
Fix rotation issue when using custom markers.
Fix issues in widgets for PostgreSQL when SRID is different to 4326
Fixes to several Workflows components
Create Isolines
Cluster K-Means
ST Voronoi
Where
Draw Custom Features
New:
New Workflows components and improvements:
Case When component for supporting column values based on conditional expressions.
Edit Schema component (replacing Refactor Columns): clean schemas, rename and cast columns.
Added 'Append' mode to Save as Table.
Added 'Maximum distance' setting to K-Nearest Neighbors.
Added Extract from JSON for extracting values from JSON columns.
Added 'Mode' setting to H3 Polyfill and Quadbin Polyfill components.
Improvements:
CARTO Builder now only loads essential properties from tables or SQL query sources when they're needed in the map (styling, interactions, etc.), instead of loading all columns. This will increase performance for most maps, and reduce the volume of data processed by the connection.
Enhanced keyboard accessibility in Builder for viewers on maps shared with organization/groups or publicly accessible.
All container images were migrated from Google Container Registry to Artifacts Registry.
Removed max-age HTTP header for statics served from workspace-www container
Other internal changes and refactors, mostly to improve stability for Maps API and connections.
Widgets filtering has been migrated to server-side for those linked to dynamic tiling sources, enhancing performance and accuracy.
Fixes from the last release:
Fixed a problem where idle connections to PostgreSQL were not being closed after cancelling tile requests from Maps API.
Fixed a problem creating connections using Workload Identity in CARTO instances running in GKE.
Known issues:
Users that requested to join an organization won't be able to join a new organization if the previous request was rejected. This issue will be fixed in upcoming versions.
New:
Improvements:
Fixes from the last release:
Fixed an issue on Maps API that prevented it working properly on docker compose versions below 2.0
New:
Improvements:
Fixes from the last release:
Fixed several broken documentation links in Workflows components.
New:
Enhanced temporal precision: You can now extract insights using custom time intervals and enjoy greater granularity, resulting in more accurate analyses.
Analysis of multiple time series: You can now analyze multiple time series simultaneously within the widget, enabling seamless concurrent analysis over time.
Enrich Points, Enrich Polygons, Enrich H3 Grid, and Enrich Quadbin Grid. Each of them allows for enriching different types of geospatial data, and all of them allow using both a Data Observatory subscription or a custom table as a source for the enrichment data.
We have also released new components for advanced Statistics and for Retail Analytics, initially supported in Google BigQuery: Getis Ord, Getis Ord Spacetime, Moran's I, Local Moran's I, Geographically Weighted Regression, and Commercial Hotspots.
These additions to Workflows will make it a lot easier to leverage data enrichment and advanced statistical capabilities in CARTO, integrating these complex processes as just another step in a workflow.
Improvements:
Null values are omitted on Spatial Indexes sources both when rendering and on Widget calculations.
Snowflake connections can be bypassed correctly when using an HTTPs proxy.
Fixed bug that caused autosaving in Workflows to be very slow.
Fixed bug with GeoJSON and JSON inputs in Workflows components.
Fixed bug with 'Stop' button in Workflows not being responsive.
Known issues:
Inconsistent behavior while working with Create Isolines workflows component and their temporal tables in Redshift.
New:
Improvements:
Fixed a problem to avoid full scans on Redshift tilesets.
Fixed some import issues with large files by increasing the memory requirements of the import-worker container from 4GB to 8GB and from 1000Mi CPUs to 2000Mi CPUs.
When previewing a table on Data Explorer and Workflows you can now preview up to 200 columns, instead of 20.
Limit when adding values from sources on SQL Parameter Text type on Builder has been increased from 20 to 1000 values.
Known issues:
Creating a BigQuery Oauth connection results in a callback loop when using certain browser versions. The issue doesn’t appear with the following version: Firefox >= 114.0.2, Chrome < 114.0.5735.33.
New:
Update nodes with more relevant and descriptive names.
Improvements:
If an internal (hidden) organization setting that disables sharing maps in public is enabled, it will now remove the public sharing option, instead of removing the entire sharing functionality.
Additional custom markers.
Router nginx component could be customized with new parameters related to buffers and max payload requests size.
Improved Maps API stability in high-concurrency environments.
Known issues:
Creating a BigQuery Oauth connection results in a callback loop when using certain browser versions. The issue doesn’t appear with the following version: Firefox >= 114.0.2, Chrome < 114.0.5735.33.
New:
Support for HTTPS Proxy: CARTO self-hosted now supports working behind an HTTPS proxy. Limitations: the proxy certificate must be issued by a recognized Root Certificate Authority (CA) that is trusted by both the underlying Node.js and Ubuntu/Debian frameworks. Snowflake is not supported.
Improvements:
Reduce dynamic tiles timeout to 20 seconds.
Increase the default pool size of connections to Redshift from 5 to 20 per container.
Enterprise customers might receive an in-app NPS survey. All requests to a service called AskNicely are related to this integration.
Widgets linked to simple features are now calculated on the server side.
We’re introducing a new mode to share Databricks connection, called “Require viewer credentials”, where all viewers will be required to authenticate independently to use the connection. Since the Databricks connector is in beta, we’ll add more details to the release notes when we enable this mode for other providers.
To ensure backward compatibility with older versions of Kubernetes, we have added a new value called kubernetesPolicyVersion in the Helm chart.
Fixes from the last release:
Fixed an issue where Kubernetes deployments were not able to import files using a BigQuery Oauth connection.
Fixed an issue where using an external HTTP proxy, some services didn’t apply the NO_PROXY variable properly.
Fixed an issue where using an external proxy, some services had issues pulling messages from Pubsub after an outage of the proxy service.
Fixed a potential issue where feature flags would return the default value instead of the actual value due to missing variables.
Fixed an issue with PostgreSQL connection where under specific circumstances, related to the connection pool, requests would start failing.
Fixed access to Data Observatory data and demo data for the CARTO DW in non-US regions.
Known Issues:
Certain browser versions may experience a callback loop when creating a BigQuery OAuth connection. This issue is not observed in Firefox versions >= 114.0.2 or Chrome versions < 114.0.5735.33.
Users who have been rejected from joining an organization by an administrator are currently unable to request to join another organization.
An error appears after creating a new Databricks connection, although the connection was created successfully.
Sharing a connection or a workflow using the only with specific groups option doesn’t work.
Sharing a workflow directly from the canvas feature does not work as expected.
An error occurs while importing geopackage datasets in Snowflake.
New:
Improvements:
Refresh buttons have been added in several places when listing and previewing data, to prevent cache issues.
We’ve added additional optional parameters in Imports API to support upcoming features.
We’ve made available a private Beta Version of a new feature: Basemap selector for public maps. Please contact the team if you’re interested.
Add support for PodDisruptionBudget (disabled by default). A PDB limits the number of Pods of a replicated application that are down simultaneously from voluntary disruptions
Disable upstream buffering in the router component for APIs that uses streaming to transfer data to the client. We disabled it for the self-hosted behavior to be aligned with the SaaS.
Other minor changes and improvements
Fixes from the last release:
Fixed potential issues where containers would not shutdown correctly after receiving SIGTERM signal by:
Start docker containers in Exec form. So the process will take up PID 1 inside the container and Kubernetes will be able to send signals to the pod.
Add terminationGracePeriodSeconds to all pods. Now, Kubernetes will wait for a specified time called the termination grace period before killing the containers when it needs to stop them, so the APIs will be able to finish their work before shutdown in a correct way.
Fixed an issue that would make embedded maps not work outside of the self-hosted domain. Now the router component returns the header X-Frame-Options = “ALLOW” for public map requests.
Fixed an issue when sending requests to SQL API larger than 1 Mb. Now you can send requests up to 10Mb of payload.
Fixed an issue while trying to download helm customer packages using the carto-selfhosted-download.sh tool
Fixed a logout problem where users with SSO would be stuck in a logout-login loop under specific circumstances.
Fixed minor issues with GEOMETRY type handling in Redshift.
Fixed an issue where the COUNT operation wouldn’t be available for Quadbin layers in Builder.
Fixed an issue where the dynamic aggregation of points into Quadbin wouldn’t work for Snowflake and PostgreSQL connections under specific circumstances in Builder.
Fixed an issue where widgets would not be accurate with tileset data sources under specific circumstances.
Other minor fixes
New:
Improvements:
The appearance of some screens in the login/signup contexts have changed to match our design system.
Import API and LDS API can now be selected and used as allowed_apis in tokens created via Tokens API.
Performance improvements related to the ability to cancel queries and manage timeouts for unused tiles in maps.
Removed support for fixed radius (meters) in Builder.
Several performance improvements for Snowflake connections, including better handling of a connection pool for Maps API and SQL API and faster queries for point-based data sources.
Database parameter is now mandatory when creating Snowflake connections.
Several improvements when importing files:
Longer timeout for importing larger files (from 10 minutes to 1 hour)
Better error handling, with improved error tolerance and clearer error messages.
The resulting tables in Snowflake after importing are now correctly optimized.
Other minor changes and improvements
Fixes from the last release:
Fixed an issue where users could attempt to delete maps owned by a different user.
Fixed an issue where invitations could be duplicated due to case sensitivity.
Fixed an issue with Builder SQL console where the spatial data type would remain cached.
Fixed an issue where an OAuth connection could be marked as shared under specific circumstances.
Fixed an issue with quantiles calculation not being consistent in static tilesets versus dynamic tiling.
Fixed several issues with the map/connection sharing dialog, where it would not behave correctly under some circumstances.
Fixed an issue where a demo dataset for retail industry use cases would appear to non-retail industry users.
Fixed an issue with the generation of “Intersect an Aggregate” SQL Analysis for Redshift in Builder.
Fixed an issue to support resolution levels lower than 4 for H3 layers and lower than 6 for Quadbin layers in Builder.
Other minor fixes
The release notes for releases prior to 2023.3.31 can be found:
View this release on GitHub -> |
: Now available in both the and as Workflows components. Users can perform , , and calculations via CARTO’s standard providers.
: AI Agents in Builder are now available as part of our Public Preview. By default, this functionality is disabled for all organizations to ensure full control over feature adoption. However, any Organization Admin can enable AI Agents as needed via the organization settings. In self-hosted (SH) environments, you’ll notice that a default OpenAI API Key is provided by CARTO, which supports immediate testing. If preferred, this can be easily overwritten with your own key to align with your organization’s security and compliance requirements.
: 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 and Snowflake—all within CARTO.
: 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.
: 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 to list all maps, workflows, and connections in a CARTO organization, bulk delete of multiple assets with a single API request and transfer the ownership of an asset (map, workflow, or connection) to another user
View this release on GitHub -> |
CARTO Workflows for Databricks leveraging native Databricks workflows.
With , 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.
We've introduced the ability to . Previously, maps could only be shared with the entire organization, specific user groups, or made publicly accessible via a link.
Snowflake users can now connect to their Data Warehouse using .
The allows you to aggregate those features in your layer visualization and interactions, improving performance while keeping access to detailed insights.
View this release on GitHub -> | New:
We’re thrilled to announce a : A completely redesigned experience that makes it even easier to browse, discover and subscribe to spatial datasets. Additionally, administrators in CARTO can now check their entire list of Data Observatory subscriptions from CARTO Workspace > Settings
: Developers can now build completely custom, performance and interactive widgets on top of spatial index sources (H3 and Quadbin) using CARTO + deck.gl
: A new connection method that establishes a trust relationship between CARTO and your Google Cloud projects, giving you flexibility to grant granular permissions in CARTO without having to export service account keys
Advanced Orchestrated container deployments of CARTO Self-hosted now support .
View this release on GitHub -> | New:
: Named sources enable applications communicate with CARTO without exposing SQL queries in the code or through the network requests.
: 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.
View this release on GitHub -> | New:
: 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.
: 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.
View this release on GitHub -> |
: Users can now export data from any node in their workflow via a new export button. The Send by Email feature now works without attached data and allows specifying custom bucket locations. Additionally, exporting to buckets now requires users to provide their own secure bucket locations, replacing the use of public buckets.
: 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.
: Many times, a single basemap doesn't fully meet all of your mapping needs. Now, with the new 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.
: 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.
: 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.
Admins can now enforce Single Sign-On as the only available authentication mechanism. This is available as a .
generally available.
View this release on GitHub -> |
: Administrators in CARTO now have a brand new section in Settings (Quotas & Activity > Activity Data) where they can export a comprehensive collection of activity logs and API usage extracts. This data can be used for engagement monitoring, audit logs, quota consumption analysis, and more. Additionally, this data can also be exported via API. Learn more about .
: Users can now require viewer credentials on their OAuth Snowflake connections, which forces everyone using the connection to authenticate with their own personal credentials.
View this release on GitHub -> |
Added a new .
(Private Preview): The installation and management of extension packages containing custom components for Workflows is available for preview. Extension Packages can be created using this .
: 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.
: We've introduced new functionality in Builder to dynamically visualize your point data as H3 aggregations, helping you gain deeper insights and uncover trends more effectively.
flow when deleting and downgrading users.
to client organizations.
View this release on GitHub -- > |
Re-designed Developers section in Workspace: that connects Developer resources with the CARTO Workspace, including a new Overview, a simplified Credentials system to manage authentication in your apps, and a new list of API-enabled Workflows.
New credentials system: We have renamed Developer Applications to OAuth Clients, and we’ve consolidated them with API Access Tokens under the new section.
Please note that developer credentials created before you upgrade to this version will be duplicated as applications to maintain the same visibility level as previously. .
: Admin users at CARTO can now upload custom basemaps and tailor the basemap gallery options available to Editor users in Builder. To learn more about how you can upload custom basemaps to the CARTO platform and the supported formats, check.
: This new feature allows you to render large 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 .
: 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.
: A variety of features designed to simplify and expand the ways you can import data into your workflows, providing greater flexibility and functionality.
: A new feature for Workflows that brings the ability to connect your workflows with external API services
: new features that are set to enable working with raster data in CARTO.
New that leverages SQL Warehouses to support Tileset and H3 tables visualizations in Builder and Data Explorer
: Use Workflows to generate tilesets to optimize visualization of very large data sources.
: Users can now create, apply and filter maps and workflows by tags in the workspace.
CARTO Self Hosted now supports in installations that use KOTS.
View this release on GitHub --> |
: Maps created with Builder can now be embedded into other websites even when they’re shared only with the organization or with specific groups. Before, only public maps could be embedded.
: This new feature simplifies the map-making process by letting Editor users switch seamlessly between editing and previewing. With Preview mode, 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.
: 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.
: With this new capability, analytical pipelines created with Workflows can be scheduled so they are executed on a specific period like 'hours', 'days', 'weeks', 'month' or 'custom'. CARTO leverages native scheduling capabilities on each data warehouse to provide this functionality in all CARTO Data Warehouse, BigQuery, Snowflake and PostgreSQL connections.
:
to split larger geometries into easier-to-process smaller features.
New UI for component
: Create composite scores with the supervised method using this component..
: Create composite scores with the supervised method using this component. .
Enrichments are moving to Workflows: the dedicated UI experience will stop being available in future CARTO Self-Hosted versions. In this version, a warning will appear if the organization was created earlier than April 1st.
Usage Quota weights have been updated. Widgets using SQL API consume now less Usage Quota (from 10 to 1), and Maps API weight will gradually change aligning with performance optimizations. .
View this release on GitHub --> |
: We have improved the experience of new users when they open a shared map or shared workflow for the first time, with automatic access when applicable (eg: successful SSO login) and a clearer user experience in all cases.
: We have added a new column to the Users & Groups table (inside the Organization settings), where admins will be able to see the authentication method used by each user (SSO, Username/Password, Google Account, etc).
: comprehensive set of new features in CARTO Workflows designed to provide the ability to trigger the execution of your workflows by calling an API. After some time when this feature was only available on-demand, it is now enabled to all users with this CARTO Self Hosted version.
: CARTO Builder has expanded its URL parameter 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.
Increased RAM memory limits for . Now each container can consume up to 6Gb instead of 4Gb.
View this release on GitHub --> |
: We've upgraded the export functionality in Builder maps, shifting the data export process to work in server-side mode for an enhanced efficiency and data integrity. This improvement ensures a more reliable data retrieval experience. Additionally, when exporting data as CSV, it now includes the geometry column in WKT (Well-Known Text) format, if applicable. This enhancement simplifies data handling and boosts compatibility with various geospatial tools, making integrations smoother.
: We have added a new component to Workflows that leverages capabilities to allow embedding Generative AI functionalities into your geospatial analytical pipelines. It can be used to interpret results from an analysis, using different variables on your data to compose a prompt that will be evaluated on each row. With this new addition, Generative AI capabilities are handy and readily available from Workflows.
The process to enable (or disable) the CARTO Data Warehouse using an environment variable now affects all organizations in your self-hosted instance, including existing organizations. Read more about it in the self-hosted guide.
View this release on GitHub --> |
: The distance measure tool that will allow users to measure distances between two points on their maps. This new functionality is ideal for a diverse range of use cases, from planning tasks to gaining a deeper understanding of spatial relationships between various map elements.
: Administrators can now configure an integration that allows all users in the organization to create Snowflake connections via OAuth. The integration can be set up to use Snowflake OAuth (using Snowflake credentials) or External OAuth (using credentials from a third-party such as Azure Active Directory or Okta)
: New, sleeker design for the results panel in Workflows; it includes some new features, focused on usability and better data exploration.
: New component that allows exporting the result from any node in a workflow to a storage bucket.
The CARTO Data Warehouse is now optional and disabled by default for new organizations, reducing the network requirements for Self-Hosted instances running behind a VPC or proxy. When this CARTO-managed data warehouse is disabled, onboarding materials and UI-based Data Observatory features won’t be available. The CARTO Data Warehouse can be enabled at any time by .
Placeholders ($a, $b, $c, $output) in "Custom SQL" and "Call Procedure" components in Workflows need to be quoted manually. .
"Import from URL" component in Workflows has been deprecated in favor of a new type of imported data source. .
Added new options to "" components in Workflows.
"" component now accepts a destination table name.
"" component now supports date/timestamp columns.
View this release on GitHub --> |
: Users can now benefit from a new type of widget in Builder, the Pie Widget. This widget can be used to quickly and easily analyze data proportions and category weights, empowering users to make more informed decisions by providing a clearer view of their data.
: We have upgraded our Time Series Widget in Builder to boost your temporal data analysis experience. These enhancements bring a new level of customization to your data exploration, offering:
: A workflow can be executed via an API call, which allows merging workflows with bigger processes, running analytics pipelines from external applications, and further integrations that enable a wide range of use cases. This includes in API executions.
: The export functionality allows downloading a .sql file with the stored procedure code that is executed by a workflow. These files also contain all the metadata that is required to restore a workflow by importing it to a CARTO account.
: We have released a new set of components in Workflows for Data Enrichment:
: With this new advanced setting in the connection's form, users can specify the location of the Analytics Toolbox location that will be observed in SQL queries generated by UIs in the CARTO. In Self Hosted installations, the default value can be set using an environment variable.
View this release on GitHub --> |
: We have just made Data Observatory subscriptions available in the Data Sources panel in Workflows.This will make premium and public dataset a lot easier to work with: just drag and drop your available samples or subscriptions to the canvas and start building your workflow.With this new addition to Workflows, the largest catalog of curated geospatial datasets is readily available to be integrated with your cloud native analytical pipelines with just a few clicks.
: This upgrade takes our existing Map Description feature to a whole new level. With Richer Map Descriptions, users will be able to not just add text; but craft a more engaging user experience. The support for Markdown syntax allows you to include various text formats, headers, links, images, and even bullet-point lists, elevating the user's understanding and interaction with your map.
: Leveraging the Numeric SQL parameter, users can now seamlessly retrieve single or pair numeric values from a Control UI to update the underlying data sources. It's an excellent option for those requiring to filter data by specific numeric ranges or adjusting analytical outputs based on numerical inputs.
: With this release, developers building applications with CARTO can now provide a seamless experience in their applications to their Single Sign-On (SSO) users, even if it’s the very first time they access CARTO. You’ll find the necessary changes to be made in the apps in our documentation.
; Developers can now control the visibility of the Applications created using CARTO, including the options to make an application visible only for specific groups inside the organization.
; Administrators have an easier and more scalable way to manage the roles of CARTO users, with a fully automated system that assigns each user a role depending on the groups they belong to. Admins can map groups to roles under Settings > Users and Groups. This feature requires SSO and Groups enabled.
We added a hidden organization setting to completely disable the “Export data from viewport” feature for all users. Please if you’re interested in disabling exports.
View this release on GitHub --> |
: Users can now define a custom schema when importing files from their computers or from a URL. CARTO will generate a preview with the columns to be set up. This functionality is available also through new endpoints and parameters in the .
: While working with Workflows, in some occasions a component needs to be defined as a custom geography (point, line or polygon). This is currently the case with "" but this tool will also be used in other components that might need a custom geospatial input.We have developed a new tool, accessible through the "Draw features" button to define custom geographies as inputs for components.
: This new feature provides advanced capabilities for users to tailor calculations and derive precise insights from their data using SQL Expressions. With custom aggregation operations, users have the flexibility to define calculations that align precisely with their unique analytical requirements. They can incorporate business-specific formulas and apply complex mathematical operations to single or multiple columns from their data source.
: We have just added a couple of new features in Workflows that are going to improve a lot the explainability of your multi-step analytical pipelines.
Rich notes supporting syntax.
: This feature now includes the ability to search for locations using coordinates. Simply input latitude and longitude values, and instantly visualize the corresponding location on the map. Whether you're exploring remote areas, analyzing specific points of interest, or seeking valuable insights, our coordinate search feature empowers you to navigate with precision and seamlessly uncover new possibilities.
: Organizations with access to the Appearance customizations (also called “custom branding”) will now be able to also remove the CARTO-branded footer from their public and embedded maps. This is an organization wide setting that the admin can enable or disable. Additionally, the admin can select if they want new users to receive the generic CARTO onboarding, for further experience customization.
: “Viewer credentials” is a new mode of sharing connections that require all users to provide credentials before using that connection, whether it is to build maps or just to view them (as well as previewing data or opening workflows). By leveraging viewer credentials, you can leverage row-level security and other policies coming from BigQuery, as well as collaborating on Builder maps.
Dynamic Tiling V2 now available: A collection of changes to the queries that Maps API runs on different data warehouses in order to produce faster and more visually complete vector tiles. For those using CARTO for React, note that this functionality has been incorporated from versions CARTO for React v2.1 or 1.6 onwards. If you are using an older version, an upgrade is necessary. For more info visit our .
View this release on GitHub --> |
: this feature allows users to automatically zoom in and center the view of the map based on their current location, providing them with a convenient and immediate view of their surroundings.
: you can now calculate routes between sets of origins and destinations, supporting different transportation modes and other advanced parameters. This is available via new endpoints in the LDS API and, outside of your deployment, in the latest Analytics Toolbox version.
: A new action has been added to the Data Observatory subscription pages, to download the data locally as csv files.
: We have added a new set of components. The majority of components in this new batch are oriented towards providing more flexibility when manipulating and getting your data ready for the analysis.
View this release on GitHub --> |
: Automate data preparation & analysis pipelines with our no-code workflow design tool. Exporting in Workflows is disabled by default in Self-Hosted instances.
: SQL Parameters are placeholders that can be used on any SQL Query data source in Builder. Once defined, the actual value for the parameter can be set through a control UI, allowing easy manipulation of the data source by both Editor and Viewer users.
: developers now have an easy way to create and manage their API Access Tokens, used for authentication in CARTO for Developers.
: CARTO will now detect automatically whenever a table could perform better thanks to geospatial optimizations, that can be applied from Data Explorer.
: CARTO Builder now supports adding labels to point layers loaded via tiles, with a set of improved features.
: admins can now select what is the default role for every new user that signs up to their organization.
: admins that have previously set up an SSO integration now have the ability to let their users skip all the onboarding steps, for a seamless signup experience.
: we have enabled an easy way of getting authorization (via a Google account) to the console of their CARTO Data Warehouse.
Beta Support in Maps API for raster sources created via Beta .
: now CARTO self-hosted supports working behind an external HTTP proxy.
Now you can (a debugging service) for www components by customizing your environment variables.
View this release on Github --> |
: There’s a new API-based usage quota, the LDS quota is now annual and combined, plus other quota-related changes. This feature brings a new component named router-metrics that will send aggregated and anonymized API usage metrics periodically.
: A set of new analyses have been added to Builder, to reach the same level of support on different data warehouse
: the feature has been released to General Availability, with no meaningful changes for self-hosted deployments, that will still be required to setup an AWS S3 bucket.
: TrackJS is a service used by CARTO for JavaScript error logging. It is now optional for self-hosted deployments.
for Docker Compose:
for Kubernetes: