What's New

What's New

improvement
APIs

We have released a few changes in how we cache API requests in the CDN that will produce a significant improvement in the overall performance of the platform; specifically applying to Builder maps and applications developed using our APIs. Learn more about such changes in our documentation for developers at api-docs.carto.com; each end-point in Maps API and SQL API now contains a reference about our caching strategies.

In Builder, users have new a couple of new features:

  • “Refresh data source”: to make sure users get non-cached versions of the data. Note that with this option your map will be skipping the CDN and getting the data each time from your data warehouse.
  • “Refresh data source every X”: to allow the user to control the update frequency of the data displayed on public maps.

New interface to manage invitations and requests

improvement
APIs

A couple important fixes have been implemented to our Dynamic Tiling strategies. Dynamic Tiling is the technology CARTO has developed to dynamically generate tiles for medium sized dataset and layers loaded as SQL Queries from your cloud data warehouse.

  • When working with points, many times widgets were not showing data due to our “visual aggregation” strategy when points were very close to each other. We have now removed this type of aggregation, and we are only applying a limit of 200k points per tile to prevent performance issues. If now you encounter widgets not showing data, you just need to zoom in to reduce the number of points per tile.
  • With our previous strategy some polygons or lines that were falling in the intersection of multiple tiles were splitted for visualization purposes, which was making the same data point count multiple times in widgets. We have solved this problem by asking the user to identify a unique id property for the data source at the time of creating widgets.

New interface to manage invitations and requests