The value of this channel can be a number or a string "height" for the height of the plot.
Y coordinates of the marks, or height of vertical "bar" and "area" without specified y2 or height. If tooltip is true or represents half of the band.The tooltip text string to show upon mouse hover or an object defining which fields should the tooltip be derived from. Number | String | Boolean | TooltipContent | ExprRef | Null For example, a bar mark with "style": "foo" will receive from and (the specified style "foo" has higher precedence). Note: Any specified style will augment the default style. For example, a bar mark will have style "bar" by default. Any mark properties explicitly defined within the encoding will override a style default.ĭefault value: The mark’s name. If style is an array, later styles will override earlier styles. A style is a named collection of mark property defaults defined within the style configuration. If specified, this property determines the “aria-label” attribute.Ī string or array of strings indicating the name of custom styles to apply to the mark. If false, the “aria-hidden” attribute will be set on the output SVG element, removing the mark item from the ARIA accessibility tree.Ī text description of the mark item for ARIA accessibility (SVG output only). This could a primitive mark type (one of "bar", "circle", "square", "tick", "line", "area", "point", "geoshape", "rule", and "text") or a composite mark type ( "boxplot", "errorband", "errorbar").Ī boolean flag indicating if ARIA attributes should be included (SVG output only). Note: If mark property encoding channels are specified, these mark properties will be overridden. For example, point marks support shape and size properties in addition to these standard properties. Additionally, some marks may have special mark properties (listed in their documentation page). The rest of this section lists standard mark properties for primitive mark types. To customize properties of a mark, users can set mark to be a mark definition object instead of a string describing mark type. Mark Definition Object // Single View Specification Supported composite mark types include "boxplot", "errorband", "errorbar".įor example, a bar chart has mark as a simple string "bar". In addition to primitive marks, Vega-Lite also support composite marks, which are “macros” for complex layered graphics that contain multiple primitive marks. However, line and area marks represent multiple data elements as a contiguous line or shape. In general, one mark instance is generated per input data element. Vega-Lite supports the following primitive mark types: "area", "bar", "circle", "line", "point", "rect", "rule", "square", "text", "tick", and "geoshape". The mark property of a single view specification can either be (1) a string describing a mark type or (2) a mark definition object. They provide basic shapes whose properties (such as position, size, and color) can be used to visually encode data, either from a data field, or a constant value.
Marks are the basic visual building block of a visualization.
0 kommentar(er)
