Datasets describe the data model of a project. Each dataset represents a database table. They also define the constraints and links between all other datasets in a project.

There are three types of datasets:

  • dwh () type is a data warehouse service dataset type, it references a table in a relational dwh database, which may contain various kinds of data (e.g. orders, customers, administrative units...)
  • vt () type is a vector tile dataset type, it references a vector tile service, which serves vector tiles that are displayed over the base map (CleverMaps vector tiles are hosted on Mapbox)
  • h3Grid () type is a H3 grid dataset, it represents a grid visualization, where the geometries are generated on the fly by the application (see Tutorial 8 for more info, and H3 grid spatial index by Uber)

Datasets of dwh type also have a subtype, which defines the type of data they contain. There are five of them:

  • basic () subtype is used to contain data which are not to be visualised on a map (e.g. orders, clients, or demography)
  • geometryPolygon () subtype contains data which represent polygons on a map (e.g. administrative units, delivery zones)
  • geometryPoint () subtype contains data which represent specific points on a map (e.g. shops, postcodes, or POIs)
  • geometryLine () subtype contains data which represent lines on a map (e.g. routes, pipelines)
  • date () subtype is a special subtype not to be used in a regular way, it is used to describe datasets the can-dim-dates data dimension

Datasets also subject to various validation checks. Datasets with ref.subtype other than basicgeometryPolygon, geometryPointgeometryLine and date must also contain properties.featureTitle key, which defines the format of visualisation of one row of the dataset (used in tooltips or the date picker). Datasets with geometry must have a link to a vt type dataset describing that geometry. More about these checks in the examples below.

Datasets are directly referencing other datasets via foreignKey property or geometry key. They are referenced by URL in marker selectors, as some datasets represent a group of points in the map. Dataset properties, declared in are referenced by name in metrics, view filters and indicator drillsReference integrity of the data model is also enforced. In order not to break this integrity, is not possible to delete a dataset, which is referenced in another dataset, either by foreignKey, or geometry.


Example of a dwh dataset with basic subtype. This subtype typically indicates a dataset, which does not have a geographical information - so it is not possible to visualise it on the map.

This dataset describes baskets (i.e. orders) from the Retail Solution Demo project. Each basket represents a purchase made by a customer, either offline in one of the shops, or online in the e-shop. You can see that it contains various purchase properties like "Date", "Purchase value", "Delivery type", etc.

This dataset describes the geometries of UK districts. These geometries are served to the application and visualised as polygons on the map. This geometry is referenced in a dwh dataset district in the examples below.

This dataset represents H3 grid visualization on resolution 8. It's very similar to vt dataset, apart from resolution you only need to define appropriate zoom. See Example to see how to link this dataset to a geometryPoint dwh dataset.

Additional syntax examples

This dwh dataset represents locations of stores. Each store has a location (lat and lon properties), and is visualised by a marker. So, in this case the "subtype" is "geometryPoint".


This dataset represents dwh data of the districts of the United Kingdom. Districts have a geometry, so they can be visualised as polygons on the map. Thus, "subtype" is "geometryPolygon".

The dataset also contains information about its data sources. The source data for UK districts was provided by Office for National Statistics under the Open Government license. For more info, see the syntax below.


This dataset represents a gas pipeline network. The pipelines are visualised by lines, so "subtype" is "geometryLine". However, remember that the actual geometries are described by the pipelines_geojson vt dataset.


This is an example of the date subtype dataset. This subtype is almost exclusively used in the can-dim-dates dimension, used for date management and filtering in a project.

This subtype also enforces the presence of the featureTitle property. The property selected as a featureTitle defines what date will be show in the date picker, or the time series indicator drill block. This is useful in cases when you want to use the date names in different language. The can-dim-dates dimension currently offers either English (date_en) or Czech (date_cz).


This dataset has the displayOptions.valueOptions object set on some properties. These are the properties that are also used in a categories block in any linked indicator drill. This gives you the ability to use the qualitative visualization (more info in Tutorial 5: Drilling down on the data).

For example, the baskets.on_off_name property has two possible values: "Online" and "Offline". So the objects with prevailing "Online" value will become green, and objects with prevailing "Offline" will become red.

