Data Sources
Last updated
Was this helpful?
Last updated
Was this helpful?
When building a widget, you always need a data source. The data source includes all the necessary connection and authentication parameters.
Data sources are available through the CARTO submodule in deck.gl, and you can re-use your existing sources from CARTO + deck.gl layers, or build your own sources exclusively for widget use.
Currently, widgets are compatible with the following sources, using server-side calculations when available, and client-side calculations as a fallback.
vectorTableSource
✅
Server-side
vectorQuerySource
✅
Server-side
vectorTilesetSource
✅
Client-side
h3TableSource
✅
Server-side
h3QuerySource
✅
Server-side
h3TilesetSource
✅
Client-side
quadbinTableSource
✅
Server-side
quadbinQuerySource
✅
Server-side
quadbinTilesetSource
✅
Client-side
rasterSource
✅
Client-side
boundaryTableSource
❌
-
boundaryQuerySource
❌
-
If you plan to use the same data sources in your deck.gl layers and in your data widgets, then your existing CARTO + deck.gl data sources are totally compatible with widgets
When using , having a layer is not a requirement. You can specify your source and build your widget without any additional layers. This is a powerful pattern to expose additional insights, use global datasets for filtering while rendering aggregated datasets, or simply to achieve advanced use cases.