This topic discusses useful information that will help you to ensure that your data is rendered properly in the 3D heat map chart.
While the Chart control allows you to easily point the chart to your own custom data, it is important that you are supplying the appropriate amount and type of data that the chart requires. If the data does not meet the minimum requirements based on the type of chart that you are using, an error will be generated.
The following is a list of data requirements for 3D heat map charts:
The data set contains at least two numeric columns (up to 255 columns are supported).
The dataset contains at least two rows.
The minimal 2x2 data set is sufficient to define one low-quality heat map tile, where each data value represents the altitude of the tile at each of its four corners.
If you are binding the 3D heat map chart to a series object, see Requirements for Series Binding for information on the series binding requirements.
The chart data is rendered using the following rules:
Data is plotted on a Heat Map chart in terms of latitude, longitude, and altitude. The data is plotted as a surface, with a physical dimension as well as color representing altitude.
Each row represents one latitude. Each column represents one longitude. The numeric data values in each cell represent the altitude at the intersection of each latitude and longitude (row and column).
In a heat map chart, the altitude is a numeric scale, while latitude and longitude are represented as a SetLabelAxis object, so latitude and longitude values will be evenly spaced according to the number of rows or columns in the data source.
The first string column encountered in the data will be used for row labels.
You can include or exclude any column from the chart using the UltraChart.Data. IncludeColumn method.
You can select an alternate column to be used for row labels, and toggle between the primary and secondary labels.
See below for an example data set, along with the rendered 3D heat map chart.<t>Jan</t>