This is a simple dwh geometryPoint dataset which contains addresses with latitude and longitude. To visualize it using H3 grid, simply add some h3Grid datasets and specify them in the ref.h3Geometries array.

Notice the concat function in featureTitle. This function allows you to concat multiple properties and text to be displayed in the dataset's features tooltip and headers.

Key description


These properties define the content of a tooltip shown on marker/area hover (example), and the details of a dataset (example).

The properties can be found on the common syntax level. The syntax example can be found in the "Example of a dwh dataset type with geometryPoint subtype" above.


defines the tooltip title shown on hover



defines the tooltip subtitle shown on hover

featureAttributesarraydefines the properties which will be displayed in the details

defines the property which contains accuracy radius value

see visual representation below

properties.featureTitle & properties.featureSubtitle

The syntax of featureTitle and featureSubtitle is identical.


property - a dataset property

function - function to apply to a dataset property (currently only concat)

[property, function]



name of the dataset property, or the function (currently only concat)

contentarrayallows you to nest properties in functions


The definition of the dataset details. Allows you to display properties of a dataset itself. These can be properties which are not explicitly to be used in a metric (e.g. store owner, opening hours, area, etc.).


property - a dataset property

expression - expression to format multiple properties (e.g. lat and lon)

[property, expression]



name of the dataset property

formatobjectobject specifying formatting of the attribute value
layoutstringattribute layout size 

[primary, secondary]



formatting type

[text, number, percentage, email, link]

the number of places after the decimal point (for number type only)

x => 0
symbolstringcustom symbol to display with the attribute (e.g. "m2", "$", etc.)



This object defines an accuracy of a feature. When hovering the feature, a circle with radius specified in given property is shown. See example below.

It's not possible to specify content, otherwise the syntax is identical to featureTitle.


type identifier, always property - a dataset property




name of the dataset property which contains the radius value in meters


In this array, you can specify a list of data sources / licences for each dataset. This includes the licence holder's name, webpage, logo and the link to the licence itself. The unique list of data sources for each project can be displayed by clicking on:

  • the Menu button in the top left corner () and selecting "Data sources"
  • selecting "Data sources" in the bottom right corner of the map window

Name of the licence holder


URL link to the licence holder's website


URL link to the licence holder's logo

preferrably .png, will be downsized automatically



URL link to the licence itself



A reference of a dataset dwh type.

typestringtype identifier, always dwh[dwh]



dwh subtype identifier

[basic, geometryPoint, geometryPolygon, geometryLine, date]

geometry reference to a vector tile dataset

required only for geometryPolygon and geometryLine subtypes


array of references to h3Grid dataset names (see example above)

enables the grid visualization


array of objects specifying the allowed visualizations of the dataset

required only for geometryPoint, geometryPolygon and geometryLine datasets

zoomobjectmap zoom object

name of the actual dwh table this dataset represents

it's derived from the name of the dataset, and _X postfix is added for each full load, where X is the number of the load


primary key of the table - must be one of the dataset properties

should be unique


indicates if the dataset is capable of being categorized in the Filters tool ()

default = true

should be true for fact datasets like "orders", "shops" or "clients", false for additional datasets like "postcodes", "dim_dates" or "price_categories"

[true, false]

indicates if the dataset's data will be indexed for full text search in Search tool ()

default = true for geometry* subtypes, false for basic and date subtypes

[true, false]

array of properties - database table column descriptions

dataset property order must be identical to the order of the data columns

size must be at least 1


Array of objects specifying the allowed visualizations of the dataset. The available visualizations are derived from the subtype of the dataset:

  • geometryPolygon subtype can be visualized by areasgrid or zones visualizations
  • geometryPoint subtype can be visualized by dotmap or heatmap visualizations
  • geometryLine subtype can be visualized by line visualization

For more info, see the additional syntax examples above.

typestringtype of the visualization[areas, grid, zones, dotmap, heatmap, line]

Array of properties describing database table of a dwh dataset.

namestringname of the column as it will be referenced in other objects(a-z0-9_-)



human-readable title of the column


name of the column as it is in the database table


column data type

detailed description in the table below

[integer, bigint, decimal, string, boolean, date, latitude, longitude, h3_grid]

name of the dataset, whose primaryKey is referenced by this foreignKey

if this key is mentioned, type must be string


