dataproperty to specify the visualization data sources by providing an array of one or more data definitions. A data definition must be an object identified by a unique name, which can be referenced in other areas of the specification. Data can be statically defined inline (
"values":), can reference columns from a database table using a SQL statement (
"SQL":), or can be loaded from an existing data set (
valuesdatabase table type:
sqldatabase table type to load latitude and longitude coordinates from the
sourcetype to use the data set defined in the
sqldata section and perform aggregation transforms:
formatproperty indicates that data preprocessing is needed before rendering the query result. If this property is not specified, data is assumed to be in row-oriented JSON format.
formatis a single string, which must be either
lines. This form is used for all polygon rendering, and for fast ‘in-situ’ rendering of LINESTRING data.
formatis an object containing other properties, as follows:
lines, each row in the query corresponds to a single line.
interleaveddata renders ten lines, all of the same length.
xonly stores points corresponding to the x coordinate and
yonly stores points corresponding to the y coordinate. Make sure that columns only contain a single coordinate if using multiple columns in sequential layout.
sourcedata definition. Transforms are defined as an array of specific transform types that are executed in sequential order. Each element of the array must be an object and must contain a
typeproperty. Currently, two transform types are supported:
true, automatically adds rowid column(s) to the SQL statement where appropriate, enabling the data block for hit-testing using the
false, the data block is not automatically hit-test enabled, and any later
get_result_row_for_pixelcalls return empty hit-test results.