indicates whether it's possible for this property to be added to a filter

default = true

[true, false]

description of the property which appears in Filters ()


options that specify how the property will be displayed

The displayOptions object allows you to specify how the property will be displayed. See the example above.

valueOptionsarrayassigns colors to values of the property

In this array, we can assign colors to specific values of the property. The valueOptions array allows you to set your own colors for the qualitative visualization. See Tutorial 5: Drilling down on the data for more info.

valuestringvalue of the property(*)

predefined color of the property

(warning) either color or hexColor can be specified

[purple, green, orange, blue, turquoise, pink, red, lime, brown, yellow]

hex color code of the property (e.g. #E8493F), see more about hex color codes

(warning) either color or hexColor can be specified


weight (or "width") of the property

(warning) for lines visualization only, see the example

x => 0

pattern of the property

(warning) for lines visualization only, see the example

[solid, dot, dash, longdash, dotdash]

Dataset property data types


a whole number

4-byte signed number, range: 2-31 .. 2+31

-1000000, -120, 0, 1, 2, 42, 2147483648

large range integer

8-byte signed number, range: 2-63 .. 2+63

-1000000, -120, 0, 1, 2, 42, 2147483648, 9223372036854775807

decimal number with precision and scale parameters:

decimal(precision,scale) ~ decimal(10,2)

-1215.0146, 1.02, 4.57, 9546.4164563

a sequence of characters

variable size, limit: 255 characters

"banana", "CleverMaps", "E=mc2", "!@#$%^&"

Boolean data type, has two values only

1-byte size

true, false

ISO 8601 date format (preferred), more available formats can be found here

4-byte size, range: 4713 BC .. 5874897 AD

1997-01-30, 2015-01-05, 2018-03-19


a geographic coordinate specifying the north-south position of a point on Earth

longitudea geographic coordinate specifying the east-west position of a point on Earth16.6057850


A reference of a dataset vt type.

typestringtype identifier, always vt[vt]

absolute URL link to the location of the vector tiles


map zoom object


Set desired zoom levels for the vector tile datasets.

minintegerminimal available zoom level2 .. 18



maximal available zoom level

2 .. 18

optimal zoom level

2 .. 18

zoom level from which the dataset's feature will be visible

(warning) this property works only for dwh datasets

2 .. 18


A reference of a dataset h3Grid type.

typestringtype identifier, always h3Grid[h3Grid]

resolution of the grid

2 .. 10

map zoom object


Set desired zoom levels for the h3Grid datasets.

minintegerminimal available zoom level2 .. 18



maximal available zoom level

2 .. 18

optimal zoom level

2 .. 18

Visual representation

The data model which the datasets describe, can be considered their visualization. It can be viewed in the application by clicking the Account button on the bottom left of a Project page, and selecting Data model. However, this functionality is available only to users with the Admin user role.

Example of a project's data model

This is the visualization of the data model from the Retail Solution Demo project.

Native datasets in this project are baskets, shops and clients. The other datasets were imported from different data dimensions. The datasets in orange were imported from the can-dim-dates dimension. Brown datasets are from a UK administrative units dimension. The dataset demography_postcode comes from a UK demography dimension. The h3Grid datasets are pink.

Detail of a dataset in the data model

If you click on any dataset a detail will be displayed.

The detail of a dwh dataset contains 3 blocks - Overview, Properties and Data load history. Please note that Data load history is diplayed only to administrators of a project. It's also possible to see the Data preview, where you can check if your data have loaded properly, sort or filter by the value of any column.

The detail of a vt dataset contains only the Overview block. It is possible click the link to Mapbox to see a geometry preview.

dwh dataset detailvt dataset detailh3Grid dataset detail

Dataset data preview

Data preview with applied filters to some shop_id, month and on_off_name dataset properties.

Tooltip shown on hover

For geometryPoint and geometryPolygon datasets, a tooltip is shown on hover. The content is defined in

"My Store: Grand Central" is the featureTitle.

"Virgin Trains, 6b 7b, Digbeth, B15" is the featureSubtitle.

Dataset details

The content of dataset details is defined in The details are shown on the dashboard, right under the indicator list.

Feature accuracy

Hovering or clicking down on a feature with properties.featureAccuracy specified.